|
|
The Cisco CDN Software Service Provider Edition software for the Content Distribution Manager, the Content Routers, and the Content Engines is already installed on your system devices. This chapter tells you how to configure these devices on your network. The chapter also tells you how to license the SystemEDGE Agent, for you to use as an SNMP agent, if needed.
Before you begin configuring CDN devices:
We recommend that you determine whether your network uses a DHCP server. If your network uses a DHCP server, the DHCP server will automatically provide your CDN devices with network configuration information when you configure your CDN devices.
If your network does not use a DHCP server, then you must provide network configuration information (the IP address, Netmask, and Gateway address) when you configure your CDN devices.
You must install the Oracle 8i database management system (DBMS) on your host network. To do so, follow the instructions included with the Oracle DBMS. During the installation, note the port number that the Oracle listener is configured to use.
 |
Note The default is port 1521. |
You will also need the database administrator account username and password.
|
Note The default database administrator account username is system and the default password is manager. |
Use the Oracle tools to create a database and note the session name you assign when you create the database.
From a Windows, Linux, or Unix client, log in as the database administrator to the Oracle session and host previously created using a database administration tool such as SQL-PLUS.
|
Note You may need to enter the connection information in the tnsnames.ora file found under the Oracle/networks/admin directory on your client system. |
Perform the following SQL commands:
|
Note The following SQL commands are provided as an example. Refer to a SQL command reference for more information. |
|
Note The datafile path will need to be changed to match the physical drives on the host Oracle server. SQL-PLUS allows you to enter a single command as multiple lines. |
SQL> create tablespace cdn DATAFILE 'e:\Oracle\OraData\cdn1\cdn.dbf' SIZE 250M REUSE default storage(initial 25K next 10K minextents 1 maxextents unlimited pctincrease 50); SQL> create tablespace cdntemp DATAFILE 'e:\Oracle\OraData\cdn1\cdntemp.dbf' SIZE 250M REUSE default storage(initial 25K next 10K minextents 1 maxextents unlimited pctincrease 50);
Additional datafiles can be associated with the tablespace using the following command:
|
Note The datafile path will need to be changed to match the physical drives on the host Oracle server. |
SQL> alter tablespace cdn add DATAFILE 'e:\Oracle\OraData\cdn1\cdn2.dbf' SIZE 250M REUSE default storage(initial 25K next 20K minextents 1 maxextents unlimited pctincrease 50);
Step 2 Increase the size of the rollback segments.
|
Note Rollback segments are used to keep information about the current transaction so that, if an error occurs, the database can be returned to the original state it was in before the transaction began. |
Step 3 List the names of the rollback segments.
SQL> select segment_name from dba_rollback_segs;
Step 4 For each name listed in Step 3, change the max extents to be unlimited.
SQL> alter rollback segment SEGMENTNAME STORAGE (NEXT 2 M MAXEXTENTS unlimited);
You may also want to create a database user for the Cisco CDN Software Service Provider Edition.
Step 5 Create the CDN Software Service Provider Edition user "USERNAME" with default tablespaces and the password "PASSWORD."
SQL> create user USERNAME identified by PASSWORD default tablespace cdn temporary tablespace cdntemp;
|
Note The Cisco CDN Software Service Provider Edition dbsetup script can also create users but an administrator account such as "dba" or "system" must be entered. |
Step 6 Grant access rights to the new user USERNAME.
SQL> grant CREATE SESSION, connect, resource to USERNAME;
You can use dbsetup to create your database schema, but you can also install the Cisco CDN Software Service Provider Edition database schema by using a SQL script shipped with the Cisco CDN Software Service Provider Edition. This script contains the table definitions for the Cisco CDN Software Service Provider Edition and can be modified to change things such as tablespace declarations, but the actual table column definition should remain unchanged.
To load and run the script you must first reconnect to the database using SQL-PLUS and login as the database user for the Cisco CDN Software Service Provider Edition. Then use the start command to run the following MerlotCreate.sql script:
SQL> start LOCALPATH\MerlotCreate.sql
The Cisco CDN Software Service Provider Edition uses the Domain Name System (DNS) to route requests to the Content Engines. Before the system can serve content, DNS must be configured.
The public interface of each Content Router must be assigned a domain name, and DNS must be able to resolve that name both forwards and backwards, domain name to IP address and IP address to domain name.
Routed domains are created by accessing the Cisco CDN Software Service Provider Edition user interface on the Content Distribution Manager. A routed domain is a hostname used for a Web page. This is the name used internally for routing. It is also the name used by end-users that appears in URLs. The user interface permits routed domains to be created even if DNS is not configured, but they are not accessible until the parent delegated domain is configured in DNS. A delegated domain is a domain suffix within which routed domains are assigned. A delegated domain is generally a third-level domain name, for example, web.example.net. It is possible for many routed domains to be created within a single delegated domain.
Delegated domains must be configured using conventional DNS tools. To configure a delegated domain, list the Content Router public interface names as name servers for the domain.
There are two naming conventions that can be used for domain names. If the routed domains should appear as subdomains of the customer, a delegated domain must be created within each customer domain:
|
Note In the following examples, sp.net is an Internet service provider serving content for company example.com. |
$ORIGIN example.com online IN NS sp-cr1.sp.net. IN NS sp-cr2.sp.net. IN NS sp-cr3.sp.net.
In this example, web.online.example.com is a possible routed domain that could be created within the delegated domain online.example.com.
Domain names can be created within the service provider domain. In this case, a single delegated domain can be shared by all customers, and the customer does not have to change the existing DNS entries. However, the routed domain would then include the domain name of the service provider.
In the following example, example.content.sp.net is a possible routed domain that could be created within the delegated domain content.sp.net.
$ORIGIN sp.net content IN NS sp-cr1.sp.net. IN NS sp-cr2.sp.net. IN NS sp-cr3.sp.net.
The following sections provide you with instructions for configuring your CDN devices.
|
Note You must configure the Content Distribution Manager first. Then you can configure each of your Content Routers and Content Engines in any order you want. |
The Content Distribution Manager is located at the logical central point of the network to control all operations associated with system policies, network device settings, content control, user interface, billing, and event logging.
The following instructions explain how to configure the Content Distribution Manager. For information about configuring other devices, see the "Configuring a Content Router" section and the "Configuring a Content Engine" section.
|
Note If you use DNS, you must configure DNS before you begin configuring the Content Distribution Manager. For information about configuring DNS, see "Configuring DNS" section. |
To configure the Cisco CDN Software Service Provider Edition for the Content Distribution Manager, follow these steps:
Step 2 Log in as root with the password default.
Step 3 Enter a meaningful name for the Content Distribution Manager.
Step 4 Enter a meaningful description of the Content Distribution Manager.
Step 5 To accept the Content Distribution Manager's default port number, press Enter.
Step 6 To accept the default database vendor, press Enter.
|
Note You must accept Oracle as the default database vendor. |
Step 7 Enter the IP address or fully qualified domain name of the Oracle database server for the database hostname.
Step 8 To accept the default database listener port, press Enter.
or
Enter the port number that you specified when you installed the Oracle server listener.
Step 9 To accept the default database service name, press Enter.
or
Enter the name that you specified when you installed the Oracle listener.
Step 10 Enter a valid Oracle database username.
Step 11 Enter the database password that you specified when you created the Oracle username.
Step 12 Enter the tablespace used in the Oracle database.
Step 13 Enter the temporary tablespace used in the Oracle database.
All the information you entered now displays so you can confirm it or correct it if needed.
Step 14 If the displayed information is correct, enter y. If the displayed information is incorrect, type n and enter the correct information.
Step 15 To set up the network using netsetup, type y.
|
Note You must use netsetup to set up the network. |
Step 16 Enter the number of the Ethernet interface that you want to use for the private interface.
|
Note The default is 0. |
Step 17 If your network uses a DHCP server for a private interface, enter y. If your network does not use a DHCP server, enter n then enter the following information:
Step 18 If you do not use a DNS server, press Enter. If you use DNS servers, enter the DNS server IP address for each DNS server. When you have specified the last DNS server, press Enter.
Step 19 To bring the network online, type y.
Step 20 To register the Content Distribution Manager, enter y.
Step 21 At the root prompt, enter dbsetup.
Since you set up Oracle before you began this configuration, the user exists. Now dbsetup asks if you want to delete the user.
Step 22 Type n to maintain the user.
Dbsetup now validates whether database tables exist. You create them now unless you already created the database schema using the SQL script shipped with the Cisco CDN Service Provider Edition software, described in the "Setting Up the Oracle 8i DBMS" section.
Step 23 To create the database tables, enter y.
Step 24 Enter the database administrator username.
Step 25 Enter the database administrator password.
Step 26 To initialize the database tables, enter y.
Step 27 At the root prompt, reboot the Content Distribution Manager.
You should now be able to open the Content Distribution Manager user interface from your Web browser by typing the following URL for the Content Distribution Manager:
https://Name_of_Content_Distribution_Manager
or by typing the IP address:
https://IP_address_of_Content_Distribution_Manager
When you are prompted whether to accept the server certificate, click Yes.
A request for a username and password displays. Enter the default username admin and the default password default.
|
Note Although you are provided with a default username and password, you should change them. |
Content Routers are deployed at strategic locations within the network. The following steps explain how to configure a Content Router.
|
Note You must configure each of the Content Routers in your network. |
For information about configuring other devices, see the "Configuring the Content Distribution Manager" section and the "Configuring a Content Engine" section.
|
Note If you use DNS, you must configure DNS before you begin configuring the Content Routers. For information about configuring DNS, see "Configuring DNS" section. |
To configure the Cisco CDN Software Service Provider Edition for a Content Router, follow these steps:
Step 2 Log in as root with the password default.
Step 3 Enter a meaningful name for the Content Router.
Step 4 Enter a meaningful description of the Content Router.
Step 5 Enter the IP address or the fully qualified domain name of the Content Distribution Manager's DNS name.
Step 6 To accept the Content Distribution Manager's default port number, press Enter.
All the information you entered now displays so you can confirm it or correct it if needed.
Step 7 If the displayed information is correct, enter y. If the displayed information is incorrect, type n then enter the correct information.
Step 8 To set up the network using netsetup, enter y.
|
Note You must use netsetup to set up the network. |
Step 9 Enter the number of the Ethernet interface that you want to use for the private interface.
|
Note The default is 0. |
Step 10 If your network uses a DHCP server for a private interface, enter y. If your network does not use a DHCP server, enter n then enter the following information:
Step 11 Enter the number of the Ethernet interface that you want to use for the public interface.
|
Note The default is 0. |
Step 12 Enter a static IP address for the public IP address.
Step 13 If you do not use a DNS server, press Enter. If you use DNS servers, enter the DNS server IP address for each DNS server. When you have specified the last DNS server, press Enter.
Step 14 To bring the network online, type y.
Step 15 To register the Content Router, type y.
Step 16 At the root prompt, reboot the Content Router.
Content Engines are located at the edge of the network to store and deliver content to users. The following instructions explain how to configure a Content Engine.
|
Note You must configure each of the Content Engines in your network. |
For information about configuring other devices, see the "Configuring the Content Distribution Manager" section and the "Configuring a Content Router" section.
|
Note If you use DNS, you must configure DNS before you begin configuring the Content Engines. For information about configuring DNS, see "Configuring DNS" section. |
To configure the Cisco CDN Software Service Provider Edition software for a Content Engine, follow these steps:
Step 2 Log in as root with the password default.
Step 3 Enter a meaningful name for the Content Engine.
Step 4 Enter a meaningful description of the Content Engine.
Step 5 Enter the IP address or the fully qualified domain name of the Content Distribution Manager's DNS name.
Step 6 To accept the Content Distribution Manager's default port number, press Enter.
All the information you entered now displays so you can confirm it or correct it if needed.
Step 7 If the displayed information is correct, enter y. If the displayed information is incorrect, type n, and then enter the correct information.
Step 8 To set up the network using netsetup, enter y.
|
Note You must use netsetup to set up the network. |
Step 9 Enter the number of the Ethernet interface that you want to use for the private interface.
|
Note The default is 0. |
Step 10 If your network uses a DHCP server for a private interface, enter y. If your network does not use a DHCP server, enter n, and then enter the following information:
Step 11 Enter the number of the Ethernet interface that you want to use for the public interface.
|
Note The default is 0. |
Step 12 Enter a static IP address for the public IP address.
Step 13 If you do not use a DNS server, press Enter. If you use DNS servers, enter the DNS server IP address for each DNS server. When you have specified the last DNS server, press Enter.
Step 14 To bring the network online, type y.
Step 15 To register the Content Engine, type y.
Step 16 At the root prompt, reboot the Content Engine.
The Cisco CDN Software Service Provider Edition includes the SystemEDGE Agent by Empire Technologies, Inc. The SystemEDGE Agent is preconfigured to allow any community to have read-only access to its enterprise Management Information Base (MIB). The enterprise MIB is organized into sections on host configuration, kernel configuration, mounted devices, users and groups, remote command execution, processes, streams, performance monitoring, inter-process communications, NFS and RPC statistics, and buffer statistics for network buffers, streams buffers, and I/O buffer cache.
Before you can use the SystemEDGE SNMP manager (or a manager from another vendor) to view statistics provided by the SystemEDGE Agent, you must license the SystemEDGE Agent on each device. The procedure for licensing the SystemEDGE Agent is provided here. You can also find detailed licensing instructions in Section 2.10 of the SystemEDGE Agent User Guide, which can be found in PDF format on your Cisco CDN Software Service Provider Edition CD.
Before you begin the licensing procedure, you should contact Empire Technologies for SystemEDGE Agent account information. You'll need this account information when you license the SystemEDGE Agent on your devices. For information about contacting Empire Technologies, see http://www.empire.com.
|
Note You need to license the SystemEDGE Agent for each device on which you want to use the SystemEDGE Agent. Each device that you are licensing must have an Internet connection. |
To license your Empire SystemEDGE SNMP Agent on a Cisco CDN Software device, follow these steps:
Step 2 Type rw to remount the file system (/) as read-write.
Step 3 Using your preferred editor, edit the file:
/cisco/merlot/config/sysedge.cf
to uncomment this line:
#community private read-write 127.0.0.1
by removing the #. The resulting line should read:
community private read-write 127.0.0.1
|
Note This enables any community named private and using this device to have read-write access to the MIB. You should revert back to read-only access after licensing. |
Step 4 Save the file, then restart the SystemEDGE Agent using the following command line:
/etc/rc.d/init.d/sysedge restart
Step 5 Run:
/cisco/merlot/sysedge/bin/licenseme
and respond to the prompts by entering the SystemEDGE Agent account information that Empire Technologies provided to you:
Step 6 Type ro to remount the file system (/) as read-only.
Step 7 Restart the SystemEdge Agent using the following command line:
/etc/rc.d/init.d/sysedge restart
If automated licensing is not available, you can get the license key by going to http://www.empire.com/license and entering your account information, along with the public key found in /cisco/merlot/config/sysedge.lic. After submitting the license request, the Empire Web server generates a license key and displays it in your Web browser. You must append this license key (exactly as you see it in your browser) to the file /cisco/merlot/config/sysedge.lic.
Posted: Wed Sep 27 14:19:34 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.