plik

4401 Great America Parkway

8 Federal Street

Santa Clara, CA 95054

Billerica, MA 01821

2131-0120 Rev 00

The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users
must take full responsibility for their applications of any products specified in this document. The information in this document is
proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that
license. A summary of the Software License is included in this document.

Trademarks

Microsoft, Microsoft Access, MS-DOS, Windows 95, and Windows NT are registered trademarks of Microsoft Corporation.

All other trademarks and registered trademarks are the property of their respective owners.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the
Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the
United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer
Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes
to the products described in this document without notice.

Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s)
described herein.

Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this
paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such
distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of
the University may not be used to endorse or promote products derived from such portions of the software without specific prior written
permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on
use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).

Federal Communications Commission (FCC) Compliance Notice: Radio Frequency Notice

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

•

This device may not cause harmful interference.

•

This device must accept any interference received, including interference that may cause undesired operation.

Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment
generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause
harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If
this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and
on, the user is encouraged to try to correct the interference by one or more of the following measures:

•

Reorient or relocate the receiving antenna.

•

Increase the separation between the equipment and receiver.

•

Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

•

Consult the dealer or an experienced radio/TV technician for help.

2131-0120 Rev 00

Notice: For equipment using loopstart lines, please note that the Ringer Equivalence Number (REN) assigned to each terminal device
provides an indication of the maximum number of terminals allowed to be connected to a telephone interface. The termination on an
interface may consist of any combination of devices subject only to the requirement that the sum of the Ringer Equivalence Numbers of all
the devices does not exceed 5. The REN is located on the “FCC Rules Part 68” label located on the bracket of the module, or on the back
of the unit.

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or installing the hardware unit
with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE,
YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS
AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If
you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase
to obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal, nonexclusive,
nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authorized device identified by host
ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in support of authorized use of the Software;
and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to
the Software only and does not extend to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent
software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws. Bay Networks and/or
its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Bay Networks or its
licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee
may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative
works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may
not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its
licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to any third party
the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is
confidential to Bay Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, and agents to
use the Software at Licensee’s facility, provided they have agreed to use the Software only in accordance with the terms of this license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Networks and properly installed and operated
on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user
manual during its warranty period, which begins on the date Software is first shipped to Licensee. If any item of Software fails to so
function during its warranty period, as the sole remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for
the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date
Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Networks during the
warranty period along with proof of the date of shipment. This warranty does not apply if the media has been damaged as a result of
accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and
for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions contained in the
software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the
Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the
Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest
Software release. These warranties do not apply to the Software if it has been (i) altered, except by Bay Networks or in accordance with its
instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment,
abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND
ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of its own data and
information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.

4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF
SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY DAMAGES
RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION
WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS
AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees. This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the
United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and
were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is
granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in
subparagraph (c)(1) of the Commercial Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this
license for civilian agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.

2131-0120 Rev 00

LCP Network Management Guide

6. Use of Software in the European Community. This provision applies to all Software acquired for use within the European
Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of
European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee
agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay
Networks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’
copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those
restrictions relating to use and disclosure of Bay Networks’ confidential information shall continue in effect. Licensee may terminate this
license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license.
Upon termination for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies.
Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or information
without first obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf
of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all export licenses and approvals required by the
U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country
to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations, or to any national
or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military
end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of
the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of
California.

Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway, P.O. Box 58185,
Santa Clara, California 95054-8185.

LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE
BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND
EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND
WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF
THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS
UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS
OF THIS AGREEMENT.

2131-0120 Rev 00

vii

About This Document

Before You Begin ........................................................................................................................................ ix

Conventions ................................................................................................................................................. x

Acronyms .................................................................................................................................................... xi

Bay Networks Technical Publications ........................................................................................................ xii

Bay Networks Customer Service ............................................................................................................... xii

How to Get Help ........................................................................................................................................xiii

Bay Networks Educational Services ..........................................................................................................xiii

Associated Documents ............................................................................................................................. xiv

Chapter 1
LCn Features

LCn Service Classes ................................................................................................................................1-1

Bandwidth Allocation ..........................................................................................................................1-2

Network Access Priority .....................................................................................................................1-2

Max TX Burst Size .............................................................................................................................1-3

Defining Service Classes ...................................................................................................................1-3

LCP-16 Modems .......................................................................................................................................1-5

Updating the Network Configuration File ...........................................................................................1-7

Automatic Software Upgrade ....................................................................................................................1-8

Before You Begin ...............................................................................................................................1-9

Network Software Upgrade ................................................................................................................1-9

CDM Software Upgrade ...................................................................................................................1-10

CDM Software Upgrade Using the LCn .....................................................................................1-10

CDM Software Upgrade Using SNMPc ..................................................................................... 1-11

Authorization Key Management .............................................................................................................1-12

Adding an Authorization Key ............................................................................................................1-13

Verifying an Authorization Key .........................................................................................................1-14

Verifying an Authorization Key in SNMPc ..................................................................................1-14

Editing an Authorization Key ............................................................................................................1-15

Deleting an Authorization Key ..........................................................................................................1-16

Resetting Modems ...........................................................................................................................1-16

Bringing the Default Key Back to the Working Key ..........................................................................1-17

Modems running version 2.14 to 3.10 .......................................................................................1-17

Modems running version 3.12 to current (4.1) ...........................................................................1-18

Chapter 2
Security Groups and Filtering

Security Groups ........................................................................................................................................2-1

Setting Up Security Groups ................................................................................................................2-3

Determining a CDM’s Security Group Number ............................................................................2-4

Defining Security Groups Using LCn .................................................................................................2-6

Filtering ..............................................................................................................................................2-9

Filtering Hierarchy ..............................................................................................................................2-9

LCP Network Management Guide

viii

2131-0120 Rev 00

Setting Filtering Variables ................................................................................................................2-10

Setting Filter Values Using the LCn Filter Data Option ....................................................................2-10

Type Filtering .................................................................................................................................... 2-11

IP Address Filtering ..........................................................................................................................2-13

Setting Up IP Address Filtering .................................................................................................2-15

IP Protocol Filtering ..........................................................................................................................2-17

IP Port Filtering ................................................................................................................................2-20

IP Options Filtering ...........................................................................................................................2-22

LCn Provisioning of Filters ...............................................................................................................2-23

Chapter 3
LCn and Health Parameters

LCn Parameters .......................................................................................................................................3-1

Health Parameters ....................................................................................................................................3-4

Modifying the Health Parameters .......................................................................................................3-6

Chapter 4
Troubleshooting

LCP LED Sequence Definitions ................................................................................................................4-1

RF Power Level Measurement .................................................................................................................4-2

Ingress ...............................................................................................................................................4-3

Reviewing Maintenance Summary Variables ..............................................................................4-3

RF Amplitude Fluctuations .................................................................................................................4-4

RF Plumbing Changes .......................................................................................................................4-5

Spectrum Analyzer Settings .....................................................................................................................4-5

Analyzer Settings ...............................................................................................................................4-6

Appendix A

Security Group Numbers ......................................................................................................................... A-1

Appendix B

LCn Serial Number Import ....................................................................................................................... B-1

2131-0120 Rev 00

About This Document

If you are responsible for managing a cable modem network including upgrading cable
modems, you need to read this guide.

Before You Begin

Before using this document, you should be familiar with the management features of the
LANcity Provisioning Server, Headend Controller, and cable modem. You should also be
familiar with an SNMP manager. Also, make sure that the required hardware and software
are installed.

If you want

Go to

Information on Service Classes, LCP-16 CDMs,
automatic software upgrade, and authorization key
management

Chapter 1

Information on Security Groups and filters

Chapter 2

To understand LCn parameters and CDM health
parameters

Chapter 3

Useful LCn and LCP troubleshooting information

Chapter 4

Security Group reference numbers

Appendix A

LCn Serial Number Import instructions

Appendix B

2131-0120 Rev 00

LCP Network Management Guide

Conventions

angle brackets (< >)

Indicate that you choose the text to enter based on the description
inside the brackets. Do not type the brackets when entering the
command.
Example: if command syntax is

ping

<ip_address>

, you enter

ping 192.32.10.12

bold text

Indicates text that you need to enter, command names, and
buttons in menu paths.
Example: Enter

wfsm &

Example: Use the

dinfo

command.

Example: ATM DXI > Interfaces > PVCs identifies the PVCs
button in the window that appears when you select the Interfaces
option from the ATM DXI menu.

brackets ([ ])

Indicate optional elements. You can choose none, one, or all of
the options.

ellipsis points

Horizontal (. . .) and vertical

ellipsis points indicate omitted

information.

italic text

Indicates variable values in command syntax descriptions, new
terms, file and directory names, and book titles.

quotation marks (“ ”)

Indicate the title of a chapter or section within a book.

screen text

Indicates data that appears on the screen.
Example:

Set Bay Networks Trap Monitor Filters

separator ( > )

Separates menu and option names in instructions and internal
pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the AppleTalk option
in the Protocols menu.

Example: Pin 7 > 19 > 20

vertical line (|)

Indicates that you enter only one of the parts of the command.
The vertical line separates choices. Do not type the vertical line
when entering the command.
Example: If the command syntax is

show at routes

nets

you enter either

show at routes

show at nets

, but not both.

About This Guide

2131-0120 Rev 00

Acronyms

BootP

Bootstrap Protocol

BRI

Basic Rate Interface

CDM

Cable Data modem

DES

Data Encryption Standard

DHCP

Dynamic Host Configuration Protocol

GUI

graphical user interface

FTP

File Transfer Protocol

HDLC

High-level Data Link Control

HFC

Hybrid Fiber Coax

Internet Protocol

ISP

Internet Service Provider

IRQ

Interrupt Request

LAN

local area network

LCb

LANcity Multiple User Cable Modem

LCe

LANcity Integrated Headend Controller

LCh

LANcity Headend Equalization Node

LCn

LANcity Provisioning Server

LCP

LANcity Personal Cable Modem

LCT

LANcity Transmaster (Frequency Translator)

MAC

Media Access Control

MAU

Media Access Unit

MIB

Management Information Base

NBMA

nonbroadcast multi-access

NDIS

Network Driver Interface Specification

NVRAM

Non-volatile random access memory

ODI

Open Datalink Interface

OSI

Open Systems Interconnection

OSPF

Open Shortest Path First (Protocol)

PPP

Point-to-Point Protocol

RDBMS

Relational database management system

SMDS

Switched Multimegabit Data Service

SNMP

Simple Network Management Protocol

STP

Spanning Tree Protocol, Shielded Twisted Pair

TCP/IP

Transmission Control Protocol/Internet Protocol

xii

2131-0120 Rev 00

LCP Network Management Guide

Telnet

Telecommunication Network

TFTP

Trivial File Transfer Protocol

TPE

twisted-pair Ethernet

UTP

Unshielded Twisted Pair

WAN

Wide Area Network

Bay Networks Technical Publications

You can now print technical manuals and release notes free, directly from the Internet. Go
to support.baynetworks.com/library/tpubs. Find the Bay Networks products for which you
need documentation. Then locate the specific category and model or version for your
hardware or software product. Using Adobe Acrobat Reader, you can open the manuals
and release notes, search for the sections you need, and print them on most standard
printers. You can download Acrobat Reader free from the Adobe Systems Web site,
www.adobe.com.

Documentation sets and CDs are available through your local Bay Networks sales office
or account representative.

Bay Networks Customer Service

You can purchase a support contract from your Bay Networks distributor or authorized
reseller, or directly from Bay Networks Services. For information about, or to purchase a
Bay Networks service contract, either call your local Bay Networks field sales office or
one of the following numbers:

Information about customer service is also available on the World Wide Web at
support.baynetworks.com.

Region

Telephone number

Fax number

United States and
Canada

800-2LANWAN; then enter Express
Routing Code (ERC) 290, when
prompted, to purchase or renew a
service contract

978-916-8880 (direct)

978-916-3514

Europe

33-4-92-96-69-66

33-4-92-96-69-96

Asia/Pacific

61-2-9927-8888 61-2-9927-8899

Latin America

561-988-7661

561-988-7550

About This Guide

2131-0120 Rev 00

xiii

How to Get Help

If you purchased a service contract for your Bay Networks product from a distributor or
authorized reseller, contact the technical support staff for that distributor or reseller for
assistance.

If you purchased a Bay Networks service program, call one of the following Bay
Networks Technical Solutions Centers:

*For cable modems and cable modem family products, use Express Routing Code 174.

Bay Networks Educational Services

Through Bay Networks Educational Services, you can attend classes and purchase CDs,
videos, and computer-based training programs about Bay Networks products. Training
programs can take place at your site or at a Bay Networks location. For more information
about training programs, call one of the following numbers:

Technical Solutions

Center

Telephone

number

Fax number

Billerica, MA

800-2LANWAN*

978-916-3514

Santa Clara, CA

800-2LANWAN

Valbonne, France

33-4-92-96-69-68

33-4-92-96-69-98

Tokyo, Japan

81-3-5402-0180

Region

Telephone number

United States and
Canada

800-2LANWAN; then enter Express
Routing Code (ERC) 282 when prompted

978-916-3460 (direct)

Europe, Middle East,
and Africa

33-4-92-96-15-83

Asia/Pacific

61-2-9927-8822

Tokyo and Japan

81-3-5402-7041

xiv

2131-0120 Rev 00

LCP Network Management Guide

Associated Documents

Refer to the following documents for further information:

•

SNMP MIB Variable Definitions - 2131-0105 Provides general descriptions of all Bay
Networks LANcity cable modem SNMP MIBs. Also provides detailed descriptions of
specific cable modem SNMP MIBs selected for use during cable plant data over cable
verification.

•

Headend Equipment Installation Guide - 2131-0072 Describes setting up the headend
for data over cable operation in four easy steps.

•

LCn Release Notes - 2131-0119 Provides details of changes in LCn software.

•

LCn Software Upgrade - 2131-0118 Provides procedures to install or upgrade Bay
Networks LANcity cable modem Provisioning Server software.

•

LCP Release Notes - 2131-0106 Provides details of changes in LCP software.

•

LCP Software Upgrade - 2131-0078 Provides procedures to upgrade Bay Networks
LANcity cable modems.

•

LCn Provisioning Server User Guide - 2131-0089 Provides Introductory and LCn
design information, Installation instructions and basic troubleshooting tests that can be
used to resolve some obvious problems, references to specific fields required to set up
a basic network using LCn, a description of the LCn database, with detailed
information about service classes available for a Bay Networks LANcity cable
modem.

2131-0120 Rev 00

1-1

Chapter 1

LCn Features

The LANcity Provisioning Server (LCn) is a tool that enables you to manage the
components of your Cable Data Modem (CDM) network. Using LCn in conjunction with
a network management application that supports Simple Network Management Protocol
(SNMP), such as Castle Rock’s SNMPc, you can control all nodes in the network and all
parameters associated with each node.

You can access LCn features by using the options on the LANcity Access Server Main
Menu and the options on the Manage menu of your network management software. Refer
to the LCn Provisioning Server User’s Guide for more information about the LANcity
Access Server.

This chapter describes the following LCn features:

•

Service class

•

LCP-16 modems

•

Automatic software upgrade

•

Authorization key management

LCn Service Classes

The LCn Service Class feature enables you to define classes of service for each CDM on
the network. Service classes enable you to manage network resources and provide quality
service to a variety of network uses. The following parameters define the service class:

•

Bandwidth allocation (forward and reverse)

•

Network access priority

•

Max transmit burst size

The procedure for defining CDM service classes follows the parameter descriptions.

Note:

This document describes options and procedures associated with the

Castle Rock SNMPc Network Manager application. The LCn features of
other SNMP applications are essentially the same, but the specific menu
options and procedures may differ.

LCP Network Management Guide

1-2

2131-0120 Rev 00

Bandwidth Allocation

The LCn uses LANcity’s UniLINK protocol, a Media Access Control (MAC) protocol
that uses a dynamic mix of reservation and contention-based access to operate efficiently
over the long distances associated with cable TV plants. Two features of this protocol,
Bandwidth Limiting and Guaranteed Access, enable you to allocate bandwidth by using
multiple service levels (service classes). Service classes make optimum use of bandwidth
and help ensure high quality service for a variety of CDM users.

Bandwidth Limiting enables you to set an upper limit on the data rate a cable modem can
transmit or receive from the cable TV data channel. The data rate on the cable TV data
channel is 10 megabits per second (Mbps) upstream and downstream. Within the 10 Mbps
limit, you can define various levels of service. For example, you might specify a limit 64
Kbps (Kilobits per second) of the bandwidth for an entry level user and up to 1.5 Mbps for
a business user. In addition, you can define different limits for both the forward and return
paths.

Guaranteed access, which operates only when the network is busy, works in conjunction
with access priority and Max TX burst. During busy times, the protocol uses a reservation
mode that guarantees access for High priority users. At all other times, the reservation
dedicated bandwidth is available to any user at any time.

Network Access Priority

Network access priority defines the level of access users have when using both forward
and return channels of the cable network. Table 1-1 describes the LCn access priorities.

Access priority only makes a difference when the network is busy. At idle times, all
service classes use contention access.

Table 1-1 LCn Access Priorities

Priority

Description

High

Provides immediate, guaranteed access to the network. Uses the UniLINK
protocol’s access reservation mechanism, which reserves bandwidth when
required.

Normal

Provides contention-only access initially, but moves to reservation when
network traffic is heavy. When traffic lessens, normal priority returns to
contention-only mode.

Low

Provides access and transmission in contention mode only.

LCn Features

2131-0120 Rev 00

1-3

Max TX Burst Size

Max TX Burst Size defines the amount of data a node can transmit onto the cable in a
single transmit burst. UniLINK allows multiple nodes to be concatenated into a single
transmission, which increases the efficiency of bandwidth use. There are five basic ranges,
within which you can specify how the data might be combined. Table 1-2 describes the
ranges.

Defining Service Classes

You can define numerous service classes using the Service Class Data feature in the LCn.
The key variables are the maximum bandwidth you define for Forward and Return
channels and the access priority you assign. You can also fine tune the Max TX Burst sizes
within the byte totals of the burst size choices.

To define a service class:

1. Log on to the LANcity Access Server. The LANcity Access Server Main Menu

(Figure 1-1) appears.

Table 1-2 Max TX Burst Size Ranges

Range

Description

Single packet mode containing 64 to 1518 bytes. Turns off the UniLINK
concatenation feature.

Allows up to 1518 bytes of data to be concatenated in a single transmit. It could be
a single packet or 21 min size packets or a random combination of packet sizes
totally 1518 bytes.

Allows up to 3036 bytes of data in a single transmission. It can be 2 max packets or
43 min packets, or a random combination totaling 3036 bytes.

Allows up to 4554 bytes of data in a single transmit. It could be 3 max packets or 65
min packets, or a random combination totaling 4554 bytes.

Allows up to 6072 bytes of data in a single transmit. It could be 4 max packets or 65
min packets, or a random combination totaling 6072 bytes.

LCn Features

2131-0120 Rev 00

1-5

4. In the Class Name box, type the name of the Service Class you want, then tab to the

Max Bandwidth per Node box.

5. Type the bandwidth you want (in Kbps) in both the Forward and Return boxes. Then

tab to the Network Access Priority box.

6. Select the priority you want from the pull-down box, then tab to the Max TX Burst

field.

7. Select the Max TX Burst you want from the pull-down box, then click Apply. The

Microsoft Access message, “Service Class Edit Complete”, appears.

8. Click OK. You have entered the service class. LCn refreshes the Service Class

Definition window.

9. Click New to add another service class, Edit to change an existing service class, Delete

to remove a service class, or Exit to return to the LANcity Access Server Main Menu.

LCP-16 Modems

The LCP-16 is a modem that can support up to 16 clients on the Ethernet side of the
device. LCP-16 replaces the current LCP and LCw modems. It resembles the LCw but
supports up to 16 client MAC addresses instead of four. The modem learns the address at
startup or the LCn can provision the MAC and IP addresses.

You can replicate the LCP by using one “Max number of clients” or the LCw by using
four. Using the LCP-16 requires a software upgrade on the existing hardware. Refer to
Software Release Notes, V4.00 and the section, “Automatic Software Upgrade,” later in
this chapter for more information.

To configure an LCP-16 modem:

1. Log on to the LCn. The LANcity Access Server Main Menu (see Figure 1-1) appears.

2. Click CDM Data. The Select CDM & Function box (Figure 1-3) appears.

Figure 1-3 Select CDM & Function Box

LCP Network Management Guide

1-6

2131-0120 Rev 00

3. Click Add New. The Enter Cable Data Modem Information window

(Figure 1-4) appears.

Figure 1-4 LCn Enter Cable Data Modem Information Window

4. Use the max number of clients box to specify the number of Ethernet client nodes the

CDM supports, ranging from 1 to 16.

5. Specify the remaining information using the brief descriptions in Table 1-3. For more

detail, refer to the section, “Cable Data Modem Information Screen,” in Chapter 3 of
the LCn Provisioning Server User’s Guide.

Table 1-3 Data Call Modem Information

Field

Description

CDM Name

A name or number identifying this cable modem. System-populated.

MAC Address

The MAC address of the CDM, available on the CDM label.
System-populated.

Serial Number

Cable modem serial number, available on the CDM label.

Resides on
Network

The network to which you want to assign the CDM. Select from the pull
down menu, then click Apply on the popup dialog box that appears.

LCn Features

2131-0120 Rev 00

1-7

6. When you finish, click Apply to write the changes to the database.

7. Click Exit to return to the LANcity Access Server Main Menu.

8. If necessary, update the network configuration file, as described in the next section.

Updating the Network Configuration File

After adding CDMs, update the network configuration file to ensure that the LCn has
current information. When the CDM goes online, it requests the information from the
LCn.

IP Address

Used to manage the CDM. Normally assigned by networks operations
group. The LCn transfers the address to the modem during the boot
process.

Network Access
Allowed

Allows the modem to access a specified network, downloaded during
the boot process.
Note: The modem does not function unless this box is checked. This is
a simple mechanism for preventing network access.

Head End
Reference Node

Enables a CDM with the required hardware and software
configurations to operate as a Headend Reference Node (HRN) for the
LCP network. Do not check for normal CDMs.

Read Only
Network Manager
Access

Assigns read-only status to all network managers.
Note: Checking this box can provide a more secure network
environment, but may create operational problems. Check only at the
direction of your network operations department.

Max Number of
Clients

Allows you to specify the maximum number of Ethernet client nodes
this CDM supports. Enter from 1-16.

Client Addresses

Addresses to which the CDM forwards data. Define an IP or MAC
address or both. Define from 1 to 16 addresses, depending on the
value in Max Number of Clients.

SNMP Manager

Specify up to five managers who can manage the CDM. If you do not
enter a manager, any network manager can manage the CDM.

Service Class

The service class assigned to this CDM. Select from pre-defined
service classes.

Encryption

Specifies whether this CDM encrypts data.

ON Net Gateway

Specifies whether this CDM acts as a decrypting gateway from the
local network. Used only if Encryption box is checked.

Subscriber Data

Enables you to access CDMs subscriber data window.

S/W Upgrade

Enables you to access the software upgrade window for this CDM.

Table 1-3 Data Call Modem Information

(continued)

Field

Description

LCP Network Management Guide

1-8

2131-0120 Rev 00

To update the network configuration file:

1. Click Update Network Configuration Files on the LANcity Access Server Main Menu.

The LCn Enter Network and Authorization window (Figure 1-5) appears.

Figure 1-5 LCn Enter Network and Authorization Window

2. Select the network you want to update from the select network to authorize pulldown

menu.

3. Select the authorization key from the select authorization key pulldown menu.

4. Click Continue. LCn updates or creates a configuration file that contains the new

CDM information.

5. Click Exit to return to the LANcity Access Server Main Menu.

Automatic Software Upgrade

Using the LCn Automatic Software Upgrade feature, you can ensure that the CDMs are
running on the latest version of software available on the system. You can perform a
network-wide software ugrade procedure or upgrade individual CDMs.

After you upgrade the software on the network, the LCn supplies parameters that specify
the software version that a particular CDM should be running, including the software
version number, the name of the software image file, and the IP address of the TFTP server
for the file. When a CDM starts up, it receives the parameters from the LCn and compares
them to the version of the software executing (and residing in FLASH). If the software is
different, the CDM automatically initiates a software upgrade.

This section includes the following information about automatic upgrades:

•

Before you begin - Steps you should take before the automatic upgrade

•

Network software upgrade procedure

•

CDM software upgrade procedure

LCn Features

2131-0120 Rev 00

1-9

Before You Begin

Before you begin any automatic software upgrade procedures, check the following:

•

The new software files are in the appropriate directories. Ftp files are typically loaded
into LCN_Data. Mib files and the Basic.mem file should be in the MIBfiles directory
in the SNMPc main directory.

•

A new MIB file has been created.

•

The DCHP, FTP, and TFTP servers are running. If not, start them prior to attempting
automatic upgrade procedures.

Refer to the Product Software Upgrade manual published with the software release for
detailed information.

Network Software Upgrade

Using the LCn to upgrade the software on the network:

1. Access the LANcity Access Server Main Menu.

2. Click Network Data. The Select Network window appears.

3. Select the network you want, then click Edit. The Enter Network Data window

appears.

4. Click S/W Upgrade Information. The system displays the Network Software Upgrade

Details window (Figure 1-6).

Figure 1-6 Network Software Upgrade Details Window

LCP Network Management Guide

1-10

2131-0120 Rev 00

5. Enter the software upgrade information. Table 1-4 describes the fields.

6. Click Apply To All Cdms in Net. The system displays the message, “All CDMs in

Network will be Modified,” in the Confirm CDM S/W Upgrade message box.

7. If you do not want to apply the upgrade to all CDMs, click Apply, or click Exit to

return to the Enter Network Data window.

8. Click Apply Net Edits to save the changes, then click Exit.

9. On the LANcity Access Main Menu, click Update Network Configuration files to save

the changes you made to the CDMs.

10. If using automatic software upgrade through a router, be sure to configure the default

gateway network parameters. This allows remote modems to upgrade if files are on a
different network. (Refer to READLCP.txt in V4.00 release for more information and
workarounds.)

CDM Software Upgrade

You can also perform the automatic software upgrade on individual modems using either
the LCn or the SNMPc.

CDM Software Upgrade Using the LCn

To upgrade CDM software using the LCn:

1. Access the LANcity Access Sever Main Menu, then click CDM Data.

2. Select the CDM you want on the Select CDM & Function dialog box (see

Figure 1-3), then click Edit.

3. On the Enter Cable Data Modem Information window (see Figure 1-4), click S/W

Upgrade. The Enter Software Upgrade Details window (Figure 1-7) appears.

Table 1-4 Software Upgrade Detail Fields

Field

Description

Network Name

The name of the network which you are upgrading.

Current S/W
Revision

The version of software you wanted LCn to use in N.xy format, where N
is the major release number and xy is the minor release number defined
in the software release notes.

S/W Upgrade
Filename

The name of the upgrade program file to be used on the network.

TFTP File
Server IP
Address

The address of the file server where the upgrade program file is located.

LCn Features

2131-0120 Rev 00

1-11

Figure 1-7 CDM Enter Software Upgrade Details Window

4. Complete the information on the window, then click Apply. Refer to Table 1-4 for

details about the required information.

5. Click Exit to return to the Enter Cable Data Modem Information window.

6. On the Enter Cable Data Modem Information window, click Apply, then do one of the

following:

a. Click Exit to return to the LANcity Access Server Main Menu.

b. Select another CDM for software upgrade, then repeat steps 1 through 6.

7. When you finish upgrading the CDMs you want, click Exit to return to the LANcity

Access Server Main Menu.

8. Click Update Network Configuration files to save the changes you made.

CDM Software Upgrade Using SNMPc

To perform an automatic software upgrade using SNMPc:

1. Access the SNMP Network Map window for the network you want.

2. Select the CDM(s) you want to upgrade.

3. Choose Manage>LCP/LCb V3.xx And Up>Control. The LCP Control Information

window (Figure 1-8) appears.

LCP Network Management Guide

1-12

2131-0120 Rev 00

Figure 1-8 LCP Control Information Window

This window shows the LCP control information for the specified CDM. (If you
selected multiple CDMs, the system displays a control information window for each
CDM.)

4. Type the LCP server address in the LsIPAddress box, then click Set.

5. Type the name of the new software file in the LoadFile box, then click Set.

6. Click Set next to the Start DownLoad box. The CDM resets and receives a new

configuration file that contains the software upgrade information.

7. Repeat steps 4 through 6 for each CDM LcpControl Information window.

Authorization Key Management

The LCn uses authorization keys to verify that a CDM is valid and should receive
operational parameters. If the CDM’s authorization key is not valid, the LCn does not
download the CDM’s configuration file. The LCn downloads the file, the CDM rejects it
due to incorrect key, the modem reboots and scans for new correct channel. The LCn is
unreachable.

The authorization key includes a key name and key data. The key name identifies a
CDM’s current key. Key names can be passed over the network in plain text. The key data
generates an MD5 digital signature and is never passed over the network in plain text.

LCn Features

2131-0120 Rev 00

1-13

LCPs are shipped with a default authorization key and the Network Utility has a key file
containing the default keys. The LCP can use one of two keys, the current key and the
previous key, which enables you to make key changes. Check the LCn parameters of any
device in SNMPc to find the key names.

You can add, verify, edit, and delete authorization keys using the LANcity Access Server
and the Change Authorization Key for Network option.

Adding an Authorization Key

To add an authorization key:

1. Access the LANcity Access Server Main Menu (Figure 1-1).

2. Click CDM key data. The Select Key dialog box (Figure 1-9) appears.

Figure 1-9 Select Key Dialog Box

3. Click New. The Enter Key Data dialog box (Figure 1-10) appears.

Figure 1-10 Enter Key Data Dialog Box

Caution:

The LCn maintains two authorization keys at all times, the current key and the

previous key. If you change the keys frequently and by chance one or more of the CDMs
on the network are shut down when you change the keys, their key may not match the
current key or the previous key and they remain inoperable until a configuration file is
generated for it with a known key. (At that point, contact LANcity customer support.)

LCP Network Management Guide

1-14

2131-0120 Rev 00

4. Type a key name in the Key Name box, using up to 64 alphanumeric characters.

5. Tab to the Key Data box and enter up to 64 alphanumeric characters.

6. Click Apply to create and enter this key into the database. After about 5 to 10 seconds

the Apply Key Edit Function Complete box appears.

7. Click OK.

8. Click Exit to return to the LANcity Access Server Main Menu.

Verifying an Authorization Key

To verify an authorization key:

1. Access the LANcity Access Server Main Menu (Figure 1-1).

2. Click CDM key data. The Select Key dialog box (see Figure 1-9) appears.

3. Check the key names in the Key Name box to verify a particular key and its key data.

Click Exit to return to the LANcity Access Server Main Menu.

Verifying an Authorization Key in SNMPc

1. Access the SNMPc desktop.

2. Select the Headend Reference Node of the network for which you want to verify the

authorization key.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>LCN Parameters. The LCn

Parameter Information window (Figure 1-11) appears.

LCP Network Management Guide

1-16

2131-0120 Rev 00

Figure 1-12 Change Authorization Key for Network Dialog Box

4. Select the network for which you want to change the authorization key.

5. Select the current key.

6. Select the new authorization key.

7. Click Continue. After 5 to 10 seconds (depends on the size of the network), the Create

Network Configuration Function complete box appears.

8. Click OK to return to the Change Authorization Key for Network dialog box.

9. Click Exit to return to the LANcity Access Server Main Menu.

Deleting an Authorization Key

To delete an authorization key:

1. Access the LANcity Access Server Main Menu (Figure 1-1).

2. Click CDM key data. The Select Key dialog box (Figure 1-9) appears.

3. Select the key you want to delete in the Key Name box. The Enter Key Data dialog

box (see Figure 1-10) appears.

4. Click Delete.

5. Click OK in the confirmation box to return to the Enter Key Data dialog box.

6. Click Exit to return to the LANcity Access Server Main Menu.

Resetting Modems

If you make any changes to authorization keys, you must log in to SNMPc and reset each
modem in the network on which you made the changes.

To reset the modems:

1. Access the SNMPc desktop.

2. Select the modems to be reset.

LCn Features

2131-0120 Rev 00

1-17

3. Choose Manage>LCP/LCb V3.xx And Up>Control. The LCP Control Information

window appears.

4. Select Write in the FlashWrite box, then click Set (not necessary).

5. Select Reset in the Reset box, then click Set. The buttons on the window become

inactive as the modem resets.

6. When the buttons re-activate, click Done. The LCP Control Information window

appears for the next modem selected.

7. Verify that the key change was made using the procedure in the section, “Verifying an

Authorization Key in SNMPc”. WorkingKeyId should now be the new key you
entered and LastKeyId should be the previous key, or the key you changed.

8. Repeat steps 4 through 6 for each modem.

Bringing the Default Key Back to the Working Key

Modems running version 2.14 to 3.10

If you want to return to the default key after making an initial key change to a new key,
follow the steps in the section, “Editing an Authorization Key,” to return to the default
key. When you change the authorization key back to the default key, the working key
becomes “default key” and the LastKeyID is also “default key”.

LCP Network Management Guide

1-18

2131-0120 Rev 00

Modems running version 3.12 to current (4.1)

The working key and LastKeyID from the factory are “default key” and “default key”.
After you make the first key change from “default key” to a new key you can not go back
to the factory condition of “default key/default key”. The modem will always remember
the last key. That is, the modem will always remember two (2) unique keys.

Table 1-5 shows examples of shifting keys and going back to the factory default for
modems running V2.14 to V3.12.

Table 1-6 shows examples of shifting keys and going back to the factory default for
modems running V3.12 to the current version.

As you can see, the modem cannot be returned to default/default and remembers the last
key ID prior to the default.

Table 1-5 Shifting Keys - Modems Running V2.14 to V3.12

Action

Working Key ID

Last Key ID

Factory ship

default

Update new
key

8 ball

default

Update new
key

any name

8 ball

Update new
key

default

any name

Update new
key

default

Table 1-6 Shifting Keys - Modems Running V3.12 to Current Version

Action

Working Key ID

Last Key ID

Factory ship

default

Update new
key

8 ball

default

Update new
key

any name

8 ball

Update new
key

default

any name

Update new
key

default

any name

LCP Network Management Guide

2-2

2131-0120 Rev 00

Figure 2-1 Sample Security Group Configuration

C h a n ne l A

Channel B

Hospital A

H ospital B

Town Hall

Public Works

Library

LCh

Dept.

LCP

LC P

CATV

Group 1

Group 2

Rehab Center

LCP

Physicians’ Building

ABC Construction

B & B B u ild in g S u p p lie s

Group 3

LCn

All Groups

LCP

JK Pharmaceuticals

Ethernet

Connection

Group 1

Group 4

Group 5

Security Groups and Filtering

2131-0120 Rev 00

2-3

Setting Up Security Groups

Although security groups are an excellent tool, they can cause network management
problems if implemented incorrectly. The following points refer to shared security groups.
Keep the following points in mind when you set up security groups:

1. The system determines a CDM’s security group by bit settings in the binary number

converted from the security group number you define for the CDM. You can enter the
number as a decimal, then the system converts it to hex on the Security Group Filter
window and to binary in the background.

2. The system considers all CDMs with a matching bit in the security group number to be

in the same security group. Therefore, when choosing the security group number,
make sure that the CDM shares matching bits with the other CDMs you want in the
security group.

3. Define the security group of each CDM before you define the security groups of the

HRN.

4. Make sure that each CDM associated with each HRN is in a security group because,

once the HRNs are in all security groups, they no longer communicate with CDMs not
in a security group.

5. After assigning a security group to a CDM using SNMPc, make sure that you set Flash

in the Control parameters in SNMPc, then reset the CDM. This ensures that the CDM
restarts with the new configuration that includes the security group.

Table 2-1 Sample Security Groups

Security Group

Description

Group 1

Includes Hospital A and Hospital B on Channel A, the rehab center and
physicians’ building on Channel B, and the LCh (headend reference node or
HRN) for each channel. The groups are linked by an Ethernet connection.
Because the group includes CDMs from two channels, at least one of the
CDMs must have the Spanning Tree Protocol variable set to on.

Group 2

Includes a town hall, town library, town public works department, and the LCh
associated with Channel A. Group 2 shares Channel A with Group 1, but they
cannot communicate with each other

Group 3

Includes a construction company and a building supplies dealer, and the LCh
associated with Channel B. Group 3 shares Channel B with Groups 1 and 4,
but cannot communicate with either.

Group 4

Includes a pharmaceutical company, the physicians’ building, and the LCh
associated with Channel B. Group 4 shares Channel B with Groups 1 and 3,
but cannot communicate with Group 3

Group 5

Group 5 includes the building supply store and the town public works
department. Group 5 spans two channels, so the Spanning Tree Protocol
variable must be set for one of the CDMs in the group.

LCP Network Management Guide

2-4

2131-0120 Rev 00

6. After assigning a security group to a CDM using LCn, make sure you click Upgrade

Network Configuration to ensure that the CDM receives the assignment.

Determining a CDM’s Security Group Number

Although you may identify security groups using letters or names, when you add a CDM
to the group, you must enter a numeric value. You can enter a decimal value, which the
system converts to hex on the entry window. In the background, the system sets a bit
which identifies the CDM’s group.

As you define security groups for each CDM, take care that you do not enter a group
number that has bit settings allowing the CDM to be in groups that you do not want it to be
in.

Example

If we defined the security groups in Figure 2-1 using decimal numbers 1, 2, and 3, we
would be allowing CDMs in groups 1 and 3 to communicate because they have a common
bit. Table 2-2 shows the decimal, hex, and binary values that would allow this
communication.

As you can see in Table 2-2, there are common bit settings among the groups. Based on
the common bits, the system would view Group 1 and Group 3 as shared groups and allow
all CDMs within those two groups to communicate. Similarly, all CDMs in groups 2 and 3
can communicate.

If you do not want the CDMs in Groups 1, 2, and 3 to communicate with CDMs in any
other group, you must choose security group numbers that do not translate to a binary
number containing a common bit. Table 2-3 shows three group numbers that do not have
matching bits and could be used for Groups 1, 2, and 3.

Note:

LANcity customer support personnel have created an interactive spreadsheet of

possible values, which can assist you in defining security groups. For a copy of the spread
sheet or assistance with security groups, call your customer support representative.

Table 2-2 Example Bit Values for Security Groups

Group Name

Decimal
Value

Hex
Value

Binary Value

Group 1

0x00000001

0000000000000001

Group 2

0x00000002

0000000000000010

Group 3

0x00000003

0000000000000011

Security Groups and Filtering

2131-0120 Rev 00

2-5

Table 2-4 shows a Security Group worksheet with security groups and their respective
hex, decimal, and binary numbers.

As you can see in the worksheet, you can set up three groups with the same LCh (Headend
Reference Node, or HRN) that are mutually exclusive. Each has one bit set. If you want
one of the groups to communicate with another group, use the LANcity Security Groups
spreadsheet to determine the decimal or hex number that provides the set bit you need.

Table 2-3 Example Group Numbers With No Matching Bits

Group Name

Decimal Value

Hex Value

Binary Value

Group 1

00000001

0000000000000001

Group 2

00000002

0000000000000010

Group 3

00000004

0000000000000100

Table 2-4 Security Group Worksheet

Dec

Hex

Bin

Group

65,535

FFFF

1111111111111111

LCh

0000000000000001

Group1

0000000000000010

Group2

0000000000000100

Group3

0000000000001000

0000000000001010

0000000000010000

0000000000100000

0000000000101000

0000000001000000

128

0000000010000000

256

100

0000000100000000

512

200

0000001000000000

1024

400

0000010000000000

2048

800

0000100000000000

4056

000100000000000

000000000010100

Group4

100

0000000001100100

LCP Network Management Guide

2-6

2131-0120 Rev 00

Example

If you have a Group 4 and want the CDMs in Group 4 to communicate with the CDMs in
Group 3, assign the decimal number 20. Group 4 is defined at the bottom of Table 2-4
using decimal 20. As you can see, when 20 is converted to binary, it shares a common bit
with Group 3.

If you need a group that shares information with Groups 3 and 4, create a Group 5 and
assign the decimal number 100 (Hex 64). The last row of Table 2-3 shows that, when
converted to binary, decimal 100 shares common bits with Groups 3 and 4.

When you assign a number to a security group, make sure to note all of the bits that are set
to avoid including another group.

You can define security groups using the SNMP management application or the LCn.

Figure 2-2 LCn Control Information Window

7. Select Write in the Flash Write box, then click Set.

8. Select Reset in the ResetNow box, then click Set. The system resets the CDM you

selected and greys out the button columns.

9. Click Done.

Defining Security Groups Using LCn

To define a security group using the LANcity Access Server:

1. Access the LANcity Access Server Main Menu by selecting management on the start

screen and then selecting LCnBeta.

2. Click Filter Data. The Select Filter dialogue box appears.

3. Click Add New. The Add New Filter dialogue box appears.

Security Groups and Filtering

2131-0120 Rev 00

2-7

4. Select Security Group in the Type box and type the name of the group in the Name

box, then click Create. The SecGrp Filter window appears.

Figure 2-3 SecGrp Filter Window

The SecGrp Filter window allows you to define the MIB variables associated with
security groups.

5. Type the Security Group name. The name can be a group identifier such as Group1 or

GroupA, or a name indicating what the group is, such as Hospitals. It does not have to
match the number you assign to the security group.

6. Click the Group Filter On box.

7. Select Shared in the Group Type box.

8. Type the Security Group Number in the Security Group box.

9. If the security group includes CDMs on more than one channel, click the Security

Group Spanning Tree Filter On box for at least one of the CDMs.

10. If you want the Broadcast or Multicast filters on, click the appropriate box. Broadcast

filtering set to ON specifies that the MAC layer broadcasts are filtered by the device.
Multicast filtering set to ON specifies MAC layer multicasts are filtered by the device.

11. When you finish, click the corner x to close the SecGrp Filter window and return to the

Form Select Filter dialog box.

12. Click one of the following:

a. Exit to return to the LANcity Access Server Main Menu

b. Add New to create another security group

c. Edit to modify an existing group

After you have created the groups you want, you can then assign them to CDMs.
Assigning Security Groups to CDMs Using LCn

LCP Network Management Guide

2-8

2131-0120 Rev 00

To assign a security group or groups to a CDM:

1. Click CDM Data on the LANcity Access Server Main Menu.

2. In the Select CDM & Function box, select the CDM you want, then click Edit. The

information for that CDM appears on the Enter Cable Data Modem Information
window.

3. Click Filters. The Select Node Filters window (Figure 2-5) appears. The system lists

the filters you have created by name and type.

Figure 2-4 Select Node Filters Window

4. Click the security group(s) for the CDM, then click Add or Add All.

5. Close the Select Node Filters window. On the Enter Cable Data Modem Information

window click Apply. The system applies the changes to the specified CDM.

6. Click OK on the Apply Node Edit function complete window. Click Exit to return to

the LANcity Access Server Main Menu.

7. Click Update Network Configuration to save the changes you made to the CDM

configurations.

Security Groups and Filtering

2131-0120 Rev 00

2-9

Filtering

You can enhance the efficiency of the CDM network using one or more of the filtering
options available in the LCn and SNMPc. You can specify that packet data be forwarded
or filtered. Most of the filters have a global variable that specifies that the filtering is on
and what the action is if there is no match.

You can configure most filters in the LCn and in SNMPc. All of the filter parameters are
MIB (Management Information Base) variables that reside in the RDMS database. Using
Filter Control windows you can set global variables which specify whether the filter is on/
off and what the action is if there is no match. Each filter has an associated table that stores
related information such as the filter’s status (ON/OFF), the action, and a match count.

The filtering options have a defined hierarchy and the system’s first decision to filter is
final. No later decision to forward a packet has any effect.

This section describes the filtering hierarchy as well as Type and IP filtering. The Type
and IP filtering sections include examples and procedures for setting up the filters. Refer
to the previous section, “Security Groups,” for information on Security Group filtering.

Filtering Hierarchy

When you specify filter parameters, the system saves them to NVRAM and preserves
them across resets. There is a defined, three-level hierarchical order that the system uses
when making filtering decisions. The first decision to filter is final, no later decision to
forward a packet has any effect.

The hierarchy is as follows:

Level One: Security Group filtering

Level Two: Ethertype filtering

Ethertype (Type) filtering is the next level of filtering that the CDM checks if you are
not using security groups. The following hierarchy exists within Type filtering:

•

IP only forwarding

If IP only is enabled, the CDM makes no further filtering decisions.

•

Novell filtering

If Novell filtering is enabled, the CDM makes no further filtering decisions.

•

Specific Type filter (Ethertype, DSAP, or SSAP)

If Type filtering is enabled, the CDM makes no further filtering decisions (i.e., IP
filtering).

Level Three: IP filtering

LCP Network Management Guide

2-10

2131-0120 Rev 00

If security groups and Type filtering are not enabled, the CDM checks to determine
whether IP filtering is enabled. It checks in the following order and makes no further
decision when it finds an IP filtering type enabled:

IP Address filtering

IP Port filtering

IP Protocol filtering

IP Options filtering

IGMP filtering

Subsequent sections describe Type and IP filtering. Refer to the previous section,
“Security Groups,” for information about security group filtering.

Setting Filtering Variables

The procedure for setting Type and IP filtering variables is the same for each filter. You
can create the filter using the LCn Access Server Filter Data option or through the Filters
menu in the SNMPc.

The next section describes using the LCn to set up filters. Each filtering section includes
the SNMPc procedure specific to that filter.

Setting Filter Values Using the LCn Filter Data Option

To create filters or specify filter variables using the LCn Access Server:

1. Access the LANcity Access Server Main Menu.

2. Click Filter Data. The Select Filter dialog box appears.

3. Click Add New. The Add New Filter dialog box appears.

4. Select the filter type you want and type a name for the new filter; then click Create.

The Add Filter window for the filter you selected appears, similar to the sample shown
in Figure 2-6.

LCP Network Management Guide

2-12

2131-0120 Rev 00

Example

Considering the CDMs shown in Figure 2-1, suppose you wanted a particular CDM or
client in Hospital A, Hospital B, and the rehab facility to receive all information about the
latest in medical research and the key source of that information was from a company
using a Novell server. Using Type filtering, you could block all data packets other than
Novell to the specified clients.

Before you set up the filters, you may want to select one CDM that is configured with the
clients. Also, apply the filter to the client CDMs only. The following procedure illustrates
how you set the variables for the example.

To enable Type filtering:

1. Access the SNMPc desktop.

2. Select client CDMs for which you want to create a filter.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Filters>

Type Filter Control. The Type Filter Control Information window (Figure 2-7)
appears.

Figure 2-6 Type Filter Control Information Window

4. Select On in the Control box to enable Type filtering, then click Set.

5. Select Off in the IPOnly box, then click Set.

6. Select Block to block Novell traffic. If Control is set to On and IP Only is set to on,

you should select Block, then click Set.

7. Select Pass in the Novell box, then click Set.

8. Click Block in the Action on No Match box to prevent the passing of non-Novell

packets, then click Set.

Security Groups and Filtering

2131-0120 Rev 00

2-13

9. Click Set All to store your entry.

10. Click Done to return to the SNMPc desktop.

You do not need to make Type Filter table entries because you enable Novell filtering on
the Control window. If you were enabling a specific Ethertype, DSAP, or SSAP filter, you
would also need to access the Type Filter table and create entries there.

To enable specific Ethertype, DSAP, or SSAP filtering:

1. Complete the previous procedure.

2. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Filters>

Type Filter Table. The Type Filter Edit Table Entry window appears. Use this window
to enter detailed specifications for Type filtering.

3. Type the number (from 1-10) of the table entry in the Index box, then click Set.

4. Select Valid to specify that the system uses the parameters in this entry to make

filtering decisions. Then click Set.

5. Select the type of Ethernet interface (Ethertype, DSAP, or SSAP). The interface you

choose specifies the type of data packet that the system should make filtering
decisions about using this table entry.

6. Type the value in hex that the system should compare in data packets matching the

Type you specified in the Type box.

7. Type Pass or Block to specify how the system should handle data packets that match

this entry.

8. When you finish, click Set All, then click Done to return to the SNMPc desktop.

The Match Count box is a system populated field. If you are editing an entry, you can use
Count Reset to set Match Count to zero.

IP Address Filtering

The LCn maintains a list of IP addresses. You can assign an IP address to a CDM when
you add it to the network. If you do assign an IP address, the CDM allows data from only
that specified IP address on the Ethernet to be forwarded to the CATV, and only data to
that IP address to be forwarded from the CATV to the Ethernet.

If you do not assign IP addresses, the CDM does not prevent the forwarding of data based
on IP address unless other IP address filter options are configured.

LCP Network Management Guide

2-14

2131-0120 Rev 00

Example

Figure 2-7 Sample IP Address Diagram

You can use IP Address filtering to manage the communication among Hospital A,
Hospital B, the rehab center, and the physicians’ building, shown in Figure 2-7. Each
CDM node on the network and its associated clients have a unique IP address. Using
address filtering you can specify what data can be transmitted and received by each client.

You can configure the clients in Hospital A so that with the exception of one IP address,
such as 192.190.3.40, they can only transmit and receive data to and from each other. You
can configure the remaining IP address so that it can communicate with all of the clients
and with other nodes in the network.

For each CDM you set up a table entry with a destination address that is the same as its IP
address. The source address could be 0.0.0.0 to allow data from any source, or you could
limit the sources as well. Note that if you limit sources you should include the HRN’s
address as a source so that the CDM can communicate with the headend. You might also
want to include the LCn server’s address as a source.

LCP

LCn

LCh

LCP

IP 192.190.3.10

IP 192.190.3.20

IP 192.190.3.25

IP 192.190.3.30

IP 192.190.3.40

IP 192.190.3.50

IP 192.190.3.60

Hospital A

Hospital B

Rehab Center

Physicians’ Bldg.

Clients

IP 192.190.3.51
IP 192.190.3.52
IP 192.190.3.53

Clients

IP 192.190.3.31
IP 192.190.3.32
IP 192.190.3.33
IP 192.190.3.34

Clients

IP 192.190.3.61
IP 192.190.3.62
IP 192.190.3.64

IP 192.190.3.41
IP 192.190.3.42
IP 192.190.3.43
IP 192.190.3.44
IP 192.190.3.45
IP 192.190.3.46

IP 192.190.3.54
IP 192.190.3.55

Security Groups and Filtering

2131-0120 Rev 00

2-15

Setting Up IP Address Filtering

To set up IP Address filtering using SNMPc:

1. Access the SNMPc desktop.

2. Select the CDM(s) you want to configure.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Filters>

IP Address Filter Control. The IP Address Filter Control Information window
(Figure 2-8) appears.

Figure 2-8 IP Address Filter Control Information Window

4. Select On in the Control box to enable IP Address filtering, then click Set.

5. Select On in the SendDu box if you want the system to send “destination unreachable”

ICMP message when a packet does not match any table entries, then click Set.

6. Select Pass or Block [Block] in the lcLcpAddrActionOnNoMatch box to specify

whether you want the system to forward or block packets that do not match the IP
Address filters. Then click Set.

7. Click Done to return to the SNMPc desktop.

8. With the same CDM(s) selected, choose Manage>LCP/LCb V3.xx And

Up>Configuration>Filters>IP Address Filter Table. The IP Address Filter Edit Table
Entry window (Figure 2-9) appears.

Security Groups and Filtering

2131-0120 Rev 00

2-17

IP Protocol Filtering

IP Protocol filtering specifies that the system forward or filter packets based on their
protocol, which is defined in the packet’s protocol field. The protocols currently supported
include ICMP, IGMP, ST, TCP, EGP, IGP, and UDP

To set up IP Protocol filtering:

1. Access the SNMPc desktop.

2. Select the CDMs for which you want protocol filtering.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Filters>IP Protocol Filter

Control. The IP Protocol Filter Control Information window (Figure 2-10) appears.

Table 2-5 IP Address Filter Variables

Variable

Description

Index

The entry number.

Status

Specifies whether this entry is valid or invalid for making filtering decisions.
Valid=Use for filtering decisions

Interface

Specifies the interface from which packets to be compared to this entry should
be.

The IP address in DOT notation that the packet’s destination address must
match when compared to this entry. If Interface=Either, the value in this entry is
compared to both the source and destination address.

DaMask

The IP mask address in DOT notation that a packet’s destination mask
address must match to pass this filter.

The IP address in DOT notation that a packet’s source address must match to
pass this filter.

SaMask

The IP mask address in DOT notification that a packet’s source mask address
must match to pass this filter.

FilterAction

The action to be taken on packets that are filtered.

FiltMatchCount System-supplied count of matches for this table entry.

FiltMatchReset
Count

Resets the count for the entries that match this table.

Security Groups and Filtering

2131-0120 Rev 00

2-19

Figure 2-11 IP Protocol Filter Add Table Entry Window

10. Make the selections you want on this window. Table 2-6 describes the variables.

11. Click Set after each entry or click Set All when you finish.

12. Click Done to return to the SNMPc desktop.

Table 2-6 IP Protocol Filter Table Variables

Variable

Description

Index
(lcLcpIpProtoFiltIndex)

[Numeric]
Specifies the index of this entry in the table.

Status
(lcLcpIpProtoFiltStatus)

[Valid/Invalid]
Indicates whether the system uses this entry to
make filtering decisions based on IP protocol.

StartProto
(lcLcpStartProto)

[ICMP/IGMP/ST/TCP/EGP/IGP/UDP]
Specifies the value of the first IP protocol in a range
that the system uses for comparison to the packet.

EndProto
(lcpLcpEndProto)

[ICMP/IGMP/ST/TCP/EGP/IGP/UDP]
Specifies the value of the last IP protocol in a range
that the system uses for comparison to the packet.

ProtoFilterAction
(lcLcpProtoFilterAction)

[Pass/Block]
Specifies whether a packet that matches this entry
is forwarded or filtered. Pass=Forwarded.

(continued)

LCP Network Management Guide

2-20

2131-0120 Rev 00

IP Port Filtering

Use IP Port filtering to specify whether TCP or UDP packets received are to be forwarded
or filtered. The filtering decision is based on source and destination port numbers.

To set up IP Port filtering:

1. Access the SNMPc desktop.

2. Select the CDM(s) for which you want to set up port filtering.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Filters>IP Port Filter

Control. The IP Port Filter Control Information window (Figure 2-12) appears.

Figure 2-12 IP Port Filter Control Information Window

4. Select on in the Control box, then click Set.

ProtoMatchCount
(lcLcpProtoMatch Count

[Numeric]
Counts the number of packets that match this table
entry.

ProtoMatchResetCount
(lcLcpProtoMatchReset
Count)

[Reset]
The counter for the number of packets that match
this table entry. If you set this variable, the
ProtoMatchCount for this table entry is set to zero.

Table 2-6 IP Protocol Filter Table Variables

(continued)

Variable

Description

LCP Network Management Guide

2-22

2131-0120 Rev 00

IP Options Filtering

IP Options filtering is a security filtering option that enables you to control IP packet data
flow based on the Source Route and Record Route.

To set up an IP Options filter:

1. Access the SNMPc desktop

2. Select the CDM(s) for which you want to create the filter.

3. Choose Manage>LCP/LCbV3.xx And Up>Configuration>Filters>IP Options Filter

Control. The IP Options Filter Control Information window (Figure 2-14) appears.

Table 2-7 IP Port Filter Table Variables

Variable

Description

Index

[Numeric]
Specifies the index of this entry in the IP Port Filter
table.

Status

[Valid/Invalid]
Specifies whether the system uses this table entry
to make filtering decisions based on TCP or UDP
port number.

StartPoint [Numeric]

The value of the first IP port in a range being used
to compare against the packet.

EndPort [Numeric]

The value of the last IP port in a range that the
system uses to compare with the packet.

PortFilterAction [Pass/Block]

Specifies whether the system forwards or filters a
packet that matches this table entry.

PortMatchCount

[Numeric]
The number of packets that matched this entry in
the filter table.

PortMatchResetCount

[Reset]
Controls the value in lcLcpPortMatchCount for this
entry. When you reset, the value returns to zero.

PortFiltInterface

[FromEnet, FromCatv, FromEither]
Specifies whether the system should compare
packets from the Ethernet, CATV, or either to this
table entry to determine whether the package
should be filtered.

PortFiltType

[SourcePort, DestinationPort, EitherPort]
Specifies whether the systems filters based on a
packet’s source port, destination port, or both.

Security Groups and Filtering

2131-0120 Rev 00

2-23

Figure 2-14 IP Options Filter Control Information Window

4. Select On in the Control box to enable IP Options filtering, then click Set.

5. If the Count box value is more than 0, select Reset in the ResetCount box, then click

Set.

6. Select On in the SendDu box if you want a “destination unreachable” message sent

when a packet is filtered. Then click Set.

7. Click Done to return to the SNMPc desktop.

LCn Provisioning of Filters

•

LCn overrides the previous set up using SNMPc on per filter type.

•

Deleting filters in LCn only removes them from the configuration file completely. It
does not change what has been set up in NVRAM in the CDM.

•

To delete a LCn provisioned filter from NVRAM, do not delete but reset values in
LCn and set it to invalid to clear filters in NVRAM.

LCn and Health Parameters

2131-0120 Rev 00

3-1

Chapter 3

LCn and Health Parameters

LCn (LANcity Provisioning Server) parameters and Health parameters, both accessible
through SNMPc provide information about how a particular CDM is operating. The LCn
parameters provide network-level information, such as configured bandwidth and if the
CDM is a headend reference node. The Health parameters information describes how the
individual CDM is performing. You can edit both LCn and Health parameters.

This chapter describes the parameters, including how and why you might need to edit
them.

LCn Parameters

LCn parameters are the definitive operational specifications for each CDM in the CATV
network. When a CDM starts up or resets, it gets reference information from the headend
reference node (HRN) that allows it to contact the LCn for the parameters. The
information ranges from transmit and receive frequency to amount of data a node can
transmit onto the cable in a single opportunity.

To view LCn parameters:

1. Access the SNMPc desktop.

2. Select the device you want to check.

3. Choose Manage>LCP/LCb V3.xx and up>Configuration>LCN Parameters. The LCP

LCn Parameters Information window (Figure 3-1) appears.

LCn and Health Parameters

2131-0120 Rev 00

3-3

Table 3-1 LCn Parameters

Parameter

Description

The CDM’s transmit frequency, in HZ, for the CATV.

The CDM’s receive frequency, in HZ, for the CATV.

RefNode

Specifies whether this CDM is configured as an HRN. It must be set to 0 for
LCPs.

MaxLd

The maximum round trip delay for the network. This value must be greater
than or equal to the loop delay of the cable modem furthest from it. All CDMs
on the HFC segment must have the same value.

AccessNet

Specifies whether this CDM has access to the CATV network. If 0, this device
cannot transmit to or receive from the network.

NmReadOnly

Specifies whether the LCn parameters are read-only (non-zero). If they are,
you cannot edit the displayed parameters.

MaxEnet

Specifies the maximum number of devices that this device can support on the
ethernet.

AuthNmIP

If not zero, the IP address of the network management station that is allowed
to access the variables of this device. If this variable and AuthNmMAC are
both not zero, both the MAC address and IP address of packets from a
network management station must match.

AuthNmMac

If not zero, the MAC address of the network management station allowed to
access the variables of this device. If this variable and AuthNumIP are both
not zero, the MAC address and the IP address of packets from a network
management station must match.

MaxCdm

The maximum number of cable modems installed on the CATV network. This
variable must be greater than or equal to the maximum number.

WorkingKeyId

The authorization key currently in use at the LCn authorizing the downloading
of configuration data from the LCn.

LastKeyId

The previous authorization key used for authorizing the downloading of
configuration data from the LCn.

MaxBWReturn

The amount of data (in bits per second) that this node is allowed to transmit
onto the CATV’s return channel.

MaxBWForward

The amount of data (in bits per second) that this node is allowed to transmit
onto the CATV’s forward channel.

NetAccessPriority

The CDM’s priority in accessing the network. High=Guaranteed, collision-free
access. Normal=Initially contention only, but can join the reservation
mechanism if busy. Low=Contention-only access. Refer to the section, “LCn
Service Classes,” in Chapter 1 for more information about access priority.

MaxTxBurst

The amount of data a node can transmit onto the cable in a single opportunity.
Refer to the section, “Max Tx Burst Size,” in Chapter 1 for more information
about data transmission bursts.

(continued)

LCP Network Management Guide

3-4

2131-0120 Rev 00

Health Parameters

Health parameters provide an indication of overall network health. The parameters include
a small set of network statistics which are displayed as status descriptions. The statistics
appear in the following groupings:

1. Group 1 is color coded: RED, YELLOW, and GREEN.

GREEN means operating as expected,

YELLOW implies something is not quite right or out of spec

RED implies something needs attention.

2. Group 2 is also color coded: RED and GREEN.

GREEN means operating as expected

RED means non-operational.

3. Group 3 is degree coded: LOW, MODERATE, and HEAVY.

These degrees indicate the percentage of traffic that is on the network.

MinPublicConten

The approximate percentage of network bandwidth that is put aside
exclusively for contention mode. (It is not available for reservation mode.) This
percentage is a factor only when the network is busy; it determines the
bandwidth split between high priority nodes and low priority nodes.

DeferTo
GuaranteedNode

Specifies whether this node defers to the network node, which is allocated
guaranteed bandwidth.

Reserved
Bandwidth

The number of bytes reserved for the guaranteed node.

Table 3-1 LCn Parameters

(continued)

Parameter

Description

LCn and Health Parameters

2131-0120 Rev 00

3-5

All of the health parameters are in the Health Summary Group. Table 3-2 lists the Health
parameter threshold default values for Green/Yellow and Yellow/Red as well as the name
of the parameter that defines the threshold in parenthesis.

Table 3-2 Health Parameter Defaults

Health Variable

Green

Green/Yellow

Threshold

Yellow

Yellow/Red

Threshold

Red

RXDeltaLDDBIndicator

150
(rxldbootgy)

300
(rxldbootyr)

Bstolddeltaindicator

50
(rxldbsdeltagy)

100
(rxldbsdeltayr)

RXBootIndicator

150
(rxbootgy)

300
(rxbootyr)

RXBSIndicator

150
(rxbsgy)

300

(rxbsyr)

MacRxPerError
Indicator

50,000

(merrgy)

40,000

(merryr)

BSRetainPerLost
Indicator

10,000
(retlostgy)

2,000
(retlostyr)

PacerChangeIndicator

10,000
(pcrchggy

2,000
(pcrchgyr)

EtherPktsPerError
Indicator

1,000,000,000
(eerrgy)

800,000,000
(eerryr)

CATVLoadIndicator

EtherLoadIndicator

30
(elm)

50
(emh)

CATVTxRxIndicator

30
(urxlm)

50
(urxmh)

EtherTxRxIndicator

30
(erxlm)

50
(erxmh)

LCP Network Management Guide

3-6

2131-0120 Rev 00

Modifying the Health Parameters

Modifications, or sets to the health parameters require that you maintain the proper
relationship between the thresholds and, depending on the thresholds you are changing,
you might need to modify Yellow/Red before Green/Yellow.

It is important to understand that although sets to these variables change the thresholds
immediately, the health variables may not change quickly. For example, the load
indicators are calculated every 30 seconds by default. Also a network that has been
running for a long time since error stats were reset may take a long time for the Packet
Error Rate to cross one of the new thresholds.

Restore Defaults resets the thresholds to the above table. The new thresholds take effect
immediately with the above caveat in effect. However, the NVRAM is not modified. If the
unit were to be reset, the User defaults would be restored.

When you are satisfied that the thresholds are appropriate for your network, you can save
them to NVRAM using the Save User Thresholds set on the Health Parameters
Information window. This ensures that the active thresholds are preserved across resets.

If the user defaults are to be permanently erased, the proper procedure is to Restore
Defaults followed by Save User Thresholds.

To modify a CDM’s health parameters:

1. Access the SNMPc desktop.

2. Select the CDM(s) you want.

3. Choose Manage>LCP/LCb V3.xx And Up>Configuration>Health

Parameters><Parameter Option, such as Yellow to Red>. The associated LANcityLCP
Health Information window appears. For illustration, Figure 3-2 shows the Health
Yellow/Red Information window.

Note:

The units on the Load Thresholds are percent.

For example, the UniLINK Low/Moderate (ulm) Threshold default of 30 means 30%
load or 3 Mbps.
The units on Rate Indicators are ratios.
For example, the Pacer Change Green/Yellow Threshold (pcrchggy) is one Pacer change
per 10,000 Block Sync Intervals (BSIs) or approximately one loss of Pacer every 5
minutes.
The units on the Level Thresholds are 1/50 of a dB.
For example, the Yellow/Red Threshold on the highest to lowest rung of the Block Sync
Packet since booting (rxbootyr) is 300*1/50 dB or 6 dB.

2131-0120 Rev 00

4-1

Chapter 4

Troubleshooting

This chapter contains information you can use to troubleshoot LANcity Provisioning
Server (LCn) problems. It includes the following:

•

LCP LED sequence definitions

•

RF power level measurement

•

C/N measurement

•

Spectrum analyzer settings

LCP LED Sequence Definitions

The LEDs on the front panel of the Cable Data modem (CDM) indicate the diagnostic that
is currently running. Figure 4-1 illustrates the LEDs.

Figure 4-1 CDM Front Panel LEDs

PWR - Power is on

BTX - CDM is using broadband

ETX-CDM is using Ethernet

BSA - CDM has achieved

block sync

LCP Network Management Guide

4-2

2131-0120 Rev 00

RF Power Level Measurement

Radio Frequency (RF) power level measurements can cause problems, particularly on the
network side.

You can use the following tools to troubleshoot the RF portion of the network using
LANcity Management Information Base (MIB) variables:

•

Ingress monitoring

•

RF amplitude fluctuations

•

RF plumbing changes

•

Power up patience

Table 4-1 Illuminated LEDs During Diagnostics

Diagnostic

PWR

ETX

BTX

BSA

Low Memory Test

KSeg0/KSeg1 Cache Test

Data Cache MATs+ Test

Instruction Cache MATs+ Test

Data Cache Block Refill Test

Instruction Cache Block Refill Test

PROM Checksum Test

Write Buffer Test

Memory Test

Ethernet Address PROM Checksum Test

UniLINK Address PROM Checksum Test

Exception Test

Sonic Registers Test

Sonic CAM Test

Sonic Loopback Test

Start Up Operational Code

Failure Loading/No Application Available

Troubleshooting

2131-0120 Rev 00

4-3

Ingress

Ingress, or noise, is the most common problem in any two-way CATV network. Typically,
noise in the network accumulates at the headend and the LANcity Headend (LCh) loses
block sync because the C/I () ratio falls below 25 dB. When the LCh loses block sync, all
the modems on that network also lose block sync and reset. Each time the LCh and
modems lose block sync for between one and two minutes, they reset themselves.

To determine whether the LCh and modems are continuously resetting, review the
Maintenance Summary Group of the LCh (LANcity headend) and the History log to
determine how many times the headend lost block sync since the last reboot.

Reviewing Maintenance Summary Variables

To review Maintenance Summary variables:

1. Access the SNMPc network experiencing the difficulty.

a. On the SNMPc desktop, select the LCh you want to check.

b. Choose Manage>LCP/LCb V3.xx or greater>Monitoring>Mainenance. An Edit

Table Entry window (Figure 4-2) displays the maintenance information for the
LCh.

Figure 4-2 Edit Table Entry Window for Maintenance Summary Information

LCP Network Management Guide

4-4

2131-0120 Rev 00

2. Check the following variables to determine how often the LCh has reset itself:

•

Loss Block Sync

•

Time-outs Establishing Block Sync

•

Bridge Resets

•

System Up Time

If the variables show that the LCh has reset more than ten times since it was last reset,
noise at the headend is most likely the problem.

One of the ways to reduce noise at the LCh, is to limit the number of combining segments
to a number that does not relate a signal to noise number less than 25 dB.

RF Amplitude Fluctuations

Cable Data modems (CDMs) are sensitive to RF amplitude fluctuations. They can adjust
to small fluctuations, such as a 3dB change. However, if the fluctuation is greater than
3dB, the CDM resets itself because it can no longer adjust its loop delay level to the level
it is supposed to transmit to itself.

You can determine whether the CDM is operating normally by checking the
AvgLDRxLevel (the level that the modem is transmitting to itself) and the
AvgBSRxLevelDbmv (the transmission level the modem is trying to match) by looking at
the Auto Adjust variables in SNMPc.

To check the Auto Adjust variables

1. Access SNMPc and select the CDM you want to check.

2. Choose Manage>LCP/LCb V3.xx or greater>Auto Adjust. The LCP CATV Info Edit

Table Entry window (4-3) appears.

Troubleshooting

2131-0120 Rev 00

4-5

Figure 4-3 LCP CATV Info Edit Table Entry Window

3. Compare the AvgBSRxLevelDbmv (receive power, block sync level) to the

MinBSrxLevelDbmv and MaxBSRxLevelDbmvs to determine the receive window of
operation for this modem since it last reset.

4. Check the AvgLDRxLevel (the level the modem is transmitting to itself) and the

AvgBSRxLevelDbmv (the level the modem is constantly trying to match by adjusting
its transmitter). TxPwrDbmv shows the level at which the modem is transmitting.

RF Plumbing Changes

When you make changes to RF equipment, such as pads, a change in path timing (loop
delay) occurs. It is important to reset associated devices. If you change the Headend
Reference node (HRN) path or swap a translator, it is critical that you reset all the devices
associated with either.

Spectrum Analyzer Settings

The LCP transmits a QPSK modulated signal. Its carrier is suppressed and its power is
distributed over the 6 MHz channel. To measure the power of the data signal, use a
spectrum analyzer. The resolution bandwidth and video bandwidth settings determine if a
correction factor is needed.

LCP Network Management Guide

4-6

2131-0120 Rev 00

Analyzer Settings

Table 4-2 shows appropriate analyzer settings using a Hewlett-Packard 8591C.
Measurements and settings may differ with other analyzers.

Measure the signal with the marker + 1 Mhz from the center frequency. The resulting
measurement should have an accuracy of + 2 dB.

Example

A customer set the LCh pads based on a measurement taken in a 300 Khz resolution
bandwidth. They did not use a correction factor, and the measurements were off by 3dB.

The section above, Verifying Signal Levels on an Operational Network shows that
measurements need to be taken in a 3Mhz resolution bandwidth (see Table 4-2). If this is
not done, a correction factor is needed. The correction factor varies from vendor to vendor
and even from model to model. It depends on the IF filter in the instrument.

If available, a 3Mhz resolution bandwidth is the most accurate measurement. However,
instrument calibration and resolution accuracy make this measurement accurate only up to
+ 2dB.

Some instruments will not have a resolution bandwidth of 3Mhz. In this case, an estimated
power level compared to the product specification and expected power levels given in the
installation guide is the best guide for estimating the measurement.

Table 4-2 Spectrum Analyzer Settings - Hewlett Packard 8591C

Span for all three settings

10 MHz

Max hold for all three setting

Resolution BW

3 Mhz

Video BW

1 Mhz - use No correction factor

Resolution BW

300 Khz

Video BW

100 Khz - add 7 dB to reading

Resolution BW

100 Khz

Video BW

30 Khz - add 13 dB to reading

Note:

This measurement should be done on a data channel that has light traffic

or no traffic.

2131-0120 Rev 00

A-1

Appendix A

Security Group Numbers

This appendix contains a table showing the decimal, hex, and binary numbers you should
use when creating security groups. In Table A-1, the security group numbers range from 1
to 31, which is the maximum number of security groups you can use.

Table A-1 Security Group Numbers

Group Number

Decimal

Hex

Binary

00000001

0000000000000001

00000002

0000000000000010

00000003

0000000000000011

00000004

0000000000000100

00000005

0000000000000101

00000006

0000000000000110

00000007

0000000000000111

00000008

0000000000001000

00000009

0000000000001001

0000000A

0000000000001010

0000000B

0000000C

0000000D

0000000E

0000000F

0000000000001111

00000010

0000000000010000

00000014

0000000000010110

LCP Network Management Guide

A-2

2131-0120 Rev 00

00000019

0000000000011001

0000001E

0000000000111100

LCh (HRN)

FFFFFFFF

1111111111111111

Table A-1 Security Group Numbers

(continued)

Group Number

Decimal

Hex

Binary

2131-0120 Rev 00

B-1

Appendix B

LCn Serial Number Import

This appendix contains instructions that enable customers to go to a Bay Networks
website and download their CDM serial numbers for importing into the LCn.

Follow these procedures to download:

1. Log on to Bay Networks Commerce Server.

2. Enter your sales order number.

3. Enter the postal zip (or international) code of the ship to address.

4. Enter the E-mail address to which you want the serial number file sent. This address

can be yours or someone else’s.

5. You may choose to receive all serial numbers or you may choose a date range by ship

date.

6. Click on submit.

7. The Baynetwork E-mail returns in a few minutes with an attached file. The attached

file name is, for example, “Client File.txt” and is a text (txt) file. The serial number is
listed first, followed by a comma and space and then the MAC address. (This is called
a comma separated file.)

8. Save the file to a floppy disk (A:\ drive) or move the file to the root directory (do not

use subdirectories) of the C drive. Be sure to use the DOS 8.3 naming scheme for A or
C.

Follow these procedures to import to the LCn:

1. Start the LCn, access the LANcity Access Server Main Menu, and click on Import

Serial Numbers.

2. Specify either the A drive or the C drive and enter the name of the file.

3. Import the file.

4. Select Edit. This screen shows what has been imported.

5. Select CMD data from the Main Menu. Select Add New. Choose the serial number

and click on Continue.

6. Enter the IP Address.

R E A D E R ’S C O M M E N TS

W h at do y ou th ink of this docu m en t? Y o ur co m m ents an d su gg es tions w ill h elp us to im prov e th e q ua lity an d u
of our p ublicatio ns.

P le ase r ate this d oc u m ent:

P oor

E xc elle nt

A cc uracy

R ea da bility

E xam ples

O rga niz atio n

C om pleten ess

D id y o u fin d erro rs in this d ocu m e nt? If s o, p le as e s p ecify th e error(s) an d pa ge n um ber(s).

G en era l co m m e nts:

S ug ges tio ns fo r im prov e m ent:

N am e:__ __ __ __ __ _ __ __ __ __ __ __ __ __ _ __ __ __ __ __ __ __ __ _ __ ___ _ __ __ __ __ _ __ _D ate:__ __ __ __ _ __ __ __ _

Title:__ __ __ __ _ __ __ __ __ __ __ __ __ _ __ __ __ __ __ __ __ _ D ep artm e nt:__ __ _ __ __ __ __ __ __ __ _ __ __ __ __ __ __ __

C om pa ny :_ __ _ __ __ __ __ __ __ __ __ _ __ __ __ __ __ __ __ _ _S treet:_ __ __ __ __ _ __ __ __ __ __ __ __ __ _ __ __ __ __ __ _

C ity:_ __ __ __ __ __ _ __ __ __ __ __ __ __ _ __ __ __ __ __ __ __ _State/C ou ntry:_ _ __ __ __ __ __ __ __ _ _Zip C od e:__ __ __

Document Outline