BSR 64000 Configuration and Management Guide
Notice Copyright © 2002 Motorola, Inc. All rights reserved No part of this publication my be reproduced in any form or by any means or used to make and any derivative work (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.
Contents Preface Scope xxi Audience xxi Documentation Set Conventions xxi xxii Notes, Cautions, Warnings Contacting Support 1 xxiii xxiv Introduction Overview 1-1 Multiservice Support 1-1 Network Management and Control 2 1-2 Using the Command Line Interface Overview 2-1 Using a Terminal Session to Access the BSR Using a Telnet Session to Access the BSR Command Mode Access 2-3 User EXEC Mode 2-5 Privileged EXEC Mode Global Configuration Mode 2-1 2-2 2-5 2-5 iii
BSR 64000 Configuration and Management Guide Interface Configuration Mode 2-6 Router Configuration Mode 2-6 Route Map Configuration Mode Cable Spectrum Group Mode Disabling and Resetting Features Using Command Aliases Obtaining Help 2-6 2-7 2-8 2-9 2-10 Context-sensitive Help 2-11 Using the Command History 2-11 Setting the Command History Buffer Size Recalling Commands 2-11 2-12 Disabling the Command History Feature Editing Features 2-12 2-13 Navigating the Command Line 2-13 Completing
Contents Defining a Privilege Level 3-9 Defining a Group Access Level 3-9 Verifying Your User Account Login Configuration Configuring Interfaces 3-10 3-10 Specifying System Time Information Configuring System Log Parameters 3-11 3-11 Configuring Logging for a Remote Syslog Server Configuring Console Logging Setting the Logging Buffer 3-12 3-14 3-15 Clearing the Buffer 3-16 Restricting Logging Rates and SNMP Traps 3-16 Setting the Recording Mechanism for CMTS Reports 3-17 Returning to the
BSR 64000 Configuration and Management Guide Downloading Software to a Specific Module 3-40 Specifying the System Image File Boot Location Specifying System Information 3-42 3-42 Configuring SRM and Chassis Alias Information 3-43 Configuring SRM and Chassis Asset ID Information 3-43 Configuring SRM and Chassis Serial Number Information Saving and Viewing Your Configuration Reseting BSR Modules 3-45 Monitoring the System 3-45 3-44 Displaying System Processing Information 3-46 Displaying Syst
Contents Associating Groups to MIB Views Configuring an SNMP Context Configuring Packet Size 4-21 4-21 4-22 Configuring SNMP Traps Enabling Traps 4-23 4-23 Configuring a Trap Destination 4-23 Specifying the Destination IP Address Specifying Specific Trap Types Specifying SNMP Trap Versions Restricting Trap Rates Monitoring SNMP 5 4-24 4-25 4-25 4-26 4-27 Configuring Interfaces and TCP/IP Features Overview 5-1 About TCP/IP Level Features 5-1 Setting IP Interface Addresses 5-2 Removing an
BSR 64000 Configuration and Management Guide Managing the Router 5-25 Enabling IP Source Routing IP Accounting 5-25 5-26 Clearing Interface Counters Clearing IP Routes 5-28 5-28 Clearing the ARP Cache Clearing IP Traffic 5-29 5-29 Clearing DNS Entries 5-29 Gathering TCP/IP Related Information 6 5-29 Configuring the CMTS Overview 6-1 Initial Cable Interface Configuration Tasks 6-1 Setting the IP DHCP Relay Functions 6-2 Configuring the Cable Helper and IP Helper Addresses Enabling Host
Contents Testing RF Carrier Modulation Configuring an Upstream Channel 6-19 6-19 Initial Upstream Configuration Tasks 6-21 Setting the Upstream Frequency 6-21 Setting the Upstream Power Level 6-22 Applying an Upstream Modulation Profile Enforcing the Upstream CM Rate Limit Enabling an Upstream Port Managing the Upstream Channel 6-24 6-25 6-26 6-27 Configuring Upstream CM Registration Parameters 6-27 Adjusting for Physical Delay between Cable Interface and CMs Activating Upstream Forward Error
BSR 64000 Configuration and Management Guide Setting QoS Parameters 6-54 Initiating a DSA 6-54 Initiating a DSC 6-55 Initiating a DSD 6-56 Viewing QoS Information 6-57 Displaying the Packet Classifier 6-57 Displaying SFID and QoS Information Displaying Service Flow Statistics 6-59 6-59 Displaying Payload Header Suppression Entries Implementing Spectrum Management 6-60 Configuring a Spectrum Group 6-61 Creating a Spectrum Group 6-60 6-62 Scheduling the Availability of a Spectrum Group B
Contents Viewing Flap List Statistics to Identify Network Health Interpreting Flap List Statistics Tips for Administering Flap Lists Managing Multicast Maps 6-101 6-106 6-107 Pinging a Cable Modem at the MAC Layer Resetting the Cable Modem 6-108 6-109 Clearing Cable Interface Counters 6-111 Gathering DOCSIS Network Information 6-111 Displaying Cable Interface Statistics 6-112 Displaying Downstream Parameters 6-114 Viewing Downstream Port Information Displaying Upstream Parameters Viewing CM
BSR 64000 Configuration and Management Guide Defining the Route 7-16 Enabling Policy-Based Routing on an Interface 7-18 Enabling Local Policy-Based Routing on a Router Gathering Routing Policy Information 8 7-18 7-18 Configuring IP Multicast Routing Overview 8-1 Enabling IP Multicast Routing on the BSR Configuring PIM 8-2 8-2 About PIM Enabling PIM 8-2 8-3 Delaying Shortest Path Tree Usage for Better Throughput Defining the PIM Domain Border Configuring Candidate BSRs Configuring Candidate R
Contents Configuring IGMP on an Interface About IGMP 8-16 8-16 Enabling IGMP 8-17 Controlling Access to IP Multicast Groups Changing the IGMP Version 8-17 8-18 Modifying the IGMP Host-Query Message Interval 8-18 Specifying the IGMP Querier Time-out Interval 8-19 Changing the Maximum Query Response Time 8-19 Configuring the BSR as a Static Multicast Group Member Managing IP Multicast Routing on the BSR 8-20 Configuring an IP Multicast Static Route 8-21 Changing the Distance for a Unicast M
BSR 64000 Configuration and Management Guide Enabling RIP Authentication 9-38 Configuring Interpacket Delay Configuring Timers 9-38 9-39 Example 9-40 Configuring a Passive Interface for RIP Redistributing Routes into RIP 9-40 9-41 Assigning a Default Metric Value for Redistributed Routes Gathering RIP Information 10 Configuring IS-IS Overview 10-1 Enabling IS-IS 10-1 Redistributing Routes into IS-IS 10-4 Assigning a Default Metric Value for Redistributed Routes Managing IS-IS on the BSR
Contents Displaying IS-IS Database Information 10-16 Displaying the Shortest Path First Log 10-17 Displaying Connectionless Network Service Information 11 10-19 Configuring OSPF Overview 11-1 Specifications Enabling OSPF 11-1 11-2 Redistributing Routes into OSPF 11-3 Assigning a Default Metric Value for Redistributed Routes Configuring OSPF Area Parameters 11-5 Configuring OSPF Area Authentication Parameters Configuring OSPF Stub Areas 11-5 11-6 Configuring OSPF Not So Stubby Area 11-8
BSR 64000 Configuration and Management Guide 12 Displaying OSPF Interface Information 11-27 Displaying OSPF Memory Information 11-28 Displaying OSPF Database Information 11-29 Configuring BGP Overview About BGP 12-1 12-1 BGP Peers 12-4 BGP Updates 12-4 BGP Sessions 12-4 Specifications 12-5 Configuring Basic BGP Connectivity 12-5 Configuring a BGP Neighbor 12-5 Advertising Networks in an AS 12-7 Configuring Advanced BGP Connectivity 12-9 Configuring BGP Peer Groups 12-10 Configuri
Contents Enabling and Disabling Synchronization 12-32 Configuring BGP Administrative Weights Using a Route Map 12-34 12-36 Using an AS Path Access List Adjusting BGP Timers 12-37 12-37 Setting the Administrative Distance for a Route Disabling Route Summarization 12-40 Configuring Aggregate Addresses 12-42 Assigning an Interface to BGP Session Configuring a Default Route Configuring BGP Update Flows 12-44 12-46 12-48 Configuring BGP Path Selection Algorithm BGP Path Selection Algorithm Config
BSR 64000 Configuration and Management Guide Configuring a Virtual IP Address 13-3 Specifying Authentication String 13-3 Configuring Primary IP Address 13-4 Enabling a Virtual Router 13-5 Configuring Authentication Type Managing VRRP on the BSR Specifying Priority 13-5 13-6 13-7 Pre-empting a Master 13-8 Specifying Advertisement Interval Clearing Statistic Counters 13-8 13-9 Gathering Virtual Router Information 13-10 Monitoring Critical Link State 13-10 Monitoring Virtual Router Informa
Contents Configuring SONET Alarms 14-15 Setting Alarm Thresholds Setting Alarm Reporting 14-16 14-17 Setting the Line Alarm Indication Signal Changing the POS Signal Rate 14-18 14-19 Specifying the POS Loopback Mode Type Gathering POS Network Information 14-20 14-21 Displaying PPP Link and Statistics Information Displaying POS Interface Information 14-21 14-22 Displaying Physical SONET Link and Alarm Information 14-25 Index xix
Preface Scope This document describes how to install and configure the Motorola™ Broadband Services Router™ 64000 (BSR 64000™). Audience This document is for use by those persons who will install and configure the BSR 64000™ product. Only trained service personnel should install, maintain, or replace the BSR 64000.
BSR 64000 Configuration and Management Guide • BSR 64000 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.
Preface Convention Example Explanation bold text cable relay-agent-option Boldface text must be typed exactly as it appears. brace brackets {} page {on | off} Brace brackets enclose required text. The example indicates you must enter either on or off after page. The system accepts the command with only one of the parameters. When entering the text, do not type the brace brackets.
BSR 64000 Configuration and Management Guide Warning: This symbol indicates that dangerous voltages levels are present within the equipment. These voltages are not insulated and may be of sufficient strength to cause serious bodily injury when touched. The symbol may also appear on schematics. Contacting Support Use the following information to contact Support: U.S. 1-888-944-HELP 1-888-944-4357 xxiv International +.215-323-0044 WWW http://www.gi.com/BUSAREA/CUSACC/websupport.
1 Introduction
Introduction Overview The BSR 64000™ system gives broadband carriers a competitive edge for defining, deploying, and managing broadband services. Based on Data Over Cable Service Interface Specification (DOCSIS) and Packet Cable standards, the BSR carrier-class solution allows Multiple System Operators (MSOs) to offer innovative differentiated data, voice, and multimedia services.
BSR 64000 Configuration and Management Guide • • Virtual Private Networks (VPNs) Application hosting Network Management and Control The BSR offers several management, control, and administration options. The BSR supports Simple Network Management Protocol (SNMP). All appropriate standard MIBs and private MIBs for monitoring and controlling the BSR value-added features are supported. The system supports the File Transfer Protocol (FTP).
2 Using the Command Line Interface
Using the Command Line Interface Overview The BSR 64000™ command line interface (CLI) lets you enter commands at a connected terminal. You use the CLI to perform basic management tasks and to configure protocols and physical layer interfaces for the BSR. For further information on CLI commands, refer to the BSR 64000 Command Reference Guide.
BSR 64000 Configuration and Management Guide Table 2-1 Console Settings Parameter Setting Parity None Stop Bits 1 5. Connect to the BSR. The console terminal session begins. The MOT> prompt displays. 6. To enter Privileged EXEC mode, use the enable command in User EXEC mode, as shown in the following example: MOT>enable The Password: prompt displays. 7. To enter Privileged EXEC mode, press the Enter key at the password prompt. The MOT# prompt displays in Privileged EXEC mode.
Using the Command Line Interface MOT> enable This brings you to Privileged EXEC mode. 4. Press the Enter key at the password prompt. The CLI Telnet session begins. 5. To terminate the Telnet connection and exit the Telnet application when finished, enter exit at the prompt in Privileged EXEC mode. Command Mode Access The available commands depend on the command mode. Table 2-2 describes the basic modes. Figure 2-1 presents a flow chart of the modes.
BSR 64000 Configuration and Management Guide Table 2-2 Command Mode Access, Prompt, and Exit Details Mode Name Access Means Prompt Display Exit Means Interface From Global MOT(config-if)# Configuration Configuration mode, enter any interface command. To return to Global Configuration mode, enter the end or exit command. To return to Privileged EXEC mode, press Ctrl-Z. Router From Global Configuration Configuration mode, enter any router command.
Using the Command Line Interface In Global Configuration mode, you can make changes to the active configuration. If you save the configuration, your changes remain in effect after you reboot the BSR. In Interface Configuration mode, you enable operation features on a per interface basis. In Router Configuration mode, you can enable routing protcol features. User EXEC Mode When you telnet into the BSR, you are in the CLI User EXEC mode. The prompt MOT> indicates User EXEC mode.
BSR 64000 Configuration and Management Guide Interface Configuration Mode You enable features on a per-interface basis. Interface Configuration commands modify the operation of an interface such as an Ethernet port. Interface Configuration commands always follow a Global Configuration command, which defines the interface type.
Using the Command Line Interface Cable Spectrum Group Mode The spectrum management system monitors the upstream signal integrity, and collects upstream spectrum information. In Cable Spectrum Group Mode, you can configure a spectrum group, apply a spectrum group to an upstream port, and evaluate spectrum performance. From Global Configuration mode, enter Cable Spectrum Group mode by entering any cable spectrum-group command. The prompt changes to MOT(config-spcgrp:)#.
BSR 64000 Configuration and Management Guide User EXEC Mode MOT> Console or Telnet MOT>enable Exit Privileged EXEC Mode MOT# Terminates Connection Ctrl Z MOT#configure End Global Configuration Mode MOT(config)# MOT(config)#interface Interface Configuration Mode MOT(config-if)# Ctrl Z MOT(config)#route-map permit/deny Route Map Configuration Mode MOT(config-rmap)# End End Exit Exit MOT(config)#router Router Configuration Mode MOT(config-
Using the Command Line Interface Configuration commands also have a default form, which returns the command setting to its default. Most commands are disabled by default, so the default form is the same as the no form. However, some commands are enabled by default and have variables set to certain default values. In these cases, the default command enables the command and sets variables to their default values. Using Command Aliases You can create your own alias for a command.
BSR 64000 Configuration and Management Guide WORD is the name of the command being replaced by the alias 5. Use the no alias command to delete an alias. For example: MOT(config)#no alias [exec | priv | conf] where: WORD is the alias name for the command The alias is removed for the associated command. Examples The following example creates an alias for the enable command, accessible from the Privileged EXEC mode.
Using the Command Line Interface Context-sensitive Help Display a list of command-associated keywords and arguments by using the context-sensitive help features. To get help for a specific command mode, command, keyword, or argument, use the entries in Table 2-3. Table 2-3 Context-sensitive Help Details Entry Result help Displays brief help system description. ? Displays commands that begin with the abbreviated entry. Do not enter a space before the question mark.
BSR 64000 Configuration and Management Guide MOT>history size [<1-256>] where: 1-256 is the number of lines of the history buffer. Use the no history size command to reset the number of lines saved in the history buffer to the default, ten lines, as shown below: MOT>no history size Recalling Commands To recall commands from the history buffer, perform one of the following actions: • Press Ctrl-P or the up arrow key - Use this action to recall commands, displaying the most recent command first.
Using the Command Line Interface Editing Features You can enter CLI commands in uppercase, lowercase, or a combination of cases. Passwords and some identifiers, such as file names or route maps, are case sensitive. You can abbreviate commands and keywords to a number of characters that represent a unique abbreviation. Enter the command line at the system prompt, and then press the Enter key to execute the command.
BSR 64000 Configuration and Management Guide Table 2-4 Cursor Movement Keys Pressing ... Function Esc B Moves the cursor back one word. Esc F Moves the cursor forward one word. Completing a Partial Command Name Press the Tab key to complete a partial entry. To invoke this feature, enter the first few letters and press the Tab key. This completes the command name.
Using the Command Line Interface Table 2-5 Command Line Control Key Sequences Pressing ... Function Ctrl-R Redisplays the current command line. Left arrow key repeatedly Scrolls back to the beginning of the command entry. Deleting Entries Table 2-6 describes actions to delete command entries. Table 2-6 Deletion Keys Press ... Function Backspace key Erases the character to the left of the cursor. Ctrl-D Deletes the character at the cursor.
BSR 64000 Configuration and Management Guide Table 2-7 Scroll Keys Press ... Function Enter key Scrolls down one line. Space bar Scrolls down one screen. Transposing Characters You can transpose characters by pressing Ctrl-T. This transposes the character to the left of the cursor with the character at the cursor. Controlling Case To capitalize or lowercase letters, use the keys in Table 2-8. Table 2-8 Case Control Keys Press ... Function Esc C Capitalizes the character at the cursor.
Using the Command Line Interface begin indicates to start with the line that matches exclude excludes lines that match. include include lines that match text is the text string to match.
3 Configuring the System
Configuring the System Overview This chapter describes the initial configuration procedures necessary to configure the BSR 64000™ system using its command line interface (CLI). For further information on the CLI commands described in this chapter, refer to the BSR 64000 Command Reference Guide.
BSR 64000 Configuration and Management Guide • • • • Interface IP address(es) and subnet mask(s) Time of Day Server IP address DHCP Server IP address Cable Modem (CM) authentication string or hexadecimal key information contained in the CM configuration file. You must have this information when you configure authentication parameters on the BSR.
Configuring the System For more information on installing the servers, refer to the vendor server software documentation. Accessing the CLI to Set System Passwords Follow these steps to access the CLI from a console session in order to configure password privileges for enabled modes and telnet: Note: Make sure that the serial cable is connected properly and the terminal application is configured correctly. Refer to the BSR 64000 Installation Guide for more information. 1.
BSR 64000 Configuration and Management Guide MOT#configure The MOT(config)# prompt displays. Setting System Passwords System passwords should be set immediately. System passwords can contain up to 31 uppercase or lowercase alphanumeric characters and a numeric character cannot be the first character. Spaces are valid password characters. The user must enter the correct password to gain access to the BSR and privileged-level commands.
Configuring the System WORD is the user-defined unencrypted password for the BSR that is no more than 31 characters. 3. To set the Privileged EXEC password, use the enable password command, as shown below: MOT(config)#enable password {0 | 7} where: 0 indicates that the following password is unencrypted (clear text). 7 indicates that the following password is encrypted. WORD is the user-defined unencrypted password for the BSR that is no more than 31 characters. 4.
BSR 64000 Configuration and Management Guide MOT(config)#show running-config Note: The show running-config command output identifies the system password with the number 0 if it is unencrypted. If the system password is encrypted, it is identified with the number 7. Specifying a Host Name To optionally assign or change your BSR system network name, use the hostname command in Global Configuration mode, as shown below: MOT(config)#hostname where: WORD is the new system network name.
Configuring the System Table 3-1 gives a brief description of each parameter required to configure a user login account. The sections that follow describe the procedural details for defining each parameter. Table 3-1 User Login Account Parameters Parameter Description username Defines the name of the user account. A user name comprises a unique set of up to 16 case-sensitive characters. nopassword Defines no password for the user account. password Defines the password for the user account.
BSR 64000 Configuration and Management Guide Defining a User Name with an Unencrypted Password Follow these steps to define a user account with an unencrypted password: 1. Use the username password command in Global Configuration mode to define an unencrypted password for a user account, as shown below: MOT(config)#username password where: WORD is the user account login name. WORD defines the user login account password.
Configuring the System Defining a Privilege Level To define a privilege level for a user account, use the following command in Global Configuration mode: MOT(config)#username privilege [ro | rw] where: name is the user account login name ro defines a privilege level of read-only that restricts this user to Privileged EXEC command mode access only rw defines a privilege level of read-write that allows this user access to any command mode For example: MOT(config)#username newuser privilege rw Defini
BSR 64000 Configuration and Management Guide For example: MOT(config)#username newuser user-group mso Verifying Your User Account Login Configuration Use the show running-config command in Privileged EXEC mode to verify your user account configuration, as shown below: MOT(config)#show running-config In the following example, user account passwords have not been encrypted: Note: The show running-config command output identifies the user account password with the number 0 if it is unencrypted.
Configuring the System Specifying System Time Information Follow these steps to set system time information: To set the time zone, use the clock timezone command in Global Configuration mode, as shown below: MOT(config)#clock timezone { where: WORD is the name of the time zone. Hours_offset is the number of hours offset from Universal Time Coordinated (UTC); valid entries are -23 to +23 hours.
BSR 64000 Configuration and Management Guide • Logging Your CLI Session to the Syslog Server Configuring Logging for a Remote Syslog Server You can configure up to three remote syslog servers. Follow these steps to configure logging parameters for a remote syslog server: 1. To configure system log parameters for a remote syslog server, use the logging command in Global Configuration mode, as shown below: MOT(config)#logging {} where: A.B.C.
Configuring the System MOT(config)#logging trap {emergencies | alerts | critical | errors | warnings | notifications | informational | debugging} where: emergencies logs emergency conditions where the system is unusable (severity level 0). alerts logs conditions where immediate action is needed (severity level 1). critical logs critical conditions (severity level 2). errors logs error conditions (severity level 3). warnings logs warning conditions (severity level 4).
BSR 64000 Configuration and Management Guide Configuring Console Logging 1. To set the severity level of messages to be logged to the local console, use the logging console command in Global Configuration mode, as shown below: MOT(config)#logging console {emergencies | alerts | critical | errors | warnings | notifications | informational | debugging} where: emergencies logs emergency conditions where the system is unusable (severity level 0).
Configuring the System Setting the Logging Buffer Buffering is used to allow space on the internal logging buffer on the BSR or syslog server for the latest messages. If buffering is enabled, messages are overwritten to allow space for the latest messages when the internal buffer reaches maximum capacity, which is 16 Megabytes. 1.
BSR 64000 Configuration and Management Guide Clearing the Buffer 1. Clear the log using the clear log command in all modes except Privileged EXEC mode, as shown below: MOT#clear log 2. Use the show log command to verify that the log has been cleared, as shown below: MOT(config)#show log Restricting Logging Rates and SNMP Traps You can restrict logging rates and SNMP traps to save space on your device. When the rate of logging messages exceeds the configured limit, logging stops.
Configuring the System MOT(config)#logging rate-limit auto-restart Note: To disable rate limitations, use the no logging rate-limit command in Global Configuration mode. Setting the Recording Mechanism for CMTS Reports Refer to Table 3-2 and Table 3-3 for the available logging options used with the logging reporting command in Global Configuration mode.
BSR 64000 Configuration and Management Guide Table 3-2 Logging Report Options Report Description informational Logs informational descriptive system information (severity level 6). debugging Logs debugging messages (severity level 7). Table 3-3 describes the location where report messages are logged: Table 3-3 Report Location Options 3-18 Report Location Description all-clear Unsets all logging locations for the report. all-set Sets all logging locations for the report.
Configuring the System Returning to the Default CMTS Log Reporting Configuration If you want to return to the default CMTS log reporting configuration, use the logging reporting default command in Privileged EXEC mode, as shown below: MOT#logging reporting default Logging Your CLI Session to the Syslog Server Use the logging session command in Privileged EXEC mode to log your CLI session to your syslog server, as shown below: MOT#logging session Sending Messages to BSR Users Use the following commands to
BSR 64000 Configuration and Management Guide Example The following example configures a MOTD. The pound sign (#) is the delimiting character. MOT(config)#banner motd The router will be rebooted at 12 a.m. Use the no motd command to delete the MOTD banner. Configuring Server Related Parameters This chapter describes how to configure server-related parameters on the BSR in order to establish proper communication between the BSR and the different types of servers that are connected to the BSR.
Configuring the System The DHCP client-server protocol enables devices on an IP network (the DHCP clients) to request configuration information from a DHCP server. DHCP Relay configures the BSR to forward UDP broadcasts, including IP address requests, from DHCP clients.Configure the BSR to be a DHCP relay agent if you have locally attached hosts and a distant DHCP or BOOTP server. To configure the BSR for DHCP relay, do the following: 1. Enter Interface Configuration mode for the Ethernet interface.
BSR 64000 Configuration and Management Guide 6. Verify that the information was entered correctly by displaying the running configuration in Privileged EXEC mode. 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 the System where: name is the default domain name. For example: MOT(config)#ip domain-name motorola.com Enabling Domain Lookup and Domain List DNS servers provide forward lookups, which determine the IP address of a provided device name. This is the most common kind of lookup performed. DNS servers also provide a domain list function which completes unqualified host names. 1. To enable IP domain name system hostname translation, use the ip domain-lookup command in Global Configuration mode.
BSR 64000 Configuration and Management Guide • • Starting the LDAP client Specifying the start of the search-tree 1. Use the ldap server command in Global Configuration mode to configure a primary or secondary LDAP server address, as shown below: MOT(config)#ldap server primary port <1-1024> where: A.B.C.D is the LDAP server IP address. 1-1024 is the port number of the LDAP server. For example: MOT(config)#ldap server primary 192.168.1.
Configuring the System 3. To specify the portion of the LDAP tree where the configuration is located, use the ldap search-base command in Global Configuration mode. MOT(config)#ldap search-base where: WORD is the distiguished location name of entry from which to start a search. 4. Verify that the information was entered correctly by displaying the running configuration in Privileged EXEC mode.
BSR 64000 Configuration and Management Guide 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. 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.
Configuring the System 6. Configure a key number for trusted time sources with the sntp trusted-key command in Global Configuration mode. For SNTP, configure the keys you are allowed to use when you configure the BSR to synchronize its time with other systems on the network. MOT(config)#sntp trusted-key <1-4294967295> where: 1-4294967295 is the key number for the trusted time sources. 7. To display information about SNTP, use the show sntp command in Privileged EXEC mode. MOT#show sntp 8.
BSR 64000 Configuration and Management Guide domain is the Domain Name Server (DNS, 53). netbios-dgm is the NetBios datagram service (138). netbios-ns is the NetBios name service (137). tacacs is the TAC Access Control System (49). tftp is the Trivial File Transfer Protocol (69). time is the Time (37) cr is a command return enables the forwarding of UDP broadcasts out the default port. You can forward the following protocols: For example: MOT(config)#ip forward-protocol udp 35 2.
Configuring the System Configuring FTP Access You can configure the BSR to transfer files between systems on the network using the Internet File Transfer Protocol (FTP). FTP is typically used to transfer upgrade files from an FTP server on the network to the BSR. To configure FTP connections on the BSR, you must specify the FTP username and password that the BSR must use when contacting the FTP server. Follow these steps to configure FTP Access on the BSR: 1.
BSR 64000 Configuration and Management Guide Enabling the RADIUS Client on the BSR Remote Authentication Dial In User Service (RADIUS) provides additional secure remote network access through authentication, authorization and accounting services. The BSR 64000 uses a RADIUS client to authenticate user login information (passwords) stored on the remote RADIUS server. The RADIUS client feature is off by default.
Configuring the System Hostname is the hostname of the remote RADIUS server. 0-65535 is the optionally defined UDP port for the RADIUS authentication server. The default port is 1812. cr is a command return that configures the RADIUS server host without a UDP port designation. 3.
BSR 64000 Configuration and Management Guide • Use the radius-server timeout command in Global Configuration mode to configure the wait time interval for when there is no response from the server before retransmitting to the RADIUS server, as shown below: MOT(config)#radius-server timeout <0-1000> where: 0-1000 is the wait time interval in seconds. The default value is 5 seconds.
Configuring the System where: LINE is the text message for the failed login and authentication. cr is a command return specifies the default failed loging and authentication message. 3. Use the console authentication radius username command in Global Configuration mode to configure a username for RADIUS client authentication for console session access to the BSR, as shown below: MOT(config)#console authentication radius username {} where: WORD is the username. 4.
BSR 64000 Configuration and Management Guide 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.
Configuring the System 2. If you need to free additional memory space in NVRAM by deleting any unwanted files, use the delete nvram: command in Privileged EXEC mode, as shown below: Caution: Ensure that you do not delete the current start-up configuration. Also ensure that you do not delete any necessary application, or boot image files. MOT#delete nvram: where: file is an application or boot image file. For example: MOT#delete nvram:image_file.Z 3. Press the Enter key when asked for confirmation.
BSR 64000 Configuration and Management Guide 6. Ensure that the correct FTP username is configured on the BSR 64000 for communication with the FTP server. If the required FTP user name is not displayed in the running configuration or is incorrect, use the ip ftp username command in Global Configuration mode as shown below: Note: If you have a TFTP server, you do not need to set a user name or password on the BSR.
Configuring the System Follow these steps to download an image file to NVRAM on the SRM: Note: The following steps describe the process of transferring the new image files from an FTP server to the SRM. If you are using FTP to transfer the image files, ensure that the FTP username and password are set correctly on the BSR 64000 using the ip ftp username and ip ftp password commands.
BSR 64000 Configuration and Management Guide 5. Compare each image file size (in bytes) in NVRAM on the SRM to the original size of each image file size on the server. To view the new image files in NVRAM on the SRM, use the dir command in Privileged EXEC mode as shown below: MOT#dir The following command output displays: 6. If the image file byte counts in NVRAM on the SRM match the image file byte counts on the server, the image files on the SRM have been copied successfully.
Configuring the System 4. The Destination file name prompt displays with the new file name. Press the Enter key to accept the new file name in flash memory. For example: Destination file name [ image_file.Z ]? The file is successfully copied to flash memory on the SRM module. Note: You can optionally rename the image file name stored in NVRAM on the SRM module. If you decide to enter a new file name in NVRAM on the SRM, enter the new file name after the Destination file name prompt.
BSR 64000 Configuration and Management Guide file is the name of the operating image intended for download, such as the application image file or boot image file. For example: MOT#download runtime nvram:image_file.Z Downloading Software to a Specific Module The download slot command lets you specify an image stored in either Nonvolatile Random Access Memory (NVRAM) or flash memory, and download it to a resource module installed in a specified chassis slot of the BSR 64000.
Configuring the System • If you want to download the executable file stored in the application image file to a particular module, use the download slot elf command in Privileged EXEC mode as shown below: MOT#download slot elf where: NUM is the module slot number of any available module.
BSR 64000 Configuration and Management Guide Specifying the System Image File Boot Location Follow these steps to specify the system image file for use when starting the BSR: 1. The show boot command can be accessed from all CLI modes except User EXEC mode. Use the show boot command to determine the current boot location for the application image. For example: MOT#show boot Boot location currently set to nvram:image_file.Z 2.
Configuring the System Configuring SRM and Chassis Alias Information To configure your alias name for the SRM module, use the srm alias command in Privileged EXEC mode, as shown below: MOT#srm alias where: string is the SRM alias name. To configure your alias name for the BSR 64000 chassis, use the chassis alias command in Privileged EXEC mode, as shown below: MOT#chassis alias where: string is the BSR 64000 alias name.
BSR 64000 Configuration and Management Guide string is the BSR 64000 asset ID number. Configuring SRM and Chassis Serial Number Information To configure the serial number assigned to your SRM module, use the srm serial-num command in Privileged EXEC mode, as shown below: MOT#srm serial-num where: string is the SRM module serial number.
Configuring the System The configuration parameters that you have set should appear in the show running-config command output. Reseting BSR Modules One or all modules on the BSR need to be reset for boot image upgrades, if significant software errors occur on a particular module or accross several modules on the BSR, or in instances where POS modules need to be synchronized.
BSR 64000 Configuration and Management Guide • • Gathering System Information Displaying Module Hardware Information Displaying System Processing Information In the BSR, process and thread are used interchangeably and mean an independent thread of execution.
Configuring the System MOT#show process msg-q-info Figure 3-2 shows the show process msg-q-info output information: Figure 3-2 show process msg-q-info Command Output • Issue 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, as shown below: MOT#show process stack [procID | procName] where: procID is the task ID number in decimal or hexidecimal form. 0x is required for hexidecimal form.
BSR 64000 Configuration and Management Guide where: NUM is the DOCSIS module slot number. • Issue the show process cpu command in Privileged EXEC Mode to display information about CPU utilization by each process, as shown below: MOT#show process cpu Note: The total utilization is approximate and may not total 100 per cent.
Configuring the System Displaying System Memory Information Follow these options to display BSR system information: • Issue the show memory command in Privileged EXEC mode to show the number of blocks of memory, the hexadecimal address of each block of memory, and the size of each block of memory in bytes, as shown below: MOT#show memory information [brief | slot | <|> | ] where: brief displays only the summary. slot displays memory information for the BSR module slot only.
BSR 64000 Configuration and Management Guide MOT#show memory
where: address is the starting memory address expressed in hexadecimal notation to dump memory. size is the number of bytes to dump. • Issue the show memory fastpath [brief] command in Privileged EXEC mode to display the number of bytes used to program the HSIM FastPath, as shown below: MOT#show memory fastpath [brief] where: brief displays the summary only.Configuring the System Figure 3-5 displays the show version command output, which presents the BSR system version information: Figure 3-5 show version Command Output 3-51
BSR 64000 Configuration and Management Guide Displaying System Buffer Information Follow these options to evaluate system buffer information: • Issue the show buffer command in Privileged EXEC mode to display information about the way in which the BSR is buffering data, as shown below: MOT#show buffer Figure 3-6 displays a sample of the show buffer command output: Figure 3-6 show buffer Command Output • Issue the show buffer all command in Privileged EXEC mode to view all memory buffer pools, as show
Configuring the System • Issue the show buffer system command in Privileged EXEC mode to view system physical structures, such as the number of sockets, routes, interface addresses, PCB, and multicast addresses in the system pool, as shown below: MOT#show buffer system Gathering System Information The following sections discuss how to gather system information and learn the current status of the BSR: • • • • Viewing SRM and Chassis Alias Information Viewing the SRM and Chassis Asset ID Information View
BSR 64000 Configuration and Management Guide Viewing the SRM and Chassis Serial Number Information To view the serial number assigned to your SRM, use the show srm serial-num command in Privileged EXEC mode, as shown below: MOT#show srm serial-num To view the serial number assigned to your BSR 64000, use the show chassis serial-num command in Privileged EXEC mode, as shown below: MOT#show chassis serial-num Viewing the Chassis Status The show chassis status command is an important diagnostic tool for lea
Configuring the System Figure 3-7 displays the show chassis status command output for a fully operational BSR 64000: Figure 3-7 show chassis status Command Output Table 3-4 describes the BSR 64000 chassis output fields: Table 3-4 BSR 64000 Chassis Status Field Descriptions Field Description Slot Module slot number from 0 to 15 Type The type of module inserted into the BSR 64000. HSIM indicates either the 8-port Fast Ethernet, POS or Gigabit Ethernet Network Interface modules (NIMs).
BSR 64000 Configuration and Management Guide Table 3-4 BSR 64000 Chassis Status Field Descriptions Field Description UpTime If the system clock has been set using the clock set command, the UpTime field displays the amount of time that the module has been operational. The time is expressed in hh:mm:ss format. LastUpTime If the module is down, the last operational time for the module displays. Success The module booted successfully. Failure The module failed the boot process.
Configuring the System upstream displays information for an upstream port including the upstream modulation type, channel width, frequency, and modulation profile information (i.e minislots, interleave, preamble, etc). downstream displays information for a downstream port including downstream modulation type, frequency (label), and symbol rate. mac displays MAC layer information about the cable interface.
BSR 64000 Configuration and Management Guide Figure 3-8 displays show controllers cable command output for the cable interface, downstream port and upstream ports. Figure 3-8 show controllers cable Command Output • Use the show controllers ethernet command to display the following fast Ethernet module information: MOT#show controllers ethernet {/} where: x is the fast Ethernet module slot number.
Configuring the System y is the Ethernet interface number. Figure 3-9 displays controller information for the Ethernet interfaces on the SRM module: Figure 3-9 show controllers ethernet Command Output • Use the show controllers gigaether command to display the following Gigabit Ethernet module information: MOT#show controllers gigaether {/} where: x is the gigabit Ethernet module slot number. y is the gigabit Ethernet interface number.
4 Configuring SNMP
Configuring SNMP Overview This chapter describes the commands used to configure SNMP for managing the BSR 64000TM 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.
BSR 64000 Configuration and Management Guide 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 4-2 Command Description Value Default snmp-server access Define SNMP Access Policy information. Enter the SNMP access group name and information. Not configured snmp-server chassis-id Define chassis 1 to 255 alphabeticID to uniquely numeric characters.
Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server docs-trap-control Set SNMP DOCSIS traps. cmtsBPKMTrap cmtsBpiInitTrap cmtsDCCAckFailTrap cmtsDCCReqFailTrap cmtsDCCRspFailTrap cmtsDynServAckFailT ap cmtsDynServReqFailTrap cmtsDynServRspFailTrap cmtsDynamicSATrap cmtsInitRegAckFailTrap cmtsInitRegReqFailTrap cmtsInitRegRspFailTrap Not configured snmp-server enable Enable SNMP Traps, informs, or traps, informs, or coexistence coexistence.
BSR 64000 Configuration and Management Guide Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server notify Configure the 1. Specify the first RowStatus {} notification table. octet-string, which is active. {} [inform | specifies the notification trap] [nonvolitile | name. volitile] [active | 2. Specify the second not-in-service | ] octet-string, which specifies the notification tag. 3.
Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description snmp-server Configure notify-filter snmpNotifyFilter {} {} table. { [included | excluded] [nonvolitile | volitile] [active | not-in-service | ] Value Default 1. Specify the first Not octet-string, which configured. specifies the snmpNotifyFilter table profile name (index #1). 2.
BSR 64000 Configuration and Management Guide Table 4-1 snmp-server Commands (continued) Command Description snmp-server Configures the notify-filter profile snmpNotifyFilter {} { subtree profile. [included | excluded] [nonvolitile | volitile] [active | not-in-service | ] Value Default 1. Specify the Not snmpNotifyFilter configured. subtree (index #2) OID, which defines the family of included and excluded subtrees. 2.
Configuring SNMP Table 4-1 snmp-server Commands (continued) Command Description Value Default snmp-server shutdown Shuts down the N/A SNMP Agent, thus preventing it from processing incoming SNMP packets, but retains all SNMP configuration data in the event the agent is restarted. Disabled snmp-server sysname Define system name information by writing to the sysName MIB object. SNMP system name Not configured snmp-server target-params Configure the snmpTarget-para ms table (rfc2573).
BSR 64000 Configuration and Management Guide Enabling SNMP To configure SNMP, enable the SNMP server using the snmp-server enable command, as shown below: 1. Use the snmp-server enable command in Global Configuration mode to enable SNMP Server operation with traps, or informs, as shown below: Note: Different SNMP versions can coexist. MOT(config)#snmp-server enable {informs | traps} where: informs enables SNMP Informs. traps enables SNMP Traps.
Configuring SNMP • • • • • • Local SNMP name (Engine-ID) (only if not already configured) SNMP User SNMP Group SNMP Access Policy SNMP View SNMP Context (only if not already configured) Use the CLI to configure an SNMP User, an SNMP Group to associate the user to an access policy, and an SNMP Access Policy. If they are not already configured, configure the local SNMP Engine-ID of the agent and an appropriate SNMP Context. 1. A default local Engine-ID is configured to the MAC address of the SRM.
BSR 64000 Configuration and Management Guide WORD is the desired engine name. Note: If you have configured SNMP Users and you change the local SNMP Engine-ID, you must also update the users to use them or delete them and set new ones. 3. The user name is the same user name you specify in a remote network management station (a MIB browser, for example) when you wish to contact the agent via SNMPv3.
Configuring SNMP eng-id specify the engine ID octet string associated with this user. WORD specifies the engine-id with this user; local value of engine ID. public sets the usmUserPublic SNMP object. 4. Assign an SNMP User to an SNMP Group by first configuring an SNMP Group with the user defined in the Group and then assign the Group to an Access Policy. Configuring an SNMP Access Policy assigns SNMP Groups to particular views into the MIB tree and further identifies them with an SNMP version.
BSR 64000 Configuration and Management Guide 6. Configure an SNMP View specifying the desired set of MIB objects. The view is either read, write, or read and write, depending on the SNMP Access Policy configured. Configure an SNMP View entry using the snmp-server view command in Global Configuration mode, as shown below. MOT(config)#snmp-server view {included | excluded} where: name is the desired name of the view. group is the group name or the object identifier (OID) value. 7.
Configuring SNMP name is the SNMP Context name. 9. To view the configuration of SNMPv3 entries, use the show running config command in Privileged EXEC mode, as shown below: MOT#show running config Example 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.
BSR 64000 Configuration and Management Guide • • • 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, as shown below: MOT(config)#snmp-server contact where: text is the system contact name.
Configuring SNMP MOT(config)#snmp-server engineID {local | remote [udp-port ] } Note: For specifying a local engineID, you need not specify the entire 24-character engineID if it contains trailing zeros. You can specify only the portion of the engineID up to the trailing zeros. 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.
BSR 64000 Configuration and Management Guide Configuring SNMP Access Levels Access to an SNMP Server by an SNMP client is determined by a specified access level. You can set access levels using the following methods: • The community name method of access control and View-based Access Control Method (VACM) are used with SNMPv1 and SNMPv2. A community name is a text string used to authenticate messages between a management station and an SNMP client.
Configuring SNMP snmp-server user user-name snmp-server community community-name Create User Model Create Community Name snmp-server group group-name user user-name Create Group Model snmp-server view view-name Create MIB View Associate User Model snmp-server access group-name view-name snmp-server community community-name view-name Associate MIB View to Group Associate MIB View to Community Name SNMPv3 SNMPv1/v2c Figure 4-1 SNMP Access Level Configuration Process 1.
BSR 64000 Configuration and Management Guide 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 not a completely secure access control method. The community string is included in every packet transmitted between an SNMP client and server but is not encrypted, which makes SNMP Get/Set operations potentially accessible to any packet capture software.
Configuring SNMP • • Associating Groups to MIB Views Configuring an SNMP Context 1. To configure a new SNMP User, use the snmp-server user command in Global Configuration mode, as shown below. MOT(config)#snmp-server user [auth {sha | md5} {password | key | local } [priv des56 {password | key | local }] [eng-id ]] where: username is the new SNMP User. password is the assigned password; valid size is up to 64 characters.
BSR 64000 Configuration and Management Guide group-name is the removed SNMP Group name. 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. You create or update an SNMP View entry using the snmp-server view command in Global Configuration mode, as shown below. You can enter this command multiple times for the same view record.
Configuring SNMP The following example creates a view that includes all objects in the MIB-II group except for the Interfaces group: snmp-server view mib-2 included snmp-server view interfaces excluded 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.
BSR 64000 Configuration and Management Guide 2. Use the no snmp-server context command to remove the specified SNMP Context. Note: You must configure a context in conjunction with configuring an access policy. If a prefix name is configured with the snmp-server access command, it should have the same name as the context. Note: If you do not specify a prefix name with the snmp-server access command, you must add a blank context such as snmp-server context.
Configuring SNMP Configuring SNMP Traps SNMP traps are generated according to standard and enterprise MIB specifications. Traps are sent to IP hosts configured in a proprietary Trap Host Table that the SNMP Agent maintains. This section provides information for: • • • Enabling trap generation Configuring trap destinations Restricting trap rates Enabling Traps 1. Use the snmp-server enable traps command in Global Configuration mode to enable SNMP traps, as shown below.
BSR 64000 Configuration and Management Guide Specifying the Destination IP Address 1. Use the snmp-server host command in Global Configuration mode to specify a destination machine to receive SNMP trap information, as shown below. This command is disabled by default, specifying that no notifications are sent. If you enter the snmp-server host command with no keywords, all trap types are sent to the host.
Configuring SNMP 2. Use the no snmp-server host command to remove the specified host. Note: If the community-string is not defined using snmp-server community command prior to using the snmp-server host command, the default form of the snmp-server community command is automatically inserted into the configuration. The password (community-string) used for this default configuration is the same as that specified in the snmp-server host command.
BSR 64000 Configuration and Management Guide port is the UDP port number; valid values are 0 to 65535. If no version keyword is present, the default is version 1. The no snmp-server enable traps command entered with no keywords disables traps, but not informs, to the host. To disable informs, use the no snmp-server enable informs command. Restricting Trap Rates You can restrict the rate of SNMP traps generated to prevent excessive traffic on the network. 1.
Configuring SNMP Monitoring SNMP To monitor the status of SNMP operations on your network and check current SNMP settings, you use a series of show snmp commands. To issue show snmp commands, do the following: 1. Enter the Privileged EXEC or Global Configuration mode. 2. Use the show snmp command to check the status of SNMP communications and access counter information for SNMP operations. Use the show snmp command with the command-name option to access specific SNMP information.
5 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 64000™ system.
BSR 64000 Configuration and Management Guide A datagram is a packet format defined by IP. An IP packet contains the necessary destination address information. A packet-switching network uses the addressing information to switch the packet from one physical network to another, moving it toward its final destination. Each packet travels the network independent of any other packet.
Configuring Interfaces and TCP/IP Features Table 5-1 describes each BSR interface and corresponding module: Table 5-1 BSR Interface and Module Descriptions CLI Interface BSR Module ethernet Supervisory Resource Ethernet interface 0 is a 10 Mbps Module (SRM) located management interface that does not support the negotiation feature and is in slot 7. associated with its corresponding port on the SRM I/O module.
BSR 64000 Configuration and Management Guide Follow these steps to assign an IP address and subnetwork mask to an interface on a module: 1. To identify where the module is in the chassis, use the show chassis status command in Privileged EXEC mode, as shown below: MOT#show chassis status 2. Determine the slot number of the module. 3. Use the configure command in Privileged EXEC mode to enter Global Configuration mode, as shown below: MOT#configure 4.
Configuring Interfaces and TCP/IP Features net-mask is the network mask of the IP network, on which the interface is associated. For example: MOT(config-if)#ip address 10.10.10.135 255.255.255.0 6. To optionally configure a secondary IP address for an interface use the ip address secondary command, in Interface Configuration mode, as shown below: Note: A secondary IP address can be used in some implementations as the loopback interface.
BSR 64000 Configuration and Management Guide The running configuration displays. If the information is not correct, repeat this procedure. Removing an IP Address You can disable IP processing on a particular interface by removing its IP address with the no ip address command. If the router detects another host using one of its IP addresses, it will print an error message on the console. The software supports multiple IP addresses per interface.
Configuring Interfaces and TCP/IP Features where: slot is the 10/100 Ethernet module slot. interface is the Ethernet interface number. 2.
BSR 64000 Configuration and Management Guide slot is the 10/100 Ethernet module slot. interface is the Ethernet interface number. 5. To verify that the information was entered correctly, use the show running-config command in Privileged EXEC mode as shown below: MOT#show running-config The running configuration displays. If the information is not correct, repeat this procedure.
Configuring Interfaces and TCP/IP Features 2. Use the ip address command in Interface Configuration mode to define an IP address for the loopback interface, as shown below: MOT(config-if)#ip address where: A.B.C.D is the IP address of the BSR interface designated for the loopback interface. net-mask is the subnetwork mask of the IP network, on which the interface is associated. 3.
BSR 64000 Configuration and Management Guide Configuring Tunnels on an Interface A tunnel interface is a logical interface that is used to encapsulate various packet types and send them over a created a point-to-point link between two devices at remote points over an IP internetwork. Multi-protocol packets are encapsulated using either IP, GRE, or DVMRP tunnel encapsulation to traverse the link.
Configuring Interfaces and TCP/IP Features 2. Use the ip address command in Interface Configuration mode to define an IP address for the tunnel interface, as shown below: MOT(config-if)#ip address where: A.B.C.D is the IP address of the tunnel interface. net-mask is the subnetwork mask of the tunnel interface. 3.
BSR 64000 Configuration and Management Guide 6. To delete a tunnel source, use the no tunnel source command in Interface Configuration mode, as shown below: MOT(config-if)#no tunnel source 7. To delete a tunnel destination, use the no tunnel destination command in Interface Configuration mode, as shown below: MOT(config-if)#no tunnel destination 8.
Configuring Interfaces and TCP/IP Features 12. To verify the tunnel interface, use the show interface tunnel command in Interface configuration mode, as shown below: MOT(config-if)#show interface tunnel where: n is the tunnel number; valid entries are 0 to 255. Configuring an Unnumbered Interface An unnumbered interface is used in point-to-point connections when an IP address is not required. This enables IP processing on an interface without assigning an explicit IP address to the interface.
BSR 64000 Configuration and Management Guide 4. To enable an interface for data processing without an explicit IP address, use the ip unnumbered command in Interface Configuration mode, as shown below: MOT(config-if)#ip unnumbered {loopback | pos / | serial / | ethernet / gigaether | / } where: loopback is the loopback interface on the POS module. n is the loopback interface from 1 to 16. pos is POS interface the on the POS module.
Configuring Interfaces and TCP/IP Features A.B.C.D is the IP address of the ARP entry, specified in dotted-decimal notation. mac-address is a 48-bit hardware address of the ARP entry. type is the encapsulation type. alias specifies that the software respond to ARP as if it owns the specified address, if proxy arp is enabled. 2.
BSR 64000 Configuration and Management Guide 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. Under proxy ARP, if the router receives an ARP request for a host that is not on the same network as the ARP request sender, and if the router has the best route to that host, the router sends an ARP reply packet giving its own local data link address.
Configuring Interfaces and TCP/IP Features To avoid broadcast storms, use a single broadcast address scheme on a network and set the address to be used as the broadcast address. The BSR can accept and interpret all possible forms of broadcast addresses. Defining Broadcast Address You can use several IP commands to perform broadcast tasks. 1. To define a broadcast address for an interface, use the ip broadcast-address command in Interface Configuration mode.
BSR 64000 Configuration and Management Guide where: size is the MTU size, expressed in bytes; valid entries are 68 to the maximum MTU of the physical interface; default is 1496. Use the no ip mtu command to restore the default MTU size. Note: The MTU depends on the type of physical interface. Configuring Static Routes You can arrange for a router to receive and send traffic by a specific static route, and you can set a default route to reduce the routing table size.
Configuring Interfaces and TCP/IP Features x is the POS module slot number. y is the POS interface number. tunnel is a tunnel interface number from 1 to 255. distance is the administrative distance; default is 1. tag specifies the match to control route-map redistribution. 1-4294967295 is the match value. range indicates an established static route; valid entries are 1 to 65536. 2. To set a default route, use the address 0.0.0.
BSR 64000 Configuration and Management Guide Clearing Route Table Entries To clear dynamic entries from the routing table, use the clear ip route command in Privileged EXEC mode, as shown below. You must specify the IP address of the routes and the mask of the IP address. Use the asterisk (*) to clear all dynamic routes. MOT(config-if)#clear ip route {* | | } where: * is the asterisk character that clears all routes in the routing table. A.B.C.D is the IP address of the route.
Configuring Interfaces and TCP/IP Features With IRDP, each router periodically multicasts or broadcasts router advertisement messages from each of its interfaces. Hosts discover the addresses of routers on the directly attached subnet by listening for these messages. Hosts can use router solicitation messages to request immediate advertisements, rather than wait for unsolicited messages. IRDP offers several advantages over other methods of discovering addresses of neighboring routers.
BSR 64000 Configuration and Management Guide maxadvertinterval is the maximum time between advertisements. number2 is the maximum interval between advertisements, expressed in seconds; valid entries are 4 to 1800; default is 600. minadvertinterval is the minimal time between advertisements, expressed in seconds. number3 is the minimum interval between advertisements, expressed in seconds; valid entries are 3 to 1800; default is 450. multicast indicates advertisements are sent with multicast.
Configuring Interfaces and TCP/IP Features number is the minimum time between IRDP advertisements, expressed in seconds; valid entries are 3 to 1800; default is 450. 6. To send IRDP advertisements with Multicast packets, use the ip irdp multicast command in Interface Configuration mode, as shown below: MOT(config-if)#ip irdp multicast The default is IRDP broadcast. 7.
BSR 64000 Configuration and Management Guide MOT#ping [ | ] [size ] [] [timeout ] [source ] [tos ] [ttl ] [df] where: hostname is the DNS host name. A.B.C.D is an IP address. number1 is the packet size value, expressed in bytes; valid entries are 40 to 65515. number2 is the packet number or request messages sent, between 1 to 65535. timeout is the duration.
Configuring Interfaces and TCP/IP Features where: A.B.C.D is the source IP address. hostname is the Domain Name Server (DNS) hostname. Managing the Router Follow these sections to manage routing operations on the BSR: • • • • • • • • Enabling IP Source Routing IP Accounting Clearing Interface Counters Clearing Interface Counters Clearing IP Routes Clearing the ARP Cache Clearing DNS Entries Clearing IP Traffic Enabling IP Source Routing The BSR examines IP header options on every packet.
BSR 64000 Configuration and Management Guide MOT(config)#ip source-route IP Accounting IP accounting provides basic IP accounting functions. By enabling IP accounting, users can see the number of bytes and packets switched through the software on a source and destination IP address basis. Only transit IP traffic is measured and only on an outbound basis; traffic generated by the software or terminating in the software is not included in the accounting statistics.
Configuring Interfaces and TCP/IP Features 4. To control the number of transit records stored in the IP accounting database, use the ip accounting-transits command, as shown below: MOT(config)#ip accounting-transits where: num is the maximum number of transit entries 5.
BSR 64000 Configuration and Management Guide Clearing Interface Counters To clear a specific or all interface counters, use the clear counters command in Privileged EXEC mode, as shown below. MOT#clear counters [ethernet / cable / | loopback | pos / | gigaether / | tunnel ] where: cable clears the cable interface counters. ethernet clears the Ethernet interface counters.
Configuring Interfaces and TCP/IP Features Clearing the ARP Cache To clear all dynamic entries from the ARP cache, use the clear arp-cache command in Privileged EXEC mode, as shown below: MOT#clear arp-cache Clearing IP Traffic To reset the IP traffic statistics counters to zero, use the clear ip traffic command in Privileged EXEC mode, as shown below: MOT#clear ip traffic Clearing DNS Entries Use the clear host command in Privileged EXEC mode to delete DNS host entries from the host-name-and-address cac
BSR 64000 Configuration and Management Guide mac-address is the MAC address. slot is the Ethernet interface slot number. port is the Ethernet interface port number. 2. Use the show ip interface command to display the current state of all IP interfaces or a specific interface, as shown below. The default is all interface types and all interfaces. MOT#show ip interface ethernet 7/0 [brief] where: brief displays summary information. 3. Use the show ip route command to display the routing table status.
6 Configuring the CMTS
Configuring the CMTS Overview The following sections contain the tasks used to configure and manage your cable network: • • • • • • • • • • • • • • • • Initial Cable Interface Configuration Tasks Configuring a Downstream Channel Configuring an Upstream Channel Bundling Cable Interfaces into a Single IP Subnet Subneting DHCP Clients on the Cable Interface Creating a Modulation Profile Setting Network Parameters for Cable Modems Configuring Baseline Privacy Setting QoS Parameters Implementing Spectrum Mana
BSR 64000 Configuration and Management Guide • • • • • Enabling Host Authorization for All CMs Creating a Static Host Authorization Entry for a Specific CM Enabling Host Authorization for an IP Range of CPEs Using DHCP Lease Query Function to Secure Cable Network Setting ARP Parameters Setting the IP DHCP Relay Functions The IP DHCP relay function is used to forward DHCP messages between clients and servers.
Configuring the CMTS 4. The DHCP server assigns an IP address to each MTA, CM, or CPE that requested an IP address by placing the IP address in the (Your IP Address) yiaddr field in the DHCP packet header. The yiaddr is the IP address to be used by the MTA, CM, or CPE. 5. The DHCP relay agent removes the MTA, CM, or CPE option and forwards the DHCP server reply, containing the IP address to the MTA, CM, or CPE. Follow these steps to configure the DHCP relay option on the BSR: 1.
BSR 64000 Configuration and Management Guide 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. The cable helper address function is used in conjunction with the DHCP relay function.
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, as shown below: MOT(config-if)#cable helper-address mta where: A.B.C.D is the destination DHCP server IP address. 4. The IP helper address necessary for the BSR to forward packets to the DHCP server.
BSR 64000 Configuration and Management Guide 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” an IP address from any legitimate user on the same cable network. A hacker takes the IP address from this user to steal their data service.
Configuring the CMTS Follow these steps to configure and verify a static host authorization: 1. Enter Privileged EXEC mode. 2. Issue the host authorization cpe command in Privileged EXEC mode to create a static entry for a specific CM and CPE in Privileged EXEC mode, as shown below: MOT#host authorization cpe where: mac is the MAC address of the cable modem. mac is the MAC address of the customer premises equipment (CPE). prefix is the IP address of the CPE. 3.
BSR 64000 Configuration and Management Guide 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. This function allows you to specify a partial subnet by allowing CPEs on different cable interfaces to automatically connect to a network.
Configuring the CMTS A CPE with an IP address that is within the start and end range defined by the host authorization range command that is currently connected remains in the host authorization table until it is individually removed by the no host authorization command, or if the BSR is reset. Using DHCP Lease Query Function to Secure Cable Network The DHCP lease query feature provides additional security on the cable network by preventing hackers from stealing service from customers.
BSR 64000 Configuration and Management Guide • Query the DHCP server to verify that one IP address to MAC address binding appears for a CM. If there is more than one IP address to MAC address combination, one IP was assigned by DHCP and the other IP address is statically (manually) set by a hacker. In this instance, only packets sent from the legal source learned through DHCP are forwarded. The DHCP lease query feature can also determine: • • • • If the BSR is replaced or inadvertently rebooted.
Configuring the CMTS 3. Use the show ip traffic command to monitor DHCP lease query statistics, which include the number of active, known, unknown, and unimplemented DHCP packet transmitions. Setting ARP Parameters The Address Resolution Protocol (ARP) is used to build a correlation between the cable network and the connected cable modems (CMs) and customer premises equipment (CPE) by translating the CM and CPE’s MAC address to a logical IP address.
BSR 64000 Configuration and Management Guide 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.
Configuring the CMTS Initial Downstream Configuration Tasks Use the tasks in this section to perform the following basic downstream configuration tasks: • • • Configuring the Downstream Frequency and Modulation Rate Enforcing the Downstream Rate Limit Enabling 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.
BSR 64000 Configuration and Management Guide where: 64 is 64 Quadrature Amplitude Modulation (QAM). 256 is 256 (QAM). To restore the default, use the no cable downstream modulation command in Interface Configuration mode, as shown below: MOT(config-if)#no cable downstream 0 modulation [64 | 256] 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.
Configuring the CMTS 1-4292967295 is the Service Flow Identifier (SFID). cr is a command return, which displays QoS service flow statistics for all SFIDs. Enabling the Downstream Port The downstream port is in an administrative shut-down state by default and must be enabled to function. Follow these steps to enable the downstream port: 1.
BSR 64000 Configuration and Management Guide 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. A higher interleave depth provides more protection from noise on the HFC network, but increases downstream latency. A lower interleave depth decreases downstream latency, but provides less protection from noise on the HFC network. 1.
Configuring the CMTS 0-0 is the downstream port number. To restore the default, use the no cable downstream interleave-depth command in Interface Configuration mode, as shown below: MOT(config-if)#no cable downstream 0 interleave-depth [8 | 16 | 32 | 64 | 128] Setting the Downstream Power Level Follow these options to adjust the downstream power level: • The default downstream power level is 55 decibels per millivolt (dBmV).
BSR 64000 Configuration and Management Guide 2. To enable the downstream port again, use the no cable downstream shutdown command in Interface Configuration mode, as shown below: MOT(config-if)#no cable downstream shutdown 3.
Configuring the CMTS Testing RF Carrier Modulation The downstream carrier-only function is disabled by default and is used for testing purposes only to control downstream output. To optionally enable this test function, use the in Interface Configuration mode, as shown below. MOT(config-if)#cable downstream <0-0> carrier-only where: 0-0 is the downstream port number. To disable the downstream carrier-only function, use the no cable downstream carrier-only command.
BSR 64000 Configuration and Management Guide Table 6-3 describes the upstream parameters: Table 6-3 Upstream Parameters 6-20 Parameter Identification Default Value Channel Width Radio frequency 1,600,000 Hz channel width (1280 ksps) 200000, 400000, 800000, 1600000, 3200000 Hz (160, 320, 640, 1280, 2560 ksps) Data Backoff Initial ranging backoff fixed start and end values Start 2 End 8 Start 0 to 15 End 0 to 15 Automatic FEC Forward Error Correction On On or Off Frequency Center frequency f
Configuring the CMTS Initial Upstream Configuration Tasks Follow these tasks for the initial configuration of the upstream channel: • • • • • Setting the Upstream Frequency Setting the Upstream Power Level Applying an Upstream Modulation Profile Enforcing the Upstream CM Rate Limit Enabling an Upstream Port 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.
BSR 64000 Configuration and Management Guide Setting the Upstream Power Level The cable interface controls CM output power levels to meet the desired upstream port input power level. Input power level adjustments to an upstream port compensate for cable interface signal degradation between the optical receiver and the upstream RF port. You can configure the upstream input power level in either absolute or relative mode.
Configuring the CMTS Setting the Upstream Power Level in Relative Mode Issue the cable upstream power-level default command in Interface Configuration mode to set the upstream input power level in relative mode, as shown below: MOT(config-if)#cable upstream power-level default where: NUM is the upstream port number. offset is the number expressed in dB above or below the default input power level.
BSR 64000 Configuration and Management Guide Setting the Upstream Power Level in Absolute Mode Issue the cable upstream power-level command in Interface Configuration mode to set the upstream input power level in absolute mode, as shown below: Caution: Use caution when increasing the input power level in absolute mode.
Configuring the CMTS MOT#show cable modulation-profile [<1-16> | ] where: 1-16 is a profile group number. cr is a command return, which displays all configured modulation profiles. 3. To apply an upstream modulation profile to an upstream port, use the cable upstream modulation-profile command in Interface Configuration mode, as shown below: MOT(config-if)#cable upstream modulation-profile <1-16> where: NUM is the upstream port number. 1-16 is the modulation profile number.
BSR 64000 Configuration and Management Guide NUM is the upstream port number. To disable the upstream rate-limiting function, use the no cable upstream rate-limit command. 3. To verify that upstream rate-limiting is enabled or disabled on the cable interface, use the show running-config command in Privileged EXEC mode, as shown below: MOT#show running-config 4.
Configuring the CMTS Managing the Upstream Channel The following upstream tasks in this sections are used to manage or improve the performance of the upstream channel: • • • • • • • • • Configuring Upstream CM Registration Parameters Adjusting for Physical Delay between Cable Interface and CMs Activating Upstream Forward Error Correction Activating the Scrambler on the Upstream Channel Enabling Pre-equalization Forcing the Fragmentation of Large Upstream Packets Disabling an Upstream Port Configuring the
BSR 64000 Configuration and Management Guide where: NUM is the upstream port number. To reset the upstream minislot size, use the no cable upstream minislot-size command in Interface Configuration mode, as shown below: MOT(config-if)#no cable upstream minislot-size [2 | 4 | 8 | 16 | 32 | 64 | 128] where: NUM is the upstream port number.
Configuring the CMTS 0-15 is the ranging backoff end value. Use the no cable upstream range-backoff command in Interface Configuration mode to return the range-backoff function to the default, as shown below: MOT(config-if)#no cable upstream range-backoff [automatic | | ] where: automatic prompts the ranging backoff to start and end automatically. NUM is the upstream port number. 0-15 is the ranging backoff start value. 0-15 is the ranging backoff end value.
BSR 64000 Configuration and Management Guide 0-15 is the start value. 0-15 is the end value. To restore the upstream data-backoff default, use the no cable upstream data-backoff command in Interface Configuration mode, as shown below: MOT(config-if)#no cable upstream data-backoff [automatic | <0-15> | <0-15>] where: NUM is the upstream port number. 0-15 is the start value. 0-15 is the end value.
Configuring the CMTS Adjusting for Physical Delay between Cable Interface and CMs The physical delay function is used to adjust the upstream propagation delay threshold between the cable interface and cable modems (CMs). The cable interface adjusts the physical delay function automatically by default. You can use the following options to adjust the physical delay function: • • A single fixed time can be set for physical delay.
BSR 64000 Configuration and Management Guide where: NUM is the upstream port number. automatic indicates adjust the physical delay automatically. 200-1600 is the fixed upstream physical delay value from 200 to 1600 microseconds. Activating Upstream Forward Error Correction The cable interface uses Forward Error Correction (FEC) to correct any corrupt upstream data. FEC is enabled by default and should not be disabled. When FEC is enabled, all CMs on the network also activate FEC.
Configuring the CMTS Activating the Scrambler on the Upstream Channel The scrambler on the upstream channel enables CMs on the HFC network to use built-in scrambler circuitry for upstream data transmissions. The scrambler circuitry improves BSR upstream receiver. The upstream scrambler is enabled by default and should not be disabled. Note: Scrambler must be enabled for normal operation. Disable only for prototype modems that do not support scrambler.
BSR 64000 Configuration and Management Guide where: NUM is the upstream port number. If you need to disable the pre-equalization adjustment, use the no cable upstream pre-equalization command. Forcing the Fragmentation of Large Upstream Packets The cable upstream force-frag command is used as a traffic shaping tool.
Configuring the CMTS Configuring the Upstream Channel Descriptor Follow the steps in this section to configure the upstream channel descriptor (UCD). 1. To disable the upstream channel, use the cable upstream shutdown command in Interface Configuration mode, as shown below: MOT(config-if)#cable upstream shutdown where: NUM is the upstream port number. 2. The default UCD message transmission interval is 1000 milliseconds.
BSR 64000 Configuration and Management Guide • The maximum number of calls is set to 32 by default. Use the cable upstream max-calls command in Interface Configuration mode to configure the maximum number of voice calls for an upstream channel, as shown below: MOT(config-if)#cable upstream max-calls <0-255> where: NUM is the upstream port number. 0-255 is the number of voice calls permitted on the upstream channel.
Configuring the CMTS • You can bundle all cable interfaces into a single bundle to share a single IP subnet. The cable bundling feature requires that the following conditions are observed: • • Cable interface bundling is only supported on cable interfaces. • • • An IP address is only assigned to master cable interface. • Cable upstream and downstream parameters remain unique for each individual cable interface. • Cable interface bundles are configured using CLI commands only.
BSR 64000 Configuration and Management Guide 3. If the IP helper address or cable helper address is not assigned to the master cable interface, use the ip helper-address or cable helper-address command in Interface configuration mode to enable DHCP relay. The ip helper-address or cable helper address specifies the DHCP server. 4.
Configuring the CMTS y is the cable interface number, which is 0. 9. To assign another cable interface as the slave interface, use the interface cable command in Global Configuration mode as shown below: MOT(config)#interface cable / where: x is the slot number of the cable module. y is the cable interface number, which is 0. For example: MOT(config)#interface cable 5/0 10.
BSR 64000 Configuration and Management Guide Adding a Static Arp Entry to a Cable Bundle Interface To optionally add a static arp entry to the cable bundle interface, use the arp cable bundle cable command in Global Configuration mode as shown below: MOT(config)#arp [arpa | snap] cablebundle cable / where: A.B.C.D is the IP address of the ARP entry. H.H.H is the 48-bit MAC address of the ARP entry.
Configuring the CMTS 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, as shown below: Note: The primary IP address for the cable interface is used for CM DHCP requests. MOT(conf-if)# ip address { } secondary {host | mta | } where: A.B.C.D is the IP address. A.B.C.D is the subnetwork IP address mask.
BSR 64000 Configuration and Management Guide 2. To view a specific modulation profile, use the show cable modulation-profile command in Privilege EXEC mode, as shown below: MOT#show cable modulation-profile {<1-16>} where: 1-16 is the profile group number. 3.
Configuring the CMTS Table 6-5 Modulation Profile Parameters and Descriptions Parameter Description 64-256 Preamble length in bits. fixed Handles the FEC for last code word. shortened 4. To remove a modulation profile parameter, use the no cable modulation-profile in Privileged EXEC mode, as shown below: MOT#no cable modulation-profile {<1-16>} where: 1-16 is the profile group number. 5.
BSR 64000 Configuration and Management Guide Enabling the CM Aging Timer The cable modem (CM) aging timer feature is disabled by default. The CM aging timer feature is used to automatically remove off-line CMs from the network after a configured time period.
Configuring the CMTS 0-200 is the insertion interval. 3. To view the insertion interval, use the show cable insert-interval command in Interface Configuration mode, as shown below: MOT(config-if)#show cable insert-interval Setting the Synchronization Interval The synchronization message interval is the interval between successive synchronization message transmissions from the cable interface to the CMs. Follow the steps in this section to set and verify the synchronization interval: 1.
BSR 64000 Configuration and Management Guide To reset the default synchronization message interval, use the no cable sync-interval command in Interface Configuration mode, as shown below: MOT(config-if)#no cable sync-interval {1-200} Setting CM Authentication Parameters The default authentication parameters are enabled, but have a null value by default. Set authentication parameters on the cable interface and the CMs to ensure security on the HFC network. 1.
Configuring the CMTS • If you want to activate CM authentication on the cable interface so that all CMs return a encrypted key to register with the cable interface for network access, use the cable shared-secret 7 command in Global Configuration mode, as shown below: MOT(config)#cable shared-secret 7 where: 7 indicates a hidden hexadecimal key. key is the shared secret key, expressed in hexadecimal notation, for example, 0x434F5453. 2.
BSR 64000 Configuration and Management Guide Denying Access to a Cable Modem Use the cable modem deny command in Privileged EXEC mode to remove a specified cable modem from the network and deny it future entry, as shown below: MOT#cable modem deny where: mac is the MAC address of the cable modem. Use the no cable modem deny command to remove the restriction from the specified cable modem, as shown below: MOT#no cable modem deny where: mac is the MAC address of the cable modem.
Configuring the CMTS 2. To verify the maximum number of hosts setting, use the show cable modem hosts command in Privileged EXEC mode, as shown below: MOT#show cable modem { | } hosts where: mac is the CM MAC address. prefix is the CM IP address. The screen displays the current number of hosts connected to the CM, the maximum number of hosts allowed for the CM, and the host CPE IP addresses behind the CM.
BSR 64000 Configuration and Management Guide Configuring BPI involves the following tasks: • • • Setting TEK Privacy Setting Authorization Key Values Displaying BPI Configuration Settings Table 6-6 describes the BPI parameters.
Configuring the CMTS 2. Use the cable privacy tek life-time command in Interface Configuration mode to configure the global TEK lifetime value, as shown below: MOT(config-if)#cable privacy tek life-time {<30-604800>} where: 30-604800 is the TEK life-time value in seconds (the maximum value is 7 days).
BSR 64000 Configuration and Management Guide 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, as shown below: MOT(config-if)#cable privacy cm-tek life-time {<0-16383>} [<1800-604800> | ] where: 0-16383 is the CM’s primary SID. 1800-604800 is the TEK lifetime value, expressed in seconds. cr is a command return enables the default TEK lifetime value. 5.
Configuring the CMTS 2. Use the cable privacy cm-auth grace-time command in Interface Configuration mode to set an individual grace-time AK value, as shown below: MOT(config-if)#cable privacy cm-auth grace-time <300-3024000> where: mac is the CM MAC address. 300-3024000 is the individual grace-time AK, expressed in seconds (5 minutes to 35 days). 3.
BSR 64000 Configuration and Management Guide Setting QoS Parameters This section describes how to configure Quality of Service (QoS) using service flows. Use the commands in this section to create, change, or delete service flows with Dynamic Service Addition (DSA), Dynamic Service Change (DSC), and Dynamic Service Deletion (DSD) MAC management messages.
Configuring the CMTS 2. Use the show cable qos svc-flow dynamic-stat command in Privileged EXEC mode to display statistics for dynamic service additions, deletions, and changes for both upstream and downstream service flows, as shown below: MOT#show cable qos svc-flow dynamic-stat Initiating a DSC Use a DSC messages to change an existing service flow. The cable interface initiates a DSC for a CM. Note: Before you begin, ensure that the correct DSA definition is entered in the CM configuration file.
BSR 64000 Configuration and Management Guide 3. To display service flow statistics, use the show cable qos svc-flow statistics command in Privileged EXEC mode, as shown below: MOT#show cable qos svc-flow statistics {/} {<1-4292967295> | } where: x is the slot number of the cable module. y is the cable interface number, which is 0. 1-4292967295 is the Service Flow Identifier (SFID) number. cr is a command return, which displays QoS service flow statistics for all SFIDs. 4.
Configuring the CMTS 2. To initiate the DSD of a specific SFID, use the cable modem qos dsd command in Privileged EXEC mode, as shown below: MOT#cable modem qos dsd {/ <1-262143>} where: x is the slot number of the cable module. y is the cable interface number; which is 0. 1-262143 is the Service Flow Identifier (SFID). 3. To display the deleted service flow log, use the show cable qos svc-flow log command in Privileged EXEC mode, as shown below: MOT#show cable qos svc-flow log 4.
BSR 64000 Configuration and Management Guide • The cable interface uses a downstream classifier to assign packets to downstream service flows. • The CM uses an upstream classifier to assign packets to upstream service flows.
Configuring the CMTS Displaying SFID and QoS Information Use the show cable qos svc-flow summary command in Privileged EXEC mode to display service flow identifier (SFID) and QoS parameter information, as shown below: MOT#show cable qos svc-flow summary {/} [<1-4292967295> | ] where: x is the slot number of the cable module. y is the cable interface number, which is 0. 1-4292967295 is the Service Flow Identifier (SFID).
BSR 64000 Configuration and Management Guide Displaying Payload Header Suppression Entries Use the show cable qos svc-flow phs command in Privileged EXEC mode to display the Payload Header Suppression (PHS) entries for a service flow, as shown below: MOT#show cable qos svc-flow phs {/} [<1-4292967295> | ] [1-65535> | ] where: x is the slot number of the cable module. y is the cable interface number, which is 0. 1-4292967295 is the Service Flow Identifier (SFID).
Configuring the CMTS 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. • The spectrum map describes the way the upstream spectrum is used for a particular band.
BSR 64000 Configuration and Management Guide Defining a spectrum group contains the following tasks outlined in this section: • • • • • • • • • • Creating a Spectrum Group Scheduling the Availability of a Spectrum Group Band Scheduling the Removal of a Spectrum Group Band Configuring Spectrum Data Collection Configuring Spectrum Hopping Rules Configuring the Spectrum Hopping Error Threshold Configuring the Spectrum Hopping Flap Threshold Enabling and Disabling Spectrum Roll-back Configuring the Guard Ban
Configuring the CMTS The Cable Spectrum Group mode displays. From this new prompt, all of the cable spectrum parameters are configured.
BSR 64000 Configuration and Management Guide For example, if you defined your spectrum1 group to have a start frequency of 8 MHz and an end frequency of 12 MHz your command syntax would look as shown below: MOT(config-spcgrp:spectrum1)#band 8000000 12000000 • If you need to add another start and end frequency band to the spectrum group, repeat this step.
Configuring the CMTS 2. If you want to schedule the time for when the spectrum group band becomes available on a daily basis, use the time band command in Cable Spectrum Group mode, as shown below: MOT(config-spcgrp:)#time band { } where: WORD is the spectrum group name. hh:mm:ss is the time of the day, which includes the hour, minute, and second when the band becomes available. start frequency is the start upstream frequency from 5000000 to 42000000 Hertz.
BSR 64000 Configuration and Management Guide 3. If you want to schedule the time for when the spectrum group band becomes available on a weekly basis, use the time band command in Cable Spectrum Group mode, as shown below: MOT(config-spcgrp:)#time { } band { } where: WORD is the spectrum group name. day is the three letter abbreviation for day of the week. hh:mm:ss is the time during the day when the band becomes available.
Configuring the CMTS Deleting an Existing Availability Time for a Band If you need to delete the existing availability time for a band, use the no time band command in Cable Spectrum Group mode, as shown below: MOT(config-spcgrp:)#no time { | } band { } 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.
BSR 64000 Configuration and Management Guide Scheduling the Removal of a Spectrum Group Band Follow these steps to schedule the removal of a spectrum group band: 1. Use the cable spectrum command in Global Configuration mode to enter Cable Spectrum Group mode, as shown below: Note: If a new removal time for a band is entered for a spectrum group, the existing removal time for a band must be deleted first. MOT(config)#cable spectrum where: WORD is the spectrum group name.
Configuring the CMTS The following example determines that the band from 21 MHz to 29 MHz, belonging to spectrum group spectrum1, is removed every Thursday morning at 11:00 AM: MOT(config-spcgrp:spectrum1)#time Thu 11:00:00 delete band 21000000 29000000 3.
BSR 64000 Configuration and Management Guide 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, as shown below: MOT(config-spcgrp:)#no time { } delete band { } Note: Ensure that the exact parameters for the removal of a time band are entered in order for the change to occur. where: WORD is the spectrum group name.
Configuring the CMTS The spectrum data collection task is split between the spectrum manager and the spectrum agent. The spectrum manager schedules the data collection with the spectrum agent, and provides data storage for the collected data, while the spectrum agent performs the actual data collection and sends the collected data to the spectrum manager.
BSR 64000 Configuration and Management Guide For example, the following syntax shows that the spectrum manager’s data collection interval rate for scanning the spectrum map occurs once every hour: MOT(config-spcgrp:spectrum1)#collect interval 3600 • Since the spectrum collection feature uses resources on the upstream channel that may affect throughput for CMs associated with the upstream port, the spectrum data collection feature should be turned off when it is no longer in use to conserve network resour
Configuring the CMTS Follow these steps to configure spectrum hopping rules: 1. The default hop period is 300 seconds. Use the hop period command in Cable Spectrum Group mode to prevent excessive frequency hops on an upstream port, as shown below: MOT(config-spcgrp:)#hop period where: WORD is the spectrum group name. num:30-3600 is the rate at which the frequency hop takes place, expressed in seconds. 2.
BSR 64000 Configuration and Management Guide 3. Use the hop action modulation-profile command in Cable Spectrum Group mode to change the modulation profile setting for a hop action, as shown below: Note: Refer to the Creating a Modulation Profile section for more information on configuring modulation profiles. MOT(config-spcgrp:)#hop action modulation-profile {<1-16>} [priority {<1-255>}] where: WORD is the spectrum group name. 1-16 is the modulation profile number.
Configuring the CMTS 4. Use the hop action channel-width command in Cable Spectrum Group mode to change the upstream channel-width setting in Hertz (Hz) for a hop action, as shown below: Note: Refer to the Configuring Upstream CM Registration Parameters section for more information on setting the upstream channel width. MOT(config-spcgrp:)#hop action channel-width [1600000 | 200000 | 3200000 | 400000 | 800000] [priority <1-255>] where: WORD is the spectrum group name.
BSR 64000 Configuration and Management Guide 5. Use the hop action band command in Cable Spectrum Group mode to determine the hop for each frequency band during the frequency hop action, as shown below: MOT(config-spcgrp:)#hop action band { } [priority <1-255>] where: WORD is the spectrum group name. start frequency is the start upstream frequency band from 5000000 to 42000000 Hz. end frequency is the end upstream frequency band from 5000000 to 42000000 Hz.
Configuring the CMTS 6. Use the hop action power-level command in Cable Spectrum Group mode to change the power-level setting for a hop action, as shown below: Note: Refer to the Setting the Upstream Power Level section for more information on setting the upstream power level parameters for relative and absolute mode. MOT(config-spcgrp:)#hop action power-level {} [priority <1-255>] where: WORD is the spectrum group name. power is the input power level, expressed in dB.
BSR 64000 Configuration and Management Guide The hopping threshold error rate is determined by the Forward Error Correction (FEC) error-rate threshold value. If the error-rate threshold is configured, the spectrum manager periodically polls the signal quality table of the member channels to compute the error rate during the polling interval. If the error rate exceeds the threshold, it triggers spectrum hopping for the affected channel. The error rate is a fraction of 1000.
Configuring the CMTS Use the hop threshold flap command in Cable Spectrum Group mode to set a value that triggers when a greater than a set percentage of CMs loose their connectivity, as shown below: MOT(config-spcgrp:)#hop threshold flap {} where: WORD is the spectrum group name. num:1-100 is the percentage of CMs from 1 to 100 that loose connectivity on the network.
BSR 64000 Configuration and Management Guide Configuring the Guard Band Use the guard-band command in Cable Spectrum Group mode to set the minimum spectrum separation or spacing between upstream channels in the same spectrum group. MOT(config-spcgrp:)#guard-band <0-37000000> where: WORD is the spectrum group name. 0-37000000 is the guard band separation size expressed in Hertz (Hz) for DOCSIS. The default guard band is 0 Hz.
Configuring the CMTS Figure 6-1 shows sample output for the show cable spectrum-group command: Figure 6-1 show cable spectrum-group Command Output To view the spectrum allocation map for the spectrum group that you created, enter the show cable spectrum-group map command in Global Configuration mode, as shown below: MOT(config)#show cable spectrum-group map where: WORD is the spectrum group name.
BSR 64000 Configuration and Management Guide Figure 6-2 shows sample output for the show cable spectrum-group map command: Figure 6-2 show cable spectrum-group map Command Output To view the spectrum schedule for the spectrum group that you created, enter the show cable spectrum-group schedule command in Global Configuration mode, as shown below: MOT(config)#show cable spectrum-group schedule where: WORD is the spectrum group name.
Configuring the CMTS 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.
BSR 64000 Configuration and Management Guide Follow these steps to assign a spectrum group to an upstream port on a cable interface: 1. To enter the cable interface, use the interface cable command in Global Configuration mode, as shown below: MOT(config)#interface cable / where: x is the slot number of the master cable module. y is the cable interface number, which is 0. 2.
Configuring the CMTS 4.
BSR 64000 Configuration and Management Guide Figure 6-4 displays the show interface cable upstream spectrum command output: Figure 6-4 show interface cable upstream spectrum Command Output Viewing Spectrum Management Configuration Changes Follow these steps to view upstream information when the spectrum manager makes changes to an upstream port: 1.
Configuring the CMTS For example, Figure 6-5 displays upstream port statistics: Figure 6-5 show cable upstream Command Output Determining the Upstream Signal to Noise Ratio Use the show interfaces cable upstream signal-quality command in Privileged EXEC mode to determine the signal power to noise ratio, and error signal quality information as shown below: MOT#show interfaces cable / upstream signal-quality where: x is the slot number of the cable module.
BSR 64000 Configuration and Management Guide For example, Figure 6-6 displays a typical signal-quality result for an upstream port: Figure 6-6 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 notifications command log output only displays the MIB Index ID number.
Configuring the CMTS The following example shows that upstream port 1 on module 0 has a MIB Index ID number (ifIndex) of 5. This number is used to determine the slot and upstream port number that is displayed in the debug specmgr and console logging output.
BSR 64000 Configuration and Management Guide For example, if the upstream frequency was changed to 20000000 Hertz, the following notification output appears: [07/23-10:57:17:SPECMGR]-N-Set to new frequency 20000000 for channel ifIndex = 4 . [07/23-10:57:17:console]-N-configuration change by [enabled-user]: cable upstream 0 frequency 20000000 Viewing Spectrum Management Hopping Actions The debug specmgr command is used to monitor all active upstream ports.
Configuring the CMTS MOT#[07/23-11:00:08:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:00:08:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0, TotalWord : 2901 [07/23-11:00:08:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -197. 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. [07/23-11:01:58:SPECMGR]-D-Error Rate: 0.
BSR 64000 Configuration and Management Guide [07/23-11:03:08:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -198. If the noise power increases at the new frequency, the next hop action rule is to change modulation profile (in this example, the hop action rule is 2 with a priority of 50). Notice that the noise power level continues to increase: [07/23-11:04:58:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:04:58:SPECMGR]-D-Error Rate: 0.
Configuring the CMTS [07/23-11:07:28:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -32. In the following output example, ingress noise causes the error rate to exceed the error threshold, and the next hop action changes the upstream channel width: [07/23-11:08:58:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:08:58:SPECMGR]-D-Error Rate: 4.5083 %, ErrorWord : 182, TotalWord : 4037 [07/23-11:08:58:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : 16.
BSR 64000 Configuration and Management Guide [07/23-11:09:38:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : -185. The following output shows the existing upstream channel width reverting to its original upstream channel width setting: [07/23-11:09:39:SPECMGR]-N-Revert to width 3200000, miniSlot succeed for channel ifIndex = 7 . [07/23-11:09:48:SPECMGR]-D-Monitor Channel IfIndex = 7 : [07/23-11:09:48:SPECMGR]-D-Error Rate: 0.
Configuring the CMTS Using Flap Lists Flap lists are used to collect statistics for determining CM problems on the network. The CM flap list keeps track of the CM MAC address, up and down transitions, registration events, missed periodic ranging packets, upstream power adjustments on the BSR.
BSR 64000 Configuration and Management Guide 2. To specify the flap list insertion time, use the cable flap-list insertion-time command in Global Configuration mode, as shown below: MOT(config)#cable flap-list insertion-time <1-86400> where: 1-86400 is the flap list insertion time, expressed in seconds. The default flap list insertion time is 60. 3.
Configuring the CMTS 4. The default miss threshold for MAC-layer keepalive messages is 6. If you want to change the threshold number of MAC-layer keepalive message misses that will result in the CMs being recorded in the flap list, use the cable flap-list miss-threshold command in Global Configuration mode, as shown below: Note: A high miss rate can indicate intermittent upstream problems, fiber laser clipping, or common-path distortion.
BSR 64000 Configuration and Management Guide 7. To display the CM flap lists and verify cable flap list information, use the show cable flap-list command in all modes except User EXEC mode. Refer to Using Flap Lists to Troubleshoot CM Problems for using the various show cable flap-list command options. MOT#show cable flap-list Figure 6-7 displays example output for the show cable flap-list command.
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. Intermittent keepalive messages are detected between the BSR and the CM. The CM upstream transmit power changes beyond the configured power adjust threshold.
BSR 64000 Configuration and Management Guide Table 6-8 lists the show cable flap-list command output fields and their descriptions: Table 6-8 show cable flap-list Command Output Field Display Fields Field Identification MAC ID Lists the MAC addresses of the CMs sorted by the flap rate or most recent flap time. The first six digits in the CM MAC address indicate the vendor ID of the CM manufacturer, followed by six digits indicating a unique host address. Each CM MAC address is unique.
Configuring the CMTS Table 6-8 show cable flap-list Command Output Field Display Fields Field Identification Type Indicates the type of event that triggered the flap. Time Indicates the most recent time a flap has occurred for a particular CM. Interpreting Flap List Statistics This section describes how to interpret flap list statistics in order to troubleshoot the cable network CM activity follows the sequence below.
BSR 64000 Configuration and Management Guide Use the following cause or symptom observations to interpret flap list activity and solve CM problems: Table 6-9 Troubleshooting CM Problems Cause or Symptom Problem Subscriber CM shows a lot of flap list activity CM is having communication problems with the BSR. Subscriber CM shows little or no flap list activity. The CM is communicating with the BSR effectively, however there is still a problem.
Configuring the CMTS Table 6-9 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. If the miss count is greater, then the CM is probably dropping out frequently and not completing registration.
BSR 64000 Configuration and Management Guide Note: CMs go offline faster than the frequency hop period and can cause the frequency to stay fixed while CMs go offline. Reduce the hop period to 10 seconds to adjust to the hop frequency period.
Configuring the CMTS Table 6-10 describes how to interpret flap list statistics: Table 6-10 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. When the BSR receives a response from the CM, the event is counted as a Hit. If the BSR does not receive a response from the CM, the event is counted as a Miss.
BSR 64000 Configuration and Management Guide Table 6-10 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. The Flap and the Ins counters are incremented when the CM tries to re-establish the RF link with the BSR within a period of time that is less than the user-configured insertion interval value.
Configuring the CMTS • Save the flap list statistics to a database server at least once a day to keep a record of flap list statistics which includes upstream performance and quality control data. These statistics can be used again at a later time to evaluate trends and solve intermittent problems on the HFC networks. Once the flap list statistics are backed up daily on the database server, the flap list statistics can be cleared.
BSR 64000 Configuration and Management Guide • To duplicate a CM certificate to provisioned certificate table, use the cable privacy provision-cert-add command in Privileged EXEC mode as shown below: MOT(config)#cable privacy provision-cert-add {} where: mac is the MAC address. Pinging a Cable Modem at the MAC Layer The ping DOCSIS command is used to “ping” or find a cable modem (CM) on the network at the MAC layer by entering the CM’s MAC or IP address.
Configuring the CMTS 4. To determine if a CM is online, use the ping docsis command in Interface Configuration mode, as shown below: MOT(config-if)#ping docsis [ | ] Note: Be sure to use the correct MAC or IP address of the CM. where: mac is the MAC address of the CM. prefix is the IP address of the CM.
BSR 64000 Configuration and Management Guide MOT#clear cable modem reset where: ip-address is the CM IP address.
Configuring the CMTS • To reset all CMs connected to the BSR, use the clear cable modem all reset command in Privileged EXEC mode, as shown below: MOT#clear cable modem all reset Clearing Cable Interface Counters To clear the counters for a cable interface, use the clear counters cable command in any mode as shown below: MOT#clear counters cable / where: x is the slot number of the cable module. y is the cable interface number, which is 0.
BSR 64000 Configuration and Management Guide Displaying Cable Interface Statistics 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, as shown below: MOT(config-if)#show stats cmts where: NUM is the slot number of one or more available cable modules.
Configuring the CMTS Figure 6-9 displays the show stats cmts command output: Figure 6-9 show stats cmts Command Output 6-113
BSR 64000 Configuration and Management Guide Displaying Downstream Parameters To show the configured parameters for the downstream port, use the show cable downstream command in Interface Configuration mode, as shown below: MOT(config-if)#show cable downstream <0-0> where: 0-0 is the downstream port number.
Configuring the CMTS Figure 6-11 displays the show interfaces cable downstream command output: Figure 6-11 show interfaces cable downstream stats Command Output Displaying Upstream Parameters To show the configured upstream parameters, use the show cable upstream command in Interface Configuration mode, as shown below: MOT(config-if)#show cable upstream where: NUM is the upstream port number.
BSR 64000 Configuration and Management Guide Figure 6-12 displays the show cable upstream command output: Figure 6-12 show cable upstream Command Output Viewing Upstream Port Information Use the show interfaces cable upstream command in all modes except User EXEC mode to view upstream port statistics, as shown below: MOT#show interfaces cable / upstream [stats | signal-quality | spectrum ] where: x is the cable module slot number.
Configuring the CMTS y is the cable interface number, which is 0. stats provides upstream information in a statistical format. signal-quality displays upstream port RF signal quality information. spectrum displays upstream port spectrum information for power levels comparing the upstream frequency to the number of microvolts and dBmV. start-freq is the upstream start of the frequency range from 5000000 to 42000000 Hertz (Hz).
BSR 64000 Configuration and Management Guide Table 6-11 Cable Modem Fields Field Identification Connectivity State Describes the connectivity state of a cable modem. Refer to Table 6-12 for more information on each connectivity state. Timing offset CM current timing adjustment. Rec Power CM receive downstream power level in dbmv.
Configuring the CMTS Table 6-12 describes the 20 cable modem connectivity states. Table 6-12 Cable Modem Connectivity States Connectivity State Identification init(o) Option file transfer was started. init(t) Time-of-day (TOD) exchange was started. init(r1) CM sent initial ranging parameters. init(r2) CM is ranging. init(rc) Ranging is complete. dhcp(d) DHCP Discover was sent by CM. dhcp(o) DHCP Offer was received. dhcp(req) DHCP Request was sent by CM.
BSR 64000 Configuration and Management Guide • Use the following options to view Customer Premises Equipment (CPE) information: • If you want to display CPE information for all cable interfaces, use the show cable modem-cpe command as shown bellow: MOT#show cable modem cpe • If you want to display information for a CPE IP or MAC address, use the show cable modem-cpe command, as shown below: MOT#show cable modem cpe [ | ] where: is the CPE MAC address.
Configuring the CMTS Figure 6-15 displays the cable modem cpe statistics for each cable interface: Figure 6-15 show cable modem cpe Command Output • To display information for a SID assigned to a CM on a specific DOCSIS interface, use the show cable modem detail command in Privileged Exec mode, as shown below: MOT#show cable modem detail / where: x is the slot number of the cable module. y is the cable interface number, which is 0, to which the CM is connected.
BSR 64000 Configuration and Management Guide Figure 6-16 displays output information for the show cable modem detail command: Figure 6-16 show cable modem detail Command Output • 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. • Active modems are those modems in any Init, DHCP or Reject state or substate.
Configuring the CMTS • Use the show cable modem summary command to display the total number of registered, unregistered and offline CMs for cable interfaces on the BSR 64000: MOT#show cable modem summary • Use the show cable modem summary total command to display the total number of registered, unregistered and offline CMs for a specific cable module: MOT#show cable modem summary [/ total] where: x is the cable module slot number. y is the cable interface number, which is 0.
BSR 64000 Configuration and Management Guide • To display the number of Customer Premises Equipment (CPE) hosts connected to a specific CM, use the show cable modem hosts command in Privileged EXEC mode, as shown below: MOT#show cable modem { | } hosts where: mac is the CM MAC address. prefix is the CM IP address. Figure 6-19 displays the current number of hosts connected to the CM.
Configuring the CMTS • Use the show cable modem registered command to display registered CMs only, as shown below: MOT#show cable modem registered where: Figure 6-21 displays the current number of registered CMs.
BSR 64000 Configuration and Management Guide slot is the slot number of the cable module to which CMs are associated. spectrum-group is used to identify a spectrum group. WORD is the spectrum group name to which the CM belongs. Figure 6-23 displays the current number of registered CMs for a cable module slot. Figure 6-23 show cable modem time-registered Command Output • The show cable modem mac command displays MAC layer (layer 2) information for CMs.
Configuring the CMTS Figure 6-24 displays MAC layer statistics for a specific CM: Figure 6-24 show cable modem mac Command Output • The show cable modem phy command displays physical hardware information for CMs. Use the following options to view CM physical layer information: • Use the show cable modem phy command to view physical layer information for CMs on a specific cable module, as shown below: MOT#show cable modem phy {/} where: x is the slot number of the cable module.
BSR 64000 Configuration and Management Guide • The show cable modem maintenance command is used to veiw station maintenance statistics, which includes station maintenance retries, station maintenance failures, and recent event timestamps. Cable modem (CM) station maintenance ranging, which occurs during the CM registration process, uses periodic time intervals to send a unicast message containing a registered SID between the cable modem and the CMTS.
Configuring the CMTS • Use the show cable modem stats command in Privileged EXEC mode to display IP statistics for the number of unicast bytes that are transmitted and received for each CM MAC address on a cable module, which includes CMs that are off-line, as shown below MOT#show cable modem [ | <0-15> | ] stats where: mac is the MAC hardware address of the CM. prefix is the IP address of the CM. 0-15 is the slot number of the cable module to which CMs are associated.
BSR 64000 Configuration and Management Guide Table 6-13 show cable modulation-profile Fields Field Identification FEC len FEC length Guard time size Guard time size Intvl usage code IUC of upstream transmit burst class Last code-word Last codeword shortened 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 Displaying BPI Configuration Settings Follow
Configuring the CMTS Figure 6-29 displays a sample output from the show cable privacy auth command: Figure 6-29 show cable privacy auth Command Output 6-131
7 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.
BSR 64000 Configuration and Management Guide MOT(config)#route-map [permit | deny] where: name is the name that uniquely identifies an instance of a route map; instances with lower sequence numbers are parsed first. permit specifies perform set operations, if the match conditions are met. deny specifies deny set operations. sequence-number identifies an instance of the route map. Once the route map is created using the route-map command, you enter Route Map Configuration mode.
Configuring Routing Policy 3. Match the destination IP address that is permitted by one or more standard or extended access lists with the match ip address command. To match destinations with an IP access list, use the match ip address command in Route Map Configuration mode, as shown in the example below: MOT(config-rmap)#match ip address [...] 4.
BSR 64000 Configuration and Management Guide 8. To match one or more tag values of the destination protocol and set the rules for routes, use the match tag command in Route Map Configuration mode, as shown in the example below: MOT(config-rmap)#match tag [... where: num is a valid value from 0 to 4294967295. Using Set Statements to Define Routing Conditions Set statements define the conditions that apply to the route.
Configuring Routing Policy 4. To set the local preference value, use the set local-preference command in Route Map Configuration mode, as shown in the example below: MOT(config-rmap)#set local-preference 5. To set the metric, use the set metric command in Route Map Configuration mode, as shown in the example below: MOT(config-rmap)#set metric 6.
BSR 64000 Configuration and Management Guide 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.
Configuring Routing Policy Example This configuration example filters BGP updates from a BGP neighbor. It 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. access-list 4 deny 10.0.0.0 0.255.255.255 any access-list 4 deny 162.15.0.0 0.0.255.255 any access-list 4 deny 180.10.0.0 0.0.255.
BSR 64000 Configuration and Management Guide Example This example configures a router with two AS-path access lists. Routes that pass AS-path access-list 1 are sent to one destination. Routes that pass AS-path access-list 2 are accepted from another destination. The commands below specify permit and deny conditions for AS-path access lists. 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 .
Configuring Routing Policy out permits the outgoing packet to be processed only if access-list permits the packet. Creating Community Lists You can use the community to control the routing information a BGP speaker accepts, prefers, or distributes to other neighbors. The BGP community attribute passes between peers when they exchange reachability information.
BSR 64000 Configuration and Management Guide AS 100 NY AS 300 LA AS 200 Boston rp0001 Figure 7-1 Using a Community List Filtering Routes To filter routes based on a community list, use the ip community-list command, as shown below: MOT(config)#ip community-list {permit | deny} {} { | no-export | no-advertise | local-as | internet} 7-10
Configuring Routing Policy where: community-list-number identifies a community list. community-number is a number that identifies a community. as-community-number is a number that identifies one or more permit or deny ASs. Example This example uses a community list to modify the local preference of routes based on community number. The commands below specify community list 1 to permit routes with community number 100 and community list 2 to permit routes with community number 200.
BSR 64000 Configuration and Management Guide Redistributing Routes You can advertise networks by redistributing routes learned from one routing protocol into another. Figure 7-2 shows Router New York redistributes the routes learned via OSPF protocol from Routers Boston and LA into BGP.
Configuring Routing Policy tag is a unique name for routing process. route-map indicates current routing protocol. match internal indicates routes that are internal to an AS. external 1 indicates routes that are external to an AS, but are imported into OSPF as either Type 1 or Type 2 external route. external 2 indicates routes that are external to an AS, but are imported into OSPF as a Type 2 external route.
BSR 64000 Configuration and Management Guide • half-life —half-life period in minutes in the range 1 - 45. The default is 10. When a BGP route has been assigned a penalty, the penalty is decreased by a half after each half-life period (which is 15 minutes by default). Each time a route flaps, the router configured for route flap damping assigns the route a penalty. Penalties are cumulative. BGP stores the penalty for all reachable and unreachable routes that have experienced recent flaps.
Configuring Routing Policy Policy-based routing is applied to incoming packets. All packets received on an interface with policy-based routing enabled are considered for policy-based routing. The router passes the packets through a route map. Based on the information defined in the route map, packets are forwarded to the appropriate next hop. Route maps contain a combination of match and set commands. The match commands define the criteria for whether or not packets meet a particular policy.
BSR 64000 Configuration and Management Guide Refer to Using Match Statements to Define Routing Conditions on page 7-2 for more information on defining a match criteria using these commands. Note: If no match parameters are specified in the route map, then all incoming packets are considered for policy-based routing. Defining the Route Set commands are used to define a route in the route map to be used for policy-based routing.
Configuring Routing Policy set ip next-hop defines a list of IP addresses that specify the next hop router in the path toward the destination to which the packets should be forwarded. The first IP address associated with a reachable interface is used to route the packets. To set the next-hop attribute of a route, use the set ip next-hop command in Route Map Configuration mode, as shown in the example below: MOT(config-rmap)#set ip next-hop set default interface defines a list of default interfaces.
BSR 64000 Configuration and Management Guide MOT(config-rmap)#set ip diff-serv <0-63> The precedence setting determines which packets will be given transmission priority. When packets with a precedence value are received by another router, the packets are ordered for transmission according to the precedence set. A higher precedence value indicates a higher priority. Refer to Table 7-1 for pre-defined precedence values.
Configuring Routing Policy • • • • • • • show ip bgp show ip bgp dampened-paths show ip community-list show ip interface show ip redistribute show ip route show route-map 1. To display an access list or all access lists, use the show ip access-list from any mode, as shown below. The resulting display includes the instances of each access list. MOT#show ip access-list [] where: number is the access list number or numbers. 2.
BSR 64000 Configuration and Management Guide MOT# show ip bgp dampened-paths[] 5. To display the configured community access list, use the show ip community-list from Global Configuration mode, as shown below. MOT(config)#show ip community-list [] where: number is the access list number; valid entries are 1 to 199. 6. To display interface multicast information, use the show ip interface from EXEC mode, as shown below.
Configuring Routing Policy ospf displays OSPF protocol transmitting the route. rip displays RIP protocol transmitting the route. static displays static routes. summary displays a summary of all routes. prefix indicates display IP address; route address. mask indicates display subnet mask. 8.
8 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. Any host, regardless of whether it is a member of a group, can send to a group. However, only the members of a group receive the message.
BSR 64000 Configuration and Management Guide Enabling IP Multicast Routing on the BSR IP multicast routing allows the BSR to forward IP multicast packets over the network.
Configuring IP Multicast Routing The BSR supports PIM in sparse mode. In sparse mode, routers must join and leave multicast groups explicitly. Upstream routers do not forward multicast traffic out a PIM interface unless the router has sent an explicit request called a join message to receive multicast traffic from a downstream router or if group members are directly connected to the interface.
BSR 64000 Configuration and Management Guide 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. The SPT threshold determines when the RP (shared tree) can join the SPT (source tree) for a specified multicast group.
Configuring IP Multicast Routing infinity indicates that the RP is always used. 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.
BSR 64000 Configuration and Management Guide If you want to configure the router to be a candidate BSR and adjust the hash mask length value in order to avoid having two RPs for the same multicast group, use the ip pim bsr-candidate command in Interface Configuration mode, as shown below: Note: It is recommended (but not required) that the hash-mask length be the same across all candidate BSRs. MOT(config-if)#ip pim bsr-candidate where: n is the hash mask length from 0 to 32 bits.
Configuring IP Multicast Routing Configuring Candidate RPs One or more rendezvous points (RPs) can be configured to serve as candidates in a PIM domain to avoid a single point of failure. Candidate RPs should be configured on the backbone portion of the network to help improve the efficiency of the multicast network. Candidate RPs send candidate RP advertisements to the bootstrap router (BSR) and the BSR then distributes all RP information to the PIM domain.
BSR 64000 Configuration and Management Guide n is the interval from 1 to 200 seconds. • If you want to configure a candidate RP that is associated with this router, use the ip pim rp-candidate ip-address command, as shown below: MOT(config-if)#ip pim rp-candidate ip-address where: ip-address is an IP address of the candidate RP. • The RP candidate priority is 0 by default.
Configuring IP Multicast Routing About DVMRP The Distance Vector Multicast Routing Protocol (DVMRP) is a distance-vector multicast routing protocol that delivers connectionless data to a group of hosts across an internetwork. DVMRP is designed to be used as an interior gateway protocol (IGP) within a multicast domain. DVMRP is often referred to as a "flood and prune" protocol.
BSR 64000 Configuration and Management Guide 1. Use the router dvmrp command in Router Configuration mode to enter Router Configuration mode from Global Configuration mode, as shown below: MOT(config)#router dvmrp 2. Use the network command in Router Configuration mode to define the network IP address and subnet mask for the DVMRP network: MOT(config-dvmrp)#network where: ip-address is the IP address of the DVMRP network. wild-card is the wild-card mask for the DVMRP network.
Configuring IP Multicast Routing MOT(config-dvmrp)#route-limit where: n is the number of DVMRP route reports. Setting the DVMRP Prune Lifetime Value DVMRP uses a basic multicast model to build a parent-child database. This database is used to create a forwarding tree that originates at the source where multicast packets are generated. Multicast packets are initially flooded down the forwarding tree making parent-child links.
BSR 64000 Configuration and Management Guide • • Rejecting a DVMRP Non-pruning Neighbor Configuring a DVMRP Summary Address Filtering Incoming DVMRP Reports Use the ip dvmrp accept-filter command in Interface Configuration mode to block an address range from being forwarded by filtering incoming DVMRP reports, as shown below: MOT(config-if)#ip dvmrp accept-filter where: n is the accept filter number from 0 to 99.
Configuring IP Multicast Routing MOT(config-if)#ip dvmrp default-information originate only Adding a Metric Offset to the DVMRP Route The DVMRP metric is the same as a hop-count. The BSR uses increments of 1 to adjust the metric of a DVMRP route advertised in incoming DVMRP reports by default. The DVMRP route metric can be changed to assist or sustain a particular route. The ip dvmrp metric-offset command is used to influence which routes are used or preferred.
BSR 64000 Configuration and Management Guide n is the increment number from 0 to 31. Note: The default value for out is 0. Setting the DVMRP Neighbor Time-out Interval The DVMRP neighbor time-out interval is the amount of time allowed before a neighbor is removed from the DVMRP neighbor table, if the neighbor does not send a probe (query) or report.
Configuring IP Multicast Routing n is the amount of delay from 1 to 10 seconds. reports is the number of route reports from 1 to 100. Setting the DVMRP Probe Interval The DVMRP probe interval is configured to send queries to neighboring multicast routers for DVMRP multicast routes. Use the ip dvmrp probe-interval command in Interface Configuration mode to set the DVMRP probe interval, as shown below: MOT(config-if)#ip dvmrp probe-interval where: n is the probe interval from 5 to 3600 seconds.
BSR 64000 Configuration and Management Guide MOT(config-if)#ip dvmrp summary-address Note: One or more specific routes must exist in the unicast routing table before a summary address is advertised. where: ip is the DVMRP IP summary address. subnetwork is the DVMRP subnetwork mask.
Configuring IP Multicast Routing For each attached network, a multicast router can be either a querier or a non-querier. The querier router periodically sends general query messages to solicit group membership information. Hosts on the network that are members of a multicast group send report messages. When a host leaves a group, it sends a leave group message. IP hosts use IGMP to report their group membership to directly connected multicast routers.
BSR 64000 Configuration and Management Guide slot is the module slot number. interface is the interface number. 2. Use the ip igmp access-group command in Interface Configuration mode to filter multicast groups that are permitted on the interface: MOT(config-if)#ip igmp access-group where: n is the access list-number from 1 to 99. Changing the IGMP Version The BSR uses IGMP Version 2 by default, which allows the IGMP query time-out and the maximum query response time features.
Configuring IP Multicast Routing Use the ip igmp query-interval command in Interface Configuration mode to change the IGMP host-query message interval, as shown below: MOT(config-if)#ip igmp query-interval where: n is the time interval from 1 to 3600 seconds that the BSR sends IGMP host-query messages to connected networks.
BSR 64000 Configuration and Management Guide Use the ip igmp query-max-response-time command to change the query response interval to change the burstiness of IGMP messages on the subnetwork. The query response interval is 10 seconds by default. MOT(config-if)#ip igmp query-max-response-time where: n is the query response interval from 1 to 25 seconds.
Configuring IP Multicast Routing 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.
BSR 64000 Configuration and Management Guide MOT(config)#ip mroute unicast distance where: n is the administrative distance number from 1 to 255. 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, as shown below: MOT(config)#ip mroute static distance where: n is the administrative distance number from 1 to 255.
Configuring IP Multicast Routing • Use the clear ip dvmrp prune * command in Privileged EXEC mode to clear all dvmrp prunes, as shown below: MOT#clear ip dvmrp prune * • Use the clear ip dvmrp prune group command in Privileged EXEC mode to clear prunes from a specific DVMRP group, as shown below: MOT#clear ip dvmrp prune group where: ip-address is the IP address of the DVMRP group.
BSR 64000 Configuration and Management Guide MOT#clear ip igmp counters Removing the IP Multicast Cache Use the following options to remove IP multicast routing information: • If you want to clear the entire IP multicast forwarding cache, use the clear ip multicast fwd-cache command in Privileged EXEC mode, as shown below: MOT#clear ip multicast fwd-cache • If you want to clear the entire IP multicast protocol cache, use the clear ip multicast proto-cache command in Privileged EXEC mode, as shown belo
Configuring IP Multicast Routing MOT#show ip multicast fwd-cache For example: Figure 8-1 IP Multicast Forward Cache Information • Use the show ip multicast interface command to list the IP address, multicast protocol (PIM, DVMRP, or IGMP), and time-to-live (TTL) information that is associated with each multicast interface, as shown below: MOT#show ip multicast interface For example: Figure 8-2 show ip multicast interface Command Output • Use the show ip multicast no-oi-fwd-cache command to display
BSR 64000 Configuration and Management Guide MOT#show ip multicast no-oi-fwd-cache • Use the show ip multicast oi-fwd-cache command to display multicast forwarding cache entries that have outgoing interfaces (OIs), as shown below: MOT#show ip multicast oi-fwd-cache • Use the show ip multicast proto-cache command to display multicast protocol cache entries, as shown below: MOT#show ip multicast proto-cache Displaying PIM Information Use the following options to view PIM information in Privileged EXEC m
Configuring IP Multicast Routing Displaying DVMRP Information Use the following options to view DVMRP information in Privileged EXEC mode: • Use the show ip dvmrp information command to gather general DVMRP information, as shown below: MOT#show ip dvmrp information • Use the show ip dvmrp interface command to gather information for all the DVMRP interfaces as shown below: MOT#show ip dvmrp interface • Use the show ip dvmrp neighbor command to gather DVMRP neighbor information, as shown below: MOT#sho
BSR 64000 Configuration and Management Guide • Use the show ip igmp interface command to gather IGMP interface information, as shown below: MOT#show ip igmp interface • Use the show ip igmp statistics command to gather IGMP statistics information, as shown below: MOT#show ip igmp interface Displaying Reverse Path Forwarding Information Use the following options to view Reverse Path Forwarding (RPF) information in Privileged EXEC mode: • Use the show ip rpf command to display a specific multicast sour
9 Configuring RIP
Configuring RIP Overview This chapter describes how to configure the Routing Information Protocol (RIP) for the BSR 64000™: • • • • • • • • • • • • About RIP Enabling RIP Specifying a RIP Version Enabling or Disabling Split Horizon Enabling Route Summarization Applying an Offset List Enabling RIP Authentication Configuring Interpacket Delay Configuring Timers Configuring a Passive Interface for RIP Redistributing Routes into RIP Gathering RIP Information About RIP Routing Information Protocol (RIP) is a
BSR 64000 Configuration and Management Guide RIP uses the hop count to rate the value of different routes. A directly connected network has a hop count of one; an unreachable network has a hop count of 16. This small range of metrics makes RIP unsuitable for large networks. The route tag field in a RIP message allows boundary routers in an autonomous system (AS) to exchange information about external routes.
Configuring RIP Enabling RIP In order to use RIP on the BSR, RIP must be enabled. The remaining tasks described in this chapter are optional. Follow these steps to enable RIP on the BSR: 1. Use the router rip command in Global Configuration mode to enable a RIP routing process on the BSR, as shown in the example below: MOT(config)#router rip This enables RIP and places you in Router Configuration mode. Use the no router rip command to disable RIP. 2. You may specify multiple network sub-commands.
BSR 64000 Configuration and Management Guide 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. 1.
Configuring RIP 2 configures an interface to send only RIPv2 packets. 3 configures an interface not to send RIP packets.
BSR 64000 Configuration and Management Guide Enabling Route Summarization RIPv2 supports route summarization, which condenses routing information and reduces the router load and the perceived network complexity. The larger the network, the more important route summarization is. Without route summarization, a router retains a route to every subnet in its network. With summarization, the router can reduce some sets of routes to a single advertisement.
Configuring RIP 1. To enable route summarization, use the auto-summary command in Router RIP Configuration mode, as shown in the example below. It is disabled by default. 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.
BSR 64000 Configuration and Management Guide In the following example, the router applies an offset of 4 to routes learned from Ethernet interface 1/0: offset-list 13 in 3 ethernet 1/0 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.
Configuring RIP MOT(config-rip)#output-delay where: delay is the delay, in milliseconds, between packets in a multiple-packet RIP update; valid values are 8 to 50 milliseconds; default is no delay. Use the no output-delay command to return to the default. 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.
BSR 64000 Configuration and Management Guide flush-timer is the interval value in seconds that elapse before a route is removed from the routing table; default is 300.The interval specified must be Note: You can adjust basic RIP timers, but they must be the same for all routers and servers. greater than the invalid value.
Configuring RIP interface is the interface number. 2. Use the passive-interface default command in Router Configuration mode to suppress routing updates on all RIP interfaces, as shown below: MOT(config-rip)#passive-interface ethernet / where: slot is the module slot number. interface is the interface number. Redistributing Routes into RIP Each routing protocol uses different metrics to transfer routes.
BSR 64000 Configuration and Management Guide where: metric is the redistribution metric number for connected routes from 1 to 16. route-map is the route-map name for the connected route. cr is a command return that redistributes of all connected routes.
Configuring RIP where: metric is the redistribution metric number for BGP routes from 1 to 16. route-map is the route-map name for the BGP route. cr is a command return that redistributes of all BGP routes. • Use the redistribute static command in Router Configuration mode to redistribute static routes into RIP, as shown below: MOT(config-rip)#redistribute static {metric | route-map | } where: metric is the redistribution metric number for static routes from 1 to 16.
BSR 64000 Configuration and Management Guide Gathering RIP Information Follow these steps to monitor RIP on the BSR: 1. To display RIP routes and the status of each rip route on the BSR interface, use the show ip route rip command in Privileged EXEC mode as shown in the following example: MOT#show ip route rip 2.
10 Configuring IS-IS
Configuring IS-IS Overview The integrated Intermediate System to Intermediate System (IS-IS) is a link state based intra-domain routing protocol used to build a complete and consistent picture of a network’s topology by sharing link state information across all network Intermediate System (IS) devices. IS-IS is based on an SPF routing algorithm and shares all the advantages common to other link-state protocols. It also routes both IP packets and pure OSI packets with no extra encapsulation by design.
BSR 64000 Configuration and Management Guide 1. Use the router isis command in Global Configuration mode to enable IS-IS routing and specify an IS-IS process for IP communication, which places you in router configuration mode. MOT(config)#router isis [tag] where: tag is the name for the routing process. If the tag is not specified, a null tag is assumed. Network Entity Titles (NETs) define the area address and the system ID for an IS-IS router. Most end systems and intermediate systems have one NET.
Configuring IS-IS • The first portion of the NET address is the area number, which is a variable number from 1 through 13 bytes. The first byte of the area number (01) is the authority and format indicator (AFI). The next bytes are the assigned domain (area) identifier, which can be from 0 through 12 bytes. In the example above, the area identifier is 0001. • The next six bytes form the system identifier (SYSID). The SYSID can be any six bytes that are unique throughout the entire domain.
BSR 64000 Configuration and Management Guide Redistributing Routes into IS-IS 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. Routes are redistributed to advertise networks on another routing protocol.
Configuring IS-IS MOT(config-isis)#redistribute connected {metric | route-map | } where: metric is the redistribution metric number for connected routes. route-map is the route-map name for the connected route. cr is a command return that redistributes of all connected routes.
BSR 64000 Configuration and Management Guide metric is the redistribution metric number for static routes. metric-type 1 redistributes OSPF External Type 1 metrics. metric-type 2 redistributes OSPF External Type 2 metrics. route-map is the route-map name for the static route. subnets allows the consideration of subnets for redistribution into IS-IS. tag sets a tag for routes redistributed into IS-IS. cr is a command return that redistributes of all static routes.
Configuring IS-IS • • • • • Configuring the Administrative Distance for IS-IS Configuring IS-IS Area or Domain Passwords Summarizing IP Address Ranges Enabling the LSP Overload Bit Configuring a Passive Interface for IS-IS Specifying Router-Level Support Use the is-type command in Router Configuration mode to specify that the BSR acts as a Level 1 (intra-area) router, as both a Level 1 router and a Level 2 (inter-area) router, or as a Level-2 router only, as shown below: MOT(config-isis)#is-type {level-1
BSR 64000 Configuration and Management Guide Configuring the Administrative Distance for IS-IS An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual router or a group of routers. Numerically, an administrative distance is an integer between 0 and 255. The higher the value, the lower the trust rating. For example, an administrative distance of 255 means the routing information source cannot be trusted and should be ignored.
Configuring IS-IS Summarizing IP Address Ranges A range of IP addresses listed in an LSP can be represented by a summary address. Routes learned from other routing protocols also can be summarized. The metric used to advertise the summary is the smallest metric of all the more specific routes.
BSR 64000 Configuration and Management Guide cable is the cable interface. ethernet is the Ethernet/Fast Ethernet interface. gigaether is the Gigabit Ethernet interface. pos is the Packet over SONET interface. slot is the module slot number. interface is the interface number. Configuring IS-IS on an Interface The following configuration tasks performed on the designated IS-IS interface are optional. They are used to adapt IS-IS to your network.
Configuring IS-IS where: level-1 indicates that a Level 1 adjacency may be established if there is at least one area address in common between this system and its neighbors. level-1-2 indicates that a Level 1 and 2 adjacency is established if the neighbor is also configured as level-1-2 and there is at least one area in common. If there is no area in common, a Level 2 adjacency is established.
BSR 64000 Configuration and Management Guide Use the isis hello-interval command in Interface Configuration mode to specify the length of time between hello packets that the BSR sends on either the Level 1 or Level 2 IS-IS router interface, as shown below: MOT(config-if)#isis hello-interval {level-1 | level-2} where: seconds is the ISIS hello interval. level-1 is for Level 1 IS-IS routing. level-2 is for Level 2 IS-IS routing.
Configuring IS-IS By default, IS-IS sends CSN packets periodically. If the BSR is the designated router on a LAN, IS-IS sends CSN packets every 10 seconds. If the BSR is on a point-to-point interface, it sends CSN packets every 3600 seconds (once an hour). Depending on your network topology you may want to modify the default interval to protect against LSP flooding.
BSR 64000 Configuration and Management Guide Setting the LSP Retransmission Interval When LSPs are dropped, LSPs are retransmitted. Use the isis retransmit-interval command in Interface Configuration mode to set the number of seconds between retransmission of each LSP for point-to-point links, as shown below: Note: The number of seconds should be greater than the expected round-trip delay between any two routers on the attached network. Set this parameter conservatively to avoid unnecessary retransmission.
Configuring IS-IS A router’s priority for becoming the designated router is indicated by an arbitrary number. Routers with a higher value are more likely to become the designated router. By default, routers have a priority value of 64. Use the isis priority command to select the designated router priority in Interface Configuration mode, as shown below: Note: Priorities can be configured for Level 1 and Level 2 individually.
BSR 64000 Configuration and Management Guide Gathering IS-IS Information The following sections are used to gather information for your IS-IS network: • • • Displaying IS-IS Database Information Displaying the Shortest Path First Log Displaying Connectionless Network Service Information Displaying IS-IS Database Information Use the following show isis database command options in Privileged EXEC mode to display all or specific IS-IS database information: • Use the show isis database detail command to d
Configuring IS-IS Table 10-1 show isis database Command Output Field Descriptions Output Field Description P P bit. Detects if Intermediate System is capable of area partition repair. OL Overload bit. Determines if Intermediate System is congested.
BSR 64000 Configuration and Management Guide Table describes a list of possible SPF triggers: Table 10-3 Reasons for SPF Log Trigger Events 10-18 Trigger Reason PERIODIC Typically, every 15 minutes a router runs a periodic full SPF calculation. NEWSYSID A new system ID through the NET was configured on this router. NEWAREA A new area (through NET) was configured on this router. NEWLEVEL A new level (through is-type) was configured on this router.
Configuring IS-IS Displaying Connectionless Network Service Information The following options are accessed from Privileged EXEC mode to display Connectionless Network Service Information (CNSI) information: • The show clns es-neighbors [detail] command displays End System neighbor adjacencies that the BSR knows. Table 10-4 describes the show clns es-neighbors command output: Table 10-4 show clns es-neighbors Command Output Fields • Output Field Description System ID System ID of the IS-IS router.
BSR 64000 Configuration and Management Guide Table 10-5 describes the show clns interface Output Fields: Table 10-5 show clns interface Output Fields Output Field Description interface The specific interface is described in the output and is described as being up (functional) and the line protocol as being up (functional) or administratively down. CLNS protocol processing Describes whether or not the CLNS protocol is enabled or disabled. Checksums enabled The checksums can be enabled or disabled.
Configuring IS-IS Table 10-6 describes the show clns is-neighbors command output: Table 10-6 show clns is-neighbors Command Output Fields • Output Field Description System ID System ID of the IS-IS router. Interface Interface on which the router was discovered. State Adjacency state. Up and Init are the states of the ES or IS neighbor. Init System is an IS and is waiting for an IS-IS hello message. IS-IS regards the neighbor as not adjacent.
BSR 64000 Configuration and Management Guide Table 10-7 show clns neighbors Command Output Fields Output Field • Description Init System is an IS and is waiting for an IS-IS hello message. IS-IS regards the neighbor as not adjacent. Up Regards the ES or IS as reachable. Holdtime The number of seconds before this adjacency entry times out. Type The level of the IS-IS router. Protocol The protocol through which the adjacency was learned.
Configuring IS-IS Table 10-8 show clns protocol Command Output Fields • Output Field Description Routing for area address(es): List of manually configured and learned area addresses. Interfaces supported by IS-IS: List of interfaces on the BSR that support IS-IS. Distance: Configured IS-IS administrative routing distance. The show clns traffic command lists the CLNS packets the BSR has processed.
BSR 64000 Configuration and Management Guide Table 10-9 describes the show clns traffic command output: Table 10-9 show clns traffic Command Output Fields 10-24 Output Field Description Corrupted LSPs The number of corrupted LSPs recorded on BSR. L1 LSP Database Overloads The number of times that the Level 1 LSP database has overloaded. L2 LSP Database Overloads The number of times that the Level 2 LSP database has overloaded.
Configuring IS-IS Table 10-9 show clns traffic Command Output Fields Output Field Description Level-1 PSNPs (sent/rcvd) Lists the number of Level 1 PSNPs sent and received. Level-2 PSNPs (sent/rcvd) Lists the number of Level 2 PSNPs sent and received. Level-1 SPF Calculations Lists the number of times a Level 1 shortest -path-first (SPF) tree was computed. Level-2 SPF Calculations List the number of times a Level 2 SPF tree was computed.
11 Configuring OSPF
Configuring OSPF Overview OSPF supports IP sub-networking and tagging of externally derived routing information. OSPF also allows packet authentication and uses IP multicast when sending and receiving packets. It advertises the states of its local network links and runs within a single Autonomous System (AS) to determine optimum routes. Each participating OSPF router within the AS has an identical database of the AS topology.
BSR 64000 Configuration and Management Guide RFC 1587 — The OSPF NSSA Option Enabling OSPF To enable OSPF, create the OSPF routing process, specify the range of IP addresses associated with the routing process, and assign the area IDs associated with that range of IP addresses. To create the OSPF routing process, perform the following steps: 1.
Configuring OSPF network 3.3.3.0 0.0.0.255 area 0 network 3.3.3.3 0.0.0.255 area 1 Redistributing Routes into OSPF 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. Routes are redistributed to advertise networks on another routing protocol.
BSR 64000 Configuration and Management Guide route-map is the route-map name for the connected route. cr is a command return that redistributes of all connected routes.
Configuring OSPF Follow these steps to assign a default metric value for all routes redistributed into OSPF: 1. Use the router ospf command to enter the OSPF routing process in Global Configuration mode, as shown below: MOT(config)#router ospf 2.
BSR 64000 Configuration and Management Guide MOT(config-if)#ip ospf authentication-key where: password 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. 5.
Configuring OSPF 2. Issue the area stub command in Router Configuration mode to configure an OSPF area as a stub area, as shown below: 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. MOT(config-ospf)#area stub where: area-id is the OSPF area ID number.
BSR 64000 Configuration and Management Guide 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. NSSA allows importing of Type 7 AS external routes within NSSA area by redistribution. These Type 7 LSAs are translated into Type 5 LSAs by NSSA ABRs and are flooded throughout the whole routing domain.
Configuring OSPF MOT(config-ospf)#summary-address [tag] where: ip-address is the IP summary address. mask is the IP summary address mask. num 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. 0.0.0.
BSR 64000 Configuration and Management Guide • Use the area range not-advertise command in Router Configuration mode to specify an address range for a single route that is not advertised, as shown below: MOT(config-ospf)#area range not-advertise where: area-id is the number or IP address for the area. ip-address is the IP address for an individual network within the area. mask is the subnet mask for the address. not-advertise indicates do not advertise the range.
Configuring OSPF tag-value is the 32-bit tag value for filtering externally derived routing information. Example In the following example, summary address 20.1.0.0 includes address 20.1.1.0, 20.1.2.0, 20.1.3.0, and so forth. Only the address 20.1.0.0 is advertised in an external LSA. summary-address 20.1.0.0 255.255.0.
BSR 64000 Configuration and Management Guide Choose from the following options to establish a virtual link that connects an OSPF area to the backbone area (area 0.0.0.
Configuring OSPF • If you want to configure the expected round-trip delay Link State Advertisement (LSA) retransmit interval between two routers on the attached network for the OSPF virtual link, use the area virtual-link retransmit-interval command in Router Configuration mode, as shown below: MOT(config-ospf)#area { | } virtual-link retransmit-interval where: area-id is the OSPF area IP address or number.
BSR 64000 Configuration and Management Guide where: area-id is the OSPF area IP address or number. ip-address is IP address associated with the OSPF area ID. is the router ID 32-bit IP address associated with the virtual link neighbor. is the number of seconds that the router does not receive hello packets from its neighbor before declaring the neighbor is down.
Configuring OSPF • Use the show ip ospf virtual-links command in Privileged EXEC mode to display information about the established virtual links, as shown below: MOT#show ip ospf virtual-links • Use the show ip ospf virtual links command in Privileged EXEC mode to display the router ID of an OSPF router, as shown below: MOT#show ip ospf virtual-links Example The following example establishes a virtual link with default values for all optional parameters: router ospf network 72.0.0.0 0.255.255.
BSR 64000 Configuration and Management Guide metric is the metric for generating the default route; default is 10; valid values are from 0 to 16777214. metric-value is the OSPF link state metric value; valid entries are 1 or 2.
Configuring OSPF 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. Note: If the assigned administrative distance for a routing source is 255, it is not trusted and is ignored.
BSR 64000 Configuration and Management Guide inter-area represents the administrative distance number from 1 to 255 for all routes from one area to another area. external represents the administrative distance number from 1 to 255 for routes learned by redistribution from other routing domains.
Configuring OSPF Configuring General OSPF Interface Parameters You can change certain interface-specific OSPF parameters using the ip ospf hello-interval, ip ospf dead-interval, and ip ospf authentication-key commands. If you change these parameters, ensure that the configurations for all routers on your network have compatible values.
BSR 64000 Configuration and Management Guide where: n is the OSPF path cost from 1 to 65535 Mbps. 2. To specify the number of seconds between link state advertisement (LSA) retransmissions for adjacencies belonging to an OSPF area, use the ip ospf retransmit-interval command in Interface Configuration mode, as shown below: MOT(config-if)#ip ospf retransmit-interval 3.
Configuring OSPF where: password is the unencrypted (clear text) with 1 to 8 characters. 8.
BSR 64000 Configuration and Management Guide Blocking OSPF LSA Flooding The OSPF LSA age indicates whether the LSA is valid. The LSA is discarded when it reaches the maximum age of one hour. During the aging process, the originating router sends a refresh packet every 30 minutes to keep the LSA from expiring, regardless of network topology changes. The router tracks and refreshes the LSAs it generates; it tracks and ages the LSAs it receives from other routers.
Configuring OSPF MOT(config-ospf)#passive-interface {cable | ethernet | gigaether | pos | serial} / where: cable is the cable interface. ethernet is the Ethernet/Fast Ethernet interface. gigaether is the Gigabit Ethernet interface. pos is the Packet over SONET interface. serial is the Serial interface. slot is the module slot number. interface is the interface number.
BSR 64000 Configuration and Management Guide Example The following example configures a loopback interface: interface loopback 1 ip address 10.10.10.1 255.255.255.255 Gathering OSPF Information There are several show commands that can be used to view and gather information about your OSPF network. These show commands are available in all command modes except for User EXEC mode, and most user access groups.
Configuring OSPF The following command output displays: Figure 11-1 show ip ospf network Command Output Showing Border Routers Use the show ip ospf border-routers command to display the autonomous system boundary router (ASBR) and an area border router (ABR) routing tables.
BSR 64000 Configuration and Management Guide The following command output displays: Figure 11-3 show ip ospf neighbor Command Output - or - • Use the show ip ospf neighbor command to display a specific OSPF neighbor by entering its IP address, as shown below: MOT#show ip ospf neighbor where: neighbor-ip-address is the OSPF neighbor IP address.
Configuring OSPF Showing 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.
BSR 64000 Configuration and Management Guide MOT#show ip ospf interface where: ip-address 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, as shown below: MOT#show ip ospf interface {cable | ethernet | gigaether | loopback | pos | tunnel } / where: cable is the CMTS interface. ethernet is the Ethernet/FastEthernet IEEE 802.3 interface.
Configuring OSPF The following command output displays: Figure 11-7 show ip ospf memory Command Output Displaying OSPF Database Information Use the following options to display OSPF neighbor information • Use the show ip ospf database command to display information for a specific OSPF router, as shown below: MOT#show ip ospf database where: ip-address is the link state ID or IP address of the OSPF router.
BSR 64000 Configuration and Management Guide • Use the show ip ospf database adv-router command to view the Link State Advertisements (LSAs) for the advertising router, as shown below: MOT#show ip ospf database adv-router where: ip-address is the IP address of the advertising router.
Configuring OSPF where: ip-address is the IP address of the specific link-state ID. self-originate displays LSAs from the local router. cr displays all external LSAs.
12 Configuring BGP
Configuring BGP Overview This chapter describes how to configure Border Gateway Protocol (BGP) for the BSR 64000™ system using the command line interface (CLI). For a complete description of the CLI commands discussed in this chapter, refer to the BSR 64000 Command Reference Guide.
BSR 64000 Configuration and Management Guide Routers that belong to the same AS and exchange BGP updates run internal BGP (IBGP). Routers that belong to different ASs and exchange BGP updates run external BGP (EBGP). With few exceptions, the commands for configuring IBGP and EBGP are identical. Figure 12-1 shows exchanges with IBGP and EBGP running between routers.
Configuring BGP 4. Router Los Angeles adds its own AS to the AS path and forwards to Router Miami. 5. Router Miami receives the route and ascertains that it comes from another AS. 6. Router Miami adds its own AS to the AS path and forwards the route to Router Dallas. 7. Router Dallas receives the route, determines that the route is a loop since its own AS is contained in the AS path, and discards the route. You can configure BGP operating parameters manually.
BSR 64000 Configuration and Management Guide BGP Peers BGP provides a means for BGP peers, or neighbors, to exchange routing information within an AS (IBGP) and with peers within other ASs (EBGP). Information is exchanged between peers about the following: • • • New active routes and their attributes Inactive routes Unusual conditions that require connection termination BGP does not require routing information to be refreshed.
Configuring BGP Specifications The BSR supports the following Request for Comment (RFC) specifications: • • • • • • RFC 1771 — A Border Gateway Protocol 4 (BGP-4) • • RFC 2439 — BGP Route Flap Damping RFC 1745 — BGP4/IDRP for IP (OSPF Interaction) RFC 1965 — Autonomous System Confederations for BGP RFC 1966 — BGP Route Reflection, an Alternative to Full Mesh IBGP RFC 1997 — BGP Communities Attributes RFC 1998 — An Application of the BGP Community Attribute in Multi-home Routing RFC 2385 — Protection o
BSR 64000 Configuration and Management Guide n is the Autonomous System (AS) to which the neighbor belongs; valid values are 1 to 65535. 3. To add an entry to the BGP neighbor table, use the neighbor remote-as command in Router BGP Configuration mode, as shown below. The BGP neighbor table identifies a router as a BGP peer and maps its IP address to a specific AS. MOT(config-bgp)#neighbor {ip-address | peer-group} remote-as number where: ip-address is the neighbor IP address.
Configuring BGP AS 100 AS 300 NY 172.30.20.2 Chicago 172.40.20.2 172.30.20.1 172.40.20.1 Miami 192.50.30.1 192.50.30.2 Boston 120.20.0.0 bgp0004 Figure 12-2 Configuring BGP Neighbors Advertising Networks in an AS 1. To inform BGP peers in other ASs about the networks, advertise them using the network command in Router BGP Configuration mode, as shown below. The network command specifies the networks that an AS originates.
BSR 64000 Configuration and Management Guide Example Figure 12-3 shows how Routers Miami, Chicago, and Los Angeles advertise networks in their ASs. The following commands configure Router Miami: MOT(config-bgp)#router bgp 100 MOT(config-bgp)#neighbor 2.2.2.2 remote-as 100 MOT(config-bgp)#network 120.60.0.0 The next commands configure Router Chicago: MOT(config-bgp)#router bgp 300 MOT(config-bgp)#neighbor 3.3.3.2 remote-as 100 MOT(config-bgp)#network 162.24.0.
Configuring BGP AS 300 162.24.0.0 Chicago 3.3.3.1 3.3.3.2 AS100 162.56.0.0 LA 2.2.2.2 AS 100 126.60.0.0 Miami 2.2.2.
BSR 64000 Configuration and Management Guide • • • • • Restoring Route Reflection from a Route Reflection Client • • • Enabling EBGP Multihop for Neighbor and Peer Groups Configuring Route-flap Dampening Shutting Down a Neighbor or Peer Group Enabling MD5 Authentication Between Peers Setting the Minimum Interval for Sending BGP Routing Updates to Neighbors or Peer Groups Controlling the Number of Prefixes Received from a Neighbor Configuring Next Hop Processing Configuring BGP Peer Groups Routing poli
Configuring BGP AS 100 SF AS 200 5.5.5.5 2.2.2.2 Philadelphia 5.5.5.1 2.2.2.1 AS 300 6.6.6.6 3.3.3.3 Seattle 3.3.3.1 Chicago Trenton 6.6.6.1 4.4.4.1 7.7.7.1 AS 400 7.7.7.7 Dallas 4.4.4.4 Boston bgp0006 Figure 12-4 BGP Peer Groups 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.
BSR 64000 Configuration and Management Guide name is the name you assign to the peer group. Examples The commands in the following example configure a BGP peer group on Router Chicago and apply it to Routers San Francisco, Dallas, and Seattle (as shown in Figure 12-4): MOT(config)#router bgp 100 MOT(config-bgp)#neighbor PACIFIC MOT(config-bgp)#neighbor PACIFIC MOT(config-bgp)#neighbor 2.2.2.2 MOT(config-bgp)#neighbor 3.3.3.3 MOT(config-bgp)#neighbor 4.4.4.
Configuring BGP AS 500 7.7.7.2 Salem AS 400 AS 100 AS 200 7.7.7.1 AS 300 140.100.40.1 San Diego Seattle Hartford Chicago 160.21.10.1 139.100.30.1 Boston Portland SF 140.100.30.1 Concord 140.100.20.1 6.6.6.6 Denver 139.100.20.1 Houston AS 600 Providence Figure 12-5 Configuring a Routing Domain Confederation 1.
BSR 64000 Configuration and Management Guide num is the AS number that internally includes multiple ASs. 2. To configure an AS to be a member of the confederation, use the bgp confederation peers command in Router BGP Configuration mode, as shown below: MOT(config-bgp)#bgp confederation peers where: num specifies the AS that is a member of the confederation.
Configuring BGP Configuring a Route Reflector A BGP speaker cannot advertise a route to an IBGP neighbor if that BGP speaker originally heard the route from another IBGP speaker. The result of the this rule requires a full mesh of IBGP sessions within an AS to fully distribute routes via IBGP. If an AS has many BGP speakers, the number of peer connections can become very large. A route reflector alleviates this problem.
BSR 64000 Configuration and Management Guide Figure 12-7 shows that an AS can have more than one route reflector. Each route reflector considers other router reflectors as non-clients. You can configure multiple route reflectors per cluster and multiple clusters per AS.
Configuring BGP name is the BGP neighbor peer group name that is the route reflector client. Example The commands in the following example configure Routers New York and Boston as route reflector clients (as shown in Figure 12-6): MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 1.1.1.1 MOT(config-bgp)#neighbor 1.1.1.1 MOT(config-bgp)#neighbor 2.2.2.2 MOT(config-bgp)#neighbor 2.2.2.
BSR 64000 Configuration and Management Guide Restoring Route Reflection from a Route Reflection Client By default, the clients of a route reflector are not required to be fully meshed and the routes from a client are reflected to other clients. However, if the clients are fully meshed, route reflection with the same set of clients is not required. Also, if client-to-client reflection is enabled, the clients of a route reflector cannot be members of a peer group.
Configuring BGP Example The commands in the following example show four configured route-reflector-clients for a router acting as a route reflector (as shown in Figure 12-8). The no bgp client-to-client reflection command disables client-to-client reflection because the clients are fully meshed. MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 140.20.10.2 route-reflector-client MOT(config-bgp)#neighbor 140.20.10.3 route-reflector-client MOT(config-bgp)#neighbor 140.20.10.
BSR 64000 Configuration and Management Guide 2. To configure individual route flap dampening parameters, use the bgp dampening command in Router BGP Configuration mode, as shown below: MOT(config-bgp)#bgp dampening [ ] where: half-life is the half-life period in minutes; valid values are 1 to 45; default is 15. reuse is the reuse penalty limit below which dampened routes become available again; valid values are 1 to 20000; default is 750.
Configuring BGP Example The following commands create the route map: 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. MOT(config)#ip as-path access-list 1 deny ^300 MOT(config)#ip as-path access-list 1 permit any Clearing Route Flap Dampening 1.
BSR 64000 Configuration and Management Guide Shutting Down a Neighbor or Peer Group 1. To terminate any active session for a specified BGP neighbor or peer group and remove all associated routing information, use the neighbor shutdown command in Router BGP Configuration mode, as shown below: MOT(config-bgp)#neighbor { | } shutdown where: ip-address is the IP address of the neighbor. name is the name of the peer group.
Configuring BGP 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; otherwise, the connection between them is not made. The authentication feature uses the MD5 algorithm command that causes the generation and checking of the MD5 digest on every segment sent on the TCP connection.
BSR 64000 Configuration and Management Guide MOT(config-bgp)#neighbor { | } advertisement-interval where: ip-address is the IP address of the neighbor. name is the name of the BGP peer group. seconds is the advertisement interval time in seconds; valid values are 0 to 600. 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.
Configuring BGP Figure 12-9 shows Router Miami is configured with Router Washington as an external peer. Because Router Miami and Router Washington are connected together via Router Boston, rather than by a direct link, the neighbor ebgp-multihop command is used. AS 200 Boston 1.1.1.2 3.3.3.1 1.1.1.1 AS 200 Washington AS 100 3.3.3.
BSR 64000 Configuration and Management Guide MOT(config-bgp)#neighbor { | } maximum-prefix [ ] [warning-only] where: ip-address is the IP address of the neighbor. name is the name of the BGP peer group. num is the maximum number of prefixes allowed from this neighbor. threshold is the percent of the maximum at which the router generates a warning message; valid entries are 1 to 100; default is 75 percent.
Configuring BGP In the network shown in Figure 12-10, Router San Francisco advertises network 172.56.0.0 to Router Miami with a next hop attribute of 172.56.20.1. Router Miami advertises network 120.80.0.0 to Router San Francisco with a next hop attribute of 172.56.20.2. In BGP, the next hop of EBGP-learned routes is carried without modification in IBGP. Because of this BGP rule, Router Miami advertises 172.56.0.0 to its IBGP peer (Router New York) with a next hop attribute of 172.56.20.1.
BSR 64000 Configuration and Management Guide The following commands configure Router New York: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 130.60.20.1 remote-as 300 The following commands configure Router San Francisco: MOT(config)#router bgp 300 MOT(config-bgp)#neighbor 172.56.20.2 remote-as 100 MOT(config-bgp)#network 172.56.0.
Configuring BGP AS 100 AS 200 172.24.0.0 172.30.0.0 172.24.30.1 172.56.10.3 NY Washington Frame Relay Network 172.24.50.1 Miami 172.56.10.2 SF 172.56.10.1 Figure 12-11 Using the neighbor next-hop-self Command Example The following commands configure Router San Francisco: MOT(config)#router bgp 200 MOT(config-bgp)#neighbor 172.56.10.1 remote-as 200 MOT(config-bgp)#neighbor 172.56.10.
BSR 64000 Configuration and Management Guide • • • • • • • • Configuring BGP Administrative Weights Adjusting BGP Timers Setting the Administrative Distance for a Route Disabling Route Summarization Configuring Aggregate Addresses Assigning an Interface to BGP Session Configuring a Default Route Redistribution Resetting BGP Connections Once you define two routers to be BGP neighbors, they form a BGP connection and exchange routing information.
Configuring BGP Configuring BGP Soft Reconfiguration To make a change in routing policy, you must clear a BGP session. This causes cache invalidation, which may have a large impact on the operation of your networks. Inbound soft reconfiguration needs inbound updates from a neighbor and enables the new inbound policy to take effect. Outbound soft reconfiguration sends a new set of updates to a neighbor and causes the new local outbound policy to take effect without resetting the BGP session.
BSR 64000 Configuration and Management Guide 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.
Configuring BGP AS 200 AS 100 NY Albany Chicago IBGP AS 300 192.56.0.
BSR 64000 Configuration and Management Guide 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. Initially, all routes learned from the neighbor have the assigned weight. The BSR chooses the route with the highest weight as the preferred route if multiple routes exist for a particular network.
Configuring BGP AS 300 192.24.0.0 NY 4.4.4.1 AS 200 AS 400 160.80.0.0 192.56.0.0 LA Albany AS 100 150.60.0.0 Boston 3.3.3.
BSR 64000 Configuration and Management Guide Example For example, the commands in the following example configure Router Los Angeles (as shown in Figure 12-13) using the neighbor weight command. This configuration assigns the weight attribute of 1000 to all route updates received from AS 100 and assigns 500 to the weight attribute of all route updates from AS 300. This causes Router Los Angeles to send traffic through Router Boston to destinations reachable via both the ASs.
Configuring BGP Using an AS Path Access List The commands in the following example configure Router Los Angeles using an AS path access list. Filter List 1 assigns a weight attribute of 1000 to updates received from neighbors from AS 100. Access List 1 permits any update whose AS-path attribute begins with 100 (specified by “^”). The same is true for Access List 2 regarding AS 300. Filter List 2 assigns a weight attribute of 500 to updates received from AS 300.
BSR 64000 Configuration and Management Guide holdtime – is the interval in seconds, after which, not receiving a keepalive or any other BGP message, the BSR declares a BGP peer dead; default is 180 seconds. To configure the keepalive frequency and holdtime interval for a BGP peer or peer-group, use the neighbor timers command in Router BGP Configuration mode, as shown below: MOT(config-bgp)#neighbor [ | ] timers where: ip-address is the IP address of the BGP peer.
Configuring BGP You can change an administrative distance if you know that another protocol provides a better route than that learned via EBGP or if you want IBGP to show preference for internal routes. Note: Changing the administrative distance of BGP internal routes is dangerous and is not recommended. It can cause the accumulation of routing table inconsistencies that can break routing within an AS and between ASs.
BSR 64000 Configuration and Management Guide MOT(config)#router bgp 100 MOT(config-bgp)#network 160.20.0.0 MOT(config-bgp)#neighbor 156.30.10.1 remote-as 100 MOT(config-bgp)#neighbor 131.65.1.2 remote-as 200 MOT(config-bgp)#distance bgp 20 20 200 Disabling Route Summarization Route summarization condenses routing information. Without summarization, each router in a network must retain a route to every subnet in the network.
Configuring BGP MOT(config-bgp)#no auto-summary Router NY's routing table Destination A1 A2 A3 A4 A5 B1 B2 B3 B4 Next hop Direct Direct Boston Albany Boston Direct Chicago Chicago Chicago B2 B1 Chicago B3 A1 B4 A4 A2 Boston Router Albany's routing table A3 Boston Router Albany's routing table Destination A1 A2 A3 A4 A5 B Next hop Direct Direct NY Direct Boston NY Destination B1 B2 B3 B4 A Next hop Direct Direct Direct Direct NY A5 Figure 12-14 Route Summarization Example The commands in the
BSR 64000 Configuration and Management Guide MOT(config-bgp)#no auto-summary 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. 1.
Configuring BGP 4. To identify the route map for manipulating the attributes of the aggregate route, use the aggregate attribute-map command in Router BGP Configuration mode, as shown below: MOT(config-bgp)#aggregate attribute-map where: ip-address is the aggregate IP address. address-mask is the aggregate IP mask. name is the route map name. 5.
BSR 64000 Configuration and Management Guide Example Network 200.10.0.0 is an illegal Class C network address. This address becomes legal when it is represented in CIDR notation as 200.10.0.0/16. The /16 specifies that the subnet mask consists of 16 bits (counting from left to right). Thus, the CIDR address, 200.10.0.0/16, is the same as 200.10.0.0 with a network mask of 255.255.0.0. MOT(config)#router bgp 100 MOT(config-bgp)#aggregate-address 200.10.0.0 255.255.0.
Configuring BGP ip-address is the IP address of the BGP neighbor. name is the name of the BGP peer group. loopback indicates the interface type. num is the loopback number; valid values are 1 to 16. Note: The loopback interface is unrelated to the IP loopback address 127.x.x.x. Example Figure 12-15 shows a network that can benefit from the use of a loopback interface, because an alternate path exists. Routers New York and Albany are running IBGP within AS 100.
BSR 64000 Configuration and Management Guide NY S0 Albany Loopback interface 0: 160.10.0.1 S1 Boston Figure 12-15 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 140.10.0.1 255.255.255.255 MOT(config-if)#exit MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 192.56.42.
Configuring BGP where: ip-address is the IP address of the neighbor. name is the name of the BGP peer group. map-name 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. Example In Figure 12-16, Router Boston originates the default route 0.0.0.0/0.0.0.0 toward Router Miami only.
BSR 64000 Configuration and Management Guide AS 100 Chicago IBGP AS 200 150.20.30.1 150.20.20.2 Boston EBGP 150.20.20.1 Miami bgp0018 Figure 12-16 Dynamically Configuring a Default Route 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.
Configuring BGP Configuring BGP Path Selection Algorithm BGP selects the best possible path for a route and installs it in its route table. If only one route exists for a specific destination, BGP selects that route, because, by definition, it is the best route. If multiple routes exist, BGP uses the BGP Path Selection Algorithm to select the best path. BGP Path Selection Algorithm The BGP path selection process uses the following sequential criteria to select a path: 1.
BSR 64000 Configuration and Management Guide 9. BGP uses the route with the lowest IGP metric to the BGP nexthop. 10. BGP prefers EBGP over IBGP. All confederation paths are considered IBGP. 11. If the best route and a new route are both external and maximum-paths n is enabled, BGP inserts the new route into the IP routing table as an alternate path. EBGP multipath load sharing can occur at this point. The forwarding table holds 1 - 2 paths. 12.
Configuring BGP AS 200 192.30.10.1 AS 100 Chicago 192.30.10.2 NY AS 300 140.20.30.1 IBGP AS 500 140.20.30.2 156.10.0.0 LA 192.56..10.1 AS 400 Boston Washington 192.56.10.2 bgp0019 Figure 12-17 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.
BSR 64000 Configuration and Management Guide 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). Use a route map to specifically assign a local preference for updates from AS 400.
Configuring BGP Table 12-1 BSR Origin Assignment BGP Route Entry Type Origin Code Redistributed INCOMPLETE Network IGP Peer-based default (0/0) IGP Example In Figure 12-18, 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.
BSR 64000 Configuration and Management Guide The following commands configure Router Boston: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 170.20.20.1 remote-as 100 MOT(config-bgp)#neighbor 1.1.1.2 remote-as 300 MOT(config-bgp)#network 150.20.0.0 MOT(config-bgp)#redistribute static MOT(config-bgp)#exit MOT(config)#ip route 175.40.0.0 255.255.0.0 The following command configure Router New York: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 150.20.30.1 remote-as 100 MOT(config-bgp)#network 175.
Configuring BGP In Figure 12-19, Router Boston advertises network 150.60.0.0 in AS 400 with an AS-path of 100. When the BGP route arrives in AS 400, Router Los Angeles adds its AS number. When the BGP route arrives at Router New York, its AS_path attribute contains AS numbers 400 and 100. AS 300 192.55.0.0 NY AS 400 192.56.0.0 LA AS 100 150.60.0 Boston 3.3.3.
BSR 64000 Configuration and Management Guide 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. To compare MED attributes from different neighbors in different ASs, use the bgp always-compare-med command.
Configuring BGP MOT(config)#router bgp 200 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.
BSR 64000 Configuration and Management Guide 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). no advertise does not advertise a route to any peer.
Configuring BGP To define a route map, use the route-map command in Global Configuration mode, as shown below: MOT(config)#route-map [permit | deny] where: name uniquely identifies a route map. permit specifies consider the route for further operation. deny specifies do not consider the route for further operation. sequence-number uniquely identifies an instance of the route map. Instances with lower sequence numbers are parsed first.
BSR 64000 Configuration and Management Guide Table 12-1 match Commands Command Description match ip address Matches an IP access list. match ip next-hop Matches the next-hop ip address. match metric Matches a routing metric value. For BGP, this is the MED. match ip route-src Matches neighbor IP address Table 12-2 shows set commands for creating route maps. Table 12-2 set Commands Command Description set as-path prepend Modifies an AS path. set comm_list Removes selected communities.
Configuring BGP The following commands, executed from Global Configuration mode, create AS_path access list 1: MOT(config-bgp)#ip as-path access-list 1 permit ^400 These commands, also executed from Global Configuration mode, apply the route map to a BGP neighbor: MOT(config)#router bgp 100 MOT(config-bgp)#neighbor 160.20.30.4 route-map locpref in MOT(config-bgp)#exit Handling Access Lists An access list is a sequential collection of permit and deny conditions.
BSR 64000 Configuration and Management Guide any is the abbreviation for 0.0.0.0 address and 255.255.255.255 wildcard to match against any IP address. Permit and deny conditions in an IP access list apply to IP addresses. Use the neighbor distribute-list command to apply an access list to a BGP neighbor. Example This sample configuration filters BGP updates from a BGP neighbor.
Configuring BGP MOT(config-bgp)#ip as-path access-list {permit | deny} where: access-list-number is the access list number. path-expression is a valid path regular expression. Example The commands in the following example configure a router with two AS path access lists. Routes that pass AS path access list 1 are sent to one destination. Routes that pass AS path access list 2 are accepted from another destination.
BSR 64000 Configuration and Management Guide • • • no-export no-advertise no-sub-confed export In addition, you can define a community number to advertise to a specific community number. All destinations belong to the general Internet community by default. 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 entries with its EBGP peers.
Configuring BGP community-list-number identifies the community list. permit indicates accept the advertisements. deny indicates reject the advertisements. local-as indicates the well-known community Local-AS. 3.
BSR 64000 Configuration and Management Guide where: community-list-number is the route map name. permit indicates accept the advertisements. deny indicates reject the advertisements. no-export is the name of a well-known community. 6.
Configuring BGP AS 200 160.30.0 3.3.3.1 NY 3.3.3.2 AS 100 160.20.0 Boston 2.2.2.2 AS 300 160.40.0 Miami 2.2.2.1 Figure 12-21 Using a Community List 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 permit routes from AS 200, as shown in Illustration 12-21.
BSR 64000 Configuration and Management Guide The next commands, also executed in Global Configuration mode, define the first instance of the route map with the appropriate match and set clauses and specify route map 10, instance 10. This permits the route to be accepted and its local preference to be set to 50. The last command indicates that the route is part of the communities defined in Community List 1.
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. Routes are redistributed to advertise networks on another routing protocol.
BSR 64000 Configuration and Management Guide 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, as shown below: MOT(config-bgp)#redistribute ospf {[external | internal] | metric | route-map | } where: The external argument is used to redistribute external OSPF routes. The internal argument is used to redistribute internal OSPF routes.
Configuring BGP weight sets the network weight value from 0 to 65535 for redistributing RIP routes into BGP. cr is a command return that redistributes of all ISIS routes. • Use the redistribute rip command in Router Configuration mode to redistribute RIP routes into BGP, as shown below: MOT(config-bgp)#redistribute rip {metric | route-map | weight | } where: metric is the redistribution metric number for RIP routes.
BSR 64000 Configuration and Management Guide Monitoring BGP Use these show commands to monitor BGP: • • • • • • • • • • show ip bgp show ip bgp cidr-only show ip bgp neighbors show ip bgp paths show ip bgp peer-group show ip bgp summary show ip bgp regexp show ip as-path-access-list show ip community list show ip protocols [summary] Use the show ip bgp community-list command to display the routes that are permitted by a BGP community list.
13 Configuring VRRP
Configuring VRRP Overview This chapter describes how to configure the Virtual Router Redundancy Protocol (VRRP) for the BSR 64000™ system using the command line interface (CLI). For further information on the CLI commands described in this chapter, refer to the BSR 64000 Command Reference Guide.
BSR 64000 Command Reference Guide • • • • • • • Enabling VRRP Creating a Virtual Router Configuring a Virtual IP Address Specifying Authentication String Configuring Primary IP Address Enabling a Virtual Router Configuring Authentication Type Enabling VRRP To enable VRRP on all interfaces that are configured to run VRRP, use the ip vrrp command in Global Configuration mode, as shown below. This command enables all interfaces so that multiple virtual routers can be enabled or disabled at one time.
Configuring VRRP Configuring a Virtual IP Address To configure a virtual IP address or addresses, use the ip vrrp address command in Interface Configuration mode, as shown below. VRRP is not enabled for the virtual router until you specify at least one IP address. If you specify one or more IP addresses, those addresses are used as the designated IP address or addresses by associated routers. Use the no ip vrrp address to remove the virtual IP address or addresses.
BSR 64000 Command Reference Guide MOT(config-if)#ip vrrp authentication key num:1,255the identification of a configured virtual router bounded-stringa string of up to 8 characters Example The following example shows how to specify the authentication string, text only. The system is configured to use mot as the authentication key to operate between other VRRP routers for virtual router 1 on the configured interface.
Configuring VRRP Enabling a Virtual Router To enable a virtual router on a configured interface, use the ip vrrp enable command in Interface Configuration mode, as shown below. This brings up a specific VRRP router on the interface when the router is enabled. The command brings the VRRP router to either backup or master when the router is enabled, if at least one IP address is configured for the virtual router. Use the no vrrp enable command to disable a virtual router on a configured interface.
BSR 64000 Command Reference Guide textauthentication type can be simple text Note: You must configure the same authentication type on all routers associated with a virtual router. An Authentication mismatch does not prevent a router from taking over as the designated master, however, it may cause VRRP to work incorrectly. This can result in lack of communication between virtual routers.
Configuring VRRP Specifying Priority To specify the priority of the router to act as master for a virtual router, use the ip vrrp priority command in Interface Configuration mode, as shown below. Use the ip vrrp priority command to select a master when multiple routers are associated with the same virtual router. If two routers have the same priority, the system compares their primary IP addresses. The router with the higher IP address value takes precedence.
BSR 64000 Command Reference Guide Pre-empting a Master To configure a higher priority backup that can pre-empt a lower priority master, use the ip vrrp preempt command in Interface Configuration mode, as shown below. If virtual routers have IP addresses that do not belong to any router interface, use the ip vrrp preempt command to specify which router may pre-empt. Use the no ip vrrp preempt command to disable pre-emption of a lower priority master by a higher priority backup.
Configuring VRRP interval is the advertisement time interval in seconds; valid entries are 1 to 255. Example This example configures the system to send VRRP advertisements every three seconds for the virtual router on the configured interface Ethernet 1/0, if the router is configured as the master for the virtual router 1. If not, this interval is the factor that determines the router configured as backup for virtual router 1.
BSR 64000 Command Reference Guide Gathering Virtual Router Information • • • • Monitoring Critical Link State Monitoring Virtual Router Information Monitoring Ethernet Virtual Routers Obtaining Summary Information Monitoring Critical Link State To configure one or more ip addresses for a virtual router to monitor as critical link states, use the ip vrrp verify-availability command in Interface Configuration mode, as shown below.
Configuring VRRP Monitoring Virtual Router Information To displays detailed information on virtual routers that are configured for VRRP, use the show ip vrrp command in all modes except User EXEC mode. This command verifies router virtual status.
BSR 64000 Command Reference Guide 0 bad authentication type, 0 mismatched authentication type 0 failed authentication, 0 zero priority Advertisement Sent: 60367 total, 0 zero priority Become master: 1 times Monitoring Ethernet Virtual Routers To display detailed information on all of the virtual routers with an Ethernet interface, use the show ip vrrp ethernet command in User EXEC mode, as shown below. MOT#show ip vrrp ethernet / [] where: slot is the interface slot number.
Configuring VRRP Advertisement Sent: 4 total, 0 zero priority Become master: 3 times Interface ethernet 7/0, VRID 3 : Status: vrrp is enabled, in state master, priority is 255 advert interval is 1 sec, preempt mode is on use no authentication, up since 16:48:59 ago last state change 16:48:59 ago primary ip is 10.10.20.20, total virtual ip address(es) is 1 virtual ip address(es): 10.10.20.
BSR 64000 Command Reference Guide Obtaining Summary Information To show summary information on all VRRP routers configured on all interfaces on the router, use the show ip vrrp summary command in User EXEC mode, as shown below.
14 Configuring Packet Over SONET
Configuring Packet Over SONET Overview This chapter describes how to configure the Packet Over SONET (POS) interface for the BSR 64000™ using the command line interface (CLI). For further information on the CLI commands described in this chapter, refer to the BSR 64000 Command Reference Guide.
BSR 64000 Configuration and Management Guide About SONET/SDH The Synchronous Optical Network (SONET) standard provides for data transmission over fiber optic cable and high-bandwidth utilization and efficiency over Internet links. The SONET standard defines industry interface standards at the physical layer of the OSI seven-layer model. This standard defines a hierarchy of interface rates that allow data streams at different rates to be multiplexed. SONET establishes Optical Carrier (OC) levels from 51.
Configuring Packet Over SONET POS Interface Configuration Tasks The following POS module configuration tasks are mandatory: • • • Configuring the POS Interface Configuring PPP Configuring the Network Clock Source for SONET Configuring the POS Interface Follow these steps to configure the POS interface: 1.
BSR 64000 Configuration and Management Guide Configuring PPP Table 14-2 describes the PPP features and commands that are available on the POS module: Table 14-2 PPP Commands Command Description Default Value ppp mtu Maximum transmission 1500 bytes unit packet size allowed on the POS interface 72 to 1500 bytes ppp negotiation-count Number of attempts before 10 attempts PPP connection is dropped 1 to 100 attempts ppp timeout ncp Maximum wait time for network layer to negotiate before PPP connecti
Configuring Packet Over SONET n is the number of permitted negotiation attempts from 1 to 100. 3. To set the maximum PPP wait time for the network layer to negotiate before disconnecting the PPP link on the POS interface when there is no activity on the link, use the ppp timeout ncp command in Interface Configuration mode, as shown in the following example.
BSR 64000 Configuration and Management Guide Table 14-3 describes the network clocking commands that are available on the BSR and the POS module: Table 14-3 Network Clocking Commands Command Description Default Value network-clock-select Enables the E1 Building none [1 | 2] bits e1 Integrated Timing Supply (BITS) network clocking to be derived from the central office (CO) BITS source. 1 sets the priority of the clocking source to primary or 2 sets the priority of the clocking source to secondary.
Configuring Packet Over SONET t1 specifies a T1 BITS signal. esf-b8zs is ESF framing with B8ZS line coding. sf-d4 is SF-D4 framing with AMI line coding. slc96 is SLC96 framing with AMI line coding. t1dm is T1DM framing with AMI line coding e1 specifies an E1 BITS signal. pcm31-crc is PCM-31 framing with AMI line coding and CRC Multiframe support. pcm31-hdb3 is PCM-31 framing with HDB3 line coding and CRC Multiframe support. pcm31-nocrc is PCM-31 framing with AMI line coding and no CRC Multiframe support.
BSR 64000 Configuration and Management Guide BSR(config)#network-clock-select 2 bits [t1 {esf-b8zs | sf-d4 | slc96 | t1dm} | e1 {pcm31-crc | pcm31-hdb3 | pcm31-nocrc}] [a | b] where: 2 is the priority assigned to the secondary network clock. t1 specifies a T1 BITS signal. esf-b8zs is ESF framing with B8ZS line coding. sf-d4 is SF-D4 framing with AMI line coding. slc96 is SLC96 framing with AMI line coding. t1dm is T1DM framing with AMI line coding e1 specifies an E1 BITS signal.
Configuring Packet Over SONET where: 1 is the priority assigned to the primary network clock. 2 is the priority assigned to the secondary network clock. slot is the POS slot on the BSR. interface is the POS interface from which the clocking is recovered. 2.
BSR 64000 Configuration and Management Guide BSR(config-if)#pos internal-clock Configuring SONET The following sections describe how to set a variety of SONET commands: • • • • Optionally Disabling SONET Payload Scrambling Changing the SONET Framing Type Changing the CRC Function on the POS Interface Defining SONET Frame Overhead Bytes Table 14-4 describes the SONET features and commands that are available on the POS module: Table 14-4 SONET Commands Command Description Default pos scramble Scramb
Configuring Packet Over SONET Table 14-4 SONET Commands Command Description Default Value pos flag j0 16byte Defines 16 byte section trace message undefined Text string containing the 16 byte sequence. pos flag j1 16byte Defines 16 byte path trace undefined message Text string containing the 16 byte sequence. pos flag j1 64byte Defines 64 byte path trace undefined message Text string containing the 64 byte sequence.
BSR 64000 Configuration and Management Guide To return to the default, which is payload scrambling, use the pos scramble command in Interface Configuration mode, as shown below: BSR(config-if)#pos scramble Changing the SONET Framing Type The BSR framing type default is SONET. Follow these steps to change the framing type: 1. To set the framing type for SDH, use the pos framing sdh command in Interface Configuration mode, as shown in the following example. MOT(config-if)#pos framing sdh 2.
Configuring Packet Over SONET Defining SONET Frame Overhead Bytes SONET overhead bytes identify information in the SONET frame. Refer to the GR-253-CORE document for STS Path Signal Label Assignments and the hexadecimal values required for the SONET frame overhead bytes. Follow these steps to specify flags for the SONET frame overhead bytes: 1. The c2 byte of the SONET frame is a path signal identifier.
BSR 64000 Configuration and Management Guide 4. To configure the j0 byte as a hexadecimal section trace byte, use the pos flag j0 command in Interface Configuration mode, as shown below: MOT(config-if)#pos flag j0 where: hexnum is the hexadecimal value for the j0 byte. 5.
Configuring Packet Over SONET string is a text string containing the 62 byte sequence. The remaining 2 bytes are automatically set to CR/LF for framing purposes. 8. To configure the j1 byte as a single hex byte, use the pos flag j1 command in Interface Configuration mode, as shown below: MOT(config-if)#pos flag j1 where: hexnum is the hexadecimal value for the j1 byte. 9. The s1 byte identifies the timing source for SONET frame synchronization.
BSR 64000 Configuration and Management Guide Table 14-5 describes the SONET alarms that can be configured on the POS module: Table 14-5 SONET Alarm Commands Command Description Default pos threshold b1-tca The BER threshold for the 4 (10E-4 b1 threshold crossing Rate) alarm (TCA) 3 to 9 (10E-3 to 10E-9 Rate) pos threshold b2-tca The BER threshold for the 4 which is b2 threshold crossing 10E-4 Rate.
Configuring Packet Over SONET MOT(config-if)#pos threshold b1-tca <3-9> where: <3-9> is the 10E-3 to 10E-9 Rate. 2. To configure the BER threshold for the b2 TCA, use the pos threshold b2-tca command in Interface Configuration mode as shown below: MOT(config-if)#pos threshold b2-tca <3-9> where: <3-9> is the 10E-3 to 10E-9 Rate. 3.
BSR 64000 Configuration and Management Guide MOT(config-if)#no pos report [all | b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos] Table 14-6 describes the SONET reports that you can configure: Table 14-6 SONET Alarm Report Selections and Descriptions Alarm Report Description all All possible alarm reporting b1-tca B1 BER TCA errors b2-tca B2 BER TCA errors b3-tca B3 BER TCA errors lais Line alarm indication signal lrdi Line remote defect indi
Configuring Packet Over SONET To disable sending the line alarm indication signal on an administrative shutdown, use the no pos ais-shut command in POS Interface Configuration mode as shown below: MOT(config-if)#no pos ais-shut Changing the POS Signal Rate Table 14-7 describes the SONET signal mode command: Table 14-7 SONET Signal Mode Command Command Description Default Value pos signal mode POS module SONET signal oc3 oc12 or oc3 To optionally change the POS module SONET signal rate for OC12, u
BSR 64000 Configuration and Management Guide Specifying the POS Loopback Mode Type You can use POS loopback commands to isolate the fault on an end-to-end circuit, especially when the circuit is down. Table 14-8 describes the POS loopback mode command: Table 14-8 SONET Signal Mode Command Command Description Default Value pos loop POS loopback mode type none internal, line, txrx-line, txpos-rxpos Follow these steps to specify the POS loopback mode: 1.
Configuring Packet Over SONET 4.
BSR 64000 Configuration and Management Guide 2.
Configuring Packet Over SONET Figure 14-4 displays the command output for the POS interface: Figure 14-4 show interface pos Command Output Table 14-9 describes the show interface pos command output fields. Table 14-9 show interface pos Output Fields and Descriptions Field Description POS1/0 is up/down Indicates whether the physical link is currently up or down. line protocol is up/down Indicates whether the PPP link or protocol is currently up or down. Hardware is Hardware type.
BSR 64000 Configuration and Management Guide Table 14-9 show interface pos Output Fields and Descriptions 14-24 Field Description LCP Indicates if the Link Control Protocol is open or closed. LCP is used to negotiate PPP configuration parameters. IPCP Indicates if the Internet Protocol Control Protocol is open or closed. IPCP is used for transporting IP traffic over a PPP connection. Last input Number of hours, minutes, and seconds since the last packet was successfully received by an interface.
Configuring Packet Over SONET Table 14-9 show interface pos Output Fields and Descriptions Field Description input errors Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts. CRC Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received.
BSR 64000 Configuration and Management Guide To display information about the POS module hardware, SONET alarms and BER thresholds, use the show controllers pos command in Privileged EXEC mode as shown below: Note: The Active Defect field in the show controllers pos command output shows all alarms currently present on the interface. MOT#show controllers pos / where: slot is the POS module slot on the BSR 64000 chassis. interface is the line POS interface on the POS module.
Configuring Packet Over SONET Figure 14-5 show controllers pos Command Output Table 14-10 defines the SONET Alarms and BER threshold information that is reported on the POS interface console: Table 14-10 SONET Alarms and Identifications Alarm Identification POS 5/0 POS slot and interface. SECTION Errors that occur in the SONET Section. A section may be between Customer Premises Equipment (CPE) and SONET Service Provider Equipment (SPE). SLOS Section los of signal errors.
BSR 64000 Configuration and Management Guide Table 14-10 SONET Alarms and Identifications 14-28 Alarm Identification SLOF Section loss of frame errors. SLOF is detected when a severely errored frame (SEF) defect on the incoming SONET signal persists for 3 milliseconds. b1-tca B1 BER TCA (crossing threshold) For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the next frame.
Configuring Packet Over SONET Table 14-10 SONET Alarms and Identifications Alarm Identification P-RDI Path remote defect indication errors. Path remote defect indication is reported by the downstream PTE when it detects a defect on the incoming signal. b3-tca B3 BER TCA (crossing threshold) For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the next frame.
Index A ABR, 11-1, 11-6, 11-9 access control using community name, 4-16 access list AS-path, 7-6 IP, 7-6 name, 9-37 number, 9-37 access policy creating, 4-18 activating upstream Forward Error Correction, 6-32 adding ARP cache entry, 5-14 permanent ARP entry, 5-14 address IP, 9-32 address range specifying, 11-9, 11-10 Address Resolution Protocol configuring, 5-14 Address Resolution Protocol (ARP), 6-11 addresses Ethernet, 5-14 Internet, 5-14 MAC, 5-14 route, 7-1, 11-10 AK BPI, 6-49 grace-time, 6-50 permanen
BSR 64000 Configuration and Management Guide stub area default summary route, 11-7 OSPF area ID, 11-2 associating group to MIB view, 4-19, 4-21 broadcast address defining, 5-17 scheme, 5-17 authenticaton OSPF MD5, 11-21 broadcast packets directed, 5-16 flooded, 5-16 limited, 5-16 Authorization Key setting, 6-49 broadcast storms avoiding, 5-17 autonomous system, 9-32 BSR configuring, 3-1 B buffer clearing, 3-16 backbone network, 1-1 OSPF, 11-11 burst profile, 6-129 C backspace key, 2-15 Baselin
Index CM authentication information obtaining, 6-47 CM information displaying, 6-118 CMTS interface BPI settings viewing, 6-50 BPI statistics viewing, 6-50 command history buffer size setting, 2-11 disabling, 2-12 using, 2-11 command line interface, 1-2, 2-1, 9-31, 13-1, 14-1 command lines handling, 2-14 commands area area-id virtual-link router-id, 11-12, 11-13, 11-14 area authentication, 11-6 area authentication message-digest, 11-6 area default-cost, 11-7 area nssa, 11-8 area-id range address mask, 11-9
BSR 64000 Configuration and Management Guide neighbor distribute-list, 7-6 neighbor filter-list, 7-7 network, 9-33 network network-number, 9-33 offset-list, 9-37 ospf database-filter all out, 11-22 output-delay, 9-38 ping, 5-23 recalling, 2-12 redistribute, 7-12 route map, 7-1 route-map, 7-1 router ospf process-id, 11-2 router rip, 9-33 set as-path prepend, 7-4 set community, 7-4 set ip next-hop, 7-4 set local-preference, 7-5 set metric, 7-5 set metric-type, 7-5 set origin, 7-3, 7-4 set-community, 7-9 show
Index snmp-server trap, 4-7 snmp-server trap rate-limit, 4-26 snmp-server user, 4-7, 4-19 snmp-server view, 4-7, 4-12, 4-20 summary address prefix mask, 11-8 summary-address, 11-10 upstream channel width, 6-28 username, 3-6 version, 9-34 community name defining, 4-16 completing partial command name, 2-14 configuration tasks basic, 3-1 configured route maps displaying, 7-19, 7-20, 7-21 configuring AS-path access list, 7-7 Baseline Privacy, 6-49 BSR, 3-1 console logging, 3-14 FTP access, 3-17, 3-29 group mod
BSR 64000 Configuration and Management Guide suppress limit, 7-13, 7-14 data backoff, 6-20 Data Encryption Standard, 6-49 Data Over Cable Service Interface Specification standard, 1-1 determing number of dropped packets, 6-14 determining number of dropped packets, 6-26 DHCP relay information option, 6-2 data packet, 9-31 diff, 6-42 datagram fragmentation, 5-2 packet format, 5-2 reassembly, 5-2 routing to remote host, 5-2 differential encoding, 6-42 decreasing OSPF link state database size, 11-10 defa
Index parent-child links, 8-11 summary address, 8-15 ICMP netmask reply, 5-23 IP redirects, 5-23 logging process, 3-11 OSPF, 11-2 MD5 authentication, 11-21 power adjustment, 6-29 rate-limiting function, 6-14 SNMP, 4-8 traps, 4-23 upstream data transmission rate-limit, 6-25 upstream FEC, 6-32 distance-vector routing, 9-31 distribution hub, 1-1 DOCSIS, 1-1 standard, 1-1 down arrow key, 2-12 downstream data encrypting, 6-49 downstream data transmission rate-limit enabling, 6-14 downstream port disabling, 6-
BSR 64000 Configuration and Management Guide flooded broadcast packets, 5-16 hop count, 9-32 forcing packet fragmentation, 6-34 host route, 9-32 Forward Error Correction CMTS use of, 6-32 upstream parameter, 6-20 host authorization dynamic, 6-6 static, 6-6 verifying, 6-6 forwarding centralized, 1-1 fragmentation, 5-17 frequency, 6-20 Host-to-Host Transport layer, 5-2 I frequency band, 6-63 ICMP, 5-20 frequency range parameter, 6-12 ICMP echo request packets sending, 5-23 FTP access configuring
Index Internet address, 5-14 Internet Control Message Protocol, 5-20 Internet Group Management Protocol (IGMP), 8-16 to 8-20 host-query messages, 8-17, 8-18 querier timeout interval, 8-19 version, 8-18 L learning route, 7-1 left arrow key, 2-13, 2-15 life-time, 6-49 limited broadcast packets, 5-16 Internet Service Provider, 11-8 line, 14-28 interpacket delay RIP update, 9-38 link state update packet, 11-20 Interval Usage Code, 6-42 IP address, 9-32, 11-23 monitoring, 5-29 multicast, 11-1 packet, 5-2
BSR 64000 Configuration and Management Guide maximum CPE host number specifying, 6-48 verifying, 6-49, 6-124 message broadcast, 9-32 metric setting, 7-5 metric type setting, 7-5 MIB, 1-2 N navigating command line, 2-13 network advertising, 7-12 local link advertisement, 11-1 number, 9-33 OSPF designated router for, 11-20 MIB view configuring, 4-20 defining, 4-19 Network Access layer, 5-2 minislot size, 6-20 next hop field, 9-32 modifying AS path, 7-4 modulation interface profile configuring, 6-41 mod
Index area ID assigning, 11-2 defining, 11-1 area parameter configuring, 11-5 configuring, 11-1, 13-1 designated network router, 11-20 distance value changing, 11-17 enabling, 11-2 interface-specific parameter changing, 11-19 link state database decreasing, 11-10 LSA flooding blocking, 11-22 NSSA area parameter specifying, 11-8 password, 11-20 route redistributing from other protocol, 11-10 routing process creating, 11-2 stub area support, 11-6 packet fragmentation forcing, 6-34 parameters BPI, 6-50 parti
BSR 64000 Configuration and Management Guide Q QoS configuring, 6-54 functions, 1-1 Quality of Service configuring, 6-54 functions, 1-1 R radio frequency channel width, 6-20 range backoff, 6-20 rate-limiting function enabling, 6-14 recalling commands, 2-12 redirects enabling, 5-23 redistributed routes specifying address, 11-10 specifying mask, 11-10 redistributing lists, 7-12 route into OSPF, 11-10 routes, 7-12 reducing routing table size, 5-18 re-enabling upstream FEC, 6-32 upstream Forward Error Correct
Index route maps defining, 7-1 router ID, 11-23 OSPF-based configuring, 11-1 update, 9-31 router discovery packets tracing, 5-20 Router Discovery Protocol, 5-20 routers internal, 11-1 routes redistributing, 7-12 routing centralized, 1-1 datagram to remote host, 5-2 distance-vector, 9-31 Routing Information Protocol, 9-31 routing metric value matching, 7-3 routing policy, 7-1 monitoring, 7-18 routing table information, 5-2 status displaying, 5-30 routing table entry clearing, 5-20 S scrolling line, 2-15 sc
BSR 64000 Configuration and Management Guide displaying, 6-55, 6-56 SFID DSD initiating, 6-57 Shortest Path Tree (SPT), 8-4 show history command, 2-12 show ip ospf memory, 11-31 show ip vrrp ethernet num, 13-12 Simple Network Management Protocol support for, 1-2 SLAs, 1-1 SNMP access levels configuring, 4-16 commands, 4-1 context configuring, 4-21 enabling, 4-8 monitoring, 4-27 server identification configuring, 4-13 support for, 1-2 traps configuring, 4-23 SONET b1-tca, 14-28 b2-tca, 14-28 b3-tca, 14-29 S
Index T tab key, 2-14 tag route, 9-32 TCP/IP, 5-1 TEK grace-time, 6-50 grace-time value displaying, 6-130 life-time, 6-50 life-time value displaying, 6-130 permanent, 6-50 setting, 6-49 temporary AK, 6-50 temporary traffic key, 6-50 tiered data services, 1-1 time-to-live (TTL), 8-18 tracing router discovery packets, 5-20 traffic key temporary, 6-50 Transmission Control Protocol/Internet Protocol, 5-1 transposing characters, 2-16 trap destination configuring, 4-23 trap rates restricting, 4-26 trap source co
BSR 64000 Configuration and Management Guide User Datagram Protocol, 9-31 User EXEC mode, 2-4, 2-5, 2-12 user models creating, 4-18 using command history, 2-11 USM security configuring, 4-18 V VACM security configuring, 4-18 verifying changes, 6-43 downstream rate-limiting status, 6-14 host authorization, 6-6 maximum CPE host number, 6-49, 6-124 synchronization message interval, 6-45 viewing BPI settings, 6-50 BPI statistics, 6-50 CMTS interface BPI settings, 6-50 CMTS interface BPI statistics, 6-50 modul
