idnits 2.17.1 draft-combes-ipdvb-mib-rcs-07.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 5 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 (October 7, 2009) is 5286 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 7 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: April 2010 October 7, 2009 9 The SatLabs Group DVB-RCS MIB 10 draft-combes-ipdvb-mib-rcs-07.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 April 7,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...................................102 97 6. IANA Considerations.......................................104 98 7. Acknowledgments...........................................105 99 8. References................................................105 100 8.1. Normative References.................................105 101 8.2. Informative References...............................106 102 9. Authors' Addresses........................................108 103 10. Disclaimer...............................................109 104 11. Copyright Notice.........................................109 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] 943 Dscp, 944 DscpOrAny 945 FROM DIFFSERV-DSCP-TC -- [RFC3289] 946 ; 948 dvbRcsMib MODULE-IDENTITY 949 LAST-UPDATED "200907201200Z" 950 ORGANIZATION "The SatLabs Group" 951 CONTACT-INFO 952 "The SatLabs Group 953 Web: www.satlabs.org 954 E-mail: info@satlabs.org" 955 DESCRIPTION 956 "DVB-RCS MIB subtree. 958 This MIB module applies to equipment that is a Return 959 Channel Satellite Terminal (RCST) defined in the Digital 960 Video Broadcasting Return Channel via Satellite system 961 (DVB-RCS) standard (ETSI EN 301 791 Digital Video 962 Broadcasting (DVB); Interaction Channel for Satellite 963 Distribution Systems, European Telecommunications 964 Standards Institute (ETSI)). 965 It defines a set of MIB entities to characterise the 966 behaviour and performance of network layer entities 967 implementing DVB-RCS. 968 This MIB module is intended to be used by DVB-RCS 969 equipment following the SatLabs System Recommendations, 970 defined by the SatLabs Group and available at 971 www.satlabs.org. 972 Note that, if not stated otherwise in the object 973 DESCRIPTION clause, all writable objects are 974 persistent." 975 REVISION "200907201200Z" 976 DESCRIPTION 977 "Revision of this MIB module, following MIB doctor review 978 and adjustments based on the MIB authoring guidelines 979 from the IETF." 980 ::= { transmission 239 } 982 --============================================================== 983 -- Textual Conventions 984 --============================================================== 986 DvbRcsSatLabsProfileMap ::= TEXTUAL-CONVENTION 987 STATUS current 988 DESCRIPTION 989 "This textual convention enumerates the declaration of 990 the SatLabs defined terminal profiles. The mapping to 991 the profiles is to be understood as described here. (0) 992 refers to the most significant bit. 994 dvbs(0) -> DVBS profile (DVB-S support) 995 dvbs2ccm(1) -> DVB-S2 CCM profile (CCM support) 996 dvbs2acm(2) -> DVB-S2 ACM profile (CCM, VCM and ACM 997 support)" 998 REFERENCE 999 "SatLabs System Recommendations available at 1000 www.satlabs.org" 1001 SYNTAX BITS { 1002 dvbs(0), 1003 dvbs2ccm(1), 1004 dvbs2acm(2), 1005 spare1(3), 1006 spare2(4), 1007 spare3(5), 1008 spare4(6), 1009 spare5(7), 1010 spare6(8), 1011 spare7(9), 1012 spare8(10), 1013 spare9(11), 1014 spare10(12), 1015 spare11(13), 1016 spare12(14), 1017 spare13(15), 1018 spare14(16), 1019 spare15(17), 1020 spare16(18), 1021 spare17(19), 1022 spare18(20), 1023 spare19(21), 1024 spare20(22), 1025 spare21(23), 1026 spare22(24), 1027 spare23(25), 1028 spare24(26), 1029 spare25(27), 1030 spare26(28), 1031 spare27(29), 1032 spare28(30), 1033 spare29(31) 1034 } 1036 DvbRcsSatLabsOptionMap ::= TEXTUAL-CONVENTION 1037 STATUS current 1038 DESCRIPTION 1039 "This textual convention enumerates the declaration of 1040 the SatLabs defined options. A value of 1 indicates 1041 that the respective option is supported. The mapping 1042 to the options is to be understood as described here. 1043 (0) refers to the most significant bit. 1045 mpegTrf(0) -> MPEG_TRF 1046 coarseSync(1) -> COARSE_SYNC 1047 wideHop(2) -> WIDE_HOPP 1048 fastHop(3) -> FAST_HOPP 1049 dynamicMfTdma(4) -> Dynamic_MF_TDMA 1050 contentionSync(5) -> CONTENTION_SYNC 1051 qpskLow(6) -> QPSKLOW 1052 mod16Apsk(7) -> 16APSK 1053 mod32Apsk(8) -> 32APSK 1054 normalFec(9) -> NORMALFEC 1055 multiTs(10) -> MULTITS 1056 gsTs(11) -> GSTS 1057 enhQoS(12) -> ENHQOS 1058 pep(13) -> PEP 1059 http(14) -> HTTP 1060 ftp(15) -> FTP 1061 dns(16) -> DNS 1062 chIdStrict(17) -> CHID_STRICT 1063 nlid(18) -> NLID 1064 snmpMisc(19) -> SNMPMISC 1066 The support of specific options mandates the support of 1067 specific objects and access levels." 1068 REFERENCE 1069 "SatLabs System Recommendations available at 1070 www.satlabs.org" 1071 SYNTAX BITS { 1072 mpegTrf(0), 1073 coarseSync(1), 1074 wideHop(2), 1075 fastHop(3), 1076 dynamicMfTdma(4), 1077 contentionSync(5), 1078 qpskLow(6), 1079 mod16Apsk(7), 1080 mod32Apsk(8), 1081 normalFec(9), 1082 multiTs(10), 1083 gsTs(11), 1084 enhQoS(12), 1085 pep(13), 1086 http(14), 1087 ftp(15), 1088 dns(16), 1089 chIdStrict(17), 1090 nlid(18), 1091 snmpMisc(19), 1092 spare1(20), 1093 spare2(21), 1094 spare3(22), 1095 spare4(23), 1096 spare5(24), 1097 spare6(25), 1098 spare7(26), 1099 spare8(27), 1100 spare9(28), 1101 spare10(29), 1102 spare11(30), 1103 spare12(31) 1104 } 1106 DvbRcsSatLabsFeatureMap ::= TEXTUAL-CONVENTION 1107 STATUS current 1108 DESCRIPTION 1109 "This textual convention enumerates the declaration 1110 of the SatLabs specified compatibility and 1111 configuration features. A value of 1 indicates that 1112 the respective feature is supported. The mapping to 1113 the features is to be understood as described here. 1114 (0) refers to the most significant bit. 1116 rcstPara(0) -> RCST_PARA feature 1117 installLog(1) -> INSTALL_LOG feature 1118 enhClassifier(2) -> ENHCLASSIFIER feature 1119 routeId(3) -> ROUTE_ID feature 1120 oduList(4) -> ODULIST feature 1121 extNetwork(5) -> EXTNETWORK feature 1122 extControl(6) -> EXTCONTROL feature 1123 extConfig(7) -> EXTCONFIG feature 1124 extStatus(8) -> EXTSTATUS feature 1126 The support of specific features mandates the support of 1127 specific objects and access levels." 1128 REFERENCE 1129 "SatLabs System Recommendations available at 1130 www.satlabs.org" 1131 SYNTAX BITS { 1132 rcstPara(0), 1133 installLog(1), 1134 enhClassifier(2), 1135 routeId(3), 1136 oduList(4), 1137 extNetwork(5), 1138 extControl(6), 1139 extConfig(7), 1140 extStatus(8), 1141 spare6(9), 1142 spare7(10), 1143 spare8(11), 1144 spare9(12), 1145 spare10(13), 1146 spare11(14), 1147 spare12(15), 1148 spare13(16), 1149 spare14(17), 1150 spare15(18), 1151 spare16(19), 1152 spare17(20), 1153 spare18(21), 1154 spare19(22), 1155 spare20(23), 1156 spare21(24), 1157 spare22(25), 1158 spare23(26), 1159 spare24(27), 1160 spare25(28), 1161 spare26(29), 1162 spare27(30), 1163 spare28(31) 1164 } 1166 --============================================================== 1167 -- object type definitions 1168 --============================================================== 1169 dvbRcsMibObjects OBJECT IDENTIFIER ::= {dvbRcsMib 1} 1170 dvbRcsConformance OBJECT IDENTIFIER ::= {dvbRcsMib 2} 1172 dvbRcsRcst OBJECT IDENTIFIER ::= {dvbRcsMibObjects 1} 1173 dvbRcsFwdLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 2} 1174 dvbRcsRtnLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 3} 1176 dvbRcsRcstSystem OBJECT IDENTIFIER ::= {dvbRcsRcst 1} 1177 dvbRcsRcstNetwork OBJECT IDENTIFIER ::= {dvbRcsRcst 2} 1178 dvbRcsRcstInstall OBJECT IDENTIFIER ::= {dvbRcsRcst 3} 1179 dvbRcsRcstQos OBJECT IDENTIFIER ::= {dvbRcsRcst 4} 1180 dvbRcsRcstControl OBJECT IDENTIFIER ::= {dvbRcsRcst 5} 1181 dvbRcsRcstState OBJECT IDENTIFIER ::= {dvbRcsRcst 6} 1183 dvbRcsFwdConfig OBJECT IDENTIFIER ::= {dvbRcsFwdLink 1} 1184 dvbRcsFwdStatus OBJECT IDENTIFIER ::= {dvbRcsFwdLink 2} 1186 dvbRcsRtnConfig OBJECT IDENTIFIER ::= {dvbRcsRtnLink 1} 1187 dvbRcsRtnStatus OBJECT IDENTIFIER ::= {dvbRcsRtnLink 2} 1189 --============================================================== 1190 -- dvbRcsRcstSystem sub-tree object types 1191 --============================================================== 1192 dvbRcsSystemMibRevision OBJECT-TYPE 1193 SYNTAX SnmpAdminString 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "This object allows the SNMP agent to report the 1198 implemented MIB module revision. 1199 The supported REVISION of this module is reported." 1200 ::= {dvbRcsRcstSystem 1} 1202 --============================================================== 1203 -- Options declared according to the textual conventions 1204 --============================================================== 1205 dvbRcsSystemSatLabsProfilesDeclaration OBJECT-TYPE 1206 SYNTAX DvbRcsSatLabsProfileMap 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "Indicates the SatLabs profiles supported as defined in 1211 the SatLabs System Recommendations." 1212 ::= {dvbRcsRcstSystem 2} 1214 dvbRcsSystemSatLabsOptionsDeclaration OBJECT-TYPE 1215 SYNTAX DvbRcsSatLabsOptionMap 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "Indicates the SatLabs options supported as defined in 1220 the SatLabs System Recommendations." 1221 ::= {dvbRcsRcstSystem 3} 1223 dvbRcsSystemSatLabsFeaturesDeclaration OBJECT-TYPE 1224 SYNTAX DvbRcsSatLabsFeatureMap 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "Indicates the optional compatibility features and minor 1229 options supported as defined in the SatLabs System 1230 Recommendations." 1231 ::= {dvbRcsRcstSystem 4} 1233 dvbRcsSystemLocation OBJECT-TYPE 1234 SYNTAX SnmpAdminString 1235 MAX-ACCESS read-write 1236 STATUS current 1237 DESCRIPTION 1238 "Physical location of the ODU antenna expressed as 1239 Longitude, Latitude and Altitude. The string 1240 shall have 31 characters in the following format: 1241 ,,,,,M 1242 where x, y and z represents digits, 1243 a=N or S, 1244 b=E or W, 1245 Reading the digits from left to right: 1246 'x' 7 latitude digits; x digits 1-2 contain the 1247 degrees, x digits 3-7 contain the minutes in decimal; 1248 'y' 8 longitude digits; y digits 1-3 contain the 1249 degrees, y digits 4-8 contain the minutes in decimal; 1250 'z' 5 altitude digits; meters above sea level in 1251 decimal; 1252 '.' is the decimal point; 1253 ',' is the field separator; 1254 'M' is the indicator for altitude meters. 1256 This format is a modified subset of the NMEA 0183 1257 (National Marine Electronics Association, Interface 1258 Standard) format for Global Positioning System Fix 1259 Data. 1261 This location and the satellite position are used to 1262 calculate the RCST-satellite path delay. 1264 Note: The system.sysLocation object of MIB-II provides 1265 physical location of the IDU unit." 1266 ::= {dvbRcsRcstSystem 5} 1268 dvbRcsSystemOduAntennaSize OBJECT-TYPE 1269 SYNTAX Unsigned32 1270 UNITS "cm" 1271 MAX-ACCESS read-write 1272 STATUS current 1273 DESCRIPTION 1274 "Diameter of the antenna." 1275 ::= {dvbRcsRcstSystem 6} 1277 dvbRcsSystemOduAntennaGain OBJECT-TYPE 1278 SYNTAX Unsigned32 1279 UNITS "x0.1 dBi" 1280 MAX-ACCESS read-write 1281 STATUS current 1282 DESCRIPTION 1283 "Antenna peak gain of the ODU." 1284 ::= {dvbRcsRcstSystem 7} 1285 dvbRcsSystemOduSspa OBJECT-TYPE 1286 SYNTAX Unsigned32 1287 UNITS "x0.1 W" 1288 MAX-ACCESS read-write 1289 STATUS current 1290 DESCRIPTION 1291 "Power level of the Solid State Power Amplifier 1292 installed in the ODU." 1293 ::= {dvbRcsRcstSystem 8} 1295 dvbRcsSystemOduTxType OBJECT-TYPE 1296 SYNTAX SnmpAdminString 1297 MAX-ACCESS read-write 1298 STATUS current 1299 DESCRIPTION 1300 "Type of transmitter installed in the ODU." 1301 ::= {dvbRcsRcstSystem 9} 1303 dvbRcsSystemOduRxType OBJECT-TYPE 1304 SYNTAX SnmpAdminString 1305 MAX-ACCESS read-write 1306 STATUS current 1307 DESCRIPTION 1308 "Type of LNB installed in the ODU, with 1309 information such as vendor type, output type (single, 1310 twin, quad,...), etc." 1311 ::= {dvbRcsRcstSystem 10} 1313 dvbRcsSystemOduRxBand OBJECT-TYPE 1314 SYNTAX INTEGER { 1315 oduHighRxBand (0), 1316 oduLowRxBand (1) 1317 } 1318 MAX-ACCESS read-write 1319 STATUS current 1320 DESCRIPTION 1321 "LNB High-Band/Low-Band selector. High Band corresponds 1322 to the emission of a 18-26 kHz tone with 0.4-0.8 Vpp in 1323 the Rx IFL cable: 1324 (0) - High Band 1325 (1) - Low Band" 1326 ::= {dvbRcsRcstSystem 11} 1328 dvbRcsSystemOduRxLO OBJECT-TYPE 1329 SYNTAX Unsigned32 1330 UNITS "x100 Hz" 1331 MAX-ACCESS read-write 1332 STATUS current 1333 DESCRIPTION 1334 "Frequency of LNB Local Oscillator (in 100 Hz)" 1335 ::= {dvbRcsRcstSystem 12} 1337 dvbRcsSystemOduTxLO OBJECT-TYPE 1338 SYNTAX Unsigned32 1339 UNITS "x100 Hz" 1340 MAX-ACCESS read-write 1341 STATUS current 1342 DESCRIPTION 1343 "Frequency of Block Up-Converter Local Oscillator 1344 (in 100 Hz)." 1345 ::= {dvbRcsRcstSystem 13} 1347 dvbRcsSystemIduPep OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 14} 1349 dvbRcsTcpPep OBJECT-TYPE 1350 SYNTAX INTEGER{ 1351 disabled (0), 1352 enabled (1) 1353 } 1354 MAX-ACCESS read-write 1355 STATUS current 1356 DESCRIPTION 1357 "Status and control of embedded TCP PEP. 1358 0 - disabled or not implemented 1359 1 - enabled" 1360 ::={dvbRcsSystemIduPep 1} 1362 dvbRcsHttpPep OBJECT-TYPE 1363 SYNTAX INTEGER{ 1364 disabled (0), 1365 enabled (1) 1366 } 1367 MAX-ACCESS read-write 1368 STATUS current 1369 DESCRIPTION 1370 "Status and control of embedded HTTP PEP. 1371 0 - disabled or not implemented 1372 1 - enabled" 1373 ::={dvbRcsSystemIduPep 2} 1375 --============================================================== 1376 -- ODU structural entities 1377 --============================================================== 1379 dvbRcsOduTx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 15} 1380 dvbRcsOduRx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 16} 1381 dvbRcsOduAntenna OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 17} 1383 --============================================================== 1384 -- ODU BUC 1385 --============================================================== 1387 dvbRcsOduTxTypeTable OBJECT-TYPE 1388 SYNTAX SEQUENCE OF DvbRcsOduTxTypeEntry 1389 MAX-ACCESS not-accessible 1390 STATUS current 1391 DESCRIPTION 1392 "This table contains the identification of each well- 1393 known BUC type supported by the IDU, and provides its 1394 associated index." 1395 ::={dvbRcsOduTx 1} 1397 dvbRcsOduTxTypeEntry OBJECT-TYPE 1398 SYNTAX DvbRcsOduTxTypeEntry 1399 MAX-ACCESS not-accessible 1400 STATUS current 1401 DESCRIPTION 1402 "An entry in the BUC type table." 1403 INDEX { dvbRcsOduTxTypeIndex } 1404 ::={dvbRcsOduTxTypeTable 1} 1406 DvbRcsOduTxTypeEntry ::= SEQUENCE { 1407 dvbRcsOduTxTypeIndex Unsigned32, 1408 dvbRcsOduTxTypeDescription SnmpAdminString 1409 } 1411 dvbRcsOduTxTypeIndex OBJECT-TYPE 1412 SYNTAX Unsigned32 (1..32) 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "Index for the BUC type." 1417 ::={dvbRcsOduTxTypeEntry 1} 1419 dvbRcsOduTxTypeDescription OBJECT-TYPE 1420 SYNTAX SnmpAdminString 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "Text based identification of a BUC type." 1425 ::={dvbRcsOduTxTypeEntry 2} 1427 dvbRcsOduTxType OBJECT-TYPE 1428 SYNTAX Unsigned32 1429 MAX-ACCESS read-write 1430 STATUS current 1431 DESCRIPTION 1432 "Index of the selected BUC type." 1433 ::={dvbRcsOduTx 2} 1435 --============================================================== 1436 -- ODU LNB 1437 --============================================================== 1439 dvbRcsOduRxTypeTable OBJECT-TYPE 1440 SYNTAX SEQUENCE OF DvbRcsOduRxTypeEntry 1441 MAX-ACCESS not-accessible 1442 STATUS current 1443 DESCRIPTION 1444 "This table contains the identification of each well- 1445 known LNB type supported by the IDU, and provides its 1446 associated index." 1447 ::={dvbRcsOduRx 1} 1448 dvbRcsOduRxTypeEntry OBJECT-TYPE 1449 SYNTAX DvbRcsOduRxTypeEntry 1450 MAX-ACCESS not-accessible 1451 STATUS current 1452 DESCRIPTION 1453 "An entry in the LNB type table." 1454 INDEX { dvbRcsOduRxTypeIndex } 1455 ::={dvbRcsOduRxTypeTable 1} 1457 DvbRcsOduRxTypeEntry ::= SEQUENCE { 1458 dvbRcsOduRxTypeIndex Unsigned32, 1459 dvbRcsOduRxTypeDescription SnmpAdminString 1460 } 1462 dvbRcsOduRxTypeIndex OBJECT-TYPE 1463 SYNTAX Unsigned32 (1..32) 1464 MAX-ACCESS not-accessible 1465 STATUS current 1466 DESCRIPTION 1467 "Index for the LNB type." 1468 ::={dvbRcsOduRxTypeEntry 1} 1470 dvbRcsOduRxTypeDescription OBJECT-TYPE 1471 SYNTAX SnmpAdminString 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "Text based identification of an LNB type." 1476 ::={dvbRcsOduRxTypeEntry 2} 1478 dvbRcsOduRxType OBJECT-TYPE 1479 SYNTAX Unsigned32 1480 MAX-ACCESS read-write 1481 STATUS current 1482 DESCRIPTION 1483 "Index of the selected LNB type." 1484 ::={dvbRcsOduRx 2} 1486 --============================================================== 1487 -- ODU Antenna 1488 --============================================================== 1490 dvbRcsOduAntennaTypeTable OBJECT-TYPE 1491 SYNTAX SEQUENCE OF DvbRcsOduAntennaTypeEntry 1492 MAX-ACCESS not-accessible 1493 STATUS current 1494 DESCRIPTION 1495 "This table contains the identification of each well- 1496 known antenna type supported by the IDU, and provides 1497 its associated index." 1498 ::={dvbRcsOduAntenna 1} 1500 dvbRcsOduAntennaTypeEntry OBJECT-TYPE 1501 SYNTAX DvbRcsOduAntennaTypeEntry 1502 MAX-ACCESS not-accessible 1503 STATUS current 1504 DESCRIPTION 1505 "An entry in the antenna type table." 1506 INDEX { dvbRcsOduAntennaTypeIndex } 1507 ::={dvbRcsOduAntennaTypeTable 1} 1509 DvbRcsOduAntennaTypeEntry ::= SEQUENCE { 1510 dvbRcsOduAntennaTypeIndex Unsigned32, 1511 dvbRcsOduAntennaTypeDescription SnmpAdminString 1512 } 1514 dvbRcsOduAntennaTypeIndex OBJECT-TYPE 1515 SYNTAX Unsigned32 (1..32) 1516 MAX-ACCESS not-accessible 1517 STATUS current 1518 DESCRIPTION 1519 "Index for the antenna type." 1520 ::={dvbRcsOduAntennaTypeEntry 1} 1522 dvbRcsOduAntennaTypeDescription OBJECT-TYPE 1523 SYNTAX SnmpAdminString 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "Text based identification of an antenna type." 1528 ::={dvbRcsOduAntennaTypeEntry 2} 1529 dvbRcsOduAntennaType OBJECT-TYPE 1530 SYNTAX Unsigned32 1531 MAX-ACCESS read-write 1532 STATUS current 1533 DESCRIPTION 1534 "Index of the selected antenna type." 1535 ::={dvbRcsOduAntenna 2} 1537 --============================================================== 1538 -- dvbRcsRcstNetwork sub-tree object types 1539 --============================================================== 1541 dvbRcsNetworkOamInetAddressType OBJECT-TYPE 1542 SYNTAX InetAddressType 1543 MAX-ACCESS read-write 1544 STATUS current 1545 DESCRIPTION 1546 "The type of internet address of 1547 dvbRcsNetworkOamInetAddress. 1548 If the terminal OAM Internet address is unassigned or 1549 unknown, then the value of this object is unknown(0)." 1550 ::= {dvbRcsRcstNetwork 1} 1552 dvbRcsNetworkOamInetAddress OBJECT-TYPE 1553 SYNTAX InetAddress 1554 MAX-ACCESS read-write 1555 STATUS current 1556 DESCRIPTION 1557 "OAM IP Address of the RCST. This object is used with 1558 both IP and interfaces MIB-II subgroups. It uniquely 1559 determines the interface through which OAM traffic 1560 passes. 1561 The OAM IP address may be statically or dynamically 1562 assigned. It is system dependent whether the OAM IP 1563 address and the Traffic IP address are the same address. 1564 If the terminal has no OAM Internet address assigned, or 1565 this Internet address is unknown, the value of this 1566 object is the zero-length OCTET STRING. 1567 The InetAddressType is given by the 1568 dvbRcsNetworkOamInetAddressType object. " 1570 ::= {dvbRcsRcstNetwork 2} 1572 dvbRcsNetworkOamInetAddressPrefixLength OBJECT-TYPE 1573 SYNTAX InetAddressPrefixLength 1574 MAX-ACCESS read-write 1575 STATUS current 1576 DESCRIPTION 1577 "Prefix length for the OAM IP Address. If this address 1578 prefix is unknown or does not apply, the value is zero." 1579 ::= {dvbRcsRcstNetwork 3} 1581 dvbRcsNetworkOamInetAddressAssign OBJECT-TYPE 1582 SYNTAX INTEGER { 1583 oamInetAddressStatic (1), 1584 oamInetAddressDynamic (2) 1585 } 1586 MAX-ACCESS read-write 1587 STATUS current 1588 DESCRIPTION 1589 "Identifies whether the OAM IP address is statically 1590 (1) or dynamically (2) assigned." 1591 ::= {dvbRcsRcstNetwork 4} 1593 dvbRcsNetworkLanInetAddressType OBJECT-TYPE 1594 SYNTAX InetAddressType 1595 MAX-ACCESS read-write 1596 STATUS current 1597 DESCRIPTION 1598 "The type of internet address of 1599 dvbRcsNetworkLanInetAddress. 1600 If the terminal Internet address on the LAN interface is 1601 unassigned or unknown, then the value of this object is 1602 unknown(0)." 1603 ::= {dvbRcsRcstNetwork 5} 1605 dvbRcsNetworkLanInetAddress OBJECT-TYPE 1606 SYNTAX InetAddress 1607 MAX-ACCESS read-write 1608 STATUS current 1609 DESCRIPTION 1610 "IP address of the LAN interface of the terminal. If the 1611 terminal has no Internet address assigned on the LAN 1612 interface, or this Internet address is unknown, the 1613 value of this object is the zero-length OCTET STRING. 1614 The InetAddressType is given by the 1615 dvbRcsNetworkLanInetAddressType object." 1616 ::= {dvbRcsRcstNetwork 6} 1618 dvbRcsNetworkLanInetAddressPrefixLength OBJECT-TYPE 1619 SYNTAX InetAddressPrefixLength 1620 MAX-ACCESS read-write 1621 STATUS current 1622 DESCRIPTION 1623 "Prefix length for the LAN IP Address of the terminal. 1624 If this address prefix is unknown or does not apply, the 1625 value is zero." 1626 ::= {dvbRcsRcstNetwork 7} 1628 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType 1629 OBJECT-TYPE 1630 SYNTAX InetAddressType 1631 MAX-ACCESS read-write 1632 STATUS current 1633 DESCRIPTION 1634 "The type of internet address of 1635 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress. 1636 If the default gateway Internet address is unassigned or 1637 unknown, then the value of this object is unknown(0)." 1638 ::= {dvbRcsRcstNetwork 8} 1640 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress OBJECT-TYPE 1641 SYNTAX InetAddress 1642 MAX-ACCESS read-write 1643 STATUS current 1644 DESCRIPTION 1645 "IP address of the default gateway for the air 1646 interface. If the terminal has no default gateway 1647 assigned on the air interface, or this Internet address 1648 is unknown, the value of this object is the zero-length 1649 OCTET STRING. 1650 The InetAddressType is given by the 1651 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType 1652 object." 1653 ::= {dvbRcsRcstNetwork 9} 1655 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressPrefixLength 1656 OBJECT-TYPE 1657 SYNTAX InetAddressPrefixLength 1658 MAX-ACCESS read-write 1659 STATUS current 1660 DESCRIPTION 1661 "Prefix length for the IP address of the default gateway 1662 for the air interface. 1663 If this address prefix is unknown or does not apply, the 1664 value is zero." 1665 ::= {dvbRcsRcstNetwork 10} 1667 dvbRcsNetworkDnsServers OBJECT IDENTIFIER ::= {dvbRcsRcstNetwork 1668 11} 1670 dvbRcsPrimaryDnsServerInetAddressType OBJECT-TYPE 1671 SYNTAX InetAddressType 1672 MAX-ACCESS read-write 1673 STATUS current 1674 DESCRIPTION 1675 "The type of internet address of 1676 dvbRcsPrimaryDnsServerInetAddress. If the primary DNS 1677 server Internet address is unassigned or unknown, then 1678 the value of this object is unknown(0)." 1679 ::= { dvbRcsNetworkDnsServers 1} 1681 dvbRcsPrimaryDnsServerInetAddress OBJECT-TYPE 1682 SYNTAX InetAddress 1683 MAX-ACCESS read-write 1684 STATUS current 1685 DESCRIPTION 1686 "IP address of the primary DNS server in the NCC. If 1687 the terminal has no primary DNS server assigned, or this 1688 Internet address is unknown, the value of this object is 1689 the zero-length OCTET STRING. 1690 The InetAddressType is given by the 1691 dvbRcsPrimaryDnsServerInetAddressType object." 1692 ::= {dvbRcsNetworkDnsServers 2} 1693 dvbRcsPrimaryDnsServerInetAddressPrefixLength OBJECT-TYPE 1694 SYNTAX InetAddressPrefixLength 1695 MAX-ACCESS read-write 1696 STATUS current 1697 DESCRIPTION 1698 "Prefix length for the IP address of the primary DNS 1699 server in the NCC. 1700 If this address prefix is unknown or does not apply, the 1701 value is zero." 1702 ::= { dvbRcsNetworkDnsServers 3} 1704 dvbRcsSecondaryDnsServerInetAddressType OBJECT-TYPE 1705 SYNTAX InetAddressType 1706 MAX-ACCESS read-write 1707 STATUS current 1708 DESCRIPTION 1709 "The type of internet address of 1710 dvbRcsSecondaryDnsServerInetAddress. If the secondary 1711 DNS server Internet address is unassigned or unknown, 1712 then the value of this object is unknown(0)." 1713 ::= { dvbRcsNetworkDnsServers 4} 1715 dvbRcsSecondaryDnsServerInetAddress OBJECT-TYPE 1716 SYNTAX InetAddress 1717 MAX-ACCESS read-write 1718 STATUS current 1719 DESCRIPTION 1720 "IP address of the secondary DNS server in the NCC. If 1721 the terminal has no secondary DNS server assigned, or 1722 this Internet address is unknown, the value of this 1723 object is the zero-length OCTET STRING. 1724 The InetAddressType is given by the 1725 dvbRcsSecondaryDnsServerInetAddressType object." 1726 ::= {dvbRcsNetworkDnsServers 5} 1728 dvbRcsSecondaryDnsServerInetAddressPrefixLength OBJECT-TYPE 1729 SYNTAX InetAddressPrefixLength 1730 MAX-ACCESS read-write 1731 STATUS current 1732 DESCRIPTION 1733 "Prefix length for the IP address of the secondary DNS 1734 server in the NCC. 1735 If this address prefix is unknown or does not apply, the 1736 value is zero." 1737 ::= { dvbRcsNetworkDnsServers 6} 1739 dvbRcsNetworkNccMgtInetAddressType OBJECT-TYPE 1740 SYNTAX InetAddressType 1741 MAX-ACCESS read-write 1742 STATUS current 1743 DESCRIPTION 1744 "The type of internet address of 1745 dvbRcsNetworkNccMgtInetAddress. If the management server 1746 Internet address is unassigned or unknown, then the 1747 value of this object is unknown(0)." 1748 ::= {dvbRcsRcstNetwork 12} 1750 dvbRcsNetworkNccMgtInetAddress OBJECT-TYPE 1751 SYNTAX InetAddress 1752 MAX-ACCESS read-write 1753 STATUS current 1754 DESCRIPTION 1755 "IP address of the management server in the NCC. If 1756 the terminal has no management server assigned, or this 1757 Internet address is unknown, the value of this object is 1758 the zero-length OCTET STRING. 1759 The InetAddressType is given by the 1760 dvbRcsNetworkNccMgtInetAddressType object." 1761 ::= {dvbRcsRcstNetwork 13} 1763 dvbRcsNetworkNccMgtInetAddressPrefixLength OBJECT-TYPE 1764 SYNTAX InetAddressPrefixLength 1765 MAX-ACCESS read-write 1766 STATUS current 1767 DESCRIPTION 1768 "Prefix length for the IP address of the management 1769 server in the NCC. 1770 If this address prefix is unknown or does not apply, the 1771 value is zero." 1772 ::= { dvbRcsRcstNetwork 14} 1773 dvbRcsNetworkConfigFileDownloadUrl OBJECT-TYPE 1774 SYNTAX Uri (SIZE(0..65535)) 1775 MAX-ACCESS read-write 1776 STATUS current 1777 DESCRIPTION 1778 "Full path name for the configuration file download. 1779 It includes the protocol type (tftp or ftp) and the 1780 associated server IP address or hostname. Hostname can 1781 only be used if DNS is supported by the RCST. 1782 The format of this parameter follows RFC 3986." 1783 ::= {dvbRcsRcstNetwork 15} 1785 dvbRcsNetworkInstallLogFileDownloadUrl OBJECT-TYPE 1786 SYNTAX Uri (SIZE(0..65535)) 1787 MAX-ACCESS read-write 1788 STATUS current 1789 DESCRIPTION 1790 "Full path of the installation log file to download. 1791 It includes the protocol type (tftp or ftp) and the 1792 associated server IP address or hostname. Hostname can 1793 only be used if DNS is supported by the RCST. The 1794 installation log file can be created on the installer's 1795 computer and downloaded to the RCST. 1796 The format of this parameter follows RFC 3986." 1797 ::= {dvbRcsRcstNetwork 16} 1799 dvbRcsNetworkConfigFileUploadUrl OBJECT-TYPE 1800 SYNTAX Uri(SIZE(0..65535)) 1801 MAX-ACCESS read-write 1802 STATUS current 1803 DESCRIPTION 1804 "Full path name for the configuration file upload. 1805 It includes the protocol type (tftp or ftp) and the 1806 associated server IP address or hostname. Hostname can 1807 only be used if DNS is supported by the RCST. 1808 The format of this parameter follows RFC 3986." 1809 ::= {dvbRcsRcstNetwork 17} 1811 dvbRcsNetworkLogFileUploadUrl OBJECT-TYPE 1812 SYNTAX Uri(SIZE(0..65535)) 1813 MAX-ACCESS read-write 1814 STATUS current 1815 DESCRIPTION 1816 "Full path of the event log file. It includes the 1817 protocol type (tftp or ftp) and the associated server IP 1818 address or hostname. Hostname can only be used if DNS is 1819 supported by the RCST. 1820 The format of this parameter follows RFC 3986." 1821 ::= {dvbRcsRcstNetwork 18} 1823 dvbRcsNetworkInstallLogFileUploadUrl OBJECT-TYPE 1824 SYNTAX Uri(SIZE(0..65535)) 1825 MAX-ACCESS read-write 1826 STATUS current 1827 DESCRIPTION 1828 "Full path of the installation log file. It includes the 1829 protocol type (tftp or ftp) and the associated server 1830 IP address or hostname. Hostname can only be used if DNS 1831 is supported by the RCST. The installation log file can 1832 be retrieved from the RCST by the NCC or by the 1833 installer via the LAN. 1834 The format of this parameter follows RFC 3986." 1835 ::= {dvbRcsRcstNetwork 19} 1837 --============================================================== 1838 -- dvbRcsRcstInstall sub-tree object types 1839 --============================================================== 1840 dvbRcsInstallAntennaAlignmentState OBJECT-TYPE 1841 SYNTAX INTEGER { 1842 antennaAlignmentStart (1), 1843 antennaAlignmentDeny (2), 1844 antennaAlignmentContinue(3), 1845 antennaAlignmentStop (4), 1846 antennaAlignmentSuccess (5), 1847 antennaAlignmentFail (6) 1848 } 1849 MAX-ACCESS read-write 1850 STATUS current 1851 DESCRIPTION 1852 "Indicates the alignment state of the antenna: 1853 (1)-Start; 1854 (2)-Deny; 1855 (3)-Continue; 1856 (4)-Stop; 1857 (5)-Success; 1858 (6)-Fail" 1859 ::= {dvbRcsRcstInstall 1} 1861 dvbRcsInstallCwFrequency OBJECT-TYPE 1862 SYNTAX Unsigned32 1863 UNITS "x100 Hz" 1864 MAX-ACCESS read-write 1865 STATUS current 1866 DESCRIPTION 1867 "Frequency at which the transmitted Continuous Wave 1868 carrier (in 100 Hz). 1869 Minimum required precision is 1 kHz." 1870 ::= {dvbRcsRcstInstall 2} 1872 dvbRcsInstallCwMaxDuration OBJECT-TYPE 1873 SYNTAX Unsigned32 1874 UNITS "seconds" 1875 MAX-ACCESS read-write 1876 STATUS current 1877 DESCRIPTION 1878 "Time after which the Continuous Wave carrier must be 1879 put down (in seconds)" 1880 ::= {dvbRcsRcstInstall 3} 1882 dvbRcsInstallCwPower OBJECT-TYPE 1883 SYNTAX Integer32 1884 UNITS "x0.1 dBm" 1885 MAX-ACCESS read-write 1886 STATUS current 1887 DESCRIPTION 1888 "IDU TX output level when the IDU is configured to send 1889 CW. The resolution is 0.1 dBm and the accuracy is +/- 1 1890 dBm. Reconfiguration is applied immediately to a CW." 1891 ::= {dvbRcsRcstInstall 4} 1893 dvbRcsInstallCoPolReading OBJECT-TYPE 1894 SYNTAX Unsigned32 1895 UNITS "x0.1 dB" 1896 MAX-ACCESS read-write 1897 STATUS current 1898 DESCRIPTION 1899 "Co-Polarisation measured value during installation 1900 procedure (in 0.1 dB)" 1901 ::= {dvbRcsRcstInstall 5} 1903 dvbRcsInstallXPolReading OBJECT-TYPE 1904 SYNTAX Unsigned32 1905 UNITS "x0.1 dB" 1906 MAX-ACCESS read-write 1907 STATUS current 1908 DESCRIPTION 1909 "Cross-Polarisation measured value during installation 1910 procedure (in 0.1 dB)" 1911 ::= {dvbRcsRcstInstall 6} 1913 dvbRcsInstallCoPolTarget OBJECT-TYPE 1914 SYNTAX Unsigned32 1915 UNITS "x0.1 dB" 1916 MAX-ACCESS read-write 1917 STATUS current 1918 DESCRIPTION 1919 "Co-Polarisation target value during installation 1920 procedure (in 0.1 dB)." 1921 ::= {dvbRcsRcstInstall 7} 1923 dvbRcsInstallXPolTarget OBJECT-TYPE 1924 SYNTAX Unsigned32 1925 UNITS "x0.1 dB" 1926 MAX-ACCESS read-write 1927 STATUS current 1928 DESCRIPTION 1929 "Cross-Polarisation target value during installation 1930 procedure (in 0.1 dB)" 1931 ::= {dvbRcsRcstInstall 8} 1933 dvbRcsInstallStandByDuration OBJECT-TYPE 1934 SYNTAX Unsigned32 1935 UNITS "seconds" 1936 MAX-ACCESS read-write 1937 STATUS current 1938 DESCRIPTION 1939 "Time to wait in stand-by mode (in seconds)" 1940 ::= {dvbRcsRcstInstall 9} 1942 dvbRcsInstallTargetEsN0 OBJECT-TYPE 1943 SYNTAX Unsigned32(0..315) 1944 UNITS "x0.1 dB" 1945 MAX-ACCESS read-write 1946 STATUS current 1947 DESCRIPTION 1948 "This value describes the wanted Es/N0 value that 1949 enables operation of the return link with the required 1950 error performance. The values shall be given in tenth of 1951 dB and the initial value shall be equal to 7 dB. The 1952 range shall be from 0 dBm to 31.5 dBm with a precision 1953 of 0.1 dB." 1954 DEFVAL { 70 } 1955 ::= {dvbRcsRcstInstall 10} 1957 --============================================================== 1958 -- dvbRcsRcstQos sub-tree object types 1959 --============================================================== 1960 dvbRcsPktClassTable OBJECT-TYPE 1961 SYNTAX SEQUENCE OF DvbRcsPktClassEntry 1962 MAX-ACCESS not-accessible 1963 STATUS current 1964 DESCRIPTION 1965 "This table describes the packet classification used in 1966 the DVB-RCS terminal. The number of entries is specified 1967 by dvbRcsPktClassIndex. " 1968 ::={dvbRcsRcstQos 1} 1970 dvbRcsPktClassEntry OBJECT-TYPE 1971 SYNTAX DvbRcsPktClassEntry 1972 MAX-ACCESS not-accessible 1973 STATUS current 1974 DESCRIPTION 1975 "An entry in the packet classification table. One object 1976 type of each entry may have a value in the active range 1977 (a non-default value).The other object types are then 1978 assumed set to 'inactive'. The entry with the lowest 1979 index value takes precedence when classifying a packet." 1980 INDEX { dvbRcsPktClassIndex } 1981 ::= {dvbRcsPktClassTable 1} 1983 DvbRcsPktClassEntry ::= SEQUENCE { 1984 dvbRcsPktClassIndex Unsigned32, 1985 dvbRcsPktClassDscpLow Dscp, 1986 dvbRcsPktClassDscpHigh Dscp, 1987 dvbRcsPktClassDscpMarkValue DscpOrAny, 1988 dvbRcsPktClassIpProtocol Unsigned32, 1989 dvbRcsPktClassSrcInetAddressType InetAddressType, 1990 dvbRcsPktClassSrcInetAddress InetAddress, 1991 dvbRcsPktClassSrcInetAddressPrefixLength 1992 InetAddressPrefixLength, 1993 dvbRcsPktClassDstInetAddressType InetAddressType, 1994 dvbRcsPktClassDstInetAddress InetAddress, 1995 dvbRcsPktClassDstInetAddressPrefixLength 1996 InetAddressPrefixLength, 1997 dvbRcsPktClassSrcPortLow InetPortNumber, 1998 dvbRcsPktClassSrcPortHigh InetPortNumber, 1999 dvbRcsPktClassDstPortLow InetPortNumber, 2000 dvbRcsPktClassDstPortHigh InetPortNumber, 2001 dvbRcsPktClassVlanUserPri Integer32, 2002 dvbRcsPktClassPhbAssociation Unsigned32, 2003 dvbRcsPktClassRowStatus RowStatus 2004 } 2006 dvbRcsPktClassIndex OBJECT-TYPE 2007 SYNTAX Unsigned32 (1..64) 2008 MAX-ACCESS not-accessible 2009 STATUS current 2010 DESCRIPTION 2011 "Index automatically incremented by one at row 2012 creation." 2013 ::={dvbRcsPktClassEntry 1} 2015 dvbRcsPktClassDscpLow OBJECT-TYPE 2016 SYNTAX Dscp 2017 MAX-ACCESS read-create 2018 STATUS current 2019 DESCRIPTION 2020 "This object specifies the low value of a range of 2021 DiffServ Code Point (DSCP) values to which a packet is 2022 compared." 2023 DEFVAL { 0 } 2024 ::={dvbRcsPktClassEntry 2} 2026 dvbRcsPktClassDscpHigh OBJECT-TYPE 2027 SYNTAX Dscp 2028 MAX-ACCESS read-create 2029 STATUS current 2030 DESCRIPTION 2031 "This object specifies the high value of a range of 2032 DiffServ Code Point (DSCP) values to which a packet is 2033 compared." 2034 DEFVAL { 63 } 2035 ::={dvbRcsPktClassEntry 3} 2037 dvbRcsPktClassDscpMarkValue OBJECT-TYPE 2038 SYNTAX DscpOrAny 2039 MAX-ACCESS read-create 2040 STATUS current 2041 DESCRIPTION 2042 "This object is the DiffServ Code Point (DSCP) value 2043 used to mark the packet, -1 indicates no DSCP marking. 2044 Possible DSCP marks values are (0..63)" 2045 DEFVAL { -1 } 2046 ::={dvbRcsPktClassEntry 4} 2048 dvbRcsPktClassIpProtocol OBJECT-TYPE 2049 SYNTAX Unsigned32 (0..255) 2050 MAX-ACCESS read-create 2051 STATUS current 2052 DESCRIPTION 2053 "This object specifies the IP protocol to which a 2054 packet is compared. A value of 255 means match all." 2055 DEFVAL { 255 } 2056 ::={dvbRcsPktClassEntry 5} 2058 dvbRcsPktClassSrcInetAddressType OBJECT-TYPE 2059 SYNTAX InetAddressType 2060 MAX-ACCESS read-create 2061 STATUS current 2062 DESCRIPTION 2063 "The type of internet address of 2064 dvbRcsPktClassSrcInetAddress. If the packet class source 2065 Internet address is unassigned or unknown, then the 2066 value of this object is unknown(0)." 2067 ::= { dvbRcsPktClassEntry 6} 2069 dvbRcsPktClassSrcInetAddress OBJECT-TYPE 2070 SYNTAX InetAddress 2071 MAX-ACCESS read-create 2072 STATUS current 2073 DESCRIPTION 2074 "This object specifies the IP source address to which a 2075 packet is compared. If the packet class has no source 2076 Internet address assigned, or this Internet address is 2077 unknown, the value of this object is the zero-length 2078 OCTET STRING. 2079 The InetAddressType is given by the 2080 dvbRcsPktClassSrcInetAddressType object." 2081 ::={dvbRcsPktClassEntry 7} 2083 dvbRcsPktClassSrcInetAddressPrefixLength OBJECT-TYPE 2084 SYNTAX InetAddressPrefixLength 2085 MAX-ACCESS read-create 2086 STATUS current 2087 DESCRIPTION 2088 "Prefix length of the IP source address that will be 2089 matched for this packet class. A value of zero indicates 2090 that the selectivity is inactive." 2091 DEFVAL { 0 } 2092 ::={dvbRcsPktClassEntry 8} 2094 dvbRcsPktClassDstInetAddressType OBJECT-TYPE 2095 SYNTAX InetAddressType 2096 MAX-ACCESS read-create 2097 STATUS current 2098 DESCRIPTION 2099 "The type of internet address of 2100 dvbRcsPktClassDstInetAddress. If the packet class 2101 destination Internet address is unassigned or unknown, 2102 then the value of this object is unknown(0)." 2103 ::= { dvbRcsPktClassEntry 9} 2105 dvbRcsPktClassDstInetAddress OBJECT-TYPE 2106 SYNTAX InetAddress 2107 MAX-ACCESS read-create 2108 STATUS current 2109 DESCRIPTION 2110 "This object specifies the IP destination address to 2111 which a packet is compared. If the packet class has no 2112 destination Internet address assigned, or this Internet 2113 address is unknown, the value of this object is the 2114 zero-length OCTET STRING. 2115 The InetAddressType is given by the 2116 dvbRcsPktClassDstInetAddressType object." 2117 ::={dvbRcsPktClassEntry 10} 2119 dvbRcsPktClassDstInetAddressPrefixLength OBJECT-TYPE 2120 SYNTAX InetAddressPrefixLength 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "Prefix length of the IP source address that will be 2125 matched for this packet class. A value of zero indicates 2126 that the selectivity is inactive." 2127 DEFVAL { 0 } 2128 ::={dvbRcsPktClassEntry 11} 2130 dvbRcsPktClassSrcPortLow OBJECT-TYPE 2131 SYNTAX InetPortNumber 2132 MAX-ACCESS read-create 2133 STATUS current 2134 DESCRIPTION 2135 "This object specifies the low range of the source 2136 port to which a packet is compared. A value of 0 2137 indicates that the selectivity is inactive." 2138 DEFVAL { 0 } 2139 ::={dvbRcsPktClassEntry 12} 2140 dvbRcsPktClassSrcPortHigh OBJECT-TYPE 2141 SYNTAX InetPortNumber 2142 MAX-ACCESS read-create 2143 STATUS current 2144 DESCRIPTION 2145 "This object specifies the high range of the source port 2146 to which a packet is compared. A value of 0 indicates 2147 that the selectivity is inactive." 2148 DEFVAL { 65535 } 2149 ::={dvbRcsPktClassEntry 13} 2151 dvbRcsPktClassDstPortLow OBJECT-TYPE 2152 SYNTAX InetPortNumber 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "This object specifies the low range of the destination 2157 port to which a packet is compared. A value of 0 2158 indicates that the selectivity is inactive." 2159 DEFVAL { 0 } 2160 ::={dvbRcsPktClassEntry 14} 2162 dvbRcsPktClassDstPortHigh OBJECT-TYPE 2163 SYNTAX InetPortNumber 2164 MAX-ACCESS read-create 2165 STATUS current 2166 DESCRIPTION 2167 "This object specifies the high range of the destination 2168 port to which a packet is compared. A value of 0 2169 indicates that the selectivity is inactive." 2170 DEFVAL { 65535 } 2171 ::={dvbRcsPktClassEntry 15} 2173 dvbRcsPktClassVlanUserPri OBJECT-TYPE 2174 SYNTAX Integer32 (-1..7) 2175 MAX-ACCESS read-create 2176 STATUS current 2177 DESCRIPTION 2178 "This object specifies the VLAN User Priority to which a 2179 packet is compared. A value of -1 indicates that the 2180 selectivity is inactive." 2182 DEFVAL { -1 } 2183 ::={dvbRcsPktClassEntry 16} 2185 dvbRcsPktClassPhbAssociation OBJECT-TYPE 2186 SYNTAX Unsigned32 2187 MAX-ACCESS read-create 2188 STATUS current 2189 DESCRIPTION 2190 "Associate the filter entry to a specific PHB (refer to 2191 dvbRcsPhbIdentifier)." 2192 ::={dvbRcsPktClassEntry 17} 2194 dvbRcsPktClassRowStatus OBJECT-TYPE 2195 SYNTAX RowStatus 2196 MAX-ACCESS read-create 2197 STATUS current 2198 DESCRIPTION 2199 "The status of this conceptual row. All writable objects 2200 in this row may be modified at any time." 2201 ::={dvbRcsPktClassEntry 18} 2203 --============================================================== 2204 -- dvbRcsPhbMappingTable 2205 --============================================================== 2206 dvbRcsPhbMappingTable OBJECT-TYPE 2207 SYNTAX SEQUENCE OF DvbRcsPhbMappingEntry 2208 MAX-ACCESS not-accessible 2209 STATUS current 2210 DESCRIPTION 2211 "This table is a list of Per-Hop Behaviour (PHB) MIB 2212 entries. 2213 It describes the PHB mapping to the Request Class." 2214 ::={dvbRcsRcstQos 2} 2216 dvbRcsPhbMappingEntry OBJECT-TYPE 2217 SYNTAX DvbRcsPhbMappingEntry 2218 MAX-ACCESS not-accessible 2219 STATUS current 2220 DESCRIPTION 2221 "An entry in the PHB mapping table." 2222 INDEX {dvbRcsPhbIdentifier} 2224 ::= {dvbRcsPhbMappingTable 1} 2226 DvbRcsPhbMappingEntry ::= SEQUENCE { 2227 dvbRcsPhbIdentifier Unsigned32, 2228 dvbRcsPhbName 2229 SnmpAdminString, 2230 dvbRcsPhbRequestClassAssociation Unsigned32, 2231 dvbRcsPhbMappingRowStatus RowStatus 2232 } 2234 dvbRcsPhbIdentifier OBJECT-TYPE 2235 SYNTAX Unsigned32 2236 MAX-ACCESS not-accessible 2237 STATUS current 2238 DESCRIPTION 2239 "Identification of the Per-Hop Behaviour (PHB). It 2240 follows the unsigned 16 bit binary encoding as specified 2241 in RFC 3140. " 2242 ::={dvbRcsPhbMappingEntry 1} 2244 dvbRcsPhbName OBJECT-TYPE 2245 SYNTAX SnmpAdminString 2246 MAX-ACCESS read-create 2247 STATUS current 2248 DESCRIPTION 2249 "The name of the Per-Hop Behaviour (PHB)." 2250 ::={dvbRcsPhbMappingEntry 2} 2252 dvbRcsPhbRequestClassAssociation OBJECT-TYPE 2253 SYNTAX Unsigned32 (1..16) 2254 MAX-ACCESS read-create 2255 STATUS current 2256 DESCRIPTION 2257 "This object is an association of this Per-Hop Behaviour 2258 (PHB) to a Request class (by reference to a Request 2259 Class index)." 2260 ::={dvbRcsPhbMappingEntry 3} 2262 dvbRcsPhbMappingRowStatus OBJECT-TYPE 2263 SYNTAX RowStatus 2264 MAX-ACCESS read-create 2265 STATUS current 2266 DESCRIPTION 2267 "The status of this conceptual row. All writable 2268 objects in this row may be modified at any time." 2269 DEFVAL { active } 2270 ::={dvbRcsPhbMappingEntry 4} 2272 --============================================================== 2273 -- dvbRcsRequestClassTable 2274 --============================================================== 2275 dvbRcsRequestClassTable OBJECT-TYPE 2276 SYNTAX SEQUENCE OF DvbRcsRequestClassEntry 2277 MAX-ACCESS not-accessible 2278 STATUS current 2279 DESCRIPTION 2280 "This table is a list of Request class entries. This 2281 class describes the layer 2 QoS objects." 2282 ::={dvbRcsRcstQos 3} 2284 dvbRcsRequestClassEntry OBJECT-TYPE 2285 SYNTAX DvbRcsRequestClassEntry 2286 MAX-ACCESS not-accessible 2287 STATUS current 2288 DESCRIPTION 2289 "An entry in the Request Class table." 2290 INDEX {dvbRcsRequestClassIndex} 2291 ::= {dvbRcsRequestClassTable 1} 2293 DvbRcsRequestClassEntry ::= SEQUENCE { 2294 dvbRcsRequestClassIndex Unsigned32, 2295 dvbRcsRequestClassName 2296 SnmpAdminString, 2297 dvbRcsRequestClassChanId Unsigned32, 2298 dvbRcsRequestClassVccVpi Unsigned32, 2299 dvbRcsRequestClassVccVci Unsigned32, 2300 dvbRcsRequestClassPidPoolReference Unsigned32, 2301 dvbRcsRequestClassCra Unsigned32, 2302 dvbRcsRequestClassRbdcMax Unsigned32, 2303 dvbRcsRequestClassRbdcTimeout Unsigned32, 2304 dvbRcsRequestClassVbdcMax Unsigned32, 2305 dvbRcsRequestClassVbdcTimeout Unsigned32, 2306 dvbRcsRequestClassVbdcMaxBackLog Unsigned32, 2307 dvbRcsRequestClassRowStatus RowStatus 2308 } 2310 dvbRcsRequestClassIndex OBJECT-TYPE 2311 SYNTAX Unsigned32 (1..16) 2312 MAX-ACCESS not-accessible 2313 STATUS current 2314 DESCRIPTION 2315 "Index of the Request Class table. A total of 16 entries 2316 are supported." 2317 ::={dvbRcsRequestClassEntry 1} 2319 dvbRcsRequestClassName OBJECT-TYPE 2320 SYNTAX SnmpAdminString 2321 MAX-ACCESS read-create 2322 STATUS current 2323 DESCRIPTION 2324 "Name of the Request Class." 2325 ::={dvbRcsRequestClassEntry 2} 2327 dvbRcsRequestClassChanId OBJECT-TYPE 2328 SYNTAX Unsigned32 (0..15) 2329 MAX-ACCESS read-create 2330 STATUS current 2331 DESCRIPTION 2332 "Channel id of the Request Class." 2333 ::={dvbRcsRequestClassEntry 3} 2335 dvbRcsRequestClassVccVpi OBJECT-TYPE 2336 SYNTAX Unsigned32 (0..255) 2337 MAX-ACCESS read-create 2338 STATUS current 2339 DESCRIPTION 2340 "Defines VPI used for the Request Class (ATM profile)." 2341 ::={dvbRcsRequestClassEntry 4} 2343 dvbRcsRequestClassVccVci OBJECT-TYPE 2344 SYNTAX Unsigned32 (0..65535) 2345 MAX-ACCESS read-create 2346 STATUS current 2347 DESCRIPTION 2348 "Defines VCI used for the Request Class (ATM profile)." 2349 ::={dvbRcsRequestClassEntry 5} 2351 dvbRcsRequestClassPidPoolReference OBJECT-TYPE 2352 SYNTAX Unsigned32 (1..16) 2353 MAX-ACCESS read-create 2354 STATUS current 2355 DESCRIPTION 2356 "Reference to the Packet IDentifier (PID) pool 2357 applicable for the Request Class." 2358 ::={dvbRcsRequestClassEntry 6} 2360 dvbRcsRequestClassCra OBJECT-TYPE 2361 SYNTAX Unsigned32 2362 UNITS "bits/s" 2363 MAX-ACCESS read-create 2364 STATUS current 2365 DESCRIPTION 2366 "Define Continuous Rate Assignment (CRA) level for the 2367 Request Class in bit per second (bits/s)." 2368 ::={dvbRcsRequestClassEntry 7} 2370 dvbRcsRequestClassRbdcMax OBJECT-TYPE 2371 SYNTAX Unsigned32 2372 UNITS "x2 kbits/s" 2373 MAX-ACCESS read-create 2374 STATUS current 2375 DESCRIPTION 2376 "Maximum Rate-Based Dynamic Capacity (RBDC) that can be 2377 requested for the Request Class, in number of 2 kbits/s" 2378 ::={dvbRcsRequestClassEntry 8} 2380 dvbRcsRequestClassRbdcTimeout OBJECT-TYPE 2381 SYNTAX Unsigned32 2382 UNITS "superframes" 2383 MAX-ACCESS read-create 2384 STATUS current 2385 DESCRIPTION 2386 "Persistence of the Rate-Based Dynamic Capacity (RBDC) 2387 request, expressed in superframes" 2388 ::={dvbRcsRequestClassEntry 9} 2390 dvbRcsRequestClassVbdcMax OBJECT-TYPE 2391 SYNTAX Unsigned32 2392 UNITS "ATM cells/MPEG packets" 2393 MAX-ACCESS read-create 2394 STATUS current 2395 DESCRIPTION 2396 "Maximum Volume-Based Dynamic Capacity (VBDC) that can 2397 be allocated to the Request Class, in payload units (one 2398 ATM cell or one MPEG packet) per superframe" 2399 ::={dvbRcsRequestClassEntry 10} 2401 dvbRcsRequestClassVbdcTimeout OBJECT-TYPE 2402 SYNTAX Unsigned32 2403 UNITS "superframes" 2404 MAX-ACCESS read-create 2405 STATUS current 2406 DESCRIPTION 2407 "Time after which the RCST considers that the pending 2408 requests are lost. The RCST may issue new requests for 2409 that traffic. Volume-Based Dynamic Capacity (VBDC) 2410 Timeout is expressed in superframes." 2411 ::={dvbRcsRequestClassEntry 11} 2413 dvbRcsRequestClassVbdcMaxBackLog OBJECT-TYPE 2414 SYNTAX Unsigned32 2415 UNITS "bytes" 2416 MAX-ACCESS read-create 2417 STATUS current 2418 DESCRIPTION 2419 "Volume-Based Dynamic Capacity (VBDC) back log per 2420 Request Class (expressed in bytes)" 2421 ::={dvbRcsRequestClassEntry 12} 2423 dvbRcsRequestClassRowStatus OBJECT-TYPE 2424 SYNTAX RowStatus 2425 MAX-ACCESS read-create 2426 STATUS current 2427 DESCRIPTION 2428 "The status of this conceptual row. It is not possible 2429 to change values in a row of this table while the row is 2430 active." 2431 ::={dvbRcsRequestClassEntry 13} 2433 --============================================================== 2434 -- The table of PID pools 2435 --============================================================== 2437 dvbRcsPidPoolTable OBJECT-TYPE 2438 SYNTAX SEQUENCE OF DvbRcsPidPoolEntry 2439 MAX-ACCESS not-accessible 2440 STATUS current 2441 DESCRIPTION 2442 "This table contains the Packet IDentifier (PID) pools. 2443 For MPEG profile several Request Classes may be mapped 2444 within a pool of several PIDs to allow Section Packing 2445 across Several Request Classes. 2446 A PID value may occur in more than one PID pool. Each 2447 PID value can effectively occur only once in each pool." 2448 ::={dvbRcsRcstQos 4} 2450 dvbRcsPidPoolEntry OBJECT-TYPE 2451 SYNTAX DvbRcsPidPoolEntry 2452 MAX-ACCESS not-accessible 2453 STATUS current 2454 DESCRIPTION 2455 "An entry in the PID pool table." 2456 INDEX { dvbRcsPidPoolIndex, dvbRcsPidIndex } 2457 ::= {dvbRcsPidPoolTable 1} 2459 DvbRcsPidPoolEntry ::= SEQUENCE { 2460 dvbRcsPidPoolIndex Unsigned32, 2461 dvbRcsPidIndex Unsigned32, 2462 dvbRcsPidValue Unsigned32, 2463 dvbRcsPidPoolRowStatus RowStatus 2464 } 2466 dvbRcsPidPoolIndex OBJECT-TYPE 2467 SYNTAX Unsigned32 (1..16) 2468 MAX-ACCESS not-accessible 2469 STATUS current 2470 DESCRIPTION 2471 "Index of the PID pool in the PID pool table." 2472 ::={dvbRcsPidPoolEntry 1} 2474 dvbRcsPidIndex OBJECT-TYPE 2475 SYNTAX Unsigned32 (1..16) 2476 MAX-ACCESS not-accessible 2477 STATUS current 2478 DESCRIPTION 2479 "Index of the PID entry within the PID pool." 2480 ::={dvbRcsPidPoolEntry 2} 2482 dvbRcsPidValue OBJECT-TYPE 2483 SYNTAX Unsigned32 (0..8191) 2484 MAX-ACCESS read-create 2485 STATUS current 2486 DESCRIPTION 2487 "Defines one of the PIDs to be used in a PID pool of 2488 dvbRcsPidPoolIndex. 2489 A PID value may occur in more than one PID pool. Each 2490 PID value can effectively occur only once in each pool." 2491 ::={dvbRcsPidPoolEntry 3} 2493 dvbRcsPidPoolRowStatus OBJECT-TYPE 2494 SYNTAX RowStatus 2495 MAX-ACCESS read-create 2496 STATUS current 2497 DESCRIPTION 2498 "The status of this conceptual row. All writable 2499 objects in this row may be modified at any time." 2500 DEFVAL { active } 2501 ::={dvbRcsPidPoolEntry 4} 2503 dvbRcsQosGlobalRbdcMax OBJECT-TYPE 2504 SYNTAX Unsigned32 2505 UNITS "x2 kbits/s" 2506 MAX-ACCESS read-write 2507 STATUS current 2508 DESCRIPTION 2509 "Global maximum RBDC that can be requested for the RCST, 2510 in number of 2 kbits/s." 2511 ::={dvbRcsRcstQos 5} 2513 dvbRcsQosGlobalVbdcMax OBJECT-TYPE 2514 SYNTAX Unsigned32 2515 UNITS "ATM cells/MPEG packets" 2516 MAX-ACCESS read-write 2517 STATUS current 2518 DESCRIPTION 2519 "Global maximum VBDC that can be allocated to the RCST, 2520 in payload units (one ATM cell or one MPEG packet) per 2521 superframe." 2522 ::={dvbRcsRcstQos 6} 2524 dvbRcsQosGlobalVbdcMaxBackLog OBJECT-TYPE 2525 SYNTAX Unsigned32 2526 UNITS "bytes" 2527 MAX-ACCESS read-write 2528 STATUS current 2529 DESCRIPTION 2530 "Global VBDC back log at RCST level (expressed in 2531 bytes). It is used only if the VBDC back log is not 2532 configured in the Request class (expressed in bytes)." 2533 ::={dvbRcsRcstQos 7} 2535 dvbRcsQosChannelIdStrictDispatching OBJECT-TYPE 2536 SYNTAX INTEGER { 2537 notStrict (0), 2538 strict (1) 2539 } 2540 MAX-ACCESS read-write 2541 STATUS current 2542 DESCRIPTION 2543 "Indicates whether the RCST will strictly follow RC 2544 association when signaled through Channel_ID in the 2545 TBTP: 2546 (0)- no strict association 2547 (1)- strict association" 2548 ::={dvbRcsRcstQos 8} 2549 --============================================================== 2550 -- dvbRcsRcstControl sub-tree object types 2551 --============================================================== 2552 dvbRcsCtrlRebootCommand OBJECT-TYPE 2553 SYNTAX INTEGER { 2554 idle (1), 2555 normal (2), 2556 alternate (3) 2557 } 2558 MAX-ACCESS read-write 2559 STATUS current 2560 DESCRIPTION 2561 "This variable shall force the RCST to reboot 2562 (1)- idle 2563 (2)- normal reboot (from current software load) 2564 (3)- reboot from alternate load (swap to alternate 2565 load before reboot)" 2566 DEFVAL {idle} 2567 ::={dvbRcsRcstControl 1} 2569 dvbRcsCtrlRcstTxDisable OBJECT-TYPE 2570 SYNTAX INTEGER { 2571 idle (1), 2572 disable (2) 2573 } 2574 MAX-ACCESS read-write 2575 STATUS current 2576 DESCRIPTION 2577 "This variable shall force the RCST to stop transmission 2578 (transmit disabled as defined in SatLabs System 2579 Recommendations): 2580 (1)- idle 2581 (2)- initiate Tx Disabled" 2582 DEFVAL {idle} 2583 ::={dvbRcsRcstControl 2} 2585 dvbRcsCtrlUserTrafficDisable OBJECT-TYPE 2586 SYNTAX INTEGER { 2587 idle (1), 2588 disable (2) 2589 } 2590 MAX-ACCESS read-write 2591 STATUS current 2592 DESCRIPTION 2593 "This variable shall disable user traffic (only RCST 2594 management traffic can be transmitted) 2595 (1)- idle 2596 (2)- disable user traffic" 2597 DEFVAL {idle} 2598 ::={dvbRcsRcstControl 3} 2600 dvbRcsCtrlCwEnable OBJECT-TYPE 2601 SYNTAX INTEGER { 2602 off (1), 2603 on (2) 2604 } 2605 MAX-ACCESS read-write 2606 STATUS current 2607 DESCRIPTION 2608 "This variable will force the RCST to start transmission 2609 of CW, if the RCST is first set to the installation 2610 state, and is properly configured for CW transmission: 2611 (1)- off 2612 (2)- on" 2613 DEFVAL {off} 2614 ::={dvbRcsRcstControl 4} 2616 dvbRcsCtrlOduTxReferenceEnable OBJECT-TYPE 2617 SYNTAX INTEGER { 2618 off (1), 2619 on (2) 2620 } 2621 MAX-ACCESS read-write 2622 STATUS current 2623 DESCRIPTION 2624 "Enables activation and deactivation of 10 MHz reference 2625 clock in the Tx IFL cable: 2626 (1) off 2627 (2) on" 2628 DEFVAL {on} 2629 ::={dvbRcsRcstControl 5} 2630 dvbRcsCtrlOduTxDCEnable OBJECT-TYPE 2631 SYNTAX INTEGER { 2632 off (1), 2633 on (2) 2634 } 2635 MAX-ACCESS read-write 2636 STATUS current 2637 DESCRIPTION 2638 "Enables activation and deactivation of DC in the Tx IFL 2639 cable: 2640 (1) off 2641 (2) on" 2642 DEFVAL {on} 2643 ::={dvbRcsRcstControl 6} 2645 dvbRcsCtrlOduRxDCEnable OBJECT-TYPE 2646 SYNTAX INTEGER { 2647 off (1), 2648 on (2) 2649 } 2650 MAX-ACCESS read-write 2651 STATUS current 2652 DESCRIPTION 2653 "Enables activation and deactivation of DC in the Rx IFL 2654 cable: 2655 (1) off 2656 (2) on" 2657 DEFVAL {on} 2658 ::={dvbRcsRcstControl 7} 2660 dvbRcsCtrlDownloadFileCommand OBJECT-TYPE 2661 SYNTAX INTEGER { 2662 idle (1), 2663 config (2), 2664 installationLog (3) 2665 } 2666 MAX-ACCESS read-write 2667 STATUS current 2668 DESCRIPTION 2669 "This variable will initiate a RCST configuration file 2670 download process 2671 (1) idle 2672 (2) download RCST configuration file from TFTP/FTP 2673 server 2674 (3) download RCST installation log file from TFTP/FTP 2675 server (INSTALL_LOG Option)" 2676 DEFVAL {idle} 2677 ::={dvbRcsRcstControl 8} 2679 dvbRcsCtrlUploadFileCommand OBJECT-TYPE 2680 SYNTAX INTEGER { 2681 idle (1), 2682 config (2), 2683 eventAlarm (3), 2684 installationLog (4) 2685 } 2686 MAX-ACCESS read-write 2687 STATUS current 2688 DESCRIPTION 2689 "This variable will initiate a RCST upload process 2690 (1) idle 2691 (2) upload RCST configuration file to TFTP/FTP server 2692 (3) upload RCST event/alarm log file to TFTP/FTP server 2693 (4) upload RCST installation log file to TFTP/FTP server 2694 (INSTALL_LOG Option)" 2695 DEFVAL {idle} 2696 ::={dvbRcsRcstControl 9} 2698 dvbRcsCtrlActivateConfigFileCommand OBJECT-TYPE 2699 SYNTAX INTEGER { 2700 idle (1), 2701 activate (2) 2702 } 2703 MAX-ACCESS read-write 2704 STATUS current 2705 DESCRIPTION 2706 "Triggers the RCST to use the configuration file and 2707 update its parameters accordingly. Some RCST 2708 implementations may require a reboot for the parameters 2709 to take effect (vendor specific). 2710 (1) Idle 2711 (2) activate" 2713 DEFVAL {idle} 2714 ::={dvbRcsRcstControl 10} 2716 dvbRcsCtrlRcstLogonCommand OBJECT-TYPE 2717 SYNTAX INTEGER { 2718 idle (1), 2719 logon (2) 2720 } 2721 MAX-ACCESS read-write 2722 STATUS current 2723 DESCRIPTION 2724 "This variable will initiate a RCST logon 2725 (1) idle 2726 (2) initiate RCST logon" 2727 DEFVAL {idle} 2728 ::={dvbRcsRcstControl 11} 2730 dvbRcsCtrlRcstLogoffCommand OBJECT-TYPE 2731 SYNTAX INTEGER { 2732 idle (1), 2733 logoff (2) 2734 } 2735 MAX-ACCESS read-write 2736 STATUS current 2737 DESCRIPTION 2738 "This variable will initiate a RCST logoff 2739 (1) idle 2740 (2) initiate RCST logoff" 2741 DEFVAL {idle} 2742 ::={dvbRcsRcstControl 12} 2744 dvbRcsCtrlRcstRxReacquire OBJECT-TYPE 2745 SYNTAX INTEGER { 2746 idle (1), 2747 reacquireForwardLink (2) 2748 } 2749 MAX-ACCESS read-write 2750 STATUS current 2751 DESCRIPTION 2752 "This variable will force the RCST to acquire the 2753 forward link and start receiving." 2755 DEFVAL {idle} 2756 ::={dvbRcsRcstControl 13} 2758 --============================================================== 2759 -- dvbRcsRcstState sub-tree object types 2760 --============================================================== 2761 dvbRcsRcstMode OBJECT-TYPE 2762 SYNTAX INTEGER { 2763 installation (0), 2764 operational (1) 2765 } 2766 MAX-ACCESS read-write 2767 STATUS current 2768 DESCRIPTION 2769 "Identifies the current mode of the RCST is and allows it 2770 to return to the installation mode when needed. Values for 2771 the RCST mode are: 2772 Installation (0) 2773 Operational (1)" 2774 ::={dvbRcsRcstState 1} 2776 dvbRcsRcstFaultStatus OBJECT-TYPE 2777 SYNTAX INTEGER { 2778 nofault (0), 2779 fault (1) 2780 } 2781 MAX-ACCESS read-only 2782 STATUS current 2783 DESCRIPTION 2784 "Provide the fault status of the terminal. The fault 2785 status management is vendor specific. Values for the 2786 Fault Status are: 2787 no fault (0) 2788 fault (1)" 2789 ::={dvbRcsRcstState 2} 2791 dvbRcsRcstFwdLinkStatus OBJECT-TYPE 2792 SYNTAX INTEGER { 2793 notAcquired (0), 2794 acquired (1) 2795 } 2796 MAX-ACCESS read-only 2797 STATUS current 2798 DESCRIPTION 2799 "Provides the status of the RCST Forward Link. Values 2800 for the Forward Link Status are: 2801 Not acquired (0) 2802 Acquired (1)" 2803 ::={dvbRcsRcstState 3} 2805 dvbRcsRcstRtnLinkStatus OBJECT-TYPE 2806 SYNTAX INTEGER { 2807 loggedOff (0), 2808 loggedOn (1) 2809 } 2810 MAX-ACCESS read-only 2811 STATUS current 2812 DESCRIPTION 2813 "Provides the status of the RCST Return Link. Values for 2814 the Return Link Status are: 2815 Logged-off (0) 2816 Logged-on (1)" 2817 ::={dvbRcsRcstState 4} 2819 dvbRcsRcstLogUpdated OBJECT-TYPE 2820 SYNTAX INTEGER { 2821 noUpdate (0), 2822 logfileUpdated (1) 2823 } 2824 MAX-ACCESS read-only 2825 STATUS current 2826 DESCRIPTION 2827 "Indicates the existence of an updated event log file: 2828 No update (0) 2829 Event Log file updated (1) 2830 The RCST should remove the Event Log file updated 2831 indication as the log file is fetched by the NCC." 2832 ::={dvbRcsRcstState 5} 2834 dvbRcsRcstCurrentSoftwareVersion OBJECT-TYPE 2835 SYNTAX SnmpAdminString 2836 MAX-ACCESS read-only 2837 STATUS current 2838 DESCRIPTION 2839 "Current RCST software version." 2840 ::={dvbRcsRcstState 6} 2842 dvbRcsRcstAlternateSoftwareVersion OBJECT-TYPE 2843 SYNTAX SnmpAdminString 2844 MAX-ACCESS read-only 2845 STATUS current 2846 DESCRIPTION 2847 "Alternate (backup/new) RCST software version." 2848 ::={dvbRcsRcstState 7} 2850 dvbRcsRcstActivatedConfigFileVersion OBJECT-TYPE 2851 SYNTAX SnmpAdminString 2852 MAX-ACCESS read-only 2853 STATUS current 2854 DESCRIPTION 2855 "Version of the most recently activated configuration 2856 file. 2857 The version is vendor specific." 2858 ::={dvbRcsRcstState 8} 2860 dvbRcsRcstDownloadedConfigFileVersion OBJECT-TYPE 2861 SYNTAX SnmpAdminString 2862 MAX-ACCESS read-only 2863 STATUS current 2864 DESCRIPTION 2865 "Version of the most recently downloaded configuration 2866 file. 2867 Version is vendor specific. If the value is different 2868 from dvbRcsRcstActivatedConfigFileVersion, it is pending 2869 for activation." 2870 ::={dvbRcsRcstState 9} 2872 --============================================================== 2873 -- dvbRcsFwdConfig sub-tree object types 2874 --============================================================== 2875 dvbRcsFwdStartTable OBJECT-TYPE 2876 SYNTAX SEQUENCE OF DvbRcsFwdStartEntry 2877 MAX-ACCESS not-accessible 2878 STATUS current 2879 DESCRIPTION 2880 "Lists Forward Links attachment points (e.g. different 2881 for installation and operation). 2882 The table describes the forward link parameters used for 2883 the start-up stream with the NCC." 2884 ::={dvbRcsFwdConfig 1} 2886 dvbRcsFwdStartEntry OBJECT-TYPE 2887 SYNTAX DvbRcsFwdStartEntry 2888 MAX-ACCESS not-accessible 2889 STATUS current 2890 DESCRIPTION 2891 "An entry in the Forward Link StartConfig table." 2892 INDEX {dvbRcsFwdStartIndex} 2893 ::= {dvbRcsFwdStartTable 1} 2895 DvbRcsFwdStartEntry ::= SEQUENCE { 2896 dvbRcsFwdStartIndex Unsigned32, 2897 dvbRcsFwdStartPopId Integer32, 2898 dvbRcsFwdStartFrequency Unsigned32, 2899 dvbRcsFwdStartPolar INTEGER, 2900 dvbRcsFwdStartFormat INTEGER, 2901 dvbRcsFwdStartRolloff INTEGER, 2902 dvbRcsFwdStartSymbolRate Unsigned32, 2903 dvbRcsFwdStartInnerFec INTEGER, 2904 dvbRcsFwdStartRowStatus RowStatus 2905 } 2907 dvbRcsFwdStartIndex OBJECT-TYPE 2908 SYNTAX Unsigned32 (1..8) 2909 MAX-ACCESS not-accessible 2910 STATUS current 2911 DESCRIPTION 2912 "Index of the Forward Link StartConfig table." 2913 ::={dvbRcsFwdStartEntry 1} 2915 dvbRcsFwdStartPopId OBJECT-TYPE 2916 SYNTAX Integer32 (-1..65535) 2917 MAX-ACCESS read-create 2918 STATUS current 2919 DESCRIPTION 2920 "Population identifier associated with the start-up 2921 forward link: 2922 -1: any (auto) 2923 0-65535: specific StartPopId 2924 If 'any' is set, the RCST will assume membership of any 2925 announced population ID and will commence with logon in 2926 accordance with this assumption." 2927 ::={dvbRcsFwdStartEntry 2} 2929 dvbRcsFwdStartFrequency OBJECT-TYPE 2930 SYNTAX Unsigned32 2931 UNITS "x100 kHz" 2932 MAX-ACCESS read-create 2933 STATUS current 2934 DESCRIPTION 2935 "Frequency of the start transponder carrying a 2936 Network Information Table to which any RCST shall 2937 trigger to acquire forward link. Its value shall be 2938 given in multiple of 100 kHz." 2939 ::={dvbRcsFwdStartEntry 3} 2941 dvbRcsFwdStartPolar OBJECT-TYPE 2942 SYNTAX INTEGER { 2943 linearHorizontal (0), 2944 linearVertical (1), 2945 circularLeft (2), 2946 circularRight (3) 2947 } 2948 MAX-ACCESS read-create 2949 STATUS current 2950 DESCRIPTION 2951 "2-bit field giving the polarization of the start 2952 transponder carrying an Network Information Table to 2953 which any RCST shall trigger to acquire forward link: 2954 00: linear and horizontal 2955 01: linear and vertical 2956 10: circular left 2957 11: circular right" 2958 ::={dvbRcsFwdStartEntry 4} 2959 dvbRcsFwdStartFormat OBJECT-TYPE 2960 SYNTAX INTEGER { 2961 auto (-1), 2962 dvbs (0), 2963 dvbs2ccm (1), 2964 dvbs2acm (2) 2965 } 2966 MAX-ACCESS read-create 2967 STATUS current 2968 DESCRIPTION 2969 "Specifies the transmission format standard applied for 2970 the startup stream. The start transport stream carries a 2971 Network Information Table that the RCST uses for 2972 acquiring the forward link signaling. Supported values 2973 are: 2974 -1: unspecified (automatic format acquisition is 2975 assumed) 2976 0: DVB-S (support of this value is mandatory if 2977 DVB-S support is claimed) 2978 1: DVB-S2 with CCM (support of this value is 2979 mandatory if DVB-S2 CCM support is claimed) 2980 2: DVB-S2 with VCM or ACM (support of this value is 2981 mandatory if DVB-S2 ACM support is claimed) 2982 This allows the RCST to discriminate between CCM and 2983 VCM/ACM when selecting the forward link. 2984 The support of automatic format selection is optional. 2985 One or several of the other format selections must be 2986 supported, according to the claimed SatLabs profile 2987 support." 2988 ::={dvbRcsFwdStartEntry 5} 2990 dvbRcsFwdStartRolloff OBJECT-TYPE 2991 SYNTAX INTEGER { 2992 autoRolloff (0), 2993 rolloff020 (1), 2994 rolloff025 (2), 2995 rolloff035 (3) 2996 } 2997 MAX-ACCESS read-create 2998 STATUS current 2999 DESCRIPTION 3000 "Specifies the receive filter roll-off applied on the 3001 start transponder. The start transponder carries a 3002 Network Information Table that the RCST uses for 3003 acquiring the forward link signaling. 3004 Supported values are: 3005 0: any (auto) 3006 1: 0.20 3007 2: 0.25 3008 3: 0.35" 3009 ::={dvbRcsFwdStartEntry 6} 3011 dvbRcsFwdStartSymbolRate OBJECT-TYPE 3012 SYNTAX Unsigned32 3013 UNITS "x100 symbols/s" 3014 MAX-ACCESS read-create 3015 STATUS current 3016 DESCRIPTION 3017 "Specifies the symbol rate on the start transponder 3018 carrying a Network Information Table to which any RCST 3019 shall trigger to acquire forward link. Its value shall 3020 be given in multiple of 100 symbols/s." 3021 ::={dvbRcsFwdStartEntry 7} 3023 dvbRcsFwdStartInnerFec OBJECT-TYPE 3024 SYNTAX INTEGER { 3025 autoFec (-1), 3026 fecRate12 (0), 3027 fecRate23 (1), 3028 fecRate34 (2), 3029 fecRate56 (3), 3030 fecRate78 (4), 3031 fecRate89 (5), 3032 fecRate35 (6), 3033 fecRate45 (7), 3034 fecRate910 (8), 3035 fecRate25 (9), 3036 fecRate13 (10), 3037 fecRate14 (11), 3038 noInnerCode (12) 3039 } 3040 MAX-ACCESS read-create 3041 STATUS current 3042 DESCRIPTION 3043 "Specifies the inner Forward Error Correction used on 3044 the start transponder carrying a Network Information 3045 Table to which any RCST shall trigger to acquire forward 3046 link. 3047 Supported values are: 3048 autoFec (-1), 3049 fecRate1/2 (0), 3050 fecRate2/3 (1), 3051 fecRate3/4 (2), 3052 fecRate5/6 (3), 3053 fecRate7/8 (4), 3054 fecRate8/9 (5), 3055 fecRate3/5 (6), 3056 fecRate4/5 (7), 3057 fecRate9/10 (8), 3058 fecRate2/5 (9), 3059 fecRate1/3 (10), 3060 fecRate1/4 (11), 3061 noInnerCode (12) 3062 The support of autoFec is optional." 3063 ::={dvbRcsFwdStartEntry 8} 3065 dvbRcsFwdStartRowStatus OBJECT-TYPE 3066 SYNTAX RowStatus 3067 MAX-ACCESS read-create 3068 STATUS current 3069 DESCRIPTION 3070 "The status of this conceptual row. It is not possible 3071 to change values in a row of this table while the row is 3072 active." 3073 ::={dvbRcsFwdStartEntry 9} 3075 --============================================================== 3076 -- dvbRcsFwdStatus sub-tree object types 3077 --============================================================== 3078 dvbRcsFwdStatusPopId OBJECT-TYPE 3079 SYNTAX Unsigned32 (0..65535) 3080 MAX-ACCESS read-only 3081 STATUS current 3082 DESCRIPTION 3083 "Population identifier applied at log-on: 3084 0-65535: specific StartPopId 3085 If the RCST was allowed to logon with any population, 3086 the RCST will report the base number of the announced 3087 population ID indicated by the RCS Map Table linkage 3088 descriptor used at logon." 3089 ::={dvbRcsFwdStatus 1} 3091 dvbRcsFwdStatusTable OBJECT-TYPE 3092 SYNTAX SEQUENCE OF DvbRcsFwdStatusEntry 3093 MAX-ACCESS not-accessible 3094 STATUS current 3095 DESCRIPTION 3096 "This table describes the current status of Forward Link 3097 interfaces." 3098 ::={dvbRcsFwdStatus 2} 3100 dvbRcsFwdStatusEntry OBJECT-TYPE 3101 SYNTAX DvbRcsFwdStatusEntry 3102 MAX-ACCESS not-accessible 3103 STATUS current 3104 DESCRIPTION 3105 "An entry in the Forward Link Status table. Each entry 3106 is associated with a physical interface. 3107 A RCST shall support at least one entry." 3108 INDEX { dvbRcsFwdStatusIndex } 3109 ::= {dvbRcsFwdStatusTable 1} 3111 DvbRcsFwdStatusEntry ::= SEQUENCE { 3112 dvbRcsFwdStatusIndex Unsigned32, 3113 dvbRcsFwdStatusIfReference Unsigned32, 3114 dvbRcsFwdStatusNetId Unsigned32, 3115 dvbRcsFwdStatusNetName 3116 SnmpAdminString, 3117 dvbRcsFwdStatusFormat INTEGER, 3118 dvbRcsFwdStatusFrequency Unsigned32, 3119 dvbRcsFwdStatusPolar INTEGER, 3120 dvbRcsFwdStatusInnerFec INTEGER, 3121 dvbRcsFwdStatusSymbolRate Unsigned32, 3122 dvbRcsFwdStatusRolloff INTEGER, 3123 dvbRcsFwdStatusModulation INTEGER, 3124 dvbRcsFwdStatusFecFrame INTEGER, 3125 dvbRcsFwdStatusPilot INTEGER, 3126 dvbRcsFwdStatusBer Integer32, 3127 dvbRcsFwdStatusCnr Integer32, 3128 dvbRcsFwdStatusRxPower Integer32 3129 } 3131 dvbRcsFwdStatusIndex OBJECT-TYPE 3132 SYNTAX Unsigned32 (1..8) 3133 MAX-ACCESS not-accessible 3134 STATUS current 3135 DESCRIPTION 3136 "Index of the Forward Link Status table." 3137 ::={dvbRcsFwdStatusEntry 1} 3139 dvbRcsFwdStatusIfReference OBJECT-TYPE 3140 SYNTAX Unsigned32 (1..8) 3141 MAX-ACCESS read-only 3142 STATUS current 3143 DESCRIPTION 3144 "Cross reference to the interface table" 3145 ::={dvbRcsFwdStatusEntry 2} 3147 dvbRcsFwdStatusNetId OBJECT-TYPE 3148 SYNTAX Unsigned32 3149 MAX-ACCESS read-only 3150 STATUS current 3151 DESCRIPTION 3152 "Interactive network identifier of the forward 3153 link (from RCS Map Table)" 3154 ::={dvbRcsFwdStatusEntry 3} 3156 dvbRcsFwdStatusNetName OBJECT-TYPE 3157 SYNTAX SnmpAdminString 3158 MAX-ACCESS read-only 3159 STATUS current 3160 DESCRIPTION 3161 "The name of the interactive network of the forward 3162 link (from RCS Map Table)" 3163 ::={dvbRcsFwdStatusEntry 4} 3164 dvbRcsFwdStatusFormat OBJECT-TYPE 3165 SYNTAX INTEGER { 3166 dvbs (0), 3167 dvbs2ccm (1), 3168 dvbs2acm (2), 3169 reservedFormat (3) 3170 } 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "Specifies the transmission format applied on the 3175 forward link. Supported values are (from RMT): 3176 0: DVB-S 3177 1: DVB-S2 using CCM 3178 2: DVB-S2 using VCM or ACM 3179 3: reserved" 3180 ::={dvbRcsFwdStatusEntry 5} 3182 dvbRcsFwdStatusFrequency OBJECT-TYPE 3183 SYNTAX Unsigned32 3184 UNITS "x100 kHz" 3185 MAX-ACCESS read-only 3186 STATUS current 3187 DESCRIPTION 3188 "An estimate of the frequency of the forward link. Its 3189 value shall be given in multiple of 100 kHz." 3190 ::={dvbRcsFwdStatusEntry 6} 3192 dvbRcsFwdStatusPolar OBJECT-TYPE 3193 SYNTAX INTEGER { 3194 linearHorizontal (0), 3195 linearVertical (1), 3196 circularLeft (2), 3197 circularRight (3) 3198 } 3199 MAX-ACCESS read-only 3200 STATUS current 3201 DESCRIPTION 3202 "2-bit field giving the polarization of the forward link 3203 (from RMT): 3205 00: linear and horizontal 3206 01: linear and vertical 3207 10: circular left 3208 11: circular right" 3209 ::={dvbRcsFwdStatusEntry 7} 3211 dvbRcsFwdStatusInnerFec OBJECT-TYPE 3212 SYNTAX INTEGER { 3213 unknown (-1), 3214 fecRate12 (0), 3215 fecRate23 (1), 3216 fecRate34 (2), 3217 fecRate56 (3), 3218 fecRate78 (4), 3219 fecRate89 (5), 3220 fecRate35 (6), 3221 fecRate45 (7), 3222 fecRate910 (8), 3223 fecRate25 (9), 3224 fecRate13 (10), 3225 fecRate14 (11), 3226 noInnerCode (12) 3227 } 3228 MAX-ACCESS read-only 3229 STATUS current 3230 DESCRIPTION 3231 "Specifies the inner Forward Error Correction used on 3232 the forward link for transmission to the RCST. 3233 Supported values are: 3234 unknown (-1), 3235 fecRate1/2 (0), 3236 fecRate2/3 (1), 3237 fecRate3/4 (2), 3238 fecRate5/6 (3), 3239 fecRate7/8 (4), 3240 fecRate8/9 (5), 3241 fecRate3/5 (6), 3242 fecRate4/5 (7), 3243 fecRate9/10 (8), 3244 fecRate2/5 (9), 3245 fecRate1/3 (10), 3246 fecRate1/4 (11), 3247 noInnerCode (12) 3248 The RCST will report a value that has been used for 3249 transmission to the RCST within the most recent 60 3250 seconds. If this is not relevant, the RCST will report 3251 'unknown'." 3252 ::={dvbRcsFwdStatusEntry 8} 3254 dvbRcsFwdStatusSymbolRate OBJECT-TYPE 3255 SYNTAX Unsigned32 3256 UNITS "x100 symbols/s" 3257 MAX-ACCESS read-only 3258 STATUS current 3259 DESCRIPTION 3260 "An estimate of the symbol rate of the forward link. 3261 Its value shall be given in multiple of 100 symbol/s." 3262 ::={dvbRcsFwdStatusEntry 9} 3264 dvbRcsFwdStatusRolloff OBJECT-TYPE 3265 SYNTAX INTEGER { 3266 undefRolloff (0), 3267 rolloff020 (1), 3268 rolloff025 (2), 3269 rolloff035 (3) 3270 } 3271 MAX-ACCESS read-only 3272 STATUS current 3273 DESCRIPTION 3274 "An estimate of the roll-off applied on the forward 3275 link. 3276 Supported values are: 3277 0: undefined 3278 1: 0.20 3279 2: 0.25 3280 3: 0.35" 3281 ::={dvbRcsFwdStatusEntry 10} 3283 dvbRcsFwdStatusModulation OBJECT-TYPE 3284 SYNTAX INTEGER { 3285 unknown (0), 3286 mBPSK (1), 3287 mQPSK (2), 3288 m8PSK (3), 3289 m16APSK (4), 3290 m32APSK (5) 3291 } 3292 MAX-ACCESS read-only 3293 STATUS current 3294 DESCRIPTION 3295 "Indicates the modulation on the forward link used for 3296 transmission to the RCST. 3297 0: unknown 3298 1: BPSK 3299 2: QPSK 3300 3: 8PSK 3301 4: 16APSK 3302 5: 32APSK 3303 The RCST will report a value that has been used for 3304 transmission to the RCST within the most recent 60 3305 seconds. 3306 If this is not relevant, the RCST will report 3307 'unknown'." 3308 ::={dvbRcsFwdStatusEntry 11} 3310 dvbRcsFwdStatusFecFrame OBJECT-TYPE 3311 SYNTAX INTEGER { 3312 unknown (0), 3313 shortframe (1), 3314 longframe (2) 3315 } 3316 MAX-ACCESS read-only 3317 STATUS current 3318 DESCRIPTION 3319 "Indicates the frame length used on the forward link for 3320 transmission to the RCST. 3321 Supported values are: 3322 0: Unknown 3323 1: Short frame 3324 2: Normal frame 3325 The RCST will report a value that has been used for 3326 transmission to the RCST within the most recent 60 3327 seconds. 3329 If this is not relevant, the RCST will report 3330 'unknown'." 3331 ::={dvbRcsFwdStatusEntry 12} 3333 dvbRcsFwdStatusPilot OBJECT-TYPE 3334 SYNTAX INTEGER { 3335 unknown (0), 3336 pilotNotused (1), 3337 pilotUsed (2) 3338 } 3339 MAX-ACCESS read-only 3340 STATUS current 3341 DESCRIPTION 3342 "Indicates whether pilots are used on the forward link 3343 for transmission to the RCST. 3344 Supported values are: 3345 0: Unknown 3346 1: Pilots are not used 3347 2: Pilots are used 3348 The RCST will report a value that has been used for 3349 transmission to the RCST within the most recent 60 3350 seconds. 3351 If this is not relevant, the RCST will report 3352 'unknown'." 3353 ::={dvbRcsFwdStatusEntry 13} 3355 dvbRcsFwdStatusBer OBJECT-TYPE 3356 SYNTAX Integer32 3357 UNITS "exponent of 10" 3358 MAX-ACCESS read-only 3359 STATUS current 3360 DESCRIPTION 3361 "Provides the RCST BER on the Forward Link in log10 3362 units." 3363 ::={dvbRcsFwdStatusEntry 14} 3365 dvbRcsFwdStatusCnr OBJECT-TYPE 3366 SYNTAX Integer32 3367 UNITS "0.1 dB" 3368 MAX-ACCESS read-only 3369 STATUS current 3370 DESCRIPTION 3371 "Provides the RCST CNR on the Forward Link in 0.1 dB 3372 units." 3373 ::={dvbRcsFwdStatusEntry 15} 3375 dvbRcsFwdStatusRxPower OBJECT-TYPE 3376 SYNTAX Integer32 3377 UNITS "0.1 dBm" 3378 MAX-ACCESS read-only 3379 STATUS current 3380 DESCRIPTION 3381 "Provides the power level of the Forward Link as 3382 received at the IDU, in 0.1 dBm units." 3383 DEFVAL { -500 } 3384 ::={dvbRcsFwdStatusEntry 16} 3386 --============================================================== 3387 -- dvbRcsRtnConfig sub-tree object types 3388 --============================================================== 3389 dvbRcsRtnConfigMaxEirp OBJECT-TYPE 3390 SYNTAX Integer32 3391 UNITS "x0.1 dBm" 3392 MAX-ACCESS read-write 3393 STATUS current 3394 DESCRIPTION 3395 "Max EIRP of the RCST given in resolution of 0.1 dBm, 3396 applied when the IDU can itself set the necessary IDU 3397 TX output level e.g. when using a BUC that has a power 3398 level detector and provides sufficient feedback to the 3399 IDU." 3400 ::= {dvbRcsRtnConfig 1} 3402 dvbRcsRtnConfigDefIfLevel OBJECT-TYPE 3403 SYNTAX Integer32 3404 UNITS "x0.1 dBm" 3405 MAX-ACCESS read-write 3406 STATUS current 3407 DESCRIPTION 3408 "IDU TX output level applied in case the 3409 dvbRcsRtnConfigMaxEirp cannot be used. The resolution 3410 is 0.1 dBm and the accuracy is +/- 1 dBm." 3412 ::= {dvbRcsRtnConfig 2} 3414 --============================================================== 3415 -- dvbRcsRtnStatus sub-tree object types 3416 --============================================================== 3417 dvbRcsRtnStatusEbN0 OBJECT-TYPE 3418 SYNTAX Integer32 3419 UNITS "x0.1 dB" 3420 MAX-ACCESS read-only 3421 STATUS current 3422 DESCRIPTION 3423 "The EbN0 value reported for the return link, referenced 3424 to the regular SYNC burst transmission, in 0.1 dB 3425 units." 3426 ::= {dvbRcsRtnStatus 1} 3428 dvbRcsRtnStatusSFDuration OBJECT-TYPE 3429 SYNTAX Unsigned32 (250..7500) 3430 UNITS "0.1 ms" 3431 MAX-ACCESS read-only 3432 STATUS current 3433 DESCRIPTION 3434 "The duration of the currently applied return link 3435 super-frame structure, in tenths of milliseconds." 3436 ::= {dvbRcsRtnStatus 2} 3438 dvbRcsRtnStatusPayloadUnit OBJECT-TYPE 3439 SYNTAX INTEGER { 3440 unitATM (0), 3441 unitMPEG (1) 3442 } 3443 MAX-ACCESS read-only 3444 STATUS current 3445 DESCRIPTION 3446 "Indicates if the payload unit used for the return link 3447 is ATM or MPEG." 3448 ::= {dvbRcsRtnStatus 3} 3450 --============================================================= 3451 -- conformance information 3452 --============================================================= 3453 dvbRcsRcstGroups OBJECT IDENTIFIER ::= 3454 {dvbRcsConformance 1} 3455 dvbRcsRcstCompliances OBJECT IDENTIFIER ::= 3456 {dvbRcsConformance 2} 3458 --============================================================= 3459 -- conformance statements 3460 --============================================================= 3461 dvbRcsRcstCompliance1 MODULE-COMPLIANCE 3462 STATUS current 3463 DESCRIPTION 3464 "The compliance statement for DVB-RCS terminals that 3465 are compliant with SatLabs System Recommendations. 3466 Compliance is linked to the support by the terminal of 3467 the options or features defined in the SatLabs System 3468 Recommendations. 3469 The supported options and features of a terminal are 3470 declared in objects 3471 dvbRcsSystemSatLabsOptionsDeclaration 3472 and dvbRcsSystemSatLabsFeaturesDeclaration 3473 respectively." 3475 MODULE -- this module 3477 MANDATORY-GROUPS {dvbRcsRcstSystemGroup, 3478 dvbRcsRcstNetworkGroup, dvbRcsRcstInstallGroup, 3479 dvbRcsRcstQosGroup, dvbRcsRcstControlGroup, 3480 dvbRcsRcstStateGroup, dvbRcsFwdConfigGroup, 3481 dvbRcsFwdStatusGroup, dvbRcsRtnConfigGroup, 3482 dvbRcsRtnStatusGroup} 3484 GROUP dvbRcsRcstExtNetworkGroup 3485 DESCRIPTION 3486 "This group is mandatory for an RCST that supports extended 3487 networking management functionality. Such RCST is qualified 3488 as supporting the EXTNETWORK feature, as defined in the 3489 SatLabs System Recommendations." 3491 GROUP dvbRcsRcstDnsGroup 3492 DESCRIPTION 3493 "This group is mandatory for an RCST that supports the DNS 3494 protocol. Such RCST is qualified as supporting the DNS 3495 option, as defined in the SatLabs System Recommendations." 3497 GROUP dvbRcsRcstExtInstallGroup 3498 DESCRIPTION 3499 "This group is mandatory for an RCST that supports the 3500 installation log file. Such RCST is qualified as supporting 3501 the INSTALL_LOG feature, as defined in the SatLabs System 3502 Recommendations." 3504 GROUP dvbRcsRcstEnhancedClassifierGroup 3505 DESCRIPTION 3506 "This group is mandatory for an RCST that supports the 3507 enhanced classifier feature. Such RCST is qualified as 3508 supporting the ENHCLASSIFIER feature, as defined in the 3509 SatLabs System Recommendations." 3511 GROUP dvbRcsRcstMpegQosGroup 3512 DESCRIPTION 3513 "This group is mandatory for an RCST that supports MPEG 3514 traffic bursts. Such RCST is qualified as supporting the 3515 MPEG_TRF option, as defined in the SatLabs System 3516 Recommendations." 3518 GROUP dvbRcsRcstGlobalQosGroup 3519 DESCRIPTION 3520 "This group is mandatory for an RCST that supports global 3521 RCST QOS configuration data. Such RCST is qualified as 3522 supporting the RCST_PARA feature, as defined in the SatLabs 3523 System Recommendations." 3525 GROUP dvbRcsRcstStrictQosGroup 3526 DESCRIPTION 3527 "This group is mandatory for an RCST that supports strict 3528 channel ID dispatching. Such RCST is qualified as supporting 3529 the CHID_STRICT option, as defined in the SatLabs System 3530 Recommendations." 3532 GROUP dvbRcsRcstExtControlGroup 3533 DESCRIPTION 3534 "This group is mandatory for an RCST that supports extended 3535 control management functionality. Such RCST is qualified as 3536 supporting the EXTCONTROL feature, as defined in the SatLabs 3537 System Recommendations." 3539 GROUP dvbRcsRtnExtConfigGroup 3540 DESCRIPTION 3541 "This group is mandatory for an RCST that supports extended 3542 return link configuration management functionality. Such 3543 RCST is qualified as supporting the EXTCONFIG feature, as 3544 defined in the SatLabs System Recommendations." 3546 GROUP dvbRcsRtnExtStatusGroup 3547 DESCRIPTION 3548 "This group is mandatory for an RCST that supports extended 3549 return link status report functionality. Such RCST is 3550 qualified as supporting the EXTSTATUS feature, as defined in 3551 the SatLabs System Recommendations." 3553 GROUP dvbRcsRcstOduListGroup 3554 DESCRIPTION 3555 "This group is mandatory for an RCST that supports the ODU 3556 structural entities defined under dvbRcsOduTx, dvbRcsOduRx 3557 and dvbRcsOduAntenna. Such RCST is qualified as supporting 3558 the ODULIST feature, as defined in the SatLabs System 3559 Recommendations." 3561 OBJECT dvbRcsSystemOduAntennaSize 3562 MIN-ACCESS read-only 3563 DESCRIPTION 3564 "Write access must be supported if dvbRcsRcstOduListGroup is 3565 not supported." 3567 OBJECT dvbRcsSystemOduAntennaGain 3568 MIN-ACCESS read-only 3569 DESCRIPTION 3570 "Write access must be supported if dvbRcsRcstOduListGroup is 3571 not supported." 3573 OBJECT dvbRcsSystemOduSspa 3574 MIN-ACCESS read-only 3575 DESCRIPTION 3576 "Write access must be supported if dvbRcsRcstOduListGroup is 3577 not supported." 3579 OBJECT dvbRcsSystemOduTxType 3580 MIN-ACCESS read-only 3581 DESCRIPTION 3582 "Write access must be supported if dvbRcsRcstOduListGroup is 3583 not supported." 3585 OBJECT dvbRcsSystemOduRxType 3586 MIN-ACCESS read-only 3587 DESCRIPTION 3588 "Write access must be supported if dvbRcsRcstOduListGroup is 3589 not supported." 3591 OBJECT dvbRcsSystemOduRxBand 3592 MIN-ACCESS read-only 3593 DESCRIPTION 3594 "Write access must be supported if dvbRcsRcstOduListGroup is 3595 not supported." 3597 OBJECT dvbRcsSystemOduRxLO 3598 MIN-ACCESS read-only 3599 DESCRIPTION 3600 "Write access must be supported if dvbRcsRcstOduListGroup is 3601 not supported." 3603 OBJECT dvbRcsSystemOduTxLO 3604 MIN-ACCESS read-only 3605 DESCRIPTION 3606 "Write access must be supported if dvbRcsRcstOduListGroup is 3607 not supported." 3609 OBJECT dvbRcsNetworkOamInetAddressType 3610 SYNTAX InetAddressType { ipv4(1) } 3611 DESCRIPTION 3612 "An implementation is only required to support IPv4 3613 addresses." 3615 OBJECT dvbRcsNetworkOamInetAddress 3616 SYNTAX InetAddress (SIZE(4)) 3617 DESCRIPTION 3618 "An implementation is only required to support IPv4 3619 addresses." 3621 OBJECT dvbRcsNetworkLanInetAddressType 3622 SYNTAX InetAddressType { ipv4(1) } 3623 DESCRIPTION 3624 "An implementation is only required to support IPv4 3625 addresses." 3627 OBJECT dvbRcsNetworkLanInetAddress 3628 SYNTAX InetAddress (SIZE(4)) 3629 DESCRIPTION 3630 "An implementation is only required to support IPv4 3631 addresses." 3633 OBJECT dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType 3634 SYNTAX InetAddressType { ipv4(1) } 3635 DESCRIPTION 3636 "An implementation is only required to support IPv4 3637 addresses." 3639 OBJECT dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress 3640 SYNTAX InetAddress (SIZE(4)) 3641 DESCRIPTION 3642 "An implementation is only required to support IPv4 3643 addresses." 3645 OBJECT dvbRcsPrimaryDnsServerInetAddressType 3646 SYNTAX InetAddressType { ipv4(1) } 3647 DESCRIPTION 3648 "An implementation is only required to support IPv4 3649 addresses." 3651 OBJECT dvbRcsPrimaryDnsServerInetAddress 3652 SYNTAX InetAddress (SIZE(4)) 3653 DESCRIPTION 3654 "An implementation is only required to support IPv4 3655 addresses." 3657 OBJECT dvbRcsSecondaryDnsServerInetAddressType 3658 SYNTAX InetAddressType { ipv4(1) } 3659 DESCRIPTION 3660 "An implementation is only required to support IPv4 3661 addresses." 3663 OBJECT dvbRcsSecondaryDnsServerInetAddress 3664 SYNTAX InetAddress (SIZE(4)) 3665 DESCRIPTION 3666 "An implementation is only required to support IPv4 3667 addresses." 3669 OBJECT dvbRcsNetworkNccMgtInetAddressType 3670 SYNTAX InetAddressType { ipv4(1) } 3671 DESCRIPTION 3672 "An implementation is only required to support IPv4 3673 addresses." 3675 OBJECT dvbRcsNetworkNccMgtInetAddress 3676 SYNTAX InetAddress (SIZE(4)) 3677 DESCRIPTION 3678 "An implementation is only required to support IPv4 3679 addresses." 3681 OBJECT dvbRcsPktClassDscpLow 3682 MIN-ACCESS read-only 3683 DESCRIPTION 3684 "Create access only required if the RCST supports the 3685 enhanced classifier feature. Such RCST is qualified as 3686 supporting the ENHCLASSIFIER feature, as defined in the 3687 SatLabs System Recommendations." 3689 OBJECT dvbRcsPktClassDscpHigh 3690 MIN-ACCESS read-only 3691 DESCRIPTION 3692 "Create access only required if the RCST supports the 3693 enhanced classifier feature. Such RCST is qualified as 3694 supporting the ENHCLASSIFIER feature, as defined in the 3695 SatLabs System Recommendations." 3697 OBJECT dvbRcsPktClassDscpMarkValue 3698 MIN-ACCESS read-only 3699 DESCRIPTION 3700 "Create access only required if the RCST supports the 3701 enhanced classifier feature. Such RCST is qualified as 3702 supporting the ENHCLASSIFIER feature, as defined in the 3703 SatLabs System Recommendations." 3705 OBJECT dvbRcsPktClassSrcInetAddressType 3706 SYNTAX InetAddressType { ipv4(1) } 3707 DESCRIPTION 3708 "An implementation is only required to support IPv4 3709 addresses." 3711 OBJECT dvbRcsPktClassSrcInetAddress 3712 SYNTAX InetAddress (SIZE(4)) 3713 DESCRIPTION 3714 "An implementation is only required to support IPv4 3715 addresses." 3717 OBJECT dvbRcsPktClassDstInetAddressType 3718 SYNTAX InetAddressType { ipv4(1) } 3719 DESCRIPTION 3720 "An implementation is only required to support IPv4 3721 addresses." 3723 OBJECT dvbRcsPktClassDstInetAddress 3724 SYNTAX InetAddress (SIZE(4)) 3725 DESCRIPTION 3726 "An implementation is only required to support IPv4 3727 addresses." 3729 OBJECT dvbRcsPhbName 3730 MIN-ACCESS read-only 3731 DESCRIPTION 3732 "Create access only required if the RCST supports extended 3733 management support. Such RCST is qualified as supporting 3734 the SNMPMISC option, as defined in the SatLabs System 3735 Recommendations." 3737 OBJECT dvbRcsPhbRequestClassAssociation 3738 MIN-ACCESS read-only 3739 DESCRIPTION 3740 "Create access only required if the RCST supports extended 3741 management support. Such RCST is qualified as supporting 3742 the SNMPMISC option, as defined in the SatLabs System 3743 Recommendations." 3745 OBJECT dvbRcsPhbMappingRowStatus 3746 MIN-ACCESS read-only 3747 DESCRIPTION 3748 "Create access only required if the RCST supports extended 3749 management support. Such RCST is qualified as supporting 3750 the SNMPMISC option, as defined in the SatLabs System 3751 Recommendations." 3753 OBJECT dvbRcsRequestClassName 3754 MIN-ACCESS read-only 3755 DESCRIPTION 3756 "Write access only required if the RCST supports extended 3757 management support. Such RCST is qualified as supporting 3758 the SNMPMISC option, as defined in the SatLabs System 3759 Recommendations." 3761 OBJECT dvbRcsRequestClassChanId 3762 MIN-ACCESS read-only 3763 DESCRIPTION 3764 "Write access only required if the RCST supports extended 3765 management support. Such RCST is qualified as supporting 3766 the SNMPMISC option, as defined in the SatLabs System 3767 Recommendations." 3769 OBJECT dvbRcsRequestClassVccVpi 3770 MIN-ACCESS read-only 3771 DESCRIPTION 3772 "Write access only required if the RCST supports extended 3773 management support. Such RCST is qualified as supporting 3774 the SNMPMISC option, as defined in the SatLabs System 3775 Recommendations." 3777 OBJECT dvbRcsRequestClassVccVci 3778 MIN-ACCESS read-only 3779 DESCRIPTION 3780 "Write access only required if the RCST supports extended 3781 management support. Such RCST is qualified as supporting 3782 the SNMPMISC option, as defined in the SatLabs System 3783 Recommendations." 3785 OBJECT dvbRcsRequestClassPidPoolReference 3786 MIN-ACCESS not-accessible 3787 DESCRIPTION 3788 "Read-only access required if the RCST supports MPEG traffic 3789 Bursts, according to the MPEG_TRF option, as defined in the 3790 SatLabs System Recommendations. Write access only required 3791 if the RCST also supports extended management support, 3792 according to the SNMPMISC option, as defined in the SatLabs 3793 System Recommendations." 3795 OBJECT dvbRcsRequestClassCra 3796 MIN-ACCESS read-only 3797 DESCRIPTION 3798 "Write access only required if the RCST supports extended 3799 management support, according to the SNMPMISC option, as 3800 defined in the SatLabs System Recommendations." 3802 OBJECT dvbRcsRequestClassRbdcMax 3803 MIN-ACCESS read-only 3804 DESCRIPTION 3805 "Write access only required if the RCST supports extended 3806 management support, according to the SNMPMISC option, as 3807 defined in the SatLabs System Recommendations." 3809 OBJECT dvbRcsRequestClassRbdcTimeout 3810 MIN-ACCESS read-only 3811 DESCRIPTION 3812 "Write access only required if the RCST supports extended 3813 management support, according to the SNMPMISC option, as 3814 defined in the SatLabs System Recommendations." 3816 OBJECT dvbRcsRequestClassVbdcMax 3817 MIN-ACCESS read-only 3818 DESCRIPTION 3819 "Write access only required if the RCST supports extended 3820 management support, according to the SNMPMISC option, as 3821 defined in the SatLabs System Recommendations." 3823 OBJECT dvbRcsRequestClassVbdcTimeout 3824 MIN-ACCESS read-only 3825 DESCRIPTION 3826 "Write access only required if the RCST supports extended 3827 management support, according to the SNMPMISC option, as 3828 defined in the SatLabs System Recommendations." 3830 OBJECT dvbRcsRequestClassVbdcMaxBackLog 3831 MIN-ACCESS read-only 3832 DESCRIPTION 3833 "Write access only required if the RCST supports extended 3834 management support, according to the SNMPMISC option, as 3835 defined in the SatLabs System Recommendations." 3837 OBJECT dvbRcsRequestClassRowStatus 3838 MIN-ACCESS read-only 3839 DESCRIPTION 3840 "Write access only required if the RCST supports extended 3841 management support, according to the SNMPMISC option, as 3842 defined in the SatLabs System Recommendations." 3844 OBJECT dvbRcsPidValue 3845 MIN-ACCESS not-accessible 3846 DESCRIPTION 3847 "Read-only access required if the RCST supports MPEG traffic 3848 Bursts, according to the MPEG_TRF option, as defined in the 3849 SatLabs System Recommendations. Write access only required 3850 if the RCST also supports extended management support, 3851 according to the SNMPMISC option, as defined in the SatLabs 3852 System Recommendations." 3854 OBJECT dvbRcsPidPoolRowStatus 3855 MIN-ACCESS not-accessible 3856 DESCRIPTION 3857 "Read-only access required the RCST supports MPEG traffic 3858 Bursts, according to the MPEG_TRF option, as defined in the 3859 SatLabs System Recommendations. Write access only required 3860 if the RCST also supports extended management support, 3861 according to the SNMPMISC option, as defined in the SatLabs 3862 System Recommendations." 3864 ::= {dvbRcsRcstCompliances 1} 3866 --============================================================= 3867 -- units of conformance 3868 --============================================================= 3870 --============================================================= 3871 -- object groups for RCST system 3872 --============================================================= 3873 dvbRcsRcstSystemGroup OBJECT-GROUP 3874 OBJECTS { 3875 dvbRcsSystemMibRevision, 3876 dvbRcsSystemSatLabsProfilesDeclaration, 3877 dvbRcsSystemSatLabsOptionsDeclaration, 3878 dvbRcsSystemSatLabsFeaturesDeclaration, 3879 dvbRcsSystemLocation, 3880 dvbRcsSystemOduAntennaSize, 3881 dvbRcsSystemOduAntennaGain, 3882 dvbRcsSystemOduSspa, 3883 dvbRcsSystemOduTxType, 3884 dvbRcsSystemOduRxType, 3885 dvbRcsSystemOduRxBand, 3886 dvbRcsSystemOduRxLO, 3887 dvbRcsSystemOduTxLO, 3888 dvbRcsTcpPep, 3889 dvbRcsHttpPep 3890 } 3891 STATUS current 3892 DESCRIPTION 3893 "A collection of objects providing information 3894 applicable for basic device management support." 3895 ::= {dvbRcsRcstGroups 1} 3897 --============================================================= 3898 -- object groups for RCST networking 3899 --============================================================= 3900 dvbRcsRcstNetworkGroup OBJECT-GROUP 3901 OBJECTS { 3902 dvbRcsNetworkOamInetAddressType, 3903 dvbRcsNetworkOamInetAddress, 3904 dvbRcsNetworkOamInetAddressPrefixLength, 3905 dvbRcsNetworkLanInetAddressType, 3906 dvbRcsNetworkLanInetAddress, 3907 dvbRcsNetworkLanInetAddressPrefixLength, 3908 dvbRcsNetworkConfigFileDownloadUrl, 3909 dvbRcsNetworkConfigFileUploadUrl, 3910 dvbRcsNetworkLogFileUploadUrl 3911 } 3912 STATUS current 3913 DESCRIPTION 3914 "A collection of objects providing basic networking 3915 management support." 3916 ::= {dvbRcsRcstGroups 2} 3918 dvbRcsRcstExtNetworkGroup OBJECT-GROUP 3919 OBJECTS { 3920 dvbRcsNetworkOamInetAddressAssign, 3921 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressType, 3922 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress, 3923 dvbRcsNetworkAirInterfaceDefaultGatewayInetAddressPrefixLength, 3924 dvbRcsNetworkNccMgtInetAddressType, 3925 dvbRcsNetworkNccMgtInetAddress, 3926 dvbRcsNetworkNccMgtInetAddressPrefixLength 3927 } 3928 STATUS current 3929 DESCRIPTION 3930 "A collection of objects providing extended networking 3931 management support." 3932 ::= {dvbRcsRcstGroups 3} 3934 dvbRcsRcstDnsGroup OBJECT-GROUP 3935 OBJECTS { 3936 dvbRcsPrimaryDnsServerInetAddressType, 3937 dvbRcsPrimaryDnsServerInetAddress, 3938 dvbRcsPrimaryDnsServerInetAddressPrefixLength, 3939 dvbRcsSecondaryDnsServerInetAddressType, 3940 dvbRcsSecondaryDnsServerInetAddress, 3941 dvbRcsSecondaryDnsServerInetAddressPrefixLength 3942 } 3943 STATUS current 3944 DESCRIPTION 3945 "A collection of objects providing DNS management 3946 support." 3947 ::= {dvbRcsRcstGroups 4} 3949 --============================================================= 3950 -- object groups for RCST installation 3951 --============================================================= 3953 dvbRcsRcstInstallGroup OBJECT-GROUP 3954 OBJECTS { 3955 dvbRcsInstallAntennaAlignmentState, 3956 dvbRcsInstallCwFrequency, 3957 dvbRcsInstallCwMaxDuration, 3958 dvbRcsInstallCwPower, 3959 dvbRcsInstallCoPolReading, 3960 dvbRcsInstallXPolReading, 3961 dvbRcsInstallCoPolTarget, 3962 dvbRcsInstallXPolTarget, 3963 dvbRcsInstallStandByDuration, 3964 dvbRcsInstallTargetEsN0 3965 } 3966 STATUS current 3967 DESCRIPTION 3968 "A collection of objects providing information 3969 applicable for basic installation support." 3970 ::= {dvbRcsRcstGroups 5} 3972 dvbRcsRcstExtInstallGroup OBJECT-GROUP 3973 OBJECTS { 3974 dvbRcsNetworkInstallLogFileDownloadUrl, 3975 dvbRcsNetworkInstallLogFileUploadUrl 3976 } 3977 STATUS current 3978 DESCRIPTION 3979 "A collection of objects providing extended device 3980 installation support." 3981 ::= {dvbRcsRcstGroups 6} 3982 --============================================================= 3983 -- object groups for QOS 3984 --============================================================= 3986 dvbRcsRcstQosGroup OBJECT-GROUP 3987 OBJECTS { 3988 dvbRcsPktClassDscpLow, 3989 dvbRcsPktClassDscpHigh, 3990 dvbRcsPktClassDscpMarkValue, 3991 dvbRcsPktClassPhbAssociation, 3992 dvbRcsPktClassRowStatus, 3993 dvbRcsPhbName, 3994 dvbRcsPhbRequestClassAssociation, 3995 dvbRcsPhbMappingRowStatus, 3996 dvbRcsRequestClassName, 3997 dvbRcsRequestClassChanId, 3998 dvbRcsRequestClassVccVpi, 3999 dvbRcsRequestClassVccVci, 4000 dvbRcsRequestClassCra, 4001 dvbRcsRequestClassRbdcMax, 4002 dvbRcsRequestClassRbdcTimeout, 4003 dvbRcsRequestClassVbdcMax, 4004 dvbRcsRequestClassVbdcTimeout, 4005 dvbRcsRequestClassVbdcMaxBackLog, 4006 dvbRcsRequestClassRowStatus 4007 } 4008 STATUS current 4009 DESCRIPTION 4010 "A collection of objects providing basic access to QOS 4011 configuration data." 4012 ::= {dvbRcsRcstGroups 7} 4014 dvbRcsRcstEnhancedClassifierGroup OBJECT-GROUP 4015 OBJECTS { 4016 dvbRcsPktClassIpProtocol, 4017 dvbRcsPktClassSrcInetAddressType, 4018 dvbRcsPktClassSrcInetAddress, 4019 dvbRcsPktClassSrcInetAddressPrefixLength, 4020 dvbRcsPktClassDstInetAddressType, 4021 dvbRcsPktClassDstInetAddress, 4022 dvbRcsPktClassDstInetAddressPrefixLength, 4023 dvbRcsPktClassSrcPortLow, 4024 dvbRcsPktClassSrcPortHigh, 4025 dvbRcsPktClassDstPortLow, 4026 dvbRcsPktClassDstPortHigh, 4027 dvbRcsPktClassVlanUserPri 4028 } 4029 STATUS current 4030 DESCRIPTION 4031 "A collection of objects providing support for 4032 management of the enhanced classifier." 4033 ::= {dvbRcsRcstGroups 8} 4035 dvbRcsRcstMpegQosGroup OBJECT-GROUP 4036 OBJECTS { 4037 dvbRcsRequestClassPidPoolReference, 4038 dvbRcsPidValue, 4039 dvbRcsPidPoolRowStatus 4040 } 4041 STATUS current 4042 DESCRIPTION 4043 "A collection of objects providing access to MPEG 4044 related link QOS configuration data." 4045 ::= {dvbRcsRcstGroups 9} 4047 dvbRcsRcstGlobalQosGroup OBJECT-GROUP 4048 OBJECTS { 4049 dvbRcsQosGlobalRbdcMax, 4050 dvbRcsQosGlobalVbdcMax, 4051 dvbRcsQosGlobalVbdcMaxBackLog 4052 } 4053 STATUS current 4054 DESCRIPTION 4055 "A collection of objects providing access to global RCST 4056 QOS configuration data." 4057 ::= {dvbRcsRcstGroups 10} 4059 dvbRcsRcstStrictQosGroup OBJECT-GROUP 4060 OBJECTS { 4061 dvbRcsQosChannelIdStrictDispatching 4062 } 4064 STATUS current 4065 DESCRIPTION 4066 "A collection of objects allowing management of strict 4067 channel ID dispatching." 4068 ::= {dvbRcsRcstGroups 11} 4070 --============================================================= 4071 -- object groups for RCST control 4072 --============================================================= 4073 dvbRcsRcstControlGroup OBJECT-GROUP 4074 OBJECTS { 4075 dvbRcsCtrlRebootCommand, 4076 dvbRcsCtrlUserTrafficDisable, 4077 dvbRcsCtrlCwEnable, 4078 dvbRcsCtrlDownloadFileCommand, 4079 dvbRcsCtrlUploadFileCommand, 4080 dvbRcsCtrlActivateConfigFileCommand, 4081 dvbRcsCtrlRcstRxReacquire 4082 } 4083 STATUS current 4084 DESCRIPTION 4085 "A collection of objects allowing basic RCST control." 4086 ::= {dvbRcsRcstGroups 12} 4088 dvbRcsRcstExtControlGroup OBJECT-GROUP 4089 OBJECTS { 4090 dvbRcsCtrlRcstTxDisable, 4091 dvbRcsCtrlOduTxReferenceEnable, 4092 dvbRcsCtrlOduTxDCEnable, 4093 dvbRcsCtrlOduRxDCEnable, 4094 dvbRcsCtrlRcstLogonCommand, 4095 dvbRcsCtrlRcstLogoffCommand 4096 } 4097 STATUS current 4098 DESCRIPTION 4099 "A collection of objects allowing extended RCST 4100 control." 4101 ::= {dvbRcsRcstGroups 13} 4103 --============================================================= 4104 -- object groups for RCST state 4105 --============================================================= 4107 dvbRcsRcstStateGroup OBJECT-GROUP 4108 OBJECTS { 4109 dvbRcsRcstMode, 4110 dvbRcsRcstFaultStatus, 4111 dvbRcsRcstFwdLinkStatus, 4112 dvbRcsRcstLogUpdated, 4113 dvbRcsRcstCurrentSoftwareVersion, 4114 dvbRcsRcstAlternateSoftwareVersion, 4115 dvbRcsRcstActivatedConfigFileVersion, 4116 dvbRcsRcstDownloadedConfigFileVersion 4117 } 4118 STATUS current 4119 DESCRIPTION 4120 "A collection of objects allowing access to RCST state." 4121 ::= {dvbRcsRcstGroups 14} 4123 --============================================================= 4124 -- object groups for forward link 4125 --============================================================= 4127 dvbRcsFwdConfigGroup OBJECT-GROUP 4128 OBJECTS { 4129 dvbRcsFwdStartPopId, 4130 dvbRcsFwdStartFrequency, 4131 dvbRcsFwdStartPolar, 4132 dvbRcsFwdStartFormat, 4133 dvbRcsFwdStartRolloff, 4134 dvbRcsFwdStartSymbolRate, 4135 dvbRcsFwdStartInnerFec, 4136 dvbRcsFwdStartRowStatus 4137 } 4138 STATUS current 4139 DESCRIPTION 4140 "A collection of objects providing basic start forward 4141 link configuration support." 4142 ::= {dvbRcsRcstGroups 15} 4144 dvbRcsFwdStatusGroup OBJECT-GROUP 4145 OBJECTS { 4146 dvbRcsFwdStatusPopId, 4147 dvbRcsFwdStatusIfReference, 4148 dvbRcsFwdStatusNetId, 4149 dvbRcsFwdStatusNetName, 4150 dvbRcsFwdStatusFormat, 4151 dvbRcsFwdStatusFrequency, 4152 dvbRcsFwdStatusPolar, 4153 dvbRcsFwdStatusInnerFec, 4154 dvbRcsFwdStatusSymbolRate, 4155 dvbRcsFwdStatusRolloff, 4156 dvbRcsFwdStatusModulation, 4157 dvbRcsFwdStatusFecFrame, 4158 dvbRcsFwdStatusPilot, 4159 dvbRcsFwdStatusBer, 4160 dvbRcsFwdStatusCnr, 4161 dvbRcsFwdStatusRxPower 4162 } 4163 STATUS current 4164 DESCRIPTION 4165 "A collection of objects providing forward link status." 4166 ::= {dvbRcsRcstGroups 16} 4168 --============================================================= 4169 -- object groups for return link 4170 --============================================================= 4172 dvbRcsRtnConfigGroup OBJECT-GROUP 4173 OBJECTS { 4174 dvbRcsRtnConfigDefIfLevel 4175 } 4176 STATUS current 4177 DESCRIPTION 4178 "A collection of objects providing basic return link 4179 configuration support." 4180 ::= {dvbRcsRcstGroups 17} 4182 dvbRcsRtnExtConfigGroup OBJECT-GROUP 4183 OBJECTS { 4184 dvbRcsRtnConfigMaxEirp 4185 } 4186 STATUS current 4187 DESCRIPTION 4188 "A collection of objects providing extended return link 4189 configuration support." 4190 ::= {dvbRcsRcstGroups 18} 4192 dvbRcsRtnStatusGroup OBJECT-GROUP 4193 OBJECTS { 4194 dvbRcsRtnStatusPayloadUnit 4195 } 4196 STATUS current 4197 DESCRIPTION 4198 "A collection of objects allowing access to return link 4199 status." 4200 ::= {dvbRcsRcstGroups 19} 4202 dvbRcsRtnExtStatusGroup OBJECT-GROUP 4203 OBJECTS { 4204 dvbRcsRcstRtnLinkStatus, 4205 dvbRcsRtnStatusEbN0, 4206 dvbRcsRtnStatusSFDuration 4207 } 4208 STATUS current 4209 DESCRIPTION 4210 "A collection of objects allowing access to extended 4211 return link status." 4212 ::= {dvbRcsRcstGroups 20} 4214 dvbRcsRcstOduListGroup OBJECT-GROUP 4215 OBJECTS { 4216 dvbRcsOduTxTypeDescription, 4217 dvbRcsOduTxType, 4218 dvbRcsOduRxTypeDescription, 4219 dvbRcsOduRxType, 4220 dvbRcsOduAntennaTypeDescription, 4221 dvbRcsOduAntennaType 4222 } 4223 STATUS current 4224 DESCRIPTION 4225 "A collection of objects supporting flexible 4226 selection of ODU devices." 4227 ::= {dvbRcsRcstGroups 21} 4228 END 4230 XXX NOTE: RFC Editor please amend the lines below to reflect 4231 copyright policy for publication of MIBs. 4233 Copyright (c) 2009 IETF Trust and the persons identified as 4234 authors of the code. All rights reserved. 4236 Redistribution and use in source and binary forms, with or 4237 without modification, are permitted provided that the following 4238 conditions are met: 4240 * Redistributions of source code must retain the above copyright 4241 notice, this list of conditions and the following disclaimer. 4243 * Redistributions in binary form must reproduce the above 4244 copyright notice, this list of conditions and the following 4245 disclaimer in the documentation and/or other materials provided 4246 with the distribution. 4248 * Neither the name of Internet Society, IETF or IETF Trust, nor 4249 the names of specific contributors, may be used to endorse or 4250 promote products derived from this software without specific 4251 prior written permission. 4253 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 4254 CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, 4255 INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 4256 MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 4257 DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR 4258 CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 4259 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 4260 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF 4261 USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED 4262 AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 4263 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 4264 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 4265 THE POSSIBILITY OF SUCH DAMAGE. 4267 5. Security Considerations 4269 This MIB module relates to a system that allows end-users to 4270 access a private network or public internet access. As such, 4271 improper manipulation of the MIB objects represented by this MIB 4272 module may result in denial of service to a large number of end- 4273 users. 4275 There are a number of management objects defined in this MIB 4276 module with a MAX-ACCESS clause of read-write and/or read- 4277 create. Such objects may be considered sensitive or vulnerable 4278 in some network environments. The support for SET operations in 4279 a non-secure environment without proper protection can have a 4280 negative effect on network operations. These are the tables and 4281 objects and their sensitivity/vulnerability: 4283 o The use of the dvbRcsNetworkNccMgtInetAddress object to 4284 specify management stations is considered only limited 4285 protection and does not protect against attacks that spoof 4286 the management station's IP address. The use of stronger 4287 mechanisms, such as SNMPv3 security, should be considered, 4288 where possible. 4290 o The dvbRcsSystemOdu objects, dvbRcsCtrlCwEnable, 4291 dvbRcsRtnConfigMaxEirp, dvbRcsRtnConfigDefIfLevel objects and 4292 dvbRcsRcstInstall sub-tree can, if improperly or maliciously 4293 used, lead to unwanted emissions or emission levels on the 4294 satellite uplink, thereby resulting in potential degradation 4295 of the RCS service or other services using the frequency band 4296 being used. 4298 o The RCST may have its configuration file changed by the 4299 actions of the management system using a combination of the 4300 following objects: dvbRcsNetworkInstallLogFileDownloadUrl, 4301 dvbRcsCtrlDownloadFileCommand, 4302 dvbRcsCtrlActivateConfigFileCommand or 4303 dvbRcsCtrlRebootCommand. An improper configuration file 4304 download may result in substantial vulnerabilities and the 4305 loss of the ability of the management system to control the 4306 satellite terminal. 4308 o Setting dvbRcsNetworkLogFileUploadUrl to a wrong address may 4309 potentially impact debugging/troubleshooting efforts. 4311 o Setting objects in dvbRcsPktClassTable could cause 4312 significant changes to default traffic filtering on a RCST. 4314 Some of the readable objects in this MIB module (i.e., objects 4315 with a MAX-ACCESS other than not-accessible) may be considered 4316 sensitive or vulnerable in some network environments. It is 4317 thus important to control even GET access to these objects and 4318 possibly to even encrypt the values of these objects when 4319 sending them over the network via SNMP. These are the tables and 4320 objects and their sensitivity/vulnerability: 4322 o The dvbRcsNetworkNccMgtInetAddress object may provide 4323 sufficient information for attackers to spoof management 4324 stations that have management access to the device. 4326 o The dvbRcsRcstCurrentSoftwareVersion object may provide hints 4327 as to the software vulnerabilities of the cable device. 4329 o The object dvbRcsNetworkOamInetAddress and the table 4330 dvbRcsPktClassTable may provide clues for attacking the cable 4331 device and other subscriber devices. 4333 SNMP versions prior to SNMPv3 did not include adequate security. 4334 Even if the network itself is secure (for example by using 4335 IPsec), even then, there is no control as to who on the secure 4336 network is allowed to access and GET/SET 4337 (read/change/create/delete) the objects in this MIB module. 4339 It is RECOMMENDED that implementers consider the security 4340 features provided by the SNMPv3 framework (see [RFC3410], 4341 section 8), including full support for the SNMPv3 cryptographic 4342 mechanisms (for authentication and privacy). 4344 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4345 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4346 enable cryptographic security. It is then a customer/operator 4347 responsibility to ensure that the SNMP entity giving access to 4348 an instance of this MIB module, is properly configured to give 4349 access to the objects only to those principals (users) that have 4350 legitimate rights to indeed GET or SET (change/create/delete) 4351 them. 4353 6. IANA Considerations 4355 This document includes no request to IANA. The transmission and 4356 ifType numbers described in Section 3 have already been assigned 4357 under the smi-numbers registry. 4359 7. Acknowledgments 4361 The authors thank Gorry Fairhurst for advice in the preparation 4362 of this document. 4364 The authors recognize this document is a collective effort of 4365 the SatLabs Group (www.satlabs.org), in particular the many 4366 corrections and suggestions brought by Juan Luis Manas. 4368 8. References 4370 8.1. Normative References 4372 [IANA] Internet Assigned Numbers Authority, "Internet 4373 Assigned Numbers Authority", June 2008, 4374 . 4376 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4377 Requirement Levels", BCP 14, RFC 2119, March 1997 4378 (BEST CURRENT PRACTICE). 4380 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4381 Schoenwaelder, Ed., "Structure of Management 4382 Information, Version 2 (SMIv2)", STD 58, RFC 2578, 4383 April 1999. 4385 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4386 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 4387 STD 58, RFC 2579, April 1999. 4389 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 4390 "Conformance Statements for SMIv2", STD 58, RFC 2580, 4391 April 1999. 4393 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group 4394 MIB", RFC 2863, June 2000. 4396 [RFC3289] F. Baker, K. Chan, A. Smith, "Management Information 4397 Base for the Differentiated Services Architecture", 4398 RFC 3289, May 2002. 4400 [RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture 4401 for Describing Simple Network Management Protocol 4402 (SNMP) Management Frameworks ", RFC 3411, December 4403 2002. 4405 [RFC4001] M. Daniele, B. Haberman, S. Routhier, J. 4406 Schoenwaelder, "Textual Conventions for Internet 4407 Network Addresses", RFC 4001, February 2005. 4409 [RFC5017] D. McWalter, Ed., "MIB Textual Conventions for Uniform 4410 Resource Identifiers (URIs)", RFC 5017, September 4411 2007. 4413 8.2. Informative References 4415 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 4416 Generic Coding of Moving Pictures and Associated Audio 4417 Information Systems", International Standardisation 4418 Organisation (ISO). 4420 [ITU-ATM] ITU-T Recommendation I.432 (all parts): "B-ISDN user- 4421 network interface - Physical layer specification". 4423 [ITU-AAL5] ITU-T Recommendation I.363-5 (1996): "B-ISDN ATM 4424 Adaptation Layer specification: Type 5 AAL". 4426 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 4427 Specifications for Data Broadcasting", European 4428 Telecommunications Standards Institute (ETSI). 4430 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); 4431 Modulation and Coding for DBS satellite systems at 4432 11/12 GHz", European Telecommunications Standards 4433 Institute (ETSI). 4435 [ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB); 4436 Second generation framing structure, channel coding 4437 and modulation systems for Broadcasting, Interactive 4438 Services, News Gathering and other broadband satellite 4439 applications", European Telecommunications Standards 4440 Institute (ETSI). 4442 [ETSI-GSE] ETSI TS 102 606 "Digital Video Broadcasting (DVB); 4443 Generic Stream Encapsulation (GSE) Protocol", European 4444 Telecommunications Standards Institute (ETSI). 4446 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 4447 Interaction Channel for Satellite Distribution 4448 Systems", European Telecommunications Standards 4449 Institute (ETSI). 4451 [ETSI-SI] ETSI EN 300 468 "Digital Video Broadcasting (DVB); 4452 Specification for Service Information (SI) in DVB 4453 Systems", European Telecommunications Standards 4454 Institute (ETSI). 4456 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 4457 "Introduction and Applicability Statements for 4458 Internet-Standard Management Framework", RFC 3410, 4459 December 2002. 4461 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- 4462 Nocker, B., and H. Linder, "A Framework for 4463 Transmission of IP Datagrams over MPEG-2 Networks", 4464 RFC 4259, November 2005. 4466 [SATLABS] SatLabs System Recommendations. Available at 4467 www.satlabs.org. 4469 9. Authors' Addresses 4471 Stephane Combes 4472 ESTEC 4473 European Space Agency 4474 Keplerlaan 1 4475 P.O. Box 299 4476 2200 AG Noordwijk ZH 4477 The Netherlands 4479 Email: stephane.combes@esa.int 4480 URL: telecom.esa.int 4482 Petter Chr. Amundsen 4483 VeriSat AS 4484 P.O Box 1 4485 1330 Fornebu 4486 Norway 4488 Email: pca@verisat.no 4489 URL: www.verisat.no 4491 Micheline Lambert 4492 Advantech Satellite Networks 4493 2341 boul. Alfred-Nobel 4494 Saint-Laurent (Montreal) 4495 H4S 2A9 4496 Quebec, Canada 4498 Email: micheline.lambert@advantechamt.com 4499 URL: www.advantechsatnet.com 4501 Hans-Peter Lexow 4502 STM Norway 4503 Vollsveien 21 4504 1366 Lysaker 4505 Norway 4507 Email: hlexow@stmi.com 4508 URL: www.stmi.com 4510 10. Disclaimer 4512 This document may contain material from IETF Documents or IETF 4513 Contributions published or made publicly available before 4514 November 10, 2008. The person(s) controlling the copyright in 4515 some of this material may not have granted the IETF Trust the 4516 right to allow modifications of such material outside the IETF 4517 Standards Process. 4518 Without obtaining an adequate license from the person(s) 4519 controlling the copyright in such materials, this document may 4520 not be modified outside the IETF Standards Process, and 4521 derivative works of it may not be created outside the IETF 4522 Standards Process, except to format it for publication as an RFC 4523 or to translate it into languages other than English. 4525 11. Copyright Notice 4527 Copyright (c) 2009 IETF Trust and the persons identified as the 4528 document authors. All rights reserved. 4530 This document is subject to BCP 78 and the IETF Trust's Legal 4531 Provisions Relating to IETF Documents in effect on the date of 4532 publication of this document (http://trustee.ietf.org/license- 4533 info). Please review these documents carefully, as they 4534 describe your rights and restrictions with respect to this 4535 document. 4537 11.1. License for Code Components 4539 XXX NOTE: RFC Editor please amend the lines below to reflect 4540 copyright policy for publication of MIBs. 4542 A copyright note for the Code Components is provided at the end 4543 of Section 4. In addition to the licenses granted above, Code 4544 Components are also licensed to each person who wishes to 4545 receive such a license on the terms of the "BSD License", as 4546 described below. The Legal Provisions are specified in the IETF 4547 Trust's Legal Provisions Relating to IETF Documents in effect on 4548 the date of publication of this document 4549 (http://trustee.ietf.org/license-info). 4550 <<< RFC Ed Note: please remove the text below, prior to 4551 publications >>> 4553 Change Log. 4555 Rev -00 4557 * First draft, for comment by the community. 4559 Rev -01 4561 * Second draft, for comment by the community. 4563 The MIB module is renamed DVBRCS-MIB to reflect that it covers 4564 more than solely interface issues. 4566 The MIB has been updated with 4568 * a conformance section that captures the options 4570 * structural changes and corrections to achieve this 4572 * SYNTAX refinements where applicable 4574 * UNITS declarations where applicable 4576 Document reformatted to conform to I-D format conventions. 4578 Rev -02 4580 * Third draft, for comment by the community. 4582 Update following comments received from the ipdvb list (Gorry 4583 Fairhurst). 4585 Rev -03 4587 * Fourth draft, for comment by the community. 4589 Update following comments received from Martin Stiemerling and 4590 complement/corrections from the SatLabs Group. 4592 Rev -04 4594 * Fifth draft 4595 Corrected read-write into read-create MAXACCESS for objects in 4596 requestClassTable and pidPoolTable. 4598 Minor updates to correct format of tables and some MIB comments. 4600 Rev -05 4602 * Sixth draft 4604 Addition of dvbRcs prefix to all descriptors, following request 4605 from MIB doctor (according to Appendix C of RFC 4181). 4607 Clarification and complements brought to ODU configuration 4608 objects (see section 3.4.1), ODU structural entities definition 4609 in dvbRcsRcstSystem group and conformance section. 4611 Modification of the interface types usage (section 3.3) in order 4612 to have alignment with Ethernet interface (dvbRcsMacLayer should 4613 count link layer packets and bytes, like Ethernet does, and not 4614 IP). 4616 Updated copyright to reflect current IETF Trust guidelines and 4617 advice from Dan Romascanu. 4619 Rev -06 4621 * Seventh draft 4623 Updated following MIB doctor review. Adjustments based on the 4624 MIB authoring guidelines from the IETF: 4625 o I-D renamed 4627 o Used name instead of number for DEFVAL where appropriate 4629 o Clarification added in the MIB module description regarding 4630 persistency behavior of objects 4632 o Integer32 replaced with Unsigned32 where appropriate 4634 o Obsoleted OBJECT-TYPES (DisplayString, IpAddress) replaced 4635 with SnmpAdminString, RFC 4001 and RFC 5017 TCs. Added 4636 conformance statements mandating IPv4 support only. 4638 o Clarification of the conformance clauses added in the MODULE- 4639 COMPLIANCE description and the following GROUPs and OBJECTs 4640 descriptions. 4642 o Re-organization of some conformance groups. Each group now 4643 refers to precise options or features. 5 new features 4644 (specified through dvbRcsSystemSatLabsFeaturesDeclaration 4645 object) are therefore defined: ODULIST, EXTNETWORK, 4646 EXTCONTROL, EXTCONFIG, EXTSTATUS. 4648 o Clarification in the RowStatus OBJECTs description whether 4649 writable objects in the dynamically created rows can change 4650 value while the RowStatus object is active. 4652 o Security section expanded. 4654 Rev -07 4656 * Eighth draft 4658 Updated following MIB doctor review. 4660 o Objects dvbRcsNetworkAirInterfaceDefaultGatewayInetAddress 4661 PrefixLength, dvbRcsPrimaryDnsServerInetAddressPrefixLength, 4662 dvbRcsSecondaryDnsServerInetAddressPrefixLength, 4663 dvbRcsNetworkNccMgtInetAddressPrefixLength were missing. 4665 o Size limit added to Uri objects 4667 o It is now described in InetAddressObjects that they are to be 4668 interpreted as defined by the corresponding 4669 InetAddressObjectType. 4671 o Dscp and DscpOrAny TC from Diffserv MIB are now used. 4673 o dvbRcsPktClassSrcInetAddressType and 4674 dvbRcsPktClassDstInetAddressType corrected to read-create 4676 o Syntax for dvbRcsSystemOduAntennaSize corrected to Unsigned32 4678 o Details of interpretation of dvbRcsSystemSatLabsXxDeclaration 4679 objects now reside in the associated TC descriptions. 4681 o Addition of RFC3289, RFC3411, RFC4001, RFC5017 as normative 4682 references. 4684 <<>