|
|
This chapter describes the basic steps for initializing Cisco Application and Content Networking Software (ACNS) and setting up the Enterprise CDN (E-CDN) application.
If you have received a Content Engine, Content Router, or Content Distribution Manager with ACNS software installed directly from the factory, you need to use this chapter to configure your network settings to get your devices up and running on your network.
The E-CDN application is a constituent of a Content Distribution Network; therefore, setting up the E-CDN application involves configuring at least one Content Engine (possibly more) to communicate with a Content Distribution Manager. ACNS software, if installed directly from the factory, requires that you configure network settings on your Content Engines, Content Routers, and Content Distribution Manager, allocate disk space, enable the E-CDN application from a command-line interface (CLI), and associate your Content Engines and Content Routers with a Content Distribution Manager, as part of the initial startup.
This chapter contains the following sections:
ACNS software boots from Flash memory. When the system boots from Flash memory, it stays network-accessible even when disk failures occur.
After you physically install the hardware and power on your Content Engine, Content Router, or Content Distribution Manager, you must access the ACNS software and perform an initial startup configuration. The initial configuration defines the network settings of your Content Engine, Content Router, or Content Distribution Manager so that your devices become active on your network.
 |
Note If you have upgraded your software from a previous software release to ACNS software, your network configuration is preserved. You do not need to reconfigure your network settings. |
If you have direct console access to the device, you can use the ACNS software initial startup dialog to configure your network settings and to enter the command-line interface (CLI). If you have a Windows-based PC on the same subnet as your Content Networking device, you can use the Installation Wizard that is part of the E-CDN application to configure the network settings of your devices.
|
Note The ACNS software comes with the Installation Wizard installed as part of the E-CDN application. To launch the Installation Wizard, refer to the instructions in the "Activating the Installation Wizard" section of Chapter 1 in the Cisco Enterprise CDN Software Configuration Guide, Version 3.0 publication. |
Once the Content Engines, Content Routers, and Content Distribution Managers are visible on the network, you need to access the device CLI. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI. From the CLI, you can enable the E-CDN application and also configure the Cache application features.
|
Note In order to use the E-CDN application, you must enable it on all devices that are going to run the application. The E-CDN application can be enabled through the ACNS software CLI only. The Cache application is always enabled in the ACNS software. |
After the E-CDN application has been enabled through the CLI, you can use the Installation Wizard to associate your Content Engine or Content Router with the IP address of the Content Distribution Manager being used to administer the E-CDN application. E-CDN proxy settings are also configured from the Installation Wizard after the E-CDN application has been enabled.
Once the Content Engine or Content Router has been associated with the Content Distribution Manager, you can edit the device configuration and access the E-CDN application features using the Content Distribution Manager graphical user interface (GUI). To complete the E-CDN application setup, the Content Engine or Content Router must then be approved within the Content Distribution Manager GUI.
For further information on how to configure the E-CDN application using the Content Distribution Manager GUI, refer to the following publications:
See also "E-CDN Application Commands in Cisco Application and Content Networking Software, Release 4.0."
|
Note The Cache application features can be configured through the CLI or through the Cache application management GUI. (See the "Administering Caching from the Cache Application Management Graphical User Interface" section 5-3.) |
For further information on configuring Cache application features, see "Cisco Application and Content Networking Software Cache Application Features." See also "Cache Application Commands in Cisco Application and Content Networking Software, Release 4.0."
For further information on how to configure the Cache application software, refer to the following publications:
|
Note Some commands in Cache software, Release 3.1 have been changed in ACNS 4.0 software. Therefore, when an apparent conflict exists between similar commands, the information in this guide supersedes all command descriptions for Cache software in releases before the ACNS 4.0 software release. |
In order to configure network settings, you must first gather the required network information for your device and then choose between two different methods of accessing the device:
1. Direct console access to the Content Engine, Content Router, or Content Distribution Manager CLI
2. Network access to the Content Engine, Content Router, or Content Distribution Manager from a Windows-based PC on the same subnet that is running the Installation Wizard
Have the following information available. When you power on the Content Engine, Content Router, or Content Distribution Manager and open a console connection for the first time, you are prompted to provide this information:
To configure network settings, follow these steps:
Step 1 Power on the device and open a console connection.
After the operating system boots up, the following prompt appears:
ACNS boot:detected no saved system configuration
Do you want to enter basic configuration now?
hit RETURN to enter basic configuration:0028
At the appearance of this prompt, a 30-second countdown begins, during which you can respond to this prompt. If you do not respond, the system automatically continues booting.
Step 2 Enter yes, and then enter values for the following fields as you are prompted:
|
Note After the device is connected to the Content Distribution Manager, the password specified in the Content Distribution Manager GUI will overwrite the one specified here. |
After you enter the initial configuration data, the following prompt appears:
Use this configuration? [yes]:
Step 3 If the initial configuration is acceptable, enter yes or press Enter.
The device performs hardware and software initialization tasks and then serves a login challenge that, when answered correctly, launches the CLI. At this point, the initial configuration is complete.
In the following sample startup dialog, administrator entries are shown in bold.
INIT:Entering runlevel:3
Nodemgr started!
ACNS boot:detected no saved system configuration
Do you want to enter basic configuration now?
hit RETURN to enter basic configuration:0028
host name:ce-590
domain name:cisco.com
admin password:*****
re-enter password:*****
Please enter an interface from the following list:
0:FastEthernet 0/0
1:FastEthernet 0/1
enter choice:0
local IP address:172.16.193.247
IP network mask:255.255.255.224
gateway IP address:172.16.193.225
DNS server:172.16.2.133
Use this configuration? [yes]:yes
To configure network settings using the Installation Wizard that is part of the E-CDN application, follow these steps:
Step 1 Follow the instructions in the "Activating the Installation Wizard" section in Chapter 1 of the Cisco Enterprise CDN Software Configuration Guide, Version 3.0 to run the Installation Wizard from the CD-ROM or local hard disk drive.
Double-click the cndwiz.exe file to launch the Installation Wizard.
The Cisco Content Delivery Network Installation Wizard dialog box appears.
Step 2 Click Next to advance to the Select a Device dialog box, which lists all Enterprise CDN devices on the subnet by their device ID or by a user-friendly name previously assigned using the Installation Wizard.
|
Note The Installation Wizard shows only the devices that are connected to the same local segment as the Windows PC that is running the Installation Wizard program. |
Step 3 Choose the first device that you want to configure and click Next to advance to the Name dialog box.
 |
Tip If you cannot determine by the MAC address which device to configure, choose a device and click Details to display the Device Details dialog box. You can also sort devices by right-clicking in the area where the devices are listed and choosing one of the sort options from the shortcut menu that appears. You can sort devices by device name (Sort by Device), status, type, version, or IP address. |
Step 4 If you have not already done so, enter a user-friendly name in the field provided.
This name supplements the alphanumeric device ID or MAC address and makes it easier to identify the device when you use the Installation Wizard or Content Distribution Manager GUI.
Step 5 Click Next to advance to the Obtain Network Settings Automatically (DHCP) dialog box.
Step 6 Indicate whether or not you are using a DHCP server:
|
Note If you are configuring the Content Distribution Manager and want to use DHCP, you must have DHCP configured to statically assign an IP address to the Content Distribution Manager. That is, even with DHCP, the IP address of the Content Distribution Manager cannot be a different IP address assigned by DHCP between reboots. |
|
Note If you do not know the exact IP address of any of these components, or if you are not sure whether your network is using static IP addresses, consult with your network administrator before proceeding. |
Step 7 Click Next to proceed to the DNS-Domain Name System dialog box and then perform one of the following actions:
Step 8 Click Next to advance to the Settings dialog box to review the configuration settings for your device.
|
Note After you click Finish in the Installation Wizard, a white status box appears. Ultimately, you see the device status as "online." Before the device status shows as online, however, it may actually show as "failed." This usually happens when the device needs to be rebooted for the changes to take effect. While it is rebooting, the Installation Wizard loses communication with it, and the device status shows as failed. However, if you wait for the device to finish booting, the status in the Installation Wizard should change to online. |
Step 9 From the Configuring dialog box, perform one of the following actions when the device comes online. (The machine status indicator turns green and reads "online" if the device is online.)
|
Tip If you want to copy the information for use in another application, document, or e-mail, click Copy info to copy the configuration settings to your Windows clipboard. You can then paste the information into another Windows application. |
|
Note It is normal for the device status to be "offline" for a minute or so during an initial configuration. But if the device does not come online within a few minutes, you might need to run the Installation Wizard again. |
|
Note Additional screens used to associate a Content Distribution Manager and configure proxy settings are available when you reopen the Installation Wizard after you have enabled the E-CDN application through the CLI. |
Once you have completed the initial network configuration, you are ready to begin setting up the device for the E-CDN application. This includes allocating disk space, enabling the E-CDN application, associating the device with the Content Distribution Manager, and approving the device within the Content Distribution Manager GUI.
See the "Setting Up the E-CDN Application" section to prepare the device for the E-CDN application.
Refer to Chapter 3, "Troubleshooting with the Installation Wizard," in the Cisco Enterprise CDN Software Configuration Guide, Version 3.0, for information on confirming configuration settings, device status indicators, and error messages to help bring devices online or identify connectivity problems.
Before you can use the ACNS software E-CDN application, you need to complete the following tasks:
1. Allocate disk space on the Content Engine, Content Router, or Content Distribution Manager for the E-CDN application. You must use the device CLI to perform this task. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI.
2. Enable the E-CDN application on the Content Engine, Content Router, or Content Distribution Manager. You must use the device CLI to perform this task. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI.
|
Note If your system has been upgraded to ACNS 4.0 software from a previous release of E-CDN software, then the E-CDN application in ACNS 4.0 software is enabled by default. If you upgraded to ACNS 4.0 software from Cache 2.x software or Cache 3.x software, then you must enable the E-CDN application before you can use it. |
3. Associate the Content Engine or Content Router with the IP address of the Content Distribution Manager.
|
Note Although you can also associate the Content Engine or Content Router with the IP address of the Content Distribution Manager using the CLI, we recommend that you use the Installation Wizard to do this after enabling the E-CDN application on the CLI. Additional Content Distribution Manager and E-CDN proxy setting screens are accessible in the Installation Wizard once the E-CDN application has been enabled. |
4. Approve the Content Engine or Content Router in the Content Distribution Manager GUI to bring the device online.
|
Note Only Content Engines or Content Routers that are newly associated with the Content Distribution Manager need to be approved in the Content Distribution Manager GUI. |
The E-CDN application uses the ecdnfs file system type for storage and must first be assigned some amount of disk space. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI. To allocate disk space for the E-CDN application, follow these steps:
Step 1 Use the command show disks current to check the current disk configurations.
Step 2 To assign disk space to all file system types (sysfs, cfs, ecdnfs, and mediafs), use the disk config command. Amounts of disk space can be specified as percentages, megabytes, or gigabytes, or as "remaining" to assign all remaining disk space to a given file system.
Adjust the allocation percentages for the ecdnfs and other file system types as needed. For example,
ContentEngine# disk config sys 10% cfs 30% ecdnfs 40% mediafs 0%
For disk-space allocation guidelines, see "Configuring and Maintaining Disk Storage."
Step 3 Check your disk-space allocation using the show disks configured command. This command shows what disk configuration is to take effect after you reboot your system.
Step 4 Reboot your system using the reload command for the new configuration to take effect.
You are now ready to enable the E-CDN application.
Once you have allocated disk space for the ecdnfs, you can then enable the E-CDN application from the CLI. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI. Complete the following steps to enable the E-CDN application:
Step 1 Enable the E-CDN application on the Content Engine, Content Router, or Content Distribution Manager from the CLI:
console(config)# ecdn enable
Step 2 To check the status of the E-CDN application, use the show ecdn EXEC command. Allow 2 minutes after enabling the E-CDN application and before checking the status for the settings to be applied.
ContentEngine# show ecdn
ECDN content engine is loading, state is no-sonoma, Waiting for CDN configuration.
For more information, point your browser to CDM 0.0.0.0
After the E-CDN application is enabled, see the "Associating Content Engines or Content Routers with the Content Distribution Manager" section for information about using the Installation Wizard for further setup task options.
To disable the E-CDN application, enter the following ACNS software command from the CLI:
console(config)# no ecdn enable
To verify the status of the E-CDN application, whether it is running or disabled, use the show ecdn EXEC command. Allow 5 minutes for the settings to be applied between disabling E-CDN and checking the status.
ContentEngine# show ecdn
ECDN content engine is not running; server 'bootnet' is 0, 'checkup' is 0.
If you'd like to turn on ECDN, use config command 'ecdn'.
If you have, then the watchdog will restart in 10 mnin.
All Content Engines and Content Routers must be associated with a Content Distribution Manager in order for the Content Distribution Manager to be able to manage the Content Engine or Content Router. This is done by entering the IP address and, optionally, the port number of the Content Distribution Manager in the Content Engine or Content Router configuration.
|
Note Content Distribution Managers do not need to be associated with one another; therefore, this setup task applies only to the Content Engine and Content Router configuration. |
You can associate the Content Engine or Content Router with the IP address of the Content Distribution Manager in two different ways:
1. Through network access to the Content Engine or Content Router from a Windows-based PC on the same subnet running the Installation Wizard (recommended).
2. Through direct console access to the Content Engine or Content Router command-line interface (CLI). If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI.
To associate the Content Engine or Content Router with the IP address of the Content Distribution Manager using the Installation Wizard, follow these steps:
Step 1 Double-click the cndwiz.exe file to launch the Installation Wizard.
The Cisco Content Delivery Network Installation Wizard dialog box appears.
Step 2 Click Next to advance to the Select a Device dialog box, which lists all Enterprise CDN devices on the subnet by their device ID or by a user-friendly name previously assigned using the Installation Wizard.
|
Note The Installation Wizard shows only the devices that are connected to the same local segment as the Windows PC that is running the Installation Wizard program. |
Step 3 Choose the first device that you want to associate and click Next to advance to the Name dialog box.
Step 4 Click Next to accept the Name dialog box settings and advance to the Content Distribution Manager dialog box, or see the "Configuring Network Settings Using the Installation Wizard" section for more information on providing a device name.
Step 5 Perform one of the following actions in the Content Distribution Manager dialog box:
192.168.0.0
|
Note You have now entered the information necessary to associate your device with a Content Distribution Manager; however, in order for these settings to take effect, you must continue through the remainder of the Installation Wizard screens and click Finish at the end. If you have already configured these options, or choose not to configure them, continue to the end by clicking Next at each screen, and then proceed to Step 12. |
Step 6 Click Next to advance to the Obtain Network Settings Automatically (DHCP) dialog box.
Step 7 Click Next to accept the Obtain Network Settings Automatically (DHCP) dialog box settings and advance to the DNS-Domain Name System dialog box, or see the "Configuring Network Settings Using the Installation Wizard" section for more information on configuring DHCP.
Step 8 Click Next to accept the DNS-Domain Name System dialog box settings and advance to the Proxy Server dialog box, or see the "Configuring Network Settings Using the Installation Wizard" section for more information on specifying DNS servers.
Step 9 Indicate whether or not you are using a proxy server:
Step 10 Indicate whether or not you are using a secure proxy server:
Step 11 Perform one of the following actions in the Proxy Exceptions List dialog box:
Step 12 Review the configuration settings for your device in the Settings dialog box.
|
Note After you click Finish in the Installation Wizard, a white status box appears with configuration information. Ultimately, the device status is "online"; however, if it is a new Content Engine or Content Router, it must first be approved within the Content Distribution Manager GUI before the device status changes to online. Before the device status shows as online, however, it may actually show as "failed." This usually happens when the device needs to be rebooted for the changes to take effect. While it is rebooting, the Installation Wizard loses communication with it, and the device status shows as failed. However, if you wait for the device to finish booting, the status in the Installation Wizard should change to online. |
Step 13 From the Configuring dialog box, perform one of the following actions:
Waiting for approval from CDM
You are now ready to approve the device using the Content Distribution Manager GUI.
See the "Approving Content Engines or Content Routers in the Content Distribution Manager GUI" section for information on approving a new device.
Refer to Chapter 3, "Troubleshooting with the Installation Wizard," in the Cisco Enterprise CDN Software Configuration Guide, Version 3.0, for information on confirming configuration settings, device status indicators, and error messages to help bring devices online or identify connectivity problems.
You can associate Content Engines or Content Routers with the Content Distribution Manager IP address using the CLI. If you do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI.
|
Note When associating the Content Engine or Content Router with the IP address of the Content Distribution Manager using the CLI, you should perform this step before enabling the E-CDN application on the Content Engine or Content Router. |
To associate the Content Engine or Content Router with the IP address of the Content Distribution Manager using the CLI, follow these steps:
Step 1 From the Content Engine or Content Router CLI, enter the following command:
console(config)# ecdn cdm ip cdm-ip-address
You can optionally specify the port number, where a valid port number ranges from 1 to 65535, if the port number of the associated Content Distribution Manager has been configured to a number other than the default of 80:
console(config)# ecdn cdm ip cdm-ip-address port port-number
If the port number is not specified, the port number is set to a default value of 80.
Step 2 Enable the E-CDN application on the Content Engine, Content Router, or Content Distribution Manager from the CLI:
console(config)# ecdn enable
See "Enabling the E-CDN Application" section.
Step 3 To verify the IP address of the associated Content Distribution Manager setting on the Content Engine or Content Router, use the show ecdn EXEC command.
Allow 2 minutes for the settings to be applied after associating the Content Distribution Manager and before checking the status.
ContentEngine# show ecdn
ECDN content engine is loading, state is no-studio, Waiting for approval from CDM.
ECDN is trying to connect to CDM
Please configure CDM ip and port and don't forget to approve it from CDM web UI
For more information, point your browser to CDM 172.31.76.76
You are now ready to approve the device using the Content Distribution Manager GUI.
New Content Engines and Content Routers need to be approved by the Content Distribution Manager in order for the device to come online. To approve a Content Engine or Content Router using the Content Distribution Manager GUI, follow these steps:
Step 1 Open the Content Distribution Manager GUI from your web browser by entering the URL or IP address of the Content Distribution Manager. For example, from your browser, enter:
http://name_of_Content_Distribution_Manager
or
http:// IP_address_of_Content_Distribution_Manager
If a dialog box appears requesting your username and password, the Content Distribution Manager was successfully activated and is up and running on your network.
Step 2 Enter the administrator username and password and then click OK. The Cisco Content Distribution Manager window appears.
Step 3 Click Device Console. The new device appears with a caution status indicator in the online column.
Step 4 Click Edit to edit the device settings. From the Identification dialog box, check the Approve check box.
Step 5 Click Save Changes.
Step 6 Once the device has been approved from within the Content Distribution Manager GUI, perform one of the following actions to verify the approval:
|
Note It may take a few moments for the new device to integrate the new configuration settings and come back online. Monitor the status messages provided in the Configuring dialog box and verify that your Content Engine or Content Router device is able to come online properly. |
|
Note Ultimately, you see the device status as "online." Before the device status shows as online, however, it may actually show as "failed." This usually happens when the device needs to be rebooted for the changes to take effect. While it is rebooting, the Installation Wizard loses communication with it, and the device status shows as failed. However, if you wait for the device to finish booting, the status in the Installation Wizard should change to online. |
ContentEngine# show ecdn
ECDN content engine is running, state is online, Running normally.
For more information, point your browser to CDM 172.31.76.76
You are now ready to begin working with the E-CDN application software using the Content Distribution Manager GUI. For further information on working with the E-CDN application software, refer to the following publications:
Refer to Chapter 3, "Troubleshooting with the Installation Wizard," in the Cisco Enterprise CDN Software Configuration Guide, Version 3.0, for information on confirming configuration settings, device status indicators, and error messages to help bring devices online or identify connectivity problems.
This section discusses how to recover a corrupted system image, how to recover a lost password, and how to recover from missing disk-based software on a Content Engine, Content Router, or Content Distribution Manager.
The Content Engine, Content Router, and Content Distribution Manager 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.
To install a new system image using the rescue image, perform the following steps:
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 on/off switch.
The rescue image dialog menu appears. The following example demonstrates how to interact with the rescue dialog (user input is denoted by entries in bold typeface):
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 \Q***' 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
- server IP address
- which protocol to use to connect to server
- username/password (if applicable)
- path to system image on server
Please enter an interface from the following list:
0: FastEthernet 0/0
1: FastEthernet 0/1
0
Using interface FastEthernet 0/0
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
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]: ce590-ACNS-400.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: ce590-ACNS-400.sysimg
Attempting download...
Downloaded 10711040 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.
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
Copyright (c) 1986-2001 by Cisco Systems, Inc.
Cisco Application and Content Networking Software Release 4.00
Compiled 18:48:10 Oct 24 2001 by (cisco)
System was restarted on Wed Oct 31 22:12:25 2001.
The system has been up for 1 day, 5 hours, 26 minutes, 53 seconds.
If a user password is forgotten, lost, or misconfigured, perform the following steps to reset the password on a Content Engine, Content Router, or Content Distribution Manager.
|
Note There is no way to restore a lost password. You must reset the password to a new one, as described in this procedure. |
Step 1 Establish a console connection to the device and open a terminal session.
Step 2 At the following prompt, press Enter:
Cisco ACNS boot:hit RETURN to set boot flags:0009
Step 3 When prompted to enter bootflags, enter this value:
0x8000
For example:
Available boot flags (enter the sum of the desired flags):
0x4000 - bypass nvram config
0x8000 - disable login security
[CE boot - enter bootflags]:0x8000
You have entered boot flags = 0x8000
Boot with these flags? [yes]:yes
[Display output omitted]
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 Content Engine Console
Username: admin
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 5 Once you see the CLI prompt, set the password for the user using the username name password new-password command in global configuration mode.
Step 6 Use the write command to save the configuration change.
Step 7 Reboot your device and set the bootflags back to 0x0.
If you forget to change the bootflags back, the device continues to bypass security every time it reboots.
This section describes the software-recovery shell feature. Use this feature if for some reason the ACNS software detects that the software installation on the first disk drive (disk00) is corrupt or missing. This situation is most likely to occur only if you replaced disk00 in your Content Engine, Content Router, or Content Distribution Manager. The software installation on disk00 cannot be corrupted by a system crash or a power failure.
|
Note For information on the physical location of disk00 and how to replace a disk drive, refer to the hardware installation guide that shipped with your system. |
After you replace disk00 and power on your system, the following error message appears:
There appears to be an incomplete or problematic software
installation on your first disk drive. This may be due to
older software having previously been installed on your system.
Alternatively, if you have just replaced the first disk drive,
software will have to be installed onto it.
Try getting on to network from saved parameters...
get-on-net-pp:got pp_signature!= 0xcfcfcfcf (0x0), bailing
no pp
Looking for network configuration from saved CLI config...
Done get to net
done
Manual intervention required to download new software!
If your network configuration was retrieved and applied successfully,
then can telnet in and interact with the software-recovery shell.
Alternatively, you can run software-recovery shell on console right now.
If the FTP download fails for any reason, the whole process is repeated. When the device has booted to the point that the above message appears, and assuming that you have previously saved network parameters, you can use Telnet to access the device at this point and interact with the software-recovery shell.
The other option is to run the software-recovery shell directly on the console by typing yes at the initial prompt, as follows:
Run software-recovery-shell on console? Enter yes if desired:yes
After you have entered the software-recovery shell, the following dialog appears. (In this example, administrator entries are shown in bold type.)
This is software-recovery-shell
In order to run ACNS 4.0 on your system, your first hard drive will need
to have software installed on it. This will necessarily mean that all
existing partitions INCLUDING ALL DATA on this disk drive will be destroyed.
If you do not want to do this now, power down and figure out how to
load another image (e.g. use the rescue image from the bootloader).
Enter yes to continue:yes
Are you really sure? First disk drive will be overwritten.
Enter yes if you are really sure:yes
Ok, deleting data on first disk drive.
10240+0 records in
10240+0 records out
Syncing partition table
Running ruby_disk hidden
FYI, /proc/mounts:
/dev/root / ext2 rw 0 0
none /proc proc rw 0 0
none /dev/pts devpts rw 0 0
/dev/sda1 /sw ext2 rw 0 0
/dev/sda2 /swstore ext2 rw 0 0
Ok, now we need to download and install a full ACNS 4.x software release.
Someone should have provided you with a .bin file containing ACNS release
software. Please place this file on an FTP server accessible
over the network from this box.
Please enter FTP server IP address:172.16.193.244
Please enter directory on ftp server containing release image (e.g.
/):/users2/johndoe/ACNS400BR/bfc/boot
Please enter filename on ftp server (e.g. filename.bin):ce590-ACNS-400.bin
Enter username for remote ftp server:johndoe
Enter password for remote ftp server:
Initiating FTP download...
Sending:USER johndoe
vista.cisco.com FTP server (Version wu-2.6.0(1) Mon Feb 28 10:30:36 EST 2000) ready.
Password required for johndoe.
Sending:PASS *****
User johndoe logged in.
Sending:TYPE I
Type set to I.
Sending:PASV
Entering Passive Mode (128,107,193,244,60,71)
Sending:CWD /users2/johndoe/ACNS400BR/bfc/boot
CWD command successful.
Sending PASV
Entering Passive Mode (128,107,193,244,60,71)
Sending:RETR ce590-ACNS-400.bin
Opening BINARY mode data connection for ce590-ACNS-400.bin (87322563 bytes).
writing flash component:
.................................................................
The new software will run after you reload.
/ACNS-400/bin/config-shell:ftp_to_install appeared to succeed.
/ACNS-400/bin/config-shell:running install-to-sw
swpart = /dev/sda1
unmounting /sw
running mke2fs on /sw partition:/dev/sda1
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
mke2fs succeeded
mounting /dev/sda1 to /sw
mount succeeded
extracting application components
extracting component /swstore/comp.diamond-apps...
extracting component /swstore/comp.linuxapps...
extracting component /swstore/comp.realproxy-ruby...
extracting component /swstore/comp.sonoma-code...
running setup_symlinks...done
Looking for post-install hooks to run...
running hook sonoma/PLATFORM-HOOKS/obsidian.post-install
Finding box-type
CE590
box-type is appliance
generating certificate.....
mac-id is 00:01:64:40:d4:56
generating certificate........done
Marking /sonoma/state as empty.....
obsidian.post-install:Done
Syncing filesystems...
marking /sw up-to-date...
mounting /sw read-only...
/ruby/bin/install-to-sw:DONE.
The release image you just downloaded contains a base system component.
Installing it to flash.
building /sw/linuxapps symlink tree.../bin/ln:/home/ftp:File exists
done.
running shell code...done.
Looking for pre-200 hooks to run...
running hook diamond/PLATFORM-HOOKS/diamond.pre-200
diamond/PLATFORM-HOOKS/diamond.pre-200:running
diamond/PLATFORM-HOOKS/diamond.pre-200:exiting
BOOT:entering runlevel 200 (full operations)!
code150.sh:no process killed
Switching to run
Cisco Content Engine Console
Username:admin
Password:
System Initializing. Please wait.....
System Initialization Finished.
johndoe-590 con now available
Press RETURN to get started!
Posted: Thu Nov 14 13:43:49 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.