Cisco ACNS Software Deployment and Configuration Guide, Release 5.0 - Chapter 3: Setting Up and Registering CDN Devices [Cisco Application and Content Networking System (ACNS) Software]

Table Of Contents

Setting Up and Registering CDN Devices

Autoregistration

Manual Setup and Registration

Configuring the Device Network Settings

About Selecting Static IP Addresses or Using DHCP

Configuring Network Settings Using the Startup Dialog

Configuring Network Settings Using the CLI

Configuring the Content Distribution Manager

Registering a Device with the Content Distribution Manager

Activating Content Engines or Content Routers in the Content Distribution Manager GUI

Configuring Disk Space

Configuring the Device Mode

Configuring Network Interfaces

Configuring Multiple Network Interfaces

Configuring Multiple IP Addresses on a Single Interface

Configuring the Fibre Channel Interface

Configuring EtherChannel

Configuring Interfaces for DHCP

Setting Device Clock and Time Zone Parameters

Setting Up and Registering CDN Devices

Initial device configuration requires the registering of local network values, such as IP address, netmask, DNS host, and gateway IP address, in order to bring the device online. These values can be set automatically through the default autoregistration feature, or they can be set manually through the local command-line-interface (CLI) on the device.

Once a device is registered, the administrator activates the device through the Content Distribution Manager GUI. This allows only desired devices to participate in the CDN and to communicate with other activated nodes.

This chapter tells you how to perform an initial configuration and how to activate the device in your CDN. It contains the following sections:

•Autoregistration

•Manual Setup and Registration

•Activating Content Engines or Content Routers in the Content Distribution Manager GUI

•Configuring Disk Space

•Configuring the Device Mode

•Configuring Network Interfaces

•Setting Device Clock and Time Zone Parameters

Autoregistration

On bootup, devices running ACNS 5.0 software (with the exception of the Content Distribution Manager itself) automatically discover the Content Distribution Manager and register with it. The administrator does not have to do any manual configuration locally on the device. When the device is registered, the administrator approves the device and configures it remotely using the Content Distribution Manager GUI. (See the "Activating Content Engines or Content Routers in the Content Distribution Manager GUI" section.)

Autoregistration uses a form of Dynamic Host Configuration Protocol (DHCP). You must have a DHCP server that is configured with the host name of the Content Distribution Manager and that is capable of handling vendor class option 43 for autoregistration to work.

Note The form of DHCP used for autoregistration is not the same as the interface-level DHCP that is configurable through the ip address dhcp command. (See the "About Selecting Static IP Addresses or Using DHCP" section for an explanation of interface-level DHCP.)

The vendor class option (option 43) information needs to be sent to the CDN device in the format for encapsulated vendor-specific options as provided in RFC 2132. The relevant section of RFC 2132, Section 8.4, is reproduced here as follows:

The encapsulated vendor-specific options field should be encoded as a sequence of code/length/value fields of syntax identical to that of the DHCP options field with the following exceptions:

1. There should not be a "magic cookie" field in the encapsulated vendor-specific extensions field.

2. Codes other than 0 or 255 may be redefined by the vendor within the encapsulated vendor-specific extensions field, but should conform to the tag-length-value syntax defined in section 2.

3. Code 255 (END), if present, signifies the end of the encapsulated vendor extensions, not the end of the vendor extensions field. If no code 255 is present, then the end of the enclosing vendor-specific information field is taken as the end of the encapsulated vendor-specific extensions field.

Following the RFC standard, the DHCP server needs to send the Content Distribution Manager host name information in code/length/value format (code and length are single octets). The code for the Content Distribution Manager host name is 0x01. DHCP server management and configuration is not within the scope of the autoregistration feature.

The CDN device sends "CISCOCDN" as the vendor class identifier in option 60, to facilitate device groupings by customers.

Autoregistration DHCP also requires that the following options be present in the DHCP server's offer to be considered valid:

•Subnet-mask (option 1)

•Routers (option 3)

•Domain-name (option 15)

•Domain-name-servers (option 6)

•Host-name (option 12)

In contrast, interface-level DHCP requires only subnet-mask (option 1), and routers (option 3) for an offer to be considered valid; domain-name (option 15), domain-name-servers (option 6), and host-name (option 12) are optional. All of the above options, with the exception of domain-name-servers (option 6), replace the existing configuration on the system. The domain-name-servers option is added to the existing list of name servers with the restriction of a maximum of eight name servers.

Autoregistration is enabled by default on the first interface of the device. The first interface depends on the Content Engine model as follows:

•For the CE-507, CE-507AV, CE-560, CE-560AV, CE-590, and CR-4430: FastEthernet 0/0

•For the CE-510, CE-565, CE-7305, CE-7325, and CE-7320: GigabitEthernet 1/0

If you do not have a DHCP server, the device is unable to complete autoregistration and eventually times out. You can disable autoregistration at any time after the device has booted and proceed with manual setup and registration. (See the "Manual Setup and Registration" section.)

To disable autoregistration, or to configure autoregistration on a different interface, use the no auto-register enable command in global configuration mode.

Note Autoregistration is automatically disabled if a static IP address or interface-level DHCP is configured on the same interface as autoregistration.

The following example disables autoregistration on Fast Ethernet port 0/0:
CE(config)# no auto-register enable FastEthernet 0/0
Autoregistration status can be obtained by using the following EXEC show command:
CE# show status auto-register
Manual Setup and Registration

If you do not have a DHCP server in your network, or if for some reason your DHCP server is configured incorrectly, you can set up and register a device manually.

To manually configure network settings and register your CDN devices, you must first disable autoregistration. This can be done using the startup dialog, or through the CLI after the device has booted.

Configuring the Device Network Settings

After you physically install the hardware and power up your device, you can access the ACNS software and perform an initial startup configuration.

The initial configuration defines the network settings of your devices so that they can become active on your network.

Note If you have upgraded your software from a previous ACNS software release to ACNS 5.x software, your network configuration is preserved. You do not need to reconfigure your network settings.

About Selecting Static IP Addresses or Using DHCP

During the initial configuration, you have the option of configuring a static IP address for the device or choosing DHCP. This section describes these two options.

DHCP is a communications protocol that lets network administrators manage their networks centrally and automate the assignment of IP addresses in an organization's network. When an organization sets up its computer users with a connection to the Internet, an IP address must be assigned to each device. Without DHCP, the IP address must be entered manually for each computer, and if computers move to another location in another part of the network, a new IP address must be entered. DHCP automatically sends a new IP address when a computer is connected to a different site in the network.

In the following sample startup dialog, the administrator has chosen to enable DHCP. Administrator entries are shown in bold. (See also the "Configuring Interfaces for DHCP" section.)
BOOT-100:sw-filesystems mounted, applying pending upgrades...
SW up-to-date
ACNS boot:detected no saved system configuration
  Do you want to enter basic configuration now?
  hit RETURN to enter basic configuration:0019
admin password:
re-enter password:
Please enter an interface from the following list:
   0:GigabitEthernet 1/0
   1:GigabitEthernet 2/0
enter choice:0
Enable DHCP on this interface? (y/n) [n]:y
        [0] Go to the CLI command prompt without saving this config.
        [1] Return back to the setup without saving this config.
        [2] Save this configuration to flash and go to CLI prompt.
Choose one? [2]:2
Running pre-200 hooks...
Configuring Network Settings Using the Startup Dialog

The startup dialog allows you to configure network settings using an interactive dialog instead of the CLI. If you wish, you can disable autoregistration by responding to the startup dialog prompt and configuring the first interface on your device (Ethernet 0/0 or GigabitEthernet 1/0) with either a static IP address or with interface-level DHCP. If you specify the configuration on the interface that uses autoregistration, autoregistration is automatically disabled.

You can also use the startup dialog to configure other interfaces if you have multiple interfaces on your device.

To use the startup dialog, follow these steps:

Step 1 Power up 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 and initiate the startup dialog. If you do not respond, the system continues booting and automatically registers with the Content Distribution Manager.

Step 2 Press Enter, and then enter values for the following fields as you are prompted:

•Admin password for the device

This is the case-sensitive password you want to use for the admin administrator user account. The password can include any printable character. You must enter a password for each Content Networking device.

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 at the local device.

•Interface identifier for the initial configuration

All other interfaces can be configured later with the CLI.

•IP address for the device, for example, 172.16.13.8 (if DHCP is not used)

•IP network mask for the device, for example, 255.255.255.224 (if DHCP is not used)

A netmask specifies which part of the IP address refers to the network; you can accept the default value by pressing Enter, or you can enter a different value.

•Gateway IP address for the device, for example, 172.16.13.7 (if DHCP is not used)

This is the IP address of the router that allows the device to connect to the network.

•DNS name server IP address for the device

•Host name for the device

•Domain name for the device

Step 3 Choose whether or not to save the configuration. After you choose to save the configuration, 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. The administrator has chosen not to enable DHCP.
BOOT-100:sw-filesystems mounted, applying pending upgrades...
SW up-to-date
ACNS boot:detected no saved system configuration
  Do you want to enter basic configuration now?
  hit RETURN to enter basic configuration:0016
admin password:
re-enter password:
Please enter an interface from the following list:
   0:GigabitEthernet 1/0
   1:GigabitEthernet 2/0
enter choice:0
Enable DHCP on this interface? (y/n) [n]:n
local IP address:172.16.13.8
IP network mask:255.255.255.254
gateway IP address:172.16.13.7
DNS server:10.10.10.11
host name:CE7305
domain name:cisco.com
		[0] Go to the CLI command prompt without saving this config.
        [1] Return back to the setup without saving this config.
        [2] Save this configuration to flash and go to CLI prompt.
Choose one? [2]:2
Running pre-200 hooks...
Step 4 To make sure that a primary interface has been configured, use the show running-config command. A primary interface should have been chosen automatically by the software during the initial startup; however, you can configure a primary interface manually by using the primary-interface command in global configuration mode.

Configuring Network Settings Using the CLI

To configure network settings using the CLI, follow these steps:

Step 1 Power up the device and log on through the console or by opening a Telnet session.

Step 2 From the device CLI, enter configuration mode.
CE-507# config
CE-507(config)#
Step 3 In configuration mode, configure the device network settings by using the following commands:

•Configure your Ethernet interface for DHCP.
interface {FastEthernet | GigabitEthernet} slot/port ip address dhcp
The remainder of your network settings are configured automatically. You have finished configuring your network settings.

•Alternatively, configure the static IP address of your Ethernet interface.
interface {FastEthernet | GigabitEthernet} slot/port ip address ip-address netmask 
Step 4 Continue configuring the remaining network settings.

a. Configure the IP domain name.
ip domain-name name1 name2 name3
b. Configure the host name.
hostname name
c. Configure the IP name server.
ip name-server {ip-addresses | serial-lookup}
d. Configure the IP default gateway.
ip default-gateway ip-address
e. Configure the primary interface.
primary-interface {FastEthernet | GigabitEthernet} slot/port [dhcp]
Configuring the Content Distribution Manager

You must configure the Content Distribution Manager before you can register any Content Engines or Content Routers with the Content Distribution Manager.

In ACNS 5.0 software, Content Distribution Managers can run in two different roles: primary and standby. The primary role is the default. You can have only one primary Content Distribution Manager that is active in your network; however, you can have any number of Content Distribution Managers running in a standby role for failover and redundancy. We recommend that you configure the primary Content Distribution Manager first.

To configure the primary Content Distribution Manager, follow these steps:

Step 1 Create and initialize the management database, and enable CDN services by using the cms enable command.
CDM-4630(config)# cms enable
Step 2 Verify that services have been enabled by using the show cms processes command. For example:
CDM-4630# show cms processes
Service cms_httpd running
Service cms_ui running
Service cms_cdm running
CDM-4630#
Step 3 Verify the current running configuration by using the show running-config command.
CDM-4630# show running-config
A message similar to the following should appear:
--------------------------------------------------------------------------------
...
cms enable
!
...
--------------------------------------------------------------------------------
Step 4 To save the configuration, use the copy running-config startup-config command.
CDM-4630# copy running-config startup-config 
To configure a standby Content Distribution Manager role, follow these steps:

Step 1 Configure the standby Content Distribution Manager role by using the cdm role command.
CDM-4630# cdm role standby
Step 2 Configure the standby Content Distribution Manager with the IP address of the primary Content Distribution Manager by using the cdm ip {ip-address | hostname} command. For example:
CDM-4630# cdm ip 10.1.1.90
This command associates the device with the primary Content Distribution Manager so that it can be approved as a part of the network.

Step 3 Create and initialize the management database, and enable CDN services by using the cms enable command.
CDM-4630(config)# cms enable
Step 4 Verify that services have been enabled by using the show cms processes command. For example:
CDM-4630# show cms processes
Service cms_httpd running
Service cms_ui running
Service cms_cdm running
Step 5 Verify the current running configuration by using the show running-config command.
CDM-4630# show running-config
A message similar to the following should appear:
--------------------------------------------------------------------------------
...
cms enable
!
...
--------------------------------------------------------------------------------
Step 6 To save the configuration, use the copy running-config startup-config command.
CDM-4630# copy running-config startup-config 
Registering a Device with the Content Distribution Manager

Before a newly installed Content Engine or Content Router can be recognized by the Content Distribution Manager, it must be registered with the Content Distribution Manager. Registering a new device (also called a node) is done through the CLI.

Note To deregister a device, see the "Deleting a Content Router" section or the "Deleting a Content Engine" section.

To register a new device, follow these steps:

Step 1 Set the IP address or host name of the Content Distribution Manager with which the device is to be associated by using the cdm ip command in global configuration mode.
CE-507# config
CE-507(config)# cdm ip {ip-address|hostname}
This command associates the device with the Content Distribution Manager so that the device can be approved as a part of the network.

After the device is configured with the Content Distribution Manager IP address, it presents a self-signed security certificate as well as other essential information, such as its IP address or host name, disk space allocation, and so forth, to the Content Distribution Manager.

Step 2 To register the device, create and initialize the management database, and enable CDN services, use the cms enable command in global configuration mode.
CE-507(config)# cms enable
The configuration management subsystem (CMS) database table stores the device node configuration, allowing the node to be centrally managed from the Content Distribution Manager.

Step 3 Use the show cms info command to verify that your device has been registered.
CE-507# show cms info
A message similar to the following should appear:
Registration information :
CDM address                      = 10.1.1.90                       
Device Mode                      = ce                              
Model                            = CE507                           
Node Id                          = 84                              
ce507#
Step 4 To verify that CMS is running, use the show cms processes command in EXEC mode.
CE-507# show cms processes
A message similar to the following should appear:
Service cms_ce running
ce507#
Step 5 Verify the current running configuration by using the show running-config command.
CE-507# show running-config
A message similar to the following should appear:
--------------------------------------------------------------------------------
...
cms enable
!
...
--------------------------------------------------------------------------------
Step 6 To save the configuration, use the copy running-config startup-config command.
CE-507# copy running-config startup-config 
The next step is to authorize the device to become part of the CDN by approving the device in the Content Distribution Manager GUI.

Activating Content Engines or Content Routers in the Content Distribution Manager GUI

New Content Engines and Content Routers need to be approved by the network administrator. The network administrator approves each device by making it active in the Content Distribution Manager GUI. This security feature prevents unauthorized devices from joining the network.

Note Before you can access the Content Distribution Manager GUI, you must use the CLI to register yourself as a user. Use the username global configuration command to configure your name and password for GUI access. (See the

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:

https://name_of_Content_Distribution_Manager:8443

or

https://IP_address_of_Content_Distribution_Manager:8443

A window appears, requesting your username and password.

Step 2 Enter the administrator username admin and the password default and then click OK. The Cisco Application and Content Networking System Home window appears.

Step 3 Choose Devices > Content Engines. A list of all your registered Content Engines appears.

For Content Routers, choose Devices > Content Routers.

Step 4 Click the Edit icon next to the device name. The Modifying Content Engine (or Content Router) window appears. (See Figure 3-1.)

Figure 3-1 Modifying Content Engine Window

Step 5 Choose a location from the Location drop-down list. If you have not yet created any locations, you must do this first. You cannot activate a device without assigning it to a location. (See the "Creating and Modifying Locations" section.)

Step 6 To activate the Content Engine or Content Router, check the Activate check box in the Modifying Content Engine (or Content Router) window.

Step 7 Click Submit.

When the device becomes active, the status changes from "Inactive" to "Online" and the check box no longer appears.

Other Content Engine properties can be configured now or at a later time. To enable routing or to modify the default bandwidth settings, see the "Modifying Content Engine Properties" section.

Configuring Disk Space

If you are configuring a brand-new device, you need to create disk space for the system file system (sysfs) by using the disk config command in EXEC mode. To configure disk space, follow these steps:

Step 1 Exit configuration mode, if you have not already done so.
CE-507(config)# exit
CE-507#
Step 2 Enter the disk config command. For example, to configure the sysfs for 5 GB:
CE-507# disk config sysfs 5GB
Step 3 Reload the Content Engine for the disk configuration to take effect.
CE-507# reload
To update the disk configuration through the Content Distribution Manager GUI, follow the procedure in the "Updating Storage Capacity on Your Content Engines" section.

For further disk space allocation guidelines, see "Cisco ACNS Software Disk Space-Allocation Guidelines."

Tip For the new disk space configuration to take effect, you must first reboot the device; however, if you are going to change the device mode, you can wait to reboot until after you have configured the new device mode.

If you are attaching and configuring a Fibre Channel storage array, see the "Using a Fibre Channel Storage Array" section. Do not attempt to assign the Fibre Channel storage to the Content Engine and configure the file systems with a single reload of the Content Engine. If you do, the Fibre Channel storage assignment is recognized, but the disk configuration is not applied. An error message appears at bootup, similar to the following:
----------------------------------------------------------------------------
ruby_disk:physical disk setup appears to have changed
ruby_disk:not applying 'disk config' changes. Please re-enter via CLI.
----------------------------------------------------------------------------
If you encounter this error message, reenter your disk configuration and use the reload command on the Content Engine for the disk configuration to be applied.

Configuring the Device Mode

This section explains how to change the device mode of a newly purchased Content Engine before activating it in your CDN.

Note Additional steps are required to change the device mode of a device that is already operating as part of your CDN. See the "Repurposing a CDN Device" section.

Configuring the device mode is not a supported option on all hardware models. However, some hardware models can be configured to operate as any one of the three Content Networking device types.

The following hardware models support device mode configuration:

•CE-7305

•CE-565

To change the device mode of your eligible Content Engine, you must be prepared to configure the disk space allocations, as required by the different device modes, and to reboot the device for the new configuration to take effect.

Devices that can be reconfigured using the device mode global configuration command are shipped from the factory by default as Content Engines. When you change the device mode of a Content Engine to a Content Router or a Content Distribution Manager, you need to configure the system file system (sysfs). (See the "Configuring Disk Space" section.)

If, however, you are changing the device mode of a Content Router or a Content Distribution Manager back to a Content Engine, you must configure disk space allocations for the sysfs, cache file system (cfs), media file system (mediafs), and Content Delivery Network file system (cdnfs) that are used on the Content Engine. (See "Cisco ACNS Software Disk Space-Allocation Guidelines.") For example:
DeviceName# disk config sysfs 10% cfs 20% mediafs 10% cdnfs 60%
To configure the device mode, follow these steps:

Step 1 Boot the device and access the device CLI through the console or Telnet session.

Step 2 Enter the show device-mode current command to view the current device mode.
DeviceName# show device-mode current
Current device mode: content-engine
Step 3 Configure the new device mode by using the device mode command in global configuration mode. For example:
DeviceName# configure
DeviceName(config)# device mode content-router
Step 4 Save the configuration by issuing the write memory command or the copy running-config startup-config command.
DeviceName# write memory 
DeviceName# copy running-config startup-config
Step 5 Use the restore factory-default preserve basic-config command to reload the software and apply the device mode configuration. Your network settings are preserved.
DeviceName# restore factory-default preserve basic-config
Step 6 Verify the new configuration. Check that the current and configured device modes are the same. For example:
DeviceName# show device-mode configured
Configured Device mode: content-router
DeviceName# show device-mode current
Current device mode: content router
Step 7 Configure the disk space allocation based on the new device mode and needs of your network by using the disk config command.

After the device reloads and you have verified the device mode configuration, you are ready to register the device with the Content Distribution Manager.

Configuring Network Interfaces

In the "Configuring Network Settings Using the Startup Dialog" section and the "Configuring Network Settings Using the CLI" section, you chose an initial interface and either configured it for DHCP, or gave it a static IP address. This section describes how to configure additional interfaces using options for redundancy, load balancing, performance optimization, and so forth.

Configuring Multiple Network Interfaces

You can configure multiple network interfaces as either active-active interfaces or as active-standby interfaces. You configure multiple interfaces as active-active by using the interface command and by assigning an IP address to each interface. When multiple interfaces are configured, they are active simultaneously. This configuration is used to achieve better performance. For example:
ContentEngine# configure 
ContentEngine(config)# interface FastEthernet 0/0 
ContentEngine(config-if)# ip address 10.10.10.10 255.0.0.0
With an active-standby configuration, the interfaces are configured using the standby command, and they remain inactive unless an active interface fails. When an active network interface fails (because of cable trouble, Layer 2 switch failure, high error count, or other failure), and that interface is part of a standby group, a standby interface can become active and take the load off the failed interface. With active-standby interface configuration, only one interface is active at a given time. Active-standby is used mainly for fault tolerance purposes. The performance of the device is limited by the single active interface.
ContentEngine# configure
ContentEngine(config)# interface FastEthernet 0/1
ContentEngine(config-if)# standby ?
  <1-4>  Standby group number
ContentEngine(config-if)# standby 3 ?
  errors    Set the maximum number of errors allowed on this interface
  ip        Set the IP address of a standby group
  priority  Set the priority of an interface for the standby group
ContentEngine(config-if)# standby 3 errors ?     
  <0-4294967295>  Max. no. of errors allowed on this interface for the standby
                  group
ContentEngine(config-if)# standby 3 ip ?
  A.B.C.D  IP address of the standby group
ContentEngine(config-if)# standby 3 priority ?
  <0-4294967295>  Priority of this interface for the standby group
To configure standby interfaces, interfaces are logically assigned to standby groups. The following rules define the standby group relationships:

•A standby group comprises two or more interfaces.

•The maximum number of standby groups on a Content Engine is four.

•Each interface is assigned a unique IP address, and each standby group is assigned a unique standby IP address, shared by all members of the group.

•Configure the duplex and speed settings of the standby group member interfaces for better reliability.

•Each interface in a standby group is assigned a priority. The operational interface with the highest priority in a standby group is the active interface. Only the active interface uses the group IP address.

•If the active interface fails, the operational interface in its standby group that is assigned the next highest priority becomes active.

•If all the members of a standby group fail and then one recovers, the ACNS software brings up the standby group on the operational interface.

•The priority of an interface in a standby group can be changed at runtime. The interface that has the highest priority after this change becomes the new active interface (the default action is to preempt the currently active interface if an interface with higher priority exists).

•The maximum number of errors allowed on the active interface before the interface is shut down and the standby is brought up is configured with the errors option, which is disabled by default.

Note Interface IP addresses and standby group IP addresses must be on different subnets to ensure reliable operation. You can use dummy IP addresses in the private address space to serve as interface primary IP addresses, and use the real Content Engine IP address to serve as the standby group IP address in a different subnet to satisfy this requirement.

Note Make sure to configure the primary interface default gateway using the ip default-gateway global configuration command instead of the ip route command.

Example

This example configures three interfaces to be part of the same standby group, with interface 3/0 as the active interface.
Console(config)# interface fastEthernet 3/0 standby 1 ip 172.16.10.10 255.255.254.0
Console(config)# interface fastEthernet 3/1 standby 1 ip 172.16.10.10 255.255.254.0
Console(config)# interface fastEthernet 3/2 standby 1 ip 172.16.10.10 255.255.254.0
Console(config)# interface fastEthernet 3/0 standby 1 priority 300
Console(config)# interface fastEthernet 3/1 standby 1 priority 200
Console(config)# interface fastEthernet 3/2 standby 1 priority 100
Console(config)# interface fastEthernet 3/0 standby 1 errors 10000
Console(config)# interface fastEthernet 3/1 standby 1 errors 10000
Console(config)# interface fastEthernet 3/2 standby 1 errors 10000
Use the show standby command to view your standby interface configuration.
Console# show standby
Standby Group:1 
IP address: 172.16.10.10, netmask: 255.255.254.0
Maximum errors allowed on the active interface: 10000 
	Member interfaces: 
		FastEthernet 3/0        priority: 300
		FastEthernet 3/1        priority: 200
		FastEthernet 3/2        priority: 100
Active interface: FastEthernet 3/0 
Configuring Multiple IP Addresses on a Single Interface

You can configure more than one IP address on the same interface by using the interface secondary command. You can configure up to four secondary IP addresses on a single interface. This configuration allows the device to be present in more than one subnet and can be used to optimize response time, because it allows the content to go directly from the Content Engine to the client that is requesting the information without being redirected through a router. The Content Engine becomes visible to the client because both are configured on the same subnet. For example:
ContentEngine# configure 
ContentEngine(config)# interface FastEthernet 0/0 
ContentEngine(config-if)# ip address 10.10.10.10 255.0.0.0 secondary
Configuring the Fibre Channel Interface

ACNS 5.0 software supports Fibre Channel interfaces. Fibre Channel is the chosen technology for interconnecting storage devices and servers in a storage area network (SAN). In a SAN, the storage need not be directly attached to the server, and data transfer happens over a high-throughput, high-availability network. Fibre Channel is capable of operating at speeds of 1gigabit per second (Gbps) and 2 Gbps.

To detect the presence of Fibre Channel storage, the storage array must be configured to assign storage space for the Content Engine, and the Content Engine must be reloaded before it can detect the storage assignment. To confirm whether the Content Engine has detected the storage assignment, use the show disks and the show disks details commands.

To configure the Fibre Channel interface on the Content Engine, use the interface FibreChannel slot/port command in interface configuration mode. For example:
DeviceName# configure
DeviceName(config)# interface FibreChannel 0/0
DeviceName(config-if)#?
  exit   Exit from this submode
  mode   Change the fibre channel interface operating mode
  no     Negate a command or set its defaults
  speed  Change the fibre channel interface speed
DeviceName(config-if)# mode ?
  autosense        Use this mode to have the CE autosense
  direct-attached  Use this mode when the CE is directly connected to storage array 
  switched         Use this mode when the CE is connected to a switch
DeviceName(config-if)# speed ?
  1          1Gbps
  2          2Gbps
  autosense  autosense
For a complete description of the interface FibreChannel command syntax and usage, refer to the Cisco ACNS Software Command Reference, Release 5.0 document.

For information regarding which Fibre Channel storage arrays are supported by Cisco Systems, refer to the Release Notes for Cisco ACNS Software, Release 5.0.

Configuring EtherChannel

EtherChannel for ACNS 5.0 software supports the grouping of up to four same-speed network interfaces into one virtual interface. This grouping capability allows the setting or removing of a virtual interface that consists of two, three, or four Fast Ethernet interfaces or two Gigabit Ethernet interfaces. EtherChannel also provides interoperability with Cisco routers, switches, and other networking devices or hosts supporting EtherChannel; load balancing; and automatic failure detection and recovery based on each interface's current link status.

To create an EtherChannel, use the interface portchannel number command in interface configuration mode. For example:
CE# configure
CE(config)# interface portchannel 2 
CE(config-if)# ip address 10.10.10.10 255.0.0.0
CE(config-if)# exit
To remove an EtherChannel, use the no form of the command:
CE(config)# interface portchannel 2 
CE(config-if)# no ip address 10.10.10.10 255.0.0.0
CE(config-if)# exit
CE(config)# no interface portchannel 2 
To add or remove ports from an EtherChannel, use the commands in the following examples. These commands add a physical Fast Ethernet port to a previously created Fast EtherChannel. The channel number is the same as the channel number specified when the port channel interface was created. You can use either the Fast Ethernet or the Gigabit Ethernet ports to form an EtherChannel; however, an EtherChannel cannot contain both Fast Ethernet and Gigabit Ethernet interfaces. Note that a physical interface can be added to an EtherChannel subject to the device configuration.

To add an interface to a channel group:
CE# configure
CE(config)# interface FastEthernet 1/1
CE(config-if)# channel-group 2
CE(config-if)# exit
To remove an interface from a channel group:
CE(config)# interface FastEthernet 1/1
CE(config-if)# no channel-group 2
CE(config-if)# exit
To configure for load balancing, use the port-channel load-balance command.
CE(config)# port-channel load-balance 
The following load-balance options are available:
dst-ip       Destination IP Address
dst-mac      Destination MAC Address
round-robin  Round robin each interface (default)
Round robin allows traffic to be distributed evenly between all interfaces in the channel group. The other balancing options give you flexibility in choosing interfaces when sending an Ethernet frame. The load-balance command is effective globally. If two channel groups are configured, they have to use the same load-balancing option.

Configuring Interfaces for DHCP

Note Autoregistration must be disabled before you can manually configure an interface for DHCP.

An interface can be enabled for DHCP by using the ip address dhcp interface configuration command. You can also configure the client-id or hostname options using this command. The client identifier is an ASCII value.
ContentEngine# configure
ContentEngine(config)# interface FastEthernet 0/0
ContentEngine(config-if)#
ContentEngine(config-if)# ip address ?
  A.B.C.D  IP address of the interface
  dhcp     IP Address negotiated via DHCP
ContentEngine(config-if)# ip address dhcp ?
  client-id  Specify client-id to use
  hostname   Specify value for hostname option
  <cr>       
The Content Engine sends its configured client identifier and host name to the DHCP server when requesting network information. DHCP servers can be configured to identify the client identifier information and the host name information that the Content Engine is sending, and then send back the specific network settings that are assigned to the Content Engine.

Setting Device Clock and Time Zone Parameters

If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP] server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Content Engine calculates Coordinated Universal Time (UTC) based on the time zone set by the clock timezone global configuration command.

Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock. The set keyword sets the software clock.

	Cisco ACNS Software Deployment and Configuration Guide, Release 5.0
	Chapter 3: Setting Up and Registering CDN Devices
Cisco ACNS Software Deployment and Configuration Guide, Release 5.0 Index Title Page Preface Chapter 1: Understanding the ACNS 5.0 Content Delivery Network Chapter 2: Using the Content Distribution Manager GUI and Assigning Privileges Chapter 3: Setting Up and Registering CDN Devices Chapter 4: Setting up Content Routing in the CDN Chapter 5: Configuring the CDN Chapter 6: Creating Manifest Files Chapter 7: Working with CDN Devices Chapter 8: Configuring Services on CDN Devices Chapter 9: Creating and Managing Playlists for Video Playback Chapter 10: Upgrading and Downgrading the Software Chapter 11: Monitoring and Troubleshooting the Content Delivery Network Appendix A: Disk Space-Allocation Guidelines Appendix B: IP Multicasting	Download this chapter Chapter 3: Setting Up and Registering CDN Devices Download the complete book Cisco ACNS Software Deployment and Configuration Guide, Release 5.0 (PDF - 7 MB) Table Of Contents Setting Up and Registering CDN Devices Autoregistration Manual Setup and Registration Configuring the Device Network Settings About Selecting Static IP Addresses or Using DHCP Configuring Network Settings Using the Startup Dialog Configuring Network Settings Using the CLI Configuring the Content Distribution Manager Registering a Device with the Content Distribution Manager Activating Content Engines or Content Routers in the Content Distribution Manager GUI Configuring Disk Space Configuring the Device Mode Configuring Network Interfaces Configuring Multiple Network Interfaces Configuring Multiple IP Addresses on a Single Interface Configuring the Fibre Channel Interface Configuring EtherChannel Configuring Interfaces for DHCP Setting Device Clock and Time Zone Parameters Setting Up and Registering CDN Devices Initial device configuration requires the registering of local network values, such as IP address, netmask, DNS host, and gateway IP address, in order to bring the device online. These values can be set automatically through the default autoregistration feature, or they can be set manually through the local command-line-interface (CLI) on the device. Once a device is registered, the administrator activates the device through the Content Distribution Manager GUI. This allows only desired devices to participate in the CDN and to communicate with other activated nodes. This chapter tells you how to perform an initial configuration and how to activate the device in your CDN. It contains the following sections: •Autoregistration •Manual Setup and Registration •Activating Content Engines or Content Routers in the Content Distribution Manager GUI •Configuring Disk Space •Configuring the Device Mode •Configuring Network Interfaces •Setting Device Clock and Time Zone Parameters Autoregistration On bootup, devices running ACNS 5.0 software (with the exception of the Content Distribution Manager itself) automatically discover the Content Distribution Manager and register with it. The administrator does not have to do any manual configuration locally on the device. When the device is registered, the administrator approves the device and configures it remotely using the Content Distribution Manager GUI. (See the "Activating Content Engines or Content Routers in the Content Distribution Manager GUI" section.) Autoregistration uses a form of Dynamic Host Configuration Protocol (DHCP). You must have a DHCP server that is configured with the host name of the Content Distribution Manager and that is capable of handling vendor class option 43 for autoregistration to work. Note The form of DHCP used for autoregistration is not the same as the interface-level DHCP that is configurable through the ip address dhcp command. (See the "About Selecting Static IP Addresses or Using DHCP" section for an explanation of interface-level DHCP.) The vendor class option (option 43) information needs to be sent to the CDN device in the format for encapsulated vendor-specific options as provided in RFC 2132. The relevant section of RFC 2132, Section 8.4, is reproduced here as follows: The encapsulated vendor-specific options field should be encoded as a sequence of code/length/value fields of syntax identical to that of the DHCP options field with the following exceptions: 1. There should not be a "magic cookie" field in the encapsulated vendor-specific extensions field. 2. Codes other than 0 or 255 may be redefined by the vendor within the encapsulated vendor-specific extensions field, but should conform to the tag-length-value syntax defined in section 2. 3. Code 255 (END), if present, signifies the end of the encapsulated vendor extensions, not the end of the vendor extensions field. If no code 255 is present, then the end of the enclosing vendor-specific information field is taken as the end of the encapsulated vendor-specific extensions field. Following the RFC standard, the DHCP server needs to send the Content Distribution Manager host name information in code/length/value format (code and length are single octets). The code for the Content Distribution Manager host name is 0x01. DHCP server management and configuration is not within the scope of the autoregistration feature. The CDN device sends "CISCOCDN" as the vendor class identifier in option 60, to facilitate device groupings by customers. Autoregistration DHCP also requires that the following options be present in the DHCP server's offer to be considered valid: •Subnet-mask (option 1) •Routers (option 3) •Domain-name (option 15) •Domain-name-servers (option 6) •Host-name (option 12) In contrast, interface-level DHCP requires only subnet-mask (option 1), and routers (option 3) for an offer to be considered valid; domain-name (option 15), domain-name-servers (option 6), and host-name (option 12) are optional. All of the above options, with the exception of domain-name-servers (option 6), replace the existing configuration on the system. The domain-name-servers option is added to the existing list of name servers with the restriction of a maximum of eight name servers. Autoregistration is enabled by default on the first interface of the device. The first interface depends on the Content Engine model as follows: •For the CE-507, CE-507AV, CE-560, CE-560AV, CE-590, and CR-4430: FastEthernet 0/0 •For the CE-510, CE-565, CE-7305, CE-7325, and CE-7320: GigabitEthernet 1/0 If you do not have a DHCP server, the device is unable to complete autoregistration and eventually times out. You can disable autoregistration at any time after the device has booted and proceed with manual setup and registration. (See the "Manual Setup and Registration" section.) To disable autoregistration, or to configure autoregistration on a different interface, use the no auto-register enable command in global configuration mode. Note Autoregistration is automatically disabled if a static IP address or interface-level DHCP is configured on the same interface as autoregistration. The following example disables autoregistration on Fast Ethernet port 0/0: CE(config)# no auto-register enable FastEthernet 0/0 Autoregistration status can be obtained by using the following EXEC show command: CE# show status auto-register Manual Setup and Registration If you do not have a DHCP server in your network, or if for some reason your DHCP server is configured incorrectly, you can set up and register a device manually. To manually configure network settings and register your CDN devices, you must first disable autoregistration. This can be done using the startup dialog, or through the CLI after the device has booted. Configuring the Device Network Settings After you physically install the hardware and power up your device, you can access the ACNS software and perform an initial startup configuration. The initial configuration defines the network settings of your devices so that they can become active on your network. Note If you have upgraded your software from a previous ACNS software release to ACNS 5.x software, your network configuration is preserved. You do not need to reconfigure your network settings. About Selecting Static IP Addresses or Using DHCP During the initial configuration, you have the option of configuring a static IP address for the device or choosing DHCP. This section describes these two options. DHCP is a communications protocol that lets network administrators manage their networks centrally and automate the assignment of IP addresses in an organization's network. When an organization sets up its computer users with a connection to the Internet, an IP address must be assigned to each device. Without DHCP, the IP address must be entered manually for each computer, and if computers move to another location in another part of the network, a new IP address must be entered. DHCP automatically sends a new IP address when a computer is connected to a different site in the network. In the following sample startup dialog, the administrator has chosen to enable DHCP. Administrator entries are shown in bold. (See also the "Configuring Interfaces for DHCP" section.) BOOT-100:sw-filesystems mounted, applying pending upgrades... SW up-to-date ACNS boot:detected no saved system configuration Do you want to enter basic configuration now? hit RETURN to enter basic configuration:0019 admin password: re-enter password: Please enter an interface from the following list: 0:GigabitEthernet 1/0 1:GigabitEthernet 2/0 enter choice:0 Enable DHCP on this interface? (y/n) [n]:y [0] Go to the CLI command prompt without saving this config. [1] Return back to the setup without saving this config. [2] Save this configuration to flash and go to CLI prompt. Choose one? [2]:2 Running pre-200 hooks... Configuring Network Settings Using the Startup Dialog The startup dialog allows you to configure network settings using an interactive dialog instead of the CLI. If you wish, you can disable autoregistration by responding to the startup dialog prompt and configuring the first interface on your device (Ethernet 0/0 or GigabitEthernet 1/0) with either a static IP address or with interface-level DHCP. If you specify the configuration on the interface that uses autoregistration, autoregistration is automatically disabled. You can also use the startup dialog to configure other interfaces if you have multiple interfaces on your device. To use the startup dialog, follow these steps: Step 1 Power up 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 and initiate the startup dialog. If you do not respond, the system continues booting and automatically registers with the Content Distribution Manager. Step 2 Press Enter, and then enter values for the following fields as you are prompted: •Admin password for the device This is the case-sensitive password you want to use for the admin administrator user account. The password can include any printable character. You must enter a password for each Content Networking device. 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 at the local device. •Interface identifier for the initial configuration All other interfaces can be configured later with the CLI. •IP address for the device, for example, 172.16.13.8 (if DHCP is not used) •IP network mask for the device, for example, 255.255.255.224 (if DHCP is not used) A netmask specifies which part of the IP address refers to the network; you can accept the default value by pressing Enter, or you can enter a different value. •Gateway IP address for the device, for example, 172.16.13.7 (if DHCP is not used) This is the IP address of the router that allows the device to connect to the network. •DNS name server IP address for the device •Host name for the device •Domain name for the device Step 3 Choose whether or not to save the configuration. After you choose to save the configuration, 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. The administrator has chosen not to enable DHCP. BOOT-100:sw-filesystems mounted, applying pending upgrades... SW up-to-date ACNS boot:detected no saved system configuration Do you want to enter basic configuration now? hit RETURN to enter basic configuration:0016 admin password: re-enter password: Please enter an interface from the following list: 0:GigabitEthernet 1/0 1:GigabitEthernet 2/0 enter choice:0 Enable DHCP on this interface? (y/n) [n]:n local IP address:172.16.13.8 IP network mask:255.255.255.254 gateway IP address:172.16.13.7 DNS server:10.10.10.11 host name:CE7305 domain name:cisco.com [0] Go to the CLI command prompt without saving this config. [1] Return back to the setup without saving this config. [2] Save this configuration to flash and go to CLI prompt. Choose one? [2]:2 Running pre-200 hooks... Step 4 To make sure that a primary interface has been configured, use the show running-config command. A primary interface should have been chosen automatically by the software during the initial startup; however, you can configure a primary interface manually by using the primary-interface command in global configuration mode. Configuring Network Settings Using the CLI To configure network settings using the CLI, follow these steps: Step 1 Power up the device and log on through the console or by opening a Telnet session. Step 2 From the device CLI, enter configuration mode. CE-507# config CE-507(config)# Step 3 In configuration mode, configure the device network settings by using the following commands: •Configure your Ethernet interface for DHCP. interface {FastEthernet \| GigabitEthernet} slot/port ip address dhcp The remainder of your network settings are configured automatically. You have finished configuring your network settings. •Alternatively, configure the static IP address of your Ethernet interface. interface {FastEthernet \| GigabitEthernet} slot/port ip address ip-address netmask Step 4 Continue configuring the remaining network settings. a. Configure the IP domain name. ip domain-name name1 name2 name3 b. Configure the host name. hostname name c. Configure the IP name server. ip name-server {ip-addresses \| serial-lookup} d. Configure the IP default gateway. ip default-gateway ip-address e. Configure the primary interface. primary-interface {FastEthernet \| GigabitEthernet} slot/port [dhcp] Configuring the Content Distribution Manager You must configure the Content Distribution Manager before you can register any Content Engines or Content Routers with the Content Distribution Manager. In ACNS 5.0 software, Content Distribution Managers can run in two different roles: primary and standby. The primary role is the default. You can have only one primary Content Distribution Manager that is active in your network; however, you can have any number of Content Distribution Managers running in a standby role for failover and redundancy. We recommend that you configure the primary Content Distribution Manager first. To configure the primary Content Distribution Manager, follow these steps: Step 1 Create and initialize the management database, and enable CDN services by using the cms enable command. CDM-4630(config)# cms enable Step 2 Verify that services have been enabled by using the show cms processes command. For example: CDM-4630# show cms processes Service cms_httpd running Service cms_ui running Service cms_cdm running CDM-4630# Step 3 Verify the current running configuration by using the show running-config command. CDM-4630# show running-config A message similar to the following should appear: -------------------------------------------------------------------------------- ... cms enable ! ... -------------------------------------------------------------------------------- Step 4 To save the configuration, use the copy running-config startup-config command. CDM-4630# copy running-config startup-config To configure a standby Content Distribution Manager role, follow these steps: Step 1 Configure the standby Content Distribution Manager role by using the cdm role command. CDM-4630# cdm role standby Step 2 Configure the standby Content Distribution Manager with the IP address of the primary Content Distribution Manager by using the cdm ip {ip-address \| hostname} command. For example: CDM-4630# cdm ip 10.1.1.90 This command associates the device with the primary Content Distribution Manager so that it can be approved as a part of the network. Step 3 Create and initialize the management database, and enable CDN services by using the cms enable command. CDM-4630(config)# cms enable Step 4 Verify that services have been enabled by using the show cms processes command. For example: CDM-4630# show cms processes Service cms_httpd running Service cms_ui running Service cms_cdm running Step 5 Verify the current running configuration by using the show running-config command. CDM-4630# show running-config A message similar to the following should appear: -------------------------------------------------------------------------------- ... cms enable ! ... -------------------------------------------------------------------------------- Step 6 To save the configuration, use the copy running-config startup-config command. CDM-4630# copy running-config startup-config Registering a Device with the Content Distribution Manager Before a newly installed Content Engine or Content Router can be recognized by the Content Distribution Manager, it must be registered with the Content Distribution Manager. Registering a new device (also called a node) is done through the CLI. Note To deregister a device, see the "Deleting a Content Router" section or the "Deleting a Content Engine" section. To register a new device, follow these steps: Step 1 Set the IP address or host name of the Content Distribution Manager with which the device is to be associated by using the cdm ip command in global configuration mode. CE-507# config CE-507(config)# cdm ip {ip-address\|hostname} This command associates the device with the Content Distribution Manager so that the device can be approved as a part of the network. After the device is configured with the Content Distribution Manager IP address, it presents a self-signed security certificate as well as other essential information, such as its IP address or host name, disk space allocation, and so forth, to the Content Distribution Manager. Step 2 To register the device, create and initialize the management database, and enable CDN services, use the cms enable command in global configuration mode. CE-507(config)# cms enable The configuration management subsystem (CMS) database table stores the device node configuration, allowing the node to be centrally managed from the Content Distribution Manager. Step 3 Use the show cms info command to verify that your device has been registered. CE-507# show cms info A message similar to the following should appear: Registration information : CDM address = 10.1.1.90 Device Mode = ce Model = CE507 Node Id = 84 ce507# Step 4 To verify that CMS is running, use the show cms processes command in EXEC mode. CE-507# show cms processes A message similar to the following should appear: Service cms_ce running ce507# Step 5 Verify the current running configuration by using the show running-config command. CE-507# show running-config A message similar to the following should appear: -------------------------------------------------------------------------------- ... cms enable ! ... -------------------------------------------------------------------------------- Step 6 To save the configuration, use the copy running-config startup-config command. CE-507# copy running-config startup-config The next step is to authorize the device to become part of the CDN by approving the device in the Content Distribution Manager GUI. Activating Content Engines or Content Routers in the Content Distribution Manager GUI New Content Engines and Content Routers need to be approved by the network administrator. The network administrator approves each device by making it active in the Content Distribution Manager GUI. This security feature prevents unauthorized devices from joining the network. Note Before you can access the Content Distribution Manager GUI, you must use the CLI to register yourself as a user. Use the username global configuration command to configure your name and password for GUI access. (See the 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: https://name_of_Content_Distribution_Manager:8443 or https://IP_address_of_Content_Distribution_Manager:8443 A window appears, requesting your username and password. Step 2 Enter the administrator username admin and the password default and then click OK. The Cisco Application and Content Networking System Home window appears. Step 3 Choose Devices > Content Engines. A list of all your registered Content Engines appears. For Content Routers, choose Devices > Content Routers. Step 4 Click the Edit icon next to the device name. The Modifying Content Engine (or Content Router) window appears. (See Figure 3-1.) Figure 3-1 Modifying Content Engine Window Step 5 Choose a location from the Location drop-down list. If you have not yet created any locations, you must do this first. You cannot activate a device without assigning it to a location. (See the "Creating and Modifying Locations" section.) Step 6 To activate the Content Engine or Content Router, check the Activate check box in the Modifying Content Engine (or Content Router) window. Step 7 Click Submit. When the device becomes active, the status changes from "Inactive" to "Online" and the check box no longer appears. Other Content Engine properties can be configured now or at a later time. To enable routing or to modify the default bandwidth settings, see the "Modifying Content Engine Properties" section. Configuring Disk Space If you are configuring a brand-new device, you need to create disk space for the system file system (sysfs) by using the disk config command in EXEC mode. To configure disk space, follow these steps: Step 1 Exit configuration mode, if you have not already done so. CE-507(config)# exit CE-507# Step 2 Enter the disk config command. For example, to configure the sysfs for 5 GB: CE-507# disk config sysfs 5GB Step 3 Reload the Content Engine for the disk configuration to take effect. CE-507# reload To update the disk configuration through the Content Distribution Manager GUI, follow the procedure in the "Updating Storage Capacity on Your Content Engines" section. For further disk space allocation guidelines, see "Cisco ACNS Software Disk Space-Allocation Guidelines." Tip For the new disk space configuration to take effect, you must first reboot the device; however, if you are going to change the device mode, you can wait to reboot until after you have configured the new device mode. If you are attaching and configuring a Fibre Channel storage array, see the "Using a Fibre Channel Storage Array" section. Do not attempt to assign the Fibre Channel storage to the Content Engine and configure the file systems with a single reload of the Content Engine. If you do, the Fibre Channel storage assignment is recognized, but the disk configuration is not applied. An error message appears at bootup, similar to the following: ---------------------------------------------------------------------------- ruby_disk:physical disk setup appears to have changed ruby_disk:not applying 'disk config' changes. Please re-enter via CLI. ---------------------------------------------------------------------------- If you encounter this error message, reenter your disk configuration and use the reload command on the Content Engine for the disk configuration to be applied. Configuring the Device Mode This section explains how to change the device mode of a newly purchased Content Engine before activating it in your CDN. Note Additional steps are required to change the device mode of a device that is already operating as part of your CDN. See the "Repurposing a CDN Device" section. Configuring the device mode is not a supported option on all hardware models. However, some hardware models can be configured to operate as any one of the three Content Networking device types. The following hardware models support device mode configuration: •CE-7305 •CE-565 To change the device mode of your eligible Content Engine, you must be prepared to configure the disk space allocations, as required by the different device modes, and to reboot the device for the new configuration to take effect. Devices that can be reconfigured using the device mode global configuration command are shipped from the factory by default as Content Engines. When you change the device mode of a Content Engine to a Content Router or a Content Distribution Manager, you need to configure the system file system (sysfs). (See the "Configuring Disk Space" section.) If, however, you are changing the device mode of a Content Router or a Content Distribution Manager back to a Content Engine, you must configure disk space allocations for the sysfs, cache file system (cfs), media file system (mediafs), and Content Delivery Network file system (cdnfs) that are used on the Content Engine. (See "Cisco ACNS Software Disk Space-Allocation Guidelines.") For example: DeviceName# disk config sysfs 10% cfs 20% mediafs 10% cdnfs 60% To configure the device mode, follow these steps: Step 1 Boot the device and access the device CLI through the console or Telnet session. Step 2 Enter the show device-mode current command to view the current device mode. DeviceName# show device-mode current Current device mode: content-engine Step 3 Configure the new device mode by using the device mode command in global configuration mode. For example: DeviceName# configure DeviceName(config)# device mode content-router Step 4 Save the configuration by issuing the write memory command or the copy running-config startup-config command. DeviceName# write memory DeviceName# copy running-config startup-config Step 5 Use the restore factory-default preserve basic-config command to reload the software and apply the device mode configuration. Your network settings are preserved. DeviceName# restore factory-default preserve basic-config Step 6 Verify the new configuration. Check that the current and configured device modes are the same. For example: DeviceName# show device-mode configured Configured Device mode: content-router DeviceName# show device-mode current Current device mode: content router Step 7 Configure the disk space allocation based on the new device mode and needs of your network by using the disk config command. After the device reloads and you have verified the device mode configuration, you are ready to register the device with the Content Distribution Manager. Configuring Network Interfaces In the "Configuring Network Settings Using the Startup Dialog" section and the "Configuring Network Settings Using the CLI" section, you chose an initial interface and either configured it for DHCP, or gave it a static IP address. This section describes how to configure additional interfaces using options for redundancy, load balancing, performance optimization, and so forth. Configuring Multiple Network Interfaces You can configure multiple network interfaces as either active-active interfaces or as active-standby interfaces. You configure multiple interfaces as active-active by using the interface command and by assigning an IP address to each interface. When multiple interfaces are configured, they are active simultaneously. This configuration is used to achieve better performance. For example: ContentEngine# configure ContentEngine(config)# interface FastEthernet 0/0 ContentEngine(config-if)# ip address 10.10.10.10 255.0.0.0 With an active-standby configuration, the interfaces are configured using the standby command, and they remain inactive unless an active interface fails. When an active network interface fails (because of cable trouble, Layer 2 switch failure, high error count, or other failure), and that interface is part of a standby group, a standby interface can become active and take the load off the failed interface. With active-standby interface configuration, only one interface is active at a given time. Active-standby is used mainly for fault tolerance purposes. The performance of the device is limited by the single active interface. ContentEngine# configure ContentEngine(config)# interface FastEthernet 0/1 ContentEngine(config-if)# standby ? <1-4> Standby group number ContentEngine(config-if)# standby 3 ? errors Set the maximum number of errors allowed on this interface ip Set the IP address of a standby group priority Set the priority of an interface for the standby group ContentEngine(config-if)# standby 3 errors ? <0-4294967295> Max. no. of errors allowed on this interface for the standby group ContentEngine(config-if)# standby 3 ip ? A.B.C.D IP address of the standby group ContentEngine(config-if)# standby 3 priority ? <0-4294967295> Priority of this interface for the standby group To configure standby interfaces, interfaces are logically assigned to standby groups. The following rules define the standby group relationships: •A standby group comprises two or more interfaces. •The maximum number of standby groups on a Content Engine is four. •Each interface is assigned a unique IP address, and each standby group is assigned a unique standby IP address, shared by all members of the group. •Configure the duplex and speed settings of the standby group member interfaces for better reliability. •Each interface in a standby group is assigned a priority. The operational interface with the highest priority in a standby group is the active interface. Only the active interface uses the group IP address. •If the active interface fails, the operational interface in its standby group that is assigned the next highest priority becomes active. •If all the members of a standby group fail and then one recovers, the ACNS software brings up the standby group on the operational interface. •The priority of an interface in a standby group can be changed at runtime. The interface that has the highest priority after this change becomes the new active interface (the default action is to preempt the currently active interface if an interface with higher priority exists). •The maximum number of errors allowed on the active interface before the interface is shut down and the standby is brought up is configured with the errors option, which is disabled by default. Note Interface IP addresses and standby group IP addresses must be on different subnets to ensure reliable operation. You can use dummy IP addresses in the private address space to serve as interface primary IP addresses, and use the real Content Engine IP address to serve as the standby group IP address in a different subnet to satisfy this requirement. Note Make sure to configure the primary interface default gateway using the ip default-gateway global configuration command instead of the ip route command. Example This example configures three interfaces to be part of the same standby group, with interface 3/0 as the active interface. Console(config)# interface fastEthernet 3/0 standby 1 ip 172.16.10.10 255.255.254.0 Console(config)# interface fastEthernet 3/1 standby 1 ip 172.16.10.10 255.255.254.0 Console(config)# interface fastEthernet 3/2 standby 1 ip 172.16.10.10 255.255.254.0 Console(config)# interface fastEthernet 3/0 standby 1 priority 300 Console(config)# interface fastEthernet 3/1 standby 1 priority 200 Console(config)# interface fastEthernet 3/2 standby 1 priority 100 Console(config)# interface fastEthernet 3/0 standby 1 errors 10000 Console(config)# interface fastEthernet 3/1 standby 1 errors 10000 Console(config)# interface fastEthernet 3/2 standby 1 errors 10000 Use the show standby command to view your standby interface configuration. Console# show standby Standby Group:1 IP address: 172.16.10.10, netmask: 255.255.254.0 Maximum errors allowed on the active interface: 10000 Member interfaces: FastEthernet 3/0 priority: 300 FastEthernet 3/1 priority: 200 FastEthernet 3/2 priority: 100 Active interface: FastEthernet 3/0 Configuring Multiple IP Addresses on a Single Interface You can configure more than one IP address on the same interface by using the interface secondary command. You can configure up to four secondary IP addresses on a single interface. This configuration allows the device to be present in more than one subnet and can be used to optimize response time, because it allows the content to go directly from the Content Engine to the client that is requesting the information without being redirected through a router. The Content Engine becomes visible to the client because both are configured on the same subnet. For example: ContentEngine# configure ContentEngine(config)# interface FastEthernet 0/0 ContentEngine(config-if)# ip address 10.10.10.10 255.0.0.0 secondary Configuring the Fibre Channel Interface ACNS 5.0 software supports Fibre Channel interfaces. Fibre Channel is the chosen technology for interconnecting storage devices and servers in a storage area network (SAN). In a SAN, the storage need not be directly attached to the server, and data transfer happens over a high-throughput, high-availability network. Fibre Channel is capable of operating at speeds of 1gigabit per second (Gbps) and 2 Gbps. To detect the presence of Fibre Channel storage, the storage array must be configured to assign storage space for the Content Engine, and the Content Engine must be reloaded before it can detect the storage assignment. To confirm whether the Content Engine has detected the storage assignment, use the show disks and the show disks details commands. To configure the Fibre Channel interface on the Content Engine, use the interface FibreChannel slot/port command in interface configuration mode. For example: DeviceName# configure DeviceName(config)# interface FibreChannel 0/0 DeviceName(config-if)#? exit Exit from this submode mode Change the fibre channel interface operating mode no Negate a command or set its defaults speed Change the fibre channel interface speed DeviceName(config-if)# mode ? autosense Use this mode to have the CE autosense direct-attached Use this mode when the CE is directly connected to storage array switched Use this mode when the CE is connected to a switch DeviceName(config-if)# speed ? 1 1Gbps 2 2Gbps autosense autosense For a complete description of the interface FibreChannel command syntax and usage, refer to the Cisco ACNS Software Command Reference, Release 5.0 document. For information regarding which Fibre Channel storage arrays are supported by Cisco Systems, refer to the Release Notes for Cisco ACNS Software, Release 5.0. Configuring EtherChannel EtherChannel for ACNS 5.0 software supports the grouping of up to four same-speed network interfaces into one virtual interface. This grouping capability allows the setting or removing of a virtual interface that consists of two, three, or four Fast Ethernet interfaces or two Gigabit Ethernet interfaces. EtherChannel also provides interoperability with Cisco routers, switches, and other networking devices or hosts supporting EtherChannel; load balancing; and automatic failure detection and recovery based on each interface's current link status. To create an EtherChannel, use the interface portchannel number command in interface configuration mode. For example: CE# configure CE(config)# interface portchannel 2 CE(config-if)# ip address 10.10.10.10 255.0.0.0 CE(config-if)# exit To remove an EtherChannel, use the no form of the command: CE(config)# interface portchannel 2 CE(config-if)# no ip address 10.10.10.10 255.0.0.0 CE(config-if)# exit CE(config)# no interface portchannel 2 To add or remove ports from an EtherChannel, use the commands in the following examples. These commands add a physical Fast Ethernet port to a previously created Fast EtherChannel. The channel number is the same as the channel number specified when the port channel interface was created. You can use either the Fast Ethernet or the Gigabit Ethernet ports to form an EtherChannel; however, an EtherChannel cannot contain both Fast Ethernet and Gigabit Ethernet interfaces. Note that a physical interface can be added to an EtherChannel subject to the device configuration. To add an interface to a channel group: CE# configure CE(config)# interface FastEthernet 1/1 CE(config-if)# channel-group 2 CE(config-if)# exit To remove an interface from a channel group: CE(config)# interface FastEthernet 1/1 CE(config-if)# no channel-group 2 CE(config-if)# exit To configure for load balancing, use the port-channel load-balance command. CE(config)# port-channel load-balance The following load-balance options are available: dst-ip Destination IP Address dst-mac Destination MAC Address round-robin Round robin each interface (default) Round robin allows traffic to be distributed evenly between all interfaces in the channel group. The other balancing options give you flexibility in choosing interfaces when sending an Ethernet frame. The load-balance command is effective globally. If two channel groups are configured, they have to use the same load-balancing option. Configuring Interfaces for DHCP Note Autoregistration must be disabled before you can manually configure an interface for DHCP. An interface can be enabled for DHCP by using the ip address dhcp interface configuration command. You can also configure the client-id or hostname options using this command. The client identifier is an ASCII value. ContentEngine# configure ContentEngine(config)# interface FastEthernet 0/0 ContentEngine(config-if)# ContentEngine(config-if)# ip address ? A.B.C.D IP address of the interface dhcp IP Address negotiated via DHCP ContentEngine(config-if)# ip address dhcp ? client-id Specify client-id to use hostname Specify value for hostname option <cr> The Content Engine sends its configured client identifier and host name to the DHCP server when requesting network information. DHCP servers can be configured to identify the client identifier information and the host name information that the Content Engine is sending, and then send back the specific network settings that are assigned to the Content Engine. Setting Device Clock and Time Zone Parameters If you have an outside source on your network that provides time services (such as a Network Time Protocol [NTP] server), you do not need to set the system clock manually. When setting the clock, enter the local time. The Content Engine calculates Coordinated Universal Time (UTC) based on the time zone set by the clock timezone global configuration command. Two clocks exist in the system: the software clock and the hardware clock. The software uses the software clock. The hardware clock is used only at bootup to initialize the software clock. The set keyword sets the software clock.
	© 1992-2008 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.