1、ETSI TS 101 762 1.1.1 (2000-10) Technical Specification Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Network Management 2 ETSI TS 1 O1 762 V1.l.l (2000-1 O) Reference DTS/BRAN-0020005 Keywords Access, broadband, HI PERLAN, network, management, radio ETSI 650 Route des Lucioles F-O6921 So
2、phia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.or
3、q The present document may be made available in more than one electronic version or in print. In any ase of existina c u perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETS
4、I 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 change of status. Information on the current status of this and other ETSI documents is available at http:/www.etsi.or
5、atb/status/ If you find errors in the present document, send your comment to: editor etsi.fr Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 8 European Telecommunications Sta
6、ndards Institute 2000. All rights reserved. ETSI 3 ETSI TS 1 O1 762 V1.l.l (2000-1 O) Contents Intellectual Property Rights 4 Foreword 4 Introduction 4 1 2 3 4 4.1 4.2 4.3 4.4 4.5 5 5.1 5.2 5.3 5.3.1 5.3.2 Scope 5 References 5 Abbreviations . 6 W2 Network Management 7 Basic Principles . 7 Management
7、 of MT . 7 Mapping of the W2 Radio Interface on the Interface Table of MIB-II (informative) 7 Definition of Normalized Octet (informative) 10 Agent Implementation . 10 W2 SNMP MIB 11 The SNMP Network Management Framework . 11 Security Considerations . 11 Overview 11 AP System . 11 Overview of W2 MIB
8、 (informative) . 12 5.3.3 Relationships to other MIBs . 13 5.3.3.1 Common Definitions 13 5.3.3.2 Relationship to the CL MIBs . 13 5.3.3.3 Relationship to the “Interfaces“ Group 13 5.3.4 Definitions to Import into a SNMP Manager (informative) . 13 5.4 Definitions 13 Annex A (normative): Annex B (norm
9、ative): ETSI.H2.REG . Common Definitions Module 14 ETSI.H2.MIB . HIPERLAN Type 2 MIB Module 16 Annex C (normative): ETSI.H2ETHCL.MIB . Ethernet CL MIB Module 39 Annex D (normative): ETSI.H2ATMCL.MIB . ATM UNI CL MIB Module . 42 History . 47 ETSI 4 ETSI TS 1 O1 762 V1.l.l (2000-1 O) Intellectual Prop
10、erty 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 O00 314: “Intellectual Property Rights (IPRs); E
11、ssential, 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 -). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No g
12、uarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 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 produced by ETSI Technical Committee Broadband
13、 Radio Access Networks (BRAN). The present document gives guidelines for network management of HIPERLAN Type 2 (HIPERLAN/2) devices and defines a HIPERLAN/2 SNMP MIB. Introduction The present document is organized in the following way: Clause 4 describes some general preconditions for the MIB defini
14、tion; Clause 5 describes the W2 SNMP MIB; Annexes A, B, C, and D contain the MIB definitions (ASN.l). TR 101 683 i contains an overall description of the HIPERLAN/2 system. The Physical (PHY) layer is described in 2, the Data Link Control (DLC) layer is described in 3, the Radio Link Control (RLC) s
15、ublayer is described in 4, and the Convergence (CL) layers for Ethernet and ATM UNI are described in 5, 6, 7, and SI. ETSI 5 ETSI TS 1 O1 762 V1.l.l (2000-1 O) 1 Scope The purpose of the present document is to provide a common view of HIPERLAN Type 2 (W2) devices from different vendors for basic net
16、work monitoring and network control. This is achieved by defining a W2 SNMP MIB to optionally be included in W2 devices. For network monitoring basic performance and fault monitoring is covered. A basic set of configuration parameters is defined for network control. Systems management like device se
17、tup, software upgrade and also the manager side for network management is out of the scope of the present document. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present documen t. References are either specific (identifie
18、d by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, subsequent revisions do apply. A non-specific reference to an ETS shall also be taken to refer to later versions published as an
19、 EN with the same number. 111 ETSI TR 101 683: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; System Overview“. 121 ETSI TS 101 475: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Physical (PHY) Layer“. ETSI TS 101 761-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2
20、; Data Link Control (DLC) Layer; Part 1: Basic Data Transport Functions“. ETSI TS 101 761-2: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 2: Radio Link Control (RLC) sublayer“. ETSI TS 101 493-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type
21、2; Packet based Convergence Layer; Part 1: Common Part“. ETSI TS 101 493-2: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 2: Ethernet Service Specific Convergence Sublayer (SSCS)“. ETSI TS 101 763-1: “Broadband Radio Access Networks (BRAN); HIPERLAN T
22、ype 2; Cell based Convergence Layer; Part 1: Common Part“. ETSI TS 101 763-2: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Cell based Convergence Layer; Part 2: UNI Service Specific Convergence Sublayer (SSCS)“. ETSI TR 101 764: “Broadband Radio Access Networks (BRAN); Definition of the
23、 BRAN domain“. 131 141 151 161 171 181 191 1101 IETF RFC 2571 (April 1999): “An Architecture for Describing SNMP Management Frameworks“, Wijnen, B., Harrington, D. and R. Presuhn. IETF STD 16 RFC 1155 (May 1990): “Structure and Identification of Management Information for TCP/IP-based Internets, Ros
24、e, M. and K. McCloghrie“. IETF STD 16 RFC 1212 (March 1991): “Concise MIB Definitions“, Rose, M. and K. McCloghrie. 1111 1121 ETSI 6 ETSI TS 1 O1 762 V1.l.l (2000-1 O) u31 u41 u71 u91 IETF RFC 1215 (March 1991): “A Convention for Defining Traps for use with the SNMP“, Rose, M. IETF STD 58 RFC 2578 (
25、April 1999): “Structure of Management Information Version 2 (SMIV)“, McCloghrie, K., Perkins, D. and J. Schoenwaelder. IETF STD 58 RFC 2579 (April 1999): “TextualConventions for SMIV“, McCloghrie, K., Perkins, D. and J. Schoenwaelder. IETF STD 58 RFC 2580 (April 1999): “Conformance Statements for SM
26、IV“, McCloghrie, K., Perkins, D. and J. Schoenwaelder. IETF STD 15 RFC 1157 (May 1990): “Simple Network Management Protocol“, Case, J., Fedor, M., Schoffstall, M. and J. Davin. IETF RFC 1901 (January 1996): “Introduction to Community-based SNMPV“, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
27、. IETF RFC 1906 (January 1996): “Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPV)“, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser. IETF RFC 2572 (April 1999): “Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)“, Case, J., Ha
28、rrington D., Presuhn R. and B. Wijnen. IETF RFC 2574 (April 1999): “User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPV)“, Blumenthal, U. and B. Wijnen. IETF RFC 1905 (January 1996): “Protocol Operations for Version 2 of the Simple Network Management Protoc
29、ol (SNMPV)“, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser. IETF RFC 2573 (April 1999): “SNMPv3 Applications“, Levi, D., Meyer, P. and B. Stewart. IETF RFC 2575 (April 1999): “View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)“, Wijnen, B., Presuhn, R. an
30、d K. McCloghrie. IETF RFC 1213 (March 1991): “Management Information Base for Network Management of TCP/IP-based internets: MIB-II“, McCloghrie, K. and M. Rose. IETF RFC 2233 (November 1997): “The Interfaces Group MIB using SMIV“, McCloghrie, K. and F. Kastenholz. 3 Abbreviations For the purposes of
31、 the present document, the following abbreviations apply: AP ASN. 1 CL w2 MIB MT OID PC SMI SNMP TS Access Pint Abstract Syntax Notation One Convergence Layer HIPERLAN Type 2 Management Information Base Mobile Terminal Object IDentifier Personal Computer Structure of Management Information Simple Ne
32、twork Management Protocol Technical Specification ETSI 7 ETSI TS 1 O1 762 V1.l.l (2000-1 O) 4 H/2 Network Management This clause gives the preconditions for clause 5 where the W2 MIB, the SNMP framework etc. are described. The purpose of defining a MIB and related principles is to provide a common v
33、iew to the human network manager of W2 devices from different vendors. Basic performance and fault monitoring is covered for network monitoring. A basic set of configuration parameters is defined for network control. Systems management like device setup and software upgrade and also the manager side
34、 for network management are considered to be vendor specific and are not described in the present document. Vendor specific additions to the W2 MIB can be placed in vendor specific MIBs. It is assumed that each W2 device with SNMP support besides the W2 MIB contains at least parts of the Internet st
35、andard MIB, MIB-II. 4.1 4.2 Basic Principles SNMP network management requires an IP core network. SNMP often implies a corporate (business) environment. Centralized mode (see 3) is covered. In the future direct mode (see 3) may be covered. The W2 SNMP MIB is defined in the present document for the A
36、P. In the future it may be adapted to any managed W2 device by excluding or adding groups and single objects. SMIv2 (Structure of Management Information) is used for the definition of the W2 MIB. An easy transformation to SMIv1 (and SNMPv1) is provided for so a SNMPv1 manager can be used. For more i
37、nformation on SMI see 5.1. SNMPv3 is recommended for security reasons, but SNMPv3 is not mandatory. For more information on security see 5.1 and 5.2. Management of MT In a corporate network the MTs (PCs) are normally not monitored via SNMP because of the large number of devices. In a W2 environment
38、the mobility of the MTs adds extra complexity. The APs view of the associated MTs is included in the W2 MIB located in the AP. This can be the start for trouble shooting MT related problems. 4.3 Mapping of the H/2 Radio Interace on the Interace Table of MIB-II (informative) The interface table (ifab
39、le) of the standard Internet MIB MIB-II provides information for understanding of how the network interfaces of a device are performing. All types of managed network devices support the interface table of MIB-II. An AP normally supports interface entries for the core network interface and the W2 rad
40、io interface. Characteristics of the W2 radio interface are mapped on an interface entry of the interface table of MIB-II. This makes the W2 device look like any network device to the network manager. Different methods can be used when mapping the W2 radio interface on the ifable of MIB-II. The mapp
41、ing can be done according to RFC 1213 25 or via an extended ifable as described in RFC 2233 26. If the extended ifable is used it is possible to define interface entries for supported CLs besides the W2 interface entry. The order of the interfaces can be defined e.g. indicating that a CL interface i
42、s on top of the W2 interface. Table 1 proposes a mapping for an AP according to RFC 1213 25. Some comments: The layer described in ifable is DLC. Upper layer is CL. The interface to and from the upper layer is DLC-U-SAP, see DLC 3. Lower layer is PHY 2. ETSI 8 ETSI TS 1 O1 762 V1.l.l (2000-1 O) 0 Pa
43、cket in RFC 1213 25 means here a UDCH, UMCH, or UBCH message (see 3). From ifspeed, ifinoctets, and ifoutoctets it should be possible to calculate the utilization of the W2 interface. Just counting the data octets does not tell the utilization because of the link adaptation. Example: In a cell, ther
44、e is a single MT near the AP constantly using a data rate of 5Mbids. The MT is moved to the cell border still using a data rate of 5 Mbids. The utilization of the W2 interface of the AP is now perhaps 5 times larger than before. This is the reason why ifinoctects and ifoutoctets in Table 1 are provi
45、ded as normalized octets. A normalized octet represents a constant portion of the MAC frame, see clause 4.4. ETSI 9 ETSI TS 1 O1 762 V1.l.l (2000-1 O) Object if Descr NOTE: ifinoctets and ifoutoctets is not showing the data traffic through the AP. The traffic can be estimated from other attributes e
46、.g. ifinUcastPkts and ifOutUcastPkts (see Table 1). Syntax I Description (RFC 121 3 25) Hl2 Implementation Access Displaystring Information about the interface including According to description. read-only the name of the manufacturer, the product name and the version of the Table 1 : Mapping of a H
47、/2 Interface Entry ifMtu ifspeed ifPhysAddress only according to the physical/link protocol(s) immediately “below“ the network layer in the protocol stack. can be sentreceived on the interface, specified in octets. Gauge read- An estimate of the interfaces current only INTEGER read- The size of the
48、largest datagram, which only Not very relevant but in order not to fool a smart management application set equal to smallest MTU size of supported CLs e.g. 1 51 8 in case of Ethernet. A fix max bit rate supported by the AP. ifspeed should be set so it is not exceeded but not too high either so the r
49、eal speed always is far from ifspeed. See also clause 4.4. bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. layer immediately “below“ the network layer in the protocol stack. For interfaces which do not have such an address (e.g., a serial line), this object should PhysAddress The interfaces address at the protocol According to description. read-only Ihardware interface. IINTEGER read- IThe type of
