1、 ETSI TS 103 161-7 V1.1.1 (2011-10) Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 7: Media Terminal Adapter (MTA) Management Information Base (MIB) Technical Specification ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)2Refe
2、rence DTS/ATTM-003011-7 Keywords access, broadband, cable, IP, multimedia, PSTN ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse
3、 (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the ref
4、erence version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or ch
5、ange of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyrig
6、ht Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Mar
7、ks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)3Co
8、ntents Intellectual Property Rights 4g3Foreword . 4g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions, symbols and abbreviations . 7g34 Void 7g35 Requirements 7g3Annex A (informative): Bibliography . 31g3History 32g3ETSI ETSI TS 103 161-7 V1.1.1 (2
9、011-10)4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual
10、Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR s
11、earches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been pro
12、duced by ETSI Technical Committee Access, Terminals, Transmission and Multiplexing (ATTM). The present document is part 7 of a multi-part IPCablecom 1.5 deliverable covering the Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services, as identifi
13、ed below: Part 1: “Overview“; Part 2: “Architectural framework for the delivery of time critical services over Cable Television Networks using Cable Modems“; Part 3: “Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Television Networks using Cable Modems“; Part 4
14、: “Network Call Signalling Protocol“; Part 5: “Dynamic Quality of Service for the Provision of Real Time Services over Cable Television Networks using Cable Modems“; Part 6: “Event Message Specification“; Part 7: “Media Terminal Adapter (MTA Management Information Base (MIB)“; Part 8: “Network Call
15、Signalling (NCS) MIB Requirements“; Part 9: “Security“; Part 10: “Management Information Base (MIB) Framework“; Part 11: “Media terminal adapter (MTA) device provisioning“; Part 12: “Management Event Mechanism“; Part 13: “Trunking Gateway Control Protocol - MGCP option“; Part 14: “Embedded MTA Analo
16、g Interface and Powering Specification“ Part 15: “Analog Trunking for PBX Specification“; Part 16: “Signalling for Call Management Server“; Part 17: “CMS Subscriber Provisioning Specification“; Part 18: “Media Terminal Adapter Extension MIB“; Part 19: “IPCablecom Audio Server Protocol Specification
17、- MGCP option“; ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)5Part 20: “Management Event MIB Specification“; Part 21: “Signalling Extension MIB Specification“. NOTE 1: Additional parts may be proposed and will be added to the list in future versions. NOTE 2: The choice of a multi-part format for this deli
18、verable is to facilitate maintenance and future enhancements. ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)61 Scope The present document describes the IPCablecom 1.5 MTA MIB requirement. 2 References References are either specific (identified by date of publication and/or edition number or version number)
19、 or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/
20、docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are not necessary for the application of the present document but they assi
21、st the user with regard to a particular subject area. 1 IETF RFC 2132 (1997): “DHCP Options and BOOTP Vendor Extensions“. 2 IETF RFC 2616 (1999): “Hypertext Transfer Protocol - HTTP/1.1“. 3 IETF RFC 3617 (2003): “Uniform Resource Identifier (URI) Scheme and Applicability Statement for the Trivial Fi
22、le Transfer Protocol (TFTP)“. 4 IETF RFC 3495 (2003): “Dynamic Host Configuration Protocol (DHCP) Option for CableLabs, Client Configuration“. 5 ETSI TS 103 161-11: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 11:
23、Media Terminal Adapter (MTA) device provisioning“. 6 ETSI TS 103 161-9: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 9: Security“. 7 ETSI ES 202 488-2: “Access and Terminals (AT); Second Generation Transmission Sys
24、tems for Interactive Cable Television Services - IP Cable Modems; Part 2: Radio frequency interface specification“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject
25、 area. Not applicable. ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)73 Definitions, symbols and abbreviations Void. 4 Void 5 Requirements The IPCablecom MTA MIB must be implemented as defined below, using these references, 1, 2, 3, 4, 5, 6, and 7. PKTC-MTA-MIB DEFINITIONS := BEGIN IMPORTS MODULE-IDENTITY,
26、 OBJECT-TYPE, Integer32, Counter32, BITS,IpAddress, NOTIFICATION-TYPE FROM SNMPv2-SMI TruthValue, RowStatus, DisplayString, MacAddress, TEXTUAL-CONVENTION FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF clabProjPacketCable FROM CLAB-DEF-MIB ifIndex FROM IF-MIB Snm
27、pAdminString FROM SNMP-FRAMEWORK-MIB sysDescr FROM SNMPv2-MIB; pktcMtaMib MODULE-IDENTITY LAST-UPDATED “200501280000Z“ - January 28, 2005 ORGANIZATION “Packet Cable OSS Group“ CONTACT-INFO “Sumanth Channabasappa Postal: Cable Television Laboratories, Inc. 858 Coal Creek Circle Louisville, Colorado 8
28、0027-9750 U.S.A. Phone: +1 303-661-9100 Fax: +1 303-661-9199 E-mail: “ DESCRIPTION “This MIB module supplies the basic management objects for the MTA Device Acknowledgements: Angela Lyda - Arris Interactive Chris Melle - AT RFC 2132, DHCP Options and BOOTP Vendor Extensions“ := pktcMtaDevBase 2 pktc
29、MtaDevHardwareVersion OBJECT-TYPE SYNTAX SnmpAdminString(SIZE (048) MAX-ACCESS read-only STATUS obsolete DESCRIPTION “The manufacturers hardware version for this MTA.“ := pktcMtaDevBase 3 pktcMtaDevMacAddress OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION “This object
30、specifies the telephony MAC address for this device. The value of this object must be identical to the value specified in DHCP option 43 sub-option 11. “ REFERENCE “PacketCable MTA Device Provisioning Specification; RFC 2132, DHCP Options and BOOTP Vendor Extensions“ := pktcMtaDevBase 4 pktcMtaDevFQ
31、DN OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION “The Fully Qualified Domain Name for this MTA.“ := pktcMtaDevBase 5 pktcMtaDevEndPntCount OBJECT-TYPE SYNTAX Integer32 (1255) MAX-ACCESS read-only STATUS current DESCRIPTION ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)9
32、“The physical end points for this MTA.“ := pktcMtaDevBase 6 pktcMtaDevEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION “This object contains the MTA Admin Status of this device. If this object is set to true, the MTA is administratively enabled and the MTA must
33、be able to interact with PacketCable entities such as CMS, Provisioning Server, KDC, other MTAs and MGs on all PacketCable interfaces. If this object is set to false, the MTA is administratively disabled and the MTA must perform the following actions for all endpoints: - Shutdown all media sessions
34、if present, - Shutdown NCS signaling by following the Restart in Progress procedures in the PacketCable NCS specification. Additionally, the MTA must maintain the SNMP Interface for management. Also, the MTA must not continue Kerberized Key Management with CMSes until this object is set to true. Not
35、e: MTAs must renew the CMS kerberos tickets according to the PacketCable Security Specification“ REFERENCE “PacketCable Security Specification; PacketCable MTA Device Provisioning Specification“ := pktcMtaDevBase 7 pktcMtaDevTypeIdentifier OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STAT
36、US current DESCRIPTION “This is a copy of the device type identifier used in the DHCP option 60 exchanged between the MTA and the DHCP server.“ := pktcMtaDevBase 8 pktcMtaDevProvisioningState OBJECT-TYPE SYNTAX INTEGER pass (1), inProgress (2), failConfigFileError (3), passWithWarnings (4), passWith
37、IncompleteParsing (5), failureInternalError (6), failOtherReason (7) MAX-ACCESS read-only STATUS current DESCRIPTION “This object indicates the completion state of the MTA device provisioning process. pass: If the configuration file could be parsed successfully and the MTA is able to reflect the sam
38、e in its MIB, the MTA must return the value pass. inProgress: If the MTA is in the process of being provisioned, the MTA must return the value inProgress. failConfigFileError: If the configuration file was in error due to incorrect values in the mandatory parameters, the MTA must reject the configur
39、ation file and the MTA must return the value failConfigFileError. ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)10passWithWarnings: If the configuration file had proper values for all the mandatory parameters but has errors in any of the optional parameters (this includes any vendor specific OIDs which are
40、 incorrect or not known to the MTA), the MTA must return the value passWithWarnings. passWithIncompleteParsing: If the configuration file is valid, but the MTA cannot reflect the same in its configuration (for example, too many entries caused memory exhaustion), it must accept the CMS configuration
41、entries related and the MTA must return the value passWithIncompleteParsing. failureInternalError: If the configuration file cannot be parsed due to an internal error, the MTA must return the value failureInternalError. failureOtherReason: If the MTA cannot accept the configuration file for any othe
42、r reason than the ones stated above, the MTA must return the value failureOtherReason. When a final SNMP INFORM is sent as part of Step 25 of the MTA Provisioning process, this parameter is also included in the final INFORM message.“ REFERENCE “PacketCable MTA Device Provisioning Specification“ := p
43、ktcMtaDevBase 9 pktcMtaDevHttpAccess OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION “This indicates whether HTTP file access is supported for MTA configuration file transfer.“ := pktcMtaDevBase 10 pktcMtaDevProvisioningTimer OBJECT-TYPE SYNTAX Integer32 (030) UNITS “mi
44、nutes“ MAX-ACCESS read-write STATUS current DESCRIPTION “This object defines the time interval for the provisioning flow to complete. The MTA must finish all provisioning operations starting from the moment when an MTA receives its DHCP ACK and ending at the moment when the MTA downloads its configu
45、ration file (e.g., MTA5 to MTA23 for Secure Flow) within the period of time set by this object. Failure to comply with this condition constitutes the provisioning flow failure. If the object is set to 0, the MTA must ignore the provisioning timer condition.“ REFERENCE “PacketCable MTA Device Provisi
46、oning Specification.“ DEFVAL 10 := pktcMtaDevBase 11 pktcMtaDevProvisioningCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION “This object is the count of the number of times the provisioning cycle has looped through step MTA-1 since the last reboot.“ := pktcMtaDevB
47、ase 12 - pktcMtaDevErrorOidsTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcMtaDevErrorOidsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “If pktcMtaDevProvisioningState is reported with anything other than a pass(1) then this table is populated with the ETSI ETSI TS 103 161-7 V1.1.1 (2011-10)1
48、1necessary information, each pertaining to observations of the configuration file. Even if different parameters share the same error ( Ex: All Realm Names are invalid ), all recognized errors must be reported as different instances.“ := pktcMtaDevBase 13 pktcMtaDevErrorOidsEntry OBJECT-TYPE SYNTAX PktcMtaDevErrorOidsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “This contains the necessary information an MTA must attempt to provide in case the configuration file is not parsed and/or accepted in its entirety.“ INDEX pktcMtaDevErr
