Beruflich Dokumente
Kultur Dokumente
Administration
Guide
Notice
EXCEPT AS INDICATED IN THE APPLICABLE SYSTEM PURCHASE AGREEMENT, THE SYSTEM,
DOCUMENTATION AND SERVICES ARE PROVIDED "AS IS", AS AVAILABLE, WITHOUT WARRANTY
OF ANY KIND. MOTOROLA MOBILITY, INC. DOES NOT WARRANT THAT THE SYSTEM WILL MEET
CUSTOMER'S REQUIREMENTS, OR THAT THEIR OPERATION WILL BE UNINTERRUPTED OR
ERROR-FREE, OR THAT ANY ERRORS CAN OR WILL BE FIXED. MOTOROLA MOBILITY, INC. HEREBY
DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, ORAL OR WRITTEN, WITH RESPECT
TO THE SYSTEM AND SERVICES INCLUDING, WITHOUT LIMITATION, ALL IMPLIED WARRANTIES OF
TITLE, NON-INFRINGEMENT, INTEGRATION, MERCHANTABILITY OR FITNESS FOR ANY
PARTICULAR PURPOSE AND ALL WARRANTIES ARISING FROM ANY COURSE OF DEALING OR
PERFORMANCE OR USAGE OF TRADE.
EXCEPT AS INDICATED IN THE APPLICABLE SYSTEM PURCHASE AGREEMENT, MOTOROLA
MOBILITY, INC. SHALL NOT BE LIABLE CONCERNING THE SYSTEM OR SUBJECT MATTER OF THIS
DOCUMENTATION, REGARDLESS OF THE FORM OF ANY CLAIM OR ACTION (WHETHER IN
CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE), FOR ANY (A) MATTER BEYOND ITS
REASONABLE CONTROL, (B) LOSS OR INACCURACY OF DATA, LOSS OR INTERRUPTION OF USE, OR
COST OF PROCURING SUBSTITUTE TECHNOLOGY, GOODS OR SERVICES, (C) INDIRECT, PUNITIVE,
INCIDENTAL, RELIANCE, SPECIAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING, BUT
NOT LIMITED TO, LOSS OF BUSINESS, REVENUES, PROFITS OR GOODWILL, OR (D) DIRECT
DAMAGES, IN THE AGGREGATE, IN EXCESS OF THE FEES PAID TO IT HEREUNDER FOR THE SYSTEM
OR SERVICE GIVING RISE TO SUCH DAMAGES DURING THE 12-MONTH PERIOD PRIOR TO THE DATE
THE CAUSE OF ACTION AROSE, EVEN IF COMPANY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. THESE LIMITATIONS ARE INDEPENDENT FROM ALL OTHER PROVISIONS OF THIS
AGREEMENT AND SHALL APPLY NOTWITHSTANDING THE FAILURE OF ANY REMEDY PROVIDED
HEREIN.
All Motorola Mobility, Inc. products are furnished under a license agreement included with the product. If you are
unable to locate a copy of the license agreement, please contact Motorola Mobility, Inc.
No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such
as translation, transformation, or adaptation) without written permission from Motorola Mobility, Inc.
Motorola Mobility reserves the right to revise this publication and to make changes in content from time to time
without obligation on the part of Motorola Mobility to provide notification of such revision or change. Motorola
Mobility provides this guide without warranty of any kind, implied or expressed, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. Motorola Mobility may make
improvements or changes in the product(s) described in this manual at any time.
MOTOROLA and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings,
LLC. All other trademarks are the property of their respective owners.
2011 Motorola Mobility, Inc. All rights reserved.
Compass ID: 379437400 Version 2
Release 6.2.0
Published: 6/11
Contents
Preface
Scope ............................................................................................................................................. xi
Audience........................................................................................................................................ xi
Documentation Set .......................................................................................................................xii
Conventions.................................................................................................................................xiv
Notes, Cautions, Warnings........................................................................................................... xv
If You Need Help ......................................................................................................................... xv
iii
Release 6.2.0
System Software........................................................................................................................1-15
Downloading Software...................................................................................................1-15
Before You Download Software......................................................................1-15
Downloading Image Files to NVRAM on the SRM........................................1-17
Downloading Image Files to Flash Memory on the SRM ...............................1-18
Upgrading BSR System Software ..................................................................................1-21
Specifying the System Image File Boot Location..........................................................1-22
System Configuration................................................................................................................1-23
Saving and Viewing Your Configuration.......................................................................1-23
Configuring SRM and Chassis Alias Information..........................................................1-24
Configuring SRM and Chassis Asset ID Information....................................................1-24
Displaying the System Configuration ............................................................................1-25
Displaying SRM and Chassis Alias Information .............................................1-25
Displaying the SRM and Chassis Asset ID Information..................................1-26
Displaying the Chassis Status ..........................................................................1-26
Displaying System Information ................................................................................................1-27
Displaying System Operation Information.....................................................................1-27
Displaying System Processing Information ...................................................................1-29
Displaying System Memory Information.......................................................................1-31
Displaying the System Version Information ..................................................................1-32
Displaying System Buffer Information ..........................................................................1-33
Displaying Module Hardware Information ....................................................................1-34
Configuring Logging
Introduction .................................................................................................................................2-1
Flash and NVRAM Memory Management Guidelines...............................................................2-2
Setting Logging Control..............................................................................................................2-3
Restricting Logging Rates...........................................................................................................2-4
Creating a Loopback Interface for Source SYSLOG IP Address ....................................2-5
Configuring System Logging ......................................................................................................2-6
Configuring Logging to a SYSLOG Server .....................................................................2-6
Configuring Console Logging..........................................................................................2-8
Configuring the Logging Buffer.......................................................................................2-9
Clearing the Logging Buffer ............................................................................2-10
iv
Release 6.2.0
Contents
Configuring TCP/IP
Introduction .................................................................................................................................3-1
Adding a Permanent ARP Entry and Timeout Value .................................................................3-2
Reverse ARP ....................................................................................................................3-3
Address Resolution Using Proxy ARP.............................................................................3-3
Configuring Broadcast Addressing .............................................................................................3-4
Configuring the MTU..................................................................................................................3-5
Configuring Static Routes ...........................................................................................................3-6
Clearing Route Table Entries ......................................................................................................3-7
Configuring the Internet Control Message Protocol ...................................................................3-8
About IRDP ......................................................................................................................3-8
Enabling IRDP..................................................................................................................3-9
Managing IRDP..............................................................................................................3-10
Enabling ICMP...............................................................................................................3-11
Tracing a Route .........................................................................................................................3-12
Managing the Router .................................................................................................................3-12
Enabling IP Source Routing ...........................................................................................3-12
Clearing Interface Counters............................................................................................3-13
Clearing IP Routes..........................................................................................................3-14
Clearing the ARP Cache.................................................................................................3-14
Release 6.2.0
Clearing IP Traffic..........................................................................................................3-14
Clearing DNS Entries .....................................................................................................3-14
Displaying TCP/IP Related Information ...................................................................................3-15
Configuring Interfaces
Introduction .................................................................................................................................4-1
Setting IP Interface Addresses ....................................................................................................4-2
Removing an IP Address ..................................................................................................4-5
Configuring Auto-Negotiation on the 10/100 Ethernet Module ......................................4-5
Verifying Your Ethernet Configuration.............................................................4-6
Configuring a Loopback Interface ..............................................................................................4-8
Configuring a Loopback Interface for TFTP Packets ....................................................4-10
Configuring Tunnels on an Interface ........................................................................................4-10
Configuring an Unnumbered Interface .....................................................................................4-12
Clearing Interface Counters ......................................................................................................4-14
Displaying Interface Information ..............................................................................................4-15
vi
Release 6.2.0
Contents
vii
Release 6.2.0
Configuring Redundancy
Introduction .................................................................................................................................7-1
SRM Redundancy .......................................................................................................................7-1
SRM Switch-over Conditions...........................................................................................7-3
SRM Redundancy Hardware Considerations...................................................................7-3
SRM Redundancy Operational Considerations................................................................7-4
Identifying the Active or Standby SRM ............................................................7-4
Conditions that Cause the SRM to Switch-over ................................................7-4
Running SRM Redundancy Functions .............................................................................7-5
Saving Your Running Configuration .................................................................7-5
Manually Switching Service to the Standby SRM.............................................7-6
Synchronizing NVRAM Between Active and Standby SRM ...........................7-6
CMTS Redundancy .....................................................................................................................7-7
CMTS Redundancy Operation .........................................................................................7-8
Voice Over IP Support .....................................................................................................7-9
Automatic CMTS Switch-Over Conditions .....................................................................7-9
CMTS Redundancy Hardware Considerations ..............................................................7-10
Viewing Redundancy Status from Module LEDs ..........................................................7-10
Managing CMTS Redundancy .......................................................................................7-11
Save the Running Configuration to the Startup Configuration........................7-11
Administratively Switching to the Standby CMTS .........................................7-11
Administratively Switching to a Primary CMTS.............................................7-15
Disabling Redundancy on a Primary CMTS Module ......................................7-16
Automatically Enabling Primary CMTS Modules...........................................7-17
Enabling Redundancy on a Primary CMTS Module .......................................7-17
NIM Redundancy ......................................................................................................................7-18
EBGP HSIM Redundancy Configuration ......................................................................7-18
Configuring Router 1 .......................................................................................7-19
Configuring Router 2 .......................................................................................7-20
Configuring the BSR........................................................................................7-21
OSPF NIM Redundancy Configuration .........................................................................7-23
Configuring Router 1 .......................................................................................7-24
Configuring Router 2 .......................................................................................7-24
Configuring the BSR........................................................................................7-25
viii
Release 6.2.0
Contents
TX32 Redundancy.....................................................................................................................7-27
Automatic CMTS Switch-Over Conditions ...................................................................7-27
Managing TX32 Redundancy.........................................................................................7-28
Save the Running Configuration to the Startup Configuration........................7-28
Administratively Switching to the Standby TX32 ...........................................7-28
Administratively Switching to a Primary TX32 ..............................................7-29
Disabling Redundancy on a Primary TX32 Module........................................7-29
Automatically Enabling Primary TX32 Modules ............................................7-30
Configuring IPDR
Introduction .................................................................................................................................9-1
Minimum Configuration...................................................................................................9-2
Advanced Configuration ..................................................................................................9-2
Enabling IPDR ............................................................................................................................9-3
Configuring the Collector............................................................................................................9-3
Configuring the Collection Interval ............................................................................................9-4
Configuring Unacknowledged IPDR records .............................................................................9-4
Configuring the Keepalive Interval for IPDR Connections ........................................................9-5
Configuring the Subscriber Transmision Rate ............................................................................9-6
Configuring a Source Interface ...................................................................................................9-6
Displaying IPDR Information .....................................................................................................9-7
ix
10
Release 6.2.0
Configuring IPv6
Introduction ...............................................................................................................................10-1
Configuring IPv6 Addresses .....................................................................................................10-2
Removing an IPv6 Address ............................................................................................10-5
Configuring IPv6 Cable Helper and Helper Addresses ............................................................10-6
Configuring IPv6 Static Routes.................................................................................................10-7
Configuring IPv6 Static Neighbors ...........................................................................................10-8
Configuring IPv6 Neighbor Discovery .....................................................................................10-8
Configuring Duplicate Address Detection .....................................................................10-9
Dynamically Configuring IPv6 Header Information......................................................10-9
Configuring Neighbor Solicitation ...............................................................................10-10
Configuring Router Advertisement ..............................................................................10-11
Configuring Reachability .............................................................................................10-11
Enabling ICMPv6 Redirects....................................................................................................10-12
Configuring IPv4 to IPv6 Address Mapping...........................................................................10-12
Configuring IPv6 to IPv4 Address Mapping...........................................................................10-12
Tracing a Route .......................................................................................................................10-13
Pinging a Device .....................................................................................................................10-14
Creating an IPv6 Cable Bundle on a Loopback Interface .......................................................10-14
Displaying IPv6 Information...................................................................................................10-16
show ipv6 dhcp ..............................................................................................10-16
show ipv6 interface ........................................................................................10-16
show ipv6 interface brief................................................................................10-17
show ipv6 neighbor........................................................................................10-17
show ipv6 route ..............................................................................................10-18
show ipv6 traffic ............................................................................................10-18
Clearing IPv6 Statistics ...........................................................................................................10-19
clear ipv6 neighbor-cache ..............................................................................10-19
clear ipv6 traffic .............................................................................................10-19
Preface
Scope
This document describes system administrative tasks used to configure and manage
the Motorola Broadband Services Router 64000 (BSR 64000). The following tasks
and procedures are described in this document:
n
Configuring Logging
Configuring TCP/IP
Configuring Interfaces
Configuring Redundancy
Configuring IPDR
Configuring IPv6
Audience
This document is for use by those persons who will install and configure the
BSR 64000 product. Only trained service personnel should install, maintain, or
replace the BSR 64000.
xi
Release 6.2.0
Documentation Set
The following documents comprise the BSR 64000 documentation set:
n
xii
Release 6.2.0
Preface
xiii
Release 6.2.0
Conventions
This document uses the conventions in the following table:
Convention
Example
Explanation
ping <ip-address>
ping 54.89.145.71
bar brackets [ ]
disable [level]
bold text
cable relay-agent-option
brace brackets {}
italic text
screen display
vertical bar |
xiv
Release 6.2.0
Preface
Warning: This symbol indicates that dangerous voltage levels are present
within the equipment. These voltages are not insulated and may be of
sufficient strength to cause serious bodily injury when touched. The symbol
may also appear on schematics.
xv
Release 6.2.0
Telephone Support
If you need assistance while working with the BSR 64000, contact the Motorola
Technical Response Center (TRC):
U.S.
1-888-944-HELP (1-888-944-4357)
International
+215-323-0044
BSR hostname
BSR error messages and logs
Output of BSR show tech command
Cable modem information
List of troubleshooting steps you have performed before calling the TRC.
xvi
Output of BSR show version command, with part numbers and serial numbers of
BSR components
Shipping information for the replacement, including contact name, company
name, address, phone number, and email address
Release 6.2.0
Preface
Online Support
Motorola BSR Customer Website
The BSR customer website, http://bsr.motorola.com, is available for BSR customers
with active service contracts to access the latest product information, software
updates, troubleshooting information, and technical publications for the BSR 64000,
BSR 2000, and BSR 1000 product line.
You may request access to the site by emailing the BSR product support team at
bsrsupportonline@motorola.com with the following information:
n
Company name
The BSR product support team will email an invitation to you with further
instructions on how to set up an account on the BSR customer information website.
xvii
1
Basic System Configuration
Introduction
This chapter discusses the configuration required for basic operation of the BSR. The
following configuration tasks are described:
n
System Software
System Configuration
1-1
Release 6.2.0
Prerequisites
Before you begin the initial configuration of the BSR, you should determine the
following information:
n
Required Servers
The following servers are required for the basic operation of the BSR on your
network, and must be configured to allow cable modems to range and register
properly on the HFC network:
n
DHCP
TFTP
IP address
Router address
The following servers can be also configured to operate on the BSR for management,
provisioning, troubleshooting and billing purposes:
1-2
LDAP
Provisioning Server
DNS
Release 6.2.0
For information on installing these servers, refer to the specific vendors server
software documentation.
3. The terminal session begins and the password prompt displays. The password is a
null value by default. Press the Enter key. The MOT> prompt displays.
4. To enter Privileged EXEC mode, use the enable command in User EXEC mode,
as shown below:
MOT>enable
The Password prompt displays.
5. To enter Privileged EXEC mode, press the Enter key at the password prompt. The
password is a null value by default.
6. Use the configure command to enter Global Configuration mode in order to set
system passwords, as shown below:
MOT:7A#configure
The MOT:7A(config)# prompt displays.
1-3
Release 6.2.0
Note: Access to a telnet session is denied if the password for both the
console and telnet is not set.
Note: If you do not want to encrypt passwords on the BSR, do not use the
service password-encryption command.
MOT:7A(config)#service password-encryption
If you want to turn off the service password encryption feature so that passwords
entered in the future are no longer encrypted, use the no service
password-encryption command, in Global Configuration mode, as shown
below:
MOT:7A(config)#no service password-encryption
Note: The no service password-encryption command does not unencrypt
passwords that are already encrypted. If you want to unencrypt encrypted
passwords, you must change them manually.
1-4
Release 6.2.0
2. To set the password for a console (terminal) session that allows access to the BSR
in User EXEC mode, use the password console command in Global
Configuration mode, as shown below:
MOT:7A(config)#password console <WORD>
where:
WORD is the user-defined password that is no more than 31 characters.
3. To set the password for a telnet session that allows access to the BSR in User
EXEC mode, use the password telnet command in Global Configuration mode,
as shown below:
MOT:7A(config)#password telnet <WORD>
where:
WORD is the user-defined password for the BSR that is no more than 31
characters.
4. To set the Privileged EXEC password, use the enable password command, as
shown below:
MOT:7A(config)#enable password <WORD>
where:
WORD is the user-defined password for the BSR that is no more than 31
characters.
5. The show running-config command displays configuration information
currently running on the BSR. You have the option of displaying the entire
running configuration or displaying specific configuration information. Use the
show running-config command to verify that the changes you made were
implemented, as shown below:
Note: The show running-config command output identifies the system
password with the number 0 if it is unencrypted. If the system password is
encrypted, it is identified with the number 7.
MOT:7A#show running-config [interface [cable <X/Y> | ethernet <X/Y> |
gigaether <X/Y> | | pos <X/Y> | loopback <1-32> | tunnel <0-255>]] [ | {begin |
exclude | include} {<WORD>}]
1-5
Release 6.2.0
where:
interface displays running configuration information on all interfaces or a
specific interface.
cable X/Y is the slot and MAC Domain number of the CMTS module
ethernet X/Y is the Ethernet/Fast Ethernet IEEE 802.3 module slot and
interface number on the BSR.
gigaether X/Y is the Gigabit Ethernet module slot and interface number on
the BSR.
loopback 1-32 is the loopback interface number.
pos X/Y is the Packet over SONET slot and port number on the BSR.
tunnel 0-255 is the tunnel interface number.
| turns on output modifiers (filters).
begin filters for output that begins with the specified string.
exclude filters for output that excludes the specified string.
include filters for output that includes the specified string.
WORD is the specified string.
The configuration parameters that you have set should appear in the show
running-config command output.
1-6
Release 6.2.0
Parameter
Description
username
nopassword
1-7
Release 6.2.0
Parameter
Description
password
privilege
user-group
1-8
Release 6.2.0
1-9
Release 6.2.0
rw defines a privilege level of read-write that allows this user access to any
command mode
For example:
MOT:7A(config)#username newuser privilege rw
sysadmin
ISP
MSO
For example:
MOT:7A(config)#username newuser user-group mso
1-10
Release 6.2.0
In the following example, user account passwords have not been encrypted:
Note: The show running-config command output identifies the user
account password with the number 0 if it is unencrypted. If the user account
password is encrypted, it is identified with the number 7.
no service password-encryption
!
username root user-group sysadmin
username root password 0 root
username manuf user-group sysadmin
username manuf password 0 river
username diag user-group sysadmin
username diag password 0 delta
username ispuser user-group isp 1
username ispuser privilege rw
username ispuser password 0 ispuser
username msouser user-group mso
username msouser privilege rw
username msouser password 0 msouser
1-11
Release 6.2.0
2. The default timeout value for a console session is five minutes. Use the
session-timeout console command in Global Configuration mode to configure
the amount of time (retroactively) that console sessions can stay connected to the
BSR, as shown below:
MOT:7A(config)#session-timeout console <0-30>
where:
0-30 is the console session limit in minutes.
3. The default number of concurrent telnet sessions are 64. Use the telnet
session-limit command in Global Configuration mode to specify a limit on the
number of concurrent telnet sessions allowed to the BSR, as shown below:
Note: Setting the session-limit to "0" disallows any telnet sessions from being
accepted. Setting a session-limit value does not affect any currently open
telnet sessions.
MOT:7A(config)#telnet session-limit <0-64>
where:
0-64 is the telnet session limit.
1-12
Release 6.2.0
1-13
Release 6.2.0
3. Use the show clock command in Privileged EXEC mode to check the BSR clock
settings that you set.
hh:mm:ss is the hour, minute, and second in hh:mm:ss format.
1-31 is the day of the month from 1 to 31.
MONTH is the first three letters of the month.
1993-2035 is any year between 1993 and 2035.
The following examples show how to manually set the clock to 4:30 a.m. on May
1, 2003:
MOT:7A#clock set 04:30:00 1 May 2003
- or MOT:7A#clock set 04:30:00 May 1 2003
Use the broadcast command to broadcast a message to all connected users at any
given moment, as shown in Privileged EXEC mode, as shown below:
MOT:7A#broadcast <WORD>
where:
WORD is the message intended for broadcast.
Use the banner motd command in Global Configuration mode to specify the
message-of-the-day (MOTD) that is displayed for all connected users before they
successfully login to the BSR, as shown below. The MOTD is not configured by
default.
MOT:7A(config)#banner motd [<WORD> | <1-10>]
where:
1-10 is the MOTD line number from 1 to 10. Up to 10 MOTD lines can be
configured.
WORD is the MOTD text.
1-14
Release 6.2.0
Example
The following example configures a MOTD. The pound sign (#) is the delimiting
character.
MOT:7A(config)#banner motd The router will be rebooted at 12 a.m.
Use the no motd command to delete the MOTD banner.
System Software
This section discusses the following system software tasks:
n
Downloading Software
Downloading Software
The following sections show different methods for downloading software on the
BSR 64000:
n
1-15
Release 6.2.0
MOT:7A#delete nvram:<file>
where:
file is an application or boot image file.
For example:
MOT:7A#delete nvram:image_file.Z
3. Press the Enter key when asked for confirmation.
For example:
MOT:7A#delete nvram:image_file.Z ? [confirm]
4. In order to download files to the BSR 64000, you must properly configure your
FTP or TFTP server and verify that your local FTP or TFTP server is running and
configured properly by doing the following:
a. Check for the correct file names and ensure that these files are located in the
proper directory on the FTP or TFTP server.
b. Ensure that the proper IP address is configured for your TFTP or FTP
server.
5. Use the ping command in Privileged EXEC mode to verify the connectivity
status of your TFTP or FTP server, as shown below.
MOT:7A#ping [<A.B.C.D> | <Hostname>]
where
A.B.C.D is the IP address of the FTP or TFTP server.
Hostname is the DNS hostname of the FTP or TFTP server.
6. Ensure that the correct FTP username is configured on the BSR 64000 for
communication with the FTP server. If the required FTP user name is not
displayed in the running configuration or is incorrect, use the ip ftp username
command in Global Configuration mode as shown below:
Note: If you have a TFTP server, you do not need to set a user name or
password on the BSR.
1-16
Release 6.2.0
1-17
Release 6.2.0
3. Enter the full path from the FTP root directory and the new application or boot
image file name after the Source file name prompt and press the Enter key.
Source file name [ ]?
For example:
Source file name [ ]? /pub/image_file.Z
4. The Destination file name prompt displays with the new file name. Press the
Enter key to accept the new file name in NVRAM. For example:
Destination file name [ image_file.Z ]?
5. Compare each image file size (in bytes) in NVRAM on the SRM to the original
size of each image file size on the server. To view the new image files in
NVRAM on the SRM, use the dir command in Privileged EXEC mode as shown
below:
MOT:7A#dir
The following command output displays:
6. If the image file byte counts in NVRAM on the SRM match the image file byte
counts on the server, the image files on the SRM have been copied successfully.
1-18
Release 6.2.0
Follow these steps to download an image file to flash memory on the SRM:
Note: The following steps describe the process of transferring the new image
files from an FTP server to the SRM. If you are using FTP to transfer the
image files, ensure that the FTP username and password are set correctly on
the BSR 64000 using the ip ftp username and ip ftp password commands.
If you are using TFTP to transfer the image files, a username and password
are not necessary and the copy tftp: nvram: command can be substituted
for the copy ftp: nvram: command.
1. To download an image file to flash memory, use the copy ftp: flash: command in
Privileged EXEC mode and press the Enter key, as shown below:
MOT:7A#copy ftp: flash:
2. Enter the IP address or DNS name of the remote FTP or TFTP server at the
Address or name of remote host prompt and press the Enter key.
For example:
Address or name of remote host[]? 10.10.10.1
3. Enter the full path from the FTP root directory and the new application or boot
image file name after the Source file name prompt and press the Enter key.
Source file name [ ]?
For example:
Source file name [ ]? /pub/image_file.Z
4. The Destination file name prompt displays with the new file name. Press the
Enter key to accept the new file name in flash memory.
For example:
Destination file name [ image_file.Z ]?
1-19
Release 6.2.0
5. Compare each image file size (in bytes) in flash memory on the SRM to the
original size of each image file size on the server. To view the new image files in
flash memory on the SRM, use the dir flash: command in Privileged EXEC
mode as shown below:
MOT:7A#dir flash:
If the image file byte counts in flash memory on the SRM match the image file
byte counts on the server, the image files on the SRM have been copied
successfully.
1-20
Release 6.2.0
Note: Using the update chassis command may result in an audible loss of
voice-over-IP data for up to 20 seconds
1-21
Release 6.2.0
1-22
Release 6.2.0
System Configuration
This section discusses the following system configuration tasks:
n
1-23
Release 6.2.0
1-24
Release 6.2.0
string is the SRM asset ID number. Enclose the alias name within quotation
marks if the string contains spaces.
To configure your organizations asset ID number that is assigned to your BSR
64000, use the chassis assetid command in Privileged EXEC mode, as shown below:
MOT:7A#chassis assetid <string>
where:
string is the BSR 64000 chassis asset ID number. Enclose the alias name within
quotation marks if the string contains spaces.
1-25
Release 6.2.0
1-26
Release 6.2.0
Use the show system command in all modes except User EXEC to display
various operating information for the BSR 64000 such as the module temperature
and status, and the number of each class of alarms, as shown below:
MOT:7A#show system [ | {begin | exclude | include} {<WORD>}]
where:
| turns on output modifiers (filters).
begin filters output that begins with the specified string.
exclude filters output that excludes the specified string.
include filters output that includes the specified string.
WORD is the specified string.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show system command.
n
Use the show system alarms command in all modes except User EXEC to
provide a summary of central office alarm information for the entire BSR 64000.
The alarm summary display can be filtered according to whether the alarm is
active, critical, major, or minor, as shown below:
MOT:7A#show system alarms [active | critical | major | minor] [ | {begin |
exclude | include} {<WORD>}]
where
1-27
Release 6.2.0
Use the show system fans command to the current state of the fan tray
subsystem. It is used for troubleshooting and operational verification.
MOT:7A#show system fans [ | {begin | exclude | include} {<WORD>}]
where
| turns on output modifiers (filters).
begin filters output that begins with the specified string.
exclude filters output that excludes the specified string.
include filters output that includes the specified string.
WORD is the specified string.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show system fans command.
1-28
Release 6.2.0
To display information about all active processes on the BSR, use the show
process command, as shown below:
MOT:7A#show process
Use the show process msg-q-info command to display information about current
message queues, as shown below:
MOT:7A#show process msg-q-info
Use the show process stack command to display the size, current usage, and
highest usage of each process stack, as shown below:
MOT:7A#show process stack [procID | procName]
where:
procID is the task ID number in decimal or hexidecimal form. 0x is required
for hexidecimal form.
procName is the task name.
Use the show process memory command to display information about memory
usage, as shown below:
MOT#show process memory {process-id | process-name | slot <NUM> |
sorted} [bytes | kilobytes | megabytes ]
where:
process-id is the Process ID in hexidecimal notation.
process-name is the alphanumeric process name (up to 15 characters).
slot NUM specifies a CMTS slot number.
sorted specifies the memory information for all processes that are sorted.
bytes optionally displays the total sizes in bytes; which is the default.
kilobytes optionally displays the total sizes in kilobytes.
megabytes optionally displays the total sizes in megabytes.
1-29
Release 6.2.0
Use the show process cpu command to display information about CPU
utilization by each process, which includes detailed CPU usage statistics for
active SRM and CMTS modules in the BSR 64000 chassis.
Note: CPU usage statistics for a standby NIM or standby SRM modules are
not displayed using this command, however for NIM (HSIM) modules, the
module sub type is displayed.
For example:
Slot: 13 Module Type: HSIM Module Sub Type: 8-port 10/100
Ethernet (ETH8)
MOT:7A#show process cpu
Note: The total utilization is approximate and may not total 100 per cent.
Use the show process cpu slot command to display information about CMTS
CPU utilization by each process, as shown below:
MOT:7A#show process cpu slot <NUM>
where:
NUM is the CMTS module slot number.
n
Use the show process cpu restart command to restart the CPU utilization
measurement process, as shown below:
MOT:7A#show process cpu restart
Use the show process cpu frequency command to determine how many times
per second that a CPU statistic measurement is taken, as shown below:
MOT:7A#show process cpu frequency <30-200>
where:
30-200 is the frequency value in Hertz.
1-30
Release 6.2.0
Use the show process cpu stop command in Privileged EXEC Mode to stop the
utilization measurement process, as shown below:
MOT:7A#show process cpu stop
Use the show process semaphores command in Privileged EXEC mode display
information about the Semaphore ID number on which process is waiting, as
shown below:
MOT:7A#show process semaphores
Refer to the BSR 64000 Command Reference Guide to see typical screen output for
the show process commands.
Use the show memory command in Privileged EXEC mode to display the
starting address where memory is dumped in hexadecimal notation, as shown
below:
MOT:7A#show memory <address> <1-4294967295>
where:
address is the starting memory address expressed in hexadecimal notation to
dump memory.
1-4294967295 is the number of bytes to dump.
Use the show memory fastpath [brief] command in Privileged EXEC mode to
display the number of bytes used to program the NIM FastPath, as shown below:
MOT:7A#show memory fastpath [brief]
where:
1-31
Release 6.2.0
Use the show version command in all modes except User EXEC mode to display
complete version information for the BSR, as shown below:
MOT:7A#show version
Use the show version command in all modes except User EXEC mode to display
specific BSR system software and hardware version information, as shown
below:
MOT:7A#show version [slot <0-15>] [ | {begin | exclude | include}
{<WORD>}]
where:
slot is the module slot in the BSR 64000 chassis.
0-15 is the module slot number from which version information is to be
displayed.
| turns on output modifiers (filters).
begin filters for output that begins with the specified string.
exclude filters for output that excludes the specified string.
include filters for output that includes the specified string.
WORD is the specified string.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show version command.
1-32
Release 6.2.0
Use the show pool command in Privileged EXEC mode to display information
about how the BSR is buffering data, as shown below:
MOT:7A#show pool [<WORD>]
where:
WORD is the name of the buffer pool.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show pool command.
n
Use the show pool all command to view all memory buffer pools, as shown
below:
MOT:7A#show pool all
Use the show pool application command to view all application-specific pools,
as shown below:
MOT:7A#show pool application
Use the show pool icp command to view chassis control messages in the ICP
pool, as shown below:
MOT:7A#show pool icp
Use the show pool network command to view the network pool, where network
data transfer information for the stack is located, as shown below:
MOT:7A#show pool network
Use the show pool system command to view system physical structures, such as
the number of sockets, routes, interface addresses, PCB, and multicast addresses
in the system pool, as shown below:
MOT:7A#show pool system
Use the show pool names command to view display names of all the mBuf pools,
as shown below:
MOT:7A#show pool names
1-33
Release 6.2.0
Use the show controllers cable command to display the following CMTS
module information:
MOT:7A#show controllers cable <X/Y> [upstream <NUM> | downstream
<port> | mac | <cr>]
where:
X/Y is the slot and MAC Domain number of the CMTS module.
upstream <NUM> displays information for an upstream port including the
upstream modulation type, channel width, frequency, and modulation profile
information (i.e minislots, interleave, preamble, etc).
downstream <port> displays information for a downstream port including
downstream modulation type, frequency (label), and symbol rate.
mac displays MAC layer information about the cable interface.
cr a command return displays RF signal information, the type of hardware
installed, FEC information for both corrected and uncorrected packets, the
spectrum group and the status of the cable interface.
Use the show controllers ethernet command to display the following fast
Ethernet module information:
MOT:7A#show controllers ethernet <X/Y>
where:
X is the fast Ethernet module slot number.
Y is the Ethernet port number.
Use the show controllers gigaether command to display the following Gigabit
Ethernet module information:
MOT:7A#show controllers gigaether <X/Y>
where:
X is the Gigabit Ethernet module slot number.
Y is the Gigabit Ethernet port number.
1-34
2
Configuring Logging
Introduction
Logging provides a means of monitoring a device or network to determine the overall
health of the system and gather data for proactive management through trend
analysis.The BSR generates log messages when there are configuration changes or
when network or device events occur. The BSR logging can be configured to save
these log messages to a file or direct log messages to a system console, memory
buffer, or other devices. BSR logging:
n
You can also log this information to multiple destinations such as several SYSLOG
servers. By default, the BSR logs normal but significant log messages to its internal
buffer and then sends these messages to the system console. You can specify which
system messages should be logged based on the severity level of the message.
Messages are time-stamped to provide real-time debugging and management.
2-1
Release 6.2.0
Logging control allows you to specify which type of log messages are logged to
which destinations - either through the CLI or automatically through the DOCSIS
docsDevEvControlTable (refer to Setting Logging Control on page 2-3).
Restricting logging rates allows you to control the amount of logging traffic to
eliminate any potential congestion on the network (refer to Restricting Logging
Rates on page 2-4).
EVT logging provides the ability to monitor internal system to allow additional
informational granularity for diagnostics and troubleshooting (refer to
Configuring EVT Logging on page 2-12).
Configure the BSR to log only errors by issuing the logging buffered errors
command.
The logging buffered errors command limits the number of log messages going
into flash memory. It does not affect syslog operation.
2-2
Make sure NVRAM file system is only 50-60% full before copying files to the
Flash memory file system
Do not run telnet and other commands in conjunction with commands which
perform operations involving the NRVAM.
Delete the large files from the NVRAM file system during the maintenance
window.
Release 6.2.0
Configuring Logging
Any configurations set with the logging <destination> <severity> command are
overridden by the logging control docsis command. The no logging control docsis
disables the docsDevEvControlTable and re-establishes CLI logging control. Any
configurations previously set with the logging <destination> <severity> command
will now control which severity logs go to which destinations.
An entry for "logging control docsis" or "no logging control docsis" is always shown
in the running-configuration file. The default is "no logging control docsis".
Table CLI Logging Default Destination/Severity Levels
Destination
console
error or higher
notification or higher
trap
disabled
SYSLOG
disabled
Destination
console
disabled
2-3
Release 6.2.0
notice or higher
trap
SYSLOG
Note: Rate limiting applies to all log messages and can not be restricted for a
particular type of log message.
To restrict the rate of log messages, specify the number of logged messages allowed
per number of seconds with the logging rate-limit command in Global configuration
mode, as shown below:
MOT:7A(config)#logging rate-limit <0-2147483647> <1-2147483647>
where:
0-2147483647 is the number of messages.
1-2147483647 is the number of seconds at which the specified number of
SYSLOG and trap messages are logged.
The following example indicates that the rate-limit on logged messages is 10
messages per second:
MOT:7A(config)#logging rate-limit 10 1s
The logging admin-status command controls the rate of log messages with respect to
the threshold, if any, specified with the logging rate-limit command. Use the logging
admin-status command as follows:
MOT:7A(config)#logging admin-status {inhibited | maintainBelowThreshold |
stopAtThres | unconstrained}
2-4
Release 6.2.0
Configuring Logging
where:
inhibited causes all trap transmission and SYSLOG messages to be suppressed if a threshold has been specified with the logging rate-limit command, a warning
message will be displayed
maintainBelowThreshold causes trap transmission and SYSLOG messages to
be suppressed if the number of traps/messages would exceed the threshold
specified with the logging rate-limit command
stopAtThres causes trap transmission SYSLOG messages to cease at the
threshold specified with the logging rate-limit command - transmission will not
resume until the logging admin-status command is reset to an option other than
"stopAtThres" or the threshold is set to a higher value with the logging rate-limit
command.
unconstrained causes all traps and SYSLOG messages to be transmitted - if a
threshold has been specified with the logging rate-limit command, a warning
message will be displayed.
Note: If using the logging admin-status commands
"maintainBelowThreshold" or "stopAtThres" options, a rate limit must be
specified with the logging rate-limit command.
2-5
Release 6.2.0
where:
1-32 is the loopback interface number.
where:
A.B.C.D is the IP address of the SYSLOG server
For example:
MOT:7A(config)#logging 10.10.10.53
2. Specify the logging facility with the logging facility command in Global
Configuration mode, as shown below:
MOT:7A(config)#logging facility {local0 | local1 | local2 | local3 | local4 |
local5 | local6 | local7}
If you do not identify the logging facility using this command, the system defaults
to local7.
2-6
Release 6.2.0
Configuring Logging
3. Specify the severity level of messages to be logged to the SYSLOG server with
the logging trap command in Global Configuration mode, as shown below:
MOT:7A(config)#logging trap {alerts | critical | emergencies | errors |
informational | notifications | warnings}
Specify the severity level of messages to be logged to the SYSLOG server with
the logging snmp-trap command, in Global Configuration mode, as shown
below:
MOT:7A(config)#logging snmp-trap [alerts | critical | emergencies | errors
| informational | notifications | warnings]
where:
alerts logs conditions where immediate action is needed
critical logs critical conditions
emergencies logs emergency conditions where the system is unusable
errors logs error conditions
informational logs informational system messages
notifications logs normal but significant conditions
warnings logs warning conditions
Note: The logging trap and logging snmp-trap commands limit the logging
messages sent to a SYSLOG server to messages with a level up to and
including the severity level specified with these commands.
The following example configure the SYSLOG server to log all messages from
warnings (severity level 4) up to emergencies (severity level 0):
MOT:7A(config)#logging trap warnings
MOT:7A(config)#logging snmp-trap warnings
5. Verify that the SYSLOG server parameters are configured correctly with the
show running-config command in all modes except User EXEC, as shown
below:
2-7
Release 6.2.0
where:
alerts logs conditions where immediate action is needed
critical logs critical conditions
emergencies logs emergency conditions where the system is unusable
errors logs error conditions
informational logs informational system messages
notifications logs normal but significant conditions
warnings logs warning conditions
For example:
MOT:7A(config)#logging console notifications
2-8
Release 6.2.0
Configuring Logging
where:
4096-5242880 is the logging buffer size expressed in bytes.
2. Specify what logged information is buffered with the logging buffered
command, in Global Configuration mode, as shown below:
MOT:7A(config)#logging buffered {alerts | critical | emergencies | errors |
4. Use the show log command to see messages logged in the internal buffer. The
oldest message is displayed first.
2-9
Release 6.2.0
2. Verify that the log has been cleared with the show log command, as shown
below:
MOT:7A#show log
2-10
Release 6.2.0
Configuring Logging
local-syslog log all messages to local NVRAM and the SYSLOG server.
local-trap log messages, excluding the specified trap level, to local
NVRAM.
local-trap-syslog log messages, excluding the specified trap level, to local
NVRAM and the SYSLOG server.
For example, if you want to log critical log messages to local non-volatile
memory (NVRAM), use the logging reporting critical local command, as
shown below:
MOT:7A(config)#logging reporting critical local
Note: Debug messages will not be reported unless debugging has been
turned on for a subsystem with the corresponding CLI debug command (e.g.
debug snmp).
2-11
Release 6.2.0
2-12
Release 6.2.0
Configuring Logging
This section describes how to configure EVT logging parameters. The tasks for
configuring EVT logging include the following:
n
Console logging
Each EVT is also defined with one of eight severity levels (debug, informational,
notice, warning, error, critical, alert, or emergency). The severity level of an EVT
determines the destination where the EVT message will be logged based on the
default destination/severity configuration.
The default destination/severity configuration depends on which logging control
mode is enabled. Refer to Table Table for the default destination/severity levels
associated with CLI logging control. Refer to Table Table for the default destination/
severity levels associated with DOCSIS logging control.
2-13
Release 6.2.0
where:
l indicates Local logging to a local logging buffer.
t indicates Traps sent to an SNMP server
s indicates Syslog messages sent to a SYSLOG server
c indicates Console logging
one of the fifteen possible combinations of l, t, s, and c, appearing in
that order, determine which of the four logging flag bits are set.
slot is an optional slot number. If omitted, the command applies to the EVTs
that occur on all slots in the system.
group is an optional name of an EVT group.
range is an optional individual EVT number within an EVT group. If a single
EVT number or EVT number + EVT number is specified, only those
particular EVTs are affected by the command.
2. Verify the EVT configuration with the show running-config command in all
modes except User EXEC, as shown below:
MOT:7A(config)#show running-config | inc logg
sets console logging of all events for the EVT group BUFMGR on all slots.
n
sets console logging of all events for the EVT group BUFMGR only on slot 6.
n
sets local logging and console logging of the EVT BUFMGR.3 events on all
slots.
n
2-14
Release 6.2.0
Configuring Logging
sets SYSLOG and console logging of all events for the EVT group BUFMGR
events on all slots.
n
sets local logging, SNMP trap, SYSLOG, and console logging for slot 6 EVT
BUFMGR.3 and BUFMGR.4 events.
n
removes all previous logging evt set and logging evt clear configurations.
This command displays the recording mechanism for logging messages based on
their severity level. The display output is in the format: logging reporting
<severity> <logging location> e.g. logging reporting alert local.
2-15
Release 6.2.0
This command disables EVT logging for the specific logging destination(s). For
example, it may be useful to turn off console logging for a warning severity
message which is originally sent to the local console.
n
This command disables logging of all EVTs and can be used to stop a flood of
EVT log messages from going to the console.
This command sequence removes the corresponding logging evt clear entry
from the running configuration file and restores the default logging control for the
EVT group.
n
This command, with no other arguments, removes all logging evt clear entries
from the running configuration file and restores default logging controls for all
EVTs modified with the logging evt set command.
2-16
Release 6.2.0
Configuring Logging
The logging default command restores the default settings for all logging, including
logging <destination> <severity>, logging reporting, and EVT configurations.
n
All logging evt configuration entries are removed from the running configuration
file.
2-17
3
Configuring TCP/IP
Introduction
IP provides basic packet delivery service for all TCP/IP networks. The
connection-oriented TCP exchanges control information with a remote device to
verify that the device is ready to receive data before it is sent. However, IP uses other
protocols to establish the connection and to supply error detection and recovery such
as ICMP.
A datagram is a packet format defined by IP. An IP packet contains the necessary
destination address information. A packet-switching network uses the addressing
information to switch the packet from one physical network to another, moving it
toward its final destination. Each packet travels the network independent of any other
packet.
IP performs the following functions:
n
Moves data between the Network Access layer and the Host-to-Host Transport
layer
3-1
Release 6.2.0
A router forwards traffic from one network to another. The router also transmits route
information to other routers. This route information is stored in routing tables that
enable a router without a direct physical connection to a packets destination to
forward the packet to a router that is closer to its destination. The process continues at
each router until the packet reaches a router attached to the same network as the
destination host. That router delivers the packet to the specified host on its local
network, and the packet reaches its final destination.
3-2
Release 6.2.0
Configuring TCP/IP
X/Y is the slot and MAC Domain number of the CMTS module.
2. The default ARP timeout is 60 minutes. Use the arp timeout command in
Interface Configuration mode to set the ARP cache timeout for a specific
interface, as shown below:
MOT:7A(config-if)#arp timeout <1-6000>
where:
1-6000 is ARP cache timeout value, expressed in minutes.
Use the no arp timeout command to restore the default.
Reverse ARP
Reverse ARP, defined in RFC 903, works like ARP, except that the RARP request
packet requests an Internet address instead of a hardware address. The BSR acts as an
RARP server. Use the ip rarp-server command in Interface Configuration mode to
enable RARP, as shown below. Set the IP address to one of the interface addresses.
MOT:7A(config-if)#ip rarp-server <A.B.C.D>
where:
A.B.C.D is the source protocol IP address in replies.
3-3
Release 6.2.0
Use a single broadcast address scheme on a network and set the address to be used as
the broadcast address to avoid broadcast storms. The BSR can accept and interpret all
possible forms of broadcast addresses.
Use the ip broadcast-address command in Interface Configuration mode to specify a
broadcast IP address for an interface, as shown below:
MOT:7Aconfig-if)#ip broadcast-address <A.B.C.D>
where:
A.B.C.D is the broadcast IP address.
3-4
Release 6.2.0
Configuring TCP/IP
where:
68-4000 is the MTU size, expressed in bytes for an 10/100 Ethernet interface.
Note: The POS interface MTU range is from 68 to 4000 bytes. The loopback
interface MTU range is from 68 to 1514 bytes.
The MTU cannot be set on a CMTS interface.
3-5
Release 6.2.0
3-6
Release 6.2.0
Configuring TCP/IP
Use the no ip route command to remove a static route from the routing table.
Table Table lists the dynamic routing protocols and their default distances.
Table Route Sources and Administrative Distances
Route Source
Default Distance
170
External BGP
20
IGRP
100
170
Internal BGP
200
90
OSPF
110
RIP
120
Static route
Unknown
255
where:
* is the asterisk character that clears all routes in the routing table.
A.B.C.D is the IP address of the route.
A.B.C.D is the subnet mask of the IP address.
3-7
Release 6.2.0
About IRDP
Enabling IRDP
Enabling ICMP
About IRDP
The router software provides router discovery, by which the router can dynamically
learn about routes to other networks using the ICMP Router Discovery Protocol
(IRDP) for detecting routers. IRDP uses router advertisement and router solicitation
messages to discover addresses of routers on directly attached subnets.
With IRDP, each router periodically multicasts or broadcasts router advertisement
messages from each of its interfaces. Hosts discover the addresses of routers on the
directly attached subnet by listening for these messages. Hosts can use router
solicitation messages to request immediate advertisements, rather than wait for
unsolicited messages.
IRDP offers several advantages over other methods of discovering addresses of
neighboring routers. Primarily, it does not require hosts to recognize routing
protocols, nor does it require manual configuration by an administrator.
Router advertisement messages allow hosts to discover the existence of neighboring
routers, but not which router is best to reach a particular destination. If a host uses a
poor first-hop router to reach a particular destination, it receives a redirect message
identifying a better choice.
3-8
Release 6.2.0
Configuring TCP/IP
Enabling IRDP
Use the following procedure to configure IRDP.:
where:
address {<A.B.C.D>} is the IP address to proxy-advertise the preference
value message.
multicast indicates advertisements are sent with multicast.
preference indicates preference value for this interface.
-2147483648-2147483647 indicates preference value for this interface
(higher values are prefered); the default is 0.
3. The default peference level for IRDP routing is 0. Use the ip irdp preference
command in Interface Configuration mode to set the IRDP routing preference
level, as shown below:
MOT:7A(config-if)#ip irdp preference <-2147483648-2147483647>
where:
-2147483648-2147483647 is the IRDP routing preference level.
3-9
Release 6.2.0
Managing IRDP
Use any of the following options to change IRDP default settings:
n
The default duration for an IRDP advertisement is 1800 seconds. Use the ip irdp
holdtime command in Interface Configuration mode to change the duration of
IRDP advertisement ages, as shown below:
MOT:7A(config-if)#ip irdp holdtime {<1-9000>}
where:
1-9000 is the hold-time in seconds that advertisements are kept valid.
n
The default IRDP maximum advertising interval is 600 seconds. Use the ip irdp
maxadvertinterval command in Interface Configuration mode to change the
maximum time between IRDP advertisements, as shown below:
MOT:7A(config-if)#ip irdp maxadvertinterval {<4-1800>}
where:
4-1800 is the maximum time in seconds.
n
The default IRDP minimal advertisement interval is 450 seconds. Use the ip irdp
minadvertinterval command in Interface Configuration mode to change the
minimum time interval between IRDP advertisements, as shown below:
MOT:7A(config-if)#ip irdp minadvertinterval {<3-1800>}
where:
3-1800 is the minimal interval in seconds between IRDP advertisements.
n
3-10
Release 6.2.0
Configuring TCP/IP
Enabling ICMP
Once IRDP is enabled, follow the steps in this section to enable ICMP:
1. Use the ip mask-reply command in Interface Configuration mode to enable
ICMP netmask reply messages, as shown below:
MOT:7A(config-if)#ip mask-reply
3. You can send ICMP echo request packets to a specified address. You can set an
optional packet count for a destination. Use the ping command from Privileged
EXEC mode to do this, as shown below:
MOT:7A#ping [<hostname> | <A.B.C.D>] [size <40-65515>] [<1-65535>]
[timeout <1-1024>] [source <A.B.C.D>] [tos <0-255>] [ttl <0-255>] [df]
where:
hostname is the DNS host name.
A.B.C.D is an IP address.
40-65515 is the packet size value expressed in bytes.
1-65535 is the packet number or request messages sent.
timeout is the duration.
1-1024 is the timeout value, expressed in seconds.
source A.B.C.D is the IP address of the source.
tos 0-255 specifies the type of service.
ttl 0-255 is the time to live value.
df sets the dont fragment flag in the IP header.
In the following example, a request packet is sent to address 192.35.42.1, with a
size of 55, a packet count of 10, and a timeout value of 10 seconds.
MOT:7A#ping 192.35.42.1 size 55 10 timeout 10
3-11
Release 6.2.0
Tracing a Route
A route path includes all IP level devices, such as routers and servers, that packets
travel through over the network on a hop-by-hop bases to get to their intended
destination.
Use the traceroute command in Privileged EXEC mode to identify the route path
from the route source to the route destination, as shown below:
MOT:7A#traceroute [<A.B.C.D> | <Hostname>]
where:
A.B.C.D is the source IP address.
Hostname is the Domain Name Server (DNS) hostname.
Clearing IP Routes
Clearing IP Traffic
3-12
Release 6.2.0
Configuring TCP/IP
You can enable IP source-route header options if they have been disabled by using the
following command in Global Configuration mode:
MOT:7A(config)#ip source-route
where:
cable clears the cable interface counters. X/Y is the slot and MAC Domain
number of the CMTS module.
ethernet clears the Ethernet interface counters.
loopback clears the loopback interface counters.
1-32 is the loopback interface number.
tunnel clears the tunnel interface counters.
0-255 is the tunnel interface number.
pos clears the Packet over SONET (POS) interface counters.
gigaether clears the Gigabit Ethernet interface counters.
X identifies the module slot number.
Y identifies the port number.
3-13
Release 6.2.0
Clearing IP Routes
Use the clear ip route command in Privileged EXEC mode to clear one or more IP
routes from the IP routing table, as shown below:
MOT:7A#clear ip route {* | <A.B.C.D> | <A.B.C.D> <A.B.C.D>}
where:
* deletes all routes.
A.B.C.D the network or subnetwork address.
A.B.C.D the associated IP address of the removed routes.
where:
A.B.C.D is the IP address for ARP table entry to be cleared.
Clearing IP Traffic
Use the clear ip traffic command in Privileged EXEC mode to reset the IP traffic
statistics counters to zero, as shown below:
MOT:7A#clear ip traffic
where:
Hostname deletes a specific DNS host entry.
* deletes all DNS host entries.
3-14
Release 6.2.0
Configuring TCP/IP
Use the show ip arp command to display ARP table information, as shown
below:
MOT:7A#show ip arp [<A.B.C.D>] [<Hostname>] [<H.H.H>] [cable <X/Y> |
where:
brief displays summary information.
pos is the Packet over SONET interface.
ethernet is any 10 or 10/100 Ethernet interface.
gigaether is the Gigabit Ethernet interface.
X/Y is the slot and port number.
cable X/Y is the slot and MAC Domain number of the CMTS module.
loopback 1-32 is the loopback interface.
3-15
Release 6.2.0
Use the show ip route command to display the routing table status. You can
specify an optional IP mask that filters specific routes. You can enter this
command from any mode.
MOT:7A#show ip route [<hostname> | bgp | connected | ospf | rip | static |
<A.B.C.D> [mask]]
Use the show ip route static command to display the status of static routes in the
routing table. You can specify an optional IP mask that filters specific routes.
MOT:7A#show ip route static [<hostname> | bgp | connected | ospf | rip | static
| <A.B.C.D> [mask]]
n
Use the show ip traffic command from Privileged EXEC mode to display
statistics about IP traffic, which includes DHCP lease query statistics, as shown
below:
MOT:7A#show ip traffic
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show ip arp, show ip interface, and show ip route
commands.
3-16
4
Configuring Interfaces
Introduction
This chapter discusses the following interface configuraion tasks on the BSR:
n
4-1
Release 6.2.0
where:
pos is the Packet over SONET interface.
ethernet is any 10 or 10/100 Ethernet interface.
gigaether is the Gigabit Ethernet interfac.e
X is the module slot on the BSR.
Y is the port number on the module.
cable X/Y is the slot and MAC Domain number of the CMTS module.
5. Use the ip address command to set a primary IP address and subnetwork mask
for an interface, as shown below:
MOT:7A(config-if)#ip address {<A.B.C.D> <A.B.C.D>}
4-2
Release 6.2.0
Configuring Interfaces
where:
A.B.C.D is the IP address of the interface.
A.B.C.D is the network mask of the IP network, on which the interface is
associated.
For example:
MOT:7A(config-if)#ip address 10.10.10.135 255.255.255.0
where:
A.B.C.D is the IP address of the BSR interface designated for the loopback
interface.
A.B.C.D is the subnetwork mask of the IP network, on which the interface is
associated.
secondary optionally designates the IP address as a secondary IP
address. Include the keyword secondary after the IP address and subnet
mask to specify additional secondary IP addresses.
Note: If you are specifying a secondary IP address for a cable interface that
has a secondary CPE host or MTA IP address, refer to Subneting DHCP
Clients on the Cable Interface in the BSR 64000 CMTS Configuration and
Management Guide for more information.
For example:
In the sample below, 198.108.1.127 is the primary address and 172.45.7.17 is
a secondary address for Ethernet 0/0.
interface ethernet 0/0
4-3
Release 6.2.0
where:
LINE is the text that describes the interface.
For example:
MOT:7A(config-if)#description charlestown_1
8. Use the show ip interface command to verify the configuration and current state
of the interface that you configured, as shown below:
MOT:7A(config-if)#show ip interface [ brief | pos <X/Y> | ethernet<X/Y> |
gigaether <X/Y> | cable <X/Y>]
where:
brief displays summary information.
pos is the Packet over SONET interface.
ethernet is any 10 or 10/100 Ethernet interface.
gigaether is the Gigabit Ethernet interface.
X is the desired module slot on the BSR.
Y is the port number on the module.
cable X/Y is the slot and MAC Domain number of the CMTS module.
Refer to the BSR 64000 Command Reference Guide to see typical screen output
and field descriptions for the show ip interface command.
4-4
Release 6.2.0
Configuring Interfaces
Removing an IP Address
You can disable IP processing on a particular interface by removing its IP address
with the no ip address command. If the router detects another host using one of its IP
addresses, it will print an error message on the console. The software supports
multiple IP addresses per interface. A specific IP address can be removed from an
interface or all IP addresses associated with the interface can be removed.
n
Note: The primary IP address can be removed only after all of the secondary
subnet addresses associated with the inteface have been removed.
where:
X is the 10/100 Ethernet module slot.
4-5
Release 6.2.0
The Ethernet interface the duplex mode is auto-negotiated by default. Use the
duplex full command in Interface Configuration mode to manually set the duplex
mode for full-duplex so that the Ethernet interface can send and receive signals at
the same time, as shown below:
MOT:7A(config-if)#duplex full
- or Use the duplex half command in Interface Configuration mode to manually set
the duplex mode for half-duplex so that the Ethernet interface can either send or
receive signals, but cannot do both at the same time, as shown below:
MOT:7A(config-if)#duplex half
The Ethernet Interface default speed is auto-negotiated. Use the speed 100
command in Interface Configuration mode to manually set the Ethernet interface
speed to 10 Mbps or 100 Mbps, as shown below:
MOT:7A(config-if)#speed [10 | 100]
where:
4-6
Release 6.2.0
Configuring Interfaces
n
n
where:
1-32 is the number of the loopback interface.
2. Use the ip address command in Interface Configuration mode to define an IP
address for the loopback interface that is a network broadcast address, as shown
below:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the BSR interface designated for the loopback
interface.
4-7
Release 6.2.0
mta]
where:
A.B.C.D is the secondary IP address of the BSR interface.
A.B.C.D is the subnetwork mask of the IP network, on which the interface is
associated.
secondary optionally designates the IP address as a secondary IP
address. Include the keyword secondary after the IP address and subnet
mask to specify additional secondary IP addresses.
host makes this IP address a secondary host (CPE) address.
mta makes this IP address a secondary MTA address.
Note: The host or mta option used when assigning a secondary IP address
to a loopback interface have no effect unless this loopback interface is
configured as a virtual cable bundle master. Refer to Bundling Cable
Interfaces into a Single IP Subnet in the BSR 64000 CMTS Configuration and
Management Guide for more information.
4. Use the show interfaces loopback command in Interface configuration mode to
verify the loopback interface configuration, as shown below:
MOT:7A(config-if)#show interfaces loopback <1-32>
where:
1-32 is the number of the loopback interface.
4-8
Release 6.2.0
Configuring Interfaces
where:
1-32 is the loopback interface number.
Up to 255 tunnel interfaces can be configured on the BSR. A separate tunnel for each
link must be configured, since it is a point-to-point link. When configuring tunnels on
an interface, you must specify the tunnel source and tunnel destination.
Follow these steps to define a tunnel address:
1. Use the interface tunnel command in Global Interface mode, to define a tunnel
interface, as shown below:
4-9
Release 6.2.0
where:
255 is the number of the tunnel interface from 0 to 255
2. Use the ip address command in Interface Configuration mode to define an IP
address for the tunnel interface, as shown below:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the tunnel interface.
A.B.C.D is the subnetwork mask of the tunnel interface.
3. Use the ip address secondary command to optionally configure a secondary IP
address for the tunnel interface in Interface Configuration mode, as shown below:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D> secondary
where:
A.B.C.D is the IP address of the tunnel interface.
A.B.C.D is the subnetwork mask of the tunnel interface.
secondary optionally designates the IP address as a secondary IP address.
Include the keyword secondary after the IP address and subnet mask to
specify additional secondary IP addresses.
4. Use the tunnel source command in Interface Configuration mode to specify the
tunnel source, as shown below:
MOT:7A(config-if)#tunnel source [<A.B.C.D> | cable <X/Y> | default
4-10
Release 6.2.0
Configuring Interfaces
where:
A.B.C.D is the IP address of the tunnel interface destination.
Hostname is the DNS name of the destination.
6. Use the show interfaces tunnel command in Interface configuration mode to
verify your tunnel interface configuration, as shown below:
MOT:7A(config-if)#show interfaces tunnel <0-255>
where:
0-255 is the tunnel interface number.
7. Use the no tunnel source command in Interface Configuration mode to
delete a tunnel source, as shown below:
MOT:7A(config-if)#no tunnel source
4-11
Release 6.2.0
where:
X is the POS module slot number.
Y is the POS port number.
4. Use the ip unnumbered command in Interface Configuration mode to enable an
interface for data processing without an explicit IP address, as shown below:
MOT:7A(config-if)#ip unnumbered [loopback <1-32> | pos <X/Y> | serial
<X/Y> | ethernet <X/Y> | gigaether <X/Y>]
where:
loopback is the loopback interface on the POS module.
1-32 is the loopback interface.
pos is POS interface on the POS module.
serial is the Serial interface on the POS module.
ethernet is the loopback interface on the 10/100 Ethernet module or Ethernet
management interface or serial interfaces on the SRM.
gigaether is the loopback interface on the Gigabit Ethernet module.
X identifies the module slot number.
Y identifies the port number.
4-12
Release 6.2.0
Configuring Interfaces
where:
cable clears the cable interface counters. X/Y is the slot and MAC Domain
number of the CMTS module.
ethernet clears the Ethernet interface counters.
loopback clears the loopback interface counters.
1-32 is the loopback interface number.
tunnel clears the tunnel interface counters.
0-255 is the tunnel interface number.
pos clears the Packet over SONET (POS) interface counters.
gigaether clears the Gigabit Ethernet interface counters.
X is the module slot number.
Y is module the port number.
4-13
Release 6.2.0
4-14
5
Configuring Network Security
Introduction
This chapter describes configuring the following network security and authentication
features on the BSR:
n
Configuring RADIUS
Configuring TACACS+
Configuring RADIUS
Remote Authentication Dial In User Service (RADIUS) provides additional secure
remote network access through authentication, authorization and accounting services.
The BSR 64000 uses a RADIUS client to authenticate user login information
(passwords) stored on a remote RADIUS server.
The RADIUS client feature is disabled by default. Once the RADIUS client feature is
enabled and configured, a user enters a password in their telnet or console session to
access the BSR 64000. The BSR 64000 uses the RADIUS client to authenticate this
RADIUS encrypted password with a remote RADIUS server. If the RADIUS server
validates the password, the user gains access to the BSR 64000.
5-1
Release 6.2.0
<0-65535> primary
where:
A.B.C.D is the IP address of the remote RADIUS server.
Hostname is the Hostname of the remote RADIUS server.
0-65535 is the optionally defined UDP port for the RADIUS authentication
server. The default port is 1812.
primary specifies the server as the primary RADIUS server.
2. Use the radius-server host command, in Global Configuration mode, to specify
a secondary or back-up RADIUS server for RADIUS client requests, as shown
below:
MOT:7A(config)#radius-server host [<A.B.C.D> | <Hostname>] [auth-port
<0-65535> ]
where:
A.B.C.D is the IP address of the remote RADIUS server.
Hostname is the hostname of the remote RADIUS server.
0-65535 is the optionally defined UDP port for the RADIUS authentication
server. The default port is 1812.
3. Use the radius-server key command in Global Configuration mode to define the
shared encryption key that is exchanged between the RADIUS server and BSR
RADIUS client, as shown below:
Note: It is recommended that the authentication key text string be more than
22 characters in length.
5-2
Release 6.2.0
where:
WORD is the shared encryption key text.
Caution: Ensure that the RADIUS server authentication key on the BSR is
the same as the RADIUS server authentication key on your RADIUS server.
If the keys are mismatched, communication does not occur between the BSR
and RADIUS server.
Use the following options to change the default RADIUS server settings:
n
where:
0-100 is the number of retransmissions. The default is 3 retransmissions.
n
where:
1-1000 is the wait time interval in seconds. The default value is 5 seconds.
5-3
Release 6.2.0
where:
1-32 is the loopback interface number
Note: User password attributes in the RADIUS request sent from the
RADIUS client on the BSR to the RADIUS server are encrypted.
Use one or more of the following options to enable and configure the RADIUS Client
feature:
1. Use the telnet authentication radius command in Global Configuration mode to
enable RADIUS client authentication for telnet session access to the BSR, as
shown below:
MOT:7A(config)#telnet authentication radius [local-password]
5-4
Release 6.2.0
where:
local-password allows password authentication by a locally configured
password if there is no response from the RADIUS server. If the RADIUS
client is not configured with the local-password command argument, access
to the BSR is denied if there is no response from the RADIUS server.
2. If you are experiencing failed telnet login authentications, use the telnet
authentication radius fail-message command in Global Configuration mode to
display failed radius client logins and authentications, as shown below:
MOT:7A(config)#telnet authentication radius fail-message [<LINE>]
where:
LINE is the text message for the failed login and authentication. If a text
message is not specified, a default failed logging and authentication message
is used.
3. Use the console authentication radius username command in Global
Configuration mode to configure a username for RADIUS client authentication
for console session access to the BSR, as shown below:
MOT:7A(config)#console authentication radius username {<WORD>}
where:
WORD is the username to use for authentication.
4. Use the console authentication radius local-password command in Global
Configuration mode to enable RADIUS client authentication for console session
access to the BSR, as shown below. This command allows you to configure a user
name for RADIUS access, use of a locally set password or both.
MOT:7A(config)#console authentication radius local-password
where:
local-password allows password authentication by a locally configured
password if there is no response from the RADIUS server. If the RADIUS
client is not configured with the local-password command argument, access
to the BSR is denied if there is no response from the RADIUS server.
5-5
Release 6.2.0
where:
local-password allows password authentication by a locally configured
password if there is no response from the RADIUS server. If the RADIUS
client is not configured with the local-password command argument, access
to the BSR is denied when there is no response from the RADIUS server.
If a user does not enter a username, the BSR will not allow the user to enter a
password as the "password" prompt will never appear.
If a user does not enter a password, the blank password field is "padded" with
some random data so that the password field is never left blank. This will prevent
all RADIUS accounts that use a blank password from gaining authentication.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show ip traffic command.
5-6
Release 6.2.0
Enabling SSH
Enabling SSH
Follow these steps to enable SSH on the BSR:
1. Host keys are required for the SSH Server and can either be generated in the BSR
64000 or generated on another BSR 64000 and copied into the BSR. Use the
ssh-keygen2 tool in Privileged EXEC mode to generate authentication key files
for the BSR 64000 Secure Shell Server, as shown below:
Note: The SSH Server must be disabled on the BSR 64000 before running
the ssh-keygen2 tool.
5-7
Release 6.2.0
Caution: The BSR 64000 Secure Shell Server only accepts host key files
generated with the ssh-keygen2 tool. Keys files generated using the
OpenSSH ssh-keygen tool will not work with the BSR 64000 Secure Shell
Server.
The ssh-keygen2 tool resolves interoperability problems associated with
OpenSSH. A key file must be generated using the ssh-keygen2 tool for the
BSR 64000 Secure Shell Server to inter operate properly with OpenSSH
Secure Shell clients.
MOT:7A#ssh-keygen2 [bits <512-1024> | hostkeyfile {flash: <filename> |
nvram: <filename>} | type {dsa | rsa}]
where:
512-1024 specifies the key strength in bits.
flash: <filename> creates the private hostkey file name stored in Flash.
nvram: <filename> creates private hostkey file name stored in NVRAM.
type dsa Digital Signature Algorithm key type.
type rsa Rivest-Shamir-Adleman public-key algorithm key type
2. Use the configure command in Privileged EXEC mode to enter Global
Configuration mode.
3. Use the ssh enable command in Global Configuration mode to enable the SSH
process, as shown below:
Note: The no ssh enable command disables the SSH process. If SSH is
disabled, all existing SSH sessions will be terminated.
MOT:7A(config)#ssh enable
5-8
Release 6.2.0
where:
WORD set a password (31 character maximum) for SSH connections. The
"%" and "!" characters must not be used.
2. Use the password ssh-passphrase command, in Global Configuration mode, to
establish a password.
MOT:7A(config)# password ssh-passphrase [0 | 7] <WORD>
where:
0 specifies that a plain text password follows.
7 specifies that an encrypted password follows.
WORD is the password (31 character maximum, 78 character maximum for
option 7) - enclosed with double quotes if the key contains spaces) - the "%"
and "!" characters must not be used. If using option 7, the password must be
entered as an encrypted password.
3. Use the ssh enable command, in Global Configuration mode, to enable the SSH
session.
MOT:7A(config)# ssh enable
5-9
Release 6.2.0
Note: If the hostkey authentication files are invalid, SSH will not run. Use the
UNIX ssh-keygen2 tool to generate a new hostkey authentication file.
where:
flash: specifies flash memory as the location of the SSH hostkey
authentication file.
nvram: specifies Non-volatile Random Access Memory (NVRAM) as the
location of the hostkey authentication file.
filename is the filename of the hostkey authentication file stored in flash or
NVRAM.
n
Release 6.2.0
The default number of SSH sessions is 8. Use the ssh session-limit command, in
Global Configuration mode, to change the maximum number of simultaneous
SSH sessions that the BSR accepts, as shown below:
MOT:7A(config)#ssh session-limit <0-8>
where:
0-8 is the number of simultaneous SSH sessions.
5-11
Release 6.2.0
The default time-out for an SSH session is 5 minutes. Use the ssh timeout
command in Global Configuration mode to specify an inactivity timeout value for
SSH sessions, as shown below:
Note: Specifying a value of "0" will disable time-out for SSH sessions.
where:
0-60 is the timeout value in minutes.
n
The default TCP port for SSH connections is port 22. Use the ssh port command
in Global Configuration mode to change the SSH port number that SSH uses to
listen for incoming connections, as shown below:
MOT:7A(config)#ssh port <1-65535>
where:
1-65535 is the desired port number for SSH connections.
n
The default number of attempted guesses for trying an SSH password is 3. The
ssh password-guesses command in Global Configuration mode to specify how
many authentication attempts (login and password exchange) are permitted for an
SSH client attempting a connection.
MOT:7A(config)#ssh password-guesses <1-5>
where:
1-5 is the number of attempted guesses for trying a password.
5-12
Release 6.2.0
2. Use the ssh logout session-id command in Privileged EXEC mode to terminate
an SSH session in progress. This command can be used when a user wants to
reconnect using new configuration parameters.
MOT:7A#ssh logout session-id <0-7>
where:
0-7 is the session ID number.
3. Use the show users ssh command again to verify which SSH sessions are
active.
where:
local-password authenticates with a locally configured password if there is no
response from the RADIUS server.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show ssh config command.
Compass ID: 379437400 Version 2
5-13
Release 6.2.0
Configuring TACACS+
This section describes the Terminal Access Controller Access Control System Plus
(TACACS+), a Cisco Systems proprietary version of TACACS. TACACS+ is an
access-control protocol that allows the BSR to provide security through a centralized
server. TACACS+ consists of three services: authentication, authorization, and
accounting (AAA). AAA is a software mechanism that provides a framework to
configure authentication, authorization, and accounting in a consistent manner.
n
Authentication is a service that determines who the user is and whether they are
allowed access to the BSR.
Authorization is a service that determines what tasks the user is allowed to do on
the BSR.
Accounting is a service that collects data related to resource usage.
5-14
Enabling AAA
Release 6.2.0
where:
hostname is the name of the TACACS+ server host.
A.B.C.D is the IP address of the TACACS+ server host.
5-15
Release 6.2.0
where:
WORD specifies an alphanumeric authentication and encryption key. This key
must match the key used by the TACACS+ server.
5-16
Release 6.2.0
where:
0-65536 specifies the global port number used for all communication between
TACACS+ clients and TACACS+ servers. The default port number is 49. If a
TACACS+ server is listening on any other port other than port 49, the port
number can be specified using this command.
where:
0-100 specifies the number of connection attempts that TACACS+ client makes
with TACACS+ server for authentication, authorization or accounting. The
default value is 3.
where:
1-1000 the interval, in seconds, that the BSR waits for a TACACS+ server host to
reply.
5-17
Release 6.2.0
where:
X/Y is the Ethernet interface slot and port number.
Use the ip tacacs source-interface loopback command, in Global Configuration
mode, to configure an Ethernet interface, as follows
MOT:7A(config)#ip tacacs source-interface loopback <1-32>
where:
1-32 is the loopback interface number.
5-18
Release 6.2.0
Enabling AAA
AAA is a network security model that consists of a software framework that provides
methods for authentication, authorization and accounting on the BSR. Use the aaa
new-model command, in Global Configuration mode, to enable the AAA network
security model, as follows:
MOT:7A(config)#aaa new-model
tacacs}
where:
enable uses the enable password command setup as the authentication method.
local uses the local database as the authentication method.
none uses no method as the authentication method.
radius uses RADIUS as the authentication method.
tacacs uses TACACS+ as the authentication method.
5-19
Release 6.2.0
tacacs}
where:
enable uses the enable password command setup as the authentication method.
local uses the local database as the authentication method.
none uses no method as the authentication method.
radius uses RADIUS as the authentication method.
tacacs uses TACACS+ as the authentication method.
5-20
Release 6.2.0
where:
local uses the local database as the authorization method.
none uses no method as the authorization method.
Compass ID: 379437400 Version 2
5-21
Release 6.2.0
5-22
Release 6.2.0
5-23
Release 6.2.0
Use the show tacacs statistics command to display overall TACACS+ statistics
including the total number of access (AAA) requests, the number of denied requests,
and the number of allowed requests.
MOT:7A#show tacacs statistics
Note: TACACS+ statistics can also be displayed with the show ip traffic
command.
Refer to the BSR 64000 Command Reference Guide to see typical screen output for
the show tacacs, show tacacs statistics, and show ip traffic commands.
These are the same TACACS+ statistics displayed with the show tacacs and show
tacacs statistics commands.
5-24
6
Configuring Network Servers
Introduction
This chapter describes how to configure server-related parameters on the BSR in
order to establish proper communication between the BSR and the different types of
servers that are connected to the BSR.
The following sections discuss configuring server-related parameters on the BSR:
n
Configuring DNS
Configuring LDAP
Configuring SNTP
6-1
Release 6.2.0
where:
X is the module slot number.
Y is the port number.
2. Use the ip helper-address command in Interface Configuration mode to forward
default UDP broadcasts including IP configuration requests to the DHCP server,
as shown below:
MOT:7A(config-if)#ip helper-address <A.B.C.D>
where:
A.B.C.D is the destination address.
Example
MOT:7A(config-if)#ip helper-address 200.200.200.1
You can use the cable helper-address command in Interface Configuration mode
to configure DHCP relay on the cable interface. Refer to Use for more
information.
3. Enable the Ethernet interface and the configuration change with the no shutdown
command.
6-2
Release 6.2.0
MOT:7A(config-if)#no shutdown
6. Verify that the information was entered correctly by displaying the running
configuration in Privileged EXEC mode.
MOT:7A#show running-config
Configuring DNS
Domain Name System (DNS) maps host names to IP addresses. For example, it
allows you to reference the host motorola.com instead of having to remember that its
IP address is 198.93.23.13.
Configuring DNS involves the following tasks:
n
where:
A.B.C.D is the IP address of the Domain Name Server (DNS).
For example:
MOT:7A(config)#ip name server 192.168.1.253
6-3
Release 6.2.0
where:
name is the default domain name.
For example:
MOT:7A(config)#ip domain-name motorola.com
2. To create a domain list of up to six (6) host names to complete unqualified host
names, use the ip domain-list command in Global Configuration mode. If the
primary domain-name fails to resolve, the software uses these names.
MOT:7A(config)#ip domain-list <WORD>
where:
WORD indicates the domain name to use to resolve unqualified host names
when the primary domain fails to resolve.
3. Verify that the information was entered correctly by displaying the running
configuration.
MOT:7A#show running-config
6-4
Release 6.2.0
Configuring LDAP
Lightweight Directory Access Protocol (LDAP) servers provide a way to name,
manage, and access collections of attribute-value pairs. LDAP servers consist of
entries that hold information about some thing or concept, such as a person or
organization. Every entry in an LDAP server belongs to one or more object classes.
n
where:
A.B.C.D is the LDAP server IP address.
1-1024 is the port number of the LDAP server.
For example:
MOT:7A(config)#ldap server primary 192.168.1.253 port 389
Use the options in Table Table to further define ldap server parameters:
Table Command options for the ldap server command.
Option
Description
ldap server binddn Distinguished LDAP server name required to bind to this server.
nobinddn
nopassword
password
Password
2. Use the ldap client command, in Global configuration mode, to start the LDAP
client, as shown below:
6-5
Release 6.2.0
MOT:7A(config)#ldap client
Note: If the primary LDAP server has not been specified, the following
message appears when attempting to start the LDAP client:
Please configure Primary LDAP server address before starting
the client.
where:
WORD is the distinguished location name of entry from which to start a
search.
4. Verify that the information was entered correctly by displaying the running
configuration.
MOT:7A(config)#show running-config
Configuring SNTP
The Simple Network Time Protocol (SNTP) provides system time with high
accuracy, but it does not provide the complex filtering and statistical mechanisms of
the Network Time Protocol (NTP). Configure the BSR to operate in client mode with
the remote system at the specified address. In this mode, the BSR can be synchronized
to the remote system, but the remote system never can be synchronized to the BSR.
Note: Ensure that the clock timezone command is configured before
configuring SNTP on the BSR. If the clock timezone command is not
configured, then time fluctuation occurs during a switchover if the Primary
SRM switches to the Standby SRM (which does not have the timezone
initialized). Refer to Setting System Passwords on page 1-3 for more
information.
Follow these steps to configure SNTP server parameters on the BSR:
1. Configure the SNTP server with the sntp server command in Global
Configuration mode.
6-6
Release 6.2.0
where
224.0.1.1 is the NTP Multicast server IP address.
A.B.C.D is the IP address of the server.
Hostname is the DNS name of the server.
Note: When the server address is 224.0.1.1, the IANA assigned multicast
address for NTP, the client transmits a multicast request to this multicast
address and waits for replies. It then binds to the first server that replies. All
subsequent transactions happen in unicast mode.
For example:
MOT:7A(config)#sntp server 192.168.1.253
MOT:7A(config)#sntp server sntpd.motorola.com
2. Authenticate SNTP time sources with the sntp authenticate command in Global
Configuration mode.
MOT:7A(config)#sntp authenticate
Note: If you configure the BSR to operate in authenticated mode, you must
also configure an authentication key and a trusted key.
3. Configure an authentication a key for the trusted time source with the sntp
authentication-key md5 command on Global Configuration mode. You
configure SNTP authentication keys so that the BSR can send authenticated
packets. The key must be identical between a set of peers sharing the same key
number.
MOT:7A(config)#sntp authentication-key <1-4294967295> [md5
<WORD>]
where:
1-4294967295 is the SNTP authentication key.
6-7
Release 6.2.0
5. Configure an SNTP broadcast delay, which is, with the sntp broacastdelay
command in Global Configuration mode.
MOT:7A(config)#sntp broadcastdelay <1-999999>
where:
1-999999 is the estimated round-trip delay in microseconds.
6. Configure a key number for trusted time sources with the sntp trusted-key
command in Global Configuration mode. For SNTP, configure the keys you are
allowed to use when you configure the BSR to synchronize its time with other
systems on the network.
MOT:7A(config)#sntp trusted-key <1-4294967295>
where:
1-4294967295 is the key number for the trusted time sources.
7. To display information about SNTP, use the show sntp command, as follows:
MOT:7A#show sntp
8. Verify that the information was entered correctly by displaying the running
configuration.
MOT:7A#show running-config
6-8
Release 6.2.0
2. Enter the Cable Interface Configuration mode from Global Configuration mode,
as follows:
MOT:7A(config)#interface cable <X/Y>
6-9
Release 6.2.0
where:
X/Y is the slot and MAC Domain number of the CMTS module.
3. Use the ip helper-address command, in Interface Configuration mode, to specify
a destination IP address for forwarding UDP broadcast packets, including
BOOTP, as shown below:
MOT:7A(config-if)#ip helper-address <A.B.C.D>
where:
A.B.C.D is the destination IP address.
4. Verify that the information was entered correctly by displaying the running
configuration:
MOT:7A(config-if)#show running-config
6-10
Release 6.2.0
where:
WORD is the FTP user name that is up to 31 characters.
Use the no ip ftp username command to delete the entry.
2. To specify the FTP password to be used for the FTP connection, use the ip ftp
password command in Global Configuration mode, as shown below.
MOT:7A(config)#ip ftp password [0 | 7] <LINE>
where:
0 indicates a unencrypted password follows.
7 indicates an encrypted password follows.
LINE is the FTP password, which comprises the password (31 character
minimum, 78 character maximum for option 7) - enclosed with double quotes
if the password contains spaces). The "%" and "!" characters must not be
used.
Use the no ip ftp password command to delete the entry.
6-11
7
Configuring Redundancy
Introduction
This chapter discusses the following BSR 64000 redundancy configuration tasks:
n
SRM Redundancy
CMTS Redundancy
NIM Redundancy
TX32 Redundancy
RX48 Redundancy
SRM Redundancy
The BSR 64000 supports1:1sparing for the Supervisory Resource Module (SRM)
redundancy by using a Standby SRM and an Active SRM in slot 7 or 8. The Standby
SRM is used to protect the Active SRM, which controls the chassis. The Standby
SRM contains the static configuration information for the Active SRM causing no
configuration changes when a switch-over situation occurs because information is
continuously updated on the Standby SRM.
7-1
Release 6.2.0
When the BSR 64000 is initially powered with SRMs seated in module slots 7 and 8,
the SRM in slot 7 becomes active and the SRM in slot 8 becomes the standby. If there
is an SRM in either Slot 7 or Slot 8 and a second SRM is inserted, this second SRM
becomes the Standby SRM. Once the Standby SRM boots, it immediately gets a copy
of the startup configuration from the Active SRM.
Note: For an SRM Redundant BSR 64000 or BSR 64000 HD where the SRM
installed in Slot 8 is the Active SRM, replacing a fan or blower module (or
removing and re-installing the existing one) can cause all CMTS and NIM
(HSIM) Resource Modules operating in the chassis to reset. Therefore,
perform a manual switchover (through the BSR CLI redundancy
force-switchover srm command) to make the SRM installed in Slot 7 the
Active SRM before replacing (or re-installing) a fan or blower module in a
BSR 64000 HD or BSR 64000 chassis.
Note: After the first administrative (manual) switchover you perform for BSR
64000 systems employing Redundant SRMs, Redundant CMTS modules, or
both; wait a minimum of 5 minutes for SRMs and 60 seconds for CMTS
modules before initiating another administrative switchover.
7-2
Release 6.2.0
Configuring Redundancy
The ejector switch is pulled down on the Active SRM causing it to power down.
Caution: To prevent hardware damage, do not insert the SRM I/O module in
I/O Slot 8. The SRM I/O Module must be inserted in I/O Slot 7.
7-3
Release 6.2.0
7-4
Telnet
SNMP requests
OSPF Version 2
BGP 4
ARP database
Radius Client
SSH2 Server
Statistics
Release 6.2.0
Configuring Redundancy
SNTP
MPLS
IS-IS
PPP
The routing protocol tasks restart and have the following affects:
n
Communications with peer routing systems are lost and must be reestablished.
The following tasks controlling the CLI, Telnet and SNMP are affected:
n
n
This command is issued so that if the Standby SRM takes over, the Standby SRM uses
the most current startup configuration, which prevents network configuration
problems in the event of a switch-over.
7-5
Release 6.2.0
Follow these steps to force the Active SRM to the Standby SRM:
1. Use the redundancy force-switchover srm in Privileged EXEC mode to
manually switch-over service from the Active SRM to the Standby SRM, as
shown below:
MOT:7A#redundancy force-switchover srm
2. Use the show chassis status command to check the redundancy status
information for both the Active SRM and the Standby SRM in the BSR 64000
chassis.
Refer to the BSR 64000 Command Reference Guide to see typical screen output
and field descriptions for the show chassis status command.
7-6
Release 6.2.0
Configuring Redundancy
CMTS Redundancy
Redundancy for CMTS module operation on the BSR is enabled through a 1:N
redundancy scheme. In this scheme, specialized hardware modules (the Standby
CMTS Resource Module and its associated I/O Module) mirror the operational
configuration of the other operating CMTS modules in the chassis (the Primary
CMTS Modules) and are able to assume the operation of a failed Primary CMTS
Module automatically without disruption to data and voice traffic on the HFC
Network. The Standby CMTS Module in Slot 6 protects up to 12 Primary CMTS
Modules and supports the first failed Primary CMTS Module. Subsequent Primary
CMTS Module failures are not supported until service is manually given back from
the Standby CMTS module to the Primary CMTS Module that had previously failed.
Primary CMTS Modules can be installed in Slots 0 through 5 or 9 through 14 of the
BSR. All Primary CMTS Modules are enabled for redundancy by default unless they
are specifically configured not to participate in the redundancy scheme.
The system automatically switches-over to the Standby CMTS module if a Primary
CMTS fails. The operator may also administratively force a switch-over from a
Primary CMTS to the Standby CMTS with a CLI command. Once the operation of a
failed Primary CMTS Module is restored, the operator must enter a CLI command to
administratively force a switch-over from the Standby CMTS module back to a
Primary CMTS.
All Primary CMTS Module configuration information and cable modem (CM)
registration information is continuously updated on the Standby CMTS Module
during normal BSR operation. As a result, CMs initially registered with a primary
CMTS Module remain registered and data and voice traffic is virtually unaffected
during a switch-over to the Standby CMTS Module or a give-back to a Primary
CMTS Module. Also, CMs do not deregister during a switch-over unless they are in
the process of registering. In this event, some CMs are forced to reregister and voice
calls must be re-established.
During a switch-over, all Multimedia Terminal Adapters (MTAs) that provide voice
services are given priority over CMs carrying data services.
7-7
Release 6.2.0
7-8
Release 6.2.0
Configuring Redundancy
If there are any internal software errors encountered when an operator performs a
CMTS module switch-over, the system software automatically resets a Primary
CMTS module, the Standby CMTS module, or both in an attempt to automatically
recover. In this event, all CMs reregister.
7-9
Release 6.2.0
The Standby CMTS Resource Module must be in Slot 6 and its associated I/O
module is installed in I/O Module Slot 6. The Standby CMTS Resource module
must also be finished booting and in a standby state.
For further information, refer to the BSR 64000 Installation Guide (50 Amp chassis)
and the BSR 64000 HD Installation Guide (100 Amp chassis).
Description
Primary
CMTS
Blinking Green
Solid Green
Blinking Green
Solid Green
Standby
CMTS
For further information on CMTS module LED display states, refer to the BSR 64000
Installation Guide (50 Amp chassis) and the BSR 64000 HD Installation Guide (100
Amp) chassis.
7-10
Release 6.2.0
Configuring Redundancy
Follow these steps to administratively switch service from a Primary CMTS Module
to the Standby CMTS Module:
1. Use the redundancy force-switchover cmts in Privileged EXEC mode to
administratively switch-over service from the specified Primary CMTS Module
to the Standby CMTS Module, as shown below:
MOT:7A#redundancy force-switchover cmts <NUM>
where:
NUM is the specified Primary CMTS Module.
7-11
Release 6.2.0
2. Use the show chassis status or show redundancy cmts command in all modes
except User EXEC mode to check the redundancy status information for both a
Primary CMTS Module and the Standby CMTS Module:
Note: After the BSR is rebooted, each Primary and Standby CMTS Module is
given 12-minutes to complete the boot process. If, after 12 minutes a CMTS
module has not booted, a timer starts that tracks the amount of time a CMTS
is unavailable (the Unavailable Timer). The Unavailable Timer indicates how
much time service belonging to a CMTS module has been unavailable to
subscribers since its last successful boot.
The following figure displays sample command line output from the show
chassis status command:
7-12
Type Sub
DTX
DTX
DTX
HSIM
CMTS
SRM4
TX32
TX32
TX32
GE2/ETH8
2x8(2.0)
DRX
CMTS
CMTS
CMTS
CMTS
DRX
RX48
2x8(2.0)
2x8(2.0)
2x8(2.0)
2x8(2.0)
RX48
Red
6
6
6
6
-
State
RUN
RUN
RUN
RUN
stby
RUN
RUN
RUN
RUN
RUN
RUN
RUN
-
RM
x
x
x
x
x
x
x
x
x
x
x
x
-
IO
x
x
x
p
p
x
x
x
x
x
x
x
x
x
x
UpTime
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
0w2d21h
Release 6.2.0
Configuring Redundancy
Filed descriptions from the show chassis command output are described below::
Field
Description
Slot
Type
The type of module that is inserted into the BSR 64000. HSIM (NIM)
indicates either the 8-port Fast Ethernet, POS or Gigabit Ethernet Network
Interface module. CMTS indicates the CMTS module. DTX and DRX
indicate TX32 and RX48 modules, respectively. SRM indicates the
Supervisory Resource Module.
Sub
Indicates the module sub-type. For example 2x8 would indicate the type of
the CMTS module that is installed in the slot number.
Red
Indicates the slot that takes over if this slot is forced to switch over.
State
RM
IO
UpTime
If the system clock has been set using the clock set command, the
UpTime column displays the amount of time that the module has been
operational. The time is expressed in hours, minutes, seconds (hh:mm:ss)
days (1-31), and the month (first 3 letters of the month).
LastUpTime When a module is down, the last operational time for the module.
Success
Failure
7-13
Release 6.2.0
The following figure displays the show redundancy cmts command output for the
Standby CMTS module and Primary CMTS module. The display includes; logging,
service switch-over instances, amount of time a CMTS module has been switched
over in minutes, and the current status of each CMTS module slot.
CMTS
Chassis Slot
Slot
Status
2
3
6
RUN
RUN
stby
Red
Slot
6
6
-
Primary
Slot
2
3
-
Logging
Status
full
full
inactive
Manual
Takeovers
Auto
Takeovers
0
0
0
0
0
0
Unavail
Time
0:00:00
0:00:00
0:00:00
The following tablr describes the module states displayed in the show redundancy
cmts command output:
7-14
Field
Description
CMTS Chassis
Slot
Slot Status
Red Slot
The redundant slot column indicates the chassis slot number to which
this slot switches over.
A dash - in the Red Slot column for Primary CMTS modules indicates
that the Primary CMTS module is either not inserted in the BSR chassis
or is booting.
A dash - in the Red Slot column for Slot 6 indicates that the Standby
CMTS module is in a standby state and does not have a redundant
peer.
If the Standby CMTS module has taken over for a Primary CMTS, this
Primary CMTS is now the Standby CMTS redundant peer and is
displayed in the Red Slot column for Slot 6.
A dash in the Red Slot column for a Primary CMTS module indicates
that it has been taken over by the Standby CMTS module in Slot 6.
For example, if the Standby CMTS module takes over for the Primary
CMTS module in Slot 4, the number 4 is displayed in the Red Slot
column for Slot 6. When the Primary CMTS module is in the stby state,
(because it has been taken over by the Standby CMTS module in Slot
6), the Red Slot column for Slot 4 is 6.
Release 6.2.0
Configuring Redundancy
Field
Description
Primary Slot
Describes the context in which this Primary CMTS module slot is active.
The chassis slot number is the same as a Primary CMTS module slot
when a Primary CMTS module slot is active. However, when the
Standby CMTS module slot is active, a Primary slot for which it is
running is indicated.
Logging Status
The full status indicates that CMTS information has been fully
replicated to the Standby CMTS module for this slot. The "inactive"
status indicates that the CMTS is not running or has no redundant slot
to which to replicate. The "partial" status indicates that replication is
currently underway. A CMTS cannot be forced to switchover until it has
completed replication.
Manual
Takeovers
Auto-takeovers
Unavailable
Time
2. Use the show chassis status or show redundancy cmts command in all modes
except User EXEC mode to check the redundancy status information for both a
Primary CMTS Module and the Standby CMTS Module.
7-15
Release 6.2.0
where:
NUM is a Primary CMTS Module slot number.
2. Use the show chassis status or show redundancy cmts command in all modes
except User EXEC mode to check the redundancy status information for both a
Primary CMTS Module and the Standby CMTS Module.
7-16
Release 6.2.0
Configuring Redundancy
where:
NUM is a Primary CMTS Module slot number.
2. Use the show chassis status or show redundancy cmts command in all modes
except User EXEC mode to check the redundancy status information for both a
Primary CMTS Module and the Standby CMTS Module.
If you need to disable a Primary CMTS module, refer to Disabling Redundancy on a
Primary CMTS Module on page 7-16, for more information.
7-17
Release 6.2.0
NIM Redundancy
NIM redundancy for the 10/100 Fast Ethernet and Gigabit Ethernet modules uses
multipath load sharing based on Equal-Cost Multi-path (ECM) which is supported
through the BGP and OSPF routing protocols.
7-18
Release 6.2.0
Configuring Redundancy
The following sections provide examples for configuring EBGP HSIM redundancy.
Note: The maximum number of paths is 2 by default. The maximum number
of paths must be set to 2 in order to establish two Equal-Cost Multi-path
(ECM) routes. If this parameter has been changed to 1, issue the
maximum-paths 2 command in Router Configuration mode.
Configuring Router 1
Follow these steps to configure Router 1:
1. Use the router bgp 200 command in Global Configuration mode to enable BGP
routing in autonomous system (AS) 200 and enter Router Configuration mode, as
shown below:
router1(config)#router bgp 200
2. Use the network mask command in Router Configuration mode to specify the
destination BGP network IP address and subnetwork IP mask, as shown below:
router1(config-bgp)#network 2.2.2.0 mask 255.255.255.0
where:
2.2.2.0 is the IP address of the destination EBGP network for Router 1.
255.255.255.0 is the 24-bit IP subnetwork address mask.
3. Use the neighbor remote-as command in Router Configuration mode to specify
the BSR neighbor network IP address and its remote autonomous system number,
as shown below:
router1(config-bgp)#neighbor 195.168.16.65 remote-as 100
where:
195.168.16.65 is the IP address of BSR Ethernet interface 1 on module slot
13.
remote-as 100 is the remote autonomous system number of the BSR.
4. Use the neighbor remote-as command in Router Configuration mode to specify
the Router 2 neighbor network IP address and its remote autonomous system
number, as shown below:
router1(config-bgp)#neighbor 2.2.2.2 remote-as 200
where:
7-19
Release 6.2.0
Configuring Router 2
Follow these steps to configure Router 2:
1. Use the router bgp 200 command in Global Configuration mode to enable BGB
routing in autonomous system (AS) 200 and enter Router Configuration mode, as
shown below:
router2(config)#router bgp 200
2. Use the network mask command in Router Configuration mode to specify the
destination BGP network IP address and subnetwork IP mask, as shown below:
router2(config-bgp)#network 2.2.2.0 mask 255.255.255.0
where:
2.2.2.0 is the IP address of the destination EBGP network for Router 2.
255.255.255.0 is the 24 bit IP subnetwork address mask.
3. Use the neighbor remote-as command in Router Configuration mode to specify
the BSR neighbor network IP address and its remote autonomous system number,
as shown below:
router2(config-bgp)#neighbor 194.168.16.65 remote-as 100
where:
194.168.16.65 is the IP address of the BSR Ethernet interface 0 on module
slot 12.
remote-as 100 is the remote autonomous system number.
4. Use the neighbor remote-as command in Router Configuration mode to specify
the Router 1 neighbor network IP address and its remote autonomous system
number, as shown below:
router2(config-bgp)#neighbor 2.2.2.1 remote-as 200
where:
2.2.2.1 is the IP address of Router 1 (associated with the 2.2.2.0 network).
7-20
Release 6.2.0
Configuring Redundancy
where:
195.168.16.66 is the IP address of the Router 1 interface (associated with the
195.168.16.64 network).
remote-as 200 is the remote autonomous system number for Router 1.
3. Use the neighbor remote-as command in Router Configuration mode to specify
the BSR neighbor network IP address and its remote autonomous system number
for Router 2, as shown below:
BSR64000:7A(config-bgp)#network 194.168.16.65 remote-as 200
where:
194.168.16.66 is the IP address of the Router 2 interface (associated with the
194.168.16.64 network).
remote-as 200 is the remote autonomous system number for Router 2.
4. Use the show ip route bgp command to view the Equal-cost Multi-path routes to
the 2.2.2.0 network, as shown below:
BSR64000:7A#show ip route bgp
7-21
Release 6.2.0
The following figure displays typical show ip route bgp command output:
BGP table version is 272, local router ID is 43.43.43.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
Metric
LocPrf Wght Path
*> 2.2.2.0/24
195.168.16.66
0
0 200 i
*>
194.168.16.66
0
200 i
The show ip route bgp command output shows the redundant EBGP routes to
destination network 2.2.2.0 through interface 195.168.16.66 on Router 1 and
through interface 194.168.16.66 on Router 2.
5. Use the show ip route ospf command to view the OSPF Equal-cost Multi-path
routes to the 2.2.2.0 network within the EBGP network, as shown below:
BSR64000:7A#show ip route ospf
The following figure displays typical show ip route ospf command output:
O
O
O
O
O
O
E2
E2
E2
E2
E2
E2
10.1.0.0/16
10.2.0.0/16
10.3.0.0/16
10.4.0.0/16
10.5.0.0/16
10.6.0.0/16
[110/20]
[110/20]
[110/20]
[110/20]
[110/20]
[110/20]
via
via
via
via
via
via
172.50.1.10,
172.50.1.10,
172.50.1.10,
172.50.1.10,
172.50.1.10,
172.50.1.10,
gigaether
gigaether
gigaether
gigaether
gigaether
gigaether
15/0
15/0
15/0
15/0
15/0
15/0
The show ip route ospf command output shows the redundant next hop routes to
destination network 2.2.2.0 through host 2, which is comprised of interface
195.168.16.66 (on Router 1) and through interface 194.168.16.66 (on Router 2).
7-22
Release 6.2.0
Configuring Redundancy
The following sections provide examples for configuring OSPF NIM redundancy.
Note: The maximum number of paths is 2 by default. The maximum number
of paths must be set to 2 in order to establish two Equal-Cost Multi-path
(ECM) routes. If this parameter has been changed to 1, issue the
maximum-paths 2 command in Router Configuration mode.
7-23
Release 6.2.0
Configuring Router 1
Follow these steps to configure Router 1:
1. Use the router ospf command in Global Configuration mode to enable OSPF
routing and enter Router Configuration mode, as shown below:
router1(config)#router ospf
2. Use the network area command in Router Configuration mode to specify the
OSPF network IP address, wildcard mask and Area ID for the BSR and Router 1,
as shown below:
router1(config-ospf)#network 195.168.16.64 0.0.0.3 area 0
where:
195.168.16.64 is the IP address of the OSPF network that is associated with
Ethernet interface 1 on module slot 13.
0.0.0.3 is the IP address type mask with dont care bits (wildcard bit mask).
This 30 bit wildcard bit mask matches all the bits of the network IP address
except the last three bits.
0 is the area number.
3. Use the network area command in Router Configuration mode to specify the
destination OSPF network IP address, wildcard mask and Area ID, as shown
below:
router1(config-ospf)#network 2.2.2.0 0.0.0.255 area 0
where:
2.2.2.0 is the IP address of the destination OSPF network for Router 1.
0.0.0.255 is the IP address type mask with dont care bits (wildcard bit
mask). This 24 bit wildcard bit mask matches all the bits of the network IP
address.
0 is the area number.
Configuring Router 2
Follow these steps to configure Router 2:
1. Use the router ospf command in Global Configuration mode to enable OSPF
routing and enter Router Configuration mode, as shown below:
7-24
Release 6.2.0
Configuring Redundancy
router2(config)#router ospf
2. Use the network area command in Router Configuration mode to specify the
OSPF network IP address, wildcard mask and Area ID for the BSR and Router 2,
as shown below:
router2(config-ospf)#network 194.168.16.64 0.0.0.3 area 0
where:
194.168.16.64 is the IP address of the OSPF network for the BSR and Router
2.
0.0.0.3 is the IP address type mask with dont care bits (wildcard bit mask).
This 30 bit wildcard bit mask matches all the bits of the network IP address
except the last three bits.
0 is the area number.
3. Use the network area command in Router Configuration mode to specify the
destination OSPF network IP address, wildcard mask and Area ID, as shown
below:
router2(config-ospf)#network 2.2.2.0 0.0.0.255 area 0
where:
2.2.2.0 is the IP address of the destination OSPF network.
0.0.0.255 is the IP address type mask with dont care bits (wildcard bit
mask). This 24 bit wildcard bit mask matches all the bits of the network IP
address.
0 is the area number.
2. Use the network area command in Router Configuration mode on the BSR to
specify the OSPF network IP address, wildcard mask and Area ID for the BSR
and Router 1, as shown below:
BSR64000:7A(config-ospf)#network 195.168.16.64 0.0.0.3 area 0
7-25
Release 6.2.0
where:
195.168.16.64 is the IP address of the OSPF network for Router 1.
0.0.0.3 is the IP address type mask with dont care bits (wildcard bit mask).
This 30 bit wildcard bit mask matches all the bits of the network IP address
except the last three bits.
0 is the area number.
3. Use the network area command in Router Configuration mode on the BSR to
specify the OSPF network IP address, wildcard mask and Area ID for the BSR
and Router 2, as shown below:
BSR64000:7A(config-ospf)#network 194.168.16.64 0.0.0.3 area 0
where:
194.168.16.64 is the IP address of the OSPF network for the BSR and Router
2.
0.0.0.3 is the IP address type mask with dont care bits (wildcard bit mask).
This 30 bit wildcard bit mask matches all the bits of the network IP address
except the last three bits.
0 is the area number.
4. Use the show ip route ospf command in Router Configuration mode on the BSR
to view the Equal-cost Multi-path routes to the 2.2.2.0 network, as shown below:
MOT:7A(config-ospf)#show ip route ospf
The show ip route ospf command output shows the redundant next hop routes to
destination network 2.2.2.0 through host 2, which is comprised of interface
195.168.16.66 (on Router 1) and through interface 194.168.16.66 (on Router 2).
Refer to the BSR 64000 Command Reference Guide to see typical screen output
from the show ip ospf route command.
7-26
Release 6.2.0
Configuring Redundancy
TX32 Redundancy
The TX32 Redundancy feature is designed to minimize any disruption to the network
in the event of a TX32 failure. A Primary TX32 module and the Standby TX32
module are synchronized by hardware to transmit the same synchronization master
clock timestamp value. The system automatically switches-over to the Standby
TX32 module if a Primary TX32 module fails. The operator may also
administratively force a switch-over from a Primary TX32 to the Standby TX32.
Once the operation of a failed Primary TX32 module is restored, the operator must
administratively force a switch-over from the Standby TX32 module back to a
Primary TX32 in order to restore redundancy protection.
The hardware foundation for TX32 redundancy is a 3-slot redundancy module. The
3-slot I/O module consists of 2 Primary TX32 modules and 1 Standby TX32 module
and is designed so that the Primary TX32s are the first and third slots in the module.
The center slot is reserved for the Standby TX32 module. The I/O design is such that
the center slot will only support the Standby TX32 and cannot be used by a Primary
TX32 module. The Standby TX32 will always be the center slot in the 3-slot
redundancy module. The TX32 3-slot I/O module can be inserted anywhere in the
BSR chassis with the exception of slots 7 and 8 which are reserved for SRM modules,
slot 6 which is reserved for a standby CMTS, and slot 15 which does not support the
necessary backplane signals.
7-27
Release 6.2.0
Follow these steps to administratively switch service from a Primary TX32 Module to
the Standby TX32 Module:
1. Use the redundancy force-switchover dtx command, in Privileged EXEC mode,
to administratively switch-over service from the specified Primary TX32 Module
to the Standby TX32 Module, as shown below:
MOT:7A#redundancy force-switchover dtx <NUM>
where:
NUM is the slot number of the Primary TX32 Module.
7-28
Release 6.2.0
Configuring Redundancy
2. Use the show chassis status or show redundancy dtx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
Primary TX32 Module and the Standby TX32 Module:
where:
NUM is the slot number of the Standby TX32 module.
2. Use the show chassis status or show redundancy dtx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
Primary TX32 Module and the Standby TX32 Module.
7-29
Release 6.2.0
where:
NUM is a Primary TX32 Module slot number.
2. Use the show chassis status or show redundancy dtx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
Primary TX32 Module and the Standby TX32 Module.
where:
NUM is a Primary TX32 Module slot number.
2. Use the show chassis status or show redundancy dtx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
Primary TX32 Module and the Standby TX32 Module.
If you need to disable a Primary TX32 module, refer to Disabling Redundancy on a
Primary CMTS Module for more information.
7-30
Release 6.2.0
Configuring Redundancy
RX48 Redundancy
The RX48 redundancy feature is designed to minimize any disruption to the network
in the event of a RX48 failure. A primary RX48 module and the standby RX48
module are synchronized by hardware to transmit the same synchronization master
clock timestamp value. The system automatically switches-over to the standby RX48
module if a primary RX48 module fails. The operator can also administratively force
a switch-over from a primary RX48 to the standby RX48. Once the operation of a
failed primary RX48 module is restored, the operator must administratively force a
switch-over from the standby RX48 module back to a primary RX48 in order to
restore redundancy protection.
The standby RX48 Resource Module is designed to operate only in slot 6 of the BSR
chassis. A single standby RX48 module supports redundancy for the primary RX48
Resource Modules. However, it can assume the operation for only one of the primary
RX48 Resource Modules at one time.
Note: When the standby RX48 Resource Module is used, 2:8 CMTS
redundancy cannot be used since the 2:8 CMTS and RX48 modules use the
same slot. A standby RX48 Resource Module does not provide redundancy
for 2:8 CMTS modules.
7-31
Release 6.2.0
Follow these steps to administratively switch service from a primary RX48 module to
the standby RX48 module:
1. Use the redundancy force-switchover drx command, in Privileged EXEC
mode, to administratively switch-over service from the specified primary RX48
module to the standby RX48 module, as shown:
MOT:7A#redundancy force-switchover drx <X>
where:
X is the slot number of the primary RX48 module.
7-32
Release 6.2.0
Configuring Redundancy
2. Use the show chassis status or show redundancy drx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
primary RX48 module and the standby RX48 module:
where:
X is the slot number of the standby RX48 module.
2. Use the show chassis status or show redundancy drx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
primary RX48 module and the standby RX48 module.
where:
7-33
Release 6.2.0
where:
X is a primary RX48 module slot number.
2. Use the show chassis status or show redundancy drx command, in all modes
except User EXEC mode, to check the redundancy status information for both a
primary RX48 module and the standby RX48 module.
If you need to disable a primary RX48 module, refer to Disabling Redundancy on a
Primary RX48 Module for more information.
7-34
8
Configuring the Ether-FlexTM
Module
Introduction
The Ether-Flex module can be configured for two Gigabit Ethernet or eight 10/100
Ethernet interfaces. This chapter provides information on configuring the Ether-Flex
Module. This chapter includes the following sections:
n
8-1
Release 6.2.0
where:
0-5, 9-15 is the module slot number.
2. Use the reset slot command to make the configuration take effect:
MOT:7A#reset slot <num>
where:
<num> is the slot number of the module that you specified in Step 1.
where:
0-5, 9-15 is the module slot number.
2. Use the reset slot command to make the configuration take effect:
MOT:7A#reset slot <num>
where:
<num> is the slot number of the module that you specified in Step 1.
8-2
Release 6.2.0
Figure Figure is typical screen output from the show chassis status command.
Ether-Flex modules appear in the display as HSIM GE2/ETH8. The command output
shows that there are Ether-Flex modules in slots 10 and 15.
Type Sub
CMTS 2x8(2.0)
CMTS 2x8
CMTS 1x8
CMTS 2x8(2.0)
SRM3
HSIM GE2/ETH8
HSIM GE2/ETH8
Red
6
6
-
State
RUN
RUN
RUN
stby
RUN
RUN
RUN
RM
x
x
x
x
x
x
x
IO
x
x
x
x
x
x
UpTime
19:06:40
19:06:30
19:08:48
19:06:30
19:11:32
19:05:05
19:09:25
8-3
Release 6.2.0
where:
X is the Ether-Flex module slot.
Y is the port number.
Figure Figure is typical screen output from the show interfaces gigaether command.
The display shows that the SFP module type is 1000BaseSX. Table Table lists and
describes the detected SFP module that can be indicated in the SFP Type field.
8-4
Release 6.2.0
1000BaseLX/EX/ZX
1000BaseT
<not installed>
8-5
Release 6.2.0
8-Path ECMP
Equal-cost multi-path (ECMP) routing is a common method used by operators to
support load sharing and redundancy. Earlier releases of the BSR 64000 software
supported two equal-cost paths across two Gig-E modules commonly installed in the
BSR 64000. The ECMP feature has been enhanced in Release 5.2.0 to support a
maximum of three equal-cost multi-paths for the installed HSIM2 and Ether-Flex
modules, and further enhanced in Release 5.3.0 to support a maximum of eight
equal-cost multi-paths required to support four Ether-Flex modules installed in a BSR
64000 chassis.
There are two Gigabit Ethernet interfaces on each HSIM4 module, which means that
two ECMP paths are supported on each HSIM4. BSR support of up to 8 ECMP routes
to distribute upstream IP traffic across dual Gigabit Ethernet interfaces is based on the
configurations shown in the following table:
Maximum Number of
Equal-Cost Multi-Paths
HSIM4
Multi-path routing maybe used with many of the common routing protocols such as
OSPF, IS-IS, RIP and BGP. The routing protocols learn the paths and the best routes
are added to the forwarding table for the HSIM modules.
8-6
9
Configuring IPDR
Introduction
IPDR.org is an open consortium of leading service providers, equipment vendors,
system integrators, and billing and mediation vendors collaborating to facilitate the
exchange of usage and control data between network and hosting elements and
operations and business support systems by deployment of Internet Protocol Detail
Record (IPDR) standards. IPDR data formatting and streaming standards are
incorporated into CableLabs' DOCSIS specifications, by ongoing collaboration
between the two organizations, specifically in CableLabs Subscriber Account
Management Interface Specification (SAMIS). The SAMIS format for providing
subscriber account and billing information is specified by the DOCSIS Operations
Support System Interface (OSSI) specification.
The IPDR Streaming Protocol is now a mandatory element within the DOCSIS 2.0
Subscriber Accounting Management Interface Specification (SAMIS), and is
expected to be widely deployed by cable operators worldwide. With this most recent
adoption of the IPDR Streaming Protocol, to be implemented within Cable Modem
Termination Systems (CMTS), cable operators will be able to practice advanced
accounting data collection processing with the benefits of IPDR's plug-and-play
interoperability for network and business systems in the usage domain.
9-1
Release 6.2.0
IPDR based subscriber usage data accounting allows MSOs to accurately and reliably
collect and account for user traffic data from a DOCSIS access network. IPDR
support on the BSR offers a cost-effective and scalable solution for cable network
infrastructure. MSOs can use the BSR for interconnecting a cable network to the ISP
network or interconnecting distributed enterprise sites over a common backbone
network. The BSR provides layer 3 routing and limited layer 2 bridging services
through the cable access and backbone network to satisfy the above mentioned
application scenarios.
IPDR based export of subscriber usage accounting data from the BSR uses a standard
protocol interface with the collectors (servers). The typical deployment scenario is for
the BSR to interface with an IPDR collection network which is a network comprised
of IPDR collection systems.
Minimum Configuration
At a minimum, a user needs to enable IPDR on the BSR and configure the IP address
and priority of the collector. This allows the operation of the IPDR Exporter on the
BSR with all other parameters using their default values. Refer to the following:
n
Enabling IPDR
Advanced Configuration
In addition to enabling IPDR and configuring the IP address and priority of the
collector, a user can change some of the other operational parameters (collect interval,
poll-rate, keepalive interval, etc.) to a value other than the default setting for the
optimal operation of the IPDR Exporter on BSR. Refer to the following:
9-2
Enabling IPDR
Release 6.2.0
Configuring IPDR
Enabling IPDR
Use the ipdr enable command, in Global Configuration mode, to enable the IPDR
export of subscriber usage based accounting information. The default is disabled.
MOT(config)# ipdr enable
where:
A.B.C.D is the IP Address of the collector.
0-3 is the priority value of the collector. The collector with highest priority value
(the one with highest numerical value) is selected as the primary collector for a
given IPDR session. If the priority value for two or more collectors is the same,
the collector with the lowest IP Address will be selected as the primary collector.
If the primary collector is unreachable for any reason, a session will be
established with the next highest priority collector.
1024-65535 specifies the TCP port for the collector connection - this should be
one of the non-reserved non-assigned TCP port number for the IPDR connection.
If not specified, the default port of 4737 will be used.
cpe-list-suppress optionally suppresses the inclusion of the CPE IP address list
as part of IPDR data record being exported to the collector. This could be useful
for improving performance and also for disabling the inclusion of CPE IP
Address List in IPDR records to be sent to collectors which do not support CPE
IP Address List ECN. If not specified, by default CPE IP Address list will be
included in IPDR records sent to a particular collector.
Note: The Session Id should be configured as "0" in the IPDR Collector when
configuring the Exporter (BSR) information in the IPDR Collector.
9-3
Release 6.2.0
Note: The ipdr collector command allows for the provisioning of a maximum
of four IPDR collectors. An IPDR collector configured with this command is
uniquely identified using its IP address.
where:
15-1440 is the collection interval in minutes. The default collection interval is 30
minutes.
where:
1-128 is the maximum number of unacknowledged (pending) IPDR records. The
default maximum number of unacknowledged IPDR records is 64.
Note: Changing the ackSequenceInterval value will not affect an existing
IPDR session with the collector. A changed ackSequenceInterval value will
be used for a new, subsequently established IPDR session.
9-4
Release 6.2.0
Configuring IPDR
where:
1-60 is the maximum time between ACKs in seconds. The default maximum time
between ACKs is 30 seconds.
Note: Changing the ackTimeInterval value will not affect an existing IPDR
session with the collector. A changed ackTimeInterval value will be used for a
new, subsequently established IPDR session.
where:
10-300 is the keepalive interval in seconds. The default keepalive interval is 60
seconds.
Note: Changing the KeepAliveInterval value will not affect any existing IPDR
connection(s) with a collector(s). The existing IPDR connection(s) will
continue to use the previously negotiated value (as per the previous
configuration) with the collector. A changed KeepAliveInterval value will be
used for a new, subsequently established IPDR connection.
9-5
Release 6.2.0
where:
16-100 is the number subscriber accounting records transmitted per second. The
default number of subscriber accounting records transmitted per second is 32.
slot NUM configures the subscriber accounting information transmission rate for
a specific the BSR 64000 CMTS slot number. The no ipdr poll-rate slot
command resets the poll rate value for a specified slot to the default.
9-6
Release 6.2.0
Configuring IPDR
where:
A.B.C.D is the IP Address of a specific collector.
Refer to Chapter 7 to see typical screen output for the show ipdr connection
command.
The show ipdr session command displays the current status of a specific IPDR
session or all of the currently active sessions.
MOT:7A# show ipdr session [<NUM> [ detail ]]
where:
NUM is the IPDR unique session identifier. "0" indicates that the statistics
associated with session ID 0 will be displayed.
detail display the details of a specific IPDR session,
Refer to Chapter 7 to see typical screen output for the show ipdr session command.
The show cable metering-status command displays the status of most recent IPDR
streaming operation to currently selected IPDR collector
MOT:7A# show cable metering-status
Refer to the BSR 64000 Command Reference to see typical screen output for the show
cable metering-status command.
9-7
10
Configuring IPv6
Introduction
IPv6 represents the evolution of the Internet Protocol from IPv4. IPv6 maintains the
same basic operational principles of IPv4 but makes some important modifications
particularly in the area of addressing. One of the most significant changes is the
creation of an entirely new support protocol for IPv6 which combines several tasks
previously performed by other protocols in IPv4. This new protocol is called the IPv6
Neighbor Discovery (ND).
The Internet Control Message Protocol (ICMPv6) provides a method for error
reporting, route discovery and diagnostics. In addition, it provides information about
multicast group membership, and performs address resolution (Address Resolution
Protocol (ARP) in IPv4). Significant functionality of ICMPv6 includes neighbor
discovery and auto configuration. Neighbor discovery allows one device in a network
to find out about other nearby devices, and stateless address auto configuration allows
a device to dynamically configure an IPv6 address.
This chapter describes the following procedures:
n
10-1
Release 6.2.0
Tracing a Route
Pinging a Device
10-2
The default link local address for the interface is automatically configured when
first IPv6 prefix is configured on that interface.
A user specified link-local address can be configured before any primary or
secondary IPv6 address is configured for the interface, or to overwrite an existing
link-local address on an interface.
BSR will not allow IPv6 address to be configured on an interface if TRI is
enabled on that interface (via the encapsulation dot1q command). Similarly the
BSR will not allow TRI to be enabled on an interface if IPv6 subnets are already
configured on that interface.
The automatically generated default link local address for the interface is deleted
when the primary IPv6 prefix is deleted on that interface.
The user configured link local address for the interface will not be automatically
be deleted when the primary IPv6 prefix is deleted on that interface.
Deleting the primary IPv6 prefix of the interface without deleting all the
secondary prefixes of the interface is not allowed.
Release 6.2.0
Configuring IPv6
When the user specified link local address for the interface is deleted, the default
link local address for the interface is automatically generated if the primary IPv6
subnet is previously configured for the interface.
The BSR will not allow the IPv4-Mapped IPv6 Addresses to be configured as
part of the ipv6 address command.
where:
A:B:C:D:E:F:G:H/1-128 is the IPv6 address/Prefix Length.
2. Use the ipv6 address secondary command to optionally configure this IPv6
address as a secondary IPv6 address for the interface.
MOT:7A(config-if)#ipv6 address <A:B:C:D:E:F:G:H/1-128> [ secondary |
eui-64 secondary]
where:
A:B:C:D:E:F:G:H/1-128 is the IPv6 address/Prefix Length.
secondary optionally designates the IPv6 address as a secondary IPv6
address. Include the keyword secondary after the IPv6 address to specify
additional secondary IP addresses.
3. Use the ipv6 address eui-64 command to optionally specify an EUI-64 interface
identifier.
The Extended Unique Identifier (EUI). EUI-64 is a 64-bit identifier that is formed
by concatenating the 24-bit Organizationally Unique Identifier (OUI) with a
40-bit extension identifier that is assigned by the organization that purchased the
OUI. The resulting identifier is generally represented as a set of octets separated
by dashes (hexadecimal notation) or colons (bit-reversed notation) as in
xx-xx-xx-xx-xx-xx-xx-xx or xx:xx:xx:xx:xx:xx:xx:xx. RFC 3513 specifies the use of
EUI-64 identifiers as part of an IPv6 address.
10-3
Release 6.2.0
[secondary]
where:
A:B:C:D:E:F:G:H/1-128 is the IPv6 address/Prefix Length.
secondary optionally designates the IPv6 address as a secondary IPv6
address. Include the keyword secondary after the IPv6 address to specify
additional secondary IP addresses.
4. Use the ipv6 address { FE80:0:0:0:E:F:G:H } link-local command to configure a
link local address.
MOT:7A(config-if)#ipv6 address FE80:0:0:0:E:F:G:H link-local
where:
FE80:0:0:0:E:F:G:H link-local is the user-configured link-local address.
Note: The link-local option will not be visible until the correct upper 8 octets
of the link-local address, which must be FE80:0:0:0, is entered. The lower 8
octets can be any valid entry.
5. Use the description command to optionally specify descriptive information for
the interface that you are configuring. This information is limited to 80 characters
and spaces cannot be used.
Note: The entered description can be seen in the running configuration, and
in the command output of show commands such as the show ipv6 interface
command.
MOT:7A(config-if)#description <LINE>
where:
LINE is the text that describes the interface.
6. Use the show ipv6 interface command to verify the configuration and current
state of the interface that you configured, as shown below:
MOT:7A(config-if)#show ipv6 interface [ brief | cable <X/Y> | ethernet
<X/Y> | gigaether <X/Y> | loopback <1-255> ]
10-4
Release 6.2.0
Configuring IPv6
where:
brief displays summary information.
cable X/Y is the slot and MAC Domain number of the CMTS module.
ethernet X/Y is the Ethernet interface slot and port number.
gigaether X/Y is the Gigabit Ethernet interface slot and port number.
loopback 1-255 is the loopback interface number.
Refer to the IPv6 Commands in the BSR 64000 Command Reference Guide to see
typical screen output and field descriptions for the show ipv6 interface
command.
Note: The primary IP address can be removed only after all of the secondary
subnet addresses associated with the interface have been removed.
10-5
Release 6.2.0
cable-modem
where:
A:B:C:D:E:F:G:H is the IP address of the destination DHCP server.
10-6
Release 6.2.0
Configuring IPv6
Note: The IP helper address must be entered for the DHCP Lease Query
function to work regardless of whether the relay agent option is used.
where:
A:B:C:D:E:F:G:H/0-128 is the IPv6 address/Prefix Length.
A:B:C:D:E:F:G:H is the forwarding router's IPv6 address
A:B:C:D:E:F:G:H is the Link Local Address.
1-255 is the administrative distance; the default is 1.
10-7
Release 6.2.0
10-8
Release 6.2.0
Configuring IPv6
10-9
Release 6.2.0
10-10
Release 6.2.0
Configuring IPv6
Configuring Reachability
Determining that a device has become unreachable is important because a host can
adapt its behavior accordingly. In the case of an unreachable host, a device may wait a
certain period of time before trying to send packets to an unreachable host instead of
flooding the network with repeated attempts to send to the host. An unreachable
router is a signal that the device needs to find a new router to use, if an alternate is
available.
Use the ipv6 nd reachable-time command, in Interface Configuration mode, to
configure the reachability time on the BSR.
MOT:7A(config-if)#ipv6 nd reachable-time <0-3600000>
where:
0-3600000 is the reachability time in milliseconds.
10-11
Release 6.2.0
10-12
Release 6.2.0
Configuring IPv6
mapto translates the above IPv6 address/Prefix Length into an IPv4 address.
A:B:C:D maps to this IPv4 address.
Tracing a Route
A route path includes all IP level devices, such as routers and switches, that packets
travel through to get to their intended destination.
Use the traceroute6 command, in User EXEC or Privileged EXEC modes, to identify
the route path from the route source to the route destination.
MOT:7A# traceroute6 {<A:B:C:D:E:F:G:H > | options <WORD>
10-13
Release 6.2.0
Pinging a Device
The Packet Internet Groper (PING) ping6 command sends an Internet Control
Message Protocol (ICMPv6) echo request to a remote host that reports errors and
provides information relevant to IP packet addressing.
Use the ping6 command, in all modes except User EXEC, to check host reachability
and network connectivity or to confirm basic network connectivity
MOT:7A#ping6 <A:B:C:D:E:F:G:H>
where:
A:B:C:D:E:F:G:H is the destination IPv6 address.
where:
1-255 is the loopback interface number for the master cable bundle.
2. Use the ipv6 address command, in Interface Configuration mode, to define an
IPv6 address for the loopback interface:
MOT:7A(config-if)#ipv6 address <A:B:C:D:E:F:G:H/1-128>
where:
A:B:C:D:E:F:G:H/1-128 is the IPv6 address/Prefix Length.
10-14
Release 6.2.0
Configuring IPv6
where:
A:B:C:D:E:F:G:H/1-128 is the IPv6 address/Prefix Length.
secondary designates the IPv6 address as a secondary IPv6 address.
4. Use the show running-config command to make sure that DHCP relay is enabled
on the master cable loopback interface. Check the command output to see if the
IP v6helper address or cable helper address is assigned to the master cable
loopback interface.
If the IPv6 helper address or cable helper address is not assigned to the master
cable loopback address, use the ip helper-address or cable ipv6 helper-address
commands, in Interface configuration mode, to enable DHCP relay. The ipv6
helper-address or cable ipv6 helper address specifies the DHCP server.
5. Use the show interfaces loopback command to determine if an IP address is
assigned to the master cable loopback interface:
MOT:7A(config-if)#show interfaces loopback <1-255>
where:
1-255 is the loopback interface number.
If the master cable loopback interface does not have IPv6 address, use the ipv6
address command to specify the master cable loopback interface IP address.
6. Use the cable bundle master command in Interface Configuration mode to
assign the loopback interface as the master cable interface and assign the bundle a
number:
MOT:7A(config-if)#cable bundle <0-255> [master]
where:
0-255 is the number of the cable bundle identifier.
7. Use the end command in Interface Configuration mode to exit the master cable
interface.
10-15
Release 6.2.0
8. Use the show interfaces cable command to make sure that the slave cable
interface does not have an IP address assigned to it:
MOT:7A(config)#show interfaces cable <X/Y>
where:
X/Y is the slot and MAC Domain number of the CMTS module:
9. Use the show running-config command verify your cable bundle configuration
for each loopback interface.
10. Use the show cable bundle command to display a particular cable bundle or the
show cable bundle 0 command to display all configured cable bundles.
Refer to Chapter 3 to see an example of typical screen output for the show ipv6 dhcp
command.
loopback <1-255>]
where:
cable X/Y is the cable interface slot and MAC domain number.
ethernet X/Y is the Ethernet interface slot and port number.
gigaether X/Y is the Gigabit Ethernet interface slot and port number.
loopback 1-255 is the loopback interface number.
Refer to Chapter 3 to see an example of typical screen output for the show ipv6
interface command.
10-16
Release 6.2.0
Configuring IPv6
where:
A:B:C:D:E:F:G:H the IPv6 address of the neighbor entry.
cable X/Y is the cable interface slot and MAC domain number.
ethernet X/Y is the Ethernet interface slot and port number.
gigaether X/Y is the Gigabit Ethernet interface slot and port number.
loopback 1-255 is the loopback interface number.
Refer to Chapter 3 to see an example of typical screen output for the show ipv6
neighbor command.
10-17
Release 6.2.0
where:
A:B:C:D:E:F:G:H is the destination IPv6 Address.
A:B:C:D:E:F:G:H/ 1-128 is the IPv6 address/Prefix Length.
connected displays connected routes.
static displays static routes.
summary displays a summary of routes in the IPv6 routing table.
Refer to Chapter 3 to see an example of typical screen output for the show ipv6 route
command
where:
detail displays detailed statistical information.
Refer to Chapter 3 to see an example of typical screen output for the show ipv6
traffic command.
10-18
Release 6.2.0
Configuring IPv6
where:
A:B:C:D:E:F:G:H is the IPv6 address of the neighbor cache entry.
A:B:C:D:E:F:G:H is the Link Local address of the neighbor cache entry.
10-19
Index
A
adding
ARP cache entry, 3-2
permanent ARP entry, 3-2
Address Resolution Protocol
configuring, 3-2
addresses
Ethernet, 3-2
Internet, 3-2
MAC, 3-2
ARP
configuring, 3-2
ARP cache
adding entry, 3-2
ARP entry
adding permanent, 3-2
ARP table information
displaying, 3-15
B
broadcast address
scheme, 3-4
C
chassis information, 1-25
clear ip route, 3-14
clearing
buffer, 2-10
routing table entry, 3-7
commands
router ospf process-id, 7-19, 7-20, 7-21, 7-24,
7-25
configuring
console logging, 2-8
FTP access, 6-10
console logging
configuring, 2-8
D
datagram
fragmentation, 3-1
packet format, 3-1
reassembly, 3-1
routing to remote host, 3-1
broadcast packets
directed, 3-4
flooded, 3-4
limited, 3-4
default route
setting, 3-6
broadcast storms
avoiding, 3-4
buffer
clearing, 2-10
default router
definition, 3-6
displaying
ARP table information, 3-15
IP interface state, 3-15, 4-15
routing table status, 3-16
Index-1
static routes
status, 3-16
Release 6.2.0
L
limited broadcast packets, 3-4
E1 clock, 7-9
enabling
ICMP netmask reply, 3-11
Ethernet
auto-negotiation, 4-5
fragmentation, 3-5
FTP
access
configuring, 6-10
P
Primary CMTS Module, 7-7
generating
ICMP unreachable messages, 3-11
H
Host-to-Host Transport layer, 3-1
reducing
routing table size, 3-6
Remote Authentication Dial In User Service
(RADIUS)
configuring, 5-1 to 5-6
remote hosts, 3-1
I
ICMP, 3-8
ICMP echo request packets
sending, 3-11
ICMP netmask reply
enabling, 3-11
ICMP unreachable messages
generating, 3-11
Internet address, 3-2
Internet Control Message Protocol, 3-8
IP
packet, 3-1
IP interface state
displaying, 3-15, 4-15
Index-2
route
configuring, 3-6
setting specific, 3-6
specifying, 3-6
router discovery packets
tracing, 3-8
Router Discovery Protocol, 3-8
routing
datagram
to remote host, 3-1
routing table
information, 3-2
status
displaying, 3-16
routing table entry
Release 6.2.0
Index
clearing, 3-7
S
Secure Shell server (SSH)
configuring, 5-7 to ??
security access
system, 1-7
sending
ICMP echo request packets, 3-11
setting
default route, 3-6
optional packet count, 3-11
specific route, 3-6
SONET
deriving network clocking from, 7-9
SRM Redundancy, 7-1
Standby CMTS Resource Module, 7-7
static routes
status
displaying, 3-16
Stratum 3 clock, 7-9
system
login
account, 1-7
security access, 1-7
system information, 1-26
T
T1 clock, 7-9
telnet
access, 1-3
configuration of, 1-11
password configuration, 1-5
RADIUS authentication, 5-4
tracing
router discovery packets, 3-8
V
VoIP calls, 7-9
Index-3