Cisco Cisco ACNS Software Version 5.5 Quick Setup Guide
27
Note
After you click Finish in the Installation Wizard, a 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.
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 8
From the Configuring screen, perform one of the following actions:
•
Click More to return to the Select a Device screen and associate another of your CDN devices, or click Exit to close
the Installation Wizard.
the Installation Wizard.
The following message appears in the status box:
Waiting for approval from CDM
The device will not come online until it has been approved within the Content Distribution Manager GUI.
•
Click Back and review your configuration settings.
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 on page 28 for information on approving a new device.
Content Routers in the Content Distribution Manager GUI” section on page 28 for information on approving a new device.
Associating Content Engines or Content Routers with the Content Distribution Manager Using
the CLI
the CLI
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.
do not have direct console access to the device CLI, then you need to open a Telnet session to the device CLI.
Note
You must associate the Content Engine or Content Router with the IP address of the Content Distribution
Manager using the CLI before enabling the E-CDN application on the Content Engine or Content Router.
Manager using the CLI 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:
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:
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