Juniper Networks G10 CMTS · Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 Part Number: 530-006461-01, Revision 2 Juniper Networks

Juniper Networks, Inc.

1194 North Mathilda Avenue

Sunnyvale, CA 94089

USA

408-745-2000

www.juniper.net

Part Number: 530-006461-01, Revision 2

Juniper NetworksG10 CMTS

SNMP and Enterprise MIBSpecification

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

ii

This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright © 1986–1997, Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part of them is in the public domain.

This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto.

This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The Regents of the University of California. Copyright © 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.

GateD software copyright © 1995, The Regents of the University. All rights reserved. Gate Daemon was originated and developed through release 3.0 by Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD software copyright © 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright © 1991, D. L. S. Associates.

This product includes software developed by Maker Communications, Inc., Copyright © 1996, 1997, Maker Communications, Inc.

Juniper Networks is registered in the U.S. Patent and Trademark Office and in other countries as a trademark of Juniper Networks, Inc. G10, Internet Processor, Internet Processor II, JUNOS, JUNOScript, M5, M10, M20, M40, M40e, and M160 are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. All specifications are subject to change without notice.

Juniper Networks G10 CMTS SNMP and Enterprise MIB SpecificationCopyright © 2002, Juniper Networks, Inc.All rights reserved. Printed in USA.

Writer: Jerry IsaacIllustrations: Paul GilmanCovers and template design: Edmonds Design

Revision History28 February 2002—Second Edition.

The information in this document is current as of the date listed in the revision history.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without notice.

Products made or sold by Juniper Networks (including the G10 CMTS, M5 router, the M10 router, the M20 router, the M40 router, the M40e router, the M160 router, and the JUNOS software) or components thereof may be covered by one or more of the following patents which are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS software has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

The DOCSIS Module performs encryption that is subject to U.S. Customs and Export regulations. A DOCSIS Module shall not be exported, sold or transferred to a country outside the USA and Canada without an appropriate export license from the U.S. Government. The specific Regulations governing exports of encryption products are set forth in the Export Administration Regulations, 15 C.F.R. (Code of Federal Regulations), Parts 730-774.

••••••••••••••••••••••••••••••••••••••••••••••••

Table of Contents iii

Table of ContentsAbout This Manual

Purpose .................................................................................................................ixOrganization ..........................................................................................................ixDocument Conventions ..........................................................................................x

Notes, Cautions, and Warnings........................................................................xG10 CMTS Document Set.......................................................................................xi

Chapter 1G10 CMTS Introduction ........................................................................................1

Overview ................................................................................................................1G10 CMTS Features and Functions .........................................................................2

Features and Benefits ......................................................................................2Management Architecture Overview.......................................................................3

G10 CMTS SNMP Support ................................................................................6G10 CMTS MIB Categories ...............................................................................6

Chapter 2G10 CMTS Standard MIB Specification......................................................7

G10 CMTS Standard MIB Support ...........................................................................7Support of Optional MIB Objects.............................................................................7

DOCS-CABLE-DEVICE-MIB Object Support.......................................................8DOCS-IF-MIB Object Support ...........................................................................8DOCS-BPI-MIB Object Support .........................................................................8

Chapter 3G10 CMTS Enterprise MIB Specification...................................................9

Module pacificBroadband .......................................................................................9Objects Beneath Object pbcRegs ...................................................................11Objects Beneath Object pbcManagement ......................................................12Objects Beneath Object pbcProducts .............................................................12Objects Beneath Object pbcManagement ......................................................12

Notifications in Enterprise MIBs............................................................................13Tables in Enterprise MIBs .....................................................................................13MIB Module PBC-ENT-MIB ....................................................................................14

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specificationiv

Imported Definitions .....................................................................................14MIB Module PBC-GENERIC-MIB ............................................................................15

Imported Definitions .....................................................................................15Textual Conventions......................................................................................16PBC-GENERIC-MIB Object Details ..................................................................18

MIB Module PBC-CMTS-MIB..................................................................................22Imported Definitions .....................................................................................22Textual Conventions......................................................................................23PBC-CMTS-MIB Object Details .......................................................................27

MIB Module PBC-KODIAK-M-G10-MIB ..................................................................31Imported Definitions .....................................................................................31

IndexIndex ..............................................................................................................................33

••••••••••••••••••••••••••••••••••••••••••••••••

List of Figures v

List of FiguresList of Figures

Figure 1: Typical CMTS Location..........................................................................2Figure 2: G10 CMTS Management Architecture ..................................................5Figure 3: Hierarchy of Module pacificBroadband ..............................................10

List of Figures

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specificationvi

••••••••••••••••••••••••••••••••••••••••••••••••

List of Tables vii

List of TablesList of Tables

Table 1: G10 CMTS SNMP-Related MIBs Supported ............................................6Table 2: G10 CMTS CMTS Standard MIBs Supported ..........................................7Table 3: Objects Beneath Module pacificBroadband .........................................11Table 4: Objects Beneath Module pbcManagement ..........................................12Table 5: Objects Beneath Module pbcManagement ..........................................12Table 6: Notifications Within Enterprise MIBs ..................................................13Table 7: Tables Within Enterprise MIBs ............................................................13

List of Tables

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specificationviii

••••••••••••••••••••••••••••••••••••••••••••••••

About This Manual ix

About This Manual

This section describes important information about the design of this document.

Purpose

The purpose of the Juniper Networks G10 CMTS SNMP and Enterprise MIB Specification is to specify the Simple Network Management Protocol (SNMP) support, and the standard and enterprise Management Information Base (MIB) support provided by the G10 Cable Modem Termination System (CMTS).

With respect to the SNMP and MIB requirements specified by the Data Over Cable Service Interface Specifications (DOCSIS™), this particular revision of the Juniper Networks G10 CMTS SNMP and Enterprise MIB Specification specifies those requirements as defined by DOCSIS version 1.0 only.

The intended audience for this information is for network management application developers and network operators of the G10 CMTS.

Organization

This document is organized as follows:

Chapter 1, “G10 CMTS Introduction”– Provides a G10 CMTS functional overview and a general overview of network management with respect to a CMTS. This chapter also specifies the SNMP-related support provided by the G10 CMTS.

Chapter 2, “G10 CMTS Standard MIB Specification” – Specifies the standard MIBs supported by the G10 CMTS as required by DOCSIS version 1.0.

Chapter 3, “G10 CMTS Enterprise MIB Specification” – Specifies the enterprise MIBs supported by the G10 CMTS.

Document Conventions

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specificationx

Document Conventions

The following document conventions are used in this manual:

Notes, Cautions, and Warnings

GeneralConventions

Italic font Denotes a) emphasis, b) first use of a new term, or c) a document title.

Screen Name font Denotes a) the on-screen name of a window, dialog box or field, or b) keys on a keyboard.

Software Conventions

Computer font Font denotes code or messages displayed on-screen.

Computer Bold font Font denotes literal commands and parameters that you enter exactly as shown.

<Computer Italic> font Font denotes parameter values that require a user-defined input.

The value strings are enclosed in angle brackets <...>.

[parameter] Square brackets denote optional parameters.

{parameter} Braces denote required parameters.

| Vertical bars separate parameters in a group from which you must choose only one.

↵ Return symbol indicates pressing the Enter key at the end of a command line.

A note indicates information that might be helpful in a particular situation, or information that might otherwise be overlooked.

A caution indicates a situation that requires careful attention. Failure to observe a cautionary note could result in injury or discomfort to yourself, or serious damage to the product.

A warning is intended to alert the user of the presence of uninsulated dangerous voltage within the product’s enclosure that may present a risk of electric shock.

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

About This Manual xi

G10 CMTS Document Set


Pre-InstallationGuide

Installation andConfiguration

Getting Started FunctionalDescription

SNMP and Enterprise MIBSpecification

PREPARATION OPERATION REFERENCE

Operation andMaintenance

CLI Reference

530-006434-01

530-006437-01

530-006461-01530-006435-01530-006433-01

530-006459-01530-006436-01


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specificationxii

••

Chapter 1G10 CMTS Introduction
••••••••••••••••••••••••••••••••••••••••••••••
Overview

This chapter provides an introduction to the G10 Cable Modem Termination System (CMTS).

The G10 CMTS manages Internet data, voice and MPEG services. It functions as the interface between the services networks—Internet, Public Switched Telephone Network (PSTN), video servers—and the hybrid fiber/coax (HFC) network of subscribers, as shown in Figure 1 on page 2. This is the “last mile” of broadband service, with the CMTS typically located in the cable headend or distribution hub. It is targeted at the following data and voice aggregation applications:

Large CATV Hub Sites — DOCSIS multi-service, residential and commercial IP network access over HFC networks maintained by cable television (CATV) multiple service operators (MSOs) needing enhanced integrated data, voice and video in large metropolitan areas.

Small CATV Hub Sites — Smaller hub sites aggregated over metropolitan fiber rings supporting Gigabit Ethernet.

G10 CMTS Introduction 1

G10 CMTS Features and Functions

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

2

Figure 1: Typical CMTS Location

G10 CMTS Features and Functions

The G10 CMTS provides true multi-services support, including the ability to simultaneously support DOCSIS IP services, VoIP services, and native MPEG transport streams.

Features and Benefits

Innovative features of the G10 CMTS include:

Scalable, high-density chassis that supports from one to eight DOCSIS modules. Each module can be configured for up to four downstream channels at 64 and 256 QAM, and up to 8 upstream channels at QPSK and 16 QAM. This provides a total system capacity of up to 32 downstream channels and 64 upstream channels.

Scaleable and high-density architecture that supports 16,000 service flows per DOCSIS module, up to 128,000 per chassis.

Logical allocation of up to 8 upstream channels to any of the four upstream ports on each DOCSIS Module. This allows channels to be provisioned by the Command Line Interface (CLI), SNMP commands, or a Network Management System without the need for physical node recombining.

Advanced upstream scheduling and a queuing algorithm that efficiently allocates resources to satisfy multiple service flows with the most stringent Quality of Service requirements (Class of Service for DOCSIS 1.0). Per-flow QoS with Diff-Serv ensures end-to-end management of Service Level Agreements (SLAs).

Cable Headendor

Distribution HubInternet

Backbone

PSTN

Servers

NetworkManagement

Switch/Router CMTS

Subscribers

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specification

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Management Architecture Overview

The G10 CMTS delivers the following benefits:

DOCSIS services – DOCSIS 1.0 and EuroDOCSIS 1.0 RF interfaces and protocols

Industry-leading RF performance – Signal-to-Noise Ratio (SNR) performance, efficiency, and configuration flexibility

Advanced diagnostics – spectrum monitoring, historical data

Quality-of-Service – Advanced DOCSIS scheduler for Voice-Over-IP and other applications

Standard network interfaces – Gigabit and Fast Ethernet

Line-rate performance

Management interfaces – CLI, Telnet, SNMP, DOCSIS 1.0 MIBs (Management Information Base)

The G10 CMTS is compliant with the following industry specifications:

DOCSIS 1.0

EuroDOCSIS 1.0


The primary management of the G10 CMTS is performed using SNMP in conjunction with the Command Line Interface (CLI). Though the initial configuration of the G10 CMTS is performed primarily through the CLI, SNMP can also be used to perform some of the steps required for configuration. The CLI can also be used to manage the G10 CMTS. Refer to the Juniper Networks G10 CMTS CLI Reference manual for more details regarding the G10 CMTS CLI.

Key components of the SNMP model of a managed network consist of one or more managed SNMP entities, one or more SNMP managers, a messaging protocol, and a transport stack to allow messaging to occur between the managed entity and the manager.

A managed SNMP entity must contain an SNMP agent that provides access to the management information and its properties contained in its Management Information Base (MIB). The management information may include configuration parameters, various statistics, and state variables that reflect the status of the managed entity. Each of the DOCSIS Modules and Chassis Control Modules contain a set of management information that must be accessible by an SNMP manager. Within the G10 CMTS, the Chassis Control Module runs an SNMP agent that provides SNMP and CLI access to all of the modules within the CMTS. In addition, the MIB can define events—a trap, an inform, or a notification—that represent specific conditions in the managed entity. The SNMP agent generates event reports to an SNMP manager or a Trap Manager that reflect these conditions.

An SNMP manager has access to the MIBs of its managed entities. Depending on the definition of the objects in each MIB, the manager can retrieve and modify the objects as part of its management role. Also, an SNMP manager receives events from SNMP agents and takes the appropriate action, depending on the type of event that has occurred. Figure 2 on page 5 provides a high-level view of the SNMP management architecture of the G10 CMTS.



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

4

A Network Management System (NMS) is comprised of servers and managers that use SNMP for multiple purposes:

The NMS Management Server and the CMTS SNMP manager use the SNMP protocol for message exchange with the SNMP agent that resides on the G10 CMTS.

The Diagnostics Server in the NMS uses SNMP to poll various statistics defined in the standard and enterprise MIBs, such as Media Access Control (MAC) variables (HCS errors, CRC errors, collisions for requests), and Physical (PHY) variables (signal-to-noise ratios, Sync loss, power levels). These statistics can then be used to detect, diagnose, and potentially correct CMTS or HFC problems. The Diagnostics Server can also be configured to generate traps or notifications to the Trap Manager.

SNMP is used between the NMS and the Network Operations Center (NOC) allowing remote management of the NMS and the G10 CMTS. Remote clients on the network can also use SNMP to access those elements of the managed network for which privilege has been granted.

There is a SYSLOG in the NMS and a Local Event Log in the CMTS that contain the same log of events, which are defined within MIBs. The CMTS uses the SYSLOG mechanism (as opposed to SNMP) to send SYSLOG events to the SYSLOG Server. The Local Event Log is SNMP accessible.

The NMS contains the SNMP manager for the DOCSIS Cable Modems (CMs). NMS management of the CMs is transparent to the CMTS since the SNMP messages, or Protocol Data Units, are encapsulated as the payload within DOCSIS MAC frames.


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


Figure 2: G10 CMTS Management Architecture

DiagnosticsServer

CMTS SNMP Manager

CM SNMPManager

Trap Manager

Remote Client

NOC SNMP

G10 CMTSNetwork Management System

DOCSIS CM

CMTS SNMP Agent

LocalEvent Log

NMS ManagementServer

SNMP

SNMP

SNMP

SNMP

SNMP

SNMP

SYSLOGServer

SYSLOG



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

6

G10 CMTS SNMP Support

As required by DOCSIS 1.0, the G10 CMTS supports SNMPv1 and SNMPv2c. The SNMPv1/v2c agent is accessible only by a v1/v2c NMS.

Table 1 provides a list of the SNMP- and SMI-related MIBs and the corresponding IETF RFCs that are supported by the G10 CMTS.

Table 1: G10 CMTS SNMP-Related MIBs Supported

G10 CMTS MIB Categories

The G10 CMTS supports two general categories of MIBs—standard and enterprise. Some standard MIBs must be supported as required by DOCSIS 1.0. However, Juniper Networks has elected to provide support for additional standard MIBs. The standard MIBs supported are listed in Chapter 2. The enterprise MIBs are defined in Chapter 3.

MIB Name RFC Number RFC Title

SNMPv2-PDU RFC 1905 Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)

SNMPv2-TM RFC 1906 Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)

SNMPv2-MIB RFC 1907 Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)

SNMPv2-SMI RFC 2578 Structure of Management Information Version 2 (SMIv2)

SNMPv2-TC RFC 2579 Textual Conventions for SMIv2

SNMPv2-CONF RFC 2580 Conformance Statements for SMIv2


••

Chapter 2G10 CMTS Standard MIB Specification
••••••••••••••••••••••••••••••••••••••••••••••
The standard MIBs supported by the G10 CMTS are a combination of those MIBs required by DOCSIS 1.0, along with additional MIBs specific to the G10 CMTS. The following sections in this chapter simply provide a list of the MIBs supported by the G10 CMTS and do not provide details regarding the management information contained therein. For details regarding a specific MIB, the reader is encouraged to read that particular MIB.

G10 CMTS Standard MIB Support

Table 2 provides a list of the standard MIBs and the corresponding IETF RFCs that are supported by the G10 CMTS.

Table 2: G10 CMTS CMTS Standard MIBs Supported

Support of Optional MIB Objects

In some cases, support for certain objects (OBJECT-TYPE or OBJECT-GROUP) within a MIB is considered optional as defined by the DOCSIS specifications. This section identifies, by MIB, those optional objects that are supported by the G10 CMTS. If an object is listed as supported, then all underlying objects are also supported. The omission of an optional object in the following tables implies that the object is not supported by the G10 CMTS.

MIB Name RFC Description

DOCS-CABLE-DEVICE-MIB RFC 2669 DOCSIS Cable Device MIB

DOCS-IF-MIB RFC 2670 Radio Frequency (RF) Interface MIB

ETHERLIKE-MIB RFC 2665 Ethernet Interface MIB

IF-MIB RFC 2233 The Interfaces Group MIB using SMIv2

BRIDGE-MIB RFC 1493 Definitions of Managed Objects for Bridges

IP-MIB RFC 2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2

UDP-MIB RFC 2013 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2

TCP-MIB RFC 2012 SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2

DOCS-BPI-MIB RFC 3083 Baseline Privacy Interface MIB

ENTITY-MIB RFC 2737 Entity MIB (Version 2)

G10 CMTS Standard MIB Specification 7

Support of Optional MIB Objects

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

8

If a MIB is not explicitly addressed in this section, then none of the optional objects within that MIB are supported in the G10 CMTS.

DOCS-CABLE-DEVICE-MIB Object Support

The DOCS-CABLE-DEVICE-MIB (“DOCSIS Cable Device MIB”) objects that are considered optional by DOCSIS 1.0, but are supported by the G10 CMTS, are as follows:

docsDevBaseGroup

docsDevEventGroup

docsDevFilterGroup

DOCS-IF-MIB Object Support

The DOCS-IF-MIB (“Radio Frequency Interface MIB”) objects that are considered optional by DOCSIS 1.0, but are supported by the G10 CMTS, are as follows:

docsIfDownChannelPower

docsIfQosProfileTable

The docsIfDownChannelPower object is supported because the G10 CMTS DOCSIS Modules contain integrated upconverters. The docsIfQosProfileTable object is supported, though entries in this table cannot be created by the NMS. Entries are created by the G10 CMTS as a result of gleaning QoS parameters from registration requests sent by CMs.

DOCS-BPI-MIB Object Support

DOCSIS 1.0 requires that all of the objects in the DOCS-BPI-MIB (“Baseline Privacy Interface MIB”) be supported in a CMTS. However, because the G10 CMTS does not support Multicast SIDs, the docsBpiIpMulticastMapTable and docsBpiMulticastAuthTable objects are not supported.

In general, the G10 CMTS does not support those objects classified by the DOCSIS specifications as Deprecated or Obsolete. In the exceptional case where a deprecated or obsolete object is supported, Juniper Networks reserves the right to remove such support in a future release without prior notice.


••

Chapter 3G10 CMTS Enterprise MIB Specification
••••••••••••••••••••••••••••••••••••••••••••••
The G10 CMTS provides support for the following enterprise MIBs:

PBC-ENT-MIB—this is the top-level MIB which defines the root structure for all of Juniper Networks’s enterprise MIBs

PBC-GENERIC-MIB—defines system and chassis management capabilities that are common to all of Juniper Networks’s CMTS product offerings

PBC-CMTS-MIB—defines management objects common to all of Juniper Networks’s CMTS product offerings

PBC-KODIAK-M-G10-MIB—defines management features specific only to the G10 CMTS

These MIBs define extensions to the standard MIBs, and provide the support for managing the proprietary features and functions of the G10 CMTS.

Module pacificBroadband

The top level of the PBC-ENT-MIB tree is the pacificBroadband module which resides under enterprise at { enterprise 5987 }. The complete path to the pacificBroadband module from the root of the Object Identifier (OID) tree is as follows:

{ iso org dod internet mgmt private enterprise pacificBroadband }

This path is equivalent to OID value { 1 3 6 1 4 1 5987 }. Figure 3 on page 10 illustrates the hierarchy of the pacificBroadband module and the next two levels beneath it. For the hierarchy, object, and event details below the second level, refer to the listing of the entire enterprise MIBs in “MIB Module PBC-ENT-MIB” on page 14 through “MIB Module PBC-KODIAK-M-G10-MIB” on page 31.

G10 CMTS Enterprise MIB Specification 9


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

10

Figure 3: Hierarchy of Module pacificBroadband

pacificBroadband

pbcModuleRegs { pbcRegs 1 }

pbcRegs { pacificBroadband 1 }

pbcGeneric { pbcManagement 1 }

pbcCmts { pbcManagement 2 }

pbcManagement { pacificBroadband 2 }

pbcKodiakMG10Cmts { pbcProducts 1 }

pbcProducts { pacificBroadband 3 }

pbcGenericSystemAgentCapsR2 { pbcCaps 1 }

pbcCaps { pacificBroadband 4 }

pbcReqs { pacificBroadband 5 }

pbcExpr { pacificBroadband 6 }

cmtsAgentCaps { pbcCaps 2 }

pbcKodiakMG10AgentCaps { pbcCaps 3 }


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


The objects one level beneath the pacificBroadband module, along with their OIDs, are presented in Table 3, which is followed by brief explanations of each of these objects.

Table 3: Objects Beneath Module pacificBroadband

pbcRegs—represents the sub-tree for PBC registrations

pbcManagement—represents assorted common management MIBs

pbcProducts—represents the sub-tree for product-specific object and event definitions

pbcCaps—represents the sub-tree for agent profiles (defined with the AGENT-CAPABILITIES construct)

pbcReqs—represents the sub-tree for management application requirements (defined with MODULE-COMPLIANCE construct)

pbcExpr—represents the sub-tree for experimental definitions

Sections “Objects Beneath Object pbcRegs” through “Objects Beneath Object pbcManagement” on page 12 itemize and describe the objects that reside beneath the objects listed in Table 3 (the pbcReqs and pbcExpr objects do not have any objects directly beneath them).

Objects Beneath Object pbcRegs

The only object that resides directly beneath the pbcRegs object is the pbcModuleRegs object which represents the sub-tree used to register the values assigned to modules with the MODULE-IDENTITY construct.

Objects OID

pbcRegs { pacificBroadband 1 }

pbcManagement { pacificBroadband 2 }

pbcProducts { pacificBroadband 3 }

pbcCaps { pacificBroadband 4 }

pbcReqs { pacificBroadband 5 }

pbcExpr { pacificBroadband 6 }



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

12

Objects Beneath Object pbcManagement

The objects immediately beneath the pbcManagement object, along with their OIDs, are presented in Table 4, which is followed by brief explanations of each of these objects.

Table 4: Objects Beneath Module pbcManagement

pbcGeneric—the root node for all Juniper Networks management objects which are common to chassis-type systems

pbcCmts—the root node for management objects which are common to all Juniper Networks CMTS products and which are not defined by standard RFCs

Objects Beneath Object pbcProducts

The only object that resides directly beneath the pbcProducts object is the pbcKodiakMG10Cmts object. There are currently no management objects specific only to the G10 CMTS model.

Objects Beneath Object pbcManagement

The objects immediately beneath the pbcManagement object, along with their OIDs, are presented in Table 5, which is followed by brief explanations of each of these objects.

Table 5: Objects Beneath Module pbcManagement

pbcGenericSystemAgentCapsR2—defines the agent capabilities which are common to all of Juniper Networks’s system/chassis products

CmtsAgentCaps—defines the baseline agent capabilities for Juniper Networks CMTS SNMP agents

pbcKodiakMG10AgentCaps—defines agent capabilities specific to the G10 CMTS

Objects OID

pbcGeneric { pacificBroadband pbcManagement 1 }

pbcCmts { pacificBroadband pbcManagement 2 }

Objects OID

pbcGenericSystemAgentCapsR2 { pacificBroadband pbcCaps 1 }

cmtsAgentCaps { pacificBroadband pbcCaps 2 }

pbcKodiakMG10AgentCaps { pacificBroadband pbcCaps 3}


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Notifications in Enterprise MIBs

Notifications in Enterprise MIBs

Table 6 summarizes the notifications that are defined in the enterprise MIB modules, along with the MIB that defines them, their descriptions, the MIB variables that are returned, and the Object ID of each notification.

Table 6: Notifications Within Enterprise MIBs

Tables in Enterprise MIBs

Table 7 summarizes the tables that are defined in the enterprise MIB modules, along with the MIB that defines them and the indices into the tables.

Table 7: Tables Within Enterprise MIBs

Notification MIB / Description / Objects Returned / OID

pbcCmtsSpectrumAnalysisSweepComplete

PBC-CMTS-MIB

Denotes the conclusion, with status and data table identification, of an RF sweep operation

pbcCardIfPortIndex

pbcSpectrumAnalysisArrayIndex

pbcSpectrumAnalysisArrayStatus

1.3.6.1.4.5987.2.2.2.2.3.1.1

Table Indices MIB

pbcCmtsIfDownstreamChannelTable ifIndex

PBC-CMTS-MIB

pbcCmtsIfUpstreamChannelTable ifIndex

pbcSpectrumAnalysisRFInputTable pbcCardIfPortIndex

pbcSpectrumAnalysisArrayIndexTable pbcCardIfPortIndex


pbcSpectrumAnalysisDataTable

pbcCardIfPortIndex


pbcSpectrumAnalysisFrequency

pbcCmtsSpectrumAnalysisNotificationTable pbcCardIfPortIndex

pbcCardIfIndexTable ifIndex

PBC-GENERIC-MIB

pbcCardTable pbcCardIfCardIndex

pbcCardPortTable pbcCardIfCardIndex

pbcCardIfPortIndex

pbcPortIfTable pbcCardIfPortIndex

pbcPortIfIndex


MIB Module PBC-ENT-MIB

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

14

MIB Module PBC-ENT-MIB

The PBC-ENT-MIB that follows has been formatted to enhance readability. It was parsed from the actual PBC-ENT-MIB file that is written in compliance with Structure of Management Information, Version 2.

Imported Definitions

Last Updated: 200106072341ZOrganization: Pacific Broadband Communications, Inc.Contact: Contact: Customer Support Group Postal: Pacific Broadband Communications, Inc 3103 North First Street San Jose, CA USA 95134 PHONE: +1 408.468.6200 EMAIL: [email protected] WEB: http://www.pacificbroadband.comPurpose: This module defines the enterprise managed object space for products from Pacific Broadband Communications, Inc. (C)opyright 2001, Pacific Broadband Communications, Inc.

Some portions of the enterprise MIBs presented in section “MIB Module PBC-ENT-MIB” on page 14 through section “MIB Module PBC-KODIAK-M-G10-MIB” on page 31 (for example, AGENT-CAPABILITIES) are not represented as they are not relevant to a discussion of private MIB objects. For the complete representation of the enterprise MIBs, refer to the MIB files provided.


Definition Source

enterprises RFC1155-SMI

MODULE-IDENTITY SNMPv2-SMI

OBJECT-IDENTITY SNMPv2-SMI


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

MIB Module PBC-GENERIC-MIB


The PBC-GENERIC-MIB that follows has been formatted to enhance readability. It was parsed from the actual PBC-GENERIC-MIB file that is written in compliance with the Structure of Management Information, Version 2.


Last Updated: 200106211620ZOrganization: Pacific Broadband CommunicationsContact: Contact: Customer Support Group Purpose: This module defines management objects which are common to all PBC chassis/system products.


Definition Source

ifIndex IF-MIB

InterfaceIndex IF-MIB

pbcModuleRegs PBC-ENT-MIB

pbcManagement PBC-ENT-MIB

pbcCaps PBC-ENT-MIB

OBJECT-GROUP SNMPv2-CONF

AGENT-CAPABILITIES SNMPv2-CONF

MODULE-COMPLIANCE SNMPv2-CONF

TimeTicks SNMPv2-SMI

Unsigned32 SNMPv2-SMI

OBJECT-TYPE SNMPv2-SMI


DisplayString SNMPv2-TC

DateAndTime SNMPv2-TC

TEXTUAL-CONVENTION SNMPv2-TC



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

16

Textual Conventions

Name: PortType

Syntax: Enumerated

OBJECT IDENTIFIERS

Identifier Registration

pbcGeneric 1.3.6.1.4.1.5987.2.1

pbcChassis 1.3.6.1.4.1.5987.2.1.1

pbcGenericConformance 1.3.6.1.4.1.5987.2.1.2

pbcGenericGroups 1.3.6.1.4.1.5987.2.1.2.1

pbcGenericCompliance 1.3.6.1.4.1.5987.2.1.2.2

pbcChassis

Name Syntax Access Registration

pbcChassisEntityIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.1

pbcChassisOperStatus Enumerated read-only 1.3.6.1.4.1.5987.2.1.1.2

pbcChassisSlots SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.3

pbcContactInfo Octet String read-only 1.3.6.1.4.1.5987.2.1.1.4

pbcHostName Octet String read-write 1.3.6.1.4.1.5987.2.1.1.5

pbcDomainName Octet String read-write 1.3.6.1.4.1.5987.2.1.1.6

pbcDateTimeOfLastChange Octet String read-only 1.3.6.1.4.1.5987.2.1.1.7

pbcCardIfIndexTableNumEntries SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.8


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


Table: pbcCardIfIndexTable

For each ifIndex currently exposed by the system, this table will provide an association to the physical and logical objects which are related to it.

Table: pbcCardTable

Chassis card table.

PbcCardIfIndexEntry


pbcCardIfCardIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.9.1.1

pbcCardIfPortNumber SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.9.1.2

pbcCardIfPortType Enumerated read-only 1.3.6.1.4.1.5987.2.1.1.9.1.3

pbcCardIfSlotNumber SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.9.1.4

pbcCardAdminStatus Enumerated read-write 1.3.6.1.4.1.5987.2.1.1.9.1.5

pbcCardIfPortIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.9.1.6

pbcChassis


pbcCardTableNumEntries SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.10

PbcCardEntry


pbcCardSlotNumber SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.11.1.1

pbcCardEntityIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.11.1.2

pbcCardOperStatus Enumerated read-only 1.3.6.1.4.1.5987.2.1.1.11.1.3

pbcCardUpTime Timeticks read-only 1.3.6.1.4.1.5987.2.1.1.11.1.4

pbcCardnvRAMSize SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.11.1.5

pbcCardNumPorts SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.11.1.6



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

18

Table: pbcCardPortTable

Describes the ports on a particular card and their current status.

Table: pbcPortIfTable

Lists the interfaces (ifIndex values) associated with a specific port.

PBC-GENERIC-MIB Object Details

pbcChassisEntityIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.1Access: read-onlyReference: NoneDescription: entPhysicalIndex of the chassis' entry in the Entity MIB's (RFC2737) entPhysicalTable or '0', if none.

pbcChassisOperStatus

Registration: 1.3.6.1.4.1.5987.2.1.1.2Access: read-onlyReference: NoneDescription: Chassis' current operational status.

pbcChassisSlots

Registration: 1.3.6.1.4.1.5987.2.1.1.3Access: read-onlyReference: NoneDescription: Number of slots in this chassis, or '0' if neither applicable nor determinable.

PbcCardPortEntry


pbcCardPortStatus Enumerated read-only 1.3.6.1.4.1.5987.2.1.1.12.1.1

pbcCardPortEntityIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.1.1.12.1.2

PbcPortIfEntry


pbcPortIfIndex Integer Range read-only 1.3.6.1.4.1.5987.2.1.1.13.1.1


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


pbcContactInfo

Registration: 1.3.6.1.4.1.5987.2.1.1.4Access: read-onlyReference: NoneDescription: Pacific Broadband contact information.

pbcHostName

Registration: 1.3.6.1.4.1.5987.2.1.1.5Access: read-writeReference: NoneDescription: Name of this system.

pbcDomainName

Registration: 1.3.6.1.4.1.5987.2.1.1.6Access: read-writeReference: NoneDescription: Domain name for this host.

pbcDateTimeOfLastChange

Registration: 1.3.6.1.4.1.5987.2.1.1.7Access: read-onlyReference: NoneDescription: Date and time of last change to either the configuration or the software.

pbcCardIfIndexTableNumEntries

Registration: 1.3.6.1.4.1.5987.2.1.1.8Access: read-onlyReference: NoneDescription: Number of entries currently in the pbcCardIfIndexTable. This should be the same number as there are entries in the ifTable.

pbcCardIfCardIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.1Access: read-onlyReference: NoneDescription: Index of the card in the Chassis pbcCardTable which contains this interface or '0' if not applicable.

pbcCardIfPortNumber

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.2Access: read-onlyReference: NoneDescription: Chassis port number, unique per port on a given card for the same interface type. If pbcCardIfPortNumber is not applicable to the card, then the object instance won't be populated.

pbcCardIfPortType

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.3Access: read-onlyReference: NoneDescription: The type of port associated with this ifIndex: 0 = Not Applicable 1 = Downstream 2 = Upstream 3 = Fast Ethernet 4 = Gigabit Ethernet 5 = 10 Gigabit Ethernet 6 = RS-232



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

20

pbcCardIfSlotNumber

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.4Access: read-onlyReference: NoneDescription: Chassis slot number, or '0' if neither applicable nor determinable.

pbcCardAdminStatus

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.5Access: read-writeReference: NoneDescription: The desired state of the card. When a card/module initializes, its initial pbcCardAdminStatus is down(2). As a result of either explicit management action or per configuration information retained by the managed system, pbcCardAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state). If a management application writes reset(4) to this object, the card will initiate a full re-initialization.

pbcCardIfPortIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.9.1.6Access: read-onlyReference: NoneDescription: The system unique port index number for the physical port associated with this ifIndex.

pbcCardTableNumEntries

Registration: 1.3.6.1.4.1.5987.2.1.1.10Access: read-onlyReference: NoneDescription: Number of entries currently in the pbcCardTable.

pbcCardSlotNumber

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.1Access: read-onlyReference: NoneDescription: Slot number relative to the containing card or chassis, or '0' if neither applicable nor determinable.

pbcCardEntityIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.2Access: read-onlyReference: NoneDescription: entPhysicalIndex of this card's entry in the Entity MIB's (RFC2737) entPhysicalTable or '0', if none.

pbcCardOperStatus

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.3Access: read-onlyReference: NoneDescription: The operational status of the card. pbcCardOperStatus is operational(2) when a card is recognized by the device and is enabled for operation. pbcCardOperStatus is disabled(3) if the card is not recognized by the device, or if it is not enabled for operation. pbcCardOperStatus is standby(4) if the card is enabled and acting as a standby/redundant slave.


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


pbcCardUpTime

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.4Access: read-onlyReference: NoneDescription: The value of sysUpTime for this management entity, when this card was last (re-)initialized.

pbcCardnvRAMSize

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.5Access: read-onlyReference: NoneDescription: Amount of non-volatile RAM in bytes.

pbcCardNumPorts

Registration: 1.3.6.1.4.1.5987.2.1.1.11.1.6Access: read-onlyReference: NoneDescription: Number of ports on this card, or '0' if no ports or not applicable or determinable.

pbcCardPortStatus

Registration: 1.3.6.1.4.1.5987.2.1.1.12.1.1Access: read-onlyReference: NoneDescription: The current operational status of this port.

pbcCardPortEntityIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.12.1.2Access: read-onlyReference: NoneDescription: entPhysicalIndex of this port's entry in the Entity MIB's (RFC2737) entPhysicalTable or '0', if none.

pbcPortIfIndex

Registration: 1.3.6.1.4.1.5987.2.1.1.13.1.1Access: read-onlyReference: NoneDescription: ifIndex associated with this port or '-1', if none.


MIB Module PBC-CMTS-MIB

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

22


The PBC-CMTS-MIB that follows has been formatted to enhance readability. It was parsed from the actual PBC-CMTS-MIB file that is written in compliance with the Structure of Management Information, Version 2.


Last Updated: 200106211721ZOrganization: Pacific Broadband CommunicationsContact: Contact: Customer Support Group Purpose: This module defines all management objects which are common to PBC CMTS products.


Definition Source

ifIndex IF-MIB

InterfaceIndex IF-MIB



pbcCaps PBC-ENT-MIB

pbcCardIfPortIndex PBC-GENERIC-MIB

OBJECT-GROUP SNMPv2-CONF


MODULE-COMPLIANCE SNMPv2-CONF

NOTIFICATION-GROUP SNMPv2-CONF

IpAddress SNMPv2-SMI

Integer32 SNMPv2-SMI

Unsigned32 SNMPv2-SMI

Gauge32 SNMPv2-SMI

Counter32 SNMPv2-SMI

OBJECT-TYPE SNMPv2-SMI


NOTIFICATION-TYPE SNMPv2-SMI

MacAddress SNMPv2-TC

DateAndTime SNMPv2-TC

RowStatus SNMPv2-TC

TruthValue SNMPv2-TC

TEXTUAL-CONVENTION SNMPv2-TC


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


Textual Conventions

Name: TenthdBmV

Syntax: Integer32

Name: TenthdB

Syntax: Integer32

Name: TenthdBmVPerHz

Syntax: Integer32

OBJECT IDENTIFIERS


pbcCmts 1.3.6.1.4.1.5987.2.2

pbcCmtsIfMibExtendedObjects 1.3.6.1.4.1.5987.2.2.1

pbcGeneral 1.3.6.1.4.1.5987.2.2.1.1

pbcDownStreamMgmt 1.3.6.1.4.1.5987.2.2.1.2

pbcUpStreamMgmt 1.3.6.1.4.1.5987.2.2.1.3

pbcCmtsCableSpectrumManagement 1.3.6.1.4.1.5987.2.2.2

pbcCmtsSpectrumAnalysisMgmt 1.3.6.1.4.1.5987.2.2.2.2

pbcCmtsSpectrumAnalysisObjects 1.3.6.1.4.1.5987.2.2.2.2.1

pbcCmtsSpectrumAnalysisNotificationEnables 1.3.6.1.4.1.5987.2.2.2.2.2

pbcCmtsSpectrumAnalysisNotificationPrefix 1.3.6.1.4.1.5987.2.2.2.2.3

pbcCmtsSpectrumAnalysisNotifications 1.3.6.1.4.1.5987.2.2.2.2.3.1

pbcCmtsConformance 1.3.6.1.4.1.5987.2.2.3

pbcCmtsGroups 1.3.6.1.4.1.5987.2.2.3.1

pbcCmtsCompliances 1.3.6.1.4.1.5987.2.2.3.2

pbcDownStreamMgmt


pbcCmtsIfDownstreamNumEntries SYNuns32 read-only 1.3.6.1.4.1.5987.2.2.1.2.1



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

24

Table: pbcCmtsIfDownstreamChannelTable

PBC-specific management objects associated with downstream channels.

Table: pbcCmtsIfUpstreamChannelTable

PBC-specific management objects associated with upstream channels.

PbcCmtsIfDownstreamChannelEntry


pbcCmtsIfDownstreamIfTxPower Enumerated read-only 1.3.6.1.4.1.5987.2.2.1.2.2.1.1

pbcUpStreamMgmt


pbcCmtsIfUpstreamNumEntries SYNuns32 read-only 1.3.6.1.4.1.5987.2.2.1.3.1

PbcCmtsIfUpstreamChannelEntry


pbcCmtsIfUpstreamPort Integer32 read-write 1.3.6.1.4.1.5987.2.2.1.3.2.1.1

pbcCmtsIfUpstreamOperMode Enumerated read-write 1.3.6.1.4.1.5987.2.2.1.3.2.1.2

pbcCmtsIfUpstreamCmdRcvdPwr Integer32 read-write 1.3.6.1.4.1.5987.2.2.1.3.2.1.3

pbcCmtsIfUpstreamPowerLevel Integer32 read-only 1.3.6.1.4.1.5987.2.2.1.3.2.1.4

pbcCmtsIfUpstreamMER Integer32 read-only 1.3.6.1.4.1.5987.2.2.1.3.2.1.5

pbcCmtsIfUpstreamHcsErrors Counter32 read-only 1.3.6.1.4.1.5987.2.2.1.3.2.1.6

pbcCmtsIfUpstreamCrcErrors Counter32 read-only 1.3.6.1.4.1.5987.2.2.1.3.2.1.7

pbcCmtsIfUpstreamCER cSYNgauge32 read-only 1.3.6.1.4.1.5987.2.2.1.3.2.1.8


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


Table: pbcSpectrumAnalysisRFInputTable

There is an entry in this table for each upstream input connector on each DOCSIS Module in the CMTS. Each port is uniquely identified within the CMTS by its pbcCardIfPortIndex value.

This index object is defined under the generic chassis management section of the PBC private MIB tree.

Table: pbcSpectrumAnalysisArrayIndexTable

The table serves as an index, with status, into the pbcSpectrumAnalysisDataTable, thus uniquely identifying all of the data points which constitute one spectral sweep.

PbcSpectrumAnalysisRFInputEntry


pbcSpectrumAnalysisEnable Enumerated read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.1

pbcSpectrumAnalysisCmdStatus Enumerated read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.2

pbcSpectrumAnalysisIntegrationLen SYNuns32 read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.3

pbcSpectrumAnalysisFreqStep Enumerated read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.4

pbcSpectrumAnalysisFreqMin SYNuns32 read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.5

pbcSpectrumAnalysisFreqMax SYNuns32 read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.6

pbcSpectrumAnalysisArraySize cSYNuns32 read-write 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.7

pbcSpectrumAnalysisActiveArray SYNuns32 read-only 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.8

PbcSpectrumAnalysisArrayIndexEntry


pbcSpectrumAnalysisArrayIndex SYNuns32 read-only 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.1

pbcSpectrumAnalysisArrayStatus Enumerated read-write 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.2

pbcSpectrumAnalysisArrayScanStart Octet String read-only 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.3

pbcSpectrumAnalysisArrayScanStop Octet String read-only 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.4



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

26

Table: pbcSpectrumAnalysisDataTable

The Frequency-Power tuples are stored in this table. The maximum number of elements is determined by the size of the frequency step and the RF range to be scanned and can therefore not exceed 1850.

Table: pbcCmtsSpectrumAnalysisNotificationTable

Allows specific 'sweep complete' trap recipients to be specified on a per-port basis.

PbcSpectrumAnalysisDataEntry


pbcSpectrumAnalysisFrequency SYNuns32 read-only 1.3.6.1.4.1.5987.2.2.2.2.1.3.1.1

pbcSpectrumAnalysisPower Integer32 read-only 1.3.6.1.4.1.5987.2.2.2.2.1.3.1.2

PbcCmtsSpectrumAnalysisNotificationEntry


pbcCmtsSpectrumAnalysisEnableSweepNotification Enumerated read-write 1.3.6.1.4.1.5987.2.2.2.2.2.1.1.1

pbcSweepNotificationRecipient OID read-write 1.3.6.1.4.1.5987.2.2.2.2.2.1.1.2


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


PBC-CMTS-MIB Object Details

pbcCmtsIfDownstreamNumEntries

Registration: 1.3.6.1.4.1.5987.2.2.1.2.1Access: read-onlyReference: NoneDescription: Number of downstream channels represented in the downstream channel table.

pbcCmtsIfDownstreamIfTxPower

Registration: 1.3.6.1.4.1.5987.2.2.1.2.2.1.1Access: read-onlyReference: NoneDescription: Intermediate Frequency (IF) signal power being supplied to the upconverter on this channel.

pbcCmtsIfUpstreamNumEntries

Registration: 1.3.6.1.4.1.5987.2.2.1.3.1Access: read-onlyReference: NoneDescription: Number of upstream channels in the upstream channel table.

pbcCmtsIfUpstreamPort

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.1Access: read-writeReference: NoneDescription: Associates the upstream channel with one of the physical upstream cable connectors. A value of -1 indicates that the channel currently is not associated with any port.

pbcCmtsIfUpstreamOperMode

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.2Access: read-writeReference: NoneDescription: Controls the usage of this channel as follows: 1 = available (for use) 2 = standby (for redundancy purposes) 3 = inUse (channel is configured for data) 4 = scanning (doing dedicated spectral analysis) 5 = unlicensed (a 'key' is required to access the channel)

pbcCmtsIfUpstreamCmdRcvdPwr

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.3Access: read-writeReference: NoneDescription: Commanded received power.

pbcCmtsIfUpstreamPowerLevel

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.4Access: read-onlyReference: NoneDescription: Upstream's sample-based measured received signal power.



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

28

pbcCmtsIfUpstreamMER

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.5Access: read-onlyReference: NoneDescription: Upstream channel's modulation error ratio expressed in dB.

pbcCmtsIfUpstreamHcsErrors

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.6Access: read-onlyReference: NoneDescription: Channel's HCS errors detected.

pbcCmtsIfUpstreamCrcErrors

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.7Access: read-onlyReference: NoneDescription: CRC errors detected on this channel.

pbcCmtsIfUpstreamCER

Registration: 1.3.6.1.4.1.5987.2.2.1.3.2.1.8Access: read-onlyReference: NoneDescription: Percentage of codewords that had unrecoverable errors.

pbcSpectrumAnalysisEnable

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.1Access: read-writeReference: NoneDescription: True ('1') enables spectrum estimation. This should be set only after setting the other parameters affecting the scan. After setting this 'true', pbcSpectrumAnalysisCmdStatus will reflect initial and, ultimately, final status of the sweep attempt.

pbcSpectrumAnalysisCmdStatus

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.2Access: read-writeReference: NoneDescription: Result of pbcSpectrumAnalysisEnable command.

pbcSpectrumAnalysisIntegrationLen

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.3Access: read-writeReference: NoneDescription: This specifies the number of estimates over which the peak of the noise power is calculated.

pbcSpectrumAnalysisFreqStep

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.4Access: read-writeReference: NoneDescription: The frequency step for scanning which defines the frequency resolution. The choices are: 20KHz, 40KHz, 80KHz and 160KHz.


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••


pbcSpectrumAnalysisFreqMin

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.5Access: read-writeReference: NoneDescription: The low end of the frequency range being scanned. The lowest legal value, per both the DOCSIS and Euro-DOCSIS standards, is 5MHz.

pbcSpectrumAnalysisFreqMax

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.6Access: read-writeReference: NoneDescription: Top end of the frequency range being scanned. For DOCSIS, the maximum is 42MHz and for Euro-DOCSIS it is 65MHz.

pbcSpectrumAnalysisArraySize

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.7Access: read-writeReference: NoneDescription: This variable holds/specifies the number of scan data tables to be allocated to this particular scan instance. The size of each table and, therefore, the total amount of buffer space required is determined by the other scan parameters. If the agent is unable to allocate that amount of space, a status of 'noResources' will be returned in pbcSpectrumAnalysisCmdStatus following the setting of pbcSpectrumAnalysisEnable.

If successful, this becomes the total number of table entries in pbcSpectrumAnalysisArrayIndexTable.

A size of '2' is the absolute minimum to permit the agent to fill one table with data points while the management application is 'draining' the other.

pbcSpectrumAnalysisActiveArray

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.1.1.8Access: read-onlyReference: NoneDescription: Contains the pbcSpectrumAnalysisArrayIndex number of the data table currently being filled with spectral data points.


Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.1Access: read-onlyReference: NoneDescription: Index number of this data table.

pbcSpectrumAnalysisArrayStatus

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.2Access: read-writeReference: NoneDescription: The operational status of this data table. The management application which is reading the spectrum monitoring data should, after reading all the data entries associated with this array (table),set this variable back to 'available'.



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

30

pbcSpectrumAnalysisArrayScanStart

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.3Access: read-onlyReference: NoneDescription: The date and time when this table's spectral sweep began.

pbcSpectrumAnalysisArrayScanStop

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.2.1.4Access: read-onlyReference: NoneDescription: The date and time when this table's spectral sweep was completed or stopped for some other reason.

pbcSpectrumAnalysisFrequency

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.3.1.1Access: read-onlyReference: NoneDescription: The frequency that was sampled.

pbcSpectrumAnalysisPower

Registration: 1.3.6.1.4.1.5987.2.2.2.2.1.3.1.2Access: read-onlyReference: NoneDescription: Measured power in tenths of a dBmV/Hz.

pbcCmtsSpectrumAnalysisEnableSweepNotification

Registration: 1.3.6.1.4.1.5987.2.2.2.2.2.1.1.1Access: read-writeReference: NoneDescription: True ('1') enables 'sweep complete' notifications so that the receiver knows it may/should retrieve the current spectral data points.

pbcSweepNotificationRecipient

Registration: 1.3.6.1.4.1.5987.2.2.2.2.2.1.1.2Access: read-writeReference: NoneDescription: The IP address of the management station wishing to receive the 'sweep complete' notifications from this system for this monitored port.


••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

MIB Module PBC-KODIAK-M-G10-MIB


The PBC-KODIAK-M-G10-MIB that follows has been formatted to enhance readability. It was parsed from the actual PBC-KODIAK-M-G10-MIB file that is written in compliance with the Structure of Management Information, Version 2.


Last Updated: 200106211721ZOrganization: Pacific Broadband CommunicationsContact: Contact: Customer Support Group Purpose: MIB Module for the Kodiak M-G10 CMTS.


Definition Source



pbcProducts PBC-ENT-MIB

pbcCaps PBC-ENT-MIB

pbcReqs PBC-ENT-MIB



OBJECT IDENTIFIERS


pbcKodiakMG10Cmts 1.3.6.1.4.1.5987.3.1



••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

32

••••••••••••••••••••••••••••••••••••••••••••••••

Index 33

IndexIndex

AAGENT-CAPABILITIES..................................................11

BBaseline Privacy Interface..............................................7

Cchannels ........................................................................2chassis...........................................................................9Chassis Control Module .................................................3CLI.................................................................................3CLI see Command Line InterfaceCM.............................................................................4, 8Command Line Interface ...............................................3CRC ...............................................................................4

DDeprecated....................................................................8Diagnostics Server .........................................................4DOCSIS .........................................................................7

Cable Modems .......................................................4MAC .......................................................................4

DOCSIS Module .........................................................3, 8document conventions ..................................................x

Eevent .............................................................................3experimental ...............................................................11

GG10 CMTSfeatures ..................................................................2functional overview................................................1

HHCS ...............................................................................4headend ........................................................................1

hybrid-fiber/coax ...........................................................4

I inform ...........................................................................3

LLocal Event Log .............................................................4

MMAC see Media Access Controlmanagement information..........................................3, 7Media Access Control ....................................................4MIB........................................................................3, 4, 7MIBs

BRIDGE-MIB ...........................................................7DOCS-BPI-MIB ....................................................7, 8DOCS-CABLE-DEVICE-MIB..................................7, 8DOCS-IF-MIB ......................................................7, 8enterprise MIB........................................................9Entity MIB ..............................................................7ETHERLIKE-MIB .....................................................7IF-MIB.....................................................................7IP-MIB ....................................................................7PBC-CMTS-MIB .................................................9, 22PBC-ENT-MIB..............................................9, 14, 31PBC-GENERIC-MIB............................................9, 15PBC-KODIAK-M-G10-MIB........................................9SNMPv2-CONF .......................................................6SNMPv2-MIB ..........................................................6SNMPv2-PDU..........................................................6SNMPv2-SMI...........................................................6SNMPv2-TC ............................................................6SNMPv2-TM............................................................6TCP-MIB .................................................................7UDP-MIB.................................................................7

MODULE-COMPLIANCE...............................................11Multicast SIDs ................................................................8

••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Index

Juniper Networks G10 CMTS SNMP and Enterprise MIB Specification34

NNetwork Management System .................................. 4, 8Network Operations Center........................................... 4NMS .............................................................................. 6NMS Management Server .............................................. 4NMS see Network Management SystemNOC see Network Operations Centernotification.............................................................. 3, 13

OObject Identifier ............................................................ 9Objects

cmtsAgentCaps .................................................... 12pbcCaps ............................................................... 11pbcCmts............................................................... 12pbcExpr ............................................................... 11pbcGeneric........................................................... 12pbcGenericSystemAgentCapsR2........................... 12pbcKodiakMG10AgentCaps .................................. 12pbcManagement ............................................ 11, 12pbcProducts ................................................... 11, 12pbcRegs ............................................................... 11pbcReqs ............................................................... 11

Obsolete........................................................................ 8OID ......................................................................... 9, 12

PpacificBroadband ........................................................ 10pacificBroadband Module.............................................. 9PHY............................................................................... 4Protocol Data Units ....................................................... 4

QQoS see Quality of Service

Rregistration.................................................................... 8RFC 1493 ...................................................................... 7RFC 1905 ...................................................................... 6RFC 1906 ...................................................................... 6RFC 1907 ...................................................................... 6RFC 2011 ...................................................................... 7RFC 2012 ...................................................................... 7RFC 2013 ...................................................................... 7RFC 2233 ...................................................................... 7RFC 2578 ...................................................................... 6RFC 2579 ...................................................................... 6RFC 2580 ...................................................................... 6RFC 2665 ...................................................................... 7RFC 2669 ...................................................................... 7RFC 2670 ...................................................................... 7RFC 2737 ...................................................................... 7

RFC 3083 ......................................................................7

Sservice flows..................................................................2SIDs...............................................................................8signal-to-noise ratio .......................................................4SNMP ........................................................................3, 4

agent..................................................................3, 4entity......................................................................3manager.............................................................3–4

Structure of Management Information ......14, 15, 22, 31SYSLOG .........................................................................4system capacity.............................................................2

Ttables...........................................................................13trap ...............................................................................3

Uupconverters .................................................................8

Documents

Juniper Networks G10 CMTS · Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 Part Number: 530-006461-01, Revision 2 Juniper Networks