|
|
This chapter describes the default configuration of the Cisco uBR905 cable access router. With this configuration, the Cisco uBR905 router functions in its "plug and play" DOCSIS-bridging mode, performing as a DOCSIS-compliant two-way cable modem. Every DOCSIS-compliant cable modem provides the following minimum set of features:
The following sections describe the configuration for "plug and play" DOCSIS bridging:
The DHCP server configuration and DOCSIS configuration file are required for every DOCSIS-compliant cable modem. The Cisco IOS image and configuration files are optional, depending on the needs of the subscribers. The remaining configurations are optional, depending on the needs of the subscribers.
The information described in this chapter applies to every Cisco uBR905 cable access router that is used in a DOCSIS-compliant network. Additional configuration steps might be needed, however, to support additional features, such as IPSec encryption—this additional configuration is described in the other chapters in this guide.
The DOCSIS specification (SP-RFI-IO5-991105 or later revision) requires that a DOCSIS-compliant cable modem connect to a DHCP server at power-on or reset to establish temporary IP connectivity with the cable network. This enables the cable modem to download the additional configuration information needed to establish a permanent connection with the headend and cable network.
The DHCP server can be a CMTS with DHCP server capabilities (such as a Cisco uBR7200 series universal broadband router), or it can be a dedicated server located at the headend. The server can be configured manually for each cable modem, or it can be part of an automated provisioning system such as Cisco Network Registrar (CNR).
The DHCP server provides the information shown in Table 2-1 to each cable modem.
| Parameter | Description | ||
|---|---|---|---|
IP address for the cable modem's cable interface | This IP address typically is assigned dynamically, but the service provider can also statically assign IP addresses on the basis of each modem's MAC address.
| ||
IP subnet mask for the cable modem's cable interface | This subnet mask typically is used for all cable modems using the same downstream, but this depends on the setup of the CMTS network and subscriber needs. | ||
IP address for the TFTP server | This TFTP server provides the DOCSIS configuration file to the cable modem and is typically a dedicated server located at the headend. | ||
IP address for the DHCP relay agent | A DHCP relay agent is required if the DHCP server is located on a different network than the IP address assigned to the cable modem's cable interface. The DHCP relay agent is also used if the DHCP server is providing IP addresses to the CPE devices connected to the cable modem, and the CPE devices are on a different subnet than the cable modem. | ||
Complete filename for the DOCSIS configuration file | This is the filename for the DOCSIS configuration file that the cable modem should download from the TFTP server. | ||
IP address for one or more time of day (ToD) servers | The cable modem uses the ToD server to get the current date and time so that it can accurately timestamp its SNMP messages and error log entries. | ||
One or more IP addresses for the routers that will forward IP traffic from the cable modem | Typically, the CMTS acts as the default gateway for the cable modem. | ||
One or more IP addresses for System Log (SYSLOG) servers | The cable modem can send its error log messages to the SYSLOG servers, which are optional and typically located at the headend. |
After making a successful DHCP request, the cable modem contacts the ToD server to get the current date and time. It also begins the TFTP download of the DOCSIS configuration file, which is described in the next section, DOCSIS Configuration File.
 |
Note At this point in the registration process, the DHCP server provides an IP address only for the cable modem, not for the CPE devices it is connecting to the network. The same DHCP server can provide the IP addresses for the CPE devices after the cable modem goes online, or the cable modem itself can be configured as a DHCP server (see "Routing with DHCP Server" section). |
The DOCSIS specification requires that a DOCSIS-compliant cable modem download a DOCSIS configuration file during its power-on or reset sequence. This file must be in the format described in the SP-RFI-IO5-991105 specification (or later revision) and must contain the information shown in Table 2-2.
|
Note The parameters shown in Table 2-2 are organized according to the categories used in the Cisco DOCSIS Cable Modem Configuration tool , which is available on CCO at http://www.cisco.com/support/toolkit/CableModem. (You must have an account on CCO to access this tool.) |
| Parameter1 | Description | ||
|---|---|---|---|
| Radio Frequency Parameters | |||
Downstream Frequency | Specifies the center frequency (in multiples of 62500 Hz) for the downstream channel to be used by the router. (This parameter does not need to be specified in the configuration file because the router will scan the downstream for available frequencies, but it can be specified to ensure that the router conforms to the provider's channel plan.) | ||
Upstream Channel ID | Specifies channel ID for the upstream channel to be used by the router. (This parameter does not need to be specified in the configuration file because it is set dynamically by the CMTS during provisioning.) | ||
Network Access Configuration | Determines whether CPE devices attached to the cable modem are allowed access to the cable network. The default is to allow access for CPE devices (which is required for normal operations). | ||
| Class of Service | |||
Class of Service ID | Specifies the ID for this class of service (1 to 16). | ||
Maximum Downstream Rate | Specifies the maximum downstream data rate (in bits/sec) allowed for traffic associated with this class of service. (This is a limit, not a guarantee of service.) | ||
Maximum Upstream Rate | Specifies the maximum upstream data rate (in bits/sec) allowed for traffic associated with this class of service. (This is a limit, not a guarantee of service.) | ||
Upstream Channel Priority | Specifies the priority for upstream traffic (0 to 7, where 7 is highest priority). | ||
Minimum Upstream Rate | Specifies the minimum upstream data rate (in bits/sec) that is guaranteed for traffic associated with this class of service. | ||
Maximum Upstream Channel Burst | Specifies the maximum size of burst traffic to be allowed on this upstream channel. The size is specified in bytes, 0 to 65535, where 0 is no limit. If this field is set to a non-zero value, it should be set to at least 1800 so that it is greater than the maximum Ethernet frame size of 1518 plus the associated packet overhead). | ||
Class of Service Privacy Enable | Specifies whether BPI encryption should be enabled on traffic associated with this class of service (1 enables BPI encryption, 0 disables BPI encryption). | ||
| Vendor-Specific Options | |||
Vendor ID | The three-byte Organization Unique Identifier for the vendor, which is also usually the first three bytes of the cable modem's MAC address. This value is usually expressed as a hexadecimal number. This field should be "00000C" for Cisco Systems routers. | ||
Vendor-Specific Options | Contains any arbitrary values that are defined by the manufacturer of the cable modem. The Cisco uBR905 cable access router uses this field to identify the Cisco IOS configuration file that should be downloaded (if any). Arbitrary Cisco IOS commands can also be specified in this field. | ||
| SNMP Management | |||
SNMP Write-Access Control and SNMP MIB Objects | Allows the service provider to set arbitrary SNMP attributes on the cable modem. For the Cisco uBR905 router, these two fields are typically used to enable SNMP management of the router because SNMP management is disabled by default.
| ||
| Baseline Privacy Interface Configuration | |||
Authorize Wait Timeout | Specifies the retransmission interval, in seconds, of Authorization Request messages from the Authorize Wait state. Valid values are 2 to 30. | ||
Reauthorize Wait Timeout | Specifies the retransmission interval, in seconds, of Reauthorization Request messages from the Authorize Wait state. Valid values are 2 to 30. | ||
Authorization Grace Timeout | Specifies the grace period for re-authorization, in seconds. Valid values are 1 to 1800. | ||
Operational Wait Timeout | Specifies the retransmission interval, in seconds, of Key Requests from the Operational Wait state. Valid values are 1 to 10. | ||
Rekey Wait Timeout | Specifies the retransmission interval, in seconds, of Key Requests from the Rekey Wait state. Valid values are 1 to 10. | ||
TEK Grace Time | Specifies the grace period for re-keying, in seconds. Valid values are 1 to 1800. | ||
Authorize Reject Wait Timeout | Specifies how long, in seconds, a cable modem waits in the Authorize Reject Wait state after receiving an Authorization Reject. Valid values are 60 to 1800. | ||
| Customer Premises Equipment | |||
Maximum Number of CPEs | Determines the maximum number of CPE devices that can use the cable modem to connect to the cable network. The default value is 1. In bridging mode, the Cisco uBR905 router supports a maximum number of 254 CPE devices. | ||
CPE Ethernet MAC Address | Configures the cable modem with the MAC addresses for one or more CPE devices that are allowed to connect to the cable network. Entering values in this field is optional because the cable modem can learn the MAC addresses of CPE devices dynamically, up to the maximum allowable number. However, DOCSIS cable modems give priority to the CPE devices whose MAC addresses are in the configuration file. | ||
| Software Upgrade | |||
TFTP Software Server IP Address | Specifies the IP address for the TFTP server that will provide software images. This server does not necessarily have to be the same TFTP server that provided the DOCSIS configuration file. | ||
Software Image Filename | Specifies the fully-qualified path name for the software image that the cable modem should be running. If necessary, the cable modem uses TFTP to download this image from the software server. | ||
| Miscellaneous | |||
Concatenation Support | Specifies whether the cable modem supports DOCSIS 1.1 concatenation of upstream packet requests. | ||
Use RFC2104 HMAC-MD5 | Specifies the algorithm used to compute the CMTS Message Integrity Check (MIC). If yes, the HMAC-MD5 algorithm specified in RFC 2104 is used; otherwise, the algorithm specified by RFC 1321 is used. (The algorithm used must match the one used on the CMTS.) | ||
CMTS Authentication | Specifies an authentication string to be used between the provisioning server (which creates the configuration files) and the CMTS. It allows the CMTS to authenticate the CM provisioning with a central authentication service, such as a RADIUS server. This field is typically used only for one-way cable modems that use telco-return. | ||
| 1The DOCSIS configuration file also contains fields for one-way cable modems that use telco-return, but these fields do not apply to the Cisco uBR905 router, which is a two-way cable modem. |
The DOCSIS configuration file contains the filename for the software image that the Cisco uBR905 router must be running. If this filename does not match the software image that is currently installed on the router, the router must use the TFTP protocol to download the new image from the server specified in the DOCSIS configuration file.
After the new software image has been downloaded, the Cisco uBR905 router resets itself and repeats the entire power-on and provisioning process. This includes downloading the DOCSIS configuration file again. However, because the software image is stored in non-volatile Flash memory, the router does not have to download it again—the software download occurs only when the service provider specifies a new software image filename in the DOCSIS configuration file.
If the Cisco uBR905 router cannot download the new image, it retries the download, up to a maximum of 16 attempts. If the router still cannot download the image, it falls back to its previous software image and attempts to go online with that image.
The service provider can also force the Cisco uBR905 router to download new software by putting a new image filename in the DOCSIS configuration file and resetting the router. This should be done only after warning the customer that the modem will be offline for a period of several minutes.
|
Note Because it can take several minutes for this download to be accomplished and for the Cisco uBR905 router to repeat its power-on sequence, the desired software image can also be installed on the router at the warehouse. In this case, the DOCSIS configuration files for each router should also be updated with the proper filename. |
The DOCSIS configuration file uses the type 43 Vendor-Specific Options field to specify that the Cisco uBR905 router should download a Cisco IOS configuration file. The router's console port is automatically disabled as part of this process to prevent users at the remote site from reconfiguring the router.
|
Note Downloading a Cisco IOS configuration file is not usually required for plug-and-play bridging. Instead, this procedure typically is required only when configuring the advanced feature sets described in the other chapters of this guide. |
Table 2-3 shows the values that would be entered in the Vendor-Specific Information Field (VSIF) to download a Cisco IOS configuration file and automatically disable the console port.
| Field | Value |
|---|---|
Subtype | 128 |
Length | Number of characters in the filename |
Filename | Complete filename, including path, for the Cisco IOS configuration file on the TFTP servers specified in the DOCSIS configuration file. |
Table 2-4 shows the values that would be entered in the Vendor-Specific Information Field (VSIF) to specify a CLI command that should be executed after the Cisco uBR905 cable access router processes the DOCSIS configuration file and comes online.
| Field | Value |
|---|---|
Subtype | 131 |
Length | Number of characters in the command |
CLI Command | The ASCII characters of one CLI command, as you would type it at the CLI prompt. To specify multiple commands, use this option once for each command. |
|
Note For more information about the Cisco IOS configuration file, see "Using Cisco IOS Software." |
The following example shows a typical Cisco IOS configuration for a Cisco uBR905 router that is operating in "plug and play" DOCSIS-compliant bridging mode.
version 12.1 service config no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname uBR905 ! clock timezone - 4 ip subnet-zero no ip routing ! interface Ethernet0 no ip directed-broadcast no ip route-cache bridge-group 59 bridge-group 59 spanning-disabled ! interface cable-modem0 ip address docsis no ip directed-broadcast no ip route-cache bridge-group 59 bridge-group 59 spanning-disabled ! ip classless no ip http server no service finger ! ! line con 0 transport input none line vty 0 4 ! end
This configuration shows the following requirements for DOCSIS-compliant bridging:
In its plug-and-play bridging mode, the Cisco uBR905 router does not need any additional configuration to support the computers or other CPE devices that will access the Internet through the router's connection to the cable network. However, the PCs and CPE devices must be configured to support DHCP allocation of IP addresses.
Each computer and CPE device performs this configuration differently. For Windows 95, for example, you open up the Network control panel, select the computer's TCP/IP Ethernet adapter, and set the IP address configuration to "Obtain an IP address automatically."
To reconfigure the Cisco uBR905 router to support DOCSIS-compliant bridging after it has been configured for routing, log in to the Cisco uBR905 router, enter global configuration mode, and enter the following commands:
| Command | Purpose | |
|---|---|---|
Step 1 | ubr905(config)# no ip routing | Disables IP routing on the Cisco uBR905 router. |
Step 2 | ubr905(config)# int e 0 | Enters interface configuration mode for the Ethernet interface. |
Step 3 | ubr905(config-if)# no ip address | Removes the IP address from the Ethernet interface. |
Step 4 | ubr905(config-if)# no ip route-cache | Removes the high-speed switching caches for IP routing. |
Step 5 | ubr905(config-if)# bridge-group bridge-group | Assigns the Ethernet interface to a bridge spanning group (choose an arbitrary integer from 1-63). |
Step 6 | ubr905(config-if)# bridge-group bridge-group spanning-disabled | Disables the spanning tree on the Ethernet interface. |
Step 7 | ubr905(config-if)# exit | Exits the interface configuration mode for the Ethernet interface. |
Step 8 | ubr905(config)# int c 0 | Enters interface configuration mode for the cable interface. |
Step 9 | ubr905(config-if)# no ip address | Removes the IP address from the cable interface. |
Step 10 | ubr905(config-if)# no keep alive | Disables keepalive messages on the cable interface. |
Step 11 | ubr905(config-if)# no ip route-cache | Removes the high-speed switching caches for IP routing. |
Step 12 | ubr905(config-if)# cable modem compliant bridge | Enables DOCSIS-compliant bridging. |
Step 13 | ubr905(config-if)# bridge-group bridge-group | Assigns the cable interface to the same bridge spanning group used for the Ethernet interface. |
Step 14 | ubr905(config-if)# bridge-group bridge-group spanning-disabled | Disables the spanning tree on the cable interface. |
Step 15 | ubr905(config-if)# Ctrl-Z | Returns to privileged EXEC mode. |
Step 16 | ubr905# copy running-config startup-config | Saves the configuration to nonvolatile RAM. |
Step 17 | ubr905# show startup-config | Displays the configuration file that was just created. |
Posted: Fri Sep 15 15:12:42 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
