|
|
This chapter provides information on configuring your CDN devices, including the Content Distribution Manager, Content Routers, and Content Engines, as well as creating user accounts and setting parameters for media replication and playback.
 |
Note Make sure that you have unpacked your Content Distribution Manager, Content Router, and Content Engine hardware, as well as activated your Content Distribution Manager. Refer to the Cisco Content Delivery Networking Products Getting Started Guide for more information on completing these preliminary steps before continuing with this chapter. |
This chapter contains the following sections:
Before attempting to log on to your Content Distribution Manager, you must have first activated the Content Distribution Manager by following the procedure outlined in the Cisco Content Delivery Networking Products Getting Started Guide.
To log on to your Content Distribution Manager, verify configuration settings, and, if necessary, modify configuration settings, perform the following steps:
If a screen appears requesting your username and password, the Content Distribution Manager was successfully activated and is up and running on your network.
|
Note If using a DNS name for the Content Distribution Manager then DNS server configuration is needed on the CLI and in the Content Manager GUI. |
Step 2 Enter the default administrator username and password as follows, and then click OK.
The Cisco Content Distribution Manager screen appears.
Step 3 Choose Devices > Device Console and verify that the Content Distribution Manager is listed as an online device.
A green circle appears in the Online column. Any other active CDN devices should also be listed here. (See Figure 2-1.)
Step 4 You can now proceed with the configuration of your other CDN devices such as Content Engines and Content Routers. See the next section, "Setting Up Content Delivery Network Devices."
Once you have verified that your Content Distribution Manager is up and running, you can set up or configure your Content Engines or Content Routers. This step is necessary in order for you to begin distributing media files to users on the CDN.
After devices have been configured for the first time using the Installation Wizard or the CLI commands, the Content Distribution Manager Device Editor can be used to modify configuration settings.
To configure your E-CDN application devices (Content Distribution Manager, Content Routers, and Content Engines), follow the sequence of steps for configuring CDN devices in the Cisco Content Delivery Networking Products Getting Started Guide.
Once initial configuration is complete, use the information that follows in this chapter to edit the configuration of your E-CDN application devices using the Content Distribution Manager Device Editor.
You use the Devices menu to manage your E-CDN application devices in your network. From the Devices menu you can configure the Content Distribution Manager, Content Routers, and Content Engines and edit device properties.
|
Note Only users with administrator privileges have access to the Devices menu. |
The E-CDN application device properties that can be edited include the device configuration properties described in Table 2-1.
Table 2-1 Device Configuration Properties
Although changing the name of a device and adding a description for it are optional, we recommend that you change the default name of each device to something more meaningful to you and that you add some descriptive information, such as location, for each device. See Figure 2-2 and Table 2-2 for more information on the Identification screen and its options.
The default name of a device is the device's system ID, which is in the form:
|
Note The name cannot contain any spaces. |
To enter an identifying name and description for a device, perform the following steps:
Step 2 Choose the device that you want to edit from the Device Selector drop-down list. Some general information about the selected device is displayed. The default name is listed in the Name field.
Step 3 Enter a new name and description, as needed.
Step 4 Click Save Changes.
Clicking Cancel Changes returns all values to their previous settings when you last clicked Save Changes.
Table 2-2 Device Identification Properties
| Device Identification | Description |
Indicates whether a device is online or not. A solid green circle shows that the device is online. A red circle shows that the device is not online. A yellow triangle indicates the device has not been approved by the Content Distribution Manager. See the "Setting Up Content Delivery Network Devices" section. |
|
Identifies the device as a Content Distribution Manager, Content Router, or Content Engine. |
|
Specifies how long the device has been running since it was last rebooted. |
|
Identifies channels, or content groups, to which the device is subscribed. See the "Creating Channels" section and the "Subscribing a Content Engine to a Channel" section for more information. |
|
Displays the Internet Protocol (IP) address assigned to the device. |
All devices on the CDN set their time based on two settings:
|
Note If the system time for the Content Distribution Manager is changed, then the devices may automatically reboot if they detect a clock skew. |
To set the system time for your CDN, perform the following steps:
Step 2 From the Device Selector drop-down list, choose the Content Distribution Manager.
Step 3 Next to the System Time heading, place your cursor in the first Date field and enter the date in MM/DD/YYYY format. Press the Tab key to move between fields when entering the date.
Step 4 Move your cursor to the first Time field and enter the time in HH:MM:SS format. Press the Tab key to move between fields when entering the time.
Step 5 Click Set. You are prompted to confirm your decision to reset your system time.
|
Note Setting or changing the system time causes the Content Distribution Manager to reboot immediately. You must manually reboot your Content Engines and Content Routers for them to begin using the new system time settings. |
Step 6 Click OK to confirm your decision. Clicking Cancel returns the system time values to their previous settings.
Use this option to set the region and time zone for each of your CDN devices. Specifying a time zone is important when coordinating activity on geographically dispersed CDN devices.
To set the time zone for a device:
Step 2 Make sure that the correct device is displayed in the Device Selector drop-down list. If it is not, choose the correct device from the drop-down list. Some general information about the selected device is displayed.
Step 3 Choose a region in the Region list. When you have chosen a region, the zone/city settings change correspondingly.
Step 4 Choose a time zone or city from the Zone/City list.
Step 5 Click Save Changes.
Clicking Cancel Changes returns all values to their previous settings when you last clicked Save Changes.
If you are using DHCP, TCP/IP properties are set automatically by the DHCP server. If you are not using DHCP, you must specify TCP/IP properties manually.
To specify a DHCP server or to enter IP address information, perform the following steps:
Step 2 Choose the correct device from the Device Selector drop-down list.
General information about the selected device is displayed.
Step 3 Click Obtain network settings automatically using DHCP and go to Step 5.
Step 4 Click Specify an IP address, subnet mask, port, and gateway to set an IP address, subnet mask, port, and gateway.
Enter the information as required for the network.
Clicking Cancel Changes returns all values to their previous settings when you last clicked Save Changes.
Step 6 Choose Devices > Device Editor > System. The Device System Editor screen appears. Click System Reboot to ensure that the new settings will take effect.
|
Note You must reboot the Content Distribution Manager from the Device Editor System screen after saving the TCP/IP settings, or the settings will not take effect. |
Changing the IP address of your Content Distribution Manager can have ramifications throughout your entire CDN. When changing the address of your Content Distribution Manager, remember to:
To reset your Content Distribution Manager IP address and point your Content Engines and Content Routers to the new location of your Content Distribution Manage, perform the following steps:
Step 2 Choose the correct device from the Device Selector drop-down list.
Step 3 Click the Specify an IP address, port, subnet mask, and gateway option. The current IP address of the Content Distribution Manager appears in the IP Address field.
Step 4 Without changing any of the information presented, place the cursor in the Alternate IP Address field and enter the IP address to which the Content Distribution Manager will be moving in valid "dotted quad" format. For example:
Step 5 Click Save Changes to save the address.
Step 6 Wait approximately 1 hour before moving the Content Distribution Manager to the address you entered in the Alternate IP Address field.
Step 7 When an hour has passed, you can change the Content Distribution Manager actual IP address using the Content Distribution Manager Device Editor or the E-CDN Installation Wizard, or by reconfiguring your DHCP server. Enter the new IP address of the Content Distribution Manager in the IP Address field on the TCP/IP screen. This address should match the address in the Alternate IP Address field.
See the "Editing TCP/IP Settings" section for more instructions on changing the IP address of E-CDN application devices.
Step 8 Click Save Changes.
Step 9 Click System.
Step 10 Make sure that the Content Distribution Manager is selected in the Device Selector drop-down list. If it is not, expand the drop-down list and choose your Content Distribution Manager from the devices listed.
Step 11 Click System Reboot to reboot your Content Distribution Manager and reconnect it to your network using the new IP address.
Step 12 Wait for your Content Engines and Content Routers to reconfigure themselves to point to the new address of the Content Distribution Manager.
|
Note Approximately 45 minutes after your Content Distribution Manager comes back online at its new address, your Content Engines and Content Routers will begin going offline because they can no longer detect the Content Distribution Manager at its prior address. They will then automatically use the alternate IP address to connect to the Content Distribution Manager's new IP address. |
Step 13 Click Device Console. Monitor your Content Engines and Content Routers and verify that each device is able to locate the Content Distribution Manager and come back online.
If one or more Content Engines or Content Routers are not able to resolve the Content Distribution Manager's new address, use the Installation Wizard to manually point them to the location of the Content Distribution Manager. See the "Installation Wizard-Based Reconfiguration" section for information.
Quality of Service (QoS) is a strategy that helps to guarantee uninterrupted high-bandwidth video and multimedia content delivery over your E-CDN application. Content Engines use QoS when sending media to requesting clients, and use one of two transmission protocols:
Using the Content Distribution Manager Device Editor, you can enable the QoS feature and then configure Content Engines to use both RSVP and DiffServ when sending data to E-CDN application clients.
|
Note Content Routers do not use QoS. The QoS option is disabled when the selected device is a Content Router. |
To enable the QoS feature, perform the following steps:
Step 2 Choose the Content Engine for which you are enabling QoS from the Device Selector drop-down list.
Step 3 Check the Enable QoS check box. Options for enabling RSVP and DiffServ appear.
See the following sections for information on configuring RSVP and DiffServ for your E-CDN application.
When enabling RSVP, you can specify the following:
To enable a Content Engine to use RSVP as part of QoS when sending media to requesting clients, perform the following steps:
Step 2 In the RSVP Timeout field, enter the timeout value in milliseconds. This is the length of time that the requesting Content Engine will wait for acknowledgment of the RSVP request from intermediary devices before canceling the request. For example, a timeout value of one-half second would be:
Step 3 If you wish RSVP requests to be sent regardless of whether bandwidth guarantees have been received from all intermediary devices along the delivery route, check the Enable RSVP Service Policy check box.
Step 4 Click Save Changes to save your RSVP configuration settings for the selected Content Engine.
If you need to configure your Content Engine to use the DiffServ protocol in addition to RSVP, see the next section, "Enabling DiffServ."
When enabling the DiffServ protocol, you are required to specify a Differentiated Services Code Point (DSCP), which controls the per-hop behavior of packets transferred from the Content Engine to the requesting client. The code point setting determines the instructions that network packets follow at each point (or hop) along their path to the requesting client. The DSCP options are:
To enable a Content Engine to use DiffServ as part of QoS when sending media to requesting clients, perform the following steps:
Step 2 Click the DiffServ CodePoint drop-down arrow.
Step 3 Choose from among the DSCP settings on the list. DSCP settings determine the per-hop instructions assigned to each network packet on the path between the Content Engine and the requesting client.
Step 4 Click Save Changes to save your DiffServ configuration settings for the selected Content Engine.
If you need to configure your Content Engine to use the RSVP protocol in addition to DiffServ but have not yet done so, see the "Enabling RSVP" section.
A DNS server is used to provide user-friendly names for computers in a
network, including the Content Distribution Manager, Content Routers, and Content Engines that make up your E-CDN application. If a DNS server is not used, the numerical value of the IP address is used to identify and access machines on your network.
To enter DNS server settings, perform the following steps:
Step 2 Make sure that the correct device is displayed from the Device Selector drop-down list. If it is not, choose it from the drop-down list.
General information about the selected device is displayed.
Step 3 Enter the following information to identify your DNS server:
If your network is using more than one DNS server, click Add Server to add another DNS server to the list, and repeat this step.
A web server or HTTP proxy server might be required by your site administrator to access the Internet. The following definitions should help you configure your proxy server for use with the E-CDN application. See Table 2-3 for information and default proxy server settings.
After saving changes to your proxy server settings, you must reboot all affected E-CDN application devices, including your Content Distribution Manager and any affected Content Routers and Content Engines, before resuming use of the E-CDN application. Rebooting affected devices ensures that changes to your proxy server settings are communicated to all devices in your CDN.
Table 2-3 Proxy Server Configuration Settings
To enter proxy server settings, perform the following steps:
Step 2 Choose the correct device from the Device Selector drop-down list. General information about the selected device is displayed.
Step 3 Enter the proxy server configuration settings.
See Table 2-3 for a description of each setting.
If you are using a secure proxy server, the address and port for the server will appear in the fields labeled Secure Address.
If you want to exempt certain IP addresses from using the proxy server, add them at this time. Enter the first exception IP address in the Exceptions field provided.
If there are multiple exception addresses, click Add Exception to add another field for entering an exception address, and then enter the proxy exception address.
Repeat this step for each exception address.
Step 5 Repeat Step 1 through Step 4 for each device that requires changes to its proxy server settings. You will have to reboot each device you have changed, beginning with any affected Content Engines and Content Routers, and concluding with the Content Distribution Manager.
Step 6 From the Device Editor, choose System. The Device Editor System screen appears.
Step 7 Choose a Content Engine from the Device Selector drop-down list.
The Device Editor System screen displays the Content Engine system information.
Step 9 Repeat Step 6 through Step 8 for each affected Content Engine and Content Router, as well as the Content Distribution Manager.
You are ready to resume use of the E-CDN application with new proxy settings when your Content Distribution Manager finishes rebooting.
If the E-CDN application is enabled in ACNS 4.1 software, with the
E-CDN application HTTP server listening on default port 80 for HTTP requests and port 443 for Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) requests, interaction may occur between the proxy and the E-CDN application.
The interaction does not occur if the E-CDN application listens on ports other than the default port 80 for HTTP and port 443 for HTTPS. Interactions between the proxy and the E-CDN application are:
The Content Distribution Manager and all Content Engines, by default, serve a coverage zone—a range of IP addresses that is assigned to a device. You can define the coverage zones of a device to maximize the efficiency with which content requests are served.
Decisions about which devices running the E-CDN application serve a particular request for content are made by the CDN software using an intelligent model designed to maximize the success of each content request.
In the simplest scenario, requests from workstations on the CDN are routed to the nearest Content Engine on the network by the Content Distribution Manager or Content Router. However, E-CDN application administrators can override the default settings and influence content routing through the deployment of "preferred coverage zones" and "regular coverage zones" for Content Engines and even the Content Distribution Manager.
Preferred coverage zones are ranges of IP addresses assigned to Content Engines or the Content Distribution Manager. When a request for content originates from an address within the preferred coverage zone of a Content Engine or the Content Distribution Manager, that device is directed to serve the request.
All requests originating from outside the preferred coverage zone for a device are processed by the nearest device. "Nearness" is determined by the local network segment of each device, defined by its IP address and network mask.
When content requests originate from addresses that are covered by more than one preferred coverage zone or regular coverage zone, the Content Distribution Manager chooses a Content Engine from among the qualified Content Engines to serve the request.
Coverage zones are ranges of IP addresses on the E-CDN application that are associated with content-serving devices. You can specify two types of coverage zones:
Preferred coverage zones are groupings of IP addresses served by a single Content Engine or group of Content Engines. Requests originating from within the range of preferred addresses are served by one of a small group of designated Content Engines, ideally devices that are in close physical proximity, ensuring optimal performance. By default, all Content Engines serve a preferred coverage zone that is defined by their local network segment (determined by the IP address and the netmask configured for the device).
Regular coverage zones are broader groupings of IP addresses served generally by a Content Distribution Manager and a pool of Content Engines on the CDN.
Coverage zones that override the network defaults can be defined separately for each Content Engine and for the Content Distribution Manager. When devices are not assigned a particular coverage zone, they use default "preferred" and "regular" coverage zones.
To assign a preferred coverage zone or regular coverage zone to a Content Engine, perform the following steps:
Step 2 Choose the correct Content Engine from the Device Selector drop-down list. General information about the selected device is displayed.
Step 3 In the section labeled Device Coverage Zones, choose the Specify coverage zone settings option. Fields for configuring your coverage zones appear.
Step 4 If you are configuring a preferred coverage zone for the Content Engines, place the cursor in the Preferred field and enter the address range and netmask in the proper format.
The format for the coverage zone address is IP_address/netmask, for example:
You can also specify a series of specific addresses and netmasks in this field separated by semicolons, for example:
Step 5 Repeat Step 4 for the regular coverage zone by moving your cursor to the Regular field and entering the address range in the proper format.
As with the preferred coverage zone address field, you can also enter a range of addresses in the Regular field.
Step 6 In the Network Hierarchy section, check the Build the network hierarchy automatically check box if you want to build a hierarchy of devices in the network. The hierarchy is used for content replication. Disabling the protocol makes this device a direct child of the Content Distribution Manager.
Step 7 Click Save Changes to assign the preferred and regular coverage zones you specified to the selected device.
|
Note If storage is added to or removed from devices (Content Distribution Managers and Content Engines only), click the Update Storage Capacity button to determine if the added or removed storage has changed and is recognized by the E-CDN software. |
You use the Content Distribution Manager Bandwidth feature to set the maximum bandwidth to be used by each device for replicating media to the Content Engines and for streaming media to user desktops. Bandwidth controls limit the bandwidth consumed by your Content Distribution Manager and Content Engines. Bandwidth can be limited in megabits per second for both replication and playback.
Intelligent bandwidth management provides the ability to limit the maximum bandwidth allowed for replication between E-CDN application devices to particular days of the week and hours of the day.
Content Engines and the Content Distribution Manager use a specific playback bandwidth when streaming media to user desktops. Although this bandwidth value can be changed, it is not possible to schedule changes to the playback bandwidth as it is with replication bandwidth.
The user has to specify the maximum bandwidth that each device can use to play back content to the user desktop. Each Content Engine has three playback servers: the WMT server, the HTTP server, and the RealServer. The user has to consider the content type and decide how to distribute maximum bandwidth among these three servers. For example, if the user has only the WMT content type, then the user should allocate 100 percent of the playback bandwidth to the WMT server and 0 percent to the HTTP server and the RealServer.
The Total playback field on the Devices Bandwidth screen is used to enter the maximum playback bandwidth. (See Figure 2-8.) Under this field are three more fields: WMT, HTTP, and Real. In these fields, the user can specify what percentage of the playback bandwidth is to be used for the WMT server, HTTP server, and RealServer, respectively.
On the left side of each field is a green or red circle that indicates whether that server is enabled or not on the device. For example, if the WMT field has a red circle, then the WMT server is not enabled on the device. If the Real field has a green circle, then the RealServer is enabled on the device. HTTP is always green because it cannot be disabled.
If a server is disabled, then its distributed bandwidth is 0. If a server is not disabled, then its associated field displays the current bandwidth distributed to that server as a percentage of total bandwidth. You can modify this field to change the bandwidth distribution.
If you do not update bandwidth settings, then default bandwidth settings are used. Default settings are:
To set the playback bandwidth for a Content Engine or the Content Distribution Manager, perform the following steps:
Step 2 Make sure that the correct device is displayed in the Device Selector drop-down list.
 |
Caution Use care when making bandwidth setting changes to an entire device group. Any unique bandwidth settings for an individual device within a group will be overridden by the group settings. You will need to reset unique settings for an individual device after completing settings for the group. |
Step 3 In the Total playback field, enter a bandwidth value in megabits per second.
Step 4 In the Distribution field, enter a bandwidth distribution value (in percentage from 0 to 100) in the field next to the enabled server type. The total of the three values for WMT, HTTP, and Real should be 100 percent.
|
Note A server must be enabled (green circle) before you can set or change its bandwidth distribution. |
Step 5 Perform one of the following actions:
Choose the desired device group from the drop-down list.
Step 6 Click Save Changes to store the new playback bandwidth setting for the selected device or device group.
Clicking Cancel Changes returns all values to their previous settings when you last clicked Save Changes.
All E-CDN application devices ship with a default replication bandwidth. This bandwidth setting is enabled from 12:00 a.m. to 11:59 p.m. (24 hours) for each day of the week. Although the default replication bandwidth can be changed, its operating schedule cannot. Instead, you use the bandwidth feature to create additional replication settings to take effect at certain times during the week.
To add a replication bandwidth setting for moving media files over the network:
You can apply bandwidth settings to an individual device or to a device group.
Step 2 Perform one of the following actions:
Step 3 Choose the desired device group from the drop-down list.
Step 4 Click Add Bandwidth. A new screen appears.
A new bandwidth setting is added to the bottom of the bandwidth list, and options appear for configuring the new bandwidth setting.
Step 5 In the Bandwidth field, enter the replication bandwidth value for this setting in megabits per second.
Step 6 Above the Bandwidth field, set the time at which the device will begin to replicate media using this bandwidth by entering a time in the From field and clicking the AM radio button or the PM radio button.
Alternatively, click the 24 hour radio button or 9-5 radio button to set the interval from 12:00 a.m. to 11:59 p.m. (24 hours), or 9:00 a.m. to 5:00 p.m.
Step 7 Set the time at which the device will cease replicating media at this bandwidth by entering a time in the To field and clicking AM radio button or the PM radio button.
Step 8 In the area beneath the Bandwidth field, check the appropriate Days check boxes to set which days of the week the device will use the replication bandwidth you are configuring.
You can click All to choose every day or click None to clear your selections.
Step 9 Click Save Changes. Clicking Cancel Changes returns all values to their previous settings when you last clicked Save Changes.
The screen refreshes, updating the replication bandwidth schedule for the device or device group.
The device replicates media at the bandwidth you set during the hours and on the days you specified. Remember that the device operates according to its local time zone. See the "Setting the Time Zone for a Device" section for information on establishing time zones for your E-CDN application.
To remove a replication bandwidth setting, perform the following steps:
Step 2 Choose the correct device from the Device Selector drop-down list.
Step 3 Perform one of the following actions:
Step 4 Click Edit next to the interval setting that you want to remove.
Step 5 Click Remove Bandwidth at the top of the screen.
To edit a replication bandwidth setting, perform the following steps:
Step 2 Perform one of the following actions:
Step 3 Click Edit next to the interval setting that you would like to change.
Step 4 Modify the playback and replication bandwidths, time intervals, or days of the week.
Step 5 Click Save Changes.
You can use load balancing to enable optimal distribution of user requests for content over the Content Distribution Manager and Content Routers.
|
Note Load balancing can only be used if you have Content Routers on your network. |
To enable load balancing, perform the following steps:
Step 2 You must first configure and add the Content Service Switch (CSS) 11000 that implements the load balancing.
|
Note For a sample CSS configuration, see Example 2-1. For more information about configuring a CSS 11000 switch, refer to the following Cisco Content Services Switch documentation on Cisco.com: http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/index.htm |
Step 3 Enter a virtual IP address or a virtual host and domain name. This should be the same as the one specified in the "vip address" section in the CSS configuration. For load balancing to take effect, the URLs that request content must contain this virtual IP address, host name, and domain name so that the CSS 11000 switch is used to implement load balancing.
Step 4 Click Save Changes.
Example 2-1 is a very basic CSS 11000 configuration for a virtual IP address that load balances between the Content Distribution Manager and Content Routers based on the least number of connections. The keepalive heartbeat is an HTTP request to /cgi/CSS-keepalive.
All devices on your CDN use time settings based on two factors:
Use the PC folders option to configure your Content Distribution Manager so that it appears in your Network Neighborhood or My Network Places. This enables CDN administrators to browse the contents of the Content Distribution Manager channel-level import directories using Windows Explorer, as well as drag and drop files for import to particular channels.
|
Note Your office network must be running the Windows 95/98, Windows NT, or Windows 2000 operating system in order to use the PC folders option to import media files. |
To configure PC folders, perform the following steps:
Step 2 Choose the correct device from the Device Selector drop-down list. General information about the selected device is displayed.
Step 3 In the Workgroup field, enter the workgroup of the Microsoft Windows PCs that will be used to browse the Content Distribution Manager media import directories.
Step 4 In the WINS Server field, enter the IP address of the Windows Internet Naming Service (WINS) server.
Step 5 In the Remote Announce field, enter either the IP address of the PC that will be used for web browsing or the address of the network that the PC is on.
Step 6 Click Save Changes.
Users can be assigned either administrator-level or user-level privileges.
Users are added through the Content Distribution Manager Users screen. To add a user, perform the following steps:
Step 2 Choose the Content Distribution Manager from the Device Selector drop-down list. Options for editing user accounts appear. Accounts are listed alphabetically.
Step 3 Enter the new username in the field next to the Add User button.
Step 4 Enter a new password for the user in the Enter Password field.
Step 5 Enter the new password a second time in the Re-enter Password field.
Step 6 Click the Admin or User radio button to designate the access level of the account, and then click Add User. The new user is added to the user list.
|
Note The Content Distribution Manager users feature only allows users to access FTP and HTTP when the E-CDN application is running. This feature does not allow users to access a Telnet connection. Use the appropriate CLI command to access Telnet. For more information about CLI commands, refer to the Cisco Application and Content Networking Software Command Reference. |
User accounts are removed using the Content Distribution Manager users feature.
|
Note It is not possible to remove the admin account, nor is it possible to remove the current user's account. |
To remove a user, perform the following steps:
Step 2 Choose the Content Distribution Manager from the Device Selector drop-down list. Options for editing user accounts appear. Accounts are listed alphabetically.
Step 3 Locate the name of the user you wish to remove.
Step 4 Click Remove next to the username that you want to remove.
If you attempt to remove the current account (the account you used to log on), you are prompted to log on again using another administrator account before you are allowed to delete the account you were using.
User privileges can be modified using the Content Distribution Manager Users feature. To change user privileges, perform the following steps:
Step 2 Choose the Content Distribution Manager from the Device Selector field. Options for editing user accounts appear. Accounts are listed alphabetically.
Step 3 Locate the account you wish to edit.
Step 4 Click the Admin or User radio button to change the designation of the account.
Step 5 Click Change.
You change the password of a user or administrator through the Content Distribution Manager users feature. Passwords can only be changed from the Content Distribution Manager user interface.
To change a user password, perform the following steps:
Step 2 Choose the Content Distribution Manager from the Device Selector drop-down list. Options for editing user accounts appear. Accounts are listed alphabetically.
Step 3 Locate the user or administrator account for which you wish to change passwords.
Step 4 Enter the new password in the Enter Password field.
Step 5 Enter the new password again in the Re-enter Password field.
Step 6 Click Change.
If the screen refreshes without error, you have successfully changed the password. If you encounter an error, see "Error Messages."
The E-CDN application system ships with a default administrator account already configured. This account, which uses the admin username, gives administrators full access to the Content Distribution Manager graphical user interface.
To access or edit the administrator account, perform the following steps:
Step 2 Choose the Content Distribution Manager from the Device Selector drop-down list. Options for editing user accounts appear. Accounts are listed alphabetically.
Step 3 Locate the admin account.
Step 4 Enter the new password in the Enter Password field.
Step 5 Enter the new password again in the Re-enter Password field.
Step 6 Click Change.
The Enter Network Password screen appears.
Step 7 Enter the new administrator password a third time in the Password field provided and click OK.
If the screen refreshes successfully, you have changed the password. If you encounter an error, see "Error Messages."
Ordinarily, E-CDN application administrators change the default administrator account password (admin) in the same manner as any other account password. Refer to the Cisco Content Delivery Networking Products Getting Started Guide for details on changing passwords for accounts.
However, if you lose track of the password for the admin account and accidentally lock yourself out of the Content Distribution Manager administrative user interface, you must manually reset the password for the admin account before regaining access to the Content Distribution Manager and the Users feature.
Resetting the admin account password restores the factory-configured password to the account. After resetting this password and rebooting the Content Distribution Manager, administrators can again log on using the admin account and configure the password for the account, as well as for other user and administrative accounts.
|
Note In order to reset the password for the default administrator account, admin, you must have physical access to the Content Distribution Manager and have sufficient permissions to be able to log on to that device. |
To reset your default administrator password, perform the following steps:
Step 2 Terminate any active Linux sessions by entering exit at the prompt.
Step 3 Reboot the Content Distribution Manager by powering the device off, and then on again.
Step 4 Wait for the following prompt:
Step 5 Log on to the Content Distribution Manager.
Step 6 Enter the following path for the reset password script, resetpass, as follows at the bash# prompt:
The script is executed, resetting the password for the admin account and rebooting the Content Distribution Manager. Once the Content Distribution Manager has completed its reboot, you can log on using the default administrator account by entering the username, admin, and the factory-configured password.
The device groups feature lets E-CDN system administrators group individual devices by category in order to efficiently apply bandwidth settings across many devices at one time. Applying bandwidth settings to each device can be repetitive and tedious. Enabling the user to apply settings to multiple devices at one time reduces configuration and administration overhead.
You can apply bandwidth settings to the existing Default Device group (to which all devices initially belong by default) or you can create, name, and describe a new device group. After you decide whether to use the existing Default Device group or create a new device group, choose Devices > Bandwidth on the Content Distribution Manager to apply the bandwidth settings.
You can perform the following device group tasks:
To add or create a new device group, perform the following steps:
Step 2 Click Add Device Group to add a new device group.
Step 3 To search for an existing device group, enter that device group name in the Search by Device Group Name field and click Get.
Step 4 To edit a device group, click Edit next to the group that you want to edit. The Device Group Editor Identification screen appears. (See Figure 2-13.)
Step 5 To remove a device group, check the Remove check box next to the group that you want to remove and click Remove Device Group.
|
Note By default, all devices are members of the Default Device Group. Auto Membership (on the Identification screen) is enabled by default. |
To name and describe a device group, perform the following steps:
Step 2 Choose the device group whose name and description you want to edit from the Device Group Selector drop-down list.
Step 3 Enter a new name for this group in the Name field. Note that a device group name must be unique and cannot have the same name as an individual device.
Step 4 Enter a description of the group in the Description field.
Step 5 If desired, uncheck the Auto Membership check box if you do not want newly added devices to automatically become members of this group.
Step 6 Click Save Changes to save any changes.
To add a device to the membership list of a group, perform the following steps:
Step 2 From the Device Group Selector drop-down list, choose the device group to which you want to add members.
Step 3 To find a device that does not appear on the Non-Member Devices list, enter the device in the Non-Member Search by Name/IP field and click Get. The device name is added to this list. You can then add it to the Member Devices list. Perform the same operation when looking for a device that is already a member. Enter its name in the Member Search by Name/IP field and click Get.
Step 4 To add a nonmember device to the Member Devices list, check the check box next to the desired nonmember device and click Add. The device now appears in the Member Devices list.
Step 5 To remove any device from Member Devices list, check the check box next to the device that you want to remove and click Remove.
Posted: Mon Mar 24 16:22:27 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
