bsr 2000 - release 1.1 - snmp configuration and management guide

BSR 2000 SNMP MIB Reference Guide

526362-001-00 Rev BRelease 1.1

NoticeCopyright © 2011Motorola Mobility, Inc.All rights reserved

No part of this publication my be reproduced in any form or by any means or used to make and any derivative work (such as translation, transformation or adaptation) without written permission from Motorola Mobility, Inc.

Motorola reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Motorola to provide notification of such revision or change. Motorola provides this guide without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Motorola may make improvements or changes in the product(s) described in this manual at any time.

Motorola and the stylized M logo are registered trademarks of Motorola, Inc. Broadband Services Router, BSR, BSR 64000, RiverDelta, and SmartFlow are trademarks of Motorola, Inc. All other trademarks and registered trademarks are the property of their respective owners.

Caring for the Environment by RecyclingWhen you see this symbol on a Motorola product, do not dispose of the product with residential or commercial waste.Recycling your Motorola EquipmentPlease do not dispose of this product with your residential or commercial waste. Some countries or regions, such as the European Union, have set up systems to collect and recycle electrical and electronic waste items. Contact your local authorities for information about practices established for your region. If collection systems are not available, call Motorola Customer Service for assistance.

526362-001-00 Rev BRelease 1.1

Published: 2/11

526362-001-00 Rev B iii

Contents

PrefaceScope .............................................................................................................................................. vAudience......................................................................................................................................... vDocumentation Set ......................................................................................................................... vConventions...................................................................................................................................viNotes, Cautions, Warnings ...........................................................................................................viiIf You Need Help.........................................................................................................................viii

1 Introduction to the Simple Network Management ProtocolOverview .....................................................................................................................................1-1About SNMP MIBs.....................................................................................................................1-2SNMP Commands.......................................................................................................................1-3How a MIB is Organized.............................................................................................................1-3

Defining MIB Objects ......................................................................................................1-4Obtaining SNMP MIB Archive Files for the BSR......................................................................1-5

2 Standard MIB SupportOverview .....................................................................................................................................2-1

Accessing MIBs with RFC Numbers ...............................................................................2-1Accessing MIBs through CableLabs ................................................................................2-1

MIB II..........................................................................................................................................2-2Transmission ...............................................................................................................................2-5SNMP..........................................................................................................................................2-6Experimental ...............................................................................................................................2-7

BSR 2000 SNMP MIB Reference Guide Release 1.1

iv 526362-001-00 Rev B

3 Motorola Private MIBSOverview .....................................................................................................................................3-1

4 MIB TrapsOverview .....................................................................................................................................4-1

Accessing MIB traps with a DOCSIS Name....................................................................4-1Accessing MIB traps with RFC Numbers ........................................................................4-2

DOCSIS and Standard MIB Trap Information............................................................................4-3Motorola Private Trap Information .............................................................................................4-5Trap Severity Levels ...................................................................................................................4-8

Private Traps and Their Severity Levels ........................................................................4-10Enabling or Disabling Traps......................................................................................................4-13Filtering Traps ...........................................................................................................................4-14

5 Using a MIB Browser to Access MIB VariablesOverview .....................................................................................................................................5-1About MIB Browsers ..................................................................................................................5-2Contacting the Device .................................................................................................................5-2Browsing the MIB Tree...............................................................................................................5-3SNMP Get/Get Next....................................................................................................................5-5SNMP Set ....................................................................................................................................5-6Compiling and Importing New SNMP MIBs .............................................................................5-6Sample Tasks...............................................................................................................................5-6

Accessing MIB Variable Information...............................................................................5-7Sample Task .......................................................................................................5-7

Changing MIB Variables ................................................................................................5-11Sample Task .....................................................................................................5-11

Index

526362-001-00 Rev B v

Preface

ScopeThis document provides descriptions of the standard SNMP and private MIBs supported by the Motorola™ Broadband Services Router™ 2000 (BSR 2000™). It also provides a tutorial on how to “walk” the MIBs using an SNMP MIB browser and provides example tasks that can be performed using the SNMP or private MIBs.

AudienceThis document is for use by those persons who will configure and manage the BSR 2000™ product. Only trained service personnel should configure and manage the BSR 2000.

Documentation SetThe following documents comprise the BSR 2000 documentation set:

n BSR 2000 Command Reference Guide

This document contains the Command Line Interface (CLI) commands for managing, configuring, and maintaining the BSR 2000.

n BSR 2000 Configuration and Management Guide

This document provides the instructions and procedures for configuring and managing the BSR 2000.

n BSR 2000 Installation Guide

This document describes how to install the BSR 2000 product.


vi 526362-001-00 Rev B

n BSR 2000 Release Notes

These documents provide information about features not described or incorrectly documented in the main documentation set; known problems and anomalies; product limitations; and problem resolutions.

n BSR 2000 SNMP MIB Reference Guide

This document describes the Simple Network Management Protocol (SNMP) MIBs; provides information that describes standard and proprietary MIB support; describes how to walk the MIBs and how to compile and load the SNMP MIBs. It also provides task examples.

ConventionsThis document uses the conventions in the following table:

Convention Example Explanation

angle brackets < > ping <ip-address> ping 54.89.145.71

Arguments in italic and enclosed by angle brackets must be replaced by the text the argument represents. In the example, 54.89.345.71 replaces <ip-address>. When entering the argument, do not type the angle brackets.

bar brackets [ ] disable [level] Bar brackets enclose optional arguments. The example indicates you can issue the disable command with or without specifying a level. Some commands accept more than one optional argument. When entering the argument, do not type the bar brackets.

bold text cable relay-agent-option Boldface text must be typed exactly as it appears.

brace brackets {} page {on | off} Brace brackets enclose required text. The example indicates you must enter either on or off after page. The system accepts the command with only one of the parameters. When entering the text, do not type the brace brackets.

italic text boot system <filename> Italic type indicates variables for which you supply values in command syntax descriptions. It also indicates file names, directory names, document titles, or emphasized text.

Release 1.1 Preface

526362-001-00 Rev B vii

Notes, Cautions, WarningsThe following icons and associated text may appear in this document.

screen display Wed May 6 17:01:03 2000

This font indicates system output.

vertical bar | page {on | off} A vertical bar separates the choices when a parameter is required. The example indicates you can enter either command: page on or page offWhen entering the parameter, do not type the vertical bar or the brace brackets.

Note: A note contains tips, suggestions, and other helpful information, such as references to material not contained in the document, that can help you complete a task or understand the subject matter.

Caution: The exclamation point, within an equilateral triangle, is intended to alert the user to the presence of important installation, servicing, and operating instructions in the documents accompanying the equipment.

Warning: This symbol indicates that dangerous voltages levels are present within the equipment. These voltages are not insulated and may be of sufficient strength to cause serious bodily injury when touched. The symbol may also appear on schematics.

Convention Example Explanation


viii 526362-001-00 Rev B

If You Need HelpSupport for your BSR 2000 hardware and software is available via telephone and the Internet.

Telephone SupportIf you need assistance while working with the BSR 2000, contact the Motorola Technical Response Center (TRC):

The Motorola TRC is on call 24 hours a day, 7 days a week.

When calling for technical support, please have the following information available:

n Your customer information, including location, main contact, and telephone number

n BSR product and modulesn Detailed description of the issuen Specific information to assist with resolving the problem, including:

• BSR hostname• BSR error messages and logs• Output of BSR show tech command• Cable modem information

n List of troubleshooting steps you have performed before calling the TRC.n Current state of your BSR 2000 productn Severity of the issue you are reporting

When calling for repair or Advanced Component Exchange (ACE) replacement, please provide the following additional information:

n Output of BSR show version command, with part numbers and serial numbers of BSR components

n Shipping information for the replacement, including contact name, company name, address, phone number, and email address

U.S. 1-888-944-HELP (1-888-944-4357)

International +215-323-0044

Release 1.1 Preface

526362-001-00 Rev B ix

Online Support

Motorola BSR Customer Website The BSR customer website, http://bsr.motorola.com, is available for BSR customers with active service contracts to access the latest product information, software updates, troubleshooting information, and technical publications for the BSR 64000, BSR 2000, and BSR 1000 product line.

You may request access to the site by emailing the BSR product support team at [email protected] with the following information:

n Company namen Contact name, phone number, and email addressn Motorola Support contactn BSR product under service contract

The BSR product support team will email an invitation to you with further instructions on how to set up an account on the BSR customer information website.

526362-001-00 Rev B 1-1

1Introduction to the Simple

Network ManagementProtocol

OverviewThe Simple Network Management Protocol (SNMP) is described in the following sections:

n About SNMP MIBsn SNMP Commandsn How a MIB is Organizedn Obtaining SNMP MIB Archive Files for the BSR


1-2 526362-001-00 Rev B

About SNMP MIBsRequest for Comments (RFC) 1155 defines the Structure of Management Information (SMI) framework for using SNMP to control different types of information. SMI places objects as nodes in an object tree. The object tree groups logically related objects into subtrees. Each of these subtrees is called a Management Information Base (MIB).

A MIB is a database maintained by the device that stores all of its known management information. Each individual element of information in the MIB is called an Object. A MIB is much like an information warehouse with specific floors, aisles and racks stocked with inventory.

Request for Comments (RFC) MIBs and Internet Drafts are written by Internet Engineering Task Force (IETF) working groups and are available for public use and are often referred to as "Standard MIBs". Other MIBs have been developed by private organizations specifically for their products and are often referred to as "Private" or "Proprietary" MIBs.

The BSR supports the following Standard and Private MIBs:

n Refer to Standard MIB Support on page 2-1 for a list of Standard MIBs supported by the BSR.

n Refer to Motorola Private MIBS on page 3-1 for a list of Private MIBs supported by the BSR.

An SNMP agent is used to communicate information between a remote management system and the information database on a device. An SNMP agent accomplishes this by retrieving information from a MIB and storing information to a MIB. SNMP management follows this model:n MIBs located on the SNMP network management station describe the

information that is relayed from the SNMP agents.n The SNMP network management station or application can send queries to each

SNMP agent.n Each SNMP agent collects information about its device and provides that

information to the SNMP network management station. The agent process acts as a server in a typical client-server model.

Release 1.1 Introduction to the Simple Network Management Protocol

526362-001-00 Rev B 1-3

SNMP CommandsTable describes the SNMP Get, GetNext, and Set commands, as defined in RFC 1157, that are supported by the SNMP agent software on the BSR:

How a MIB is OrganizedBecause networking devices are made by a variety of manufacturers they must all be able to communicate with one another. The Internet standards organization requires that each network device organize its management information according to a pre-defined tree format. This tree structure branches out from the Internet layer into several subtrees, with each subtree organized into branches (groups of related information) and leaves (the individual pieces of information, or objects). Among these subtrees is an Enterprises subtree, in which private vendors can apply to the Internet Assigned Numbers Authority for a branch in which to store management information (or objects) specific to their products.

Each layer of this tree is numerically encoded, so that each group and object is identified by a unique number known as an Object Identifier (OID). This identifier is a path to the information stored as the object’s value, and provides the means by which the SNMP agent is able to locate the object in a device’s MIB. An ASCII name is also assigned to each branch or OID, for convenience in identifying a management object. For example, the MIB II object ipForwarding is identified as follows:

Numeric OID: 1.3.6.1.2.1.4.1

ASCII string: iso/org/dod/internet/mgmt/mib-2/ip/ipForwarding

Table 1-1 SNMP Commands

Command Description

Get Retrieves the value of a specific object from one of the supported MIBs.

GetNext Traverses the MIB tree to retrieve the next object’s management information.

Set Modifies the values of MIB objects. The BSR 2000 private MIBs and several objects in the standard MIBs allow you to configure the BSR 2000 from an SNMP management station on the network.


1-4 526362-001-00 Rev B

Some objects may occur multiple times for a single device. Objects of this type are called tabular objects and are organized in tables. Each occurrence of a tabular object is called an instance, and each instance also numerically encoded. For example, if you were querying a two-port bridge’s interface table, there would be two instances (values) returned for each object in the table (one for each port), and each instance would have a unique instance value appended to the object’s OID.

Defining MIB ObjectsMIB objects represent data that the device can retrieve or configuration information that can be modified. n RFC 1155 (Structure and Identification of Management Information for TCP/

IP-based Internets) describes the layout and encoding of exchanged data objects. The SMI uses the ISO standard ASN.1 (Abstract Syntax Notation One) to define a method for describing a hierarchical name space for managed information.

n RFC 1212 (Concise MIB Definitions) is an easier-to-read form used in most standard MIBs today. It defines the private enterprise MIB.

A MIB object is defined and identified by the following:

OBJECT_TYPE The object’s ASN.1 (Abstract Syntax Notation.1) defined name and type.

SYNTAX How the data represented by this object is structured: Integer, Octet String, Object Identifier, Null, Sequence, Sequence of, IpAddress, NetworkAddress, Counter, Gauge, TimeTicks, Opaque, or some other user-defined data type.

ACCESS The level of management access available for this specific object: read-only (instances of the object may be read, but not set), read-write (instances of the object may be read or set), write-only (instances of the object may be set but not read), or not-accessible (instances of the object may not be read or set). Note that this does not designate the level of access provided by the community name you used to contact the device, but the maximum level of access available for the object by definition.

Release 1.1 Introduction to the Simple Network Management Protocol

526362-001-00 Rev B 1-5

The following is an example of the MIB object ifNumber which is part of the Interfaces group of RFC 1213 (Management Information Base for Network Management of TCP/IP-based internets:MIB-II.)

ifNumber OBJECT-TYPESYNTAX INTEGERACCESS read-onlySTATUS mandatoryDESCRIPTION

"The number of network interfaces (regardless of their current state) present on this system.”

::= { interfaces 1 }

Obtaining SNMP MIB Archive Files for the BSRContact Motorola Technical Response Center (TRC) to obtain the SNMP MIB archive files for use with the BSR 2000 Release 4.1 software. Refer to If You Need Help on page viii for more information.

: Indicates whether a managed device is required to implement this object in its MIB. A status of mandatory indicates that the device must use this object (by convention, all MIBs adhering to the Internet-standard contain only mandatory objects); a status of optional indicates that the device may implement this object (by Internet-standard MIB convention, this is used to denote objects within an experimental MIB); and a status of obsoleted indicates that the device need no longer implement this object, as it is no longer meaningful in an Internet-standard MIB.

DESCRIPTION A brief description of the management information provided by this object.

::= The variable name of the object, in the form OBJECT TYPE OBJECT IDENTIFIER fragment.

526362-001-00 Rev B 2-1

2Standard MIB Support

OverviewThis chapter gives instructions on how to access standard MIBs and provides information for the standard MIBs supported by the BSR 2000:

Accessing MIBs with RFC NumbersFollow these steps to access MIBs with Request for Comments (RFCs) numbers:

1. Click on the blue World Wide Web link to access an RFC from the Internet Engineering Task Force (IETF) Web site:

http://www.ietf.org/rfc.html

2. Find the RFC number and enter it in the RFC number: box and click the go button. The RFC displays as a text document.

Accessing MIBs through CableLabsFollow these steps to access MIB names for the MIB-II group through CableLabs:

1. Click on the blue World Wide Web link to access the CableLabs Web site:

http://www.cablelabs.com


http://www.cablelabs.com/


2-2 526362-001-00 Rev B

2. Find the CableLabs MIB name in and enter it in the Search field and click the Search button. The document displays as a PDF in your Web browser.

MIB IITable 2-1 provides a list of MIB Request for Comments (RFCs) and/or MIB names for the MIB-II group, which includes their corresponding Internet Engineering Task Force (IETF) working groups and document titles:

Table 2-1 Supported MIB II Groups

RFC/MIB Name IETF Working Group Title

RFC 1213RFC1213-MIB

SNMP Management Information Base for Network Management of TCP/IP-based internets: MIB-II

RFC 1493BRIDGE-MIB

Bridge Sub-Working Group of the SNMP Working Group.

Definitions of Managed Objects for Bridges

RFC 1657BGP4-MIB

BGP Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2

RFC 1724RIPv2-MIB

RIP-II Routing Information Protocol Version 2 MIB Extension.

RFC 1850OSPF-MIB

OSPF OSPF Version 2 Management Information Base

RFC 1870SMTP Size Declaration

Standards Track SMTP Service Extension for Message Size Declaration

RFC 2013UDP-MIB

SNMPv2 SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2

RFC 2096IP-FORWARD-MIB

OSPF IP Forwarding Table MIB

RFC 2213INTEGRATED-SERVICES-MIB

Integrated Services Integrated Services Management Information Base using SMIv2

RFC 2493PerfHist-TC-MIB

AToMMIB and TrunkMIB Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals

Release 1.1 Standard MIB Support

526362-001-00 Rev B 2-3

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

RFC 2579 Textual Conventions for SMIv2

RFC 2863IF-MIB

Interfaces MIB The Interfaces Group MIB

CLAB-DEF-MIB IP over Cable Data Network (IPCDN)

CableLabs Definition MIB Specification

DOCS-LOAD-BAL-MIB

DOCS-TEST-MIB CableLabs DOCSIS 2.0 Testing MIB Specification

DSG-IF-MIB DOCSIS Set-top Gateway (DSG) Interface Specification

DOCSIS BPI Plus MIB (bpip_05-mib)

Management Information Base for DOCSIS Cable Modems and Cable Modem Termination Systems for Baseline Privacy Plus

RFC 3083DOCSIS Baseline Privacy MIB

Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems

DOCS-IF-EXT-MIB Extends RFC 2670 by providing:docsIfDevDocsisCapabilitydocsIfDevDocsisOperStatusdocsIfCmtsCmStatusDocsisVersion




2-4 526362-001-00 Rev B

DOCS-CABLE-DEVICE-TRAP-MIB

IPCDN (continued) Trap definitions for DOCSIS cable devices

DOCS-SUBMGT-MIB

RFC-version of Subscriber Management MIB

RFC 2669DOCS-CABLE-DEVICE-MIB

DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems

draft-ietf-ipcdn-docs-rfmibv2-13DOCSIS 2.0 Radio Frequency (RFI) MIB

Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces

draft-ietf-ipcdn-qos-mib-12.txtDOCS-QOS-MIB

Data Over Cable System Interface Specification Quality of Service Management Information Base

RFC 2737ENTITY-MIB

ENTMIB Entity MIB (Version 2)

RFC 2666ETHER-CHIPSET-MIB

802.3 Hub MIB Definitions of Object Identifiers for Identifying Ethernet Chip Sets.

RFC 2933IGMP-STD-MIB

Inter-Domain Multicast Routing (IDMR)

Internet Group Management Protocol (IGMP) MIB

RFC 2011IP-MIB

SNMPv2 SNMPv2 Management Information Base for the Internet Protocol using SMIv2. This MIB is enhanced to support sub-interfaces

RFC 2012TCP-MIB

SNMPv2 Management Information Base for the Transmission Control Protocol using SMIv2

IANAifType-MIB Internet Assigned Numbers Authority (IANA)

This MIB module defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable

IANA-RTPROTO-MIB

This MIB module defines the IANAipRouteProtocol and IANAipMRouteProtocol textual conventions for use in MIBs which need to identify unicast or multicast routing mechanisms




526362-001-00 Rev B 2-5

TransmissionTable 2-2 provides a list of MIB Request for Comments (RFCs) and/or MIB names for the Transmission group, which includes their corresponding Internet Engineering Task Force (IETF) working groups and document titles:

RFC 2932IPMROUTE-STD-MIB

IETF IDMR IPv4 Multicast Routing MIB

RFC 3291 INET-ADDRESS-MIB

Operations and Management Area

Textual Conventions for Internet Network Addresses

RFC 3289Differentiated Services MIB

Differentiated Services Management Information Base for the Differentiated Services Architecture

Table 2-2 Supported Transmission Groups

RFC/MIB NameIETF Working Group Title

RFC 2665EtherLike-MIB

Ethernet Interfaces and Hub MIB

The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol

RFC 1473PPP-IP-NCP-MIB

PPP The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol

RFC 1471PPP-LCP-MIB

The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol.




2-6 526362-001-00 Rev B

SNMPTable 2-3 provides a list of MIB Request for Comments (RFCs) and/or MIB names for the SNMP group, which includes their corresponding Internet Engineering Task Force (IETF) working groups and document titles:

Table 2-3 Supported SNMP Groups


RFC 3411SNMP-FRAMEWORK-MIB

SNMPv3 An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

RFC 3412SNMP-MPD-MIB

Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

RFC 3413SNMP-TARGET-MIB

Simple Network Management Protocol (SNMP) Applications

RFC 3414SNMP-USER-BASED-SM-MIB

User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

RFC 3415SNMP-VIEW-BASED-ACM-MIB

View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 3417Transport Mappings for SNMP MIB

Transport Mappings for the Simple Network Management Protocol (SNMP)

RFC 3418SNMP-MIB

Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

RFC 2576SNMP-COMMUNITY-MIB

Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework


526362-001-00 Rev B 2-7

ExperimentalTable 2-4 provides the MIB Request for Comment (RFC) for the Experimental group, which includes their corresponding Internet Engineering Task Force (IETF) working group and document title:

Table 2-4 Supported Experimental Groups


RFC 2934 IDMR Protocol Independent Multicast MIB for IPv4.

526362-001-00 Rev B 3-1

3Motorola Private MIBS

OverviewTable 3-1 describes the Motorola BSR 2000 Private MIBs:

Table 3-1 Motorola Private MIBs

Private MIB File Module Identities Description

rdn-cmts.mib RDN-CMTS-MIB Cable Modem Termination System (CMTS)

rdn-definitions.mib RDN-DEFINITIONS-MIBRDN-PRODUCTS-MIBRDN-CHASSIS-TYPE-MIBRDN-SLOTS-MIBRDN-MODULES-MIBRDN-PORTS-MIBRDN-SENSOR-TYPE-MIB

Definitions for Motorola products, chassis, ports, modules, etc.

rdn-dlb.mib RDN-DLP-MIB Dynamic Load Balancing MIB evenly distributes voice and/or data traffic across upstream and downstream channels within a Load Balance group.

rdn_pktcable.mib RDN-PKTCABLE-GROUP-MIB PacketCable


3-2 526362-001-00 Rev B

rdn-process.mib RDN-PROCESS-MIB Active system processes and memory usage

rdn-sensor.mib RDN-SENSOR-MIB Hardware sensors

rdn-syslog.mib RDN-SYSLOG-MIB System log

rdn.mib RDN-MIB Motorola module definitions

RDN-CABLE-SPECTRUM.mib RDN-CABLE-SPECTRUM-MIB Cable Spectrum Management for MCNS compliant Cable Modem Termination Systems (CMTS)

RDN-SpectrumGroup.mib RDN-CABLE-SPECTRUM-GROUP-MIB

Cable Spectrum Group Management for MCNS compliant Cable Modem Termination Systems (CMTS)

rdn-evtNotifications.mib RDN-EVT-NOTIFICATIONS Critical and higher level EVT notifications

Table 3-1 Motorola Private MIBs

Private MIB File Module Identities Description

Release 1.1 Motorola Private MIBS

526362-001-00 Rev B 3-3

Figure 3-1 shows the Motorola BSR 2000 Private MIB structure:

Figure 3-1 Motorola BSR 2000 Private MIB Structure

ISO (1)

ORG (3)

DoD (6)

Internet (1)

Private (4)

Enterprises (1)

RDN (4981)

rdn-cmts (2)

rdn-syslog (3)

rdn-chassis (1)

rdn-definitions (4)

RDN-CABLE-SPECTRUM (6)

rdn-SpectrumGroup (8)

rdn-sensor (5)

rdn-pktcable (7)

rdnProcessMIB (20)

rdn-evtNotifications (0)

526362-001-00 Rev B 4-1

4MIB Traps

OverviewThis chapter gives instructions on how to access both standard and private MIB traps that are supported by the BSR 2000.

Accessing MIB traps with a DOCSIS NameFollow these steps to access DOCSIS-related MIB trap names through CableLabs:

1. Click on the blue World Wide Web link to access the CableLabs Web site:

http://www.cablelabs.com

2. Find the desired MIB trap name and enter it in the Search field and click the Search button. Once you find the document, the document displays as a PDF in your Web browser.

http://www.cablelabs.com/


4-2 526362-001-00 Rev B

Accessing MIB traps with RFC NumbersFollow these steps to access MIB traps with Request for Comments (RFCs) numbers:

1. Click on the blue World Wide Web link to access an RFC from the Internet Engineering Task Force (IETF) Web site:


2. Find the desired RFC number and enter it in the field and click the go button. The RFC displays as a text document.


Release 1.1 MIB Traps

526362-001-00 Rev B 4-3

DOCSIS and Standard MIB Trap InformationTable 4-1 displays a description and the DOCSIS and Standard MIB file names that are supported by the BSR 2000. The Associated Traps Column provides the trap names for each DOCSIS and Standard MIB file:

Table 4-1 DOCSIS and Standard MIB Traps

MIB File Associated Traps

DOCS-CABLE-DEVICE-TRAP.mib docsDevCmInitTLVUnknownTrapdocsDevCmDynServReqFailTrap’docsDevCmDynServRspFailTrapdocsDevCmDynServAckFailTrapdocsDevCmBpiInitTrapdocsDevCmBPKMTrapdocsDevCmDynamicSATrapdocsDevCmDhcpFailTrapdocsDevCmSwUpgradeInitTrapdocsDevCmSwUpgradeFailTrapdocsDevCmSwUpgradeSuccessTrapdocsDevCmSwUpgradeCVCFailTrapdocsDevCmTODFailTrapdocsDevCmDCCReqFailTrapdocsDevCmDCCRspFailTrapdocsDevCmDCCAckFailTrapdocsDevCmtsInitRegReqFailTrapdocsDevCmtsInitRegRspFailTrapdocsDevCmtsInitRegAckFailTrapdocsDevCmtsDynServReqFailTrapdocsDevCmtsDynServRspFailTrapdocsDevCmtsDynServAckFailTrapdocsDevCmtsBpiInitTrapdocsDevCmtsBPKMTrapdocsDevCmtsDynamicSATrapdocsDevCmtsDCCReqFailTrapdocsDevCmtsDCCRspFailTrapdocsDevCmtsDCCAckFailTrap

rfc1657.mib bgpEstablishedbgpBackwardTransition


4-4 526362-001-00 Rev B

rfc1850.mib ospfIfStateChangeospfVirtIfStateChangeospfNbrStateChangeospfVirtNbrStateChangeospfIfConfigErrorospfVirtIfConfigErrorospfIfAuthFailureospfVirtIfAuthFailureospfIfRxBadPacketospfVirtIfRxBadPacketospfTxRetransmitospfVirtIfTxRetransmitospfOriginateLsaospfMaxAgeLsaospfLsdbOverflowospfLsdbApproachingOverflow

rfc2737.mib entConfigChange

rfc2787.mib vrrpTrapNewMastervrrpTrapAuthFailure

rfc2863.mib linkDownlinkUp

rfc2934.mib pimNeighborLoss

rfc3418.mib coldStartwarmStartauthenticationFailure

Table 4-1 DOCSIS and Standard MIB Traps

MIB File Associated Traps


526362-001-00 Rev B 4-5

Motorola Private Trap InformationTable 4-2 describes each applicable Motorola Private MIB and its associated trap(s):

Table 4-2 Motorola Private Traps

MIB File Trap Name

rdn-chassis.mib chassisPowerFailureTrap

chassisFanFailureTrap

rdnBSRSrmSwitchoverTrap

rdnLinkUpTrap

rdnLinkDownTrap

rdn-cmts.mib rdnCmtsCmRegisteredNotification Trap

rdnCmtsCmDeregisteredNotification Trap

rdnCmtsUpstreamIfLinkUpTrap

rdnCmtsUpstreamIfLinkDownTrap

rdn_pktcable.mib rdnPktDQoSCopsTrap

rdnPktDQoSResReqTrap

rdnPktDQoSEmergencyTrap

rdnPktESTrap

rdn-sensor.mib rdnSensorThresholdExceeded

rdn-syslog.mib rdnSyslogSeverityTrap

RDN-CABLE-SPECTRUM.mib rdnFlapListNotification

rdnFlapModemNotification


4-6 526362-001-00 Rev B

rdn-evtNotifications.mib

Note: Refer to Configuring EVT Logging Chapter in the BSR 2000 Configuration and Management Guide for more information on configuring EVT traps.

rdnEvtMacrtrGetQIdFailure

rdnEvtMacrtrUnknownCase

rdnEvtMacrtrMsgQReceiveFailure

rdnEvtMacrtrRdbDefineTableFailure

rdnEvtMacrtrRxUnexpectedMsgType

rdnEvtMacrtrRegTaskMonFailure

rdnEvtMacrtrInvalidFuncParam

rdnEvtMacrtrUnknownCmId

rdnEvtBpiLoadAuthRunRecFailure

rdnEvtBpiLoadTekRunRecFailure

rdnEvtBpiLoadCmCertificateFailure

rdnEvtDraTaskSpawnFailure

rdnEvtDraMsgQCreateFailure

rdnEvtDraMsgQReceiveFailure

rdnEvtDraRegTaskMonFailure

rdnEvtDraCreateRdbFailure

rdnEvtDraRxUnexpectedMsgType

rdnEvtDraRxUnexpectedMsgSubType

rdnEvtDraTmrInitFailure

rdnEvtDraInvalidFuncParam

rdnEvtDraInvalidMsgParam


MIB File Trap Name


526362-001-00 Rev B 4-7

rdn-evtNotifications.mib(continued)

rdnEvtRdbMsgQCheckFailure

rdnEvtRdbCreateDatabaseFailure

rdnEvtRdbInitDatabaseFailure

rdnEvtRdbSemCreateFailure

rdnEvtRdbUnknownTableFromPeer

rdnEvtRdbDefineTableNotEnoughMemory

rdnEvtRdbMsgBufAllocFailure

rdnEvtRdbMemPoolAllocFailure

rdnEvtRdbMallocFailure

rdnEvtDrmSpareCmtsActive

rdnEvtDrmFailedAutoTakeover

rdnEvtDrmFailedAutoGiveback

rdnEvtDrmSpareXmittersRcvrsMismatch

rdnEvtAccrtrRdbDefineTableFailure

rdnEvtAccrtrRdbNextFailure

rdnEvtAccrtrNotFrozenLoad

rdnEvtArdrtrRdbDefineTableFailure

rdnEvtArdrtrRdbNextFailure

rdnEvtArdrtrNotFrozenLoad

rdnEvtArdrtrLoadFailure

rdnEvtMacmgrValidateCmError

rdnEvtMacmgrInvalidateCmError

rdnEvtMacmgrNullPtr

rdnEvtDocsifCmtsCmIndexAddFreeListFailure

rdnEvtDocsifCmtsCmIndexDelFreeListFailure

rdnEvtDocsifCmtsCmIndexReloadFreeListFailure

rdnEvtUpcTaskSpawnFailure

rdnEvtUpcMsgQCreateFailure

rdnEvtUpcMsgQReceiveFailure


MIB File Trap Name


4-8 526362-001-00 Rev B

Trap Severity LevelsTable 4-3 describes the trap severity levels that are described in this book from 1, which is most severe, to 7, which is informational:

rdn-evtNotifications.mib(continued)

rdnEvtUpcRegTaskMonFailure

rdnEvtUpcRxUnexpectedMsgType

rdnEvtUpcRxUnexpectedMsgSubType

rdnEvtUpcSemCreateFailure

rdnEvtSvcfloNullPtr

rdnEvtSvcfloWriteNextFlowTlvError

rdnEvtSvcfloSidInsertFailure

rdnEvtUbshaCollectionRspMallocError

rdnEvtUbshaTaskSuspended

Table 4-3 Trap Severity Levels

Level Severity Description

1 emergencies Emergency conditions where the system is unusable - reserved for vendor-specific, fatal hardware or software errors that prevents normal system operation and causes reporting system to reboot

2 alerts Conditions where immediate action is needed - a serious failure which causes the reporting system to reboot but is not caused by hardware or software malfunctioning

3 critical Critical conditions - a serious failure that requires immediate attention and prevents the device from transmitting data but the system could recover without rebooting

4 errors Error conditions - a failure occurred that could interrupt the normal data flow

5 warnings Warning conditions - a failure occurred that could interrupt the normal data flow


MIB File Trap Name


526362-001-00 Rev B 4-9

6 notifications Normal but significant conditions - an event of importance occurred which is not a failure

7 informational Informational descriptive system messages - an unimportant event, which could be helpful for tracing normal operations

Table 4-3 Trap Severity Levels

Level Severity Description


4-10 526362-001-00 Rev B

Private Traps and Their Severity LevelsTable 4-4 provides a list of SNMP Trap severity levels for SNMP traps:

Table 4-4 Private Trap Severity Levels

Trap Severity Level Associated Traps

Emergency None

Alert rdnBSRSrmSwitchoverTraprdnEvtMacrtrGetQIdFailurerdnEvtMacrtrUnknownCaserdnEvtMacrtrMsgQReceiveFailurerdnEvtMacrtrRdbDefineTableFailurerdnEvtMacrtrRxUnexpectedMsgTyperdnEvtMacrtrRegTaskMonFailurerdnEvtMacrtrInvalidFuncParamrdnEvtMacrtrUnknownCmIdrdnEvtBpiLoadAuthRunRecFailurerdnEvtBpiLoadTekRunRecFailurerdnEvtBpiLoadCmCertificateFailurerdnEvtDraTaskSpawnFailurerdnEvtDraMsgQCreateFailurerdnEvtDraMsgQReceiveFailurerdnEvtDraRegTaskMonFailurerdnEvtDraCreateRdbFailurerdnEvtDraRxUnexpectedMsgTyperdnEvtDraRxUnexpectedMsgSubTyperdnEvtDraInvalidFuncParamrdnEvtDraInvalidMsgParamrdnEvtRdbMsgQCheckFailurerdnEvtRdbCreateDatabaseFailurerdnEvtRdbInitDatabaseFailurerdnEvtRdbSemCreateFailurerdnEvtRdbUnknownTableFromPeerrdnEvtRdbDefineTableNotEnoughMemoryrdnEvtRdbMsgBufAllocFailure


526362-001-00 Rev B 4-11

Alert (continued) rdnEvtRdbMemPoolAllocFailurerdnEvtRdbMallocFailurerdnEvtDrmSpareXmittersRcvrsMismatchrdnEvtAccrtrRdbDefineTableFailurerdnEvtAccrtrRdbNextFailurerdnEvtAccrtrNotFrozenLoadrdnEvtMacmgrInvalidateCmErrorrdnEvtMacmgrNullPtrrdnEvtDocsifCmtsCmIndexAddFreeListFailurerdnEvtDocsifCmtsCmIndexDelFreeListFailurerdnEvtDocsifCmtsCmIndexReloadFreeListFailurerdnEvtUpcTaskSpawnFailurerdnEvtUpcMsgQCreateFailurerdnEvtUpcMsgQReceiveFailurerdnEvtUpcRegTaskMonFailurerdnEvtUpcRxUnexpectedMsgTyperdnEvtUpcRxUnexpectedMsgSubTyperdnEvtUpcSemCreateFailurerdnEvtSvcfloNullPtrrdnEvtSvcfloWriteNextFlowTlvErrorrdnEvtSvcfloSidInsertFailurerdnEvtUbshaCollectionRspMallocErrorrdnEvtUbshaTaskSuspended

coldStartwarmStartchassisFanFailureTrapchassisPowerFailureTrap

Critical rdnEvtDrmSpareCmtsActiverdnEvtDrmFailedAutoTakeoverrdnEvtDrmFailedAutoGiveback




4-12 526362-001-00 Rev B

Error rdnFlapModemNotificationrdnFlapListNotification

docsDevCmBpiInitTrapdocsDevCmBPKMTrapdocsDevCmDynamicSATrap

Warning rdnPktDQoSCopsTraprdnPktDQoSResReqTraprdnPktDQoSEmergencyTraprdnPktESTrap

authenticationFailure

docsDevCmtsInitRegReqFailTrapdocsDevCmtsInitRegRspFailTrapdocsDevCmtsInitRegAckFailTrapdocsDevCmtsDynServReqFailTrapdocsDevCmtsDynServRspFailTrapdocsDevCmtsDynServAckFailTrapdocsDevCmtsDCCReqFailTrapdocsDevCmtsDCCRspFailTrapdocsDevCmtsDCCAckFailTrap

Notice rdnLinkDownTraprdnLinkUpTraprdnCmtsUpstreamIfLinkUpTraprdnCmtsUpstreamIfLinkDownTraprdnCmtsCmRegisteredNotificationrdnCmtsCmDeregisteredNotification

linkDownlinkUp

rdnSensorThresholdExceededGrdnSyslogSeverityTrap




526362-001-00 Rev B 4-13

Enabling or Disabling TrapsTable 4-5 describes the Motorola Private SNMP trap enable and disable flags and their associated CLI commands. Refer to the BSR 2000 Command Reference Guide for more detailed configuration information pertaining to these commands:

Information None

Debug None

Table 4-5 Enabling or Disabling Trap Flags using their associated CLI commands

Private MIB File Trap Flag Associated CLI Command(s)

RDN-CABLE-SPECTRUM.mib

flapListTrapEnable cable flap-list trap-enableno cable flap-list percentage-threshold

rdn-cmts.mib rdnCmtsLinkUpDownTrapEnableTable cable upstream trap-enable-cmtsno cable upstream trap-enable-rdnrdnCmtsLinkUpDownTrapEnableEntry

rdnCmtsLinkupDownTrapEnable

rdnCmtsCmRegisteredTrapEnable snmp-server enable traps registrationno snmp-server enable traps registration

rdn-pktcable.mib rdnPktDQoSCopsTrapEnable dqos cops-trap-enable enabledqos cops-trap-enable disable

rdnPktDQoSResReqTrapEnable dqos res-req-trap-enable enabledqos res-req-trap-enable disable

rdnPktESTrapEnable es trap-enable enablees trap-enable disableclear configuration es

rdnPktDQoSEmergency TrapEnable dqos emergency-trap-enable




4-14 526362-001-00 Rev B

Filtering TrapsTable 4-6 describes the SNMP trap filter tables and their associated CLI commands. Refer to the BSR 2000 Command Reference Guide for more detailed configuration information pertaining to these commands:

rfc2863.mib ifLinkUpDownTrapEnable trap-enable-ifno trap-enable-if

rfc3418.mib rfc3418snmpEnableAuthenTraps snmp-server enable traps snmp auth-failure

Table 4-6 Using the CLI to Filter Traps

MIB File Trap Filter Table Associated CLI Command(s)

docs-cable-device-trap.mib docsDevEvControlTable logging snmp-traplogging reporting severityno logging control docsis

docsDevCmtsTrapControl snmp-server docs-trap-controlno snmp-server docs-trap-control

mib2c.mib snmpNotifyFilterProfileTable snmp-server notify-filter-profilesnmp-server host

Table 4-5 Enabling or Disabling Trap Flags using their associated CLI commands

Private MIB File Trap Flag Associated CLI Command(s)

526362-001-00 Rev B 5-1

5Using a MIB Browser to

Access MIB Variables

OverviewThis chapter provides a brief overview of using a graphical interface MIB browser including:

n Basic procedures for using the browser n The SNMP Get, GetNext, and Set commandsn The rationale behind updating a MIB database.

Note: The information and procedures provided use a “generic” graphical interface MIB browser application as an example. There are many interface-based MIB browsers available and, while they support similar functionality and presentation, there are vendor-specific differences in procedure.

There are also several command line MIB browsers available which are beyond the scope of this document.


5-2 526362-001-00 Rev B

About MIB BrowsersWith a MIB browser, you can examine the MIBs supported by an active device on your network and perform SNMP Get, GetNext, and Set commands on the MIB objects.

To successfully communicate with intelligent devices with SNMP, some MIB browsers rely on their own database of MIB information. The OIDs, ASCII names, and other technical information stored in this database allow you to easily search for and select the objects whose information you want to view or change. You use the MIB browser application to both query and set objects in your intelligent devices.

The following sections describe using a MIB browser to:

n Contact a device n Navigate through its supported MIBsn Query the device for MIB values n Set a new value for a MIB object at the device

Contacting the DeviceBefore you can access MIB information for a device through a MIB browser, you must establish contact with the device. You contact a device through the MIB browser interface by specifying the device’s IP address and the community name.

SNMP community names are used to control management access to a device. The level of control that a managing entity has over the device corresponds to the access level provided by the community name used in a management request: Read Only, Read-Write, or Superuser.

For SNMP communication to take place, the SNMP agent must be running on the device and the specified community name must match one of the device’s community names. SNMP runs as a daemon on Solaris and as a service on NT.

Follow these steps to determine if the SNMP agent is running on the device:

1. Telnet to the device

2. Issue the ps command and look for an entry for the snmpd process. For example, this entry may read:

407 0 S0 7e8d0 103c 7f7f4 12 12 0 18 0:00.017 ? snmpd

Release 1.1 Using a MIB Browser to Access MIB Variables

526362-001-00 Rev B 5-3

Browsing the MIB TreeA graphical MIB browser provides an interface that lets you query any SNMP device on your network and examine its supported MIBs. The MIB information is visually structured into a tree format, similar to a directory tree. Using the mouse, you can scroll through the tree and click on folder icons to open the tree layer of interest. Like a file directory tree, the MIB Tree is represented by a series of collapsible and expandable folders, with the individual MIB Objects contained in each folder.

Once you have successfully contacted a device, you will be able to browse its supported MIBs through a MIB tree display in the browser window, and query the device for its MIB object values. Like a file directory tree, the MIB tree is represented by a series of collapsible and expandable folders, containing the individual MIB objects.

Figure 5-1 shows the top level of the MIB tree is shown. When you click on a level of a tree, it is highlighted to show that it is selected. Each branch of the tree is indicated by a folder.

Figure 5-1 The Top Level of the MIB Tree

iso (1)

ccitt (0)

joint-iso-ccitt (2)


5-4 526362-001-00 Rev B

Figure 5-2 shows that the iso –> org –> dod –> internet branch has been opened. Each folder icon changes and is marked with a minus sign (-) to denote that it has been expanded. The mgmt and private folders are marked with a plus sign (+), indicating that they are expandable to reveal more information, but have not yet been opened.

A folder without a plus sign (+) or minus sign (-) indicates an empty tree branch that is not expandable.

Figure 5-2 The Path to the Internet Branch of the MIB Tree

iso (1)org (3)

dod (6)

internet (1)directory (1)

mgmt (2)

private (4)

experimental (3)


526362-001-00 Rev B 5-5

Figure 5-3 shows the MIB tree further expanded to reveal a management object (leaf), specifically the iso -> org -> dod -> internet -> mgmt -> mib-2 -> system -> sysDescr object

Figure 5-3 The MIB Tree Expanded to Reveal an Object

SNMP Get/Get NextTo find the current value set at the selected device for a specific MIB object or set of objects, you must query the device for the information. A query consists of an SNMP Get (to retrieve a specific piece of management information) or SNMP GetNext (to traverse a portion of the tree and retrieve all its information) command issued by the browser to the contacted device. When you query a device, it returns a value for every instance of the specified object(s).

iso (1)org (3)

dod (6)

internet (1)directory (1)

mgmt (2)mib-2 (1)

system (1)

sysDescr (1)


5-6 526362-001-00 Rev B

SNMP SetWith a MIB browser, you can change the value of a writable object in a device’s MIB. This is accomplished with an SNMP Set command. If you attempt to change the value of an object and a message similar to “Selected item is not write enabled.” appears. This may occur because:

n You do not have permission to write to the devicen The object itself has been designated read-only. n Objects which are present in the device have not been added to the current MIB

database.

Before you begin, you can determine if an object is writable by performing a query on the object and reading the data that is returned.

Compiling and Importing New SNMP MIBsThere are several reasons that you may want to import additional or updated MIBs into your database, or create custom MIB databases:

n You want to manage third-party devices not already supported, you will need to import their vendors’ private MIBs (which will not be included in your default MIB database).

n MIBs — especially private MIBs — are frequently updated, and you may need to import a new version of a MIB.

n Some of your newer networking devices may still be under heavy development, and new firmware may include functionality provided by entirely new private MIBs.

By importing new and updated MIBs to create custom MIB databases, you can ensure that your MIB databases remain up-to-date and contain all the MIB information you need to successfully monitor and manage your network devices.

Sample TasksThis section provides two sample tasks using a graphical MIB browser:

n Accessing MIB variable informationn Changing a MIB variable


526362-001-00 Rev B 5-7

Accessing MIB Variable InformationTo find the current value set at the selected device for a specific MIB object or set of objects, the MIB browser issues an SNMP Get command (to retrieve a specific piece of management information) or SNMP Get Next command (to traverse a portion of the tree and retrieve all its information).

Sample TaskA network administrator needs to know how long a particular device has been on-line since it was last rebooted. In our example, we will be finding the value of the sysUpTime object. The MIB hierarchy that leads to the sysUpTime object is:

1.2.6.1.2.1.13

iso -> org -> dod-> internet -> mgmt -> mib-2 -> system -> sysUpTime

To query a device for the value of the sysUpTime object, do the following:

1. Start your MIB browser.

2. Connect to the device of interest by specifying the device’s IP address and community name.

Note: Be sure that you have contacted the device and that you are using a community name which provides you with write access to the desired MIB object. The appropriate community name may depend upon which MIB component contains the object you want to set. Refer to Contacting the Device on page 5-2.


5-8 526362-001-00 Rev B

3. In the MIB tree display, navigate through the MIB hierarchy until you reach the mib-2 folder (Figure 5-4)

Figure 5-4 The mib-2 Hierarchy

4. Open the mib-2 folder

iso (1)

dod (6)internet (1)

mgmt (2)

org (2)

mib-2 (1)Navigate to themib-2 folder


526362-001-00 Rev B 5-9

5. Open the system folder to display the objects in the system group (Figure 5-5).

Figure 5-5 The mib-2 and system Folders

iso (1)

dod (6)internet (1)

mgmt (2)

org (2)

mib-2 (1)system (1)

interface (2)

sysServices (7)

sysLocation (6)

sysName (5)

sysContact (4)

sysUpTime (3)

sysObjectID (2)

sysDescr (1)

Open the mib-2and system folders


5-10 526362-001-00 Rev B

6. Select the sysUpTime object (Figure 5-6).

Figure 5-6 Selecting the sysUpTime Object

iso (1)

dod (6)internet (1)

mgmt (2)

org (2)

mib-2 (1)system (1)

interface (2)

sysServices (7)

sysLocation (6)

sysName (5)

sysContact (4)

sysObjectID (2)

sysDescr (1)

sysUptime (3) Select thesysUpTime object


526362-001-00 Rev B 5-11

All or part of the following should be retrieved and displayed for the sysUpTime object:

Object Name sysUpTimeObject ID 1.2.6.1.2.1.1.3Type TimeTicksAccess read-onlyDescription The time (in hundredths of a second)

since the network management portion of the system was last re-initialized.

Value 28 days 20:05:41

Changing MIB VariablesTo change the value of a writable MIB object, the MIB browser issues an SNMP Set command. Before you begin, you can determine if an object is writable by performing a query on the object and reading the data that is returned. See Accessing MIB Variable Information on page 5-7.

Sample TaskA network administrator wants to clear all messages from the syslog files on a remote syslog server device. In our example, we will be changing the value of the rdnSyslogClear object. The MIB hierarchy that leads to the rdnSyslogClear object is:

1.2.6.1.4.1.4981.3.7

iso -> org -> dod -> internet -> private -> enterprises -> rdn -> syslog ->rdnSyslogClear

Note: Depending on the particular MIB browser application that you are using, the query information for the sysUpTime object may be accessed and displayed differently. Refer to your MIB browser documentation.

Note: Be sure that you have contacted the device and that you are using a community name which provides you with write access to the desired MIB object. The appropriate community name may depend upon which MIB component contains the object you want to set. Refer to Contacting the Device on page 5-2.


5-12 526362-001-00 Rev B

Follow these steps to change the value of the rdnSyslogClear object on a device:

1. Start your MIB browser.

2. Connect to the device of interest by specifying the device’s IP address and community name.

3. In the MIB tree display, navigate through the MIB hierarchy until you reach the rdn folder (Figure 5-7).

Figure 5-7 The rdn MIB Hierarchy

4. Open the rdn folder

iso (1)

dod (6)internet (1)

private (4)

org (2)

rdn (4981)Navigate to the

rdn folder

enterprises (1)


526362-001-00 Rev B 5-13

5. Open the syslog folder to display the objects in the syslog group (Figure 5-8).

Figure 5-8 The rdn and syslog Folders

iso (1)

dod (6)internet (1)

private (4)

org (2)

enterprises (1)rdn (4981)

syslog (3)

rdnSyslogClear (7)

rdnSyslogConsoleSeverity (6)

rdnSyslogSeverity (5)

rdnSyslogServerTable (4)

rdnSyslogServerEnable (3)

rdnSyslogMaxSize (2)

rdnSyslogSize (1)

cmts (2)

Open therdn folder

Open thesyslog folder


5-14 526362-001-00 Rev B

6. Select the rdnSyslogClear object (Figure 5-9).

Figure 5-9 Selecting the rdnSyslogClear Object

iso (1)

dod (6)internet (1)

private (4)

org (2)

enterprises (1)rdn (4981)

syslog (3)

rdnSyslogConsoleSeverity (6)

rdnSyslogSeverity (5)

rdnSyslogServerTable (4)

rdnSyslogServerEnable (3)

rdnSyslogMaxSize (2)

rdnSyslogSize (1)

cmts (2)

rdnSyslogClear (7) Select therdnSyslogClear object


526362-001-00 Rev B 5-15

7. Set the rdnSyslogClear object to “TRUE”.

Note: The exact procedure for changing an object’s value through a MIB browser interface depends on the particular MIB browser application that you are using. Refer to your MIB browser documentation.

526362-001-00 Rev B Index-1

A

Abstract Syntax Notation One, 1-4

B

BSR 2000proprietary MIBs, 1-3

RDN, 3-1SNMP agent software, 1-3

C

Cable Modem Termination Systems, 3-1

F

firmware, 5-6folder, 5-3

icon, 5-4

G

Get, 1-3GetNext, 1-3

I

IETF, 1-2Internet Assigned Numbers Authority, 1-3Internet Engineering Task Force, 1-2IP address, 5-2, 5-7, 5-12

M

Management Information Base, 1-2MIB, 1-2

browser, 5-1, 5-3, 5-6command line, 5-1graphical, 5-1, 5-6interface, 5-1, 5-15

compiling, 5-6database, 5-1, 5-6hierarchy, 5-7, 5-8, 5-11, 5-12importing, 5-6Object Identifier, 1-3OID, 1-3organization, 1-3private, 1-2, 5-6proprietary, 5-6RFC, 1-2standard, 2-1supported, 5-2, 5-3tree, 5-3, 5-8, 5-12

browsing, 5-3values, 5-2variable

accessing, 5-6changing, 5-6

O

objectACCESS, 1-4DESCRIPTION, 1-5instance, 1-4OBJECT_TYPE, 1-4

Index

Index-2 526362-001-00 Rev B


STATUSmandatory, 1-5obsoleted, 1-5optional, 1-5

SYNTAX, 1-4tabular, 1-4writable, 5-6, 5-11

Q

query, 5-2, 5-5

R

Request for Comments, 1-2

S

Set, 1-3, 5-6SMI, 1-2, 1-4SNMP, 1-1, 1-2

agent, 1-2, 1-3, 5-2commands, 1-3community name, 5-2, 5-7, 5-11Get, 5-5get, 5-1, 5-7get next, 5-7GetNext, 5-2, 5-5management, 1-2network management station, 1-2, 1-3Set, 5-2, 5-6, 5-11

Structure of Management Information, 1-2

T

treebranches, 1-3leaves, 1-3MIB, 5-3structure, 1-3

526362-001-00 Rev B2/11

Visit our website at:www.motorola.com

bsr 2000 - release 1.1 - snmp configuration and management guide

Documents

motorola product

motorola mobility

motorola equipmentplease

motorola customer service

commercial waste

rev brelease

electronic waste items

rev b iiicontentsprefacescope