idnits 2.17.1 draft-combes-ipdvb-mib-rcs-05.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: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 8 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 215 has weird spacing: '... dBi deci...' == Line 217 has weird spacing: '... dBm deci...' == Line 705 has weird spacing: '...vel, if the T...' == Line 1135 has weird spacing: '...scribed here....' == Line 1944 has weird spacing: '...vity is inact...' == 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 (May 11, 2009) is 5463 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Transport Area Working Group S. Combes 2 Internet-Draft P. Amundsen 3 Intended status: Informational M. Lambert 4 H-P. Lexow 5 SatLabs Group 6 Expires: November 2009 May 11, 2009 8 The DVB-RCS MIB 9 draft-combes-ipdvb-mib-rcs-05.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 This document may not be modified, and derivative works of it may not 17 be created, except to format it for publication as an RFC or to 18 translate it into languages other than English. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 This Internet-Draft will expire on November 11, 2009. 38 Abstract 40 This document describes the MIB module for the Digital Video 41 Broadcasting Return Channel via Satellite system (DVB-RCS). It 42 defines a set of MIB entities to characterize the behavior and 43 performance of network layer entities deploying DVB-RCS. 45 Table of Contents 47 1. Introduction...................................................3 48 2. Conventions used in this document..............................4 49 2.1. Abbreviations.............................................5 50 2.2. Glossary..................................................7 51 2.2.1. Star DVB-RCS network.................................7 52 2.2.2. Mesh DVB-RCS network.................................7 53 2.2.3. Transparent DVB-RCS network..........................7 54 2.2.4. Regenerative DVB-RCS network.........................7 55 2.2.5. DVB-RCS MAC layer....................................8 56 2.2.6. DVB-RCS TDM..........................................8 57 2.2.7. DVB-RCS TDMA.........................................8 58 2.2.8. IDU..................................................8 59 2.2.9. ODU..................................................8 60 2.2.10. RCST................................................8 61 2.2.11. NCC.................................................9 62 2.2.12. Configuration file..................................9 63 2.2.13. Log file............................................9 64 2.2.14. Installation log file...............................9 65 2.2.15. Antenna alignment...................................9 66 2.2.16. CW frequency........................................9 67 2.2.17. Request Class.......................................9 68 2.2.18. Channel ID..........................................9 69 2.2.19. ATM profile........................................10 70 2.2.20. MPEG profile.......................................10 71 2.2.21. PID pool...........................................10 72 2.2.22. Capacity Categories................................10 73 2.2.23. Start transponder..................................11 74 2.2.24. DVB-S..............................................11 75 2.2.25. DVB-S2 and CCM/VCM/ACM.............................11 76 2.2.26. Interactive Network................................12 77 3. MIB Module overview...........................................12 78 3.1. Textual Conventions......................................13 79 3.2. Structure of the MIB.....................................13 80 3.3. Relationship to the Interfaces MIB Module................14 81 3.4. MIB groups description...................................18 82 3.4.1. dvbRcsRcstSystem....................................18 83 3.4.2. dvbRcsRcstNetwork...................................19 84 3.4.3. dvbRcsRcstInstall...................................19 85 3.4.4. dvbRcsRcstQos.......................................19 86 3.4.5. dvbRcsRcstControl...................................19 87 3.4.6. dvbRcsRcstState.....................................20 88 3.4.7. dvbRcsFwdLink (dvbRcsFwdConfig and dvbRcsFwdStatus 89 groups)....................................................20 90 3.4.8. dvbRcsRtnLink (dvbRcsRtnConfig and dvbRcsRtnStatus 91 groups)....................................................20 92 4. Definitions...................................................21 93 5. Security Considerations.......................................91 94 6. IANA Considerations...........................................92 95 7. Acknowledgments...............................................92 96 8. References....................................................93 97 8.1. Normative References.....................................93 98 8.2. Informative References...................................93 99 9. Authors' Addresses............................................95 100 10. Disclaimer...................................................95 101 11. Copyright Notice.............................................96 103 1. Introduction 105 The SatLabs Group [SATLABS] is an international non-profit EEIG 106 (European Economic Interest Grouping) committed to large-scale 107 adoption and deployment of the Digital Video Broadcasting Return 108 Channel via Satellite (DVB-RCS) standard [ETSI-RCS]. SatLabs members 109 are service providers, satellite operators, system integrators, 110 terminal manufacturers and technology providers with an interest in 111 DVB-RCS. 113 Since its creation in 2001, the main goal of the SatLabs Group has 114 been to achieve interoperability between DVB-RCS terminals and 115 systems. Therefore, the Group has defined the SatLabs Qualification 116 Program that provides an independent certification process for DVB- 117 RCS Terminals based on System Recommendations defined by SatLabs. To 118 enhance products interoperability, beyond the physical and MAC layer 119 mechanisms defined in the DVB-RCS standard, SatLabs has expanded its 120 Recommendations in the field of DVB-RCS terminal management 121 [SATLABS]. As a part of this effort, SatLabs has specified a common 122 SNMP Management Information Base (MIB) for DVB-RCS terminals, which 123 is defined in this document. 125 A DVB-RCS terminal is denoted as a Return Channel Satellite Terminal 126 (RCST) in the remainder of this document. This consists of an Indoor 127 Unit (IDU) and an Outdoor Unit (ODU) connected through an Inter 128 Facility Link (IFL), usually a coaxial L-band interface. On the user 129 side, the IDU is connected to the user network through a Local Area 130 Network (LAN) interface (usually Ethernet). On the network side, the 131 ODU is connected via a satellite link (the Air Interface). 133 The DVB-RCS MIB is implemented in the IDU of an RCST. RCST 134 management can be performed either through the LAN interface (Local 135 management) or through the Air Interface (Remote management from the 136 Network Control Center, NCC). RCST and NCC elements are shown on 137 Figure 1. 139 +------------+ 140 | IP | 141 | End Host | 142 +-----+------+ 143 | 144 - - - - - - - -|- - - - - - - - - - - - - - - - 145 | | LAN interface | 146 | 147 | +------+--------+ | 148 | Indoor Unit | 149 | | (IDU) | | 150 +------+--------+ 151 | | | 152 Inter Facility Link (IFL) 153 | | | 154 +-----+---------+ 155 | | OutDoor Unit | | 156 | (ODU) | 157 | +------+--------+ | 158 | 159 | | Air Interface | 160 - - - - - - - |- - - - - - - - - - - - - - - - 161 RCST | 162 | +----------------+ 163 +------->| Network Control| 164 | Center (NCC) | 165 +----------------+ 167 FIGURE 1: RCST architecture 169 2. Conventions used in this document 171 This memo defines a portion of the Management Information Base (MIB) 172 for use with network management protocols in the Internet community. 174 For a detailed overview of the documents that describe the current 175 Internet-Standard Management Framework, please refer to section 7 of 176 RFC 3410 [RFC3410]. 178 Managed objects are accessed via a virtual information store, termed 179 the Management Information Base or MIB. MIB objects are generally 180 accessed through the Simple Network Management Protocol (SNMP). 181 Objects in the MIB are defined using the mechanisms defined in the 182 Structure of Management Information (SMI). This memo specifies a MIB 183 module that is compliant to the SMIv2, which is described in STD 58, 184 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 185 [RFC2580]. 187 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 188 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 189 document are to be interpreted as described in RFC 2119 [RFC2119]. 191 2.1. Abbreviations 193 AAL5 ATM Adaptation Layer Type 5 195 ACM Adaptive Coding and Modulation (defined in [ETSI-DVBS2]) 197 ATM Asynchronous Transfer Mode 199 AVBDC Absolute Volume-Based Dynamic Capacity 201 BER Bit Error Ratio 203 BUC Block Up-Converter 205 CCM Constant Coding and Modulation 207 CNR Carrier to Noise Ratio 209 CRA Continuous Rate Assignment 211 CSC Common Signalling Channel 213 CW Continuous Wave (carrier frequency) 215 dBi deciBel (isotropic) 217 dBm deciBel (with respect to 1 mW) 219 DSCP DiffServ Code Point 221 ETSI European Telecommunications Standards Institute 223 FEC Forward Error Correction 224 GS Generic Stream 226 GSE Generic Stream Encapsulation 228 IDU InDoor Unit 230 IFL Inter-Facility Link 232 LNB Low Noise Block 234 LO Local Oscillator 236 MAC Medium Access Control 238 MIB Management Information Base 240 MPEG Motion Pictures Expert Group 242 MPE Multi-Protocol Encapsulation 244 NCC Network Control Centre 246 OAM Operations and Management 248 ODU OutDoor Unit 250 PHB Per-Hop Behavior 252 PEP Performance Enhancing Proxy 254 PID Packet IDentifier (MPEG, used as Program Identifier in DVB) 256 QoS Quality of Service 258 RBDC Rate-Based Dynamic Capacity 260 RC Request Class 262 RCST Return Channel via Satellite Terminal (DVB-RCS Terminal) 264 Rx Receive 266 SDU Service Data Unit 268 SSPA Solid State Power Amplifier 270 TDM Time Division Multiplex 271 TDMA Time Division Multiple Access 273 TS Transport Stream (as defined by MPEG) 275 Tx Transmit 277 VBDC Volume-Based Dynamic Capacity 279 VCI Virtual Channel Identifier (ATM) 281 VPI Virtual Path Identifier (ATM) 283 Vpp Volts peak-to-peak 285 2.2. Glossary 287 The terms in this document are derived either from DVB-RCS standard 288 specifications [ETSI-RCS] or from SatLabs System Recommendations 289 [SATLABS]. 291 2.2.1. Star DVB-RCS network 293 This denotes a hub-and-spoke configuration where all communications 294 pass through a central hub, that usually also includes the NCC. Peer- 295 to-peer communication between RCSTs is possible, but through a double 296 satellite hop (this traffic has to pass through the hub). 298 2.2.2. Mesh DVB-RCS network 300 This denotes a mesh configuration that supports peer-to-peer 301 communications in a single satellite hop directly between RCSTs. 303 2.2.3. Transparent DVB-RCS network 305 This denotes a network using transparent satellite transponders. Star 306 or mesh network configurations can be supported. In the case of a 307 mesh configuration, RCSTs need to incorporate a TDMA receiver in 308 addition to the TDM receiver. 310 2.2.4. Regenerative DVB-RCS network 312 This denotes a network using regenerative satellite transponders, 313 i.e. including some On-Board Processing functionality allowing 314 demodulation and decoding of the uplink TDMA signals and re-multiplex 315 the traffic on the downlink. Star or mesh network configurations can 316 be supported. 318 2.2.5. DVB-RCS MAC layer 320 The DVB-RCS MAC Layer represents the air interface of an RCST, as 321 specified in [ETSI-RCS]. The interface is bi-directional and supports 322 IP traffic over hub-spoke (star) and mesh satellite network 323 topologies. 325 2.2.6. DVB-RCS TDM 327 The DVB-RCS TDM corresponds to the forward link of a DVB-RCS 328 transparent system or the downlink of a DVB-RCS regenerative system. 329 It is based on either the DVB-S or DVB-S2 standard specified in 330 [ETSI-DVBS] and [ETSI-DVBS2], respectively. In the DVB-RCS context, 331 this interface is uni or bi-directional, as it may also be used for a 332 return channel dedicated to a single terminal. 334 2.2.7. DVB-RCS TDMA 336 The DVB-RCS TDMA corresponds to the return or mesh link of a RCS 337 transparent system or the uplink of a RCS regenerative system. It is 338 specified in [ETSI-RCS]. 340 In the context of star transparent and mesh regenerative DVB-RCS 341 systems, this interface is uni-directional. 343 In the context of mesh transparent DVB-RCS systems, this interface is 344 bi-directional. 346 2.2.8. IDU 348 This is the indoor part of the RCST (including at least the power 349 supply, and usually also the modem and networking functions). 351 2.2.9. ODU 353 This is the outdoor part of the RCST (including at least the aerial, 354 and usually also the LNB and BUC). 356 2.2.10. RCST 358 This is the Satellite Terminal, installed on the customer premises. 359 It is composed of the IDU and ODU. 361 2.2.11. NCC 363 The NCC provides Control and Monitoring Functions. It generates 364 control and timing signals for the operation of the DVB-RCS Network. 366 2.2.12. Configuration file 368 The configuration file is XML formatted file, storing configuration 369 parameters for the RCST and their values. 371 2.2.13. Log file 373 The log file is stored at the RCST. This is used to log particular 374 events that occur on RCST side. 376 2.2.14. Installation log file 378 The installation log file is stored at the RCST. This logs particular 379 events that occur on RCST side, related to RCST installation phase. 381 2.2.15. Antenna alignment 383 This is the process to align the RCST antenna, part of the ODU, in 384 order to enable bi-directional communication (uplink, downlink) with 385 the satellite network. 387 2.2.16. CW frequency 389 The CW frequency is the frequency of a Continuous Wave signal. It is 390 a narrowband carrier transmitted for the duration of measurements 391 during the installation of a RCST. 393 2.2.17. Request Class 395 A Request Class (RC) is a representation of a Per Hop Behavior (PHB) 396 at the MAC layer. It defines a behavior of the MAC layer for a given 397 aggregation of traffic. This behavior includes a combination of 398 Capacity Categories associated to the RC and a Priority with respect 399 to the other RCs supported by a RCST. 401 2.2.18. Channel ID 403 Each Request Class is identified by a unique Channel_ID in the 404 communication between the RCST and the NCC. 406 2.2.19. ATM profile 408 The ATM profile is one of the two profiles for traffic burst format 409 on a DVB-RCS uplink. It is based on one or more concatenated ATM 410 cells, each of length 53 bytes, plus an optional prefix. 412 2.2.20. MPEG profile 414 The MPEG profile is one of the two profiles for traffic burst format 415 on the DVB-RCS uplink. It is based on a number of concatenated MPEG2- 416 TS packets, each of length 188 bytes. 418 2.2.21. PID pool 420 For the MPEG profile several RCs may be mapped within a pool of 421 several PIDs to allow cross-RC Section Packing [RFC4259]. Section 422 packing can be used on all PIDs and higher priority traffic can 423 always pre-empt lower priority streams. This reduces the need for 424 padding. 426 2.2.22. Capacity Categories 428 The TDMA timeslot allocation process for the DVB-RCS uplink supports 429 several capacity categories. 431 The Capacity Categories CRA, RBDC and A/VBDC, when authorized for a 432 RC, have to be configured from the NCC. These configuration 433 parameters are used to inform the RCST of the configuration of each 434 Category at the NCC side and thus help in Capacity Requests 435 computation. 437 The configuration of these parameters is performed for each RC. A 438 SatLabs optional feature is defined that allows their configuration 439 at the RCST level in addition to configuration per RC. This feature 440 is denoted RCST_PARA. 442 2.2.22.1. Continuous Rate Assignment (CRA) 444 CRA is a rate capacity that is provided in full in a continuous 445 manner to the RCST while required. 447 2.2.22.2. Rate-Based Dynamic Capacity (RBDC) 449 RBDC is rate capacity that is requested dynamically by an RCST. RBDC 450 capacity is provided in response to explicit requests from the RCST 451 to the NCC, such requests being absolute (i.e. corresponding to the 452 full rate currently being requested). Each request overrides all 453 previous RBDC requests from the same RCST, and is subject to a 454 maximum rate limit. 456 2.2.22.3. Volume-Based Dynamic Capacity (VBDC) 458 VBDC is volume capacity that is requested dynamically by an RCST. 459 VBDC capacity is provided in response to explicit requests from the 460 RCST to the NCC, such requests being cumulative (i.e. each request 461 adds to all previous requests from the same RCST). 463 2.2.22.4. Absolute Volume-Based Dynamic Capacity (AVBDC) 465 AVBDC is volume capacity that is requested dynamically by an RCST. 466 This capacity is provided in response to explicit requests from the 467 RCST to the NCC, such requests being absolute (i.e. this request 468 replaces the previous ones from the same RCST). 470 The combination of AVBDC and VBDC is seen as a single Capacity 471 Category, denoted A/VBDC. 473 2.2.22.5. Population ID 475 This defines a group of RCSTs within a Network. 477 2.2.23. Start transponder 479 This is the satellite transponder on which the communication is 480 initiated from a RCST point-of-view when in the installation mode. 481 The parameters corresponding to this transponder (satellite orbital 482 position, frequency, etc.) are stored at the RCST as power-up 483 configuration data. 485 2.2.24. DVB-S 487 DVB-S is the Digital Video Broadcast over Satellite [ETSI-DVBS]. It 488 is a framework and set of associated standards published by ETSI for 489 the transmission of video, audio, and data, using the ISO MPEG-2 490 Standard [ISO-MPEG], over satellite links. 492 2.2.25. DVB-S2 and CCM/VCM/ACM 494 DVB-S2 is the Second Generation of the Digital Video Broadcast for 495 Satellite applications standard [ETSI-DVBS2]. It is a framework and 496 set of associated standards published by ETSI for the transmission of 497 video, audio and data. 499 BBFRAME: The main framing unit of the DVB-S2 protocol stack. 501 CCM: In CCM transmission mode, the forward link uses a constant set 502 of transmission parameters (FEC coding rate and modulation scheme) 503 for all receivers. 505 VCM: In VCM transmission mode, the forward link uses transmission 506 parameters which are variable on a BBFRAME-by-BBFRAME, but fixed on a 507 Receiver basis, according to fixed link and propagation conditions 508 for each Receiver. 510 ACM: In ACM transmission mode, the forward link uses transmission 511 parameters which are dynamically adjusted on a BBFRAME-by-BBFRAME and 512 Receiver-per-Receiver basis, according to actual link and propagation 513 conditions. In order to implement ACM, feedback from each Receiver 514 has to be provided by DVB-RCS return channel. 516 2.2.26. Interactive Network 518 This is another name for a DVB-RCS based satellite network. 520 3. MIB Module overview 522 This MIB module provides a set of objects required for the management 523 of SatLabs-compliant RCST. The specification is derived from the 524 parameters and protocols described in [SATLABS]. 526 The MIB module in this document uses the following OBJECT IDENTIFIER 527 values as already assigned by IANA under the smi-numbers registry 528 [IANA]: 530 +------------+---------------------------+ 531 | Descriptor | OBJECT IDENTIFIER value | 532 +------------+---------------------------+ 533 |dvbRcsMib |{ mib-2 transmission 239 } | 534 +------------+---------------------------+ 536 TABLE 1: Object Identifiers for the MIB 538 These values have been assigned for this MIB under the 'mib- 539 2.transmission' subtree. 541 3.1. Textual Conventions 543 This MIB module defines new textual conventions for RCST indications 544 of SatLabs defined capabilities, including profiles, options and 545 optional features. 547 DvbRcsSystemSatLabsProfileMap represents the SatLabs profiles 548 supported as defined in [SATLABS]. 550 DvbRcsSystemSatLabsOptionMap represents the SatLabs options supported 551 as defined in [SATLABS]. These are options that are used for the 552 certification of SatLabs terminals. They represent important 553 functionality, with impact on interoperability, and their support is 554 advertised with the RCST certification level. 556 DvbRcsSystemSatLabsFeatureMap represents the SatLabs optional 557 features supported as defined in [SATLABS]. These represent minor 558 features, not necessary for interoperability. They are not used for 559 the certification of SatLabs terminals. 561 3.2. Structure of the MIB 563 This MIB module is structured into two top level groups: 565 o The dvbRcsMibObjects group includes all the managed objects of the 566 DVB-RCS MIB. 568 o The dvbRcsConformance group includes the compliance statements for 569 DVB-RCS terminals that are compliant with [SATLABS]. The managed 570 objects are grouped into formal object groups (i.e. units of 571 conformance) according to the relation to specific SatLabs options 572 or features. The conformance statements (MODULE-COMPLIANCE 573 specification) are described within the dvbRcsRcstCompliances 574 group while the units of conformance are described within the 575 dvbRcsRcstGroups group. 577 The dvbRcsMibObjects group is further structured into three groups: 578 dvbRcsRcst, dvbRcsFwdLink and dvbRcsRtnLink. 580 The dvbRcsRcst group covers management related to the RCST equipment. 581 It is structured into six groups: 583 o dvbRcsRcstSystem 585 o dvbRcsRcstNetwork 587 o dvbRcsRcstInstall 588 o dvbRcsRcstQos 590 o dvbRcsRcstControl 592 o dvbRcsRcstState 594 The dvbRcsFwdLink group covers management information related to the 595 RCST forward link. It is structured into two groups: 597 o dvbRcsFwdConfig 599 o dvbRcsFwdStatus 601 The dvbRcsRtnLink group covers management information related to the 602 RCST return link. It is structured into two groups: 604 o dvbRcsRtnConfig 606 o dvbRcsRtnStatus 608 Tables within each of these groups cover different functions like 609 return link traffic management (packet classes, Request Classes, PID 610 pools) and forward links configuration and status. 612 Rows created automatically (e.g., by the device according to the 613 hardware configuration) may and generally will have a mixture of 614 configuration and status objects within them. Rows that are meant to 615 be created by the management station are generally restricted to 616 configuration (read-create) objects. 618 3.3. Relationship to the Interfaces MIB Module 620 This section clarifies the relationship of this MIB module to the 621 Interfaces MIB [RFC2863]. Several areas of correlation are addressed 622 in the following. The implementer is referred to the Interfaces MIB 623 document in order to understand the general intent of these areas. 625 IANA has assigned three ifType labels for DVB-RCS. Each RCST MUST 626 support at least the three following interfaces: 628 o dvbRcsMacLayer (239), -- DVB-RCS MAC Layer 630 DVB-RCS MAC Layer represents the complete air interface of an RCST, 631 as specified in [ETSI-RCS]. This interface supports star and mesh 632 networks and is bi-directional. Only star networks are considered 633 by the present MIB module. 635 o dvbTdm (240), -- DVB Satellite TDM 637 DVB-RCS Physical link based on Time Division Multiplexing. It 638 corresponds to the forward link of a RCS transparent system or the 639 downlink of a RCS regenerative system. It is based on either DVB-S 640 or DVB-S2 standard specified in [ETSI-DVBS] and [ETSI-DVBS2]. Only 641 transparent systems are considered by the present MIB module. 643 In the DVB-RCS context, this interface is uni or bi-directional. 645 In the present MIB module, only a uni-directional (i.e. forward 646 link, or downstream) dvbTdm interface is considered. 648 o dvbRcsTdma (241), -- DVB-RCS TDMA 650 DVB-RCS Physical link based on Time Division Multiple Access. It 651 corresponds to the return or mesh link of a RCS transparent system 652 or the uplink of a RCS regenerative system. It is based on the DVB- 653 RCS standard specified in [ETSI-RCS]. 655 In the context of star transparent and mesh regenerative DVB-RCS 656 systems, this interface is uni-directional. 658 In the context of mesh transparent DVB-RCS systems, this interface 659 is bi-directional. 661 Only star transparent systems are considered by the present MIB 662 module (i.e. return link, or upstream). 664 The protocol stack (as reflected in ifStackTable) will be as follows: 666 +--------------------------+ 667 | IP | 668 +--------------------------+ 669 | dvbRcsMacLayer | 670 +---------------+----------+ 671 | dvbRcsTdma | dvbTdm | 672 +---------------+----------+ 673 | MPEG/ATM | MPEG/GS | 674 +---------------+----------+ 676 FIGURE 2: RCST protocol stack 678 An additional Ethernet interface is used on the LAN side of the RCST 679 (see Figure 1). 681 An instance of ifEntry exists for each dvbTdm interface, for each 682 dvbRcsTdma (normally only one), and for each dvbRcsMac layer 683 (normally only one). 685 The interface counters relate to: 687 o dvbRcsMacLayer: DVB-RCS two-way MAC interface that counts 688 aggregate Multi-Protocol Encapsulation (MPE) frames, Generic 689 Stream Encapsulation (GSE) encapsulated PDUs (equals IP packets), 690 and ATM Adaptation Layer 5 (AAL5) frames. 692 MPE is specified in [ETSI-DAT] and is transported over MPEG, which is 693 specified in [ISO-MPEG]. MPEG is transported over GS or TS (Transport 694 Stream) carriers. The TS carrier is specified in [ETSI-DVBS] for DVB- 695 S and [ETSI-DVBS2] for DVB-S2. 697 GSE is specified in [ETSI-GSE] and is transported over the GS 698 (Generic Stream) carrier, which is specified in [ETSI-DVBS2]. 700 ATM is specified in [ITU-ATM]. 702 AAL5 is specified in [ITU-AAL5]. 704 o dvbTdm: The DVB-RCS TDM interface that counts MPEG TS packets at 705 stream level, if the TS format is used. If the Generic Stream 706 (GS) format is used, it counts GSE packets. 708 o dvbRcsTdma: The DVB-RCS TDMA interface that counts aggregate ATM 709 and MPEG TS packets. 711 The ifStackTable [RFC2863] MUST be implemented to identify the 712 relationships among sub-interfaces. 714 The following example is a DVB-RCS star network with DVB-S and DVB- 715 RCS. As illustrated on Figure 3, it shows a DVB-RCS MAC interface 716 with one downstream and one upstream interface. In this network, ATM 717 encapsulation is used in the DVB-RCS uplink. Two ATM Logical Ports 718 are shown. DVB-S2 or DVB-S can be used in the downlink. 720 ifType 214 'mpegTransport' can also be used for counting TS packets 721 and bytes for subinterfaces of dvbRcsTdma or dvbTdm, e.g. per PID 722 oriented or per TS oriented as desired and applicable. 724 +----------------------------------------------------------+ 725 | IP Network Layer | 726 +------+----------------------------------+----------------+ 727 | | 728 +------+-------+ +------------------+----------------+ 729 | Ethernet LAN | | dvbRcsMacLayer | 730 +--------------+ +-------------+---------------------+ 731 | | 732 +-------------+-----------+ +---+---+ 733 | dvbRcsTdma | |dvbTdm | 734 +-----+-------------+-----+ +-------+ 735 | | 736 +-----+-----+ +-----+-----+ 737 |atm-logical| |atm-logical| 738 +-----------+ +-----------+ 740 FIGURE 3: Example stacking 742 As can be seen from this example, the dvbRcsMacLayer interface is 743 layered on top of the downstream and upstream interfaces, and the 744 upstream interface is layered on top of upstream ATM logical links. 746 In this example, the assignment of index values could be as follows: 748 ifIndex ifType Description 749 2 dvbRcsMacLayer (239) DVB-RCS MAC Layer 750 3 dvbRcsTdma (241) DVB-RCS TDMA Upstream 751 4 dvbTdm(240) DVB-RCS TDM Downstream 752 5 atm-logical(80) ATM Logical Port 753 6 atm-logical(80) ATM Logical Port 755 The corresponding ifStack entries would then be: 757 +--------------------+-------------------+ 758 | IfStackHigherLayer | ifStackLowerLayer | 759 +--------------------+-------------------+ 760 | 0 | 1 | 761 | 0 | 2 | 762 | 1 | 0 | 763 | 2 | 3 | 764 | 2 | 4 | 765 | 3 | 5 | 766 | 3 | 6 | 767 | 4 | 0 | 768 | 5 | 0 | 769 | 6 | 0 | 770 +--------------------+-------------------+ 772 TABLE 2: Example ifStack entries 774 3.4. MIB groups description 776 3.4.1. dvbRcsRcstSystem 778 The MIB objects in this group gather some basic information that 779 would allow anyone to trace the history - the life - of the RCST as 780 well as to get a complete description of its constitution on the 781 component point of view, including the SatLabs options/features 782 support statement. Many of the parameters will be defined at 783 installation. 785 This group contains description parameters related to the RCST type 786 (ODU type) and location. These parameters are believed to stay 787 unchanged once it has been defined during installation. Modification 788 of hardware equipment, maintenance operations and geographical re- 789 location may require an update of those MIB objects. Note that 790 dvbRcsRcstSystem. dvbRcsSystemLocation object gives the location of 791 the ODU antenna, which is needed for network operation, while the 792 system.sysLocation (MIB-II SNMP OID) provides the location of the IDU 793 unit, which can not be used for the same purpose. 795 The RCST must provide either Read-Write access to dvbRcsSystemOdu 796 parameters or, alternatively, provide the list of supported devices 797 through the rcstOduListGroup (see conformance section). This group of 798 parameters, defined in dvbRcsRcstSystem group, allows the selection 799 by the RCST installer of the actual ODU type. In such a case, the 800 installer must set dvbRcsOduTxType, dvbRcsOduRxType and 801 dvbRcsOduAntennaType according to the selected BUC, LNB and antenna 802 respectively. 804 3.4.2. dvbRcsRcstNetwork 806 This group contains all the MIB objects related to network 807 parameters. 809 In this subgroup, two objects have been defined in order to 810 differentiate between control and user traffic and associate them 811 with a physical interface. Both dvbRcsRcstNetwork. 812 dvbRcsNetworkLanIpAddress (Traffic) and dvbRcsRcstNetwork. 813 dvbRcsNetworkOamIpAddress (OAM) provide the value of the IP address 814 of, respectively, the user traffic and the control and management 815 traffic. 817 3.4.3. dvbRcsRcstInstall 819 This group contains all the information related to the RCST 820 installation and commissioning. Many parameters are believed to stay 821 unchanged once it has been defined during installation. Modification 822 of hardware equipment, maintenance operations and geographical re- 823 location may require an update of those MIB objects. 825 3.4.4. dvbRcsRcstQos 827 This group contains objects to configure the Quality of Service (QoS) 828 of the RCST by the NCC. 830 The dvbRcsPktClass table defines the packet classification for IP 831 layer 3 classifications. Each dvbRcsPktClass entry is mapped to a 832 dvbRcsPhbEntry in the dvbRcsPhbMappingTable. 834 The dvbRcsPhbMappingTable makes the relation between a packet 835 classification entry, a Per-Hop Behavior (PHB) identifier and a 836 Request class entry. 838 The dvbRcsRequestClassTable defines all the layer 2 DVB-RCS QoS 839 parameters. 841 3.4.5. dvbRcsRcstControl 843 This MIB group contains objects a network manager can use to invoke 844 actions and tests supported by the RCST agent and to retrieve the 845 action/test results. 847 3.4.6. dvbRcsRcstState 849 This MIB group describes the fault state, software versions and 850 configuration file versions of the RCST. 852 3.4.7. dvbRcsFwdLink (dvbRcsFwdConfig and dvbRcsFwdStatus groups) 854 This MIB group contains parameters that enable the NCC to have access 855 to data about the forward link. 857 Configuration information is kept into the dvbRcsFwdLink. 858 dvbRcsFwdConfig subgroup. Status information is kept into the 859 dvbRcsFwdLink.dvbRcsFwdStatus subgroup. 861 The information in dvbRcsFwdLink.dvbRcsFwdConfig.dvbRcsFwdStartTable 862 is used for the first time the RCST tries to acquire the forward 863 link. All these objects values are aligned with the Satellite 864 Delivery System Descriptor in the Network Information Table (NIT) 865 table [ETSI-SI]. 867 The objects in the dvbRcsFwdLink.dvbRcsFwdConfig.dvbRcsFwdStatusTable 868 are aligned with the satellite forward path descriptor form the RCS 869 Map Table (RMT) [ETSI-RCS] and with the Physical Layer (PL) Header 870 [ETSI-DVBS2], which specified the MODCOD (modulation and FEC rate) 871 and the Type (frame length short of long and the presence/absence of 872 pilots). 874 3.4.8. dvbRcsRtnLink (dvbRcsRtnConfig and dvbRcsRtnStatus groups) 876 This MIB group contains parameters that enable the NCC to have access 877 to data about the return link. 879 Configuration information is kept into the dvbRcsRtnLink. 880 dvbRcsRtnConfig subgroup. Status information is kept into the 881 dvbRcsRtnLink.dvbRcsrtnStatus subgroup. 883 The RCST is only able to deal with one return link at a time. Hence, 884 there is no need to define a table to collect the different SNMP 885 objects, as it is done for the forward. 887 4. Definitions 889 DVBRCS-MIB DEFINITIONS ::= BEGIN 891 IMPORTS 892 MODULE-IDENTITY, 893 Integer32, 894 IpAddress, 895 transmission, 896 OBJECT-TYPE 897 FROM SNMPv2-SMI -- [RFC2578] 898 TEXTUAL-CONVENTION, 899 DisplayString, 900 RowStatus 901 FROM SNMPv2-TC -- [RFC2579] 902 OBJECT-GROUP, 903 MODULE-COMPLIANCE 904 FROM SNMPv2-CONF; -- [RFC2580] 906 dvbRcsMib MODULE-IDENTITY 907 LAST-UPDATED "200902251200Z" 908 ORGANIZATION "The SatLabs Group" 909 CONTACT-INFO 910 "The SatLabs Group 911 Web: www.satlabs.org 912 E-mail: info@satlabs.org" 913 DESCRIPTION 914 "DVB-RCS MIB subtree. 915 This MIB module applies to equipment that is a 916 Return Channel Satellite Terminal (RCST) defined in 917 the Digital Video Broadcasting Return 918 Channel via Satellite system (DVB-RCS) standard (ETSI EN 301 919 791 Digital Video Broadcasting (DVB); Interaction Channel 920 for Satellite Distribution Systems, European 921 Telecommunications Standards Institute (ETSI)). 922 It defines a set of MIB entities to characterise the 923 behaviour and performance of network layer entities 924 implementing DVB-RCS. 925 This MIB module is intended to be used by DVB-RCS equipment 926 following the SatLabs System Recommendations, defined by the 927 SatLabs Group and available at www.satlabs.org." 929 REVISION "200902251200Z" 930 DESCRIPTION 931 "Revision of this MIB module, following comments from ipdvb 932 WG." 933 ::= { transmission 239 } 935 --=================================================================== 936 -- Textual Conventions 937 --=================================================================== 939 DvbRcsSatLabsProfileMap ::= TEXTUAL-CONVENTION 940 STATUS current 941 DESCRIPTION 942 "This textual convention enumerates the declaration of the 943 SatLabs defined terminal profiles. (0) refers to the most 944 significant bit." 945 REFERENCE 946 "SatLabs System Recommendations available at www.satlabs.org" 947 SYNTAX BITS { 948 dvbs(0), 949 dvbs2ccm(1), 950 dvbs2acm(2), 951 spare1(3), 952 spare2(4), 953 spare3(5), 954 spare4(6), 955 spare5(7), 956 spare6(8), 957 spare7(9), 958 spare8(10), 959 spare9(11), 960 spare10(12), 961 spare11(13), 962 spare12(14), 963 spare13(15), 964 spare14(16), 965 spare15(17), 966 spare16(18), 967 spare17(19), 968 spare18(20), 969 spare19(21), 970 spare20(22), 971 spare21(23), 972 spare22(24), 973 spare23(25), 974 spare24(26), 975 spare25(27), 976 spare26(28), 977 spare27(29), 978 spare28(30), 979 spare29(31) 980 } 982 DvbRcsSatLabsOptionMap ::= TEXTUAL-CONVENTION 983 STATUS current 984 DESCRIPTION 985 "This textual convention enumerates the declaration of the 986 SatLabs defined options. (0) refers to the most significant 987 bit." 988 REFERENCE 989 "SatLabs System Recommendations available at www.satlabs.org" 990 SYNTAX BITS { 991 mpegTrf(0), 992 coarseSync(1), 993 wideHop(2), 994 fastHop(3), 995 dynamicMfTdma(4), 996 contentionSync(5), 997 qpskLow(6), 998 mod16Apsk(7), 999 mod32Apsk(8), 1000 normalFec(9), 1001 multiTs(10), 1002 gsTs(11), 1003 enhQoS(12), 1004 pep(13), 1005 http(14), 1006 ftp(15), 1007 dns(16), 1008 chIdStrict(17), 1009 nlid(18), 1010 snmpMisc(19), 1011 spare1(20), 1012 spare2(21), 1013 spare3(22), 1014 spare4(23), 1015 spare5(24), 1016 spare6(25), 1017 spare7(26), 1018 spare8(27), 1019 spare9(28), 1020 spare10(29), 1021 spare11(30), 1022 spare12(31) 1023 } 1025 DvbRcsSatLabsFeatureMap ::= TEXTUAL-CONVENTION 1026 STATUS current 1027 DESCRIPTION 1028 "This textual convention enumerates the declaration of 1029 the SatLabs specified compatibility and configuration 1030 features. (0) refers to the most significant bit." 1031 REFERENCE 1032 "SatLabs System Recommendations available at 1033 www.satlabs.org" 1034 SYNTAX BITS { 1035 rcstPara(0), 1036 installLog(1), 1037 enhClassifier(2), 1038 routeId(3), 1039 spare1(4), 1040 spare2(5), 1041 spare3(6), 1042 spare4(7), 1043 spare5(8), 1044 spare6(9), 1045 spare7(10), 1046 spare8(11), 1047 spare9(12), 1048 spare10(13), 1049 spare11(14), 1050 spare12(15), 1051 spare13(16), 1052 spare14(17), 1053 spare15(18), 1054 spare16(19), 1055 spare17(20), 1056 spare18(21), 1057 spare19(22), 1058 spare20(23), 1059 spare21(24), 1060 spare22(25), 1061 spare23(26), 1062 spare24(27), 1063 spare25(28), 1064 spare26(29), 1065 spare27(30), 1066 spare28(31) 1067 } 1069 --=================================================================== 1070 -- object type definitions 1071 --=================================================================== 1072 dvbRcsMibObjects OBJECT IDENTIFIER ::= {dvbRcsMib 1} 1073 dvbRcsConformance OBJECT IDENTIFIER ::= {dvbRcsMib 2} 1075 dvbRcsRcst OBJECT IDENTIFIER ::= {dvbRcsMibObjects 1} 1076 dvbRcsFwdLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 2} 1077 dvbRcsRtnLink OBJECT IDENTIFIER ::= {dvbRcsMibObjects 3} 1079 dvbRcsRcstSystem OBJECT IDENTIFIER ::= {dvbRcsRcst 1} 1080 dvbRcsRcstNetwork OBJECT IDENTIFIER ::= {dvbRcsRcst 2} 1081 dvbRcsRcstInstall OBJECT IDENTIFIER ::= {dvbRcsRcst 3} 1082 dvbRcsRcstQos OBJECT IDENTIFIER ::= {dvbRcsRcst 4} 1083 dvbRcsRcstControl OBJECT IDENTIFIER ::= {dvbRcsRcst 5} 1084 dvbRcsRcstState OBJECT IDENTIFIER ::= {dvbRcsRcst 6} 1086 dvbRcsFwdConfig OBJECT IDENTIFIER ::= {dvbRcsFwdLink 1} 1087 dvbRcsFwdStatus OBJECT IDENTIFIER ::= {dvbRcsFwdLink 2} 1089 dvbRcsRtnConfig OBJECT IDENTIFIER ::= {dvbRcsRtnLink 1} 1090 dvbRcsRtnStatus OBJECT IDENTIFIER ::= {dvbRcsRtnLink 2} 1092 --=================================================================== 1093 --- dvbRcsRcstSystem sub-tree object types 1094 --=================================================================== 1095 dvbRcsSystemMibRevision OBJECT-TYPE 1096 SYNTAX DisplayString 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 "This object allows the SNMP agent to report the implemented 1101 MIB module revision. 1102 The supported REVISION of this module is reported." 1103 ::= {dvbRcsRcstSystem 1} 1105 --=================================================================== 1106 -- Options declared according to the textual conventions 1107 --=================================================================== 1108 dvbRcsSystemSatLabsProfilesDeclaration OBJECT-TYPE 1109 SYNTAX DvbRcsSatLabsProfileMap 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "Indicates the SatLabs profiles supported as defined in the 1114 SatLabs System Recommendations. A value of 1 indicates that 1115 the respective option is supported. The mapping to the 1116 profiles is to be understood as described here. (0) refers 1117 to the most significant bit. 1119 dvbs(0) -> DVBS profile (DVB-S support) 1120 dvbs2ccm(1) -> DVB-S2 CCM profile (CCM support) 1121 dvbs2acm(2) -> DVB-S2 ACM profile (CCM, VCM and ACM 1122 support)" 1123 REFERENCE 1124 "SatLabs System Recommendations available at www.satlabs.org" 1125 ::= {dvbRcsRcstSystem 2} 1127 dvbRcsSystemSatLabsOptionsDeclaration OBJECT-TYPE 1128 SYNTAX DvbRcsSatLabsOptionMap 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "Indicates the SatLabs options supported as defined in the 1133 SatLabs System Recommendations. A value of 1 indicates that 1134 the respective option is supported. The mapping to the 1135 options is to be understood as described here.(0) refers to 1136 the most significant bit. 1138 mpegTrf(0) -> MPEG_TRF 1139 coarseSync(1) -> COARSE_SYNC 1140 wideHop(2) -> WIDE_HOPP 1141 fastHop(3) -> FAST_HOPP 1142 dynamicMfTdma(4) -> Dynamic_MF_TDMA 1143 contentionSync(5) -> CONTENTION_SYNC 1144 qpskLow(6) -> QPSKLOW 1145 mod16Apsk(7) -> 16APSK 1146 mod32Apsk(8) -> 32APSK 1147 normalFec(9) -> NORMALFEC 1148 multiTs(10) -> MULTITS 1149 gsTs(11) -> GSTS 1150 enhQoS(12) -> ENHQOS 1151 pep(13) -> PEP 1152 http(14) -> HTTP 1153 ftp(15) -> FTP 1154 dns(16) -> DNS 1155 chIdStrict(17) -> CHID_STRICT 1156 nlid(18) -> NLID 1157 snmpMisc(19) -> SNMPMISC 1159 The support of specific options mandates the support of 1160 specific objects and access levels." 1161 REFERENCE 1162 "SatLabs System Recommendation available at www.satlabs.org" 1163 ::= {dvbRcsRcstSystem 3} 1165 dvbRcsSystemSatLabsFeaturesDeclaration OBJECT-TYPE 1166 SYNTAX DvbRcsSatLabsFeatureMap 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "Indicates the optional compatibility features and minor 1171 options supported as defined in the SatLabs System 1172 Recommendations. A value of 1 indicates that the respective 1173 feature is supported. The mapping to the features is to be 1174 understood as described here. (0) refers to the most 1175 significant bit. 1177 rcstPara(0) -> RCST_PARA feature 1178 installLog(1) -> INSTALL_LOG feature 1179 enhClassifier(2) -> ENHCLASSIFIER feature 1180 routeId(3) -> ROUTE_ID feature 1182 The support of specific features mandates the support of 1183 specific objects and access levels." 1184 REFERENCE 1185 "SatLabs System Recommendation available at www.satlabs.org" 1186 ::= {dvbRcsRcstSystem 4} 1188 dvbRcsSystemLocation OBJECT-TYPE 1189 SYNTAX DisplayString 1190 MAX-ACCESS read-write 1191 STATUS current 1192 DESCRIPTION 1193 "Physical location of the ODU antenna expressed as 1194 Longitude, Latitude and Altitude. The string 1195 shall have 31 characters in the following format: 1196 ,,,,,M 1197 where x, y and z represents digits, 1198 a=N or S, 1199 b=E or W, 1200 Reading the digits from left to right: 1201 'x' 7 latitude digits; x digits 1-2 contain the degrees, 1202 x digits 3-7 contain the minutes in decimal; 1203 'y' 8 longitude digits; y digits 1-3 contain the degrees, 1204 y digits 4-8 contain the minutes in decimal; 1205 ''' 5 altitude digits; meters above sea level in decimal; 1206 '.' is the decimal point; 1207 ',' is the field separator; 1208 'M' is the indicator for altitude meters. 1210 This format is a modified subset of the NMEA 0183 1211 (National Marine Electronics Association, Interface 1212 Standard) format for Global Positioning System Fix Data. 1214 This location and the satellite position are used to 1215 calculate the RCST-satellite path delay. 1217 Note: The system.sysLocation object of MIB-II provides 1218 physical location of the IDU unit." 1219 ::= {dvbRcsRcstSystem 5} 1221 dvbRcsSystemOduAntennaSize OBJECT-TYPE 1222 SYNTAX DisplayString 1223 UNITS "cm" 1224 MAX-ACCESS read-write 1225 STATUS current 1226 DESCRIPTION 1227 "Diameter of the antenna." 1228 ::= {dvbRcsRcstSystem 6} 1230 dvbRcsSystemOduAntennaGain OBJECT-TYPE 1231 SYNTAX Integer32 1232 UNITS "x0.1 dBi" 1233 MAX-ACCESS read-write 1234 STATUS current 1235 DESCRIPTION 1236 "Antenna peak gain of the ODU." 1237 ::= {dvbRcsRcstSystem 7} 1239 dvbRcsSystemOduSspa OBJECT-TYPE 1240 SYNTAX Integer32 1241 UNITS "x0.1 W" 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "Power level of the Solid State Power Amplifier installed 1246 in the ODU." 1247 ::= {dvbRcsRcstSystem 8} 1249 dvbRcsSystemOduTxType OBJECT-TYPE 1250 SYNTAX DisplayString 1251 MAX-ACCESS read-write 1252 STATUS current 1253 DESCRIPTION 1254 "Type of transmitter installed in the ODU." 1255 ::= {dvbRcsRcstSystem 9} 1256 dvbRcsSystemOduRxType OBJECT-TYPE 1257 SYNTAX DisplayString 1258 MAX-ACCESS read-write 1259 STATUS current 1260 DESCRIPTION 1261 "Type of LNB installed in the ODU, with 1262 information such as vendor type, output type (single, twin, 1263 quad,...), etc." 1264 ::= {dvbRcsRcstSystem 10} 1266 dvbRcsSystemOduRxBand OBJECT-TYPE 1267 SYNTAX INTEGER { 1268 oduHighRxBand (0), 1269 oduLowRxBand (1) 1270 } 1271 MAX-ACCESS read-write 1272 STATUS current 1273 DESCRIPTION 1274 "LNB High-Band/Low-Band selector. High Band corresponds to 1275 the emission of a 18-26 kHz tone with 0.4-0.8 Vpp in the Rx 1276 IFL cable: 1277 (0) - High Band 1278 (1) - Low Band" 1279 ::= {dvbRcsRcstSystem 11} 1281 dvbRcsSystemOduRxLO OBJECT-TYPE 1282 SYNTAX Integer32 1283 UNITS "x100 Hz" 1284 MAX-ACCESS read-write 1285 STATUS current 1286 DESCRIPTION 1287 "Frequency of LNB Local Oscillator (in 100 Hz)" 1288 ::= {dvbRcsRcstSystem 12} 1290 dvbRcsSystemOduTxLO OBJECT-TYPE 1291 SYNTAX Integer32 1292 UNITS "x100 Hz" 1293 MAX-ACCESS read-write 1294 STATUS current 1295 DESCRIPTION 1296 "Frequency of Block Up-Converter Local Oscillator 1297 (in 100 Hz)." 1298 ::= {dvbRcsRcstSystem 13} 1300 dvbRcsSystemIduPep OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 14} 1302 dvbRcsTcpPep OBJECT-TYPE 1303 SYNTAX INTEGER{ 1304 disabled (0), 1305 enabled (1) 1306 } 1307 MAX-ACCESS read-write 1308 STATUS current 1309 DESCRIPTION 1310 "Status and control of embedded TCP PEP. 1311 0 - disabled or not implemented 1312 1 - enabled" 1313 ::={dvbRcsSystemIduPep 1} 1315 dvbRcsHttpPep OBJECT-TYPE 1316 SYNTAX INTEGER{ 1317 disabled (0), 1318 enabled (1) 1319 } 1320 MAX-ACCESS read-write 1321 STATUS current 1322 DESCRIPTION 1323 "Status and control of embedded HTTP PEP. 1324 0 - disabled or not implemented 1325 1 - enabled" 1326 ::={dvbRcsSystemIduPep 2} 1328 --=================================================================== 1329 -- ODU structural entities 1330 --=================================================================== 1332 dvbRcsOduTx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 15} 1333 dvbRcsOduRx OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 16} 1334 dvbRcsOduAntenna OBJECT IDENTIFIER ::= {dvbRcsRcstSystem 17} 1336 --=================================================================== 1337 -- ODU BUC 1338 --=================================================================== 1340 dvbRcsOduTxTypeTable OBJECT-TYPE 1341 SYNTAX SEQUENCE OF DvbRcsOduTxTypeEntry 1342 MAX-ACCESS not-accessible 1343 STATUS current 1344 DESCRIPTION 1345 "This table contains the identification of each well-known BUC 1346 type supported by the IDU, and provides its associated index." 1347 ::={dvbRcsOduTx 1} 1349 dvbRcsOduTxTypeEntry OBJECT-TYPE 1350 SYNTAX DvbRcsOduTxTypeEntry 1351 MAX-ACCESS not-accessible 1352 STATUS current 1353 DESCRIPTION 1354 "An entry in the BUC type table." 1355 INDEX { dvbRcsTxTypeIndex } 1356 ::={dvbRcsOduTxTypeTable 1} 1358 DvbRcsOduTxTypeEntry ::= SEQUENCE { 1359 dvbRcsTxTypeIndex Integer32, 1360 dvbRcsTxTypeDescription DisplayString 1361 } 1363 dvbRcsTxTypeIndex OBJECT-TYPE 1364 SYNTAX Integer32 (1..16) 1365 MAX-ACCESS not-accessible 1366 STATUS current 1367 DESCRIPTION 1368 "Index for the BUC type." 1369 ::={dvbRcsOduTxTypeEntry 1} 1371 dvbRcsTxTypeDescription OBJECT-TYPE 1372 SYNTAX DisplayString 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "Text based identification of a BUC type." 1377 ::={dvbRcsOduTxTypeEntry 2} 1378 dvbRcsOduTxType OBJECT-TYPE 1379 SYNTAX Integer32 1380 MAX-ACCESS read-write 1381 STATUS current 1382 DESCRIPTION 1383 "Index of the selected BUC type." 1384 ::={dvbRcsOduTx 2} 1386 --=================================================================== 1387 -- ODU LNB 1388 --=================================================================== 1390 dvbRcsOduRxTypeTable OBJECT-TYPE 1391 SYNTAX SEQUENCE OF DvbRcsOduRxTypeEntry 1392 MAX-ACCESS not-accessible 1393 STATUS current 1394 DESCRIPTION 1395 "This table contains the identification of each well-known LNB 1396 type supported by the IDU, and provides its associated index." 1397 ::={dvbRcsOduRx 1} 1399 dvbRcsOduRxTypeEntry OBJECT-TYPE 1400 SYNTAX DvbRcsOduRxTypeEntry 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION 1404 "An entry in the LNB type table." 1405 INDEX { dvbRcsRxTypeIndex } 1406 ::={dvbRcsOduRxTypeTable 1} 1408 DvbRcsOduRxTypeEntry ::= SEQUENCE { 1409 dvbRcsRxTypeIndex Integer32, 1410 dvbRcsRxTypeDescription DisplayString 1411 } 1413 dvbRcsRxTypeIndex OBJECT-TYPE 1414 SYNTAX Integer32 (1..16) 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "Index for the LNB type." 1419 ::={dvbRcsOduRxTypeEntry 1} 1421 dvbRcsRxTypeDescription OBJECT-TYPE 1422 SYNTAX DisplayString 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "Text based identification of an LNB type." 1427 ::={dvbRcsOduRxTypeEntry 2} 1429 dvbRcsOduRxType OBJECT-TYPE 1430 SYNTAX Integer32 1431 MAX-ACCESS read-write 1432 STATUS current 1433 DESCRIPTION 1434 "Index of the selected LNB type." 1435 ::={dvbRcsOduRx 2} 1437 --=================================================================== 1438 -- ODU Antenna 1439 --=================================================================== 1441 dvbRcsOduAntennaTypeTable OBJECT-TYPE 1442 SYNTAX SEQUENCE OF DvbRcsOduAntennaTypeEntry 1443 MAX-ACCESS not-accessible 1444 STATUS current 1445 DESCRIPTION 1446 "This table contains the identification of each well-known 1447 antenna type supported by the IDU, and provides its associated 1448 index." 1449 ::={dvbRcsOduAntenna 1} 1451 dvbRcsOduAntennaTypeEntry OBJECT-TYPE 1452 SYNTAX DvbRcsOduAntennaTypeEntry 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "An entry in the antenna type table." 1457 INDEX { dvbRcsAntennaTypeIndex } 1458 ::={dvbRcsOduAntennaTypeTable 1} 1459 DvbRcsOduAntennaTypeEntry ::= SEQUENCE { 1460 dvbRcsAntennaTypeIndex Integer32, 1461 dvbRcsAntennaTypeDescription DisplayString 1462 } 1464 dvbRcsAntennaTypeIndex OBJECT-TYPE 1465 SYNTAX Integer32 (1..16) 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "Index for the antenna type." 1470 ::={dvbRcsOduAntennaTypeEntry 1} 1472 dvbRcsAntennaTypeDescription OBJECT-TYPE 1473 SYNTAX DisplayString 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "Text based identification of an antenna type." 1478 ::={dvbRcsOduAntennaTypeEntry 2} 1480 dvbRcsOduAntennaType OBJECT-TYPE 1481 SYNTAX Integer32 1482 MAX-ACCESS read-write 1483 STATUS current 1484 DESCRIPTION 1485 "Index of the selected antenna type." 1486 ::={dvbRcsOduAntenna 2} 1488 --=================================================================== 1489 -- dvbRcsRcstNetwork sub-tree object types 1490 --=================================================================== 1491 dvbRcsNetworkOamIpAddress OBJECT-TYPE 1492 SYNTAX IpAddress 1493 MAX-ACCESS read-write 1494 STATUS current 1495 DESCRIPTION 1496 "OAM IP Address of the RCST. This object is used with both 1497 IP and interfaces MIB-II subgroups. It uniquely determines 1498 the interface through which OAM traffic passes. 1500 The OAM IP address may be statically or dynamically 1501 assigned. It is system dependent whether the OAM IP address 1502 and the Traffic IP address are the same address." 1503 ::= {dvbRcsRcstNetwork 1} 1505 dvbRcsNetworkOamIpNetworkMask OBJECT-TYPE 1506 SYNTAX IpAddress 1507 MAX-ACCESS read-write 1508 STATUS current 1509 DESCRIPTION 1510 "Network Mask for the OAM IP Address." 1511 ::= {dvbRcsRcstNetwork 2} 1513 dvbRcsNetworkOamIpAddressAssign OBJECT-TYPE 1514 SYNTAX INTEGER { 1515 oamIpAddressStatic (1), 1516 oamIpAddressDynamic (2) 1517 } 1518 MAX-ACCESS read-write 1519 STATUS current 1520 DESCRIPTION 1521 "Identifies whether the OAM IP address is statically 1522 (1) or dynamically (2) assigned." 1523 ::= {dvbRcsRcstNetwork 3} 1525 dvbRcsNetworkLanIpAddress OBJECT-TYPE 1526 SYNTAX IpAddress 1527 MAX-ACCESS read-write 1528 STATUS current 1529 DESCRIPTION 1530 "IP address of the LAN interface" 1531 ::= {dvbRcsRcstNetwork 4} 1533 dvbRcsNetworkLanIpNetworkMask OBJECT-TYPE 1534 SYNTAX IpAddress 1535 MAX-ACCESS read-write 1536 STATUS current 1537 DESCRIPTION 1538 "Mask for the LAN interface" 1539 ::= {dvbRcsRcstNetwork 5} 1540 dvbRcsNetworkAirInterfaceDefaultGateway OBJECT-TYPE 1541 SYNTAX IpAddress 1542 MAX-ACCESS read-write 1543 STATUS current 1544 DESCRIPTION 1545 "Default Gateway for the air interface" 1546 ::= {dvbRcsRcstNetwork 6} 1548 dvbRcsNetworkDnsServers OBJECT IDENTIFIER ::= {dvbRcsRcstNetwork 7} 1550 dvbRcsPrimaryDnsServerIpAddress OBJECT-TYPE 1551 SYNTAX IpAddress 1552 MAX-ACCESS read-write 1553 STATUS current 1554 DESCRIPTION 1555 "IP address of the primary DNS server in the NCC." 1556 ::= {dvbRcsNetworkDnsServers 1} 1558 dvbRcsSecondaryDnsServerIpAddress OBJECT-TYPE 1559 SYNTAX IpAddress 1560 MAX-ACCESS read-write 1561 STATUS current 1562 DESCRIPTION 1563 "IP address of the secondary DNS server in the NCC." 1564 ::= {dvbRcsNetworkDnsServers 2} 1566 dvbRcsNetworkNccMgtIpAddress OBJECT-TYPE 1567 SYNTAX IpAddress 1568 MAX-ACCESS read-write 1569 STATUS current 1570 DESCRIPTION 1571 "IP address of the management server in the NCC." 1572 ::= {dvbRcsRcstNetwork 8} 1574 dvbRcsNetworkConfigFileDownloadUrl OBJECT-TYPE 1575 SYNTAX DisplayString 1576 MAX-ACCESS read-write 1577 STATUS current 1578 DESCRIPTION 1579 "Full path name for the configuration file download. 1580 It includes the protocol type (tftp or ftp) and the 1581 associated server IP address or hostname. Hostname can 1582 only be used if DNS is supported by the RCST. 1583 The format of this parameter follows RFC 1738." 1584 ::= {dvbRcsRcstNetwork 9} 1586 dvbRcsNetworkInstallLogFileDownloadUrl OBJECT-TYPE 1587 SYNTAX DisplayString 1588 MAX-ACCESS read-write 1589 STATUS current 1590 DESCRIPTION 1591 "Full path of the installation log file to download. 1592 It includes the protocol type (tftp or ftp) and the 1593 associated server IP address or hostname. Hostname can 1594 only be used if DNS is supported by the RCST. The 1595 installation log file can be created on the installer's 1596 computer and downloaded to the RCST. 1597 The format of this parameter follows RFC 1738." 1598 ::= {dvbRcsRcstNetwork 10} 1600 dvbRcsNetworkConfigFileUploadUrl OBJECT-TYPE 1601 SYNTAX DisplayString 1602 MAX-ACCESS read-write 1603 STATUS current 1604 DESCRIPTION 1605 "Full path name for the configuration file upload. 1606 It includes the protocol type (tftp or ftp) and the 1607 associated server IP address or hostname. Hostname can 1608 only be used if DNS is supported by the RCST. 1609 The format of this parameter follows RFC 1738." 1610 ::= {dvbRcsRcstNetwork 11} 1612 dvbRcsNetworkLogFileUploadUrl OBJECT-TYPE 1613 SYNTAX DisplayString 1614 MAX-ACCESS read-write 1615 STATUS current 1616 DESCRIPTION 1617 "Full path of the event log file. It includes the protocol 1618 type (tftp or ftp) and the associated server IP address 1619 or hostname. Hostname can only be used if DNS is supported 1620 by the RCST. 1621 The format of this parameter follows RFC 1738." 1623 ::= {dvbRcsRcstNetwork 12} 1625 dvbRcsNetworkInstallLogFileUploadUrl OBJECT-TYPE 1626 SYNTAX DisplayString 1627 MAX-ACCESS read-write 1628 STATUS current 1629 DESCRIPTION 1630 "Full path of the installation log file. It includes the 1631 protocol type (tftp or ftp) and the associated server 1632 IP address or hostname. Hostname can only be used if DNS is 1633 supported by the RCST. The installation log file can be 1634 retrieved from the RCST by the NCC or by the installer 1635 via the LAN. 1636 The format of this parameter follows RFC 1738." 1637 ::= {dvbRcsRcstNetwork 13} 1639 --=================================================================== 1640 -- dvbRcsRcstInstall sub-tree object types 1641 --=================================================================== 1642 dvbRcsInstallAntennaAlignmentState OBJECT-TYPE 1643 SYNTAX INTEGER { 1644 antennaAlignmentStart (1), 1645 antennaAlignmentDeny (2), 1646 antennaAlignmentContinue(3), 1647 antennaAlignmentStop (4), 1648 antennaAlignmentSuccess (5), 1649 antennaAlignmentFail (6) 1650 } 1651 MAX-ACCESS read-write 1652 STATUS current 1653 DESCRIPTION 1654 "Indicates the alignment state of the antenna: 1655 (1)-Start; 1656 (2)-Deny; 1657 (3)-Continue; 1658 (4)-Stop; 1659 (5)-Success; 1660 (6)-Fail" 1661 ::= {dvbRcsRcstInstall 1} 1663 dvbRcsInstallCwFrequency OBJECT-TYPE 1664 SYNTAX Integer32 1665 UNITS "x100 Hz" 1666 MAX-ACCESS read-write 1667 STATUS current 1668 DESCRIPTION 1669 "Frequency at which the transmitted Continuous Wave carrier 1670 (in 100 Hz). 1671 Minimum required precision is 1 kHz." 1672 ::= {dvbRcsRcstInstall 2} 1674 dvbRcsInstallCwMaxDuration OBJECT-TYPE 1675 SYNTAX Integer32 1676 UNITS "seconds" 1677 MAX-ACCESS read-write 1678 STATUS current 1679 DESCRIPTION 1680 "Time after which the Continuous Wave carrier must be put 1681 down (in seconds)" 1682 ::= {dvbRcsRcstInstall 3} 1684 dvbRcsInstallCwPower OBJECT-TYPE 1685 SYNTAX Integer32 1686 UNITS "x0.1 dBm" 1687 MAX-ACCESS read-write 1688 STATUS current 1689 DESCRIPTION 1690 "IDU TX output level when the IDU is configured to send CW. 1691 The resolution is 0.1 dBm and the accuracy is +/- 1 dBm. 1692 Reconfiguration is applied immediately to a CW." 1693 ::= {dvbRcsRcstInstall 4} 1695 dvbRcsInstallCoPolReading OBJECT-TYPE 1696 SYNTAX Integer32 1697 UNITS "x0.1 dB" 1698 MAX-ACCESS read-write 1699 STATUS current 1700 DESCRIPTION 1701 "Co-Polarisation measured value during installation 1702 procedure (in 0.1 dB)" 1703 ::= {dvbRcsRcstInstall 5} 1704 dvbRcsInstallXPolReading OBJECT-TYPE 1705 SYNTAX Integer32 1706 UNITS "x0.1 dB" 1707 MAX-ACCESS read-write 1708 STATUS current 1709 DESCRIPTION 1710 "Cross-Polarisation measured value during installation 1711 procedure (in 0.1 dB)" 1712 ::= {dvbRcsRcstInstall 6} 1714 dvbRcsInstallCoPolTarget OBJECT-TYPE 1715 SYNTAX Integer32 1716 UNITS "x0.1 dB" 1717 MAX-ACCESS read-write 1718 STATUS current 1719 DESCRIPTION 1720 "Co-Polarisation target value during installation procedure 1721 (in 0.1 dB)." 1722 ::= {dvbRcsRcstInstall 7} 1724 dvbRcsInstallXPolTarget OBJECT-TYPE 1725 SYNTAX Integer32 1726 UNITS "x0.1 dB" 1727 MAX-ACCESS read-write 1728 STATUS current 1729 DESCRIPTION 1730 "Cross-Polarisation target value during installation procedure 1731 (in 0.1 dB)" 1732 ::= {dvbRcsRcstInstall 8} 1734 dvbRcsInstallStandByDuration OBJECT-TYPE 1735 SYNTAX Integer32 1736 UNITS "seconds" 1737 MAX-ACCESS read-write 1738 STATUS current 1739 DESCRIPTION 1740 "Time to wait in stand-by mode (in seconds)" 1741 ::= {dvbRcsRcstInstall 9} 1743 dvbRcsInstallTargetEsN0 OBJECT-TYPE 1744 SYNTAX Integer32(0..315) 1745 UNITS "x0.1 dB" 1746 MAX-ACCESS read-write 1747 STATUS current 1748 DESCRIPTION 1749 "This value describes the wanted Es/N0 value that enables 1750 operation of the return link with the required error 1751 performance. The values shall be given in tenth of dB and 1752 the initial value shall be equal to 7 dB. The range shall be 1753 from 0 dBm to 31.5 dBm with a precision of 0.1 dB." 1754 DEFVAL { 70 } 1755 ::= {dvbRcsRcstInstall 10} 1757 --=================================================================== 1758 -- dvbRcsRcstQos sub-tree object types 1759 --=================================================================== 1760 dvbRcsPktClassTable OBJECT-TYPE 1761 SYNTAX SEQUENCE OF DvbRcsPktClassEntry 1762 MAX-ACCESS not-accessible 1763 STATUS current 1764 DESCRIPTION 1765 "This table describes the packet classification used in the 1766 DVB-RCS terminal. The number of entries is specified by 1767 dvbRcsPktClassIndex. " 1768 ::={dvbRcsRcstQos 1} 1770 dvbRcsPktClassEntry OBJECT-TYPE 1771 SYNTAX DvbRcsPktClassEntry 1772 MAX-ACCESS not-accessible 1773 STATUS current 1774 DESCRIPTION 1775 "An entry in the packet classification table. One object type 1776 of each entry may have a value in the active range (a non- 1777 default value).The other object types are then assumed set to 1778 'inactive'. The entry with the lowest index value takes 1779 precedence when classifying a packet." 1780 INDEX { dvbRcsPktClassIndex } 1781 ::= {dvbRcsPktClassTable 1} 1783 DvbRcsPktClassEntry ::= SEQUENCE { 1784 dvbRcsPktClassIndex Integer32, 1785 dvbRcsPktClassDscpLow Integer32, 1786 dvbRcsPktClassDscpHigh Integer32, 1787 dvbRcsPktClassDscpMarkValue Integer32, 1788 dvbRcsPktClassIpProtocol Integer32, 1789 dvbRcsPktClassIpSrcAddress IpAddress, 1790 dvbRcsPktClassIpSrcAddressMask IpAddress, 1791 dvbRcsPktClassIpDstAddress IpAddress, 1792 dvbRcsPktClassIpDstAddressMask IpAddress, 1793 dvbRcsPktClassSrcPortLow Integer32, 1794 dvbRcsPktClassSrcPortHigh Integer32, 1795 dvbRcsPktClassDstPortLow Integer32, 1796 dvbRcsPktClassDstPortHigh Integer32, 1797 dvbRcsPktClassVlanUserPri Integer32, 1798 dvbRcsPktClassPhbAssociation Integer32, 1799 dvbRcsPktClassRowStatus RowStatus 1800 } 1802 dvbRcsPktClassIndex OBJECT-TYPE 1803 SYNTAX Integer32 (1..64) 1804 MAX-ACCESS not-accessible 1805 STATUS current 1806 DESCRIPTION 1807 "Index automatically incremented by one at row creation." 1808 ::={dvbRcsPktClassEntry 1} 1810 dvbRcsPktClassDscpLow OBJECT-TYPE 1811 SYNTAX Integer32 (0..63) 1812 MAX-ACCESS read-create 1813 STATUS current 1814 DESCRIPTION 1815 "This object specifies the low value of a range of DiffServ 1816 Code Point (DSCP) values to which a packet is compared. 1817 A value of 0 is used to inactivate." 1818 DEFVAL { 0 } 1819 ::={dvbRcsPktClassEntry 2} 1821 dvbRcsPktClassDscpHigh OBJECT-TYPE 1822 SYNTAX Integer32 (0..63) 1823 MAX-ACCESS read-create 1824 STATUS current 1825 DESCRIPTION 1826 "This object specifies the high value of a range of DiffServ 1827 Code Point (DSCP) values to which a packet is compared. 1828 A value of 63 is used to inactivate." 1829 DEFVAL { 63 } 1830 ::={dvbRcsPktClassEntry 3} 1832 dvbRcsPktClassDscpMarkValue OBJECT-TYPE 1833 SYNTAX Integer32 (-1..63) 1834 MAX-ACCESS read-create 1835 STATUS current 1836 DESCRIPTION 1837 "This object is the DiffServ Code Point (DSCP) value used to 1838 mark the packet, -1 indicates no DSCP marking. Possible DSCP 1839 marks values are (0..63)" 1840 DEFVAL { -1 } 1841 ::={dvbRcsPktClassEntry 4} 1843 dvbRcsPktClassIpProtocol OBJECT-TYPE 1844 SYNTAX Integer32 (-1..255) 1845 MAX-ACCESS read-create 1846 STATUS current 1847 DESCRIPTION 1848 "This object specifies the IP protocol to which a 1849 packet is compared. A value of 255 indicates inactive." 1850 DEFVAL { -1 } 1851 ::={dvbRcsPktClassEntry 5} 1853 dvbRcsPktClassIpSrcAddress OBJECT-TYPE 1854 SYNTAX IpAddress 1855 MAX-ACCESS read-create 1856 STATUS current 1857 DESCRIPTION 1858 "This object specifies the IP source address to which a 1859 packet is compared." 1860 ::={dvbRcsPktClassEntry 6} 1862 dvbRcsPktClassIpSrcAddressMask OBJECT-TYPE 1863 SYNTAX IpAddress 1864 MAX-ACCESS read-create 1865 STATUS current 1866 DESCRIPTION 1867 "This object specifies which bits of the IP source address 1868 will be matched. A mask of all zeros indicates that the 1869 selectivity is inactive." 1870 DEFVAL { '00000000'H } 1871 ::={dvbRcsPktClassEntry 7} 1873 dvbRcsPktClassIpDstAddress OBJECT-TYPE 1874 SYNTAX IpAddress 1875 MAX-ACCESS read-create 1876 STATUS current 1877 DESCRIPTION 1878 "This object specifies the IP destination address to which a 1879 packet is compared." 1880 ::={dvbRcsPktClassEntry 8} 1882 dvbRcsPktClassIpDstAddressMask OBJECT-TYPE 1883 SYNTAX IpAddress 1884 MAX-ACCESS read-create 1885 STATUS current 1886 DESCRIPTION 1887 "This object specifies which bits of the IP destination 1888 address will be matched. A mask of all zeros indicates that 1889 the selectivity is inactive." 1890 DEFVAL { '00000000'H } 1891 ::={dvbRcsPktClassEntry 9} 1893 dvbRcsPktClassSrcPortLow OBJECT-TYPE 1894 SYNTAX Integer32 (-1..65535) 1895 MAX-ACCESS read-create 1896 STATUS current 1897 DESCRIPTION 1898 "This object specifies the low range of the source 1899 port to which a packet is compared. A value of -1 indicates 1900 that the selectivity is inactive." 1901 DEFVAL { -1 } 1902 ::={dvbRcsPktClassEntry 10} 1904 dvbRcsPktClassSrcPortHigh OBJECT-TYPE 1905 SYNTAX Integer32 (-1..65535) 1906 MAX-ACCESS read-create 1907 STATUS current 1908 DESCRIPTION 1909 "This object specifies the high range of the source port to 1910 which a packet is compared. A value of -1 indicates that the 1911 selectivity is inactive." 1912 DEFVAL { -1 } 1913 ::={dvbRcsPktClassEntry 11} 1915 dvbRcsPktClassDstPortLow OBJECT-TYPE 1916 SYNTAX Integer32 (-1..65535) 1917 MAX-ACCESS read-create 1918 STATUS current 1919 DESCRIPTION 1920 "This object specifies the low range of the destination 1921 port to which a packet is compared. A value of -1 indicates 1922 that the selectivity is inactive." 1923 DEFVAL { -1 } 1924 ::={dvbRcsPktClassEntry 12} 1926 dvbRcsPktClassDstPortHigh OBJECT-TYPE 1927 SYNTAX Integer32 (-1..65535) 1928 MAX-ACCESS read-create 1929 STATUS current 1930 DESCRIPTION 1931 "This object specifies the high range of the destination 1932 port to which a packet is compared. A value of -1 indicates 1933 that the selectivity is inactive." 1934 DEFVAL { -1 } 1935 ::={dvbRcsPktClassEntry 13} 1937 dvbRcsPktClassVlanUserPri OBJECT-TYPE 1938 SYNTAX Integer32 (-1..7) 1939 MAX-ACCESS read-create 1940 STATUS current 1941 DESCRIPTION 1942 "This object specifies the VLAN User Priority to which a 1943 packet is compared. A value of -1 indicates that the 1944 selectivity is inactive." 1945 DEFVAL { -1 } 1946 ::={dvbRcsPktClassEntry 14} 1948 dvbRcsPktClassPhbAssociation OBJECT-TYPE 1949 SYNTAX Integer32 (0..63) 1950 MAX-ACCESS read-create 1951 STATUS current 1952 DESCRIPTION 1953 "Associate the filter entry to a specific PHB (refer to 1954 dvbRcsPhbIdentifier)." 1955 ::={dvbRcsPktClassEntry 15} 1957 dvbRcsPktClassRowStatus OBJECT-TYPE 1958 SYNTAX RowStatus 1959 MAX-ACCESS read-create 1960 STATUS current 1961 DESCRIPTION 1962 "Standard SNMP row status" 1963 ::={dvbRcsPktClassEntry 16} 1965 --=================================================================== 1966 -- dvbRcsPhbMappingTable 1967 --=================================================================== 1968 dvbRcsPhbMappingTable OBJECT-TYPE 1969 SYNTAX SEQUENCE OF DvbRcsPhbMappingEntry 1970 MAX-ACCESS not-accessible 1971 STATUS current 1972 DESCRIPTION 1973 "This table is a list of Per-Hop Behaviour (PHB) MIB entries. 1974 It describes the PHB mapping to the Request Class." 1975 ::={dvbRcsRcstQos 2} 1977 dvbRcsPhbMappingEntry OBJECT-TYPE 1978 SYNTAX DvbRcsPhbMappingEntry 1979 MAX-ACCESS not-accessible 1980 STATUS current 1981 DESCRIPTION 1982 "An entry in the PHB mapping table." 1983 INDEX {dvbRcsPhbIdentifier} 1984 ::= {dvbRcsPhbMappingTable 1} 1986 DvbRcsPhbMappingEntry ::= SEQUENCE { 1987 dvbRcsPhbIdentifier Integer32, 1988 dvbRcsPhbName DisplayString, 1989 dvbRcsPhbRequestClassAssociation Integer32, 1990 dvbRcsPhbMappingRowStatus RowStatus 1991 } 1993 dvbRcsPhbIdentifier OBJECT-TYPE 1994 SYNTAX Integer32 (1..64) 1995 MAX-ACCESS not-accessible 1996 STATUS current 1997 DESCRIPTION 1998 "Identification of the Per-Hop Behaviour (PHB) (1..64)." 1999 ::={dvbRcsPhbMappingEntry 1} 2001 dvbRcsPhbName OBJECT-TYPE 2002 SYNTAX DisplayString 2003 MAX-ACCESS read-create 2004 STATUS current 2005 DESCRIPTION 2006 "The name of the Per-Hop Behaviour (PHB)." 2007 ::={dvbRcsPhbMappingEntry 2} 2009 dvbRcsPhbRequestClassAssociation OBJECT-TYPE 2010 SYNTAX Integer32 (1..16) 2011 MAX-ACCESS read-create 2012 STATUS current 2013 DESCRIPTION 2014 "This object is an association of this Per-Hop Behaviour 2015 (PHB) to a Request class (by reference to a Request Class 2016 index)." 2017 ::={dvbRcsPhbMappingEntry 3} 2019 dvbRcsPhbMappingRowStatus OBJECT-TYPE 2020 SYNTAX RowStatus 2021 MAX-ACCESS read-create 2022 STATUS current 2023 DESCRIPTION 2024 "Standard SNMP row status" 2025 DEFVAL { active } 2026 ::={dvbRcsPhbMappingEntry 4} 2028 --=================================================================== 2029 -- dvbRcsRequestClassTable 2030 --=================================================================== 2031 dvbRcsRequestClassTable OBJECT-TYPE 2032 SYNTAX SEQUENCE OF DvbRcsRequestClassEntry 2033 MAX-ACCESS not-accessible 2034 STATUS current 2035 DESCRIPTION 2036 "This table is a list of Request class entries. This class 2037 describes the layer 2 QoS objects." 2038 ::={dvbRcsRcstQos 3} 2040 dvbRcsRequestClassEntry OBJECT-TYPE 2041 SYNTAX DvbRcsRequestClassEntry 2042 MAX-ACCESS not-accessible 2043 STATUS current 2044 DESCRIPTION 2045 "An entry in the Request Class table." 2046 INDEX {dvbRcsRequestClassIndex} 2047 ::= {dvbRcsRequestClassTable 1} 2049 DvbRcsRequestClassEntry ::= SEQUENCE { 2050 dvbRcsRequestClassIndex Integer32, 2051 dvbRcsRequestClassName DisplayString, 2052 dvbRcsRequestClassChanId Integer32, 2053 dvbRcsRequestClassVccVpi Integer32, 2054 dvbRcsRequestClassVccVci Integer32, 2055 dvbRcsRequestClassPidPoolReference Integer32, 2056 dvbRcsRequestClassCra Integer32, 2057 dvbRcsRequestClassRbdcMax Integer32, 2058 dvbRcsRequestClassRbdcTimeout Integer32, 2059 dvbRcsRequestClassVbdcMax Integer32, 2060 dvbRcsRequestClassVbdcTimeout Integer32, 2061 dvbRcsRequestClassVbdcMaxBackLog Integer32, 2062 dvbRcsRequestClassRowStatus RowStatus 2063 } 2065 dvbRcsRequestClassIndex OBJECT-TYPE 2066 SYNTAX Integer32 (1..16) 2067 MAX-ACCESS not-accessible 2068 STATUS current 2069 DESCRIPTION 2070 "Index of the Request Class table. A total of 16 entries are 2071 supported." 2072 ::={dvbRcsRequestClassEntry 1} 2074 dvbRcsRequestClassName OBJECT-TYPE 2075 SYNTAX DisplayString 2076 MAX-ACCESS read-create 2077 STATUS current 2078 DESCRIPTION 2079 "Name of the Request Class." 2080 ::={dvbRcsRequestClassEntry 2} 2082 dvbRcsRequestClassChanId OBJECT-TYPE 2083 SYNTAX Integer32 (0..15) 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "Channel id of the Request Class." 2088 ::={dvbRcsRequestClassEntry 3} 2090 dvbRcsRequestClassVccVpi OBJECT-TYPE 2091 SYNTAX Integer32 (0..255) 2092 MAX-ACCESS read-create 2093 STATUS current 2094 DESCRIPTION 2095 "Defines VPI used for the Request Class (ATM profile)." 2096 ::={dvbRcsRequestClassEntry 4} 2098 dvbRcsRequestClassVccVci OBJECT-TYPE 2099 SYNTAX Integer32 (0..65535) 2100 MAX-ACCESS read-create 2101 STATUS current 2102 DESCRIPTION 2103 "Defines VCI used for the Request Class (ATM profile)." 2104 ::={dvbRcsRequestClassEntry 5} 2106 dvbRcsRequestClassPidPoolReference OBJECT-TYPE 2107 SYNTAX Integer32 (1..16) 2108 MAX-ACCESS read-create 2109 STATUS current 2110 DESCRIPTION 2111 "Reference to the Packet IDentifier (PID) pool applicable 2112 for the Request Class." 2113 ::={dvbRcsRequestClassEntry 6} 2115 dvbRcsRequestClassCra OBJECT-TYPE 2116 SYNTAX Integer32 2117 UNITS "bits/s" 2118 MAX-ACCESS read-create 2119 STATUS current 2120 DESCRIPTION 2121 "Define Continuous Rate Assignment (CRA) level for the 2122 Request Class in bit per second (bits/s)." 2123 ::={dvbRcsRequestClassEntry 7} 2125 dvbRcsRequestClassRbdcMax OBJECT-TYPE 2126 SYNTAX Integer32 2127 UNITS "x2 kbits/s" 2128 MAX-ACCESS read-create 2129 STATUS current 2130 DESCRIPTION 2131 "Maximum Rate-Based Dynamic Capacity (RBDC) that can be 2132 requested for the Request Class, in number of 2 kbits/s" 2133 ::={dvbRcsRequestClassEntry 8} 2135 dvbRcsRequestClassRbdcTimeout OBJECT-TYPE 2136 SYNTAX Integer32 2137 UNITS "superframes" 2138 MAX-ACCESS read-create 2139 STATUS current 2140 DESCRIPTION 2141 "Persistence of the Rate-Based Dynamic Capacity (RBDC) 2142 request, expressed in superframes" 2143 ::={dvbRcsRequestClassEntry 9} 2145 dvbRcsRequestClassVbdcMax OBJECT-TYPE 2146 SYNTAX Integer32 2147 UNITS "ATM cells/MPEG packets" 2148 MAX-ACCESS read-create 2149 STATUS current 2150 DESCRIPTION 2151 "Maximum Volume-Based Dynamic Capacity (VBDC) that can be 2152 allocated to the Request Class, in payload units (one ATM 2153 cell or one MPEG packet) per superframe" 2154 ::={dvbRcsRequestClassEntry 10} 2156 dvbRcsRequestClassVbdcTimeout OBJECT-TYPE 2157 SYNTAX Integer32 2158 UNITS "superframes" 2159 MAX-ACCESS read-create 2160 STATUS current 2161 DESCRIPTION 2162 "Time after which the RCST considers that the pending 2163 requests are lost. The RCST may issue new requests for that 2164 traffic. Volume-Based Dynamic Capacity (VBDC) Timeout is 2165 expressed in superframes." 2166 ::={dvbRcsRequestClassEntry 11} 2168 dvbRcsRequestClassVbdcMaxBackLog OBJECT-TYPE 2169 SYNTAX Integer32 2170 UNITS "bytes" 2171 MAX-ACCESS read-create 2172 STATUS current 2173 DESCRIPTION 2174 "Volume-Based Dynamic Capacity (VBDC) back log per Request 2175 Class (expressed in bytes)" 2176 ::={dvbRcsRequestClassEntry 12} 2178 dvbRcsRequestClassRowStatus OBJECT-TYPE 2179 SYNTAX RowStatus 2180 MAX-ACCESS read-create 2181 STATUS current 2182 DESCRIPTION 2183 "Standard SNMP row status" 2184 DEFVAL { active } 2185 ::={dvbRcsRequestClassEntry 13} 2187 --=================================================================== 2188 -- The table of PID pools 2189 --=================================================================== 2191 dvbRcsPidPoolTable OBJECT-TYPE 2192 SYNTAX SEQUENCE OF DvbRcsPidPoolEntry 2193 MAX-ACCESS not-accessible 2194 STATUS current 2195 DESCRIPTION 2196 "This table contains the Packet IDentifier (PID) pools. 2197 For MPEG profile several Request Classes may be mapped 2198 within a pool of several PIDs to allow Section Packing 2199 across Several Request Classes. 2200 A PID value may occur in more than one PID pool. Each PID 2201 value can effectively occur only once in each pool." 2202 ::={dvbRcsRcstQos 4} 2204 dvbRcsPidPoolEntry OBJECT-TYPE 2205 SYNTAX DvbRcsPidPoolEntry 2206 MAX-ACCESS not-accessible 2207 STATUS current 2208 DESCRIPTION 2209 "An entry in the PID pool table." 2210 INDEX { dvbRcsPidPoolIndex, dvbRcsPidIndex } 2211 ::= {dvbRcsPidPoolTable 1} 2213 DvbRcsPidPoolEntry ::= SEQUENCE { 2214 dvbRcsPidPoolIndex Integer32, 2215 dvbRcsPidIndex Integer32, 2216 dvbRcsPidValue Integer32, 2217 dvbRcsPidPoolRowStatus RowStatus 2218 } 2220 dvbRcsPidPoolIndex OBJECT-TYPE 2221 SYNTAX Integer32 (1..16) 2222 MAX-ACCESS not-accessible 2223 STATUS current 2224 DESCRIPTION 2225 "Index of the PID pool in the PID pool table." 2226 ::={dvbRcsPidPoolEntry 1} 2228 dvbRcsPidIndex OBJECT-TYPE 2229 SYNTAX Integer32 (1..16) 2230 MAX-ACCESS not-accessible 2231 STATUS current 2232 DESCRIPTION 2233 "Index of the PID entry within the PID pool." 2234 ::={dvbRcsPidPoolEntry 2} 2235 dvbRcsPidValue OBJECT-TYPE 2236 SYNTAX Integer32 (0..8191) 2237 MAX-ACCESS read-create 2238 STATUS current 2239 DESCRIPTION 2240 "Defines one of the PIDs to be used in a PID pool of 2241 dvbRcsPidPoolIndex. 2242 A PID value may occur in more than one PID pool. Each PID 2243 value can effectively occur only once in each pool." 2244 ::={dvbRcsPidPoolEntry 3} 2246 dvbRcsPidPoolRowStatus OBJECT-TYPE 2247 SYNTAX RowStatus 2248 MAX-ACCESS read-create 2249 STATUS current 2250 DESCRIPTION 2251 "Standard SNMP row status" 2252 DEFVAL { active } 2253 ::={dvbRcsPidPoolEntry 4} 2255 dvbRcsQosGlobalRbdcMax OBJECT-TYPE 2256 SYNTAX Integer32 2257 UNITS "x2 kbits/s" 2258 MAX-ACCESS read-write 2259 STATUS current 2260 DESCRIPTION 2261 "Global maximum RBDC that can be requested for the RCST, in 2262 number of 2 kbits/s." 2263 ::={dvbRcsRcstQos 5} 2265 dvbRcsQosGlobalVbdcMax OBJECT-TYPE 2266 SYNTAX Integer32 2267 UNITS "ATM cells/MPEG packets" 2268 MAX-ACCESS read-write 2269 STATUS current 2270 DESCRIPTION 2271 "Global maximum VBDC that can be allocated to the RCST, in 2272 payload units (one ATM cell or one MPEG packet) per 2273 superframe." 2274 ::={dvbRcsRcstQos 6} 2275 dvbRcsQosGlobalVbdcMaxBackLog OBJECT-TYPE 2276 SYNTAX Integer32 2277 UNITS "bytes" 2278 MAX-ACCESS read-write 2279 STATUS current 2280 DESCRIPTION 2281 "Global VBDC back log at RCST level (expressed in bytes). It 2282 is used only if the VBDC back log is not configured in the 2283 Request class (expressed in bytes)." 2284 ::={dvbRcsRcstQos 7} 2286 dvbRcsQosChannelIdStrictDispatching OBJECT-TYPE 2287 SYNTAX INTEGER { 2288 notStrict (0), 2289 strict (1) 2290 } 2291 MAX-ACCESS read-write 2292 STATUS current 2293 DESCRIPTION 2294 "Indicates whether the RCST will strictly follow RC 2295 association when signaled through Channel_ID in the TBTP: 2296 (0)- no strict association 2297 (1)- strict association" 2298 ::={dvbRcsRcstQos 8} 2300 --=================================================================== 2301 -- dvbRcsRcstControl sub-tree object types 2302 --=================================================================== 2303 dvbRcsCtrlRebootCommand OBJECT-TYPE 2304 SYNTAX INTEGER { 2305 idle (1), 2306 normal (2), 2307 alternate (3) 2308 } 2309 MAX-ACCESS read-write 2310 STATUS current 2311 DESCRIPTION 2312 "This variable shall force the RCST to reboot 2313 (1)- idle 2314 (2)- normal reboot (from current software load) 2315 (3)- reboot from alternate load (swap to alternate load 2316 before reboot)" 2317 DEFVAL {1} 2318 ::={dvbRcsRcstControl 1} 2320 dvbRcsCtrlRcstTxDisable OBJECT-TYPE 2321 SYNTAX INTEGER { 2322 idle (1), 2323 disable (2) 2324 } 2325 MAX-ACCESS read-write 2326 STATUS current 2327 DESCRIPTION 2328 "This variable shall force the RCST to stop transmission 2329 (transmit disabled as defined in SatLabs System 2330 Recommendations): 2331 (1)- idle 2332 (2)- initiate Tx Disabled" 2333 DEFVAL {1} 2334 ::={dvbRcsRcstControl 2} 2336 dvbRcsCtrlUserTrafficDisable OBJECT-TYPE 2337 SYNTAX INTEGER { 2338 idle (1), 2339 disable (2) 2340 } 2341 MAX-ACCESS read-write 2342 STATUS current 2343 DESCRIPTION 2344 "This variable shall disable user traffic (only RCST 2345 management traffic can be transmitted) 2346 (1)- idle 2347 (2)- disable user traffic" 2348 DEFVAL {1} 2349 ::={dvbRcsRcstControl 3} 2351 dvbRcsCtrlCwEnable OBJECT-TYPE 2352 SYNTAX INTEGER { 2353 off (1), 2354 on (2) 2355 } 2356 MAX-ACCESS read-write 2357 STATUS current 2358 DESCRIPTION 2359 "This variable will force the RCST to start transmission of 2360 CW, if the RCST is first set to the installation state, and 2361 is properly configured for CW transmission: 2362 (1)- off 2363 (2)- on" 2364 DEFVAL {1} 2365 ::={dvbRcsRcstControl 4} 2367 dvbRcsCtrlOduTxReferenceEnable OBJECT-TYPE 2368 SYNTAX INTEGER { 2369 off (1), 2370 on (2) 2371 } 2372 MAX-ACCESS read-write 2373 STATUS current 2374 DESCRIPTION 2375 "Enables activation and deactivation of 10 MHz reference 2376 clock in the Tx IFL cable: 2377 (1) off 2378 (2) on" 2379 DEFVAL {2} 2380 ::={dvbRcsRcstControl 5} 2382 dvbRcsCtrlOduTxDCEnable OBJECT-TYPE 2383 SYNTAX INTEGER { 2384 off (1), 2385 on (2) 2386 } 2387 MAX-ACCESS read-write 2388 STATUS current 2389 DESCRIPTION 2390 "Enables activation and deactivation of DC in the Tx IFL 2391 cable: 2392 (1) off 2393 (2) on" 2394 DEFVAL {2} 2395 ::={dvbRcsRcstControl 6} 2396 dvbRcsCtrlOduRxDCEnable OBJECT-TYPE 2397 SYNTAX INTEGER { 2398 off (1), 2399 on (2) 2400 } 2401 MAX-ACCESS read-write 2402 STATUS current 2403 DESCRIPTION 2404 "Enables activation and deactivation of DC in the Rx IFL 2405 cable: 2406 (1) off 2407 (2) on" 2408 DEFVAL {2} 2409 ::={dvbRcsRcstControl 7} 2411 dvbRcsCtrlDownloadFileCommand OBJECT-TYPE 2412 SYNTAX INTEGER { 2413 idle (1), 2414 config (2), 2415 installationLog (3) 2416 } 2417 MAX-ACCESS read-write 2418 STATUS current 2419 DESCRIPTION 2420 "This variable will initiate a RCST configuration file 2421 download process 2422 (1) idle 2423 (2) download RCST configuration file from TFTP/FTP server 2424 (3) download RCST installation log file from TFTP/FTP server 2425 (INSTALL_LOG Option)" 2426 DEFVAL {1} 2427 ::={dvbRcsRcstControl 8} 2429 dvbRcsCtrlUploadFileCommand OBJECT-TYPE 2430 SYNTAX INTEGER { 2431 idle (1), 2432 config (2), 2433 eventAlarm (3), 2434 installationLog (4) 2435 } 2436 MAX-ACCESS read-write 2437 STATUS current 2438 DESCRIPTION 2439 "This variable will initiate a RCST upload process 2440 (1) idle 2441 (2) upload RCST configuration file to TFTP/FTP server 2442 (3) upload RCST event/alarm log file to TFTP/FTP server 2443 (4) upload RCST installation log file to TFTP/FTP server 2444 (INSTALL_LOG Option)" 2445 DEFVAL {1} 2446 ::={dvbRcsRcstControl 9} 2448 dvbRcsCtrlActivateConfigFileCommand OBJECT-TYPE 2449 SYNTAX INTEGER { 2450 idle (1), 2451 activate (2) 2452 } 2453 MAX-ACCESS read-write 2454 STATUS current 2455 DESCRIPTION 2456 "Triggers the RCST to use the configuration file and update 2457 its parameters accordingly. Some RCST implementations may 2458 require a reboot for the parameters to take effect (vendor 2459 specific). 2460 (1) Idle 2461 (2) activate" 2462 DEFVAL {1} 2463 ::={dvbRcsRcstControl 10} 2465 dvbRcsCtrlRcstLogonCommand OBJECT-TYPE 2466 SYNTAX INTEGER { 2467 idle (1), 2468 logon (2) 2469 } 2470 MAX-ACCESS read-write 2471 STATUS current 2472 DESCRIPTION 2473 "This variable will initiate a RCST logon 2474 (1) idle 2475 (2) initiate RCST logon" 2476 DEFVAL {1} 2477 ::={dvbRcsRcstControl 11} 2478 dvbRcsCtrlRcstLogoffCommand OBJECT-TYPE 2479 SYNTAX INTEGER { 2480 idle (1), 2481 logoff (2) 2482 } 2483 MAX-ACCESS read-write 2484 STATUS current 2485 DESCRIPTION 2486 "This variable will initiate a RCST logoff 2487 (1) idle 2488 (2) initiate RCST logoff" 2489 DEFVAL {1} 2490 ::={dvbRcsRcstControl 12} 2492 dvbRcsCtrlRcstRxReacquire OBJECT-TYPE 2493 SYNTAX INTEGER { 2494 idle (1), 2495 reacquireForwardLink (2) 2496 } 2497 MAX-ACCESS read-write 2498 STATUS current 2499 DESCRIPTION 2500 "This variable will force the RCST to acquire the forward 2501 link and start receiving." 2502 DEFVAL {1} 2503 ::={dvbRcsRcstControl 13} 2505 --=================================================================== 2506 -- dvbRcsRcstState sub-tree object types 2507 --=================================================================== 2508 dvbRcsRcstMode OBJECT-TYPE 2509 SYNTAX INTEGER { 2510 installation (0), 2511 operational (1) 2512 } 2513 MAX-ACCESS read-write 2514 STATUS current 2515 DESCRIPTION 2516 "Identifies the current mode of the RCST is and allows it to 2517 return to the installation mode when needed. Values for the 2518 RCST mode are: 2519 Installation (0) 2520 Operational (1)" 2521 ::={dvbRcsRcstState 1} 2523 dvbRcsRcstFaultStatus OBJECT-TYPE 2524 SYNTAX INTEGER { 2525 nofault (0), 2526 fault (1) 2527 } 2528 MAX-ACCESS read-only 2529 STATUS current 2530 DESCRIPTION 2531 "Provide the fault status of the terminal. The fault status 2532 management is vendor specific. Values for the Fault Status 2533 are: 2534 no fault (0) 2535 fault (1)" 2536 ::={dvbRcsRcstState 2} 2538 dvbRcsRcstFwdLinkStatus OBJECT-TYPE 2539 SYNTAX INTEGER { 2540 notAcquired (0), 2541 acquired (1) 2542 } 2543 MAX-ACCESS read-only 2544 STATUS current 2545 DESCRIPTION 2546 "Provides the status of the RCST Forward Link. Values for the 2547 Forward Link Status are: 2548 Not acquired (0) 2549 Acquired (1)" 2550 ::={dvbRcsRcstState 3} 2552 dvbRcsRcstRtnLinkStatus OBJECT-TYPE 2553 SYNTAX INTEGER { 2554 loggedOff (0), 2555 loggedOn (1) 2556 } 2557 MAX-ACCESS read-only 2558 STATUS current 2559 DESCRIPTION 2560 "Provides the status of the RCST Return Link. Values for the 2561 Return Link Status are: 2562 Logged-off (0) 2563 Logged-on (1)" 2564 ::={dvbRcsRcstState 4} 2566 dvbRcsRcstLogUpdated OBJECT-TYPE 2567 SYNTAX INTEGER { 2568 noUpdate (0), 2569 logfileUpdated (1) 2570 } 2571 MAX-ACCESS read-only 2572 STATUS current 2573 DESCRIPTION 2574 "Indicates the existence of an updated event log file: 2575 No update (0) 2576 Event Log file updated (1) 2577 The RCST should remove the Event Log file updated indication 2578 as the log file is fetched by the NCC." 2579 ::={dvbRcsRcstState 5} 2581 dvbRcsRcstCurrentSoftwareVersion OBJECT-TYPE 2582 SYNTAX DisplayString 2583 MAX-ACCESS read-only 2584 STATUS current 2585 DESCRIPTION 2586 "Current RCST software version." 2587 ::={dvbRcsRcstState 6} 2589 dvbRcsRcstAlternateSoftwareVersion OBJECT-TYPE 2590 SYNTAX DisplayString 2591 MAX-ACCESS read-only 2592 STATUS current 2593 DESCRIPTION 2594 "Alternate (backup/new) RCST software version." 2595 ::={dvbRcsRcstState 7} 2597 dvbRcsRcstActivatedConfigFileVersion OBJECT-TYPE 2598 SYNTAX DisplayString 2599 MAX-ACCESS read-only 2600 STATUS current 2601 DESCRIPTION 2602 "Version of the most recently activated configuration file. 2603 The version is vendor specific." 2604 ::={dvbRcsRcstState 8} 2606 dvbRcsRcstDownloadedConfigFileVersion OBJECT-TYPE 2607 SYNTAX DisplayString 2608 MAX-ACCESS read-only 2609 STATUS current 2610 DESCRIPTION 2611 "Version of the most recently downloaded configuration file. 2612 Version is vendor specific. If the value is different from 2613 dvbRcsRcstActivatedConfigFileVersion, it is pending for 2614 activation." 2615 ::={dvbRcsRcstState 9} 2617 --=================================================================== 2618 -- dvbRcsFwdConfig sub-tree object types 2619 --=================================================================== 2620 dvbRcsFwdStartTable OBJECT-TYPE 2621 SYNTAX SEQUENCE OF DvbRcsFwdStartEntry 2622 MAX-ACCESS not-accessible 2623 STATUS current 2624 DESCRIPTION 2625 "Lists Forward Links attachment points (e.g. different for 2626 installation and operation). 2627 The table describes the forward link parameters used for the 2628 start-up stream with the NCC." 2629 ::={dvbRcsFwdConfig 1} 2631 dvbRcsFwdStartEntry OBJECT-TYPE 2632 SYNTAX DvbRcsFwdStartEntry 2633 MAX-ACCESS not-accessible 2634 STATUS current 2635 DESCRIPTION 2636 "An entry in the Forward Link StartConfig table." 2637 INDEX {dvbRcsFwdStartIndex} 2638 ::= {dvbRcsFwdStartTable 1} 2640 DvbRcsFwdStartEntry ::= SEQUENCE { 2641 dvbRcsFwdStartIndex Integer32, 2642 dvbRcsFwdStartPopId Integer32, 2643 dvbRcsFwdStartFrequency Integer32, 2644 dvbRcsFwdStartPolar INTEGER, 2645 dvbRcsFwdStartFormat INTEGER, 2646 dvbRcsFwdStartRolloff INTEGER, 2647 dvbRcsFwdStartSymbolRate Integer32, 2648 dvbRcsFwdStartInnerFec INTEGER, 2649 dvbRcsFwdStartRowStatus RowStatus 2650 } 2652 dvbRcsFwdStartIndex OBJECT-TYPE 2653 SYNTAX Integer32 (1..8) 2654 MAX-ACCESS not-accessible 2655 STATUS current 2656 DESCRIPTION 2657 "Index of the Forward Link StartConfig table." 2658 ::={dvbRcsFwdStartEntry 1} 2660 dvbRcsFwdStartPopId OBJECT-TYPE 2661 SYNTAX Integer32 (-1..65535) 2662 MAX-ACCESS read-create 2663 STATUS current 2664 DESCRIPTION 2665 "Population identifier associated with the start-up 2666 forward link: 2667 -1: any (auto) 2668 0-65535: specific StartPopId 2669 If 'any' is set, the RCST will assume membership of any 2670 announced population ID and will commence with logon in 2671 accordance with this assumption." 2672 ::={dvbRcsFwdStartEntry 2} 2674 dvbRcsFwdStartFrequency OBJECT-TYPE 2675 SYNTAX Integer32 2676 UNITS "x100 kHz" 2677 MAX-ACCESS read-create 2678 STATUS current 2679 DESCRIPTION 2680 "Frequency of the start transponder carrying a 2681 Network Information Table to which any RCST shall 2682 trigger to acquire forward link. Its value shall be given 2683 in multiple of 100 kHz." 2684 ::={dvbRcsFwdStartEntry 3} 2686 dvbRcsFwdStartPolar OBJECT-TYPE 2687 SYNTAX INTEGER { 2688 linearHorizontal (0), 2689 linearVertical (1), 2690 circularLeft (2), 2691 circularRight (3) 2692 } 2693 MAX-ACCESS read-create 2694 STATUS current 2695 DESCRIPTION 2696 "2-bit field giving the polarization of the start 2697 transponder carrying an Network Information Table 2698 to which any RCST shall trigger to acquire forward link: 2699 00: linear and horizontal 2700 01: linear and vertical 2701 10: circular left 2702 11: circular right" 2703 ::={dvbRcsFwdStartEntry 4} 2705 dvbRcsFwdStartFormat OBJECT-TYPE 2706 SYNTAX INTEGER { 2707 auto (-1), 2708 dvbs (0), 2709 dvbs2ccm (1), 2710 dvbs2acm (2) 2711 } 2712 MAX-ACCESS read-create 2713 STATUS current 2714 DESCRIPTION 2715 "Specifies the transmission format standard applied for the 2716 startup stream. The start transport stream carries a Network 2717 Information Table that the RCST uses for acquiring the 2718 forward link signaling. Supported values are: 2719 -1: unspecified (automatic format acquisition is 2720 assumed) 2721 0: DVB-S (support of this value is mandatory if DVB-S 2722 support is claimed) 2723 1: DVB-S2 with CCM (support of this value is mandatory 2724 if DVB-S2 CCM support is claimed) 2725 2: DVB-S2 with VCM or ACM (support of this value is 2726 mandatory if DVB-S2 ACM support is claimed) 2727 This allows the RCST to discriminate between CCM and VCM/ACM 2728 when selecting FL. 2729 The support of automatic format selection is optional. One 2730 Or several of the other format selections must be supported, 2731 according to the claimed SatLabs profile support." 2732 ::={dvbRcsFwdStartEntry 5} 2734 dvbRcsFwdStartRolloff OBJECT-TYPE 2735 SYNTAX INTEGER { 2736 autoRolloff (0), 2737 rolloff020 (1), 2738 rolloff025 (2), 2739 rolloff035 (3) 2740 } 2741 MAX-ACCESS read-create 2742 STATUS current 2743 DESCRIPTION 2744 "Specifies the receive filter roll-off applied on the start 2745 transponder. The start transponder carries a Network 2746 Information Table that the RCST uses for acquiring the 2747 forward link signaling. 2748 Supported values are: 2749 0: any (auto) 2750 1: 0.20 2751 2: 0.25 2752 3: 0.35" 2753 ::={dvbRcsFwdStartEntry 6} 2755 dvbRcsFwdStartSymbolRate OBJECT-TYPE 2756 SYNTAX Integer32 2757 UNITS "x100 symbols/s" 2758 MAX-ACCESS read-create 2759 STATUS current 2760 DESCRIPTION 2761 "Specifies the symbol rate on the start transponder 2762 carrying a Network Information Table to which any RCST 2763 shall trigger to acquire forward link. Its value shall be 2764 given in multiple of 100 symbols/s." 2765 ::={dvbRcsFwdStartEntry 7} 2767 dvbRcsFwdStartInnerFec OBJECT-TYPE 2768 SYNTAX INTEGER { 2769 autoFec (-1), 2770 fecRate12 (0), 2771 fecRate23 (1), 2772 fecRate34 (2), 2773 fecRate56 (3), 2774 fecRate78 (4), 2775 fecRate89 (5), 2776 fecRate35 (6), 2777 fecRate45 (7), 2778 fecRate910 (8), 2779 fecRate25 (9), 2780 fecRate13 (10), 2781 fecRate14 (11), 2782 noInnerCode (12) } 2783 MAX-ACCESS read-create 2784 STATUS current 2785 DESCRIPTION 2786 "Specifies the inner Forward Error Correction used on the 2787 start transponder carrying a Network Information Table 2788 to which any RCST shall trigger to acquire forward link. 2789 Supported values are: 2790 autoFec (-1), 2791 fecRate1/2 (0), 2792 fecRate2/3 (1), 2793 fecRate3/4 (2), 2794 fecRate5/6 (3), 2795 fecRate7/8 (4), 2796 fecRate8/9 (5), 2797 fecRate3/5 (6), 2798 fecRate4/5 (7), 2799 fecRate9/10 (8), 2800 fecRate2/5 (9), 2801 fecRate1/3 (10), 2802 fecRate1/4 (11), 2803 noInnerCode (12) 2805 The support of autoFec is optional." 2806 ::={dvbRcsFwdStartEntry 8} 2808 dvbRcsFwdStartRowStatus OBJECT-TYPE 2809 SYNTAX RowStatus 2810 MAX-ACCESS read-create 2811 STATUS current 2812 DESCRIPTION 2813 "Standard SNMP row status" 2814 DEFVAL { active } 2815 ::={dvbRcsFwdStartEntry 9} 2817 --=================================================================== 2818 -- dvbRcsFwdStatus sub-tree object types 2819 --=================================================================== 2820 dvbRcsFwdStatusPopId OBJECT-TYPE 2821 SYNTAX Integer32 (0..65535) 2822 MAX-ACCESS read-only 2823 STATUS current 2824 DESCRIPTION 2825 "Population identifier applied at log-on: 2826 0-65535: specific StartPopId 2827 If the RCST was allowed to logon with any population, the 2828 RCST will report the base number of the announced 2829 population ID indicated by the RCS Map Table linkage 2830 descriptor used at logon." 2831 ::={dvbRcsFwdStatus 1} 2833 dvbRcsFwdStatusTable OBJECT-TYPE 2834 SYNTAX SEQUENCE OF DvbRcsFwdStatusEntry 2835 MAX-ACCESS not-accessible 2836 STATUS current 2837 DESCRIPTION 2838 "This table describes the current status of Forward Link 2839 interfaces." 2840 ::={dvbRcsFwdStatus 2} 2842 dvbRcsFwdStatusEntry OBJECT-TYPE 2843 SYNTAX DvbRcsFwdStatusEntry 2844 MAX-ACCESS not-accessible 2845 STATUS current 2846 DESCRIPTION 2847 "An entry in the Forward Link Status table. Each entry is 2848 associated with a physical interface. 2849 A RCST shall support at least one entry." 2850 INDEX { dvbRcsFwdStatusIndex } 2851 ::= {dvbRcsFwdStatusTable 1} 2853 DvbRcsFwdStatusEntry ::= SEQUENCE { 2854 dvbRcsFwdStatusIndex Integer32, 2855 dvbRcsFwdStatusIfReference Integer32, 2856 dvbRcsFwdStatusNetId Integer32, 2857 dvbRcsFwdStatusNetName DisplayString, 2858 dvbRcsFwdStatusFormat INTEGER, 2859 dvbRcsFwdStatusFrequency Integer32, 2860 dvbRcsFwdStatusPolar INTEGER, 2861 dvbRcsFwdStatusInnerFec INTEGER, 2862 dvbRcsFwdStatusSymbolRate Integer32, 2863 dvbRcsFwdStatusRolloff INTEGER, 2864 dvbRcsFwdStatusModulation INTEGER, 2865 dvbRcsFwdStatusFecFrame INTEGER, 2866 dvbRcsFwdStatusPilot INTEGER, 2867 dvbRcsFwdStatusBer Integer32, 2868 dvbRcsFwdStatusCnr Integer32, 2869 dvbRcsFwdStatusRxPower Integer32 2870 } 2872 dvbRcsFwdStatusIndex OBJECT-TYPE 2873 SYNTAX Integer32 (1..8) 2874 MAX-ACCESS not-accessible 2875 STATUS current 2876 DESCRIPTION 2877 "Index of the Forward Link Status table." 2878 ::={dvbRcsFwdStatusEntry 1} 2880 dvbRcsFwdStatusIfReference OBJECT-TYPE 2881 SYNTAX Integer32 (1..8) 2882 MAX-ACCESS read-only 2883 STATUS current 2884 DESCRIPTION 2885 "Cross reference to the interface table" 2886 ::={dvbRcsFwdStatusEntry 2} 2887 dvbRcsFwdStatusNetId OBJECT-TYPE 2888 SYNTAX Integer32 2889 MAX-ACCESS read-only 2890 STATUS current 2891 DESCRIPTION 2892 "Interactive network identifier of the forward 2893 link (from RCS Map Table)" 2894 ::={dvbRcsFwdStatusEntry 3} 2896 dvbRcsFwdStatusNetName OBJECT-TYPE 2897 SYNTAX DisplayString 2898 MAX-ACCESS read-only 2899 STATUS current 2900 DESCRIPTION 2901 "The name of the interactive network of the forward 2902 link (from RCS Map Table)" 2903 ::={dvbRcsFwdStatusEntry 4} 2905 dvbRcsFwdStatusFormat OBJECT-TYPE 2906 SYNTAX INTEGER { 2907 dvbs (0), 2908 dvbs2ccm (1), 2909 dvbs2acm (2), 2910 reservedFormat (3) 2911 } 2912 MAX-ACCESS read-only 2913 STATUS current 2914 DESCRIPTION 2915 "Specifies the transmission format applied on the forward 2916 link. Supported values are (from RMT): 2917 0: DVB-S 2918 1: DVB-S2 using CCM 2919 2: DVB-S2 using VCM or ACM 2920 3: reserved" 2921 ::={dvbRcsFwdStatusEntry 5} 2923 dvbRcsFwdStatusFrequency OBJECT-TYPE 2924 SYNTAX Integer32 2925 UNITS "x100 kHz" 2926 MAX-ACCESS read-only 2927 STATUS current 2928 DESCRIPTION 2929 "An estimate of the frequency of the forward link. Its value 2930 shall be given in multiple of 100 kHz." 2931 ::={dvbRcsFwdStatusEntry 6} 2933 dvbRcsFwdStatusPolar OBJECT-TYPE 2934 SYNTAX INTEGER { 2935 linearHorizontal (0), 2936 linearVertical (1), 2937 circularLeft (2), 2938 circularRight (3) 2939 } 2940 MAX-ACCESS read-only 2941 STATUS current 2942 DESCRIPTION 2943 "2-bit field giving the polarization of the forward link 2944 (from RMT): 2945 00: linear and horizontal 2946 01: linear and vertical 2947 10: circular left 2948 11: circular right" 2949 ::={dvbRcsFwdStatusEntry 7} 2951 dvbRcsFwdStatusInnerFec OBJECT-TYPE 2952 SYNTAX INTEGER { 2953 unknown (-1), 2954 fecRate12 (0), 2955 fecRate23 (1), 2956 fecRate34 (2), 2957 fecRate56 (3), 2958 fecRate78 (4), 2959 fecRate89 (5), 2960 fecRate35 (6), 2961 fecRate45 (7), 2962 fecRate910 (8), 2963 fecRate25 (9), 2964 fecRate13 (10), 2965 fecRate14 (11), 2966 noInnerCode (12) 2967 } 2968 MAX-ACCESS read-only 2969 STATUS current 2970 DESCRIPTION 2971 "Specifies the inner Forward Error Correction used on the 2972 forward link for transmission to the RCST. 2973 Supported values are: 2974 unknown (-1), 2975 fecRate1/2 (0), 2976 fecRate2/3 (1), 2977 fecRate3/4 (2), 2978 fecRate5/6 (3), 2979 fecRate7/8 (4), 2980 fecRate8/9 (5), 2981 fecRate3/5 (6), 2982 fecRate4/5 (7), 2983 fecRate9/10 (8), 2984 fecRate2/5 (9), 2985 fecRate1/3 (10), 2986 fecRate1/4 (11), 2987 noInnerCode (12) 2988 The RCST will report a value that has been used for transmission 2989 to the RCST within the most recent 60 seconds. 2990 If this is not relevant, the RCST will report 'unknown'." 2991 ::={dvbRcsFwdStatusEntry 8} 2993 dvbRcsFwdStatusSymbolRate OBJECT-TYPE 2994 SYNTAX Integer32 2995 UNITS "x100 symbols/s" 2996 MAX-ACCESS read-only 2997 STATUS current 2998 DESCRIPTION 2999 "An estimate of the symbol rate of the forward link. 3000 Its value shall be given in multiple of 100 symbol/s." 3001 ::={dvbRcsFwdStatusEntry 9} 3003 dvbRcsFwdStatusRolloff OBJECT-TYPE 3004 SYNTAX INTEGER { 3005 undefRolloff (0), 3006 rolloff020 (1), 3007 rolloff025 (2), 3008 rolloff035 (3) 3010 } 3011 MAX-ACCESS read-only 3012 STATUS current 3013 DESCRIPTION 3014 "An estimate of the roll-off applied on the forward link. 3015 Supported values are: 3016 0: undefined 3017 1: 0.20 3018 2: 0.25 3019 3: 0.35" 3020 ::={dvbRcsFwdStatusEntry 10} 3022 dvbRcsFwdStatusModulation OBJECT-TYPE 3023 SYNTAX INTEGER { 3024 unknown (0), 3025 mBPSK (1), 3026 mQPSK (2), 3027 m8PSK (3), 3028 m16APSK (4), 3029 m32APSK (5) 3030 } 3031 MAX-ACCESS read-only 3032 STATUS current 3033 DESCRIPTION 3034 "Indicates the modulation on the forward link used for 3035 transmission to the RCST. 3036 0: unknown 3037 1: BPSK 3038 2: QPSK 3039 3: 8PSK 3040 4: 16APSK 3041 5: 32APSK 3042 The RCST will report a value that has been used for 3043 transmission to the RCST within the most recent 60 seconds. 3044 If this is not relevant, the RCST will report 'unknown'." 3045 ::={dvbRcsFwdStatusEntry 11} 3047 dvbRcsFwdStatusFecFrame OBJECT-TYPE 3048 SYNTAX INTEGER { 3049 unknown (0), 3050 shortframe (1), 3051 longframe (2) 3052 } 3053 MAX-ACCESS read-only 3054 STATUS current 3055 DESCRIPTION 3056 "Indicates the frame length used on the forward link for 3057 transmission to the RCST. 3058 Supported values are: 3059 0: Unknown 3060 1: Short frame 3061 2: Normal frame 3062 The RCST will report a value that has been used for 3063 transmission to the RCST within the most recent 60 seconds. 3064 If this is not relevant, the RCST will report 'unknown'." 3065 ::={dvbRcsFwdStatusEntry 12} 3067 dvbRcsFwdStatusPilot OBJECT-TYPE 3068 SYNTAX INTEGER { 3069 unknown (0), 3070 pilotNotused (1), 3071 pilotUsed (2) 3072 } 3073 MAX-ACCESS read-only 3074 STATUS current 3075 DESCRIPTION 3076 "Indicates whether pilots are used on the forward link for 3077 transmission to the RCST. 3078 Supported values are: 3079 0: Unknown 3080 1: Pilots are not used 3081 2: Pilots are used 3082 The RCST will report a value that has been used for 3083 transmission to the RCST within the most recent 60 seconds. 3084 If this is not relevant, the RCST will report 'unknown'." 3085 ::={dvbRcsFwdStatusEntry 13} 3087 dvbRcsFwdStatusBer OBJECT-TYPE 3088 SYNTAX Integer32 3089 UNITS "exponent of 10" 3090 MAX-ACCESS read-only 3091 STATUS current 3092 DESCRIPTION 3093 "Provides the RCST BER on the Forward Link in log10 units." 3094 ::={dvbRcsFwdStatusEntry 14} 3096 dvbRcsFwdStatusCnr OBJECT-TYPE 3097 SYNTAX Integer32 3098 UNITS "0.1 dB" 3099 MAX-ACCESS read-only 3100 STATUS current 3101 DESCRIPTION 3102 "Provides the RCST CNR on the Forward Link in 0.1 dB units." 3103 ::={dvbRcsFwdStatusEntry 15} 3105 dvbRcsFwdStatusRxPower OBJECT-TYPE 3106 SYNTAX Integer32 3107 UNITS "0.1 dBm" 3108 MAX-ACCESS read-only 3109 STATUS current 3110 DESCRIPTION 3111 "Provides the power level of the Forward Link as received at 3112 the IDU, in 0.1 dBm units." 3113 DEFVAL { -500 } 3114 ::={dvbRcsFwdStatusEntry 16} 3116 --=================================================================== 3117 -- dvbRcsRtnConfig sub-tree object types 3118 --=================================================================== 3119 dvbRcsRtnConfigMaxEirp OBJECT-TYPE 3120 SYNTAX Integer32 3121 UNITS "x0.1 dBm" 3122 MAX-ACCESS read-write 3123 STATUS current 3124 DESCRIPTION 3125 "Max EIRP of the RCST given in resolution of 0.1 dBm, 3126 applied when the IDU can itself set the necessary IDU TX 3127 output level e.g. when using a BUC that has a power level 3128 detector and provides sufficient feedback to the IDU." 3129 ::= {dvbRcsRtnConfig 1} 3131 dvbRcsRtnConfigDefIfLevel OBJECT-TYPE 3132 SYNTAX Integer32 3133 UNITS "x0.1 dBm" 3134 MAX-ACCESS read-write 3135 STATUS current 3136 DESCRIPTION 3137 "IDU TX output level applied in case the 3138 dvbRcsRtnConfigMaxEirp cannot be used. The resolution is 0.1 3139 dBm and the accuracy is +/- 1 dBm." 3140 ::= {dvbRcsRtnConfig 2} 3142 --=================================================================== 3143 -- dvbRcsRtnStatus sub-tree object types 3144 --=================================================================== 3145 dvbRcsRtnStatusEbN0 OBJECT-TYPE 3146 SYNTAX Integer32 3147 UNITS "x0.1 dB" 3148 MAX-ACCESS read-only 3149 STATUS current 3150 DESCRIPTION 3151 "The EbN0 value reported for the return link, referenced to 3152 the regular SYNC burst transmission, in 0.1 dB units." 3153 ::= {dvbRcsRtnStatus 1} 3155 dvbRcsRtnStatusSFDuration OBJECT-TYPE 3156 SYNTAX Integer32 (250..7500) 3157 UNITS "0.1 ms" 3158 MAX-ACCESS read-only 3159 STATUS current 3160 DESCRIPTION 3161 "The duration of the currently applied return link super- 3162 frame structure, in tenths of milliseconds." 3163 ::= {dvbRcsRtnStatus 2} 3165 dvbRcsRtnStatusPayloadUnit OBJECT-TYPE 3166 SYNTAX INTEGER { 3167 unitATM (0), 3168 unitMPEG (1) 3169 } 3170 MAX-ACCESS read-only 3171 STATUS current 3172 DESCRIPTION 3173 "Indicates if the payload unit used for the return link is 3174 ATM or MPEG." 3175 ::= {dvbRcsRtnStatus 3} 3177 --================================================================= 3178 -- conformance information 3179 --================================================================== 3180 dvbRcsRcstGroups OBJECT IDENTIFIER ::= {dvbRcsConformance 1} 3181 dvbRcsRcstCompliances OBJECT IDENTIFIER ::= {dvbRcsConformance 2} 3183 --================================================================== 3184 -- conformance statements 3185 --================================================================== 3186 dvbRcsRcstCompliance1 MODULE-COMPLIANCE 3187 STATUS current 3188 DESCRIPTION 3189 "The compliance statement for DVB-RCS terminals that are 3190 compliant with SatLabs System Recommendations. " 3192 MODULE -- this module 3194 MANDATORY-GROUPS {dvbRcsRcstSystemGroup, 3195 dvbRcsRcstNetworkGroup, dvbRcsRcstInstallGroup, dvbRcsRcstQosGroup, 3196 dvbRcsRcstControlGroup, dvbRcsRcstStateGroup, dvbRcsFwdConfigGroup, 3197 dvbRcsFwdStatusGroup, dvbRcsRtnConfigGroup, dvbRcsRtnStatusGroup} 3199 GROUP dvbRcsRcstExtSystemGroup 3200 DESCRIPTION "This group is mandatory for an RCST 3201 that claims to support the SNMPMISC option." 3203 GROUP dvbRcsRcstExtNetworkGroup 3204 DESCRIPTION "This group is mandatory for an RCST 3205 that claims to support the SNMPMISC option." 3207 GROUP dvbRcsRcstDnsGroup 3208 DESCRIPTION "This group is mandatory for an RCST 3209 that claims to support the DNS option." 3211 GROUP dvbRcsRcstExtInstallGroup 3212 DESCRIPTION "This group is mandatory for an RCST 3213 that claims to support the INSTALL_LOG feature." 3214 GROUP dvbRcsRcstEnhancedClassifierGroup 3215 DESCRIPTION "This group is mandatory for an RCST 3216 that claims to support the ENHCLASSIFIER feature." 3218 GROUP dvbRcsRcstMpegQosGroup 3219 DESCRIPTION "This group is mandatory for an RCST 3220 that claims to support the MPEG_TRF option." 3222 GROUP dvbRcsRcstGlobalQosGroup 3223 DESCRIPTION "This group is mandatory for an RCST 3224 that claims to support the RCST_PARA feature." 3226 GROUP dvbRcsRcstStrictQosGroup 3227 DESCRIPTION "This group is mandatory for an RCST 3228 that claims to support the CHID_STRICT option." 3230 GROUP dvbRcsRcstExtControlGroup 3231 DESCRIPTION "This group is mandatory for an RCST 3232 that claims to support the SNMPMISC option." 3234 GROUP dvbRcsRtnExtConfigGroup 3235 DESCRIPTION "This group is mandatory for an RCST 3236 that claims to support the SNMPMISC option." 3238 GROUP dvbRcsRtnExtStatusGroup 3239 DESCRIPTION "This group is mandatory for an RCST 3240 that claims to support the SNMPMISC option." 3242 GROUP dvbRcsRcstOduListGroup 3243 DESCRIPTION "This group is mandatory for an RCST that 3244 does not provide write access to the dvbRcsSystemOdu 3245 parameters." 3247 OBJECT dvbRcsSystemOduAntennaGain 3248 MIN-ACCESS read-only 3249 DESCRIPTION "Write access is supported if the 3250 dvbRcsRcstOduListGroup is not supported." 3252 OBJECT dvbRcsSystemOduSspa 3253 MIN-ACCESS read-only 3254 DESCRIPTION "Write access is supported if the 3255 dvbRcsRcstOduListGroup is not supported." 3257 OBJECT dvbRcsSystemOduTxType 3258 MIN-ACCESS read-only 3259 DESCRIPTION " Write access is supported if the 3260 dvbRcsRcstOduListGroup is not supported." 3262 OBJECT dvbRcsSystemOduRxType 3263 MIN-ACCESS read-only 3264 DESCRIPTION " Write access is supported if the 3265 dvbRcsRcstOduListGroup is not supported." 3267 OBJECT dvbRcsSystemOduRxBand 3268 MIN-ACCESS read-only 3269 DESCRIPTION " Write access is supported if the 3270 dvbRcsRcstOduListGroup is not supported." 3272 OBJECT dvbRcsSystemOduRxLO 3273 MIN-ACCESS read-only 3274 DESCRIPTION " Write access is supported if the 3275 dvbRcsRcstOduListGroup is not supported." 3277 OBJECT dvbRcsSystemOduTxLO 3278 MIN-ACCESS read-only 3279 DESCRIPTION " Write access is supported if the 3280 dvbRcsRcstOduListGroup is not supported." 3282 OBJECT dvbRcsPktClassDscpLow 3283 MIN-ACCESS read-only 3284 DESCRIPTION "Create access only required if 3285 ENHCLASSIFIER support is claimed." 3287 OBJECT dvbRcsPktClassDscpHigh 3288 MIN-ACCESS read-only 3289 DESCRIPTION "Create access only required if 3290 ENHCLASSIFIER support is claimed." 3292 OBJECT dvbRcsPktClassDscpMarkValue 3293 MIN-ACCESS read-only 3294 DESCRIPTION "Create access only required if 3295 ENHCLASSIFIER support is claimed." 3297 OBJECT dvbRcsPhbName 3298 MIN-ACCESS read-only 3299 DESCRIPTION "Create access only required if SNMPMISC 3300 support is claimed." 3302 OBJECT dvbRcsPhbRequestClassAssociation 3303 MIN-ACCESS read-only 3304 DESCRIPTION "Create access only required if SNMPMISC 3305 support is claimed." 3307 OBJECT dvbRcsPhbMappingRowStatus 3308 MIN-ACCESS read-only 3309 DESCRIPTION "Create access only required if SNMPMISC 3310 support is claimed." 3312 OBJECT dvbRcsRequestClassName 3313 MIN-ACCESS read-only 3314 DESCRIPTION "Write access only required if SNMPMISC 3315 support is claimed." 3317 OBJECT dvbRcsRequestClassChanId 3318 MIN-ACCESS read-only 3319 DESCRIPTION "Write access only required if SNMPMISC 3320 support is claimed." 3322 OBJECT dvbRcsRequestClassVccVpi 3323 MIN-ACCESS read-only 3324 DESCRIPTION "Write access only required if SNMPMISC 3325 support is claimed." 3327 OBJECT dvbRcsRequestClassVccVci 3328 MIN-ACCESS read-only 3329 DESCRIPTION "Write access only required if SNMPMISC 3330 support is claimed." 3332 OBJECT dvbRcsRequestClassPidPoolReference 3333 MIN-ACCESS not-accessible 3334 DESCRIPTION "Read-only access required if MPEG option 3335 is claimed. Write access only required if also SNMPMISC 3336 support is claimed." 3338 OBJECT dvbRcsRequestClassCra 3339 MIN-ACCESS read-only 3340 DESCRIPTION "Write access only required if SNMPMISC 3341 support is claimed." 3343 OBJECT dvbRcsRequestClassRbdcMax 3344 MIN-ACCESS read-only 3345 DESCRIPTION "Write access only required if SNMPMISC 3346 support is claimed." 3348 OBJECT dvbRcsRequestClassRbdcTimeout 3349 MIN-ACCESS read-only 3350 DESCRIPTION "Write access only required if SNMPMISC 3351 support is claimed." 3353 OBJECT dvbRcsRequestClassVbdcMax 3354 MIN-ACCESS read-only 3355 DESCRIPTION "Write access only required if SNMPMISC 3356 support is claimed." 3358 OBJECT dvbRcsRequestClassVbdcTimeout 3359 MIN-ACCESS read-only 3360 DESCRIPTION "Write access only required if SNMPMISC 3361 support is claimed." 3363 OBJECT dvbRcsRequestClassVbdcMaxBackLog 3364 MIN-ACCESS read-only 3365 DESCRIPTION "Write access only required if SNMPMISC 3366 support is claimed." 3368 OBJECT dvbRcsRequestClassRowStatus 3369 MIN-ACCESS read-only 3370 DESCRIPTION "Write access only required if SNMPMISC 3371 support is claimed." 3373 OBJECT dvbRcsPidValue 3374 MIN-ACCESS not-accessible 3375 DESCRIPTION "Read-only access required if MPEG option 3376 is claimed. Write access only required if also SNMPMISC 3377 support is claimed." 3379 OBJECT dvbRcsPidPoolRowStatus 3380 MIN-ACCESS not-accessible 3381 DESCRIPTION "Read-only access required if MPEG option 3382 is claimed. Write access only required if also SNMPMISC 3383 support is claimed." 3385 ::= {dvbRcsRcstCompliances 1} 3387 --================================================================== 3388 -- units of conformance 3389 --================================================================== 3391 --================================================================== 3392 -- object groups for RCST system 3393 --================================================================== 3394 dvbRcsRcstSystemGroup OBJECT-GROUP 3395 OBJECTS { 3396 dvbRcsSystemMibRevision, 3397 dvbRcsSystemSatLabsProfilesDeclaration, 3398 dvbRcsSystemSatLabsOptionsDeclaration, 3399 dvbRcsSystemSatLabsFeaturesDeclaration, 3400 dvbRcsSystemLocation, 3401 dvbRcsSystemOduAntennaGain, 3402 dvbRcsSystemOduSspa, 3403 dvbRcsSystemOduTxType, 3404 dvbRcsSystemOduRxType, 3405 dvbRcsSystemOduRxBand, 3406 dvbRcsSystemOduRxLO, 3407 dvbRcsSystemOduTxLO, 3408 dvbRcsTcpPep, 3409 dvbRcsHttpPep 3410 } 3411 STATUS current 3412 DESCRIPTION "A collection of objects providing information 3413 applicable for basic device management support." 3414 ::= {dvbRcsRcstGroups 1} 3416 dvbRcsRcstExtSystemGroup OBJECT-GROUP 3417 OBJECTS { 3418 dvbRcsSystemOduAntennaSize 3419 } 3420 STATUS current 3421 DESCRIPTION "A collection of objects providing information 3422 applicable for extended device management support." 3423 ::= {dvbRcsRcstGroups 2} 3425 --================================================================== 3426 -- object groups for RCST networking 3427 --================================================================== 3428 dvbRcsRcstNetworkGroup OBJECT-GROUP 3429 OBJECTS { 3430 dvbRcsNetworkOamIpAddress, 3431 dvbRcsNetworkOamIpNetworkMask, 3432 dvbRcsNetworkLanIpAddress, 3433 dvbRcsNetworkLanIpNetworkMask, 3434 dvbRcsNetworkConfigFileDownloadUrl, 3435 dvbRcsNetworkConfigFileUploadUrl, 3436 dvbRcsNetworkLogFileUploadUrl 3437 } 3438 STATUS current 3439 DESCRIPTION "A collection of objects providing basic 3440 networking management support." 3441 ::= {dvbRcsRcstGroups 3} 3443 dvbRcsRcstExtNetworkGroup OBJECT-GROUP 3444 OBJECTS { 3445 dvbRcsNetworkOamIpAddressAssign, 3446 dvbRcsNetworkAirInterfaceDefaultGateway, 3447 dvbRcsNetworkNccMgtIpAddress 3448 } 3449 STATUS current 3450 DESCRIPTION "A collection of objects providing extended 3451 networking management support." 3452 ::= {dvbRcsRcstGroups 4} 3454 dvbRcsRcstDnsGroup OBJECT-GROUP 3455 OBJECTS { 3456 dvbRcsPrimaryDnsServerIpAddress, 3457 dvbRcsSecondaryDnsServerIpAddress 3458 } 3459 STATUS current 3460 DESCRIPTION "IP addresses of the primary and secondary DNS 3461 servers to be used to resolve URL's as needed." 3462 ::= {dvbRcsRcstGroups 5} 3464 --================================================================== 3465 -- object groups for RCST installation 3466 --================================================================== 3468 dvbRcsRcstInstallGroup OBJECT-GROUP 3469 OBJECTS { 3470 dvbRcsInstallAntennaAlignmentState, 3471 dvbRcsInstallCwFrequency, 3472 dvbRcsInstallCwMaxDuration, 3473 dvbRcsInstallCwPower, 3474 dvbRcsInstallCoPolReading, 3475 dvbRcsInstallXPolReading, 3476 dvbRcsInstallCoPolTarget, 3477 dvbRcsInstallXPolTarget, 3478 dvbRcsInstallStandByDuration, 3479 dvbRcsInstallTargetEsN0 3480 } 3481 STATUS current 3482 DESCRIPTION "A collection of objects providing information 3483 applicable for basic installation support." 3484 ::= {dvbRcsRcstGroups 6} 3486 dvbRcsRcstExtInstallGroup OBJECT-GROUP 3487 OBJECTS { 3488 dvbRcsNetworkInstallLogFileDownloadUrl, 3489 dvbRcsNetworkInstallLogFileUploadUrl 3490 } 3491 STATUS current 3492 DESCRIPTION "A collection of objects providing extended 3493 device installation support." 3494 ::= {dvbRcsRcstGroups 7} 3496 --================================================================== 3497 -- object groups for QOS 3498 --================================================================== 3499 dvbRcsRcstQosGroup OBJECT-GROUP 3500 OBJECTS { 3501 dvbRcsPktClassDscpLow, 3502 dvbRcsPktClassDscpHigh, 3503 dvbRcsPktClassDscpMarkValue, 3504 dvbRcsPktClassPhbAssociation, 3505 dvbRcsPktClassRowStatus, 3506 dvbRcsPhbName, 3507 dvbRcsPhbRequestClassAssociation, 3508 dvbRcsPhbMappingRowStatus, 3509 dvbRcsRequestClassName, 3510 dvbRcsRequestClassChanId, 3511 dvbRcsRequestClassVccVpi, 3512 dvbRcsRequestClassVccVci, 3513 dvbRcsRequestClassCra, 3514 dvbRcsRequestClassRbdcMax, 3515 dvbRcsRequestClassRbdcTimeout, 3516 dvbRcsRequestClassVbdcMax, 3517 dvbRcsRequestClassVbdcTimeout, 3518 dvbRcsRequestClassVbdcMaxBackLog, 3519 dvbRcsRequestClassRowStatus 3520 } 3521 STATUS current 3522 DESCRIPTION "A collection of objects providing basic access to 3523 QOS configuration data." 3524 ::= {dvbRcsRcstGroups 8} 3526 dvbRcsRcstEnhancedClassifierGroup OBJECT-GROUP 3527 OBJECTS { 3528 dvbRcsPktClassIpProtocol, 3529 dvbRcsPktClassIpSrcAddress, 3530 dvbRcsPktClassIpSrcAddressMask, 3531 dvbRcsPktClassIpDstAddress, 3532 dvbRcsPktClassIpDstAddressMask, 3533 dvbRcsPktClassSrcPortLow, 3534 dvbRcsPktClassSrcPortHigh, 3535 dvbRcsPktClassDstPortLow, 3536 dvbRcsPktClassDstPortHigh, 3537 dvbRcsPktClassVlanUserPri 3538 } 3540 STATUS current 3541 DESCRIPTION "A collection of objects providing support for 3542 management of the enhanced classifier." 3543 ::= {dvbRcsRcstGroups 9} 3545 dvbRcsRcstMpegQosGroup OBJECT-GROUP 3546 OBJECTS { 3547 dvbRcsRequestClassPidPoolReference, 3548 dvbRcsPidValue, 3549 dvbRcsPidPoolRowStatus 3550 } 3551 STATUS current 3552 DESCRIPTION "A collection of objects providing access to MPEG 3553 related link QOS configuration data." 3554 ::= {dvbRcsRcstGroups 10} 3556 dvbRcsRcstGlobalQosGroup OBJECT-GROUP 3557 OBJECTS { 3558 dvbRcsQosGlobalRbdcMax, 3559 dvbRcsQosGlobalVbdcMax, 3560 dvbRcsQosGlobalVbdcMaxBackLog 3561 } 3562 STATUS current 3563 DESCRIPTION "A collection of objects providing access to 3564 global RCST QOS configuration data." 3565 ::= {dvbRcsRcstGroups 11} 3567 dvbRcsRcstStrictQosGroup OBJECT-GROUP 3568 OBJECTS { 3569 dvbRcsQosChannelIdStrictDispatching 3570 } 3571 STATUS current 3572 DESCRIPTION "A collection of objects allowing management of 3573 strict channel ID dispatching." 3574 ::= {dvbRcsRcstGroups 12} 3576 --================================================================== 3577 -- object groups for RCST control 3578 --================================================================== 3579 dvbRcsRcstControlGroup OBJECT-GROUP 3580 OBJECTS { 3581 dvbRcsCtrlRebootCommand, 3582 dvbRcsCtrlUserTrafficDisable, 3583 dvbRcsCtrlCwEnable, 3584 dvbRcsCtrlDownloadFileCommand, 3585 dvbRcsCtrlUploadFileCommand, 3586 dvbRcsCtrlActivateConfigFileCommand, 3587 dvbRcsCtrlRcstRxReacquire 3588 } 3589 STATUS current 3590 DESCRIPTION "A collection of objects allowing basic RCST 3591 control." 3592 ::= {dvbRcsRcstGroups 13} 3594 dvbRcsRcstExtControlGroup OBJECT-GROUP 3595 OBJECTS { 3596 dvbRcsCtrlRcstTxDisable, 3597 dvbRcsCtrlOduTxReferenceEnable, 3598 dvbRcsCtrlOduTxDCEnable, 3599 dvbRcsCtrlOduRxDCEnable, 3600 dvbRcsCtrlRcstLogonCommand, 3601 dvbRcsCtrlRcstLogoffCommand 3602 } 3603 STATUS current 3604 DESCRIPTION "A collection of objects allowing extended RCST 3605 control." 3606 ::= {dvbRcsRcstGroups 14} 3608 --================================================================== 3609 -- object groups for RCST state 3610 --================================================================== 3612 dvbRcsRcstStateGroup OBJECT-GROUP 3613 OBJECTS { 3614 dvbRcsRcstMode, 3615 dvbRcsRcstFaultStatus, 3616 dvbRcsRcstFwdLinkStatus, 3617 dvbRcsRcstLogUpdated, 3618 dvbRcsRcstCurrentSoftwareVersion, 3619 dvbRcsRcstAlternateSoftwareVersion, 3620 dvbRcsRcstActivatedConfigFileVersion, 3621 dvbRcsRcstDownloadedConfigFileVersion 3622 } 3623 STATUS current 3624 DESCRIPTION "A collection of objects allowing access to RCST 3625 state." 3626 ::= {dvbRcsRcstGroups 15} 3628 --================================================================== 3629 -- object groups for forward link 3630 --================================================================== 3632 dvbRcsFwdConfigGroup OBJECT-GROUP 3633 OBJECTS { 3634 dvbRcsFwdStartPopId, 3635 dvbRcsFwdStartFrequency, 3636 dvbRcsFwdStartPolar, 3637 dvbRcsFwdStartFormat, 3638 dvbRcsFwdStartRolloff, 3639 dvbRcsFwdStartSymbolRate, 3640 dvbRcsFwdStartInnerFec, 3641 dvbRcsFwdStartRowStatus 3642 } 3643 STATUS current 3644 DESCRIPTION "A collection of objects providing basic start 3645 forward link configuration support." 3646 ::= {dvbRcsRcstGroups 16} 3648 dvbRcsFwdStatusGroup OBJECT-GROUP 3649 OBJECTS { 3650 dvbRcsFwdStatusPopId, 3651 dvbRcsFwdStatusIfReference, 3652 dvbRcsFwdStatusNetId, 3653 dvbRcsFwdStatusNetName, 3654 dvbRcsFwdStatusFormat, 3655 dvbRcsFwdStatusFrequency, 3656 dvbRcsFwdStatusPolar, 3657 dvbRcsFwdStatusInnerFec, 3658 dvbRcsFwdStatusSymbolRate, 3659 dvbRcsFwdStatusRolloff, 3660 dvbRcsFwdStatusModulation, 3661 dvbRcsFwdStatusFecFrame, 3662 dvbRcsFwdStatusPilot, 3663 dvbRcsFwdStatusBer, 3664 dvbRcsFwdStatusCnr, 3665 dvbRcsFwdStatusRxPower 3666 } 3667 STATUS current 3668 DESCRIPTION "A collection of objects providing forward link 3669 status." 3670 ::= {dvbRcsRcstGroups 17} 3672 --================================================================== 3673 -- object groups for return link 3674 --================================================================== 3676 dvbRcsRtnConfigGroup OBJECT-GROUP 3677 OBJECTS { 3678 dvbRcsRtnConfigDefIfLevel 3679 } 3680 STATUS current 3681 DESCRIPTION "A collection of objects providing basic return 3682 link configuration support." 3683 ::= {dvbRcsRcstGroups 18} 3685 dvbRcsRtnExtConfigGroup OBJECT-GROUP 3686 OBJECTS { 3687 dvbRcsRtnConfigMaxEirp 3688 } 3689 STATUS current 3690 DESCRIPTION "A collection of objects providing extended 3691 return link configuration support." 3692 ::= {dvbRcsRcstGroups 19} 3694 dvbRcsRtnStatusGroup OBJECT-GROUP 3695 OBJECTS { 3696 dvbRcsRtnStatusPayloadUnit 3697 } 3698 STATUS current 3699 DESCRIPTION "A collection of objects allowing access to return 3700 link status." 3701 ::= {dvbRcsRcstGroups 20} 3703 dvbRcsRtnExtStatusGroup OBJECT-GROUP 3704 OBJECTS { 3705 dvbRcsRcstRtnLinkStatus, 3706 dvbRcsRtnStatusEbN0, 3707 dvbRcsRtnStatusSFDuration 3708 } 3709 STATUS current 3710 DESCRIPTION "A collection of objects allowing access to 3711 extended return link status." 3712 ::= {dvbRcsRcstGroups 21} 3714 dvbRcsRcstOduListGroup OBJECT-GROUP 3715 OBJECTS { 3716 dvbRcsTxTypeDescription, 3717 dvbRcsOduTxType, 3718 dvbRcsRxTypeDescription, 3719 dvbRcsOduRxType, 3720 dvbRcsAntennaTypeDescription, 3721 dvbRcsOduAntennaType 3722 } 3723 STATUS current 3724 DESCRIPTION "A collection of objects supporting flexible 3725 selection of ODU devices." 3726 ::= { dvbRcsRcstGroups 22 } 3728 END 3730 XXX NOTE: RFC Editor please ammend the lines below to reflect 3731 copyright policy for publication of MIBs. 3733 Copyright (c) 2009 IETF Trust and the persons identified as authors 3734 of the code. All rights reserved. 3736 Redistribution and use in source and binary forms, with or without 3737 modification, are permitted provided that the following conditions 3738 are met: 3740 * Redistributions of source code must retain the above copyright 3741 notice, this list of conditions and the following disclaimer. 3743 * Redistributions in binary form must reproduce the above copyright 3744 notice, this list of conditions and the following disclaimer in the 3745 documentation and/or other materials provided with the distribution. 3747 * Neither the name of Internet Society, IETF or IETF Trust, nor the 3748 names of specific contributors, may be used to endorse or promote 3749 products derived from this software without specific prior written 3750 permission. 3752 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 3753 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT 3754 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 3755 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT 3756 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, 3757 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 3758 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 3759 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 3760 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 3761 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 3762 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3764 5. Security Considerations 3766 Some of the readable objects in this MIB module (i.e., objects with a 3767 MAX-ACCESS other than not-accessible) may be considered sensitive or 3768 vulnerable in some network environments. 3770 SNMP versions prior to SNMPv3 did not include adequate security. Even 3771 if the network itself is secure (for example by using IPsec), even 3772 then, there is no control as to who on the secure network is allowed 3773 to access and GET/SET (read/change/create/delete) the objects in this 3774 MIB module. 3776 It is RECOMMENDED that implementers consider the security features 3777 provided by the SNMPv3 framework (see [RFC3410], section 8), 3778 including full support for the SNMPv3 cryptographic mechanisms (for 3779 authentication and privacy). 3781 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3782 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3783 enable cryptographic security. It is then a customer/operator 3784 responsibility to ensure that the SNMP entity giving access to an 3785 instance of this MIB module, is properly configured to give access to 3786 the objects only to those principals (users) that have legitimate 3787 rights to indeed GET or SET (change/create/delete) them. 3789 6. IANA Considerations 3791 This document includes no request to IANA. The transmission and 3792 ifType numbers described in Section 3 have already been assigned 3793 under the smi-numbers registry. 3795 7. Acknowledgments 3797 The authors thank Gorry Fairhurst for advice in the preparation of 3798 this document. 3800 The authors recognize this document is a collective effort of the 3801 SatLabs Group (www.satlabs.org), in particular the many corrections 3802 and suggestions brought by Juan Luis Manas. 3804 8. References 3806 8.1. Normative References 3808 [IANA] Internet Assigned Numbers Authority, "Internet Assigned 3809 Numbers Authority", June 2008, 3810 . 3812 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3813 Requirement Levels", BCP 14, RFC 2119, March 1997 (BEST 3814 CURRENT PRACTICE). 3816 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3817 Schoenwaelder, Ed., "Structure of Management Information, 3818 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3820 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3821 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3822 STD 58, RFC 2579, April 1999. 3824 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3825 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 3826 1999. 3828 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB", 3829 RFC 2863, June 2000. 3831 8.2. Informative References 3833 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 3834 Generic Coding of Moving Pictures and Associated Audio 3835 Information Systems", International Standardisation 3836 Organisation (ISO). 3838 [ITU-ATM] ITU-T Recommendation I.432 (all parts): "B-ISDN user- 3839 network interface - Physical layer specification". 3841 [ITU-AAL5] ITU-T Recommendation I.363-5 (1996): "B-ISDN ATM 3842 Adaptation Layer specification: Type 5 AAL". 3844 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 3845 Specifications for Data Broadcasting", European 3846 Telecommunications Standards Institute (ETSI). 3848 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); Modulation 3849 and Coding for DBS satellite systems at 11/12 GHz", 3850 European Telecommunications Standards Institute (ETSI). 3852 [ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB); 3853 Second generation framing structure, channel coding and 3854 modulation systems for Broadcasting, Interactive Services, 3855 News Gathering and other broadband satellite applications", 3856 European Telecommunications Standards Institute (ETSI). 3858 [ETSI-GSE] ETSI TS 102 606 "Digital Video Broadcasting (DVB); 3859 Generic Stream Encapsulation (GSE) Protocol", European 3860 Telecommunications Standards Institute (ETSI). 3862 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 3863 Interaction Channel for Satellite Distribution Systems", 3864 European Telecommunications Standards Institute (ETSI). 3866 [ETSI-SI] ETSI EN 300 468 "Digital Video Broadcasting (DVB); 3867 Specification for Service Information (SI) in DVB Systems", 3868 European Telecommunications Standards Institute (ETSI). 3870 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3871 "Introduction and Applicability Statements for Internet- 3872 Standard Management Framework", RFC 3410, December 2002. 3874 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- 3875 Nocker, B., and H. Linder, "A Framework for Transmission of 3876 IP Datagrams over MPEG-2 Networks", RFC 4259, November 3877 2005. 3879 [SATLABS] SatLabs System Recommendations. Available at 3880 www.satlabs.org. 3882 9. Authors' Addresses 3884 Stephane Combes 3885 ESTEC 3886 European Space Agency 3887 Keplerlaan 1 - P.O. Box 299 3888 2200 AG Noordwijk ZH 3889 The Netherlands 3891 Email: stephane.combes@esa.int 3892 URL: telecom.esa.int 3894 Petter Chr. Amundsen 3895 VeriSat AS 3896 P.O Box 1 3897 1330 Fornebu 3898 Norway 3900 Email: pca@verisat.no 3901 URL: www.verisat.no 3903 Micheline Lambert 3904 Advantech Satellite Networks 3905 2341 boul. Alfred-Nobel 3906 Saint-Laurent (Montreal,)H4S 2A9 3907 Quebec, Canada 3909 Email: micheline.lambert@advantechamt.com 3910 URL: www.advantechsatnet.com 3912 Hans-Peter Lexow 3913 STM Norway 3914 Vollsveien 21 3915 1366 Lysaker 3916 Norway 3918 Email: hlexow@stmi.com 3919 URL: www.stmi.com 3921 10. Disclaimer 3923 This document may contain material from IETF Documents or IETF 3924 Contributions published or made publicly available before November 3925 10, 2008. The person(s) controlling the copyright in some of this 3926 material may not have granted the IETF Trust the right to allow 3927 modifications of such material outside the IETF Standards Process. 3928 Without obtaining an adequate license from the person(s) 3929 controlling the copyright in such materials, this document may not 3930 be modified outside the IETF Standards Process, and derivative 3931 works of it may not be created outside the IETF Standards Process, 3932 except to format it for publication as an RFC or to translate it 3933 into languages other than English. 3935 11. Copyright Notice 3937 Copyright (c) 2009 IETF Trust and the persons identified as the 3938 document authors. All rights reserved. 3940 This document is subject to BCP 78 and the IETF Trust's Legal 3941 Provisions Relating to IETF Documents in effect on the date of 3942 publication of this document (http://trustee.ietf.org/license-info). 3943 Please review these documents carefully, as they describe your rights 3944 and restrictions with respect to this document. 3946 11.1. License for Code Components 3948 XXX NOTE: RFC Editor please ammend the lines below to reflect 3949 copyright policy for publication of MIBs. 3951 A copyright note for the Code Components is provided at the end of 3952 Section 4. In addition to the licenses granted above, Code Components 3953 are also licensed to each person who wishes to receive such a license 3954 on the terms of the "BSD License", as described below. The Legal 3955 Provisions are specified in the IETF Trust's Legal Provisions 3956 Relating to IETF Documents in effect on the date of publication of 3957 this document (http://trustee.ietf.org/license-info). 3958 <<< RFC Ed Note: please remove the text below, prior to publications 3959 >>> 3961 Change Log. 3963 Rev -00 3965 * First draft, for comment by the community. 3967 Rev -01 3969 * Second draft, for comment by the community. 3971 The MIB module is renamed DVBRCS-MIB to reflect that it covers more 3972 than solely interface issues. 3974 The MIB has been updated with 3976 * a conformance section that captures the options 3978 * structural changes and corrections to achieve this 3980 * SYNTAX refinements where applicable 3982 * UNITS declarations where applicable 3984 Document reformatted to conform to I-D format conventions. 3986 Rev -02 3988 * Third draft, for comment by the community. 3990 Update following comments received from the ipdvb list (Gorry 3991 Fairhurst). 3993 Rev -03 3995 * Fourth draft, for comment by the community. 3997 Update following comments received from Martin Stiemerling and 3998 complement/corrections from the SatLabs Group. 4000 Rev -04 4001 * Fifth draft 4003 Corrected read-write into read-create MAXACCESS for objects in 4004 requestClassTable and pidPoolTable. 4006 Minor updates to correct format of tables and some MIB comments. 4008 Rev -05 4010 * Sixth draft 4012 Addition of dvbRcs prefix to all descriptors, following request from 4013 MIB doctor (according to Appendix C of RFC 4181). 4015 Clarification and complements brought to ODU configuration objects 4016 (see section 3.4.1), ODU structural entities definition in 4017 dvbRcsRcstSystem group and conformance section. 4019 Modification of the interface types usage (section 3.3) in order to 4020 have alignment with Ethernet interface (dvbRcsMacLayer should count link 4021 layer packets and bytes, like Ethernet does, and not IP). 4023 Updated copyright to reflect current IETF Trust guidelines and advice 4024 from Dan Romascanu. 4026 <<>