idnits 2.17.1 draft-combes-ipdvb-mib-rcs-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 3703. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3680. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3687. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3693. 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 Copyright Line does not match the current year == Line 219 has weird spacing: '... dBi deci...' == Line 221 has weird spacing: '... dBm deci...' == 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 lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 1, 2008) is 5709 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 7 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: February 2009 September 1, 2008 8 The DVB-RCS MIB 9 draft-combes-ipdvb-mib-rcs-04.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that 14 any applicable patent or other IPR claims of which he or she is 15 aware have been or will be disclosed, and any of which he or she 16 becomes aware will be disclosed, in accordance with Section 6 of 17 BCP 79. 19 This document may not be modified, and derivative works of it may not 20 be created, except to publish it as an RFC and to translate it into 21 languages other than English, or to extract section 4 as-is for 22 separate use. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that 26 other groups may also distribute working documents as Internet- 27 Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html 40 This Internet-Draft will expire on March 1, 2009. 42 Abstract 44 This document describes the MIB module for the Digital Video 45 Broadcasting Return Channel via Satellite system (DVB-RCS). It 46 defines a set of MIB entities to characterize the behavior and 47 performance of network layer entities deploying DVB-RCS. 49 Table of Contents 51 1. Introduction...................................................3 52 2. Conventions used in this document..............................4 53 2.1. Abbreviations.............................................5 54 2.2. Glossary..................................................6 55 2.2.1. Star DVB-RCS network.................................6 56 2.2.2. Mesh DVB-RCS network.................................6 57 2.2.3. Transparent DVB-RCS network..........................6 58 2.2.4. Regenerative DVB-RCS network.........................6 59 2.2.5. DVB-RCS MAC layer....................................6 60 2.2.6. DVB-RCS Downlink.....................................6 61 2.2.7. DVB-RCS Uplink.......................................6 62 2.2.8. IDU..................................................6 63 2.2.9. ODU..................................................6 64 2.2.10. RCST................................................6 65 2.2.11. NCC.................................................6 66 2.2.12. Configuration file..................................6 67 2.2.13. Logfile.............................................6 68 2.2.14. InstallLogfile......................................6 69 2.2.15. Antenna alignment...................................6 70 2.2.16. CW frequency........................................6 71 2.2.17. Request Class.......................................6 72 2.2.18. Channel ID..........................................6 73 2.2.19. ATM profile.........................................6 74 2.2.20. MPEG profile........................................6 75 2.2.21. PID pool............................................6 76 2.2.22. Capacity Categories.................................6 77 2.2.23. Start transponder...................................6 78 2.2.24. DVB-S...............................................6 79 2.2.25. DVB-S2 and CCM/VCM/ACM..............................6 80 2.2.26. Interactive Network.................................6 81 3. MIB Module overview............................................6 82 3.1. Textual Conventions.......................................6 83 3.2. Structure of the MIB......................................6 84 3.3. Relationship to the Interfaces MIB Module.................6 85 3.4. MIB groups description....................................6 86 3.4.1. rcstSystem...........................................6 87 3.4.2. rcstNetwork..........................................6 88 3.4.3. rcstInstall..........................................6 89 3.4.4. rcstQos..............................................6 90 3.4.5. rcstControl..........................................6 91 3.4.6. rcstState............................................6 92 3.4.7. fwdLink (fwdConfig and fwdStatus groups).............6 93 3.4.8. rtnLink (rtnConfig and rtnStatus groups).............6 95 4. Definitions....................................................6 96 5. Security Considerations........................................6 97 6. IANA Considerations............................................6 98 7. Acknowledgments................................................6 99 8. References.....................................................6 100 8.1. Normative References......................................6 101 8.2. Informative References....................................6 102 9. Authors' Addresses.............................................6 103 10. Intellectual Property Statement...............................6 104 11. Disclaimer of Validity........................................6 105 12. Copyright Statement...........................................6 107 1. Introduction 109 The SatLabs Group [SATLABS] is an international non-profit EEIG 110 (European Economic Interest Grouping) committed to large-scale 111 adoption and deployment of the Digital Video Broadcasting Return 112 Channel via Satellite (DVB-RCS) standard [ETSI-RCS]. SatLabs members 113 are service providers, satellite operators, system integrators, 114 terminal manufacturers and technology providers with an interest in 115 DVB-RCS. 117 Since its creation in 2001, the main goal of the SatLabs Group has 118 been to achieve interoperability between DVB-RCS terminals and 119 systems. Therefore, the Group has defined the SatLabs Qualification 120 Program that provides an independent certification process for DVB- 121 RCS Terminals based on System Recommendations defined by SatLabs. To 122 enhance products interoperability, beyond the physical and MAC layer 123 mechanisms defined in the DVB-RCS standard, SatLabs has expanded its 124 Recommendations in the field of DVB-RCS terminal management 125 [SATLABS]. As a part of this effort, SatLabs has specified a common 126 SNMP Management Information Base (MIB) for DVB-RCS terminals, which 127 is defined in this document. 129 A DVB-RCS terminal is denoted as a Return Channel Satellite Terminal 130 (RCST) in the remainder of this document. This consists of an Indoor 131 Unit (IDU) and an Outdoor Unit (ODU) connected through an Inter 132 Facility Link (IFL), usually a coaxial L-band interface. On the user 133 side, the IDU is connected to the user network through a Local Area 134 Network (LAN) interface (usually Ethernet). On the network side, the 135 ODU is connected via a satellite link (the Air Interface). 137 The DVB-RCS MIB is implemented in the IDU of an RCST. RCST 138 management can be performed either through the LAN interface (Local 139 management) or through the Air Interface (Remote management from the 140 Network Control Center, NCC). RCST and NCC elements are shown on 141 Figure 1. 143 +------------+ 144 | IP | 145 | End Host | 146 +-----+------+ 147 | 148 - - - - - - - -|- - - - - - - - - - - - - - - - 149 | | LAN interface | 150 | 151 | +------+--------+ | 152 | Indoor Unit | 153 | | (IDU) | | 154 +------+--------+ 155 | | | 156 Inter Facility Link (IFL) 157 | | | 158 +------+--------+ 159 | | OutDoor Unit | | 160 | (ODU) | 161 | +------+--------+ | 162 | 163 | | Air Interface | 164 - - - - - - - |- - - - - - - - - - - - - - - - 165 RCST | 166 | +----------------+ 167 +------->| Network Control| 168 | Center (NCC) | 169 +----------------+ 171 FIGURE 1: RCST architecture 173 2. Conventions used in this document 175 This memo defines a portion of the Management Information Base (MIB) 176 for use with network management protocols in the Internet community. 178 For a detailed overview of the documents that describe the current 179 Internet-Standard Management Framework, please refer to section 7 of 180 RFC 3410 [RFC3410]. 182 Managed objects are accessed via a virtual information store, termed 183 the Management Information Base or MIB. MIB objects are generally 184 accessed through the Simple Network Management Protocol (SNMP). 185 Objects in the MIB are defined using the mechanisms defined in the 186 Structure of Management Information (SMI). This memo specifies a MIB 187 module that is compliant to the SMIv2, which is described in STD 58, 188 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 189 [RFC2580]. 191 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 192 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 193 document are to be interpreted as described in RFC 2119 [RFC2119]. 195 2.1. Abbreviations 197 AAL5 ATM Adaptation Layer Type 5 199 ACM Adaptive Coding and Modulation (defined in [ETSI-DVBS2]) 201 ATM Asynchronous Transfer Mode 203 AVBDC Absolute Volume-Based Dynamic Capacity 205 BER Bit Error Ratio 207 BUC Block Up-Converter 209 CCM Constant Coding and Modulation 211 CNR Carrier to Noise Ratio 213 CRA Continuous Rate Assignment 215 CSC Common Signalling Channel 217 CW Continuous Wave (carrier frequency) 219 dBi deciBel (isotropic) 221 dBm deciBel (with respect to 1 mW) 223 DSCP DiffServ Code Point 225 ETSI European Telecommunications Standards Institute 226 FEC Forward Error Correction 228 GS Generic Stream 230 GSE Generic Stream Encapsulation 232 IDU InDoor Unit 234 IFL Inter-Facility Link 236 LNB Low Noise Block 238 LO Local Oscillator 240 MAC Medium Access Control 242 MIB Management Information Base 244 MPEG Motion Pictures Expert Group 246 MPE Multi-Protocol Encapsulation 248 NCC Network Control Centre 250 OAM Operations and Management 252 ODU OutDoor Unit 254 PHB Per-Hop Behavior 256 PID Packet IDentifier (MPEG, used as Program Identifier in DVB) 258 QoS Quality of Service 260 RBDC Rate-Based Dynamic Capacity 262 RC Request Class 264 RCST Return Channel via Satellite Terminal (DVB-RCS Terminal) 266 Rx Receive 268 SDU Service Data Unit 270 SSPA Solid State Power Amplifier 272 TDM Time Division Multiplex 273 TDMA Time Division Multiple Access 275 TS Transport Stream (as defined by MPEG) 277 Tx Transmit 279 VBDC Volume-Based Dynamic Capacity 281 VCI Virtual Channel Identifier (ATM) 283 VPI Virtual Path Identifier (ATM) 285 Vpp Volts peak-to-peak 287 2.2. Glossary 289 The terms in this document are derived either from DVB-RCS standard 290 specifications [ETSI-RCS] or from SatLabs System Recommendations 291 [SATLABS]. 293 2.2.1. Star DVB-RCS network 295 This denotes a hub-and-spoke configuration where all communications 296 pass through a central hub, that usually also includes the NCC. Peer- 297 to-peer communication between RCSTs is possible, but through a double 298 satellite hop (this traffic has to pass through the hub). 300 2.2.2. Mesh DVB-RCS network 302 This denotes a mesh configuration that supports peer-to-peer 303 communications in a single satellite hop directly between RCSTs. 305 2.2.3. Transparent DVB-RCS network 307 This denotes a network using transparent satellite transponders. Star 308 or mesh network configurations can be supported. In the case of a 309 mesh configuration, RCSTs need to incorporate a TDMA receiver in 310 addition to the TDM receiver. 312 2.2.4. Regenerative DVB-RCS network 314 This denotes a network using regenerative satellite transponders, 315 i.e. including some On-Board Processing functionality allowing 316 demodulation and decoding of the uplink TDMA signals and re-multiplex 317 the traffic on the downlink. Star or mesh network configurations can 318 be supported. 320 2.2.5. DVB-RCS MAC layer 322 The DVB-RCS MAC Layer represents the air interface of an RCST, as 323 defined in the DVB-RCS standard. The interface supports star and mesh 324 networks and is bi-directional. 326 2.2.6. DVB-RCS Downlink 328 The downlink is a DVB-RCS physical link based on TDM. It corresponds 329 to the forward link of a DVB-RCS transparent system or the downlink 330 of a DVB-RCS regenerative system. It is based on either the DVB-S or 331 DVB-S2 standard. In the DVB-RCS context, this interface is bi- 332 directional. 334 2.2.7. DVB-RCS Uplink 336 The DVB-RCS Uplink is based on TDMA. It corresponds to the return or 337 mesh link of a RCS transparent system or the uplink of a RCS 338 regenerative system. It is based on the DVB-RCS standard. 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. Logfile 373 The logfile is stored at the RCST. This is used to log particular 374 events that occurr on RCST side. 376 2.2.14. InstallLogfile 378 The Installlogfile is stored at the RCST. This logs particular events 379 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 systemSatLabsProfileMap represents the SatLabs profiles supported as 548 defined in [SATLABS]. 550 systemSatLabsOptionMap represents the SatLabs options supported as 551 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 systemSatLabsFeatureMap represents the SatLabs optional features 557 supported as defined in [SATLABS]. These represent minor features, 558 not necessary for interoperability. They are not used for the 559 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 rcstCompliance group while 574 the units of conformance are described within the rcstGroups 575 group. 577 The dvbrcsMIBobjects group is further structured into three groups: 578 rcst, fwdLink and rtnLink. 580 The rcst group covers management related to the RCST equipment. It is 581 structured into six groups: 583 o rcstSystem 584 o rcstNetwork 586 o rcstInstall 588 o rcstQos 590 o rcstControl 592 o rcstState 594 The fwdLink group covers management information related to the RCST 595 forward link. It is structured into two groups: 597 o fwdConfig 599 o fwdStatus 601 The rtnLink group covers management information related to the RCST 602 return link. It is structured into two groups: 604 o rtnConfig 606 o rtnStatus 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 The MIB module finally includes a conformance section including 619 conformance groups and compliance statements. 621 3.3. Relationship to the Interfaces MIB Module 623 This section clarifies the relationship of this MIB module to the 624 Interfaces MIB [RFC2863]. Several areas of correlation are addressed 625 in the following. The implementer is referred to the Interfaces MIB 626 document in order to understand the general intent of these areas. 628 IANA has assigned three ifType labels for DVB-RCS. Each RCST MUST 629 support at least the three following interfaces: 631 o dvbRcsMacLayer (239), -- DVB-RCS MAC Layer 633 DVB-RCS MAC Layer represents the air interface of a RCST, as 634 defined in [ETSI-RCS]. This interface supports star and mesh 635 networks and is bi-directional. Only star networks are considered 636 by the present MIB module. 638 o dvbTdm (240), -- DVB Satellite TDM 640 DVB-RCS Physical link based on Time Division Multiplexing. It 641 corresponds to the forward link of a RCS transparent system or the 642 downlink of a RCS regenerative system. It is based on either DVB-S 643 or DVB-S2 standard. Only transparent systems are considered by the 644 present MIB module. 646 In the DVB-RCS context, this interface is uni-directional (i.e. 647 forward link, or downstream). 649 o dvbRcsTdma (241), -- DVB-RCS TDMA 651 DVB-RCS Physical link based on Time Division Multiple Access. It 652 corresponds to the return or mesh link of a RCS transparent system 653 or the uplink of a RCS regenerative system. It is based on the DVB- 654 RCS standard. 656 In the context of star transparent and mesh regenerative DVB-RCS 657 systems, this interface is uni-directional. 659 In the context of mesh transparent DVB-RCS systems, this interface 660 is bi-directional. 662 Only star transparent systems are considered by the present MIB 663 module (i.e. return link, or upstream). 665 The protocol stack (as reflected in ifStackTable) will be as follows: 667 +--------------------------+ 668 | IP | 669 +--------------------------+ 670 | dvbRcsMacLayer | 671 +---------------+----------+ 672 | dvbRcsTdma | dvbTdm | 673 +---------------+----------+ 674 | MPEG/ATM | MPEG/GS | 675 +---------------+----------+ 677 FIGURE 2: RCST protocol stack 679 GS (Generic Stream) is defined in [ETSI-DVBS2]. 681 The additional Ethernet interface is used on the LAN side of the 682 RCST. 684 An instance of ifEntry exists for each DvbTdm interface, for each 685 DvbRcsTdma (normally only one), and for each DvbRcsMac layer 686 (normally only one). 688 The interface counters relate to: 690 o dvbRcsMacLayer: DVB-RCS two-way MAC that counts aggregate DVB-RCS 691 SDU traffic (IP layer) 693 o dvbTdm: DVB-RCS TDM that counts either Generic Stream 694 Encapsulation(GSE) or Multi-Protocol Encapsulation (MPE) traffic, 695 as applicable for the specific configuration 697 . GSE is defined in [ETSI-GSE] 698 . MPE is defined in [ETSI-DAT] 700 o dvRcsTdma: DVB-RCS TDMA that counts either ATM Adaptation Layer 5 701 (AAL5) or MPE traffic, as applicable for a specific configuration 703 The ifStackTable [RFC2863] MUST be implemented to identify the 704 relationships among sub-interfaces. 706 The following example is a DVB-RCS star network with DVB-S and DVB- 707 RCS. As illustrated on Figure 3, it shows a DVB-RCS MAC interface 708 with one downstream and one upstream interfaces. In this network, ATM 709 encapsulation is used in the DVB-RCS uplink. Two ATM Logical Ports 710 are shown. DVB-S2 or DVB-S can be used in the downlink. MPEG can be 711 used as well instead of ATM Logical Ports. 713 +----------------------------------------------------------+ 714 | IP Network Layer | 715 +------+----------------------------------+----------------+ 716 | | 717 +------+-------+ +------------------+----------------+ 718 | Ethernet LAN | | dvbRcsMacLayer | 719 +--------------+ +-------------+---------------------+ 720 | | 721 +-------------+-----------+ +---+---+ 722 | dvbRcsTdma | |dvbTdm | 723 +-----+-------------+-----+ +-------+ 724 | | 725 +-----+-----+ +-----+-----+ 726 |atm-logical| |atm-logical| 727 +-----------+ +-----------+ 729 FIGURE 3: Example stacking 731 As can be seen from this example, the dvbRcsMacLayer interface is 732 layered on top of the downstream and upstream interfaces, and the 733 upstream interface is layered on top of upstream ATM logical links. 735 In this example, the assignment of index values could be as follows: 737 ifIndex ifType Description 738 2 dvbRcsMacLayer (239) DVB-RCS MAC Layer 739 3 dvbRcsTdma (240) DVB-RCS TDMA Upstream 740 4 dvbTdm(241) DVB-RCS TDM Downstream 741 5 atm-logical(80) ATM Logical Port 742 6 atm-logical(80) ATM Logical Port 744 The corresponding ifStack entries would then be: 746 +--------------------+-------------------+ 747 | IfStackHigherLayer | ifStackLowerLayer | 748 +--------------------+-------------------+ 749 | 0 | 1 | 750 | 0 | 2 | 751 | 1 | 0 | 752 | 2 | 3 | 753 | 2 | 4 | 754 | 3 | 5 | 755 | 3 | 6 | 756 | 4 | 0 | 757 | 5 | 0 | 758 | 6 | 0 | 759 +--------------------+-------------------+ 761 FIGURE 1: Example ifStack entries 763 3.4. MIB groups description 765 3.4.1. rcstSystem 767 The MIB objects in this group gather some basic information that 768 would allow anyone to trace the history - the life - of the RCST as 769 well as to get a complete description of its constitution on the 770 component point of view, including the SatLabs options/features 771 support statement. Many of the parameters will be defined at 772 installation. 774 This group contains description parameters related to the RCST type 775 (ODU type) and location. These parameters are believed to stay 776 unchanged once it has been defined during installation. Modification 777 of hardware equipment, maintenance operations and geographical re- 778 location may require an update of those MIB objects. They are. Note 779 that rcstSystem.systemLocation object gives the location of the ODU 780 antenna, which is needed for network operation, while the 781 system.sysLocation (MIB-II SNMP OID) provides the location of the IDU 782 unit, which can not be used for the same purpose. 784 3.4.2. rcstNetwork 786 This group contains all the MIB objects related to network 787 parameters. 789 In this subgroup, two objects have been defined in order to 790 differentiate between control and user traffic and associate them 791 with a physical interface. Both rcstNetwork.networkLanIpAddress 792 (Traffic) and rcstNetwork.networkOamIpAddress (OAM) provide the value 793 of the IP address of, respectively, the user traffic and the control 794 and management traffic. 796 3.4.3. rcstInstall 798 This group contains all the information related to the RCST 799 installation and commissioning. Many parameters are believed to stay 800 unchanged once it has been defined during installation. Modification 801 of hardware equipment, maintenance operations and geographical re- 802 location may require an update of those MIB objects. 804 3.4.4. rcstQos 806 This group contains objects to configure the Quality of Service (QoS) 807 of the RCST by the NCC. 809 The pktClass table defines the packet classification for IP layer 3 810 classifications. Each pktClass entry is mapped to a phbEntry in the 811 phbMappingTable. 813 The phbMappingTable makes the relation between a packet 814 classification entry, a Per-Hop Behavior (PHB) identifier and a 815 Request class entry. 817 The requestClassTable defines all the layer 2 DVB-RCS QoS parameters. 819 3.4.5. rcstControl 821 This MIB group contains objects a network manager can use to invoke 822 actions and tests supported by the RCST agent and to retrieve the 823 action/test results. 825 3.4.6. rcstState 827 This MIB group describes the fault state, software versions and 828 configuration file versions of the RCST. 830 3.4.7. fwdLink (fwdConfig and fwdStatus groups) 832 This MIB group contains parameters that enable the NCC to have access 833 to data about the forward link. 835 Configuration information is kept into the fwdLink.fwdConfig 836 subgroup. Status information is kept into the fwdLink.fwdStatus 837 subgroup. 839 The information of the fwdLink.fwdConfig.fwdStartTable are used for 840 the first time the RCST tries to acquire the forward link. All these 841 objects values are aligned with the Satellite Delivery System 842 Descriptor in the Network Information Table (NIT) table [ETSI-SI]. 844 The objects in the fwdLink.fwdConfig.fwdStatusTable are aligned with 845 the satellite forward path descriptor form the RCS Map Table (RMT) 846 [ETSI-RCS] and with the Physical Layer (PL) Header [ETSI-DVBS2], 847 which specified the MODCOD (modulation and FEC rate) and the Type 848 (frame length short of long and the presence/absence of pilots). 850 3.4.8. rtnLink (rtnConfig and rtnStatus groups) 852 This MIB group contains parameters that enable the NCC to have access 853 to data about the return link. 855 Configuration information is kept into the rtnLink.rtnConfig 856 subgroup. Status information is kept into the rtnLink.rtnStatus 857 subgroup. 859 The RCST is only able to deal with one return link at a time. Hence, 860 there is no need to define a table to collect the different SNMP 861 objects, as it is done for the forward. 863 4. Definitions 865 DVBRCS-MIB DEFINITIONS ::= BEGIN 867 IMPORTS 868 MODULE-IDENTITY, 869 Integer32, 870 IpAddress, 871 transmission, 872 OBJECT-TYPE 873 FROM SNMPv2-SMI -- [RFC2578] 874 TEXTUAL-CONVENTION, 875 DisplayString, 876 RowStatus 877 FROM SNMPv2-TC -- [RFC2579] 878 OBJECT-GROUP, 879 MODULE-COMPLIANCE 880 FROM SNMPv2-CONF; -- [RFC2580] 882 dvbrcsMIB MODULE-IDENTITY 883 LAST-UPDATED "200807291200Z" 884 ORGANIZATION "The SatLabs Group" 885 CONTACT-INFO 886 "The SatLabs Group 887 Web: www.satlabs.org 888 E-mail: info@satlabs.org" 889 DESCRIPTION 890 "DVB-RCS MIB subtree. 891 This MIB module applies to equipment that is a 892 Return Channel Satellite Terminal (RCST) defined in 893 the Digital Video Broadcasting Return 894 Channel via Satellite system (DVB-RCS) standard (ETSI EN 301 895 791 Digital Video Broadcasting (DVB); Interaction Channel 896 for Satellite Distribution Systems, European 897 Telecommunications Standards Institute (ETSI)). 898 It defines a set of MIB entities to characterise the 899 behaviour and performance of network layer entities 900 implementing DVB-RCS. 901 This MIB module is intended to be used by DVB-RCS equipment 902 following the SatLabs System Recommendations, defined by the 903 SatLabs Group and available at www.satlabs.org." 905 REVISION "200807291200Z" 906 DESCRIPTION 907 "Revision of this MIB module, following comments from ipdvb 908 WG." 909 ::= { transmission 239 } 911 --=================================================================== 912 -- Textual Conventions 913 --=================================================================== 915 SatLabsProfileMap ::= TEXTUAL-CONVENTION 916 STATUS current 917 DESCRIPTION 918 "This textual convention enumerates the declaration of the 919 SatLabs defined terminal profiles. (0) refers to the most 920 significant bit." 921 REFERENCE 922 "SatLabs System Recommendations available at www.satlabs.org" 923 SYNTAX BITS { 924 dvbs(0), 925 dvbs2ccm(1), 926 dvbs2acm(2), 927 spare1(3), 928 spare2(4), 929 spare3(5), 930 spare4(6), 931 spare5(7), 932 spare6(8), 933 spare7(9), 934 spare8(10), 935 spare9(11), 936 spare10(12), 937 spare11(13), 938 spare12(14), 939 spare13(15), 940 spare14(16), 941 spare15(17), 942 spare16(18), 943 spare17(19), 944 spare18(20), 945 spare19(21), 946 spare20(22), 947 spare21(23), 948 spare22(24), 949 spare23(25), 950 spare24(26), 951 spare25(27), 952 spare26(28), 953 spare27(29), 954 spare28(30), 955 spare29(31) 956 } 958 SatLabsOptionMap ::= TEXTUAL-CONVENTION 959 STATUS current 960 DESCRIPTION 961 "This textual convention enumerates the declaration of the 962 SatLabs defined options. (0) refers to the most significant 963 bit." 964 REFERENCE 965 "SatLabs System Recommendations available at www.satlabs.org" 966 SYNTAX BITS { 967 mpegTrf(0), 968 coarseSync(1), 969 wideHop(2), 970 fastHop(3), 971 dynamicMfTdma(4), 972 contentionSync(5), 973 qpskLow(6), 974 mod16Apsk(7), 975 mod32Apsk(8), 976 normalFec(9), 977 multiTs(10), 978 gsTs(11), 979 enhQoS(12), 980 pep(13), 981 http(14), 982 ftp(15), 983 dns(16), 984 chIdStrict(17), 985 nlid(18), 986 snmpMisc(19), 987 spare1(20), 988 spare2(21), 989 spare3(22), 990 spare4(23), 991 spare5(24), 992 spare6(25), 993 spare7(26), 994 spare8(27), 995 spare9(28), 996 spare10(29), 997 spare11(30), 998 spare12(31) 999 } 1001 SatLabsFeatureMap ::= TEXTUAL-CONVENTION 1002 STATUS current 1003 DESCRIPTION 1004 "This textual convention enumerates the declaration of 1005 the SatLabs specified compapatibility and configuration 1006 features. (0) refers to the most significant bit." 1007 REFERENCE 1008 "SatLabs System Recommendations available at 1009 www.satlabs.org" 1010 SYNTAX BITS { 1011 rcstPara(0), 1012 installLog(1), 1013 enhClassifier(2), 1014 routeId(3), 1015 spare1(4), 1016 spare2(5), 1017 spare3(6), 1018 spare4(7), 1019 spare5(8), 1020 spare6(9), 1021 spare7(10), 1022 spare8(11), 1023 spare9(12), 1024 spare10(13), 1025 spare11(14), 1026 spare12(15), 1027 spare13(16), 1028 spare14(17), 1029 spare15(18), 1030 spare16(19), 1031 spare17(20), 1032 spare18(21), 1033 spare19(22), 1034 spare20(23), 1035 spare21(24), 1036 spare22(25), 1037 spare23(26), 1038 spare24(27), 1039 spare25(28), 1040 spare26(29), 1041 spare27(30), 1042 spare28(31) 1043 } 1045 --=================================================================== 1046 -- object type definitions 1047 --=================================================================== 1048 dvbrcsMIBObjects OBJECT IDENTIFIER ::= {dvbrcsMIB 1} 1049 dvbrcsConformance OBJECT IDENTIFIER ::= {dvbrcsMIB 2} 1051 rcst OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 1} 1052 fwdLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 2} 1053 rtnLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 3} 1055 rcstSystem OBJECT IDENTIFIER ::= {rcst 1} 1056 rcstNetwork OBJECT IDENTIFIER ::= {rcst 2} 1057 rcstInstall OBJECT IDENTIFIER ::= {rcst 3} 1058 rcstQos OBJECT IDENTIFIER ::= {rcst 4} 1059 rcstControl OBJECT IDENTIFIER ::= {rcst 5} 1060 rcstState OBJECT IDENTIFIER ::= {rcst 6} 1062 fwdConfig OBJECT IDENTIFIER ::= {fwdLink 1} 1063 fwdStatus OBJECT IDENTIFIER ::= {fwdLink 2} 1065 rtnConfig OBJECT IDENTIFIER ::= {rtnLink 1} 1066 rtnStatus OBJECT IDENTIFIER ::= {rtnLink 2} 1068 --=================================================================== 1069 --- rcstSystem sub-tree object types 1070 --=================================================================== 1071 systemMibRevision OBJECT-TYPE 1072 SYNTAX DisplayString 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "This object allows the SNMP agent to report the implemented 1077 MIB module revision. 1078 The supported REVISION of this module is reported." 1079 ::= {rcstSystem 1} 1081 --=================================================================== 1082 -- Options declared according to the textual conventions 1083 --=================================================================== 1084 systemSatLabsProfilesDeclaration OBJECT-TYPE 1085 SYNTAX SatLabsProfileMap 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "Indicates the SatLabs profiles supported as defined in the 1090 SatLabs System Recommendations. A value of 1 indicates that 1091 the respective option is supported. The mapping to the 1092 profiles is to be understood as described here. (0) refers 1093 to the most significant bit. 1095 dvbs(0) -> DVBS profile (DVB-S support) 1096 dvbs2ccm(1) -> DVB-S2 CCM profile (CCM support) 1097 dvbs2acm(2) -> DVB-S2 ACM profile (CCM, VCM and ACM 1098 support)" 1099 REFERENCE 1100 "SatLabs System Recommendations available at www.satlabs.org" 1101 ::= {rcstSystem 2} 1103 systemSatLabsOptionsDeclaration OBJECT-TYPE 1104 SYNTAX SatLabsOptionMap 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "Indicates the SatLabs options supported as defined in the 1109 SatLabs System Recommendations. A value of 1 indicates that 1110 the respective option is supported. The mapping to the 1111 options is to be understood as described here. (0) refers to 1112 the most significant bit. 1114 mpegTrf(0) -> MPEG_TRF 1115 coarseSync(1) -> COARSE_SYNC 1116 wideHop(2) -> WIDE_HOPP 1117 fastHop(3) -> FAST_HOPP 1118 dynamicMfTdma(4) -> Dynamic_MF_TDMA 1119 contentionSync(5) -> CONTENTION_SYNC 1120 qpskLow(6) -> QPSKLOW 1121 mod16Apsk(7) -> 16APSK 1122 mod32Apsk(8) -> 32APSK 1123 normalFec(9) -> NORMALFEC 1124 multiTs(10) -> MULTITS 1125 gsTs(11) -> GSTS 1126 enhQoS(12) -> ENHQOS 1127 pep(13) -> PEP 1128 http(14) -> HTTP 1129 ftp(15) -> FTP 1130 dns(16) -> DNS 1131 chIdStrict(17) -> CHID_STRICT 1132 nlid(18) -> NLID 1133 snmpMisc(19) -> SNMPMISC 1135 The support of specific options mandates the support of 1136 specific objects and access levels." 1137 REFERENCE 1138 "SatLabs System Recommendation available at www.satlabs.org" 1139 ::= {rcstSystem 3} 1141 systemSatLabsFeaturesDeclaration OBJECT-TYPE 1142 SYNTAX SatLabsFeatureMap 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "Indicates the optional compatibility features and minor 1147 options supported as defined in the SatLabs System 1148 Recommendations. A value of 1 indicates that the respective 1149 feature is supported. The mapping to the features is to be 1150 understood as described here. (0) refers to the most 1151 significant bit. 1153 rcstPara(0) -> RCST_PARA feature 1154 installLog(1) -> INSTALL_LOG feature 1155 enhClassifier(2) -> ENHCLASSIFIER feature 1156 routeId(3) -> ROUTE_ID feature 1158 The support of specific features mandates the support of 1159 specific objects and access levels." 1160 REFERENCE 1161 "SatLabs System Recommendation available at www.satlabs.org" 1162 ::= {rcstSystem 4} 1164 systemLocation OBJECT-TYPE 1165 SYNTAX DisplayString 1166 MAX-ACCESS read-write 1167 STATUS current 1168 DESCRIPTION 1169 "Physical location of the ODU antenna expressed as 1170 Longitude, Latitude and Altitude. The string 1171 shall have 31 characters in the following format: 1172 ,,,,,M 1173 where x, y and z represents digits, 1174 a=N or S, 1175 b=E or W, 1176 Reading the digits from left to right: 1177 'x' 7 latitude digits; x digits 1-2 contain the degrees, 1178 x digits 3-7 contain the minutes in decimal; 1179 'y' 8 longitude digits; y digits 1-3 contain the degrees, 1180 y digits 4-8 contain the minutes in decimal; 1181 ''' 5 altitude digits; meters above sea level in decimal; 1182 '.' is the decimal point; 1183 ',' is the field separator; 1184 'M' is the indicator for altitude meters. 1186 This format is a modified subset of the NMEA 0183 1187 (National Marine Electronics Association, Interface 1188 Standard) format for Global Positioning System Fix Data. 1190 This location and the satellite position are used to 1192 calculate the RCST-satellite path delay. 1194 Note: The system.sysLocation object of MIB-II provides physical 1195 location of the IDU unit." 1196 ::= {rcstSystem 5} 1198 systemOduAntennaSize OBJECT-TYPE 1199 SYNTAX DisplayString 1200 UNITS "cm" 1201 MAX-ACCESS read-write 1202 STATUS current 1203 DESCRIPTION 1204 "This object gives the diameter of the antenna. This value 1205 shall be given in centimeters. It is defined at 1206 installation. 1207 The object can be used in conjunction with environmental 1208 requirements. " 1209 ::= {rcstSystem 6} 1211 systemOduAntennaGain OBJECT-TYPE 1212 SYNTAX Integer32 1213 UNITS "x0.1 dBi" 1214 MAX-ACCESS read-write 1215 STATUS current 1216 DESCRIPTION 1217 "This field describes the antenna peak gain of the ODU and 1218 shall be defined by the installer. The gain shall be given 1219 in tenth of dBi for more flexibility, i.e. 46.5 dBi will be 1220 represented by 465. Defined at installation." 1221 ::= {rcstSystem 7} 1223 systemOduSspa OBJECT-TYPE 1224 SYNTAX Integer32 1225 UNITS "x0.1 W" 1226 MAX-ACCESS read-write 1227 STATUS current 1228 DESCRIPTION 1229 "This field describes the Solid State Power Amplifier 1230 installed in the ODU and shall be defined by the installer. 1231 The power shall be given in tenth of a Watt, i.e. 0,5 W will 1232 be represented by 5, 1 W by 10 and 2 W by 20. 1234 Defined at installation." 1235 ::= {rcstSystem 8} 1237 systemOduTxType OBJECT-TYPE 1238 SYNTAX DisplayString 1239 MAX-ACCESS read-write 1240 STATUS current 1241 DESCRIPTION 1242 "Describes the type of transmitter installed in the ODU." 1243 ::= {rcstSystem 9} 1245 systemOduRxType OBJECT-TYPE 1246 SYNTAX DisplayString 1247 MAX-ACCESS read-write 1248 STATUS current 1249 DESCRIPTION 1250 "Describes the type of LNB installed in the ODU, with 1251 information such as vendor type, output type (single, twin, 1252 quad,...), etc." 1253 ::= {rcstSystem 10} 1255 systemOduRxBand OBJECT-TYPE 1256 SYNTAX INTEGER { 1257 oduHighRxBand (0), 1258 oduLowRxBand (1) 1259 } 1260 MAX-ACCESS read-write 1261 STATUS current 1262 DESCRIPTION 1263 "Describes whether High Band or Low Band is selected in 1264 the LNB. Specifying High Band results in activation of a 1265 18-26 kHz tone with 0.4-0.8 Vpp in the Rx IFL cable: 1266 (0) - High Band 1267 (1) - Low Band" 1268 ::= {rcstSystem 11} 1270 systemOduRxLO OBJECT-TYPE 1271 SYNTAX Integer32 1272 UNITS "x100 Hz" 1273 MAX-ACCESS read-write 1274 STATUS current 1275 DESCRIPTION 1276 "Frequency of LNB Local Oscillator (in 100 Hz)" 1277 ::= {rcstSystem 12} 1279 systemOduTxLO OBJECT-TYPE 1280 SYNTAX Integer32 1281 UNITS "x100 Hz" 1282 MAX-ACCESS read-write 1283 STATUS current 1284 DESCRIPTION 1285 "Frequency of Block Up-Converter Local Oscillator 1286 (in 100 Hz)." 1287 ::= {rcstSystem 13} 1289 systemIduPep OBJECT IDENTIFIER ::= {rcstSystem 14} 1291 tcpPep OBJECT-TYPE 1292 SYNTAX INTEGER{ 1293 disabled (0), 1294 enabled (1) 1295 } 1296 MAX-ACCESS read-write 1297 STATUS current 1298 DESCRIPTION 1299 "Status and control of embedded TCP PEP. 1300 0 - disabled or not implemented 1301 1 - enabled " 1302 ::={ systemIduPep 1} 1304 httpPep OBJECT-TYPE 1305 SYNTAX INTEGER{ 1306 disabled (0), 1307 enabled (1) 1308 } 1309 MAX-ACCESS read-write 1310 STATUS current 1311 DESCRIPTION 1312 "Status and control of embedded HTTP PEP. 1313 0 - disabled or not implemented 1314 1 - enabled " 1316 ::={ systemIduPep 2} 1318 --=================================================================== 1319 -- rcstNetwork sub-tree object types 1320 --=================================================================== 1321 networkOamIpAddress OBJECT-TYPE 1322 SYNTAX IpAddress 1323 MAX-ACCESS read-write 1324 STATUS current 1325 DESCRIPTION 1326 "OAM IP Address of the RCST. This object is used with both 1327 IP and interfaces MIB-II subgroups. It uniquely determines 1328 the interface through which OAM traffic passes. 1329 The OAM IP address may be statically or dynamically 1330 assigned. It is system dependent whether the OAM IP address 1331 and the Traffic IP address are the same address." 1332 ::= {rcstNetwork 1} 1334 networkOamIpNetworkMask OBJECT-TYPE 1335 SYNTAX IpAddress 1336 MAX-ACCESS read-write 1337 STATUS current 1338 DESCRIPTION 1339 "Network Mask for the OAM IP Address." 1340 ::= {rcstNetwork 2} 1342 networkOamIpAddressAssign OBJECT-TYPE 1343 SYNTAX INTEGER { 1344 oamIpAddressStatic (1), 1345 oamIpAddressDynamic (2) 1346 } 1347 MAX-ACCESS read-write 1348 STATUS current 1349 DESCRIPTION 1350 "Identifies whether the OAM IP address is statically 1351 (1) or dynamically (2) assigned." 1352 ::= {rcstNetwork 3} 1354 networkLanIpAddress OBJECT-TYPE 1355 SYNTAX IpAddress 1356 MAX-ACCESS read-write 1357 STATUS current 1358 DESCRIPTION 1359 "IP address of the LAN interface" 1360 ::= {rcstNetwork 4} 1362 networkLanIpNetworkMask OBJECT-TYPE 1363 SYNTAX IpAddress 1364 MAX-ACCESS read-write 1365 STATUS current 1366 DESCRIPTION 1367 "Mask for the LAN interface" 1368 ::= {rcstNetwork 5} 1370 networkAirInterfaceDefaultGateway OBJECT-TYPE 1371 SYNTAX IpAddress 1372 MAX-ACCESS read-write 1373 STATUS current 1374 DESCRIPTION 1375 "Default Gateway for the air interface" 1376 ::= {rcstNetwork 6} 1378 networkDnsServers OBJECT IDENTIFIER ::= {rcstNetwork 7} 1380 primaryDnsServerIpAddress OBJECT-TYPE 1381 SYNTAX IpAddress 1382 MAX-ACCESS read-write 1383 STATUS current 1384 DESCRIPTION 1385 "IP address of the primary DNS server in the NCC." 1386 ::= { networkDnsServers 1} 1388 secondaryDnsServerIpAddress OBJECT-TYPE 1389 SYNTAX IpAddress 1390 MAX-ACCESS read-write 1391 STATUS current 1392 DESCRIPTION 1393 "IP address of the secondary DNS server in the NCC." 1394 ::= { networkDnsServers 2} 1396 networkNccMgtIpAddress OBJECT-TYPE 1397 SYNTAX IpAddress 1398 MAX-ACCESS read-write 1399 STATUS current 1400 DESCRIPTION 1401 "IP address of the management server in the NCC." 1402 ::= {rcstNetwork 8} 1404 networkConfigFileDownloadUrl OBJECT-TYPE 1405 SYNTAX DisplayString 1406 MAX-ACCESS read-write 1407 STATUS current 1408 DESCRIPTION 1409 "Full path name for the configuration file download. 1410 It includes the protocol type (tftp or ftp) and the 1411 associated server IP address or hostname. Hostname can 1412 only be used if DNS is supported by the RCST. 1413 The format of this parameter follows RFC 1738." 1414 ::= {rcstNetwork 9} 1416 networkInstallLogFileDownloadUrl OBJECT-TYPE 1417 SYNTAX DisplayString 1418 MAX-ACCESS read-write 1419 STATUS current 1420 DESCRIPTION 1421 "Full path of the installation log file to download. 1422 It includes the protocol type (tftp or ftp) and the 1423 associated server IP address or hostname. Hostname can 1424 only be used if DNS is supported by the RCST. The 1425 installation log file can be created on the installer's 1426 computer and downloaded to the RCST. 1427 The format of this parameter follows RFC 1738." 1428 ::= {rcstNetwork 10} 1430 networkConfigFileUploadUrl OBJECT-TYPE 1431 SYNTAX DisplayString 1432 MAX-ACCESS read-write 1433 STATUS current 1434 DESCRIPTION 1435 "Full path name for the configuration file upload. 1436 It includes the protocol type (tftp or ftp) and the 1437 associated server IP address or hostname. Hostname can 1438 only be used if DNS is supported by the RCST. 1440 The format of this parameter follows RFC 1738." 1441 ::= {rcstNetwork 11} 1443 networkLogFileUploadUrl OBJECT-TYPE 1444 SYNTAX DisplayString 1445 MAX-ACCESS read-write 1446 STATUS current 1447 DESCRIPTION 1448 "Full path of the event log file. It includes the protocol 1449 type (tftp or ftp) and the associated server IP address 1450 or hostname. Hostname can only be used if DNS is supported 1451 by the RCST. 1452 The format of this parameter follows RFC 1738." 1453 ::= {rcstNetwork 12} 1455 networkInstallLogFileUploadUrl OBJECT-TYPE 1456 SYNTAX DisplayString 1457 MAX-ACCESS read-write 1458 STATUS current 1459 DESCRIPTION 1460 "Full path of the installation log file. It includes the 1461 protocol type (tftp or ftp) and the associated server 1462 IP address or hostname. Hostname can only be used if DNS is 1463 supported by the RCST. The installation log file can be 1464 retrieved from the RCST by the NCC or by the installer 1465 via the LAN. 1466 The format of this parameter follows RFC 1738." 1467 ::= {rcstNetwork 13} 1469 --=================================================================== 1470 -- rcstInstall sub-tree object types 1471 --=================================================================== 1472 installAntennaAlignmentState OBJECT-TYPE 1473 SYNTAX INTEGER { 1474 antennaAlignmentStart (1), 1475 antennaAlignmentDeny (2), 1476 antennaAlignmentContinue(3), 1477 antennaAlignmentStop (4), 1478 antennaAlignmentSuccess (5), 1479 antennaAlignmentFail (6) 1480 } 1481 MAX-ACCESS read-write 1482 STATUS current 1483 DESCRIPTION 1484 "Indicates the alignment state of the antenna: 1485 (1)-Start; 1486 (2)-Deny; 1487 (3)-Continue; 1488 (4)-Stop; 1489 (5)-Success; 1490 (6)-Fail" 1491 ::= {rcstInstall 1} 1493 installCwFrequency OBJECT-TYPE 1494 SYNTAX Integer32 1495 UNITS "x100 Hz" 1496 MAX-ACCESS read-write 1497 STATUS current 1498 DESCRIPTION 1499 "Frequency at which the transmitted Continuous Wave carrier 1500 (in 100 Hz). 1501 Minimum required precision is 1 kHz." 1502 ::= {rcstInstall 2} 1504 installCwMaxDuration OBJECT-TYPE 1505 SYNTAX Integer32 1506 UNITS "seconds" 1507 MAX-ACCESS read-write 1508 STATUS current 1509 DESCRIPTION 1510 "Time after which the Continuous Wave carrier must be put 1511 down (in seconds)" 1512 ::= {rcstInstall 3} 1514 installCwPower OBJECT-TYPE 1515 SYNTAX Integer32 1516 UNITS "x0.1 dBm" 1517 MAX-ACCESS read-write 1518 STATUS current 1519 DESCRIPTION 1520 "IDU TX output level when the IDU is configured to send CW. 1521 The resolution is 0.1 dBm and the accuracy is +/- 1 dBm. 1523 Reconfiguration is applied immediately to a CW." 1524 ::= {rcstInstall 4} 1526 installCoPolReading OBJECT-TYPE 1527 SYNTAX Integer32 1528 UNITS "x0.1 dB" 1529 MAX-ACCESS read-write 1530 STATUS current 1531 DESCRIPTION 1532 "Co-Polarisation measured value during installation 1533 procedure (in 0.1 dB)" 1534 ::= {rcstInstall 5} 1536 installXPolReading OBJECT-TYPE 1537 SYNTAX Integer32 1538 UNITS "x0.1 dB" 1539 MAX-ACCESS read-write 1540 STATUS current 1541 DESCRIPTION 1542 "Cross-Polarisation measured value during installation 1543 procedure (in 0.1 dB)" 1544 ::= {rcstInstall 6} 1546 installCoPolTarget OBJECT-TYPE 1547 SYNTAX Integer32 1548 UNITS "x0.1 dB" 1549 MAX-ACCESS read-write 1550 STATUS current 1551 DESCRIPTION 1552 "Co-Polarisation target value during installation procedure 1553 (in 0.1 dB)." 1554 ::= {rcstInstall 7} 1556 installXPolTarget OBJECT-TYPE 1557 SYNTAX Integer32 1558 UNITS "x0.1 dB" 1559 MAX-ACCESS read-write 1560 STATUS current 1561 DESCRIPTION 1562 "Cross-Polarisation target value during installation procedure 1563 (in 0.1 dB)" 1565 ::= {rcstInstall 8} 1567 installStandByDuration OBJECT-TYPE 1568 SYNTAX Integer32 1569 UNITS "seconds" 1570 MAX-ACCESS read-write 1571 STATUS current 1572 DESCRIPTION 1573 "Time to wait in stand-by mode (in seconds)" 1574 ::= {rcstInstall 9} 1576 installTargetEsN0 OBJECT-TYPE 1577 SYNTAX Integer32(0..315) 1578 UNITS "x0.1 dB" 1579 MAX-ACCESS read-write 1580 STATUS current 1581 DESCRIPTION 1582 "This value describes the wanted Es/N0 value that enables 1583 operation of the return link with the required error 1584 performance. The values shall be given in tenth of dB and 1585 the initial value shall be equal to 7 dB. The range shall be 1586 from 0 dBm to 31.5 dBm with a precision of 0.1 dB." 1587 DEFVAL { 70 } 1588 ::= {rcstInstall 10} 1590 --=================================================================== 1591 -- rcstQos sub-tree object types 1592 --=================================================================== 1593 pktClassTable OBJECT-TYPE 1594 SYNTAX SEQUENCE OF PktClassEntry 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "This table describes the packet classification used in the 1599 DVB-RCS terminal. The number of entries is specified by 1600 PktClassIndex. " 1601 ::={rcstQos 1} 1603 pktClassEntry OBJECT-TYPE 1604 SYNTAX PktClassEntry 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "An entry in the packet classification table. One object type 1609 of each entry may have a value in the active range (a non- 1610 default value).The other object types are then assumed set to 1611 'inactive'. The entry with the lowest index value takes 1612 precedence when classifying a packet." 1613 INDEX { pktClassIndex } 1614 ::= { pktClassTable 1 } 1616 PktClassEntry ::= SEQUENCE { 1617 pktClassIndex Integer32, 1618 pktClassDscpLow Integer32, 1619 pktClassDscpHigh Integer32, 1620 pktClassDscpMarkValue Integer32, 1621 pktClassIpProtocol Integer32, 1622 pktClassIpSrcAddress IpAddress, 1623 pktClassIpSrcAddressMask IpAddress, 1624 pktClassIpDstAddress IpAddress, 1625 pktClassIpDstAddressMask IpAddress, 1626 pktClassSrcPortLow Integer32, 1627 pktClassSrcPortHigh Integer32, 1628 pktClassDstPortLow Integer32, 1629 pktClassDstPortHigh Integer32, 1630 pktClassVlanUserPri Integer32, 1631 pktClassPhbAssociation Integer32, 1632 pktClassRowStatus RowStatus 1633 } 1635 pktClassIndex OBJECT-TYPE 1636 SYNTAX Integer32 (1..64) 1637 MAX-ACCESS not-accessible 1638 STATUS current 1639 DESCRIPTION 1640 "Index automatically incremented by one at row creation." 1641 ::={pktClassEntry 1} 1643 pktClassDscpLow OBJECT-TYPE 1644 SYNTAX Integer32 (0..63) 1645 MAX-ACCESS read-create 1646 STATUS current 1647 DESCRIPTION 1648 "This object specifies the low value of a range of DiffServ 1649 Code Point (DSCP) values to which a packet is compared. 1650 A value of 0 is used to inactivate." 1651 DEFVAL { 0 } 1652 ::={pktClassEntry 2} 1654 pktClassDscpHigh OBJECT-TYPE 1655 SYNTAX Integer32 (0..63) 1656 MAX-ACCESS read-create 1657 STATUS current 1658 DESCRIPTION 1659 "This object specifies the high value of a range of DiffServ 1660 Code Point (DSCP) values to which a packet is compared. 1661 A value of 63 is used to inactivate." 1662 DEFVAL { 63 } 1663 ::={pktClassEntry 3} 1665 pktClassDscpMarkValue OBJECT-TYPE 1666 SYNTAX Integer32 (-1..63) 1667 MAX-ACCESS read-create 1668 STATUS current 1669 DESCRIPTION 1670 "This object is the DiffServ Code Point (DSCP) value used to 1671 mark the packet, -1 indicates no DSCP marking. Possible DSCP 1672 marks values are (0..63)" 1673 DEFVAL { -1 } 1674 ::={pktClassEntry 4} 1676 pktClassIpProtocol OBJECT-TYPE 1677 SYNTAX Integer32 (-1..255) 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "This object specifies the IP protocol to which a 1682 packet is compared. A value of 255 indicates inactive." 1683 DEFVAL { -1 } 1684 ::={pktClassEntry 5} 1686 pktClassIpSrcAddress OBJECT-TYPE 1687 SYNTAX IpAddress 1688 MAX-ACCESS read-create 1689 STATUS current 1690 DESCRIPTION 1691 "This object specifies the IP source address to which a 1692 packet is compared." 1693 ::={pktClassEntry 6} 1695 pktClassIpSrcAddressMask OBJECT-TYPE 1696 SYNTAX IpAddress 1697 MAX-ACCESS read-create 1698 STATUS current 1699 DESCRIPTION 1700 "This object specifies which bits of the IP source address 1701 will be matched. A mask of all zeros indicates that the 1702 selectivity is inactive." 1703 DEFVAL { '00000000'H } 1704 ::={pktClassEntry 7} 1706 pktClassIpDstAddress OBJECT-TYPE 1707 SYNTAX IpAddress 1708 MAX-ACCESS read-create 1709 STATUS current 1710 DESCRIPTION 1711 "This object specifies the IP destination address to which a 1712 packet is compared." 1713 ::={pktClassEntry 8} 1715 pktClassIpDstAddressMask OBJECT-TYPE 1716 SYNTAX IpAddress 1717 MAX-ACCESS read-create 1718 STATUS current 1719 DESCRIPTION 1720 "This object specifies which bits of the IP destination 1721 address will be matched. A mask of all zeros indicates that 1722 the selectivity is inactive." 1723 DEFVAL { '00000000'H } 1724 ::={pktClassEntry 9} 1726 pktClassSrcPortLow OBJECT-TYPE 1727 SYNTAX Integer32 (-1..65535) 1728 MAX-ACCESS read-create 1729 STATUS current 1730 DESCRIPTION 1731 "This object specifies the low range of the source 1732 port to which a packet is compared. A value of -1 indicates 1733 that the selectivity is inactive." 1734 DEFVAL { -1 } 1735 ::={pktClassEntry 10} 1737 pktClassSrcPortHigh OBJECT-TYPE 1738 SYNTAX Integer32 (-1..65535) 1739 MAX-ACCESS read-create 1740 STATUS current 1741 DESCRIPTION 1742 "This object specifies the high range of the source port to 1743 which a packet is compared. A value of -1 indicates that the 1744 selectivity is inactive." 1745 DEFVAL { -1 } 1746 ::={pktClassEntry 11} 1748 pktClassDstPortLow OBJECT-TYPE 1749 SYNTAX Integer32 (-1..65535) 1750 MAX-ACCESS read-create 1751 STATUS current 1752 DESCRIPTION 1753 "This object specifies the low range of the destination 1754 port to which a packet is compared. A value of -1 indicates 1755 that the selectivity is inactive." 1756 DEFVAL { -1 } 1757 ::={pktClassEntry 12} 1759 pktClassDstPortHigh OBJECT-TYPE 1760 SYNTAX Integer32 (-1..65535) 1761 MAX-ACCESS read-create 1762 STATUS current 1763 DESCRIPTION 1764 "This object specifies the high range of the destination 1765 port to which a packet is compared. A value of -1 indicates 1766 that the selectivity is inactive." 1767 DEFVAL { -1 } 1768 ::={pktClassEntry 13} 1769 pktClassVlanUserPri OBJECT-TYPE 1770 SYNTAX Integer32 (-1..7) 1771 MAX-ACCESS read-create 1772 STATUS current 1773 DESCRIPTION 1774 "This object specifies the VLAN User Priority to which a 1775 packet is compared. A value of -1 indicates that the 1776 selectivity is inactive." 1777 DEFVAL { -1 } 1778 ::={pktClassEntry 14} 1780 pktClassPhbAssociation OBJECT-TYPE 1781 SYNTAX Integer32 (0..63) 1782 MAX-ACCESS read-create 1783 STATUS current 1784 DESCRIPTION 1785 "Associate the filter entry to a specific PHB (refer to 1786 phbIdentifier)." 1787 ::={pktClassEntry 15} 1789 pktClassRowStatus OBJECT-TYPE 1790 SYNTAX RowStatus 1791 MAX-ACCESS read-create 1792 STATUS current 1793 DESCRIPTION 1794 "Standard SNMP row status" 1795 ::={pktClassEntry 16} 1797 --=================================================================== 1798 -- PhbMappingTable 1799 --=================================================================== 1800 phbMappingTable OBJECT-TYPE 1801 SYNTAX SEQUENCE OF PhbMappingEntry 1802 MAX-ACCESS not-accessible 1803 STATUS current 1804 DESCRIPTION 1805 "This table is a list of Per-Hop Behaviour (PHB) MIB entries. 1806 It describes the PHB mapping to the Request Class." 1807 ::={rcstQos 2} 1808 phbMappingEntry OBJECT-TYPE 1809 SYNTAX PhbMappingEntry 1810 MAX-ACCESS not-accessible 1811 STATUS current 1812 DESCRIPTION 1813 "An entry in the PHB mapping table." 1814 INDEX { phbIdentifier } 1815 ::= { phbMappingTable 1 } 1817 PhbMappingEntry ::= SEQUENCE { 1818 phbIdentifier Integer32, 1819 phbName DisplayString, 1820 phbRequestClassAssociation Integer32, 1821 phbMappingRowStatus RowStatus 1822 } 1824 phbIdentifier OBJECT-TYPE 1825 SYNTAX Integer32 (1..64) 1826 MAX-ACCESS not-accessible 1827 STATUS current 1828 DESCRIPTION 1829 "Identification of the Per-Hop Behaviour (PHB) (1..64)." 1830 ::={phbMappingEntry 1} 1832 phbName OBJECT-TYPE 1833 SYNTAX DisplayString 1834 MAX-ACCESS read-create 1835 STATUS current 1836 DESCRIPTION 1837 "The name of the Per-Hop Behaviour (PHB)." 1838 ::={phbMappingEntry 2} 1840 phbRequestClassAssociation OBJECT-TYPE 1841 SYNTAX Integer32 (1..16) 1842 MAX-ACCESS read-create 1843 STATUS current 1844 DESCRIPTION 1845 "This object is an association of this Per-Hop Behaviour 1846 (PHB) to a Request class (by reference to a Request Class 1847 index)." 1848 ::={phbMappingEntry 3} 1849 phbMappingRowStatus OBJECT-TYPE 1850 SYNTAX RowStatus 1851 MAX-ACCESS read-create 1852 STATUS current 1853 DESCRIPTION 1854 "Standard SNMP row status" 1855 DEFVAL { active } 1856 ::={phbMappingEntry 4} 1858 --=================================================================== 1859 -- RequestClassTable 1860 --=================================================================== 1861 requestClassTable OBJECT-TYPE 1862 SYNTAX SEQUENCE OF RequestClassEntry 1863 MAX-ACCESS not-accessible 1864 STATUS current 1865 DESCRIPTION 1866 "This table is a list of Request class entries. This class 1867 describes the layer 2 QoS objects." 1868 ::={rcstQos 3} 1870 requestClassEntry OBJECT-TYPE 1871 SYNTAX RequestClassEntry 1872 MAX-ACCESS not-accessible 1873 STATUS current 1874 DESCRIPTION 1875 "An entry in the Request Class table." 1876 INDEX { requestClassIndex } 1877 ::= { requestClassTable 1 } 1879 RequestClassEntry ::= SEQUENCE { 1880 requestClassIndex Integer32, 1881 requestClassName DisplayString, 1882 requestClassChanId Integer32, 1883 requestClassVccVpi Integer32, 1884 requestClassVccVci Integer32, 1885 requestClassPidPoolReference Integer32, 1886 requestClassCra Integer32, 1887 requestClassRbdcMax Integer32, 1888 requestClassRbdcTimeout Integer32, 1889 requestClassVbdcMax Integer32, 1890 requestClassVbdcTimeout Integer32, 1891 requestClassVbdcMaxBackLog Integer32, 1892 requestClassRowStatus RowStatus 1893 } 1895 requestClassIndex OBJECT-TYPE 1896 SYNTAX Integer32 (1..16) 1897 MAX-ACCESS not-accessible 1898 STATUS current 1899 DESCRIPTION 1900 "Index of the Request Class table. A total of 16 entries are 1901 supported." 1902 ::={requestClassEntry 1} 1904 requestClassName OBJECT-TYPE 1905 SYNTAX DisplayString 1906 MAX-ACCESS read-create 1907 STATUS current 1908 DESCRIPTION 1909 "Name of the Request Class." 1910 ::={requestClassEntry 2} 1912 requestClassChanId OBJECT-TYPE 1913 SYNTAX Integer32 (0..15) 1914 MAX-ACCESS read-create 1915 STATUS current 1916 DESCRIPTION 1917 "Channel id of the Request Class." 1918 ::={requestClassEntry 3} 1920 requestClassVccVpi OBJECT-TYPE 1921 SYNTAX Integer32 (0..255) 1922 MAX-ACCESS read-create 1923 STATUS current 1924 DESCRIPTION 1925 "Defines VPI used for the Request Class (ATM profile)." 1926 ::={requestClassEntry 4} 1928 requestClassVccVci OBJECT-TYPE 1929 SYNTAX Integer32 (0..65535) 1930 MAX-ACCESS read-create 1931 STATUS current 1932 DESCRIPTION 1933 "Defines VCI used for the Request Class (ATM profile)." 1934 ::={requestClassEntry 5} 1936 requestClassPidPoolReference OBJECT-TYPE 1937 SYNTAX Integer32 (1..16) 1938 MAX-ACCESS read-create 1939 STATUS current 1940 DESCRIPTION 1941 "Reference to the Packet IDentifier (PID) pool applicable 1942 for the Request Class." 1943 ::={requestClassEntry 6} 1945 requestClassCra OBJECT-TYPE 1946 SYNTAX Integer32 1947 UNITS "bits/s" 1948 MAX-ACCESS read-create 1949 STATUS current 1950 DESCRIPTION 1951 "Define Continuous Rate Assignment (CRA) level for the 1952 Request Class in bit per second (bits/s)." 1953 ::={requestClassEntry 7} 1955 requestClassRbdcMax OBJECT-TYPE 1956 SYNTAX Integer32 1957 UNITS "x2 kbits/s" 1958 MAX-ACCESS read-create 1959 STATUS current 1960 DESCRIPTION 1961 "Maximum Rate-Based Dynamic Capacity (RBDC) that can be 1962 requested for the Request Class, in number of 2 kbits/s" 1963 ::={requestClassEntry 8} 1965 requestClassRbdcTimeout OBJECT-TYPE 1966 SYNTAX Integer32 1967 UNITS "superframes" 1968 MAX-ACCESS read-create 1969 STATUS current 1970 DESCRIPTION 1971 "Persistence of the Rate-Based Dynamic Capacity (RBDC) 1972 request, expressed in superframes" 1973 ::={requestClassEntry 9} 1975 requestClassVbdcMax OBJECT-TYPE 1976 SYNTAX Integer32 1977 UNITS "ATM cells/MPEG packets" 1978 MAX-ACCESS read-create 1979 STATUS current 1980 DESCRIPTION 1981 "Maximum Volume-Based Dynamic Capacity (VBDC) that can be 1982 allocated to the Request Class, in payload units (one ATM 1983 cell or one MPEG packet) per superframe" 1984 ::={requestClassEntry 10} 1986 requestClassVbdcTimeout OBJECT-TYPE 1987 SYNTAX Integer32 1988 UNITS "superframes" 1989 MAX-ACCESS read-create 1990 STATUS current 1991 DESCRIPTION 1992 "Time after which the RCST considers that the pending 1993 requests are lost. The RCST may issue new requests for that 1994 traffic. Volume-Based Dynamic Capacity (VBDC) Timeout is 1995 expressed in superframes." 1996 ::={requestClassEntry 11} 1998 requestClassVbdcMaxBackLog OBJECT-TYPE 1999 SYNTAX Integer32 2000 UNITS "bytes" 2001 MAX-ACCESS read-create 2002 STATUS current 2003 DESCRIPTION 2004 "Volume-Based Dynamic Capacity (VBDC) back log per Request 2005 Class (expressed in bytes)" 2006 ::={requestClassEntry 12} 2008 requestClassRowStatus OBJECT-TYPE 2009 SYNTAX RowStatus 2010 MAX-ACCESS read-create 2011 STATUS current 2012 DESCRIPTION 2013 "Standard SNMP row status" 2014 DEFVAL { active } 2015 ::={requestClassEntry 13} 2017 --=================================================================== 2018 -- The table of PID pools 2019 --=================================================================== 2021 pidPoolTable OBJECT-TYPE 2022 SYNTAX SEQUENCE OF PidPoolEntry 2023 MAX-ACCESS not-accessible 2024 STATUS current 2025 DESCRIPTION 2026 "This table contains the Packet IDentifier (PID) pools. 2027 For MPEG profile several Request Classes may be mapped 2028 within a pool of several PIDs to allow Section Packing 2029 across Several Request Classes. 2030 A PID value may occur in more than one PID pool. Each PID 2031 value can effectively occur only once in each pool." 2032 ::={rcstQos 4} 2034 pidPoolEntry OBJECT-TYPE 2035 SYNTAX PidPoolEntry 2036 MAX-ACCESS not-accessible 2037 STATUS current 2038 DESCRIPTION 2039 "An entry in the PID pool table." 2040 INDEX { pidPoolIndex, pidIndex } 2041 ::= { pidPoolTable 1 } 2043 PidPoolEntry ::= SEQUENCE { 2044 pidPoolIndex Integer32, 2045 pidIndex Integer32, 2046 pidValue Integer32, 2047 pidPoolRowStatus RowStatus 2048 } 2050 pidPoolIndex OBJECT-TYPE 2051 SYNTAX Integer32 (1..16) 2052 MAX-ACCESS not-accessible 2053 STATUS current 2054 DESCRIPTION 2055 "Index of the PID pool in the PID pool table." 2056 ::={pidPoolEntry 1} 2058 pidIndex OBJECT-TYPE 2059 SYNTAX Integer32 (1..16) 2060 MAX-ACCESS not-accessible 2061 STATUS current 2062 DESCRIPTION 2063 "Index of the PID entry within the PID pool." 2064 ::={pidPoolEntry 2} 2066 pidValue OBJECT-TYPE 2067 SYNTAX Integer32 (0..8191) 2068 MAX-ACCESS read-create 2069 STATUS current 2070 DESCRIPTION 2071 "Defines one of the PIDs to be used in a PID pool of 2072 pidPoolIndex. 2073 A PID value may occur in more than one PID pool. Each PID 2074 value can effectively occur only once in each pool." 2075 ::={pidPoolEntry 3} 2077 pidPoolRowStatus OBJECT-TYPE 2078 SYNTAX RowStatus 2079 MAX-ACCESS read-create 2080 STATUS current 2081 DESCRIPTION 2082 "Standard SNMP row status" 2083 DEFVAL { active } 2084 ::={pidPoolEntry 4} 2086 qosGlobalRbdcMax OBJECT-TYPE 2087 SYNTAX Integer32 2088 UNITS "x2 kbits/s" 2089 MAX-ACCESS read-write 2090 STATUS current 2091 DESCRIPTION 2092 "Global maximum RBDC that can be requested for the RCST, in 2093 number of 2 kbits/s." 2094 ::={rcstQos 5} 2096 qosGlobalVbdcMax OBJECT-TYPE 2097 SYNTAX Integer32 2098 UNITS "ATM cells/MPEG packets" 2099 MAX-ACCESS read-write 2100 STATUS current 2101 DESCRIPTION 2102 "Global maximum VBDC that can be allocated to the RCST, in 2103 payload units (one ATM cell or one MPEG packet) per 2104 superframe." 2105 ::={rcstQos 6} 2107 qosGlobalVbdcMaxBackLog OBJECT-TYPE 2108 SYNTAX Integer32 2109 UNITS "bytes" 2110 MAX-ACCESS read-write 2111 STATUS current 2112 DESCRIPTION 2113 "Global VBDC back log at RCST level (expressed in bytes). It 2114 is used only if the VBDC back log is not configured in the 2115 Request class (expressed in bytes)." 2116 ::={rcstQos 7} 2118 qosChannelIdStrictDispatching OBJECT-TYPE 2119 SYNTAX INTEGER { 2120 notStrict (0), 2121 strict (1) 2122 } 2123 MAX-ACCESS read-write 2124 STATUS current 2125 DESCRIPTION 2126 "Indicates whether the RCST will strictly follow RC 2127 association when signaled through Channel_ID in the TBTP: 2128 (0)- no strict association 2129 (1)- strict association" 2130 ::={rcstQos 8} 2132 --=================================================================== 2133 -- rcstControl sub-tree object types 2134 --=================================================================== 2135 ctrlRebootCommand OBJECT-TYPE 2136 SYNTAX INTEGER { 2137 idle (1), 2138 normal (2), 2139 alternate (3) 2140 } 2141 MAX-ACCESS read-write 2142 STATUS current 2143 DESCRIPTION 2144 "This variable shall force the RCST to reboot 2145 (1)- idle 2146 (2)- normal reboot (from current software load) 2147 (3)- reboot from alternate load (swap to alternate load 2148 before reboot)" 2149 DEFVAL {1} 2150 ::={rcstControl 1} 2152 ctrlRcstTxDisable OBJECT-TYPE 2153 SYNTAX INTEGER { 2154 idle (1), 2155 disable (2) 2156 } 2157 MAX-ACCESS read-write 2158 STATUS current 2159 DESCRIPTION 2160 "This variable shall force the RCST to stop transmission 2161 (transmit disabled as defined in SatLabs System 2162 Recommendations): 2163 (1)- idle 2164 (2)- initiate Tx Disabled" 2165 DEFVAL {1} 2166 ::={rcstControl 2} 2168 ctrlUserTrafficDisable OBJECT-TYPE 2169 SYNTAX INTEGER { 2170 idle (1), 2171 disable (2) 2172 } 2173 MAX-ACCESS read-write 2174 STATUS current 2175 DESCRIPTION 2176 "This variable shall disable user traffic (only RCST 2177 management traffic can be transmitted) 2178 (1)- idle 2179 (2)- disable user traffic" 2180 DEFVAL {1} 2181 ::={rcstControl 3} 2183 ctrlCwEnable OBJECT-TYPE 2184 SYNTAX INTEGER { 2185 off (1), 2186 on (2) 2187 } 2188 MAX-ACCESS read-write 2189 STATUS current 2190 DESCRIPTION 2191 "This variable will force the RCST to start transmission of 2192 CW, if the RCST is first set to the installation state, and 2193 is properly configured for CW transmission: 2194 (1)- off 2195 (2)- on" 2196 DEFVAL {1} 2197 ::={rcstControl 4} 2199 ctrlOduTxReferenceEnable OBJECT-TYPE 2200 SYNTAX INTEGER { 2201 off (1), 2202 on (2) 2203 } 2204 MAX-ACCESS read-write 2205 STATUS current 2206 DESCRIPTION 2207 "Enables activation and deactivation of 10 MHz reference 2208 clock in the Tx IFL cable: 2209 (1) off 2210 (2) on" 2211 DEFVAL {2} 2212 ::={rcstControl 5} 2214 ctrlOduTxDCEnable OBJECT-TYPE 2215 SYNTAX INTEGER { 2216 off (1), 2217 on (2) 2218 } 2219 MAX-ACCESS read-write 2220 STATUS current 2221 DESCRIPTION 2222 "Enables activation and deactivation of DC in the Tx IFL 2223 cable: 2224 (1) off 2225 (2) on" 2226 DEFVAL {2} 2227 ::={rcstControl 6} 2229 ctrlOduRxDCEnable OBJECT-TYPE 2230 SYNTAX INTEGER { 2231 off (1), 2232 on (2) 2233 } 2234 MAX-ACCESS read-write 2235 STATUS current 2236 DESCRIPTION 2237 "Enables activation and deactivation of DC in the Rx IFL 2238 cable: 2239 (1) off 2240 (2) on" 2241 DEFVAL {2} 2242 ::={rcstControl 7} 2244 ctrlDownloadFileCommand OBJECT-TYPE 2245 SYNTAX INTEGER { 2246 idle (1), 2247 config (2), 2248 installationLog (3) 2249 } 2250 MAX-ACCESS read-write 2251 STATUS current 2252 DESCRIPTION 2253 "This variable will initiate a RCST configuration file 2254 download process 2255 (1) idle 2256 (2) download RCST configuration file from TFTP/FTP server 2257 (3) download RCST installation log file from TFTP/FTP server 2258 (INSTALL_LOG Option)" 2259 DEFVAL {1} 2260 ::={rcstControl 8} 2262 ctrlUploadFileCommand OBJECT-TYPE 2263 SYNTAX INTEGER { 2264 idle (1), 2265 config (2), 2266 eventAlarm (3), 2267 installationLog (4) 2268 } 2269 MAX-ACCESS read-write 2270 STATUS current 2271 DESCRIPTION 2272 "This variable will initiate a RCST upload process 2273 (1) idle 2274 (2) upload RCST configuration file to TFTP/FTP server 2275 (3) upload RCST event/alarm log file to TFTP/FTP server 2276 (4) upload RCST installation log file to TFTP/FTP server 2277 (INSTALL_LOG Option)" 2278 DEFVAL {1} 2279 ::={rcstControl 9} 2281 ctrlActivateConfigFileCommand OBJECT-TYPE 2282 SYNTAX INTEGER { 2283 idle (1), 2284 activate (2) 2285 } 2286 MAX-ACCESS read-write 2287 STATUS current 2288 DESCRIPTION 2289 "Triggers the RCST to use the configuration file and update 2290 its parameters accordingly. Some RCST implementations may 2291 require a reboot for the parameters to take effect (vendor 2292 specific). 2293 (1) Idle 2294 (2) activate" 2295 DEFVAL {1} 2296 ::={rcstControl 10} 2297 ctrlRcstLogonCommand OBJECT-TYPE 2298 SYNTAX INTEGER { 2299 idle (1), 2300 logon (2) 2301 } 2302 MAX-ACCESS read-write 2303 STATUS current 2304 DESCRIPTION 2305 "This variable will initiate a RCST logon 2306 (1) idle 2307 (2) initiate RCST logon" 2308 DEFVAL {1} 2309 ::={rcstControl 11} 2311 ctrlRcstLogoffCommand OBJECT-TYPE 2312 SYNTAX INTEGER { 2313 idle (1), 2314 logoff (2) 2315 } 2316 MAX-ACCESS read-write 2317 STATUS current 2318 DESCRIPTION 2319 "This variable will initiate a RCST logoff 2320 (1) idle 2321 (2) initiate RCST logoff" 2322 DEFVAL {1} 2323 ::={rcstControl 12} 2325 --=================================================================== 2326 -- rcstState sub-tree object types 2327 --=================================================================== 2328 rcstMode OBJECT-TYPE 2329 SYNTAX INTEGER { 2330 installation (0), 2331 operational (1) 2332 } 2333 MAX-ACCESS read-write 2334 STATUS current 2335 DESCRIPTION 2336 "Identifies the current mode of the RCST is and allows it to 2337 return to the installation mode when needed. Values for the 2338 RCST mode are: 2339 Installation (0) 2340 Operational (1)" 2341 ::={rcstState 1} 2343 rcstFaultStatus OBJECT-TYPE 2344 SYNTAX INTEGER { 2345 nofault (0), 2346 fault (1) 2347 } 2348 MAX-ACCESS read-only 2349 STATUS current 2350 DESCRIPTION 2351 "Provide the fault status of the terminal. The fault status 2352 management is vendor specific. Values for the Fault Status 2353 are: 2354 no fault (0) 2355 fault (1)" 2356 ::={rcstState 2} 2358 rcstFwdLinkStatus OBJECT-TYPE 2359 SYNTAX INTEGER { 2360 notAcquired (0), 2361 acquired (1) 2362 } 2363 MAX-ACCESS read-only 2364 STATUS current 2365 DESCRIPTION 2366 "Provides the status of the RCST Forward Link. Values for the 2367 Forward Link Status are: 2368 Not acquired (0) 2369 Acquired (1)" 2370 ::={rcstState 3} 2372 rcstRtnLinkStatus OBJECT-TYPE 2373 SYNTAX INTEGER { 2374 loggedOff (0), 2375 loggedOn (1) 2376 } 2377 MAX-ACCESS read-only 2378 STATUS current 2379 DESCRIPTION 2380 "Provides the status of the RCST Return Link. Values for the 2381 Return Link Status are: 2382 Logged-off (0) 2383 Logged-on (1)" 2384 ::={rcstState 4} 2386 rcstLogUpdated OBJECT-TYPE 2387 SYNTAX INTEGER { 2388 noUpdate (0), 2389 logfileUpdated (1) 2390 } 2391 MAX-ACCESS read-only 2392 STATUS current 2393 DESCRIPTION 2394 "Indicates the existence of an updated event log file: 2395 No update (0) 2396 Event Log file updated (1) 2397 The RCST should remove the Event Log file updated indication 2398 as the log file is fetched by the NCC." 2399 ::={rcstState 5} 2401 rcstCurrentSoftwareVersion OBJECT-TYPE 2402 SYNTAX DisplayString 2403 MAX-ACCESS read-only 2404 STATUS current 2405 DESCRIPTION 2406 "Current RCST software version." 2407 ::={rcstState 6} 2409 rcstAlternateSoftwareVersion OBJECT-TYPE 2410 SYNTAX DisplayString 2411 MAX-ACCESS read-only 2412 STATUS current 2413 DESCRIPTION 2414 "Alternate (backup/new) RCST software version." 2415 ::={rcstState 7} 2417 rcstActivatedConfigFileVersion OBJECT-TYPE 2418 SYNTAX DisplayString 2419 MAX-ACCESS read-only 2420 STATUS current 2421 DESCRIPTION 2422 "Version of the most recently activated configuration file. 2423 The version is vendor specific." 2424 ::={rcstState 8} 2426 rcstDownloadedConfigFileVersion OBJECT-TYPE 2427 SYNTAX DisplayString 2428 MAX-ACCESS read-only 2429 STATUS current 2430 DESCRIPTION 2431 "Version of the most recently downloaded configuration file. 2432 Version is vendor specific. If the value is different from 2433 rcstActivatedConfigFileVersion, it is pending for activation." 2434 ::={rcstState 9} 2436 --=================================================================== 2437 -- fwdConfig sub-tree object types 2438 --=================================================================== 2439 fwdStartTable OBJECT-TYPE 2440 SYNTAX SEQUENCE OF FwdStartEntry 2441 MAX-ACCESS not-accessible 2442 STATUS current 2443 DESCRIPTION 2444 "Lists Forward Links attachment points (e.g. different for 2445 installation and operation). 2446 The table describes the forward link parameters used for the 2447 start-up stream with the NCC." 2448 ::={fwdConfig 1} 2450 fwdStartEntry OBJECT-TYPE 2451 SYNTAX FwdStartEntry 2452 MAX-ACCESS not-accessible 2453 STATUS current 2454 DESCRIPTION 2455 "An entry in the Forward Link StartConfig table." 2456 INDEX { fwdStartIndex } 2457 ::= { fwdStartTable 1 } 2459 FwdStartEntry ::= SEQUENCE { 2460 fwdStartIndex Integer32, 2461 fwdStartPopId Integer32, 2462 fwdStartFrequency Integer32, 2463 fwdStartPolar INTEGER, 2464 fwdStartFormat INTEGER, 2465 fwdStartRolloff INTEGER, 2466 fwdStartSymbolRate Integer32, 2467 fwdStartInnerFec INTEGER, 2468 fwdStartRowStatus RowStatus 2469 } 2471 fwdStartIndex OBJECT-TYPE 2472 SYNTAX Integer32 (1..8) 2473 MAX-ACCESS not-accessible 2474 STATUS current 2475 DESCRIPTION 2476 "Index of the Forward Link StartConfig table." 2477 ::={fwdStartEntry 1} 2479 fwdStartPopId OBJECT-TYPE 2480 SYNTAX Integer32 (-1..65535) 2481 MAX-ACCESS read-create 2482 STATUS current 2483 DESCRIPTION 2484 "Population identifier associated with the start-up 2485 forward link: 2486 -1: any (auto) 2487 0-65535: specific StartPopId 2488 If 'any' is set, the RCST will assume membership of any 2489 announced population ID and will commence with logon in 2490 accordance with this assumption." 2491 ::={fwdStartEntry 2} 2493 fwdStartFrequency OBJECT-TYPE 2494 SYNTAX Integer32 2495 UNITS "x100 kHz" 2496 MAX-ACCESS read-create 2497 STATUS current 2498 DESCRIPTION 2499 "Frequency of the start transponder carrying a 2500 Network Information Table to which any RCST shall 2501 trigger to acquire forward link. Its value shall be given 2502 in multiple of 100 kHz." 2503 ::={fwdStartEntry 3} 2505 fwdStartPolar OBJECT-TYPE 2506 SYNTAX INTEGER { 2507 linearHorizontal (0), 2508 linearVertical (1), 2509 circularLeft (2), 2510 circularRight (3) 2511 } 2512 MAX-ACCESS read-create 2513 STATUS current 2514 DESCRIPTION 2515 "2-bit field giving the polarization of the start 2516 transponder carrying an Network Information Table 2517 to which any RCST shall trigger to acquire forward link: 2518 00: linear and horizontal 2519 01: linear and vertical 2520 10: circular left 2521 11: circular right" 2522 ::={fwdStartEntry 4} 2524 fwdStartFormat OBJECT-TYPE 2525 SYNTAX INTEGER { 2526 auto (-1), 2527 dvbs (0), 2528 dvbs2ccm (1), 2529 dvbs2acm (2) 2530 } 2531 MAX-ACCESS read-create 2532 STATUS current 2533 DESCRIPTION 2534 "Specifies the transmission format standard applied for the 2535 startup stream. The start transport stream carries a Network 2536 Information Table that the RCST uses for acquiring the 2537 forward link signaling. Supported values are: 2538 -1: unspecified (automatic format acquisition is 2539 assumed) 2540 0: DVB-S (support of this value is mandatory if DVB-S 2541 support is claimed) 2542 1: DVB-S2 with CCM (support of this value is mandatory 2543 if DVB-S2 CCM support is claimed) 2544 2: DVB-S2 with VCM or ACM (support of this value is 2545 mandatory if DVB-S2 ACM support is claimed) 2546 This allows the RCST to discriminate between CCM and VCM/ACM 2547 when selecting FL. 2548 The support of automatic format selection is optional. One 2549 Or several of the other format selections must be supported, 2550 according to the claimed SatLabs profile support." 2551 ::={fwdStartEntry 5} 2553 fwdStartRolloff OBJECT-TYPE 2554 SYNTAX INTEGER { 2555 autoRolloff (0), 2556 rolloff020 (1), 2557 rolloff025 (2), 2558 rolloff035 (3) 2559 } 2560 MAX-ACCESS read-create 2561 STATUS current 2562 DESCRIPTION 2563 "Specifies the receive filter roll-off applied on the start 2564 transponder. The start transponder carries a Network 2565 Information Table that the RCST uses for acquiring the 2566 forward link signaling. 2567 Supported values are: 2568 0: any (auto) 2569 1: 0.20 2570 2: 0.25 2571 3: 0.35" 2572 ::={fwdStartEntry 6} 2574 fwdStartSymbolRate OBJECT-TYPE 2575 SYNTAX Integer32 2576 UNITS "x100 symbols/s" 2577 MAX-ACCESS read-create 2578 STATUS current 2579 DESCRIPTION 2580 "Specifies the symbol rate on the start transponder 2581 carrying a Network Information Table to which any RCST 2582 shall trigger to acquire forward link. Its value shall be 2583 given in multiple of 100 symbols/s." 2584 ::={fwdStartEntry 7} 2586 fwdStartInnerFec OBJECT-TYPE 2587 SYNTAX INTEGER { 2588 autoFec (-1), 2589 fecRate12 (0), 2590 fecRate23 (1), 2591 fecRate34 (2), 2592 fecRate56 (3), 2593 fecRate78 (4), 2594 fecRate89 (5), 2595 fecRate35 (6), 2596 fecRate45 (7), 2597 fecRate910 (8), 2598 fecRate25 (9), 2599 fecRate13 (10), 2600 fecRate14 (11), 2601 noInnerCode (12) } 2602 MAX-ACCESS read-create 2603 STATUS current 2604 DESCRIPTION 2605 "Specifies the inner Forward Error Correction used on the 2606 start transponder carrying a Network Information Table 2607 to which any RCST shall trigger to acquire forward link. 2608 Supported values are: 2609 autoFec (-1), 2610 fecRate1/2 (0), 2611 fecRate2/3 (1), 2612 fecRate3/4 (2), 2613 fecRate5/6 (3), 2614 fecRate7/8 (4), 2615 fecRate8/9 (5), 2616 fecRate3/5 (6), 2617 fecRate4/5 (7), 2618 fecRate9/10 (8), 2619 fecRate2/5 (9), 2620 fecRate1/3 (10), 2621 fecRate1/4 (11), 2622 noInnerCode (12) 2623 The support of autoFec is optional." 2624 ::={fwdStartEntry 8} 2626 fwdStartRowStatus OBJECT-TYPE 2627 SYNTAX RowStatus 2628 MAX-ACCESS read-create 2629 STATUS current 2630 DESCRIPTION 2631 "Standard SNMP row status" 2632 DEFVAL { active } 2633 ::={fwdStartEntry 9} 2635 --=================================================================== 2636 -- fwdStatus sub-tree object types 2637 --=================================================================== 2638 fwdStatusPopId OBJECT-TYPE 2639 SYNTAX Integer32 (0..65535) 2640 MAX-ACCESS read-only 2641 STATUS current 2642 DESCRIPTION 2643 "Population identifier applied at log-on: 2644 0-65535: specific StartPopId 2645 If the RCST was allowed to logon with any population, the 2646 RCST will report the base number of the announced 2647 population ID indicated by the RCS Map Table linkage 2648 descriptor used at logon." 2649 ::={fwdStatus 1} 2651 fwdStatusTable OBJECT-TYPE 2652 SYNTAX SEQUENCE OF FwdStatusEntry 2653 MAX-ACCESS not-accessible 2654 STATUS current 2655 DESCRIPTION 2656 "This table describes the current status of Forward Link 2657 interfaces." 2658 ::={fwdStatus 2} 2660 fwdStatusEntry OBJECT-TYPE 2661 SYNTAX FwdStatusEntry 2662 MAX-ACCESS not-accessible 2663 STATUS current 2664 DESCRIPTION 2665 "An entry in the Forward Link Status table. Each entry is 2666 associated with a physical interface. 2667 A RCST shall support at least one entry." 2668 INDEX { fwdStatusIndex } 2669 ::= { fwdStatusTable 1 } 2671 FwdStatusEntry ::= SEQUENCE { 2672 fwdStatusIndex Integer32, 2673 fwdStatusIfReference Integer32, 2674 fwdStatusNetId Integer32, 2675 fwdStatusNetName DisplayString, 2676 fwdStatusFormat INTEGER, 2677 fwdStatusFrequency Integer32, 2678 fwdStatusPolar INTEGER, 2679 fwdStatusInnerFec INTEGER, 2680 fwdStatusSymbolRate Integer32, 2681 fwdStatusRolloff INTEGER, 2682 fwdStatusModulation INTEGER, 2683 fwdStatusFecFrame INTEGER, 2684 fwdStatusPilot INTEGER, 2685 fwdStatusBer Integer32, 2686 fwdStatusCnr Integer32, 2687 fwdStatusRxPower Integer32 2688 } 2690 fwdStatusIndex OBJECT-TYPE 2691 SYNTAX Integer32 (1..8) 2692 MAX-ACCESS not-accessible 2693 STATUS current 2694 DESCRIPTION 2695 "Index of the Forward Link Status table." 2696 ::={fwdStatusEntry 1} 2698 fwdStatusIfReference OBJECT-TYPE 2699 SYNTAX Integer32 (1..8) 2700 MAX-ACCESS read-only 2701 STATUS current 2702 DESCRIPTION 2703 "Cross reference to the interface table" 2705 ::={fwdStatusEntry 2} 2707 fwdStatusNetId OBJECT-TYPE 2708 SYNTAX Integer32 2709 MAX-ACCESS read-only 2710 STATUS current 2711 DESCRIPTION 2712 "Interactive network identifier of the forward 2713 link (from RCS Map Table)" 2714 ::={fwdStatusEntry 3} 2716 fwdStatusNetName OBJECT-TYPE 2717 SYNTAX DisplayString 2718 MAX-ACCESS read-only 2719 STATUS current 2720 DESCRIPTION 2721 "The name of the interactive network of the forward 2722 link (from RCS Map Table)" 2723 ::={fwdStatusEntry 4} 2725 fwdStatusFormat OBJECT-TYPE 2726 SYNTAX INTEGER { 2727 dvbs (0), 2728 dvbs2ccm (1), 2729 dvbs2acm (2), 2730 reservedFormat (3) 2731 } 2732 MAX-ACCESS read-only 2733 STATUS current 2734 DESCRIPTION 2735 "Specifies the transmission format applied on the forward 2736 link. Supported values are (from RMT): 2737 0: DVB-S 2738 1: DVB-S2 using CCM 2739 2: DVB-S2 using VCM or ACM 2740 3: reserved" 2741 ::={fwdStatusEntry 5} 2743 fwdStatusFrequency OBJECT-TYPE 2744 SYNTAX Integer32 2745 UNITS "x100 kHz" 2746 MAX-ACCESS read-only 2747 STATUS current 2748 DESCRIPTION 2749 "An estimate of the frequency of the forward link. Its value 2750 shall be given in multiple of 100 kHz." 2751 ::={fwdStatusEntry 6} 2753 fwdStatusPolar OBJECT-TYPE 2754 SYNTAX INTEGER { 2755 linearHorizontal (0), 2756 linearVertical (1), 2757 circularLeft (2), 2758 circularRight (3) 2759 } 2760 MAX-ACCESS read-only 2761 STATUS current 2762 DESCRIPTION 2763 "2-bit field giving the polarization of the forward link 2764 (from RMT): 2765 00: linear and horizontal 2766 01: linear and vertical 2767 10: circular left 2768 11: circular right" 2769 ::={fwdStatusEntry 7} 2771 fwdStatusInnerFec OBJECT-TYPE 2772 SYNTAX INTEGER { 2773 unknown (-1), 2774 fecRate12 (0), 2775 fecRate23 (1), 2776 fecRate34 (2), 2777 fecRate56 (3), 2778 fecRate78 (4), 2779 fecRate89 (5), 2780 fecRate35 (6), 2781 fecRate45 (7), 2782 fecRate910 (8), 2783 fecRate25 (9), 2784 fecRate13 (10), 2785 fecRate14 (11), 2786 noInnerCode (12) 2788 } 2789 MAX-ACCESS read-only 2790 STATUS current 2791 DESCRIPTION 2792 "Specifies the inner Forward Error Correction used on the 2793 forward link for transmission to the RCST. 2794 Supported values are: 2795 unknown (-1), 2796 fecRate1/2 (0), 2797 fecRate2/3 (1), 2798 fecRate3/4 (2), 2799 fecRate5/6 (3), 2800 fecRate7/8 (4), 2801 fecRate8/9 (5), 2802 fecRate3/5 (6), 2803 fecRate4/5 (7), 2804 fecRate9/10 (8), 2805 fecRate2/5 (9), 2806 fecRate1/3 (10), 2807 fecRate1/4 (11), 2808 noInnerCode (12) 2809 The RCST will report a value that has been used for transmission 2810 to the RCST within the most recent 60 seconds. 2811 If this is not relevant, the RCST will report 'unknown'." 2812 ::={fwdStatusEntry 8} 2814 fwdStatusSymbolRate OBJECT-TYPE 2815 SYNTAX Integer32 2816 UNITS "x100 symbols/s" 2817 MAX-ACCESS read-only 2818 STATUS current 2819 DESCRIPTION 2820 "An estimate of the symbol rate of the forward link. 2821 Its value shall be given in multiple of 100 symbol/s." 2822 ::={fwdStatusEntry 9} 2824 fwdStatusRolloff OBJECT-TYPE 2825 SYNTAX INTEGER { 2826 undefRolloff (0), 2827 rolloff020 (1), 2828 rolloff025 (2), 2829 rolloff035 (3) 2830 } 2831 MAX-ACCESS read-only 2832 STATUS current 2833 DESCRIPTION 2834 "An estimate of the roll-off applied on the forward link. 2835 Supported values are: 2836 0: undefined 2837 1: 0.20 2838 2: 0.25 2839 3: 0.35" 2840 ::={fwdStatusEntry 10} 2842 fwdStatusModulation OBJECT-TYPE 2843 SYNTAX INTEGER { 2844 unknown (0), 2845 mBPSK (1), 2846 mQPSK (2), 2847 m8PSK (3), 2848 m16APSK (4), 2849 m32APSK (5) 2850 } 2851 MAX-ACCESS read-only 2852 STATUS current 2853 DESCRIPTION 2854 "Indicates the modulation on the forward link used for 2855 transmission to the RCST. 2856 0: unknown 2857 1: BPSK 2858 2: QPSK 2859 3: 8PSK 2860 4: 16APSK 2861 5: 32APSK 2862 The RCST will report a value that has been used for 2863 transmission to the RCST within the most recent 60 seconds. 2864 If this is not relevant, the RCST will report 'unknown'." 2865 ::={fwdStatusEntry 11} 2867 fwdStatusFecFrame OBJECT-TYPE 2868 SYNTAX INTEGER { 2869 unknown (0), 2870 shortframe (1), 2871 longframe (2) 2872 } 2873 MAX-ACCESS read-only 2874 STATUS current 2875 DESCRIPTION 2876 "Indicates the frame length used on the forward link for 2877 transmission to the RCST. 2878 Supported values are: 2879 0: Unknown 2880 1: Short frame 2881 2: Normal frame 2882 The RCST will report a value that has been used for 2883 transmission to the RCST within the most recent 60 seconds. 2884 If this is not relevant, the RCST will report 'unknown'." 2885 ::={fwdStatusEntry 12} 2887 fwdStatusPilot OBJECT-TYPE 2888 SYNTAX INTEGER { 2889 unknown (0), 2890 pilotNotused (1), 2891 pilotUsed (2) 2892 } 2893 MAX-ACCESS read-only 2894 STATUS current 2895 DESCRIPTION 2896 "Indicates whether pilots are used on the forward link for 2897 transmission to the RCST. 2898 Supported values are: 2899 0: Unknown 2900 1: Pilots are not used 2901 2: Pilots are used 2902 The RCST will report a value that has been used for 2903 transmission to the RCST within the most recent 60 seconds. 2904 If this is not relevant, the RCST will report 'unknown'." 2905 ::={fwdStatusEntry 13} 2907 fwdStatusBer OBJECT-TYPE 2908 SYNTAX Integer32 2909 UNITS "exponent of 10" 2910 MAX-ACCESS read-only 2911 STATUS current 2912 DESCRIPTION 2913 "Provides the RCST BER on the Forward Link in log10 units." 2914 ::={fwdStatusEntry 14} 2916 fwdStatusCnr OBJECT-TYPE 2917 SYNTAX Integer32 2918 UNITS "0.1 dB" 2919 MAX-ACCESS read-only 2920 STATUS current 2921 DESCRIPTION 2922 "Provides the RCST CNR on the Forward Link in 0.1 dB units." 2923 ::={fwdStatusEntry 15} 2925 fwdStatusRxPower OBJECT-TYPE 2926 SYNTAX Integer32 2927 UNITS "0.1 dBm" 2928 MAX-ACCESS read-only 2929 STATUS current 2930 DESCRIPTION 2931 "Provides the power level of the Forward Link as received at 2932 the IDU, in 0.1 dBm units." 2933 DEFVAL { -500 } 2934 ::={fwdStatusEntry 16} 2936 --=================================================================== 2937 -- rtnConfig sub-tree object types 2938 --=================================================================== 2939 rtnConfigMaxEirp OBJECT-TYPE 2940 SYNTAX Integer32 2941 UNITS "x0.1 dBm" 2942 MAX-ACCESS read-write 2943 STATUS current 2944 DESCRIPTION 2945 "Max EIRP of the RCST given in resolution of 0.1 dBm, 2946 applied when the IDU can itself set the necessary IDU TX 2947 output level e.g. when using a BUC that has a power level 2948 detector and provides sufficient feedback to the IDU." 2949 ::= {rtnConfig 1} 2950 rtnConfigDefIfLevel OBJECT-TYPE 2951 SYNTAX Integer32 2952 UNITS "x0.1 dBm" 2953 MAX-ACCESS read-write 2954 STATUS current 2955 DESCRIPTION 2956 "IDU TX output level applied in case the rtnConfigMaxEirp 2957 cannot be used. The resolution is 0.1 dBm and the accuracy 2958 is +/- 1 dBm." 2959 ::= {rtnConfig 2} 2961 --=================================================================== 2962 -- rtnStatus sub-tree object types 2963 --=================================================================== 2964 rtnStatusEbN0 OBJECT-TYPE 2965 SYNTAX Integer32 2966 UNITS "x0.1 dB" 2967 MAX-ACCESS read-only 2968 STATUS current 2969 DESCRIPTION 2970 "The EbN0 value reported for the return link, referenced to 2971 the regular SYNC burst transmission, in 0.1 dB units." 2972 ::= {rtnStatus 1} 2974 rtnStatusSFDuration OBJECT-TYPE 2975 SYNTAX Integer32 (250..7500) 2976 UNITS "0.1 ms" 2977 MAX-ACCESS read-only 2978 STATUS current 2979 DESCRIPTION 2980 "The duration of the currently applied return link super- 2981 frame structure, in tenths of milliseconds." 2982 ::= {rtnStatus 2} 2984 rtnStatusPayloadUnit OBJECT-TYPE 2985 SYNTAX INTEGER { 2986 unitATM (0), 2987 unitMPEG (1) 2988 } 2989 MAX-ACCESS read-only 2990 STATUS current 2991 DESCRIPTION 2992 "Indicates if the payload unit used for the return link is 2993 ATM or MPEG." 2994 ::= {rtnStatus 3} 2996 --================================================================== 2997 -- conformance information 2998 --================================================================== 2999 rcstGroups OBJECT IDENTIFIER ::= {dvbrcsConformance 1} 3000 rcstCompliances OBJECT IDENTIFIER ::= {dvbrcsConformance 2} 3002 --================================================================== 3003 -- conformance statements 3004 --================================================================== 3005 rcstCompliance1 MODULE-COMPLIANCE 3006 STATUS current 3007 DESCRIPTION 3008 "The compliance statement for DVB-RCS terminals that are 3009 compliant with SatLabs System Recommendations. " 3011 MODULE -- this module 3013 MANDATORY-GROUPS {rcstSystemGroup, rcstNetworkGroup, 3014 rcstInstallGroup, rcstQosGroup, rcstControlGroup, rcstStateGroup, 3015 fwdConfigGroup, fwdStatusGroup, rtnConfigGroup, rtnStatusGroup} 3017 GROUP rcstExtSystemGroup 3018 DESCRIPTION "This group is mandatory for an RCST 3019 that claims to support the SNMPMISC option." 3021 GROUP rcstExtNetworkGroup 3022 DESCRIPTION "This group is mandatory for an RCST 3023 that claims to support the SNMPMISC option." 3025 GROUP rcstDnsGroup 3026 DESCRIPTION "This group is mandatory for an RCST 3027 that claims to support the DNS option." 3029 GROUP rcstExtInstallGroup 3030 DESCRIPTION "This group is mandatory for an RCST 3031 that claims to support the INSTALL_LOG feature." 3032 GROUP rcstEnhancedClassifierGroup 3033 DESCRIPTION "This group is mandatory for an RCST 3034 that claims to support the ENHCLASSIFIER feature." 3036 GROUP rcstMpegQosGroup 3037 DESCRIPTION "This group is mandatory for an RCST 3038 that claims to support the MPEG_TRF option." 3040 GROUP rcstGlobalQosGroup 3041 DESCRIPTION "This group is mandatory for an RCST 3042 that claims to support the RCST_PARA feature." 3044 GROUP rcstStrictQosGroup 3045 DESCRIPTION "This group is mandatory for an RCST 3046 that claims to support the CHID_STRICT option." 3048 GROUP rcstExtControlGroup 3049 DESCRIPTION "This group is mandatory for an RCST 3050 that claims to support the SNMPMISC option." 3052 GROUP rtnExtConfigGroup 3053 DESCRIPTION "This group is mandatory for an RCST 3054 that claims to support the SNMPMISC option." 3056 GROUP rtnExtStatusGroup 3057 DESCRIPTION "This group is mandatory for an RCST 3058 that claims to support the SNMPMISC option." 3060 OBJECT systemOduAntennaGain 3061 MIN-ACCESS read-only 3062 DESCRIPTION "Write access only required if SNMPMISC 3063 support is claimed." 3065 OBJECT systemOduTxType 3066 MIN-ACCESS read-only 3067 DESCRIPTION "Write access required if the RCST does 3068 not provide the information." 3070 OBJECT systemOduRxType 3071 MIN-ACCESS read-only 3072 DESCRIPTION "Write access required if the RCST does 3073 not provide the information." 3075 OBJECT systemOduRxBand 3076 MIN-ACCESS read-only 3077 DESCRIPTION "Write access only required if SNMPMISC 3078 support is claimed." 3080 OBJECT systemOduRxLO 3081 MIN-ACCESS read-only 3082 DESCRIPTION "Write access only required if SNMPMISC 3083 support is claimed." 3085 OBJECT systemOduTxLO 3086 MIN-ACCESS read-only 3087 DESCRIPTION "Write access only required if SNMPMISC 3088 support is claimed." 3090 OBJECT pktClassDscpLow 3091 MIN-ACCESS read-only 3092 DESCRIPTION "Create access only required if 3093 ENHCLASSIFIER support is claimed." 3095 OBJECT pktClassDscpHigh 3096 MIN-ACCESS read-only 3097 DESCRIPTION "Create access only required if 3098 ENHCLASSIFIER support is claimed." 3100 OBJECT pktClassDscpMarkValue 3101 MIN-ACCESS read-only 3102 DESCRIPTION "Create access only required if 3103 ENHCLASSIFIER support is claimed." 3105 OBJECT phbName 3106 MIN-ACCESS read-only 3107 DESCRIPTION "Create access only required if SNMPMISC 3108 support is claimed." 3110 OBJECT phbRequestClassAssociation 3111 MIN-ACCESS read-only 3112 DESCRIPTION "Create access only required if SNMPMISC 3113 support is claimed." 3115 OBJECT phbMappingRowStatus 3116 MIN-ACCESS read-only 3117 DESCRIPTION "Create access only required if SNMPMISC 3118 support is claimed." 3120 OBJECT requestClassName 3121 MIN-ACCESS read-only 3122 DESCRIPTION "Write access only required if SNMPMISC 3123 support is claimed." 3125 OBJECT requestClassChanId 3126 MIN-ACCESS read-only 3127 DESCRIPTION "Write access only required if SNMPMISC 3128 support is claimed." 3130 OBJECT requestClassVccVpi 3131 MIN-ACCESS read-only 3132 DESCRIPTION "Write access only required if SNMPMISC 3133 support is claimed." 3135 OBJECT requestClassVccVci 3136 MIN-ACCESS read-only 3137 DESCRIPTION "Write access only required if SNMPMISC 3138 support is claimed." 3140 OBJECT requestClassPidPoolReference 3141 MIN-ACCESS not-accessible 3142 DESCRIPTION "Read-only access required if MPEG option 3143 is claimed. Write access only required if also SNMPMISC 3144 support is claimed." 3146 OBJECT requestClassCra 3147 MIN-ACCESS read-only 3148 DESCRIPTION "Write access only required if SNMPMISC 3149 support is claimed." 3151 OBJECT requestClassRbdcMax 3152 MIN-ACCESS read-only 3153 DESCRIPTION "Write access only required if SNMPMISC 3154 support is claimed." 3156 OBJECT requestClassRbdcTimeout 3157 MIN-ACCESS read-only 3158 DESCRIPTION "Write access only required if SNMPMISC 3159 support is claimed." 3161 OBJECT requestClassVbdcMax 3162 MIN-ACCESS read-only 3163 DESCRIPTION "Write access only required if SNMPMISC 3164 support is claimed." 3166 OBJECT requestClassVbdcTimeout 3167 MIN-ACCESS read-only 3168 DESCRIPTION "Write access only required if SNMPMISC 3169 support is claimed." 3171 OBJECT requestClassVbdcMaxBackLog 3172 MIN-ACCESS read-only 3173 DESCRIPTION "Write access only required if SNMPMISC 3174 support is claimed." 3176 OBJECT requestClassRowStatus 3177 MIN-ACCESS read-only 3178 DESCRIPTION "Write access only required if SNMPMISC 3179 support is claimed." 3181 OBJECT pidValue 3182 MIN-ACCESS not-accessible 3183 DESCRIPTION "Read-only access required if MPEG option 3184 is claimed. Write access only required if also SNMPMISC 3185 support is claimed." 3187 OBJECT pidPoolRowStatus 3188 MIN-ACCESS not-accessible 3189 DESCRIPTION "Read-only access required if MPEG option 3190 is claimed. Write access only required if also SNMPMISC 3191 support is claimed." 3193 ::= { rcstCompliances 1 } 3194 --================================================================== 3195 -- units of conformance 3196 --================================================================== 3198 --================================================================== 3199 -- object groups for rcst system 3200 --================================================================== 3201 rcstSystemGroup OBJECT-GROUP 3202 OBJECTS { 3203 systemMibRevision, 3204 systemSatLabsProfilesDeclaration, 3205 systemSatLabsOptionsDeclaration, 3206 systemSatLabsFeaturesDeclaration, 3207 systemLocation, 3208 systemOduAntennaGain, 3209 systemOduTxType, 3210 systemOduRxType, 3211 systemOduRxBand, 3212 systemOduRxLO, 3213 systemOduTxLO, 3214 tcpPep, 3215 httpPep 3216 } 3217 STATUS current 3218 DESCRIPTION "A collection of objects providing information 3219 applicable for basic device management support." 3220 ::= { rcstGroups 1 } 3222 rcstExtSystemGroup OBJECT-GROUP 3223 OBJECTS { 3224 systemOduAntennaSize, 3225 systemOduSspa 3226 } 3227 STATUS current 3228 DESCRIPTION "A collection of objects providing information 3229 applicable for extended device management support." 3230 ::= { rcstGroups 2 } 3231 --================================================================== 3232 -- object groups for rcst networking 3233 --================================================================== 3234 rcstNetworkGroup OBJECT-GROUP 3235 OBJECTS { 3236 networkOamIpAddress, 3237 networkOamIpNetworkMask, 3238 networkLanIpAddress, 3239 networkLanIpNetworkMask, 3240 networkConfigFileDownloadUrl, 3241 networkConfigFileUploadUrl, 3242 networkLogFileUploadUrl 3243 } 3244 STATUS current 3245 DESCRIPTION "A collection of objects providing basic 3246 networking management support." 3247 ::= { rcstGroups 3 } 3249 rcstExtNetworkGroup OBJECT-GROUP 3250 OBJECTS { 3251 networkOamIpAddressAssign, 3252 networkAirInterfaceDefaultGateway, 3253 networkNccMgtIpAddress 3254 } 3255 STATUS current 3256 DESCRIPTION "A collection of objects providing extended 3257 networking management support." 3258 ::= { rcstGroups 4 } 3260 rcstDnsGroup OBJECT-GROUP 3261 OBJECTS { 3262 primaryDnsServerIpAddress, 3263 secondaryDnsServerIpAddress 3264 } 3265 STATUS current 3266 DESCRIPTION "IP addresses of the primary and secondary DNS 3267 servers to be used to resolve URL's as needed." 3268 ::= { rcstGroups 5 } 3270 --================================================================== 3271 -- object groups for rcst installation 3272 --================================================================== 3274 rcstInstallGroup OBJECT-GROUP 3275 OBJECTS { 3276 installAntennaAlignmentState, 3277 installCwFrequency, 3278 installCwMaxDuration, 3279 installCwPower, 3280 installCoPolReading, 3281 installXPolReading, 3282 installCoPolTarget, 3283 installXPolTarget, 3284 installStandByDuration, 3285 installTargetEsN0 3286 } 3287 STATUS current 3288 DESCRIPTION "A collection of objects providing information 3289 applicable for basic installation support." 3290 ::= { rcstGroups 6 } 3292 rcstExtInstallGroup OBJECT-GROUP 3293 OBJECTS { 3294 networkInstallLogFileDownloadUrl, 3295 networkInstallLogFileUploadUrl 3296 } 3297 STATUS current 3298 DESCRIPTION "A collection of objects providing extended 3299 device installation support." 3300 ::= { rcstGroups 7 } 3302 --================================================================== 3303 -- object groups for QOS 3304 --================================================================== 3306 rcstQosGroup OBJECT-GROUP 3307 OBJECTS { 3308 pktClassDscpLow, 3309 pktClassDscpHigh, 3310 pktClassDscpMarkValue, 3311 pktClassPhbAssociation, 3312 pktClassRowStatus, 3313 phbName, 3314 phbRequestClassAssociation, 3315 phbMappingRowStatus, 3316 requestClassName, 3317 requestClassChanId, 3318 requestClassVccVpi, 3319 requestClassVccVci, 3320 requestClassCra, 3321 requestClassRbdcMax, 3322 requestClassRbdcTimeout, 3323 requestClassVbdcMax, 3324 requestClassVbdcTimeout, 3325 requestClassVbdcMaxBackLog, 3326 requestClassRowStatus 3327 } 3328 STATUS current 3329 DESCRIPTION "A collection of objects providing basic access to 3330 QOS configuration data." 3331 ::= { rcstGroups 8 } 3333 rcstEnhancedClassifierGroup OBJECT-GROUP 3334 OBJECTS { 3335 pktClassIpProtocol, 3336 pktClassIpSrcAddress, 3337 pktClassIpSrcAddressMask, 3338 pktClassIpDstAddress, 3339 pktClassIpDstAddressMask, 3340 pktClassSrcPortLow, 3341 pktClassSrcPortHigh, 3342 pktClassDstPortLow, 3343 pktClassDstPortHigh, 3344 pktClassVlanUserPri 3345 } 3346 STATUS current 3347 DESCRIPTION "A collection of objects providing support for 3348 management of the enhanced classifier." 3349 ::= { rcstGroups 9 } 3350 rcstMpegQosGroup OBJECT-GROUP 3351 OBJECTS { 3352 requestClassPidPoolReference, 3353 pidValue, 3354 pidPoolRowStatus 3355 } 3356 STATUS current 3357 DESCRIPTION "A collection of objects providing access to MPEG 3358 related link QOS configuration data." 3359 ::= { rcstGroups 10 } 3361 rcstGlobalQosGroup OBJECT-GROUP 3362 OBJECTS { 3363 qosGlobalRbdcMax, 3364 qosGlobalVbdcMax, 3365 qosGlobalVbdcMaxBackLog 3366 } 3367 STATUS current 3368 DESCRIPTION "A collection of objects providing access to 3369 global RCST QOS configuration data." 3370 ::= { rcstGroups 11 } 3372 rcstStrictQosGroup OBJECT-GROUP 3373 OBJECTS { 3374 qosChannelIdStrictDispatching 3375 } 3376 STATUS current 3377 DESCRIPTION "A collection of objects allowing management of 3378 strict channel ID dispatching." 3379 ::= { rcstGroups 12 } 3381 --================================================================== 3382 -- object groups for rcst control 3383 --================================================================== 3384 rcstControlGroup OBJECT-GROUP 3385 OBJECTS { 3386 ctrlRebootCommand, 3387 ctrlUserTrafficDisable, 3388 ctrlCwEnable, 3389 ctrlDownloadFileCommand, 3390 ctrlUploadFileCommand, 3391 ctrlActivateConfigFileCommand 3392 } 3393 STATUS current 3394 DESCRIPTION "A collection of objects allowing basic RCST 3395 control." 3396 ::= { rcstGroups 13 } 3398 rcstExtControlGroup OBJECT-GROUP 3399 OBJECTS { 3400 ctrlRcstTxDisable, 3401 ctrlOduTxReferenceEnable, 3402 ctrlOduTxDCEnable, 3403 ctrlOduRxDCEnable, 3404 ctrlRcstLogonCommand, 3405 ctrlRcstLogoffCommand 3406 } 3407 STATUS current 3408 DESCRIPTION "A collection of objects allowing extended RCST 3409 control." 3410 ::= { rcstGroups 14 } 3412 --================================================================== 3413 -- object groups for rcst state 3414 --================================================================== 3416 rcstStateGroup OBJECT-GROUP 3417 OBJECTS { 3418 rcstMode, 3419 rcstFaultStatus, 3420 rcstFwdLinkStatus, 3421 rcstLogUpdated, 3422 rcstCurrentSoftwareVersion, 3423 rcstAlternateSoftwareVersion, 3424 rcstActivatedConfigFileVersion, 3425 rcstDownloadedConfigFileVersion 3426 } 3427 STATUS current 3428 DESCRIPTION "A collection of objects allowing access to RCST 3429 state." 3430 ::= { rcstGroups 15 } 3431 --================================================================== 3432 -- object groups for forward link 3433 --================================================================== 3435 fwdConfigGroup OBJECT-GROUP 3436 OBJECTS { 3437 fwdStartPopId, 3438 fwdStartFrequency, 3439 fwdStartPolar, 3440 fwdStartFormat, 3441 fwdStartRolloff, 3442 fwdStartSymbolRate, 3443 fwdStartInnerFec, 3444 fwdStartRowStatus 3445 } 3446 STATUS current 3447 DESCRIPTION "A collection of objects providing basic start 3448 forward link configuration support." 3449 ::= { rcstGroups 16 } 3451 fwdStatusGroup OBJECT-GROUP 3452 OBJECTS { 3453 fwdStatusPopId, 3454 fwdStatusIfReference, 3455 fwdStatusNetId, 3456 fwdStatusNetName, 3457 fwdStatusFormat, 3458 fwdStatusFrequency, 3459 fwdStatusPolar, 3460 fwdStatusInnerFec, 3461 fwdStatusSymbolRate, 3462 fwdStatusRolloff, 3463 fwdStatusModulation, 3464 fwdStatusFecFrame, 3465 fwdStatusPilot, 3466 fwdStatusBer, 3467 fwdStatusCnr, 3468 fwdStatusRxPower 3469 } 3471 STATUS current 3472 DESCRIPTION "A collection of objects providing forward link 3473 status." 3474 ::= { rcstGroups 17 } 3476 --================================================================== 3477 -- object groups for return link 3478 --================================================================== 3480 rtnConfigGroup OBJECT-GROUP 3481 OBJECTS { 3482 rtnConfigDefIfLevel 3483 } 3484 STATUS current 3485 DESCRIPTION "A collection of objects providing basic return 3486 link configuration support." 3487 ::= { rcstGroups 18 } 3489 rtnExtConfigGroup OBJECT-GROUP 3490 OBJECTS { 3491 rtnConfigMaxEirp 3492 } 3493 STATUS current 3494 DESCRIPTION "A collection of objects providing extended 3495 return link configuration support." 3496 ::= { rcstGroups 19 } 3498 rtnStatusGroup OBJECT-GROUP 3499 OBJECTS { 3500 rtnStatusPayloadUnit 3501 } 3502 STATUS current 3503 DESCRIPTION "A collection of objects allowing access to return 3504 link status." 3505 ::= { rcstGroups 20 } 3507 rtnExtStatusGroup OBJECT-GROUP 3508 OBJECTS { 3509 rcstRtnLinkStatus, 3510 rtnStatusEbN0, 3511 rtnStatusSFDuration 3512 } 3513 STATUS current 3514 DESCRIPTION "A collection of objects allowing access to 3515 extended return link status." 3516 ::= { rcstGroups 21 } 3518 END 3520 5. Security Considerations 3522 Some of the readable objects in this MIB module (i.e., objects with a 3523 MAX-ACCESS other than not-accessible) may be considered sensitive or 3524 vulnerable in some network environments. 3526 SNMP versions prior to SNMPv3 did not include adequate security. Even 3527 if the network itself is secure (for example by using IPsec), even 3528 then, there is no control as to who on the secure network is allowed 3529 to access and GET/SET (read/change/create/delete) the objects in this 3530 MIB module. 3532 It is RECOMMENDED that implementers consider the security features 3533 provided by the SNMPv3 framework (see [RFC3410], section 8), 3534 including full support for the SNMPv3 cryptographic mechanisms (for 3535 authentication and privacy). 3537 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3538 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3539 enable cryptographic security. It is then a customer/operator 3540 responsibility to ensure that the SNMP entity giving access to an 3541 instance of this MIB module, is properly configured to give access to 3542 the objects only to those principals (users) that have legitimate 3543 rights to indeed GET or SET (change/create/delete) them. 3545 6. IANA Considerations 3547 This document includes no request to IANA. The transmission and 3548 ifType numbers described in Section 3 have already been assigned 3549 under the smi-numbers registry. 3551 7. Acknowledgments 3553 The authors thank Gorry Fairhurst for advice in the preparation of 3554 this document. 3556 The authors recognize this document is a collective effort of the 3557 SatLabs Group (www.satlabs.org), in particular the many corrections 3558 and suggestions brought by Juan Luis Manas. 3560 8. References 3562 8.1. Normative References 3564 [IANA] Internet Assigned Numbers Authority, "Internet Assigned 3565 Numbers Authority", June 2008, 3566 . 3568 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3569 Requirement Levels", BCP 14, RFC 2119, March 1997 (BEST 3570 CURRENT PRACTICE). 3572 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3573 Schoenwaelder, Ed., "Structure of Management Information, 3574 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3576 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3577 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3578 STD 58, RFC 2579, April 1999. 3580 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3581 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 3582 1999. 3584 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB", 3585 RFC 2863, June 2000. 3587 8.2. Informative References 3589 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 3590 Generic Coding of Moving Pictures and Associated Audio 3591 Information Systems", International Standardisation 3592 Organisation (ISO). 3594 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 3595 Specifications for Data Broadcasting", European 3596 Telecommunications Standards Institute (ETSI). 3598 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); Modulation 3599 and Coding for DBS satellite systems at 11/12 GHz", 3600 European Telecommunications Standards Institute (ETSI). 3602 [ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB); 3603 Second generation framing structure, channel coding and 3604 modulation systems for Broadcasting, Interactive Services, 3605 News Gathering and other broadband satellite applications", 3606 European Telecommunications Standards Institute (ETSI). 3608 [ETSI-GSE] ETSI TS 102 606 "Digital Video Broadcasting (DVB); 3609 Generic Stream Encapsulation (GSE) Protocol", European 3610 Telecommunications Standards Institute (ETSI). 3612 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 3613 Interaction Channel for Satellite Distribution Systems", 3614 European Telecommunications Standards Institute (ETSI). 3616 [ETSI-SI] ETSI EN 300 468 "Digital Video Broadcasting (DVB); 3617 Specification for Service Information (SI) in DVB Systems", 3618 European Telecommunications Standards Institute (ETSI). 3620 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3621 "Introduction and Applicability Statements for Internet- 3622 Standard Management Framework", RFC 3410, December 2002. 3624 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- 3625 Nocker, B., and H. Linder, "A Framework for Transmission of 3626 IP Datagrams over MPEG-2 Networks", RFC 4259, November 3627 2005. 3629 [SATLABS] SatLabs System Recommendations. Available at 3630 www.satlabs.org. 3632 9. Authors' Addresses 3634 Stephane Combes 3635 ESTEC 3636 European Space Agency 3637 Keplerlaan 1 - - P.O. Box 299 3638 2200 AG Noordwijk ZH 3639 The Netherlands 3641 Email: stephane.combes@esa.int 3642 URL: telecom.esa.int 3644 Petter Chr. Amundsen 3645 VeriSat AS 3646 P.O Box 1 3647 1330 Fornebu 3648 Norway 3650 Email: pca@verisat.no 3651 URL: www.verisat.no 3653 Micheline Lambert 3654 Advantech Satellite Networks 3655 2341 boul. Alfred-Nobel 3656 Saint-Laurent (Montreal,)H4S 2A9 3657 Quebec, Canada 3659 Email: micheline.lambert@advantechamt.com 3660 URL: www.advantechsatnet.com 3662 Hans-Peter Lexow 3663 STM Norway 3664 Vollsveien 21 3665 1366 Lysaker 3666 Norway 3668 Email: hlexow@stmi.com 3669 URL: www.stmi.com 3671 10. Intellectual Property Statement 3673 The IETF takes no position regarding the validity or scope of any 3674 Intellectual Property Rights or other rights that might be claimed to 3675 pertain to the implementation or use of the technology described in 3676 this document or the extent to which any license under such rights 3677 might or might not be available; nor does it represent that it has 3678 made any independent effort to identify any such rights. Information 3679 on the procedures with respect to rights in RFC documents can be 3680 found in BCP 78 and BCP 79. 3682 Copies of IPR disclosures made to the IETF Secretariat and any 3683 assurances of licenses to be made available, or the result of an 3684 attempt made to obtain a general license or permission for the use of 3685 such proprietary rights by implementers or users of this 3686 specification can be obtained from the IETF on-line IPR repository at 3687 http://www.ietf.org/ipr. 3689 The IETF invites any interested party to bring to its attention any 3690 copyrights, patents or patent applications, or other proprietary 3691 rights that may cover technology that may be required to implement 3692 this standard. Please address the information to the IETF at 3693 ietf-ipr@ietf.org. 3695 11. Disclaimer of Validity 3697 This document and the information contained herein are provided on an 3698 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3699 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3700 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3701 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3702 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3703 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3705 12. Copyright Statement 3707 Copyright (C) The IETF Trust (2008). 3709 This document is subject to the rights, licenses and restrictions 3710 contained in BCP 78, and except as set forth therein, the authors 3711 retain all their rights. 3713 <<< RFC Ed Note: please remove the text below, prior to publications 3714 >>> 3716 Change Log. 3718 Rev -00 3720 * First draft, for comment by the community. 3722 Rev -01 3724 * Second draft, for comment by the community. 3726 The MIB module is renamed DVBRCS-MIB to reflect that it covers more 3727 than solely interface issues. 3729 The MIB has been updated with 3731 * a conformance section that captures the options 3733 * structural changes and corrections to achieve this 3735 * SYNTAX refinements where applicable 3737 * UNITS declarations where applicable 3739 Document reformatted to conform to I-D format conventions. 3741 Rev -02 3743 * Third draft, for comment by the community. 3745 Update following comments received from the ipdvb list (Gorry 3746 Fairhurst). 3748 Rev -03 3750 * Fourth draft, for comment by the community. 3752 Update following comments received from Martin Stiemerling and 3753 complement/corrections from the SatLabs Group. 3755 Rev -04 3756 * Fifth draft 3758 Corrected read-write into read-create MAXACCESS for objects in 3759 requestClassTable and pidPoolTable. 3761 Minor updates to correct format of tables and some MIB comments. 3763 <<>