Page 1 BSR 2000 Configuration and Management Guide 526360-001-00 Rev. B Release 1.0 MGBI...
Page 2 (such as translation, transformation or adaptation) without written permission from Motorola, Inc. Motorola reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Motorola to provide notification of such revision or change. Motorola provides this guide without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
Page 3 Caring for the Environment by Recycling When you see this symbol on a Motorola product, do not dispose of the product with residential or commercial waste. Recycling your Motorola Equipment Please do not dispose of this product with your residential or commercial waste. Some countries or regions, such as the European Union, have set up systems to collect and recycle electrical and electronic waste items.
Page 4 Motorola Kundeservice. Milieubewust recycleren Als u dit symbool op een Motorola-product ziet, gooi het dan niet bij het huishoudelijk afval of het bedrijfsafval. Uw Motorola-materiaal recycleren. Gooi dit product niet bij het huishoudelijk afval het of bedrijfsafval. In sommige landen of regio's zoals de Eu- ropese Unie, zijn er bepaalde systemen om elektrische of elektronische afvalproducten in te zamelen en te recycleren.
Page 5 Motorolas kundtjänst för hjälp. Újrahasznosítással a környezet védelméért Ha ezt a jelzést látja egy Motorola terméken, ne dobja ki azt lakossági vagy ipari hulladékba. Motorola termékének újrahasznosítása Kérjük ne dobja ki ezt a terméket lakossági vagy ipari hulladékba. Egyes országok ill. régiók, mint az Európai Unió...
Page 6 Motorola Motorola Motorola Motorola Motorola Motorola Motorola Motorola Motorola...
Page 7: Table Of Contents
Contents Preface Scope ............................xxvii Audience...........................xxvii Documentation Set ........................xxvii Conventions..........................xxviii Notes, Cautions, Warnings ......................xxix If You Need Help........................xxx Introduction Overview .............................1-1 Multiservice Support ........................1-2 Network Management and Control .....................1-2 Using the Command Line Interface Overview .............................2-1 Using a Console Session to Access the CLI ................2-2 Using a Telnet Session to Access the CLI...................2-3 CLI Command Modes .........................2-3 User EXEC Mode......................2-4...
Page 8 BSR 2000 Configuration and Management Guide Release 1.0 IPSec Configuration Mode ....................2-7 Router Configuration Mode .....................2-7 Route Map Configuration Mode ..................2-7 Cable Spectrum Group Mode...................2-8 Command Mode Summary....................2-8 Editing and Navigating with the CLI ..................2-11 Moving the Cursor on the Command Line..............2-12 Partial Command Names ....................2-12...
Page 9 Release 1.0 Defining a Group Access Level ...............3-10 Verifying Your User Account Login Configuration.........3-10 Configuring Interfaces....................3-11 Specifying System Time Information................3-11 Controlling Telnet and Console Access ..................3-13 Configuring Logging.........................3-14 Flash and NVRAM Memory Management Guidelines..........3-15 Setting Logging Control ....................3-16 Restricting Logging Rates ....................3-17 Creating a Loopback Interface for Source SYSLOG IP Address ....3-19 Configuring System Logging ..................3-19 Configuring Logging to a SYSLOG Server.............3-19...
Page 10 BSR 2000 Configuration and Management Guide Release 1.0 Enabling Domain Lookup and Domain List ............3-34 Configuring SNTP......................3-35 Configuring UDP Broadcast Relay ................3-37 Configuring FTP Access ....................3-38 Configuring a Loopback Interface for TFTP Packets ............3-39 Enabling the RADIUS Client on the BSR..............3-40 Configuring the RADIUS Client for Server Communication......3-40...
Page 11 Release 1.0 Displaying System Parameters....................3-68 Displaying System Processing Information ..............3-68 Displaying System Memory Information...............3-72 Displaying the System Version Information..............3-73 Displaying System Buffer Information ................3-75 Displaying Hardware Information..................3-77 Configuring SNMP Overview .............................4-1 Configuring SNMP Server Parameters ..................4-1 Configuring SNMP Informs and Traps ..................4-8 Setting Trap Logging Control...................4-8 Configuring a Trap Destination..................4-9 Specifying the Destination IP Address ..............4-9...
Page 12 BSR 2000 Configuration and Management Guide Release 1.0 Associating Groups to MIB Views ..............4-31 Configuring an SNMP Context................4-31 Configuring Packet Size......................4-32 Monitoring SNMP........................4-32 Configuring Interfaces and TCP/IP Features Overview .............................5-1 About TCP/IP Level Features .....................5-2 Setting IP Interface Addresses ....................5-2 Removing an IP Address ....................5-6...
Page 13 Obtaining Detailed DOCSIS 2.0 Information..........6-22 DOCSIS 2.0 and the BSR 2000..................6-22 BSR 2000 Hardware Support for DOCSIS 2.0..........6-22 BSR 2000 Software Support for DOCSIS 2.0 ..........6-23 DOCSIS 2.0 Logical Channel Configuration Task Summary........6-24 Configuring the Channel Type ..................6-24 Configuring Spectrum Power Density Maintenance for a Logical Channel....6-27 Additional S-CDMA Logical Channel Configurations ..........6-27...
Page 14 Configuring S-CDMA Codes Per Minislot............6-28 Configuring the S-CDMA Hopping Seed ............6-29 Configuring the S-CDMA Spreading Interval ..........6-29 Displaying the Upstream Logical Channel Configuration ..........6-29 Using the RF Sentry on the BSR 2000..................6-32 Power Level Measurement......................6-32 Configuring FFT......................6-33 Configuring the FFT Processor ..................6-33 Displaying the FFT Processor Configuration..............6-33...
Page 15 Release 1.0 Setting the Downstream Power Level..............6-50 Resetting a Downstream Port................6-50 Reserving Downstream Bandwidth ..............6-51 Unreserving Downstream Bandwidth ..............6-51 Cable Modem Downstream Frequency Override During Ranging ....6-52 Testing RF Carrier Modulation ................6-52 Specifying Downstream Queue Thresholds.............6-53 Limiting Downstream Multicast Traffic ............6-53 Configuring an Upstream Channel....................6-54 Initial Upstream Configuration Tasks ................6-55 Setting the Upstream Frequency ..............6-56...
Page 16 BSR 2000 Configuration and Management Guide Release 1.0 Disabling an Upstream Port ................6-81 Configuring the Upstream Channel Descriptor ..........6-81 Limiting the Number of Voice Calls on an Upstream Channel .......6-82 Enabling/Disabling CMTS Concatenation Capabilities ........6-83 Enabling/Disabling Concatenation for DOCSIS 1.0 or 1.1 Cable Modems ..6-83 Configuring AntiVirus/AntiWorm Protection ................6-84...
Page 17 Displaying Upstream Service Flow Statistics ..........6-128 Displaying Payload Header Suppression Entries...........6-128 Displaying Class of Service (Qos) Profiles............6-129 Configuring the BSR 2000 for DOCSIS 1.0+ Interoperability ........6-131 Verifying that DOCSIS 1.0+ Devices Successfully Register......6-134 Troubleshooting DOCSIS 1.0+ Interoperability ..........6-134 Implementing Spectrum Management ..................6-134 Configuring a Spectrum Group ..................6-135...
Page 18 BSR 2000 Configuration and Management Guide Release 1.0 Configuring the Spectrum Hopping Error Threshold ........6-147 Configuring the Spectrum Hopping Flap Threshold........6-148 Enabling and Disabling Spectrum Roll-back..........6-149 Configuring the Guard Band................6-149 Reviewing the Spectrum Group that You Created .........6-149 Viewing Your Spectrum Group Configuration ..........6-152 Applying a Spectrum Group to an Upstream Port............6-152...
Page 19 Release 1.0 Clearing UCC or DCC Statistics ..................6-184 Configuring Cable Intercepts ....................6-184 Enabling a Cable Intercept ...................6-184 Disabling a Cable Intercept ..................6-187 Gathering DOCSIS Network Information................6-188 Determining the Enabled DOCSIS CMTS Module Type ..........6-188 Through SNMP: .....................6-188 Through the CLI: ...................6-189 Displaying Cable Interface Parameters ................6-189 Displaying Downstream Parameters ................6-191 Viewing Downstream Port Information ............6-191...
Page 20 BSR 2000 Configuration and Management Guide Release 1.0 Configuring the COPS Client Timer..............7-7 Displaying COPS Connections ................7-8 Verifying the COPS Configuration ..............7-9 Configuring Event Messages....................7-9 Enabling the Event Message System ..............7-9 Configuring Event Message Parameters ............7-10 Configuring a Mask for Disabling Event Messages ........7-13 Disabling Event Messages ................7-15...
Page 21 Release 1.0 Configuring Routing Policy Overview .............................8-1 Defining Route Maps ........................8-2 Creating a Route Map.......................8-2 Using Match Statements to Define Routing Conditions ..........8-2 Using Set Statements to Define Routing Conditions ............8-4 Defining Access Lists and Groups ....................8-6 Configuring an IP Access List..................8-6 Configuring an AS-path Access-list.................8-7 Configuring an IP Access Group..................8-8 Creating Community Lists ......................8-8...
Page 22 BSR 2000 Configuration and Management Guide Release 1.0 Adjusting PIM Query Message Interval for DR...............9-8 Configuring the Type of PIM Packet Checksum..............9-8 Retrieving PIM Unicast Routes..................9-8 Configuring IGMP on an Interface .....................9-8 About IGMP ........................9-9 Enabling IGMP.......................9-10 Controlling Access to IP Multicast Groups..............9-10 Changing the IGMP Version ..................9-10...
Page 23 Release 1.0 Enabling RIP Authentication ....................10-7 Configuring Interpacket Delay....................10-7 Configuring Timers ........................10-8 Example ......................10-8 Configuring a Passive Interface for RIP ...................10-9 Redistributing Routes into RIP ....................10-9 Assigning a Default Metric Value for Redistributed Routes ........10-11 Gathering RIP Information......................10-11 Configuring OSPF Overview ...........................11-1 Specifications .........................11-2 Enabling OSPF..........................
Page 24 BSR 2000 Configuration and Management Guide Release 1.0 Displaying Network Information ..............11-22 Displaying Neighboring Routers ..............11-23 Displaying Virtual Links ................11-24 Displaying OSPF Interface Information...............11-24 Displaying OSPF Memory Information ...............11-25 Displaying OSPF Database Information ..............11-26 Configuring BGP Overview ...........................12-1 About BGP ..........................12-2 BGP Peers........................12-4...
Page 25 Release 1.0 Enabling and Disabling Synchronization ..............12-26 Configuring BGP Administrative Weights..............12-28 Using a Route Map ..................12-30 Using an AS Path Access List................12-30 Adjusting BGP Timers ....................12-31 Setting the Administrative Distance for a Route............12-32 Disabling Route Summarization...................12-33 Configuring Aggregate Addresses ................12-35 Assigning an Interface to BGP Session................12-37 Configuring a Default Route ..................12-38 Configuring BGP Update Flows .....................12-40...
Page 26 BSR 2000 Configuration and Management Guide Release 1.0 Configuring VLAN Stacking on a Bridging Cable Modem...........13-9 Enabling VLAN Stacking through an Enhanced Bridge Mode TLV....13-9 Enabling VLAN Stacking through the CLI ...........13-10 Configuring VLAN Tagged Routing..................13-11 Configuring the External L2/L3 Switch..................13-12 Bridging Packet Sizes......................13-13...
Page 27: Preface
BSR 2000 Configuration and Management Guide This document provides the instructions and procedures for configuring and managing the BSR 2000. BSR 2000 Installation Guide This document describes how to install the BSR 2000 HD product. 526360-001-00 Rev. B MGBI xxvii...
Page 28: Conventions
BSR 2000 Configuration and Management Guide Release 1.0 BSR 2000 Release Notes These documents provide information about features not described or incorrectly documented in the main documentation set; known problems and anomalies; product limitations; and problem resolutions. BSR 2000 SNMP MIB Reference Guide This document describes the Simple Network Management Protocol (SNMP) MIBs;...
Page 29: Notes, Cautions, Warnings
Release 1.0 Preface Convention Example Explanation This font indicates system output. screen display Wed May 6 17:01:03 2000 vertical bar | page {on | off} A vertical bar separates the choices when a parameter is required. The example indicates you can enter either command: page on or page off When entering the parameter, do not type the vertical bar or the brace brackets.
Page 30: If You Need Help
Outside the U.S. +1-215-323-0044 Motorola Online http://businessonline.motorola.com The TRC is on call 24 hours a day, 7 days a week. In addition, Motorola Online offers a searchable solutions database, technical documentation, and low-priority issue creation and tracking. MGBI 526360-001-00 Rev. B...
Page 31: Introduction
Introduction Overview The BSR 2000™ system gives broadband carriers a competitive edge for defining, deploying, and managing broadband services. Based on Data Over Cable Service Interface Specification (DOCSIS) and PacketCable standards, the BSR carrier-class solution allows Multiple System Operators (MSOs) to offer innovative differentiated data, voice, and multimedia services.
Page 32: Multiservice Support
BSR 2000 Configuration and Management Guide Release 1.0 Centralized routing and distributed forwarding provide simple configuration, scalable performance, and low cost. Deployed in a distribution hub, the BSR provides an interchange point between the regional fiber network and the cable plant. In a regional headend, it interconnects the regional network with a backbone network and allows connectivity to local content servers and management systems.
Page 33: Using The Command Line Interface
The CLI is used to perform basic management tasks and to configure protocols and physical layer interfaces for the BSR. For detailed information on CLI commands, refer to the BSR 2000 Command Reference Guide. This chapter discusses the following topics:...
Page 34: Using A Console Session To Access The Cli
BSR 2000 Configuration and Management Guide Release 1.0 Using a Console Session to Access the CLI This section describes accessing the CLI by connecting a terminal or PC with terminal emulation software to the BSR’s console port. The BSR supports one CLI session through its console port.
Page 35: Using A Telnet Session To Access The Cli
Release 1.0 Using the Command Line Interface Using a Telnet Session to Access the CLI This section describes accessing the CLI by establishing a telnet session to the BSR. Note: If an IP address has not been configured for the Ethernet interface and a password has not been configured for the BSR, you can not access the BSR through telnet.
Page 36: User Exec Mode
BSR 2000 Configuration and Management Guide Release 1.0 • User EXEC Mode • Privileged EXEC Mode Configuration command line interface modes allow you to make changes to the BSR’s running configuration. The configuration modes are as follows: • Global Configuration Mode •...
Page 37: Privileged Exec Mode
Release 1.0 Using the Command Line Interface Privileged EXEC Mode Privileged EXEC mode includes the commands in User EXEC mode, additional system configuration commands, and the configure command, which serves as a gateway to access the remaining command modes and high-level testing commands, such as debugging commands.
Page 38: Interface Configuration Mode
BSR 2000 Configuration and Management Guide Release 1.0 Interface Configuration Mode Interface Configuration commands modify the operation of an interface, such as an Ethernet port, and allow you to enable features on a per-interface basis. Interface Configuration mode is available for cable, Ethernet, GigaEthernet, and loopback interface types.
Page 39: Ipsec Configuration Mode
Release 1.0 Using the Command Line Interface To exit PacketCable Configuration mode and return to Global Configuration mode, enter the exit or end commands. To exit PacketCable Configuration mode and return to Privileged EXEC mode, press Ctrl-Z. IPSec Configuration Mode IPSec (IP Security) Configuration mode is used to configure a security policy that protects network traffic between two IPSec peers.
Page 40: Cable Spectrum Group Mode
BSR 2000 Configuration and Management Guide Release 1.0 To exit Route-map Configuration mode and return to Global Configuration mode, enter the exit or end commands. To exit Route-map Configuration mode and return to Privileged EXEC mode, press Ctrl-Z. Cable Spectrum Group Mode The spectrum management system monitors the upstream signal integrity, and collects upstream spectrum information.
Page 41 Release 1.0 Using the Command Line Interface Table 2-2 Command Mode Access, Prompt, and Exit Details Mode Access Name Means Prompt Display Exit Means User EXEC Console or Telnet To exit the CLI, MOT> enter the logout or exit commands. To enter Privileged EXEC mode, enter the...
Page 42 BSR 2000 Configuration and Management Guide Release 1.0 Table 2-2 Command Mode Access, Prompt, and Exit Details Mode Access Name Means Prompt Display Exit Means Interface From Global To return to MOT(config-if)# Configuration Configuration Global mode, enter the Configuration interface mode, enter the command.
Page 43: Editing And Navigating With The Cli
Release 1.0 Using the Command Line Interface Table 2-2 Command Mode Access, Prompt, and Exit Details Mode Access Name Means Prompt Display Exit Means PacketCable From Global To return to MOT(config-pktcable)# Configuration Configuration Global mode, enter the Configuration packet-cable mode, enter the command.
Page 44: Moving The Cursor On The Command Line
BSR 2000 Configuration and Management Guide Release 1.0 Moving the Cursor on the Command Line Table 2-3 describes the key sequences to move the cursor on the command line to make corrections or changes, or scroll back to the beginning of the command line.
Page 45: Deleting Command Line Entries
Release 1.0 Using the Command Line Interface Deleting Command Line Entries Table 2-4 describes the key sequences to delete command entries. Table 2-4 Deletion Keys Press ... Function Backspace key Erases the character to the left of the cursor. Ctrl-W Deletes the word to the left of the cursor.
Page 46: Disabling And Resetting Commands
BSR 2000 Configuration and Management Guide Release 1.0 Disabling and Resetting Commands The no form of a command disables the command or resets the command to the default value. The command without the keyword no re-enables a disabled feature or enables a feature that is disabled by default.
Page 47: Using The Command History
Release 1.0 Using the Command Line Interface WORD is the alias name for the command The alias is removed for the associated command. The show aliases command displays a list of all aliases: MOT# show aliases Alias Examples The following example creates an alias for the enable command, accessible from the Privileged EXEC mode.
Page 48: Disabling The Command History Feature
BSR 2000 Configuration and Management Guide Release 1.0 Press Ctrl-P or the up arrow key - Use this action to recall commands, displaying the most recent command first. Repeat the key sequence to display successively older commands.The up arrow key displays the most recent commands on the current CLI command mode.
Page 49: Getting Help
Release 1.0 Using the Command Line Interface If the <WORD> to be matched has more than one space character in a row, then the entire text string must be surrounded by quotation marks and any imbedded space characters in the string to be matched must be included as part of the <WORD>.
Page 51: Configuring The System
This chapter describes the initial configuration procedures necessary to configure the BSR 2000™ system using its command line interface (CLI). For further information on the CLI commands described in this chapter, refer to the BSR 2000 Command Reference Guide. This chapter discusses the following topics:...
Page 52: Initial Configuration Tasks
BSR 2000 Configuration and Management Guide Release 1.0 Initial Configuration Tasks This section describes the initial basic configuration tasks for configuring the BSR: Gathering Network Information Required Servers Accessing the CLI to Set System Passwords Specifying a Host Name Configuring User Login Accounts...
Page 53: Accessing The Cli To Set System Passwords
Note: Make sure that the serial cable is connected properly and the terminal application is configured correctly. Refer to the BSR 2000 Installation Guide for more information. 1. Start your terminal or terminal application to connect to the BSR. Refer to...
Page 54: Setting System Passwords
BSR 2000 Configuration and Management Guide Release 1.0 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...
Page 55 Release 1.0 Configuring the System 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: MOT(config)# no service password-encryption Note: The no service password-encryption command does not unencrypt passwords that are already encrypted.
Page 56: Specifying A Host Name
BSR 2000 Configuration and Management Guide Release 1.0 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 in Privileged EXEC mode to verify that the...
Page 57: Configuring User Login Accounts
Release 1.0 Configuring the System MOT(config)# hostname <WORD> where: WORD is the new system network name. After you execute this command, the Command Line Interface (CLI) prompt changes to the new host name: newhostname(config)# Configuring User Login Accounts Define a unique system login account for each user requiring access to the command line interface.
Page 58: Defining A User Name Without A Password
BSR 2000 Configuration and Management Guide Release 1.0 Table 3-1 User Login Account Parameters Parameter Description privilege Defines user account privileges. Read-only privileges allow a user access to the Privileged EXEC command line mode only. Read-write privileges allow a user access to all command...
Page 59: Defining A User Name With An Encrypted Password
Release 1.0 Configuring the System Defining a User Name with an Encrypted Password Follow these steps to define a user account that is encrypted: 1. Use the username password command in Global Configuration mode to define a password for a user account that is encrypted: MOT (config)#username <WORD>...
Page 60: Defining A Group Access Level
BSR 2000 Configuration and Management Guide Release 1.0 For example: MOT (config)#username newuser privilege rw Defining a Group Access Level To define a group access level for a user account, use the following command in Global Configuration mode: MOT (config)#username <WORD> user-group {isp <1-1> | mso | sysadmin}...
Page 61: Configuring Interfaces
Release 1.0 Configuring the System 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...
Page 62 BSR 2000 Configuration and Management Guide Release 1.0 2. Enter the end command to return to Privileged EXEC mode to set the system clock and enter the clock set command: MOT #clock set <hh:mm:ss> <1-31> <MONTH> <2000-2035> where: hh:mm:ss is the hour, minute, and second in hh:mm:ss format.
Page 63: Controlling Telnet And Console Access
Release 1.0 Configuring the System Controlling Telnet and Console Access Follow these steps to configure telnet and console access to the BSR: 1. The default time-out value for a telnet session is five minutes. Use the session-timeout telnet command in Global Configuration mode to configure the amount of time (retroactively) that telnet sessions can stay connected to the BSR: MOT(config)# session-timeout telnet <0-30>...
Page 64: Configuring Logging
BSR 2000 Configuration and Management Guide Release 1.0 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: Note: Setting the session-limit to "0"...
Page 65: Flash And Nvram Memory Management Guidelines
Release 1.0 Configuring the System 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 3-17). 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 3-25).
Page 66: Setting Logging Control
BSR 2000 Configuration and Management Guide Release 1.0 The Flash log file can be much larger than the docsDevEventTable and has a maximum size that is configurable with the logging buffered command. If the Flash log file’s maximum size is smaller than the equivalent of 100 log entries, then the docsDevEventTable would reflect the size of the Flash log file.
Page 67: Restricting Logging Rates
Release 1.0 Configuring the System Table 3-3 CLI Logging Default Destination/Severity Levels trap disabled SYSLOG disabled Table 3-4 DOCSIS Logging Default Destination/Severity Levels Destination Default Severity Level console disabled log buffer (local) notice or higher trap notice, warning, error, critical SYSLOG notice, warning, error, critical Restricting Logging Rates...
Page 68 BSR 2000 Configuration and Management Guide Release 1.0 The following example indicates that the rate-limit on logged messages is 10 messages per second: MOT (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.
Page 69: Creating A Loopback Interface For Source Syslog Ip Address
Release 1.0 Configuring the System Creating a Loopback Interface for Source SYSLOG IP Address The logging source-interface loopback command allows an operator to control the source IP address of SYSLOG packets generated by the BSR by specifying a loopback interface as the source IP address for SYSLOG packets. The normal convention for generated SYSLOG packets is to set the source IP address equal to the IP address of the outgoing interface.
Page 70 BSR 2000 Configuration and Management Guide Release 1.0 A.B.C.D is the IP address of the SYSLOG server For example: MOT (config )# logging 10.10.10.53 2. Specify the logging facility with the logging facility command in Global Configuration mode: MOT (config )# logging facility {local0 | local1 | local2 | local3 | local4 | local5...
Page 71: Configuring Console Logging
Release 1.0 Configuring the System The following example configure the SYSLOG server to log all messages from warnings (severity level 4) up to emergencies (severity level 0): MOT (config )# logging trap warnings MOT (config )# logging snmp-trap warnings 4. Enable logging with the logging on command. MOT (config )# logging on 5.
Page 72: Configuring The Logging Buffer
BSR 2000 Configuration and Management Guide Release 1.0 3. Verify the console logging configuration with the show running-config command in all modes except User EXEC: MOT (config )# show running-config | inc logg Configuring the Logging Buffer Buffering is used to provide space on the BSR’s internal buffer or on the SYSLOG server for the latest log messages.
Page 73: Configuring Logging Reports
Release 1.0 Configuring the System 4. Use the show log command in Privileged EXEC or Global Configuration mode to see messages logged in the internal buffer. The oldest message is displayed first. Clearing the Logging Buffer 1. Clear the logging buffer with the clear log command in all modes except User EXEC: MOT #clear log 2.
Page 74 BSR 2000 Configuration and Management Guide Release 1.0 local log all messages to local-nonvolatile memory (NVRAM) 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...
Page 75: Configuring Evt Logging
Release 1.0 Configuring the System Configuring EVT Logging The EVT system is an enhancement to the BSR logging mechanism that provides the ability to monitor internal system events. This allows for additional granularity in monitoring system activity. As EVT monitored events occur, they can be logged in a similar manner as the existing BSR logging mechanism although the configuration procedure for EVT logging is different.
Page 76: Evt Logging Default Configurations
BSR 2000 Configuration and Management Guide Release 1.0 This section describes how to configure EVT logging parameters. The tasks for configuring EVT logging include the following: Configuring EVT Logging Displaying EVT Counts Clearing EVT Counts Disabling EVT Logging Restoring EVT Default Logging Configurations EVT Logging Default Configurations Each individual EVT has a “logging flags”...
Page 77 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 always 0 for the BSR 2000. group is an optional name of an EVT group.
Page 78: Displaying Evt Counts
BSR 2000 Configuration and Management Guide Release 1.0 removes all previous logging evt set configurations. MOT (config)# no logging evt removes all previous logging evt set and logging evt clear configurations. Displaying the EVT Configuration Use the following commands to display EVT configuration information:...
Page 79: Restoring Evt Default Logging Configurations
Release 1.0 Configuring the System Restoring EVT Default Logging Configurations The following no logging evt clear command options restore the EVT default logging configurations: MOT (config)# no logging evt clear [<slot:group>] [<range>] 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.
Page 80: Disabling The Bpi Authorization Reject Message
BSR 2000 Configuration and Management Guide Release 1.0 Disabling the BPI Authorization Reject Message Use the logging disable bpi_auth_reject_messages command in Global Configuration mode to disable the logging of extraneous "BPI authorization reject" DOCSIS error messages. The no logging disable bpi_auth_reject_messages enables the logging of this error message.
Page 81: Sending Messages To Bsr Users
Release 1.0 Configuring the System logging facility local7 Sending Messages to BSR Users Use the following commands to send messages to BSR users: Use the broadcast command to broadcast a message to all connected users at any given moment, as shown in Privileged EXEC mode: MOT# broadcast <WORD>...
Page 82: Configuring Dhcp Relay
BSR 2000 Configuration and Management Guide Release 1.0 Configuring UDP Broadcast Relay Configuring FTP Access Configuring a Loopback Interface for TFTP Packets Enabling the RADIUS Client on the BSR Configuring Secure Shell Server Security Configuring TACACS+ Configuring DHCP Relay This section describes how to configure the BSR to forward UDP broadcasts, including IP address requests, from Dynamic Host Configuration Protocol (DHCP) clients.
Page 83: Configuring Dns
MOT# 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:...
Page 84: Configuring The Domain Name
BSR 2000 Configuration and Management Guide Release 1.0 Configuring the Domain Name For each BSR, you should configure the name of the domain in which the BSR is located. This is the default domain name that is appended to host names that are not fully qualified.
Page 85: Configuring Sntp
It then binds to the first server that replies. All subsequent transactions happen in unicast mode. For example: MOT (config)#sntp server 192.168.1.253 MOT (config)#sntp server sntpd.motorola.com 2. Authenticate SNTP time sources with the sntp authenticate command in Global Configuration mode. 526360-001-00 Rev. B...
Page 86 BSR 2000 Configuration and Management Guide Release 1.0 MOT (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.
Page 87: Configuring Udp Broadcast Relay
Release 1.0 Configuring the System 7. To display information about SNTP, use the show sntp command in Privileged EXEC mode. MOT #show sntp 8. Verify that the information was entered correctly by displaying the running configuration. MOT# show running-config Configuring UDP Broadcast Relay Network hosts occasionally employ UDP broadcasts to determine address, configuration, and name information.
Page 88: Configuring Ftp Access
BSR 2000 Configuration and Management Guide Release 1.0 You can forward the following protocols: For example: MOT (config)#ip forward-protocol udp 35 2. Enter the cable interface from Global Configuration mode. MOT (config)#interface cable <X/Y> where: X is 0. Y is the cable port number.
Page 89: Configuring A Loopback Interface For Tftp Packets
Release 1.0 Configuring the System MOT (config)#ip ftp username <WORD> 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.
Page 90: Enabling The Radius Client On The Bsr
BSR 2000. The BSR 2000 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 2000.
Page 91 Release 1.0 Configuring the System 0-65535 is the optionally defined UDP port for the RADIUS authentication server. The default port is 1812. cr is a command return that configures the RADIUS server host without a UDP port designation. 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: Note: It is recommended that the authentication key text string be more than...
Page 92: Configuring A Loopback Interface For Radius Packets
Configuring RADIUS Client Access Before you configure RADIUS client access parameters, ensure that user password parameters are configured on the BSR 2000 and the RADIUS server. Refer to Accessing the CLI to Set System Passwords on page 3-3 for more information.
Page 93 Release 1.0 Configuring the System 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.
Page 94: Viewing Radius Client Statistics
BSR 2000 Configuration and Management Guide Release 1.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.
Page 95: Enabling Ssh
1. Host keys are required for the SSH Server and can either be generated in the BSR 2000 or generated on another BSR 2000 and copied into the BSR 2000. Use the ssh-keygen2 tool in Privileged EXEC mode to generate authentication key files...
Page 96: Managing Ssh Parameters
BSR 2000 Configuration and Management Guide Release 1.0 3. Use the ssh enable command in Global Configuration mode to enable the SSH process: Note: The no ssh enable command disables the SSH process. If SSH is disabled, all existing SSH sessions will be terminated.
Page 97 Release 1.0 Configuring the System aes192-cbc is the AES with 192-bit keys. aes256-cbc is the AES with 256-bit keys. any attempts all possible Ciphers, none excluded. arcfour streams cipher with 128-bit keys. blowfish-cbc Blowfish in CBC mode, with 128-bit keys. cast128-cbc CAST cipher in cbc mode.
Page 98 BSR 2000 Configuration and Management Guide Release 1.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: Note: Specifying a value of "0" will disable time-out for SSH sessions.
Page 99: Viewing And Logging Out Ssh Sessions
Release 1.0 Configuring the System Viewing and Logging out SSH Sessions Follow these steps to view and log out SSH sessions: 1. The show users ssh command displays information about active SSH sessions including the username, user group and privilege level, the IP address of the show users ssh command in originating host, and the session ID.
Page 100: Configuring Tacacs
BSR 2000 Configuration and Management Guide Release 1.0 Table 3-5 describes the show ssh config command output field descriptions: Table 3-5 show ssh config Command Output Field Descriptions Output Field Description SSH2 Secure Shell The SSH version number. sshTaskId The task identifier for this SSH session.
Page 101: Configuring Tacacs+ Servers
Release 1.0 Configuring the System 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.
Page 102 BSR 2000 Configuration and Management Guide Release 1.0 Specifying a Global Retry Count - A global retry count is the number of command authentication attempts that all TACACS+ clients make with all TACACS+ server before going to the next configured/available TACACS+ server.
Page 103 Release 1.0 Configuring the System timeout 1-1000 specifies a timeout value in seconds for this TACACS+ server. The default value is 10. Note: Specifying timeout or key parameters with the tacacs-server host command overrides any global values entered with the tacacs-server key, tacacs-server...
Page 104 BSR 2000 Configuration and Management Guide Release 1.0 tacacs-server retry <0-100> (config)# 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. Specifying a Global Timeout Value...
Page 105: Enabling Aaa
Release 1.0 Configuring the System Use the ip tacacs source-interface loopback command, in Global Configuration mode, to configure an Ethernet interface, as follows MOT(config)# ip tacacs source-interface loopback <1-64> where: 1-64 is the loopback interface number 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.
Page 106: Configuring Aaa Authorization
BSR 2000 Configuration and Management Guide Release 1.0 Configuring Administrative Authentication Configuring AAA administrative authentication determines if a user can access privilege level 15 (system administrator) on the BSR by establishing one or more authentication methods that are invoked when an attempt is made to access this privilege level.
Page 107: Configuring Aaa Accounting
Release 1.0 Configuring the System Configuring Command Authorization Command authorization determines if a user is allowed to run commands at a specified privilege level. Use the aaa authorization commands default command, in Global Configuration mode, to configure command authorization, as follows: aaa authorization commands {exec | isp-ro | isp-rw | mso-ro | (config)# mso-rw | sysadmin} default {local | none | tacacs}...
Page 108 BSR 2000 Configuration and Management Guide Release 1.0 Configuring Terminal Session Accounting Configuring Command Use Accounting Configuring command use accounting provides resource usage data for commands used at a specified privilege level. Use the aaa accounting commands default command, in Global Configuration mode, to enable command use accounting, as...
Page 109: Displaying Tacacs+ Information
Release 1.0 Configuring the System tacacs uses TACACS+ as the accounting method. Configuring Terminal Session Accounting Configuring terminal session accounting provides resource usage data for a specified terminal session. Use the aaa accounting exec default command, in Global Configuration mode, to enable privilege level authorization, as follows: #aaa accounting exec {none | start-stop | stop-only | wait-start} (config) default {local | none | tacacs}...
Page 110: Clearing Tacacs+ Statistics
Upgrading BSR System Software Before You Download Software Follow these steps before downloading software to the BSR 2000: 1. Use the dir command in Privileged EXEC mode to ensure that you have enough memory space in Nonvolatile Random Access Memory (NVRAM) for the new...
Page 111 For example: MOT# delete nvram:image_file.bin ? [confirm] 4. In order to download files to the BSR 2000, 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: Check for the correct file names and ensure that these files are located in the proper directory on the FTP or TFTP server.
Page 112: Downloading Image Files To Nvram
WORD is the username configured on the FTP server 7. Ensure that the correct FTP password is configured on the BSR 2000 for communication with the FTP server. If the required FTP password is not displayed in the running configuration or is incorrect, use the ip ftp password command in Global Configuration mode as shown below: MOT(config)# ip ftp password <LINE>...
Page 113: Downloading Image Files To Flash Memory
Release 1.0 Configuring the System 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.
Page 114 FTP username and password are set correctly on the BSR 2000 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.
Page 115: Upgrading Bsr System Software
BSR system software (boot ROM, FPGA, and Application image, respectively) while the BSR is in operation. Caution: When upgrading and downgrading BSR 2000 boot ROM images and Application image, ensure that this is done through a console session only and only during a scheduled maintenance window.
Page 116: Upgrading The Boot Rom
BSR 2000 Configuration and Management Guide Release 1.0 Upgrading the Boot ROM Use the boot-update command to upgrade the boot ROM as follows: MOT #boot-update <prefix> <string> where: <prefix> is the server IP addess <string> is the boot image name.
Page 117: Saving And Viewing Your Configuration
Release 1.0 Configuring the System filename is the name of the operating image archive file, which contains the application image, boot image, and FPGA files from which to boot. For example: MOT#boot system NVRAM:image_file.Z Saving and Viewing Your Configuration Saving the current running configuration to nonvolatile random access memory (NVRAM) is done to prevent your current configuration from being lost the next time the BSR is rebooted.
Page 118: Displaying System Parameters
BSR 2000 Configuration and Management Guide Release 1.0 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.
Page 119 Release 1.0 Configuring the System All CPU accounting is approximate, there are 103 ticks per second NAME total % (ticks) delta % (ticks) -------- ------- ------------------ ------------------ tExcTask f7fc738 000.01%( 113) 000.00%( TaskMon 83544d8 000.00%( 000.00%( ctrlMon 8356ef8 000.00%( 000.00%( tWdbTask ad39c08 000.00%(...
Page 120 BSR 2000 Configuration and Management Guide Release 1.0 Use the show process command with the stack keyword in Privileged EXEC mode to display the size, current usage, and highest usage of each process stack: MOT# show process stack [procID | procName] where: procID is the task ID number in decimal or hexadecimal form.
Page 121 Release 1.0 Configuring the System MOT# show process cpu All CPU accounting is approximate, there are 503 ticks per second NAME total % (ticks) delta % (ticks) -------- ------- ------------------ ------------------ tExcTask fbfd9f8 000.00%( 000.00%( TaskMon eeaf558 000.00%( 000.00%( tShell eeea688 000.00%( 000.00%(...
Page 122: Displaying System Memory Information
BSR 2000 Configuration and Management Guide Release 1.0 Use the show process semaphores command in Privileged EXEC mode display information about the Semaphore ID number on which process is waiting: MOT# show process semaphores Figure 3-4 displays an example of the show process semaphores command...
Page 123: Displaying The System Version Information
Release 1.0 Configuring the System Figure 3-5 displays an example of the show memory information command output: FREE LIST: addr size --- ---------- ---------- 0x6ea6718 0x6ee8248 0x6ea67e0 0x6ee8d60 0x6ea6a10 0x6ea6960 Figure 3-5 show memory information Command Output Use the show memory command in Privileged EXEC mode to display the starting address where memory is dumped in hexadecimal notation: MOT# show memory <address>...
Page 124 BSR 2000 Configuration and Management Guide Release 1.0 Use the show version command in all modes except User EXEC mode to display specific BSR system software and hardware version information: MOT# show version [ | {begin | exclude | include} {<WORD>}] where: | turns on output modifiers (filters).
Page 125: Displaying System Buffer Information
3-6 displays typical show version command output, which presents the BSR system version information: BSR 2000(tm) version 1.0.0P16.TRAU Copyright (c) 2005 by Motorola. Compiled Wed Oct 26 13:57:24 EDT 2005 MPC7447A processor with 512MB memory.
Page 126 BSR 2000 Configuration and Management Guide Release 1.0 Statistics for pool: network number of FREE mbufs: 37030 number of mbufs: 38272 number of times failed to find space: number of times waited for space: number of times drained protocols for space: 0...
Page 127: Displaying Hardware Information
Displaying Hardware Information The show controllers command displays detailed hardware and configuration information for the BSR 2000. Use the show controllers cable command to display RF signal information, the type of CMTS hardware installed, FEC information for both corrected and...
Page 128 BSR 2000 Configuration and Management Guide Release 1.0 Figure 3-8 displays typical show controllers cable command output. Interface Cable 0/0 mac_part_id=3214, rev_id=A3 MAC regs base: BAR0=0x82000000, BAR1=0x82100000 Tx ring 0xB46CE00, Free head index: 506, Used head index: 506 Tx PD in use, MAC: 0, data: 0, passthrough 0...
Page 129 Release 1.0 Configuring the System Figure 3-9 displays typical controller information for the Ethernet interfaces on the BSR 2000: ethernet 0/0 is up, line protocol is up Hardware address is 00:30:b8:80:d9:31 Internet address is 192.168.110.2/24 MTU 1500 bytes, BW 100000 Kbits...
Page 131: Configuring Snmp
Configuring SNMP Overview This chapter describes the commands used to configure SNMP for managing the BSR 64000 system and monitoring the network using its command line interface. For further information on the CLI commands described in this chapter, refer to the BSR Command Reference Guide.
Page 132 BSR 2000 Configuration and Management Guide Release 1.0 1. Enter Global Configuration mode. MOT #configure 2. Type snmp-server followed by the available SNMP command and its associated parameters that are listed in Table 4-1: Table 4-1 snmp-server Commands Command Description...
Page 133 Release 1.0 Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server Set SNMP cmtsBPKMTrap docs-trap-control DOCSIS traps. configured cmtsBpiInitTrap cmtsDCCAckFailTrap cmtsDCCReqFailTrap cmtsDCCRspFailTrap cmtsDynServAckFailT ap cmtsDynServReqFailTrap cmtsDynServRspFailTrap cmtsDynamicSATrap cmtsInitRegAckFailTrap cmtsInitRegReqFailTrap cmtsInitRegRspFailTrap snmp-server enable Enable SNMP Traps, informs, or traps, informs, or coexistence configured...
Page 134 BSR 2000 Configuration and Management Guide Release 1.0 Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server notify Configure the 1. Specify the first RowStatus {<octet-string>} notification table. octet-string, which is active. {<octet-string>} [inform | specifies the notification trap] [nonvolatile | name.
Page 135 Release 1.0 Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server notify-filter Configure 1. Specify the first {<octet-string>} {<OID>} snmpNotifyFilter octet-string, which configured. {<octet-string> [included | table. specifies the excluded] [nonvolatile | snmpNotifyFilter table volatile] [active | profile name (index #1).
Page 136 BSR 2000 Configuration and Management Guide Release 1.0 Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server notify-filter Configures the 1. Specify the profile {<OID>} snmpNotifyFilter snmpNotifyFilter configured. {<octet-string> [included | subtree profile. subtree (index #2) OID, excluded] [nonvolatile |...
Page 137 Release 1.0 Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server shutdown Shuts down the Disabled SNMP Agent, thus preventing it from processing incoming SNMP packets, but retains all SNMP configuration data in the event the agent is restarted.
Page 138: Configuring Snmp Informs And Traps
BSR 2000 Configuration and Management Guide Release 1.0 Configuring SNMP Informs and Traps SNMP traps and informs are disabled by default. SNMP traps are generated according to standard and enterprise MIB specifications. The SNMP Agent maintains a configuration of IP hosts to which traps are sent. This section provides information...
Page 139: Configuring A Trap Destination
These tables can also be manipulated directly through the CLI. Refer to the BSR 2000 Command Reference Guide for detailed descriptions of the associated CLI commands. Note: Before to using the...
Page 140: Specifying Specific Trap Types
BSR 2000 Configuration and Management Guide Release 1.0 traps indicates enable SNMP traps. informs indicates enable SNMP informs. WORD is the SNMPv1/v2c community string or SNMPv3 user name. version indicates the version of notifications. If no version keyword is specified, the default is version 1.
Page 141: Specifying Snmp Trap Versions
Release 1.0 Configuring SNMP A.B.C.D is the IP address of the host WORD is the SNMPv1/v2c community string or SNMPv3 user name. udp-port 0-65535 is the UDP port number. bgp specifies BGP state change traps. docsdevcmts specifies DOCSIS device CMTS traps. entity specifies entity state change traps.
Page 142: Enabling Informs
BSR 2000 Configuration and Management Guide Release 1.0 Enabling Informs Use the snmp-server enable informs command in Global configuration mode to enable SNMP Informs: MOT (config)#snmp-server enable informs To disable informs, use the no snmp-server enable informs command. Note: For SNMP informs to be sent, you must also SNMP enable traps with the snmp-server enable traps command even if there are no hosts to which you are actually sending traps.
Page 143: Enabling Cmts Traps
Release 1.0 Configuring SNMP ospf enables OSPF state change traps. pim enables PIM state change traps. registration enables CM (de)registration traps snmp enables SNMP state change traps. Enabling CMTS Traps CMTS traps are enabled with the snmp-server docs-trap-control command in Global Configuration mode, as follows: MOT (config)#snmp-server docs-trap-control {cmtsBPKMTrap | cmtsBpiInitTrap | cmtsDCCAckFailTrap | cmtsDCCReqFailTrap |...
Page 144: Restricting Trap Rates
BSR 2000 Configuration and Management Guide Release 1.0 Table 4-2 CMTS Trap Definitions CMTS Trap Name Definition the failure of a dynamic service acknowledgement cmtsDynServAckFailTrap that happened during the dynamic services process and detected on the CMTS side the failure of a dynamic service request that...
Page 145: Disabling Traps
Release 1.0 Configuring SNMP where: 0-2147483647 is the number of SNMP traps. 0-2147483647 is the number of seconds during which the specified number of trap messages are logged. The following example sets a limit of 100 traps per second. MOT (config)#snmp-server trap rate-limit 100 1 To restrict the rate of SNMP traps in DOCSIS logging control mode, use the logging rate-limit command in Global configuration mode: MOT (config)#logging rate-limit <0-2147483647>...
Page 146: Configuring A Loopback Interface For An Snmp Trap Source
Global Configuration mode, as follows: MOT (config)#logging snmp-trap emergencies Refer to the BSR 2000 Command Reference Guide for detailed descriptions of these CLI commands. Configuring a Loopback Interface for an SNMP Trap Source The snmp-server trap-source loopback command allows an operator to control the source IP address of SNMP traps generated by the BSR by specifying a loopback interface as the source IP address for SNMP traps.
Page 147 Release 1.0 Configuring SNMP logging admin-status unconstrained logging snmp-trap warnings snmp-server community public rw snmp-server enable traps snmp-server host 150.31.1.180 traps version 1 public Example #2 SNMPv3 traps in proprietary logging control mode no logging control docsis logging admin-status maintainBelowThreshold logging snmp-trap warnings snmp-server engineid local 80001375030030b8022d0000 snmp-server user myuser eng-id 80001375030030b8022d0000...
Page 148 BSR 2000 Configuration and Management Guide Release 1.0 snmp-server host 150.21.2.61 traps version 3 noauth myuser udp-port 1500 snmp-server trap rate-limit 100 1 Example #3 SNMPv3 informs in DOCSIS logging control mode logging control docsis logging admin-status maintainBelowThreshold logging rate-limit 20 60 snmp-server engineid remote 150.31.1.180 udp-port 1596 8000052301961f01b4...
Page 149: Disabling Snmp
Release 1.0 Configuring SNMP snmp-server target-addr 0x01 150.31.1.190 udp-port 162 1500 3 myusertrap MYPARAM NULL 1400 nonvolatile active snmp-server target-params MYPARAM 3 3 myusertrap noauthnopriv nonvolatile active Disabling SNMP If you must disable the SNMP, use the snmp-server shutdown command in Global Configuration mode: MOT (config)#snmp-server shutdown Configuring SNMPv3...
Page 150 BSR 2000 Configuration and Management Guide Release 1.0 Local SNMP engine-ID: 0030b8008300000000000000 Note: The local SNMP Engine-ID is configured as b80042005959000000000000. If the agent is not running, you can enable it by entering any SNMP command in Global Configuration mode, such as defining a community string using the snmp-server community public command.
Page 151 Release 1.0 Configuring SNMP auth indicates the user authentication parameter. sha indicates the HMAC-SHA algorithm for authentication. md5 indicates the HMAC-MD5 algorithm for authentication. key <string> is the standard key. local <string> is the localized authentication key for user. password <string> is the assigned password; valid size is up to 64 characters.
Page 152 BSR 2000 Configuration and Management Guide Release 1.0 group-name is the name of the SNMP Group. mib-view-name is the name of the MIB view for the type of process. notify specifies a notify view for this access group. read specifies a read view for this access group.
Page 153 The example below uses the commands described above to specify sha_user as the user, sha as the authentication algorithm, and motorola as the password. It assigns the user to an SNMP Group auth_g and specifies that this user and group combination applies for SNMPv3 only.
Page 154: Configuring Snmp Server Identification
BSR 2000 Configuration and Management Guide Release 1.0 Configuring SNMP Server Identification Configuring the following parameters provides unique network identification for the SNMP Agent: Contact person System location Engine identifier Configuring System Contact Information Establish a system contact string using the snmp-server contact command in Global Configuration mode: MOT (config)#snmp-server contact <text>...
Page 155: Configuring Snmp Access Levels
Release 1.0 Configuring SNMP Note: Upon shipment, the agent has a default engineID that is equal to the chassis MAC address. where: engine-id is the local or remote SNMP Engine engineID. ip-address is the remote SNMP Engine IP address. port-num is the optional UDP port number. 2.
Page 156: Defining A Community Name
BSR 2000 Configuration and Management Guide Release 1.0 Figure 4-1 provides an overview of the SNMP access level configuration process and the SNMP version (v1, v2c, or v3) that supports each snmp-server command. Defining a Community Name The community name access method, used predominantly with SNMPv1 and...
Page 157 Release 1.0 Configuring SNMP snmp-server user user-name snmp-server community community-name Create Create Community User Model Name snmp-server group group-name user user-name snmp-server view view-name Create Create Associate Group User View Model Model snmp-server access group-name view-name snmp-server community community-name view-name Associate Associate MIB View...
Page 158: Configuring Usm And Vacm Security
BSR 2000 Configuration and Management Guide Release 1.0 2. Use the no snmp-server community command to remove the specified community string. Caution: Using only a community name to establish SNMP access levels is The community string is not a completely secure access control method.
Page 159: Configuring A Group Model
Release 1.0 Configuring SNMP 1. To configure a new SNMP User, use the snmp-server user command in Global Configuration mode. MOT (config)#snmp-server user <username> [auth {sha | md5} {password <password> | key <key> | local <localized_key>} [priv des56 {password <password> | key <key> | local <localized_key>}] [eng-id <engine-id>]] where: username is the new SNMP User.
Page 160: Configuring A Mib View
BSR 2000 Configuration and Management Guide Release 1.0 Configuring a MIB View You can assign MIB views to SNMP Groups or community strings to limit the MIB objects that an SNMP manager can access. You can use a predefined view or create your own view.
Page 161: Associating Groups To Mib Views
Release 1.0 Configuring SNMP Associating Groups to MIB Views You can associate an SNMP Group to specific SNMP MIB views. This restricts access to the MIB objects defined in the view to the SNMP Group, limiting which MIB objects an SNMP manager can access. Use the snmp-server access command in Global Configuration mode to map SNMP Groups to SNMP MIB views.
Page 162: Configuring Packet Size
BSR 2000 Configuration and Management Guide Release 1.0 Example The following example shows how to create a context to be used to further restrict access: (config)#snmp-server context mycontext Configuring Packet Size 1. Use the snmp-server packetsize command in Global Configuration mode to...
Page 163 Release 1.0 Configuring SNMP Table 4-3 show snmp Commands Command Description show snmp context Displays SNMP v3 context information. show snmp description Displays SNMP system description. show snmp engineID Displays local and remote engineIDs. show snmp group Display the names of the SNMP Groups, security names, security models, status of the different views, and storage type for each group.
Page 165: Configuring Interfaces And Tcp/Ip Features
Configuring Interfaces and TCP/IP Features Overview This chapter describes how to configure the various interfaces on the BSR and the Transmission Control Protocol/Internet Protocol (TCP/IP) features for the BSR 2000™ system. This chapter discusses the following topics: About TCP/IP Level Features Setting IP Interface Addresses Configuring a Loopback Interface Adding a Permanent ARP Entry and Timeout Value...
Page 166: About Tcp/Ip Level Features
BSR 2000 Configuration and Management Guide Release 1.0 Tracing a Route Managing the Router Gathering TCP/IP Related Information About TCP/IP Level Features 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.
Page 167 T1/E1 BITS Redundancy Port clock . The other, labeled RED, is a 10/100 Base-T Ethernet port for interconnectivity to another BSR 2000 for future redundancy implementation. cable DOCSIS 1:4 Ports CMTS that provides 1 downstream channel and 4 upstream channels.
Page 168 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config)# interface [ethernet | gigaether | cable] {<X/Y>} where: ethernet is any 10/100 Ethernet interface. gigaether is the Gigabit Ethernet interface cable is any DOCSIS interface. X is 0. Y is the port number.
Page 169 Release 1.0 Configuring Interfaces and TCP/IP Features 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.
Page 170: Removing An Ip Address
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-if)# show ip interface [ brief | ethernet<X/Y> | gigaether <X/ Y> | cable <X/Y>] where: brief displays summary information. ethernet is any 10 or 10/100 Ethernet interface. gigaether is the Gigabit Ethernet interface cable is any DOCSIS interface.
Page 171: Configuring Auto-Negotiation On The 10/100 Ethernet Module
Release 1.0 Configuring Interfaces and TCP/IP Features MOT(config-if)# no ip address Note: The primary IP address can be removed only after all of the secondary subnet addresses associated with the interface have been removed. Configuring Auto-Negotiation on the 10/100 Ethernet Module The Ethernet interface on the 10/100 Ethernet module can be configured for the Ethernet port speed (10 or 100), duplex mode (full or half), and to enable/disable auto-negotiation:...
Page 172: Configuring A Loopback Interface
BSR 2000 Configuration and Management Guide Release 1.0 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:...
Page 173 Release 1.0 Configuring Interfaces and TCP/IP Features Loopback interfaces are used for the following reasons: Collect accurate service-related information through an SNMP manager about active or down interfaces on the BSR. Indirectly access an outbound physical interface that cannot be directly accessed. When the designated router election process occurs in OSPF, the designated router choice can be forced by assigning a higher IP address for the loopback address.
Page 174: Adding A Permanent Arp Entry And Timeout Value
BSR 2000 Configuration and Management Guide Release 1.0 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.
Page 175: Reverse Arp
Release 1.0 Configuring Interfaces and TCP/IP Features A.B.C.D is the IP address of the ARP entry, specified in dotted-decimal notation. H.H.H is a 48-bit hardware MAC address of the ARP entry. arpa is the Advanced Research Projects Agency (ARPA) packet encapsulation type.
Page 176: Address Resolution Using Proxy Arp
BSR 2000 Configuration and Management Guide Release 1.0 Address Resolution Using Proxy ARP The router uses proxy ARP, as defined in RFC 1027, to help hosts with no knowledge of routing determine the hardware addresses of hosts on the same or other networks or subnets.
Page 177: Configuring The Mtu
Release 1.0 Configuring Interfaces and TCP/IP Features where: A.B.C.D is the broadcast IP address. Configuring the MTU Fragmentation occurs when an IP datagram is too large for a network maximum transmission unit (MTU) size, and the large datagram is divided into several smaller pieces for transmission.
Page 178: Clearing Route Table Entries
BSR 2000 Configuration and Management Guide Release 1.0 where: A.B.C.D is the static route destination IP address. A.B.C.D is the static route destination IP address mask. A.B.C.D is the forwarding router’s IP address. null 0-0 is null interface and port.
Page 179: Configuring The Internet Control Message Protocol
Release 1.0 Configuring Interfaces and TCP/IP Features MOT (config-if)#clear ip route {* | <A.B.C.D> | <A.B.C.D> <A.B.C.D>} 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. Configuring the Internet Control Message Protocol The Internet Control Message Protocol (ICMP) allows a router or destination host to report errors in data traffic processing to the original packet source.
Page 180: Enabling Irdp
BSR 2000 Configuration and Management Guide Release 1.0 Enabling IRDP Use the following procedure to configure IRDP.: Note: IRDP is not available on a CMTS interface. 1. Use the ip irdp command in Interface Configuration mode to enable IRDP: MOT (config-if)#ip irdp 2.
Page 181: Enabling Icmp
Release 1.0 Configuring Interfaces and TCP/IP Features 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: MOT (config-if)#ip irdp holdtime {<1-9000>} where: 1-9000 is the hold-time in seconds that advertisements are kept valid.
Page 182: Tracing A Route
BSR 2000 Configuration and Management Guide Release 1.0 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: MOT #ping [<hostname>...
Page 183: Managing The Router
Release 1.0 Configuring Interfaces and TCP/IP Features Managing the Router Follow these sections to manage routing operations on the BSR: Enabling IP Source Routing Clearing Interface Counters Clearing IP Routes Clearing the ARP Cache Clearing IP Traffic Clearing DNS Entries Enabling IP Source Routing The BSR examines IP header options on every packet.
Page 184: Clearing Ip Routes
BSR 2000 Configuration and Management Guide Release 1.0 loopback clears the loopback interface counters. 1-64 is the loopback interface number. gigaether clears the Gigabit Ethernet interface counters. X is 0. Y identifies the port number. 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: MOT #clear ip route {* | <A.B.C.D>...
Page 185: Gathering Tcp/Ip Related Information
Release 1.0 Configuring Interfaces and TCP/IP Features where: Hostname deletes a specific DNS host entry. * deletes all DNS host entries. Gathering TCP/IP Related Information Follow these steps to view IP information: 1. Use the show ip arp command to display ARP table information: MOT #show ip arp [<A.B.C.D>] [<Hostname>] [<H.H.H>] [cable <X/Y>...
Page 186 BSR 2000 Configuration and Management Guide Release 1.0 3. 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.
Page 187: Configuring The Cmts
The following sections contain the tasks used to configure and manage your cable network: Initial Cable Interface Configuration Tasks Configuring a DOCSIS 2.0 Upstream Logical Channel Using the RF Sentry on the BSR 2000 Post Equalization on the BSR 2000 Configuring a Downstream Channel Configuring an Upstream Channel...
Page 188: Initial Cable Interface Configuration Tasks
BSR 2000 Configuration and Management Guide Release 1.0 Using Flap Lists Managing Multicast Maps Pinging a Cable Modem at the MAC Layer Resetting the Cable Modem Clearing Cable Modem Counters Clearing Cable Interface Counters Configuring Static Upstream Load Balancing Gathering DOCSIS Network Information...
Page 189 Release 1.0 Configuring the CMTS The ip dhcp relay information command enables the BSR's DHCP relay agent to insert the Spectrum Group Name that DHCP client belongs to and/or inserts the MAC address of the DHCP client and the DOCSIS Device Class Identifier into outbound requests to the DHCP server.
Page 190: Dhcp Rate Limiting
BSR 2000 Configuration and Management Guide Release 1.0 3. Use the ip dhcp relay information option command in Interface Configuration mode to enable the DHCP relay agent to insert a MAC address (Agent Remote ID) only into a client’s DHCP packet: Note: The ip dhcp relay information option command must be entered to enable the DHCP relay information option function.
Page 191 Release 1.0 Configuring the CMTS 1. Use the dhcp throttle on command, in Cable Interface Configuration mode, to enable DHCP Rate Limiting for all CM or CPEs, as follows: MOT (config-if)#dhcp throttle {cm | cpe} on where: cm enables DHCP rate limiting for all CMs. cpe enables DHCP rate limiting for all CPEs.
Page 192: Configuring The Cable Helper And Ip Helper Addresses
BSR 2000 Configuration and Management Guide Release 1.0 cm disables DHCP rate limiting for all CMs. cpe disables DHCP rate limiting for all CPEs. Configuring the Cable Helper and IP Helper Addresses The cable helper IP address function disassembles a CM DHCP broadcast packet, and reassembles it into a unicast packet so that the packet can traverse the router and communicate with the DHCP server.
Page 193: Configuring Multiple Isps
Release 1.0 Configuring the CMTS 3. Optionally use the cable helper-address mta command in Interface Configuration mode to configure a secondary helper IP address for the Multimedia Terminal Adapter (MTA) device to forward only UDP broadcasts: MOT(config-if)# cable helper-address <A.B.C.D> mta where: A.B.C.D is the destination DHCP server IP address.
Page 194: Enabling A Vci On A Cable Interface
BSR 2000 Configuration and Management Guide Release 1.0 The host and mta VCI options are used to configure a CPE host or MTA gateway IP address (giaddr) for the cable interface. During the DHCP process, the DHCP relay agent requests an IP address in a particular subnet by inserting the cable interface giaddr into the DHCP requests from CMs, hosts, and MTAs.
Page 195: Selecting A Specific Isp
Release 1.0 Configuring the CMTS mta optionally defines this secondary IP MTA address as the giaddr to be inserted into MTA DHCP requests. Note: The BSR supports 128 secondary IP subnets per cable bundle. The maximum number of IP subnets that can be configured on the BSR chassis is 1024.
Page 196 BSR 2000 Configuration and Management Guide Release 1.0 11. The CPE sends a DHCP request to the cable helper-address that has been defined for all CPEs that are connected to a CM with IP address assignment in the isp-bind sub network. The giaddr is set to the giaddr of the secondary IP address that has been defined for all CPEs that are connected to a CM with an IP address in the isp-bind network.
Page 197 Release 1.0 Configuring the CMTS A.B.C.D is the IP address. A.B.C.D is the subnetwork IP address mask. secondary specifies that the secondary IP address is a secondary IP address for CM DHCP requests. isp-bind A.B.C.D specifies the secondary IP subnet that this secondary IP address is bound to.
Page 198: Enabling Host Authorization For All Cms
BSR 2000 Configuration and Management Guide Release 1.0 Enabling Host Authorization for All CMs The host authorization feature is used for security purposes on the cable network. When enabled, host authorization denies access to any hacker who tries to take or “spoof”...
Page 199: Deleting A Static Host Authorization Entry For A Specific Cm
Release 1.0 Configuring the CMTS 2. Use the host authorization cpe command in Interface Configuration mode to create a static entry for a specific CM and CPE in Privileged EXEC mode: MOT(config-if)# host authorization {<mac> cpe <mac> <prefix>} where: mac is the MAC address of the cable modem. mac is the MAC address of the CPE.
Page 200: Enabling Host Authorization For An Ip Range Of Cpes
BSR 2000 Configuration and Management Guide Release 1.0 Enabling Host Authorization for an IP Range of CPEs Instead of adding individual static CPEs on a specific cable interface using the cable host authorization cpe command, CPEs can be added automatically to the network by specifying a start and end range of IP addresses.
Page 201: Displaying Host Authorization Information
Release 1.0 Configuring the CMTS Displaying Host Authorization Information Use the following show command options to view host authorization information in all modes except UserEXEC mode: If you want to view a summary of ARP authorization table information, issue the show host authorization cpe leased command: MOT# show host authorization summary Figure 6-1...
Page 202: Using Dhcp Lease Query Function To Secure The Cable Network
BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-2 displays typical show host authorization command output: Device Type State Seconds Modem MAC Addr Host IP Addr Modem Ack-TD-TF 600 0090.833d.bbcf 7.1.1.17 Modem Ack-TD-TF 600 000b.0696.4730 7.1.1.18 Modem Ack-TD-TF 600 000b.0626.3bf0...
Page 203 Release 1.0 Configuring the CMTS If the DHCP Lease Query attempt fails, packets associated with the CM and its CPE are discarded. The BSR sends DHCPLEASEQUERY messages to the specified DHCP server and accepts DHCPACTIVE, DHCPKNOWN and DHCPUNKNOWN replies from the DHCP server. The DHCP lease query function requires that the DHCP Server is configured with the following values for the different DHCP message types: DHCP Lease Query (13)
Page 204: Setting Arp Parameters
BSR 2000 Configuration and Management Guide Release 1.0 When the cable interface learns about the DHCP lease through a DHCPLEASEQUERY exchange. When the CM or CPE can continue passing data. Follow these steps to enable the DHCP lease query feature: 1.
Page 205: Configuring A Docsis 2.0 Upstream Logical Channel
Release 1.0 Configuring the CMTS 2. Use the arp command in Interface configuration mode to specify the type of ARP packet that is used on the BSR 2000: MOT (config-if)# arp [arpa | snap] where: arpa is entered for the standard ARP protocol.
Page 206: Logical Channels
Logical Channels For DOCSIS 1.0 and 1.1, a single channel was associated with each single physical port on a BSR 2000. DOCSIS 2.0 introduces the ability to have logical upstream channels on each single physical port. Logical channels allow accommodation of DOCSIS 1.0 and 1.1 (legacy) cable modems in a DOCSIS 2.0 environment.
Page 207: Docsis 2.0 Only Channel Types
Release 1.0 Configuring the CMTS DOCSIS 2.0 Only Channel Types The DOCSIS 2.0 only channel types, A-TDMA and S-CDMA, greatly enhance upstream channel capacity, as shown in Table 6-2: Table 6-2 Features of DOCSIS 2.0 Logical Channel Types DOCSIS 2.0 Channel Type Features A-TDMA A-TDMA features include:...
Page 208: Obtaining Detailed Docsis 2.0 Information
DOCSIS 2.0 and the BSR 2000 The ability to configure the BSR 2000 successfully for operation in a DOCSIS 2.0 environment is dependent upon the BSR 2000 hardware configuration, your awareness of limitations imposed by the DOCSIS 2.0 specification itself, and the software characteristics of the Motorola implementation of DOCSIS 2.0.
Page 209: Bsr 2000 Software Support For Docsis 2.0
A-TDMA, MTDMA, TDMA BSR 2000 Software Support for DOCSIS 2.0 DOCSIS 2.0 is supported by BSR 2000 Release 1.0 and later as follows: The default channel type for all Primary (or Standby) DOCSIS 2.0 2:8 CMTS Module logical channels is TDMA.
Page 210: Docsis 2.0 Logical Channel Configuration Task Summary
BSR 2000 Configuration and Management Guide Release 1.0 The Motorola implementation of DOCSIS 2.0 offers 128QAM and 256QAM in addition to those specified in the CableLabs DOCSIS 1.0, 1.1, and 2.0 specifications. Note: Only the Primary (and Standby) 2:8 DOCSIS 2.0 CMTS Module supports the configuration of logical channels.
Page 211 Release 1.0 Configuring the CMTS X is 0. Y is the MAC Domain. 2. Use the cable upstream channel-type command in Cable Interface Configuration mode to configure an upstream channel type, as shown below: MOT(config-if)#cable upstream {<NUM> | <X/Y>} channel-type {tdma | atdma | mtdma | scdma} where: NUM is the upstream port number and default channel number 0.
Page 212 BSR 2000 Configuration and Management Guide Release 1.0 The following is screen output from the show interfaces cable configuration command which displays the channel type configuration. In this example, four logical channels with an MTDMA channel type have been configured on upstream port 0.
Page 213: Configuring Spectrum Power Density Maintenance For A Logical Channel
Release 1.0 Configuring the CMTS Configuring Spectrum Power Density Maintenance for a Logical Channel The Maintain Power Spectral Density feature can be enabled for each logical channel. If Maintain Power Spectral Density is enabled and the modulation rate is different from the previous UCD, the cable modem must change its transmit power level to keep the power spectral density as close as possible to what it was prior to the modulation rate change.
Page 214: Configuring S-Cdma Active Codes
BSR 2000 Configuration and Management Guide Release 1.0 The existing time stamp mechanism is not sufficient for synchronizing these new frames so an additional level of synchronization is added called a timestamp snapshot. This information contains the frame number, mini-slot number, and time stamp.
Page 215: Configuring The S-Cdma Hopping Seed
Release 1.0 Configuring the CMTS X/Y is the upstream port and logical channel number (0-3). 2-32 is the number of codes allowed per minislot. Configuring the S-CDMA Hopping Seed Use the cable upstream hopping-seed command, in Cable Interface Configuration mode, to specify the 15 bit S-CDMA hopping seed value used for the code hopping sequence initialization, as shown below: MOT(config-if)#cable upstream <X/Y>...
Page 216 BSR 2000 Configuration and Management Guide Release 1.0 where: NUM is the upstream port number and default channel number 0. X/Y the upstream port number and logical channel number (0-3). The following is screen output from the show cable upstream command which displays a complete channel configuration.
Page 217 Release 1.0 Configuring the CMTS ifIndex: 118161 description: centerFreq: 22800000 rng_back_st: rng_back_en: data_back_st: data_back_en: channelWidth: 3200000 powerLevel: 0 (10th of dB) slotSize: force-frag: map-interval: 4000 (usec) pre-equalization: invited-range-interval: 10000 (msec) range-forced-continue: range-power-override: false concatenation: true physical-delay: Mode 0, Min 400, Max 1600 rate-limit: modulation-profile: max-calls:...
Page 218: Using The Rf Sentry On The Bsr 2000
Release 1.0 Using the RF Sentry on the BSR 2000 The BSR 2000 provides an RF Sentry upstream Spectrum analysis tool. The RF Sentry tool is used to measure either power levels or signal to noise ratios of each of the eight upstream ports.
Page 219: Configuring Fft
MOT#fft setup <Slot/Port> [sample {<256-2048>} mode {Tap-in} window {blackman | blackman-harris | hamming | hanning | rectangular}] where: Slot is always 0 for the BSR 2000. Port is a valid upstream port number. sample 256-2048 is the number of samples of the power level measurement. The default is 2048.
Page 220: Starting Fft Power Level Measurement
MOT#fft start <Slot/Port> [sample {<256-2048>}] [mode {Tap-in}] [window {rectangular | hamming | hanning | blackman | blackman-harris}] where: Slot is always 0 for the BSR 2000. Port is a valid upstream port number. sample 256-2048 is the number of samples of the power level measurement. The default is 2048, mode Tap-in is the RF Sentry’s operational mode...
Page 221: Displaying Fft Power Level Measurement Data
MOT#fft display {<Slot/Port>} startfreq {<0-81920000>} endfreq {<0-81920000>} {table | graph} where: Slot is always 0 for the BSR 2000. Port is a valid upstream port number. startfreq 0-81920000 is the start of the frequency range (0 Hz - 81.92 MHz).
Page 222: Signal To Noise Ratio Measurement
BSR 2000 Configuration and Management Guide Release 1.0 where: nvram: retrieves the power level measurement data from the NVRAM file system. flash: retrieves the power level measurement data from the Flash file system. WORD is the power level measurement data filename - limit of 20 characters excluding the ".fft"...
Page 223 5000000-55000000 is the J-DOCSIS standard start frequency in Hz. 5000000-55000000 is the J-DOCSIS standard end frequency in Hz. Note: Depending on the configuration of the BSr 2000, the start and end frequencies will reflect the North American DOCSIS, EURODOCSIS, or J-DOCSIS standards 1600000 is the channel width 1600 kHz.
Page 224: Configuring An Automatically Repeated Snr Test
BSR 2000 Configuration and Management Guide Release 1.0 Configuring an Automatically Repeated SNR Test SNR measurement tests to perform SNR measurements for a specified number of times on one particular frequency. Configuring a automatically repeated SNR measurement test involves specifying a loop count and a center frequency. This type of SNR measurement test is used for diagnostic purposes.
Page 225: Displaying The Snr Configuration
Release 1.0 Configuring the CMTS ingress-cancel on evaluates the SNR with ingress cancellation. modulation-type 16qam evaluates the SNR for 16qam mode. modulation-type auto evaluates the SNR for both QPSK and 16QAM modes. modulation-type qpsk evaluates the SNR for QPSK mode. Displaying the SNR Configuration Use the snr setup-get command, without any additional arguments, to display the current SNR measurement configuration for a particular port or all ports on a...
Page 226: Storing Snr Measurement Data
The snr store command saves the latest SNR measurement data for a CMTS module to a file system. The user specifies a slot (always 0 for the BSR 2000) and port, the file system (NVRAM or Flash), and a file name without any extension to be used to store the SNR measurement data.
Page 227: Retrieving Snr Data From An Operational Cmts Module
Release 1.0 Configuring the CMTS Retrieving SNR Data from an Operational CMTS Module SNR measurement data can be directly retrieved from an operational CMTS module. Use the snr display command, in Privileged EXEC mode, to retrieve SNR data from a CMTS module, as follows: MOT#snr display {<NUM>{<NUM>} where: NUM is 0.
Page 228: Post Equalization On The Bsr 2000
More importantly, the BSR 2000 equalizer length is 24 TAPS which supports a time span that is three times longer than the length supported by other offerings. Cable operators can customize Post Equalization for their needs through modulation profile configuration commands available in the BSR Command Line Interface (CLI).
Page 229: Recommended Post Equalization Upstream Modulation Profiles
Recommended Post Equalization Upstream Modulation Profiles This section lists and describes the recommended Post Equalization modulation profiles to use with the BSR 2000. The recommended standard Post Equalization modulation profile as well as several customizations are included. Refer to Modulation Profiles for information on using the CLI to create and apply modulation profiles.
Page 230 BSR 2000 Configuration and Management Guide Release 1.0 cable modulation-profile 11 initial 5 34 0 qpsk scrambler 0x152 no-diff 320 fixed cable modulation-profile 11 station 5 34 0 qpsk scrambler 0x152 no-diff 320 fixed cable modulation-profile 11 short 2 75 7 16qam scrambler 0x152 no-diff 584...
Page 231: Configuring A Downstream Channel
Release 1.0 Configuring the CMTS Configuring a Downstream Channel A downstream channel is configured to control the data flow from the cable interface to the user CM. This section is divided into two parts. The downstream parameters that must be configured for the minimal operation of the downstream port are discussed in the Initial Downstream Configuration Tasks section.
Page 232: Configuring The Downstream Frequency And Modulation Rate
BSR 2000 Configuration and Management Guide Release 1.0 Enforcing the Downstream Rate Limit Enabling the Downstream Port Entering a Description of the Downstream Port Configuring the Downstream Frequency and Modulation Rate Follow the steps in this section to configure the downstream center frequency and modulation rate: 1.
Page 233: Enforcing The Downstream Rate Limit
Release 1.0 Configuring the CMTS Enforcing the Downstream Rate Limit Use the cable downstream rate-limit command to enable the downstream data transmission rate-limit to CMs on the HFC network. Once the downstream data transmission rate-limit function is enabled, data sent from the cable interface to the CMs is rate-limited according to each CM configuration.
Page 234: Entering A Description Of The Downstream Port
BSR 2000 Configuration and Management Guide Release 1.0 MOT (config-if)# no cable downstream shutdown 2. Use the show interfaces cable command in Interface Configuration mode to verify that the downstream port is enabled: MOT (config-if)# show interfaces cable <X/Y> where: X is 0.
Page 235: Configuring The Downstream Interleave Depth
Release 1.0 Configuring the CMTS Reserving Downstream Bandwidth Unreserving Downstream Bandwidth Cable Modem Downstream Frequency Override During Ranging Testing RF Carrier Modulation Specifying Downstream Queue Thresholds Limiting Downstream Multicast Traffic Configuring the Downstream Interleave Depth The cable operator can protect the downstream path from excess noise or decrease latency on the downstream path by setting the interleave depth.
Page 236: Setting The Downstream Power Level
BSR 2000 Configuration and Management Guide Release 1.0 2. Use the cable downstream interleave-depth command in Interface Configuration mode to set the downstream port interleave depth: Note: A higher interleave depth provides more protection from bursts of noise on the HFC network; however, it increases downstream latency.
Page 237: Reserving Downstream Bandwidth
Release 1.0 Configuring the CMTS 1. Use the cable downstream shutdown command in Interface Configuration mode to optionally disable a downstream port if it must be reset: MOT (config-if)# cable downstream <0-0> shutdown where: 0-0 is the downstream port number. 2.
Page 238: Cable Modem Downstream Frequency Override During Ranging
BSR 2000 Configuration and Management Guide Release 1.0 Cable Modem Downstream Frequency Override During Ranging The Cable Modem Downstream Frequency Override helps the BSR to accelerate ranging in an RF environment where all downstream signals are seen by all cable modems but upstream signals are wired discretely.
Page 239: Specifying Downstream Queue Thresholds
Release 1.0 Configuring the CMTS Specifying Downstream Queue Thresholds If the BSR is running both a time critical application (such as Voice Over IP) and best effort service, the cable downstream threshold command guarantees that the downstream scheduler can only release bandwidth within a certain specified range to the downstream channel.
Page 240: Configuring An Upstream Channel
BSR 2000 Configuration and Management Guide Release 1.0 A.B.C.D is the destination IP multicast address mask. WORD is the optional service class name. If the service class is not specified, the downstream service flow defaults to the DefMCDown service class.
Page 241: Initial Upstream Configuration Tasks
Release 1.0 Configuring the CMTS Table 6-8 describes the upstream parameters: Table 6-8 Upstream Parameters Parameter Identification Default Value Channel Width Radio frequency 1,600,000 Hz 200000, 400000, 800000, channel width 1600000, 3200000 Hz (1280 ksps) (160, 320, 640, 1280, 2560 ksps) Data Backoff Initial ranging...
Page 242: Setting The Upstream Frequency
BSR 2000 Configuration and Management Guide Release 1.0 Setting the Upstream Frequency The cable interface does not operate until a fixed upstream frequency is set. The RF upstream frequency must comply with the expected CM output frequency. Note: Make sure that the upstream frequency selected does not interfere with the frequencies used for any other upstream applications running in the cable plant.
Page 243 Release 1.0 Configuring the CMTS If the upstream input power level is set in relative mode, the input power level changes when the upstream channel width is changed. For example, if the input power level is +11 dBmV for a DOCSIS 3.2 MHz upstream channel bandwidth setting in relative mode and is changed to 1.6 MHz, the default receive power is +8 dBmV.
Page 244 BSR 2000 Configuration and Management Guide Release 1.0 Example 1: Use the cable upstream power-level default command in Interface Configuration mode to set the input power level for a 3.2 MHz channel in relative mode from +11 dBmV to +5 dBmV: MOT (config-if)# cable upstream 0 power-level default -60 The default input power level is reduced by 6 dBmV.
Page 245: Enforcing The Upstream Cm Rate Limit
Release 1.0 Configuring the CMTS Enforcing the Upstream CM Rate Limit Use the cable upstream rate-limit command to enable the upstream data transmission rate-limit. This limits the traffic rate for data sent from the CMs to the cable interface. Packets are buffered by the CMTS, when the data exceeds the permitted bandwidth of the CM, and queued for transmission once upstream bandwidth for the CM becomes available.
Page 246: Entering A Description Of The Upstream Port
BSR 2000 Configuration and Management Guide Release 1.0 1. Use the show interfaces cable command in Privileged EXEC mode to determine if an upstream port is activated or deactivated: MOT # show interfaces cable 2. The upstream ports are in a shutdown state by default. Use the no cable...
Page 247: The Modulation Profile Numbering Scheme
11 may use higher modulation orders not supported by DOCSIS 1.0 and 1.1. IUC 11 was added for unsolicited grant service (UGS) flows. Note: Motorola does not recommend modification of modulation profile parameters without a thorough understanding of modulation changes and DOCSIS interface specifications.
Page 248: Displaying Configured Modulation Profiles
BSR 2000 Configuration and Management Guide Release 1.0 The total number of defined modulation profiles can be determined with the show cable modulation-profile brief command. Note: For a complete list and configuration of all 23 pre-defined modulation profiles, refer to...
Page 249: Determining The Modulation Profile Applied To An Upstream Port
Release 1.0 Configuring the CMTS Determining the Modulation Profile Applied to an Upstream Port Follow these steps to determine which modulation profile is applied to a specific upstream channel: 1. Navigate to Cable Interface Configuration mode, as follows: MOT(config)#interface cable <X/Y> where: X is 0.
Page 250: Modulation Profile Configuration Mode
BSR 2000 Configuration and Management Guide Release 1.0 ifIndex: 46989444 description: centerFreq: 13200000 rng_back_st: rng_back_en: data_back_st: data_back_en: channelWidth: 3200000 powerLevel: 0 (10th of dB) slotSize: force-frag: map-interval: 4000 (usec) pre-equalization: invited-range-interval: 10000 (msec) range-forced-continue: range-power-override: false concatenation: true physical-delay: Mode 0, Min 400, Max 1600...
Page 251: Entering Modulation Profile Configuration Mode
1-600 is the modulation profile number. Note: Modulation profiles 1-4, 101-116, 201-205, and 301-310 are pre-configured modulation profiles. Motorola recommends that user-created modulation profiles use the numbering range of 401-600 to ensure better future portability. The prompt changes to config-modprof followed by the specified modulation...
Page 252: Configuring A Modulation Profile
Note: Modulation profiles 1-4, 101-116, 201-205, and 301-310 are pre-configured modulation profiles. Motorola recommends that user-created modulation profiles use the numbering range of 401-600 to ensure better future portability. For a complete list and configuration of all 23 pre-defined modulation profiles,...
Page 253 Release 1.0 Configuring the CMTS MOT (config-modprof:<modulation profile number>:<IUC Submode>)# iuc {a-long | a-short | a-ugs | initial | long | request | short | station} [atdma | mtdma | scdma | tdma] {128qam | 16qam | 256qam | 32qam | 64qam | 8qam | qpsk} {<0-16>} {<16-253>} {fixed | short} {<0-255>} {off | on} {<0x0-0x7fff>} {off | on} {none | qpsk0 | qpsk1} {<0-1536>} {<0-2048>} {<0-2048>} {<0-32>} {off | on} {<0-128>} {off | on}...
Page 254 BSR 2000 Configuration and Management Guide Release 1.0 Table 6-10 iuc Command Modulation Profile Parameters and Descriptions Parameter Description The Interval Usage Code: a-long Advanced PHY long data grant a-short Advanced PHY short data grant a-ugs Unsolicited Grant Service initial...
Page 255 Release 1.0 Configuring the CMTS Parameter Description 0-16 the number of bytes that can be corrected per FEC code word 16-253 the FEC code word length fixed fixed handling of FEC for last code word short shortened handling of FEC for last code word 0-255 the maximum burst length in minislots off | on...
Page 256: Configuring A Modulation Profile Through An Iuc Submode
Note: Modulation profiles 1-4, 101-116, 201-205, and 301-310 are pre-configured modulation profiles. Motorola recommends that user-created modulation profiles use the numbering range of 401-600 to ensure better future portability. For a complete list and configuration of all 23 pre-defined modulation profiles,...
Page 257 Release 1.0 Configuring the CMTS Table 6-11 IUC Submode Commands Command Description channel-type Specifies the channel type for a modulation profile. codes-subframe Specifies the sub-frame size. (S-CDMA only) differential-encoding on Disables or enables differential encoding. fec-codeword Specifies the Forward Error Correction (FEC) code word length.
Page 258: Applying A Modulation Profile
Modulation profiles 1-4, 101-116, 201-205, and 301-310 are pre-configured modulation profiles. Motorola recommends that user-created modulation profiles use the numbering range of 401-600 to ensure better future portability. For a complete list and configuration of all 23 pre-defined modulation profiles,...
Page 259: Copying A Modulation Profile
Release 1.0 Configuring the CMTS MOT (config-if)# no cable upstream {<NUM> | <X/Y>} modulation-profile <1-600> where: NUM is the upstream port number. X/Y is the upstream port number and logical channel number (0-3). 1-600 is the modulation profile number. Copying a Modulation Profile Use the cable modulation-profile copy command, in Global Configurtion mode, to copy an existing modulation profile from a source modulation profile number to a destination modulation profile number, as show below.
Page 260: Managing The Upstream Channel
BSR 2000 Configuration and Management Guide Release 1.0 where: 1-600 is a modulation profile number to be deleted. 2. Use the no cable modulation-profile command, in Global Configuration mode, to delete an IUC from a configured modulation profile, as shown below: MOT(config)# no cable modulation-profile <1-600>...
Page 261: Configuring Upstream Cm Registration Parameters
Release 1.0 Configuring the CMTS Configuring Upstream CM Registration Parameters Configuring upstream CM registration parameters includes the following options: Setting the Upstream Minislot Size Setting the Upstream Channel Width Setting the Upstream Range-backoff Forcing a Range-response Forcing a Range Power Override Setting the Upstream Data-backoff Configuring the Invited Ranging Interval Configuring the Map Interval...
Page 262 BSR 2000 Configuration and Management Guide Release 1.0 where: NUM is the upstream port number. Use the cable upstream channel-width command in Interface Configuration mode to set the upstream channel width in Hertz (Hz): MOT(config-if)#cable upstream <NUM> channel-width [200000 |...
Page 263 Release 1.0 Configuring the CMTS NUM is the upstream port number. 0-15 is the start value. 0-15 is the end value. Use the no cable upstream data-backoff command in Interface Configuration mode to restore the upstream data-backoff default: MOT (config-if)# no cable upstream <NUM> data-backoff [automatic | <0-15>...
Page 264 BSR 2000 Configuration and Management Guide Release 1.0 The initial ranging start and end backoff values are a part of the Upstream Bandwidth Allocation Map (MAP) that CMs use to register with the CMTS. If a CM initial ranging request collides with requests from other CMs during the initial ranging process, the CM initial ranging request is lost.
Page 265: Moving A Cm Or Mta To A Different Upstream Channel
Release 1.0 Configuring the CMTS Moving a CM or MTA to a Different Upstream Channel Use the cable modem ucc command in Privileged EXEC mode to move a CM/MTA to a different upstream channel A CM or MTA can be moved to a different upstream channel within the same spectrum group and the same MAC domain after registration to balance the number of CM/MTAs evenly among the receivers of the CMTS module to utilize the entire upstream bandwidths more efficiently.
Page 266: Enabling Pre-Equalization
BSR 2000 Configuration and Management Guide Release 1.0 200-1600 is the maximum upstream physical delay in microseconds. The default value is 1600 microseconds. -or- Use the cable upstream physical-delay command in Interface Configuration mode to set the fixed value for an upstream channel: MOT (config-if)# cable upstream <NUM>...
Page 267: Disabling An Upstream Port
Release 1.0 Configuring the CMTS MOT (config-if)# cable upstream <NUM> force-frag <0-255> where: NUM is the upstream port number. 0-255 is the threshold number of minislots without fragmentation for large data grants. Disabling an Upstream Port Follow these steps to administratively shut down an upstream port: 1.
Page 268: Limiting The Number Of Voice Calls On An Upstream Channel
BSR 2000 Configuration and Management Guide Release 1.0 3. Use the show cable ucd-interval command in Interface Configuration mode to display the configured ucd interval value: MOT(config-if)# show cable ucd-interval 4. Use the no cable upstream shutdown command in Interface Configuration mode to re-enable the upstream channel: MOT(config-if)# no cable upstream <NUM>...
Page 269: Enabling/Disabling Cmts Concatenation Capabilities
Release 1.0 Configuring the CMTS Enabling/Disabling CMTS Concatenation Capabilities CMTS concatenation allows an MSO to enable or disable CMTS concatenation capabilities. Enabling the concatenation feature allows the CMTS to do concatenation with participating cable modems. This increases per-CM upstream throughput by combining multiple MAC frames into one packet request.
Page 270: Configuring Antivirus/Antiworm Protection
BSR 2000 Configuration and Management Guide Release 1.0 docsis-1.1 enables/disables concatenation for DOCSIS 1.1 cable modems only. Note: Concatenation must be enabled globally with the cable upstream concatenation command before any setting specified with the cable concatenation command is valid. Once concatenation is enabled globally, the cable concatenation command will enable or disable concatentation for DOCSIS 1.0 and 1.1 cable modems only and concatenation will always be...
Page 271: Configuring The Cable Channel Utilization Interval
Release 1.0 Configuring the CMTS Use the no form of this command, no cable deny ip, to delete a filter you created, as follows: MOT (config-if)# no cable deny ip <0-255> <20-65535> Configuring the Cable Channel Utilization Interval The cable utilization-interval command is used to estimate the amount of bandwidth used on each BSR CMTS module for their downstream and upstream channels for a specified interval.
Page 272: Forcing The Primary Cable Address For Dhcp Requests
BSR 2000 Configuration and Management Guide Release 1.0 2. Use the ip address secondary command to define the Gateway IP address (giaddr) for CPE host DHCP requests or MTA DHCP requests that creates individual subnets for host CPEs, and MTAs: Note: The primary IP address for the cable interface is used for CM DHCP requests.
Page 273: Enabling The Cm Aging Timer
MOT# clear cable modem offline Use the clear cable modem offline command to remove a specific offline CM from the offline list or all CMs from a CMTS slot (always 0 for the BSR 2000) and port: MOT# clear cable modem offline {<mac> | <X/Y>} where: 526360-001-00 Rev.
Page 274: Setting The Insertion Interval For Cms
BSR 2000 Configuration and Management Guide Release 1.0 mac is the MAC address of the CM. X is 0. Y is a CMTS port number Setting the Insertion Interval for CMs The insertion interval is the fixed time period available for CM initial channel request.
Page 275: Setting Cm Authentication Parameters
Release 1.0 Configuring the CMTS 1. Use the cable sync-interval command in Interface Configuration mode to set the synchronization message interval value: Note: Ensure that the interface is down before setting the synchronization message interval. MOT(config-if)# cable sync-interval {0-200} where: 0-200 is the synchronization interval set in milliseconds (msecs).
Page 276 BSR 2000 Configuration and Management Guide Release 1.0 1. Use one the following two options to configure CM authentication parameters so that all CMs return a known text string to register with the cable interface for network access Caution: Ensure that the authentication string or hexadecimal key in the CM configuration file matches the authentication string or hexadecimal key configured on the cable interface.
Page 277: Restoring Previously Defined Authentication Parameters
Release 1.0 Configuring the CMTS where: interface displays running configuration information on all interfaces or a specific interface. cable X = 0 and Y is the CMTS port number on the BSR. | turns on output modifiers (filters). begin filters for output that begins with the specified string. exclude filters for output that excludes the specified string.
Page 278: Setting The Maximum Number Of Hosts
BSR 2000 Configuration and Management Guide Release 1.0 mac is the MAC address of the cable modem. Setting the Maximum Number of Hosts Use the cable modem max-hosts command to set the number of CPE hosts that can connect to a CM on the HFC subnetwork.
Page 279: Configuring Baseline Privacy
Release 1.0 Configuring the CMTS Configuring Baseline Privacy This section contains the tasks to configure Baseline Privacy (BPI). You must configure BPI to encrypt upstream and downstream data on an HFC network. BPI is activated by default and, in most cases, the BPI parameter default values are satisfactory.
Page 280: Setting Tek Privacy
BSR 2000 Configuration and Management Guide Release 1.0 Table 6-12 BPI Parameters Parameter Identification Default Value TEK grace-time Temporary traffic key assigned to 600 seconds 300 to 1,800 seconds TEK lifetime More permanent TEK assigned to 43,200 seconds 1,800 to...
Page 281: Setting Authorization Key Values
Release 1.0 Configuring the CMTS MOT(config-if)#cable privacy cm-tek reset [<1-16383>] where: 1-16383 is the primary Service Identifier (SID) of the cable modem. 4. The default lifetime TEK is 43,200 seconds. Use the cable privacy cm-tek life-time command to set a lifetime TEK for an individual CM in Interface Configuration mode: MOT(config-if)#cable privacy cm-tek life-time <0-16383>...
Page 282: Configuring Service Classes With Mab
BSR 2000 Configuration and Management Guide Release 1.0 cr is a command return that enables the default AK lifetime value. 2. Use the cable privacy cm-auth reset command in Interface Configuration mode to reset the individual CM life-time value once a new AK life-time value is configured: MOT(config-if)#cable privacy cm-auth reset <mac>...
Page 283: Service Classes
Release 1.0 Configuring the CMTS Service Classes The concept of service classes implies assigning service flows to a service class and providing all flows belonging to that class with a defined quality of service. DOCSIS 1.1 has defined a set of QoS parameters, including maximum sustained and minimum reserved traffic rates, and a way for associating specific QoS parameter values to service flows.
Page 284: Scheduling Priority
BSR 2000 Configuration and Management Guide Release 1.0 Scheduling Priority The scheduling priority of a service class determines the order in which service flows are serviced by the packet scheduling algorithm. All service flows belonging to a service class with a higher scheduling priority will be serviced before service flows belonging to service classes with a lower scheduling priority.
Page 285: Default Parameter Settings
Release 1.0 Configuring the CMTS Table 6-13 Default Service Classes Default Service Class Description DefBE-Down Default downstream service class, no minimum rate. DefRRDown Default downstream service class, non-zero minimum rate. DefBEUp Default upstream best-effort service class, no minimum rate. DefRRUp Default upstream best-effort service class, non-zero minimum rate.
Page 286: Sharing Bandwidth Between Service Classes
BSR 2000 Configuration and Management Guide Release 1.0 Table 6-14 Default Parameters Parameter Downstream Best-effort UGS UGS-AD RTPS Non-RTPS Assumed Minimum Rate Packet Size Maximum Concatenated Burst Nominal Polling Interval 10000 50000 50000 Tolerated Poll Jitter 5000 25000 Unsolicited Grant Size...
Page 287: Dqos Emergency Call Service Classes
Release 1.0 Configuring the CMTS a maximum amount of bandwidth that may be allocated non-exclusively to normal voice and emergency communications sessions. This may be 100% of the bandwidth capacity. the amount of bandwidth that may be allocated exclusively to normal voice and emergency communications sessions.
Page 288: Configuring The Dqos Emergency Call Service Classes
BSR 2000 Configuration and Management Guide Release 1.0 All other normal voice calls will not be allowed to use the bandwidth reserved for the emergency class. However, emergency calls are allowed to use the bandwidth for other service classes if the bandwidth of the emergency service class is full. Also, bandwidth reserved for the emergency service class can be used for other applications if the bandwidth is not already being used for emergency voice calls.
Page 289: Displaying Dqos Emergency Call Information
Use the show packet-cable gate command to view the gate ID in hexadecimal notation, CM MAC address, subscriber IP address, CMTS slot number (always 0 for the BSR 2000), upstream and downstream SFID, status and committed time gate summary information for the emergency service classes:...
Page 290 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config)# cable service-class <WORD> where: WORD is the service class name. Note: Default service classes can be changed, but cannot be deleted. 2. Use the name schedule-type command in Cable Service Class mode to create a...
Page 291 Release 1.0 Configuring the CMTS 3. Use the mab command in Cable Service Class mode to specify the bandwidth that a service class is permitted to consume on an interface. Note: The default MAB for any user-defined service class is set to 1 regardless of the scheduling type.
Page 292: Calculating Mab Percentages
BSR 2000 Configuration and Management Guide Release 1.0 Calculating MAB Percentages The total percentage of combined MABs for all upstream or all downstream service classes can not exceed 100%. If a user attempts to exceed this threshold, the BSR will adjust the desired MAB percentage accordingly so it does not exceed 100%.
Page 293: Modifying Service Class Parameters
Release 1.0 Configuring the CMTS Modifying Service Class Parameters Follow these options to make adjustments to service class parameters for either a default service class or a created service class: Configured Active Percent (CAP) is used to estimate the percent of service flows which are likely to be simultaneously active since all service flows are not active simultaneously.
Page 294 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-srvclass)# schedpriority <WORD> <1-32> where: WORD is the service class name. 1-32 is the priority of this service class. Note: The larger the priority number is, the higher the priority it has.
Page 295 Release 1.0 Configuring the CMTS Use the max-burst command in Cable Service Class mode to control the maximum traffic burst size at the transmission line rate of a service flows in a service class: MOT(config-srvclass)# max-burst <WORD> <1522-65535> where: WORD is the service class name. 1522-65535 is the maximum burst size at the transmission line rate of a service flow in bytes or the value of the maximum concatenated burst size QoS parameter.
Page 296 BSR 2000 Configuration and Management Guide Release 1.0 where: WORD is the service class name. 0-65535 is the maximum upstream burst size. Use the activity-timeout command in Cable Service Class mode to specify the amount of time that an active service flow can be unused if there is no activity on the service flow within the time-out interval: MOT(config-srvclass)# activity-timeout <WORD>...
Page 297 Release 1.0 Configuring the CMTS Use the poll-interval command in Cable Service Class mode to specify the nominal interval between unicast request opportunities. The nominal polling interval is relevant for service flows using UGS-AD scheduling, real-time, and non-real time polling scheduling. MOT(config-srvclass)# poll-interval <WORD>...
Page 298 BSR 2000 Configuration and Management Guide Release 1.0 Use the grant-interval command in Cable Service Class mode to specify the apparent or “nominal” time between grants: Note: The nominal grant interval function is relevant only for service flows using UGS or UGS-AD scheduling.
Page 299: Viewing Service Class Information
Release 1.0 Configuring the CMTS where: WORD is the service class name. 0-127 is the number of grants permitted past the nominal grant interval. Use the tos-overwrite command in Cable Service Class mode to provide an ‘AND’ and ‘OR’ mask that the CMTS uses to overwrite the type of service (TOS) field on all upstream IP packets on a service flow Note: If the TOS and mask is omitted, then the TOS field on upstream IP packets are not modified by the CMTS.
Page 300: Displaying Service Class Statistics
BSR 2000 Configuration and Management Guide Release 1.0 Displaying Service Class Statistics If you want to view statistics for a service class on the BSR, issue the show cable srvclass-stats command in Service Class Configuration mode: MOT(config-srvclass)# show cable srvclass-stats [<X/Y> <WORD>] where: X is 0.
Page 301: Displaying Service Flow Statistics
Release 1.0 Configuring the CMTS Use the show interfaces cable service-class command, in all modes except User EXEC, to display interface level service class information for all downstream and upstream service classes, downstream service classes, or upstream service classes that are active on the BSR: MOT# show interfaces cable <X/Y>...
Page 302: Displaying Service Class Statistics
BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-4 displays typical show cable modem svc-flow-id command output for a specific CM: Service flow id Interface Flow Direction Flow Max Rate cable Upstream no restriction cable Downstream no restriction Figure 6-4 show cable modem svc-flow-id Command Output 2.
Page 303: Creating Or Modifying A Qos Profile
Release 1.0 Configuring the CMTS Deleting a QoS Profile Viewing a QoS Profile Initiating a DSA Initiating a DSC Initiating a DSD Configuring an Active Timeout for Dynamic Service Flows Viewing QoS Information Creating or Modifying a QoS Profile A QoS Profile is used for authentication and bandwidth management of DOCSIS1.0 and DOCSIS1.0+ cable modems.
Page 304 BSR 2000 Configuration and Management Guide Release 1.0 • max-us-bandwidth • max-us-burst • priority • tos-mask • tos-value • grant-interval • grant-size • name For example: To configure the grant-interval and grant-size, you would do the following: MOT(config-qosprof:< QoS Profile Number >)# grant-interval MOT(config-qosprof:<...
Page 305: Resetting The Default Values
Release 1.0 Configuring the CMTS Table 6-15 QoS Profile Parameters QoS Profile Description Default max-us-burst The maximum upstream transmit burst size in < > 0-10000000 bits per second that the modem can send for any single transmit burst. "0" indicates no burst size limit.
Page 306: Deleting A Qos Profile
BSR 2000 Configuration and Management Guide Release 1.0 Deleting a QoS Profile Use the no cable qos-profile command, in Global Configuration mode, to delete a QoS Profile as follows: MOT(config)# no cable qos-profile <prof-num> where: prof-num is the QoS Profile identifying number from 1-16.
Page 307 MOT# show cable qos profile NUM where: NUM is always 0 for the BSR 2000. Use the show cable qos profile NUM <1-32> command, to view a specific QoS Profile for the specified Profile Index of the specified CMTS, as follows: MOT# show cable qos profile NUM <1-32>...
Page 308: Initiating A Dsa
BSR 2000 Configuration and Management Guide Release 1.0 Prof Pri Max Guar Flow Created DOWN Mode Count Mask Value By Burst 384000 3072000 1600 true Modem 0008.0e16.fafe 0008.0e17.0026 For detailed descriptions of the command output, refer to the show cable qos profile command.
Page 309: Initiating A Dsc
Release 1.0 Configuring the CMTS MOT# cable modem {<mac> | <prefix>} qos dsa {<prefix> <string>} where: mac is the CM MAC address. prefix is the CM IP address. prefix is the TFTP server IP address. string is the CM configuration file name. 2.
Page 310 BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-5 displays typical show cable modem svc-flow-id command output for a specific CM: Service flow id Interface Flow Direction Flow Max Rate cable Upstream no restriction cable Downstream no restriction Figure 6-5 show cable modem svc-flow-id Command Output 2.
Page 311: Initiating A Dsd
Release 1.0 Configuring the CMTS Initiating a DSD Follow these steps to cause the CMTS to initiate DSD messages to delete an existing service flow for a CM: Note: Before you begin, ensure that the correct CM SFID is selected. 1.
Page 312: Configuring An Active Timeout For Dynamic Service Flows
BSR 2000 Configuration and Management Guide Release 1.0 Configuring an Active Timeout for Dynamic Service Flows CMs dynamically request resources to CMTS such as service flow identifiers (SFIDs) and bandwidth by using a Dynamic Service Addition (DSA) transaction. If the CM fails to issue a Dynamic Service Deletion Request (DSD-REQ) to the CMTS or the DSD-REQ is being dropped for any reasons (e.g.
Page 313: Displaying The Packet Classifier
Release 1.0 Configuring the CMTS Displaying Upstream Service Flow Statistics Displaying Payload Header Suppression Entries Displaying Class of Service (Qos) Profiles Displaying the Packet Classifier A service flow classifier matches a packet to a service flow using a service flow reference.
Page 314: Displaying Service Flow Statistics
BSR 2000 Configuration and Management Guide Release 1.0 X is 0. Y is the port number. 1-4292967295 is the Service Flow Identifier (SFID). Displaying Service Flow Statistics Use the show cable qos svc-flow statistics command in Privileged EXEC mode to display service flow statistics: MOT# show cable qos svc-flow statistics [<X/Y>...
Page 315: Displaying Class Of Service (Qos) Profiles
Release 1.0 Configuring the CMTS 1-65535 is the classifier identifier. Note: If the Classifier ID is not given, all the classifiers with the given SFID are listed. Displaying Class of Service (Qos) Profiles Use the show cable qos profile command to display the priority, bandwidth allocation, and baseline privacy information for all QoS profiles or a selected QoS profile which applies to DOCSIS 1.0, DOCSIS 1.0+, and Euro-DOCSIS 1.0 cable modems, as follows:...
Page 316 BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-6 displays typical show cable qos profile command output for the class of service (QoS) profile 1 which is configured in a CM configuration file: Serv Prio Max Guarantee Max Max tx Baseline Reference...
Page 317: Configuring The Bsr 2000 For Docsis 1.0+ Interoperability
Configuring the BSR 2000 for DOCSIS 1.0+ Interoperability In order for the BSR 2000 to register DOCSIS 1.0+ cable modems successfully, the BSR 2000 must be configured to accept and process DSA-REQs from DOCSIS 1.0+ devices.
Page 318 5. Define the following five QoS Profiles in the BSR 2000 running configuration file. Refer to the section, Creating or Modifying a QoS Profile, that precedes this procedure.
Page 319 Release 1.0 Configuring the CMTS cable qos profile 12 guaranteed-upstream 221 cable qos profile 12 max-upstream 221 cable qos profile 12 grant-size 149 cable qos profile 12 grant-interval 5 cable qos profile 12 name CALLS_4_AT_10MSEC cable qos profile 11 guaranteed-upstream 221 cable qos profile 11 max-upstream 221 cable qos profile 11 grant-size 229 cable qos profile 11 grant-interval 10...
Page 320: Verifying That Docsis 1.0+ Devices Successfully Register
BSR 2000 Configuration and Management Guide Release 1.0 Verifying that DOCSIS 1.0+ Devices Successfully Register There are two ways to verify that DOCSIS 1.0+ devices successfully register and that the BSR 2000 recognizes them. Review the EVT messages displayed on the console. The following information EVT should be displayed on the console if a cable modem has successfully registered as DOCSIS 1.0+:...
Page 321: Configuring A Spectrum Group
Release 1.0 Configuring the CMTS Configuring a Spectrum Group Applying a Spectrum Group to an Upstream Port Evaluating Spectrum Management Performance Configuring a Spectrum Group Each spectrum group contains spectrum data, a spectrum map, and channel assignment: The spectrum data is where the collected spectrum noise information is kept. It contains the starting frequency, resolution, number of data points, time of the last measurement, and a pointer to an array where the noise level is kept.
Page 322: Creating A Spectrum Group
BSR 2000 Configuration and Management Guide Release 1.0 Spectrum hopping rules determine the action taken when the spectrum manager decides to change the parameters of an upstream channel to combat noise. Operators can improve upstream channel conditions to combat ingress noise by...
Page 323 Release 1.0 Configuring the CMTS The Cable Spectrum Group mode displays. From this new prompt, all of the cable spectrum parameters are configured. For example, if you defined your group name as spectrum1 the prompt would display as shown below: MOT(config-spcgrp:spectrum1)# •...
Page 324: Scheduling The Availability Of A Spectrum Group Band
BSR 2000 Configuration and Management Guide Release 1.0 • If you need to add another start and end frequency band to the spectrum group, repeat this step. • If you need to delete a start and end frequency band from a spectrum group, use the no band command as shown below: •...
Page 325 Release 1.0 Configuring the CMTS 5000000-42000000 is the start upstream frequency in Hertz. 5000000-42000000 is the end upstream frequency in Hertz. For example: The following example defines the 25 MHz to 35 MHz upstream frequency band as being available daily at 4:00 PM for spectrum group spectrum1: MOT(config-spcgrp:spectrum1)# time 16:00:00 band 25000000 35000000 3.
Page 326: Scheduling The Removal Of A Spectrum Group Band
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-spcgrp: <WORD>)#no time {<day> | <hh:mm:ss>} band {<5000000-42000000> <5000000-42000000>} Note: When deleting the time for a band, ensure that the exact day, hh:mm:ss, and start and end upstream frequencies are used. where: WORD is the spectrum group name.
Page 327 Release 1.0 Configuring the CMTS where: WORD is the spectrum group name. hh:mm:ss is the time during the day when the band is removed. 5000000-42000000 is the start upstream frequency in Hertz. 5000000-42000000 is the end upstream frequency in Hertz. The following example determines that the band from 25 MHz to 35 MHz, belonging to spectrum group spectrum1, is removed every day at 20:00 PM: MOT(config-spcgrp:spectrum1)# time 20:00:00 delete band 25000000...
Page 328: Configuring Spectrum Data Collection
BSR 2000 Configuration and Management Guide Release 1.0 Deleting an Existing Removal Time for a Band If you need to delete the existing removal time for a band, use the no time delete band command in Cable Spectrum Group mode: MOT(config-spcgrp: <WORD>)#no time {<day>...
Page 329: Configuring Spectrum Hopping Rules
Release 1.0 Configuring the CMTS Follow these options to change the default spectrum data collection parameters used by the spectrum manager: The default resolution is 200000 Hertz (Hz). Use the collect resolution command in Cable Spectrum Group mode to change the frequency resolution rate that the spectrum manager performs: MOT(config-spcgrp: <WORD>)#collect resolution <200000-4000000>...
Page 330 BSR 2000 Configuration and Management Guide Release 1.0 The following spectrum hopping rules apply: No actions are taken if spectrum hopping rules are not defined. The rules include the preferred frequency, modulation profile, channel-width parameters, and power adjustment. Multiple hopping rules with same type of action are allowed.
Page 331 Release 1.0 Configuring the CMTS MOT(config-spcgrp: spectrum1)#hop action frequency 28000000 priority 3. Use the hop action modulation-profile command in Cable Spectrum Group mode to change the modulation profile setting for a hop action: Note: Refer to the Setting Network Parameters for Cable Modems for more information on configuring modulation profiles.
Page 332 BSR 2000 Configuration and Management Guide Release 1.0 WORD is the spectrum group name. 1-255 is the priority number of the upstream channel width setting. When no priority is assigned, the default priority is 128. For example, the following syntax determines that the upstream channel width of 1.6 MHz replaces the existing upstream channel width when the hop action is...
Page 333: Configuring The Spectrum Hopping Error Threshold
Release 1.0 Configuring the CMTS where: WORD is the spectrum group name. 200-3200 is the input power level, expressed in dB. default -150 - +150> is the number of dB above or below the default input power level. Refer to Table 6-17 for more information on this setting.
Page 334: Configuring The Spectrum Hopping Flap Threshold
BSR 2000 Configuration and Management Guide Release 1.0 WORD is the spectrum group name. 1-1000 is the error rate as a fraction of 1000. For example, an error rate of 1 implies 0.1 percent or an error rate of 1000 implies 100 percent.
Page 335: Enabling And Disabling Spectrum Roll-Back
Release 1.0 Configuring the CMTS Enabling and Disabling Spectrum Roll-back The spectrum roll-back function is disabled by default and is used to return the upstream channel width or modulation profile setting, that was adjusted during a hop action, to the original configuration when upstream channel conditions improve. Use the hop action rollback command in Cable Spectrum Group mode to enable the spectrum roll-back function: MOT(config-spcgrp: <WORD>)#hop action rollback...
Page 336 BSR 2000 Configuration and Management Guide Release 1.0 Spectrum Group: spectrum0 Member channels: Schedule Band Schedule (Mhz) From time: To Time 16.000 - 20.000 10.000 - 30.000 Spectrum Group: spectrum1 Member channels: Schedule Band Schedule (Mhz) From time: To Time 8.000 - 12.000...
Page 337 Release 1.0 Configuring the CMTS Spectrum Group : spectrum1 Map status start Frequency (Hz) stop Frequency (Hz) SPEC_AVAILABLE 8000000 12000000 SPEC_AVAILABLE 17000000 18000000 SPEC_OCCUPIED 18000000 21200000 SPEC_AVAILABLE 21200000 22000000 SPEC_AVAILABLE 26000000 30000000 Figure 6-8 show cable spectrum-group map Command Output Use the show cable spectrum-group schedule command in Global Configuration mode to view the spectrum schedule for the spectrum group that you created: MOT(config)#show cable spectrum-group <WORD>...
Page 338: Viewing Your Spectrum Group Configuration
BSR 2000 Configuration and Management Guide Release 1.0 Viewing Your Spectrum Group Configuration The show running config command does not show the configured parameters if the spectrum manager makes changes the upstream frequency, channel width, modulation or power level by hopping action. However, you can issue the show running-config...
Page 339: Evaluating Spectrum Management Performance
Release 1.0 Configuring the CMTS MOT(config)# interface cable <X/Y> where: X is 0. Y is the port number. 2. Use the cable upstream spectrum-group command in Interface Configuration mode to apply a spectrum group to an upstream port: Note: All upstream ports sharing the same return path must be configured to the same spectrum group.
Page 340: Showing Spectrum Data
BSR 2000 Configuration and Management Guide Release 1.0 Determining the MIB Index ID Number of an Upstream Port Viewing Spectrum Management Activity Viewing Spectrum Management Hopping Actions Viewing the Spectrum Management Roll-back Function Showing Spectrum Data Use the show interfaces cable upstream spectrum command in Privileged EXEC mode to view the noise power level for the whole spectrum: MOT# show interfaces cable <X/Y>...
Page 341: Viewing Spectrum Management Configuration Changes
Release 1.0 Configuring the CMTS Frequency (Hz) Voltage (microvolt) Power (dBmV) 5000000 -60.0 5200000 -60.0 5400000 -60.0 5600000 -60.0 5800000 -60.0 6000000 -60.0 6200000 -60.0 6400000 -60.0 6600000 -60.0 6800000 -60.0 7000000 -60.0 7200000 -60.0 7400000 -60.0 7600000 -60.0 7800000 -60.0 8000000 -60.0...
Page 342: Determining The Upstream Signal To Noise Ratio
BSR 2000 Configuration and Management Guide Release 1.0 where: NUM is the upstream port number. Figure 6-11 displays typical show cable upstream command output: ifIndex: 295172 description: centerFreq: 19600000 rng_back_st: rng_back_en: data_back_st: data_back_en: channelWidth: 3200000 powerLevel: 0 (10th of dB)
Page 343: Determining The Mib Index Id Number Of An Upstream Port
Release 1.0 Configuring the CMTS NUM is the upstream port number. For example, Figure 6-12 displays typical show interfaces cable upstream signal-quality command output: ifIndex 229634 includesContention unerroreds 107841126 correctables uncorrectables signalToNoise microReflections equalData Figure 6-12 show interfaces cable upstream signal-quality Command Output Determining the MIB Index ID Number of an Upstream Port It is important to learn the MIB Index ID number that is associated to a specific upstream port on a DOCSIS module because the debug specmgr and logging console...
Page 344: Viewing Spectrum Management Activity
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config)#interface cable 0/0 MOT(config-if)#show cable upstream 1 ifIndex: centerFreq: 13200000 rng_back_st: rng_back_en: data_back_st: data_back_en: channelWidth: 3200000 powerLevel: slotSize: force-frag: map-interval: 4000 pre-equalization: invited-range-interval: 10000 range-forced-continue: range-power-override: physical-delay: Mode 0, Min 1600, Max 1600...
Page 345: Viewing Spectrum Management Hopping Actions
Release 1.0 Configuring the CMTS Viewing Spectrum Management Hopping Actions The debug specmgr command is used to monitor all active upstream ports. The debug specmgr command output in this section describes what can happen when spectrum management hopping actions occur. Note: Ensure that the logging console notifications command is activated so that you can view spectrum management changes.
Page 346 BSR 2000 Configuration and Management Guide Release 1.0 The following command output example displays what happens when the ingress noise power increases causing the error rate to exceed the error threshold on an upstream port: Note: Notice that the noise power level increases.
Page 347 Release 1.0 Configuring the CMTS [07/23-11:04:58:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0, TotalWord : 3054 [07/23-11:04:58:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -172. [07/23-11:05:18:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:05:18:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0, TotalWord : 4044 [07/23-11:05:18:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -102.
Page 348: Viewing The Spectrum Management Roll-Back Function
BSR 2000 Configuration and Management Guide Release 1.0 The following output displays that the hop action succeeded and that a new channel width has been assigned to the upstream port by the spectrum manager: [07/23-11:08:59:SPECMGR]-N-Set to new width 1600000, miniSlot 8 for channel ifIndex = 7 .
Page 349: Using Flap Lists
Release 1.0 Configuring the CMTS [07/23-11:09:58:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0, TotalWord : 2108 [07/23-11:09:58:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -197. [07/23-11:10:08:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:10:08:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0, TotalWord : 1926 [07/23-11:10:08:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -196.
Page 350: Setting Flap List Parameters
BSR 2000 Configuration and Management Guide Release 1.0 Setting Flap List Parameters Flap list parameters are configured to define a criteria for the proper functioning of your cable network. When a CM makes an insertion request more frequently than the defined insertion time (the time allowed for CMs to complete registration), the CM is placed in the flap list for recording.
Page 351 2 dBmV. The power adjustment threshold causes a flap-list event to be recorded when the threshold is exceeded: Note: Motorola recommends that you do not change the power adjustment threshold from the default value, which is 2 dbmV. Ensure that you evaluate the need to enable this function before applying it to your network.
Page 352: Using Flap Lists To Troubleshoot Cm Problems
BSR 2000 Configuration and Management Guide Release 1.0 where: 1-8191 is a number that defines the maximum number of CMs. 7. Use the clear cable flap-list command in Global Configuration mode to remove a CM from the flap list. MOT(config)# clear cable flap-list [<mac>] | all where: mac is the CM MAC address.
Page 353: Viewing Flap List Statistics To Identify Network Health
Release 1.0 Configuring the CMTS Viewing Flap List Statistics to Identify Network Health This section describes the different show cable flap list sorting options and describes the command output fields. CMs appear in the flap list when any of the following conditions are detected: The CM re-registers more frequently than the configured insertion time.
Page 354 BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-13 displays example output for the show cable flap-list command: MAC ID CableIF Hit Miss Flap Type Time 0008.0e95.48e4 0/0 U1 8692 TUE OCT 21 17:09:50 2003 000b.0696.4730 0/0 U1 8670 TUE OCT 21 17:10:45 2003 000b.0699.f77e...
Page 355 Cable IF Detects the cable interface up/down flap. This is the cable interface on the BSR 2000. It denotes the DOCSIS module number (always 0 for the BSR 2000), and the downstream and upstream port numbers. The flap list data can be sorted based on the upstream port number which is useful when isolating reverse path problems unique to certain combining groups.
Page 356: Interpreting Flap List Statistics
BSR 2000 Configuration and Management Guide Release 1.0 Table 6-18 show cable flap-list Command Output Field Display Fields Field Identification Indicates the number of times the CM has ranged. Type Indicates the type of event that triggered the flap. Time Indicates the most recent time a flap has occurred for a particular CM.
Page 357 Release 1.0 Configuring the CMTS Table 6-19 Troubleshooting CM Problems Cause or Symptom Problem Subscriber CM shows a lot of flap list CM is having communication problems with activity the BSR. Subscriber CM shows little or no flap list The CM is communicating with the BSR activity.
Page 358 BSR 2000 Configuration and Management Guide Release 1.0 Table 6-19 Troubleshooting CM Problems Cause or Symptom Problem High ratio of misses over hits (> 10%) Hit/miss analysis should be done after the "Ins" count stops incrementing. In general, if the hit and miss counts are about the same order of magnitude, then the upstream may be experiencing noise.
Page 359 Release 1.0 Configuring the CMTS Table 6-20 describes how to interpret flap list statistics: Table 6-20 Flap List Statistic Interpretations Field Description Hit and Miss The HIT and MISS columns are keepalive polling statistics between the BSR and the CM. The station maintenance process occurs for every CM approximately every 10 seconds.
Page 360: Tips For Administering Flap Lists
BSR 2000 Configuration and Management Guide Release 1.0 Table 6-20 Flap List Statistic Interpretations Field Description Flap The Flap counter indicates the number of times the CM has flapped. This counter is incremented when one of the following events is detected: Unusual CM insertion or re-registration attempts.
Page 361: Managing Multicast Maps
Release 1.0 Configuring the CMTS Managing Multicast Maps Follow this option to manage multicast maps on the BSR: Use the cable privacy mcast access command in Interface Configuration mode to configure a multicast address list: MOT(config-if)# cable privacy mcast access {<H.H.H>} {<A.B.C.D>} where: H.H.H is the MAC address.
Page 362: Resetting The Cable Modem
BSR 2000 Configuration and Management Guide Release 1.0 Resetting the Cable Modem Use these options to reset cable modems (CMs) on the DOCSIS network: Use the clear cable modem reset command in Privileged EXEC mode to reset a single CM by using its MAC address: MOT# clear cable modem <mac>...
Page 363: Clearing Cable Interface Counters
Release 1.0 Configuring the CMTS mac optionally specifies a set of CM MAC addresses to reset counters by masking a portion of the MAC address. Use the clear cable modem counters command in Privileged EXEC mode to clear and reset a specific CM’s traffic counters from the station maintenance list by using its IP address: MOT# clear cable modem <prefix>...
Page 364: Enabling Static Upstream Load Balancing
Note: Using the static load balancing feature requires a thorough knowledge of creating and using Spectrum Groups. Refer to the BSR 2000 Configuration and Management Guide and the BSR 2000 Command Reference Guide for detailed instruction on creating and using Spectrum Groups.
Page 365 Release 1.0 Configuring the CMTS where: WORD is the Spectrum Group name Note: Before a new upstream channel that is added to a Spectrum Group is considered for load balancing, the new upstream channel must have at least one cable modem registered on it. To do this, a user must use the cable modem ucc command to manually force a cable modem onto the new upstream channel.
Page 366: Load Balancing Across All Upstream Channels
BSR 2000 Configuration and Management Guide Release 1.0 Note: Cable modems will not be moved with the load-balancing static command if any of the following conditions apply: a cable modem has TLV type 2, upstream channel ID, assigned in the configuration file.
Page 367: Moving A Cable Modem To A Specified Upstream Channel
Release 1.0 Configuring the CMTS Moving a Cable Modem to a Specified Upstream Channel The cable modem ucc command allows an operator to manually move a CM or embedded MTA to a different upstream channel within the same Spectrum Group and the same MAC domain.
Page 368: Displaying Ucc Statistics
BSR 2000 Configuration and Management Guide Release 1.0 The show cable modem summary and show cable modem summary total commands display a summary of cable modem information, including the Spectrum Group name for each upstream channel, for each cable interface on the BSR.
Page 369: Displaying Ucc/Dcc Statistics
DCC statistics for a MAC Domain, as shown below: MOT# show cable ucc-stats [<X/Y>] where: X is 0. Y is the MAC Domain. Refer to the BSR 2000 Command Reference Guide to see typical screen output from show cable ucc-stats command. MOT# show cable dcc-stats [<X/Y>] where: X is 0.
Page 370: Clearing Ucc Or Dcc Statistics
BSR 2000 Configuration and Management Guide Release 1.0 Clearing UCC or DCC Statistics Use the following commands to clear statistics displayed with show cable ucc-stats and show cable dcc-stats commands: MOT#clear cable ucc-stats [X/Y] MOT#clear cable dcc-stats [X/Y] where: X is 0.
Page 371 Release 1.0 Configuring the CMTS 1. Use the interface command in Global Configuration mode to enter the cable interface on which you want to enable a cable intercept: MOT(config)# interface cable <X/Y> where: X is 0. Y is the port number. 2.
Page 372 BSR 2000 Configuration and Management Guide Release 1.0 interface cable 0/0 ip address 150.42.10.1 255.255.255.0 ip address 150.42.11.1 255.255.255.0 secondary cable helper-address 10.14.38.235 cable-modem cable helper-address 10.14.38.235 host no shutdown cable bundle 1 master no ip unreachables no cable downstream 0 shutdown...
Page 373: Disabling A Cable Intercept
Release 1.0 Configuring the CMTS 6. Use the show interfaces cable intercept command to view intercept information for each intercepted CPE MAC address. Each destination IP address and UDP port for the data collection server are displayed and the total number of packets and bytes that are intercepted from this CPE are also displayed: MOT(config-if)# show interfaces cable <X/Y>...
Page 374: Gathering Docsis Network Information
BSR 2000 Configuration and Management Guide Release 1.0 where: mac is the intercept source, which is the MAC address from which traffic is intercepted. Packets with a source or destination MAC address that matches this address are copied and forwarded to the data collection server. Most often, this MAC address is the user's CPE device, and not the MAC address of the user's CM.
Page 375: Through The Cli
Release 1.0 Configuring the CMTS private.enterprises.riverdelta.rdnCmtsMib.rdnCmtsMiscObjects.rdnCmtsCardType Through the CLI: Use the show running-config command to display the DOCSIS CMTS module type as follows: MOT (config)#show running-config | inc cmts type Displaying Cable Interface Parameters Select from the following options to view CMTS (cable) interface parameters: Use the show interfaces cable downstream command in all modes except User EXEC mode to view a specified downstream port’s statistics for a cable interface.
Page 376 BSR 2000 Configuration and Management Guide Release 1.0 Y is the port number. 0-7 is the upstream port number. Use the show stats cmts command in all modes except User EXEC mode to view cable interface statistics, which includes both downstream and upstream port statistics and QOS service flow dynamic statistics: MOT# show stats <NUM>...
Page 377: Displaying Downstream Parameters
Release 1.0 Configuring the CMTS Displaying Downstream Parameters Use the show cable downstream command in Interface Configuration mode to show the configured parameters for the downstream port: MOT(config-if)# show cable downstream <0-0> where: 0-0 is the downstream port number. Figure 6-17 displays typical show cable downstream command output: ifIndex: 229377...
Page 378: Displaying Upstream Parameters
BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-18 displays typical show interfaces cable downstream command output: Cable 0/0: Downstream 0 is up 172710494 packet output, 14328983931 bytes, 0 discarded 6 total active modems Spectrum Group: Figure 6-18 show interfaces cable downstream Command Output...
Page 379: Viewing Upstream Port Information
Release 1.0 Configuring the CMTS Viewing Upstream Port Information Use the show interfaces cable upstream command in all modes except User EXEC mode to view upstream port statistics: MOT# show interfaces cable <X/Y> upstream [stats | signal-quality | spectrum <5000000-42000000> <5000000-42000000>] where: X is 0.
Page 380 BSR 2000 Configuration and Management Guide Release 1.0 Table 6-21 describes the show cable modem command output column fields. Table 6-21 Cable Modem Fields Field Identification Interface CM interface with active connection Upstream IF Index Upstream interface to which the cable modem belongs.
Page 381 Release 1.0 Configuring the CMTS Figure 6-21 displays typical show cable modem command output: Interface Prim Connect Timing Rec Ip Address Mac Address State Offset Power Cable 0/0/U0 5 online 1861 21.21.21.43 000b.0696.4760 Cable 0/0/U1 1 online 1868 21.21.21.42 000b.0696.476c Cable 0/0/U3 4 online...
Page 382 BSR 2000 Configuration and Management Guide Release 1.0 Table 6-22 Cable Modem Connectivity States Connectivity State Identification online(pt) CM registered; BPI enabled, and traffic encryption key (TEK) is assigned. reject(m) CM did attempt to register; registration was refused due to bad mic.
Page 383 Release 1.0 Configuring the CMTS NUM is the upstream port number. Figure 6-22 displays typical cable modem cpe statistics command output for each cable interface: Interface Prim Connect Timing Rec Ip Address State Offset Power Cable 0/0/U1 1 online 1868 21.21.21.42 Number of Hosts = 0 Interface...
Page 384 BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-23 displays typical show cable modem detail command output: CM Record (index 4) Dump: Psid Config Status regComplete BPI Enabled MAC Address 000b.0696.476c IP Addr 21.21.21.42 US Chan DS Chan Vendor Id...
Page 385 Release 1.0 Configuring the CMTS The show cable modem summary command displays information for the total number of CMs, registered CMs, and unregistered CMs: • Registered modems are modems which have reached the Online(d), Online (pk), Online(pt) or Online(un) states. •...
Page 386 BSR 2000 Configuration and Management Guide Release 1.0 Use the show cable modem svc-flow-id command in Privileged Exec mode to view the service flow ID for a CM connected to a slot and cable interface on the BSR: MOT# show cable modem <mac> svc-flow-id where: mac is the cable modem MAC address.
Page 387 Release 1.0 Configuring the CMTS Use the show cable modem offline command to display offline CMs only: Note: The show cable modem offline command output is updated if the aging timer interval expires for an offline CM. Also, the CM offline table can contain 6100 entries.
Page 388 BSR 2000 Configuration and Management Guide Release 1.0 MOT# show cable modem time-registered [<mac> | spectrum-group <WORD>] where: mac is the MAC hardware address of the CM. spectrum-group is used to identify a spectrum group. WORD is the spectrum group name to which the CM belongs.
Page 389 Release 1.0 Configuring the CMTS Figure 6-29 displays typical show cable modem mac command output. MAC Address Prim Ver Frag Concat PHS Priv State Saids Sids 0090.833d.bba0 online DOC1.0 Figure 6-29 show cable modem mac Command Output The show cable modem phy command displays physical hardware information for CMs.
Page 390 BSR 2000 Configuration and Management Guide Release 1.0 MAC Address USPwr USSNR Timing Mod (dBmV) (tenthdB) Offset Type 0008.0e10.3cb2 C0/0/U0 2 1494 TDMA 0010.1848.2004 C0/0/U1 2 1788 TDMA 0010.9518.f403 C0/0/U3 1 1872 TDMA 0012.c90b.cff8 C0/0/U3 2 1787 TDMA 0020.4094.e238 C0/0/U0 0...
Page 391: Multiple Ip Addresses Per Mac Address
Release 1.0 Configuring the CMTS Figure 6-31 displays typical show cable modem maintenance command output. The following example demonstrates that there have been no CM station maintenance ranging retries or failures: MAC Address Prim SM Exhausted SM Aborted Count - Time Count - Time 0090.833d.bba0 C0/0/U1 xxx xx xx:xx:xx...
Page 392: Viewing The Timing Adjustments For Cms
BSR 2000 Configuration and Management Guide Release 1.0 Interface Prim Connect Timing Rec Ip Address Mac Address State Offset Power Cable 0/0/U1 7 online 1230 7.1.1.22 0090.8336.cdf1 Number of Hosts = 0 Interface Prim Connect Timing Rec Ip Address Mac Address...
Page 393: Displaying Modulation Profiles
Release 1.0 Configuring the CMTS where: 0-500000 is the timing offset value that displays all CMs below this timing offset value. X is 0. Y is the port number. Use the show cable modem timing-offset above command in Privileged EXEC mode to identify all CMs with a timing offset above the entered number: MOT# show cable modem timing-offset above <0-500000>...
Page 394: Viewing The Timing Adjustments For Cms
BSR 2000 Configuration and Management Guide Release 1.0 Table 6-23 show cable modulation-profile Fields Field Identification MOD type mod Upstream modulation type Preambl length Length of the preamble Profile (1-16) Modulation profile group Scrambl Scramble enabled indication Scrambl seed Seed of the scrambler Viewing the Timing Adjustments for CMs Each CM manufacturer uses a different initial timing offset value.
Page 395: Displaying Bpi Configuration Settings
Release 1.0 Configuring the CMTS 0-500000 is the timing offset value that displays all CMs above this timing offset value. X is 0. Y is the port number. Displaying BPI Configuration Settings Follow these steps to ensure that the correct Traffic Encryption Key (TEK) and Authorization Key (AK) privacy values are set: 1.
Page 396 BSR 2000 Configuration and Management Guide Release 1.0 Figure 6-33 displays typical show cable privacy auth command output: Interface Cable 0/0 Auth grace time: 600 Auth life time: 604800 Interface Cable 0/1 Auth grace time: 600 Auth life time: 604800...
Page 397: Configuring Packetcable
Configuring PacketCable Overview The BSR fully supports the Cablelabs® PacketCable™ 1.x and PacketCable Multimedia (PCMM) specifications. PacketCable Multimedia, building on the VoIP capabilities of PacketCable 1.x, provides an IP-based platform for delivering Quality-of-Service (QoS)-enhanced multimedia services over DOCSIS 1.1 and 2.0 HFC networks.
Page 398 BSR 2000 Configuration and Management Guide Release 1.0 Table 7-1 describes the PacketCable and PacketCable Multimedia functional components. Table 7-1 Required PacketCable and PacketCable Multimedia Functional Components Functional Component Description PCMM Application Controls application sessions and communicates with the Customer...
Page 399: Configuration Task Summary
Release 1.0 Configuring PacketCable Table 7-1 Required PacketCable and PacketCable Multimedia Functional Components Functional Component Description PCMM Media Gateway Manages the connection with the PSTN by controlling the Media Controller (MGC) Gateway and Signaling Gateway and maintains the call state for calls requiring PSTN interconnection.
Page 400: Common Network Configuration Tasks
BSR 2000 Configuration and Management Guide Release 1.0 Common Network Configuration Tasks Table 7-2 provides a common configuration task summary: Table 7-2 Common Configuration Task Summary Task Refer to: 1. Specify the network or loopback interface IP Specifying the Protocol IP Address on page 7-6 address used for the PacketCable protocols.
Page 401: Packetcable Multimedia Configuration Task
Release 1.0 Configuring PacketCable PacketCable Multimedia Configuration Task Table 7-4 provides a summary of tasks specific to PacketCable Multimedia: Table 7-4 PacketCable Multimedia Configuration Task Summary Task Refer to: 1. Enable PacketCable Multimedia. Enabling PacketCable Multimedia on page 7-36 Related Tasks Table 7-5 provides a summary of tasks related to both PacketCable and PacketCable Multimedia:...
Page 402: Configuring Common Parameters
BSR 2000 Configuration and Management Guide Release 1.0 The prompt changes to the following: MOT(config-pktcable)# Configuring Common Parameters Follow the procedures in these sections to configure parameters common to both PacketCable 1.x and PacketCable Multimedia: Specifying the Protocol IP Address...
Page 403: Restricting Cops Connections
MOT(config-pktcable)# cops pep-id <WORD> where: WORD is a text string that is between 1 and 32 characters. The default is “Motorola CMTS” Configuring the COPS Client Timer Follow these steps to configure the COPS Client timer: 1. Issue the show packet-cable statistics gate command in PacketCable Configuration mode.
Page 404: Displaying Cops Connections
BSR 2000 Configuration and Management Guide Release 1.0 2. If the show packet-cable statistics gate command output for the Client-Open Sent field in the COPS Statistics section is incrementing, the network and the PDP server need to be examined to determine the reason for the COPS Client timeouts.
Page 405: Verifying The Cops Configuration
Figure 7-2 displays typical show packet-cable configuration cops command output: MOT#show packet-cable configuration cops COPS Configuration ------------------ PEP ID: Motorola CMTS Client Timer: 4000 milliseconds Status trap: disabled Figure 7-2 Output for the show packet-cable configuration cops Command. Configuring Event Messages...
Page 406: Configuring Event Message Parameters
BSR 2000 Configuration and Management Guide Release 1.0 3. Issue the show packet-cable configuration em command to verify that event messages are enabled and the event message Element ID number is configured properly. Figure 7-3 displays typical show packet-cable configuration em command output:...
Page 407 Release 1.0 Configuring PacketCable Configuring the Priority for Event Messages Based on the overall PacketCable network, the Record Keeping Server can prioritize event messages from the BSR. The higher the number, the lower the priority. Issue the em event-priority command in PacketCable Configuration mode to configure the priority value of event messages generated from the BSR relative to other events: MOT(config-pktcable)# em event-priority <0-255>...
Page 408 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-pktcable)# em retry-interval <1-3600> where: 1-3600 is the retry interval in seconds. The default is 2. Configuring the Retry Message Count If an Accounting-Response event message is not received by the BSR from the Record Keeping Server, the BSR sends the event message again.
Page 409: Configuring A Mask For Disabling Event Messages
Release 1.0 Configuring PacketCable Configuring the Number of Batched Event Messages The number of batched event messages can be configured so that multiple event messages can be combined into one packet to reduce network traffic. Event messages are batched together before being sent to the Record Keeping Server. Issue the em max-batch-events command in PacketCable Configuration mode to configure the amount of event messages that are batched.
Page 410 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-pktcable)# em event-disable-mask 0x00000040 Note: Hexidecimal values can also be combined. For example, QoS_Release and QoS_Commit event messages can be disabled by entering the hexidecimal number: 0x00040080. Overriding the Event Message Flag Function The Call Management Server handles the logging of event messages to the Record Keeping Server.
Page 411: Disabling Event Messages
Release 1.0 Configuring PacketCable Disabling Event Messages Issue the em shutdown command in PacketCable Configuration mode to disable event messages generated from the BSR if they are not needed. Note: Event messages are enabled by default. Displaying Event Message Statistics Issue the show packet-cable statistics em command in all modes except User Exec mode to display event messages or Gate statistical information.
Page 412: Configuring Ip Security
BSR 2000 Configuration and Management Guide Release 1.0 Figure 7-4 displays typical show packet-cable statistics em command output: MOT#show packet-cable statistics em Event Message Statistics -------------------------------------------------------------------------- Account Request Sent: Account Response Received: Account Request Failure: Account Response Discarded: DQoS Event Message Statistics...
Page 413: Configuring A Security Policy Using Ipsec And Ike
Release 1.0 Configuring PacketCable Enabling IPSec and IKE Deleting Security Policy Database Policy Entries Displaying the IPSec Configuration Configuring a Security Policy Using IPSec and IKE A security policy that contains the following attributes must be configured to protect the network traffic between two IPSec peers: source and destination address source and destination port protocol type to identify the traffic...
Page 414 BSR 2000 Configuration and Management Guide Release 1.0 string is the name of the Pre-shared Key which is between 1 to 128 characters. 3. Repeat Step 2 if more Pre-shared Key IP addresses must be configured or go to the next step.
Page 415 Release 1.0 Configuring PacketCable ipAddr{-ipAddr2|:ipMask} is the source network IP address followed by a colon and subnetwork mask. If a hyphen is used between ipAddr and ipAddr2, this specifies a range of source network IP addresses. ipAddr{-ipAddr2|:ipMask} is the destination network IP address followed by a colon and subnetwork mask.
Page 416 BSR 2000 Configuration and Management Guide Release 1.0 Figure 7-5 displays typical show ipsec spd policy command output: MOT#show ipsec spd policy Index Source Address Destination Address SPort DPort Processing Indicator IPsec Mode Proto Handle 150.31.40.10 150.31.50.10 Apply Transport Mode 150.31.50.10...
Page 417 Release 1.0 Configuring PacketCable Allowing a Peer to Negotiate a Connection with the SPD Use the spd allow-dynamic-rsp command in IPSec Configuration mode to allow a dynamic response from a peer to negotiate Internet Key Exchange (IKE) even though the IPSec Security Policy Database (SPD) policy setting is other than the "APPLY" policy setting.
Page 418: Configuring Ipsec And Ike Parameters
BSR 2000 Configuration and Management Guide Release 1.0 Configuring IPSec and IKE Parameters Follow the procedures in these sections to configure IPSec and IKE network parameters: Configuring IKE Retransmissions Configuring the IKE Retransmission Timeout Interval Configuring the IKE Phase 1 Lifetime Interval and Lifesize Value...
Page 419 Release 1.0 Configuring PacketCable 4. Issue the ike timeout command to configure the IKE retransmission timeout interval: MOT(config-ipsec)# ike timeout <1-20> where: 1-20 is the timeout interval in seconds. The default is 10. Configuring the IKE Phase 1 Lifetime Interval and Lifesize Value The IKE Phase 1 Lifetime interval and IKE Phase 1 Lifesize can be configured to enhance security.
Page 420: Enabling Ipsec And Ike
BSR 2000 Configuration and Management Guide Release 1.0 2. Issue the ike phase2 lifetime command in IPSec Configuration mode to configure the IKE phase 2 lifetime value, and optionally configure the lifesize value for the lifetime: MOT(config-ipsec)# ike phase2 lifetime <0, 300-2592000> [lifesize <0, 10240-4190000>]...
Page 421: Deleting Security Policy Database Policy Entries
Release 1.0 Configuring PacketCable Deleting Security Policy Database Policy Entries Follow these steps to delete Security Policy Database (SPD) policy entries: 1. Issue the no spd policy command in IPSec Configuration mode to delete SPD entries when they are no longer needed. A single rule or all the rules in the table can be deleted at once: MOT(config-ipsec)# no spd policy {all | <num>} where:...
Page 422: Controlling Electronic Surveillance
BSR 2000 Configuration and Management Guide Release 1.0 Figure 7-7 displays typical show ipsec ike command output: MOT#show ipsec ike IKE: Initialized = false Timeout in seconds = 0 Number of retries = 0 IKE Client IP Address = 150.31.50.10...
Page 423: Displaying Electronic Surveillance Information
"disabled". Displaying Electronic Surveillance Information Use the following commands in all modes except User EXEC mode to display electronic surveillance information. Refer to the BSR 2000 Command Reference Guide for detailed command output information. show packet-cable configuration es command display...
Page 424 BSR 2000 Configuration and Management Guide Release 1.0 show packet-cable configuration es Figure 7-9 displays typical command output: MOT#show packet-cable configuration es Electronic Surveillance Configuration ------------------------------------- ES is disabled ES trap: disabled Figure 7-9 Output for the show packet-cable configuration es Command.
Page 425: Configuring Packetcable Specific Parameters
Release 1.0 Configuring PacketCable Issue the show packet-cable statistics es identifier command to display with the gate’s IP ad duplicated byte and packet counts along dress and UDP port MOT #show packet-cable statistics es identifier <0x00000000-0xffffffff> where: 0x00000000-0xffffffff is the gate identifier in hexadecimal notation. Note: The statistics for an inactive gate are not displayed.
Page 426 BSR 2000 Configuration and Management Guide Release 1.0 3. Issue the interface cable command to enter a cable interface: MOT(config)# interface cable <X/Y> where: X is 0. Y is the port number. 4. Issue the cable dynamic-service authorization-mode command in Interface...
Page 427: Configuring Dqos Parameters
Release 1.0 Configuring PacketCable Figure 7-12 displays typical show packet-cable configuration dqos command output: MOT(config-if)#show packet-cable configuration dqos Dynamic QoS Configuration ------------------------- DQoS is enabled T0 Timer: 30 seconds T1 Timer: 60 seconds Resource Request trap: disabled Emergency trap: disabled Figure 7-12 Output for the show packet-cable configuration dqos Command.
Page 428: Displaying Gates
Displaying Gates Issue the following show commands in all modes except User EXEC mode to display gate information. Refer to the BSR 2000 Command Reference Guide for detailed command output information. Issue the show packet-cable gate command to display the gate ID in...
Page 429 Release 1.0 Configuring PacketCable Figure 7-13 displays typical show packet-cable gate command output. MOT#show packet-cable gate DQoS Gates: -------------------------------------------------------------------------------- GateID | Modem Subscriber |CM| SFID |Pri| Status |Committed (0x) | MAC Address IP Address |TS| Up | Dn Time -------------------------------------------------------------------------------- 00000D3C 0011.8065.f57a 150.31.55.101 58 Low...
Page 430 BSR 2000 Configuration and Management Guide Release 1.0 Issue the show packet-cable gate modem command to display gate summary information for a specified CM: MOT# show packet-cable gate modem <mac> where: mac is the MAC address of the CM. Issue the show packet-cable gate subscriber command to display gate...
Page 431: Displaying Gate Statistics
Release 1.0 Configuring PacketCable Displaying Gate Statistics Issue the show packet-cable statistics gate command in all modes except User EXEC mode to display detailed statistics for all DQoS gates. Figure 7-14 displays typical show packet-cable statistics gate command output: DQoS Gate Statistics -------------------------------------------------------------------------- Gate-Alloc Count: Gate-Open Count:...
Page 432: Configuring Packetcable Multimedia Specific Parameters
BSR 2000 Configuration and Management Guide Release 1.0 Configuring PacketCable Multimedia Specific Parameters If you intend to configure a PacketCable Multimedia network and have already completed the common configuration tasks as described in Table 7-2 on page 7-4, then complete the procedures in this section. These procedures are specific to PacketCable Multimedia.
Page 433: Configuring The Multimedia Gate Timer T1
Release 1.0 Configuring PacketCable Configuring the Multimedia Gate Timer T1 The Multimedia Gate Timer T1 has a default setting for the interval that elapses between authorizing and reserving a PacketCable Multimedia gate. The multimedia T1 timer starts when a gate is authorized. The Multimedia T1 timer is stopped when an operation is performed (e.g.
Page 434: Enabling The Cops Status Snmp Trap
BSR 2000 Configuration and Management Guide Release 1.0 Enabling the COPS Status SNMP Trap Issue the cops status-trap enable command in PacketCable Configuration mode to optionally enable the COPS status SNMP trap through the DQoSCopsTrap SNMP MIB object. MOT(config-pktcable)# cops status-trap-enable [enable | disable] where: enable enables COPS status SNMP trap.
Page 435: Enabling The Resource Request Snmp Trap
Release 1.0 Configuring PacketCable Enabling the Resource Request SNMP Trap Issue the dqos res-req-trap command in PacketCable Configuration mode to optionally enable the Resource Request SNMP trap through the DQoSResReq SNMP MIB object. MOT(config-pktcable)# dqos res-req-trap-enable [enable | disable] where: enable enables Resource Request SNMP trap.
Page 436: Clearing Gates
BSR 2000 Configuration and Management Guide Release 1.0 Clearing Gates PacketCable gate information can be displayed using the show packet-cable gate command, which provides the information necessary to clear them. Figure 7-16 displays typical show packet-cable gate command output: MOT#show packet-cable gate...
Page 437: Clearing Packetcable Statistics
Release 1.0 Configuring PacketCable For example: MOT # clear packet-cable gate identifier 0x6bde0001 Issue the clear packet-cable gate all command to clear all gates: Issue the clear packet-cable gate cops command to clear all gates for a COPS Client handle: MOT# clear packet-cable gate cops <0-99>...
Page 438: Clearing Packetcable Configuration
BSR 2000 Configuration and Management Guide Release 1.0 Clearing PacketCable Configuration Issue the following command options in PacketCable Configuration mode to clear PacketCable configuration(s): Issue the clear configuration cops command to set all COPS configuration parameters to default values. Issue the clear configuration dqos command to set all DQoS configuration parameters to default values.
Page 439: Configuring Routing Policy
Configuring Routing Policy Overview Routing policy can be used to enforce agreements between two or more ISPs concerning the amount and type of traffic that is allowed to pass between them. Routing policy determines the following: Routes to accept from neighboring routers Preferences for accepted routes Routes to be advertised to neighbors Routes to be redistributed into and out of another protocol...
Page 440: Defining Route Maps
BSR 2000 Configuration and Management Guide Release 1.0 Defining Route Maps Route maps establish the conditions for redistributing routes from one routing protocol to another, and for advertising and learning routes from one router to another. A route map consists of route-map commands, match statements that define the conditions that a route must meet, and set statements that define the conditions that apply to a route.
Page 441 Release 1.0 Configuring Routing Policy 1-99 is the standard AS path access list. 100-199 is the extended AS path access list. 2. Use the match community command in Route Map Configuration mode to match one or more BGP community lists: MOT (config-rmap)#match community <1-99>...
Page 442: Using Set Statements To Define Routing Conditions
BSR 2000 Configuration and Management Guide Release 1.0 6. Use the match metric command in Global Configuration mode to match a routing metric value: Note: The match metric for BGP is Multi-Exit Discriminator (MED). MOT (config-rmap)#match metric <0-4294967295> 7. Use the match route-type external command in Route Map Configuration mode...
Page 443 Release 1.0 Configuring Routing Policy MOT (config-rmap)#set as-path prepend <1-65535> [...<1-65535>] 2. Use the set community command in Route Map Configuration mode to set the BGP community attribute: MOT (config-rmap)#set community <1-4294967295> [...<1-4294967295>] 3. Use the set ip next-hop command in Route Map Configuration mode to set the next-hop attribute of a route: MOT (config-rmap)#set ip next-hop <A.B.C.D>...
Page 444: Defining Access Lists And Groups
BSR 2000 Configuration and Management Guide Release 1.0 The commands below apply the route map to a BGP neighbor: router bgp 100 neighbor 160.20.30.4 route-map locpref in Defining Access Lists and Groups An access list is a sequential collection of permit and deny conditions. The BSR tests each condition against conditions in an access list, and supports the following access lists.
Page 445: Configuring An As-Path Access-List
Release 1.0 Configuring Routing Policy Example filters BGP updates from a BGP neighbor. It This configuration example configures Access List 4 by specifying its permit and deny conditions. Access list 4 prohibits the propagation of networks specified in the deny statements (10.0.0.0, 162.15.0.0, and 180.10.0.0) and permits all others.
Page 446: Configuring An Ip Access Group
BSR 2000 Configuration and Management Guide Release 1.0 ip as-path-access-list 1 permit _200$ ip as-path-access-list 1 permit ^100$ ip as-path-access-list 2 deny _690$ ip as-path-access-list 2 permit .* The commands below enable BGP and specify an autonomous system, define two...
Page 447 Release 1.0 Configuring Routing Policy no-export no-advertise local-as Use the no export keyword to disallow advertising to EBGP peers. This is useful in a network that uses IBGP heavily but does not want to share its internal routing policies with its EBGP peers. Use the no-advertise keyword to prevent communities from being propagated beyond the local router, even to IBGP peers.
Page 448: Filtering Routes
BSR 2000 Configuration and Management Guide Release 1.0 AS 100 AS 300 AS 200 Boston rp0001 Figure 8-1 Using a Community List Filtering Routes Use the ip community-list command to filter routes based on a community list: < > MOT (config)#ip community-list 1-99>...
Page 449 Release 1.0 Configuring Routing Policy 100-199 identifies an extended community list. deny allows access for matching. permit prevents access for matching. 1-4294967295 is a number that identifies a community. internet is the internet community. local-as indicates not to advertise this route to peers outside of the local autonomous system.
Page 450: Redistributing Routes
BSR 2000 Configuration and Management Guide Release 1.0 The final commands enable BGP and specify the AS for Router Boston in AS 200, specify the AS of the BGP neighbor (Router A) to which the route map applies, and apply the route map localpref for all incoming routes.
Page 451: Applying A Damping Criteria
Release 1.0 Configuring Routing Policy For detailed information on the redistribute command, refer to the BSR 2000 Command Reference Guide. Example This example redistributes routes learned from OSPF into BGP. The commands enable BGP, specify the autonomous system 100, and specify OSPF as the protocol type for the redistribution.
Page 452: Policy-Based Routing
BSR 2000 Configuration and Management Guide Release 1.0 Example The following example sets the half life to 30 minutes, the reuse value to 1500, the suppress value to 10000, and the maximum suppress time to 120 minutes for route map "new york".
Page 453: Configuring A Policy-Based Route Map
Release 1.0 Configuring Routing Policy Configuring a Policy-Based Route Map You must identify or create a route map to use for policy-based routing to enable policy-based routing. The route map specifies the match and set parameter and the resulting action if all of these parameters are met. You can define additional route map parameters to be used for policy-based routing.
Page 454 BSR 2000 Configuration and Management Guide Release 1.0 Use the set interface null0 command in Route Map Configuration mode to add “null0” as the last entry in the interface list to force packets to be dropped and not routed with the default destination-based routing process.
Page 455: Enabling Policy-Based Routing On An Interface
Release 1.0 Configuring Routing Policy Note: The set commands, described previously, will be applied in the following order: set interface set ip next-hop set default interface set ip default next-hop The first applicable set command in the list will be applied. For example, if the interface specified by “set interface”...
Page 456: Enabling Local Policy-Based Routing On A Router
BSR 2000 Configuration and Management Guide Release 1.0 Enabling Local Policy-Based Routing on a Router Local policy-based routing is applied to all packets originating from this router. Use the ip local policy route-map command in Global Configuration mode to enable...
Page 457 Release 1.0 Configuring Routing Policy 100-199 is the expanded community list number 5. Use the show ip traffic from Privileged EXEC mode to display policy forwarding and drop counts information. MOT #show ip traffic 6. Use the show ip route from Privileged EXEC or Global Configuration mode to display the routing table entries.
Page 459: Configuring Ip Multicast Routing
Configuring IP Multicast Routing Overview The IP multicast routing environment allows a host to send packets to a group of hosts called group members. Multicast packets delivered to group members are identified by a single multicast group address and use best-effort reliability. Hosts can be both senders and receivers.
Page 460: Enabling Ip Multicast Routing On The Bsr
BSR 2000 Configuration and Management Guide Release 1.0 Multicast routing protocols, such as Protocol-Independent Multicast (PIM) are used to maintain forwarding tables in order to forward multicast datagrams between routers on the network. The BSR uses the Internet Group Management Protocol (IGMP) on a specified interface to learn whether members of a group are present on their directly attached subnetworks.
Page 461: About Pim
Release 1.0 Configuring IP Multicast Routing Retrieving PIM Unicast Routes About PIM Protocol-Independent Multicast (PIM) is used to efficiently route to multicast groups that might span wide-area and inter-domain internetworks. It is referred to as “protocol independent” because it is not dependent on any particular unicast routing protocol.
Page 462: Configuring A Static Pim Rendezvous Point
BSR 2000 Configuration and Management Guide Release 1.0 A.B.C.D is the wild-card mask for the PIM network. Configuring a Static PIM Rendezvous Point If a static PIM Rendezvous Point (RP) network IP address is used for a particular multicast group, this IP address must be configured on all RP routers. First-hop routers send registration packets to the RP IP address on behalf of source multicast hosts.
Page 463: Setting Pim Rp To Accept Select Join And Prune Messages
Release 1.0 Configuring IP Multicast Routing MOT(config-pim)# pim rp-address 147.106.6.22 1 Setting PIM RP to Accept Select Join and Prune Messages The PIM Rendezvous Point (RP), which is the BSR, processes all Join and Prune messages by default. The PIM RP can be configured to only receive Join messages destined for the specified PIM RP multicast group IP address, which must be in the range specified by the access list.
Page 464: Delaying Shortest Path Tree Usage For Better Throughput
BSR 2000 Configuration and Management Guide Release 1.0 Delaying Shortest Path Tree Usage for Better Throughput You can control the data threshold rate to delay when the PIM rendezvous point (RP) switches to the Shortest Path Tree (SPT) in order to enhance throughput on your multicast network.
Page 465: Defining The Pim Domain Border
Release 1.0 Configuring IP Multicast Routing Defining the PIM Domain Border A border can be configured for the PIM domain, so that bootstrap messages do not cross the border in either direction. Creating a border allows different Bootstrap Routers (BSRs) to be elected on both sides of the PIM border. Use the ip pim border command in Interface Configuration mode to configure a PIM domain boundary on the interface of a border router peering with one or more neighbors outside the PIM domain:...
Page 466: Adjusting Pim Query Message Interval For Dr
BSR 2000 Configuration and Management Guide Release 1.0 1-255 is the priority of the router to be selected as the DR. Adjusting PIM Query Message Interval for DR IP multicast routers send PIM query "Hello" messages to determine which router is the Designated Router (DR) for each LAN segment (subnetwork).
Page 467: About Igmp
Release 1.0 Configuring IP Multicast Routing Enabling IGMP Controlling Access to IP Multicast Groups Changing the IGMP Version Modifying the IGMP Host-Query Message Interval Specifying the IGMP Querier Time-out Interval Changing the Maximum Query Response Time Configuring the BSR as a Static Multicast Group Member About IGMP IGMP manages the membership of hosts and routers in multicast groups.
Page 468: Enabling Igmp
BSR 2000 Configuration and Management Guide Release 1.0 Enabling IGMP IGMP is enabled on all interfaces on which PIM is configured by default. Controlling Access to IP Multicast Groups The BSR learns about multicast group members that are connected to local networks by sending IGMP host-query messages.
Page 469: Modifying The Igmp Host-Query Message Interval
Release 1.0 Configuring IP Multicast Routing If you need to return to IGMP Version 2, use the ip igmp version 2 command in Interface Configuration mode to return the version of IGMP on the BSR to IGMP Version 2: MOT(config-if)# ip igmp version 2 Modifying the IGMP Host-Query Message Interval When the BSR is configured for multicast routing, it can periodically send IGMP host-query messages to connected networks in order to refresh multicast group...
Page 470: Changing The Maximum Query Response Time
BSR 2000 Configuration and Management Guide Release 1.0 60-3600 is the time interval in seconds. Changing the Maximum Query Response Time IGMP Version 2 allows the maximum query response time advertised in IGMP queries to be changed. The maximum query response time allows a router to quickly detect that there are no more directly connected group members on a subnetwork.
Page 471: Configuring An Ip Multicast Static Route
Release 1.0 Configuring IP Multicast Routing Changing the Distance for a Static Multicast Route Clearing IP Multicast Information Configuring an IP Multicast Static Route IP multicast static routes (mroutes) enable unicast and multicast packets to take different paths over combined multicast and unicast network topologies by allowing multicast packets to travel from the router that is configured with the static multicast route to the next multicast router, even if there are one or more unicast routers in the path.
Page 472: Changing The Distance For A Static Multicast Route
BSR 2000 Configuration and Management Guide Release 1.0 Changing the Distance for a Static Multicast Route Use the ip mroute static distance command in Global Configuration mode to set the default administrative distance for a multicast static route: MOT(config)# ip mroute static distance <1-255>...
Page 473: Gathering Ip Multicast Information
Release 1.0 Configuring IP Multicast Routing Gathering IP Multicast Information Use the following sections to gather information for your multicast network: Displaying General IP Multicast Information Displaying PIM Information Displaying IGMP Information Displaying Reverse Path Forwarding Information Displaying General IP Multicast Information Use the following options to view IP multicast cache information in Privileged EXEC mode: Use the show ip multicast cache-summary command to display the total...
Page 474: Displaying Pim Information
BSR 2000 Configuration and Management Guide Release 1.0 Use the show ip multicast interface command to list the IP address, multicast protocol (PIM or IGMP), and time-to-live (TTL) information that is associated with each multicast interface: MOT# show ip multicast interface...
Page 475: Displaying Igmp Information
Release 1.0 Configuring IP Multicast Routing Use the show ip pim neighbor command to display the PIM neighboring router information: MOT# show ip pim neighbor Use the show ip pim rp command to display the PIM Rendezvous Point (RP) information: MOT# show ip pim rp Use the show ip pim rp-hash command to display the RP to be chosen based on the selected group:...
Page 476 BSR 2000 Configuration and Management Guide Release 1.0 - or - If you want to show any available multicast source router(s) use the show ip rpf command: MOT# show ip rpf 9-18 MGBI 526360-001-00 Rev. B...
Page 477: Configuring Rip
Configuring RIP Overview This chapter describes how to configure the Routing Information Protocol (RIP) for the BSR 2000™: About RIP Enabling RIP Specifying a RIP Version Enabling or Disabling Split Horizon Enabling Route Summarization Applying an Offset List Enabling RIP Authentication...
Page 478: About Rip
BSR 2000 Configuration and Management Guide Release 1.0 About RIP Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) that uses distance-vector routing to measure the shortest path between two points on a network. Distance-vector routing requires that each router inform its neighbors of its routing table.
Page 479: Specifications
Release 1.0 Configuring RIP Specifications The BSR supports the following Request for Comment (RFC) specifications: RFC 1058 — Routing Information Protocol RFC 2453 — RIP Version 2 Enabling RIP In order to use RIP on the BSR, RIP must be enabled. The remaining tasks described in this chapter are optional.
Page 480: Specifying A Rip Version
BSR 2000 Configuration and Management Guide Release 1.0 Specifying a RIP Version By default, the software receives RIPv1 and v2 packets, but sends only RIPv2 packets. You can configure the software to receive and send only RIPv1 packets. You can also configure the software to receive and send only RIPv2 packets.
Page 481: Enabling Or Disabling Split Horizon
Release 1.0 Configuring RIP Examples The following example configures the interface to send RIPv1 packets from the interface: ip rip send version 1 The next example configures the interface to send RIPv2 packets from the interface: ip rip send version 2 This example configures the interface to receive only RIPv1 packets: ip rip receive version 1 Enabling or Disabling Split Horizon...
Page 482: Applying An Offset List
BSR 2000 Configuration and Management Guide Release 1.0 MOT (config-rip)# auto-summary 2. If you disconnect subnetworks, disable automatic route summarization to advertise the subnetworks, using the no auto-summary command. When route summarization is disabled, the software transmits subnet and host routing information across classful network boundaries.
Page 483: Enabling Rip Authentication
Release 1.0 Configuring RIP Enabling RIP Authentication RIPv1 does not support authentication. If you send and receive RIPv2 packets, you can enable RIP authentication on a particular interface. The BSR supports plain-text password authentication and MD5-encrypted password authentication on a RIP interface.
Page 484: Configuring Timers
BSR 2000 Configuration and Management Guide Release 1.0 Configuring Timers Routing protocols use timers to determine time intervals for route information adjustment.A number of seconds to the setting to prevent collisions. 1. To determine the current timers, use the show ip protocols command in...
Page 485: Configuring A Passive Interface For Rip
Release 1.0 Configuring RIP Configuring a Passive Interface for RIP You can configure a passive interface to prevent other routers on a local network from learning about routes dynamically. A passive interface does not transmit routing updates. 1. Use the passive-interface command in Router Configuration mode to create a passive RIP interface, as shown in the following example: MOT(config-rip)# passive-interface {cable <X/Y>...
Page 486 BSR 2000 Configuration and Management Guide Release 1.0 Follow these steps to redistribute routes into RIP: 1. Enter the routing process in which the routes are to be redistributed: MOT(config)#router rip 2. Choose from one or more of the following options to redistribute routes from a specified protocol: •...
Page 487: Assigning A Default Metric Value For Redistributed Routes
Release 1.0 Configuring RIP route-map <WORD> is the route-map name for the BGP route. cr is a command return that redistributes all BGP routes. • Use the redistribute static command in Router Configuration mode to redistribute static routes into RIP: MOT (config-rip)#redistribute static {metric <n>...
Page 488 BSR 2000 Configuration and Management Guide Release 1.0 2. To display the configured network parameters for RIP, use the show ip protocols in Privileged EXEC mode, as shown in the following example: MOT# show ip protocols Figure 10-1 gives an example of the show ip protocols command output: Routing Protocol is "rip...
Page 489 Release 1.0 Configuring RIP 172.19.13.0 255.255.255.0 redistributed 172.17.1.1 10.10.0.0 255.255.255.0 redistributed 58.58.58.2 172.22.251.0 255.255.255.0 redistributed 58.58.58.2 172.22.244.0 255.255.252.0 redistributed 58.58.58.2 10.10.10.0 255.255.255.0 58.58.58.2 t:12 Figure 10-2 show ip rip database Command Output 4. To view the routing table, enter the show ip route command in Privileged EXEC mode, as shown in the following example: MOT# show ip route Figure 10-3...
Page 491: Configuring Ospf
The advanced tasks are optional, but include some parameters that you may choose to change. If a parameter default is satisfactory, you can ignore its associated task. Use the following section to implement OSPF on the BSR 2000™: Enabling OSPF 526360-001-00 Rev.
Page 492: Specifications
BSR 2000 Configuration and Management Guide Release 1.0 The following optional tasks are used to manage OSPF on the BSR 2000™: Redistributing Routes into OSPF Configuring OSPF Area Parameters Managing OSPF on the BSR Configuring OSPF on an Interface Gathering OSPF Information...
Page 493: Redistributing Routes Into Ospf
Release 1.0 Configuring OSPF Example The following example creates the OSPF routing process and adds two OSPF ranges (123.3.4.0 and 125.6.6.0) with each range belonging to a different area. Area 0 is configured for 123.3.4.0 and Area 1 is configured for 125.6.6.0.The example creates two OSPF interfaces.
Page 494 BSR 2000 Configuration and Management Guide Release 1.0 MOT (config-ospf)#redistribute connected [metric <1-16777214> | route-map <WORD>] where: 1-16777214 is the default OSPF redistribution metric number for connected routes. WORD is the route map name for the connected route. • Use the redistribute rip command in Router Configuration mode to redistribute RIP routes into OSPF: MOT (config-ospf)#redistribute rip [metric <1-16777214>...
Page 495: Assigning A Default Metric Value For Redistributed Routes
Release 1.0 Configuring OSPF Assigning a Default Metric Value for Redistributed Routes The default metric function is used to eliminate the need for separate metric definitions for each routing protocol redistribution. Follow these steps to assign a default metric value for all routes redistributed into OSPF: 1.
Page 496: Configuring Ospf Stub Areas
BSR 2000 Configuration and Management Guide Release 1.0 MOT (config-if)#ip ospf authentication-key <WORD> where: WORD is the unencrypted (clear text) with 1 to 8 characters. 3. Exit Interface Configuration mode by using the end command. 4. Enter the OSPF router on the BSR, using the router ospf command in Global Configuration mode.
Page 497 Release 1.0 Configuring OSPF 1. Use the router ospf command in Global Configuration mode to enter OSPF Router Configuration mode. 2. Use the area stub command in Router Configuration mode to configure an OSPF area as a stub area: Note: If there is more than one router within a stub area, ensure that the area that you are creating as a stub area is defined as a stub area on each of these routers.
Page 498: Configuring Ospf Not So Stubby Area
BSR 2000 Configuration and Management Guide Release 1.0 Configuring OSPF Not So Stubby Area The Not So Stubby Area (NSSA) is similar to the OSPF stub area. The BSR does not flood Type 5 external LSAs from the backbone into the NSSA area, but it can import AS external routes in a limited fashion within the area.
Page 499: Configuring Route Summarization Between Ospf Areas
Release 1.0 Configuring OSPF where: A.B.C.D is the IP summary address. A.B.C.D is the IP summary address mask. 0-4294967295 is the 32-bit tag value for filtering externally derived routing information. Example The following example enables NSSA authentication on area 1: router ospf redistribute rip subnets network 180.21.54.0.
Page 500: Configuring Route Summarization Into Ospf Area
BSR 2000 Configuration and Management Guide Release 1.0 0-4294967295 is the number or IP address for the area. A.B.C.D is the IP address for an individual network within the area. A.B.C.D is the subnet mask for the address. Example This example configures an ABR to summarize the aggregate range 1.1.0.0/16.
Page 501: Managing Ospf On The Bsr
Release 1.0 Configuring OSPF Managing OSPF on the BSR This section discusses the following optional OSPF tasks: Establishing a Virtual Link Assign a Default Route for an ASBR Controlling OSPF Link Cost Metrics Allowing Dynamic OSPF Virtual Links Changing OSPF Administrative Distances Configuring Route Calculation Timers Blocking OSPF LSA Flooding Establishing a Virtual Link...
Page 502 BSR 2000 Configuration and Management Guide Release 1.0 A.B.C.D is IP address associated with the OSPF area ID. A.B.C.D is the router ID 32-bit IP address associated with the virtual link neighbor. Use the area virtual-link hello-interval command in Router Configuration mode...
Page 503 Release 1.0 Configuring OSPF MOT (config-ospf)#area {<0-4294967295> | <A.B.C.D>} virtual-link <A.B.C.D> transmit-delay <1-65535> where: 0-4294967295 is the OSPF area IP address or number. A.B.C.D is IP address associated with the OSPF area ID. A.B.C.D is the router ID 32-bit IP address associated with the virtual link neighbor.
Page 504: Assign A Default Route For An Asbr
BSR 2000 Configuration and Management Guide Release 1.0 Use the area virtual-link message-digest-key command in Router Configuration mode if you want to set an encrypted password for the OSPF virtual link: MOT (config-ospf)#area {<0-4294967295> | <A.B.C.D>} virtual-link <A.B.C.D> message-digest-key <1-255>...
Page 505: Controlling Ospf Link Cost Metrics
Release 1.0 Configuring OSPF Use the default-information originate command in Router Configuration mode to force the ASBR to generate a default route into the OSPF routing domain: MOT (config-ospf)#default-information originate [always] [metric <0-16777214>] [metric-type <1-2>] where: always indicates always advertise the default route even when the software does not have one.
Page 506: Changing Ospf Administrative Distances
BSR 2000 Configuration and Management Guide Release 1.0 Changing OSPF Administrative Distances The administrative distance number between 0 and 255 rates the credibility of routing information from one or more routers. A routing source assigned a low administrative distance is trusted more than a routing source that is assigned a high administrative distance value.
Page 507: Configuring Route Calculation Timers
Release 1.0 Configuring OSPF Configuring Route Calculation Timers Timers are used by routing protocols to determine time intervals for when route information is adjusted: Use the timers spf command in Router Configuration mode to configure the delay time after OSPF receives a topology change until it starts a shortest path first (SPF) calculation and hold time between two consecutive SPF calculations, as shown in the following example: MOT(config-ospf)# timers spf {<0-65535>...
Page 508 BSR 2000 Configuration and Management Guide Release 1.0 Table 11-1 OSPF Parameters Parameter Description Default Values transmit-delay Time interval for LSA retransmissions 1second 1 to 65535 seconds priority Value used to determine OSPF 1seconds 0 to 255 designated router seconds...
Page 509 Release 1.0 Configuring OSPF where: 1-3600 is the OSPF transmission delay in seconds. 4. Use the ip ospf priority command in Interface Configuration mode to set priority of this router interface to determine the OSPF designated router on the OSPF network: MOT (config-if)#ip ospf priority <1-255>...
Page 510: Blocking Ospf Lsa Flooding
BSR 2000 Configuration and Management Guide Release 1.0 WORD is the encrypted MD5 password (1-16 characters). Examples The following example sets the cost of sending a packet over an interface to 30: interface ethernet 0/0 ip ospf cost 30 The following example sets the time interval between transmissions of an LSA to 20...
Page 511: Forcing Router Id Choice With Loopback Interface
Release 1.0 Configuring OSPF MOT (config-if)#ip ospf database-filter all out Examples The following example prevents flooding of OSPF LSAs to broadcast, non-broadcast, or point-to-point networks accessible through Ethernet interface 7/0: interface ethernet 0/0 ip ospf database-filter all out Forcing Router ID Choice with Loopback Interface OSPF uses the largest IP address configured on the interfaces as its router ID.
Page 512: Gathering Ospf Information
BSR 2000 Configuration and Management Guide Release 1.0 A.B.C.D is the subnetwork mask of the IP network, on which the interface is associated. 255.255.255.255) Note: A 32-bit mask ( is permitted for a loopback IP address. Gathering OSPF Information There are several show commands that can be used to view and gather information about your OSPF network.
Page 513 Release 1.0 Configuring OSPF Displaying Neighboring Routers Use the following options to display OSPF neighbor information: Use the show ip ospf neighbor command to display information about all OSPF neighbors: Note: The show ip ospf neighbor can be accessed by the ISP user group. MOT# show ip ospf neighbor Figure 11-2 displays typical show ip ospf neighbor command output:...
Page 514 BSR 2000 Configuration and Management Guide Release 1.0 Displaying Virtual Links The show ip ospf virtual-links command displays parameters regarding the current state of the OSPF virtual links. MOT# show ip ospf virtual-links Displaying OSPF Interface Information Use the following options to display OSPF interface information: Use the show ip ospf interface command to display information about all interfaces on which OSPF is configured.
Page 515: Displaying Ospf Memory Information
Release 1.0 Configuring OSPF Use the show ip ospf interface command with the known IP address of the OSPF interface: MOT# show ip ospf interface <A.B.C.D> where: A.B.C.D is the interface IP address. - or - Use the show ip ospf interface command with modifiers to display information about individual interfaces on which OSPF is configured: MOT# show ip ospf interface {cable | ethernet | gigaether | <X/Y>...
Page 516: Displaying Ospf Database Information
BSR 2000 Configuration and Management Guide Release 1.0 Figure 11-5 displays typical show ip ospf memory command output: OSPF Memory Usage Mem Pool Free In-Use Hi-Water Mark ------------------------------------------------------------------ IntfConfig Circ CfgRange 1024 Area Network Neighbor HostRt PentBlk PassiveIntf RetransNode LsaAck...
Page 517 Release 1.0 Configuring OSPF Figure 11-6 displays typical show ip ospf database command output: OSPF Router with ID (9.1.1.1) Router Link States (Area 0) Link ID ADV Router Seq# Checksum Link count 9.1.1.1 9.1.1.1 1016 0x800000AE 0xDA24 172.17.1.103 172.17.1.103 0x80000149 0xDCD 172.17.82.152 172.17.82.152 1621...
Page 518 BSR 2000 Configuration and Management Guide Release 1.0 Use the show ip ospf database asbr-summary adv-router command to display summary link state information for Advertising Router link states: MOT# show ip ospf database asbr-summary adv-router [<A.B.C.D>| self-originate] where: A.B.C.D is the link state identifier (IP address) of the ASBR..
Page 519: Configuring Bgp
This chapter describes how to configure Border Gateway Protocol (BGP) for the BSR 2000™ system using the command line interface (CLI). For a complete description of the CLI commands discussed in this chapter, refer to the BSR 2000 Command Reference Guide. This chapter discusses the following topics:...
Page 520: About Bgp
BSR 2000 Configuration and Management Guide Release 1.0 About BGP BGP, an Exterior Gateway Protocol (EGP) allows you to set up an inter-domain routing system that automatically guarantees the loop-free exchange of routing information between autonomous systems (ASs). An AS is a set of routers that use a single routing policy running under a single technical administration.
Page 521 Release 1.0 Configuring BGP Note: Set up your router with BGP if your AS or router is dual or multihomed (if it has two or more backbone connections, either direct or daisy-chained thorough another point of presence). Also, use BGP if the BSR provides IP routing to a downstream site or customer or if you must preserve AS path information in your network.
Page 522: Bgp Peers
BSR 2000 Configuration and Management Guide Release 1.0 You can configure BGP operating parameters manually. BGP selects among different routes by comparing specific path attributes or metrics for each route. The local administrator can configure each of these and assign them different values.
Page 523: Bgp Updates
Release 1.0 Configuring BGP BGP Updates BGP routers exchange routing information in the form of BGP updates. BGP updates contain the following attributes associated with routes that a BGP peer advertises to its neighbors: A list of ASs the routing update passed through The AS routing update origin Next hop information Metrics specifying route preference...
Page 524: Configuring Basic Bgp Connectivity
BSR 2000 Configuration and Management Guide Release 1.0 Configuring Basic BGP Connectivity BGP provides a means to organize the connectivity of BGP neighbors and peer groups. The following are basic BGP connectivity configuration tasks: Configuring a BGP neighbor Advertising networks in an AS...
Page 525 Release 1.0 Configuring BGP WORD is the name of the BGP peer group. LINE is up to 80 characters of text that describes the neighbor. Example The following commands configure Routers Miami with Routers Chicago, Boston, and New York as neighbors (as shown in Figure 12-2): MOT(config-bgp)#router bgp 100...
Page 526 BSR 2000 Configuration and Management Guide Release 1.0 Advertising Networks in an AS Follow these steps to advertise networks in an AS: 1. Use the network command in Router Configuration mode to advertise BGP peers in other ASs about the networks in which your AS originates: MOT(config-bgp)#network <1-65535>...
Page 527: Configuring Advanced Bgp Connectivity
Release 1.0 Configuring BGP AS 300 162.24.0.0 3.3.3.1 Chicago AS100 3.3.3.2 162.56.0.0 2.2.2.2 AS 100 126.60.0.0 Miami 2.2.2.1 Figure 12-3 Advertising Networks in an AS Configuring Advanced BGP Connectivity The following are advanced BGP connectivity configuration tasks: Configuring BGP Peer Groups Configuring a Routing Domain Confederation Configuring Route Flap Dampening Shutting Down a Neighbor or Peer Group...
Page 528: Configuring Bgp Peer Groups
BSR 2000 Configuration and Management Guide Release 1.0 Setting the Routing Updates Interval Enabling EBGP Multihop for Neighbor and Peer Groups Controlling the Number of Prefixes Configuring Next Hop Processing Configuring Next Hop Processing for Frame Relay Configuring BGP Peer Groups Routing policies are usually defined by route maps, filter lists, and distribution lists.
Page 529 Release 1.0 Configuring BGP You can create a BGP peer group or you can configure a BGP neighbor to be a member of a BGP peer group using the neighbor peer-group command. 1. Use the neighbor peer-group command in Router Configuration mode to create a BGP peer group: MOT(config-bgp)#neighbor <WORD>...
Page 530: Configuring A Routing Domain Confederation
BSR 2000 Configuration and Management Guide Release 1.0 Configuring a Routing Domain Confederation You can reduce the IBGP mesh inside an AS by creating a BGP confederation. In Figure 12-5, AS 400 consists of ten BGP neighbors that, without confederations, require that the routers be fully meshed.
Page 531 Release 1.0 Configuring BGP Although the peers in different ASs within the same confederation have EBGP sessions, they exchange routing information as if they were IBGP peers. Specifically, the next-hop and local preference information is preserved. This lets you retain a single IGP for all the ASs in the confederation.
Page 532: Configuring Route Flap Dampening
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-bgp)#bgp confederation identifier <1-65535> where: 1-65535 is the AS number that internally includes multiple ASs. 2. Use the bgp confederation peers command in Router Configuration mode to configure an AS to be a member of the confederation: MOT(config-bgp)#bgp confederation peers <1-65535>...
Page 533: Global Route Flap Dampening
Release 1.0 Configuring BGP Route flapping occurs when a link constantly fluctuates between being available and unavailable. When a link changes its availability, the upstream neighbor sends an update message to all its neighbors. These routes are advertised globally. This process continues until the underlying problem is fixed.
Page 534: Clearing Route Flap Dampening
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config)#router bgp 100 MOT(config-bgp)#bgp dampening route-map dallas MOT(config-bgp)#route-map dallas permit 10 MOT(config-bgp)#ip as-path access-list 1 MOT(config-bgp)#set dampening 5 1000 1500 15 These commands specify AS path access list 1 as the filter to determine the permitted ASs.
Page 535 Release 1.0 Configuring BGP MOT(config-bgp)#neighbor {<A.B.C.D> | <WORD>} shutdown where: A.B.C.D is the IP address of the neighbor. WORD is the name of the peer group. Note: In the case of a peer group, use of the neighbor shutdown command may suddenly terminate a large number of peering sessions.
Page 536: Enabling Message Digest 5 Authentication Between Peers
BSR 2000 Configuration and Management Guide Release 1.0 Enabling Message Digest 5 Authentication Between Peers You can enable Message Digest 5 (MD5) authentication between two BGP peers, causing each segment sent on the TCP connection between them to be verified. You must configure the same password on both BGP peers;...
Page 537: Enabling Ebgp Multihop For Neighbor And Peer Groups
Release 1.0 Configuring BGP WORD is the name of the BGP peer group. 0-600 is the advertisement interval time in seconds. Example The commands in the following example set the minimum time between sending BGP routing updates to 4 seconds: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 3.3.3.3 advertisement-interval 4 Enabling EBGP Multihop for Neighbor and Peer Groups...
Page 538: Controlling The Number Of Prefixes
BSR 2000 Configuration and Management Guide Release 1.0 AS 200 1.1.1.2 Boston 3.3.3.1 1.1.1.1 AS 200 Washington AS 100 3.3.3.3 Miami rp0011 Figure 12-6 Using EBGP-Multihop Controlling the Number of Prefixes Use the neighbor maximum-prefix command in Router Configuration mode to control the number of prefixes received from a neighbor router: MOT(config-bgp)#neighbor {<A.B.C.D>...
Page 539: Configuring Next Hop Processing
Release 1.0 Configuring BGP WORD is the name of the BGP peer group. 1-65536 is the maximum number of prefixes allowed from this neighbor. 1-100 is the percent of the maximum at which the router generates a warning message. The default is 75 percent. warning-only gives a warning message when the limit is exceeded instead of shutting down the peer.
Page 540: Configuring Next Hop Processing For Frame Relay
BSR 2000 Configuration and Management Guide Release 1.0 AS 100 120.80.30.2 Washington IBGP 130.60.20.1 AS 300 172.56.20.1 172.56.20.2 Miami 172.56.20.1 EBGP Figure 12-7 Configuring Next Hop Processing The following commands configure Router Miami: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 172.56.20.1 remote-as 300 MOT(config-bgp)#neighbor 120.80.30.2 remote-as 100...
Page 541 Release 1.0 Configuring BGP MOT(config-bgp)#neighbor {<A.B.C.D> | <WORD>} next-hop-self where: A.B.C.D is the IP address of the neighbor. WORD is the name of the neighbor peer group. The network shown in Figure 12-8 shows a situation that may require a different IP address for the next hop.
Page 542: Configuring Global Bgp Tasks
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-bgp)#neighbor 172.56.10.1 next-hop-self Configuring Global BGP Tasks The following are global configuration tasks that apply to overall BGP routing and not to a single BGP peer: Resetting BGP Connections Configuring BGP Soft Reconfiguration...
Page 543: Configuring Bgp Soft Reconfiguration
Release 1.0 Configuring BGP 2. Use the clear ip bgp flap-statistics command in Privileged EXEC mode to reset flap statistics information for a BGP neighbor: MOT#clear ip bgp {<A.B.C.D> | <WORD>} flap-statistics where: A.B.C.D is the BGP neighbor address. WORD is the BGP peer group name. Configuring BGP Soft Reconfiguration To make a change in routing policy, you must clear a BGP session.
Page 544: Enabling And Disabling Synchronization
BSR 2000 Configuration and Management Guide Release 1.0 Enabling and Disabling Synchronization Synchronization is a feature of BGP that prevents a BGP speaker from advertising a route before all routers within an AS have learned the route. Without synchronization, traffic may be dropped as a result of intermediate non-BGP routers not having learned routes when the AS provides transit service to other ASs.
Page 545 Release 1.0 Configuring BGP AS 200 AS 100 Chicago Albany IBGP AS 300 192.56.0.0 Boston Figure 12-9 Synchronization If your AS does not pass traffic from one AS to another or if all the transit routers in your AS run BGP, Use the no synchronization command in Router Configuration mode to disable synchronization: MOT(config-bgp)#no synchronization Example...
Page 546: Configuring Bgp Administrative Weights
BSR 2000 Configuration and Management Guide Release 1.0 Configuring BGP Administrative Weights You can assign a weight to a neighbor connection if more than one route exists for the same destination. A weight indicates a preference for a particular route; a higher weight indicates a preferred route.
Page 547 Release 1.0 Configuring BGP AS 300 192.24.0.0 4.4.4.1 AS 200 AS 400 160.80.0.0 192.56.0.0 Albany AS 100 150.60.0.0 Boston 3.3.3.1 Figure 12-10 Assigning a Weight to a Neighbor Connection Example For example, the commands in the following example configure Router Los Angeles (as shown in Figure 12-10) using the neighbor weight command.
Page 548: Using An As Path Access List
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-bgp)#neighbor 3.3.3.1 remote-as 100 MOT(config-bgp)#neighbor 3.3.3.1 weight 1000 MOT(config-bgp)#neighbor 4.4.4.1 remote-as 300 MOT(config-bgp)#neighbor 4.4.4.1 weight 500 Using a Route Map The commands in the following example configure Router Los Angeles using a route map.
Page 549: Adjusting Bgp Timers
Release 1.0 Configuring BGP Adjusting BGP Timers BGP supports the following two commands that set the frequency of keepalive and holdtime timers: timers bgp — globally sets the keepalive timers for BGP neighbor timers — sets the keepalive timers for a BGP peer or peer group Keepalive messages are exchanged between BGP peers or peer groups to monitor the health of the link between them.
Page 550: Setting The Administrative Distance For A Route
BSR 2000 Configuration and Management Guide Release 1.0 Example The commands in the following example, configure the keepalive frequency and holdtime interval for BGP on a BSR and configure the keepalive frequency and holdtime interval for a BGP peer: MOT(config)#router bgp 100 MOT(config-bgp)#timers bgp 80 200 MOT(config-bgp)#neighbor 192.56.20.2 timers 80 200...
Page 551: Disabling Route Summarization
Release 1.0 Configuring BGP 1-255 is the administrative distance for routes external to the AS. The default is 1-255 is the distance for routes internal to the AS. The default is 200. 1-255 is the administrative distance for local routes. The default is 200. Example In the following example, internal routes are preferable to those learned through the IGP.
Page 552 BSR 2000 Configuration and Management Guide Release 1.0 Router NY's routing table Destination Next hop Direct Direct Boston Albany Boston Direct Chicago Chicago Chicago Chicago Boston Router Albany's routing table Destination Next hop Direct Direct Direct Boston Direct Router Albany's routing table...
Page 553: Configuring Aggregate Addresses
Release 1.0 Configuring BGP Configuring Aggregate Addresses Using CIDR addressing, you can combine routes so that multiple routes are advertised as a single route. CIDR replaces the concept of classes (such as Class A, Class B, and Class C) with the concept of IP prefixes. An IP prefix is a network address that indicates the number of bits that comprise the network number.
Page 554 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-bgp)#aggregate-address {<A.B.C.D> <A.B.C.D>} attribute-map <name> where: A.B.C.D is the aggregate IP address. A.B.C.D is the aggregate IP subnetwork mask. name is the route map name. Use the aggregate-address summary-only command in Router Configuration mode to filter all more specific routes from updates: MOT(config-bgp)#aggregate-address {<A.B.C.D>...
Page 555: Assigning An Interface To Bgp Session
Release 1.0 Configuring BGP Assigning an Interface to BGP Session The neighbor update-source command is used to allow a BGP session to use any operational interface for TCP connections by specifying an IP address or peer-group and the proper interface. This feature is often used in conjunction with loopback interfaces.
Page 556: Configuring A Default Route
BSR 2000 Configuration and Management Guide Release 1.0 Albany Loopback interface 0: 160.10.0.1 Boston Figure 12-12 Using a Loopback Interface The following commands configure a loopback interface for Router Albany, enter the following: MOT(config)#interface loopback 1 MOT(config-if)#ip address 160.10.0.1 255.255.255.255...
Page 557 Release 1.0 Configuring BGP A.B.C.D is the IP address of the neighbor. WORD is the name of the BGP peer group. WORD is name of the route map. The route map allows route 0.0.0.0/0.0.0.0 to be injected conditionally. It is important to control defaults in BGP, because a BGP neighbor, in an attempt to advertise a default route to a specific peer, may send the default to all of its neighbors.
Page 558: Configuring Bgp Update Flows
BSR 2000 Configuration and Management Guide Release 1.0 Configuring BGP Update Flows BGP update messages are exchanged between BGP peers to determine how a BGP router updates route entries in its routing table. Use BGP commands to modify the information in BGP updates sent out by a router to one or more of its peers.
Page 559: Configuring The Local Preference
Release 1.0 Configuring BGP 6. BGP uses the route with the shortest AS path. 7. BGP uses the route with the lowest origin type. IGP is lower than EGP, and EGP is lower than INCOMPLETE. 8. BGP uses the route with the lowest MED. The comparison is made only if the neighboring AS is the same, except when the bgp always-compare-med command is enabled.
Page 560 BSR 2000 Configuration and Management Guide Release 1.0 AS 200 192.30.10.1 Chicago AS 100 192.30.10.2 140.20.30.1 AS 300 156.10.0.0 IBGP AS 500 140.20.30.2 192.56..10.1 AS 400 Boston Washington 192.56.10.2 bgp0019 Figure 12-14 Configuring the Local Preference Attribute Router New York sets the local preference for all updates from AS 200 to 125. Router Boston sets the local preference for all updates from AS 400 to 200.
Page 561: Configuring The Origin Attribute
Release 1.0 Configuring BGP Example: Using a Route Map to Set the Local Preference A route map setting the local preference allows more flexibility in determining updates from a specific AS. In the previous example, all updates received by Router Boston are set to a local preference of 200 (including updates from AS 500).
Page 562 BSR 2000 Configuration and Management Guide Release 1.0 Example Figure 12-15, from Router Boston, the route for reaching 192.56.0.0 has an AS-path of 300 with an origin attribute of IGP. From Router Boston, the route for reaching 175.40.30.0 has an origin attribute of IGP. From Router Los Angeles, the route for reaching 150.20.0.0 has an AS-path of 100 with an origin attribute of IGP.
Page 563: Configuring The As-Path Attribute
Release 1.0 Configuring BGP MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 150.20.30.1 remote-as 100 MOT(config-bgp)#network 175.40.30.0 The following commands configure Router Los Angeles: MOT(config)#router bgp 300 MOT(config-bgp)#neighbor 1.1.1.1 remote-as 100 MOT(config-bgp)#network 192.56.0.0 Configuring the AS-path Attribute When a BGP route passes through an AS, BGP prepends its AS number to the route. The AS_path attribute contains the list of ASs that a route has gone through.
Page 564: Configuring The Med Attribute
BSR 2000 Configuration and Management Guide Release 1.0 AS 300 192.55.0.0 AS 400 192.56.0.0 AS 100 150.60.0 Boston 3.3.3.2 Figure 12-16 The AS-path Attribute Configuring the MED Attribute The MED attribute carries a metric expressing a degree of preference for a particular route.
Page 565 Release 1.0 Configuring BGP If two ASs are connected in more than one place, you can change this value so that a router chooses the optimal link to reach a specific prefix in or behind that AS. Unlike the Local Preference attribute, the MED attribute is exchanged between ASs. When BGP sends an update to another AS, the MED attribute is reset to 0.
Page 566 BSR 2000 Configuration and Management Guide Release 1.0 MOT(config-bgp)#neighbor 5.5.5.2 remote-as 100 MOT(config-bgp)#neighbor 4.4.4.2 remote-as 100 MOT(config-bgp)#neighbor 6.6.6.1 remote-as 300 The following commands configure Router Los Angeles: MOT(config)#router bgp 300 MOT(config-bgp)#neighbor 6.6.6.2 remote-as 200 MOT(config-bgp)#neighbor 6.6.6.2 route-map 10 out MOT(config-bgp)#neighbor 7.7.7.1 remote-as 100...
Page 567: Configuring The Community Attribute
Release 1.0 Configuring BGP Configuring the Community Attribute A community is a group of destinations that share a common policy. You can define the communities a destination belongs to. This determines how routes are advertised. Use a route map to set the community attribute. BGP defines the following well-known communities: no-export advertises a route to IBGP peers only (peers within the local AS).
Page 568: Match And Set Statements
BSR 2000 Configuration and Management Guide Release 1.0 WORD uniquely identifies a route map. permit specifies consider the route for further operation. deny specifies do not consider the route for further operation. 0-65535 uniquely identifies an instance of the route map. Instances with lower sequence numbers are parsed first.
Page 569 Release 1.0 Configuring BGP Table 12-3 shows set commands for creating route maps. Table 12-3 set Commands Command Description set as-path prepend Modifies an AS path. set comm_list Removes selected communities. set community Sets the BGP community attribute. set ip next-hop Sets the next-hop attribute of a route.
Page 570: Handling Access Lists
BSR 2000 Configuration and Management Guide Release 1.0 Handling Access Lists An access list is a sequential collection of permit and deny conditions. The BSR tests conditions one-by-one against conditions in an access list. The BSR supports the following two types of access-lists:...
Page 571: Configuring An As Path Access List
Release 1.0 Configuring BGP MOT(config)#access-list 4 permit any Note: Any type of list always has an assumed deny all entry as the last statement. If there are no matches at the end, the route or match (depending on the type of list and/or how it is used) is denied. The following commands, also executed in Global Configuration mode, enable BGP, specify an AS, and apply Access List 4 to a neighbor.
Page 572: Creating A Community List
BSR 2000 Configuration and Management Guide Release 1.0 MOT(config)#ip as-path access-list 2 deny _690 MOT(config)#ip as-path access-list 2 permit.* The next command, executed in Global Configuration mode, enables BGP and specifies an AS. MOT(config)#router bgp 100 The following commands, executed in Router Configuration mode, define two neighbor peers, and assign the AS path list to one of the neighbor BGP peers.
Page 573 Release 1.0 Configuring BGP Figure 12-18 details creating a route map based on the network in which Router Boston sets the value of the local preference attribute based on the value of the community attribute. Any route that has a community attribute of 100 matches community list 1 and has its local preference set to 50.
Page 574 BSR 2000 Configuration and Management Guide Release 1.0 community-list-number identifies the community list. permit indicates accept the advertisements. deny indicates reject the advertisements. internet is the name of the Internet community. 4. To create a community list that accepts or rejects advertisements with "No-Advertise"...
Page 575 Release 1.0 Configuring BGP community-numbers is a number that identifies a community. no-export is the name of a well-known community. no-advertise is the name of a well-known community. local-as indicates the well-known community Local-AS. internet is the name of the Internet community. AS 200 160.30.0 3.3.3.1...
Page 576 BSR 2000 Configuration and Management Guide Release 1.0 Example This example uses a community list to filter routes based on the local preference. The following commands, executed in Global Configuration mode, define a community list. Specify community list 1 to permit routes from AS 100 and community list 2 to...
Page 577: Redistributing Routes Into Bgp
Release 1.0 Configuring BGP Redistributing Routes into BGP Each routing protocol uses different metrics to transfer routes. Some protocols use hop count metrics, while others use bandwidth and delay attributes to define metrics. When a specific route is redistributed from one routing protocol or domain into another, a common metric must be applied by the receiving protocol.
Page 578 BSR 2000 Configuration and Management Guide Release 1.0 2. Choose from one or more of the following options to redistribute routes from a specified protocol: • Use the redistribute ospf command in Router Configuration mode to redistribute OSPF routes into BGP: MOT(config-bgp)#redistribute ospf {[external | internal] | metric <0-4294967295>...
Page 579: Assigning A Default Metric Value For Redistributed Routes
Release 1.0 Configuring BGP weight <0-65535> sets the network weight value from 0 to 65535 for redistributing RIP routes into BGP. cr is a command return that redistributes all RIP routes into BGP. • Use the redistribute static command in Router Configuration mode to redistribute static routes into BGP: MOT(config-bgp)#redistribute static {metric <0-4294967295>...
Page 581: Configuring Vlan Tagging
Configuring VLAN Tagging Introduction The BSR 2000 normally acts as a IP router, forwarding only IP packets at ISO layer 3 between Customer Premises Equipment (CPEs) attached to DOCSIS cable modems and a network port of the BSR 2000. The VLAN Tagging feature of the BSR...
Page 582 BSR 2000 Configuration and Management Guide Release 1.0 VLAN Tagging represents a major business opportunity for cable operators. Many businesses with multiple branches in the cable operator’s region interconnect their branches to their main office using technolgies such as Frame Relay connections.
Page 583 Release 1.0 Configuring VLAN Tagging Internet Router Layer 2/3 Backbone Internet L2/L3 Switch L2/L3 Switch BSR 1 BSR 2 Home Subscribers Customer A Customer A Branch Main Office Figure 13-1 Transparent LAN Service The home subscribers of the cable operator continue to have all packets routed through an Internet router to the Internet.
Page 584: Vlan Tagging Packet Formats
BSR 2000 Configuration and Management Guide Release 1.0 Each enterprise requires a "per-Enterprise" VLAN implemented on the L2/L3 backbone. In addition, each cable modem configured for bridging requires a "per-CM" VLAN on the connection between the L2/L3 switch and the BSR. The L2/ L3 switch performs inter-VLAN bridging of the per-CM VLANs together into the per-Enterprise VLAN.
Page 585: Enabling Vlan Tagging
Interface Configuration Mode for the Ethernet interface, for example: interface ethernet <X/Y> MOT(config)# where: X/Y is 0/0 for the BSR 2000. 2. Use the bridge mode trunk command to enable VLAN tagging for the network port. bridge mode trunk MOT(config-if)# This configures the port to tag all layer 2 forwarded traffic.
Page 586 If a VLAN tag is not present, the packet will always be routed. The BSR 2000 supports bridging of traffic received from CPEs behind a PacketCable Embedded Multimedia Terminal Adapter (E-MTA) which is registered as a bridging modem.
Page 587: Specifying A Bridging Cable Modem Through A Bridge Mode Tlv
Configuring VLAN Tagging Specifying a Bridging Cable Modem through a Bridge Mode Motorola supports a “Bridge Mode TLV”, in a cable modem’s configuration file, that associates the cable modem’s traffic to a specified VLAN by specifying the cable modem as the Bridging CM. The format of the Bridge Mode TLV is as follows: Motorola vendor-specific TLV –Type = 43...
Page 588: Specifying A Bridging Cable Modem Through The Cli
Bridging Cable Modem through the CLI. The Motorola Bridge Mode TLV is supported by all DOCSIS standard cable modems. A bridging cable modem need not be manufactured by Motorola. An MSO must change the total length and subtype 3 length values specified in the TLV file based on the number of characters in the file’s VLAN Value...
Page 589: Configuring Vlan Stacking On A Bridging Cable Modem
The BSR does not look at the CPE VLAN tag for any information. Enabling VLAN Stacking through an Enhanced Bridge Mode Motorola provides a proprietary enhanced “Bridge Mode TLV”, in a cable modem’s configuration file, that enables VLAN stacking for the corresponding cable modem.
Page 590: Enabling Vlan Stacking Through The Cli
BSR 2000 Configuration and Management Guide Release 1.0 Motorola vendor-specific TLV –Type = 43 –Length = 26 –Subtype=8 –Length=3 –Value=0x08003E –Subtype = 3 –Length = 19 –Value = “vlan:<VLAN identifying number> stackable" Indicates that VLAN stacking is enabled. Enabling VLAN Stacking through the CLI The Command Line Interface (CLI) can be used to enable or disable VLAN stacking.
Page 591: Configuring Vlan Tagged Routing
1. Use the interface ethernet command to navigate to the BSR’s Ethernet interface, as follows: interface ethernet <X/Y> MOT(config)# where: X/Y is 0/0 for the BSR 2000. 2. If not already configured, use the ip address command to define a router interface on the port: ip address <A.B.C.D> <A.B.C.D> MOT(config-if)# where: A.B.C.D is the IP host address of the interface.
Page 592: Configuring The External L2/L3 Switch
BSR 2000 Configuration and Management Guide Release 1.0 3. Use the encapsulation dot1q command to configure a routed VLAN on the BSR’s Ethernet interface, as follows: encapsulation dot1q <2-4094> MOT(config-if)# where: 2-4094 specifies the VLAN ID for routed traffic. Note: The encapsulation dot1q command is applicable only if the corresponding Ethernet interface is configured with bridge mode trunk command.
Page 593: Bridging Packet Sizes
Release 1.0 Configuring VLAN Tagging Bridging Packet Sizes The VLAN Tagging feature will accept upstream Ethernet packets from CPEs up to a maximum size of 1522 bytes from start of the Destination Address to the end of FCS. A maximum size Ethernet packet with a single "inner" 802.1Q tag added by the customer CPE is supported.
Page 594: Clearing Vlan Tagging Statistics
BSR 2000 Configuration and Management Guide Release 1.0 2-4094 is the VLAN ID of the bridging CM to display statistics. The following is typical screen output from the show bridge vlan counters command: VLAN Upstream Upstream Downstream Downstream Packets Discards...
Page 595: A Pre-Defined Modulation Profiles
Pre-Defined Modulation Profiles Introduction This appendix lists the pre-defined modulation profiles supported in Release 4.1.0 of the BSR software. There are 23 default modulation profiles assigned to the TDMA (1-4), MTDMA (101-116), ATDMA (201-205), and SCDMA (301-310) channel types. 526360-001-00 Rev. B MGBI...
Page 596 BSR 2000 Configuration and Management Guide Release 1.0 TDMA ATDMA Modulation Profile 1 Modulation Profile 201 Modulation Profile 2 Modulation Profile 202 Modulation Profile 3 Modulation Profile 203 Modulation Profile 4 Modulation Profile 204 Modulation Profile 205 MTDMA SCDMA Modulation Profile 101...
Page 597 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 1 Cable Modulation Profile 1 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 598 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 2 Cable Modulation Profile 2 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 599 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 3 Cable Modulation Profile 3 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 600 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 4 Cable Modulation Profile 4 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 601 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 101 Cable Modulation Profile 101 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 602 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 102 Cable Modulation Profile 102 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 603 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 103 Cable Modulation Profile 103 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 604 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 104 Cable Modulation Profile 104 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 605 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 105 Cable Modulation Profile 105 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 606 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 106 Cable Modulation Profile 106 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 607 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 107 Cable Modulation Profile 107 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 608 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 108 Cable Modulation Profile 108 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 609 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 109 Cable Modulation Profile 109 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 610 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 110 Cable Modulation Profile 110 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 611 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 111 Cable Modulation Profile 111 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 612 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 112 Cable Modulation Profile 112 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 613 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 113 Cable Modulation Profile 105 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 614 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 114 Cable Modulation Profile 114 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 615 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 115 Cable Modulation Profile 115 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 616 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 116 Cable Modulation Profile 116 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 617 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 201 Cable Modulation Profile 201 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 618 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 202 Cable Modulation Profile 202 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 619 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 203 Cable Modulation Profile 203 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 620 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 204 Cable Modulation Profile 204 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 621 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 205 Cable Modulation Profile 205 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 622 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 301 Cable Modulation Profile 301 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 623 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 302 Cable Modulation Profile 302 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 624 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 303 Cable Modulation Profile 303 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 625 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 304 Cable Modulation Profile 304 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 626 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 305 Cable Modulation Profile 305 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 627 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 306 Cable Modulation Profile 306 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 628 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 307 Cable Modulation Profile 307 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 629 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 308 Cable Modulation Profile 308 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 630 BSR 2000 Configuration and Management Guide Release 1.0 Modulation Profile 309 Cable Modulation Profile 309 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long |...
Page 631 Release 1.0 Pre-Defined Modulation Profiles Modulation Profile 310 Cable Modulation Profile 310 +--------------+------+------+------+------+------+------+------+------+ IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv | | Maint| Maint| Data | Data | Short| Long | UGS | +--------------+------+------+------+------+------+------+------+------+ Modulation...
Page 633 Index 11-9 network, 11-1 11-6 11-9 ABR, 8-12 networks, access control 11-10 route, 4-25 using community name, access list 6-93 BPI, AS-path, 6-93 grace-time, 6-93 permanent, 10-6 name, 6-93 temporary, 10-6 number, application hosting, access policy application image 4-28 creating, 3-65 upgrading, 7-11...
Page 634 BSR 2000 Configuration and Management Guide Release 1.0 13-7 13-9 modifying, Bridge Mode TLV, AS-path broadcast 10-2 access list message, configuring, broadcast address 5-12 assigning scheme, cost broadcast packets 11-7 stub area default summary route, 5-12 directed, 5-12 associating flooded,...
Page 635 Release 1.0 Index characters configuring 2-13 6-19 transposing, a DOCSIS 2.0 upstream logical channel, additional S-CDMA logical channel parameters, 5-20 clear ip route, 6-27 clearing 6-41 an SNR offset, 3-23 buffer, AS-path 6-184 dcc statistics, access list, 5-14 routing table entry, 6-38 automatically repeated SNR tests, 6-184...
Page 636 BSR 2000 Configuration and Management Guide Release 1.0 controlling default power-level 2-13 6-57 case, range, 11-8 6-50 summarization and filtering, returning, 6-56 upstream input power level, default route 5-14 copying setting, 6-73 a modulation profile, default router 5-13 creating definition,...
Page 637 EGP, 6-131 configuring, 7-26 Electronic Surveillance, DOCSIS 2.0 6-22 and the BSR 2000, Element ID, 6-22 BSR 2000 hardware support for, enabling 6-23 BSR 2000 software support for, 6-47 downstream data transmission rate-limit, 6-19 capabilities, 5-17 ICMP netmask reply, 526360-001-00 Rev. B...
Page 638 BSR 2000 Configuration and Management Guide Release 1.0 6-163 OSPF flap lists, 11-19 6-166 MD5 authentication, troubleshooting, 6-76 power adjustment, 5-12 flooded broadcast packets, 6-47 rate-limiting function, forcing SNMP, 6-80 packet fragmentation, 4-12 traps, forwarding 6-59 upstream data transmission rate-limit,...
Page 639 Release 1.0 Index 2-17 5-15 context-sensitive, Internet Control Message Protocol, 2-17 obtaining, Internet Group Management Protocol (IGMP), 2-15 9-12 history buffer, 9-10 9-11 host-query messages, 10-2 hop count, 9-11 querier timeout interval, host 9-10 version, 10-2 route, 7-22 Internet Key Exchange (IKE), host authorization 7-16 Internet Protocol Security (IPSec),...
Page 640 BSR 2000 Configuration and Management Guide Release 1.0 2-12 Left Arrow, Gateway description, 6-93 life-time, Media Server (MS) description, 5-12 limited broadcast packets, message link state 10-2 broadcast, 11-18 update packet, metric link state advertisement setting, 11-18 retransmission, metric type...
Page 641 Release 1.0 Index multicast audio, 10-2 addressing, music, video, multicast group, optional packet count Multimedia Terminal Adapter (MTA) 5-18 setting, description, OSPF 10-7 multiple-packet RIP update, area ID 11-1 defining, area parameter 11-5 configuring, navigating 11-1 configuring, 2-12 command line, 11-19 designated network router, network...
Page 642 BSR 2000 Configuration and Management Guide Release 1.0 10-4 6-76 Version 2, disabling, 6-76 enabling, packet cable standards, 6-55 power level, packet fragmentation 6-45 parameter, 6-80 forcing, pre-defined modulation profiles, PacketCable 7-17 description, Pre-shared Key, PacketCable Multimedia Privileged EXEC mode,...
Page 643 6-56 RF output upstream frequency, 5-15 Router Discovery Protocol, 6-56 setting, routers RF Sentry 11-1 internal, 6-32 using on the BSR 2000, routes 6-36 using to measure SNR, 8-12 redistributing, 2-12 right arrow key, routing centralized, 10-2 and distance vector routing,...
Page 644 BSR 2000 Configuration and Management Guide Release 1.0 6-124 information, displaying, status set statements, 5-22 displaying, setting routing table entry 6-93 Authorization Key, 5-14 clearing, BGP community attribute, BGP origin, 2-15 command history buffer size, 5-13 5-14 default route, 6-28...
Page 645 Release 1.0 Index 4-25 4-10 configuring, specific trap types, 4-11 context specific trap versions, 4-31 configuring, 6-142 spectrum data collection, enabling, 6-135 spectrum groups, 4-32 monitoring, 6-134 spectrum management, server identification 4-24 configuring, spectrum power density maintenance support for, 6-27 configuring for a logical channel, traps standards...
Page 646 BSR 2000 Configuration and Management Guide Release 1.0 13-1 security access, trunk, 2-12 tab key, ucc statistics 6-184 clearing, 6-183 displaying, 10-2 route, UCD message transmission interval TCP, 6-81 setting, TCP/IP, 10-2 UDP, 2-16 up arrow key, 6-94 grace-time, grace-time value...
Page 647 Release 1.0 Index upstream range-backoff default 6-78 resetting, 10-2 User Datagram Protocol, 2-16 User EXEC mode, user models 4-28 creating, USM security 4-28 configuring, VACM security 4-28 configuring, verifying 6-47 downstream rate-limiting status, 6-15 host authorization, 6-92 6-200 maximum CPE host number, 6-89 synchronization message interval, viewing...
Page 650 Visit our website at: www.motorola.com 526360-001-00 Rev. B 7/06 MGBI...

This manual is also suitable for:

Bsr 64000

Motorola BSR 2000 Configuration And Management Manual

Preface

1 Introduction

2 Using the Command Line Interface

3 Configuring the System

4 Configuring SNMP

5 Configuring Interfaces and TCP/IP Features

6 Configuring the CMTS

Quick Links

Troubleshooting

Related Manuals for Motorola BSR 2000

Summary of Contents for Motorola BSR 2000