Transcript
Page 1: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Touchstone® TelephonyManagement GuideRelease 6.1 Standard 1.3Date: June 2009

Chapter 1: Managing Touchstone NIUsThis chapter provides information useful for managing TelephonyModems and Telephony Ports and various sub-systems and compo-nents. Featuresinclude battery monitoring and signaling messagetracing.

Chapter 2: Using SNMP to Monitor Network Ele-mentsThis chapter describes cable modem and CMTS MIBs that can beused for network or element monitoring.

Chapter 3: IPv6 SupportTS6.1 and later versions of Touchstone firmware provide IPv6 sup-port in the CM portion of the Telephony Modem. Thischapterdescribes provisioning, management, and troubleshooting supportfor IPv6.

Chapter 4: SNMP SecurityThis chapter describes SNMP security features.

Chapter 5: Configuring SNMP CM CoexistenceTouchstone firmware provides several SNMPv3 security-related fea-tures. SNMPCoexistence is a feature that allows SNMPv1 andSNMPv2c network management systems to function within the con-text of SNMPv3 security and view-based MIB access.

Chapter 6: ARRIS-specific MT A SNMP CoexistenceThe ARRIS MTA SNMP Proprietary Coexistence feature allowsSNMPv1 and SNMPv2c network management systems to functionwithin the context of SNMPv3 security and view-based MIB access.

Appendix A: Endpoint and Event DefinitionsThis appendix describes the Touchstone endpoint format and typicalev ent definitions. Not all the events and packages described in thisappendix apply to Touchstone NIUs.

Page 2: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

ii

© 2004–2009 ARRISAll rights reserved

Pr inted in the USA

The infor mation in this document is subject to change without notice. The statements, configurations, technical data,and recommendations in this document are believed to be accurate and reliable, but are presented without express orimplied warranty. Users must take full responsibility for their applications of any products specified in this document.The infor mation in this document is proprietar y to ARRIS.

ARRIS, C3™, C4®, and Touchstone® are trademar ks or registered trademar ks of ARRIS Group, Inc. Cadant® is aregistered trademar k of ARRIS Group, Inc. All other trademar ks and registered trademar ks are the property of theirrespective holders.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 3: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Publication history

June 2009 Release 6.1 Standard 1.3 version of this document for TS6.1 MSUP3.

Januar y 2009 Release 6.1 Standard 1.0 version of this document for TS6.1.

October 2007 Release 5.2 Standard 1.1 version of this document for TS5.2.

May 2007 Release 5.1 Standard 1.0 version of this document for TS5.1.

December 2006 Release 5.0 Standard 2.0 version of this document for TS5.0 MSUP.

October 2006 Release 5.0 Standard 1.0 version of this document.

December 2005 Release 4.5 Standard 2.0 version of this document for TS4.5 MSUP 2.

November 2005 Release 4.5 Standard 1.0 version of this document for TS4.5 MSUP 1.

March 2005 Release 4.4 Standard 1.0 version of this document.

August 2004 Release 4.2 Standard 1.0 version of this document.

Release 4.1 Standard 2.0 version of this document.

April 2004 Release 4.1 Standard 1.0 version of this document.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 4: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

iv Publication history

September 2003 Release 3.2 Standard 1.0 version of this document.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 5: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Contents

Audience ........................................................................................... ixIn this Document ............................................................................... ixTerminology ....................................................................................... x

Managing Touchstone eMT As 1Batter y Management ......................................................................... 1

Batter y Management Interfaces .................................................. 1Monitor ing Batter y Status Using the Web Pages ........................ 1Monitor ing Batter y Levels ........................................................... 3

Other Model 4 Considerations .............................................. 3Po wer-related MIB Objects ......................................................... 4Controlling Battery Testing .......................................................... 4Batter y Over-Temperature Protection ......................................... 5

CLI Commands .................................................................... 6Po wer-related MIB Objects ......................................................... 6

RFC 1628 MIB Objects ........................................................ 6ARRIS Battery MIB Objects ................................................. 9SNMP Battery Telemetr y States(TM502, TM504, TM602, TM604) ...................................... 13SNMP Battery Telemetr y States(TM508, TM512, TM608) ................................................... 15

TM508/512 Telemetr y Block Pinouts ........................................ 15Considerations for the 8-cell Battery ......................................... 16

TS5.0 and Earlier Behavior ................................................ 16TS5.1 Behavior ................................................................... 16

DTM602 Considerations ........................................................... 17Monitor ing MTA Provisioning Status ................................................ 17

Fir mware Upgrade Status ......................................................... 19Monitor ing Quarantined Events ....................................................... 19

Monitor ing Quarantine Status ................................................... 19Monitor ing Quarantined Events Using the CLI .......................... 20

Captur ing Signaling Traces ............................................................. 21Controlling Signaling Tracing .................................................... 21Inter preting the Signaling Trace Output Data ............................ 22

Inter preting the Transmit Data Payload .............................. 22Inter preting the Receive Data Payload ............................... 23Signaling Trace Feature Example Output ........................... 24

Management Guide Release 6.1 Standard 1.3 June 2009

Page 6: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

vi Contents

Monitor ing Device Parameters ........................................................ 25Example .................................................................................... 26

Using SNMP to Monitor Network Elements 27Element Over view ........................................................................... 27

Interface Index Scheme ............................................................ 27ARRIS MIB Indexing ................................................................. 28Interface Types .......................................................................... 28

Subscr iber Device MIBs .................................................................. 29Line Status MIBs ....................................................................... 29Call Statistics Objects ............................................................... 29ARRIS RIP Objects ................................................................... 30

CMTS MIBs ..................................................................................... 31

IPv6 Suppor t 33About IPv6 Support ......................................................................... 33Provisioning Notes .......................................................................... 34

Provisioning Modes ................................................................... 34Selecting an Addressing Mode ................................................. 34DHCP Behavior for IPv6 Provisioning ....................................... 34Provisioning File Notes ............................................................. 35TLV38 Enhancements ............................................................... 35

Management ................................................................................... 35Coexistence .............................................................................. 35DHCPv6 MIB Objects ............................................................... 36SNMP Access ........................................................................... 38

SNMP Security 39SNMP Access Mode Over view ....................................................... 39

SNMP Access Policy (CM-side) ................................................ 40SNMP Access Policy (MTA-side) .............................................. 40SNMPv1/v2c NmAccess Mode ................................................. 40SNMP Coexistence Mode ......................................................... 41SNMP Coexistence Types ........................................................ 41

SNMPv1/v2c-only Coexistence .......................................... 41SNMPv1/v2c/v3 Coexistence ............................................. 41SNMPv3-only Coexistence ................................................. 42

Configur ing the Cable Modem for NmAccess Mode ....................... 42Configur ing SNMP Access withthe docsDevNmAccessTable .................................................... 42Configur ing Tr ap Transmission withthe docsDevNmAccessTable .................................................... 43Rules for the docsDevNmAccessTable ..................................... 43

docsDevNmAccessIp and docsDevNmAccessIpMask ....... 44docsDevNmAccessCommunity .......................................... 44docsDevNmAccessControl ................................................. 45docsDevNmAccessInterfaces ............................................. 45docsDevNmAccessStatus .................................................. 46docsDevNmAccessTrapVersion .......................................... 46

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 7: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Contents vii

Configur ing the CM for Coexistence Mode ...................................... 47Configur ing SNMPv1/v2c only coexistence .............................. 47

snmpCommunityTable, Indexed bysnmpCommunityIndex ........................................................ 48How it Wor ks ...................................................................... 48vacmSecur ityToGroupTable, Indexed byvacmSecur ityModel, vacmSecur ityName ........................... 48vacmAccessTable, Indexed byvacmGroupName, vacmAccessContextPrefix,vacmAccessSecur ityModel, vacmAccessSecur ityLevel ..... 49

Configur ing SNMPv1/v2c/v3 coexistence ................................. 49SnmpV3 Kickstar t Value ..................................................... 50SnmpV3 Kickstar t Secur ity Name ...................................... 50SnmpV3 Kickstar t Manager Public Number ....................... 50Example: Adding a TLV-34 element in PacketACE ............. 51

Configur ing SNMPv3-only coexistence ..................................... 53Configur ing Tr ap Transmission within Coexistence Mode ......... 53

SNMPv3 Notification Receiverconfig file element (TLV-38) ................................................ 53SNMPv3 Notification Receiver IP Address ......................... 54SNMPv3 Notification Receiver UDP Por t Number ............. 54SNMPv3 Notification Receiver Trap Type ........................... 54SNMPv3 Notification Receiver Timeout ............................. 54SNMPv3 Notification Receiver Retries ............................... 55SNMPv3 Notification Receiver Filtering Parameters .......... 55SNMPv3 Notification Receiver Security Name ................... 55Example Configuration ....................................................... 56Example: Adding a TLV-38 element in PacketACE ............. 56

Configur ing a Cloned USM User ..................................................... 58usmUserTable Parameters ........................................................ 59vacmSecur ityToGroupTable Parameters ................................... 60vacmAccessTable Parameters .................................................. 61Example Configuration File ....................................................... 61

Configuring SNMP CM Coe xistence 65Over view ......................................................................................... 65

Configuration File Notes ........................................................... 65SNMP Access Mode ................................................................. 65SNMP Trap Transmission .......................................................... 66

Procedure : Configur ing SNMP Coexistence .................................. 67snmpCommunityTable Parameters ........................................... 67vacmSecur ityToGroupTable Parameters ................................... 67vacmAccessTable Parameters .................................................. 68Adding the snmpCommunityTable ............................................ 69Adding the vacmSecur ityToGroupTable .................................... 72Adding the vacmAccessTable ................................................... 75

Procedure : Configur ing Tr ap Ser vers ............................................. 78

Management Guide Release 6.1 Standard 1.3 June 2009

Page 8: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

viii Contents

ARRIS-specific MT A SNMP Coexistence 81MTA Coexistence Over view ............................................................. 81MIB Access for MTA Coexistence ................................................... 82MIB Access for CM Coexistence ..................................................... 82Configur ing MTA SNMP Coexistence .............................................. 82snmpCommunityTable Parameters .................................................. 83

Example: MTA SNMP Coexistence ........................................... 83vacmSecur ityToGroupTable Parameters ......................................... 83

Example: MTA SNMP Coexistence ........................................... 83vacmAccessTable Parameters ........................................................ 84

Example: MTA SNMP Coexistence ........................................... 84SNMPv3 Notification Receiver Configuration File Element(TLV−38) ........................................................................................ 84

Example MTA TLV -38 Configuration ......................................... 85Configuration File Examples ........................................................... 86

MTA Coexistence/Notifications Provisioned in the MTA Con-figuration File............................................................................... 86

Appendix A: Endpoint and Event Definitions 89Endpoint Definition .......................................................................... 89Event Definitions ............................................................................. 89

Basic Packages ......................................................................... 89Line Package ............................................................................ 90FAX Package ............................................................................ 91VoIP Metrics Package ............................................................... 92

Local Connection Options .................................................. 92Audit Connection Procedures ............................................. 92

Index 95

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 9: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

About This Document

This document describes management features supported by Touchstone®Telephony TS6.1 firmware.

Audience

This manual assumes that you have a basic understanding of SNMP manage-ment systems, DOCSIS® and PacketCable™ standards, and a workingknowledge of cable data and telephony networks.

In this Document

This document contains the following information:

• Chapter 1,‘‘ Managing Touchstone eMTAs,’’ describes information use-ful for managing Telephony Ports and Telephony Modems and theirvarious sub-systems.

• Chapter 2,‘‘ Using SNMP to Monitor Network Elements,’’ describescable modem and CMTS MIB objects that can be used for network orelement monitoring.

• Chapter 3,‘‘ SNMP Security,’’ describes security features and how toconfigure them.

• Chapter 4, ‘‘Configuring SNMP CMCoexistence,’’ describes SNMPcoexistence, a feature that allows SNMPv1 and SNMPv2c networkmanagement systems to function within the context of SNMPv3 secu-rity and view-based MIB access.

• Chapter 5, ‘‘A RRIS-specific MTA SNMP Coexistence,’’ describesSNMP coexistence features that are proprietary to Touchstone Tele-phony eMTAs.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 10: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

x About This Document

• Appendix A, ‘‘Endpoint and Event Definitions,’’ describes the Touch-stone endpoint format and typical event definitions.

Terminology

The following is a list of terms and abbreviations used in this manual.

Best Eff or t (BE)The default Service Flow type. BEis intended for non-telephonyapplications, where jitter and latency are of little importance.

Call Agent (CA)A device that maintains call state, and controls the line side of calls.The CA is often a portion of a Call Management Server (CMS).

Call Mana gement Server (CMS)A generic term for the devices connecting a VoIP network to thePSTN. A CMS includes both a Call Agent (CA) and the PSTNgateway, and controls audio call connections.

CALFVCall Forwarding Unconditional (dialing feature).

CallPCall Processing. Firmware controlling the current state of a call.

CALRTCall Return (dialing feature).

CASCPE Alert Signal.A method of encoding signaling information in atelephone connection.

CBRConstant Bit Rate.A data service that provides a guaranteed, fixedamount of bandwidth.Technically, it is not possible to provideactual CBR services over an IP network due to factors such as con-tention and latency. UGS service flows and low-latency hardwaresuch as the ARRIS™ Cadant® C4 CMTS, however, can provide anapproximation suitable for carrier-grade telephone service.

CFFDSCall Forwarding Unconditional Disable (dialing feature).

CIDTECaller iD Temp Enable (dialing feature).

ClassifierRules used to classify packets into a Service Flow. The device com-pares incoming packets to an ordered list of rules at several protocollevels. Each rule is a row in the docsQosPktClassTable . A

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 11: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

About This Document xi

matching rule provides a Service Flow ID (SFID) to which thepacket is classified. All rules need to match for a packet to match aclassifier. Packets that do not match any classifiers are assigned tothe default (or primary) Service Flow.

CLWPDCall Waiting Permanent Disable (dialing feature).

CMCable Modem. Typically a device installed at the subscriberpremises that provides a high-speed data (Internet) connectionthrough the HFC network.

CMTSCable Modem Termination System.A device at a cable headendthat connects to cable modems over an HFC network to an IP net-work.

CODECCoder-decoder. In VoIP products, one of several possible schemesof converting audio (i.e. a phone call) to digital data and vice versa.Attributes of a codec include fidelity (e.g. voice quality), bandwidth,and latency.

CPECustomer Premises Equipment.Subscriber-owned equipment con-nected to the network. Technically, a cable modem, MTA, or NIUfalls into this category, although many operators do not designatethem as such.

CVCCode Verification Certificate, an encryption key that allows securedownloading of encrypted firmware over the HFC network.

DHCPDynamic Host Configuration Protocol. An IP protocol used to pro-vide an IP address and location of services (such as DNS and TFTP)needed by a device connecting to the network.

DNSDomain Name Service (Server). An IP service that associates adomain name (such as www.example.com) with an IP address.

DownstreamIn an HFC network, the direction from the headend to the sub-scriber. Some older cable documentation may refer to this as theforward path.

DOCSISData Over Cable Service Interface Specification.The interoperabil-ity standards used for data communications equipment on an HFCnetwork.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 12: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

xii About This Document

DQoSDynamic Quality of Service.The mechanism by which the MTAchooses the proper quality of service settings for a particular serviceflow. Touchstone firmware supports both full PacketCable DQoSand ‘‘DSx QoS’’ f or interoperability with non-PacketCable compli-ant networks.

eMTAEmbedded MTA. A device, such as the ARRIS Touchstone Tele-phony Modem, that contains both an MTA and a cable modem.

Euro-DOCSISThe European version of DOCSIS.Euro-DOCSIS specifies an8 MHz downstream bandwidth (vs. 6 MHz for DOCSIS); otherminor differences exist as well.

FQDNFully Qualified Domain Name. The name used to identify a singledevice on the Internet. See RFC2821 for details.

FSKFrequency Shift Keying. A method of encoding signaling informa-tion in a telephone connection.

Global Universal Pr ov isioning Interface (GUPI)A PacketCable subset, intended to accommodate a wide range ofpartially-compliant equipment. SNMP communication usesSNMPv1 or SNMPv2, with INFORM disabled. IPsec and mediaencryption are disabled.

HeadendThe ‘‘central office’’ i n an HFC network. Theheadend houses bothvideo and data equipment.In larger MSO networks, a ‘‘master’’headend often feeds several ‘‘remote’’ headends to provide distrib-uted services.

HFCHybrid Fiber-Coaxial. A broadband, bi-directional shared mediatransmission system using fiber trunks between the headend andfiber nodes, and coaxial distribution cable between the fiber nodesand subscriber premises.

IANAInternet Assigned Numbers Authority. The coordinating body that:assigns IP addresses to regional Internet registries; recognizes top-level domains; and assigns protocol numbers for well-known ser-vices.

JitterVariance in packet arrival time. Jitteris a factor in applications suchas telephony, where the originating device sends packets at a con-stant rate.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 13: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

About This Document xiii

LatencyThe time required for a signal element (e.g. packet) to pass througha device or network.

KDCKerberos Key Distribution Center.

LCOLocal Connection Options.A structure that describes the character-istics of the media data connection from the point of view of theCMS creating the connection.

MACMedia Access Control.A general term for the link-level networkinglayer and associated protocols.MAC protocols used in HFC datanetworks include Ethernet, the DOCSIS RF interface, and Home-PNA.

Maintenance windowThe usual period of time for performing maintenance and repairoperations. Sincethese activities often affect service to one or moresubscribers, the maintenance window is usually an overnight period(often 1 a.m. to 5 a.m. local time).

MD5Message Digest 5.A one-way hashing algorithm that maps variablelength plaintext into fixed-length (16-byte) ciphertext. MD5 files,built by a provisioning server, contain provisioning data for eachNIU on the network.

MIBManagement Information Base. The data representing the state of amanaged object in an SNMP-based network management system.Often used colloquially to refer to a single object or variable in thebase; e.g. ‘‘the lcCmtsUpMaxCbrFlows MIB.’’

MSOMulti-System Operator. A cable company that operates multipleheadend locations, usually in several cities.

MPIMicro-Processor Interface. An internal Touchstone TelephonyModem component.

MTAMultimedia Terminal Adapter. A subscriber premises device thatcontains the network interface, codecs, and all signalling and encap-sulation functions required for telephony transport, CLASS featuressignalling, and QoS signalling. The MTA is an integral part ofTouchstone Telephony embedded MTA (eMTA) products.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 14: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

xiv About This Document

NCSNetwork-based Call Signaling. The PacketCable protocol used tocontrol calls.

NIUNetwork Interface Unit.A generic term for a device providing dataand telephony connections at a subscriber site. Also referred to asembedded MTA (eMTA).

NMSNetwork Management System.Software, usually SNMP-based,that allows you to monitor and control devices on the network. In aVoIP network, managed devices include NIUs, CMTS, servers,PSTN interface devices, and routers. An NMS works by readingand setting values of MIB variables presented by each device.

NVRAMNon-volatile RAM. A block of non-volatile memory used to storesettings that should persist across reboots.

Off-netA call between a Touchstone phone line and a line on the PSTN.

On-netA call between two Touchstone phone lines. Depending on theCMS used, the connection may be established directly between theMTAs or be routed through a gateway.

PacketCableA CableLabs-led initiative aimed at developing interoperable inter-face specifications for delivering advanced, real-time multimediaservices over two-way cable plant.

PCMPulse Code Modulation.A commonly employed algorithm to digi-tize an analog signal (e.g. voice) into a digital bit stream using sim-ple analog to digital conversion techniques. PCM is employed inthe popular G.711 codec.

PLOPermanent Lock-Out.A l ine card may enter this state when left off-hook with no connection after a certain amount of time.

POSPoint of Sale (terminal).Typically, an electronic cash register.

PSTNPublic Switched Telephone Network.

QAMQuadrature Amplitude Modulation.A method of modulating digitalsignals onto an RF carrier, inv olving both amplitude and phase cod-ing. QAM16 modulation encodes four digital bits per state and isused on upstream carriers; QAM64 and QAM256 encode six oreight bits (respectively) for use on downstream carriers.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 15: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

About This Document xv

QoSQuality of Service. An attribute of a Service Flow, defining limita-tions or guarantees for data rate, latency, and jitter.

QPSKQuadrature Phase Shift Keying. A method of modulating digitalsignals onto an RF carrier, using four phase states to encode twodigital bits.

QuarantineA state where an endpoint (phone line) may potentially bufferev ents. Events not quarantined are processed normally. Processingof quarantined events may be delayed, potentially indefinitely.

RFRadio Frequency.

SDPSession Description Protocol. SDP describes multimedia sessionsfor the purposes of session announcement, session invitation, andother forms of multimedia session initiation.

Ser vice FlowA unidirectional, MAC-layer transport service that provides trafficshaping, policy, and priority according to QoS parameters definedfor the flow.

SFIDService Flow ID. A number used to identify a particular ServiceFlow.

SLACSubscriber Line Audio Circuit.An internal Touchstone TelephonyModem component.

SIPSession Initiation Protocol.A signaling protocol for Internet con-ferencing, telephony, presence, events notification and instant mes-saging.

SNMPSimple Network Management Protocol.

TFTPTrivial File Transfer Protocol. Used in DOCSIS networks to trans-fer firmware and provisioning files to network devices.

TMTelephony Modem.

Uniform Resource Identifier (URI)A way to identify a specific phone line for an MTA. For examplesip:<phone number>@<IP address or domain>.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 16: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

xvi About This Document

Unsolicited Grant Service (UGS)A Service Flow type used for applications such as telephony inwhich latency and jitter are critical.Packets have a fixed size andinterval. Within the constraints of IP networking, UGS flowsattempt to deliver a constant bit rate (CBR) stream of data.

UpstreamThe path from a subscriber device to the headend. Some older cabledocumentation may refer to this as the return path or reverse path.

VA CMView-based Access Control Model.An SNMP MIB for controllingaccess to management information.

VFVoice Frequency.

VoIPVoice Over Internet Protocol.A generic term for technology thatallows telephone calls to be made across an Internet connectioninstead of a traditional two-wire copper connection.

WTMWireless Telephony Modem.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 17: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

1 ManagingTouchstone eMTAs

This chapter provides information useful for managing Telephony Modemsand Telephony Ports and various sub-systems and components.Featuresinclude battery monitoring and signaling message tracing.

Batter y Management

Monitoring the status of Telephony Modem battery backup is critical whenproviding lifeline telephone service.Touchstone firmware provides a numberof features useful for monitoring and controlling Telephony Modem batterybackup systems.

Batter y Man-ag ement Inter-faces

Touchstone eMTAs with battery backup provide battery status through sev-eral interfaces:

• Syslog

• Alarms (including SNMP traps)

• Logs

• Web-based troubleshooting interface

• SNMP MIBs

• CLI

See theTouchstone Telephony Troubleshooting Guidefor details.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 18: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

2 Chapter 1

Monitoring BatteryStatus Using theWeb Pag es

The basic Registration Status web page is available from theCM State link,and displays information about the power supply and battery status.

If the Battery Part Number is ‘‘Contact ARRIS’’ as shown below, the batteryis either defective or the Telephony Modem has the wrong type of batteryinstalled (for example, an 8.8Ah battery installed in a TM502).

The operational status is ‘‘No Status Reported’’ if t he battery charger hasbeen disabled.Check the Event Log page for a ‘‘Battery Charger Disabled’’alarm to verify. Power-cycle or reset the eMTA to re-enable the charger.

If you see this display, contact ARRIS Technical Support.Make a note of thehexadecimal code and operational status before calling.

The battery serial number is available on most two- and four-line Model5Telephony Modems. Thefollowing is a list of other messages that mayappear in the Battery Serial Number field:

Battery Serial Number Not SupportedThe Telephony Modem is a Model4, an early Model 5, or a multi-line Telephony Modem.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 19: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 3

Battery MissingNo battery is installed.

AC Failed. S/N Temporarily UnavailableAppears when the Telephony Modem is running on battery power.

Unable to obtain Battery Serial Number(s)Appears in cases where the serial number is missing or unreadable.

The MTA Parameters page displays the state of the high battery temperaturealarm (enabled or disabled) in the ‘‘Temperature Alarm’’ section, at the bot-tom of the page.

Monitoring BatteryLevels

After the battery has been completely charged, the Telephony Modem canprovide an estimate of the remaining charge.

The arrisMtaDevEstimatedMinutesRemaining MIB object reports an esti-mate of the time, in minutes, to battery charge depletion under the presentload conditions if:

• power is off and remains off; or

• power were to be lost and remain off

The MIB objectarrisMtaDevEstimatedChar geRemaining reports an esti-mate of the battery charge remaining, expressed as a percent of full charge.

Note: When the value of either MIB is−1, the capacity measurements are notcompletely initialized. Model 5 and Model6 Telephony Modems requireabout 5 minutes after initialization to provide accurate capacity reporting.Model 4 Telephony Modems require the battery to be fully charged beforereporting capacity; this can take up to 24 hours per battery, depending on thebattery charge at initialization time.

Other Model 4 Considerations

Model 4 Telephony Modem charger hardware provides limited battery capac-ity reporting capabilities.Touchstone firmware provides an estimate of bat-tery charge levels, which requires the batteries to be fully charged to providea known point of reference for calculating remaining capacity. Once the bat-teries are charged, Touchstone firmware estimates remaining capacity basedon internal hardware and the number of lines off-hook.

Charger firmware can indicate a ‘‘replace battery’’ condition, but does notprovide more precise data.Touchstone firmware bases its capacity estimateson assuming a good battery has most of its rated capacity, and a battery need-ing replacement has about half of its rated capacity.

Model 4 battery estimates provided by Touchstone firmware can vary signifi-cantly from actual capacity, but the algorithms attempt to provide a conserva-tive estimate. Theworst-case exception is when a battery is unable to hold acharge at all; the firmware assumes the battery capacity is about half of itsrated capacity, and the actual capacity is zero.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 20: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

4 Chapter 1

Po wer-related MIBObjects

The arrisMtaDe vBatter yOr deringCode MIB object displays the orderingcode of the installed battery. The following table lists the current batterytypes:

Code Description

710476 Model4 Battery718003 Model5/6 2.2Ah Battery721944 Model5/6 2.4Ah Battery718006 Model5/6 4.4Ah Battery721192 Model5/6 8.8Ah Battery

The same information is available in the CM State troubleshooting web page.See theTouchstone Telephony Troubleshooting Guidefor other informationabout the web interface.

Controlling Bat-ter y Testing

On Model5 and Model6 Telephony Modems, Touchstone firmware periodi-cally performs a battery capacity test to determine whether the battery needsto be replaced.The capacity test is performed (after initially charging thebattery) when the Telephony Modem is powered up (either for the first timeor after replacing a battery), and every 180 days afterward. Thecapacity test,including initial charging, may last 3 to 6 days.

On Model4 Telephony Modems, Touchstone firmware charges the battery tocapacity on power up or after replacing the battery. The firmware performsthe capacity test on the third day after charging, and then every 180 days.

Use the following MIB objects to view or change the testing interval, pausethe interval timer, or start a test immediately.

• arrisMtaDevPwrSuppl yBatter yT estTime A read-only object thatshows the time (in days) to the next capacity test.A value of0xff (255)indicates that the timer has been paused.

• arrisMtaDevPwrSuppl yBatter yT est The object that controls the bat-tery test schedule. It can take the following values:

testScheduled (0)When written, resumes the battery test scheduler at its currentvalue. Whenread, indicates that the battery test runs when thescheduled time expires.

disableAutoTesting (1)When written, pauses the battery test scheduler at its currentvalue.

When read, indicates that the battery test never runs — exceptwhen the battery is removed and replaced, the test runs immedi-ately. Once the test completes, the pause status is still in effect.Therefore, the battery test does not run a second time.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 21: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 5

testInProgress (2)When written, starts the battery test cycle immediately and resetsthe test scheduler to its default value of 180 days. This commandis ignored if there is a test in progress.When read, indicates thata test is in progress.

testPending (3)This is a read-only value.

If a battery test is in progress, and either: AC power is lost or afull charge is requested, the battery test is paused and the status isreported as pending. When AC power is restored, or the fullcharge period expires, the battery test that was in progress beforethe event resumes.

Use thearrisMtaDevPwrSupplyTestedBatCapacity MIB object to view themeasured battery capacity. The Telephony Modem uses this value to deter-mine typical hold-up times.

Batter yOver-TemperatureProtection

TS5.0 MSUP and later versions of Touchstone firmware provides provision-able control over the behavior of the Model5 and Model6 battery chargercircuitry at high temperatures. When enabled, the Telephony Modem raises awarning alarm when a provisionable temperature is exceeded (the default is60°C), and shuts down the charger and disconnects the battery if the tempera-ture exceeds 90°C.

Note: The TM602 does not allow disabling of over-temperature protection,but does allow changing the alarm temperature.

CAUTIONPotentiall y Ser vice-aff ectingIf a fire or other emergency causes the Telephony Modem to reach a tempera-ture of 90°C, enabling this feature could potentially remove power to theTelephony Modem and prevent the subscriber from calling emergency ser-vices.

Three MIB objects provide monitoring and control of the battery over-tem-perature protection feature.

arrisMtaDevPwrSupplyOverTempAlarmControlSet toenable (1) to enable battery over-temperature protection, ordisable (0) (default) to disable. The TM602 does not allow dis-abling of over-temperature protection.

arrisMtaDevPwrSupplyOverTempAlarmThresholdThe temperature, in degrees C,when the Telephony Modem raisesthe ‘‘Charger Temperature High’’ alarm. Valid range:50 to 70 (°C).Default:60.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 22: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

6 Chapter 1

arrisMtaDevPwrSupplyTemperatureA read-only object, showing the current charger temperature indegrees C.The charger temperature is available only when thearrisMtaDevPwrSupplyOverTempAlarmControl MIB object isenabled.

Note that the charger temperature does not necessarily correspond toambient temperature.

The values of these MIB objects are available on the MTA Status web page(see theTouchstone Telephony Troubleshooting Guide) when the chargerover-temperature protection feature is enabled.

TS6.1 and later versions of Touchstone firmware provide a feature to recordand report the historic high charger temperature:

arrisMtaDevPwrSupplyHighestTemperatureProvides the highest temperature, in degrees C,recorded by the bat-tery charger.

arrisMtaDevPwrSupplyHighestTemperatureTimeProvides the date and time that the eMTA recorded the high temper-ature.

arrisMtaDevPwrSupplyHighestTemperatureClearResets the highest temperature and time data.

CLI Commands

The CLI Telemetryalarm command lets you view and configure the status ofthe charger over-temperature protection feature.

The CLI Telemetryhitempbatsd command controls the high-temperaturebattery shutdown feature for TM602G/CT Telephony Modems.

See theTouchstone Telephony Troubleshooting Guidefor more details aboutthese commands.

Po wer-related MIBObjects

The CLAB-UPS-MIB lists RFC 1628 MIB objects that are required by Pack-etCable 1.5. ARRIS implements a subset of this MIB, and provides morepower-related information in the ARRIS-MTA-DEVICE-MIB. Both thePacketCable and ARRIS MIBs provide power and battery status; the ARRISMIBs provide some control over the behavior of the Telephony Modemcharging system. This section lists the supported objects.

RFC 1628 MIB Objects

These objects are required by PacketCable 1.5.TS6.1 and later versions ofTouchstone firmware support all battery backup objects required by Packet-Cable 1.5.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 23: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 7

upsIdentManufacturerThe name of the UPS manufacturer. For Touchstone TelephonyModems, this object always contains the string ‘‘A RRIS Interactive,L.L.C.’’

upsIdentModelThe model name or number of the UPS.

upsIdentAg entSoftwareV ersionThe UPS agent software version.

upsIdentNameA customer-designated string identifying the UPS.

upsIdentAttachedDevicesA customer-designated string identifying devices attached to theUPS output.

upsBatter yStatusThe current battery capacity status, one of:

• batter yNormal (2)—the remaining hold-up time is greater thanthe configuredupsConfigLowBattTime .

• batter yLo w(3)—the remaining hold-up time is less than the con-figuredupsConfigLowBattTime .

• batter yDepleted (4)—if AC power is present, the battery does nothave the capacity to sustain the load if AC power is lost. If ACpower is not present, shutdown is imminent.

upsSecondsOnBatter yIf the unit is on battery power, the elapsed time since the UPS lastswitched to battery power, or the time since the network manage-ment subsystem was last restarted, whichever is less. IfAC poweris present, this object returns0.

upsEstimatedMinutesRemainingThe estimated time, in minutes, to battery charge depletion underthe current load conditions if AC power is off and remains off, or ifAC power were to be lost and remain off.

upsEstimatedChar geRemainingThe estimated battery charge remaining, express as a percentage offull charge.

upsInputNumLinesThe number of input lines; also the number of rows in theupsInput-Table.

upsOutputSourceThe output power source; one of:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 24: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

8 Chapter 1

• none (2) (theupsShutdownAfterDelay MIB object is set to0; theTelephony Modem will shut down if AC power is lost)

• normal (3)

• batter y (5)

upsOutputNumLinesThe number of output lines; also the number of rows in theupsOut-putTable .

upsAlarmsPresentThe number of active alarm conditions.

upsAlarmDescrA reference to an alarm description object.

upsAlarmTimeStores the sysUpTime value when the alarm condition wasdetected. Avalue of 0 indicates that the alarm condition waspresent before the eMTA’ s SNMP agent started up.

upsConfigLowBattTimeThe value ofupsEstimatedMinutesRemaining at which a ‘‘lowbattery’’ condition is declared.This object may be changed anddefaults to60 (minutes).

upsShutdownTypeSpecifies the type of UPS shutdown to perform. TS6.1 supportsonly theoutput (1) type (do not provide battery power in the eventof an AC failure).

upsShutdownAfterDelayShuts off the UPS output after the specified time (in seconds).Validrange:1 to 604800 (7 days), or−1 (the default) to disable the timer.

This object cannot be set on TM402, TM508, and TM512 Tele-phony Modems and always returns−1.

upsStar tupAfterDela yTurns on the UPS output after the specified time (in seconds),assuming that the UPS output is currently off. Valid range:1 to604800 (7 days), or−1 (the default) to disable the timer.

This object cannot be set on TM402, TM508, and TM512 Tele-phony Modems and always returns−1.

upsRebootWithDurationImmediately executes the specifiedupsShutdownType for thespecified time (in seconds). After this period, the eMTA enables theUPS output.Valid range:1 to 604800 (7 days), or−1 (the default)to disable the timer.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 25: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 9

This object cannot be set on TM402, TM508, and TM512 Tele-phony Modems and always returns−1.

ARRIS Batter y MIB Objects

arrisMtaDe vBatter yOr deringCodeThe ordering code of the installed battery. The following table liststhe current battery types:

Code Description

710476 Model4 Battery718003 Model5/6 2.2Ah Battery721944 Model5/6 2.4Ah Battery718006 Model5/6 4.4Ah Battery721192 Model5/6 8.8Ah Battery

The same information is available in the CM State troubleshootingweb page. See theTouchstone Telephony Troubleshooting Guideforother information about the web interface.

arrisMtaDe vBatter yEpr omContains a semicolon-delimited text string; the fields (in order) areas follows:

• EPROM Data Revision

• PCB Assy Part Number

• PCB Assembly Revision

• PCB Assembly Test Code

• Cell Manufacturer

• Cell Manufacturer Factory Location

• Cell Lot

• Cell Capacity

• Pack Serial Number

• Pack Test Code

Example:

A;00884;C;ee;MI;1;018603;22;08065000715;ee;

arrisMtaDe vBatter yChar gerFWRevThe battery charger firmware revision.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 26: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

10 Chapter 1

arrisMtaDevPwrSupplyEnableDataShutdownEnables or disables automatic shutdown of data services, but nottelephony services, after the Telephony Modem has been using bat-tery power for a specified period of time. The default value for thisobject isenabled (1). Setto disabled (2) to maintain data communi-cations during a power outage.

arrisMtaDevPwrSupplyEnableDataShutdownTimeIndicates the timeout period, in seconds, that the Telephony Modemcontinues to provide data services after loss of AC power. The timerstarts when the Telephony Modem loses AC power. After the timerexpires, the Telephony Modem shuts down data services—Ethernet(all models) and USB (Model5 and newer)—to conserve batterycapacity. The default value for this object is900 seconds (15 min-utes).

arrisMtaDevPwrSupplyLo wBatter yThreshSets the low battery threshold, in units of 10watt*minutes/count.The initial default value is equivalent to 1 hour of holdup time.

Note: This object is supported only on Model5 and newer Tele-phony Modems.

arrisMtaDevPwrSupplyTypicalIdlePwrThe typical idle power, in 50 mW units. EacheMTA provides itsown estimated value for this object.It is used in conjunction withthe Tested Battery Capacity, Low Battery Threshold, and theReplace Battery Threshold to determine when to raise the ReplaceBattery alarm or the Low Battery Alarm.

Note: This object is supported only on Model5 and newer Tele-phony Modems.

arrisMtaDevPwrSupplyReplaceBatThreshThe minimum acceptable battery charge, in 10watt*minutes units,needed to achieve the desired End of Life holdup time based on typ-ical idle power. If the Tested Battery Capacity minus the ChargeHysteresis loss (20%) is less than this value, the eMTA raises aReplace Battery alarm. The default value provides 1hour of holduptime; the operator may change the threshold as needed.

Note: This object is supported only on Model5 and newer Tele-phony Modems.

arrisMtaDevPwrSupplyChar geStateThe value, in 10 watt*minutes units, to which the eMTA charges thebattery. Changing this value causes the charger to enter a dis-charge/charge cycle. Thisobject should be used with discretion.

Note: This object is supported only on Model5 and newer Tele-phony Modems.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 27: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 11

arrisMtaDevPwrSuppl yBatter yT estControls scheduling of the battery test. See ‘‘Controlling BatteryTesting’’ on page 4 for details.

arrisMtaDevPwrSupplyConfigRunTimeThe estimated available battery hold-up time, in minutes, basedupon the unit’s typical idle power and the programmed batterycharge setting.

The available battery hold-up time may be adjusted using this value.Setting the run-time to a lower value extends the total service life ofthe battery. Increasing the run-time in turn decreases the total ser-vice life of the battery.

Setting this value greater thanarrisMtaDevPwrSupplyBatA vail-ableMinutes does not provide a run-time greater thanarrisMtaDev-PwrSupplyBatA vailableMinutes . This object may be set only inmultiples of 5 minutes.

arrisMtaDevPwrSupplyConfigReplaceBatTimeThe replace battery threshold, in terms of run-time minutes.If abattery’s capacity has degraded to a point where it can no longerprovide more than the specified amount of run-time, the eMTA acti-vates the Replace Battery condition.The default value at power upis 60 minutes. This value can only be set to multiples of 5 minutes.

arrisMtaDevPwrSupplyFullChar geTimeThe time, in days, that the battery is charged and maintained at100% of its rated voltage. Afterthis time has elapsed, the batterycharge level is returned to the value specified byarrisMtaDevPwr-SupplyChar geState .

Valid range:0 to 16 (days). If the value is not zero, changing thevalue to0 aborts the full charge state and the battery charge returnsto the set charge state, or the test resumes if pending.

Note: This object is supported only on Model5 and newer Tele-phony Modems.

arrisMtaDevPwrSupplyHiT empBatter yShutdo wnControl(TM602G/CT Telephony Modems only) Controls the high-tempera-ture battery shutdown feature. When enabled, the TelephonyModem shuts off the battery if the battery temperature reaches 75°C±10%. TheTelephony Modem turns the battery on again when thebattery temperature falls to 65°C±10%.

arrisMtaDevPwrSupplyHighestTemperatureProvides the highest temperature, in degrees C,recorded by the bat-tery charger.

Note: This object is supported only on TM502, TM504, WTM552,and all Model6 Telephony Modems equipped with a battery. Onunsupported devices, this object always returns0.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 28: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

12 Chapter 1

arrisMtaDevPwrSupplyHighestTemperatureTimeProvides the date and time that the eMTA recorded the high temper-ature. Note: This object is supported only on TM502, TM504,WTM552, and all Model6 Telephony Modems equipped with a bat-tery. On unsupported devices, this object always returns a value of1970-1-1,0:0:0:0 (midnight, January 1, 1970).

arrisMtaDevPwrSupplyHighestTemperatureClearResets the highest temperature and time data.

arrisMtaDe vBatter yStatusEntr yStatus information for a single battery pack. An entry in thearris-MtaDevBatter yStatusT able exists for each battery pack containedin the device.

arrisMtaDe vBatter yOperStateCurrent operational status of the Lithium-Ion battery pack:unavailable (0), invalid (1), shutdownWarning (2), batter y-ReversedShor ted (3), batter yLowreplaceBatter y acFail (4),batter yLowreplaceBatter y (5), batter yLo wacFail (6), batter y-Low (7), batter yMissing (8), acFailreplaceBatter y (9), replaceBat-ter y (10), acFail (11), normal (12), testInProgress (13) (the MTA istesting the battery)

In versions previous to TS5.0, this object was available only if theMTA had a valid IP address.In TS5.0 and later versions, this objectis available when the CM has a valid IP address as well.

arrisMtaDe vBatter yLastStateChang eThe value ofsysUpTime when the battery entered its current opera-tional state.If the current state has not changed since the eMTA lastre-initialized, this object contains a zero value.

arrisMtaDe vBatter yOperSubStateA string containing the current sub-state of the battery.

arrisMtaDevPwrSuppl yBatter yT estTimeThe value of the test timer scheduler, in days. If the value is 0xFF(255), the timer has been paused.

arrisMtaDevPwrSupplyRatedBatCapacityThe rated capacity of the battery, in 10 watt*minutes units.

arrisMtaDevPwrSupplyTestedBatCapacityThe measured battery capacity, in 10 watt*minutes units, as deter-mined by the last battery test cycle.

arrisMtaDevPwrSupplyBatStateOfChar geThe present battery state of charge, in 10watt*minutes units. Thisvalue is approximate and is re-calibrated following a battery testcycle.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 29: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 13

arrisMtaDevPwrSuppl yReadBatter yPwrThe present load power, as an eight-second moving average, in 0.1watt units. When AC power is not present, this is the power beingremoved from the battery. When the eMTA is charging the battery,this is the power being applied.

arrisMtaDevPwrSuppl ySecondsOnBatter yThe amount of time, in seconds, that the eMTA has been running onbattery power.

arrisMtaDevPwrSupplyBatRatedMinutesThe estimated battery hold-up time, in minutes, based upon the idlepower and the rated capacity of the battery when fully charged.

arrisMtaDevPwrSupplyBatA vailableMinutesThe estimated available battery hold-up time, in minutes, basedupon the idle power and the tested capacity of the battery when fullycharged.

SNMP Batter y Telemetr y States (TM502, TM504, TM602, TM604)

Telemetry states for Model5 and Model6 Telephony Modems, with up tofour available lines (for example: TM502, TM504, TM602, TM604), can becompletely described by using thearrisMtaDe vBatter yOperState andarris-MtaDevBatter yOperSubState MIB objects. The following table showswhich sub-states are associated with each state.

Each battery state has an associated ‘‘Power Supply Telemetry’’ l og andalarm. For more information about battery states and required action (if any),see theTouchstone Telephony Troubleshooting Guide.

State Sub-State

unavailable(0) Charger Failure

invalid(1) N/A

shutdownWarning(2) N/A

batteryReversedShorted(3) N/A

batteryLow-replaceBattery- AC-Fail & Replace Bat & Bat Low

acFail(4) Test is Pending, AC-Fail, Replace Battery, Battery Low

batteryLow-replaceBattery(5) N/A

AC-Fail & Battery Low

Test is Pending, AC-Fail, Battery LowbatteryLow-acFail(6)

batteryLow(7) N/A

batteryMissing(8) BatteryMissing

AC-Fail & Replace Battery

Test is Pending, AC-Fail, Replace BatteryacFail-replaceBattery(9)

Management Guide Release 6.1 Standard 1.3 June 2009

Page 30: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

14 Chapter 1

State Sub-State

Battery OFF & Replace Battery

Replace Battery

Replace Battery & Battery Low

Battery is Charging & Replace Battery

Battery is Charging & Replace Battery & Battery Low

Battery Test Load ON & Replace Battery

Battery Test Load ON & Replace Battery & Battery Low

Test in Progress, Replace Battery

Test in Progress, Replace Battery, Battery Low

Test in Progress, Battery is Charging & Rpl Bat

Test in Progress, Battery is Charging & Rpl Bat & Bat Low

Test is Pending, Replace Battery

Test is Pending, Replace Battery, Battery Low

Test is Pending, Battery is Charging & Rpl Bat

Test is Pending, Battery is Charging & Rpl Bat & Bat Low

Battery OFF & Replace Battery & Battery Low

replaceBattery(10)

AC-Fail

Test is Pending, AC-FailacFail(11)

Battery is Turned OFF

Battery Backup Normal

Battery Low

Battery is Charging & Backup is Normal

Battery is Charging & Battery Low

Battery Test Load ON & Backup is Normal

Battery Test Load ON & Battery Low

Test in Progress

Test in Progress, Battery Low

Test in Progress, Battery is Charging

Test in Progress, Battery is Charging & Bat Low

Test is Pending

Test is Pending, Battery Low

Test is Pending, Battery is Charging

Test is Pending, Battery is Charging & Bat Low

normal(12)

Test in Progress, Battery Test Load ON

Test in Progress, Battery Test Load ON & Rpl Bat

Test in Progress, Battery Test Load ON & Bat Low

Test in Progress, Battery Test Load ON & Rpl Bat & Bat Low

testInProgress(13)

chargerFailure(14) N/A

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 31: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 15

SNMP Batter y Telemetr y States (TM508, TM512, TM608)

The following table shows battery telemetry sub-states associated with eachstate for TM508 and TM512 Multi-Line Telephony Modems.

Each battery state has an associated ‘‘Power Supply Telemetry’’ l og andalarm. For more information about battery states and required action (if any),see theTouchstone Telephony Troubleshooting Guide.

State Sub-State

unavailable(0) Charger Failureinvalid(1) N/AshutdownWarning(2) N/AbatteryReversedShorted(3) N/AbatteryLow-replaceBattery-acFail(4) AC-Fail & Replace Bat & Bat LowbatteryLow-replaceBattery(5) Batteryis Charging & Replace BatterybatteryLow-acFail(6) N/AbatteryLow(7) Batteryis ChargingbatteryMissing(8) N/AacFail-replaceBattery(9) N/AreplaceBattery(10) N/AacFail(11) N/Anormal(12) N/AtestInProgress(13) N/AchargerFailure(14) N/A

TM508/512Telemetr y BlockPinouts

The Telemetry block provides an interface between the signals from an ACpower supply with battery backup and the TM508/512 Telephony Modemnetwork management agent. The following diagram shows the Telemetryblock and the contacts.

Telemetr y

1 2 3 4 Rtn

The following table defines the function of each contact in the Telemetryblock. When the Telephony Modem detects a short between RTN andanother contact, it generates the alarm shown.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 32: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

16 Chapter 1

Contact Alarm Generated

1 AC Fail2 Replace Battery3 Battery Missing4 Battery Low

RTN (telemetry return line) not applicable

Considerations forthe 8-cell Battery

An 8.8Ah (8-cell) battery is available for use in TM504 Telephony Modems,with TS5.2 and newer versions of Touchstone firmware. TS5.3supports the8-cell battery for use with Model6 and newer Telephony Modems. Thebat-tery can be installed in TM502 and WTM552 Telephony Modems, but thecharger hardware does not support the battery capacity. Like other Model5and Model6 compatible batteries, the 8.8Ah battery is physically incompati-ble with Model 4 Telephony Modems.

This section describes Touchstone firmware behavior with 8.8Ah batteries.

TS5.0 and Earlier Behavior

If an 8.8Ah battery is installed in any Telephony Modem, Touchstonefirmware behaves as follows.

• New batteries are charged to about 50% of capacity at the factorybefore shipping.If the battery is new from the factory, the TelephonyModem attempts to charge the battery but fails after about 36 hours.

After failing to charge the battery, Touchstone firmware raises ‘‘ReplaceBattery’’ and ‘‘Battery Low’’ alarms and disables the battery pack.TheTelephony Modem does not provide battery back-up in this case.

• If the battery is charged to more than about 60% of capacity beforeinstallation, the Telephony Modem may be able to charge the battery.The battery pack performs as a 2-cell (3.2Ah) battery pack until the bat-tery is discharged (as a result of AC power loss or a scheduled batterytest).

After the battery is discharged, the Telephony Modem fails to rechargethe battery and raises alarms as described above.

In either case, the battery part number is set to ‘‘Contact ARRIS.’’ T he serialnumber may display properly, depending on the MTA hardware revision.

TS5.1 Behavior

TS5.1 recognizes the 8-cell battery pack but does not support its use.Installing the 8-cell battery pack in a Telephony Modem raises ‘‘Replace Bat-tery’’ and ‘‘Battery Low’’ alarms.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 33: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 17

The battery part number is set to ‘‘Contact ARRIS (Code00).’’ T he serialnumber may display properly, depending on the MTA hardware revision.

DTM602 Consider-ations

TS6.1 supports the DTM602, a Telephony Modem with an embedded DECTbase. TheDECT hardware (base and handset) communicate with a Casabi(Vtech) CasaWare server that can provide firmware updates to the DECTmodules, web content features, and other value-added content.

The DECT base is internally bridged to the Telephony Modem Ethernet portand telephony Line 1. When AC power is removed, the Ethernet hardwareshuts down to save power. The DECT handset can make and receive calls,but access to extended features is disabled.

Monitoring MT A Prov isioning Status

ThearrisMtaDevPr ovState MIB reports the current provisioning state of theMTA. The possible values of this MIB object represent the following stepsof the provisioning sequence, and depend on the provisioning method used:

• dhcpBound (1)

• dnsReqPr ovSvrIP (2)

• kdcHostNameDnsReq (3)

• kdcHostNameDnsRply (4)

• kdcIpDnsReq (5)

• kdcIpDnsRply (6)

• asReqSent (7)

• asRplyRcvd (8)

• tgsReqSent (9)

• tgsRplyRcvd (10)

• apReqSent (11)

• apRplyRcvd (12)

• enrollmentInform (13)

• cfgUrlSet (14)

• dnsReqTftpSvrIp (15)

• cfgFileReq (16)

Management Guide Release 6.1 Standard 1.3 June 2009

Page 34: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

18 Chapter 1

• rcvCfgFile (17)

• syslogMsgPr ovComplete (18)

• statusInform (19)

• provcomplete (20)

The following table shows the provisioning states that can be reported foreach provisioning method.

Provisioning Method States Reported

docsisOnly NonefullPacketCable enrollmentInform(13)

cfgUrlSet(14)dnsReqTftpSvrIp(15)cfgFileReq(16)rcvCfgFile(17)syslogMsgProvComplete(18)statusInform(19)provcomplete(20)

PacketCableMinusKDC dhcpBound(1)dnsReqProvSvrIP(2)enrollmentInform(13)cfgUrlSet(14)dnsReqTftpSvrIp(15)cfgFileReq(16)rcvCfgFile(17)syslogMsgProvComplete(18)statusInform(19)provcomplete(20)

Gupi,gupiEncryptedMtaConfig,gupiMacMta,gupiEncryptedMacMta

dhcpBound(1)dnsReqProvSvrIP(2)dnsReqTftpSvrIp(15)cfgFileReq(16)rcvCfgFile(17)syslogMsgProvComplete(18)provcomplete(20)

singleMAC Nonebasic1 dhcpBound(1)

dnsReqProvSvrIP(2)dnsReqTftpSvrIp(15)cfgFileReq(16)rcvCfgFile(17)syslogMsgProvComplete(18)provcomplete(20)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 35: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 19

Provisioning Method States Reported

basic2 dhcpBound(1)dnsReqProvSvrIP(2)dnsReqTftpSvrIp(15)cfgFileReq(16)rcvCfgFile(17)syslogMsgProvComplete(18)statusInform(19)provcomplete(20)

Firmware UpgradeStatus

The arrisMtaDevSWUpgradeStatus MIB reports the current firmwareupgrade status of the device. Itsvalue is a direct copy of docsDevSwOper-Status . The possible values for this MIB are:

• inProgress (1)

• completeFromPr ov isioning (2)

• completeFromMgt (3)

• failed (4)

• other (5)

Monitoring Quarantined Events

An eMTA endpoint enters a state in which detected CallP events may bequarantined (buffered) for a number of reasons, defined in the PacketCableNCS specification (PKT-SP-EC-MGCP-C01-071129). Examplesof eventbuffering include:

• The endpoint enters the NOTIFICATION state when an outstandingNotify exists. Thisstate is exited when an ACK for the outstandingNotify is received.

• The endpoint enters the LOCKSTEP state at this point if the Notify waspreviously triggered in STEP (versus LOOP) mode as defined by theCall Server’s use of the Quarantine Handling parameter.

An event being quarantined does not necessarily indicate a service-affectingcondition. However, a sharp increase in the number of quarantined eventsmay indicate, for example, a network issue or an inefficiently designed CMS.This feature may also be useful in attempting to debug slow dial tone or nodial tone problems.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 36: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

20 Chapter 1

MonitoringQuarantine Status

For notification of a service-affecting condition where events may be quaran-tined and a loss of communications between the eMTA and the CMS hasoccurred, use the existing ‘‘Call Agent Loss of Communications’’ alarm, asexplained in theTouchstone Telephony Troubleshooting Guidesection ‘‘Inter-preting Alarms.’’

Monitoring Quar-antined EventsUsing the CLI

In addition to SNMP trap generation, Touchstone firmware provides addi-tional information using the CallPdmon CLI command:

Console> callpCall Processing> dmon

When CLI monitoring is active, the MTA continuously tracks the total num-ber of events quarantined per quarantine state. The internal quarantine statesare defined as follows:

• NOTIFICATION—an NCS Notify message is outstanding.

• LOCKSTEP—the endpoint is waiting for a new Request for Notifica-tion (RQNT).

• DISC_NOTIFICATION—an NCS Notify message is outstanding andthe endpoint is disconnected from the CMS (loss of communicationsdetected).

• PROC_LOCKSTEP_LINE—the endpoint is actively processing a line-based NCS message and is not yet complete (e.g. RQNT).

• PROC_LOCKSTEP_CX—the endpoint is actively processing a con-nection-oriented NCS message and is not yet complete (e.g. MDCX).

• TDMIN—the endpoint is waiting for minimum time to wait betweenDISCONNECTED procedures before processing events.

• PERM_ERROR—the endpoint has received a permanent error (e.g.500 Unknown Endpoint) from the CMS to its RSIP message.

• Count of ‘‘No or Slow Dialtone’’ occurrences due to quarantine state—the number of off-hook events that are quarantined (delayed) due to theev ent being quarantined.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 37: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 21

Capturing Signaling Traces

CAUTIONPotential security breachThis feature allows NCS signaling messages to enter the network as cleartext. This breaks security as defined in the PacketCable Security specifica-tion. IPsecis used to secure the message link between the MTA and CMS to,among other things, keep the voice keys exchanged between endpointssecure. Unauthorizedpersonnel may potentially be able to monitor a sub-scriber’s voice traffic.

TS4.5 MSUP2 and newer loads can generate a Syslog report that contains afull signaling trace on a Touchstone eMTA. Individual signaling messagesmay be up to 4000 bytes in length. Since messages of this size would violatethe maximum message size limitations of the Syslog server, long messagesare broken into blocks of 128 bytes, time stamped, and numbered forreassembly. The MTA then sends the blocks to the Syslog server IP addressdefined during normal eMTA provisioning.

Signaling tracing is controlled using thearrisMtaDevEnableCallpSigTraceMIB object. You can enable or disable message tracing output on an eMTAusing an SNMP manager.

Note: Touchstone firmware supports this feature only for capturing NCS sig-naling traces.Support for capturing SIP signaling traces may be added in afuture release.

Controlling Signal-ing Tracing

Use thearrisMtaDevEnableCallpSigTrace MIB object (part of thearrisMta-DevBase MIB) to enable or disable signal tracing. The default value for thisMIB object isdisable (1).

CAUTIONPotential performance impactsThe number of messages expected as a result of enabling this feature canaffect the real-time performance of the eMTA, and may cause network con-gestion.

Set the MIB as follows:

• To enable signaling message tracing, set the object toEnable (1). Trac-ing continues until disabled using the MIB object, or the eMTA is reset.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 38: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

22 Chapter 1

• To disable signaling message tracing, set the MIB object toDisable (0).

Note: The signaling trace feature cannot be enabled through either the CMconfiguration file or the MTA configuration file.

Interpreting theSignaling TraceOutput Data

The following is an example of a single part transmission from the eMTA toa NCS Call server:

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03

2005 mta17.dev61 <44> <4115> <37> <00:13:11:23:23:E7>

<Xmit: (17: 1 of 1) - ’NTFY 8 aaln/[email protected] MGCP 1.0 NCS

1.0 X: 26002 O: hu ’>

The following is an example of a single part Receive from a NCS Call Serverto the eMTA:

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03

2005 mta17.dev61 <45> <4115> <38> <00:13:11:23:23:E7>

<Rcv: (19: 1 of 1) - ’200 8 OK ’>

The following output is part of the Syslog header, and appears in both Trans-mit and Receive trace messages.

Oct 21 10:55:04Syslog server Date and Time.

10.1.61.17The IP address of the MTA that sent the message.

Oct 21 10:55:03 2005The eMTA generated Data and Time.

mta17.dev61The FQDN of the eMTA.

<44>The Syslog message Event Number. It is incremented for each mes-sage in the Syslog.

<4115>The Arris Enterprise Number.

The following sections describe the transmit and receive data payloads.

Interpreting the Transmit Data P ayload

The following is an example of a single part transmission from the eMTA toa NCS Call server:

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 39: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 23

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03

2005 mta17.dev61 <44> <4115> <37> <00:13:11:23:23:E7>

<Xmit: (17: 1 of 1) - ’NTFY 8 aaln/[email protected] MGCP 1.0 NCS

1.0 X: 26002 O: hu ’>

The transmit message data can be broken down into two parts, the Headerand the signaling data itself.The header indicates that this is a transmittedmessage from the eMTA; it provides the sequence number of the message,the block number, total number of blocks in this message, and the payload ofthe signaling message.

The following table shows the data payload that is part of the transmit mes-sage trace. The first two parts comprise the header; the next two parts are theactual message.

<37>An Index number indicating that this is a transmitted message.Alltransmitted messages are of type 37.

<00:13:11:23:23:E7>The MAC address of the eMTA that transmitted the message.

Xmit: (17: 1 of 1) -All transmitted messages start with Xmit.The 17 is a messagesequence number. All transmitted messages have a unique sequencenumber that increases by one for each complete message transmit-ted. Thisinternal value is a 32-bit unsigned integer value that incre-ments only when tracing is active. Sequence numbers start at zero.The sequence numbers increment only when a message is sent tothe Syslog. The ‘‘1 of 1’’ i ndicates that this is part1 of a one partmessage. Allparts of the same message have the same sequencenumber.

’NTFY 8 aaln/[email protected] 1.0 NCS 1.0 X: 26002 O: hu ’

The actual signaling message data. The data is surrounded by singlequotes. Allsignaling messages are NULL terminated strings.

Interpreting the Receive Data P ayload

The following is an example of a single part Receive from a NCS Call Serverto the eMTA:

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03

2005 mta17.dev61 <45> <4115> <38> <00:13:11:23:23:E7>

<Rcv: (19: 1 of 1) - ’200 8 OK ’>

The receive message data can be broken down into two parts, the Header andthe signaling data. The header indicates that this is a signaling messagereceived by the eMTA; it provides the sequence number of the message, theblock number, total number of blocks in this message, and the signaling datareceived.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 40: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

24 Chapter 1

The following table shows the data payload that is part of a receive messagetrace:

<38>An index number indicating that this is a received signaling mes-sage. Allreceived messages are type 38.

<00:13:11:23:23:E7>The MAC address of the Message Destination.

Rcv: (19: 1 of 1)All received messages start withRcv:. The 19 is a messagesequence number. All received messages have a unique sequencenumber that increases by one for every complete message receivedby the eMTA. This internal value is a 32-bit unsigned integer valueand only increments when the tracing is active. Sequence numbersstart at zero. All messages have a unique sequence number. The ‘‘1of 1’’ i ndicates that this is part1 of a 1-part message. All parts ofthe same message have the same sequence number.

’200 8 OK ’The actual received signaling data. The data is surrounded by singlequotes.

Signaling Trace Feature Example Output

Below is a small sample output for a typical off-hook and on-hook sequencein NCS. In a real world situation on an actual network Syslog server, therecould be messages unrelated to this feature interleaved with these messages:

Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59

2005 mta17.dev61 <37> <4115> <37> <00:13:11:23:23:E7>

<Xmit: (14: 1 of 1) - ’NTFY 7 aaln/[email protected] MGCP 1.0 NCS

1.0 X: 25888 O: hd ’>

Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<38> <4115> <38> <00:13:11:23:23:E7> <Rcv: (16:

1 of 1) - ’200 7 OK ’>

Oct 21 10:55:00 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<39> <4115> <38> <00:13:11:23:23:E7> <Rcv: (17:

1 of 1) - ’RQNT 3752 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26001

S: Q: loop R: hf(I), hu(N) ’>

Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<40> <4115> <37> <00:13:11:23:23:E7> <Xmit: (15:

1 of 1) - ’200 3752 OK ’>

Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<41> <4115> <38> <00:13:11:23:23:E7> <Rcv: (18:

1 of 2) - ’RQNT 3753 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26002

D: (#|A|D|[2-9]11|0[2-9]11|0T|00|010|11X|[2-9]XXXXXX|[01][2-9]XXXXXXXXX|0’>

Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<42> <4115> <38> <00:13:11:23:23:E7> <Rcv: (18:

2 of 2) - ’1[1-9]XXXXX|10XXXX|X.#) S: dl R: hf(I,K), hu(N), oc,

of, [0-9*#T](D) ’>

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 41: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Managing Touchstone eMTAs 25

Oct 21 10:55:01 10.1.61.17 Oct 21 10:54:59 2005 mta17.dev61

<43> <4115> <37> <00:13:11:23:23:E7> <Xmit: (16:

1 of 1) - ’200 3753 OK ’>

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03 2005 mta17.dev61

<44> <4115> <37> <00:13:11:23:23:E7> <Xmit: (17:

1 of 1) - ’NTFY 8 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26002 O:

hu ’>

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03 2005 mta17.dev61

<45> <4115> <38> <00:13:11:23:23:E7> <Rcv: (19:

1 of 1) - ’200 8 OK ’>

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03 2005 mta17.dev61

<46> <4115> <38> <00:13:11:23:23:E7> <Rcv: (20:

1 of 1) - ’RQNT 3788 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26025

S: Q: loop R: hd(N) ’>

Oct 21 10:55:04 10.1.61.17 Oct 21 10:55:03 2005 mta17.dev61

<47> <4115> <37> <00:13:11:23:23:E7> <Xmit: (18:

1 of 1) - ’200 3788 OK’>

Oct 21 10:55:33 10.1.61.17 Oct 21 10:55:32 2005 mta17.dev61

<48> <4115> <37> <00:13:11:23:23:E7> <Xmit: (19:

1 of 1) - ’NTFY 9 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26025 O:

hd ’>

Oct 21 10:55:33 10.1.61.17 Oct 21 10:55:32 2005 mta17.dev61

<49> <4115> <38> <00:13:11:23:23:E7> <Rcv: (21:

1 of 1) - ’200 9 OK ’>

Oct 21 10:55:33 10.1.61.17 Oct 21 10:55:32 2005 mta17.dev61

<50> <4115> <38> <00:13:11:23:23:E7> <Rcv: (22:

1 of 1) - ’RQNT 3940 aaln/[email protected] MGCP 1.0 NCS 1.0 X: 26060

S: Q: loop R: hf(I), hu(N) ’>

Monitoring Device Parameters

Touchstone firmware provides a set of read-only MTA device parameter MIBobjects under the ARRIS-MTA-MIB. These objects comprise thearrisM-taDevParameters MIB.

arrisMtaDevMaxCpeAllowedReflects the ‘‘MaxCpeAllowed’’ parameter in the CM configurationfile.

arrisMtaDevNetworkAccessReflects the ‘‘NetworkAccess’’ parameter in the CM configurationfile.

arrisMtaDevLineParameterTableA table, indexed by line number, containing the following objects:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 42: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

26 Chapter 1

• arrisMtaDevInterfaceIndex —the value ofifIndex for the speci-fied line. For example, readingarrisMtaDevInterfaceIndex.2returns the interface index for line 2.

• arrisMtaDevPktcDevEvEndpointName —the value of the end-point name for the specified line.

The endpoint name format is:

AALN/X:fqdn/ipaddr

where X is the line number, fqdn is the fully qualified domainname (such asmta201.dev51) if available, andipaddr is the IPaddress of the MTA.

• arrisMtaDevActiveConnections —shows the number of activeconnections on the specified line whose mode is one of: receiveonly, send only, or send/receive. Inactive connections are notcounted.

arrisMtaDevUpSvcFlowParameterTableA table, indexed by service flow, containing the following objects:

• arrisMtaDevDocsQosParamUpSvdFlowSFID —the service flowSFID for the service flow. The value of this object is the value of‘‘ PcSfId’’ in the configuration file.

• arrisMtaDevDocsQosParamUpSvdFlowSchedulingType —reflects the value of ‘‘SfSchedulingType’’ in the configuration file.

arrisMtaDevQosModeReturns the value of the DSx/access-only DQoS bit (0x00004000)in the CallP feature switch. If the returned value is1, the MTA isoperating in DSx QoS mode.If the returned value is0, the MTA isusing Best Effort, full DQoS, or PCMM.

Example The following is the output of a MIB walk of the Device Parameters MIB onan operating Telephony Modem.

1: arrisMtaDevMaxCpeAllowed.0 (integer) 16

2: arrisMtaDevNetworkAccess.0 (integer) yes(1)

3: arrisMtaDevInterfaceIndex.1 (integer) 9

4: arrisMtaDevInterfaceIndex.2 (integer) 10

5: arrisMtaDevPktcDevEvEndpointName.1 (octet string) AALN/1:mta170s7.dev35/10.1.35.170

6: arrisMtaDevPktcDevEvEndpointName.2 (octet string) AALN/2:mta170s7.dev35/10.1.35.170

7: arrisMtaDevActiveConnections.1 (integer) 0

8: arrisMtaDevActiveConnections.2 (integer) 0

9: arrisMtaDevDocsQosParamUpSvcFlowSFID.1 (integer) 18559385

10: arrisMtaDevDocsQosParamUpSvcFlowSFID.2 (integer) 18559387

11: arrisMtaDevDocsQosParamUpSvcFlowSchedulingType.1 (integer) 2

12: arrisMtaDevDocsQosParamUpSvcFlowSchedulingType.2 (integer) 2

13: arrisMtaDevQosMode.0 (integer) bestEffort-FullDQos-PCMM(0)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 43: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

2 Using SNMP to MonitorNetwork Elements

This chapter describes cable modem and CMTS MIBs that can be used fornetwork or element monitoring.

Element Overview

For network management purposes, a network element (CMTS, cablemodem, or MTA) can be viewed as a collection of interfaces. TheifTableMIB contains an entry for each interface that is part of an element.

Note: Network management systems treat Touchstone Telephony Modems astwo separate devices, a cable modem and an MTA, with separate IPaddresses. Theexception is when using Single MAC provisioning mode.

Interface IndexScheme

Entries in theifTable are indexed by the ifIndex . Touchstone firmware gen-erally conforms to the eDOCSIS specification, CM-SP-eDOCSIS-I13-070803 section 5.2.2, forifIndex designations. For Touchstone productswith 1 to 4 lines, the eDOCSIS (and Touchstone)ifIndex designations are:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 44: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

28 Chapter 2

ifIndex Interface

1 Ethernet CPE Interface2 RF MAC Interface3 RF Downstream Interface4 RF Upstream Interface5 USB CPE Interface9 Telephone Line 1

10 Telephone Line 211 Telephone Line 3 (TM504, TP404)12 Telephone Line 4 (TM504, TP404)16 PacketCable Embedded Interface17 Reserved for eSTB-IP2618 Reserved for eSTB-DSG27

19–31 Reserved for other eDOCSIS interfaces32 + Other CPE interfaces

Telephony interfaces begin withifIndex 9. Notethat multi-line Touchstoneproducts (TM508 and TM512) conflict with the eDOCSIS specification,since the index range for telephony interfaces on these products is9 to 20(TM512) or9 to 16 (TM508).

ARRIS MIB Index-ing

Global MIB objects — those applying to the entire Telephony Modem, or tothe entire CM or MTA, use index 0. For example,arrisMtaDevLoopVolt-ag ePolic y.0 is the proper index for loop voltage policy settings. Theexcep-tion is for SIP MIB objects, which use index 1 for all global (non-table)objects.

MIB objects that apply to a single line are indexed by the line number:1 tothe maximum number of lines supported by the MTA. This applies to bothSIP and NCS loads.

Interface Types Each entry in theifTable has anifType that indicates the interface type asso-ciated with the entry. The ifType is one of the following:

ifType Description

6 Ethernet127 DOCSISMAC cable layer128 DOCSIScable downstream interface129 DOCSIScable upstream interface (DOCSIS 1.x)160 USB198 Telephony205 DOCSIScable upstream channel (DOCSIS 2.x)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 45: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Using SNMP to Monitor Networ k Elements 29

Subscriber Device MIBs

The following MIBs are available at the cable modem and MTA elements:

MIB Description

Traffic counters, addressingifTable

docsIfCmStatusTable DOCSIS error counters, transmit power, mod-ulationPower supply statusarrisMtaDevP owerSup-

plyTelemetr y

Local event logdocsDevEventTable

USB port configurationuserPor tTable

Upstream SID parameters and countersdocsIfCmSer viceT able

Reports the range delay value set by the CMTSarrisCmDe vRang eDela y

Line Status MIBs ThearrisMtaDevLineCard MIB object indicates the line card status:oos (0),idle (1), addressing (2), talking (3), frwd-disc (5), ringing (6), onhook-tx (7),protection (12),diags (13),plo (14).

Call Statistics Ob-jects

The following MIB objects provide basic call statistics for the MTA.

arrisMtaDevRtpTxPktsTotalThe total number of RTP packets transmitted, across all endpoints,since the MTA was started or reset.

arrisMtaDevRtpRxPktsTotalThe total number of RTP packets received, across all endpoints,since the MTA was started or reset.

arrisMtaDevRtpPktsLostTotalThe total number of RTP packets lost, across all endpoints, since theMTA was started or reset.

arrisMtaDevRtpPercentPktsLostTotalThe percentage of RTP packets lost, across all endpoints, since theMTA was started or reset.

arrisMtaDe vLastCallStar tTimeThe start time of the last call made from the MTA.

arrisMtaDevLastCallEndTimeThe end time of the last call made from the MTA.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 46: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

30 Chapter 2

Set thearrisMtaDevResetCallStats object totrue (1) to clear these counters.

See theTouchstone Telephony Troubleshooting Guidefor information aboutVoice Quality Monitoring, which provides detailed per-call statistics.

ARRIS RIPObjects

Touchstone firmware implements a subset of the RIPv2-MIB defined inRFC 1724.The following objects are those supported in TS6.1; other objectsin the RIPv2-MIB are not supported.

Note: The WTM552 and WTM652 can read and write these objects.For allother Telephony Modems, these objects are read-only.

rip2IfConfAddressThe IP Address of this system on the indicated subnet.For unnum-bered interfaces, the value is0.0.0.N, whereN is theifIndex for theinterface.

rip2IfConfDomainThe value inserted into the Routing Domain field of all RIP packetssent on this interface.

rip2IfConfAuthTypeThe type of authentication used on this interface, one of:noAuthen-tication (1) (the default),simplePass word (2), ormd5 (3).

rip2IfConfAuthK eyWhen rip2IfConfAuthType has a value other thannoAuthentica-tion, this object contains the authentication key. The key can be upto 16 octets long; shorter keys are padded with null characters.

Reading this object always results in an octet string of length zero.

rip2IfConfSendThe type of RIP updates sent on this interface, one of:doNot-Send(1) or ripVersion2 (2) (multicast RIPv2 updates, the default).

rip2IfConfReceiveWhich version of RIP updates are to be accepted, one of:rip2 (1),rip1OrRip2 (2) (the default), ordoNotRecieve (3). Note that rip2andrip1OrRip2 implies reception of multicast packets.

rip2IfConfDefaultMetricThe metric value to be used for the default route entry in RIPupdates originated on this interface. Avalue of zero indicates thatno default route should be originated; in this case, a default route viaanother router may be propagated. Valid range:0 through15.

Note: The Telephony Modem is always connected to a CMTSthrough the WAN interface, so the metric value is always 1.

rip2IfConfStatusWriting invalid deletes this interface.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 47: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Using SNMP to Monitor Networ k Elements 31

rip2IfConfSrcAddressThe IP address this system uses as a source address on this inter-face. If it is a numbered interface, this MUST be the same value asrip2IfConfAddress . On unnumbered interfaces, it must be thevalue of rip2IfConfAddress for some interface on the system.

CMTS MIBs

The following MIBs are available at the CMTS:

MIB Description

Traffic counters, addressingifTable

MAC-level countersdocsIfCmtsStatusTable

docsIfCmtsChannelUtiliza-tionTable

Traffic utilization for each physicalinterface on the CMTS. This tablemay be used to watch for heavytraffic that may cause interruptionsin telephony service.Local event logdocsDevEventTable

docsIfCmtsCmStatusTable Cable modem information andcounters kept by the CMTS. Thistable has an entry for each cablemodem recognized by the CMTS.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 48: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

32 Chapter 2

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 49: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

3 IPv6 Support

TS6.1 and later versions of Touchstone firmware provide IPv6 support inTouchstone CM550 Cable Modems and in the CM portion of the TelephonyModem. This document describes provisioning, management, and trou-bleshooting support for IPv6.

Note: Touchstone firmware enhances DOCSIS 2.0 support by providingDOCSIS 3.0 IPv6 support only on the cable modem portion of the eMTA.The MTA portion still operates only with IPv4 addresses.

About IPv6 Support

IPv6 allows cable operators to expand their IP address ranges for cablemodems, allowing reclamation of traditional IPv4 addresses for use withMTAs. TS6.1supports the following IPv6-related protocols:

• DHCPv6

• DNSv6

• TFTPv6

• TODv6

• SNMPv6

• TELNETv6

• HTTPv6

• SSHv6

Note: Touchstone firmware does not support Early Authentication andEncryption (EAE) functionality.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 50: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

34 Chapter 3

Prov isioning Notes

This section describes provisioning modes and flows appropriate to IPv6 sup-port. SeetheTouchstone Telephony Provisioning Guidefor configuration filesetup and related issues.

Prov isioningModes

Touchstone firmware supports the following provisioning modes for IPv6:

• SECURE (full PacketCable)

• BASIC.1/2 (PacketCable and ARRIS versions)

• HYBRID.1/2

• GUPI

• GUPI with Encrypted MTA config file

• PacketCable Minus KDC

Single MAC provisioning is explicitly not supported.

Selecting an Ad-dressing Mode

TS6.1 supports the DOCSIS 3.0 MAC Domain Descriptor (MDD) message,defined in theDOCSIS 3.0 MAC and Upper Layer Protocols Interface, CM-SP-MULPIv3.0-I04-070518, for selecting IPv4 or IPv6 addressing.The CMuses TLV 5.1 in the MDD to select the addressing mode as follows:

Value Addressing Mode

0 IPv41 IPv6

Alternate Provisioning Mode (APM):try IPv4 first, then IPv6

2

3 Not supported

If the eMTA does not find an MDD during provisioning, it always selectsIPv4 addressing.

DHCP Behavior forIPv6 Prov isioning

When the CM receives an MDD message that specifies IPv6 operation, itacquires its IP address according to theDOCSIS 3.0 MAC and Upper LayerProtocols Interface, CM-SP-MULPIv3.0-I04-070518. TS6.1supports bothSLAAC and DAD mechanisms.

TS6.1 supports the DHCPv6 options listed in the following table.Fordetails, see theDOCSIS 2.0 +IPv6 Cable Modem Technical Report, CM-TR-DOCSIS2.0-IPv6-V01-080307.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 51: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

IPv6 Support 35

Option # Sub-Option Name

1 Client Identifier option (DUID)2 Server Identifier Option3 IA_NA option (IPv6 address)6 Option Request Option

14 RapidCommit Option19 ReconfigureMessage option20 ReconfigureAccept Option17 Vendor-specific information option17 32 TFTP Server Addresses option17 33 Configuration File Name option17 34 Syslog Server Addresses option17 35 TLV5 Encoding17 36 DOCSIS Device Identifier option17 37 Time Protocol Servers option17 38 Time Offset option

TS6.1 supports the DHCP Reconfigure message described in RFC3315.Upon receiving a DHCP Reconfigure message, the CM validates the messagethen acquires updated DHCP parameters from the server.

Prov isioning FileNotes

The configuration file must be specific to either IPv6 or IPv4.If the plant hasmixed IPv4 and IPv6 CMs, you will need separate provisioning files for eachaddress type.

For IPv6 configuration, addresses must be fully qualified and cannot use anycompression. For example, an IPv6 address of2001:0200:0000:0000:0000:0000:0000:0022 cannot be entered as2001:0200::0022 .

TLV38 Enhance-ments

TS6.1 supports TLV38 (Notification) sub-type8 (SNMP notification IPv6address). Specifythis sub-TLV to send SNMP traps and informs to anIPv6-configured receiver.

Management

Managing Touchstone eMTAs using IPv6 addressing in the CM requireSNMP management software capable of handing both IPv4 & IPv6, or sepa-rate tools for CM and MTA.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 52: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

36 Chapter 3

Coexistence TS6.1 supports SNMP co-existence for both the ARRIS version of coexis-tence and coexistence using the coexistence MIBs.

The following is an example provisioning file fragment for setting up co-existence.

SnmpMib = snmpCommunityStatus.rocablelabs createAndGoSnmpMib = snmpCommunityName.rocablelabs "ro_cm"SnmpMib = snmpCommunitySecurityName.rocablelabs "rotesting1"SnmpMib = snmpCommunityStorageType.rocablelabs volatileSnmpMib = snmpCommunityStatus.rwcablelabs createAndGoSnmpMib = snmpCommunityName.rwcablelabs "rw_cm"SnmpMib = snmpCommunitySecurityName.rwcablelabs "rwtesting1"SnmpMib = snmpCommunityStorageType.rwcablelabs volatileSnmpMib = vacmSecurityToGroupStatus.1 rotesting1 createAndGoSnmpMib = vacmGroupName.1 rotesting1 "rotesting2"SnmpMib = vacmSecurityToGroupStorageType.1 rotesting1 volatileSnmpMib = vacmSecurityToGroupStatus.1 rwtesting1 createAndGoSnmpMib = vacmGroupName.1 rwtesting1 "rwtesting2"SnmpMib = vacmSecurityToGroupStorageType.1 rwtesting1 volatileSnmpMib = vacmSecurityToGroupStatus.2 rotesting1 createAndGoSnmpMib = vacmGroupName.2 rotesting1 "rotesting2"SnmpMib = vacmSecurityToGroupStorageType.2 rotesting1 volatileSnmpMib = vacmSecurityToGroupStatus.2 rwtesting1 createAndGoSnmpMib = vacmGroupName.2 rwtesting1 "rwtesting2"SnmpMib = vacmSecurityToGroupStorageType.2 rwtesting1 volatileSnmpMib = vacmAccessStatus.rotesting2 1 1 createAndGoSnmpMib = vacmAccessContextMatch.rotesting2 1 1 exactSnmpMib = vacmAccessReadViewName.rotesting2 1 1 "docsisManagerView"SnmpMib = vacmAccessStorageType.rotesting2 1 1 volatileSnmpMib = vacmAccessStatus.rwtesting2 1 1 createAndGoSnmpMib = vacmAccessContextMatch.rwtesting2 1 1 exactSnmpMib = vacmAccessReadViewName.rwtesting2 1 1 "docsisManagerView"SnmpMib = vacmAccessWriteViewName.rwtesting2 1 1 "docsisManagerView"SnmpMib = vacmAccessStorageType.rwtesting2 1 1 volatileSnmpMib = vacmAccessStatus.rotesting2 2 1 createAndGoSnmpMib = vacmAccessContextMatch.rotesting2 2 1 exactSnmpMib = vacmAccessReadViewName.rotesting2 2 1 "docsisManagerView"SnmpMib = vacmAccessStorageType.rotesting2 2 1 volatileSnmpMib = vacmAccessStatus.rwtesting2 2 1 createAndGoSnmpMib = vacmAccessContextMatch.rwtesting2 2 1 exactSnmpMib = vacmAccessReadViewName.rwtesting2 2 1 "docsisManagerView"SnmpMib = vacmAccessWriteViewName.rwtesting2 2 1 "docsisManagerView"SnmpMib = vacmAccessStorageType.rwtesting2 2 1 volatileSNMPV3Kickstart =

SNMPV3SecurityName = "docsisManager"SNMPV3PublicNumber = hexstr: C1.FC.52.36.97.06.C0.22.99.61.D5.CA.C5.

4F.C6.68.51.71.A8.DC.69.AB.EB.D6.21.AC.AC.1D.FC.A6.0A.3A.8E.77.B5.15.AB.AC.60.7C.5F.EB.AF.5F.86.B8.3F.2B.A1.DB.3D.ED.51.E2.EB.5D.E0.6A.EB.2D.AE.E3.A4.DA.AC.DA.30.42.DC.A2.3C.5B.FE.65.83.B8.B8.9E.48.02.FB.70.A5.E9.97.0C.95.9F.96.44.B4.BA.B4.2C.71.97.D1.1A.96.99.C9.4F.9C.53.3F.00.24.3E.1A.12.AB.23.CF.DB.05.6C.97.62.4B.B2.A3.FC.7D.91.F4.90.C7.7C

DHCPv6 MIB Ob-jects

The following MIB objects indicate the DHCP mode (v4 or v6) and assignedIP address:

docsDe vSer verDhcpAd dressTypeThe IP address type; one of:

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 53: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

IPv6 Support 37

1: DHCPv42: DHCPv63: IPv4 non-global address with a zone index4: IPv6 non-global address with a zone index

16: DNS domain name0: the IP address was statically assigned

docsDe vSer verDhcpAd dressThe IP address assigned to the CM, or an empty string if the IPaddress was statically assigned.

The following MIB objects indicate the IP address and type of the assignedtime and TFTP servers:

docsDe vSer verTimeAd dressTypeThe IP address type as defined bydocsDe vSer verDhcpAd-dressType .

docsDe vSer verTimeAd dressThe IP address of the time server.

docsDe vSer verConfigTftpAd dressTypeThe IP address type as defined bydocsDe vSer verDhcpAd-dressType .

docsDe vSer verConfigTftpAd dressThe IP address of the TFTP server.

The Syslog server address must be configured manually, either through anSNMP manager or the configuration file. In either case, the following twoobjects must be set in the order shown:

docsDevEvSyslogAddressTypeThe IP address type; either1 (IPv4) or2 (IPv6).

docsDevEvSyslogAddressThe IP address of the Syslog server, or a blank string to inhibit Sys-log transmission.

The following MIB objects provide IPv6-oriented display of other DHCPinformation. Theparallel IPv4-specific objects are still valid for use withIPv4 configurations, but may be deprecated in future releases.

arrisCmDevDhcpIpModeDisplays the current DHCP IP address mode; one of:

0: (null)1: IPv42: IPv6

The following objects use the IP address type specified in thisobject.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 54: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

38 Chapter 3

arrisCmDevDhcpCmIpAddrV6The currently-leased IPv6 address.

arrisCmDevDhcpCmSubNetMaskV6In IPv4 mode, the number of bits in the subnet mask.

in IPv6 mode, the prefix length.

arrisCmDevDhcpCmGatewayIpAddrV6The current IPv6 gateway address.

arrisCmDe vDhcpPrimar yDhcpSer verIpAd drV6The primary DHCP server IPv6 address.

arrisCmDevDhcpTftpSvrIpAddrV6The current TFTP server IPv6 address.

SNMP Access The CM expects SNMP access to use the same IP mode (IPv4 or IPv6) that itis provisioned with.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 55: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

4 SNMP Security

This chapter describes SNMP security features:

• configure the eMTA to control (restrict) SNMP access to the cablemodem MIB objects by Network Management Stations (NMS)

• configure the transmission of notifications (traps) on the cable modem

• create ‘‘cloned’’ User-based Security Modem (USM) users, based onexisting USM users

SNMP Access Mode Overview

Touchstone eMTAs support the following SNMP modes: SNMPv1,SNMPv2c, and SNMPv3 as well as SNMP-coexistence (RFC 2567).

The contents of the CM configuration file determines the eMTA’ s SNMPmode after registration:

• The CM runs in NmAccess mode if the CM configuration file containsonly docsDevNmAccessTable settings. With these settings, SNMPaccess is controlled by the entries in thedocsDevNmAccessTable .

• The CM runs in SNMP coexistence mode if the CM configuration filecontains any of the following:

– any snmpCommunityTable settings

– any TLV type 34.1 and 34.2 (SNMPv3 Kickstart User) elements

– any TLV type 38 (SNMPv3 Notification Receiver) elements

In SNMP coexistence mode, any configuration file entries made to thedocsDevNmAccessTable are ignored.

• If the configuration file does not contain any SNMP access controlitems (no docsDevNmAccessTable or snmpCommunityTable set-tings and no TLV 34.1/34.2 or TLV 38 elements, then the CM runs inNmAccess mode and SNMP access to MIB objects is unrestricted.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 56: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

40 Chapter 4

The rules for each SNMP access mode are described below.

SNMP Access Pol-icy (CM-side)

The following rules apply to SNMP access to CM MIBs:

• Before obtaining an IP address: no access.

• After obtaining an IP address, but before downloading the CM configu-ration file: any community string accepted, but the SNMP view isrestricted to read-only.

• After downloading the CM configuration file (with no communitystring defined): any community string accepted, all CM MIBs can beaccessed.

• After downloading the CM configuration file (with community stringdefined): only the defined community string accepted, all CM MIBs canbe accessed with the proper community string.

SNMP Access Pol-icy (MTA-side)

The following rules apply to SNMP access to MTA MIBs:

• Before obtaining an IP address: no access.

• After obtaining an IP address, but before downloading the MTA config-uration file: any community string accepted, all MTA MIBs can beaccessed.

• After downloading the MTA configuration file (with no communitystring defined): any community string accepted, all MTA MIBs can beaccessed.

• After downloading the MTA configuration file (with community stringdefined): only the defined community string accepted, all MTA MIBscan be accessed with the proper community string.

SNMPv1/v2cNmAccess Mode

The following rules apply in NmAccess mode:

• Only SNMPv1/v2c packets are processed.

• SNMPv3 packets are dropped.

• The docsDevNmAccessTable controls access and trap destinations asdescribed in RFC 2669.

• None of the SNMPv3 MIBs as defined in RFC2571 through RFC2576are accessible.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 57: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 41

SNMP Coexis-tence Mode

The following rules apply in SNMP Coexistence mode:

• SNMPv1/v2c/v3 Packets are processed as described by RFC2571through RFC 2576.

• ThedocsDevNmAccessTable is not accessible.

• Access control and trap destinations are determined by thesnmpCom-munityTable , Notification MIB, Target MIB, VACM-MIB, and USM-MIB.

• The Community MIB controls the translation of the SNMPv1/v2cpacket community string into a security name that selects entries in theUSM MIB. Access control is provided by the VACM MIB.

• The USM MIB and VACM MIB controls SNMPv3 packets.

• Trap destinations are specified in the Target MIB and Notification MIB.

SNMP Coexis-tence Types

There are three different types of SNMP coexistence that can be configured.

Note 1: VACM table group names must be unique within the MTA and CMconfiguration files.

Note 2: Although SNMPv1/v2c or SNMPv1/v2c/v3 coexistence modes areenabled as shown below, SNMPv1 and v2c access via community strings isgranted only if the community table,vacmSecurityToGroupTable , andvacmAccessTable parameters are provisioned in the configuration file.

SNMPv1/v2c-onl y Coexistence

SNMPv1/v2c coexistence takes effect if the configuration file contains:

• Any TLV-11 Coexistence Settings (i.e.snmpCommunityMIB , vacm-SecurityToGroupTable , vacmAccessTable ) OR

• Any SNMPv3 Notification Receiver (TLV-38) elements and noSNMPv3 Kickstart (TLV-34) elements.

The cable modem only accepts SNMPv1/v2c packets in this mode.

SNMPv1/v2c/v3 Coexistence

SNMPv1/v2c/v3 coexistence takes effect if the configuration file contains allof the following:

• Any TLV-11 Coexistence Settings (i.e.snmpCommunityMIB , vacm-SecurityToGroupTable , vacmAccessTable )

Management Guide Release 6.1 Standard 1.3 June 2009

Page 58: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

42 Chapter 4

• any SNMPv3 Kickstart (TLV-34) elements

The cable modem accepts SNMPv1/v2c/v3 packets in this mode.

SNMPv3-onl y Coexistence

SNMPv3 coexistence takes effect if the configuration file contains both:

• Any SNMPv3 Kickstart (TLV-34) elements

• NO coexistence settings

The cable modem only accepts SNMPv3 packets in this mode.

Configuring the Cable Modem for NmAccess Mode

When the CM is in SNMPv1/v2cdocsDevNmAccess mode, thedocs-DevNmAccessTable controls SNMP access and SNMP trap destinations asdescribed in the DOCS-CABLE-DEVICE-MIB (RFC2669). Thereare sev-eral different ways in which the table can be configured depending on whattype of SNMP access and trap filtering you want to apply to the modem.This section describes a basic setup.

Configuring SNMPAccess with thedocsDevNm-AccessTable

The simplest way to configure the SNMP access filtering—configuring auser-defined community string for access—is to create one or moredocs-DevNmAccessTable entries within the cable modem configuration file.Touchstone firmware supports up to 32 NmAccess entries on ARRIS CMdevices: CM300, CM450, Telephony Modems, Telephony Ports, etc.

Create a table row by setting thedocsDevNmAccessStatus MIB object to avalue of createAndGo (4) and thedocsDevNmAccessCommunity MIBobject to a user-defined community string; for example,my_pass word . Thiscreates an entry in the table with the following default parameters.This entryallows read-only SNMP access to the CM from any NMS using a communitystring ofmy_pass word :

docsDevNmAccessIp.1 (ipaddress) = 255.255.255.255

docsDevNmAccessIpMask.1 (ipaddress) = 0.0.0.0

docsDevNmAccessCommunity.1 (octet string) = my_password

/* Your password, use whatever string you like. */

docsDevNmAccessControl.1 (integer) = read(2)

/* Allow read-only access */

docsDevNmAccessInterfaces.1 (octet string) = FF (hex)

/* Allow access from all interfaces of the cable modem */

docsDevNmAccessStatus.1 (integer) = active(1)

/* createAndGo(4) will automatically go to active(1) */

docsDevNmAccessTrapVersion.1 (integer) = DisableSNMPv2trap(1)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 59: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 43

Note: The other objects of the table row entry are set to their default valuesunless you also add them to the configuration file.

The ‘‘.1’’ is the instance (or index) value of this particular table entry. It doesnot have to be a 1, it can be any number. You can create up to 32 entries inthe configuration file, depending on how you want to setup the SNMP Accessfiltering.

The above description is a basic setup, but you can configure the NmAccessentry in additional ways. For example, allow read and write access for theabove entry by setting thedocsDevNmAccessControl MIB object toread-Write (3) in the configuration file.You can also configure which of themodem’s interfaces you want to grant access to by changingdocsDev-NmAccessInterfaces accordingly (see below), etc. The section belowdescribes how to setup trap transmission using thedocsDevNmAccess-Table.

Configuring TrapTransmissionwith the docsDev-NmAccessTable

To enable trap transmission, three objects in thedocsDevNmAccessTableMUST be configured to specific values:docsDevNmAccessIp , docsDev-NmAccessIpMask , and docsDevNmAccessControl . A fourth object,docsDevNmAccessTrapVersion , can optionally be configured to enable ordisable SNMPv2 traps. It the TrapVersion object is not configured, then itsvalue defaults toDisableSNMPv2trap (1) and SNMPv1 traps are sent for thatparticular row entry.

Note: DisableSNMPv2trap (1) may appear asversion (1) in the PacketACEConfiguration Editor.

For trap transmission, the relevant objects, highlighted in bold, MUST beconfigured as shown below:

docsDevNmAccessIp.15 (ipaddress)

= (IP address of your Trap server)

docsDevNmAccessIpMask.15 (ipaddress) = 255.255.255.255

docsDevNmAccessCommunity.15 (octet string) = (any community string)

/* Default community string */

docsDevNmAccessControl.15 (integer) = roWithTraps(4) or rwWithTraps(5)

/* Allow traps to be sent */

docsDevNmAccessInterfaces.15 (octet string) = FF (hex) /*

Allow access from all interfaces of the cable modem */

docsDevNmAccessStatus.15 (integer) = createAndGo(4)

docsDevNmAccessTrapVersion.15 (integer) = DisableSNMPv2trap(1) or EnableSNMPv2trap(2)

You can configure multiple NmAccess entries for trap transmission if, forexample, you want to send traps to several different trap servers.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 60: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

44 Chapter 4

Rules for thedocsDevNm-AccessTable

Below is a brief overview of each of the MIB objects that comprise a rowentry in thedocsDevNmAccessTable .

docsDevNmAccessIp and docsDevNmAccessIpMask

If the docsDevNmAccessTable is used for SNMP access filtering, the fol-lowing rules are applied in order to determine whether to permit SNMPaccess from a given source IP address (SrcIpAddr):

1 If (docsDevNmAccessIp == 255.255.255.255), the CM permitsSNMP access from any SrcIpAddr.

2 If (docsDevNmAccessIpMask == 0.0.0.0), the CM permits SNMPaccess from any SrcIpAddr.

3 If ((docsDevNmAccessIp AND docsDevNmAccessIpMask ) ==(SrcIpAddr AND docsDevNmAccessIpMask )), the CM permitsSNMP access from SrcIpAddr.

4 If neither #1 nor #2 is applied, the CM denies SNMP access from Src-IpAddr.

The CM’s default value of thedocsDevNmAccessIpMask is set to0.0.0.0.

The following table contains sample MIB values and the access granted.

docsDevNmAccessIp AccessdocsDevNmAccessIpMask

255.255.255.255 Any IP address mask Any NMS

Any IP address 0.0.0.0 Any NMS

255.255.255.255 SingleNMSAny IP address except

255.255.255.255

0.0.0.0 255.255.255.255 No NMS

IP address of IP subnet Netmask of the subnet A subnet group of NMS

docsDevNmAccessCommunity

Default value: ‘‘public’’

• If this object is set to a zero-length string, then any community stringmatches.

• The value of this object does not appear in MIB walks of thedocsDev-NmAccessTable .

Note: When read, this object returns a zero-length string, no matter whatvalue it contains.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 61: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 45

docsDevNmAccessControl

Value list:

• none (1)—destroys this table row entry

• read (2)—default

• readWrite (3)

• roWithTraps (4)

• rwWithTraps (5)

• trapsOnly (6)

Default value:read (2).

• Setting the value of this object tonone (1) causes the table row entry tobe destroyed.

• An SNMP Walk on thedocsDevNmAccessTable requires Read-Writeaccess to succeed. Therefore, if this value is set toread (2) or roWith-Traps (4), then the docsDevNmAccessTable requires Read-Writeaccess to succeed. Therefore, if this value is set toread (2) or roWith-Traps (4), then thedocsDevNmAccessTable is not accessible using thecommunity string that is associated with thisdocsDevNmAccessCon-trol entry.

• In order for traps to be enabled for the associated row entry, this objectmust have a value of roWithTraps (4), rwWithTraps (5), or trap-sOnly (6).

docsDevNmAccessInterfaces

This object specifies the set of interfaces from which requests from this NMSare accepted. Each octet within the value of this MIB object specifies a set ofeight interfaces, with the first octet specifying interfaces 1 through 8, the sec-ond octet specifying interfaces 9 through 16, etc.Within each octet, the mostsignificant bit represents the lowest numbered interface, and the least signifi-cant bit represents the highest numbered interface. Thus,each interface isrepresented by a single bit within the value of this object.If that bit has avalue of1, then that interface is included in the set.

Default value:0xFF

Note that entries in this table apply only to link-layer interfaces (e.g., Ether-net and CATV MAC). Upstreamand downstream channel interfaces mustnot be specified.

In the CM, the interfaces are numbered as follows:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 62: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

46 Chapter 4

Interface Type

1 Primary CPE Interface (Ethernet Interface)2 RF MAC Interface3 RF Downstream4 RF Upstream5 Secondary CPE Interface (USB Interface)5+n OtherInterfaces

16 PacketCable Embedded Interface

The bitmask for thedocsDevNmAccessInterfaces MIB object is as fol-lows:

27 26 25 24 23 22 21 20

Ethernet RF RF U/S RF D/S USB - - -

Following are examples of typical settings for thedocsDevNmAccess-Interfaces MIB object:

Value (hex) Description

Most common settingsFF Apply to all interfaces (Default value)C0 EthernetInterface + RF Interface80 EthernetInterface only40 RFInterface only

Other settings08 USBInterface only48 RF+ USB88 Ethernet+ USBC8 Ethernet+ RF + USB

docsDevNmAccessStatus

If this object is configured in the CM’s configuration file, then it should havea value ofcreateAndGo (4) or createAndWait (5). If set tocreateAndGo (4)in the configuration file, the value of this object automatically changes toactive (1) upon successful creation of the row entry and the row entrybecomes active. If set to createAndWait (5) in the configuration file, thevalue of this object automatically changes tonotInSer vice (2) and the associ-ated row entry becomes inactive.

docsDevNmAccessTrapVersion

This object specifies the trap version.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 63: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 47

• version1 (1)—send SNMPv1 traps (default)

• version2 (2)—send SNMPv2 traps

Note that the values for this object may appear asDisableSNMPv2trap (1)for version1 (1) andEnableSNMPv2trap (2) for version2 (2).

Configuring the CM for Coexistence Mode

When the CM is in coexistence mode, SNMP access and SNMP trap destina-tions are processed within the context of the SNMPv3 protocol architectureas defined in the SNMPv3 MIBs (RFC 2571 through RFC2576). Any one ofthe three coexistence modes (v1/v2c only, v1/v2/v3, or v3 only) can be con-figured by using various combinations of the following elements in the con-figuration file:

• TLV-11 MIB settings to thesnmpCommunityMIB , vacmSecurity-ToGroupTable , and vacmAccessTable

• SNMP Notification Receiver element (TLV-38)

• SNMP Kickstart User element (TLV-34)

The particular coexistence mode is determined as described in ‘‘SNMPAccess Mode Overview’’ on page 39.

ConfiguringSNMPv1/v2c onlycoexistence

Configuring the modem in SNMPv1/v2c only coexistence mode allows youto use a simple community string within the context of SNMPv3 USM secu-rity to access the CM’s MIBs. This mode of coexistence makes use of thesnmpCommunityTable , which is defined in thesnmpCommunityMIB . ThesnmpCommunityTable contains objects that allow you to map a communitystring into the following SNMPv3 message parameters:

• securityName

• contextEngineID

• contextName

The snmpCommunityTable , in combination with the vacmSecurity-ToGroupTable and thevacmAccessTable , permits coexistence.

The coexistence settings can be configured in numerous different ways. Fordetailed information of their operation, see the SNMPv3 MIB RFCs(RFC 2571 through RFC 2576).

Following is a basic coexistence example that configures two SNMPv1/v2ccommunity strings, which maps to the DOCSIS-defined SNMPv3 securityuser: docsisManager. ThesnmpCommunityTable is configured with the fol-lowing community strings: 1) a read/write community string, which providesfull read-write access to the entire MIB tree; and 2) a read-only community

Management Guide Release 6.1 Standard 1.3 June 2009

Page 64: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

48 Chapter 4

string, which provides read-only access to the MIB tree.

snmpCommunityTab le , Indexed by s nmpCommunityIndex

Table Index rw r o

snmpCommunityIndex (I) rw ro

snmpCommunityName readwrite readonly

snmpCommunitySecurityName rwAccess roAccess

snmpCommunityContextEngineID local snmpEngineID local snmpEngineID

snmpCommunityContextName (zero-length) (zero-length)

snmpCommunityTransportTag (zero-length) (zero-length)

snmpCommunityStorageType volatile(2) volatile(2)

snmpCommunityStatus createAndGo(4) createAndGo(4)

(I) indicates this object is an index value.

Italics indicates that this value is the default value of the MIB object.

How it Works

When an SNMPv1 (or SNMPv2c) Request (GET or SET) is received by themodem, each row within the snmpCommunityTable is checked until amatching row is found or all the rows have been searched. If no matchingrows are found, then the request results in an authorization failure and theSNMP Request is rejected.

In order for a row to match, thesnmpCommunityName must first match thecommunity name contained within the SNMP Request message.

If the community name matches a row in snmpCommunityTable , then thesnmpCommunitySecurityName for that row is next compared against thevacmSecurityName entries in thevacmSecurityToGroupTable .

vacmSecurityToGroupTab le , Indexed by vacmSecurityModel, v acmSe-curityName

Table Index 1.roAccess 1.rwAccess 2.roAccess 2.rwAccess

vacmSecurityModel (I) 1 (SNMPv1) 1 (SNMPv1) 2 (SNMPv2) 2 (SNMPv2)

vacmSecurityName (I) roAccess rwAccess roAccess rwAccess

vacmGroupName roAccess1 rwAccess1 roAccess2 rwAccess2

vacmSecurityToGroupStorageType volatile(2) volatile(2) volatile(2) volatile(2)

vacmSecurityToGroupStatus createAndGo(4) createAndGo(4) createAndGo(4) createAndGo(4)

(I) indicates this object is an index value.

Italics indicates that this value is the default value of the MIB object.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 65: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 49

If an entry is found with avacmSecurityName that matches thesnmpCom-munitySecurityName , then the corresponding group name (vacmGroup-Name) for that row entry is used in thevacmAccessTable to determine ifMIB access is allowed for that community string.

In order for SNMP GET-Requests to be allowed, thevacmAccessRead-ViewName must be valid.

In order for SNMP SET-Requests to be allowed, thevacmAccessWrite-ViewName must be valid.

In order for SNMP Trap messages to be allowed, thevacmAccessNoti-fyViewName must be valid.

The ‘‘docsisManagerView’’ entry is a pre-configured default DOCSIS-defined MIB access view that allows full read, write, and notify access to themodem’s entire MIB tree.

vacmAccessTab le , Indexed by v acmGr oupName , vacmAccessCon-textPrefix, vacmAccessSecurityModel, vacmAccessSecurityLevel

Table Index roAccess.[].1.1 roAccess.[].2.1 rwAccess.[].1.1 rwAccess.[].2.1

vacmAccessContextPrefix (I) ‘‘ ’’ ‘‘’’ ‘‘’’ ‘‘ ’’

vacmAccessSecurityModel (I) 1 (SNMPv1) 1 (SNMPv1) 2 (SNMPv2) 2 (SNMPv2)

vacmAccessSecurityLevel (I) 1 (noAuthnoPriv) 1 (noAuthnoPriv) 1 (noAuthnoPriv) 1 (noAuthnoPriv)

vacmAccessContextMatch exact(1) exact(1) exact(1) exact(1)

vacmAccessReadViewName docsisManagerView docsisManagerView docsisManagerView docsisManagerView

vacmAccessWriteViewName ‘‘’ ’ ‘ ‘’ ’ docsisManagerView docsisManagerView

vacmAccessNotifyViewName docsisManagerView docsisManagerView docsisManagerView docsisManagerView

vacmAccessStorageType volatile(2) volatile(2) volatile(2) volatile(2)

vacmAccessStatus createAndGo(4) createAndGo(4) createAndGo(4) createAndGo(4)

(I) indicates this object is an index value.

‘‘ ’’ i ndicates a (zero-length) string

Italics indicates that this value is the Default value of the MIB object.

ConfiguringSNMPv1/v2c/v3coexistence

The configuration of SNMPv1/v2c/v3 coexistence is the same as v1/v2c onlycoexistence above, but with the addition of a TLV-34 (SNMP Kickstart User)element in the configuration file.

The SNMP Kickstart User element is added to the configuration file in orderto ‘‘kickstart’’ SNMPv3 initialization and Diffie-Helman Key Change calcu-lations. Adescription of the TLV-34 element follows.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 66: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

50 Chapter 4

SnmpV3 Kic kstar t Value

The following TLV and its sub-elements are placed in the modem’s configu-ration file to kickstart SNMPv3 access to the modem.

Type Length Value34 n Composite

Up to 5 of these objects may be included in the configuration file.Eachresults in an additional row being added to theusmDHKic kstar tT able andtheusmUserTable and results in an agent public number being generated forthose rows.

SnmpV3 Kic kstar t Security Name

Type Length Value34.1 2to 16 UTF8 Encoded security name

Normally, this is specified as one of the DOCSIS built-in USM users, e.g.,‘‘ docsisManager,’’ ‘ ‘docsisOperator,’’ ‘ ‘docsisMonitor,’’ ‘ ‘docsisUser.’’ Thisobject is reported in theusmDHKic kStar tT able asusmDHKic kStar tSecuri-tyName and in theusmUserTable asusmUserName andusmUserSecuri-tyName .

SnmpV3 Kic kstar t Manager Public Number

Type Length Value34.2 n Manager’s Diffie-Helman public number

expressed as an octet string.

This number is the Diffie-Helman public number derived from a privately (bythe NMS or operator) generated random number and transformed accordingto RFC2786. Thisis reported in theusmDHKic kStar tT able as usmKick-startMgrPublic. Whencombined with the object reported in the same row asusmKickstartMyPublic, it can be used to derive the keys in the related row intheusmUserTable .

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 67: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 51

Example: Adding a TL V-34 element in PacketACE

Management Guide Release 6.1 Standard 1.3 June 2009

Page 68: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

52 Chapter 4

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 69: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 53

ConfiguringSNMPv3-onl y co-existence

To configure SNMPv3-only coexistence, enter the TLV-34 (SNMP KickstartUser) element in the configuration file and NO Coexistence MIB settings inthe configuration file.

Configuring TrapTransmissionwithin Coexis-tence Mode

There are two ways to configure traps for coexistence mode:

• Through the configuration file

• Through SNMP

The simplest way to configure traps is to add the SNMPv3 NotificationReceiver element to the CM configuration file.Below is a description of thiselement:

SNMPv3 Notification Receiver config file element (TL V-38)

The SNMPv3 Notification Receiver (TLV-38) is used to easily configureSNMPv3 tables for notification (i.e. trap) transmission.The TLV specifies aNetwork Management Station (NMS) that receives notifications (traps) fromthe modem when the modem is in Coexistence mode.

Up to 10 TLV-38 elements may be included in the configuration file.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 70: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

54 Chapter 4

Note: The CM processes this TLV only if the CM is in Coexistence mode.

Type Length Value38 n composite

Note: If using the TLV-38 element in the configuration file, the only two sub-TLVs that MUST be present are 38.1 (IP Address) and 38.3 (Trap Type). Allof the other sub-TLVs are configured to their default values if they are notpresent.

SNMPv3 Notification Receiver IP Address

This sub-TLV specifies the IP address of the notification receiver.

Type Length Value38.1 4 ip1,ip2,ip3,ip4

SNMPv3 Notification Receiver UDP P or t Number

This sub-TLV specifies the UDP port number of the notification receiver. Ifthis sub-TLV is not present, the default value is 162.

Type Length Value38.2 2 UDP port number

SNMPv3 Notification Receiver Trap Type

Type Length Value38.3 2 trap value

This sub-TLV specifies the type of trap to send. The trap type may take thefollowing values:

1 SNMP v1 trap in an SNMP v1 packet

2 SNMP v2c trap in an SNMP v2c packet

3 SNMP inform in an SNMP v2c packet

4 SNMP v2c trap in an SNMP v3 packet

5 SNMP inform in an SNMP v3 packet

SNMPv3 Notification Receiver Timeout

This sub-TLV specifies the timeout value to use when sending an Informmessage to the notification receiver.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 71: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 55

Type Length Value38.4 2 time in milliseconds

SNMPv3 Notification Receiver Retries

This sub-TLV specifies the number of times to retry sending an Inform mes-sage if an acknowledgment is not received.

Type Length Value38.5 2 number of retries

SNMPv3 Notification Receiver Filtering Parameters

This sub-TLV specifies the Object Identifier of the snmpTrapOID value thatidentifies the notifications to be sent to the notification receiver. SNMP V3allows the specification of which Trap OIDs are to be sent to a trap receiver.This object specifies the OID of the root of a trap filter sub-tree.All Trapswith a Trap OID contained in this trap filter sub-tree are sent to the trapreceiver.

Type Length Value38.6 n filter OID

SNMPv3 Notification Receiver Security Name

This sub-TLV specifies the V3 Security Name to use when sending a V3Notification. Thissub-TLV is only used if the Trap Type is set to4 or 5.This name must be a name specified in a configuration file TLV Type 34 aspart of the DH Kickstart procedure. The notifications are sent using theAuthentication and Privacy Keys calculated by the modem during the DHKickstart procedure. This sub-TLV is not required for Trap Types 1, 2, or 3.If it is not supplied for a Trap type of 4 or 5, the V3 Notification is sent in thenoAuthNoPriv security level using the security name ‘‘@config’’.

Type Length Value38.7 n security name

Based on the contents of the TLV, the CM creates entries in the followingtables in order to setup the desired trap transmission: snmpNotifyTable,snmpCommunityTable, usmUserTable, vacmSecurityToGroupTable, vacm-AccessTable, and vacmViewTreeFamilyTable.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 72: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

56 Chapter 4

Example Configuration

Following is an example configuration of three TLV-38 Notification ele-ments.

Note 1: The TrapOID for DOCSIS events is: 1.3.6.1.2.1.69.2.1.2.0 (= docs-DevCmTraps)

Note 2: The TrapOID for PacketCable/ARRIS-proprietary MTA events is:1.3.6.1.4.1.4491.2.2.3.6.0.2 ( = pktcDevEvTrap)

// Send DOCSIS events to IP Addr: 192.168.78.99 as SNMPv2 traps

IP Address (38.1) = 192.168.78.99

Trap Type (TLV 38.2) = 2

Filtering Parameters (TLV 38.6) = 1.3.6.1.2.1.69.2.1.2.0

// Send PacketCable and ARRIS-proprietary MTA events to IP Addr: 192.168.78.100

//as SNMPv1 traps

IP Address (TLV 38.1) = 192.168.78.100

Trap Type (TLV 38.2) = 1

Filtering Parameters (TLV 38.6) = 1.3.6.1.4.1.4491.2.2.3.6.0.2

// Send PacketCable and ARRIS-proprietary MTA events to IP Addr: 192.168.78.150

//as SNMPv2 traps

IP Address (TLV 38.1) = 192.168.78.150

Trap Type (TLV 38.2) = 2

Filtering Parameters (TLV 38.6) = 1.3.6.1.4.1.4491.2.2.3.6.0.2

Example: Adding a TL V-38 element in PacketACE

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 73: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 57

Management Guide Release 6.1 Standard 1.3 June 2009

Page 74: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

58 Chapter 4

Configuring a Cloned USM User

SNMP USM User cloning provides the ability to create new USM Usersbased on an existing USM User row in theusmUserTable . The cloned usermay be mapped to any of the pre-existing SNMP Views.

USM Users for CM SNMP Views may be cloned using the CM configurationfile or SNMP SET-BULK operations on the CM IP Address. USM Users forMTA SNMP Views may be cloned using only SNMP SET_BULK opera-tions.

To clone a USM user in the eMTA, you must create row entries in the follow-ing tables:

• usmUserTable —one row entry to create the cloned USM User. Thenew USM User is cloned from an existing row in the usmUserTable .The cloned USM User maps to thevacmSecurityToGroupTable .

• vacmSecurityToGroupTable —one row entry containing VACM groupname information.The entry supports SNMPv3 access for the clonedUSM User.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 75: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 59

• vacmAccessTable —one row entry to map the VACM group name to aparticular Read, Write, and Notify view.

The following example starts with a basic DOCSIS 1.1 CM configuration filecontaining enough information to allow a cable modem to range and register,and then adds the cloning MIB elements to it.If you have a CM configura-tion file that you are already using, you can start with that file and add thecloning elements to it.

usmUserTableParameters

The following table shows the example row to add to theusmUserTable .This table has an index consisting of two objects:

• usmUserEngineID —A unique identifier for the eMTA’ s SNMP engine.The eMTA uses a single SNMP engine for the CM and MTA so theusmUserEngineID is the same for both the CM and the MTA.

• usmUserName —A text string representing the new cloned USM user.The value of theusmUserName MIB object is used for the value of theusmUserSecurityName MIB object for this row in theusmUserTable .TheusmUserSecurityName maps to thevacmSecurityToGroupTableand so in effect theusmUserName maps to thevacmSecurity-ToGroupTable .

Management Guide Release 6.1 Standard 1.3 June 2009

Page 76: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

60 Chapter 4

Object Name Index1 usmUserEngineID Index2 usmUserName Value

usmUserSecurityName 00.00.10.13.03.00.00.CA.3A.C1.F9.01cmNoAuthNoPrivUser Read-Only* See Note 1 below

usmUserCloneFrom 00.00.10.13.03.00.00.CA.3A.C1.F9.01cmNoAuthNoPrivUser 1.3.6.1.6.3.15.1.2.2.1.3.

12.0.0.16.19.3.0.0.202.58.

193.249.1.13.100.111.99.115.

105.115.77.97.110.97.103.

101.114

See Note 2 below

usmUserAuthProtocol 00.00.10.13.03.00.00.CA.3A.C1.F9.01cmNoAuthNoPrivUser 1.3.6.1.6.3.10.1.1.1

(usmNoAuthProtocol)

usmUserAuthKeyChange 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser (zero-length)

usmUserOwnAuthKeyChange 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser (zero-length)

usmUserPrivProtocol 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser 1.3.6.1.6.3.10.1.2.1

(usmNoPrivProtocol)

usmUserPrivKeyChange 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser (zero-length)

usmUserOwnPrivKeyChange 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser (zero-length)

usmUserPublic 00.00.10.13.03.00.00.CA.3A.C1.F9.01cmNoAuthNoPrivUser (zero-length)

usmUserStorageType 00.00.10.13.03.00.00.CA.3A.C1.F9.01 cmNoAuthNoPrivUser Volatile(2)

usmUserStatus 00.00.10.13.03.00.00.CA.3A.C1.F9.01cmNoAuthNoPrivUser createAndGo(4)

Note 1: Do not include this MIB object in your configuration file.TheusmUserSecurityName MIB object is read-only. The value ofusmUserSe-curityName is populated with the Index2 value (usmUserName ) for eachrespective row of theusmUserTable .

Note 2: The value of the MIB object usmUserCloneFrom(1.3.6.1.6.3.15.1.2.2.1.3.12.0.0.16.19.3.0.0.202.58.193.249.1.13.100.111.99.115.105.115.77.97.110.97.103.101.114) is a RowPointer to theusmUserSe-curityName of the user we want to clone from.It is made up of three partsas described below:

1 Part one (1.3.6.1.6.3.15.1.2.2.1.3) is the OID of theusmUserSecuri-tyName MIB object.

2 Part two (12.0.0.16.19.3.0.0.202.58.193.249.1) is theusmUser-EngineID (Index1 of theusmUserSecurityName MIB object for therow to clone from). The first octet of this string (12) represents thelength of the string.

3 Part three (13.100.111.99.115.105.115.77.97.110.97.103) is theusmUserName (Index2 of the usmUserSecurityName MIB object forthe row to clone from). The first octet of this string (13) representsthe length of the string.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 77: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 61

vacmSecurity-ToGroupTableParameters

The following table shows the example row to add to theusmUserTable .This table has an index consisting of two objects:

• vacmSecurityModel —corresponds to the SNMP version in use; in thisexample it takes the value 3 to allow support for SNMPv3 requestswithout Authentication and Privacy.

• vacmSecurityName —maps to the usmUserSecurityName MIBobject in theusmUserTable (cmNoAuthNoPrivUser in this example).

Index1 Index2vacmSecurityModel vacmSecurityName

Object Name Value

vacmGroupName 3(SNMPv3) cmNoAuthNoPrivUser V3_Access

vacmSecurityToGroupStorageType 3(SNMPv3) cmNoAuthNoPrivUser Volatile(2)

vacmSecurityToGroupStatus 3(SNMPv3) cmNoAuthNoPrivUser createAndGo(4)

vacmAccessTableParameters

The following table shows the example row to add to theusmUserTable .This table has an index consisting of four objects:

• vacmGroupName —maps to thevacmGroupName MIB object in thevacmSecurityToGroupTable (V3_Access in our example).

• vacmAccessContextPrefix —an octet string; in this example we use anempty (zero length) string. This is shown as ‘‘’’ in the table below.

• vacmAccessSecurityModel —corresponds to the SNMP version inuse; in this example it takes the value 3 to allow support for SNMPv3requests without Authentication and Privacy.

• vacmAccessSecurityLevel —for SNMP coexistence, use a value of1(noAuthnoPriv). This means that the eMTA has no configuredSNMPv3 USM security users/keys.

Object Name (ROW1) ValueIndex1 vacm-

GroupName

Index2 vacmAccess

ContextPrefix

Index3 vacmAccess

SecurityModel

Index4 vacmAccess

SecurityLevel

vacmAccessContextMatch V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) (zero-length)

vacmAccessReadViewName V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) docsisManagerView

vacmAccessWriteViewName V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) docsisManagerView

vacmAccessNotifyViewName V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) docsisManagerView

vacmAccessStorageType V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) Volatile(2)

vacmAccessStatus V3_Access ‘‘ ’’ 3 (SNMPv3) 1(noAuthnoPriv) createAndGo(4)

Example Configu-ration File

The following is an example configuration file showing a cloned user.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 78: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

62 Chapter 4

Example Config File

NetworkAccess = 1

MaxCpeAllowed = 16

MaxClassifiers = 20

PrivacyEnable = 0

BaselinePrivacy =

AuthorizeWaitTimeout = 10

ReauthorizeWaitTimeout = 10

KekGraceTime = 600

OpWaitTimeout = 10

RekeyWaitTimeout = 10

TekGraceTime = 600

AuthorizeRejectWaitTimeout = 60

SAMapWaitTimeout = 1

SAMapMaxRetries = 4

UpstreamServiceFlow =

SfReference = 1

SfClassName = "USPrimaryBE"

SfQosSetType = 7

SfTrafficPriority = 1

SfMaxTrafficRate = 0

SfMaxTrafficBurst = 1522

SfMinReservedRate = 0

SfMinReservedRatePktsize = 64

SfActiveQosTimeout = 0

SfAdmittedQosTimeout = 200

SfMaxConcatBurst = 0

SfSchedulingType = 2

SfRqTxPolicy = 128

SfIpTosOverwrite = 64512

UpstreamServiceFlow =

SfReference = 2

SfClassName = "USMTAMGCP"

SfQosSetType = 7

SfTrafficPriority = 7

SfMaxTrafficRate = 0

SfMaxTrafficBurst = 1522

SfMinReservedRate = 0

SfMinReservedRatePktsize = 64

SfActiveQosTimeout = 0

SfAdmittedQosTimeout = 200

SfMaxConcatBurst = 3000

SfSchedulingType = 2

SfRqTxPolicy = 136

SfIpTosOverwrite = 64512

DownstreamServiceFlow =

SfReference = 101

SfClassName = "DSPrimaryBE"

SfQosSetType = 7

SfTrafficPriority = 1

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 79: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

SNMP Security 63

SfMaxTrafficRate = 100000000

SfMaxTrafficBurst = 1522

SfMinReservedRate = 0

SfMinReservedRatePktsize = 64

SfActiveQosTimeout = 0

SfAdmittedQosTimeout = 200

SfMaxDownstreamLatency = 20000

DownstreamServiceFlow =

SfReference = 102

SfClassName = "DSMTAMGCP"

SfQosSetType = 7

SfTrafficPriority = 7

SfMaxTrafficRate = 10000000

SfMaxTrafficBurst = 1522

SfMinReservedRate = 12000

SfMinReservedRatePktsize = 64

SfActiveQosTimeout = 0

SfAdmittedQosTimeout = 200

SfMaxDownstreamLatency = 5000

UpstreamPacketClassification =

PcServiceFlowReference = 2

PcReference = 2

PcRulePriority = 1

PcActivationState = 1

PcIpClassification =

PcIpProtocol = 17

PcIpSourceAddress = 0.0.0.0

PcIpSourceMask = 0.0.0.0

PcIpDestAddress = 0.0.0.0

PcIpDestMask = 0.0.0.0

PcIpSourcePortStart = 2727

PcIpSourcePortEnd = 2727

DownstreamPacketClassification =

PcServiceFlowReference = 102

PcReference = 102

PcRulePriority = 1

PcActivationState = 1

PcIpClassification =

PcIpProtocol = 17

PcIpSourceAddress = 0.0.0.0

PcIpSourceMask = 0.0.0.0

PcIpDestAddress = 0.0.0.0

PcIpDestMask = 0.0.0.0

PcIpDestPortStart = 2427

PcIpDestPortEnd = 2427

SnmpMib = usmUserCloneFrom.00.00.10.13.03.00.00.CA.3A.C1.F9.01

cmNoAuthNoPrivUser 1.3.6.1.6.3.15.1.2.2.1.3.12.0.0.16.19.3.0.0.202.

58.193.249.1.13.100.111.99.115.105.115.77.97.110.97.103.101.114

SnmpMib = usmUserPrivProtocol.00.00.10.13.03.00.00.CA.3A.C1.F9.01

cmNoAuthNoPrivUser 1.3.6.1.6.3.10.1.2.1

Management Guide Release 6.1 Standard 1.3 June 2009

Page 80: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

64 Chapter 4

SnmpMib = usmUserAuthProtocol.00.00.10.13.03.00.00.CA.3A.C1.F9.01

cmNoAuthNoPrivUser 1.3.6.1.6.3.10.1.1.1

SnmpMib = usmUserStorageType.00.00.10.13.03.00.00.CA.3A.C1.F9.01

cmNoAuthNoPrivUser volatile

SnmpMib = usmUserStatus.00.00.10.13.03.00.00.CA.3A.C1.F9.01

cmNoAuthNoPrivUser createAndGo

SnmpMib = vacmGroupName.3 cmNoAuthNoPrivUser "V3_Access"

SnmpMib = vacmSecurityToGroupStorageType.3 cmNoAuthNoPrivUser volatile

SnmpMib = vacmSecurityToGroupStatus.3 cmNoAuthNoPrivUser createAndGo

SnmpMib = vacmAccessReadViewName.V3_Access 3 1 "docsisManagerView"

SnmpMib = vacmAccessWriteViewName.V3_Access 3 1 "docsisManagerView"

SnmpMib = vacmAccessNotifyViewName.V3_Access 3 1 "docsisManagerView"

SnmpMib = vacmAccessStorageType.V3_Access 3 1 volatile

SnmpMib = vacmAccessStatus.V3_Access 3 1 createAndGo

SNMPV3Kickstart =

SNMPV3SecurityName = "docsisManager"

SNMPV3PublicNumber = hexstr: C1.FC.52.36.97.06.C0.22.99.61.D5.

CA.C5.4F.C6.68.51.71.A8.DC.69.AB.EB.D6.21.AC.AC.1D.FC.A6.0A.3A.8E.

77.B5.15.AB.AC.60.7C.5F.EB.AF.5F.86.B8.3F.2B.A1.DB.3D.ED.51.E2.EB.

5D.E0.6A.EB.2D.AE.E3.A4.DA.AC.DA.30.42.DC.A2.3C.5B.FE.65.83.B8.B8.

9E.48.02.FB.70.A5.E9.97.0C.95.9F.96.44.B4.BA.B4.2C.71.97.D1.1A.96.

99.C9.4F.9C.53.3F.00.24.3E.1A.12.AB.23.CF.DB.05.6C.97.62.4B

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 81: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

5 Configuring SNMPCM Coexistence

Touchstone firmware provides several SNMPv3 security-related features.SNMP Coexistence is a feature that allows SNMPv1 and SNMPv2c networkmanagement systems to function within the context of SNMPv3 security andview-based MIB access. The NMS can use an SNMPv1 or SNMPv2 com-munity string to access the eMTA’ s MIBs or to receive traps.

The procedures in this chapter provide details on adding the necessary MIBsand TLVs to a cable modem configuration file. See theTouchstone Tele-phony Provisioning Guidefor a listing of the completed configuration file.

For notes and procedures for provisioning ARRIS-specific MTA Coexis-tence, see Chapter 5.

Over vie w

The procedures in this section use the ARRIS PacketACE Configuration Edi-tor to create the configuration file, covering only the details needed to add thedesired functionality. See thePack etACE Configuration Tools User’s Guidefor more information about using PacketACE.

Configuration FileNotes

Keep the following notes in mind when creating or editing configurationfiles.

• A MIB object whose type is ‘‘StorageType’’ must always have a valueof volatile .

• A MIB object whose type is ‘‘RowStatus’’ should have a value ofcre-ateAndGo . The eMTA automatically changes its value toactive aftersuccessfully adding the row.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 82: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

66 Chapter 5

SNMP AccessMode

The following examples configure SNMP access to the eMTA forSNMPv1v2c coexistence mode.This allows an NMS (i.e. a MIB Browser)to access the eMTA’ s MIBs with a simple community string using eitherSNMPv1 or SNMPv2.

The SNMP requests GET, GET-NEXT, and SET are all supported.Theexamples use the community namemy_pass word .

SNMP Trap Trans-mission

SNMP trap transmission uses the DOCSIS TLV-38 (SNMPv3 NotificationReceiver) configuration file element.

The example configures two trap destinations, each with a different IPaddress. Onedestination supports SNMPv1 traps and the other destinationsupports SNMPv2 traps. The parameters for each trap destination are:

• Trap destination #1:

– IP Address: 10.1.50.100

– Trap Type: SNMPv1

• Trap destination #2:

– IP Address: 10.1.50.80

– Trap Type: SNMPv2

Note: Change the trap IP address to the IP address of your specific trap serverin the configuration file.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 83: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 67

Configuring SNMP CoexistenceTo configure the eMTA for coexistence mode, you must create row entries inthe following MIB tables:

• snmpCommunityTable —one row entry, to map the community stringto an SNMPv3 security name.

• vacmSecurityToGroupTable —two row entries, containing group nameinformation. Oneentry supports SNMPv1 access and the other entrysupports SNMPv2 access.

• vacmAccessTable —two row entries, which map the community name,security name, and group name information to an SNMPv3 securityname. TheDOCSIS-standard default security name for cable modemsis docsisMana ger. One entry supports SNMPv1 access and the otherentry supports SNMPv2 access.

This example starts with a basic DOCSIS 1.1 CM configuration file, contain-ing enough information to allow a cable modem to range and register, andthen add the coexistence MIB elements to it. If you have a CM configurationfile that you are already using, start with that file and add the coexistence ele-ments to it.

snmpCommunity-Table Parameters

The following table shows the example row to add to the snmpCommunity-Table. Theindex for this table is an octet string; the example uses the stringcomm1 as the index value. You can use a different string if you desire.Itali-cized values in the table are default values that are created automatically.

Object Name Value

snmpComm unityName . comm1 my_passwordsnmpComm unitySecurityName . comm1 rwAccesssnmpCommunityContextEngineID. comm1 local snmpEngineIDsnmpCommunityConte xtName . comm1 (zero-length)snmpCommunityT ranspor tT ag.comm1 (zero-length)snmpCommunityStora geType .comm1 volatile (2)snmpCommunityStatus. comm1 createAndGo(4)

Note: Avoid adding table index objects to the configuration file; the firmwarefills in the index object using the index value supplied with the object name(.comm1 in this example).

Object order is not important.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 84: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

68 Chapter 5

vacmSecurity-ToGroupTable Pa-rameters

The following table shows the example row to add to thevacmSecurity-ToGroupTable . This table has an index consisting of two objects:

• vacmSecurityModel —corresponds to the SNMP version in use; in thisexample; it takes the values1 and2 to allow support for both SNMPv1and SNMPv2 requests.

• vacmSecurityName —corresponds to thesnmpCommunitySecurity-Name MIB object in thesnmpCommunityTable (rwAccess in thisexample).

Object Name Value (row 1) Value (row 2)

vacmSecurityModel (row index 1) 1 (SNMPv1) 2(SNMPv2)vacmSecurityName (row index 2) rwAccess rwAccessvacmGroupName rwAccess1 rwAccess2vacmSecurityToGroupStora geType volatile (2) volatile (2)vacmSecurityToGroupStatus createAndGo(4) createAndGo(4)

vacmAccessTableParameters

The following table shows the example row to add to thevacmAccessTable .This table has an index consisting of four objects:

• vacmGroupName —corresponds to the vacmGroupName object in thevacmSecurityToGroupTable (rwAccess in our example). CM andMTA group names should be unique.

• vacmAccessContentPrefix —an octet string; in this example we usean empty (zero length) string. This is shown as ‘‘’’ in the table below.

• vacmAccessSecurityModel —corresponds to the SNMP version inuse; in this example; it takes the values1 and 2 to allow support forboth SNMPv1 and SNMPv2 requests.

• vacmAccessSecurityLevel —for SNMP coexistence, use a value of1(noAuthnoPriv). This means that the eMTA has no configuredSNMPv3 USM security users/keys.

Object Name Value (row 1) Value (row 2)

GroupName (row index 1) rwAccess rwAccessContentPrefix (row index 2) ‘‘’ ’ ‘ ‘’’SecurityModel (row index 3) 1 (SNMPv1) 2(SNMPv2)SecurityLevel (row index 4) 1 (noAuthnoPriv) 1 (noAuthnoPriv)vacmAccessContextMatch exact(1) exact(1)vacmAccessReadViewName docsisManagerView docsisManagerViewvacmAccessWriteViewName docsisManagerView docsisManagerViewvacmAccessNotifyViewName docsisManagerView docsisManagerViewvacmAccesssStora geType volatile (2) volatile (2)vacmAccessStatus createAndGo(4) createAndGo(4)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 85: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 69

Action Perform the following tasks in the order shown.

Task Pag e

Adding the snmpCommunityTable 69Adding the vacmSecurityToGroupTable 72Adding the vacmAccessTable 75

Adding the snmp-CommunityTable Follow these steps to add coexistence MIB objects to a CM configuration file

using PacketACE.

1 Click the ‘‘A dd SNMP MIB’’ i con or selectEdit men u -> Add SNMPMIB.

The Available MIBs tree appears:

2 Locate thesnmpCommunityTable MIB. If you are not sure wherethe MIB is located in the tree, enter the name of the MIB in the upperfield along the right side of the PacketACE window and then clickFind MIB b y Name. The following figure shows the snmpCommun-ityTable MIB.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 86: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

70 Chapter 5

3 Double-click on one of the objects listed in the following table.

Object Name Value

snmpCommunityName my_passwordsnmpCommunitySecurityName rwAccesssnmpCommunityStora geType volatile (2)snmpCommunityStatus createAndGo(4)

The Add SNMP MIB window appears:

4 Enter the index name (comm1 ) in the Index,DisplayString field, andthe value from the table in step 3 in theValue field.

Some of the objects have a fixed set of values; this is indicated by thedrop-down menu button at the end of theValue field. Click the menubutton to display a list of allowed values, and choose the correct

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 87: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 71

value.

5 Repeat steps 3 and 4 until all values are filled in.

The configuration file should now look similar to the following:

Note: The order of your MIB entries may be different than what isshown above.

6 Proceed to ‘‘Adding the vacmSecurityToGroupTable.’’

Management Guide Release 6.1 Standard 1.3 June 2009

Page 88: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

72 Chapter 5

Adding the vacm-SecurityToGroup-Table

Follow these steps to add coexistence MIB objects to a CM configuration fileusing PacketACE.

1 Click the ‘‘A dd SNMP MIB’’ i con or selectEdit men u -> Add SNMPMIB.

The Available MIBs tree appears.

2 Locate thevacmSecurityToGroupTable MIB. If you are not surewhere the MIB is located in the tree, enter the name of the MIB in theupper field along the right side of the PacketACE window and thenclick Find MIB b y Name.

3 Double-click on one of the objects listed in the following table.

Object Name Value (row 1) Value (row 2)

vacmGroupName rwAccess rwAccess

vacmSecurityToGroupStora geType volatile (2) volatile (2)

vacmSecurityToGroupStatus createAndGo(4) createAndGo(4)

The Add SNMP MIB window appears:

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 89: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 73

4 Enter the first index (1 or 2) in the Index1,Integ er field, the secondindex (rwAccess ) in the Index2,DisplayString field, and the valuefrom the table in step 3 in theValue field.

Some of the objects have a fixed set of values; this is indicated by thedrop-down menu button at the end of theValue field. Click the menubutton to display a list of allowed values, and choose the correctvalue.

5 Repeat steps 3 and 4 until all values are filled in.

The configuration file should now be similar to the following:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 90: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

74 Chapter 5

Note: The order of your MIB entries may be different than what isshown above.

6 Proceed to ‘‘Adding the vacmAccessTable.’’

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 91: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 75

Adding the vacm-AccessTable

Follow these steps to add coexistence MIB objects to a CM configuration fileusing PacketACE.

1 Click the ‘‘A dd SNMP MIB’’ i con or selectEdit men u -> Add SNMPMIB.

The Available MIBs tree appears:

2 Locate thevacmAccessTable MIB. If you are not sure where theMIB is located in the tree, enter the name of the MIB in the upperfield along the right side of the PacketACE window and then clickFind MIB b y Name.

3 Double-click on one of the objects listed in the following table.

Object Name Value (row 1) Value (row 2)

vacmAccessContextMatch exact(1) exact(1)

vacmAccessReadViewName docsisManagerView docsisManagerView

vacmAccessWriteViewName docsisManagerView docsisManagerView

vacmAccessNotifyViewName docsisManagerView docsisManagerView

vacmAccesssStora geType volatile (2) volatile (2)

vacmAccessStatus createAndGo(4) createAndGo(4)

The Add SNMP MIB window appears:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 92: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

76 Chapter 5

4 Enter indexes as follows, and the value from the table in step3 in theValue field.

• Index1,DisplayString —rwAccess (or the value of the vacmGroup-Name object from the vacmSecurityToGroupTable)

• Index2,DisplayString —leave blank

• Index3,Integ er — 1 or 2, depending on the SNMP level row

• Index4,Integ er —1 (noAuthnoPriv)

Some of the objects have a fixed set of values; this is indicated by thedrop-down menu button at the end of theValue field. Click the menubutton to display a list of allowed values, and choose the correctvalue.

5 Repeat steps 3 and 4 until all values are filled in.

The configuration file should now be similar to the following:

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 93: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 77

Note: MIB entries may be in a different order than what is shownabove.

6 Proceed to ‘‘Configuring Trap Servers.’’

Management Guide Release 6.1 Standard 1.3 June 2009

Page 94: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

78 Chapter 5

Configuring Trap Servers

Use this procedure to configure trap destinations, using TLV-38 SNMPv3Notification Receiver elements. Thefollowing procedure assumes that Pack-etACE is running and the coexistence MIBs are in the configuration file, butyou can add the TLVs to the configuration file before adding the MIBs if youprefer.

Action 1 Click the ‘‘A dd TLV parameter’’ i con or selectEdit men u -> AddTLV.

The following window appears:

2 Select SNMPv3NotificationReceiver from the Type drop-downmenu, then click theAdd TLV button.

The SNMPv3NotificationReceiver element appears in the main Pack-etACE window.

3 In the main PacketACE window, select theSNMPv3NotificationRe-ceiver element, then click the ‘‘A dd TLV sub-parameter’’ i con orselectEdit men u -> Add Sub-TLV .

The following window appears:

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 95: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Configur ing SNMP CM Coexistence 79

4 SelectSNMPv3NrIpAddress from the Sub-Type drop-down menu.

5 Enter the IP address of the trap server (10.1.50.100 in this example) inthe Value box.

6 Click theAdd TLV button.

Pack etACE adds the Trap IP address sub-type to the SNMPv3Notifica-tionReceiver element.

7 Repeat steps 4 through 6, adding theSNMPv3NrTrapType sub-parameter and specifying a value of1: SNMP v1 trap in an SNMP v1packet .

8 Repeat steps 1 through 7 to create a secondSNMPv3Notification-Receiver element with an IP address of10.1.50.80 and a trap type of2: SNMP v2c trap in an SNMP v2c packet .

The configuration file should now resemble the following:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 96: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

80 Chapter 5

9 Sav ethe configuration file and exit PacketACE.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 97: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

6 ARRIS-specific MTASNMP Coexistence

The ARRIS MTA SNMP Proprietary Coexistence feature allows SNMPv1and SNMPv2c network management systems to function within the contextof SNMPv3 security and view-based MIB access. The NMS can useSNMPv1 or SNMPv2c community strings to access the eMTA’ s MIBs or toreceive Notifications (traps).

MTA Coexistence Overview

MTA SNMP Coexistence and Notifications (Traps) are configurable only inthe MTA configuration file. CM SNMP Coexistence and Notifications(Traps) are configurable only in the CM configuration file. The followingCoexistence and Notification TLV configurations are permitted:

• MTA Coexistence/Notifications only (CM Coexistence/Notifications isnot provisioned). MTA Coexistence/Notifications may be provisionedonly in the MTA configuration file.

• CM Coexistence/Notifications only (MTA Coexistence/Notifications isnot provisioned). CMCoexistence/Notifications may be provisionedonly in the CM configuration file.

• CM and MTA Coexistence/Notifications together. CM Coexis-tence/Notifications is provisioned in the CM configuration file andMTA Coexistence/Notifications is provisioned in the MTA configura-tion file.

Management Guide Release 6.1 Standard 1.3 June 2009

Page 98: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

82 Chapter 6

MIB Access for MT A Coexistence

When in MTA SNMP Coexistence mode, an eMTA’ s MTA MIB access isrestricted to PacketCable specified MIB views (ReadOnlyView, Full-AccessView, NotifyView). SNMPmanagement using the CM IP Address isnot permitted.

MIB Access for CM Coexistence

If CM SNMP Coexistence is also provisioned, then CM MIB access isrestricted to DOCSIS specified MIB views (docsisManagerView, docsisOper-atorWriteView, docsisMonitorView, docsisUserView). CM SNMP manage-ment using the MTA IP Address is not permitted.

Configuring MT A SNMP Coexistence

The following examples configure SNMP access to the eMTA for SNMPv1and SNMPv2c coexistence mode. This allows an NMS (e.g. a MIB browser)to access the eMTA’ s MIBs with a simple community string using eitherSNMPv1 or SNMPv2c.The SNMP requests GET, GET-NEXT, and SET areall supported.Then you need to create row entries in the following MIBtables:

• snmpCommunityTable —One row entry to map the community name(snmpCommunityName) to an SNMPv3 security name (snmpCommu-nitySecurityName).

• vacmSecurityToGroupTable —Two row entries which map theSNMPv3 security name (snmpCommunitySecurityName) from thesnmpCommunityTable to a group name (vacmGroupName). Oneentrysupports SNMPv1 access and the other entry supports SNMPv2caccess.

• vacmAccessTable —Two row entries which map the community name(snmpCommunityName), security name (snmpCommunitySecurity-Name), and group name (vacmGroupName) information to a VACMView name (vacmAccessReadViewName, vacmAccessWriteView-Name, vacmAccessNotifyViewName). Oneentry supports SNMPv1access and the other entry supports SNMPv2c access.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 99: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

ARRIS-specific MTA SNMP Coexistence 83

snmpCommunityTable Parameters

The following examples show the MTA Coexistence parameters which mustbe included in the configuration file to create the necessary rows in thesnmpCommunityTable .

The index for this table is an octet string; the examples use the stringcomm1as the index value. You can use a different string if you desire.

The order in which you add objects is not important.

Example: MTASNMP Coexis-tence

The following configuration shows MTA SNMP coexistence provisioned inthe MTA configuration file.

SnmpMib = snmpCommunityName.comm1 "mta_pwd"

SnmpMib = snmpCommunitySecurityName.comm1 "mtaAccess"

SnmpMib = snmpCommunityStorageType.comm1 volatile

SnmpMib = snmpCommunityStatus.comm1 active

vacmSecurityToGroupTable Parameters

The following examples show the MTA Coexistence parameters which mustbe included in the configuration file to create the necessary rows in thevacm-SecurityToGroupTable . This table has an index consisting of two objects:

• vacmSecurityModel —Corresponds to the SNMP version in use; in thisexample; it takes the values 1 and 2 to allow support for both SNMPv1and SNMPv2 requests.

• vacmSecurityName —Corresponds to the snmpCommunitySecurity-Name object in the snmpCommunityTable (mtaAccess in example 1,mtaAccess/cmAccess in example 2).

Example: MTASNMP Coexis-tence

The following configuration file fragment shows MTA SNMP Coexistenceprovisioned in the MTA configuration file.

SnmpMib = vacmGroupName.1 mtaAccess "mtaGroup"

SnmpMib = vacmSecurityToGroupStorageType.1 mtaAccess volatile

SnmpMib = vacmSecurityToGroupStatus.1 mtaAccess active

SnmpMib = vacmGroupName.2 mtaAccess "mtaGroup"

SnmpMib = vacmSecurityToGroupStorageType.2 mtaAccess volatile

SnmpMib = vacmSecurityToGroupStatus.2 mtaAccess active

Management Guide Release 6.1 Standard 1.3 June 2009

Page 100: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

84 Chapter 6

vacmAccessTable Parameters

The following examples show the MTA Coexistence parameters which mustbe included in the configuration file to create the necessary rows in thevacm-AccessTable . This table has an index consisting of four objects:

• vacmGroupName —Corresponds to the vacmGroupName object in thevacmSecurityToGroupTable (mtaGroup in our example).

• vacmAccessContentPrefix —An octet string; this example uses anempty (zero length) string. This is shown as ‘‘’’ in the table below.

• vacmAccessSecurityModel —Corresponds to the SNMP version inuse; in this example; it takes the values 1 and 2 to allow support forboth SNMPv1 and SNMPv2 requests.

• vacmAccessSecurityLevel —For SNMP coexistence use a value of 1(noAuthnoPriv). This means that the eMTA has no configuredSNMPv3 USM security users/keys.

Example: MTASNMP Coexis-tence

The following configuration fragment shows MTA SNMP Coexistence provi-sioned in the MTA configuration file.

SnmpMib = vacmAccessContextMatch.mtaGroup "" 1 1 exact

SnmpMib = vacmAccessReadViewName.mtaGroup "" 1 1 "ReadOnlyView"

SnmpMib = vacmAccessWriteViewName.mtaGroup "" 1 1 "FullAccessView"

SnmpMib = vacmAccessNotifyViewName.mtaGroup "" 1 1 "NotifyView"

SnmpMib = vacmAccessStorageType.mtaGroup "" 1 1 volatile

SnmpMib = vacmAccessStatus.mtaGroup "" 1 1 active

SnmpMib = vacmAccessContextMatch.mtaGroup "" 2 1 exact

SnmpMib = vacmAccessReadViewName.mtaGroup "" 2 1 "ReadOnlyView"

SnmpMib = vacmAccessWriteViewName.mtaGroup "" 2 1 "FullAccessView"

SnmpMib = vacmAccessNotifyViewName.mtaGroup "" 2 1 "NotifyView"

SnmpMib = vacmAccessStorageType.mtaGroup "" 2 1 volatile

SnmpMib = vacmAccessStatus.mtaGroup "" 2 1 active

SNMPv3 Notification Receiver Configuration File Element(TLV−38)

Use the SNMPv3 Notification Receiver TLV-38 to easily configure SNMPv3tables for notification (i.e. trap) transmission.TLV-38 specifies a NetworkManagement Station (NMS) that receive notifications (traps) from themodem when the modem is in MTA Coexistence mode.

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 101: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

ARRIS-specific MTA SNMP Coexistence 85

Note 1: The CM processes this TLV only if the CM is in Coexistence mode.

Note 2: If using the TLV-38 element in the configuration file, the only twosub-TLVs that MUST be present are 38.1 (IP Address) and 38.3 (Trap Type).All of the other sub-TLVs are configured to their default values if they are notpresent.

Example MTATLV-38 Configura-tion

Following is an example configuration of three MTA TLV-38 Notificationelements.

Note 1: The TrapOID for DOCSIS events is: 1.3.6.1.2.1.69.2.1.2.0 (docsDev-CmTraps)

Note 2: The TrapOID for PacketCable/ARRIS-proprietary MTA events is:1.3.6.1.4.1.4491.2.2.3.6.0.2 (pktcDevEvTrap)

Example #1: Send PacketCable events to IP Address 10.1.44.241 as SNMPv1traps.

SNMPv3NotificationReceiver =

SNMPv3NrIpAddress = 10.1.44.241

SNMPv3NrTrapType = 1

SNMPv3NrFilteringParameters = 1.3.6.1.4.1.4491.2.2.3.6.0.2

Example #2: Send PacketCable and ARRIS-proprietary MTA events to IPAddress 10.1.44.241 as SNMPv2c traps

SNMPv3NotificationReceiver =

SNMPv3NrIpAddress = 10.1.44.241

SNMPv3NrTrapType = 2

SNMPv3NrFilteringParameters = 1.3.6.1.4.1.4491.2.2.3.6.0.2

Example #3: Send PacketCable and ARRIS-proprietary MTA events to IPAddress 10.1.44.241 as SNMPv2 traps in an SNMPv3 packet.

SNMPv3NotificationReceiver =

SNMPv3NrIpAddress = 10.1.44.241

SNMPv3NrTrapType = 4

SNMPv3NrFilteringParameters = 1.3.6.1.4.1.4491.2.2.3.6.0.2

Management Guide Release 6.1 Standard 1.3 June 2009

Page 102: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

86 Chapter 6

Configuration File Examples

MTA Coexistence/Notifications Pro-visioned in theMTA ConfigurationFile

TelephonyConfigFileBeginEnd = 1SnmpMib = ppCfgMtaFeatureSwitch.0 hexstr: 08SnmpMib = pktcMtaDevEnabled.0 trueSnmpMib = pktcNcsEndPntConfigCallAgentId.9 "[email protected]"SnmpMib = pktcNcsEndPntConfigCallAgentId.10 "[email protected]"SnmpMib = pktcNcsEndPntConfigCallAgentUdpPort.9 2727SnmpMib = pktcNcsEndPntConfigCallAgentUdpPort.10 2727SnmpMib = pktcNcsEndPntConfigMWD.9 10SnmpMib = pktcNcsEndPntConfigMWD.10 10SnmpMib = pktcMtaDevRealmOrgName.DEV50 "CableLabs"SnmpMib = pktcMtaDevCmsKerbRealmName.DSHAHALPS.DEV50 "DEV50"SnmpMib = pktcMtaDevCmsIpsecCtrl.DSHAHALPS.DEV50 falseSnmpMib = snmpCommunityName.comm3 "mta_pwd"SnmpMib = snmpCommunitySecurityName.comm3 "mtaAccess"SnmpMib = snmpCommunityStorageType.comm3 volatileSnmpMib = snmpCommunityStatus.comm3 activeSnmpMib = vacmGroupName.1 mtaAccess "mtaGroup"SnmpMib = vacmSecurityToGroupStorageType.1 mtaAccess volatileSnmpMib = vacmSecurityToGroupStatus.1 mtaAccess activeSnmpMib = vacmGroupName.2 mtaAccess "mtaGroup"SnmpMib = vacmSecurityToGroupStorageType.2 mtaAccess volatileSnmpMib = vacmSecurityToGroupStatus.2 mtaAccess activeSnmpMib = vacmAccessContextMatch.mtaGroup 1 1 exactSnmpMib = vacmAccessReadViewName.mtaGroup 1 1 "ReadOnlyView"SnmpMib = vacmAccessWriteViewName.mtaGroup 1 1 "FullAccessView"SnmpMib = vacmAccessNotifyViewName.mtaGroup 1 1 "NotifyView"SnmpMib = vacmAccessStorageType.mtaGroup 1 1 volatileSnmpMib = vacmAccessStatus.mtaGroup 1 1 activeSnmpMib = vacmAccessContextMatch.mtaGroup 2 1 exactSnmpMib = vacmAccessReadViewName.mtaGroup 2 1 "ReadOnlyView"SnmpMib = vacmAccessWriteViewName.mtaGroup 2 1 "FullAccessView"SnmpMib = vacmAccessNotifyViewName.mtaGroup 2 1 "NotifyView"SnmpMib = vacmAccessStorageType.mtaGroup 2 1 volatileSnmpMib = vacmAccessStatus.mtaGroup 2 1 activeSnmpMib = pktcDevEvProgrammableReporting.65534 4115 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65533 4115 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65530 4115 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65529 4115 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65534 4491 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65533 4491 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65530 4491 hexstr: E0SnmpMib = pktcDevEvProgrammableReporting.65529 4491 hexstr: E0SnmpMib = pktcDevEvFixedReporting.1 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.2 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.3 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.4 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.5 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.6 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.7 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.8 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.10 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.11 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.14 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.15 4115 hexstr: E0.0

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 103: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

ARRIS-specific MTA SNMP Coexistence 87

SnmpMib = pktcDevEvFixedReporting.16 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.17 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.18 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.19 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.20 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.21 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.22 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.23 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.24 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.25 4115 hexstr: E0.0SnmpMib = pktcDevEvFixedReporting.26 4115 hexstr: E0.0SNMPv3NotificationReceiver =

SNMPv3NrIpAddress = 10.1.44.249SNMPv3NrTrapType = 2

TelephonyConfigFileBeginEnd = 255

Management Guide Release 6.1 Standard 1.3 June 2009

Page 104: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

88 Chapter 6

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 105: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

7 Appendix A: Endpointand Event Definitions

This appendix describes the Touchstone endpoint format and typical eventdefinitions. Notall the events and packages described in this appendix applyto Touchstone eMTAs.

Endpoint Definition

Touchstone Telephony endpoints (phone lines) use the formataaln/X , whereX is the line number (valid range is1 to the number of lines supported by theMTA).

Event Definitions

The MGCP package and event definitions in this section are based ondescriptions in Appendix A ofNetwork-Based Call Signaling Protocol, PKT-SP-NCS1.5-I02.

Basic Packa ges The following table shows the basic packages.

Package Name

Line Package LFAX Package FXRVoIP Metrics Package XRM

In the tables of events for each package, there are five columns:

Management Guide Release 6.1 Standard 1.3 June 2009

Page 106: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

90 Chapter 7

CodeThe unique symbol used for the event.

Descriptiona short description of the event

EventOne or more of:

• ✓ — the event can be requested by the call agent.

• P— the event is persistent.

• S— the event is a state that may be audited.

• C — the event may be detected or applied on a connection.

Signalif nothing appears in this column for an event, then the event cannotbe signaled on command by the call agent.Otherwise, the follow-ing symbols identify the type of event:

Symbol Event

OO On/Off signal. Thesignal is turned on untilcommanded by the call agent to turn it off, andvice versa.

TO Timeout signal. The signal lasts for a givenduration unless it is superseded by a new signal.A value of zero indicates an infinite timeoutperiod.

BR Brief signal. The event has a short, known dura-tion.

Additional InfoSpecifies the duration of TO signals and provides other informationas needed.

Line Packa ge Package Name: L

The Line package provides events and signals for analog access lines.

Code Definition Event Signal Additional Info

DTMF tones ✓ BR0-9,*,#, A,B,C,Dbz Busytone - TO Time-out = 30 seconds.cf Confirmationtone - BRci(ti, nu, na) Caller Id - BR "ti" : time; "nu" : number; "na"

: name.dl Dial tone - TO Time-out = 16 seconds.ft Fax tone ✓ -hd Off-hook transition P, S -

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 107: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Appendix A: Endpoint and Event Definitions 91

Code Definition Event Signal Additional Info

hf Flashhook P -hu On-hooktransition P, S -L DTMF long duration ✓ -ld Longduration connection C -ma Mediastart C -mt Modemtones ✓ -mwi Messagewaiting indicator - TO Time-out = 16 seconds.oc Operationcomplete ✓ -of Operationfailure ✓ -osi Openinterval - TO Default = 900ms.ot Off-hook warning tone - TO Time-out = infinite.

Distinctive ringing (0..7) - TO Time-out = 180 seconds.r0, r1, r2, r3, r4,r5, r6 or r7rg Ringing - TO Time-out = 180 seconds.ro Reordertone - TO Time-out = 30 seconds.rs Ringsplash - BRrt Ringback tone C TO Time-out = 180 seconds.sl Stutterdial tone - TO Time-out = 16 seconds.t Timer ✓ -TDD ✓ -Telecomm Devices for the

Deaf (TDD) tonesvmwi - OOVisual message waiting

indicatorwt1, wt2, wt3, wt4 Call waiting tones - TO Time-out = [(MaxReps + 1) +

(MaxReps * Delay)] seconds,where the default values forMaxReps = 1 and Delay = 10are defined in the NCS Sig-nalling MIB specification.

X DTMF tones wildcard ✓ - Matches any of the digits "0-9".

FAX Package Package Name: FXR

The FAX package proivdes local connection options, eents, and connectionparameters for FAX connections.

Code Definition Event Signal Additional Info

Gateway controlled fax xgwfax(stop, start,failure)

No special fax handling xnopfax(start)T.38 fax relay xt38(start, stop,

failure)

Management Guide Release 6.1 Standard 1.3 June 2009

Page 108: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

92 Chapter 7

In addition, the FAX package defines the following connection parameters:

Parameter Description

PGS=n Number of FAX pages sent.PGR=n Number of FAX pages received.

VoIP Metrics Pack-ag e

Package Name: XRM

The VoIP package enables collection and reporting of metrics that measurevoice traffic quality on VoIP connections.

Local Connection Options

The following local connection option (LCO) is available in the VoIP Metricspackage:

LCO Values Description

off Disable VoIP metrics collection/reporting.on EnableVoIP metrics collection/reporting.negotiate

mcrAllow VoIP metrics collection ifrequested but disable VoIP reporting.

Audit Connection Procedures

The following RequestedInfo values are returned in a DeleteConnection(DLCX) sequence and can be returned in an AuditConnection (AUCX)response.

Value Definition

XRM/LVM Returnlocal metric values.XRM/RVM Returnremote metric values.

The following extension parameters can be returned with the above proce-dures.

Code Definition

NLR Network packet loss rate (n/256)JDR Jitterbuffer discard rate (n/256)BLD Burst loss density (n/256)GLD Gaploss density (n/256)BD Burstduration (ms)GD Gapduration (ms)RTD Round trip network delay (ms)ESD Endsystem delay (ms)SL Signallevel (dBm0)

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 109: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Appendix A: Endpoint and Event Definitions 93

Code Definition

NL Noiselevel (dB)ERL Residualecho return loss (dB)GMN Minimum gap threshold (1–255)NSR Rfactor (1–100)XSR ExternalR factor (1–100)MLQ EstimatedMOS-LQ (10–50)MCQ EstimatedMOS-CQ (10–50)

Packet loss concealment type:0: unspecified1: disabled2: enhanced3: standard

PLC

Jitter Buffer Adaptive:0: unknown1: reserved2: non-adaptive3: adaptive

JBA

JBR JitterBuffer Rate (0–15)JBN Nominaljitter buffer delay (ms)JBM Maximumjitter buffer delay (ms)JBS Absolutemaximum jitter buffer delay (ms)IAJ Inter-arrival Jitter (ms)

Management Guide Release 6.1 Standard 1.3 June 2009

Page 110: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

94 Chapter 7

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 111: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

8 Index

8.8Ah, battery 16

Aaccess

mode, SNMP 66modes, coexistence, SNMP 39coexistence, SNMP 41modes, NmAccess, SNMP 39modes, SNMP 39

adding snmpCommunityTable 69Adding

vacmAccessTable 75vacmSecurityToGroupTable 72

alarm command, battery telemetry 6ARRIS MIBs, indexing 28arrisCmDevDhcpCmGatewayIpAddrV6, MIB 38arrisCmDevDhcpCmIpAddrV6, MIB 38arrisCmDevDhcpCmSubNetMaskV6, MIB 38arrisCmDevDhcpIpMode, MIB 37arrisCmDevDhcpPrimaryDhcpServerIpAddrV6, MIB 38arrisCmDevDhcpTftpSvrIpAddrV6, MIB 38arrisCmDevRangeDelay, MIB 29arrisMtaDevActiveConnections, MIB 26arrisMtaDevBase, MIB 21arrisMtaDevBatteryChargerFWRev, MIB 9arrisMtaDevBatteryEprom, MIB 9arrisMtaDevBatteryLastStateChange, MIB 12arrisMtaDevBatteryOperState, MIB 12–13arrisMtaDevBatteryOperSubState, MIB 12–13arrisMtaDevBatteryOrderingCode, MIB 4, 9arrisMtaDevBatteryStatusEntry, MIB 12arrisMtaDevBatteryStatusTable, MIB 12arrisMtaDevDocsQosParamUpSvdFlowSchedulingType, MIB 26arrisMtaDevDocsQosParamUpSvdFlowSFID, MIB 26arrisMtaDevEnableCallpSigTrace, MIB 21arrisMtaDevEstimatedChargeRemaining, MIB 3arrisMtaDevEstimatedMinutesRemaining, MIB 3arrisMtaDevInterfaceIndex, MIB 26arrisMtaDevLastCallEndTime, MIB 29arrisMtaDevLastCallStartTime, MIB 29arrisMtaDevLineCard, MIB 29arrisMtaDevLineParameterTable, MIB 25arrisMtaDevMaxCpeAllowed, MIB 25arrisMtaDevNetworkAccess, MIB 25arrisMtaDevParameters, MIB 25arrisMtaDevPktcDevEvEndpointName, MIB 26arrisMtaDevPowerSupplyTelemetry, MIB 29

arrisMtaDevProvState, MIB 17arrisMtaDevPwrSupplyBatAvailableMinutes, MIB 11, 13arrisMtaDevPwrSupplyBatRatedMinutes, MIB 13arrisMtaDevPwrSupplyBatStateOfCharge, MIB 12arrisMtaDevPwrSupplyBatteryTest, MIB 4, 11arrisMtaDevPwrSupplyBatteryTestTime, MIB 4, 12arrisMtaDevPwrSupplyChargeState, MIB 10–11arrisMtaDevPwrSupplyConfigReplaceBatTime, MIB 11arrisMtaDevPwrSupplyConfigRunTime, MIB 11arrisMtaDevPwrSupplyEnableDataShutdown, MIB 10arrisMtaDevPwrSupplyEnableDataShutdownTime, MIB 10arrisMtaDevPwrSupplyFullChargeTime, MIB 11arrisMtaDevPwrSupplyHighestTemperature, MIB 6, 11arrisMtaDevPwrSupplyHighestTemperatureClear, MIB 6, 12arrisMtaDevPwrSupplyHighestTemperatureTime, MIB 6, 12arrisMtaDevPwrSupplyHiTempBatteryShutdownControl, MIB 11arrisMtaDevPwrSupplyLowBatteryThresh, MIB 10arrisMtaDevPwrSupplyOverTempAlarmControl, MIB 5arrisMtaDevPwrSupplyOverTempAlarmThreshold, MIB 5arrisMtaDevPwrSupplyRatedBatCapacity, MIB 12arrisMtaDevPwrSupplyReadBatteryPwr, MIB 13arrisMtaDevPwrSupplyReplaceBatThresh, MIB 10arrisMtaDevPwrSupplySecondsOnBattery, MIB 13arrisMtaDevPwrSupplyTemperature, MIB 6arrisMtaDevPwrSupplyTestedBatCapacity, MIB 5, 12arrisMtaDevPwrSupplyTypicalIdlePwr, MIB 10arrisMtaDevQosMode, MIB 26arrisMtaDevResetCallStats, MIB 29arrisMtaDevRtpPercentPktsLostTotal, MIB 29arrisMtaDevRtpPktsLostTotal, MIB 29arrisMtaDevRtpRxPktsTotal, MIB 29arrisMtaDevRtpTxPktsTotal, MIB 29arrisMtaDevSWUpgradeStatus, MIB 19arrisMtaDevUpSvcFlowParameterTable, MIB 26

Bbattery

8.8Ah 16levels, monitoring 3management 1mismatch 2ordering code 4, 9over-temperature protection 5states, SNMP 13telemetry, alarm command 6telemetry, hitempbatsd command 6testing 4setting low 8

Management Guide Release 6.1 Standard 1.3 June 2009

Page 112: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

96 Chapter 8

Ccall statistics 29CMTS MIBs 31code, battery ordering 4, 9coexistence

Configuring, SNMP 67SNMP 65SNMP access modes 39SNMP access modes 41SNMP, configuration for 65SNMP, configuring 67SNMP 41

command, batterybattery telemetry, alarm 6battery telemetry, hitempbatsd 6

configuration for coexistence, SNMP 65configuring coexistence, SNMP 67Configuring

SNMP coexistence 67trap servers 78

Ddefinitions

endpoint 89ev ent 89

docsDevEventTable, MIB 29, 31docsDevEvSyslogAddress, MIB 37docsDevEvSyslogAddressType, MIB 37docsDevNmAccess, MIB 42docsDevNmAccessCommunity, MIB 42docsDevNmAccessControl, MIB 43, 45docsDevNmAccessInterfaces, MIB 43, 46docsDevNmAccessIp, MIB 43–44docsDevNmAccessIpMask, MIB 43–44docsDevNmAccessStatus, MIB 42docsDevNmAccessTable, MIB 39–45docsDevNmAccessTrapVersion, MIB 43docsDevServerConfigTftpAddress, MIB 37docsDevServerConfigTftpAddressType, MIB 37docsDevServerDhcpAddress, MIB 37docsDevServerDhcpAddressType, MIB 36–37docsDevServerTimeAddress, MIB 37docsDevServerTimeAddressType, MIB 37docsDevSwOperStatus, MIB 19docsIfCmServiceTable, MIB 29docsIfCmStatusTable, MIB 29docsIfCmtsChannelUtilizationTable, MIB 31docsIfCmtsCmStatusTable, MIB 31docsIfCmtsStatusTable, MIB 31DSx QoS 26

Eendpoint

definitions 89name format 26

ev ent definitions 89ev ents, monitoring quarantined 19

Ffeatures, SNMP security 39firmware upgrade status 19for coexistence, SNMP, configuration 65

Hhitempbatsd command, battery telemetry 6

IifIndex, MIB 26–28, 30ifTable, MIB 27–29, 31ifType, MIB 28indexing, ARRIS MIBs 28interface index 27interface types 28interfaces, network management 27

Llevels, monitoring battery 3line card status MIBs 29low battery time, setting 8

Mmanagement, battery 1MaxCpeAllowed 25MIB

arrisCmDevDhcpCmGatewayIpAddrV6 38arrisCmDevDhcpCmIpAddrV6 38arrisCmDevDhcpCmSubNetMaskV6 38arrisCmDevDhcpIpMode 37arrisCmDevDhcpPrimaryDhcpServerIpAddrV6 38arrisCmDevDhcpTftpSvrIpAddrV6 38arrisCmDevRangeDelay 29arrisMtaDevActiveConnections 26arrisMtaDevBase 21arrisMtaDevBatteryChargerFWRev 9arrisMtaDevBatteryEprom 9arrisMtaDevBatteryLastStateChange 12arrisMtaDevBatteryOperState 12–13arrisMtaDevBatteryOperSubState 12–13arrisMtaDevBatteryOrderingCode 4,9arrisMtaDevBatteryStatusEntry 12arrisMtaDevBatteryStatusTable 12arrisMtaDevDocsQosParamUpSvdFlowSchedulingType 26arrisMtaDevDocsQosParamUpSvdFlowSFID 26arrisMtaDevEnableCallpSigTrace 21arrisMtaDevEstimatedChargeRemaining 3arrisMtaDevEstimatedMinutesRemaining 3arrisMtaDevInterfaceIndex 26arrisMtaDevLastCallEndTime 29arrisMtaDevLastCallStartTime 29arrisMtaDevLineCard 29arrisMtaDevLineParameterTable 25arrisMtaDevMaxCpeAllowed 25arrisMtaDevNetworkAccess 25arrisMtaDevParameters 25arrisMtaDevPktcDevEvEndpointName 26arrisMtaDevPowerSupplyTelemetry 29arrisMtaDevProvState 17arrisMtaDevPwrSupplyBatAvailableMinutes 11,13arrisMtaDevPwrSupplyBatRatedMinutes 13arrisMtaDevPwrSupplyBatStateOfCharge 12arrisMtaDevPwrSupplyBatteryTest 4,11arrisMtaDevPwrSupplyBatteryTestTime 4,12arrisMtaDevPwrSupplyChargeState 10–11arrisMtaDevPwrSupplyConfigReplaceBatTime 11arrisMtaDevPwrSupplyConfigRunTime 11arrisMtaDevPwrSupplyEnableDataShutdown 10arrisMtaDevPwrSupplyEnableDataShutdownTime 10arrisMtaDevPwrSupplyFullChargeTime 11arrisMtaDevPwrSupplyHighestTemperature 6,11arrisMtaDevPwrSupplyHighestTemperatureClear 6,12arrisMtaDevPwrSupplyHighestTemperatureTime 6,12arrisMtaDevPwrSupplyHiTempBatteryShutdownControl 11arrisMtaDevPwrSupplyLowBatteryThresh 10arrisMtaDevPwrSupplyOverTempAlarmControl 5arrisMtaDevPwrSupplyOverTempAlarmThreshold 5arrisMtaDevPwrSupplyRatedBatCapacity 12

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 113: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Index 97

arrisMtaDevPwrSupplyReadBatteryPwr 13arrisMtaDevPwrSupplyReplaceBatThresh 10arrisMtaDevPwrSupplySecondsOnBattery 13arrisMtaDevPwrSupplyTemperature 6arrisMtaDevPwrSupplyTestedBatCapacity 5,12arrisMtaDevPwrSupplyTypicalIdlePwr 10arrisMtaDevQosMode 26arrisMtaDevResetCallStats 29arrisMtaDevRtpPercentPktsLostTotal 29arrisMtaDevRtpPktsLostTotal 29arrisMtaDevRtpRxPktsTotal 29arrisMtaDevRtpTxPktsTotal 29arrisMtaDevSWUpgradeStatus 19arrisMtaDevUpSvcFlowParameterTable 26docsDevEventTable 29,31docsDevEvSyslogAddress 37docsDevEvSyslogAddressType 37docsDevNmAccess 42docsDevNmAccessCommunity 42docsDevNmAccessControl 43,45docsDevNmAccessInterfaces 43,46docsDevNmAccessIp 43–44docsDevNmAccessIpMask 43–44docsDevNmAccessStatus 42docsDevNmAccessTable 39–45docsDevNmAccessTrapVersion 43docsDevServerConfigTftpAddress 37docsDevServerConfigTftpAddressType 37docsDevServerDhcpAddress 37docsDevServerDhcpAddressType 36–37docsDevServerTimeAddress 37docsDevServerTimeAddressType 37docsDevSwOperStatus 19docsIfCmServiceTable 29docsIfCmStatusTable 29docsIfCmtsChannelUtilizationTable 31docsIfCmtsCmStatusTable 31docsIfCmtsStatusTable 31docsQosPktClassTable xifIndex 26–28, 30ifTable 27–29,31ifType 28rip2IfConfAddress 30–31rip2IfConfAuthKey 30rip2IfConfAuthType 30rip2IfConfDefaultMetric 30rip2IfConfDomain 30rip2IfConfReceive 30rip2IfConfSend 30rip2IfConfSrcAddress 31rip2IfConfStatus 30snmpCommunityContextEngineID 67snmpCommunityContextName 67snmpCommunityMIB 41,47snmpCommunityName 48snmpCommunityName 67,70snmpCommunitySecurityName 48–49,68snmpCommunitySecurityName 67,70snmpCommunityStatus 67,70snmpCommunityStorageType 67,70snmpCommunityTable 39,41, 47–48, 67–69, 82–83snmpCommunityTransportTag 67sysUpTime 8,12upsAlarmDescr 8upsAlarmsPresent 8upsAlarmTime 8upsBatteryStatus 7upsConfigLowBattTime 7–8upsEstimatedChargeRemaining 7upsEstimatedMinutesRemaining 7–8upsIdentAgentSoftwareVersion 7upsIdentAttachedDevices 7

upsIdentManufacturer 7upsIdentModel 7upsIdentName 7upsInputNumLines 7upsInputTable 7upsOutputNumLines 8upsOutputSource 7upsOutputTable 8upsRebootWithDuration 8upsSecondsOnBattery 7upsShutdownAfterDelay 8upsShutdownType 8upsStartupAfterDelay 8userPortTable 29usmDHKickStartSecurityName 50usmDHKickStartTable 50usmDHKickstartTable 50usmUserCloneFrom 60usmUserEngineID 59–60usmUserName 50,59–60usmUserSecurityName 59–61usmUserSecurityName. 50usmUserTable 50,58–61vacmAccessContentPrefix 68,84vacmAccessContextMatch 68,75vacmAccessContextPrefix 61vacmAccessNotifyViewName 49vacmAccessNotifyViewName 68,75vacmAccessReadViewName 49vacmAccessReadViewName 68,75vacmAccessSecurityLevel 61, 68, 84vacmAccessSecurityModel 61,68, 84vacmAccesssStorageType 68,75vacmAccessStatus 68,75vacmAccessTable 41,47, 49, 58, 67–68, 75, 82, 84vacmAccessWriteViewName 49vacmAccessWriteViewName 68,75vacmGroupName 49,61, 68, 84vacmGroupName 68,72vacmSecurityModel 61,68, 83vacmSecurityModel 68vacmSecurityName 48–49,61, 68, 83vacmSecurityName 68vacmSecurityToGroupStatus 68,72vacmSecurityToGroupStorageType 68,72vacmSecurityToGroupTable 41,47–48, 58–59, 61, 67–68,

72, 82–83MIBs

CMTS 31indexing, ARRIS 28line card status 29subscriber device 29

mismatch, battery 2mode, SNMP, access 66modes

coexistence, SNMP access 39NmAccess, SNMP access 39SNMP access 39

monitoringbattery levels 3provisioning status 17quarantined events 19

Nname format, endpoint 26network management interfaces 27NetworkAccess 25NmAccess, SNMP access modes 39

Management Guide Release 6.1 Standard 1.3 June 2009

Page 114: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

98 Chapter 8

Oordering code, battery 4, 9over-temperature protection, battery 5

PPacketACE 43parameters, vacmAccessTable 68pinouts, TM508/512 telemetry block 15protection, battery over-temperature 5provisioning status, monitoring 17

QQoS, DSx 26quarantined events, monitoring 19

Rrip2IfConfAddress, MIB 30–31rip2IfConfAuthKey, MIB 30rip2IfConfAuthType, MIB 30rip2IfConfDefaultMetric, MIB 30rip2IfConfDomain, MIB 30rip2IfConfReceive, MIB 30rip2IfConfSend, MIB 30rip2IfConfSrcAddress, MIB 31rip2IfConfStatus, MIB 30

Ssecurity features, SNMP 39servers

Configuring, trap 78Trap 78

setting low battery time 8signaling trace 21SNMP

access mode 66access modes 39access modes, coexistence 39access modes, coexistence 41access modes, NmAccess 39battery states 13coexistence 65coexistence, Configuring 67coexistence types 41configuration for coexistence 65configuring coexistence 67security features 39trap transmission 66vacmAccessTable 68

snmpCommunityContextEngineID, MIB 67snmpCommunityContextName, MIB 67snmpCommunityMIB, MIB 41, 47snmpCommunityName, MIB 48, 67, 70snmpCommunitySecurityName, MIB 48–49, 67–68, 70snmpCommunityStatus, MIB 67, 70snmpCommunityStorageType, MIB 67, 70snmpCommunityTable

adding 69MIB 39, 41, 47–48, 67–69, 82–83

snmpCommunityTransportTag, MIB 67states, SNMP, battery 13statistics, call 29status

firmware upgrade 19MIBs, line card 29monitoring provisioning 17

subscriber device MIBs 29

sysUpTime, MIB 8, 12

Ttelemetry

alarm command, battery 6pinouts, TM508/512 15hitempbatsd command, battery 6

testing, battery 4TM508/512 telemetry block pinouts 15trace, signaling 21transmission, SNMP, trap 66Trap servers 78trap

servers, Configuring 78transmission, SNMP 66

Uupgrade status, firmware 19upsAlarmDescr, MIB 8upsAlarmsPresent, MIB 8upsAlarmTime, MIB 8upsBatteryStatus, MIB 7upsConfigLowBattTime, MIB 7–8upsEstimatedChargeRemaining, MIB 7upsEstimatedMinutesRemaining, MIB 7–8upsIdentAgentSoftwareVersion, MIB 7upsIdentAttachedDevices, MIB 7upsIdentManufacturer, MIB 7upsIdentModel, MIB 7upsIdentName, MIB 7upsInputNumLines, MIB 7upsInputTable, MIB 7upsOutputNumLines, MIB 8upsOutputSource, MIB 7upsOutputTable, MIB 8upsRebootWithDuration, MIB 8upsSecondsOnBattery, MIB 7upsShutdownAfterDelay, MIB 8upsShutdownType, MIB 8upsStartupAfterDelay, MIB 8userPortTable, MIB 29usmDHKickStartSecurityName, MIB 50usmDHKickStartTable, MIB 50usmDHKickstartTable, MIB 50usmUserCloneFrom, MIB 60usmUserEngineID, MIB 59–60usmUserName, MIB 50, 59–60usmUserSecurityName, MIB 59–61usmUserSecurityName., MIB 50usmUserTable, MIB 50, 58–61

VvacmAccessContentPrefix, MIB 68, 84vacmAccessContextMatch, MIB 68, 75vacmAccessContextPrefix, MIB 61vacmAccessNotifyViewName, MIB 49, 68, 75vacmAccessReadViewName, MIB 49, 68, 75vacmAccessSecurityLevel, MIB 61, 68, 84vacmAccessSecurityModel, MIB 61, 68, 84vacmAccesssStorageType, MIB 68, 75vacmAccessStatus, MIB 68, 75vacmAccessTable 75

Adding 75MIB 41, 47, 49, 58, 67–68, 75, 82, 84parameters 68SNMP 68

vacmAccessWriteViewName, MIB 49, 68, 75vacmGroupName, MIB 49, 61, 68, 72, 84

Touchstone® Telephony Release 6.1 Standard 1.3 June 2009

Page 115: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Index 99

vacmSecurityModel, MIB 61, 68, 83vacmSecurityName, MIB 48–49, 61, 68, 83vacmSecurityToGroupStatus, MIB 68, 72vacmSecurityToGroupStorageType, MIB 68, 72vacmSecurityToGroupTable 72

Adding 72MIB 41, 47–48, 58–59, 61, 67–68, 72, 82–83

Management Guide Release 6.1 Standard 1.3 June 2009

Page 116: Touchstone® Telephony for cable modems...Touchstone® Telephony Management Guide Release 6.1 Standard 1.3 Date: June 2009 Chapter 1: Managing Touchstone NIUs This chapter provides

Touchstone® TelephonyManagement Guide

© 2004–2009 ARRISAll rights reserved

Pr inted in the USA

The infor mation in this document is subject to change withoutnotice. The statements, configurations, technical data, andrecommendations in this document are believed to beaccurate and reliable, but are presented without express orimplied warranty. Users must take full responsibility for theirapplications of any products specified in this document. Theinfor mation in this document is proprietar y to ARRIS.

ARRIS, C3™, C4®, and Touchstone® are trademar ks orregistered trademar ks of ARRIS Group, Inc. Cadant® is aregistered trademar k of ARRIS Group, Inc. All othertrademar ks and registered trademar ks are the property oftheir respective holders.


Top Related