idnits 2.17.1 draft-combes-ipdvb-mib-rcs-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 8 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 222 has weird spacing: '... dBi dec...' == Line 224 has weird spacing: '... dBm dec...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 27, 2009) is 5384 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC3411' is mentioned on line 935, but not defined == Missing Reference: 'RFC4001' is mentioned on line 940, but not defined == Missing Reference: 'RFC5017' is mentioned on line 942, but not defined Summary: 1 error (**), 0 flaws (~~), 10 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Transport Area Working Group S. Combes 3 Internet-Draft P. Amundsen 4 Intended status: Informational M. Lambert 5 H-P. Lexow 6 SatLabs Group 7 Expires: January 2010 July 27, 2009 9 The SatLabs Group DVB-RCS MIB 10 draft-combes-ipdvb-mib-rcs-06.txt 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance 15 with the provisions of BCP 78 and BCP 79. 17 This document may not be modified, and derivative works of it 18 may not be created, except to format it for publication as an 19 RFC or to translate it into languages other than English. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as "work 30 in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html 38 This Internet-Draft will expire on January 27,2010. 40 Abstract 42 This document describes the MIB module for the Digital Video 43 Broadcasting Return Channel via Satellite system (DVB-RCS), as 44 defined by the SatLabs Group. It defines a set of MIB entities 45 to characterize the behavior and performance of network layer 46 entities deploying DVB-RCS. 48 Table of Contents 50 1. Introduction................................................3 51 2. Conventions used in this document...........................4 52 2.1. Abbreviations..........................................5 53 2.2. Glossary...............................................7 54 2.2.1. Star DVB-RCS network..............................7 55 2.2.2. Mesh DVB-RCS network..............................7 56 2.2.3. Transparent DVB-RCS network.......................7 57 2.2.4. Regenerative DVB-RCS network......................8 58 2.2.5. DVB-RCS MAC layer.................................8 59 2.2.6. DVB-RCS TDM.......................................8 60 2.2.7. DVB-RCS TDMA......................................8 61 2.2.8. IDU...............................................8 62 2.2.9. ODU...............................................8 63 2.2.10. RCST.............................................9 64 2.2.11. NCC..............................................9 65 2.2.12. Configuration file...............................9 66 2.2.13. Log file.........................................9 67 2.2.14. Installation log file............................9 68 2.2.15. Antenna alignment................................9 69 2.2.16. CW frequency.....................................9 70 2.2.17. Request Class....................................9 71 2.2.18. Channel ID......................................10 72 2.2.19. ATM profile.....................................10 73 2.2.20. MPEG profile....................................10 74 2.2.21. PID pool........................................10 75 2.2.22. Capacity Categories.............................10 76 2.2.23. Start transponder...............................11 77 2.2.24. DVB-S...........................................11 78 2.2.25. DVB-S2 and CCM/VCM/ACM..........................12 79 2.2.26. Interactive Network.............................12 80 3. MIB Module overview........................................12 81 3.1. Textual Conventions...................................13 82 3.2. Structure of the MIB..................................13 83 3.3. Relationship to the Interfaces MIB Module.............14 84 3.4. MIB groups description................................18 85 3.4.1. dvbRcsRcstSystem.................................18 86 3.4.2. dvbRcsRcstNetwork................................19 87 3.4.3. dvbRcsRcstInstall................................19 88 3.4.4. dvbRcsRcstQos....................................19 89 3.4.5. dvbRcsRcstControl................................20 90 3.4.6. dvbRcsRcstState..................................20 91 3.4.7. dvbRcsFwdLink (dvbRcsFwdConfig and dvbRcsFwdStatus 92 groups).................................................20 93 3.4.8. dvbRcsRtnLink (dvbRcsRtnConfig and dvbRcsRtnStatus 94 groups).................................................20 95 4. Definitions................................................21 96 5. Security Considerations...................................101 97 6. IANA Considerations.......................................103 98 7. Acknowledgments...........................................103 99 8. References................................................103 100 8.1. Normative References.................................103 101 8.2. Informative References...............................104 102 9. Authors' Addresses........................................106 103 10. Disclaimer...............................................107 104 11. Copyright Notice.........................................107 106 1. Introduction 108 The SatLabs Group [SATLABS] is an international non-profit EEIG 109 (European Economic Interest Grouping) committed to large-scale 110 adoption and deployment of the Digital Video Broadcasting Return 111 Channel via Satellite (DVB-RCS) standard [ETSI-RCS]. SatLabs 112 members are service providers, satellite operators, system 113 integrators, terminal manufacturers and technology providers 114 with an interest in DVB-RCS. 116 Since its creation in 2001, the main goal of the SatLabs Group 117 has been to achieve interoperability between DVB-RCS terminals 118 and systems. Therefore, the Group has defined the SatLabs 119 Qualification Program that provides an independent certification 120 process for DVB-RCS Terminals based on System Recommendations 121 defined by SatLabs. To enhance products interoperability, beyond 122 the physical and MAC layer mechanisms defined in the DVB-RCS 123 standard, SatLabs has expanded its Recommendations in the field 124 of DVB-RCS terminal management [SATLABS]. As a part of this 125 effort, SatLabs has specified a common SNMP Management 126 Information Base (MIB) for DVB-RCS terminals, which is defined 127 in this document. 129 A DVB-RCS terminal is denoted as a Return Channel Satellite 130 Terminal (RCST) in the remainder of this document. This consists 131 of an Indoor Unit (IDU) and an Outdoor Unit (ODU) connected 132 through an Inter Facility Link (IFL), usually a coaxial L-band 133 interface. On the user side, the IDU is connected to the user 134 network through a Local Area Network (LAN) interface (usually 135 Ethernet). On the network side, the ODU is connected via a 136 satellite link (the Air Interface). 138 The SatLabs Group DVB-RCS MIB is implemented in the IDU of an 139 RCST. RCST management can be performed either through the LAN 140 interface (Local management) or through the Air Interface 141 (Remote management from the Network Control Center, NCC). RCST 142 and NCC elements are shown on Figure 1. 144 +------------+ 145 | IP | 146 | End Host | 147 +-----+------+ 148 | 149 - - - - - - - -|- - - - - - - - - - - - - - - - 150 | | LAN interface | 151 | 152 | +------+--------+ | 153 | Indoor Unit | 154 | | (IDU) | | 155 +------+--------+ 156 | | | 157 Inter Facility Link (IFL) 158 | | | 159 +-----+---------+ 160 | | OutDoor Unit | | 161 | (ODU) | 162 | +------+--------+ | 163 | 164 | | Air Interface | 165 - - - - - - - |- - - - - - - - - - - - - - - - 166 RCST | 167 | +----------------+ 168 +------->| Network Control| 169 | Center (NCC) | 170 +----------------+ 172 FIGURE 1: RCST architecture 174 2. Conventions used in this document 176 This memo defines a portion of the Management Information Base 177 (MIB) for use with network management protocols in the Internet 178 community. 180 For a detailed overview of the documents that describe the 181 current Internet-Standard Management Framework, please refer to 182 section 7 of RFC 3410 [RFC3410]. 184 Managed objects are accessed via a virtual information store, 185 termed the Management Information Base or MIB. MIB objects are 186 generally accessed through the Simple Network Management 187 Protocol (SNMP). Objects in the MIB are defined using the 188 mechanisms defined in the Structure of Management Information 189 (SMI). This memo specifies a MIB module that is compliant to 190 the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 191 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 193 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 194 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 195 "OPTIONAL" in this document are to be interpreted as described 196 in BCP 14, RFC 2119 [RFC2119]. 198 2.1. Abbreviations 200 AAL5 ATM Adaptation Layer Type 5 202 ACM Adaptive Coding and Modulation (defined in [ETSI-DVBS2]) 204 ATM Asynchronous Transfer Mode 206 AVBDC Absolute Volume-Based Dynamic Capacity 208 BER Bit Error Ratio 210 BUC Block Up-Converter 212 CCM Constant Coding and Modulation 214 CNR Carrier to Noise Ratio 216 CRA Continuous Rate Assignment 218 CSC Common Signalling Channel 220 CW Continuous Wave (carrier frequency) 222 dBi deciBel (isotropic) 224 dBm deciBel (with respect to 1 mW) 226 DSCP DiffServ Code Point 228 ETSI European Telecommunications Standards Institute 229 FEC Forward Error Correction 231 GS Generic Stream 233 GSE Generic Stream Encapsulation 235 IDU InDoor Unit 237 IFL Inter-Facility Link 239 LNB Low Noise Block 241 LO Local Oscillator 243 MAC Medium Access Control 245 MIB Management Information Base 247 MPEG Motion Pictures Expert Group 249 MPE Multi-Protocol Encapsulation 251 NCC Network Control Centre 253 OAM Operations and Management 255 ODU OutDoor Unit 257 PHB Per-Hop Behavior 259 PEP Performance Enhancing Proxy 261 PID Packet IDentifier (MPEG, used as Program Identifier in 262 DVB) 264 QoS Quality of Service 266 RBDC Rate-Based Dynamic Capacity 268 RC Request Class 270 RCST Return Channel via Satellite Terminal (DVB-RCS Terminal) 272 Rx Receive 274 SDU Service Data Unit 275 SSPA Solid State Power Amplifier 277 TDM Time Division Multiplex 279 TDMA Time Division Multiple Access 281 TS Transport Stream (as defined by MPEG) 283 Tx Transmit 285 VBDC Volume-Based Dynamic Capacity 287 VCI Virtual Channel Identifier (ATM) 289 VPI Virtual Path Identifier (ATM) 291 Vpp Volts peak-to-peak 293 2.2. Glossary 295 The terms in this document are derived either from DVB-RCS 296 standard specifications [ETSI-RCS] or from SatLabs System 297 Recommendations [SATLABS]. 299 2.2.1. Star DVB-RCS network 301 This denotes a hub-and-spoke configuration where all 302 communications pass through a central hub, that usually also 303 includes the NCC. Peer-to-peer communication between RCSTs is 304 possible, but through a double satellite hop (this traffic has 305 to pass through the hub). 307 2.2.2. Mesh DVB-RCS network 309 This denotes a mesh configuration that supports peer-to-peer 310 communications in a single satellite hop directly between RCSTs. 312 2.2.3. Transparent DVB-RCS network 314 This denotes a network using transparent satellite transponders. 315 Star or mesh network configurations can be supported. In the 316 case of a mesh configuration, RCSTs need to incorporate a TDMA 317 receiver in addition to the TDM receiver. 319 2.2.4. Regenerative DVB-RCS network 321 This denotes a network using regenerative satellite 322 transponders, i.e. including some On-Board Processing 323 functionality allowing demodulation and decoding of the uplink 324 TDMA signals and re-multiplex the traffic on the downlink. Star 325 or mesh network configurations can be supported. 327 2.2.5. DVB-RCS MAC layer 329 The DVB-RCS MAC Layer represents the air interface of an RCST, 330 as specified in [ETSI-RCS]. The interface is bi-directional and 331 supports IP traffic over hub-spoke (star) and mesh satellite 332 network topologies. 334 2.2.6. DVB-RCS TDM 336 The DVB-RCS TDM corresponds to the forward link of a DVB-RCS 337 transparent system or the downlink of a DVB-RCS regenerative 338 system. It is based on either the DVB-S or DVB-S2 standard 339 specified in [ETSI-DVBS] and [ETSI-DVBS2], respectively. In the 340 DVB-RCS context, this interface is uni or bi-directional, as it 341 may also be used for a return channel dedicated to a single 342 terminal. 344 2.2.7. DVB-RCS TDMA 346 The DVB-RCS TDMA corresponds to the return or mesh link of a RCS 347 transparent system or the uplink of a RCS regenerative system. 348 It is specified in [ETSI-RCS]. 350 In the context of star transparent and mesh regenerative DVB-RCS 351 systems, this interface is uni-directional. 353 In the context of mesh transparent DVB-RCS systems, this 354 interface is bi-directional. 356 2.2.8. IDU 358 This is the indoor part of the RCST (including at least the 359 power supply, and usually also the modem and networking 360 functions). 362 2.2.9. ODU 364 This is the outdoor part of the RCST (including at least the 365 aerial, and usually also the LNB and BUC). 367 2.2.10. RCST 369 This is the Satellite Terminal, installed on the customer 370 premises. It is composed of the IDU and ODU. 372 2.2.11. NCC 374 The NCC provides Control and Monitoring Functions. It generates 375 control and timing signals for the operation of the DVB-RCS 376 Network. 378 2.2.12. Configuration file 380 The configuration file is XML formatted file, storing 381 configuration parameters for the RCST and their values. 383 2.2.13. Log file 385 The log file is stored at the RCST. This is used to log 386 particular events that occur on RCST side. 388 2.2.14. Installation log file 390 The installation log file is stored at the RCST. This logs 391 particular events that occur on RCST side, related to RCST 392 installation phase. 394 2.2.15. Antenna alignment 396 This is the process to align the RCST antenna, part of the ODU, 397 in order to enable bi-directional communication (uplink, 398 downlink) with the satellite network. 400 2.2.16. CW frequency 402 The CW frequency is the frequency of a Continuous Wave signal. 403 It is a narrowband carrier transmitted for the duration of 404 measurements during the installation of a RCST. 406 2.2.17. Request Class 408 A Request Class (RC) is a representation of a Per Hop Behavior 409 (PHB) at the MAC layer. It defines a behavior of the MAC layer 410 for a given aggregation of traffic. This behavior includes a 411 combination of Capacity Categories associated to the RC and a 412 Priority with respect to the other RCs supported by a RCST. 414 2.2.18. Channel ID 416 Each Request Class is identified by a unique Channel_ID in the 417 communication between the RCST and the NCC. 419 2.2.19. ATM profile 421 The ATM profile is one of the two profiles for traffic burst 422 format on a DVB-RCS uplink. It is based on one or more 423 concatenated ATM cells, each of length 53 bytes, plus an 424 optional prefix. 426 2.2.20. MPEG profile 428 The MPEG profile is one of the two profiles for traffic burst 429 format on the DVB-RCS uplink. It is based on a number of 430 concatenated MPEG2-TS packets, each of length 188 bytes. 432 2.2.21. PID pool 434 For the MPEG profile several RCs may be mapped within a pool of 435 several PIDs to allow cross-RC Section Packing [RFC4259]. 436 Section packing can be used on all PIDs and higher priority 437 traffic can always pre-empt lower priority streams. This reduces 438 the need for padding. 440 2.2.22. Capacity Categories 442 The TDMA timeslot allocation process for the DVB-RCS uplink 443 supports several capacity categories. 445 The Capacity Categories CRA, RBDC and A/VBDC, when authorized 446 for a RC, have to be configured from the NCC. These 447 configuration parameters are used to inform the RCST of the 448 configuration of each Category at the NCC side and thus help in 449 Capacity Requests computation. 451 The configuration of these parameters is performed for each RC. 452 A SatLabs optional feature is defined that allows their 453 configuration at the RCST level in addition to configuration per 454 RC. This feature is denoted RCST_PARA. 456 2.2.22.1. Continuous Rate Assignment (CRA) 458 CRA is a rate capacity that is provided in full in a continuous 459 manner to the RCST while required. 461 2.2.22.2. Rate-Based Dynamic Capacity (RBDC) 463 RBDC is rate capacity that is requested dynamically by an RCST. 464 RBDC capacity is provided in response to explicit requests from 465 the RCST to the NCC, such requests being absolute (i.e. 466 corresponding to the full rate currently being requested). Each 467 request overrides all previous RBDC requests from the same RCST, 468 and is subject to a maximum rate limit. 470 2.2.22.3. Volume-Based Dynamic Capacity (VBDC) 472 VBDC is volume capacity that is requested dynamically by an 473 RCST. VBDC capacity is provided in response to explicit requests 474 from the RCST to the NCC, such requests being cumulative (i.e. 475 each request adds to all previous requests from the same RCST). 477 2.2.22.4. Absolute Volume-Based Dynamic Capacity (AVBDC) 479 AVBDC is volume capacity that is requested dynamically by an 480 RCST. This capacity is provided in response to explicit requests 481 from the RCST to the NCC, such requests being absolute (i.e. 482 this request replaces the previous ones from the same RCST). 484 The combination of AVBDC and VBDC is seen as a single Capacity 485 Category, denoted A/VBDC. 487 2.2.22.5. Population ID 489 This defines a group of RCSTs within a Network. 491 2.2.23. Start transponder 493 This is the satellite transponder on which the communication is 494 initiated from a RCST point-of-view when in the installation 495 mode. The parameters corresponding to this transponder 496 (satellite orbital position, frequency, etc.) are stored at the 497 RCST as power-up configuration data. 499 2.2.24. DVB-S 501 DVB-S is the Digital Video Broadcast over Satellite [ETSI-DVBS]. 502 It is a framework and set of associated standards published by 503 ETSI for the transmission of video, audio, and data, using the 504 ISO MPEG-2 Standard [ISO-MPEG], over satellite links. 506 2.2.25. DVB-S2 and CCM/VCM/ACM 508 DVB-S2 is the Second Generation of the Digital Video Broadcast 509 for Satellite applications standard [ETSI-DVBS2]. It is a 510 framework and set of associated standards published by ETSI for 511 the transmission of video, audio and data. 513 BBFRAME: The main framing unit of the DVB-S2 protocol stack. 515 CCM: In CCM transmission mode, the forward link uses a constant 516 set of transmission parameters (FEC coding rate and modulation 517 scheme) for all receivers. 519 VCM: In VCM transmission mode, the forward link uses 520 transmission parameters which are variable on a BBFRAME-by- 521 BBFRAME, but fixed on a Receiver basis, according to fixed link 522 and propagation conditions for each Receiver. 524 ACM: In ACM transmission mode, the forward link uses 525 transmission parameters which are dynamically adjusted on a 526 BBFRAME-by-BBFRAME and Receiver-per-Receiver basis, according to 527 actual link and propagation conditions. In order to implement 528 ACM, feedback from each Receiver has to be provided by DVB-RCS 529 return channel. 531 2.2.26. Interactive Network 533 This is another name for a DVB-RCS based satellite network. 535 3. MIB Module overview 537 This MIB module provides a set of objects required for the 538 management of SatLabs-compliant RCST. The specification is 539 derived from the parameters and protocols described in 540 [SATLABS]. 542 The MIB module in this document uses the following OBJECT 543 IDENTIFIER values as already assigned by IANA under the smi- 544 numbers registry [IANA]: 546 +------------+---------------------------+ 547 | Descriptor | OBJECT IDENTIFIER value | 548 +------------+---------------------------+ 549 |dvbRcsMib |{ mib-2 transmission 239 } | 550 +------------+---------------------------+ 552 TABLE 1: Object Identifiers for the MIB 554 These values have been assigned for this MIB under the 'mib- 555 2.transmission' subtree. 557 3.1. Textual Conventions 559 This MIB module defines new textual conventions for RCST 560 indications of SatLabs defined capabilities, including profiles, 561 options and optional features. 563 DvbRcsSystemSatLabsProfileMap represents the SatLabs profiles 564 supported as defined in [SATLABS]. 566 DvbRcsSystemSatLabsOptionMap represents the SatLabs options 567 supported as defined in [SATLABS]. These are options that are 568 used for the certification of SatLabs terminals. They represent 569 important functionality, with impact on interoperability, and 570 their support is advertised with the RCST certification level. 572 DvbRcsSystemSatLabsFeatureMap represents the SatLabs optional 573 features supported as defined in [SATLABS]. These represent 574 minor features, not necessary for interoperability. They are not 575 used for the certification of SatLabs terminals. 577 3.2. Structure of the MIB 579 This MIB module is structured into two top level groups: 581 o The dvbRcsMibObjects group includes all the managed objects 582 of the DVB-RCS MIB. 584 o The dvbRcsConformance group includes the compliance 585 statements for DVB-RCS terminals that are compliant with 586 [SATLABS]. The managed objects are grouped into formal object 587 groups (i.e. units of conformance) according to the relation 588 to specific SatLabs options or features. The conformance 589 statements (MODULE-COMPLIANCE specification) are described 590 within the dvbRcsRcstCompliances group while the units of 591 conformance are described within the dvbRcsRcstGroups group. 593 The dvbRcsMibObjects group is further structured into three 594 groups: dvbRcsRcst, dvbRcsFwdLink and dvbRcsRtnLink. 596 The dvbRcsRcst group covers management related to the RCST 597 equipment. It is structured into six groups: 599 o dvbRcsRcstSystem 601 o dvbRcsRcstNetwork 603 o dvbRcsRcstInstall 605 o dvbRcsRcstQos 607 o dvbRcsRcstControl 609 o dvbRcsRcstState 611 The dvbRcsFwdLink group covers management information related to 612 the RCST forward link. It is structured into two groups: 614 o dvbRcsFwdConfig 616 o dvbRcsFwdStatus 618 The dvbRcsRtnLink group covers management information related to 619 the RCST return link. It is structured into two groups: 621 o dvbRcsRtnConfig 623 o dvbRcsRtnStatus 625 Tables within each of these groups cover different functions 626 like return link traffic management (packet classes, Request 627 Classes, PID pools) and forward links configuration and status. 629 Rows created automatically (e.g., by the device according to the 630 hardware configuration) may and generally will have a mixture of 631 configuration and status objects within them. Rows that are 632 meant to be created by the management station are generally 633 restricted to configuration (read-create) objects. 635 3.3. Relationship to the Interfaces MIB Module 637 This section clarifies the relationship of this MIB module to 638 the Interfaces MIB [RFC2863]. Several areas of correlation are 639 addressed in the following. The implementer is referred to the 640 Interfaces MIB document in order to understand the general 641 intent of these areas. 643 IANA has assigned three ifType labels for DVB-RCS. Each RCST 644 MUST support at least the three following interfaces: 646 o dvbRcsMacLayer (239), -- DVB-RCS MAC Layer 648 DVB-RCS MAC Layer represents the complete air interface of an 649 RCST, as specified in [ETSI-RCS]. This interface supports star 650 and mesh networks and is bi-directional. Only star networks 651 are considered by the present MIB module. 653 o dvbTdm (240), -- DVB Satellite TDM 655 DVB-RCS Physical link based on Time Division Multiplexing. It 656 corresponds to the forward link of a RCS transparent system or 657 the downlink of a RCS regenerative system. It is based on 658 either DVB-S or DVB-S2 standard specified in [ETSI-DVBS] and 659 [ETSI-DVBS2]. Only transparent systems are considered by the 660 present MIB module. 662 In the DVB-RCS context, this interface is uni or bi- 663 directional. 665 In the present MIB module, only a uni-directional (i.e. 666 forward link, or downstream) dvbTdm interface is considered. 668 o dvbRcsTdma (241), -- DVB-RCS TDMA 670 DVB-RCS Physical link based on Time Division Multiple Access. 671 It corresponds to the return or mesh link of a RCS transparent 672 system or the uplink of a RCS regenerative system. It is based 673 on the DVB-RCS standard specified in [ETSI-RCS]. 675 In the context of star transparent and mesh regenerative DVB- 676 RCS systems, this interface is uni-directional. 678 In the context of mesh transparent DVB-RCS systems, this 679 interface is bi-directional. 681 Only star transparent systems are considered by the present 682 MIB module (i.e. return link, or upstream). 684 The protocol stack (as reflected in ifStackTable) will be as 685 follows: 687 +--------------------------+ 688 | IP | 689 +--------------------------+ 690 | dvbRcsMacLayer | 691 +---------------+----------+ 692 | dvbRcsTdma | dvbTdm | 693 +---------------+----------+ 694 | MPEG/ATM | MPEG/GS | 695 +---------------+----------+ 697 FIGURE 2: RCST protocol stack 699 An additional Ethernet interface is used on the LAN side of the 700 RCST (see Figure 1). 702 An instance of ifEntry exists for each dvbTdm interface, for 703 each dvbRcsTdma (normally only one), and for each dvbRcsMac 704 layer (normally only one). 706 The interface counters relate to: 708 o dvbRcsMacLayer: DVB-RCS two-way MAC interface that counts 709 aggregate Multi-Protocol Encapsulation (MPE) frames, Generic 710 Stream Encapsulation (GSE) encapsulated PDUs (equals IP 711 packets), and ATM Adaptation Layer 5 (AAL5) frames. 713 MPE is specified in [ETSI-DAT] and is transported over MPEG, 714 which is specified in [ISO-MPEG]. MPEG is transported over GS or 715 TS (Transport Stream) carriers. The TS carrier is specified in 716 [ETSI-DVBS] for DVB-S and [ETSI-DVBS2] for DVB-S2. 718 GSE is specified in [ETSI-GSE] and is transported over the GS 719 (Generic Stream) carrier, which is specified in [ETSI-DVBS2]. 721 ATM is specified in [ITU-ATM]. 723 AAL5 is specified in [ITU-AAL5]. 725 o dvbTdm: The DVB-RCS TDM interface that counts MPEG TS packets 726 at stream level, if the TS format is used. If the Generic 727 Stream (GS) format is used, it counts GSE packets. 729 o dvbRcsTdma: The DVB-RCS TDMA interface that counts aggregate 730 ATM and MPEG TS packets. 732 The ifStackTable [RFC2863] MUST be implemented to identify the 733 relationships among sub-interfaces. 735 The following example is a DVB-RCS star network with DVB-S and 736 DVB-RCS. As illustrated on Figure 3, it shows a DVB-RCS MAC 737 interface with one downstream and one upstream interface. In 738 this network, ATM encapsulation is used in the DVB-RCS uplink. 739 Two ATM Logical Ports are shown. DVB-S2 or DVB-S can be used in 740 the downlink. 742 ifType 214 'mpegTransport' can also be used for counting TS 743 packets and bytes for subinterfaces of dvbRcsTdma or dvbTdm, 744 e.g. per PID oriented or per TS oriented as desired and 745 applicable. 747 +----------------------------------------------------------+ 748 | IP Network Layer | 749 +------+----------------------------------+----------------+ 750 | | 751 +------+-------+ +------------------+----------------+ 752 | Ethernet LAN | | dvbRcsMacLayer | 753 +--------------+ +-------------+---------------------+ 754 | | 755 +-------------+-----------+ +---+---+ 756 | dvbRcsTdma | |dvbTdm | 757 +-----+-------------+-----+ +-------+ 758 | | 759 +-----+-----+ +-----+-----+ 760 |atm-logical| |atm-logical| 761 +-----------+ +-----------+ 763 FIGURE 3: Example stacking 765 As can be seen from this example, the dvbRcsMacLayer interface 766 is layered on top of the downstream and upstream interfaces, and 767 the upstream interface is layered on top of upstream ATM logical 768 links. 770 In this example, the assignment of index values could be as 771 follows: 773 ifIndex ifType Description 774 2 dvbRcsMacLayer (239) DVB-RCS MAC Layer 775 3 dvbRcsTdma (241) DVB-RCS TDMA Upstream 776 4 dvbTdm(240) DVB-RCS TDM Downstream 777 5 atm-logical(80) ATM Logical Port 778 6 atm-logical(80) ATM Logical Port 780 The corresponding ifStack entries would then be: 782 +--------------------+-------------------+ 783 | IfStackHigherLayer | ifStackLowerLayer | 784 +--------------------+-------------------+ 785 | 0 | 1 | 786 | 0 | 2 | 787 | 1 | 0 | 788 | 2 | 3 | 789 | 2 | 4 | 790 | 3 | 5 | 791 | 3 | 6 | 792 | 4 | 0 | 793 | 5 | 0 | 794 | 6 | 0 | 795 +--------------------+-------------------+ 797 TABLE 2: Example ifStack entries 799 3.4. MIB groups description 801 3.4.1. dvbRcsRcstSystem 803 The MIB objects in this group gather some basic information that 804 would allow anyone to trace the history - the life - of the RCST 805 as well as to get a complete description of its constitution on 806 the component point of view, including the SatLabs 807 options/features support statement. Many of the parameters will 808 be defined at installation. 810 This group contains description parameters related to the RCST 811 type (ODU type) and location. These parameters are believed to 812 stay unchanged once it has been defined during installation. 813 Modification of hardware equipment, maintenance operations and 814 geographical re-location may require an update of those MIB 815 objects. Note that dvbRcsRcstSystem. dvbRcsSystemLocation object 816 gives the location of the ODU antenna, which is needed for 817 network operation, while the system.sysLocation (MIB-II SNMP 818 OID) provides the location of the IDU unit, which can not be 819 used for the same purpose. 821 The RCST must provide either Read-Write access to 822 dvbRcsSystemOdu parameters or, alternatively, provide the list 823 of supported devices through the rcstOduListGroup (see 824 conformance section). This group of parameters, defined in 825 dvbRcsRcstSystem group, allows the selection by the RCST 826 installer of the actual ODU type. In such a case, the installer 827 must set dvbRcsOduTxType, dvbRcsOduRxType and 828 dvbRcsOduAntennaType according to the selected BUC, LNB and 829 antenna respectively. 831 3.4.2. dvbRcsRcstNetwork 833 This group contains all the MIB objects related to network 834 parameters. 836 In this subgroup, two objects have been defined in order to 837 differentiate between control and user traffic and associate 838 them with a physical interface. Both dvbRcsRcstNetwork. 839 dvbRcsNetworkLanIpAddress (Traffic) and dvbRcsRcstNetwork. 840 dvbRcsNetworkOamIpAddress (OAM) provide the value of the IP 841 address of, respectively, the user traffic and the control and 842 management traffic. 844 3.4.3. dvbRcsRcstInstall 846 This group contains all the information related to the RCST 847 installation and commissioning. Many parameters are believed to 848 stay unchanged once it has been defined during installation. 849 Modification of hardware equipment, maintenance operations and 850 geographical re-location may require an update of those MIB 851 objects. 853 3.4.4. dvbRcsRcstQos 855 This group contains objects to configure the Quality of Service 856 (QoS) of the RCST by the NCC. 858 The dvbRcsPktClass table defines the packet classification for 859 IP layer 3 classifications. Each dvbRcsPktClass entry is mapped 860 to a dvbRcsPhbEntry in the dvbRcsPhbMappingTable. 862 The dvbRcsPhbMappingTable makes the relation between a packet 863 classification entry, a Per-Hop Behavior (PHB) identifier and a 864 Request class entry. 866 The dvbRcsRequestClassTable defines all the layer 2 DVB-RCS QoS 867 parameters. 869 3.4.5. dvbRcsRcstControl 871 This MIB group contains objects a network manager can use to 872 invoke actions and tests supported by the RCST agent and to 873 retrieve the action/test results. 875 3.4.6. dvbRcsRcstState 877 This MIB group describes the fault state, software versions and 878 configuration file versions of the RCST. 880 3.4.7. dvbRcsFwdLink (dvbRcsFwdConfig and dvbRcsFwdStatus groups) 882 This MIB group contains parameters that enable the NCC to have 883 access to data about the forward link. 885 Configuration information is kept into the dvbRcsFwdLink. 886 dvbRcsFwdConfig subgroup. Status information is kept into the 887 dvbRcsFwdLink.dvbRcsFwdStatus subgroup. 889 The information in 890 dvbRcsFwdLink.dvbRcsFwdConfig.dvbRcsFwdStartTable is used for 891 the first time the RCST tries to acquire the forward link. All 892 these objects values are aligned with the Satellite Delivery 893 System Descriptor in the Network Information Table (NIT) table 894 [ETSI-SI]. 896 The objects in the 897 dvbRcsFwdLink.dvbRcsFwdConfig.dvbRcsFwdStatusTable are aligned 898 with the satellite forward path descriptor form the RCS Map 899 Table (RMT) [ETSI-RCS] and with the Physical Layer (PL) Header 900 [ETSI-DVBS2], which specified the MODCOD (modulation and FEC 901 rate) and the Type (frame length short of long and the 902 presence/absence of pilots). 904 3.4.8. dvbRcsRtnLink (dvbRcsRtnConfig and dvbRcsRtnStatus groups) 906 This MIB group contains parameters that enable the NCC to have 907 access to data about the return link. 909 Configuration information is kept into the dvbRcsRtnLink. 910 dvbRcsRtnConfig subgroup. Status information is kept into the 911 dvbRcsRtnLink.dvbRcsrtnStatus subgroup. 913 The RCST is only able to deal with one return link at a time. 914 Hence, there is no need to define a table to collect the 915 different SNMP objects, as it is done for the forward. 917 4. Definitions 919 DVBRCS-MIB DEFINITIONS ::= BEGIN 921 IMPORTS 922 MODULE-IDENTITY, 923 OBJECT-TYPE, 924 Integer32, 925 Unsigned32, 926 transmission 927 FROM SNMPv2-SMI -- [RFC2578] 928 TEXTUAL-CONVENTION, 929 RowStatus 930 FROM SNMPv2-TC -- [RFC2579] 931 OBJECT-GROUP, 932 MODULE-COMPLIANCE 933 FROM SNMPv2-CONF -- [RFC2580] 934 SnmpAdminString 935 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 936 InetAddressType, 937 InetAddress, 938 InetAddressPrefixLength, 939 InetPortNumber 940 FROM INET-ADDRESS-MIB -- [RFC4001] 941 Uri 942 FROM URI-TC-MIB; -- [RFC5017] 944 dvbRcsMib MODULE-IDENTITY 945 LAST-UPDATED "200907201200Z" 946 ORGANIZATION "The SatLabs Group" 947 CONTACT-INFO 948 "The SatLabs Group 949 Web: www.satlabs.org 950 E-mail: info@satlabs.org" 951 DESCRIPTION 952 "DVB-RCS MIB subtree. 953 This MIB module applies to equipment that is a Return 954 Channel Satellite Terminal (RCST) defined in the Digital 955 Video Broadcasting Return Channel via Satellite system 956 (DVB-RCS) standard (ETSI EN 301 791 Digital Video 957 Broadcasting (DVB); Interaction Channel for Satellite 958 Distribution Systems, European Telecommunications 959 Standards Institute (ETSI)). 960 It defines a set of MIB entities to characterise the 961 behaviour and performance of network layer entities 962 implementing DVB-RCS. 963 This MIB module is intended to be used by DVB-RCS 964 equipment following the SatLabs System Recommendations, 965 defined by the SatLabs Group and available at 966 www.satlabs.org. 967 Note that, if not stated otherwise in the object 968 DESCRIPTION clause, all writable objects are 969 persistent." 970 REVISION "200907201200Z" 971 DESCRIPTION 972 "Revision of this MIB module, following MIB doctor review 973 and adjustments based on the MIB authoring guidelines 974 from the IETF." 975 ::= { transmission 239 } 977 --============================================================== 978 -- Textual Conventions 979 --============================================================== 981 DvbRcsSatLabsProfileMap ::= TEXTUAL-CONVENTION 982 STATUS current 983 DESCRIPTION 984 "This textual convention enumerates the declaration of 985 the SatLabs defined terminal profiles. (0) refers to the 986 most significant bit." 987 REFERENCE 988 "SatLabs System Recommendations available at 989 www.satlabs.org" 990 SYNTAX BITS { 991 dvbs(0), 992 dvbs2ccm(1), 993 dvbs2acm(2), 994 spare1(3), 995 spare2(4), 996 spare3(5), 997 spare4(6), 998 spare5(7), 999 spare6(8), 1000 spare7(9), 1001 spare8(10), 1002 spare9(11), 1003 spare10(12), 1004 spare11(13), 1005 spare12(14), 1006 spare13(15), 1007 spare14(16), 1008 spare15(17), 1009 spare16(18), 1010 spare17(19), 1011 spare18(20), 1012 spare19(21), 1013 spare20(22), 1014 spare21(23), 1015 spare22(24), 1016 spare23(25), 1017 spare24(26), 1018 spare25(27), 1019 spare26(28), 1020 spare27(29), 1021 spare28(30), 1022 spare29(31) 1023 } 1025 DvbRcsSatLabsOptionMap ::= TEXTUAL-CONVENTION 1026 STATUS current 1027 DESCRIPTION 1028 "This textual convention enumerates the declaration of 1029 the SatLabs defined options. (0) refers to the most 1030 significant bit." 1031 REFERENCE 1032 "SatLabs System Recommendations available at 1033 www.satlabs.org" 1034 SYNTAX BITS { 1035 mpegTrf(0), 1036 coarseSync(1), 1037 wideHop(2), 1038 fastHop(3), 1039 dynamicMfTdma(4), 1040 contentionSync(5), 1041 qpskLow(6), 1042 mod16Apsk(7), 1043 mod32Apsk(8), 1044 normalFec(9), 1045 multiTs(10), 1046 gsTs(11), 1047 enhQoS(12), 1048 pep(13), 1049 http(14), 1050 ftp(15), 1051 dns(16), 1052 chIdStrict(17), 1053 nlid(18), 1054 snmpMisc(19), 1055 spare1(20), 1056 spare2(21), 1057 spare3(22), 1058 spare4(23), 1059 spare5(24), 1060 spare6(25), 1061 spare7(26), 1062 spare8(27), 1063 spare9(28), 1064 spare10(29), 1065 spare11(30), 1066 spare12(31) 1067 } 1069 DvbRcsSatLabsFeatureMap ::= TEXTUAL-CONVENTION 1070 STATUS current 1071 DESCRIPTION 1072 "This textual convention enumerates the declaration 1073 of the SatLabs specified compatibility and 1074 configuration features. (0) refers to the most 1075 significant bit." 1076 REFERENCE 1077 "SatLabs System Recommendations available at 1078 www.satlabs.org" 1079 SYNTAX BITS { 1080 rcstPara(0), 1081 installLog(1), 1082 enhClassifier(2), 1083 routeId(3), 1084 oduList(4), 1085 extNetwork(5), 1086 extControl(6), 1087 extConfig(7), 1088 extStatus(8), 1089 spare6(9), 1090 spare7(10), 1091 spare8(11), 1092 spare9(12), 1093 spare10(13), 1094 spare11(14), 1095 spare12(15), 1096 spare13(16), 1097 spare14(17), 1098 spare15(18), 1099 spare16(19), 1100 spare17(20), 1101 spare18(21), 1102 spare19(22), 1103 spare20(23), 1104 spare21(24), 1105 spare22(25), 1106 spare23(26), 1107 spare24(27), 1108 spare25(28), 1109 spare26(29), 1110 spare27(30), 1111 spare28(31) 1112 } 1114 --============================================================== 1115 -- object type definitions 1116 --============================================================== 1117 dvbRcsMibObjects OBJECT IDENTIFIER ::= {dvbRcsMib 1} 1118 dvbRcsConformance OBJECT IDENTIFIER ::= {dvbRcsMib 2} 1120 dvbRcsRcst OBJECT IDENTIFIER ::= {dvbRcsMibObjects 1} 1121 dvbRcsFwdLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 2} 1122 dvbRcsRtnLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 3} 1124 dvbRcsRcstSystem OBJECT IDENTIFIER ::= {dvbRcsRcst 1} 1125 dvbRcsRcstNetwork OBJECT IDENTIFIER ::= {dvbRcsRcst 2} 1126 dvbRcsRcstInstall OBJECT IDENTIFIER ::= {dvbRcsRcst 3} 1127 dvbRcsRcstQos OBJECT IDENTIFIER ::= {dvbRcsRcst 4} 1128 dvbRcsRcstControl OBJECT IDENTIFIER ::= {dvbRcsRcst 5} 1129 dvbRcsRcstState OBJECT IDENTIFIER ::= {dvbRcsRcst 6} 1131 dvbRcsFwdConfig OBJECT IDENTIFIER ::= {dvbRcsFwdLink 1} 1132 dvbRcsFwdStatus OBJECT IDENTIFIER ::= {dvbRcsFwdLink 2} 1134 dvbRcsRtnConfig OBJECT IDENTIFIER ::= {dvbRcsRtnLink 1} 1135 dvbRcsRtnStatus OBJECT IDENTIFIER ::= {dvbRcsRtnLink 2} 1137 --============================================================== 1138 -- dvbRcsRcstSystem sub-tree object types 1139 --============================================================== 1140 dvbRcsSystemMibRevision OBJECT-TYPE 1141 SYNTAX SnmpAdminString 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "This object allows the SNMP agent to report the 1146 implemented MIB module revision. 1147 The supported REVISION of this module is reported." 1148 ::= {dvbRcsRcstSystem 1} 1150 --============================================================== 1151 -- Options declared according to the textual conventions 1152 --============================================================== 1153 dvbRcsSystemSatLabsProfilesDeclaration OBJECT-TYPE 1154 SYNTAX DvbRcsSatLabsProfileMap 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "Indicates the SatLabs profiles supported as defined in 1159 the SatLabs System Recommendations. A value of 1 1160 indicates that the respective option is supported. The 1161 mapping to the profiles is to be understood as described 1162 here. (0) refers to the most significant bit. 1164 dvbs(0) -> DVBS profile (DVB-S support) 1165 dvbs2ccm(1) -> DVB-S2 CCM profile (CCM support) 1166 dvbs2acm(2) -> DVB-S2 ACM profile (CCM, VCM and ACM 1167 support)" 1168 REFERENCE 1169 "SatLabs System Recommendations available at 1170 www.satlabs.org" 1171 ::= {dvbRcsRcstSystem 2} 1173 dvbRcsSystemSatLabsOptionsDeclaration OBJECT-TYPE 1174 SYNTAX DvbRcsSatLabsOptionMap 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "Indicates the SatLabs options supported as defined in the 1179 SatLabs System Recommendations. A value of 1 indicates 1180 that the respective option is supported. The mapping to 1181 the options is to be understood as described here.(0) 1182 refers to the most significant bit. 1184 mpegTrf(0) -> MPEG_TRF 1185 coarseSync(1) -> COARSE_SYNC 1186 wideHop(2) -> WIDE_HOPP 1187 fastHop(3) -> FAST_HOPP 1188 dynamicMfTdma(4) -> Dynamic_MF_TDMA 1189 contentionSync(5) -> CONTENTION_SYNC 1190 qpskLow(6) -> QPSKLOW 1191 mod16Apsk(7) -> 16APSK 1192 mod32Apsk(8) -> 32APSK 1193 normalFec(9) -> NORMALFEC 1194 multiTs(10) -> MULTITS 1195 gsTs(11) -> GSTS 1196 enhQoS(12) -> ENHQOS 1197 pep(13) -> PEP 1198 http(14) -> HTTP 1199 ftp(15) -> FTP 1200 dns(16) -> DNS 1201 chIdStrict(17) -> CHID_STRICT 1202 nlid(18) -> NLID 1203 snmpMisc(19) -> SNMPMISC 1205 The support of specific options mandates the support of 1206 specific objects and access levels." 1207 REFERENCE 1208 "SatLabs System Recommendation available at 1209 www.satlabs.org" 1210 ::= {dvbRcsRcstSystem 3} 1212 dvbRcsSystemSatLabsFeaturesDeclaration OBJECT-TYPE 1213 SYNTAX DvbRcsSatLabsFeatureMap 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "Indicates the optional compatibility features and minor 1218 options supported as defined in the SatLabs System 1219 Recommendations. A value of 1 indicates that the 1220 respective feature is supported. The mapping to the 1221 features is to be understood as described here. (0) 1222 refers to the most significant bit. 1224 rcstPara(0) -> RCST_PARA feature 1225 installLog(1) -> INSTALL_LOG feature 1226 enhClassifier(2) -> ENHCLASSIFIER feature 1227 routeId(3) -> ROUTE_ID feature 1228 oduList(4) -> ODULIST feature 1229 extNetwork(5) -> EXTNETWORK feature 1230 extControl(6) -> EXTCONTROL feature 1231 extConfig(7) -> EXTCONFIG feature 1232 extStatus(8) -> EXTSTATUS feature 1234 The support of specific features mandates the support of 1235 specific objects and access levels." 1236 REFERENCE 1237 "SatLabs System Recommendation available at 1238 www.satlabs.org" 1239 ::= {dvbRcsRcstSystem 4} 1241 dvbRcsSystemLocation OBJECT-TYPE 1242 SYNTAX SnmpAdminString 1243 MAX-ACCESS read-write 1244 STATUS current 1245 DESCRIPTION 1246 "Physical location of the ODU antenna expressed as 1247 Longitude, Latitude and Altitude. The string 1248 shall have 31 characters in the following format: 1249 ,,,,,M 1250 where x, y and z represents digits, 1251 a=N or S, 1252 b=E or W, 1253 Reading the digits from left to right: 1254 'x' 7 latitude digits; x digits 1-2 contain the 1255 degrees, x digits 3-7 contain the minutes in decimal; 1256 'y' 8 longitude digits; y digits 1-3 contain the 1257 degrees, y digits 4-8 contain the minutes in decimal; 1258 'z' 5 altitude digits; meters above sea level in 1259 decimal; 1260 '.' is the decimal point; 1261 ',' is the field separator; 1262 'M' is the indicator for altitude meters. 1264 This format is a modified subset of the NMEA 0183 1265 (National Marine Electronics Association, Interface 1266 Standard) format for Global Positioning System Fix 1267 Data. 1269 This location and the satellite position are used to 1270 calculate the RCST-satellite path delay. 1272 Note: The system.sysLocation object of MIB-II provides 1273 physical location of the IDU unit." 1274 ::= {dvbRcsRcstSystem 5} 1276 dvbRcsSystemOduAntennaSize OBJECT-TYPE 1277 SYNTAX SnmpAdminString 1278 UNITS "cm" 1279 MAX-ACCESS read-write 1280 STATUS current 1281 DESCRIPTION 1282 "Diameter of the antenna." 1283 ::= {dvbRcsRcstSystem 6} 1284 dvbRcsSystemOduAntennaGain OBJECT-TYPE 1285 SYNTAX Unsigned32 1286 UNITS "x0.1 dBi" 1287 MAX-ACCESS read-write 1288 STATUS current 1289 DESCRIPTION 1290 "Antenna peak gain of the ODU." 1291 ::= {dvbRcsRcstSystem 7} 1293 dvbRcsSystemOduSspa OBJECT-TYPE 1294 SYNTAX Unsigned32 1295 UNITS "x0.1 W" 1296 MAX-ACCESS read-write 1297 STATUS current 1298 DESCRIPTION 1299 "Power level of the Solid State Power Amplifier 1300 installed in the ODU." 1301 ::= {dvbRcsRcstSystem 8} 1303 dvbRcsSystemOduTxType OBJECT-TYPE 1304 SYNTAX SnmpAdminString 1305 MAX-ACCESS read-write 1306 STATUS current 1307 DESCRIPTION 1308 "Type of transmitter installed in the ODU." 1309 ::= {dvbRcsRcstSystem 9} 1311 dvbRcsSystemOduRxType OBJECT-TYPE 1312 SYNTAX SnmpAdminString 1313 MAX-ACCESS read-write 1314 STATUS current 1315 DESCRIPTION 1316 "Type of LNB installed in the ODU, with 1317 information such as vendor type, output type (single, 1318 twin, quad,...), etc." 1319 ::= {dvbRcsRcstSystem 10} 1321 dvbRcsSystemOduRxBand OBJECT-TYPE 1322 SYNTAX INTEGER { 1323 oduHighRxBand (0), 1324 oduLowRxBand (1) 1326 } 1327 MAX-ACCESS read-write 1328 STATUS current 1329 DESCRIPTION 1330 "LNB High-Band/Low-Band selector. High Band corresponds 1331 to the emission of a 18-26 kHz tone with 0.4-0.8 Vpp in 1332 the Rx IFL cable: 1333 (0) - High Band 1334 (1) - Low Band" 1335 ::= {dvbRcsRcstSystem 11} 1337 dvbRcsSystemOduRxLO OBJECT-TYPE 1338 SYNTAX Unsigned32 1339 UNITS "x100 Hz" 1340 MAX-ACCESS read-write 1341 STATUS current 1342 DESCRIPTION 1343 "Frequency of LNB Local Oscillator (in 100 Hz)" 1344 ::= {dvbRcsRcstSystem 12} 1346 dvbRcsSystemOduTxLO OBJECT-TYPE 1347 SYNTAX Unsigned32 1348 UNITS "x100 Hz" 1349 MAX-ACCESS read-write 1350 STATUS current 1351 DESCRIPTION 1352 "Frequency of Block Up-Converter Local Oscillator 1353 (in 100 Hz)." 1354 ::= {dvbRcsRcstSystem 13} 1356 dvbRcsSystemIduPep OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 14} 1358 dvbRcsTcpPep OBJECT-TYPE 1359 SYNTAX INTEGER{ 1360 disabled (0), 1361 enabled (1) 1362 } 1363 MAX-ACCESS read-write 1364 STATUS current 1365 DESCRIPTION 1366 "Status and control of embedded TCP PEP. 1368 0 - disabled or not implemented 1369 1 - enabled" 1370 ::={dvbRcsSystemIduPep 1} 1372 dvbRcsHttpPep OBJECT-TYPE 1373 SYNTAX INTEGER{ 1374 disabled (0), 1375 enabled (1) 1376 } 1377 MAX-ACCESS read-write 1378 STATUS current 1379 DESCRIPTION 1380 "Status and control of embedded HTTP PEP. 1381 0 - disabled or not implemented 1382 1 - enabled" 1383 ::={dvbRcsSystemIduPep 2} 1385 --============================================================== 1386 -- ODU structural entities 1387 --============================================================== 1389 dvbRcsOduTx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 15} 1390 dvbRcsOduRx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 16} 1391 dvbRcsOduAntenna OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 17} 1393 --============================================================== 1394 -- ODU BUC 1395 --============================================================== 1397 dvbRcsOduTxTypeTable OBJECT-TYPE 1398 SYNTAX SEQUENCE OF DvbRcsOduTxTypeEntry 1399 MAX-ACCESS not-accessible 1400 STATUS current 1401 DESCRIPTION 1402 "This table contains the identification of each well- 1403 known BUC type supported by the IDU, and provides its 1404 associated index." 1405 ::={dvbRcsOduTx 1} 1407 dvbRcsOduTxTypeEntry OBJECT-TYPE 1408 SYNTAX DvbRcsOduTxTypeEntry 1409 MAX-ACCESS not-accessible 1410 STATUS current 1411 DESCRIPTION 1412 "An entry in the BUC type table." 1413 INDEX { dvbRcsOduTxTypeIndex } 1414 ::={dvbRcsOduTxTypeTable 1} 1416 DvbRcsOduTxTypeEntry ::= SEQUENCE { 1417 dvbRcsOduTxTypeIndex Unsigned32, 1418 dvbRcsOduTxTypeDescription SnmpAdminString 1419 } 1421 dvbRcsOduTxTypeIndex OBJECT-TYPE 1422 SYNTAX Unsigned32 (1..32) 1423 MAX-ACCESS not-accessible 1424 STATUS current 1425 DESCRIPTION 1426 "Index for the BUC type." 1427 ::={dvbRcsOduTxTypeEntry 1} 1429 dvbRcsOduTxTypeDescription OBJECT-TYPE 1430 SYNTAX SnmpAdminString 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "Text based identification of a BUC type." 1435 ::={dvbRcsOduTxTypeEntry 2} 1437 dvbRcsOduTxType OBJECT-TYPE 1438 SYNTAX Unsigned32 1439 MAX-ACCESS read-write 1440 STATUS current 1441 DESCRIPTION 1442 "Index of the selected BUC type." 1443 ::={dvbRcsOduTx 2} 1445 --============================================================== 1446 -- ODU LNB 1447 --============================================================== 1449 dvbRcsOduRxTypeTable OBJECT-TYPE 1450 SYNTAX SEQUENCE OF DvbRcsOduRxTypeEntry 1451 MAX-ACCESS not-accessible 1452 STATUS current 1453 DESCRIPTION 1454 "This table contains the identification of each well- 1455 known LNB type supported by the IDU, and provides its 1456 associated index." 1457 ::={dvbRcsOduRx 1} 1459 dvbRcsOduRxTypeEntry OBJECT-TYPE 1460 SYNTAX DvbRcsOduRxTypeEntry 1461 MAX-ACCESS not-accessible 1462 STATUS current 1463 DESCRIPTION 1464 "An entry in the LNB type table." 1465 INDEX { dvbRcsOduRxTypeIndex } 1466 ::={dvbRcsOduRxTypeTable 1} 1468 DvbRcsOduRxTypeEntry ::= SEQUENCE { 1469 dvbRcsOduRxTypeIndex Unsigned32, 1470 dvbRcsOduRxTypeDescription SnmpAdminString 1471 } 1473 dvbRcsOduRxTypeIndex OBJECT-TYPE 1474 SYNTAX Unsigned32 (1..32) 1475 MAX-ACCESS not-accessible 1476 STATUS current 1477 DESCRIPTION 1478 "Index for the LNB type." 1479 ::={dvbRcsOduRxTypeEntry 1} 1481 dvbRcsOduRxTypeDescription OBJECT-TYPE 1482 SYNTAX SnmpAdminString 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "Text based identification of an LNB type." 1487 ::={dvbRcsOduRxTypeEntry 2} 1489 dvbRcsOduRxType OBJECT-TYPE 1490 SYNTAX Unsigned32 1491 MAX-ACCESS read-write 1492 STATUS current 1493 DESCRIPTION 1494 "Index of the selected LNB type." 1495 ::={dvbRcsOduRx 2} 1497 --============================================================== 1498 -- ODU Antenna 1499 --============================================================== 1501 dvbRcsOduAntennaTypeTable OBJECT-TYPE 1502 SYNTAX SEQUENCE OF DvbRcsOduAntennaTypeEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "This table contains the identification of each well- 1507 known antenna type supported by the IDU, and provides 1508 its associated index." 1509 ::={dvbRcsOduAntenna 1} 1511 dvbRcsOduAntennaTypeEntry OBJECT-TYPE 1512 SYNTAX DvbRcsOduAntennaTypeEntry 1513 MAX-ACCESS not-accessible 1514 STATUS current 1515 DESCRIPTION 1516 "An entry in the antenna type table." 1517 INDEX { dvbRcsOduAntennaTypeIndex } 1518 ::={dvbRcsOduAntennaTypeTable 1} 1520 DvbRcsOduAntennaTypeEntry ::= SEQUENCE { 1521 dvbRcsOduAntennaTypeIndex Unsigned32, 1522 dvbRcsOduAntennaTypeDescription SnmpAdminString 1523 } 1525 dvbRcsOduAntennaTypeIndex OBJECT-TYPE 1526 SYNTAX Unsigned32 (1..32) 1527 MAX-ACCESS not-accessible 1528 STATUS current 1529 DESCRIPTION 1530 "Index for the antenna type." 1531 ::={dvbRcsOduAntennaTypeEntry 1} 1532 dvbRcsOduAntennaTypeDescription OBJECT-TYPE 1533 SYNTAX SnmpAdminString 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "Text based identification of an antenna type." 1538 ::={dvbRcsOduAntennaTypeEntry 2} 1540 dvbRcsOduAntennaType OBJECT-TYPE 1541 SYNTAX Unsigned32 1542 MAX-ACCESS read-write 1543 STATUS current 1544 DESCRIPTION 1545 "Index of the selected antenna type." 1546 ::={dvbRcsOduAntenna 2} 1548 --============================================================== 1549 -- dvbRcsRcstNetwork sub-tree object types 1550 --============================================================== 1552 dvbRcsNetworkOamInetAddressType OBJECT-TYPE 1553 SYNTAX InetAddressType 1554 MAX-ACCESS read-write 1555 STATUS current 1556 DESCRIPTION 1557 "The type of internet address of 1558 dvbRcsNetworkOamInetAddress. 1559 If the terminal OAM Internet address is unassigned or 1560 unknown, then the value of this object is unknown(0)." 1561 ::= {dvbRcsRcstNetwork 1} 1563 dvbRcsNetworkOamInetAddress OBJECT-TYPE 1564 SYNTAX InetAddress 1565 MAX-ACCESS read-write 1566 STATUS current 1567 DESCRIPTION 1568 "OAM IP Address of the RCST. This object is used with 1569 both IP and interfaces MIB-II subgroups. It uniquely 1570 determines the interface through which OAM traffic 1571 passes. 1573 The OAM IP address may be statically or dynamically 1574 assigned. It is system dependent whether the OAM IP 1575 address and the Traffic IP address are the same address. 1576 If the terminal has no OAM Internet address assigned, or 1577 this Internet address is unknown, the value of this 1578 object is the zero-length OCTET STRING." 1579 ::= {dvbRcsRcstNetwork 2} 1581 dvbRcsNetworkOamInetAddressPrefixLength OBJECT-TYPE 1582 SYNTAX InetAddressPrefixLength 1583 MAX-ACCESS read-write 1584 STATUS current 1585 DESCRIPTION 1586 "Prefix length for the OAM IP Address. If this address 1587 prefix is unknown or does not apply, the value is zero." 1588 ::= {dvbRcsRcstNetwork 3} 1590 dvbRcsNetworkOamInetAddressAssign OBJECT-TYPE 1591 SYNTAX INTEGER { 1592 oamInetAddressStatic (1), 1593 oamInetAddressDynamic (2) 1594 } 1595 MAX-ACCESS read-write 1596 STATUS current 1597 DESCRIPTION 1598 "Identifies whether the OAM IP address is statically 1599 (1) or dynamically (2) assigned." 1600 ::= {dvbRcsRcstNetwork 4} 1602 dvbRcsNetworkLanInetAddressType OBJECT-TYPE 1603 SYNTAX InetAddressType 1604 MAX-ACCESS read-write 1605 STATUS current 1606 DESCRIPTION 1607 "The type of internet address of 1608 dvbRcsNetworkLanInetAddress. 1609 If the terminal Internet address on the LAN interface is 1610 unassigned or unknown, then the value of this object is 1611 unknown(0)." 1612 ::= {dvbRcsRcstNetwork 5} 1613 dvbRcsNetworkLanInetAddress OBJECT-TYPE 1614 SYNTAX InetAddress 1615 MAX-ACCESS read-write 1616 STATUS current 1617 DESCRIPTION 1618 "IP address of the LAN interface of the terminal. If the 1619 terminal has no Internet address assigned on the LAN 1620 interface, or this Internet address is unknown, the 1621 value of this object is the zero-length OCTET STRING." 1622 ::= {dvbRcsRcstNetwork 6} 1624 dvbRcsNetworkLanInetAddressPrefixLength OBJECT-TYPE 1625 SYNTAX InetAddressPrefixLength 1626 MAX-ACCESS read-write 1627 STATUS current 1628 DESCRIPTION 1629 "Prefix length for the LAN IP Address of the terminal. 1630 If this address prefix is unknown or does not apply, the 1631 value is zero." 1632 ::= {dvbRcsRcstNetwork 7} 1634 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType 1635 OBJECT-TYPE 1636 SYNTAX InetAddressType 1637 MAX-ACCESS read-write 1638 STATUS current 1639 DESCRIPTION 1640 "The type of internet address of 1641 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress. 1642 If the default gateway Internet address is unassigned or 1643 unknown, then the value of this object is unknown(0)." 1644 ::= {dvbRcsRcstNetwork 8} 1646 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress OBJECT-TYPE 1647 SYNTAX InetAddress 1648 MAX-ACCESS read-write 1649 STATUS current 1650 DESCRIPTION 1651 "IP address of the default gateway for the air 1652 interface. If the terminal has no default gateway 1653 assigned on the air interface, or this Internet address 1654 is unknown, the value of this object is the zero-length 1655 OCTET STRING." 1656 ::= {dvbRcsRcstNetwork 9} 1658 dvbRcsNetworkDnsServers OBJECT IDENTIFIER ::= {dvbRcsRcstNetwork 1659 10} 1661 dvbRcsPrimaryDnsServerInetAddressType OBJECT-TYPE 1662 SYNTAX InetAddressType 1663 MAX-ACCESS read-write 1664 STATUS current 1665 DESCRIPTION 1666 "The type of internet address of 1667 dvbRcsPrimaryDnsServerInetAddress. If the primary DNS 1668 server Internet address is unassigned or unknown, then 1669 the value of this object is unknown(0)." 1670 ::= { dvbRcsNetworkDnsServers 1} 1672 dvbRcsPrimaryDnsServerInetAddress OBJECT-TYPE 1673 SYNTAX InetAddress 1674 MAX-ACCESS read-write 1675 STATUS current 1676 DESCRIPTION 1677 "IP address of the primary DNS server in the NCC. If 1678 the terminal has no primary DNS server assigned, or this 1679 Internet address is unknown, the value of this object is 1680 the zero-length OCTET STRING." 1681 ::= {dvbRcsNetworkDnsServers 2} 1683 dvbRcsSecondaryDnsServerInetAddressType OBJECT-TYPE 1684 SYNTAX InetAddressType 1685 MAX-ACCESS read-write 1686 STATUS current 1687 DESCRIPTION 1688 "The type of internet address of 1689 dvbRcsSecondaryDnsServerInetAddress. If the secondary 1690 DNS server Internet address is unassigned or unknown, 1691 then the value of this object is unknown(0)." 1692 ::= { dvbRcsNetworkDnsServers 3} 1694 dvbRcsSecondaryDnsServerInetAddress OBJECT-TYPE 1695 SYNTAX InetAddress 1696 MAX-ACCESS read-write 1697 STATUS current 1698 DESCRIPTION 1699 "IP address of the secondary DNS server in the NCC. If 1700 the terminal has no secondary DNS server assigned, or 1701 this Internet address is unknown, the value of this 1702 object is the zero-length OCTET STRING." 1703 ::= {dvbRcsNetworkDnsServers 4} 1705 dvbRcsNetworkNccMgtInetAddressType OBJECT-TYPE 1706 SYNTAX InetAddressType 1707 MAX-ACCESS read-write 1708 STATUS current 1709 DESCRIPTION 1710 "The type of internet address of 1711 dvbRcsNetworkNccMgtInetAddress. If the management server 1712 Internet address is unassigned or unknown, then the 1713 value of this object is unknown(0)." 1714 ::= {dvbRcsRcstNetwork 11} 1716 dvbRcsNetworkNccMgtInetAddress OBJECT-TYPE 1717 SYNTAX InetAddress 1718 MAX-ACCESS read-write 1719 STATUS current 1720 DESCRIPTION 1721 "IP address of the management server in the NCC. If 1722 the terminal has no management server assigned, or this 1723 Internet address is unknown, the value of this object is 1724 the zero-length OCTET STRING." 1725 ::= {dvbRcsRcstNetwork 12} 1727 dvbRcsNetworkConfigFileDownloadUrl OBJECT-TYPE 1728 SYNTAX Uri 1729 MAX-ACCESS read-write 1730 STATUS current 1731 DESCRIPTION 1732 "Full path name for the configuration file download. 1733 It includes the protocol type (tftp or ftp) and the 1734 associated server IP address or hostname. Hostname can 1735 only be used if DNS is supported by the RCST. 1737 The format of this parameter follows RFC 3986." 1738 ::= {dvbRcsRcstNetwork 13} 1740 dvbRcsNetworkInstallLogFileDownloadUrl OBJECT-TYPE 1741 SYNTAX Uri 1742 MAX-ACCESS read-write 1743 STATUS current 1744 DESCRIPTION 1745 "Full path of the installation log file to download. 1746 It includes the protocol type (tftp or ftp) and the 1747 associated server IP address or hostname. Hostname can 1748 only be used if DNS is supported by the RCST. The 1749 installation log file can be created on the installer's 1750 computer and downloaded to the RCST. 1751 The format of this parameter follows RFC 3986." 1752 ::= {dvbRcsRcstNetwork 14} 1754 dvbRcsNetworkConfigFileUploadUrl OBJECT-TYPE 1755 SYNTAX Uri 1756 MAX-ACCESS read-write 1757 STATUS current 1758 DESCRIPTION 1759 "Full path name for the configuration file upload. 1760 It includes the protocol type (tftp or ftp) and the 1761 associated server IP address or hostname. Hostname can 1762 only be used if DNS is supported by the RCST. 1763 The format of this parameter follows RFC 3986." 1764 ::= {dvbRcsRcstNetwork 15} 1766 dvbRcsNetworkLogFileUploadUrl OBJECT-TYPE 1767 SYNTAX Uri 1768 MAX-ACCESS read-write 1769 STATUS current 1770 DESCRIPTION 1771 "Full path of the event log file. It includes the 1772 protocol type (tftp or ftp) and the associated server IP 1773 address or hostname. Hostname can only be used if DNS is 1774 supported by the RCST. 1775 The format of this parameter follows RFC 3986." 1776 ::= {dvbRcsRcstNetwork 16} 1777 dvbRcsNetworkInstallLogFileUploadUrl OBJECT-TYPE 1778 SYNTAX Uri 1779 MAX-ACCESS read-write 1780 STATUS current 1781 DESCRIPTION 1782 "Full path of the installation log file. It includes the 1783 protocol type (tftp or ftp) and the associated server 1784 IP address or hostname. Hostname can only be used if DNS 1785 is supported by the RCST. The installation log file can 1786 be retrieved from the RCST by the NCC or by the 1787 installer via the LAN. 1788 The format of this parameter follows RFC 3986." 1789 ::= {dvbRcsRcstNetwork 17} 1791 --============================================================== 1792 -- dvbRcsRcstInstall sub-tree object types 1793 --============================================================== 1794 dvbRcsInstallAntennaAlignmentState OBJECT-TYPE 1795 SYNTAX INTEGER { 1796 antennaAlignmentStart (1), 1797 antennaAlignmentDeny (2), 1798 antennaAlignmentContinue(3), 1799 antennaAlignmentStop (4), 1800 antennaAlignmentSuccess (5), 1801 antennaAlignmentFail (6) 1802 } 1803 MAX-ACCESS read-write 1804 STATUS current 1805 DESCRIPTION 1806 "Indicates the alignment state of the antenna: 1807 (1)-Start; 1808 (2)-Deny; 1809 (3)-Continue; 1810 (4)-Stop; 1811 (5)-Success; 1812 (6)-Fail" 1813 ::= {dvbRcsRcstInstall 1} 1815 dvbRcsInstallCwFrequency OBJECT-TYPE 1816 SYNTAX Unsigned32 1817 UNITS "x100 Hz" 1818 MAX-ACCESS read-write 1819 STATUS current 1820 DESCRIPTION 1821 "Frequency at which the transmitted Continuous Wave 1822 carrier (in 100 Hz). 1823 Minimum required precision is 1 kHz." 1824 ::= {dvbRcsRcstInstall 2} 1826 dvbRcsInstallCwMaxDuration OBJECT-TYPE 1827 SYNTAX Unsigned32 1828 UNITS "seconds" 1829 MAX-ACCESS read-write 1830 STATUS current 1831 DESCRIPTION 1832 "Time after which the Continuous Wave carrier must be 1833 put down (in seconds)" 1834 ::= {dvbRcsRcstInstall 3} 1836 dvbRcsInstallCwPower OBJECT-TYPE 1837 SYNTAX Integer32 1838 UNITS "x0.1 dBm" 1839 MAX-ACCESS read-write 1840 STATUS current 1841 DESCRIPTION 1842 "IDU TX output level when the IDU is configured to send 1843 CW. The resolution is 0.1 dBm and the accuracy is +/- 1 1844 dBm. Reconfiguration is applied immediately to a CW." 1845 ::= {dvbRcsRcstInstall 4} 1847 dvbRcsInstallCoPolReading OBJECT-TYPE 1848 SYNTAX Unsigned32 1849 UNITS "x0.1 dB" 1850 MAX-ACCESS read-write 1851 STATUS current 1852 DESCRIPTION 1853 "Co-Polarisation measured value during installation 1854 procedure (in 0.1 dB)" 1855 ::= {dvbRcsRcstInstall 5} 1857 dvbRcsInstallXPolReading OBJECT-TYPE 1858 SYNTAX Unsigned32 1859 UNITS "x0.1 dB" 1860 MAX-ACCESS read-write 1861 STATUS current 1862 DESCRIPTION 1863 "Cross-Polarisation measured value during installation 1864 procedure (in 0.1 dB)" 1865 ::= {dvbRcsRcstInstall 6} 1867 dvbRcsInstallCoPolTarget OBJECT-TYPE 1868 SYNTAX Unsigned32 1869 UNITS "x0.1 dB" 1870 MAX-ACCESS read-write 1871 STATUS current 1872 DESCRIPTION 1873 "Co-Polarisation target value during installation 1874 procedure (in 0.1 dB)." 1875 ::= {dvbRcsRcstInstall 7} 1877 dvbRcsInstallXPolTarget OBJECT-TYPE 1878 SYNTAX Unsigned32 1879 UNITS "x0.1 dB" 1880 MAX-ACCESS read-write 1881 STATUS current 1882 DESCRIPTION 1883 "Cross-Polarisation target value during installation 1884 procedure (in 0.1 dB)" 1885 ::= {dvbRcsRcstInstall 8} 1887 dvbRcsInstallStandByDuration OBJECT-TYPE 1888 SYNTAX Unsigned32 1889 UNITS "seconds" 1890 MAX-ACCESS read-write 1891 STATUS current 1892 DESCRIPTION 1893 "Time to wait in stand-by mode (in seconds)" 1894 ::= {dvbRcsRcstInstall 9} 1896 dvbRcsInstallTargetEsN0 OBJECT-TYPE 1897 SYNTAX Unsigned32(0..315) 1898 UNITS "x0.1 dB" 1899 MAX-ACCESS read-write 1900 STATUS current 1901 DESCRIPTION 1902 "This value describes the wanted Es/N0 value that 1903 enables operation of the return link with the required 1904 error performance. The values shall be given in tenth of 1905 dB and the initial value shall be equal to 7 dB. The 1906 range shall be from 0 dBm to 31.5 dBm with a precision 1907 of 0.1 dB." 1908 DEFVAL { 70 } 1909 ::= {dvbRcsRcstInstall 10} 1911 --============================================================== 1912 -- dvbRcsRcstQos sub-tree object types 1913 --============================================================== 1914 dvbRcsPktClassTable OBJECT-TYPE 1915 SYNTAX SEQUENCE OF DvbRcsPktClassEntry 1916 MAX-ACCESS not-accessible 1917 STATUS current 1918 DESCRIPTION 1919 "This table describes the packet classification used in 1920 the DVB-RCS terminal. The number of entries is specified 1921 by dvbRcsPktClassIndex. " 1922 ::={dvbRcsRcstQos 1} 1924 dvbRcsPktClassEntry OBJECT-TYPE 1925 SYNTAX DvbRcsPktClassEntry 1926 MAX-ACCESS not-accessible 1927 STATUS current 1928 DESCRIPTION 1929 "An entry in the packet classification table. One object 1930 type of each entry may have a value in the active range 1931 (a non-default value).The other object types are then 1932 assumed set to 'inactive'. The entry with the lowest 1933 index value takes precedence when classifying a packet." 1934 INDEX { dvbRcsPktClassIndex } 1935 ::= {dvbRcsPktClassTable 1} 1937 DvbRcsPktClassEntry ::= SEQUENCE { 1938 dvbRcsPktClassIndex Unsigned32, 1939 dvbRcsPktClassDscpLow Unsigned32, 1940 dvbRcsPktClassDscpHigh Unsigned32, 1941 dvbRcsPktClassDscpMarkValue Integer32, 1942 dvbRcsPktClassIpProtocol Unsigned32, 1943 dvbRcsPktClassSrcInetAddressType InetAddressType, 1944 dvbRcsPktClassSrcInetAddress InetAddress, 1945 dvbRcsPktClassSrcInetAddressPrefixLength 1946 InetAddressPrefixLength, 1947 dvbRcsPktClassDstInetAddressType InetAddressType, 1948 dvbRcsPktClassDstInetAddress InetAddress, 1949 dvbRcsPktClassDstInetAddressPrefixLength 1950 InetAddressPrefixLength, 1951 dvbRcsPktClassSrcPortLow InetPortNumber, 1952 dvbRcsPktClassSrcPortHigh InetPortNumber, 1953 dvbRcsPktClassDstPortLow InetPortNumber, 1954 dvbRcsPktClassDstPortHigh InetPortNumber, 1955 dvbRcsPktClassVlanUserPri Integer32, 1956 dvbRcsPktClassPhbAssociation Unsigned32, 1957 dvbRcsPktClassRowStatus RowStatus 1958 } 1960 dvbRcsPktClassIndex OBJECT-TYPE 1961 SYNTAX Unsigned32 (1..64) 1962 MAX-ACCESS not-accessible 1963 STATUS current 1964 DESCRIPTION 1965 "Index automatically incremented by one at row 1966 creation." 1967 ::={dvbRcsPktClassEntry 1} 1969 dvbRcsPktClassDscpLow OBJECT-TYPE 1970 SYNTAX Unsigned32 (0..63) 1971 MAX-ACCESS read-create 1972 STATUS current 1973 DESCRIPTION 1974 "This object specifies the low value of a range of 1975 DiffServ Code Point (DSCP) values to which a packet is 1976 compared. A value of 0 is used to inactivate." 1977 DEFVAL { 0 } 1978 ::={dvbRcsPktClassEntry 2} 1980 dvbRcsPktClassDscpHigh OBJECT-TYPE 1981 SYNTAX Unsigned32 (0..63) 1982 MAX-ACCESS read-create 1983 STATUS current 1984 DESCRIPTION 1985 "This object specifies the high value of a range of 1986 DiffServ Code Point (DSCP) values to which a packet is 1987 compared. A value of 63 is used to inactivate." 1988 DEFVAL { 63 } 1989 ::={dvbRcsPktClassEntry 3} 1991 dvbRcsPktClassDscpMarkValue OBJECT-TYPE 1992 SYNTAX Integer32 (-1..63) 1993 MAX-ACCESS read-create 1994 STATUS current 1995 DESCRIPTION 1996 "This object is the DiffServ Code Point (DSCP) value 1997 used to mark the packet, -1 indicates no DSCP marking. 1998 Possible DSCP marks values are (0..63)" 1999 DEFVAL { -1 } 2000 ::={dvbRcsPktClassEntry 4} 2002 dvbRcsPktClassIpProtocol OBJECT-TYPE 2003 SYNTAX Unsigned32 (0..255) 2004 MAX-ACCESS read-create 2005 STATUS current 2006 DESCRIPTION 2007 "This object specifies the IP protocol to which a 2008 packet is compared. A value of 255 means match all." 2009 DEFVAL { 255 } 2010 ::={dvbRcsPktClassEntry 5} 2012 dvbRcsPktClassSrcInetAddressType OBJECT-TYPE 2013 SYNTAX InetAddressType 2014 MAX-ACCESS read-write 2015 STATUS current 2016 DESCRIPTION 2017 "The type of internet address of 2018 dvbRcsPktClassSrcInetAddress. If the packet class source 2019 Internet address is unassigned or unknown, then the 2020 value of this object is unknown(0)." 2021 ::= { dvbRcsPktClassEntry 6} 2022 dvbRcsPktClassSrcInetAddress OBJECT-TYPE 2023 SYNTAX InetAddress 2024 MAX-ACCESS read-create 2025 STATUS current 2026 DESCRIPTION 2027 "This object specifies the IP source address to which a 2028 packet is compared. If the packet class has no source 2029 Internet address assigned, or this Internet address is 2030 unknown, the value of this object is the zero-length 2031 OCTET STRING." 2032 ::={dvbRcsPktClassEntry 7} 2034 dvbRcsPktClassSrcInetAddressPrefixLength OBJECT-TYPE 2035 SYNTAX InetAddressPrefixLength 2036 MAX-ACCESS read-create 2037 STATUS current 2038 DESCRIPTION 2039 "Prefix length of the IP source address that will be 2040 matched for this packet class. A value of zero indicates 2041 that the selectivity is inactive." 2042 DEFVAL { 0 } 2043 ::={dvbRcsPktClassEntry 8} 2045 dvbRcsPktClassDstInetAddressType OBJECT-TYPE 2046 SYNTAX InetAddressType 2047 MAX-ACCESS read-write 2048 STATUS current 2049 DESCRIPTION 2050 "The type of internet address of 2051 dvbRcsPktClassDstInetAddress. If the packet class 2052 destination Internet address is unassigned or unknown, 2053 then the value of this object is unknown(0)." 2054 ::= { dvbRcsPktClassEntry 9} 2056 dvbRcsPktClassDstInetAddress OBJECT-TYPE 2057 SYNTAX InetAddress 2058 MAX-ACCESS read-create 2059 STATUS current 2060 DESCRIPTION 2061 "This object specifies the IP destination address to 2062 which a packet is compared. If the packet class has no 2063 destination Internet address assigned, or this Internet 2064 address is unknown, the value of this object is the 2065 zero-length OCTET STRING." 2066 ::={dvbRcsPktClassEntry 10} 2068 dvbRcsPktClassDstInetAddressPrefixLength OBJECT-TYPE 2069 SYNTAX InetAddressPrefixLength 2070 MAX-ACCESS read-create 2071 STATUS current 2072 DESCRIPTION 2073 "Prefix length of the IP source address that will be 2074 matched for this packet class. A value of zero indicates 2075 that the selectivity is inactive." 2076 DEFVAL { 0 } 2077 ::={dvbRcsPktClassEntry 11} 2079 dvbRcsPktClassSrcPortLow OBJECT-TYPE 2080 SYNTAX InetPortNumber 2081 MAX-ACCESS read-create 2082 STATUS current 2083 DESCRIPTION 2084 "This object specifies the low range of the source 2085 port to which a packet is compared. A value of 0 2086 indicates that the selectivity is inactive." 2087 DEFVAL { 0 } 2088 ::={dvbRcsPktClassEntry 12} 2090 dvbRcsPktClassSrcPortHigh OBJECT-TYPE 2091 SYNTAX InetPortNumber 2092 MAX-ACCESS read-create 2093 STATUS current 2094 DESCRIPTION 2095 "This object specifies the high range of the source port 2096 to which a packet is compared. A value of 0 indicates 2097 that the selectivity is inactive." 2098 DEFVAL { 65535 } 2099 ::={dvbRcsPktClassEntry 13} 2101 dvbRcsPktClassDstPortLow OBJECT-TYPE 2102 SYNTAX InetPortNumber 2103 MAX-ACCESS read-create 2104 STATUS current 2105 DESCRIPTION 2106 "This object specifies the low range of the destination 2107 port to which a packet is compared. A value of 0 2108 indicates that the selectivity is inactive." 2109 DEFVAL { 0 } 2110 ::={dvbRcsPktClassEntry 14} 2112 dvbRcsPktClassDstPortHigh OBJECT-TYPE 2113 SYNTAX InetPortNumber 2114 MAX-ACCESS read-create 2115 STATUS current 2116 DESCRIPTION 2117 "This object specifies the high range of the destination 2118 port to which a packet is compared. A value of 0 2119 indicates that the selectivity is inactive." 2120 DEFVAL { 65535 } 2121 ::={dvbRcsPktClassEntry 15} 2123 dvbRcsPktClassVlanUserPri OBJECT-TYPE 2124 SYNTAX Integer32 (-1..7) 2125 MAX-ACCESS read-create 2126 STATUS current 2127 DESCRIPTION 2128 "This object specifies the VLAN User Priority to which a 2129 packet is compared. A value of -1 indicates that the 2130 selectivity is inactive." 2131 DEFVAL { -1 } 2132 ::={dvbRcsPktClassEntry 16} 2134 dvbRcsPktClassPhbAssociation OBJECT-TYPE 2135 SYNTAX Unsigned32 (0..63) 2136 MAX-ACCESS read-create 2137 STATUS current 2138 DESCRIPTION 2139 "Associate the filter entry to a specific PHB (refer to 2140 dvbRcsPhbIdentifier)." 2141 ::={dvbRcsPktClassEntry 17} 2142 dvbRcsPktClassRowStatus OBJECT-TYPE 2143 SYNTAX RowStatus 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "The status of this conceptual row. All writable objects 2148 in this row may be modified at any time." 2149 ::={dvbRcsPktClassEntry 18} 2151 --============================================================== 2152 -- dvbRcsPhbMappingTable 2153 --============================================================== 2154 dvbRcsPhbMappingTable OBJECT-TYPE 2155 SYNTAX SEQUENCE OF DvbRcsPhbMappingEntry 2156 MAX-ACCESS not-accessible 2157 STATUS current 2158 DESCRIPTION 2159 "This table is a list of Per-Hop Behaviour (PHB) MIB 2160 entries. 2161 It describes the PHB mapping to the Request Class." 2162 ::={dvbRcsRcstQos 2} 2164 dvbRcsPhbMappingEntry OBJECT-TYPE 2165 SYNTAX DvbRcsPhbMappingEntry 2166 MAX-ACCESS not-accessible 2167 STATUS current 2168 DESCRIPTION 2169 "An entry in the PHB mapping table." 2170 INDEX {dvbRcsPhbIdentifier} 2171 ::= {dvbRcsPhbMappingTable 1} 2173 DvbRcsPhbMappingEntry ::= SEQUENCE { 2174 dvbRcsPhbIdentifier Unsigned32, 2175 dvbRcsPhbName 2176 SnmpAdminString, 2177 dvbRcsPhbRequestClassAssociation Unsigned32, 2178 dvbRcsPhbMappingRowStatus RowStatus 2179 } 2181 dvbRcsPhbIdentifier OBJECT-TYPE 2182 SYNTAX Unsigned32 (1..64) 2183 MAX-ACCESS not-accessible 2184 STATUS current 2185 DESCRIPTION 2186 "Identification of the Per-Hop Behaviour (PHB) (1..64)." 2187 ::={dvbRcsPhbMappingEntry 1} 2189 dvbRcsPhbName OBJECT-TYPE 2190 SYNTAX SnmpAdminString 2191 MAX-ACCESS read-create 2192 STATUS current 2193 DESCRIPTION 2194 "The name of the Per-Hop Behaviour (PHB)." 2195 ::={dvbRcsPhbMappingEntry 2} 2197 dvbRcsPhbRequestClassAssociation OBJECT-TYPE 2198 SYNTAX Unsigned32 (1..16) 2199 MAX-ACCESS read-create 2200 STATUS current 2201 DESCRIPTION 2202 "This object is an association of this Per-Hop Behaviour 2203 (PHB) to a Request class (by reference to a Request 2204 Class index)." 2205 ::={dvbRcsPhbMappingEntry 3} 2207 dvbRcsPhbMappingRowStatus OBJECT-TYPE 2208 SYNTAX RowStatus 2209 MAX-ACCESS read-create 2210 STATUS current 2211 DESCRIPTION 2212 "The status of this conceptual row. All writable 2213 objects in this row may be modified at any time." 2214 DEFVAL { active } 2215 ::={dvbRcsPhbMappingEntry 4} 2217 --============================================================== 2218 -- dvbRcsRequestClassTable 2219 --============================================================== 2220 dvbRcsRequestClassTable OBJECT-TYPE 2221 SYNTAX SEQUENCE OF DvbRcsRequestClassEntry 2222 MAX-ACCESS not-accessible 2223 STATUS current 2224 DESCRIPTION 2225 "This table is a list of Request class entries. This 2226 class describes the layer 2 QoS objects." 2227 ::={dvbRcsRcstQos 3} 2229 dvbRcsRequestClassEntry OBJECT-TYPE 2230 SYNTAX DvbRcsRequestClassEntry 2231 MAX-ACCESS not-accessible 2232 STATUS current 2233 DESCRIPTION 2234 "An entry in the Request Class table." 2235 INDEX {dvbRcsRequestClassIndex} 2236 ::= {dvbRcsRequestClassTable 1} 2238 DvbRcsRequestClassEntry ::= SEQUENCE { 2239 dvbRcsRequestClassIndex Unsigned32, 2240 dvbRcsRequestClassName 2241 SnmpAdminString, 2242 dvbRcsRequestClassChanId Unsigned32, 2243 dvbRcsRequestClassVccVpi Unsigned32, 2244 dvbRcsRequestClassVccVci Unsigned32, 2245 dvbRcsRequestClassPidPoolReference Unsigned32, 2246 dvbRcsRequestClassCra Unsigned32, 2247 dvbRcsRequestClassRbdcMax Unsigned32, 2248 dvbRcsRequestClassRbdcTimeout Unsigned32, 2249 dvbRcsRequestClassVbdcMax Unsigned32, 2250 dvbRcsRequestClassVbdcTimeout Unsigned32, 2251 dvbRcsRequestClassVbdcMaxBackLog Unsigned32, 2252 dvbRcsRequestClassRowStatus RowStatus 2253 } 2255 dvbRcsRequestClassIndex OBJECT-TYPE 2256 SYNTAX Unsigned32 (1..16) 2257 MAX-ACCESS not-accessible 2258 STATUS current 2259 DESCRIPTION 2260 "Index of the Request Class table. A total of 16 entries 2261 are supported." 2262 ::={dvbRcsRequestClassEntry 1} 2263 dvbRcsRequestClassName OBJECT-TYPE 2264 SYNTAX SnmpAdminString 2265 MAX-ACCESS read-create 2266 STATUS current 2267 DESCRIPTION 2268 "Name of the Request Class." 2269 ::={dvbRcsRequestClassEntry 2} 2271 dvbRcsRequestClassChanId OBJECT-TYPE 2272 SYNTAX Unsigned32 (0..15) 2273 MAX-ACCESS read-create 2274 STATUS current 2275 DESCRIPTION 2276 "Channel id of the Request Class." 2277 ::={dvbRcsRequestClassEntry 3} 2279 dvbRcsRequestClassVccVpi OBJECT-TYPE 2280 SYNTAX Unsigned32 (0..255) 2281 MAX-ACCESS read-create 2282 STATUS current 2283 DESCRIPTION 2284 "Defines VPI used for the Request Class (ATM profile)." 2285 ::={dvbRcsRequestClassEntry 4} 2287 dvbRcsRequestClassVccVci OBJECT-TYPE 2288 SYNTAX Unsigned32 (0..65535) 2289 MAX-ACCESS read-create 2290 STATUS current 2291 DESCRIPTION 2292 "Defines VCI used for the Request Class (ATM profile)." 2293 ::={dvbRcsRequestClassEntry 5} 2295 dvbRcsRequestClassPidPoolReference OBJECT-TYPE 2296 SYNTAX Unsigned32 (1..16) 2297 MAX-ACCESS read-create 2298 STATUS current 2299 DESCRIPTION 2300 "Reference to the Packet IDentifier (PID) pool 2301 applicable for the Request Class." 2302 ::={dvbRcsRequestClassEntry 6} 2303 dvbRcsRequestClassCra OBJECT-TYPE 2304 SYNTAX Unsigned32 2305 UNITS "bits/s" 2306 MAX-ACCESS read-create 2307 STATUS current 2308 DESCRIPTION 2309 "Define Continuous Rate Assignment (CRA) level for the 2310 Request Class in bit per second (bits/s)." 2311 ::={dvbRcsRequestClassEntry 7} 2313 dvbRcsRequestClassRbdcMax OBJECT-TYPE 2314 SYNTAX Unsigned32 2315 UNITS "x2 kbits/s" 2316 MAX-ACCESS read-create 2317 STATUS current 2318 DESCRIPTION 2319 "Maximum Rate-Based Dynamic Capacity (RBDC) that can be 2320 requested for the Request Class, in number of 2 kbits/s" 2321 ::={dvbRcsRequestClassEntry 8} 2323 dvbRcsRequestClassRbdcTimeout OBJECT-TYPE 2324 SYNTAX Unsigned32 2325 UNITS "superframes" 2326 MAX-ACCESS read-create 2327 STATUS current 2328 DESCRIPTION 2329 "Persistence of the Rate-Based Dynamic Capacity (RBDC) 2330 request, expressed in superframes" 2331 ::={dvbRcsRequestClassEntry 9} 2333 dvbRcsRequestClassVbdcMax OBJECT-TYPE 2334 SYNTAX Unsigned32 2335 UNITS "ATM cells/MPEG packets" 2336 MAX-ACCESS read-create 2337 STATUS current 2338 DESCRIPTION 2339 "Maximum Volume-Based Dynamic Capacity (VBDC) that can 2340 be allocated to the Request Class, in payload units (one 2341 ATM cell or one MPEG packet) per superframe" 2342 ::={dvbRcsRequestClassEntry 10} 2343 dvbRcsRequestClassVbdcTimeout OBJECT-TYPE 2344 SYNTAX Unsigned32 2345 UNITS "superframes" 2346 MAX-ACCESS read-create 2347 STATUS current 2348 DESCRIPTION 2349 "Time after which the RCST considers that the pending 2350 requests are lost. The RCST may issue new requests for 2351 that traffic. Volume-Based Dynamic Capacity (VBDC) 2352 Timeout is expressed in superframes." 2353 ::={dvbRcsRequestClassEntry 11} 2355 dvbRcsRequestClassVbdcMaxBackLog OBJECT-TYPE 2356 SYNTAX Unsigned32 2357 UNITS "bytes" 2358 MAX-ACCESS read-create 2359 STATUS current 2360 DESCRIPTION 2361 "Volume-Based Dynamic Capacity (VBDC) back log per 2362 Request Class (expressed in bytes)" 2363 ::={dvbRcsRequestClassEntry 12} 2365 dvbRcsRequestClassRowStatus OBJECT-TYPE 2366 SYNTAX RowStatus 2367 MAX-ACCESS read-create 2368 STATUS current 2369 DESCRIPTION 2370 "The status of this conceptual row. It is not possible 2371 to change values in a row of this table while the row is 2372 active." 2373 ::={dvbRcsRequestClassEntry 13} 2375 --============================================================== 2376 -- The table of PID pools 2377 --============================================================== 2379 dvbRcsPidPoolTable OBJECT-TYPE 2380 SYNTAX SEQUENCE OF DvbRcsPidPoolEntry 2381 MAX-ACCESS not-accessible 2382 STATUS current 2383 DESCRIPTION 2384 "This table contains the Packet IDentifier (PID) pools. 2385 For MPEG profile several Request Classes may be mapped 2386 within a pool of several PIDs to allow Section Packing 2387 across Several Request Classes. 2388 A PID value may occur in more than one PID pool. Each 2389 PID value can effectively occur only once in each pool." 2390 ::={dvbRcsRcstQos 4} 2392 dvbRcsPidPoolEntry OBJECT-TYPE 2393 SYNTAX DvbRcsPidPoolEntry 2394 MAX-ACCESS not-accessible 2395 STATUS current 2396 DESCRIPTION 2397 "An entry in the PID pool table." 2398 INDEX { dvbRcsPidPoolIndex, dvbRcsPidIndex } 2399 ::= {dvbRcsPidPoolTable 1} 2401 DvbRcsPidPoolEntry ::= SEQUENCE { 2402 dvbRcsPidPoolIndex Unsigned32, 2403 dvbRcsPidIndex Unsigned32, 2404 dvbRcsPidValue Unsigned32, 2405 dvbRcsPidPoolRowStatus RowStatus 2406 } 2408 dvbRcsPidPoolIndex OBJECT-TYPE 2409 SYNTAX Unsigned32 (1..16) 2410 MAX-ACCESS not-accessible 2411 STATUS current 2412 DESCRIPTION 2413 "Index of the PID pool in the PID pool table." 2414 ::={dvbRcsPidPoolEntry 1} 2416 dvbRcsPidIndex OBJECT-TYPE 2417 SYNTAX Unsigned32 (1..16) 2418 MAX-ACCESS not-accessible 2419 STATUS current 2420 DESCRIPTION 2421 "Index of the PID entry within the PID pool." 2422 ::={dvbRcsPidPoolEntry 2} 2423 dvbRcsPidValue OBJECT-TYPE 2424 SYNTAX Unsigned32 (0..8191) 2425 MAX-ACCESS read-create 2426 STATUS current 2427 DESCRIPTION 2428 "Defines one of the PIDs to be used in a PID pool of 2429 dvbRcsPidPoolIndex. 2430 A PID value may occur in more than one PID pool. Each 2431 PID value can effectively occur only once in each pool." 2432 ::={dvbRcsPidPoolEntry 3} 2434 dvbRcsPidPoolRowStatus OBJECT-TYPE 2435 SYNTAX RowStatus 2436 MAX-ACCESS read-create 2437 STATUS current 2438 DESCRIPTION 2439 "The status of this conceptual row. All writable 2440 objects in this row may be modified at any time." 2441 DEFVAL { active } 2442 ::={dvbRcsPidPoolEntry 4} 2444 dvbRcsQosGlobalRbdcMax OBJECT-TYPE 2445 SYNTAX Unsigned32 2446 UNITS "x2 kbits/s" 2447 MAX-ACCESS read-write 2448 STATUS current 2449 DESCRIPTION 2450 "Global maximum RBDC that can be requested for the RCST, 2451 in number of 2 kbits/s." 2452 ::={dvbRcsRcstQos 5} 2454 dvbRcsQosGlobalVbdcMax OBJECT-TYPE 2455 SYNTAX Unsigned32 2456 UNITS "ATM cells/MPEG packets" 2457 MAX-ACCESS read-write 2458 STATUS current 2459 DESCRIPTION 2460 "Global maximum VBDC that can be allocated to the RCST, 2461 in payload units (one ATM cell or one MPEG packet) per 2462 superframe." 2463 ::={dvbRcsRcstQos 6} 2464 dvbRcsQosGlobalVbdcMaxBackLog OBJECT-TYPE 2465 SYNTAX Unsigned32 2466 UNITS "bytes" 2467 MAX-ACCESS read-write 2468 STATUS current 2469 DESCRIPTION 2470 "Global VBDC back log at RCST level (expressed in 2471 bytes). It is used only if the VBDC back log is not 2472 configured in the Request class (expressed in bytes)." 2473 ::={dvbRcsRcstQos 7} 2475 dvbRcsQosChannelIdStrictDispatching OBJECT-TYPE 2476 SYNTAX INTEGER { 2477 notStrict (0), 2478 strict (1) 2479 } 2480 MAX-ACCESS read-write 2481 STATUS current 2482 DESCRIPTION 2483 "Indicates whether the RCST will strictly follow RC 2484 association when signaled through Channel_ID in the 2485 TBTP: 2486 (0)- no strict association 2487 (1)- strict association" 2488 ::={dvbRcsRcstQos 8} 2490 --============================================================== 2491 -- dvbRcsRcstControl sub-tree object types 2492 --============================================================== 2493 dvbRcsCtrlRebootCommand OBJECT-TYPE 2494 SYNTAX INTEGER { 2495 idle (1), 2496 normal (2), 2497 alternate (3) 2498 } 2499 MAX-ACCESS read-write 2500 STATUS current 2501 DESCRIPTION 2502 "This variable shall force the RCST to reboot 2503 (1)- idle 2504 (2)- normal reboot (from current software load) 2505 (3)- reboot from alternate load (swap to alternate 2506 load before reboot)" 2507 DEFVAL {idle} 2508 ::={dvbRcsRcstControl 1} 2510 dvbRcsCtrlRcstTxDisable OBJECT-TYPE 2511 SYNTAX INTEGER { 2512 idle (1), 2513 disable (2) 2514 } 2515 MAX-ACCESS read-write 2516 STATUS current 2517 DESCRIPTION 2518 "This variable shall force the RCST to stop transmission 2519 (transmit disabled as defined in SatLabs System 2520 Recommendations): 2521 (1)- idle 2522 (2)- initiate Tx Disabled" 2523 DEFVAL {idle} 2524 ::={dvbRcsRcstControl 2} 2526 dvbRcsCtrlUserTrafficDisable OBJECT-TYPE 2527 SYNTAX INTEGER { 2528 idle (1), 2529 disable (2) 2530 } 2531 MAX-ACCESS read-write 2532 STATUS current 2533 DESCRIPTION 2534 "This variable shall disable user traffic (only RCST 2535 management traffic can be transmitted) 2536 (1)- idle 2537 (2)- disable user traffic" 2538 DEFVAL {idle} 2539 ::={dvbRcsRcstControl 3} 2541 dvbRcsCtrlCwEnable OBJECT-TYPE 2542 SYNTAX INTEGER { 2543 off (1), 2544 on (2) 2546 } 2547 MAX-ACCESS read-write 2548 STATUS current 2549 DESCRIPTION 2550 "This variable will force the RCST to start transmission 2551 of CW, if the RCST is first set to the installation 2552 state, and is properly configured for CW transmission: 2553 (1)- off 2554 (2)- on" 2555 DEFVAL {off} 2556 ::={dvbRcsRcstControl 4} 2558 dvbRcsCtrlOduTxReferenceEnable OBJECT-TYPE 2559 SYNTAX INTEGER { 2560 off (1), 2561 on (2) 2562 } 2563 MAX-ACCESS read-write 2564 STATUS current 2565 DESCRIPTION 2566 "Enables activation and deactivation of 10 MHz reference 2567 clock in the Tx IFL cable: 2568 (1) off 2569 (2) on" 2570 DEFVAL {on} 2571 ::={dvbRcsRcstControl 5} 2573 dvbRcsCtrlOduTxDCEnable OBJECT-TYPE 2574 SYNTAX INTEGER { 2575 off (1), 2576 on (2) 2577 } 2578 MAX-ACCESS read-write 2579 STATUS current 2580 DESCRIPTION 2581 "Enables activation and deactivation of DC in the Tx IFL 2582 cable: 2583 (1) off 2584 (2) on" 2585 DEFVAL {on} 2586 ::={dvbRcsRcstControl 6} 2587 dvbRcsCtrlOduRxDCEnable OBJECT-TYPE 2588 SYNTAX INTEGER { 2589 off (1), 2590 on (2) 2591 } 2592 MAX-ACCESS read-write 2593 STATUS current 2594 DESCRIPTION 2595 "Enables activation and deactivation of DC in the Rx IFL 2596 cable: 2597 (1) off 2598 (2) on" 2599 DEFVAL {on} 2600 ::={dvbRcsRcstControl 7} 2602 dvbRcsCtrlDownloadFileCommand OBJECT-TYPE 2603 SYNTAX INTEGER { 2604 idle (1), 2605 config (2), 2606 installationLog (3) 2607 } 2608 MAX-ACCESS read-write 2609 STATUS current 2610 DESCRIPTION 2611 "This variable will initiate a RCST configuration file 2612 download process 2613 (1) idle 2614 (2) download RCST configuration file from TFTP/FTP 2615 server 2616 (3) download RCST installation log file from TFTP/FTP 2617 server (INSTALL_LOG Option)" 2618 DEFVAL {idle} 2619 ::={dvbRcsRcstControl 8} 2621 dvbRcsCtrlUploadFileCommand OBJECT-TYPE 2622 SYNTAX INTEGER { 2623 idle (1), 2624 config (2), 2625 eventAlarm (3), 2626 installationLog (4) 2628 } 2629 MAX-ACCESS read-write 2630 STATUS current 2631 DESCRIPTION 2632 "This variable will initiate a RCST upload process 2633 (1) idle 2634 (2) upload RCST configuration file to TFTP/FTP server 2635 (3) upload RCST event/alarm log file to TFTP/FTP server 2636 (4) upload RCST installation log file to TFTP/FTP server 2637 (INSTALL_LOG Option)" 2638 DEFVAL {idle} 2639 ::={dvbRcsRcstControl 9} 2641 dvbRcsCtrlActivateConfigFileCommand OBJECT-TYPE 2642 SYNTAX INTEGER { 2643 idle (1), 2644 activate (2) 2645 } 2646 MAX-ACCESS read-write 2647 STATUS current 2648 DESCRIPTION 2649 "Triggers the RCST to use the configuration file and 2650 update its parameters accordingly. Some RCST 2651 implementations may require a reboot for the parameters 2652 to take effect (vendor specific). 2653 (1) Idle 2654 (2) activate" 2655 DEFVAL {idle} 2656 ::={dvbRcsRcstControl 10} 2658 dvbRcsCtrlRcstLogonCommand OBJECT-TYPE 2659 SYNTAX INTEGER { 2660 idle (1), 2661 logon (2) 2662 } 2663 MAX-ACCESS read-write 2664 STATUS current 2665 DESCRIPTION 2666 "This variable will initiate a RCST logon 2667 (1) idle 2668 (2) initiate RCST logon" 2670 DEFVAL {idle} 2671 ::={dvbRcsRcstControl 11} 2673 dvbRcsCtrlRcstLogoffCommand OBJECT-TYPE 2674 SYNTAX INTEGER { 2675 idle (1), 2676 logoff (2) 2677 } 2678 MAX-ACCESS read-write 2679 STATUS current 2680 DESCRIPTION 2681 "This variable will initiate a RCST logoff 2682 (1) idle 2683 (2) initiate RCST logoff" 2684 DEFVAL {idle} 2685 ::={dvbRcsRcstControl 12} 2687 dvbRcsCtrlRcstRxReacquire OBJECT-TYPE 2688 SYNTAX INTEGER { 2689 idle (1), 2690 reacquireForwardLink (2) 2691 } 2692 MAX-ACCESS read-write 2693 STATUS current 2694 DESCRIPTION 2695 "This variable will force the RCST to acquire the 2696 forward link and start receiving." 2697 DEFVAL {idle} 2698 ::={dvbRcsRcstControl 13} 2700 --============================================================== 2701 -- dvbRcsRcstState sub-tree object types 2702 --============================================================== 2703 dvbRcsRcstMode OBJECT-TYPE 2704 SYNTAX INTEGER { 2705 installation (0), 2706 operational (1) 2707 } 2708 MAX-ACCESS read-write 2709 STATUS current 2710 DESCRIPTION 2711 "Identifies the current mode of the RCST is and allows it 2712 to return to the installation mode when needed. Values for 2713 the RCST mode are: 2714 Installation (0) 2715 Operational (1)" 2716 ::={dvbRcsRcstState 1} 2718 dvbRcsRcstFaultStatus OBJECT-TYPE 2719 SYNTAX INTEGER { 2720 nofault (0), 2721 fault (1) 2722 } 2723 MAX-ACCESS read-only 2724 STATUS current 2725 DESCRIPTION 2726 "Provide the fault status of the terminal. The fault 2727 status management is vendor specific. Values for the 2728 Fault Status are: 2729 no fault (0) 2730 fault (1)" 2731 ::={dvbRcsRcstState 2} 2733 dvbRcsRcstFwdLinkStatus OBJECT-TYPE 2734 SYNTAX INTEGER { 2735 notAcquired (0), 2736 acquired (1) 2737 } 2738 MAX-ACCESS read-only 2739 STATUS current 2740 DESCRIPTION 2741 "Provides the status of the RCST Forward Link. Values 2742 for the Forward Link Status are: 2743 Not acquired (0) 2744 Acquired (1)" 2745 ::={dvbRcsRcstState 3} 2747 dvbRcsRcstRtnLinkStatus OBJECT-TYPE 2748 SYNTAX INTEGER { 2749 loggedOff (0), 2750 loggedOn (1) 2751 } 2752 MAX-ACCESS read-only 2753 STATUS current 2754 DESCRIPTION 2755 "Provides the status of the RCST Return Link. Values for 2756 the Return Link Status are: 2757 Logged-off (0) 2758 Logged-on (1)" 2759 ::={dvbRcsRcstState 4} 2761 dvbRcsRcstLogUpdated OBJECT-TYPE 2762 SYNTAX INTEGER { 2763 noUpdate (0), 2764 logfileUpdated (1) 2765 } 2766 MAX-ACCESS read-only 2767 STATUS current 2768 DESCRIPTION 2769 "Indicates the existence of an updated event log file: 2770 No update (0) 2771 Event Log file updated (1) 2772 The RCST should remove the Event Log file updated 2773 indication as the log file is fetched by the NCC." 2774 ::={dvbRcsRcstState 5} 2776 dvbRcsRcstCurrentSoftwareVersion OBJECT-TYPE 2777 SYNTAX SnmpAdminString 2778 MAX-ACCESS read-only 2779 STATUS current 2780 DESCRIPTION 2781 "Current RCST software version." 2782 ::={dvbRcsRcstState 6} 2784 dvbRcsRcstAlternateSoftwareVersion OBJECT-TYPE 2785 SYNTAX SnmpAdminString 2786 MAX-ACCESS read-only 2787 STATUS current 2788 DESCRIPTION 2789 "Alternate (backup/new) RCST software version." 2790 ::={dvbRcsRcstState 7} 2792 dvbRcsRcstActivatedConfigFileVersion OBJECT-TYPE 2793 SYNTAX SnmpAdminString 2794 MAX-ACCESS read-only 2795 STATUS current 2796 DESCRIPTION 2797 "Version of the most recently activated configuration 2798 file. 2799 The version is vendor specific." 2800 ::={dvbRcsRcstState 8} 2802 dvbRcsRcstDownloadedConfigFileVersion OBJECT-TYPE 2803 SYNTAX SnmpAdminString 2804 MAX-ACCESS read-only 2805 STATUS current 2806 DESCRIPTION 2807 "Version of the most recently downloaded configuration 2808 file. 2809 Version is vendor specific. If the value is different 2810 from dvbRcsRcstActivatedConfigFileVersion, it is pending 2811 for activation." 2812 ::={dvbRcsRcstState 9} 2814 --============================================================== 2815 -- dvbRcsFwdConfig sub-tree object types 2816 --============================================================== 2817 dvbRcsFwdStartTable OBJECT-TYPE 2818 SYNTAX SEQUENCE OF DvbRcsFwdStartEntry 2819 MAX-ACCESS not-accessible 2820 STATUS current 2821 DESCRIPTION 2822 "Lists Forward Links attachment points (e.g. different 2823 for installation and operation). 2824 The table describes the forward link parameters used for 2825 the start-up stream with the NCC." 2826 ::={dvbRcsFwdConfig 1} 2828 dvbRcsFwdStartEntry OBJECT-TYPE 2829 SYNTAX DvbRcsFwdStartEntry 2830 MAX-ACCESS not-accessible 2831 STATUS current 2832 DESCRIPTION 2833 "An entry in the Forward Link StartConfig table." 2835 INDEX {dvbRcsFwdStartIndex} 2836 ::= {dvbRcsFwdStartTable 1} 2838 DvbRcsFwdStartEntry ::= SEQUENCE { 2839 dvbRcsFwdStartIndex Unsigned32, 2840 dvbRcsFwdStartPopId Integer32, 2841 dvbRcsFwdStartFrequency Unsigned32, 2842 dvbRcsFwdStartPolar INTEGER, 2843 dvbRcsFwdStartFormat INTEGER, 2844 dvbRcsFwdStartRolloff INTEGER, 2845 dvbRcsFwdStartSymbolRate Unsigned32, 2846 dvbRcsFwdStartInnerFec INTEGER, 2847 dvbRcsFwdStartRowStatus RowStatus 2848 } 2850 dvbRcsFwdStartIndex OBJECT-TYPE 2851 SYNTAX Unsigned32 (1..8) 2852 MAX-ACCESS not-accessible 2853 STATUS current 2854 DESCRIPTION 2855 "Index of the Forward Link StartConfig table." 2856 ::={dvbRcsFwdStartEntry 1} 2858 dvbRcsFwdStartPopId OBJECT-TYPE 2859 SYNTAX Integer32 (-1..65535) 2860 MAX-ACCESS read-create 2861 STATUS current 2862 DESCRIPTION 2863 "Population identifier associated with the start-up 2864 forward link: 2865 -1: any (auto) 2866 0-65535: specific StartPopId 2867 If 'any' is set, the RCST will assume membership of any 2868 announced population ID and will commence with logon in 2869 accordance with this assumption." 2870 ::={dvbRcsFwdStartEntry 2} 2872 dvbRcsFwdStartFrequency OBJECT-TYPE 2873 SYNTAX Unsigned32 2874 UNITS "x100 kHz" 2875 MAX-ACCESS read-create 2876 STATUS current 2877 DESCRIPTION 2878 "Frequency of the start transponder carrying a 2879 Network Information Table to which any RCST shall 2880 trigger to acquire forward link. Its value shall be 2881 given in multiple of 100 kHz." 2882 ::={dvbRcsFwdStartEntry 3} 2884 dvbRcsFwdStartPolar OBJECT-TYPE 2885 SYNTAX INTEGER { 2886 linearHorizontal (0), 2887 linearVertical (1), 2888 circularLeft (2), 2889 circularRight (3) 2890 } 2891 MAX-ACCESS read-create 2892 STATUS current 2893 DESCRIPTION 2894 "2-bit field giving the polarization of the start 2895 transponder carrying an Network Information Table to 2896 which any RCST shall trigger to acquire forward link: 2897 00: linear and horizontal 2898 01: linear and vertical 2899 10: circular left 2900 11: circular right" 2901 ::={dvbRcsFwdStartEntry 4} 2903 dvbRcsFwdStartFormat OBJECT-TYPE 2904 SYNTAX INTEGER { 2905 auto (-1), 2906 dvbs (0), 2907 dvbs2ccm (1), 2908 dvbs2acm (2) 2909 } 2910 MAX-ACCESS read-create 2911 STATUS current 2912 DESCRIPTION 2913 "Specifies the transmission format standard applied for 2914 the startup stream. The start transport stream carries a 2915 Network Information Table that the RCST uses for 2916 acquiring the forward link signaling. Supported values 2917 are: 2918 -1: unspecified (automatic format acquisition is 2919 assumed) 2920 0: DVB-S (support of this value is mandatory if 2921 DVB-S support is claimed) 2922 1: DVB-S2 with CCM (support of this value is 2923 mandatory if DVB-S2 CCM support is claimed) 2924 2: DVB-S2 with VCM or ACM (support of this value is 2925 mandatory if DVB-S2 ACM support is claimed) 2926 This allows the RCST to discriminate between CCM and 2927 VCM/ACM when selecting the forward link. 2928 The support of automatic format selection is optional. 2929 One or several of the other format selections must be 2930 supported, according to the claimed SatLabs profile 2931 support." 2932 ::={dvbRcsFwdStartEntry 5} 2934 dvbRcsFwdStartRolloff OBJECT-TYPE 2935 SYNTAX INTEGER { 2936 autoRolloff (0), 2937 rolloff020 (1), 2938 rolloff025 (2), 2939 rolloff035 (3) 2940 } 2941 MAX-ACCESS read-create 2942 STATUS current 2943 DESCRIPTION 2944 "Specifies the receive filter roll-off applied on the 2945 start transponder. The start transponder carries a 2946 Network Information Table that the RCST uses for 2947 acquiring the forward link signaling. 2948 Supported values are: 2949 0: any (auto) 2950 1: 0.20 2951 2: 0.25 2952 3: 0.35" 2953 ::={dvbRcsFwdStartEntry 6} 2955 dvbRcsFwdStartSymbolRate OBJECT-TYPE 2956 SYNTAX Unsigned32 2957 UNITS "x100 symbols/s" 2958 MAX-ACCESS read-create 2959 STATUS current 2960 DESCRIPTION 2961 "Specifies the symbol rate on the start transponder 2962 carrying a Network Information Table to which any RCST 2963 shall trigger to acquire forward link. Its value shall 2964 be given in multiple of 100 symbols/s." 2965 ::={dvbRcsFwdStartEntry 7} 2967 dvbRcsFwdStartInnerFec OBJECT-TYPE 2968 SYNTAX INTEGER { 2969 autoFec (-1), 2970 fecRate12 (0), 2971 fecRate23 (1), 2972 fecRate34 (2), 2973 fecRate56 (3), 2974 fecRate78 (4), 2975 fecRate89 (5), 2976 fecRate35 (6), 2977 fecRate45 (7), 2978 fecRate910 (8), 2979 fecRate25 (9), 2980 fecRate13 (10), 2981 fecRate14 (11), 2982 noInnerCode (12) 2983 } 2984 MAX-ACCESS read-create 2985 STATUS current 2986 DESCRIPTION 2987 "Specifies the inner Forward Error Correction used on 2988 the start transponder carrying a Network Information 2989 Table to which any RCST shall trigger to acquire forward 2990 link. 2991 Supported values are: 2992 autoFec (-1), 2993 fecRate1/2 (0), 2994 fecRate2/3 (1), 2995 fecRate3/4 (2), 2996 fecRate5/6 (3), 2997 fecRate7/8 (4), 2998 fecRate8/9 (5), 2999 fecRate3/5 (6), 3000 fecRate4/5 (7), 3001 fecRate9/10 (8), 3002 fecRate2/5 (9), 3003 fecRate1/3 (10), 3004 fecRate1/4 (11), 3005 noInnerCode (12) 3006 The support of autoFec is optional." 3007 ::={dvbRcsFwdStartEntry 8} 3009 dvbRcsFwdStartRowStatus OBJECT-TYPE 3010 SYNTAX RowStatus 3011 MAX-ACCESS read-create 3012 STATUS current 3013 DESCRIPTION 3014 "The status of this conceptual row. It is not possible 3015 to change values in a row of this table while the row is 3016 active." 3017 ::={dvbRcsFwdStartEntry 9} 3019 --============================================================== 3020 -- dvbRcsFwdStatus sub-tree object types 3021 --============================================================== 3022 dvbRcsFwdStatusPopId OBJECT-TYPE 3023 SYNTAX Unsigned32 (0..65535) 3024 MAX-ACCESS read-only 3025 STATUS current 3026 DESCRIPTION 3027 "Population identifier applied at log-on: 3028 0-65535: specific StartPopId 3029 If the RCST was allowed to logon with any population, 3030 the RCST will report the base number of the announced 3031 population ID indicated by the RCS Map Table linkage 3032 descriptor used at logon." 3033 ::={dvbRcsFwdStatus 1} 3035 dvbRcsFwdStatusTable OBJECT-TYPE 3036 SYNTAX SEQUENCE OF DvbRcsFwdStatusEntry 3037 MAX-ACCESS not-accessible 3038 STATUS current 3039 DESCRIPTION 3040 "This table describes the current status of Forward Link 3041 interfaces." 3042 ::={dvbRcsFwdStatus 2} 3044 dvbRcsFwdStatusEntry OBJECT-TYPE 3045 SYNTAX DvbRcsFwdStatusEntry 3046 MAX-ACCESS not-accessible 3047 STATUS current 3048 DESCRIPTION 3049 "An entry in the Forward Link Status table. Each entry 3050 is associated with a physical interface. 3051 A RCST shall support at least one entry." 3052 INDEX { dvbRcsFwdStatusIndex } 3053 ::= {dvbRcsFwdStatusTable 1} 3055 DvbRcsFwdStatusEntry ::= SEQUENCE { 3056 dvbRcsFwdStatusIndex Unsigned32, 3057 dvbRcsFwdStatusIfReference Unsigned32, 3058 dvbRcsFwdStatusNetId Unsigned32, 3059 dvbRcsFwdStatusNetName 3060 SnmpAdminString, 3061 dvbRcsFwdStatusFormat INTEGER, 3062 dvbRcsFwdStatusFrequency Unsigned32, 3063 dvbRcsFwdStatusPolar INTEGER, 3064 dvbRcsFwdStatusInnerFec INTEGER, 3065 dvbRcsFwdStatusSymbolRate Unsigned32, 3066 dvbRcsFwdStatusRolloff INTEGER, 3067 dvbRcsFwdStatusModulation INTEGER, 3068 dvbRcsFwdStatusFecFrame INTEGER, 3069 dvbRcsFwdStatusPilot INTEGER, 3070 dvbRcsFwdStatusBer Integer32, 3071 dvbRcsFwdStatusCnr Integer32, 3072 dvbRcsFwdStatusRxPower Integer32 3073 } 3075 dvbRcsFwdStatusIndex OBJECT-TYPE 3076 SYNTAX Unsigned32 (1..8) 3077 MAX-ACCESS not-accessible 3078 STATUS current 3079 DESCRIPTION 3080 "Index of the Forward Link Status table." 3081 ::={dvbRcsFwdStatusEntry 1} 3083 dvbRcsFwdStatusIfReference OBJECT-TYPE 3084 SYNTAX Unsigned32 (1..8) 3085 MAX-ACCESS read-only 3086 STATUS current 3087 DESCRIPTION 3088 "Cross reference to the interface table" 3089 ::={dvbRcsFwdStatusEntry 2} 3091 dvbRcsFwdStatusNetId OBJECT-TYPE 3092 SYNTAX Unsigned32 3093 MAX-ACCESS read-only 3094 STATUS current 3095 DESCRIPTION 3096 "Interactive network identifier of the forward 3097 link (from RCS Map Table)" 3098 ::={dvbRcsFwdStatusEntry 3} 3100 dvbRcsFwdStatusNetName OBJECT-TYPE 3101 SYNTAX SnmpAdminString 3102 MAX-ACCESS read-only 3103 STATUS current 3104 DESCRIPTION 3105 "The name of the interactive network of the forward 3106 link (from RCS Map Table)" 3107 ::={dvbRcsFwdStatusEntry 4} 3109 dvbRcsFwdStatusFormat OBJECT-TYPE 3110 SYNTAX INTEGER { 3111 dvbs (0), 3112 dvbs2ccm (1), 3113 dvbs2acm (2), 3114 reservedFormat (3) 3115 } 3116 MAX-ACCESS read-only 3117 STATUS current 3118 DESCRIPTION 3119 "Specifies the transmission format applied on the 3120 forward link. Supported values are (from RMT): 3122 0: DVB-S 3123 1: DVB-S2 using CCM 3124 2: DVB-S2 using VCM or ACM 3125 3: reserved" 3126 ::={dvbRcsFwdStatusEntry 5} 3128 dvbRcsFwdStatusFrequency OBJECT-TYPE 3129 SYNTAX Unsigned32 3130 UNITS "x100 kHz" 3131 MAX-ACCESS read-only 3132 STATUS current 3133 DESCRIPTION 3134 "An estimate of the frequency of the forward link. Its 3135 value shall be given in multiple of 100 kHz." 3136 ::={dvbRcsFwdStatusEntry 6} 3138 dvbRcsFwdStatusPolar OBJECT-TYPE 3139 SYNTAX INTEGER { 3140 linearHorizontal (0), 3141 linearVertical (1), 3142 circularLeft (2), 3143 circularRight (3) 3144 } 3145 MAX-ACCESS read-only 3146 STATUS current 3147 DESCRIPTION 3148 "2-bit field giving the polarization of the forward link 3149 (from RMT): 3150 00: linear and horizontal 3151 01: linear and vertical 3152 10: circular left 3153 11: circular right" 3154 ::={dvbRcsFwdStatusEntry 7} 3156 dvbRcsFwdStatusInnerFec OBJECT-TYPE 3157 SYNTAX INTEGER { 3158 unknown (-1), 3159 fecRate12 (0), 3160 fecRate23 (1), 3161 fecRate34 (2), 3162 fecRate56 (3), 3163 fecRate78 (4), 3164 fecRate89 (5), 3165 fecRate35 (6), 3166 fecRate45 (7), 3167 fecRate910 (8), 3168 fecRate25 (9), 3169 fecRate13 (10), 3170 fecRate14 (11), 3171 noInnerCode (12) 3172 } 3173 MAX-ACCESS read-only 3174 STATUS current 3175 DESCRIPTION 3176 "Specifies the inner Forward Error Correction used on 3177 the forward link for transmission to the RCST. 3178 Supported values are: 3179 unknown (-1), 3180 fecRate1/2 (0), 3181 fecRate2/3 (1), 3182 fecRate3/4 (2), 3183 fecRate5/6 (3), 3184 fecRate7/8 (4), 3185 fecRate8/9 (5), 3186 fecRate3/5 (6), 3187 fecRate4/5 (7), 3188 fecRate9/10 (8), 3189 fecRate2/5 (9), 3190 fecRate1/3 (10), 3191 fecRate1/4 (11), 3192 noInnerCode (12) 3193 The RCST will report a value that has been used for 3194 transmission to the RCST within the most recent 60 3195 seconds. If this is not relevant, the RCST will report 3196 'unknown'." 3197 ::={dvbRcsFwdStatusEntry 8} 3199 dvbRcsFwdStatusSymbolRate OBJECT-TYPE 3200 SYNTAX Unsigned32 3201 UNITS "x100 symbols/s" 3202 MAX-ACCESS read-only 3203 STATUS current 3204 DESCRIPTION 3205 "An estimate of the symbol rate of the forward link. 3206 Its value shall be given in multiple of 100 symbol/s." 3207 ::={dvbRcsFwdStatusEntry 9} 3209 dvbRcsFwdStatusRolloff OBJECT-TYPE 3210 SYNTAX INTEGER { 3211 undefRolloff (0), 3212 rolloff020 (1), 3213 rolloff025 (2), 3214 rolloff035 (3) 3215 } 3216 MAX-ACCESS read-only 3217 STATUS current 3218 DESCRIPTION 3219 "An estimate of the roll-off applied on the forward 3220 link. 3221 Supported values are: 3222 0: undefined 3223 1: 0.20 3224 2: 0.25 3225 3: 0.35" 3226 ::={dvbRcsFwdStatusEntry 10} 3228 dvbRcsFwdStatusModulation OBJECT-TYPE 3229 SYNTAX INTEGER { 3230 unknown (0), 3231 mBPSK (1), 3232 mQPSK (2), 3233 m8PSK (3), 3234 m16APSK (4), 3235 m32APSK (5) 3236 } 3237 MAX-ACCESS read-only 3238 STATUS current 3239 DESCRIPTION 3240 "Indicates the modulation on the forward link used for 3241 transmission to the RCST. 3242 0: unknown 3243 1: BPSK 3244 2: QPSK 3245 3: 8PSK 3246 4: 16APSK 3247 5: 32APSK 3248 The RCST will report a value that has been used for 3249 transmission to the RCST within the most recent 60 3250 seconds. 3251 If this is not relevant, the RCST will report 3252 'unknown'." 3253 ::={dvbRcsFwdStatusEntry 11} 3255 dvbRcsFwdStatusFecFrame OBJECT-TYPE 3256 SYNTAX INTEGER { 3257 unknown (0), 3258 shortframe (1), 3259 longframe (2) 3260 } 3261 MAX-ACCESS read-only 3262 STATUS current 3263 DESCRIPTION 3264 "Indicates the frame length used on the forward link for 3265 transmission to the RCST. 3266 Supported values are: 3267 0: Unknown 3268 1: Short frame 3269 2: Normal frame 3270 The RCST will report a value that has been used for 3271 transmission to the RCST within the most recent 60 3272 seconds. 3273 If this is not relevant, the RCST will report 3274 'unknown'." 3275 ::={dvbRcsFwdStatusEntry 12} 3277 dvbRcsFwdStatusPilot OBJECT-TYPE 3278 SYNTAX INTEGER { 3279 unknown (0), 3280 pilotNotused (1), 3281 pilotUsed (2) 3282 } 3283 MAX-ACCESS read-only 3284 STATUS current 3285 DESCRIPTION 3286 "Indicates whether pilots are used on the forward link 3287 for transmission to the RCST. 3288 Supported values are: 3289 0: Unknown 3290 1: Pilots are not used 3291 2: Pilots are used 3292 The RCST will report a value that has been used for 3293 transmission to the RCST within the most recent 60 3294 seconds. 3295 If this is not relevant, the RCST will report 3296 'unknown'." 3297 ::={dvbRcsFwdStatusEntry 13} 3299 dvbRcsFwdStatusBer OBJECT-TYPE 3300 SYNTAX Integer32 3301 UNITS "exponent of 10" 3302 MAX-ACCESS read-only 3303 STATUS current 3304 DESCRIPTION 3305 "Provides the RCST BER on the Forward Link in log10 3306 units." 3307 ::={dvbRcsFwdStatusEntry 14} 3309 dvbRcsFwdStatusCnr OBJECT-TYPE 3310 SYNTAX Integer32 3311 UNITS "0.1 dB" 3312 MAX-ACCESS read-only 3313 STATUS current 3314 DESCRIPTION 3315 "Provides the RCST CNR on the Forward Link in 0.1 dB 3316 units." 3317 ::={dvbRcsFwdStatusEntry 15} 3319 dvbRcsFwdStatusRxPower OBJECT-TYPE 3320 SYNTAX Integer32 3321 UNITS "0.1 dBm" 3322 MAX-ACCESS read-only 3323 STATUS current 3324 DESCRIPTION 3325 "Provides the power level of the Forward Link as 3326 received at the IDU, in 0.1 dBm units." 3328 DEFVAL { -500 } 3329 ::={dvbRcsFwdStatusEntry 16} 3331 --============================================================== 3332 -- dvbRcsRtnConfig sub-tree object types 3333 --============================================================== 3334 dvbRcsRtnConfigMaxEirp OBJECT-TYPE 3335 SYNTAX Integer32 3336 UNITS "x0.1 dBm" 3337 MAX-ACCESS read-write 3338 STATUS current 3339 DESCRIPTION 3340 "Max EIRP of the RCST given in resolution of 0.1 dBm, 3341 applied when the IDU can itself set the necessary IDU 3342 TX output level e.g. when using a BUC that has a power 3343 level detector and provides sufficient feedback to the 3344 IDU." 3345 ::= {dvbRcsRtnConfig 1} 3347 dvbRcsRtnConfigDefIfLevel OBJECT-TYPE 3348 SYNTAX Integer32 3349 UNITS "x0.1 dBm" 3350 MAX-ACCESS read-write 3351 STATUS current 3352 DESCRIPTION 3353 "IDU TX output level applied in case the 3354 dvbRcsRtnConfigMaxEirp cannot be used. The resolution 3355 is 0.1 dBm and the accuracy is +/- 1 dBm." 3356 ::= {dvbRcsRtnConfig 2} 3358 --============================================================== 3359 -- dvbRcsRtnStatus sub-tree object types 3360 --============================================================== 3361 dvbRcsRtnStatusEbN0 OBJECT-TYPE 3362 SYNTAX Integer32 3363 UNITS "x0.1 dB" 3364 MAX-ACCESS read-only 3365 STATUS current 3366 DESCRIPTION 3367 "The EbN0 value reported for the return link, referenced 3368 to the regular SYNC burst transmission, in 0.1 dB 3369 units." 3370 ::= {dvbRcsRtnStatus 1} 3372 dvbRcsRtnStatusSFDuration OBJECT-TYPE 3373 SYNTAX Unsigned32 (250..7500) 3374 UNITS "0.1 ms" 3375 MAX-ACCESS read-only 3376 STATUS current 3377 DESCRIPTION 3378 "The duration of the currently applied return link 3379 super-frame structure, in tenths of milliseconds." 3380 ::= {dvbRcsRtnStatus 2} 3382 dvbRcsRtnStatusPayloadUnit OBJECT-TYPE 3383 SYNTAX INTEGER { 3384 unitATM (0), 3385 unitMPEG (1) 3386 } 3387 MAX-ACCESS read-only 3388 STATUS current 3389 DESCRIPTION 3390 "Indicates if the payload unit used for the return link 3391 is ATM or MPEG." 3392 ::= {dvbRcsRtnStatus 3} 3394 --============================================================= 3395 -- conformance information 3396 --============================================================= 3397 dvbRcsRcstGroups OBJECT IDENTIFIER ::= 3398 {dvbRcsConformance 1} 3399 dvbRcsRcstCompliances OBJECT IDENTIFIER ::= 3400 {dvbRcsConformance 2} 3402 --============================================================= 3403 -- conformance statements 3404 --============================================================= 3405 dvbRcsRcstCompliance1 MODULE-COMPLIANCE 3406 STATUS current 3407 DESCRIPTION 3408 "The compliance statement for DVB-RCS terminals that 3409 are compliant with SatLabs System Recommendations. 3410 Compliance is linked to the support by the terminal of 3411 the options or features defined in the SatLabs System 3412 Recommendations. 3413 The supported options and features of a terminal are 3414 declared in objects 3415 dvbRcsSystemSatLabsOptionsDeclaration 3416 and dvbRcsSystemSatLabsFeaturesDeclaration 3417 respectively." 3419 MODULE -- this module 3421 MANDATORY-GROUPS {dvbRcsRcstSystemGroup, 3422 dvbRcsRcstNetworkGroup, dvbRcsRcstInstallGroup, 3423 dvbRcsRcstQosGroup, dvbRcsRcstControlGroup, 3424 dvbRcsRcstStateGroup, dvbRcsFwdConfigGroup, 3425 dvbRcsFwdStatusGroup, dvbRcsRtnConfigGroup, 3426 dvbRcsRtnStatusGroup} 3428 GROUP dvbRcsRcstExtNetworkGroup 3429 DESCRIPTION 3430 "This group is mandatory for an RCST that supports extended 3431 networking management functionality. Such RCST is qualified 3432 as supporting the EXTNETWORK feature, as defined in the 3433 SatLabs System Recommendations." 3435 GROUP dvbRcsRcstDnsGroup 3436 DESCRIPTION 3437 "This group is mandatory for an RCST that supports the DNS 3438 protocol. Such RCST is qualified as supporting the DNS 3439 option, as defined in the SatLabs System Recommendations." 3441 GROUP dvbRcsRcstExtInstallGroup 3442 DESCRIPTION 3443 "This group is mandatory for an RCST that supports the 3444 installation log file. Such RCST is qualified as supporting 3445 the INSTALL_LOG feature, as defined in the SatLabs System 3446 Recommendations." 3448 GROUP dvbRcsRcstEnhancedClassifierGroup 3449 DESCRIPTION 3450 "This group is mandatory for an RCST that supports the 3451 enhanced classifier feature. Such RCST is qualified as 3452 supporting the ENHCLASSIFIER feature, as defined in the 3453 SatLabs System Recommendations." 3455 GROUP dvbRcsRcstMpegQosGroup 3456 DESCRIPTION 3457 "This group is mandatory for an RCST that supports MPEG 3458 traffic bursts. Such RCST is qualified as supporting the 3459 MPEG_TRF option, as defined in the SatLabs System 3460 Recommendations." 3462 GROUP dvbRcsRcstGlobalQosGroup 3463 DESCRIPTION 3464 "This group is mandatory for an RCST that supports global 3465 RCST QOS configuration data. Such RCST is qualified as 3466 supporting the RCST_PARA feature, as defined in the SatLabs 3467 System Recommendations." 3469 GROUP dvbRcsRcstStrictQosGroup 3470 DESCRIPTION 3471 "This group is mandatory for an RCST that supports strict 3472 channel ID dispatching. Such RCST is qualified as supporting 3473 the CHID_STRICT option, as defined in the SatLabs System 3474 Recommendations." 3476 GROUP dvbRcsRcstExtControlGroup 3477 DESCRIPTION 3478 "This group is mandatory for an RCST that supports extended 3479 control management functionality. Such RCST is qualified as 3480 supporting the EXTCONTROL feature, as defined in the SatLabs 3481 System Recommendations." 3483 GROUP dvbRcsRtnExtConfigGroup 3484 DESCRIPTION 3485 "This group is mandatory for an RCST that supports extended 3486 return link configuration management functionality. Such 3487 RCST is qualified as supporting the EXTCONFIG feature, as 3488 defined in the SatLabs System Recommendations." 3490 GROUP dvbRcsRtnExtStatusGroup 3491 DESCRIPTION 3492 "This group is mandatory for an RCST that supports extended 3493 return link status report functionality. Such RCST is 3494 qualified as supporting the EXTSTATUS feature, as defined in 3495 the SatLabs System Recommendations." 3497 GROUP dvbRcsRcstOduListGroup 3498 DESCRIPTION 3499 "This group is mandatory for an RCST that supports the ODU 3500 structural entities defined under dvbRcsOduTx, dvbRcsOduRx 3501 and dvbRcsOduAntenna. Such RCST is qualified as supporting 3502 the ODULIST feature, as defined in the SatLabs System 3503 Recommendations." 3505 OBJECT dvbRcsSystemOduAntennaSize 3506 MIN-ACCESS read-only 3507 DESCRIPTION 3508 "Write access is supported if the dvbRcsRcstOduListGroup is 3509 not supported." 3511 OBJECT dvbRcsSystemOduAntennaGain 3512 MIN-ACCESS read-only 3513 DESCRIPTION 3514 "Write access is supported if the dvbRcsRcstOduListGroup is 3515 not supported." 3517 OBJECT dvbRcsSystemOduSspa 3518 MIN-ACCESS read-only 3519 DESCRIPTION 3520 "Write access is supported if the dvbRcsRcstOduListGroup is 3521 not supported." 3523 OBJECT dvbRcsSystemOduTxType 3524 MIN-ACCESS read-only 3525 DESCRIPTION 3526 "Write access is supported if the dvbRcsRcstOduListGroup is 3527 not supported." 3529 OBJECT dvbRcsSystemOduRxType 3530 MIN-ACCESS read-only 3531 DESCRIPTION 3532 "Write access is supported if the dvbRcsRcstOduListGroup is 3533 not supported." 3535 OBJECT dvbRcsSystemOduRxBand 3536 MIN-ACCESS read-only 3537 DESCRIPTION 3538 "Write access is supported if the dvbRcsRcstOduListGroup is 3539 not supported." 3541 OBJECT dvbRcsSystemOduRxLO 3542 MIN-ACCESS read-only 3543 DESCRIPTION 3544 "Write access is supported if the dvbRcsRcstOduListGroup is 3545 not supported." 3547 OBJECT dvbRcsSystemOduTxLO 3548 MIN-ACCESS read-only 3549 DESCRIPTION 3550 "Write access is supported if the dvbRcsRcstOduListGroup is 3551 not supported." 3553 OBJECT dvbRcsNetworkOamInetAddressType 3554 SYNTAX InetAddressType { ipv4(1) } 3555 DESCRIPTION 3556 "An implementation is only required to support IPv4 3557 addresses." 3559 OBJECT dvbRcsNetworkOamInetAddress 3560 SYNTAX InetAddress (SIZE(4)) 3561 DESCRIPTION 3562 "An implementation is only required to support IPv4 3563 addresses." 3565 OBJECT dvbRcsNetworkLanInetAddressType 3566 SYNTAX InetAddressType { ipv4(1) } 3567 DESCRIPTION 3568 "An implementation is only required to support IPv4 3569 addresses." 3571 OBJECT dvbRcsNetworkLanInetAddress 3572 SYNTAX InetAddress (SIZE(4)) 3573 DESCRIPTION 3574 "An implementation is only required to support IPv4 3575 addresses." 3577 OBJECT dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType 3578 SYNTAX InetAddressType { ipv4(1) } 3579 DESCRIPTION 3580 "An implementation is only required to support IPv4 3581 addresses." 3583 OBJECT dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress 3584 SYNTAX InetAddressType { ipv4(1) } 3585 DESCRIPTION 3586 "An implementation is only required to support IPv4 3587 addresses." 3589 OBJECT dvbRcsPrimaryDnsServerInetAddressType 3590 SYNTAX InetAddressType { ipv4(1) } 3591 DESCRIPTION 3592 "An implementation is only required to support IPv4 3593 addresses." 3595 OBJECT dvbRcsPrimaryDnsServerInetAddress 3596 SYNTAX InetAddressType { ipv4(1) } 3597 DESCRIPTION 3598 "An implementation is only required to support IPv4 3599 addresses." 3601 OBJECT dvbRcsSecondaryDnsServerInetAddressType 3602 SYNTAX InetAddressType { ipv4(1) } 3603 DESCRIPTION 3604 "An implementation is only required to support IPv4 3605 addresses." 3607 OBJECT dvbRcsSecondaryDnsServerInetAddress 3608 SYNTAX InetAddressType { ipv4(1) } 3609 DESCRIPTION 3610 "An implementation is only required to support IPv4 3611 addresses." 3613 OBJECT dvbRcsNetworkNccMgtInetAddressType 3614 SYNTAX InetAddressType { ipv4(1) } 3615 DESCRIPTION 3616 "An implementation is only required to support IPv4 3617 addresses." 3619 OBJECT dvbRcsNetworkNccMgtInetAddress 3620 SYNTAX InetAddressType { ipv4(1) } 3621 DESCRIPTION 3622 "An implementation is only required to support IPv4 3623 addresses." 3625 OBJECT dvbRcsPktClassDscpLow 3626 MIN-ACCESS read-only 3627 DESCRIPTION 3628 "Create access only required if the RCST supports the 3629 enhanced classifier feature. Such RCST is qualified as 3630 supporting the ENHCLASSIFIER feature, as defined in the 3631 SatLabs System Recommendations." 3633 OBJECT dvbRcsPktClassDscpHigh 3634 MIN-ACCESS read-only 3635 DESCRIPTION 3636 "Create access only required if the RCST supports the 3637 enhanced classifier feature. Such RCST is qualified as 3638 supporting the ENHCLASSIFIER feature, as defined in the 3639 SatLabs System Recommendations." 3641 OBJECT dvbRcsPktClassDscpMarkValue 3642 MIN-ACCESS read-only 3643 DESCRIPTION 3644 "Create access only required if the RCST supports the 3645 enhanced classifier feature. Such RCST is qualified as 3646 supporting the ENHCLASSIFIER feature, as defined in the 3647 SatLabs System Recommendations." 3649 OBJECT dvbRcsPktClassSrcInetAddressType 3650 SYNTAX InetAddressType { ipv4(1) } 3651 DESCRIPTION 3652 "An implementation is only required to support IPv4 3653 addresses." 3655 OBJECT dvbRcsPktClassSrcInetAddress 3656 SYNTAX InetAddressType { ipv4(1) } 3657 DESCRIPTION 3658 "An implementation is only required to support IPv4 3659 addresses." 3661 OBJECT dvbRcsPktClassDstInetAddressType 3662 SYNTAX InetAddressType { ipv4(1) } 3663 DESCRIPTION 3664 "An implementation is only required to support IPv4 3665 addresses." 3667 OBJECT dvbRcsPktClassDstInetAddress 3668 SYNTAX InetAddressType { ipv4(1) } 3669 DESCRIPTION 3670 "An implementation is only required to support IPv4 3671 addresses." 3673 OBJECT dvbRcsPhbName 3674 MIN-ACCESS read-only 3675 DESCRIPTION 3676 "Create access only required if the RCST supports extended 3677 management support. Such RCST is qualified as supporting 3678 the SNMPMISC option, as defined in the SatLabs System 3679 Recommendations." 3681 OBJECT dvbRcsPhbRequestClassAssociation 3682 MIN-ACCESS read-only 3683 DESCRIPTION 3684 "Create access only required if the RCST supports extended 3685 management support. Such RCST is qualified as supporting 3686 the SNMPMISC option, as defined in the SatLabs System 3687 Recommendations." 3689 OBJECT dvbRcsPhbMappingRowStatus 3690 MIN-ACCESS read-only 3691 DESCRIPTION 3692 "Create access only required if the RCST supports extended 3693 management support. Such RCST is qualified as supporting 3694 the SNMPMISC option, as defined in the SatLabs System 3695 Recommendations." 3697 OBJECT dvbRcsRequestClassName 3698 MIN-ACCESS read-only 3699 DESCRIPTION 3700 "Write access only required if the RCST supports extended 3701 management support. Such RCST is qualified as supporting 3702 the SNMPMISC option, as defined in the SatLabs System 3703 Recommendations." 3705 OBJECT dvbRcsRequestClassChanId 3706 MIN-ACCESS read-only 3707 DESCRIPTION 3708 "Write access only required if the RCST supports extended 3709 management support. Such RCST is qualified as supporting 3710 the SNMPMISC option, as defined in the SatLabs System 3711 Recommendations." 3713 OBJECT dvbRcsRequestClassVccVpi 3714 MIN-ACCESS read-only 3715 DESCRIPTION 3716 "Write access only required if the RCST supports extended 3717 management support. Such RCST is qualified as supporting 3718 the SNMPMISC option, as defined in the SatLabs System 3719 Recommendations." 3721 OBJECT dvbRcsRequestClassVccVci 3722 MIN-ACCESS read-only 3723 DESCRIPTION 3724 "Write access only required if the RCST supports extended 3725 management support. Such RCST is qualified as supporting 3726 the SNMPMISC option, as defined in the SatLabs System 3727 Recommendations." 3729 OBJECT dvbRcsRequestClassPidPoolReference 3730 MIN-ACCESS not-accessible 3731 DESCRIPTION 3732 "Read-only access required if the RCST supports MPEG traffic 3733 Bursts, according to the MPEG_TRF option, as defined in the 3734 SatLabs System Recommendations. Write access only required 3735 if the RCST also supports extended management support, 3736 according to the SNMPMISC option, as defined in the SatLabs 3737 System Recommendations." 3739 OBJECT dvbRcsRequestClassCra 3740 MIN-ACCESS read-only 3741 DESCRIPTION 3742 "Write access only required if the RCST supports extended 3743 management support, according to the SNMPMISC option, as 3744 defined in the SatLabs System Recommendations." 3746 OBJECT dvbRcsRequestClassRbdcMax 3747 MIN-ACCESS read-only 3748 DESCRIPTION 3749 "Write access only required if the RCST supports extended 3750 management support, according to the SNMPMISC option, as 3751 defined in the SatLabs System Recommendations." 3753 OBJECT dvbRcsRequestClassRbdcTimeout 3754 MIN-ACCESS read-only 3755 DESCRIPTION 3756 "Write access only required if the RCST supports extended 3757 management support, according to the SNMPMISC option, as 3758 defined in the SatLabs System Recommendations." 3760 OBJECT dvbRcsRequestClassVbdcMax 3761 MIN-ACCESS read-only 3762 DESCRIPTION 3763 "Write access only required if the RCST supports extended 3764 management support, according to the SNMPMISC option, as 3765 defined in the SatLabs System Recommendations." 3767 OBJECT dvbRcsRequestClassVbdcTimeout 3768 MIN-ACCESS read-only 3769 DESCRIPTION 3770 "Write access only required if the RCST supports extended 3771 management support, according to the SNMPMISC option, as 3772 defined in the SatLabs System Recommendations." 3774 OBJECT dvbRcsRequestClassVbdcMaxBackLog 3775 MIN-ACCESS read-only 3776 DESCRIPTION 3777 "Write access only required if the RCST supports extended 3778 management support, according to the SNMPMISC option, as 3779 defined in the SatLabs System Recommendations." 3781 OBJECT dvbRcsRequestClassRowStatus 3782 MIN-ACCESS read-only 3783 DESCRIPTION 3784 "Write access only required if the RCST supports extended 3785 management support, according to the SNMPMISC option, as 3786 defined in the SatLabs System Recommendations." 3788 OBJECT dvbRcsPidValue 3789 MIN-ACCESS not-accessible 3790 DESCRIPTION 3791 "Read-only access required if the RCST supports MPEG traffic 3792 Bursts, according to the MPEG_TRF option, as defined in the 3793 SatLabs System Recommendations. Write access only required 3794 if the RCST also supports extended management support, 3795 according to the SNMPMISC option, as defined in the SatLabs 3796 System Recommendations." 3798 OBJECT dvbRcsPidPoolRowStatus 3799 MIN-ACCESS not-accessible 3800 DESCRIPTION 3801 "Read-only access required the RCST supports MPEG traffic 3802 Bursts, according to the MPEG_TRF option, as defined in the 3803 SatLabs System Recommendations. Write access only required 3804 if the RCST also supports extended management support, 3805 according to the SNMPMISC option, as defined in the SatLabs 3806 System Recommendations." 3808 ::= {dvbRcsRcstCompliances 1} 3810 --============================================================= 3811 -- units of conformance 3812 --============================================================= 3814 --============================================================= 3815 -- object groups for RCST system 3816 --============================================================= 3817 dvbRcsRcstSystemGroup OBJECT-GROUP 3818 OBJECTS { 3819 dvbRcsSystemMibRevision, 3820 dvbRcsSystemSatLabsProfilesDeclaration, 3821 dvbRcsSystemSatLabsOptionsDeclaration, 3822 dvbRcsSystemSatLabsFeaturesDeclaration, 3823 dvbRcsSystemLocation, 3824 dvbRcsSystemOduAntennaSize, 3825 dvbRcsSystemOduAntennaGain, 3826 dvbRcsSystemOduSspa, 3827 dvbRcsSystemOduTxType, 3828 dvbRcsSystemOduRxType, 3829 dvbRcsSystemOduRxBand, 3830 dvbRcsSystemOduRxLO, 3831 dvbRcsSystemOduTxLO, 3832 dvbRcsTcpPep, 3833 dvbRcsHttpPep 3834 } 3835 STATUS current 3836 DESCRIPTION 3837 "A collection of objects providing information 3838 applicable for basic device management support." 3839 ::= {dvbRcsRcstGroups 1} 3841 --============================================================= 3842 -- object groups for RCST networking 3843 --============================================================= 3844 dvbRcsRcstNetworkGroup OBJECT-GROUP 3845 OBJECTS { 3846 dvbRcsNetworkOamInetAddressType, 3847 dvbRcsNetworkOamInetAddress, 3848 dvbRcsNetworkOamInetAddressPrefixLength, 3849 dvbRcsNetworkLanInetAddressType, 3850 dvbRcsNetworkLanInetAddress, 3851 dvbRcsNetworkLanInetAddressPrefixLength, 3852 dvbRcsNetworkConfigFileDownloadUrl, 3853 dvbRcsNetworkConfigFileUploadUrl, 3854 dvbRcsNetworkLogFileUploadUrl 3855 } 3856 STATUS current 3857 DESCRIPTION 3858 "A collection of objects providing basic networking 3859 management support." 3860 ::= {dvbRcsRcstGroups 2} 3862 dvbRcsRcstExtNetworkGroup OBJECT-GROUP 3863 OBJECTS { 3864 dvbRcsNetworkOamInetAddressAssign, 3865 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType, 3866 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress, 3867 dvbRcsNetworkNccMgtInetAddressType, 3868 dvbRcsNetworkNccMgtInetAddress 3869 } 3870 STATUS current 3871 DESCRIPTION 3872 "A collection of objects providing extended networking 3873 management support." 3874 ::= {dvbRcsRcstGroups 3} 3876 dvbRcsRcstDnsGroup OBJECT-GROUP 3877 OBJECTS { 3878 dvbRcsPrimaryDnsServerInetAddressType, 3879 dvbRcsPrimaryDnsServerInetAddress, 3880 dvbRcsSecondaryDnsServerInetAddressType, 3881 dvbRcsSecondaryDnsServerInetAddress 3882 } 3883 STATUS current 3884 DESCRIPTION 3885 "A collection of objects providing DNS management 3886 support." 3887 ::= {dvbRcsRcstGroups 4} 3889 --============================================================= 3890 -- object groups for RCST installation 3891 --============================================================= 3893 dvbRcsRcstInstallGroup OBJECT-GROUP 3894 OBJECTS { 3895 dvbRcsInstallAntennaAlignmentState, 3896 dvbRcsInstallCwFrequency, 3897 dvbRcsInstallCwMaxDuration, 3898 dvbRcsInstallCwPower, 3899 dvbRcsInstallCoPolReading, 3900 dvbRcsInstallXPolReading, 3901 dvbRcsInstallCoPolTarget, 3902 dvbRcsInstallXPolTarget, 3903 dvbRcsInstallStandByDuration, 3904 dvbRcsInstallTargetEsN0 3905 } 3906 STATUS current 3907 DESCRIPTION 3908 "A collection of objects providing information 3909 applicable for basic installation support." 3910 ::= {dvbRcsRcstGroups 5} 3912 dvbRcsRcstExtInstallGroup OBJECT-GROUP 3913 OBJECTS { 3914 dvbRcsNetworkInstallLogFileDownloadUrl, 3915 dvbRcsNetworkInstallLogFileUploadUrl 3916 } 3917 STATUS current 3918 DESCRIPTION 3919 "A collection of objects providing extended device 3920 installation support." 3921 ::= {dvbRcsRcstGroups 6} 3923 --============================================================= 3924 -- object groups for QOS 3925 --============================================================= 3927 dvbRcsRcstQosGroup OBJECT-GROUP 3928 OBJECTS { 3929 dvbRcsPktClassDscpLow, 3930 dvbRcsPktClassDscpHigh, 3931 dvbRcsPktClassDscpMarkValue, 3932 dvbRcsPktClassPhbAssociation, 3933 dvbRcsPktClassRowStatus, 3934 dvbRcsPhbName, 3935 dvbRcsPhbRequestClassAssociation, 3936 dvbRcsPhbMappingRowStatus, 3937 dvbRcsRequestClassName, 3938 dvbRcsRequestClassChanId, 3939 dvbRcsRequestClassVccVpi, 3940 dvbRcsRequestClassVccVci, 3941 dvbRcsRequestClassCra, 3942 dvbRcsRequestClassRbdcMax, 3943 dvbRcsRequestClassRbdcTimeout, 3944 dvbRcsRequestClassVbdcMax, 3945 dvbRcsRequestClassVbdcTimeout, 3946 dvbRcsRequestClassVbdcMaxBackLog, 3947 dvbRcsRequestClassRowStatus 3948 } 3949 STATUS current 3950 DESCRIPTION 3951 "A collection of objects providing basic access to QOS 3952 configuration data." 3953 ::= {dvbRcsRcstGroups 7} 3955 dvbRcsRcstEnhancedClassifierGroup OBJECT-GROUP 3956 OBJECTS { 3957 dvbRcsPktClassIpProtocol, 3958 dvbRcsPktClassSrcInetAddressType, 3959 dvbRcsPktClassSrcInetAddress, 3960 dvbRcsPktClassSrcInetAddressPrefixLength, 3961 dvbRcsPktClassDstInetAddressType, 3962 dvbRcsPktClassDstInetAddress, 3963 dvbRcsPktClassDstInetAddressPrefixLength, 3964 dvbRcsPktClassSrcPortLow, 3965 dvbRcsPktClassSrcPortHigh, 3966 dvbRcsPktClassDstPortLow, 3967 dvbRcsPktClassDstPortHigh, 3968 dvbRcsPktClassVlanUserPri 3969 } 3970 STATUS current 3971 DESCRIPTION 3972 "A collection of objects providing support for 3973 management of the enhanced classifier." 3974 ::= {dvbRcsRcstGroups 8} 3976 dvbRcsRcstMpegQosGroup OBJECT-GROUP 3977 OBJECTS { 3978 dvbRcsRequestClassPidPoolReference, 3979 dvbRcsPidValue, 3980 dvbRcsPidPoolRowStatus 3981 } 3982 STATUS current 3983 DESCRIPTION 3984 "A collection of objects providing access to MPEG 3985 related link QOS configuration data." 3986 ::= {dvbRcsRcstGroups 9} 3988 dvbRcsRcstGlobalQosGroup OBJECT-GROUP 3989 OBJECTS { 3990 dvbRcsQosGlobalRbdcMax, 3991 dvbRcsQosGlobalVbdcMax, 3992 dvbRcsQosGlobalVbdcMaxBackLog 3993 } 3994 STATUS current 3995 DESCRIPTION 3996 "A collection of objects providing access to global RCST 3997 QOS configuration data." 3998 ::= {dvbRcsRcstGroups 10} 4000 dvbRcsRcstStrictQosGroup OBJECT-GROUP 4001 OBJECTS { 4002 dvbRcsQosChannelIdStrictDispatching 4003 } 4004 STATUS current 4005 DESCRIPTION 4006 "A collection of objects allowing management of strict 4007 channel ID dispatching." 4008 ::= {dvbRcsRcstGroups 11} 4010 --============================================================= 4011 -- object groups for RCST control 4012 --============================================================= 4013 dvbRcsRcstControlGroup OBJECT-GROUP 4014 OBJECTS { 4015 dvbRcsCtrlRebootCommand, 4016 dvbRcsCtrlUserTrafficDisable, 4017 dvbRcsCtrlCwEnable, 4018 dvbRcsCtrlDownloadFileCommand, 4019 dvbRcsCtrlUploadFileCommand, 4020 dvbRcsCtrlActivateConfigFileCommand, 4021 dvbRcsCtrlRcstRxReacquire 4022 } 4023 STATUS current 4024 DESCRIPTION 4025 "A collection of objects allowing basic RCST control." 4026 ::= {dvbRcsRcstGroups 12} 4028 dvbRcsRcstExtControlGroup OBJECT-GROUP 4029 OBJECTS { 4030 dvbRcsCtrlRcstTxDisable, 4031 dvbRcsCtrlOduTxReferenceEnable, 4032 dvbRcsCtrlOduTxDCEnable, 4033 dvbRcsCtrlOduRxDCEnable, 4034 dvbRcsCtrlRcstLogonCommand, 4035 dvbRcsCtrlRcstLogoffCommand 4036 } 4037 STATUS current 4038 DESCRIPTION 4039 "A collection of objects allowing extended RCST 4040 control." 4041 ::= {dvbRcsRcstGroups 13} 4043 --============================================================= 4044 -- object groups for RCST state 4045 --============================================================= 4047 dvbRcsRcstStateGroup OBJECT-GROUP 4048 OBJECTS { 4049 dvbRcsRcstMode, 4050 dvbRcsRcstFaultStatus, 4051 dvbRcsRcstFwdLinkStatus, 4052 dvbRcsRcstLogUpdated, 4053 dvbRcsRcstCurrentSoftwareVersion, 4054 dvbRcsRcstAlternateSoftwareVersion, 4055 dvbRcsRcstActivatedConfigFileVersion, 4056 dvbRcsRcstDownloadedConfigFileVersion 4057 } 4058 STATUS current 4059 DESCRIPTION 4060 "A collection of objects allowing access to RCST state." 4061 ::= {dvbRcsRcstGroups 14} 4062 --============================================================= 4063 -- object groups for forward link 4064 --============================================================= 4066 dvbRcsFwdConfigGroup OBJECT-GROUP 4067 OBJECTS { 4068 dvbRcsFwdStartPopId, 4069 dvbRcsFwdStartFrequency, 4070 dvbRcsFwdStartPolar, 4071 dvbRcsFwdStartFormat, 4072 dvbRcsFwdStartRolloff, 4073 dvbRcsFwdStartSymbolRate, 4074 dvbRcsFwdStartInnerFec, 4075 dvbRcsFwdStartRowStatus 4076 } 4077 STATUS current 4078 DESCRIPTION 4079 "A collection of objects providing basic start forward 4080 link configuration support." 4081 ::= {dvbRcsRcstGroups 15} 4083 dvbRcsFwdStatusGroup OBJECT-GROUP 4084 OBJECTS { 4085 dvbRcsFwdStatusPopId, 4086 dvbRcsFwdStatusIfReference, 4087 dvbRcsFwdStatusNetId, 4088 dvbRcsFwdStatusNetName, 4089 dvbRcsFwdStatusFormat, 4090 dvbRcsFwdStatusFrequency, 4091 dvbRcsFwdStatusPolar, 4092 dvbRcsFwdStatusInnerFec, 4093 dvbRcsFwdStatusSymbolRate, 4094 dvbRcsFwdStatusRolloff, 4095 dvbRcsFwdStatusModulation, 4096 dvbRcsFwdStatusFecFrame, 4097 dvbRcsFwdStatusPilot, 4098 dvbRcsFwdStatusBer, 4099 dvbRcsFwdStatusCnr, 4100 dvbRcsFwdStatusRxPower 4101 } 4103 STATUS current 4104 DESCRIPTION 4105 "A collection of objects providing forward link status." 4106 ::= {dvbRcsRcstGroups 16} 4108 --============================================================= 4109 -- object groups for return link 4110 --============================================================= 4112 dvbRcsRtnConfigGroup OBJECT-GROUP 4113 OBJECTS { 4114 dvbRcsRtnConfigDefIfLevel 4115 } 4116 STATUS current 4117 DESCRIPTION 4118 "A collection of objects providing basic return link 4119 configuration support." 4120 ::= {dvbRcsRcstGroups 17} 4122 dvbRcsRtnExtConfigGroup OBJECT-GROUP 4123 OBJECTS { 4124 dvbRcsRtnConfigMaxEirp 4125 } 4126 STATUS current 4127 DESCRIPTION 4128 "A collection of objects providing extended return link 4129 configuration support." 4130 ::= {dvbRcsRcstGroups 18} 4132 dvbRcsRtnStatusGroup OBJECT-GROUP 4133 OBJECTS { 4134 dvbRcsRtnStatusPayloadUnit 4135 } 4136 STATUS current 4137 DESCRIPTION 4138 "A collection of objects allowing access to return link 4139 status." 4140 ::= {dvbRcsRcstGroups 19} 4142 dvbRcsRtnExtStatusGroup OBJECT-GROUP 4143 OBJECTS { 4144 dvbRcsRcstRtnLinkStatus, 4145 dvbRcsRtnStatusEbN0, 4146 dvbRcsRtnStatusSFDuration 4147 } 4148 STATUS current 4149 DESCRIPTION 4150 "A collection of objects allowing access to extended 4151 return link status." 4152 ::= {dvbRcsRcstGroups 20} 4154 dvbRcsRcstOduListGroup OBJECT-GROUP 4155 OBJECTS { 4156 dvbRcsOduTxTypeDescription, 4157 dvbRcsOduTxType, 4158 dvbRcsOduRxTypeDescription, 4159 dvbRcsOduRxType, 4160 dvbRcsOduAntennaTypeDescription, 4161 dvbRcsOduAntennaType 4162 } 4163 STATUS current 4164 DESCRIPTION 4165 "A collection of objects supporting flexible 4166 selection of ODU devices." 4167 ::= {dvbRcsRcstGroups 21} 4169 END 4171 XXX NOTE: RFC Editor please amend the lines below to reflect 4172 copyright policy for publication of MIBs. 4174 Copyright (c) 2009 IETF Trust and the persons identified as 4175 authors of the code. All rights reserved. 4177 Redistribution and use in source and binary forms, with or 4178 without modification, are permitted provided that the following 4179 conditions are met: 4181 * Redistributions of source code must retain the above copyright 4182 notice, this list of conditions and the following disclaimer. 4184 * Redistributions in binary form must reproduce the above 4185 copyright notice, this list of conditions and the following 4186 disclaimer in the documentation and/or other materials provided 4187 with the distribution. 4189 * Neither the name of Internet Society, IETF or IETF Trust, nor 4190 the names of specific contributors, may be used to endorse or 4191 promote products derived from this software without specific 4192 prior written permission. 4194 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 4195 CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, 4196 INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 4197 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 4198 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR 4199 CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4200 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4201 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF 4202 USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 4203 AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 4204 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 4205 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 4206 THE POSSIBILITY OF SUCH DAMAGE. 4208 5. Security Considerations 4210 This MIB module relates to a system that allows end-users to 4211 access a private network or public internet access. As such, 4212 improper manipulation of the MIB objects represented by this MIB 4213 module may result in denial of service to a large number of end- 4214 users. 4216 There are a number of management objects defined in this MIB 4217 module with a MAX-ACCESS clause of read-write and/or read- 4218 create. Such objects may be considered sensitive or vulnerable 4219 in some network environments. The support for SET operations in 4220 a non-secure environment without proper protection can have a 4221 negative effect on network operations. These are the tables and 4222 objects and their sensitivity/vulnerability: 4224 o The use of the dvbRcsNetworkNccMgtInetAddress object to 4225 specify management stations is considered only limited 4226 protection and does not protect against attacks that spoof 4227 the management station's IP address. The use of stronger 4228 mechanisms, such as SNMPv3 security, should be considered, 4229 where possible. 4231 o The dvbRcsSystemOdu objects, dvbRcsCtrlCwEnable, 4232 dvbRcsRtnConfigMaxEirp, dvbRcsRtnConfigDefIfLevel objects and 4233 dvbRcsRcstInstall sub-tree can, if improperly or maliciously 4234 used, lead to unwanted emissions or emission levels on the 4235 satellite uplink, thereby resulting in potential degradation 4236 of the RCS service or other services using the frequency band 4237 being used. 4239 o The RCST may have its configuration file changed by the 4240 actions of the management system using a combination of the 4241 following objects: dvbRcsNetworkInstallLogFileDownloadUrl, 4242 dvbRcsCtrlDownloadFileCommand, 4243 dvbRcsCtrlActivateConfigFileCommand or 4244 dvbRcsCtrlRebootCommand. An improper configuration file 4245 download may result in substantial vulnerabilities and the 4246 loss of the ability of the management system to control the 4247 satellite terminal. 4249 o Setting dvbRcsNetworkLogFileUploadUrl to a wrong address may 4250 potentially impact debugging/troubleshooting efforts. 4252 o Setting objects in dvbRcsPktClassTable could cause 4253 significant changes to default traffic filtering on a RCST. 4255 Some of the readable objects in this MIB module (i.e., objects 4256 with a MAX-ACCESS other than not-accessible) may be considered 4257 sensitive or vulnerable in some network environments. It is 4258 thus important to control even GET access to these objects and 4259 possibly to even encrypt the values of these objects when 4260 sending them over the network via SNMP. These are the tables and 4261 objects and their sensitivity/vulnerability: 4263 o The dvbRcsNetworkNccMgtInetAddress object may provide 4264 sufficient information for attackers to spoof management 4265 stations that have management access to the device. 4267 o The dvbRcsRcstCurrentSoftwareVersion object may provide hints 4268 as to the software vulnerabilities of the cable device. 4270 o The object dvbRcsNetworkOamInetAddress and the table 4271 dvbRcsPktClassTable may provide clues for attacking the cable 4272 device and other subscriber devices. 4274 SNMP versions prior to SNMPv3 did not include adequate security. 4275 Even if the network itself is secure (for example by using 4276 IPsec), even then, there is no control as to who on the secure 4277 network is allowed to access and GET/SET 4278 (read/change/create/delete) the objects in this MIB module. 4280 It is RECOMMENDED that implementers consider the security 4281 features provided by the SNMPv3 framework (see [RFC3410], 4282 section 8), including full support for the SNMPv3 cryptographic 4283 mechanisms (for authentication and privacy). 4285 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4286 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4287 enable cryptographic security. It is then a customer/operator 4288 responsibility to ensure that the SNMP entity giving access to 4289 an instance of this MIB module, is properly configured to give 4290 access to the objects only to those principals (users) that have 4291 legitimate rights to indeed GET or SET (change/create/delete) 4292 them. 4294 6. IANA Considerations 4296 This document includes no request to IANA. The transmission and 4297 ifType numbers described in Section 3 have already been assigned 4298 under the smi-numbers registry. 4300 7. Acknowledgments 4302 The authors thank Gorry Fairhurst for advice in the preparation 4303 of this document. 4305 The authors recognize this document is a collective effort of 4306 the SatLabs Group (www.satlabs.org), in particular the many 4307 corrections and suggestions brought by Juan Luis Manas. 4309 8. References 4311 8.1. Normative References 4313 [IANA] Internet Assigned Numbers Authority, "Internet 4314 Assigned Numbers Authority", June 2008, 4315 . 4317 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4318 Requirement Levels", BCP 14, RFC 2119, March 1997 4319 (BEST CURRENT PRACTICE). 4321 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4322 Schoenwaelder, Ed., "Structure of Management 4323 Information, Version 2 (SMIv2)", STD 58, RFC 2578, 4324 April 1999. 4326 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4327 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 4328 STD 58, RFC 2579, April 1999. 4330 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 4331 "Conformance Statements for SMIv2", STD 58, RFC 2580, 4332 April 1999. 4334 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group 4335 MIB", RFC 2863, June 2000. 4337 8.2. Informative References 4339 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 4340 Generic Coding of Moving Pictures and Associated Audio 4341 Information Systems", International Standardisation 4342 Organisation (ISO). 4344 [ITU-ATM] ITU-T Recommendation I.432 (all parts): "B-ISDN user- 4345 network interface - Physical layer specification". 4347 [ITU-AAL5] ITU-T Recommendation I.363-5 (1996): "B-ISDN ATM 4348 Adaptation Layer specification: Type 5 AAL". 4350 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 4351 Specifications for Data Broadcasting", European 4352 Telecommunications Standards Institute (ETSI). 4354 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); 4355 Modulation and Coding for DBS satellite systems at 4356 11/12 GHz", European Telecommunications Standards 4357 Institute (ETSI). 4359 [ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB); 4360 Second generation framing structure, channel coding 4361 and modulation systems for Broadcasting, Interactive 4362 Services, News Gathering and other broadband satellite 4363 applications", European Telecommunications Standards 4364 Institute (ETSI). 4366 [ETSI-GSE] ETSI TS 102 606 "Digital Video Broadcasting (DVB); 4367 Generic Stream Encapsulation (GSE) Protocol", European 4368 Telecommunications Standards Institute (ETSI). 4370 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 4371 Interaction Channel for Satellite Distribution 4372 Systems", European Telecommunications Standards 4373 Institute (ETSI). 4375 [ETSI-SI] ETSI EN 300 468 "Digital Video Broadcasting (DVB); 4376 Specification for Service Information (SI) in DVB 4377 Systems", European Telecommunications Standards 4378 Institute (ETSI). 4380 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 4381 "Introduction and Applicability Statements for 4382 Internet-Standard Management Framework", RFC 3410, 4383 December 2002. 4385 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- 4386 Nocker, B., and H. Linder, "A Framework for 4387 Transmission of IP Datagrams over MPEG-2 Networks", 4388 RFC 4259, November 2005. 4390 [SATLABS] SatLabs System Recommendations. Available at 4391 www.satlabs.org. 4393 9. Authors' Addresses 4395 Stephane Combes 4396 ESTEC 4397 European Space Agency 4398 Keplerlaan 1 4399 P.O. Box 299 4400 2200 AG Noordwijk ZH 4401 The Netherlands 4403 Email: stephane.combes@esa.int 4404 URL: telecom.esa.int 4406 Petter Chr. Amundsen 4407 VeriSat AS 4408 P.O Box 1 4409 1330 Fornebu 4410 Norway 4412 Email: pca@verisat.no 4413 URL: www.verisat.no 4415 Micheline Lambert 4416 Advantech Satellite Networks 4417 2341 boul. Alfred-Nobel 4418 Saint-Laurent (Montreal) 4419 H4S 2A9 4420 Quebec, Canada 4422 Email: micheline.lambert@advantechamt.com 4423 URL: www.advantechsatnet.com 4425 Hans-Peter Lexow 4426 STM Norway 4427 Vollsveien 21 4428 1366 Lysaker 4429 Norway 4431 Email: hlexow@stmi.com 4432 URL: www.stmi.com 4434 10. Disclaimer 4436 This document may contain material from IETF Documents or IETF 4437 Contributions published or made publicly available before 4438 November 10, 2008. The person(s) controlling the copyright in 4439 some of this material may not have granted the IETF Trust the 4440 right to allow modifications of such material outside the IETF 4441 Standards Process. 4442 Without obtaining an adequate license from the person(s) 4443 controlling the copyright in such materials, this document may 4444 not be modified outside the IETF Standards Process, and 4445 derivative works of it may not be created outside the IETF 4446 Standards Process, except to format it for publication as an RFC 4447 or to translate it into languages other than English. 4449 11. Copyright Notice 4451 Copyright (c) 2009 IETF Trust and the persons identified as the 4452 document authors. All rights reserved. 4454 This document is subject to BCP 78 and the IETF Trust's Legal 4455 Provisions Relating to IETF Documents in effect on the date of 4456 publication of this document (http://trustee.ietf.org/license- 4457 info). Please review these documents carefully, as they 4458 describe your rights and restrictions with respect to this 4459 document. 4461 11.1. License for Code Components 4463 XXX NOTE: RFC Editor please amend the lines below to reflect 4464 copyright policy for publication of MIBs. 4466 A copyright note for the Code Components is provided at the end 4467 of Section 4. In addition to the licenses granted above, Code 4468 Components are also licensed to each person who wishes to 4469 receive such a license on the terms of the "BSD License", as 4470 described below. The Legal Provisions are specified in the IETF 4471 Trust's Legal Provisions Relating to IETF Documents in effect on 4472 the date of publication of this document 4473 (http://trustee.ietf.org/license-info). 4474 <<< RFC Ed Note: please remove the text below, prior to 4475 publications >>> 4477 Change Log. 4479 Rev -00 4481 * First draft, for comment by the community. 4483 Rev -01 4485 * Second draft, for comment by the community. 4487 The MIB module is renamed DVBRCS-MIB to reflect that it covers 4488 more than solely interface issues. 4490 The MIB has been updated with 4492 * a conformance section that captures the options 4494 * structural changes and corrections to achieve this 4496 * SYNTAX refinements where applicable 4498 * UNITS declarations where applicable 4500 Document reformatted to conform to I-D format conventions. 4502 Rev -02 4504 * Third draft, for comment by the community. 4506 Update following comments received from the ipdvb list (Gorry 4507 Fairhurst). 4509 Rev -03 4511 * Fourth draft, for comment by the community. 4513 Update following comments received from Martin Stiemerling and 4514 complement/corrections from the SatLabs Group. 4516 Rev -04 4517 * Fifth draft 4519 Corrected read-write into read-create MAXACCESS for objects in 4520 requestClassTable and pidPoolTable. 4522 Minor updates to correct format of tables and some MIB comments. 4524 Rev -05 4526 * Sixth draft 4528 Addition of dvbRcs prefix to all descriptors, following request 4529 from MIB doctor (according to Appendix C of RFC 4181). 4531 Clarification and complements brought to ODU configuration 4532 objects (see section 3.4.1), ODU structural entities definition in 4533 dvbRcsRcstSystem group and conformance section. 4535 Modification of the interface types usage (section 3.3) in order 4536 to have alignment with Ethernet interface (dvbRcsMacLayer should 4537 count link layer packets and bytes, like Ethernet does, and not 4538 IP). 4540 Updated copyright to reflect current IETF Trust guidelines and 4541 advice from Dan Romascanu. 4543 Rev -06 4545 * Seventh draft 4547 Updated following MIB doctor review. Adjustments based on the 4548 MIB authoring guidelines from the IETF: 4549 o I-D renamed 4551 o Used name instead of number for DEFVAL where appropriate 4553 o Clarification added in the MIB module description regarding 4554 persistency behavior of objects 4556 o Integer32 replaced with Unsigned32 where appropriate 4558 o Obsoleted OBJECT-TYPES (DisplayString, IpAddress) replaced 4559 with SnmpAdminString, RFC 4001 and RFC 5017 TCs. Added 4560 conformance statements mandating IPv4 support only. 4562 o Clarification of the conformance clauses added in the MODULE- 4563 COMPLIANCE description and the following GROUPs and OBJECTs 4564 descriptions. 4566 o Re-organization of some conformance groups. Each group now 4567 refers to precise options or features. 5 new features 4568 (specified through dvbRcsSystemSatLabsFeaturesDeclaration 4569 object) are therefore defined: ODULIST, EXTNETWORK, 4570 EXTCONTROL, EXTCONFIG, EXTSTATUS. 4572 o Clarification in the RowStatus OBJECTs description whether 4573 writable objects in the dynamically created rows can change 4574 value while the RowStatus object is active. 4576 o Security section expanded. 4578 <<>