ADC CUDA 3 Administration Manual

Ip access switch cli-based administration guide
Table of Contents

Advertisement

Quick Links

P
N
. 780-000052-00
ART
O
P
S
2001
UBLISHED
EPTEMBER
Cuda 12000 IP Access Switch
CLI-based Administration Guide
Release 3.0
http://www.adc.com

Advertisement

Table of Contents
loading

Summary of Contents for ADC CUDA 3

  • Page 1 . 780-000052-00 2001 UBLISHED EPTEMBER Cuda 12000 IP Access Switch CLI-based Administration Guide Release 3.0 http://www.adc.com...
  • Page 3 This manual is provided by ADC on an ”AS IS, WITH ALL FAULTS” basis, without any representation or warranty of any kind, either express or implied, including without limitation any representations or endorsements regarding use of, the results of, or performance of the equipment or software, its appropriateness, accuracy, reliability, or correctness.
  • Page 4 What follows is a summary of the warranty statement. The summary is not binding on ADC and is provided to you merely as a convenience.
  • Page 5: Table Of Contents

    ONTENTS 12000 IP A UIDE BOUT UIDE Document Objective Audience Document Organization Notations Command Syntax Related Documentation Contacting Customer Support DMINISTRATION 12000 O VERVIEW Introducing the Cuda 12000 IP Access Switch Hardware Software Minimum Chassis Configuration Understanding the Cuda 12000 Within Your Network Cable Modem Termination System (CMTS) IP Routing Configuration BOUT THE...
  • Page 6 IP Interface Mode OSPF Global Configuration Mode Import and Export OSPF Route Filter Modes RIP Configuration Mode Import and Export RIP Route Filter Modes Slot Mode ANAGING Understanding User Accounts Configuring Access Profiles Creating and Modifying Access Profiles Displaying Access Profiles Deleting a Profile Managing User Accounts Creating and Modifying User Accounts...
  • Page 7 ULTI HASSIS UPPORT About Multi-Chassis Support Planning Multi-Chassis Support Enabling the Jini Lookup Service Configuring Multi-Chassis Support Creating a Common User Account for the Group Viewing Chassis Details ODULE DMINISTRATION Cuda Application Modules Configuring the 10/100 Ethernet and GigE Modules Viewing Module Information Viewing Installed Modules Viewing Module Versions...
  • Page 8 IMING AND LARM About Timing and Alarm Controller Fault Reporting Assertion Levels Configuring the Power Assertion Level Configuring Fan Unit Assertion Levels Configuring Fault Reporting Removing a Fault Notification Viewing Fault Reporting Status Configuring Alarms Out Viewing Alarm Signals Out the DB-15 Connector IMPLE ETWORK About SNMP...
  • Page 9 Configuring Event Reporting Viewing Event Reporting Configuration Event Classes and SNMP System Events Clearing the Event Log Displaying Event Transmission, Reporting, and Syslog Parameters Displaying the Event Log III IP R OUTING REATING OUTE About RIP and OSPF Route Maps Creating Route Maps Using the Match Command Using the Override Command...
  • Page 10 DHCP A ONFIGURING About DHCP Authority Enabling DHCP Authority Configuring DHCP Authority Ranges Removing DHCP Authority Ranges DHCP Authority Configuration Examples ONFIGURING Configuring IP Addresses Viewing IP Interfaces Deleting IP Addresses Displaying the Routing Table Configuring Static Routes Adding Static Routes Deleting Static Routes Adding the Default Route Deleting the Default Route...
  • Page 11 Removing OSPF Virtual Interfaces Configuring OSPF Neighbor Traps Configuring IP Source Routing About IP Source Routing Adding IP Source Routes Displaying IP Source Routes Removing IP Source Routes Source Routing Configuration Example IP P ACKET ILTERING About IP Packet Filtering Enabling and Disabling IP Packet Filtering Understanding Access Lists Creating Access Lists...
  • Page 12 Joining IGMP Groups Configuring IGMP Interface Parameters Displaying IGMP Groups and Interface Parameters Deleting IGMP Groups Managing IGMP Proxies Configuring Proxies Displaying Proxies Deleting Proxies Displaying Multicast Routes IV C ABLE ODEM ONFIGURING ABLE CMTS Upstream Frequency Reuse Configuring the MAC Interface Displaying MAC Interface Parameters and Statistics Understanding MAC Interface Statistics Configuring MAC Interface Parameters...
  • Page 13 Configuring CMTS Privacy Parameters Configuring Flap Control ANAGING ABLE Viewing Cable Modems Displaying the Summary of Cable Modem Registration States Displaying a Detailed Listing for an Interface Displaying Specific Cable Modems Displaying Cable Modem Statistics Tracking Offline Cable Modems Setting the Duration for Tracking Offline Cable Modems Maintaining Statistics for Offline Cable Modems Clearing Offline Cable Modems Resetting Cable Modems...
  • Page 14 UBSCRIBER ANAGEMENT About Subscriber Management Filtering About CPE Control Configuring Filter Groups Viewing Filter Groups Deleting Filter Groups and Filters Modifying Existing Filter Groups Assigning Default Filter Groups Modifying Filter Groups Per Cable Modem Viewing Filter Group Assignments Configuring CPE Control Parameters Modifying CPE Control Parameters Per Cable Modem Viewing CPE Control Parameters and CPE Devices Viewing CPE Control Parameters...
  • Page 15 Packet Over SONET (POS) Commands Ethernet Commands ONFIGURING XTERNAL LOSSARY NDEX ROVISIONING ERVERS...
  • Page 17: Guide

    BOUT This chapter introduces you to the Cuda 12000 IP Access Switch CLI-based Administration Guide and contains the following sections: Document Objective (page 16) Audience (page 16) Document Organization (page 17) Notations (page 19) Command Syntax (page 20) Related Documentation (page 21) Contacting Customer Support (page 21) UIDE...
  • Page 18: Document Objective

    This guide targets the network administrator, responsible for configuring and managing the Cuda 12000 within a cable television headend site. It assumes a working knowledge of network operations, although it does not assume prior knowledge of ADC’s network equipment. ADC Telecommunications, Inc.
  • Page 19: Document Organization

    Document Organization The Cuda 12000 IP Access Switch CLI-based Administration Guide is organized as follows: Part I: Administration Overview Chapter 1: Cuda 12000 Overview — Provides an overview of product functionality and includes information on how the Cuda 12000 integrates into your network. Chapter 2: About the Command Line Interface —...
  • Page 20 Customer Premise Equipment (CPE) device management on the Cuda 12000. Chapter 21: MIB Browsing — Provides information on how to browse cable modem and MTA MIBs and the MIB objects that are returned. ADC Telecommunications, Inc.
  • Page 21: Notations

    Appendices Appendix A: Command Summary — Provides a complete listing of CLI commands and a brief description of each; organized by function. Appendix B: Configuring External Provisioning Servers — Provides information on configuring external FastFlow BPM and third-party provisioning servers. Appendix C: Glossary —...
  • Page 22: Command Syntax

    In this example, the user can specify either the line keyword or the internal keyword following the loop command. Expressed as three dots (...). For example: snmp-server host [<notification-type>...] In this example, the user can specify multiple notification types. ADC Telecommunications, Inc.
  • Page 23: Related Documentation

    , then select the Technical Assistance Center link. You can then report the problem online, search the ADC Customer Support database for known problems and solutions, and check Frequently Asked Questions. When contacting Customer Support for technical assistance, be sure to have...
  • Page 24 HAPTER BOUT UIDE ADC Telecommunications, Inc.
  • Page 25: I Administration Overview

    DMINISTRATION Chapter 1 Cuda 12000 Overview Chapter 2 About the Command Line Interface Chapter 3 Managing User Accounts VERVIEW...
  • Page 27: Cuda 12000 Overview

    This chapter explains the overall features of the Cuda 12000 IP Access Switch and describes how your Cuda 12000 IP Access Switch fits into your network. This chapter consists of the following sections: Introducing the Cuda 12000 IP Access Switch (page 26) Understanding the Cuda 12000 Within Your Network (page 32) 12000 O VERVIEW...
  • Page 28: Introducing The Cuda 12000 Ip Access Switch

    (CMTS) and IP router, and supports DOCSIS and EuroDOCSIS RFI Specification 1.0 and 1.1. To understand the Cuda 12000 IP Access Switch, you need to understand the following aspects of the switch: Hardware Software Minimum Chassis Configuration VERVIEW ADC Telecommunications, Inc.
  • Page 29: Hardware

    Hardware This section provides a brief overview of Cuda 12000 IP Access Switch hardware features and modules. For more information on Cuda 12000 IP Access Switch hardware, refer to the Cuda 12000 IP Access Switch Installation Guide. Features The Cuda 12000 provides the following hardware features: Table 1-1 Cuda 12000 Hardware Features Feature Total System...
  • Page 30 All system modules can be replaced while the system is running without interruption to other interconnected networks. Both application modules and Management modules are hot-swappable. ADC Telecommunications, Inc.
  • Page 31 Introducing the Cuda 12000 IP Access Switch DOCSIS (Data Over Cable Service Interface Specification) is a CableLabs ® standard for interoperability between a CMTS and cable modems. EuroDOCSIS (European Data Over Cable Service Interface Specification) is a CableLabs ® and tComLabs ®...
  • Page 32: Software

    CudaView offers topology views, fault views, performance graphs, and many other useful features. For more information on CudaView, refer to the Cuda 12000 IP Access Switch CudaView Administration Guide. ADC Telecommunications, Inc.
  • Page 33: Minimum Chassis Configuration

    Minimum Chassis Configuration The minimum configuration of a Cuda 12000 IP Access Switch comprises the following: A minimum of one management module, plus the base software package. The module and base software are required to configure the Cuda 12000 IP Access Switch. An Octal 10/100 Ethernet, Gigabit Ethernet, or POS module.
  • Page 34: Understanding The Cuda 12000 Within Your Network

    This example shows how the Cuda 12000 IP Access Switch can fit into your network. Figure 1-1 How the Cuda 12000 IP Access Switch Fits into Your Network VERVIEW Optional FastFlow BPM Prov. Server Cuda 12000 Cable Modem/MTA ADC Telecommunications, Inc.
  • Page 35: Cable Modem Termination System (Cmts)

    Cable Modem Termination System (CMTS) The Cuda 12000 implements DOCSIS and EuroDOCSIS CMTS functionality, providing connectivity and data forwarding for cable modems over the RF cable plant. The DOCSIS and EuroDOCSIS modules interface with your HFC network, using a 1-to-4 downstream-to-upstream port ratio (referred to as 1 x 4), or a 1-to-6 downstream-to-upstream port ratio (referred to as 1 x 6).
  • Page 36 1: C 12000 O HAPTER VERVIEW ADC Telecommunications, Inc.
  • Page 37: About The Command Line Interface

    BOUT THE NTERFACE This chapter introduces you to the command line interface (CLI) and covers the following topics: About the CLI (page 35) Accessing the CLI (page 37) Command Modes (page 40) About the CLI The Cuda 12000 management module runs the Linux operating system. The CLI operates within this environment.
  • Page 38 For most commands within the CLI, hyphens are placed between nouns, (such as cpe-control), while no hyphen is placed between verbs and nouns (such as no shutdown and show ip). Also note that commands and their associated arguments are case-sensitive. NTERFACE ADC Telecommunications, Inc.
  • Page 39: Accessing The Cli

    Accessing the CLI Your first form of access to the CLI (after installing the Cuda 12000) is through COM port 1 located on the front of the management module. Once you assign the Craft Ethernet port on the management module an IP address, you can access the CLI remotely through Telnet or SSH.
  • Page 40 3. When the cli:null:root prompt appears, enter your Cuda 12000 login name and password, as follows: enable <account name> <password> The system ships with the following system defaults: Account Name: root Password: bas NTERFACE ADC Telecommunications, Inc.
  • Page 41 Accessing the CLI For example: ADC Cuda 12000 cli:null:root> enable root password: *** Connecting to 192.168.208.3... Java Server version is compatible logon complete Sending message: User root just logged in from techpubs FROM:root@techpubs:: User root just logged in from techpubs Note that the default login name and password are case-sensitive —...
  • Page 42: Command Modes

    Help Command help NTERFACE Description Displays the commands and command descriptions. Displays all commands available within the current mode without descriptions; you can also display all commands by pressing the Tab key twice. ADC Telecommunications, Inc.
  • Page 43 The command modes that are available for system configuration depend on the product packages installed. Base package system management command modes include: If the FastFlow Broadband Provisioning Manager is installed on your Cuda 12000 IP Access Switch, additional command modes are available. Refer to the FastFlow Broadband Provisioning Manager CLI-based Administration Guide and the FastFlow Broadband Provisioning Manager CLI Reference Guide for more information on FastFlow Broadband Provisioning Manager...
  • Page 44: Global Commands

    FastFlow Broadband Provisioning Manager is installed on your Cuda 12000 IP Access Switch. Shortened form of quit. Enables you to exit from the CLI. Changes you to root mode. Changes you to router mode. ADC Telecommunications, Inc.
  • Page 45 Table 2-1 Global Commands Command server show sleep slot source talk traceroute Cuda 12000 IP Access Switch CLI-based Administration Guide Description Shortened form of prov-server. Sets several user session parameters. Specifies the show form of a command, which provides a read-only view of configuration parameters and other information.
  • Page 46: Root Mode

    Creates a cable modem filter. Validates provisioning database information. Configures access to the provisioning database. Configures event reporting, throttling, and syslog parameters. Empties the event log. Starts and stops the Web server. Controls the Jini lookup service on the chassis. ADC Telecommunications, Inc.
  • Page 47 Table 2-2 Root Mode Commands Command modulation-profile Configures modulation profiles, which contain burst privacy radius-server reset save snmp-server tacacs-server traffic-relay Cuda 12000 IP Access Switch CLI-based Administration Guide Description properties for upstream data channels. Configures X.509 certificate parameters for BPI plus. Configures a RADIUS authentication server.
  • Page 48: Physical Interface Mode

    Applies an access list to the current interface. Creates an access list, which consists of IP filtering rules. Enables and disables admission control. Enables the protocol analyzer. Sets the ARP timeout parameter. Defines BOOTP request policies. Optional prefix to commands in this mode. ADC Telecommunications, Inc.
  • Page 49 Table 2-3 DOCSIS Interface Mode Commands Command cm-filter cm-offline dhcp-authority dhcp-policy dhcp-relay downstream flap-list insertion-interval link-trap map-timer modulation-profile Configures modulation profiles, which contain burst periodic-ranging- interval plant-delay pll-state privacy proxy-arp ranging-attempts shared-secret shutdown Cuda 12000 IP Access Switch CLI-based Administration Guide Description First element in various cable modem and subscriber management commands, such as cm modify active,...
  • Page 50 Configures the duplex mode for the interface (full duplex, half duplex, or auto). Enables link traps for the interface. Configures an Ethernet port to automatically negotiate duplex and speed. Enables you to administratively shut down an interface. Configures the speed for an Ethernet port. ADC Telecommunications, Inc.
  • Page 51 Table 2-5 POS Interface Mode Commands Command access-class access-list bootp-policy clock-source dhcp-authority dhcp-policy dhcp-relay link-trap loop shutdown Cuda 12000 IP Access Switch CLI-based Administration Guide Description Applies an access list to the current interface. Creates an access list, which consists of IP filtering rules.
  • Page 52: Ip Interface Mode

    In IP address mode, the following commands are available: All commands that are available in the associated physical interface mode (DOCSIS, Ethernet, or POS). Commands for configuring RIP and OSPF on the interface (ip rip commands and ip ospf commands). NTERFACE ADC Telecommunications, Inc.
  • Page 53: Ospf Global Configuration Mode

    Command Modes OSPF Global Configuration Mode OSPF commands allow you to configure global OSPF (Open Shortest Path First) parameters. The system supports OSPF version 2 as defined in RFC 1583. OSPF global configuration mode allows you to enable the protocol on a system-wide basis, and set system-wide OSPF parameters —...
  • Page 54 Changes you to router export mode. Changes you to router import mode. Configures an OSPF area. Configures an OSPF virtual interface. Enables sending of OSPF neighbor state and OSPF virtual neighbor state events. Configures the OSPF router ID. ADC Telecommunications, Inc.
  • Page 55: Import And Export Ospf Route Filter Modes

    Import and Export OSPF Route Filter Modes Route filters control the flow of routes to and from the routing table. Import route filters control which routes are stored in the routing table. Export filters control which routes are advertised to other routers. You can define route filters to control the flow of both OSPF and RIP routes.
  • Page 56: Rip Configuration Mode

    RIP configuration mode allows you to enter RIP import and export route filter modes using the import and export commands. It does not allow you to set global parameters. RIP parameters are configured on a per-IP-interface basis within IP interface mode by means of the ip rip command. ADC Telecommunications, Inc.
  • Page 57: Import And Export Rip Route Filter Modes

    Import and Export RIP Route Filter Modes Route filters control the flow of routes to and from the routing table. Import route filters control which routes are stored in the routing table. Export filters control which routes are advertised to other routers. You can define route filters to control the flow of both OSPF and RIP routes.
  • Page 58: Slot Mode

    Downloads a file from a TFTP server to flash. Enables CPU utilization on the module. Configures IP packet filtering for all interfaces in the slot. Reboots a module. Saves the system configuration for all slots to persistent storage. Configures event logging for the slot. ADC Telecommunications, Inc.
  • Page 59: Managing

    This chapter provides information and procedures on how to manage user accounts and consists of the following tasks: Configuring Access Profiles (page 57) Managing User Accounts (page 58) Configuring User Authentication (page 63) Before you can effectively perform these tasks, you need to understand some concepts of user accounts.
  • Page 60: Configuring Access Profiles

    The user can type help or ? to determine the available commands. Functions associated with provisioning-related tasks, such as configuring DHCP servers and subnets. Functions associated with router-related tasks, such as configuring IP, RIP, and OSPF interfaces. ADC Telecommunications, Inc.
  • Page 61 The system ships with the following default access profiles. Note that these profiles are displayed in all capital letters when viewed to distinguish them from user-defined profiles. Also note that you cannot modify or remove these built-in profiles: AUDITORPROFILE. Provides read-only access to DOCSIS, routing, and provisioning functionality;...
  • Page 62: Creating And Modifying Access Profiles

    Readonly PrivilegeList: router: readonly 'routemonitor' was successfully created cli:172.16.19.10:root# CCOUNTS Command root access-profile <profile name> description <text string> {addprivilege | removeprivilege} {admin | hfc | observer | prov | router} {noaccess | read/write | readonly} ADC Telecommunications, Inc.
  • Page 63: Displaying Access Profiles

    Displaying Access Profiles You display access profile information by performing the following tasks: Task 1. Enter root mode. 2. Display all access profiles. 3. Display a specific access profile. Example The following example displays a profile named routemonitor: cli:172.16.19.10:root# show access-profile routemonitor Showing single profile: profileName: routemonitor profileDescription: Readonly...
  • Page 64: Deleting A Profile

    Task 1. Enter root mode. 2. Remove a specified access profile. Example The following example deletes an access profile named routemonitor: cli:172.16.19.10:root# no access-profile routemonitor 'routemonitor' was successfully removed cli:172.16.19.10:root# CCOUNTS Command root no access-profile <profile name> ADC Telecommunications, Inc.
  • Page 65: Managing User Accounts

    Managing User Accounts You create and modify local user accounts on the Cuda 12000 using the account command. You must have root profile privileges to manage user accounts which the following: Creating and Modifying User Accounts Displaying User Accounts Deleting User Accounts For each user account, you define the following parameters: Table 3-2 User Account Parameters Parameter...
  • Page 66: Creating And Modifying User Accounts

    Readonly PrivilegeList: 'Route_1' was successfully created cli:172.16.19.10:root# User account names and passwords are case-sensitive. CCOUNTS Command root account <account name> {add-profile <profile name> | remove-profile <profile name> | password <password> | description <string>} router: readonly ADC Telecommunications, Inc.
  • Page 67: Displaying User Accounts

    Displaying User Accounts You view user accounts configured on the system by performing the following tasks: Task 1. Enter root mode. 2. Show all user accounts. 3. Show a specified user account. Example The following example shows the user account named Route_1: cli:172.16.19.10:root# show account Route_1 Showing single account: UserName: Route_1...
  • Page 68: Deleting User Accounts

    To remove a user account from the system, perform the following task: Task Delete account. Example The following example removes the user account Route_1 from the system: cli:172.16.19.10:root# no account Route_1 'Route_1' was successfully removed cli:172.16.19.10:root# CCOUNTS Command no account <account name> ADC Telecommunications, Inc.
  • Page 69: Configuring User Authentication

    Configuring User Authentication The Cuda 12000 IP Access Switch supports three types of user authentication: Local authentication – Users are authenticated locally by the Cuda 12000. This is the default authentication type. TACACS+ authentication – Users are authenticated by a TACACS+ server. When the user attempts to login to the Cuda 12000, the Cuda 12000 encrypts the username and pasword, and forwards them to the TACACS+ server for authentication.
  • Page 70: Configuring Local Authentication

    1. Enter root mode. 2. Enable local authentication. 3. Verify that local authentication is enabled. Example cli:192.168.208.3:root# aaa authentication login default local cli:192.168.208.3:root# show aaa aaa authentication login default local CCOUNTS Command root aaa authentication login default local show aaa ADC Telecommunications, Inc.
  • Page 71: Configuring Tacacs+ Authentication

    Configuring TACACS+ Authentication Before you configure TACACS+ authentication on the Cuda 12000, make sure that: At least one account for Cuda 12000 users has been created on the TACACS+ server. Users must login to the Cuda 12000 an account created on the TACACS+ server.
  • Page 72 Example cli:192.168.208.3:root# tacacs-server host 192.168.220.200 cli:192.168.208.3:root# tacacs-server key one4me cli:192.168.208.3:root# show tacacs-server tacacs-server host 192.168.220.200 tacacs-server key one4me cli:192.168.208.3:root# aaa authentication login default tacacs+ cli:192.168.208.3:root# show aaa aaa authentication login default tacacs+ cli:192.168.208.3:root# CCOUNTS Command show aaa ADC Telecommunications, Inc.
  • Page 73: Configuring Radius Authentication

    Configuring RADIUS Authentication Before you configure RADIUS authentication on the Cuda 12000, make sure that: At least one account for Cuda 12000 users has been created on the RADIUS server. Users must login to the Cuda 12000 an account created on the RADIUS server.
  • Page 74 Example cli:192.168.208.3:root# radius-server host 192.168.220.202 cli:192.168.208.3:root# radius-server key one4me cli:192.168.208.3:root# show radius-server radius-server host 192.168.220.202 radius-server key one4me cli:192.168.208.3:root# aaa authentication login default radius cli:192.168.208.3:root# show aaa aaa authentication login default radius cli:192.168.208.3:root# CCOUNTS Command show aaa ADC Telecommunications, Inc.
  • Page 75: Hassis

    HASSIS Chapter 4 Chassis Configuration Chapter 5 Multi-Chassis Support Chapter 6 Module Administration Chapter 7 Packet Over SONET Administration Chapter 8 Timing and Alarm Controller Management Chapter 9 Simple Network Management Protocol (SNMP) Chapter 10 Managing System Events DMINISTRATION...
  • Page 77: Chassis Configuration

    HASSIS This chapter explains the configuration features of the Cuda 12000 chassis and includes the following sections: Understanding Chassis Identification (page 76) Understanding Management Module Redundancy (page 76) Configuring Chassis Parameters (page 78) Displaying Current Chassis Configuration (page 81) Configuring Clock Sources (page 86) Starting and Stopping the HTTP Server (page 88) Enabling and Disabling Traffic Relay (page 89) Broadcasting Messages to Users (page 91)
  • Page 78: Understanding Chassis Identification

    Chassis Number — The Cuda 12000 chassis is shipped with a unique chassis-number, which is a fixed value assigned to each chassis during manufacturing at the ADC plant. Chassis ID — Each Cuda 12000 switch should be configured with a unique chassis identification (ID) number.
  • Page 79 A secondary management module can take over the primary role in two ways: Automatically, when the secondary management module detects that the primary management module is not functioning properly. Manually, through the chassis-config CLI command. In this case, you use the command to force the current primary management module into the secondary role, which in turn forces the current secondary management module into the primary role.
  • Page 80: Configuring Chassis Parameters

    Chassis configuration includes the following parameters: Chassis Number — A fixed number assigned to the Cuda 12000 chassis during manufacturing at the ADC plant. Chassis ID — User-defined. A unique identification number that you assign to the Cuda 12000 chassis in the network. The Cuda uses a multi-range numbering system.
  • Page 81 Configuration of chassis parameters is achieved using the chassis-config command within root mode. Perform the following tasks within root mode to configure chassis parameters: Task 1. Identify the chassis number. 2. Configure the chassis ID. 3. Configure the Cluster ID 4.
  • Page 82 Primary Manager Slot: Secondary Manager Slot: 14 Scope: cli:192.168.222.200:root# chassis-config 101 manager secondary Connection to 192.168.222.200 refused or closed! Note that you must reconnect to the Cuda 12000 after you force the management modules to change roles. Cluster ADC Telecommunications, Inc.
  • Page 83: Displaying Current Chassis Configuration

    The xml argument displays the output in XML format. The server-name argument is reserved for ADC internal use only. In addition to displaying the running configuration, you have the ability to generate a script to a file. This script may be used to configure other chassis to use the same configuration.
  • Page 84 IP Protocol Bridge Group Holder Bas SNMP Manager snmp-server group adc v1 read public write private notify public context adc s torage nonvolatile snmp-server group adc v2c read public write private notify public context adc storage nonvolatile...
  • Page 85 storage...
  • Page 86 Interface 1/3/1 Gigabit Ethernet Mac Interface 1/11/1 10/100 Ethernet MAC IP Address Interface 1/11/2 10/100 Ethernet MAC Interface 1/11/3 10/100 Ethernet MAC Interface 1/11/4 10/100 Ethernet MAC Interface 1/11/5 10/100 Ethernet MAC Interface 1/11/6 10/100 Ethernet MAC ADC Telecommunications, Inc.
  • Page 87 interface ethernet 1/11/6 root interface ethernet 1/11/7 root interface ethernet 1/11/8 root slot 1/1 interface cable 1/1/1 dhcp-policy default permit forward-internal dhcp-relay add-agent-options enable ip source-route 201.1.2.0 255.255.255.0 201.1.3.1 ip source-route 201.1.4.0 255.255.255.0 201.1.5.0 ip source-route 201.4.6.0 255.255.255.0 201.2.7.0 admission-control disable privacy base auth-lifetime 604800 tek-lifetime 43200 cert-trust trusted enab le-cert-validity-periods true...
  • Page 88: Configuring Clock Sources

    (remote) side of the POS link. To do this, issue the following command from within POS interface mode: clock-source line Refer to Chapter 7 “Packet Over SONET Administration” for more information on configuring POS interfaces. POS Module Interface 1/8/1 POS MAC BasPppProtocol ADC Telecommunications, Inc.
  • Page 89 A typical configuration would be as follows: Primary clock configured to use a BITS-A or BITS-B external clock source Secondary clock configured to use the internal Stratum-3 oscillator clock source. The example at the end of this section illustrates the commands you would issue to create this typical configuration.
  • Page 90: Starting And Stopping The Http Server

    CudaView. By default, the HTTP server is enabled and running. To start and stop the HTTP server, perform these tasks: Task 1. Enter root mode. 2. Start the HTTP server. 3. Stop the HTTP server. Command root http-server enable http-server disable ADC Telecommunications, Inc.
  • Page 91: Enabling And Disabling Traffic Relay

    Enabling and Disabling Traffic Relay You can configure processes, such as the HTTP server, to send and receive TCP or UDP packets using an internal address on the Cuda 12000. This method of sending and receiving packets is called traffic relay. If you are running a TFTP server on the Cuda 12000 as part of FastFlow BPM provisioning, you must enable traffic relay for the TFTP server in order to download configuration files to cable modems.
  • Page 92 In this example, traffic relay is enabled for Telnet. cli:192.168.208.3:root# traffic-relay telnet cli:192.168.208.3:root# show traffic-relay row count: 10 Protocol ------------ -------- ----------- tftp time_of_day syslog snmp telnet http snmp-trap cli:192.168.208.3:root# State Port Number enable enable disable disable disable enable disable disable disable disable ADC Telecommunications, Inc.
  • Page 93: Broadcasting Messages To Users

    Broadcasting Messages to Users The talk command enables you to broadcast messages to all chassis users and to enable and disable the ability to broadcast messages. To broadcast messages to users, perform the following task: Task From any mode, send a broadcast message.
  • Page 94 4: C HAPTER HASSIS ONFIGURATION ADC Telecommunications, Inc.
  • Page 95: Multi -Chassis Support

    ULTI This chapter describes multi-chassis support, and includes the following sections: About Multi-Chassis Support (page 94) Planning Multi-Chassis Support (page 96) Enabling the Jini Lookup Service (page 97) Configuring Multi-Chassis Support (page 98) Creating a Common User Account for the Group (page 100) Viewing Chassis Details (page 101) HASSIS UPPORT...
  • Page 96: About Multi-Chassis Support

    You can manage SNMPv3 resources (contexts and users) on the host chassis only. In addition, you can manage hardware alarms/faults and user accounts on the host chassis only. You cannot manage SNMPv3, hardware alarms/faults, and user accounts by proxy. ADC Telecommunications, Inc.
  • Page 97 The multi-chassis group, MCS-Group1, in the example below consists of three chassis: A, B, and C. The group name “MCS-Group1” is configured on each chassis, and each chassis registers this name with the Jini lookup service running on Chassis C. In this example, the network administrator logs in to Chassis B (the host chassis), but keep in mind that the network administrator can also log in to Chassis A and Chassis C to access the group.
  • Page 98: Planning Multi-Chassis Support

    3. Create a common user account on each chassis in the group. Refer to “Creating a Common User Account for the Group” on page 100. 4. Monitor the group as needed. Refer to “Viewing Chassis Details” on page 101. UPPORT ADC Telecommunications, Inc.
  • Page 99: Enabling The Jini Lookup Service

    Enabling the Jini Lookup Service Enable the Jini lookup service on at least two Cuda 12000 chassis. Each chassis that runs the Jini lookup service must be on the same physical network as the multi-chassis group that it serves. To enable the Jini lookup service on a chassis, perform the following tasks: Tasks 1.
  • Page 100: Configuring Multi-Chassis Support

    3. Display multi-chassis group status. 4. Access another chassis while in the current log-in session. UPPORT Commands root chassis {mcs {enable | disable} | group <group name> | description <string>} show chassis {local | <ip-address>} connect <ip address> ADC Telecommunications, Inc.
  • Page 101 Example In this example, the administrator enables multi-chassis support, specifies a group name, and displays multi-chassis status on the chassis (local chassis) that the administrator is currently configuring. cli:192.168.208.3:root# chassis mcs enable cli:192.168.208.3:root# chassis group Cuda-Group1 cli:192.168.208.3:root# chassis description "Cuda Group 1" cli:192.168.208.3:root# show chassis local Multi Chassis Service : enable Host Name...
  • Page 102: Creating A Common User Account For The Group

    You can manage user accounts on a chassis to which you are directly connected and logged into only (on the host chassis). You cannot manage user accounts by proxy. Refer to Chapter 3 “Managing User Accounts” for more information on creating user accounts. ADC Telecommunications, Inc.
  • Page 103: Viewing Chassis Details

    Viewing Chassis Details You can view chassis details for a local chassis, a particular chassis within a group, or all the chassis in a group. Chassis details include the following information: Table 5-1 Chassis Details Parameter Multi Chassis Service Host Name IP Address Group Name Version...
  • Page 104 : 3.0.6 release3.1_bgp 10 2001_08_10_0647 : sw19_cuda : xxx.xxx.xxx.xxx : cuda : 3.0.9 R3dev_cmts 10 2001_07_25_1610 : adc_cuda : xxx.xxx.xxx.xxx : cuda : 3.0.9 Release3.1 29 2001_07_24_1130 : c0222 : xxx.xxx.xxx.xxx : cuda : 3.0.13 Release3.0_Beta 140 2001_08_08_1331 ADC Telecommunications, Inc.
  • Page 105: Module Administration

    ODULE This chapter provides general information on how to view and manage Cuda application modules through the CLI and provides specific information on managing Ethernet modules. The chapter includes the following sections: Cuda Application Modules (page 104) Configuring the 10/100 Ethernet and GigE Modules (page 105) Viewing Module Information (page 106) Viewing Ethernet Interface Packet Statistics (page 110) Refer to Chapter 7 “Packet Over SONET Administration”...
  • Page 106: Cuda Application Modules

    Ethernet network. Gigabit Ethernet — Provides 1000 Mbps connection to your Gigabit Ethernet network. Packet-Over-SONET (POS) — Available in both OC-3 and OC-12 configurations, provides high-speed transmission of IP packets directly over SONET links. ADC Telecommunications, Inc.
  • Page 107: Configuring The 10/100 Ethernet And Gige Modules

    Configuring the 10/100 Ethernet and GigE Modules The Cuda 12000 allows you to configure duplex mode for interfaces on the 10/100 module and the interface on the GigE modules. The Cuda 12000 also allows you to configure speed for interfaces on the 10/100 module. You may set duplex mode to full duplex, half duplex, or auto negotiation.
  • Page 108: Viewing Module Information

    You can pipe the output to an include utility to scope the display down to content of interest. For example, the command show topology | include Ethernet will scope the output to only Ethernet interfaces. Note that the string you specify is case-sensitive. Command show topology ADC Telecommunications, Inc.
  • Page 109 Viewing Module Information The following example shows the modules currently installed in the Cuda chassis: Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 110: Viewing Module Versions

    Viewing Module Versions You can view the software version currently installed on each module. To do so, perform the following task within any mode. Task Show the firmware version installed on each module. For example: Command show version ADC Telecommunications, Inc.
  • Page 111 For information on how slots are numbered, see the Cuda 12000 IP Access Switch Installation Guide. Logical port utilized by the module. For ADC use only. Indicates date and time of last module bootup. Specifies the following: Hardware and software version of the module.
  • Page 112: Viewing Ethernet Interface Packet Statistics

    The following example uses the show topology command piped to include to grep for all Ethernet interfaces. It then displays incoming packet statistics for Ethernet interface 8: Command show interface ethernet <c/s/i> in-counters show interface ethernet <c/s/i> out-counters ADC Telecommunications, Inc.
  • Page 113 The following incoming statistics are displayed for each interface: In Octets — Total number of Octets that have been received on this interface, including framing characters. In Unicast Packets — Number of Unicast packets that have been received on this interface. In Multicast Packets —...
  • Page 114: Displaying Statistics For All System Interfaces

    2. Show outgoing packet statistics for a selected Ethernet interface. The following example displays incoming statistics for all system interfaces, then pipes the output to include outgoing statistics for only cable (DOCSIS) interfaces: Command show in-counters show out-counters ADC Telecommunications, Inc.
  • Page 115 Viewing Ethernet Interface Packet Statistics Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 116 6: M HAPTER ODULE DMINISTRATION ADC Telecommunications, Inc.
  • Page 117: Packet Over Sonet Administration

    ACKET DMINISTRATION This chapter provides information on how to configure Packet over SONET (POS) on the Cuda 12000 using the CLI and includes the following sections: About Packet Over SONET (page 116) Packet Over SONET (POS) Interface Administration (page 117) Configuring and Viewing SONET Alarms (page 132) Configuring Point-to-Point Protocol (PPP) (page 137) The section covers functionality available in the Cuda 12000 Base System...
  • Page 118: About Packet Over Sonet

    IP data at layer 2, as described in “Configuring Point-to-Point Protocol (PPP)” on page 137. DMINISTRATION IP Datagram Layer 3 — Network Layer PPP Encapsulation Layer 2 — Data Link Layer SONET Layer 1 — Physical Transport Layer ADC Telecommunications, Inc.
  • Page 119: Packet Over Sonet (Pos) Interface Administration

    Packet Over SONET (POS) Interface Administration Packet over Synchronous Optical Network (SONET) allows for high-speed transport of IP data packets over a SONET network. The OC-3 and OC-12 POS modules contain a single physical interface that supports connection to STS networks and supports transmission speeds of up to 155 Mbps. A SONET frame is 810 bytes represented as a grid of 9 rows by 90 columns.
  • Page 120 SONET interface administration on the Cuda 12000 includes: Displaying POS Interface Information Disabling and Enabling Interfaces Viewing POS Interface Packet Statistics Viewing SONET Line-Layer Information Viewing SONET Path Layer Information Viewing and Configuration Section Layer Administration Configuring and Viewing SONET Alarms DMINISTRATION ADC Telecommunications, Inc.
  • Page 121: Displaying Pos Interface Information

    Displaying POS Interface Information You can display information for each POS interface. To do so, perform the following task within root mode: Task Display POS interface statistics and settings. The following example uses the show topology command to obtain a list of modules installed on the system, then uses the show interface command to display information for the select POS interface.
  • Page 122 Path Signal Id - C2 Section Trace Byte - J0 Packet Scrambling Loopback Last clearing of counters PPP Authentication Security Mode: NONE DMINISTRATION Single Mode (15km) None closed None Enabled Sonet Line 0xCF 0xCC Disabled 431:47:9 (HH:MM:SS) ADC Telecommunications, Inc.
  • Page 123: Hardware Is Packet Over Sonet

    The display includes a number of statistics, as described in the following table. Table 7-1 POS Interface Statistics Display Element Interface Type POS 1/3/1 (line protocol) Hardware is Packet over SONET Internet Address Rx Giants Bad FCS’s Bad Addresses Bad Controls Local MRU FCS Size Transmission Errors (Tx)
  • Page 124: Rx Abort

    IP datagrams. IP Control Protocol (IPCP) is the network control protocol used. Indicates SONET line type. Indicates the clock source configured for this interface. C2 byte received in last packet. Indicates whether packet scrambling in enabled or disabled. ADC Telecommunications, Inc.
  • Page 125: Disabling And Enabling Interfaces

    Display Element Loopback Last clearing of counters PPP Authentication Security Mode Clearing Interface Counters You can clear interface counters for a selected POS interface. To do so, perform the following task within interface pos <c/s/i> mode: Task Clear all counters for the current POS interface.
  • Page 126: Viewing Pos Interface Packet Statistics

    In Multicast Packets — Number of Multicast packets that have been received on this interface. In Broadcast Packets — Number of Broadcast packets that have been received on this interface. DMINISTRATION Command show interface pos <c/s/i> in-counters show in-counters show interface pos <c/s/i> out-counters show out-counters ADC Telecommunications, Inc.
  • Page 127 Packet Over SONET (POS) Interface Administration The following outgoing statistics are displayed for each interface: Out Octets — Total number of PPP negotiations octets that have been transmitted from this interface. This does not include octets for data packets. Out Unicast Packets — Total number of Unicast packets that have been transmitted from this interface.
  • Page 128: Viewing Sonet Line-Layer Information

    PRDI occurs if bits 5,6 and 7 of the G1 byte received with the same value for 5 consecutive frames. Far end block errors - Indicates the number of B2 errors that were detected by the remote side in its receive signal. ADC Telecommunications, Inc.
  • Page 129: Viewing Sonet Path Layer Information

    Display Element BIP (B2) Viewing SONET Path Layer Information The Path layer is responsible for mapping the data to be transported into the synchronous payload envelope (SPE) of the SONET frame. It creates the STS-1 SPE and passes it to the line layer. You can view Path-layer performance information for a selected POS interface.
  • Page 130 Even Parity is calculated over all bits in the SPE, including POH of each frame. These values are then compared to the B3 values received in the packet. Mismatches are reported. ADC Telecommunications, Inc.
  • Page 131: Section Layer Administration

    Section Layer Administration The primary roles of the section layer include synchronization and timing of the SONET transmission, and passing the electrical STS-n frame format to the photonic layer where it is then converted to an optical signal and transported to the adjacent device.
  • Page 132 Currently, the system supports only SONET STS-n framing. To configure the framing type used on a POS interface, perform the following task in interface pos <c/s/i> mode: Task Configure POS framing. DMINISTRATION Command clock-source {line | internal} Command pos framing {sonet | sdh} ADC Telecommunications, Inc.
  • Page 133 Packet Scrambling Enables scrambling of SONET Synchronous Payload Envelopes (SPEs) on this interface. Note that both end-points of the transmission must use the same scrambling. Scrambling is disabled by default. To configure scrambling on a POS interface, perform the following task in interface pos <c/s/i>...
  • Page 134: Configuring And Viewing Sonet Alarms

    Viewing Alarm Information — You can verify the alarms that are enabled and disabled on a selected POS interface, as well as the alarms that have been reported, using the show controller pos <c/s/i> command within root mode. DMINISTRATION ADC Telecommunications, Inc.
  • Page 135: Configuring Pos Alarm Reporting

    Configuring POS Alarm Reporting You can configure reporting of 12 different POS alarms. To do so, perform the following tasks within interface pos <c/s/i> mode: Alarm Report Description Line Alarm Indication Disabled by default, configures the Signal (LAIS) interface to report line alarm indication signal errors.
  • Page 136 To set the B2 Signal Fail threshold: pos threshold sf-ber <number> To enable reporting: pos report slof To disable reporting: no pos report slof To enable reporting: pos report slos To disable reporting: no pos report slos ADC Telecommunications, Inc.
  • Page 137: Viewing Alarm Information

    Viewing Alarm Information Using the show controllers pos <c/s/i> command within root mode, you can display both the alarms that you have enabled on the POS interface, and whether or not specific alarms have been reported. To view the alarm reporting configuration on a POS interface, perform the following task in root mode: Task View whether the reporting of...
  • Page 138 7: P SONET A HAPTER ACKET DMINISTRATION The following example indicates whether or not a specific alarm has been reported: ADC Telecommunications, Inc.
  • Page 139: Configuring Point-To-Point Protocol (Ppp)

    Configuring Point-to-Point Protocol (PPP) PPP is well-suited for delivery of data over SONET networks, as SONET links are provisioned as point-to-point circuits. The system encapsulates IP datagrams using PPP, then places the PPP frames into the SONET payload before transmission over the SONET circuit. PPP also provides security protocols that support the authentication of peers.
  • Page 140: Configuring Ppp Security

    You can enable CHAP and PAP client-side authentication and configure the security information — username and password — that the POS interface sends to a PPP server when initiating a point-to-point connection. ADC Telecommunications, Inc.
  • Page 141 To configure CHAP authentication, perform the following tasks within interface pos <c/s/i> mode: Task 1. Enable CHAP authentication. 2. Configure the hostname the POS interface will use to respond to CHAP Challenges. 3. Configure the password the POS interface will use to respond to CHAP Challenges.
  • Page 142 CHAP second. To enable CHAP then PAP: ppp authentication chap pap The interface will negotiate the authentication protocol to use. It will try to agree on CHAP authentication first, then PAP second. ppp pap-sent-username <name> password <password> ADC Telecommunications, Inc.
  • Page 143 Configuring Server-Side Security Parameters When a remote peer (client) calls into the POS interface and attempts to establish a point-to-point connection, the interface functions as a PPP access server. Enabling server-side authentication configures the POS interface to authenticate all peers that call into it. Configuring server-side authentication involves the following: Specifying which protocol you want the interface to use to authenticate clients.
  • Page 144 To enable PAP then CHAP: ppp authentication pap chap The interface will negotiate the authentication protocol to use. It will try to agree on PAP authentication first, then CHAP second. ppp chap-hostname <name> ppp username <name> password <password> ADC Telecommunications, Inc.
  • Page 145 Perform the following tasks within interface pos <c/s/i> mode to configure PPP PAP server-side security parameters: Task 1. Enable PAP authentication 2. Configure the username and password that a requesting client must provide for authentication to allow the connection. Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring Point-to-Point Protocol (PPP) Command To enable the use of PAP only:...
  • Page 146: Configuring Lcp

    Frame Check Sequence (FCS) Size Perform the following task within interface pos <c/s/i> to enter the frame check sequence size: Task Configure frame check sequence size. DMINISTRATION Command mtu 1500 Command crc {16 | 32} ADC Telecommunications, Inc.
  • Page 147 Max Negotiation Attempts Perform the following task within interface pos <c/s/i> mode to configure the maximum number of link negotiation attempts allowed by the current interface: Task Configure maximum negotiation attempts. Time Between Negotiation Attempts Perform the following task within interface pos <c/s/i> mode to configure the number of seconds that the interface waits between LCP negotiations.
  • Page 148: Enabling Ncp

    <c/s/i> mode: Task 1. Enable the reporting of the IP address during IPCP negotiation. 2. Disable the reporting of the IP address during IPCP negotiation. DMINISTRATION Command ppp ipcp-report-address no ppp ipcp-report-address ADC Telecommunications, Inc.
  • Page 149: Timing And Alarm Controller Management

    IMING AND ANAGEMENT The Cuda 12000 utilizes an external fan tray for cooling and obtains power from an external power source. Fault management features on the Cuda 12000 for the fan tray and power source are: The Timing and Alarms Controller (TAC) that resides on the Management module.
  • Page 150: About Timing And Alarm Controller Fault Reporting

    (Refer to the next chapter, “Simple Network Management Protocol (SNMP)” on page 161 for information about configuring destinations for fault events.) ONTROLLER ANAGEMENT Description Receives fault signals from the connected units. Transmits fault signals to an external device. ADC Telecommunications, Inc.
  • Page 151 Configuring power and fan tray fault reporting involves performing the following tasks: You must specify whether the auxiliary device utilizes an active-high or active-low assertion level to report fault conditions, as described in “Assertion Levels” on page 150. Configure the faults that you want the system to report, as described in “Configuring Fault Reporting”...
  • Page 152: Assertion Levels

    Set to report DC current faults of the power supply. Set to report AC current faults of the power supply. Set to report temperature faults of the fan unit. Set to report rotation faults of the fan unit. ADC Telecommunications, Inc.
  • Page 153: Configuring The Power Assertion Level

    Configuring the Power Assertion Level You must verify the assertion level specified by the power supply vendor to indicate fault conditions, and set the assertion levels as specified by the vendor. To configure the assertion level that the power supply utilizes when indicating a fault condition, perform the following tasks: Task 1.
  • Page 154: Configuring Fan Unit Assertion Levels

    The following example displays the assertion level currently configured for the fan temperature: cli:192.168.208.3:root# show aux-device fan-temp Assert Fan Temp Fault ONTROLLER ANAGEMENT Command root aux-device fan-temp fault-level {active-high | active-low} aux-device fan-rotation fault-level {active-high | active-low} Command root show aux-device fan-temp show aux-device fan-rotation active-high ADC Telecommunications, Inc.
  • Page 155: Configuring Fault Reporting

    Configuring Fault Reporting The system reports faults in the form of SNMP traps and syslog messages. You must configure the faults for which you want to be notified. For each fault that you choose to report, the system sends an SNMP trap or syslog message to all specified destinations if a fault is detected.
  • Page 156 {backplane | backplane-power | backplane-power-a | backplane-power-b | backplane-temp | bits-a | bits-b | blue | fan-rotation | fan-temp | local-pwr-a | local-pwr-b | processor-temp | ps-ac | ps-dc | ps-temp | red-alarm | yellow} ADC Telecommunications, Inc.
  • Page 157: Removing A Fault Notification

    Removing a Fault Notification In the event that you no longer wish to be notified of a fault condition, you may remove a specified fault notification by performing the following tasks: Task 1. Enter root mode. 2. Remove the fault condition from the notification report.
  • Page 158: Viewing Fault Reporting Status

    Ps AC Fault Ps DC Fault Fan Temp Fault Fan Rotation Fault Local Pwr A Fault Local Pwr B Fault disabled disabled disabled disabled okay disabled disabled disabled disabled disabled disabled disabled disabled disabled disabled disabled okay disabled ADC Telecommunications, Inc.
  • Page 159: Configuring Alarms Out

    Configuring Alarms Out A DB-15 connector on the Cuda 12000 chassis rear panel serves as the alarms out port. You can configure the Cuda 12000 to send specific types of alarm signals out this DB-15 connector to an external indication device to notify the external device that a particular type of fault has occurred.
  • Page 160 DB-15 connector: ONTROLLER ANAGEMENT To Provide Notification of These Faults: local-pwr-a-fault local-pwr-b-fault backplane-pwr-fault backplane-pwr-a-fault backplane-pwr-b-fault ps-ac-fault ps-dc-fault processor-temp-fault ps-temp-fault fan-temp-fault local-pwr-a-fault local-pwr-b-fault backplane-pwr-a-fault backplane-pwr-b-fault ps-ac-fault ps-dc-fault local-pwr-a-fault local-pwr-b-fault bits-a-fault bits-b-fault red-alarm-fault ADC Telecommunications, Inc.
  • Page 161 Task 1. Enter root mode. 2. Specify the types of alarm signals that you want to enable, to set the fault to send alarm signals out the DB-15 connector. 3. Specify the types of alarm signals that you want to disable, to prohibit the faults from being sent out the DB-15 connector.
  • Page 162: Viewing Alarm Signals Out The Db-15 Connector

    Command root show aux-device db15 enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled enabled disabled enabled enabled ADC Telecommunications, Inc.
  • Page 163: Simple Network Management Protocol (Snmp)

    IMPLE ROTOCOL Simple Network Management Protocol (SNMP) is a standard for managing networks. This chapter provides an overview of SNMP (refer to “About SNMP” on page 162). This chapter also provides information on performing the following tasks to configure SNMP on the Cuda 12000: Configuring SNMP Access Control (page 164) Configuring System Name, Contact, and Location (page 180) Configuring SNMP Event Notification Types (page 182)
  • Page 164: About Snmp

    The level of security is determined primarily by the specific SNMP application implementation and by the specific security model implementation. The Cuda 12000 supports DOCSIS 1.1 OSS Interface Specification (SP-OSSIv1.1-I02-000714) and SNMP configuration, as defined by RFCs 1157, 2571, 2572, 2573, 2574, 2575 and 2576. ADC Telecommunications, Inc.
  • Page 165 Configuring and monitoring SNMP on the Cuda 12000 involves the following processes. These processes are explained in the sections that follow: 1. Configuring SNMP access control. 2. Configuring system name, contact, and location information. Refer to “Configuring System Name, Contact, and Location” on page 180. 3.
  • Page 166: Configuring Snmp Access Control

    SNMP access control follows a hierarchy and it is recommended that you perform configuration functions in the following order: 1. Configure SNMP Access Views. 2. Configure SNMP Groups. 3. Configure Models, as follows: a Configure SNMPv1, v2c Communities, and/or b Configure SNMPv3 Users and Contexts (SNMP) ANAGEMENT ROTOCOL ADC Telecommunications, Inc.
  • Page 167: Configuring Snmp Access Views

    Configuring SNMP Access Views SNMP Access Views control access to a MIB subtree. Configuring SNMP Access Views involves the following: 1. Creating a MIB view. You create a MIB view by specifying a name for the view, by defining the MIB subtree to be viewed, and by specifying whether instances of the MIB subtree are included in the MIB view or excluded from the MIB view.
  • Page 168 <view name> <oid-tree> {included | excluded} [storage {volatile | nonvolatile | permanent | readonly}] snmp-server view <view name> <oid-tree> {included | excluded} [status {enable | disable}] show snmp view [<view name>] no snmp-server view <view name> ADC Telecommunications, Inc.
  • Page 169 Example The following example configures and displays an SNMP MIB view using the default storage type and status. cli:192.168.208.3:root# snmp-server view auditorview1 1.3.6.1 included cli:192.168.208.3:root# show snmp view row count: 5 View Name Subtree ---------------- --------------------------- -------- ----------- ----------- public 1.3.6.1 private 1.3.6.1...
  • Page 170: Configuring Snmp Groups

    V3 security model provides this level of security. Authorizes the group to have read access to the specific MIB view. Authorizes the group to have write access to the specific MIB view. Authorizes the group to have notify access to the specific MIB view. ADC Telecommunications, Inc.
  • Page 171 Parameter Storage Perform the following tasks to configure an SNMP group. Refer to the configuration examples below: Read, write or notify privileges are associated to an SNMP MIB view. If an SNMP view already exists, you assign the privileges to that existing view name.
  • Page 172 ---------- ------- ----- ------ ----------- ----------- ----------- ----------- alemap The following example assigns the group read privileges to an SNMP MIB view: root# snmp-server group alemaps v1 read adc root# show snmp group Group Context Model Level ---------- ------- ----- ------ ----------- ----------- ----------- ----------- alemaps cli:192.168.208.3:root#...
  • Page 173 The following example associates an existing context to the group: root# snmp-server group alemaps v1 read public context adc root# show snmp group Group Context Model Level ---------- ------- ----- ------ ----------- ----------- ----------- ----------- alemaps Example 2 The following example specifies the storage type for a group:...
  • Page 174: Configuring Snmp Communities

    The context is one of the parameters that allows access to a group entry, along with group name, security model and security level. NOTE: Refer to the section “Configuring SNMPv3 Contexts” on page 178, for detailed information about SNMP contexts. ADC Telecommunications, Inc.
  • Page 175 Parameter Storage Perform the following tasks to configure an SNMPv1 or v2c community. Refer to the configuration example below: Task 1. Enter configuration mode. 2. Create an SNMP community and a corresponding security group. 3. Specify the host that has access to the SNMP community.
  • Page 176 192.168.20.12 mask 255.255.255.0 context cuda cli:192.168.208.3:root# show snmp community row count: 5 Name Security Name --------------------------------------------------------------- beta build guitraps guitraps private public (SNMP) ANAGEMENT ROTOCOL Context cuda Storage NonVolatile NonVolatile NonVolatile NonVolatile NonVolatile ADC Telecommunications, Inc.
  • Page 177: Configuring Snmpv3 Users

    Configuring SNMPv3 Users The SNMPv3 user is anyone who requires management operations to be authorized by a particular SNMP entity. SNMP entities must have knowledge of a user and the user’s attributes. Configuring an SNMPv3 user involves the following: 1. Specifying a user’s name. 2.
  • Page 178 Set to Enable to indicate Active, or set to Disable to indicate Not in Service. Commands root snmp-server user <user> snmp-server user <user> [auth {md5 | sha} <auth-password>] snmp-server user <user> [auth {md5 | sha} <auth-password>] [priv des56 <priv-password>]] ADC Telecommunications, Inc.
  • Page 179 Tasks 4. Specify how user attributes are stored. By default, storage type is set to NonVolatile. 5. Specify the user’s status. By default, the Cuda sets status type to Active. 6. Display SNMP user attributes. 7. Remove an SNMP user. Example The following example configures an SNMP user with authentication type and privacy attributes:...
  • Page 180: Configuring Snmpv3 Contexts

    The entry is stored in volatile memory. The information is lost during a system reboot. Sets the state of the context, as follows: Activates a context. Temporarily sets the context to “Not In Service.” By default, the context is enabled. ADC Telecommunications, Inc.
  • Page 181 Perform the following tasks to configure SNMPv3 contexts. Refer to the configuration example below: Task 1. Enter configuration mode. 2. Provide the name of the context. Enter a single text or numeric string, up to 32 characters. 3. Set the storage type for the context.
  • Page 182: Configuring System Name, Contact, And Location

    The contact is typically a network administrator’s name, extension, and/or e-mail address. The physical location of the Cuda 12000 (sysLocation MIB object). Command root snmp-server contact <contact> snmp-server name <name> snmp-server location <location> show snmp no snmp-server {contact | name | location} ADC Telecommunications, Inc.
  • Page 183 Example The following example creates and displays name, contact, and location information: root# snmp-server name "cuda 111" root# snmp-server contact “John Smith, x334” root# snmp-server location "bldg. 1400" root# show snmp Contact Name Location SNMP packets received Bad SNMP version errors Unknown community names Illegal community names Encoding errors...
  • Page 184: Configuring Snmp Event Notification Types

    Informs are notifications that are acknowledged by the SNMP manager, so they are considered reliable. If an inform is sent and not acknowledged, it may be sent again. Informs are held in memory, which means they consume more router and network resources. ADC Telecommunications, Inc.
  • Page 185 A change in the craft port IP address. The secondary will not come up because its software revision does not match the software revision of the primary. For ADC internal use only. Generated when module boots from power up. Generated when module boots from reset. Notice A change in the ICL link.
  • Page 186 DOCSIS events refer to initialization faults on DOCSIS and EuroDOCSIS modules. A dynamic service response failure occurred during the dynamic services process. Event Class Notice Notice Error Critical Notice Notice Notice Notice Notice Notice Notice Notice Notice Warning ADC Telecommunications, Inc.
  • Page 187 System Event docss-dyn-ack-fail docs-dyn-req-fail docs-bpi-init docs-bpkm docs-dcc-ack-fail docs-dcc-req-fail docs-dcc-rsp-fail docs-dynamic-sa docs-init-ack-fail docs-init-req-fail docs-init-rsp-fail Routing events: Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Event Notification Types Description A dynamic service acknowledgement failure occurred during the dynamic services process. A dynamic service request failure occurred during the dynamic services process.
  • Page 188 A modem deregistration event refers to the deregistration of cable modems. Signifies that a number or percentage of modems have deregistered over the deregistration time interval. Event Class Notice Notice Warning ADC Telecommunications, Inc.
  • Page 189 The following table describes the parameters that you set to configure notifications: Table 9-8 Parameters Contained in Event Notification Configuration Parameter Host:Port Timeout Retry Notify or Community Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Event Notification Types Description The IP address and UDP port number on which the SNMP host is configured...
  • Page 190 Values range from 484 to 65535. The default is 484. The SNMP security model used to process SNMP messages and gain access to the group. Your options are V1, V2c or V3. ADC Telecommunications, Inc.
  • Page 191 Parameter Level Group Name Type Notifications Sent Cluster events: authentication-failure bcm-failover-down bcm-failover-up bcm-state-change Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Event Notification Types Description The level of security to process SNMP messages. You can choose one of the following three levels: No Authentication: Provides no authentication and no encryption.
  • Page 192 Description The secondary will not come up because its software revision does not match the software revision of the primary. For ADC internal use only. Generated when module boots from power up. Generated when module boots from reset. A change in the ICL link.
  • Page 193 Parameter chassis-fault-cleared DOCSIS events: docs-dyn-rsp-fail docss-dyn-ack-fail docs-dyn-req-fail docs-bpi-init docs-bpkm docs-dcc-ack-fail docs-dcc-req-fail docs-dcc-rsp-fail docs-dynamic-sa docs-init-ack-fail docs-init-req-fail Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Event Notification Types Description Indicates the chassis event that caused a fault is fixed. DOCSIS events refer to initialization faults on DOCSIS and EuroDOCSIS modules.
  • Page 194 OSPF virtual neighbors. Signifies a change in the state of an OSPF neighbor on a physical interface. To send this notification type, note that you also have to enable sending of OSPF neighbor state traps using the report command. ADC Telecommunications, Inc.
  • Page 195 Parameter ospf-virt-nbr-state Modem deregistration event: dereg-modems Perform the following tasks to configure event notifications. Refer to the configuration examples, below: Tasks 1. Enter configuration mode. 2. Create an SNMP host to receive trap messages. 3. Specify the UDP port number on which the SNMP host will receive traps.
  • Page 196 <retries>]} [version {1 | 2c | 3 {auth | noauth | priv}] [notification-type <type>...] show snmp host [parameters] show snmp notify [<ip address>] no snmp-server host <ip address> {traps | informs} [mask] [notification-type <type>...] version 2c noauth Mask Storage NonVolatile ADC Telecommunications, Inc.
  • Page 197 Example 2 The following example displays all SNMP hosts notification destinations and associated notification types. root# show snmp notify row count: 2 Host:Port Storage -------------------- ----------- --------------------------------------- ------ 136.4.6.6:164 NonVolatile trace-log cold-start link-up 127.0.0.1:54321 NonVolatile prov-service ldap-failed ldap-restored Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Event Notification Types Notifications Sent subnet-addr-low subnet-addr-high...
  • Page 198: Monitoring Snmp

    SetRequest-PDUs, and InformRequest-PDU packets that the SNMP entity receives and drops. Total number of packets that the SNMP engine receives and drops because the security model was not known or supported by the SNMP engine. Commands root show snmp ADC Telecommunications, Inc.
  • Page 199 Parameter Invalid Messages Unknown PDU Handlers Authentication Traps Example In the following example, the user issues the show snmp command to monitor SNMP activity. root# show snmp Contact Name Location SNMP packets received Bad SNMP version errors Unknown community names Illegal community names Encoding errors Silent drops...
  • Page 200: Sample Snmp Configurations

    The administrator then creates the community “monitor,” which includes an association to the group named “monitorgroup.” cli:192.168.208.3:root# snmp-server community monitor monitorgroup (SNMP) ANAGEMENT ROTOCOL ADC Telecommunications, Inc.
  • Page 201: Sample Snmpv3 Access Control

    To configure the “admincon” community, the administrator issues the following commands: cli:192.168.208.3:root# snmp-server view allaccess 1.3.6.1 included cli:192.168.208.3:root# snmp-server group admingroup v1 read allaccess write allaccess cli:192.168.208.3:root# snmp-server group admingroup v2 read allaccess write allaccess cli:192.168.208.3:root# snmp-server community admincon admingroup address 100.100.0.0 mask 255.255.0.0 To configure the “justme”...
  • Page 202 The group entry allows the context “admin” to have read and write access to the entire MIB. Only management hosts that use the user “superman” and the context “admin” can access the view “allaccess.” (SNMP) ANAGEMENT ROTOCOL ADC Telecommunications, Inc.
  • Page 203: Sample Notification Configuration

    Sample Notification Configuration The following sample commands configure the Cuda 12000 to send SNMPv1 traps to a host (201.1.1.20): cli:192.168.208.3:root# snmp-server view allaccess 1.3.6.1 included cli:192.168.208.3:root# snmp-server group trapcommunity v1 notify allaccess cli:192.168.208.3:root# snmp-server group trapcommunity v2 notify allaccess cli:192.168.208.3:root# snmp-server community trapcommunity trapcommunity cli:192.168.208.3:root# snmp-server host 201.1.1.20 trapcommunity traps version 1 In this example, the SNMP agent on the Cuda 12000 sends SNMPv1 traps (on the default UDP port of 162) to a host with an IP address of 201.1.1.20.
  • Page 204 9: S (SNMP) HAPTER IMPLE ETWORK ANAGEMENT ROTOCOL ADC Telecommunications, Inc.
  • Page 205: Managing System Events

    ANAGING This chapter describes how to manage event transmission and includes the following sections: About System Events (page 204) Configuring the Syslog Server (page 205) Configuring SNMP Trap Recipients (page 206) Configuring Event Transmission (page 208) Event Reporting (page 210) Event Classes and SNMP System Events (page 214) Clearing the Event Log (page 216) Displaying Event Transmission, Reporting, and Syslog Parameters...
  • Page 206: About System Events

    An event is a problem, a configuration change or some other noteworthy incident that occurs on the Cuda 12000 or in the network. Events create the generation of: System log (syslog) messages SNMP traps, which the Cuda 12000 sends to network management stations Internal log messages VENTS ADC Telecommunications, Inc.
  • Page 207: Configuring The Syslog Server

    Configuring the Syslog Server Before you manage event transmission or reporting using the syslog server, you set the IP address of the syslog server to which your Cuda 12000 writes system log messages, as required by DOCSIS 1.1 standards. You may specify the IP address of the local Syslog server on your Cuda 12000 or a remote syslog server on another Cuda 12000.
  • Page 208: Configuring Snmp Trap Recipients

    For information on command arguments, refer to Chapter 9, Simple Network Management Protocol (SNMP), on page page 161, or see snmp-server host command in the Cuda 12000 IP Access Switch CLI Reference Guide. show snmp host <ip-address> ADC Telecommunications, Inc.
  • Page 209: Removing Snmp Trap Recipients

    Removing SNMP Trap Recipients Perform this task to remove an SNMP trap recipient: Task Remove the trap recipient. Example root# no snmp-server host 136.4.6.6 Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring SNMP Trap Recipients Command no snmp-server host <ip-address>...
  • Page 210: Configuring Event Transmission

    — The Cuda 12000 stops trap and syslog message transmissions at the threshold. To resume trap and syslog message transmission, you must reset the threshold. inhibited – The Cuda 12000 suppresses all trap transmissions and syslog messages. ADC Telecommunications, Inc.
  • Page 211 Parameter Throttle Inhibited To configure event transmission, perform the following tasks: Task 1. Enter root mode. 2. Specify the event threshold. 3. Specify the event threshold interval. 4. Specify the event administrative status. 5. Display the event threshold. Example The following is an example of an event threshold configuration, using the default settings: cli:192.168.208.3:root# show event-config throttle Event Throttle Parameters...
  • Page 212: Event Reporting

    Error events.) Indicates an event that requires attention, but is not a failure. Indicates an event that may be helpful for tracing normal operation. Informational events do not report failures. An event used for only debugging purposes. ADC Telecommunications, Inc.
  • Page 213: Reporting Actions

    Reporting Actions Each event class is associated with a reporting action. The following table lists the reporting actions: Table 10-3 Reporting Actions Reporting Action local local|traps local|syslog local|traps|syslog none Configuring Event Reporting By default, the Cuda 12000 reports events as follows: Table 10-4 Default Event Class Reporting Actions Event Class Emergency...
  • Page 214 {local|traps|syslog} {local|traps} {local|syslog} event-config reporting error {local|traps|syslog} {local|traps} {local|syslog} event-config reporting warning {local|traps|syslog} {local|traps} {local|syslog} event-config reporting notice {local|traps|syslog} {local|traps} {local|syslog} event-config reporting info event-config reporting debug ADC Telecommunications, Inc.
  • Page 215: Viewing Event Reporting Configuration

    Viewing Event Reporting Configuration You may view the event reporting configuration. The output includes event reporting configuration for all current event classes. To view the current event reporting configuration, perform the following tasks: Task 1. Enter root mode. 2. Display current event reporting configuration Example The following example displays the current event reporting configuration.
  • Page 216: Event Classes And Snmp System Events

    Interface-related events: link up link down chassis-fault chassis-fault-cleared VENTS Event Class Notice Notice Notice Notice Notice Notice Notice Notice Notice Notice Critical Notice Critical Notice Warning Error Error Notice Notice Error Critical Notice ADC Telecommunications, Inc.
  • Page 217 SNMP System Event Provisioning events: duplicate-addr isp-addr-high isp-addr-low ldap-failed ldap-restored prov-service subnet-addr-high subnet-addr-low DOCSIS events: docs-dyn-rsp-fail docss-dyn-ack-fail docs-dyn-req-fail docs-bpi-init docs-bpkm docs-dcc-ack-fail docs-dcc-req-fail docs-dcc-rsp-fail docs-dynamic-sa docs-init-ack-fail docs-init-req-fail docs-init-rsp-fail Routing events: ospf-nbr-state ospf-virt-nbr-state Modem deregistration event: dereg-modems Cuda 12000 IP Access Switch CLI-based Administration Guide Event Classes and SNMP System Events Event Class Notice...
  • Page 218: Clearing The Event Log

    Use this procedure to display the event transmission, reporting, and syslog parameters: Task 1. Enter root mode. 2. Display event transmission, reporting, and syslog parameters. VENTS Command root event-log clear Command root show event-config {throttle | reporting | syslog} ADC Telecommunications, Inc.
  • Page 219 Example root# show event-config Event Throttle Parameters ------------------------- Threshold Interval Admin Status Throttle Inhibited Event Reporting Priorities -------------------------- row count: 8 Priority ----------- ------------------ emergency local critical local|traps|syslog warning traps|syslog information none Syslog Server cli:192.168.208.3:root# show event-config throttle Event Throttle Parameters ------------------------- Threshold Interval...
  • Page 220: Displaying The Event Log

    The count starts at 1 when the entry is created and increments by one for each subsequent duplicate event. The event’s class (emergency, alert, critical, error, warning, notice, info, debug). 133.132.1.1 Command root show event-log ADC Telecommunications, Inc.
  • Page 221 Field Text Example root# show event-log row count: 133 Index First Time Last Time ------ ---------- ---------- ---------- ---------- ---------- ---------- 1 2000-12-31 2000-12-31 ,21:1:40.0 ,21:1:40.0 ,455:0 ,455:0 2 2000-12-31 2000-12-31 ,21:31:40. ,21:31:40. 0,455:0 0,455:0 3 2001-1-1,1 2001-3-6,1 :20:0.0,45 :26:40.0,4 55:0 4 2000-12-31 2000-12-31 ,19:28:20.
  • Page 222 10: M HAPTER ANAGING YSTEM VENTS ADC Telecommunications, Inc.
  • Page 223: Ip Routing

    IP R Chapter 11 Creating Route Filters Chapter 12 Configuring DHCP Relay Chapter 13 Configuring DHCP Authority Chapter 14 Configuring IP Chapter 15 IP Packet Filtering Chapter 16 Network-Layer Bridging Chapter 17 Managing IP Multicast OUTING...
  • Page 225: Creating Route Filters

    REATING This chapter provides information and procedures on how to create route filters to control the flow of routes on your network. You create these route filters in the form of route-maps and map-lists. Route-maps contain the fundamental gating action (permit or deny) based on selected route-match criteria with optional override actions.
  • Page 226: About Rip And Ospf Route Maps

    Map lists are made up of one or more route maps. The same route map may be shared among multiple map lists. Route maps within each map list must be sorted in order of the specific-to-general match criteria and action needs of the map list. ADC Telecommunications, Inc.
  • Page 227: Creating Route Maps

    Creating Route Maps You can use route maps to control and modify routing information and to define the conditions by which routes are redistributed. When you run the route-map command within router:rip:import or export mode, or router:ospf:export mode the following syntax applies: The map-tag is a number that identifies the route map.
  • Page 228 11: C HAPTER REATING OUTE ILTERS While within any route-map mode, you can display a summary of all route maps configured within that mode using the show route-map command as follows: ADC Telecommunications, Inc.
  • Page 229: Using The Match Command

    Using the Match Command Use the match command within route-map configuration mode to define the match criteria for the route map. Refer to the following sections for more information on using this command: “Creating OSPF Import Route Maps” on page 229 “Creating OSPF Export Route Maps”...
  • Page 230: Using The Override Command

    The following example configures route-map 80 to redistribute matching routes with a cost metric of 10. cli:172.16.19.10:router:ospf:export:route-map(80)# override metric 10 cli:172.16.19.10:router:ospf:export:route-map(80)# show route-map 80 Description Route Address Route Mask Type Specific1 Specific2 Key Bits Metric Flags Action Tag cli:172.16.19.10:router:ospf:export:route-map(80)# ILTERS 172.16.19.0 255.255.255.0 0.0.0.0 0.0.0.0 ADC Telecommunications, Inc.
  • Page 231: Creating Ospf Import Route Maps

    Creating OSPF Import Route Maps You can use OSPF import route-maps to override the preference of incoming OSPF routes. Preference is the local ranking of the route. OSPF import route maps are created within router-ospf import mode using the route-map command. To create an OSPF import route map, use this procedure: Permit and deny options do not apply to OSPF import routes as all OSPF routes are always learned.
  • Page 232 1 cli:172.16.19.10:router:ospf:import:route-map(1)# match ip-address 172.16.0.0 255.255.0.0 cli:172.16.19.10:router:ospf:import:route-map(1)# override preference 100 cli:172.16.19.10:router:ospf:import:route-map(1)# show route-map 1 Description Route Address Route Mask Peer Address Peer Mask Key Bits Preference Flags cli:172.16.19.10:router:ospf:import:route-map(1)# ILTERS 172.16.0.0 255.255.0.0 0.0.0.0 0.0.0.0 2049 ADC Telecommunications, Inc.
  • Page 233: Creating Ospf Export Route Maps

    Creating OSPF Export Route Maps You can use OSPF route maps to permit or deny advertisement of routes learned from a non-OSPF protocol. For example, you can choose to advertise select routes onto your OSPF network if they were originally learned through the RIP protocol, or if they were manually added as a static route.
  • Page 234 (a route to a directly connected network). override {metric <metric-value> | tag <tag-value>} show route-map <map-tag> specific1 <specific1-value> | specific2 <specific2-value> | route-type {none | connected | static | special | rip | bgp-ext | bgp-int | ADC Telecommunications, Inc.
  • Page 235 Creating Route Maps The following example creates an export route map that prevents the 176.16.0.0 RIP network from being advertised. Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 236: Creating Rip Import Route Maps

    ILTERS Command router rip import route-map <map-tag> match {ip-address <ip-address> <mask> | tag <tag-value> {exact | exclude} | peer-address <ip-address> <mask>} override {metric <metric-value> | tag <tag-value> | preference <preference-value>} show route-map <map-tag> ADC Telecommunications, Inc.
  • Page 237 Creating Route Maps The following example creates a RIP import route-map that prevents the 176.16.0.0 network learned through a non-RIP protocol from being advertised via the RIP protocol. Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 238: Creating Rip Export Route Maps

    To create a RIP export route map, use this procedure: Task 1. Enter router-rip mode. 2. Enter export mode. 3. Specify the route map or create a new one if it does not already exist. ILTERS Command router rip export route-map <map-tag> {permit | deny} ADC Telecommunications, Inc.
  • Page 239 Task 4. Define that match criteria for this route map. 5. Define the override criteria that you want the system to apply to any routes that match. 6. Optional: You can then verify the route map with the show route-map command. Cuda 12000 IP Access Switch CLI-based Administration Guide Creating Route Maps Command...
  • Page 240 11: C HAPTER REATING OUTE ILTERS The following example creates a RIP export route map that allows the 176.16.0.0 network that was learned through a non-RIP protocol to be advertised via RIP with a cost of 16. ADC Telecommunications, Inc.
  • Page 241: Creating Map Lists

    Creating Map Lists A map-list is a sequential grouping of route maps. These route-maps serve as the filter criteria within the map-list. A route is sequentially compared against all route maps that comprise the active route list. Upon finding a match, the system takes the action defined by the route map and exists the list.
  • Page 242 ILTERS Command For more information about the route-map command and defining route maps, see “Creating Route Maps” on page 225. router rip router ospf import export map-list <route-map-list-number> route-map <route-map-number> set {active | inactive} ADC Telecommunications, Inc.
  • Page 243: Route Filter Configuration Example

    The following example creates a RIP import filter by adding route maps 1, 2, and 3 to the a map list number 20 and designates it as the active list to use for RIP imports. Route Filter Configuration Example The following example creates two RIP import route-maps and adds them to map-list 1: Cuda 12000 IP Access Switch CLI-based Administration Guide Route Filter Configuration Example...
  • Page 244 11: C HAPTER REATING OUTE ILTERS ADC Telecommunications, Inc.
  • Page 245: Configuring Dhcp Relay

    ONFIGURING This chapter provides information and procedures on how to configure DHCP relay on a cable interface and includes the following sections: About DHCP Relay (page 244) Displaying DHCP Relay Configuration (page 245) Configuring DHCP Relay Options (page 247) Specifying DHCP Servers (page 249) DHCP and BOOTP Policies (page 251) DHCP R ELAY...
  • Page 246: About Dhcp Relay

    DHCP Relay requests on behalf of the cable modem. This is the same address as the Gateway Address configured on the interface. When a DHCP Request is received and it is from the cable modem, then the CM Gateway Address is used by the DHCP Relay. ADC Telecommunications, Inc.
  • Page 247: Displaying Dhcp Relay Configuration

    Enable or disable agent options. Displaying DHCP Relay Configuration You can display the current DHCP relay configuration using the show dhcp-relay command from within interface cable <c/s/i> mode, as shown in the following example: cli:192.168.208.3:interface:cable:csi(1/1/1)# show dhcp-relay dhcp-relay Add Agent Options Drop Mismatch Max.
  • Page 248 Maximum packet length allowed to be relayed. DHCP Relay mode configured on this interface. Indicates the IP gateway that is used Cable modems (CM) CPE devices attached to this cable interface MTA devices ADC Telecommunications, Inc.
  • Page 249: Configuring Dhcp Relay Options

    Configuring DHCP Relay Options The Cuda 12000 allows you to enable and configure DHCP Relay functionality on each IP interface so that the interface can forward DHCP requests to a central DHCP server. You must enable DHCP Relay on a select CMTS interface to dynamically allocate network addresses to the attached cable modems.
  • Page 250 Drop Mismatch Max. Pkt. Len. Relay Mode Server Address ---------------- giAddresses: ELAY Command dhcp-relay cm-gateway <gateway address> dhcp-relay mta-gateway <gateway address> show dhcp-relay 1/1/1 Interface Priority 8781825 Other 8781825 Primary enable enable disable replace 201.1.2.1 201.1.2.1 201.1.2.1 ADC Telecommunications, Inc.
  • Page 251: Specifying Dhcp Servers

    Specifying DHCP Servers You must specify the DHCP server to which you want the cable interface to forward DHCP Requests. The DHCP server is configured on a per interface basis. You may add up to 32 DHCP servers. If a DHCP server is not configured, then the DHCP server drops all DHCP requests as it does not know where to forward them.
  • Page 252: Specifying The Internal Dhcp Server

    The following example configures cable interface 1/1/1 to forward DHCP messages to the internal FastFlow BPM DHCP server: cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# dhcp-policy default permit forward-internal ELAY Command interface cable <c/s/i> dhcp-policy default permit forward-internal ADC Telecommunications, Inc.
  • Page 253: Dhcp And Bootp Policies

    DHCP and BOOTP Policies You can use Dynamic Host Configuration Protocol (DHCP) and Bootstrap Protocol (BOOTP) policies to control which devices obtain IP addresses and which DHCP and BOOTP servers allocate those addresses. This section provides information and procedures about configuring DHCP and BOOTP policies on the Cuda 12000 and includes the following sections: About DHCP Policies About BOOTP Policies...
  • Page 254: About Bootp Policies

    BOOTP is a protocol that allows diskless workstations to boot off of a network server, called a BOOTP server. You can configure the cable interface to deny (drop) a matching BOOTP request or permit it to be forwarded to a list of BOOTP servers. ADC Telecommunications, Inc.
  • Page 255: Configuring Dhcp And Bootp Policies

    Configuring DHCP and BOOTP Policies DHCP Policies determine the DHCP servers to which a CMTS interface forwards DHCP requests from attached cable modems, CPE devices and MTA devices. BOOTP Policies determine the BOOTP servers to which a CMTS interface forwards BOOTP requests from attached cable modems and diskless workstations.
  • Page 256 Deny (drop) the packet without forwarding Specifies that the current cable interface forwards DHCP requests internally (meaning, to a DHCP server on the local Cuda 12000). Optionally, you can specify the disable keyword to disable internal forwarding. ADC Telecommunications, Inc.
  • Page 257 The following table describes the parameters that you set to configure BOOTP policies: Table 12-3 BOOTP Policy Parameters Parameter Index Number Policy Server List Match Criteria Policy Action Cuda 12000 IP Access Switch CLI-based Administration Guide DHCP and BOOTP Policies Description Determines the sequence in which a BOOTP request is compared to each policy.
  • Page 258 [vendor-class-id {cm | mta}] [description <string>] bootp-policy {<policy-index> | default} {deny mac <mac-address> [mask <mask>] ... | permit <ip-address>... mac <mac-address> [mask <mask>] ...} [description <string>] Command interface cable <c/s/i> show dhcp-policy show bootp-policy show bootp-policy <policy-index> show bootp-policy default ADC Telecommunications, Inc.
  • Page 259 To remove DHCP or BOOTP policies from the current cable interface, perform the following tasks within interface cable <c/s/i> mode: Task 1. Remove all DHCP policies from the current cable interface. 2. Remove all BOOTP policies from the current cable interface. 3.
  • Page 260 2. Display the default BOOTP policy. Note that you cannot delete the default DHCP or BOOTP policy. ELAY Command dhcp-policy default {permit <ip-address>... | deny} bootp-policy default {permit <ip-address>... | deny} Command show dhcp-policy default show bootp-policy default ADC Telecommunications, Inc.
  • Page 261: Dhcp Policy Configuration Examples

    DHCP Policy Configuration Examples This section contains examples illustrating how to configure DHCP policies for a specified cable interface. The following example configures the DHCP relay agent to forward DHCP requests internally to the local FastFlow BPM DHCP server: cli:172.16.19.10:interface:cable:csi(1/1/1)# dhcp-policy default permit forward-internal The following example configures the DHCP relay agent on cable interface 1/1/1 to deny and drop any DHCP request from cable modem...
  • Page 262 Mac Mask Cable Modem Mac Policy Action Policy Server List Description C/S/I/P cli:172.16.19.10:interface:cable:csi(1/1/1)# ELAY 102.12.1.12 172.16.19.3 1 / 1 / 1 / 2 101.1.13.5 0 / 0 / 0 / 0 permit False False permit False True ADC Telecommunications, Inc.
  • Page 263 The following example configures the cable interface to forward all DHCP requests containing a source MAC address of 09:08:a4:95:2e:3a to server 101.1.1.1: cli:172.16.19.10:interface:cable:csi(1/1/1)# dhcp-policy 4 permit 101.1.1.1 mac 09:08:a4:95:2e:3a mask 00:00:00:00:00:00 cli:172.16.19.10:interface:cable:csi(1/1/1)# show dhcp-policy 4 Index Mac Address Mac Mask Cable Modem Mac Policy Action Policy Server List...
  • Page 264 12: C DHCP R HAPTER ONFIGURING ELAY ADC Telecommunications, Inc.
  • Page 265: Configuring Dhcp Authority

    ONFIGURING This chapter provides instructions on how to configure DHCP authority and includes the following sections: About DHCP Authority (page 264) Enabling DHCP Authority (page 266) Configuring DHCP Authority Ranges (page 267) Removing DHCP Authority Ranges (page 268) DHCP Authority Configuration Examples (page 269) DHCP A UTHORITY...
  • Page 266: About Dhcp Authority

    DHCP server responds with a DHCP offer containing the IP address that the client should use. After receiving the IP address, the client sends a DHCP request back to the DHCP server. The DHCP server then sends a DHCP acknowledgement to the client through the DHCP relay. UTHORITY ADC Telecommunications, Inc.
  • Page 267 When the DHCP relay agent sees this acknowledgement, it then checks to verify whether the IP address falls within a DHCP authority range configured on the interface, and one of the following actions occur: If the address does fall within a preconfigured DHCP authority range and DHCP Authority is enabled for that interface, an ARP entry is added to the ARP cache for that interface and tagged as being assigned through DHCP.
  • Page 268: Enabling Dhcp Authority

    2. Enable DHCP Authority on the current interface. Example The following example enables DHCP authority on cable interface 1/1/1, then uses the show dhcp-authority command to verify the configuration: UTHORITY Command interface <c/s/i> dhcp-authority {enable | disable} ADC Telecommunications, Inc.
  • Page 269: Configuring Dhcp Authority Ranges

    Configuring DHCP Authority Ranges The DHCP Authority ranges that you define for an interface dictate which addresses are protected by the authority feature. These DHCP authority IP address ranges that you define must fall within the range of IP addresses as allowed by the IP interface (as dictated by the network mask for that IP interface).
  • Page 270: Removing Dhcp Authority Ranges

    DHCP Authority Status cli:192.168.208.3:interface:cable:csi(1/1/1)# no dhcp-authority 1 cli:192.168.208.3:interface:cable:csi(1/1/1)# show dhcp-authority Range Number Lower Range ---------------- ---------------- ---------------- ------ DHCP Authority Status UTHORITY Command interface <c/s/i> no dhcp-authority <index number> Upper Range 172.16.19.20 enable Upper Range enable Status Status ADC Telecommunications, Inc.
  • Page 271: Dhcp Authority Configuration Examples

    DHCP Authority Configuration Examples In the following example, cable interface 1/1/1 has an IP interface of 192.168.19.50: cli:172.16.19.10:interface:cable:csi(1/1/1)# show ip address Chassis/Slot/Interface row count: 1 IP Address ---------------- ---------------- ---------- ---------- 192.168.19.50 In the following example, this IP address is configured as the cable modem gateway.
  • Page 272 192.168.19.55 192.168.19.56 192.168.19.57 192.168.19.58 192.168.19.59 192.168.19.60 192.168.19.61 192.168.19.62 cli:172.16.19.10:interface:cable:csi(1/1/1)# UTHORITY MAC Address 00:10:95:04:0a:c4 00:10:95:04:0a:b7 00:90:96:00:29:6d 00:10:95:04:0a:c3 00:10:95:01:ef:d8 00:a0:73:69:39:65 00:90:83:36:82:f1 00:90:96:00:39:f9 00:90:96:00:39:7f 00:10:95:01:f0:05 00:90:83:32:9f:8c 00:90:83:36:82:ee Type other other other other other dynamic dynamic dynamic dynamic dynamic dynamic dynamic ADC Telecommunications, Inc.
  • Page 273: Configuring Ip

    ONFIGURING This chapter provides information on how to configure Internet Protocol (IP) routing protocols on the Cuda 12000 and describes the following functions: Configuring IP Addresses (page 272) Displaying the Routing Table (page 277) Configuring Static Routes (page 278) Managing the Address Resolution Protocol (ARP) (page 284) Configuring RIP (page 290) Configuring OSPF (page 298) Configuring IP Source Routing (page 320)
  • Page 274: Configuring Ip Addresses

    CMTS interface). You can also configure static routes via the loopback interface to act as backup routes to those configured via physical interfaces. Note that the <c/s/i> of the interface appears as 131/1/1 in show command output displays. ADC Telecommunications, Inc.
  • Page 275 You add an IP address to a selected physical interface or the loopback interface, and then enter configuration mode for that IP interface by performing the following tasks: Task 1. Enter configuration mode for the selected interface 2. Add the IP address. Example 1 cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1)
  • Page 276: Viewing Ip Interfaces

    The following example displays all IP addresses added to cable interface 1/1/1: cli:192.168.208.3:interface:cable:csi(1/1/1)# show ip address Chassis/Slot/Interface row count: 2 IP Address ---------------- ---------------- ---------- ---------- 201.1.1.1 201.1.2.1 1/1/1 Net Mask Interface 255.255.255.0 8781825 255.255.255.0 8781825 Priority Other Primary ADC Telecommunications, Inc.
  • Page 277 Example 2 The following example displays IP interface information for interface 1/1/1: cli:192.168.208.3:interface:cable:csi(1/1/1)# show ip interface Chassis/Slot/Interface Description Admin Status Oper Status - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - IP Address Net Mask Interface...
  • Page 278: Deleting Ip Addresses

    Chassis/Slot/Interface row count: 0 IP Address Net Mask ---------------- ---------------- ---------- ---------- cli:192.168.208.3:interface:ethernet:csi(1/11/1)# Command interface {<c/s/i> | loopback} no ip address <ip-address> show ip interface 1/11/1 Interface Priority 11337729 Primary 1/11/1 Interface Priority ADC Telecommunications, Inc.
  • Page 279: Displaying The Routing Table

    Displaying the Routing Table You can display the contents of the routing table using the show ip command within any mode, as shown in the following example: cli:192.168.208.3:root# show ip row count: 8 Protocol Route Destination Type -------- ------ --------------- --------------- --------------- ------ ------ Net Mgmt Remote 133.1.1.0 Local Local...
  • Page 280: Configuring Static Routes

    Assigns a metric to this static route. The metric is a number that is used to select the route when multiple routes to the same destination exist. The route with the lowest metric is selected. The default is 1. ADC Telecommunications, Inc.
  • Page 281 Perform the following tasks to add a static route to the routing table: Task 1. Enter configuration mode for the interface on which you want to add the route. 2. Add the static route. Example cli:192.168.208.3:root# interface 1/11/1 mode: interface:ethernet:csi(1/11/1) cli:192.168.208.3:interface:ethernet:csi(1/11/1)# ip route 222.2.1.0 255.255.255.0 222.2.2.1 cli:192.168.208.3:interface:ethernet:csi(1/11/1)# show ip...
  • Page 282: Deleting Static Routes

    3. Delete the static route. Command interface {<c/s/i> | loopback} show ip no ip route <dest-network> <mask> [<gateway-ip-address>] Note that you specify the IP address of the gateway only if a route with a duplicate destination network and mask exists. ADC Telecommunications, Inc.
  • Page 283 Example cli:192.168.208.3:root# interface 1/11/1 mode: interface:ethernet:csi(1/11/1) cli:192.168.208.3:interface:ethernet:csi(1/11/1)# show ip row count: 8 Protocol Route Destination Type -------- ------ --------------- --------------- --------------- ------ ------ Local Local 155.144.1.0 Local Local 199.3.1.0 Net Mgmt Remote 199.3.2.0 Local Local 201.1.1.0 Local Local 201.1.2.0 Net Mgmt Remote 222.2.1.0 Local Local 222.2.2.0...
  • Page 284: Adding The Default Route

    Net Mask Next Hop 0.0.0.0 201.1.1.10 255.255.255.0 155.144.1.1 255.255.255.0 199.3.1.1 255.255.255.0 199.3.1.3 255.255.255.0 201.1.1.1 255.255.255.0 201.1.2.1 255.255.255.0 222.2.2.2 255.255.255.0 222.2.2.1 ADC Telecommunications, Inc. Metric C/S/I 1 1/1/1 0 1/8/1 0 131/1/1 1 131/1/1 0 1/1/1 0 1/1/1 0 1/11/1 1 1/11/1...
  • Page 285: Deleting The Default Route

    Deleting the Default Route To add the default route, perform the following task: Task From any mode, delete the default route. Example cli:192.168.208.3:root# show ip row count: 8 Protocol Route Destination Type -------- ------ --------------- --------------- --------------- ------ ------ Net Mgmt Remote 0.0.0.0 Local Local 155.144.1.0...
  • Page 286: Managing The Address Resolution Protocol (Arp)

    To forward packets to a host on an IP network, an interface must know the IP address of the target host. Once the interface learns IP-to-MAC address mapping for a host, it stores this information in its ARP cache. ADC Telecommunications, Inc.
  • Page 287: Displaying The Arp Cache

    Displaying the ARP Cache Use the following procedure to display the ARP cache for a selected interface Task 1. Enter configuration mode for the selected interface. 2. Display the ARP cache for the selected interface. Example The following example displays the contents of the ARP cache maintained by cable interface 1/1/1: cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1)
  • Page 288: Adding Arp Entries

    The following example adds a static ARP entry to Ethernet interface 1/11/1: cli:172.16.19.10:root# interface 1/11/1 mode: interface:ethernet:csi(1/11/1) cli:172.16.19.10:interface:ethernet:csi(1/11/1)# add arp 172.31.1.70 00:10:93:01:ef:d7 cli:172.16.19.10:interface:ethernet:csi(1/11/1)# show arp row count: 1 IP Address ---------------- ------------------ ---------- 172.31.1.70 cli:172.16.19.10:interface:ethernet:csi(1/11/1)# Command interface <c/s/i> add arp <ip-address> <mac-address> MAC Address Type 00:10:93:01:ef:d7 static ADC Telecommunications, Inc.
  • Page 289: Deleting Arp Entries

    Deleting ARP Entries Static entries remain in the ARP cache until you manually remove them. You can remove any ARP entry using the following procedure. Task 1. Enter configuration mode for the selected Ethernet interface. 2. Remove the IP-to-MAC address mapping by specifying the IP address.
  • Page 290: Configuring The Arp Timeout

    2)# arp timeout 700 cli:192.168.208.3:interface:ethernet:csi(1/11/2)# show arp timeout ARP Aging ARP Timeout cli:192.168.208.3:interface:ethernet:csi(1/11/2)# no arp timeout cli:192.168.208.3:interface:ethernet:csi(1/11/2)# show arp timeout ARP Aging ARP Timeout Command interface <c/s/i> arp timeout <seconds> show arp timeout Enabled Disabled ADC Telecommunications, Inc.
  • Page 291: Clearing The Arp Cache

    Clearing the ARP Cache The clear arp-cache command allows you to delete all non-static entries in the ARP cache. If you issue this command from root mode, you delete all non-static ARP entries associated with all interfaces. If you issue this command from interface mode, you delete only the non-static ARP entries associated with the current interface.
  • Page 292: Configuring Rip

    “RIPv1 compatible” mode is enabled on interfaces by default for transmission. Before you can configure RIP, you must configure the IP interface on which you want to run RIP. See “Configuring IP Addresses” on page 272 for more information. ADC Telecommunications, Inc.
  • Page 293 Descriptions of the RIP parameters that you configure are listed below. Table 14-2 RIP Parameters Parameter IP Address Send Version Receive Version Cost Authentication ON Authentication Type Send Default Only Send Default Also Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring RIP Description IP address of the current interface.
  • Page 294 Indicates whether RIP is active (enabled) or inactive (disabled) on this interface. When RIP is disabled, RIP packets are not sent or received. ADC Telecommunications, Inc.
  • Page 295 You configure RIP on an IP interface by performing the following tasks: Task 1. Enter configuration mode for the interface on which you want to enable RIP. 2. Enter the IP address of this interface. 3. Enable RIP on the current interface.
  • Page 296 <number> Note: Before you can specify a default cost, you must issue the ip rip send default-only or ip rip send default-also commands. ip rip split-horizon ip rip poisoned-reverse ip rip neighbor <ip-address> ADC Telecommunications, Inc.
  • Page 297 Task 15.Configure the authentication type for the interface. When RIP is enabled for the first time on the interface, no authentication is in effect by default. 16.Configure the authentication key for the interface. 17.Verify the RIP configuration on the current interface. For more information on these commands, refer to the Cuda 12000 IP Access Switch CLI Reference Guide.
  • Page 298 Split Horizon Poisoned Reverse Status For more information on the ip rip commands, refer to the Cuda 12000 IP Access Switch CLI Reference Guide. 201.1.1.1 RIPv2 RIPv2 True Simple Password False False True True True True Active ADC Telecommunications, Inc.
  • Page 299: Disabling Rip On Ip Interfaces

    Disabling RIP on IP Interfaces Use this procedure to disable RIP on an interface: Task 1. Enter configuration mode for the interface for which you want to disable RIP. 2. Enter the IP address of this interface. 3. Disable RIP on the interface. For more information on these commands, refer to the Cuda 12000 IP Access Switch CLI Reference Guide.
  • Page 300: Configuring Ospf

    Link-state database size increases in proportion to network size. This causes several problems. Demand for router resources, such as memory and CPU time, can increase significantly. It also takes longer to calculate link costs for more links and generate large routing tables that large networks require. ADC Telecommunications, Inc.
  • Page 301 Configuring OSPF OSPF Areas To address large link-state databases, OSPF employs areas, which are groups of OSPF routers that exchange topology information. Designated routers only send LSAs to routers in the same area. If an autonomous system (AS) has one area, all routers in the AS receive LSAs; however, if the AS consists of many areas, LSAs are only sent to the appropriate areas, which minimizes traffic and the link-state database size.
  • Page 302 CPE ROUTER CPE ROUTER Area 1 Area Internal Border Router Router Figure 14-2 OSPF Router and Routing Classifications OSPF Routing Domain Internal Router CPE ROUTER CPE ROUTER Area 2 Area Border Router Routing Domain CPE ROUTER Boundary Router ADC Telecommunications, Inc.
  • Page 303: Ospf Configuration Task Overview

    OSPF Configuration Task Overview Configuration of the Cuda 12000 within an OSPF network includes: Configuring OSPF Global Parameters Adding OSPF Areas Removing OSPF Areas Configuring OSPF on IP Interfaces Removing OSPF from IP Interfaces Configuring OSPF Virtual Interfaces Removing OSPF Virtual Interfaces Configuring OSPF Neighbor Traps Configuring OSPF Global Parameters OSPF Global Parameters provide information about this router to other OSPF...
  • Page 304 Note that ASBR is disabled by default. If you configure this router as an ASBR, and then later decide to disable ASBR, issue this command: no asbr show ospf Enabled False 201.1.1.1 False True Disabled Disabled ADC Telecommunications, Inc.
  • Page 305: Adding Ospf Areas

    Adding OSPF Areas You can divide an AS into smaller, more manageable sub-divisions or areas. This reduces the amount of routing information that must travel through the network and serves to reduce the size of each router’s routing database. In order for the Cuda 12000 to support OSPF, you must add at least one area.
  • Page 306 <area-id> {enable | disable} show ospf area <area-id> Command Refer to “Removing OSPF Areas” on page 305. no ospf area <area-id> range <ip address> <mask> [advertise-matching] no ospf area <area-id> authentication ADC Telecommunications, Inc.
  • Page 307: Removing Ospf Areas

    Example cli# router ospf mode: router:ospf cli# ospf area 0.0.0.1 cli# ospf area 0.0.0.1 authentication md5 cli# ospf area 0.0.0.1 stub cli# ospf area 0.0.0.1 default-cost 10 cli# Removing OSPF Areas You remove a specified OSPF area by performing the following tasks: Task 1.
  • Page 308: Configuring Ospf On Ip Interfaces

    1. Create the IP interface. 2. Enter IP address configuration mode for the interface. 3. Assign an area ID to the interface. Command Refer to “Configuring IP Addresses” on page 272. ip address <ip-address> <mask> ip ospf area-id <area-id> ADC Telecommunications, Inc.
  • Page 309 Example The following example enters IP address configuration mode for interface 1/1/1 and assigns the interface an area ID of 1.1.1.1. cli:172.16.19.10:root# router ospf mode: router:ospf cli:172.16.19.10:router:ospf# ospf area 1.1.1.1 cli:172.16.19.10:router:ospf# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# ip address 172.16.9.8 255.255.255.0 cli:172.16.19.10:interface:cable:csi(1/1/1):ip-address(172.16.9.8)# ip ospf area-id 1.1.1.1 cli:172.16.19.10:interface:cable:csi(1/1/1):ip-address(172.16.9.8)# show ip...
  • Page 310 The Cuda 12000 and all of its OSPF neighbors on the IP interface you are configuring must have matching hello interval values. Otherwise, the neighbors cannot form adjacencies. Command ip ospf cost <number> ip ospf dead-interval <seconds> ip ospf hello-interval <seconds> ADC Telecommunications, Inc.
  • Page 311 Task 4. Configure the interface priority. This number identifies the priority of the Cuda 12000 relative to other OSPF routers on the current interface. The number is used to elect the designated and backup designated routers. The router with the highest priority is considered the designated router.
  • Page 312 <key> | key <key>} Use the key-id <id> key <key> argument with MD5; use key <key> with simple password. show ip ospf Command Refer to “Removing OSPF from IP Interfaces” on page 312. no ip ospf authentication ADC Telecommunications, Inc.
  • Page 313 Example The following example configures OSPF parameters on IP interface 201.1.1.1: cli:# router ospf mode: router:ospf cli:# show ospf area row count: 2 Area Id Auth Type ImpAsExt SPF ---------------- --------- -------- ---- ----- ----- ----- ------ ------- ----- 0.0.0.0 0.0.0.1 cli:# interface 1/1/1 mode: interface:cable:csi(1/1/1)
  • Page 314: Removing Ospf From Ip Interfaces

    2. Enter the IP address of this interface. 3. Remove OSPF from the interface. For more information on these commands, refer to the Cuda 12000 IP Access Switch CLI Reference Guide. Command interface <c/s/i> ip address <ip-address> <mask> no ip ospf area-id <area-id> ADC Telecommunications, Inc.
  • Page 315: Configuring Ospf Virtual Interfaces

    Configuring OSPF Virtual Interfaces OSPF requires that all areas be attached to the OSPF backbone area (area 0.0.0.0). However, you may encounter situations in which you cannot connect an OSPF area directly to the backbone. If your Cuda 12000 is an area border router between one area that is physically connected to the OSPF backbone and one area that is not, you can create a virtual interface on your Cuda 12000 to connect the non-contiguous area to the OSPF...
  • Page 316 Cuda 12000. You would specify 0.0.0.1 for the transit area and 133.132.1.1 for the neighbor router ID. Area 0.0.0.1 (Transit Area) CPE ROUTER Router ID = 133.132.1.1 Third Party Router (ABR) Area 0.0.0.0 (Backbone) ADC Telecommunications, Inc.
  • Page 317 Use this procedure to configure a virtual interface: Task 1. Enter router-ospf mode. 2. Configure the transit area and the router ID of the neighbor for this virtual interface. 3. Configure the dead-interval, in seconds. OSPF neighbors connected by a virtual interface must have matching dead interval values in their respective virtual interface configurations.
  • Page 318 <neighbor-router-id> authentication ospf-vi <transit-area-id> <neighbor-router-id> authentication {key-id <id> key <key> | key <key>} Use the key-id <id> key <key> argument with MD5; use the key <key> argument with password. show ospf interface virtual show ospf neighbor virtual ADC Telecommunications, Inc.
  • Page 319: Removing Ospf Virtual Interfaces

    Example The following example illustrates how to create a virtual interface that links a non-contiguous area to the backbone via a transit area of 0.0.0.1 and an ABR with a router ID of 133.132.1.1: cli:192.168.208.3:root# router ospf mode: router:ospf cli:192.168.208.3:router:ospf# ospf-vi 0.0.0.1 133.132.1.1 cli:192.168.208.3:router:ospf# ospf-vi 0.0.0.1 133.132.1.1 dead-interval 500 cli:192.168.208.3:router:ospf# ospf-vi 0.0.0.1 133.132.1.1 hello-interval 400 cli:192.168.208.3:router:ospf# ospf-vi 0.0.0.1 133.132.1.1 retransmit-interval...
  • Page 320: Configuring Ospf Neighbor Traps

    Note: To disable the trap, issue this command: no report ospf-virt-nbr-state Refer to Chapter 10 “Managing System Events” for more information. Refer to Chapter 9 “Simple Network Management Protocol (SNMP)” for more information. ADC Telecommunications, Inc.
  • Page 321 Example cli:192.168.220.230:router:ospf# report ospf-nbr-state cli:192.168.220.230:router:ospf# report ospf-virt-nbr-state cli:192.168.220.230:router:ospf# show ospf Admin Status TOS Support Router Id ABR Status ASBR Status Report ospf-nbr-state Report ospf-virt-nbr-state For snmp-server host command examples, refer to Chapter 9 “Simple Network Management Protocol (SNMP)” for more information. For event-config reporting command examples, refer to Chapter 10 “Managing System Events”...
  • Page 322: Configuring Ip Source Routing

    Adding IP Source Routes Displaying IP Source Routes Removing IP Source Routes In addition, a sample source routing configuration is provided. Before you can effectively perform source routing configuration tasks, you need to understand some concepts behind IP source routing. ADC Telecommunications, Inc.
  • Page 323: About Ip Source Routing

    About IP Source Routing Source routing allows you to configure a different default route for each IP network or host. Specifically, source routing allows you to define the default route (next hop gateway) to which a packet containing a particular source IP address should be forwarded in the event that a local route to the destination does not exist.
  • Page 324: Adding Ip Source Routes

    Similarly, the following example configures interface 1/1/1 to forward any packets received from host 172.16.19.4 to a next-hop destination of 171.16.19.50: cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# ip source-route 172.16.19.4 255.255.255.255 172.20.19.50 Command interface <c/s/i> ip source-route <ip address> <mask> <next hop gateway> ADC Telecommunications, Inc.
  • Page 325: Displaying Ip Source Routes

    Displaying IP Source Routes You display the source routing entries configured on a particular interface by performing the following tasks: Task 1. Enter interface mode. 2. Display a source route entry. Example The following example displays all source route entries configured on interface 1/1/1: cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1)
  • Page 326: Removing Ip Source Routes

    ---------------- ---------------- ---------------- 172.16.19.0 row count: 1 cli:172.16.19.10:interface:cable:csi(1/1/1)# show ip interface source-route Address ---------------- ---------------- ---------------- row count: 0 cli:172.16.19.10:interface:cable:csi(1/1/1)# Command interface <c/s/i> no ip source-route <ip address> <mask> <next hop gateway> Mask NextHop 255.255.255.0 172.20.19.4 Mask NextHop ADC Telecommunications, Inc.
  • Page 327: Source Routing Configuration Example

    Source Routing Configuration Example For example, if 3 users are connected to a single DOCSIS module on interface 1/1/1; each user would belong to a different internet service provider, ISP-1, ISP-2, ISP-3, as described in the following table: Customer Host 172.16.19.2 172.16.19.5 172.16.19.9...
  • Page 328 14: C HAPTER ONFIGURING ADC Telecommunications, Inc.
  • Page 329: Ip Packet Filtering

    IP P This chapter covers IP packet filtering on the Cuda 12000 and includes the following sections: About IP Packet Filtering (page 328) Enabling and Disabling IP Packet Filtering (page 329) Understanding Access Lists (page 330) Creating Access Lists (page 331) Applying Access Lists to Interfaces (page 336) Packet Filtering Considerations and Example (page 340) Note that IP packet filtering is only supported on cable interfaces.
  • Page 330: About Ip Packet Filtering

    2. Apply the access lists to specified interfaces using the access-class command as described in “Applying Access Lists to Interfaces” on page 336. 3. Enable IP packet filtering on the specified interface as described in “Enabling and Disabling IP Packet Filtering,” next. ADC Telecommunications, Inc.
  • Page 331: Enabling And Disabling Ip Packet Filtering

    Enabling and Disabling IP Packet Filtering Whenever you apply an access-list to an interface using the access-class command IP filtering is automatically enabled. You can disable IP filtering so that all packets are permitted to cross the interface. You must disable access lists manually; IP filtering is not automatically disabled when access lists are removed.
  • Page 332: Understanding Access Lists

    You cannot modify an existing access list, which means that if you want to change an access list, you must delete it and then recreate it with the same name. ADC Telecommunications, Inc.
  • Page 333: Creating Access Lists

    Creating Access Lists Access lists are comprised of rules that are sequenced according to assigned rule numbers. These rules are created and assigned to access lists using the access-list command. Packets are matched against the lowest numbered rules first. Each rule defines a permit or deny action which determines whether the packet is accepted or permitted when matched.
  • Page 334 | host <destination ip address> | any} {<ip address> <IP mask> | host <ip address> | <operator> <port> [<port>] | any}] {< IP address> < mask > | any | host <ip address> [<operator> <port> [<port>] ] established] [tos <tos> <tos mask>] [change-tos <tos>] ADC Telecommunications, Inc.
  • Page 335 For example, the following access list permits TCP traffic on port 23 (Telnet) from host 172.16.19.200 to any IP address destination. cli:172.16.19.10:root# access-list 5 permit 1 tcp 172.16.19.200 0.0.0.0 any eq 23 To create a UDP access list, perform the following task in either root mode or Creating UDP Access Lists interface configuration mode:...
  • Page 336 For TCP protocol only. Indicates an established TCP connection. Match occurs when the ACK or RST bits of a TCP datagram are set. Type of Service level identified in the IP packet header. Valid Range 0 – 15. Type of Service mask. ADC Telecommunications, Inc.
  • Page 337: Displaying Access Lists

    Displaying Access Lists To display the contents of a specified access list, perform the following task within root or interface <c/s/i> mode: Task 1. Display all access lists within the system. 2. Display a specified access list. Deleting Access Lists To delete an access list, perform the following task within root or interface <c/s/i>...
  • Page 338: Applying Access Lists To Interfaces

    You apply access lists to a specific interface by using the access-class command. To do so, perform the following task within interface <c/s/i> mode: Task Apply filters to the current interface to restrict incoming or outgoing traffic. Command access-class <list number> {in | out} priority <priority number> ADC Telecommunications, Inc.
  • Page 339 Applying Access Lists to Interfaces The following example applies access list 1 to the inbound interface and access list 2 to the outbound interface of cable interface 1/1/1: Just as the rule number determines the sequence of rule examination within an access list, priority specifies the order of access list examination within the access class that you apply to an inbound or outbound interface.
  • Page 340: Displaying Access Classes

    Access List 5 / Priority 5 Command show access-class Access Class/Outbound Access List 1 / Priority 1 Access List 2 / Priority 2 Access List 3 / Priority 3 Access List 4 / Priority 4 Access List 5 / Priority 5 ADC Telecommunications, Inc.
  • Page 341: Removing Access Lists From Access Classes

    Removing Access Lists from Access Classes To remove an access list from an interface, remove it from the access class on that interface. To do so, perform the following task within interface <c/s/i> mode: Task Remove an access list from an interface. Cuda 12000 IP Access Switch CLI-based Administration Guide Applying Access Lists to Interfaces Command...
  • Page 342: Packet Filtering Considerations And Example

    To solve this, place a permit any statement in the list as follows: cli:172.16.19.10:interface:pos:csi(1/3/1)# access-list 2 permit 2 ip any any Access list 2 is now comprised of the following rules: deny 172.16.19.20 any permit any any deny any any ADC Telecommunications, Inc.
  • Page 343: Match Sequence

    With the added permit any rule, only packets from the 172.16.19.20 are rejected, all others pass. This is because once the permit any condition is met, no further lines in the access list are read. Match Sequence The sequence in which an inbound or outbound packet is matched against the filter criteria of an interface is determined by the following: Rule number within access list —...
  • Page 344 15: IP P HAPTER ACKET ILTERING ADC Telecommunications, Inc.
  • Page 345: Network -Layer Bridging

    ETWORK Network-layer bridging allows a single subnet to span across multiple DOCSIS modules. This chapter provides information and procedures about network-layer bridging on the Cuda 12000 and includes the following sections: About Network-Layer Bridging (page 344) Creating Network-Layer Bridges (page 345) Creating Bridge Groups (page 347) Adding Interfaces to Bridge Groups (page 349) Assigning IP Addresses To Bridge Groups (page 351)
  • Page 346: About Network-Layer Bridging

    After you assign an IP address to this bridge group, the address will apply to all interfaces that are members of the bridge group. ADC Telecommunications, Inc.
  • Page 347: Creating Network-Layer Bridges

    Creating Network-Layer Bridges The key to spanning a single subnet across multiple DOCSIS modules is to configure the same IP gateway on each module. Because the gateway serves as the key that dictates address assignment for cable modems, CPE devices or MTAs, configuring the same IP gateway on each cable interface enables the DHCP server to assign those devices IP addresses from the same subnet or subnet pool.
  • Page 348 You can only assign 1 IP address to a specified bridge group. A single egress port can belong to a maximum of 16 different NLBGs. An NLBG can contain up to 32 physical interfaces; you can define a maximum of 16 NLBGs on single chassis. RIDGING ADC Telecommunications, Inc.
  • Page 349: Creating Bridge Groups

    Creating Bridge Groups You must first create a network-layer bridge group before you can configure it. After you create the bridge group, you then configure it within interface configuration mode. You can identify bridge groups using either numbers or strings; the text string that you specify is case-sensitive.
  • Page 350 The follow example removes all bridge groups configured on the system: cli:172.16.19.10:root# show bridge-group Bridge Group: Bridge_1 Bridge Group: 5 cli:172.16.19.10:root# no bridge-group all 2 Bridge Groups have been deleted cli:172.16.19.10:root# RIDGING Command no bridge-group <bridge-group> no bridge-group all ADC Telecommunications, Inc.
  • Page 351: Adding Interfaces To Bridge Groups

    Adding Interfaces to Bridge Groups After you create a bridge group, you can then enter configuration mode for the group and assign system interfaces to it. All interfaces that you add to the bridge group become part of the layer 3 bridge. To add an interface to a specified bridge group, perform the following tasks: Task 1.
  • Page 352 16: N HAPTER ETWORK AYER RIDGING To remove an interface from a bridge group, use the no bridge-interface command, as shown in the following example: ADC Telecommunications, Inc.
  • Page 353: Assigning Ip Addresses To Bridge Groups

    Assigning IP Addresses To Bridge Groups A network-layer bridge is comprised of interfaces that belong to the same bridge group. They share any IP address that you assign to the bridge group. The IP address that you assign to the bridge-group is automatically added to the routing table.
  • Page 354 16: N HAPTER ETWORK AYER RIDGING ADC Telecommunications, Inc.
  • Page 355: Managing Ip Multicast

    ANAGING This chapter describes how to manage IP Multicast on the Cuda 12000 and includes the following sections: About IP Multicast (page 354) Managing IGMP Interfaces (page 356) Managing IGMP Proxies (page 363) Displaying Multicast Routes (page 366) IP M ULTICAST...
  • Page 356: About Ip Multicast

    Cuda 12000 about the multicast groups from which PC4, PC3, PC2 and PC1 want to receive packets. To transmit the multicast traffic to hosts PC4, PC3, PC2, and PC1, the remote multicast router is made aware that a host is requesting traffic for these multicast groups. ULTICAST ADC Telecommunications, Inc.
  • Page 357 If IGMP proxy is enabled for these multicast groups, the Cuda 12000 joins these groups on the proxy interface. When the remote multicast router sends an IGMP query to the Cuda 12000, the Cuda 12000 replies with IGMP reports for all multicast groups joined by the hosts. Since the remote multicast router knows about the additional multicast groups joined by the hosts, it routes multicast traffic for these groups onto the common Ethernet.
  • Page 358: Managing Igmp Interfaces

    Use the following procedure to join a multicast group on an IP interface manually: Task 1. Enter configuration mode for the selected interface. 2. Join the group on the interface. ULTICAST Command interface <c/s/i> ip igmp join-group <group-address> ADC Telecommunications, Inc.
  • Page 359: Configuring Igmp Interface Parameters

    Configuring IGMP Interface Parameters You can configure the following IGMP interface parameters: Query Interval — Specifies the frequency, in seconds, that the Cuda 12000 transmits IGMP host query packets on this particular interface. The default is 125 seconds with a range of 10 to 65535 seconds. Query Max Response Time —...
  • Page 360: Displaying Igmp Groups And Interface Parameters

    ULTICAST Command interface <c/s/i> query-max-response time <seconds> | version {2 | 1 | v2_only} | robustness <value> | router | last-query-interval <seconds>} Command root. show ip igmp {groups {<group-address> | <c/s/i>} | interface <c/s/i>} ADC Telecommunications, Inc.
  • Page 361 Table 17-1 describes interface details that the show ip igmp interface command displays. Table 17-2 displays details that the show ip igmp groups command displays. Table 17-1 Interface Details Parameter Multicast forwarding IP Address Interface is IGMP Host IGMP Querier Non-querier Interface Querier...
  • Page 362 1 of IGMP. The default is 1 and the range is 1 to 25 seconds. Remaining time until the Cuda 12000 determines that no IGMPv1 routers are present on the interface. When the value is greater than 0, the host replies to all queries with IGMPv1 membership reports. ADC Telecommunications, Inc.
  • Page 363 Table 17-2 Group Details Parameter Group Address Up Time Expires Last Reporter Status Learned Self Proxy Displaying Groups and Parameters from Interface Mode To display IGMP groups and interface parameters from interface mode: Task 1. Enter configuration mode for the interface.
  • Page 364: Deleting Igmp Groups

    ULTICAST Command root show ip igmp groups no ip igmp groups <group-address> Command enable root interface <c/s/i> show ip igmp groups clear ip igmp group [<group-address>] ADC Telecommunications, Inc.
  • Page 365: Managing Igmp Proxies

    Managing IGMP Proxies You can configure an interface to proxy for a single multicast group or a range of multicast groups. You can also display and delete IGMP proxies. Configuring Proxies Before configuring an interface to proxy for multicast groups, note that: You must assign an IP address to that interface.
  • Page 366 The interface proxies for an address range from 225.1.0.0 to 255.1.255.255 Example 2 — This example shows a single multicast group for which the interface proxies: Group Address — 226.1.1.1 Mask — 255.255.255.255 The interface proxies for the multicast group 226.1.1.1. ULTICAST ADC Telecommunications, Inc.
  • Page 367: Displaying Proxies

    Displaying Proxies Use this procedure to display proxies for multicast groups: Task 1. Enter root mode. 2. Display proxies. The show ip igmp proxy command displays the following information about each proxy: Group Address — IP Multicast group address or address range for which the interface acts as a proxy.
  • Page 368: Displaying Multicast Routes

    Outgoing Interface — Interface on which the multicast route is learned or joined. Outgoing Interface Up Time — Time in hours, minutes, and seconds since the multicast routing information was learned. ULTICAST Command enable root interface <c/s/i> show ip igmp mroute {<group-address> | summary} ADC Telecommunications, Inc.
  • Page 369: Configuring Cable Modem Termination Systems

    ABLE YSTEMS Chapter 18 Configuring Cable Modem Termination Systems Chapter 19 Managing Cable Modems Chapter 20 Subscriber Management Chapter 21 MIB Browsing ODEM ERMINATION...
  • Page 371: Cmts Upstream Frequency Reuse

    ONFIGURING ERMINATION Cable Modem Termination Systems (CMTS) consists of DOCSIS and EuroDOCSIS modules within the Cuda 12000. Configuring a CMTS consists of the following functions: Configuring the MAC Interface (page 370) Configuring the Downstream Channel (page 379) Configuring Upstream Channels (page 390) Configuring Admission Control (page 408) Configuring Frequency Hopping (page 411) Defining Modulation Profiles (page 418)
  • Page 372: Configuring The Mac Interface

    2. Display MAC parameters and statistics for the current cable interface from the cable interface configuration mode. ABLE ODEM ERMINATION YSTEMS Command show interface cable <c/s/i> mac show mac ADC Telecommunications, Inc.
  • Page 373 Example The following example displays the current MAC configuration and related statistics for cable interface 1/1/1: cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# show mac Insertion Interval Invited Ranging Attempts Sync Interval UCD Interval Hardware Map Timer Periodic Ranging Timer Plant Delay PLL State PLL Value Stats:...
  • Page 374: Understanding Mac Interface Statistics

    Number of multicast packets transmitted from the downstream channel. Number of broadcast packets transmitted from the downstream channel. Aggregate number of error packets transmitted from the downstream channel. Aggregate number of packets discarded on the downstream channel. ADC Telecommunications, Inc.
  • Page 375 Statistic Invalid Range Requests Ranging Aborts Invalid Registration Requests Failed Regestration Requests Invalid Data Requests T5 Timeouts Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring the MAC Interface Description Aggregate number of invalid ranging requests received on the MAC interface.
  • Page 376: Configuring Mac Interface Parameters

    1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# shared-secret 123456 cli:172.16.19.10:interface:cable:csi(1/1/1)# show shared-secret Shared Key ASCII: "4V" HEX: ODEM ERMINATION YSTEMS Command interface cable <c/s/i> shared-secret [ascii] <secret-string> show interface cable <c/s/i> shared-secret Within cable interface mode: show shared-secret "12:34:56" ADC Telecommunications, Inc.
  • Page 377 Sync Interval (millisec) The Sync Interval parameters sets the time interval between the CMTS transmission of SYNC messages. By default, the SYNC message is sent by the MAC hardware every 5 milliseconds. Acceptable values are 1 to 200 milliseconds. You set the sync interval by performing the following tasks. Task 1.
  • Page 378 You set the CMTS Ranging-attempts parameter by performing the following tasks: Task 1. Enter interface cable mode. 2. Configure the CMTS ranging attempts. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> insertion-interval <value> Command interface cable <c/s/i> ranging-attempts <value> ADC Telecommunications, Inc.
  • Page 379 Map-timer The Map-timer parameter sets the time interval between the CMTS transmission of MAP messages for each active upstream channel. Acceptable values are 1000 – 10000 microseconds. The default is 10 milliseconds. Setting this value at less than 6 milliseconds causes performance problems. Perform the following task to set the Map-timer parameter for the current cable interface.
  • Page 380 You can also verify the PLL State by performing the following task. Task 1. Enter interface cable mode. 2. Verify PLL state of the current cable interface. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> plant-delay <value> Command interface cable <c/s/i> show interface cable <c/s/i> pll-state ADC Telecommunications, Inc.
  • Page 381: Configuring The Downstream Channel

    Configuring the Downstream Channel The Downstream Channel sends data from the headend site to subscriber cable modems. Configuring the downstream channel involves setting parameters to maximize the performance of the data transfer. Downstream channel parameters are based on the modulation type for a downstream channel on the CMTS.
  • Page 382 Out Errors Out Discards cli:172.16.19.10:interface:cable:csi(1/1/1)# The Annex Type for EuroDOCSIS modules is Annex A. ODEM ERMINATION YSTEMS 1 / 1 / 2 / 2 taps32Increment4 507.0 (MHz) qam256 (MHz) (1/10 dBmV) Annex B 5360537 (baud) 629121492 14416 14134320 ADC Telecommunications, Inc.
  • Page 383: Understanding Downstream Channel Statistics

    Understanding Downstream Channel Statistics Downstream statistics are displayed as part of the show interface cable <c/s/i> downstream display as shown in the previous section. Table 18-2 provides a brief description for each MAC statistic. Table 18-2 Downstream Channel Statistics Statistic Symbol Rate Out Octets Unicast Packets...
  • Page 384: Configuring Downstream Parameters

    Perform the following tasks to set the downstream channel status. Task 1. Enter interface cable mode. 2. Set the downstream status to up. 3. Set the downstream status to down. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> downstream no shutdown downstream shutdown ADC Telecommunications, Inc.
  • Page 385 Downstream Frequency The Downstream Frequency (Hz) parameter sets the downstream signal for the RF carrier. By default, Center Frequency is set at 507 MHz. DOCSIS acceptable values are 93 MHz to 855 MHz; EuroDOCSIS acceptable values are 91.0 MHz to 858 MHz. You set the downstream center frequency by performing the following tasks.
  • Page 386 TenthdBmV. Acceptable values: 0–650. You set the downstream output transmit power level by performing the following tasks. Task 1. Enter interface cable mode. 2. Set the output transmit power level. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> downstream transmit-power <0..650> ADC Telecommunications, Inc.
  • Page 387 Downstream Modulation The Downstream modulation parameter sets the modulation rate for a downstream channel. The CMTS supports the following two modulation types. You set the downstream modulation type by performing the following tasks. Task 1. Enter interface configuration mode. 2. Configure modulation used on the downstream channel.
  • Page 388 3. Configure the EuroDOCSIS downstream interleave depth. The valid interleave depth value is: taps12Increment7 ODEM ERMINATION YSTEMS Command interface cable <c/s/i> downstream interleave-depth {8 | 16 | 32 | 64 | 128} downstream interleave-depth 12 ADC Telecommunications, Inc.
  • Page 389 Example Procedure of Downstream Configuration The following procedure steps you through the process of configuring a DOCSIS downstream channel. An example of a DOCSIS configuration follows: Task 1. View a list of CMTS interfaces that you have installed on your chassis. You can do so by using a combination BAS/UNIX command.
  • Page 390 8. Set the downstream channel power. Acceptable values: 0 – 650. 9. Verify the downstream configuration for this CMTS card. ODEM ERMINATION YSTEMS Command downstream modulation {qam64 | qam256} downstream transmit-power <value> show interface cable <c/s/i> downstream ADC Telecommunications, Inc.
  • Page 391 Configuring the Downstream Channel Example The following example shows a downstream channel configuration. Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 392: Configuring Upstream Channels

    Channel IDs range from 1 to 4 (for 1x4 modules) or from 1 to 6 (for 1x6 modules). ABLE ODEM ERMINATION YSTEMS Command show interface cable <c/s/i> upstream show upstream show interface cable <c/s/i> upstream <port number> ADC Telecommunications, Inc.
  • Page 393 Task 4. Enter this command within cable interface mode to display parameters and statistics for a specific upstream channel on the current cable interface. Example cli:172.16.19.10:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:172.16.19.10:interface:cable:csi(1/1/1)# show upstream 1 Upstream Channel Id Center Frequency Channel Width Slot Size Receive Power Modulation Profile...
  • Page 394: Configuring Upstream Channel Parameters

    Task 1. Enter interface cable mode. 2. Set the upstream channel status to up. Set the upstream channel status to down. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> no shutdown upstream <port number> shutdown ADC Telecommunications, Inc.
  • Page 395 Frequency The Frequency (MHz) parameter sets the upstream signal frequency for the RF carrier. You may choose an acceptable DOCSIS range from 5.0 - 42.0 MHz; or an acceptable EuroDOCSIS range from 5.0 - 65.0 MHz. You set the upstream channel status by performing the following tasks. Task 1.
  • Page 396 WARNING: The slot size affects the performance of the CMTS. It is recommended that configuration is done by an expert-level administrator. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> channel-width {200 | 400 | 800 | 1600 | 3200} ADC Telecommunications, Inc.
  • Page 397 You set the upstream slot size by performing the following tasks. Task 1. Enter interface cable mode. 2. Set the upstream channel mini-slot size. Receive Power The Receive Power parameter sets the level for the upstream interface in TenthdBmV. By default, the Receive Power is set at 0, which is the optimal setting for the upstream power level.
  • Page 398 Task 1. Enter interface cable mode. 2. Configure the transmit backoff range. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> modulation-profile <profile number> Command interface cable <c/s/i> upstream <port number> data-backoff <start> <end> ADC Telecommunications, Inc.
  • Page 399 Range-Backoff The Range Backoff Start parameter sets the fixed start value for range backoff on the upstream channels. By default the start value is set to 2 and the end value is set to 10. Acceptable values are 0 to 15. You set ranging backoff values on the upstream channel by performing the following task.
  • Page 400 [<port number>] upstream <port number> no shutdown (Sets the upstream channel status to up.) upstream <port number> shutdown (Sets the upstream channel status to down.) upstream <port number> data-backoff <start-number> <end-number> upstream <port number> range-backoff <start-number> <end-number> ADC Telecommunications, Inc.
  • Page 401 Task 7. Set the upstream channel frequency. Valid range: 5.0 – 42.0 MHz. 8. Set the mini-slot size for the downstream channel. 9. Set the receive power level. Acceptable range: -160 – 260 TenthdBmV. 10.Set the upstream channel width. 11.Specify the modulation profile.
  • Page 402 18: C HAPTER ONFIGURING ABLE ODEM ERMINATION YSTEMS Example The following example configures upstream channel 1 on the CMTS interface installed in slot 1. ADC Telecommunications, Inc.
  • Page 403: Upstream Channel Map Configuration

    Upstream Channel MAP Configuration You can fine tune MAP generation for upstream channels, as described in the following sections. Initial Maint Region Size (microsec) The size of the upstream channel Initial Maintenance (IM) contention region. Maps with Initial Maint regions are sent periodically. By default, Initial Maint Contention Region Size is set at 500.
  • Page 404 1. Enable interface cable mode. 2. Set maximum deferred ranging for a specific upstream channel. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> map ucd-grant-size <0..65535> Command interface cable <c/s/i> upstream <port number> map max-ranging-invitations <0..65535> ADC Telecommunications, Inc.
  • Page 405 Minimum Request Region The minimum size, in minislots, for request contention region. By default, Minimum Request Region Size is set at 20. You set maximum request contention region size for an upstream channel by performing the following tasks. Task 1. Enable interface cable mode. 2.
  • Page 406: Upstream Channel Ranging Configuration

    You set the power offset threshold for an upstream channel by performing the following tasks. Task 1. Enable interface cable mode. 2. Set the power offset threshold for the current cable interface. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> ranging power-offset-threshold <0..255> ADC Telecommunications, Inc.
  • Page 407 CM Range Invite Timeout (millisec) This is the minimum time allowed for a cable modem following receipt of a RNG-RSP, before it is expected to reply to an invitation to range request in milliseconds. By default, the CM Range Invite Timeout is set at 400 milliseconds.
  • Page 408 1. Enable interface cable mode. 2. Enable or disable zero timing adjustment. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> upstream <port number> ranging zero-power-adjust {enable | disable} Command interface cable <c/s/i> upstream <port number> ranging zero-timing-adjust {enable | disable} ADC Telecommunications, Inc.
  • Page 409 Enable Zero Frequency Adjustment If enabled, the frequency adjustment item in range response message is unconditionally set to 0. Useful for debugging. By default, Enable Zero Frequency Adjustment is disabled. Perform the following task within interface cable <c/s/i> mode to enable or disable zero frequency adjustment on an upstream channel.
  • Page 410: Configuring Admission Control

    0.0 to 100.0. The default is 75.0 percent. 5. Verify the bandwidth percentage setting. ABLE ODEM ERMINATION YSTEMS Command interface cable <c/s/i> admission-control enable show admission-control upstream <port number> voice-bw-reserve <number> show upstream <port number> ADC Telecommunications, Inc.
  • Page 411 To disable admission control on a cable interface, perform these tasks: Task 1. Access interface cable mode. 2. Disable admission control. 3. Verify that admission control is disabled. Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring Admission Control Command interface cable <c/s/i>...
  • Page 412 In Unicast Packets In Multicast Packets In Broadcast Packets In Errors In Discards --More-- ODEM ERMINATION YSTEMS Enable Enable 1 (1 / 1 / 3 / 2) 20.0 (MHz) 3200.0 (KHz) (uSec) (TenthdBmV) 65.0 2752130 8540 8468 ADC Telecommunications, Inc.
  • Page 413: Configuring Frequency Hopping

    Frequency Hopping Statistics Understanding Frequency Hopping Configuration The ADC Policy-based Frequency Hopping function continuously monitors the quality of the upstream spectrum that is in use to avoid unacceptable error rates due to noise. When the plant quality degrades to an unacceptable level, the operating parameters of the tuned upstream are adjusted based on the policy configuration.
  • Page 414: Understanding Frequency Hopping Parameters

    The upstream burst profile number to be used when error threshold is reached in configured threshold interval time. The center frequency value to be used when error threshold is reached in configured threshold interval time ADC Telecommunications, Inc.
  • Page 415 To configure frequency hopping on an upstream channel, perform the following tasks in interface:cable:csi <c/s/i> mode: Task 1. Setup a policy for an upstream channel. 2. Set the upstream burst profile number. 3. Set the percentage error threshold. 4. Set the threshold interval, in seconds.
  • Page 416 1 upstream 1 Upstream ID Rule Number Threshold Interval Frequency (MHz) Profile Num cli:192.168.208.3:interface:cable:csi(1/1/1)# ODEM ERMINATION YSTEMS Command interface cable <c/s/i> show spectrum-group upstream <port number> ADC Telecommunications, Inc.
  • Page 417 Display All Policies on All Upstream Channels You display all policies on all upstream channels by performing the following tasks: Task 1. Enter interface cable mode. 2. Display the frequency hopping policy on all upstream channels. Example cli:192.168.208.3:interface:cable:csi(1/1/1)# show spectrum-group upstream 1 row count: 3 Rule Number...
  • Page 418: Frequency Hopping Statistics

    Task 1. Enter cable interface mode. 2. Display statistics to monitor the condition of your plant. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> show spectrum-group stats upstream <port number> Command interface cable <c/s/i> show spectrum-group stats upstream ADC Telecommunications, Inc.
  • Page 419 Example This example displays statistics for all policies on all channels: cli:192.168.208.3:interface:cable:csi(1/1/1)# show spectrum-group stats upstream row count: 3 Rule Upstream Threshold Interval Freq (MHz) Profile Error Error Count Error Packet Number ID ------ -------- --------- -------- ---------- ------- ----- ----------- ------------ cli:192.168.208.3:interface:cable:csi(1/1/1)# NOTE: If you delete the current frequency hopping policy, then frequency hopping uses the next policy.
  • Page 420: Defining Modulation Profiles

    Modulation Profile configuration. Guard Time The Guard Time parameter is the number of symbol-times that must follow the end of this channel's burst. Note that this parameter is read-only. ABLE ODEM ERMINATION YSTEMS ADC Telecommunications, Inc.
  • Page 421 Mod qpsk The Mod qpsk parameter is the modulation type for an upstream channel. Acceptable values are QPSK and QAM16. You set the modulation type by performing the following tasks: Task 1. Enter cable interface mode. 2. Configure the modulation type. Pre-len Preamble pattern length.
  • Page 422 Command interface cable <c/s/i> modulation-profile <profile number> interval-usage {initial | long | request | short | station} burst-len <0..255> Command interface cable <c/s/i> modulation-profile <profile number> interval-usage {initial | long | request | short | station} diff ADC Telecommunications, Inc.
  • Page 423 Task 3. Disable the differential encoding. FEC-tbytes The Fec-tbytes parameter is the number of errored bytes that can be corrected in forward error correction code. By default, FEC-tbypes is set at zero. The value of zero indicates no correction is employed. Acceptable values are 0 to 10.
  • Page 424 <c/s/i> modulation-profile <profile number> interval-usage {initial | long | request | short | station} fec-len <1...255> Command interface cable <c/s/i> modulation-profile <profile number> interval-usage {initial | long | request | short | station} seed < 0x0000..0x7fff> ADC Telecommunications, Inc.
  • Page 425 Shortened The Shortened parameter enables the truncation of FEC codeword. You specify whether to keep the codeword fixed or enable truncation of the FEC codeword by performing the following tasks: Task 1. Enter cable interface mode. 2. Configure codeword length. Scrambler The Scrambler parameter enables or disables the scrambler.
  • Page 426: Example - Creating A Modulation Profile

    3 interval-usage short fec-tbytes 6 cli# modulation-profile 3 interval-usage short fec-len 8 cli# modulation-profile 3 interval-usage short burst-len 120 cli# modulation-profile 3 interval-usage short mod qpsk cli# modulation-profile 3 interval-usage short no scrambler ODEM ERMINATION YSTEMS ADC Telecommunications, Inc.
  • Page 427: Displaying Modulation Profiles

    cli# modulation-profile 3 interval-usage short diff cli# modulation-profile 3 interval-usage short seed cli# modulation-profile 3 interval-usage short pre-len 8 cli# modulation-profile 3 interval-usage short last-cw fixed cli# modulation-profile 3 interval-usage long fec-tbytes 6 cli# modulation-profile 3 interval-usage long fec-len 8 cli# modulation-profile 3 interval-usage long burst-len 120 cli# modulation-profile 3 interval-usage long mod qpsk cli# modulation-profile 3 interval-usage long no scrambler...
  • Page 428 4. Enter this command within cable interface configuration mode to display a specific modulation profile on the current cable interface. Example ODEM ERMINATION YSTEMS Command show interface cable <c/s/i> modulation-profile [<profile-index>] show modulation-profile [<profile-index>] ADC Telecommunications, Inc.
  • Page 429: Deleting Modulation Profiles

    Deleting Modulation Profiles You delete a modulation profile from a cable interface by performing the following tasks Task 1. Enter cable interface mode. 2. Delete the specified modulation profile. The following example deletes modulation profile 3 from interface 1/1/1: Cuda 12000 IP Access Switch CLI-based Administration Guide Defining Modulation Profiles Command interface cable <c/s/i>...
  • Page 430: Configuring Cmts Privacy Parameters

    Acceptable values are 0 to 8192. You configure the maximum flap list size by performing the following tasks: Task 1. Enter cable interface mode. 2. Set maximum flap table size. ABLE ODEM ERMINATION YSTEMS Command interface cable <c/s/i> flap-list size <value> ADC Telecommunications, Inc.
  • Page 431 Flap-list aging The Flap-list aging parameter sets the number of days to age the cable modem from the flap list table. Setting the aging threshold to zero results in modems never being aged from the table. By default, flap-list aging threshold is set at 60 days.
  • Page 432 1. Enter cable interface mode. 2. Display flap list control configuration. For more information about flap lists, see “Managing Flap Lists” on page 466. ODEM ERMINATION YSTEMS Command interface cable <c/s/i> flap-list power-adj-threshold <value> Command interface cable <c/s/i> show flap-list control ADC Telecommunications, Inc.
  • Page 433: Managing Cable Modems

    ANAGING This chapter provides information on managing cable modems. Managing cable modems consists of the tasks listed below. These tasks do not need to be performed in specific order. Viewing Cable Modems (page 432) Tracking Offline Cable Modems (page 441) Resetting Cable Modems (page 443) Changing Upstream Channels (page 447) Viewing Services (page 449)
  • Page 434: Viewing Cable Modems

    2. Enter this command from within cable interface mode to display all cable modems on the current interface. ODEMS Command show interface cable <c/s/i> modem summary show modem summary ADC Telecommunications, Inc.
  • Page 435 Viewing Cable Modems Example The following example displays the results of the show modem summary command. Refer to the next section, Displaying Detailed Listing, for explanations of the modem states. Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 436: Displaying A Detailed Listing For An Interface

    0 1:2 0 1:2 0 1:2 0 1:2 0 1:2 0 1:2 0 1:2 0 1:2 Timing Modem (dbMV) State 2216 Registered 1240 RegBpiTek 2216 Registered 2726 Registered 2212 Registered 2208 RegFailBad 2724 Ranging 2219 Registered 2724 Registered ADC Telecommunications, Inc.
  • Page 437 The display includes the following parameter information: Table 19-1 Cable Modem Display Parameters Parameter MAC Address IP Address Power (dbMV) Cuda 12000 IP Access Switch CLI-based Administration Guide Viewing Cable Modems Description The RF MAC address of this cable modem. The IP address assigned to this cable modem by DHCP.
  • Page 438 Response (success) message to the cable modem. DhcpDiscRcvd: The CMTS has received a DHCP Discover message from the cable modem. DhcpReqRcvd: The CMTS has received a DHCP Request from the cable modem. TimeReqRcvd: The CMTS has received a Time Request. ADC Telecommunications, Inc.
  • Page 439 Viewing Cable Modems Modem State (continued) TftpReqRcvd: The CMTS has received a TFTP Request from the cable modem. Registered: The cable modem is registered, without Baseline Privacy. RegNoNetAccess: The cable modem is registered, but Network Access is disabled. RegBpiKek: The cable modem is registered, with Baseline Privacy enable.
  • Page 440: Displaying Specific Cable Modems

    Example cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem 00:90:83:32:9f:8c S l o t MAC Address IP Address Power Timing Modem State ODEMS Command show interface cable <c/s/i> modem <mac-address> show modem <mac-address> 00:90:83:32:9f:8c 201.1.1.110 (dbMV) 1652 Registered ADC Telecommunications, Inc.
  • Page 441: Displaying Cable Modem Statistics

    Displaying Cable Modem Statistics To display cable modem statistics, perform the following tasks: Task 1. Enter this command from within root mode or cable interface mode to display statistics for cable modems attached to the specified interface. 2. Enter this command within cable interface mode to display statistics for cable modems attached to the current cable...
  • Page 442 00:10:95:04:0a:c3 0.0.0.0 00:10:95:04:0a:b7 201.1.1.101 00:90:96:00:39:7f 201.1.1.107 00:90:96:00:39:f9 201.1.1.105 00:10:95:04:0a:c4 201.1.1.104 00:10:95:01:ef:d8 201.1.1.106 ODEMS Vendor Pkts NonErr Name ASKEY COMPUTE ASKEY COMPUTE THOMSON CONSU THOMSON CONSU THOMSON CONSU ASKEY COMPUTE ASKEY COMPUTE THOMSON CONSU THOMSON CorrErr UnCorr 23463 ADC Telecommunications, Inc.
  • Page 443: Tracking Offline Cable Modems

    Tracking Offline Cable Modems You can control how long the CMTS tracks offline cable modems, and manage cable modem statistics when a cable modem transitions out of the offline state. Tracking offline cable modems involves: Specifying the number of days that you want the CMTS to track offline cable modems.
  • Page 444: Maintaining Statistics For Offline Cable Modems

    Task 1. Enter cable interface mode. 2. Set the CMTS to remove all offline cable modems from the summary table. ODEMS enabled Command interface cable <c/s/i> cm-offline persist no cm-offline persist Command interface cable <c/s/i> cm-offline clear ADC Telecommunications, Inc.
  • Page 445: Resetting Cable Modems

    Resetting Cable Modems The Cuda lets you reset a single modem or multiple modems attached to the same cable interface. You can specify the modem that you want to reset in terms of its IP address, MAC address, or Service Identifier (SID). Use the cm reset command within interface cable <c/s/i>...
  • Page 446: Resetting Multiple Modems

    <hex-values> match The hex values that you want to match entered with “ff” values specified as wildcards. For example, if you want to reset all cable modems from vendor 00:50:72, enter the following command: cm-reset 00:50:72:ff:ff:ff match ADC Telecommunications, Inc.
  • Page 447 Example The following example displays the modems attached to cable interface 1/1/1. The administrator uses the match argument to reset all modems with the vendor ID: 00:90:96. cli:interface:cable:csi(1/1/1)# show modem row count: 11 MAC Address IP Address ----------------- --------------- ---- ---- 00:90:96:00:29:6d 201.1.1.103 00:10:95:01:ef:d8 201.1.1.100 00:10:95:04:0a:c4 201.1.1.102...
  • Page 448: Resetting All Modems On A Network

    <address-string> match The IP address that you want to match entered with a “255” wildcard mask. For example, if you want to reset all cable modems attached to subnet 189.23.3.x, enter the following command: cm reset 189.23.3.255 match ADC Telecommunications, Inc.
  • Page 449: Changing Upstream Channels

    Changing Upstream Channels You can change the upstream channel that a cable modem is using by changing the upstream channel ID for the specified modem. To change the upstream channel, perform the following task in interface cable <c/s/i> mode. Task Modify the upstream channel ID for a select modem.
  • Page 450 0 1:2 2723 Ranging 0 1:2 2726 Registered 0 1:2 2216 Registered 0 1:2 2212 Registered 0 1:2 2727 Registered 0 1:2 2205 Registered 0 1:2 1247 Registered 0 1:2 1228 Registered 0 1:2 1652 Registered (dbMV) ADC Telecommunications, Inc.
  • Page 451: Viewing Services

    Viewing Services Services are assigned when the cable modems are provisioned. The CMTS dynamically assigns a Service ID number to the cable modem. A cable modem keeps the same Service ID for as long as it continues to range and is registered with the CMTS.
  • Page 452 The DOCSIS 1.0 class of service ID. MAC address of the cable modem to which this SID is assigned. IP address of the cable modem to which this SID is assigned. IP Address ADC Telecommunications, Inc.
  • Page 453 To view statistics for each service identifier, perform the following task in interface cable <c/s/i> mode. Task View SID statistics. Example The following example displays the results of the show sid stats command. Cuda 12000 IP Access Switch CLI-based Administration Guide Viewing Services Command show interface cable <c/s/i>...
  • Page 454 The number of packets transmitted from this cable modem The aggregate number of discard packets transmitted The number of bandwidth requests received from this cable modem. The number of bandwidth requests transmitted to this cable modem. ADC Telecommunications, Inc.
  • Page 455: Configuring Bpi And Bpi+ Parameters

    Configuring BPI and BPI+ Parameters Configuring BPI and BPI+ includes the following tasks: Configuring Authorization and Traffic Encryption Keys. This task applies to both BPI and BPI+. Configuring Trust and Validity for Manufacturer Certificates. This task applies to BPI+ only. Configuring IP Multicast Address Mapping.
  • Page 456 BPI+, the cable modem’s BPI+ security functions initialize. After successfully completing authentication and authorization with the CMTS, the cable modem sends a request to the CMTS requesting Traffic Encryption Keys (TEKs) to use with each of the SAIDs. The CMTS response contains the TEKs. ADC Telecommunications, Inc.
  • Page 457: Configuring Authorization And Traffic Encryption Keys

    Configuring Authorization and Traffic Encryption Keys You can configure and display lifetime in seconds for all new authorization and Traffic Encryption Keys (TEK), as well as for existing authorization and TEKs for a specified interface or a specified cable modem. Note that this task applies to both BPI and BPI+.
  • Page 458 43200. privacy auth <mac-address> {cm-lifetime <1..6048000> | cm-reset {invalidateAuth | invalidateTeks | sendAuthInvalid}}. The default value for cm-lifetime is 6048000. privacy tek <said> {tek-lifetime <1..6048000> | reset} The default tek-lifetime is 43200. privacy encryption {40-bit-des | 56-bit-des} ADC Telecommunications, Inc.
  • Page 459 Task 6. Display the current BPI and BPI+ base configuration, for all interfaces or for a specified interface. 7. Display the authorization key configuration and statistics for all interfaces, a specified interface, or a specified cable modem. 8. Display the TEK configuration and statistics with associated SAID for all interfaces, or a specified interface.
  • Page 460: Configuring Trust And Validity For Manufacturer Certificates

    Indicates that you want to display the certificates for the cable modems. Indicates that you want to display the certificates for the provisioned cable modem. Indicates that you want to display the BPI+ privacy authorization for the provisioned cable modem. ADC Telecommunications, Inc.
  • Page 461 Parameter filename chained root Before you configure trust and validity for certificates, you must create the /bas/data/certification directory in Linux on the Cuda 12000. Certificates will reside in this directory. To create this directory, access Linux on the Cuda 12000 through the local console or an SSH session with sufficient access privileges (such as root).
  • Page 462 [interface cable <c/s/i>] privacy cm-cert [<mac-address>] {learnt | provisioned [details]}. privacy cm-cert <mac-address> [{trusted | untrusted}] certificate <filename> no privacy cm-cert <mac-address>. privacy ca-cert <1..10000> {trusted | untrusted | chained | root} certificate <filename> no privacy ca-cert <1..10000> ADC Telecommunications, Inc.
  • Page 463: Configuring Ip Multicast Address Mapping

    Configuring IP Multicast Address Mapping You can configure and display an IP multicast address mapping entry, and set the associated multicast SAID authorization for each cable modem on each CMTS MAC interface. Configuring an IP multicast address mapping and associated SAID involves setting the following parameters: Table 19-6 Parameters for Setting and Displaying IP Multicast Address Parameter...
  • Page 464 Specifies one of the following encryption algorithms: des40cbcMode – Specifies 40-bit DES packet data encryption. des56cbcMode – Specifies 56-bit DES packet data encryption. none – Specifies no encryption. At this time, only a value of none is supported. ADC Telecommunications, Inc.
  • Page 465 You use the following commands within interface cable <c/s/i> mode to configure and display IP multicast address mapping entries: Task 1. Set the IP multicast address mapping entry and its mask for the associated SAID. 2. Remove the IP multicast address mapping entry.
  • Page 466: Viewing Privacy Keys

    Displays the algorithm used to encrypt the key. No authentication algorithm is supported at this time. Displays the lifetime of the key, in seconds. Specifies “true” if the TEK value range is reset. Otherwise, this field displays “false.” ADC Telecommunications, Inc.
  • Page 467 Sequence Number When issued with the said argument, the display shows the same information, but for the specified SAID only. When issued with the stats argument, the display shows the following statistics: Table 19-8 Privacy Statistics Statistic SAID Requests Replies Rejects Invalids Cuda 12000 IP Access Switch CLI-based Administration Guide...
  • Page 468: Managing Flap Lists

    1. Display the flap list for a specified cable interface. 1. Sort the flap-list display by flap count. 2. Sort the flap-list display by time. ODEMS Command show interface cable <c/s/i> flap-list show interface cable <c/s/i> flap-list sortbyflapcnt show interface cable <c/s/i> flap-list sortbytime ADC Telecommunications, Inc.
  • Page 469 Example The following example displays the flap list for cable interface 1/1/1: The parameters that you can display through the flap list are listed below: Table 19-9 Flap List Parameters Parameter MAC Address Flap Count Last Known State Insert Time Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Flap Lists Description...
  • Page 470 MAC layer keep alive messages. It can indicate intermittent upstream, laser clipping, or common-path distortion. Specifies the number of times the cable modem misses the MAC layer keep alive messages. It can indicate intermittent upstream, laser clipping, or common-path distortion. ADC Telecommunications, Inc.
  • Page 471: Clearing The Flap List

    Clearing the Flap List To delete all entries in the flap list table on a specific cable interface, perform the following task within interface cable <c/s/i> mode. Task Clear the flap list. Example Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Flap Lists Command flap-list clear...
  • Page 472: Managing Quality Of Service

    This section describes service flows and classifiers, and the processes for viewing the statistics and configuration associated with these QoS mechanisms. The Cuda 12000 supports QoS as defined by the Data-Over-Cable Service Interface Specifications, RFI SP-RFIv1.1-106001215. ODEMS ADC Telecommunications, Inc.
  • Page 473: Service Flows

    Service Flows A Service Flow is a QoS protocol mechanism that serves as a MAC-layer transport service and provides a unidirectional flow of packets transmitted either upstream by the cable modem or downstream by the CMTS. A Service Flow is characterized by a Service Flow ID (SFID), the service ID (SID) and a set of QoS parameters.
  • Page 474 (appears only on upstream Service Flows) real time polling service (appears only on upstream Service Flows) unsolicited grant service with AD (appears only on upstream Service Flows) unsolicited grant service (appears only on upstream Service Flows) ADC Telecommunications, Inc.
  • Page 475 Table 19-12 Parameters Contained in Upstream Service Flows Display Parameter Fragments Discarded Fragments Concatenated Bursts Table 19-13 Parameters Contained in Parameter Sets Display Parameter Cable Modem SFID Param Type Service Class Name Priority Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Quality of Service Description The Service ID for the upstream Service Flow.
  • Page 476 A value of zero indicates an infinite amount of time. Maximum concatenated burst, in bytes, for an upstream Service Flow. A value of zero indicates no maximum burst. ADC Telecommunications, Inc.
  • Page 477 Parameter Scheduling Type Nominal Polling Interval (usecs) Tolerable Poll Jitter (usecs) Unsolicited Grant Size (bytes) Nominal Grant Interval (usecs) Tolerable Grant Jitter (usecs) Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Quality of Service Description Upstream scheduling service for an upstream Service Flow.
  • Page 478 Request Policy Octets does not apply to downstream flows. Indicates the set of QoS parameters actually signaled in the DOCSIS registration or dynamic service request message that created the QoS parameter set. ADC Telecommunications, Inc.
  • Page 479 Viewing Service Flows Perform the following tasks within interface:cable:csi <c/s/i> mode to view Service Flow summaries, upstream Service Flows and Service Flow parameter sets. Views may be defined for all Service Flows, for a specified Service Flow and for a specified cable modem: Task 1.
  • Page 480 The following example displays Upstream Service Flows: interface:cable:csi(1/1/1)# show modem 00:90:83:36:82:f1 service-flow upstream Cable Modem: row count: 1 SFID -------- --------- ---------- ------------- ODEMS Time Created Class Name Scheduling 01-07-02 16:03 01-07-02 16:03 00:90:83:36:82:f1 Fragments Discarded Fragments Type undefined best effort Concatenated Bursts ADC Telecommunications, Inc.
  • Page 481 Example 3 The following example displays an Admitted parameter set for a specified Service flow: interface:cable:csi(1/1/1)# show modem 00:90:83:36:82:EE service-flow 26 parameter-set 2 Cable Modem: SFID Param Type Service Class Name Priority Max Traffic Rate Max Traffic Burst Min Reserved Rate Min Reserved Packet Active Timeout Admitted Timeout...
  • Page 482: Classifiers

    You define the matching criteria for Classifiers when you provision cable modems. For information about provisioning cable modems, refer to the Fast Flow Broadband Provisioning Manager CLI-based Administration Guide or the guide for your third-party provisioning vendor. ODEMS ADC Telecommunications, Inc.
  • Page 483 The following table describes the parameters contained in viewing Service Flow Classifiers: Table 19-14 Parameters Contained in Viewing Service Flow Classifiers Parameter SFID Direction Priority IP TOS Low IP TOS High IP TOS Mask Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Quality of Service Description The Service Flow Identifier.
  • Page 484 Specifies the high end inclusive range of TCP/UDP source port numbers to which a packet compares. Specifies the low end inclusive range of TCP/UDP destination port number to which a packet compares. ADC Telecommunications, Inc.
  • Page 485 Parameter IP Dest Port End Dest MAC Addr Dest MAC Mask Src MAC Addr Enet Protocol Type none ethertype dsap Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Quality of Service Description Specifies the low end inclusive range of TCP/UDP destination port numbers to which a packet compares.
  • Page 486 Applies to Ethernet frames using the 802.1P/Qtag header. If this parameter is a non-zero value, tagged packets must have a VLAN identifier that matches the value to match the rule. ADC Telecommunications, Inc.
  • Page 487 Parameter State Packets Bit Map Viewing Classifiers Perform the following tasks within interface:cable:csi <c/s/i> mode to view Classifiers. Views may be defined for all Service Flows, for a specified Service Flow and for a specified cable modem: Task 1. View Classifiers for all Service Flows.
  • Page 488: Service Flow Logs

    Service Flow log. The number of packets on the specified Service Flow after payload header suppression. The time the Service Flow was deleted. The time the Service Flow was created. The total time the Service Flow is active. ADC Telecommunications, Inc.
  • Page 489 Viewing and Clearing Service Flow Logs Perform the following tasks within interface:cable:csi <c/s/i> mode to view and clear Service Flow logs. NOTE: Service Flow logs are not indexed by SFID. You may choose to view and clear Service Flow logs for all Service Flows, by cable modem or by the index number of the log.
  • Page 490 Time Deleted 6 01-06-30 19:14 01-07-02 16:03 254 01-06-30 19:14 01-07-02 16:03 7 01-06-29 17:09 01-07-01 21:43 228 01-06-29 17:09 01-07-01 21:43 ec:5b:20:00:00:ee 01-06-30 19:14 01-07-02 16:03 Time Created Time Active 44:49:32 44:49:32 52:33:55 52:33:55 1045 44:49:32 ADC Telecommunications, Inc.
  • Page 491: Dynamic Service

    Dynamic Service This section describes Dynamic Service and explains the process for viewing Dynamic Service Flow Statistics. In addition to Service Flow creation at the time the cable modem registers, Dynamic Service creates Service Flows that are defined by the cable modem (CM) or the CMTS.
  • Page 492 The number of dynamic channel change request messages traversing an interface. This value is only non-zero for the downstream. The number of dynamic channel change response messages traversing an interface. This value is only non-zero for the upstream. ADC Telecommunications, Inc.
  • Page 493 Parameter DCCs DCC Fails DCC Acks View Dynamic Service Flow Statistics Perform the following tasks within interface:cable:csi <c/s/i> mode to view Dynamic Service Flow Statistics: Task Display Service Flow statistics. Cuda 12000 IP Access Switch CLI-based Administration Guide Managing Quality of Service Description The number of successful dynamic channel change transactions.
  • Page 494 DSC Requests DSC Responses DSC Acks DSD Requests DSD Responses Dynamic Adds Dynamic Add Fails Dynamic Changes Dynamic Change Fails Dynamic Deletes Dynamic Delete Fails DCC Requests DCC Responses DCC Acks DCCs DCC Fails ODEMS Outbound Inbound ADC Telecommunications, Inc.
  • Page 495: Subscriber Management

    UBSCRIBER Through Subscriber Management, the Cuda 12000 provides added security for your cable network against: Malicious tampering with the cable modem software Unwanted traffic from entering the cable network To achieve added security, the Cuda 12000 provides protocol filtering to and from the cable modem, and limits the number of IP addresses available to Customer Premise Equipment (CPE) devices.
  • Page 496: About Subscriber Management Filtering

    Cuda 12000 to that cable modem. Modifications to default filter groups on a per cable modem basis involve sending SNMP sets directly to the cable modem. The modifications do not persist, so the default filter group is not overwritten. ADC Telecommunications, Inc.
  • Page 497: About Cpe Control

    About CPE Control In addition to providing added security through filtering, Subscriber Management provides added security by limiting the number of IP addresses available to CPE devices, which minimizes the risk of malicious tampering against your cable network. Subscriber Management allows a maximum of 16 IP addresses available to CPE devices.
  • Page 498: Configuring Filter Groups

    For detail information about the IP packet filtering system, refer to Chapter 15, IP Packet Filtering beginning on page 327. The following table lists the matching criteria parameters that you configure to assign global Subscriber Management filter groups on the Cuda 12000: ADC Telecommunications, Inc.
  • Page 499 Table 20-1 Subscriber Management Global Filtering Parameters Parameter Group number Filter number Deny or Permit Source IP Address Source IP Mask Destination IP Address Destination IP Mask Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring Filter Groups Description Group number specifies the ID of the filter group to which you want the filter to belong.
  • Page 500 Any: Match any source port Number: Match a source port number to a TCP or UDP port. The allowable TCP or UDP port number range is 0 to 65536. Note that specifying 65536 is the same as specifying “Any.” ADC Telecommunications, Inc.
  • Page 501 Parameter TCP Flag TCP Mask Cuda 12000 IP Access Switch CLI-based Administration Guide Configuring Filter Groups Description Optional. The value of the TCP flags. The following is a list of the TCP flag options. Leaving this field blank indicates a null value (no flags).
  • Page 502 {deny | permit} prot {any | tcp | udp | <number>} [tcp-flag {ack | fin | push | reset | syn | urgent} tcp-flag-mask {ack | fin | push | reset | syn | ask | urgent}] ADC Telecommunications, Inc.
  • Page 503 Example The following example displays global Subscriber Management filter group 2 and index 1, which is configured to deny packets, to filter TCP packets and to use a destination IP and mask address of 144.133.1.1 255.255.255.0: cli:192.168.208.3:root# cm-filter 2 1 deny prot tcp dest 144.133.1.1 255.255.255.0 cli:192.168.208.3:root# show cm-filter 2 1 Group...
  • Page 504: Viewing Filter Groups

    3 0.0.0.0 4 0.0.0.0 1 0.0.0.0 cli:192.168.208.3:root# Command show cm-filter show cm-filter [<group number> [<filter number>]] Src Mask Dest Address 255.255.255.0 2.2.2.2 0.0.0.0 0.0.0.0 0.0.0.0 3.3.3.3 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Dest Mask 255.255.255.0 0.0.0.0 255.255.255.0 0.0.0.0 0.0.0.0 ADC Telecommunications, Inc.
  • Page 505: Deleting Filter Groups And Filters

    Deleting Filter Groups and Filters You can delete a particular Subscriber Management filter group or a filter within the group. To delete Subscriber Management filter groups and filters, perform the following tasks: Task 1. Delete a Subscriber Management filter group. 2.
  • Page 506: Modifying Existing Filter Groups

    2. Issue the show cm-filter command to identify the filter group you want to modify. 3. Perform Task 2 on page 500. 4. Complete Tasks 3 through 8 on page 500 by specifying the new source matching criteria to replace the existing criteria for the filter group. ADC Telecommunications, Inc.
  • Page 507: Assigning Default Filter Groups

    Assigning Default Filter Groups Default filter groups are used by cable modems and CPE devices on all cable interfaces, for upstream and downstream traffic. You assign four default Subscriber Management filter groups: One upstream and one downstream default filter group for cable modems.
  • Page 508 CM US Filter Group Command cm-filter-default cpe downstream <group id> cm-filter-default cpe upstream <group id> cm-filter-default cm downstream <group id> cm-filter-default cm upstream <group id> Src Mask Dest Address 255.255.255.0 2.2.2.2 255.255.255.0 205.1.1.0 Dest Mask 255.255.255.0 255.255.255.0 ADC Telecommunications, Inc.
  • Page 509: Modifying Filter Groups Per Cable Modem

    Modifying Filter Groups Per Cable Modem The Cuda 12000 allows the network administrator to temporarily modify the matching criteria of a default filter group on a per cable modem basis. A default filter group is modified when the network administrator feels it is necessary to use different matching criteria for a particular cable modem or CPE device.
  • Page 510 {<ip address> | <mac address> | <sid>} cm modify cpe-upstream <group id> {<ip address> | <mac address> | <sid>} cm modify cm-downstream <group id> {<ip address> | <mac address> | <sid>} cm modify cm-upstream <group id> {<ip address> | <mac address> | <sid>} ADC Telecommunications, Inc.
  • Page 511 Example In this example, the administrator enters interface mode for a cable interface. Then, the administrator assigns a filter group with a group number of 10 to filter upstream and downstream traffic for a cable modem with an SID of 12. cli:192.168.208.3:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem...
  • Page 512: Viewing Filter Group Assignments

    2. Display filter group assignments for all cable modems (and associated CPE devices). 3. Display filter group assignments for a specific cable modem (and associated CPE devices). Command interface:cable:csi <c/s/i> show modem cm-filter show modem <mac-address> cm-filter ADC Telecommunications, Inc.
  • Page 513 Example The following example displays filter group assignments for: All cable modems and associated CPE devices A specific cable modem and associated CPE devices cli:192.168.208.3:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem cm-filter row count: 12 MAC Address IP Address ----------------- --------------- ---------- ---------- ---------- ---------- 00:90:96:00:29:71 201.1.1.102 00:90:96:00:29:6d 201.1.1.103...
  • Page 514: Configuring Cpe Control Parameters

    CPE device. If this parameter is set to zero, the cable modem drops all CPE traffic. The allowable range is 0 to 16. Specifies whether the CMTS learns all CPE IP addresses on the current interface. By default, the CMTS learns all CPE IP addresses on current interfaces. ADC Telecommunications, Inc.
  • Page 515 To set chassis-wide Subscriber Management defaults for CPE devices, perform the following tasks: Task 1. Enter cable interface mode. 2. From any mode, specify that you do not want to disable Subscriber Management on all cable interfaces on the chassis. 3.
  • Page 516 IP addresses available to CPE devices per cable modem is set to 10, and the ability of the CMTS to learn CPE IP addresses is enabled. cli:192.168.208.3:root# cpe-control active cli:192.168.208.3:root# cpe-control max-ip 10 cli:192.168.208.3:root# cpe-control learnable cli:192.168.208.3:root# show cpe-control MAX IP Active Learnable True True ADC Telecommunications, Inc.
  • Page 517: Modifying Cpe Control Parameters Per Cable Modem

    Modifying CPE Control Parameters Per Cable Modem The Cuda 12000 allows the network administrator to modify Subscriber Management CPE control per cable modem. Modifications on a per-cable- modem basis are not persisted on the Route Server, and are sent in the form of SNMP sets directly to the cable modem.
  • Page 518 {<ip address> | <mac address> | <sid>} cm modify max-ip <0..16> {<ip address> | <mac address> | <sid>} cm modify learnable {<ip address> | <mac address> | <sid>} no cm modify learnable {<ip address> | <mac address> | <sid>} show modem cpe-control ADC Telecommunications, Inc.
  • Page 519 Example In this example, the administrator restricts CPE devices that use a specific cable modem (201.1.1.101) to access the network to five IP addresses. cli:192.168.208.3:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem row count: 12 MAC Address IP Address ----------------- --------------- ---- ---- --- --- ------ ------ ---------- 00:90:96:00:29:71 201.1.1.102 00:90:96:00:29:6d 201.1.1.103 00:10:95:01:f0:05 201.1.1.100...
  • Page 520: Viewing Cpe Control Parameters And Cpe Devices

    3. From interface:cable:csi<c/s/i> mode, view CPE control parameters for a specific cable modem using the interface (specify the cable modem’s MAC address). Command show cpe-control show modem cpe-control show modem <mac-address> cpe-control ADC Telecommunications, Inc.
  • Page 521 Example In this example, the administrator displays default CPE control parameters and then displays CPE control parameters for all cable modems on a specific interface. cli:192.168.208.3:root# show cpe-control MAX IP Active Learnable cli:192.168.208.3:root# interface 1/1/1 mode: interface:cable:csi(1/1/1) cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem cpe-control row count: 12 MAC Address IP Address...
  • Page 522: Viewing Cpe Devices

    00:90:83:36:82:f1 cpe-hosts MAC Address IP Address row count: 1 CPE IP Address ---------------- ----------------- ----------- 201.1.2.100 Command interface <c/s/i> show modem cpe-hosts show modem <mac-address> cpe-hosts 00:90:83:36:82:f1 201.1.1.111 CPE MAC Address Source 00:b0:d0:72:b2:93 Learned ADC Telecommunications, Inc.
  • Page 523: Mib Browsing

    MIB B ROWSING The Cuda 12000 supports MIB browsing of cable modems and embedded Multimedia Terminal Adapters (MTAs). This chapter provides information on how to browse cable modem and MTA MIBs, and the MIB objects that are returned. The cable modem and MTA MIB tables are in compliance with DOCSIS Operations Support System Interface Specification SP-OSSIv1.1-103-001220;...
  • Page 524: Cable Modem Mibs

    Describes the basic- and authorization- related Baseline Privacy Plus attributes of each cable modem MAC interface. Describes the attributes of each CM Traffic Encryption Key (TEK) association for BPI Plus. Provides system identification, such as, contact name, device name and location. ADC Telecommunications, Inc.
  • Page 525 MIB Table subset of ifTable & ifXTable docsDevBaseGroup, docsDevSoftwareGroup, docsDevServerGroup docsDevEvControl Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem MIBs Description Provides status information and statistics on interface activity. Provides objects needed for cable device system management. Provides control and logging for event reporting, and contains the following MIB tables: docsDevEvSyslog...
  • Page 526: Mta Mibs

    Provides the public key certificates and other security-related information for the MTA device. Contains information regarding Display Network Call Signaling (NCS). NCS displays include values for the following parameters. Service-level Configuration CODEC Conversion Types End Point IDs ADC Telecommunications, Inc.
  • Page 527: Browsing Cable Modem And Mta Status

    Browsing Cable Modem and MTA Status The Cuda 12000 supports the retrieval and display of status information that is maintained by individual cable modems and MTAs connected to the HFC network. This information is useful when you have to monitor the network and troubleshoot network problems.
  • Page 528 Table 21-22 on page 556. MTA Security (pktcMtaDevSecurityTable). Refer to . MTA Signalling Configuration (pktcSigDevConfigObjects). Refer to Table 21-23 on page 557. MTA Codec (pktcSigDevCodecTable). Refer to Table 21-24 on page 557. (pktcSigEndPntConfigTable). Refer to Table 21-25 on page 558. ADC Telecommunications, Inc.
  • Page 529 For example, to display cable modem device status, you would issue the following command: cli:192.168.208.3:interface:cable:csi(1/1/1)# show modem 00:90:83:57:52:5b cm downstream S l o t MAC Address IP Address docsIfDownChannelId docsIfDownChannelFrequency docsIfDownChannelWidth docsIfDownChannelModulatio docsIfDownChannelInterleav docsIfDownChannelPower docsIfDownChannelAnnex The corresponding output from the cable modem’s MIB would be: snmptalk@172.30.1.13>...
  • Page 530: Cable Modem And Mta Command Output Descriptions

    Number of attempts to transmit data PDUs containing requests for acknowledgement that did not result in acknowledgement. to excessive retries without acknowledgement. Number of attempts to transmit bandwidth requests that did not result in acknowledgement. ADC Telecommunications, Inc.
  • Page 531 CLI Output docsIfCmServiceRqExceededs Number of requests for bandwidth that failed Table 21-6 docsIfCmStatusTable Parameters CLI Output docsIfCmServiceStatusValue docsIfCmServiceStatusCode docsIfCmServiceTxPower docsIfCmServiceResets docsIfCmServiceLostSyncs docsIfCmServiceInvalidMaps docsIfCmServiceInvalidUcds docsIfCmServiceInvalidRangi docsIfCmServiceInvalidRegis docsIfCmServiceT1Timeouts docsIfCmServiceT2Timeouts docsIfCmServiceT3Timeouts docsIfCmServiceT4Timeouts docsIfCmServiceRangingAbort Number of times the ranging process was Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description due to excessive retries without...
  • Page 532 If the interface is down, the value is either the value configured at the CMTS, the most current value from the cable modem, or a value of zero. MIB browsing for this field is not supported in this release. ADC Telecommunications, Inc.
  • Page 533 Table 21-8 docsIfUpstreamChannelTable Parameters CLI Output docsIfUpChannelId docsIfUpChannelFrequency docsIfUpChannelWidth docsIfDownChannelModulation Profile docsIfUpChannelSlotSize docsIfUpChannelTxTimingOffset docsIfUpChannelRangingBackoff Start docsIfUpChannelRangingBackoff docsIfUpChannelTxBackoffStart Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description CMTS identification of the upstream channel within this particular MAC interface. If the interface is down, the most current value displays.
  • Page 534 At the CMTS, this is the average signal/noise of the upstream channel. At the cable modem, this value indicates the equalization data for the downstream channel. At the CMTS, this value indicates the average equalization data for the upstream channel. ADC Telecommunications, Inc.
  • Page 535 Table 21-10 docsIfQosProfileTable Parameters CLI Output docsIfQosProfPriority docsIfQosProfMaxUpBandwidth docsIfQosProfGuarUpBandwidth docsIfQosProfMaxDownBandwidth Maximum downstream bandwidth, in docsIfQosProfMaxTxBurst docsIfQosProfBaselinePrivacy docsIfQosProfStatus Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Relative priority assigned to this service when allocating bandwidth. Zero indicates lowest priority, and seven indicates the highest priority.
  • Page 536 (an Authorization Invalid message from the CMTS) that its authorization was no longer valid. The cable modem sent an Authorization Request message to the CMTS and is waiting for a response. ADC Telecommunications, Inc.
  • Page 537 CLI Output docsBpiCmAuthKeySequence Number docsBpiCmAuthExpires docsBpiCmAuthReset The options are: docsBpiCmAuthGraceTime docsBpiCmTEKGraceTime docsBpiCmAuthWaitTimeout docsBpiCmReauthWaitTimeout Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Auth Reject Wait The cable modem received an Authorization Reject message in response to its last Authorization Request.
  • Page 538 Authorization Reject in response to an Authorization Request with an error code of 2 (unauthorized SAID). The display string in the most recent authorization reject message the cable modem receives since reboot. If no authorization has been received, this value is zero. ADC Telecommunications, Inc.
  • Page 539 CLI Output docsBpiCmAuthInvalidErrorCode docsBpiCmAuthInvalidErrorString Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Enumerated description of the error code in the most recent authorization invalid message that the cable modem receives. none No authorization invalid messages have been received since reboot.
  • Page 540 FSM. Enumerated description of the error-code in most recent key reject message received by the cable modem. No key reject message has been received since reboot. Last error-code was zero. SID was unauthorized. ADC Telecommunications, Inc.
  • Page 541 CLI Output docsBpiCmTEKKeyRejectErro rCode docsBpiCmTEKKeyRejectErro rString docsBpiCmTEKInvalidErrorC docsBpiCmTEKInvalidErrorSt ring Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Display string in the most recent key reject message received by the cable modem. This displays a zero length string if no key reject message has been received since reboot.
  • Page 542 (an Authorization Invalid message from the CMTS) that its authorization was no longer valid. The cable modem sent an Authorization Request message to the CMTS and is waiting for a response. ADC Telecommunications, Inc.
  • Page 543 CLI Output docsBpi2CmAuthKeySequence Number docsBpi2CmAuthExpiresOld docsBpi2CmAuthExpiresNew docsBpi2CmAuthReset The options are: docsBpi2CmAuthGraceTime Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Auth Reject Wait The cable modem received an Authorization Reject message in response to its last Authorization Request.
  • Page 544 Enumerated description of the error code in the most recent authorization reject message the cable modem receives. none No authorization reject messages have been received since reboot. unknown Last error code value was zero. ADC Telecommunications, Inc.
  • Page 545 CLI Output docsBpi2CmAuthRejectErrorString docsBpi2CmAuthInvalidErrorCode Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description unauthorized cm The cable modem received an Authorization Reject in response to an Authorization Request with an error code of 1 (unauthorized cable modem). unauthorized The cable modem received an SAID...
  • Page 546 CMTS and cable modem have lost authorization key synchronization. unsolicited Unsolicited. invalidkey Invalid key sequence number. sequence keyRequest Message (key request) authentication Authentication failure. Failure Display string in most recent Authorization Invalid message received by the cable modem. ADC Telecommunications, Inc.
  • Page 547 Table 21-14 docsBpi2CmTEKTable CLI Output docsBpi2CmTEKSAType docsBpi2CmTEKData EncryptAlg docsBpi2CmTEKData AuthentAlg docsBpi2CmTEKState Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Type of security association. The options are: none primary static dynamic Data encryption algorithm being used. The options are: none des56cbcmode...
  • Page 548 Enumerated description of the error code in the modem recent TEK invalid message reviewed by the cable modem. No TEK invalid message has been received since reboot. Last error code was zero. Invalid key sequence. ADC Telecommunications, Inc.
  • Page 549 CLI Output docsBpi2CmTEKInvalidError String Table 21-15 systemGroup Parameters CLI Output Descriptor Contact Name Location Table 21-16 docsDevBase, docsDevSoftware, and docsDevServer Parameters CLI Output Serial Number STP Control stEnabled noStFilter Bpdu noStPass Bpdu SW Server SW Filename Admin Status Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Display string in the most recent TEK invalid...
  • Page 550 A DHCP Discover has been transmitted and no offer has yet been received. A DHCP Request has been transmitted and no response has yet been received. A Time Request has been transmitted and no response has yet been received. ADC Telecommunications, Inc.
  • Page 551 CLI Output WaitingFor Tftp RefusedBy Cmts Forwarding Denied Other Unknown DHCP Server Time Server TFTP Server Server Config File Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description A request to the TFTP parameter server has been made and no response has been received.
  • Page 552 Causes the suppression of all trap transmission and syslog messages. Indicates whether the trap and syslog transmission is inhibited because of thresholds or the current settings of the Throttle Admin parameter. ADC Telecommunications, Inc.
  • Page 553 Table 21-18 docsDevEventTable Parameters CLI Output First Time Last Time Counts Level Text Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Creation time for the entry. If multiple events are reported through the same entry, the time that the last event for this entry occurred.
  • Page 554 Determines how the event notification is sent. The options are: local: The event logs to the internal log. trap: The event logs generates a trap. syslog: A syslog message is sent. ADC Telecommunications, Inc.
  • Page 555 Table 21-20 ifTable and IfXTable Parameters and Statistics CLI Output Description Type Admin Status Oper Status The options are: down testing unknown dormant In Octets In Unicast Packets In Multicast Packets Number of packets, delivered by this sub layer to a higher In Broadcast Packets In Errors...
  • Page 556 Number of outbound packets that could not be transmitted because of errors. Number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. ADC Telecommunications, Inc.
  • Page 557 Table 21-21 pktcMtaDevBaseTable Parameters CLI Output Serial Number Hardware Version MAC Address Fully Qualified Domain Name End Points Voice Enabled Type ID Provisioned State HTTP Access Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Manufacturer’s serial number for this MTA.
  • Page 558 This is a value of null is the server address is unknown. IP address or FQDN of the SNMP entity for provisioning trap handling that assigned an IP address to this device. This value is 0.0.0.0 if DHCP was not used for IP address assignment. ADC Telecommunications, Inc.
  • Page 559 Table 21-23 pktcSigEndPntConfigTable Parameters CLI Output Call Agent ID Call Agent UDP Port Table 21-24 pktcSigDevCodecTable Parameters CLI Output Index Type Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description The call agent name. The call agent name can be a FQDN or an IP address.
  • Page 560 (signals for setting up calls) in the IP header. Displays the default Type of Service (TOS) value for media stream packets in the IP header. Audio and video streams are examples of media streams. ADC Telecommunications, Inc.
  • Page 561 CLI Output TOS Format Selector Cuda 12000 IP Access Switch CLI-based Administration Guide Cable Modem and MTA Command Output Descriptions Description Displays one of the following formats for the default call signalling and media stream TOS values: dscpCodepoint – Specifies that the TOS field is treated as a Differentiated Service Code Point (DSCP).
  • Page 562 21: MIB B HAPTER ROWSING ADC Telecommunications, Inc.
  • Page 563: Command Summary

    OMMAND This chapter provides a summary of all Cuda 12000 CLI-based administration commands categorized by primary function. Note that the no and show forms of the commands are not included. The following command functions are listed in this chapter: Access Control Commands (page 562) Mode Commands (page 563) General Commands (page 564) IP Administration and Route Filtering Commands (page 565)
  • Page 564: Access Control Commands

    Used to log into the CLI environment. Exits out of the Cuda 12000 CLI environment. root Specifies a RADIUS authentication server. Changes the password of the current account. root Sets the IP address and encryption key of the TACACS+ authentication server. ADC Telecommunications, Inc.
  • Page 565: Mode Commands

    Mode Commands Table A-2 Mode Commands Command interface <c/s/i> ip address <ip-address> <mask> prov-server root router router ospf router rip slot <c/s> Cuda 12000 IP Access Switch CLI-based Administration Guide Mode Commands Mode Description Enters configuration mode for a selected interface. interface <c/s/i>...
  • Page 566: General Commands

    Sets the system time. Sets the timeout for idle CLI sessions. interface:<type>:csi Disables a specified interface. Enables sending of broadcast messages to users. This command also allows you to send a broadcast message. ADC Telecommunications, Inc.
  • Page 567: Ip Administration And Route Filtering Commands

    IP Administration and Route Filtering Commands Table A-4 IP Administration and Route Filtering Commands Command access-class <list number> {in | out} priority <priority number> access-list <list number> {deny | permit} <rule number> ip {<source ip address> <source IP mask> | host <ip address>...
  • Page 568 Adds a source routing entry on the current interface to ensure local destinations are used first should no default root exist for the network. router:ospf:import Adds a route-map to a specified map-list for creation of RIP and router:ospf:export OSPF route filters. router:rip:import router:rip:export ADC Telecommunications, Inc.
  • Page 569 Command match {ip-address <ip-address> <mask> | neighbor <ip-address> <mask> |tag <tag-value> [exact | exclude]} override {metric <metric-value> | tag <tag-value> ping [-l <size>] [-n <count>] [-w <timeout>] [-s <src-ip-address>] <dest-ip-address> proxy-arp route-map <map-tag> {permit | deny} traceroute [-w <timeout>] [-i <number>] [-m <number>] [-p <number>][-q <number>] [-t <number>] [-s <src-ip-address>]...
  • Page 570: Rip Commands

    <ip address> interface:<type>:csi Configures the version of RIP the <c/s/i>:ip-address current IP interface uses to receive <ip address> routes. interface:<type>:csi Configures the interface to <c/s/i>:ip-address advertise the default route in <ip address> addition to other routes. ADC Telecommunications, Inc.
  • Page 571 Command ip rip send default-only ip rip send-version {1 | 2 |1 2| none} ip rip split-horizon reset rip stats router rip Cuda 12000 IP Access Switch CLI-based Administration Guide Mode Description interface:<type>:csi Configures the interface to <c/s/i>:ip-address advertise only the Cuda 12000’s <ip address>...
  • Page 572: Ospf Commands

    Sets the Link State Advertisement <c/s/i>:ip-address (LSA) retransmit interval in seconds <ip address> for the current IP interface. interface:<type>:csi Sets the number of seconds it <c/s/i>:ip-address takes to transmit a link state <ip address> update packet on the current IP interface. ADC Telecommunications, Inc.
  • Page 573 Command ospf area <area-id> <area id> [authentication {md5 | password}] [[stub [no-summary]] [default-cost <cost>] [range <ip-address> <mask> [advertise-matching]] [{enable | disable}] ospf-vi <transit-area-id> <neighbor-router-id> ospf-vi <transit-area-id> <neighbor-router-id> authentication {md5 | password} ospf-vi <transit-area-id> <neighbor-router-id> authentication {key-id <id> key <key> | key <key>} ospf-vi <transit-area-id>...
  • Page 574: Dhcp Relay Commands

    Configures DHCP policies on the current interface. DHCP policies dictate the servers to which DHCP requests are forwarded. interface:cable:csi Configure DHCP relay options on the current cable interface. Note that you configure the DHCP relay server using the dhcp-policy command. ADC Telecommunications, Inc.
  • Page 575: Cable Interface Administration Commands

    Cable Interface Administration Commands Table A-8 Cable Interface Administration Commands Command admission-control {enable | disable} cm modify upstream <new-upstream-channel> {<ip-address> | <mac-address> | <sid>} downstream frequency <freq-number> downstream interleave-depth <number> downstream modulation {qam64 | qam256} downstream no shutdown downstream shutdown downstream transmit-power <number>...
  • Page 576 Creates a cable modulation profile. interface:cable:csi Specifies how often this cable interface periodically invites modems to range. interface:cable:csi Specifies the estimated plant propagation delay, in microseconds. interface:cable:csi Sets the phase lock loop state (PLL) for the current cable interface. ADC Telecommunications, Inc.
  • Page 577 Command qos permission modems ranging-attempts <value> shared-secret [ascii] <string> sync-interval <value> ucd-interval <value> upstream <port number> channel-width {200 | 400| 800 | 1600 | 3200} upstream <port number> data-backoff <start value> <end value> upstream <port number> frequency <value> upstream <port number> map {init-maint-size-adjust <value>...
  • Page 578 Sets the channel status for the specified upstream port to down. interface:cable:csi Reserves a percentage of upstream bandwidth for voice traffic on the current interface. ADC Telecommunications, Inc.
  • Page 579: Cable Modem And Subscriber Administration Commands

    Cable Modem and Subscriber Administration Commands Table A-9 Cable Modem and Subscriber Administration Commands Command clear service-flow log <all> cm-filter <group-number> <filter-number> {deny | permit} prot {any | tcp | udp | <number>} [src <ip-address> <mask>] [dest <ip-address> <mask>] [tos <tos-value>...
  • Page 580 Sets the lifetime in seconds that the CMTS assigns to an authorization key for a specified cable modem. interface:cable:csi Sets the lifetime in seconds that the CMTS assigns to a new authorization key. ADC Telecommunications, Inc.
  • Page 581 Command privacy base cert-trust {trusted | untrusted} privacy base enable-cert-validity-periods {true | false} privacy base tek-lifetime <0..6048000> privacy ca-cert <number> [{trusted | untrusted | chained | root}] certificate <filename> privacy cm-cert <mac> [{trusted | untrusted}] certificate <filename> privacy encryption {40-bit-des | 56-bit-des} privacy multicast ip <index>...
  • Page 582: Network-Layer Bridge Commands

    Network interface:cable:csi layer bridging is especially useful in spanning a single subnet across multiple modules. interface:bridge-group Adds an interface to the current bridge group. interface:bridge-group Configures aging and reply timers for bridge group interface:cable:csi broadcast flows. ADC Telecommunications, Inc.
  • Page 583: Fault Management Commands

    Fault Management Commands Table A-11 Fault Management Commands Command alarm-throttle {alarms <number> | interval <number> | default} aux-device ac-monitor <args> aux-device db15 alarm <args> aux-device dc-monitor <args> aux-device fan-rotation <args> aux-device fan-temp <args> aux-device ps-temp <args> basmonitor chassis-fault [backplane] [backplane-power] [backplane-power-a] [backplane-power-b] [backplane-temp] [bits-a] [bits-b]...
  • Page 584: Chassis Commands

    Assigns the selected chassis to a cluster. root Configures the management module as a primary or secondary manager. root Defines the management scope. root Connects you to another Cuda 12000. root Validates provisioning database access information. root Configures provisioning information. ADC Telecommunications, Inc.
  • Page 585 Command http-server {enable | disable} lookup {enable | disable} reset [{hard | soft}] save traffic-relay {dns | ftp | http | snmp | snmp-trap | ssh | syslog | telnet | tftp | time_of_day} [port <port>] Cuda 12000 IP Access Switch CLI-based Administration Guide Mode Description root...
  • Page 586: Snmp Commands

    Creates an SNMP group. root Creates an SNMP host to receive trap messages. root Specifies the physical location of the Cuda 12000. root Specifies the system name. root Creates an SNMPv3 user for the SNMP entity. ADC Telecommunications, Inc.
  • Page 587 Command snmp-server view <view-name> <oid-tree> {included | excluded} [storage {volatile | nonvolatile | permanent | readonly}] [status {enable | disable}] Packet Over SONET (POS) Commands Table A-14 POS Commands Command clear counters clock-source {line | internal} crc {16 | 32} loop {line | internal} mtu <value>...
  • Page 588 Enables the interface to negotiate the authentication protocol to use. It will try first to agree on PAP authentication. interface:pos:csi Configures the username with which the POS interface responds to Challenge Handshake Protocol (CHAP) challenges. ADC Telecommunications, Inc.
  • Page 589 Command ppp chap-password <password> ppp ipcp-report-address ppp negotiation-count <0...100> ppp pap-sent-username <name> password <password> ppp username <name> password <password> timeout <0 ... 65535> Cuda 12000 IP Access Switch CLI-based Administration Guide Packet Over SONET (POS) Commands Mode Description interface:pos:csi Configures the password with which the POS interface responds to Challenge Handshake Protocol (CHAP) challenges.
  • Page 590: Ethernet Commands

    {auto | full | half} negotiation auto speed {auto | 10 | 100} Mode Description interface:ethernet:csi Sets duplex mode. interface:ethernet:csi Configures an Ethernet port to automatically negotiate duplex mode and speed. interface:ethernet:csi Sets the speed on an Ethernet port. ADC Telecommunications, Inc.
  • Page 591 ONFIGURING ROVISIONING A DHCP server is required for cable modems, MTAs, and CPE devices to boot and receive their IP configuration information — such as IP address and host options. DHCP servers fall into two categories: External — DHCP servers that reside on systems other than your local Cuda 12000 (that is, the Cuda 12000 that has the cable interface that you are configuring).
  • Page 592 DHCP requests. ROVISIONING ERVERS Command prov-server ps-config serverstate disable show ps-config | include ServerState Note that command strings are case-sensitive. interface <c/s/i> show dhcp-policy default dhcp-policy default permit forward-internal disable dhcp-policy default permit <ip address> ADC Telecommunications, Inc.
  • Page 593 Task 8. Verify the new DHCP server configuration. Example The following example disables the Cuda 12000 internal FastFlow Broadband Provisioning Manager DHCP server and configures the cable interface to forward DHCP requests to an external DHCP server at 192.168.23.26. cli:192.168.208.3:interface:cable:csi(1/1/1)# prov-server mode: prov-server cli:192.168.208.3:prov-server# ps-config serverstate disable cli:192.168.208.3:prov-server# show ps-config | include ServerState...
  • Page 594 B: C PPENDIX ONFIGURING XTERNAL ROVISIONING ERVERS ADC Telecommunications, Inc.
  • Page 595 LOSSARY 16 QAM Modulation mode used by the CMTS. QAM uses both amplitude and phase modulation to encode multiple bits of data in one signaling element, thus achieving higher data transfer rates than just amplitude or phase modulation alone. 16 QAM encodes four bits per symbol as one of sixteen possible amplitude and phase combinations.
  • Page 596 A modulator-demodulator at subscriber locations intended for use in (CM) conveying data communications on a cable television system. Cable Modem A device located at the cable system head-end or distribution hub, that Termination interfaces the HFC network to local or remote IP networks. System (CMTS) ADC Telecommunications, Inc.
  • Page 597 Cable Modem The interface, defined in [DOCSIS3], between a CMTS and the equipment on Termination its network side. System - Network Side Interface (CMTS-NSI) Cable Modem to The interface, defined in [DOCSIS4], between a CM and CPE. CPE Interface (CMCI) Carrier Hum The peak-to-peak magnitude of the amplitude distortion relative to the RF Modulation...
  • Page 598 In the U.S., reverse path signals come to the head-end from 5 to 42 MHz. Forward path signals go from the head-end from 50 or 54 MHz to the upper frequency limit. FDDI See Fiber Distributed Data Interface. See Forward Error Correction. ADC Telecommunications, Inc.
  • Page 599 Feeder Cable Coaxial cables that run along streets within the served area and connect between the individual taps which serve the customer drops. Fiber Node The interface between a fiber trunk and the coaxial distribution. Fiber nodes are located in a subscribers neighborhood. File Transfer A protocol that allows users to log into a remote system, identify themselves, Protocol (FTP)
  • Page 600 ICMP See Internet Control Message Protocol. IEEE See Institute of Electrical and Electronic Engineers. IETF See Internet Engineering Task Force. IGMP See Internet Group Management Protocol. Impulse Noise Noise characterized by non-overlapping transient disturbances. ADC Telecommunications, Inc.
  • Page 601 Incremental A method of spacing NTSC television channels on a cable television system in Related Carriers which all channels except 5 and 6 correspond to the standard channel plan, (IRC) used to reduce composite triple beat distortions. Information The fields that make up a MAP and define individual grants, deferred grants, Element etc.
  • Page 602 See International Telecommunications Union. Java A high level programming language developed by Sun Microsystems. See Local Area Network. Latency The time delay, expressed in quantity of symbols, taken for a signal element to pass through a device. ADC Telecommunications, Inc.
  • Page 603 Layer A subdivision of the Open System Interconnection (OSI) architecture, constituted by subsystems of the same rank. LDAP See Lightweight Directory Access Protocol. Lightweight A set of protocols for accessing information directories. LDAP is based on the Directory Access standards contained within the X.500 standard, but is significantly simpler. Protocol (LDAP) And unlike X.500, LDAP supports TCP/IP, which is necessary for any type of Internet access to a directory server.
  • Page 604 Network line needed for Voice Over IP. (MTA) Multipoint Access User access in which more than one terminal equipment is supported by a single network termination. Multipoint A connection among more than two data network terminations. Connection ADC Telecommunications, Inc.
  • Page 605 National Cable A voluntary association of cable television operators which, among other Television things, provides guidance on measurements and objectives for cable Association (NCTA) television systems in the United States. National Television A committee which developed a set of standard protocol for television Systems broadcast transmission and reception in the United States.
  • Page 606 Radio Frequency Signals that are used by the CMTS transmitter and receiver to send data over (RF) HFC network. A radio frequency carrier is modulated to encode the digital data stream for transmission across the cable network. ADC Telecommunications, Inc.
  • Page 607 Request For A technical policy document of the IETF; these documents can be accessed Comments (RFC) on the World Wide Web at http://ds.internic.net/ds/rfcindex.html. Return Loss The parameter describing the attenuation of a guided wave signal (e.g., via a coaxial cable) returned to a source by a device or medium resulting from reflections of the signal generated by the source.
  • Page 608 A reliable stream service which operates at the transport-layer Internet Control Protocol protocol which ensures successful end-to-end delivery of data packets (TCP) without error. Transmission A sublayer of the Physical Layer that provides an interface between the Data Convergence Link Layer and the PMD Sublayer. Sublayer ADC Telecommunications, Inc.
  • Page 609 Transmission The material on which information signals may be carried; e.g., optical fiber, Medium coaxial cable, and twisted-wirepairs. Transport Stream In MPEG-2, a packet-based method of multiplexing one or more digital video and audio streams having one or more independent time bases into a single stream.
  • Page 610 The range of the radio spectrum is the band extending from 30 MHz to 300 Frequency (VHF) MHz. The wavelengths corresponding to these limit frequencies are 10 meters and 1 meter. Video Graphics Array display system. See Very High Frequency. ADC Telecommunications, Inc.
  • Page 611 NDEX access classes displaying 338 removing access lists 339 access lists applying to interfaces 336 creating 331 deleting 335 displaying 335 understanding 330 address resolution protocol (ARP) adding entries 286 clearing cache 289 configuring the timeout 288 deleting entries 287 displaying cache 285 IP address 284 MAC address 284...
  • Page 612 NDEX modulation type 385 configuring MAC interface parameters hardware MAP timer 377 insertion interval 376 invited ranging attempts 376 periodic ranging timer 377 phase-locked loops (PLL) state 378 plant propagation delay 378 shared secret 374 sync interval 375 UCD interval 375 configuring upstream channel MAP initial maintenance region size 401 maximum deferred ranging invitations 402...
  • Page 613 global commands 42 IP interface 50 OSPF global configuration 51 physical interface 46 RIP configuration 54 root 44 slot 56 commands access control 562 cable interface administration 573 cable modem administration 577 cable modem configuration 577 chassis 582 DHCP server administration 580 DHCP subnet administration 580 general 564 IP administration and route filtering 565...
  • Page 614 NDEX example 206 configuring the syslog server 205 displaying event transmission, reporting, and syslog parameters 216 example 217 displaying the event log 218 example 219 removing SNMP trap recipients commands 207 example 207 fan tray alarms configuring assertion levels 150 fault reporting 153 fan unit assertion levels 152 fault management...
  • Page 615 access classes displaying 338 removing access lists 339 access lists applying 336 creating IP access list 332 creating TCP access list 332 creating UDP access list 333 deleting 335 displaying 335 understanding 330 considerations 340 disable 329 enable 329 example 341 IP source routing about 321 next hop gateway 321...
  • Page 616 NDEX network structure Packet Over SONET (POS) 116 SONET 117 network-layer bridging about 344 assigning IP addresses 351 bridge groups adding interfaces 349 creating 347 removing 350 creating 345 open shortest path first (OSPF) configuring interfaces authentication 310 cost 308 dead-interval 308 hello interval 308 interface priority 309...
  • Page 617 LCP 144 security 138 server-side security parameters 141 enabling NCP 146 frame check sequence (FCS) size 144 initial maximum transmit/receive unit (MTU) 144 max negotiation attempts 145 parameters 144 time between negotiation attempts 145 policies frequency 412 interval 412 profile 412 power and fan tray alarms configuring assertion levels 150...
  • Page 618 NDEX commands 193 description 182 example 194 list of system events 183 parameters 187 SNMP groups commands 169 example 170 parameters 168 SNMP hosts example 194 SNMP network system identification commands 180 example 180 parameters 180 SNMP security models 162 SNMPv3 contexts commands 179 example 179...
  • Page 619 cable modem termination systems (CMTS) 369 upstream parameters configuring channel status 392 channel width 393 frequency 393 modulation profile 396 ranging backoff start 397 receive power 395 slot size 394 tx backoff start 396 upstream statistics displaying 390 user manager about user manager 57 access privileges 58 access profiles 58...
  • Page 620 NDEX...

This manual is also suitable for:

Cuda 12000

Table of Contents