idnits 2.17.1 draft-combes-ipdvb-mib-rcs-02.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 3225. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3202. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3209. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3215. 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 4 instances of lines with control characters in the document. == There are 4 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 202 has weird spacing: '... dBi deci...' == Line 204 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 (December 3, 2007) is 5988 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'ETSI-DAT' is defined on line 3125, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPDVB Working Group S. Combes 2 Internet-Draft P. Amundsen 3 Intended status: Informational M. Lambert 4 Expires: May 3, 2008 H-P. Lexow 5 SatLabs Group 6 December 3, 2007 8 The DVB-RCS MIB 9 draft-combes-ipdvb-mib-rcs-02.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 3 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 May 3, 2008. 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 characterise the behaviour and 47 performance of network layer entities deploying DVB-RCS. 49 Table of Contents 51 1. Introduction...................................................2 52 2. Conventions used in this document..............................2 53 2.1. Abbreviations.............................................2 54 2.2. Glossary..................................................2 55 2.2.1. Star DVB-RCS network.................................2 56 2.2.2. Mesh DVB-RCS network.................................2 57 2.2.3. Transparent DVB-RCS network..........................2 58 2.2.4. Regenerative DVB-RCS network.........................2 59 2.2.5. DVB-RCS MAC layer....................................2 60 2.2.6. DVB-RCS Downlink.....................................2 61 2.2.7. DVB-RCS Uplink.......................................2 62 2.2.8. IDU..................................................2 63 2.2.9. ODU..................................................2 64 2.2.10. RCST................................................2 65 2.2.11. NCC.................................................2 66 2.2.12. Configuration file..................................2 67 2.2.13. Logfile.............................................2 68 2.2.14. InstallLogfile......................................2 69 2.2.15. Antenna alignment...................................2 70 2.2.16. CW frequency........................................2 71 2.2.17. Request Class.......................................2 72 2.2.18. Channel ID..........................................2 73 2.2.19. ATM profile.........................................2 74 2.2.20. MPEG profile........................................2 75 2.2.21. PID pool............................................2 76 2.2.22. Capacity Categories.................................2 77 2.2.23. Start transponder...................................2 78 2.2.24. DVB-S...............................................2 79 2.2.25. DVB-S2 and CCM/VCM/ACM..............................2 80 2.3. MIB Module................................................2 81 3. Definitions....................................................2 82 4. Security Considerations........................................2 83 5. IANA Considerations............................................2 84 6. Acknowledgments................................................2 85 7. References.....................................................2 86 7.1. Normative References......................................2 87 7.2. Informative References....................................2 88 8. Authors' Addresses.............................................2 89 9. Intellectual Property Statement................................2 90 10. Disclaimer of Validity........................................2 91 11. Copyright Statement...........................................2 93 1. Introduction 95 The SatLabs Group [SATLABS] is an international non-profit EEIG 96 (European Economic Interest Grouping) committed to large-scale 97 adoption and deployment of the Digital Video Broadcasting Return 98 Channel via Satellite (DVB-RCS) standard [ETSI-RCS]. SatLabs members 99 are service providers, satellite operators, system integrators, 100 terminal manufacturers and technology providers with an interest in 101 DVB-RCS. 103 Since its creation in 2001, the main goal of the SatLabs Group has 104 been to achieve interoperability between DVB-RCS terminals and 105 systems. Therefore, the Group has defined the SatLabs Qualification 106 Program that provides an independent certification process for DVB- 107 RCS Terminals based on System Recommendations defined by SatLabs. To 108 enhance products interoperability, beyond the physical and MAC layer 109 mechanisms defined in the DVB-RCS standard, SatLabs has expanded its 110 Recommendations in the field of DVB-RCS terminal management 111 [SATLABS]. As a part of this effort, SatLabs has specified a common 112 SNMP Management Information Base (MIB) for DVB-RCS terminals, which 113 is defined in this document. 115 A DVB-RCS terminal is denoted as a Return Channel Satellite Terminal 116 (RCST) in the remainder of this document. This consists of an Indoor 117 Unit (IDU) and an Outdoor Unit (ODU) connected through an Inter 118 Facility Link (IFL), usually a coaxial L-band interface. On the user 119 side, the IDU is connected to the user network through a Local Area 120 Network (LAN) interface (usually Ethernet). On the network side, the 121 ODU is connected via a satellite link (the Air Interface). 123 The DVB-RCS MIB is implemented in the IDU of an RCST. RCST 124 management can be performed either through the LAN interface (Local 125 management) or through the Air Interface (Remote management from the 126 Network Control Center, NCC). 128 +------------+ 129 | IP | 130 | End Host | 131 +-----+------+ 132 | 133 - - - - - - - -|- - - - - - - - - - - - - - - - 134 | | LAN interface | 135 | 136 | +------+--------+ | 137 | Indoor Unit | 138 | | (IDU) | | 139 +------+--------+ 140 | | | 141 Inter Facility Link (IFL) 142 | | | 143 +-----+--------+ 144 | | OutDoor Unit | | 145 | (ODU) | 146 | +------+--------+ | 147 | 148 | | Air Interface | 149 - - - - - - - |- - - - - - - - - - - - - - - - 150 RCST | 151 | +----------------+ 152 +------->| Network Control| 153 | Center (NCC) | 154 +----------------+ 156 FIGURE 1: RCST architecture 158 2. Conventions used in this document 160 This memo defines a portion of the Management Information Base (MIB) 161 for use with network management protocols in the Internet community. 163 For a detailed overview of the documents that describe the current 164 Internet-Standard Management Framework, please refer to section 7 of 165 RFC 3410 [RFC3410]. 167 Managed objects are accessed via a virtual information store, termed 168 the Management Information Base or MIB. MIB objects are generally 169 accessed through the Simple Network Management Protocol (SNMP). 170 Objects in the MIB are defined using the mechanisms defined in the 171 Structure of Management Information (SMI). This memo specifies a MIB 172 module that is compliant to the SMIv2, which is described in STD 58, 173 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 174 [RFC2580]. 176 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 177 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 178 document are to be interpreted as described in RFC 2119 [RFC2119]. 180 2.1. Abbreviations 182 ACM Adaptive Coding and Modulation (defined in [ETSI-DVBS2]) 184 ATM Asynchronous Transfer Mode (cell framing) 186 AVBDC Absolute Volume-Based Dynamic Capacity 188 BER Bit Error Ratio 190 BUC Block Up-Converter 192 CCM Constant Coding and Modulation 194 CNR Carrier to Noise Ratio 196 CRA Continuous Rate Assignment 198 CSC Common Signalling Channel 200 CW Continuous Wave (carrier frequency) 202 dBi deciBel (isotropic) 204 dBm deciBel (with respect to 1 mW) 206 DSCP DiffServ Code Point 208 ETSI European Telecommunications Standards Institute 210 IDU InDoor Unit 211 IFL Inter-Facility Link 213 LNB Low Noise Block 215 LO Local Oscillator 217 MAC Medium Access Control 219 MIB Management Information Base 221 MPEG Motion Pictures Expert Group (TS Packet framing) 223 NCC Network Control Centre 225 OAM Operations and Management 227 ODU OutDoor Unit 229 PHB Per-Hop Behavior 231 PID Packet IDentifier (MPEG, used as Program Identifier in DVB) 233 RBDC Rate-Based Dynamic Capacity 235 RC Request Class 237 RCST Return Channel via Satellite Terminal (DVB-RCS Terminal) 239 Rx Receive 241 SSPA Solid State Power Amplifier 243 TDM Time Division Multiplex 245 TDMA Time Division Multiple Access 247 Tx Transmit 249 VBDC Volume-Based Dynamic Capacity 251 VCI Virtual Channel Identifier (ATM) 253 VPI Virtual Path Identifier (ATM) 255 Vpp Volts peak-to-peak 257 2.2. Glossary 259 The terms in this document are derived either from DVB-RCS standard 260 specifications [ETSI-RCS] or from SatLabs System Recommendations 261 [SATLABS]. 263 2.2.1. Star DVB-RCS network 265 This denotes a hub-and-spoke configuration where all communications 266 pass through a central hub, that usually also includes the NCC. Peer- 267 to-peer communication between RCSTs is possible, but through a double 268 satellite hop (this traffic has to pass through the hub). 270 2.2.2. Mesh DVB-RCS network 272 This denotes a mesh configuration that supports peer-to-peer 273 communications in a single satellite hop directly between RCSTs. 275 2.2.3. Transparent DVB-RCS network 277 This denotes a network using transparent satellite transponders. Star 278 or mesh network configurations can be supported. In the case of a 279 mesh configuration, RCSTs need to incorporate a TDMA receiver in 280 addition to the TDM receiver. 282 2.2.4. Regenerative DVB-RCS network 284 This denotes a network using regenerative satellite transponders, 285 i.e. including some On-Board Processing functionality allowing 286 demodulation and decoding of the uplink TDMA signals and re-multiplex 287 the traffic on the downlink. Star or mesh network configurations can 288 be supported. 290 2.2.5. DVB-RCS MAC layer 292 The DVB-RCS MAC Layer represents the air interface of an RCST, as 293 defined in the DVB-RCS standard. The interface supports star and mesh 294 networks and is bi-directional. 296 2.2.6. DVB-RCS Downlink 298 The downlink is a DVB-RCS physical link based on TDM. It corresponds 299 to the forward link of a DVB-RCS transparent system or the downlink 300 of a DVB-RCS regenerative system. It is based on either the DVB-S or 301 DVB-S2 standard. In the DVB-RCS context, this interface is bi- 302 directional. 304 2.2.7. DVB-RCS Uplink 306 The DVB-RCS Uplink is based on TDMA. It corresponds to the return or 307 mesh link of a RCS transparent system or the uplink of a RCS 308 regenerative system. It is based on the DVB-RCS standard. 310 In the context of star transparent and mesh regenerative DVB-RCS 311 systems, this interface is uni-directional. 313 In the context of mesh transparent DVB-RCS systems, this interface is 314 bi-directional. 316 2.2.8. IDU 318 This is the indoor part of the RCST (including at least the power 319 supply, and usually also the modem and networking functions). 321 2.2.9. ODU 323 This is the outdoor part of the RCST (including at least the aerial, 324 and usually also the LNB and BUC). 326 2.2.10. RCST 328 This is the Satellite Terminal, installed on the customer premises. 329 It is composed of the IDU and ODU. 331 2.2.11. NCC 333 The NCC provides Control and Monitoring Functions. It generates 334 control and timing signals for the operation of the DVB-RCS Network. 336 2.2.12. Configuration file 338 The configuration file is XML formatted file, storing configuration 339 parameters for the RCST and their values. 341 2.2.13. Logfile 343 The logfile is stored at the RCST. This is used to log particular 344 events that occurr on RCST side. 346 2.2.14. InstallLogfile 348 The Installlogfile is stored at the RCST. This logs particular events 349 that occur on RCST side, related to RCST installation phase. 351 2.2.15. Antenna alignment 353 This is the process to align the RCST antenna, part of the ODU, in 354 order to enable bi-directional communication (uplink, downlink) with 355 the satellite network. 357 2.2.16. CW frequency 359 The CW frequency is the frequency of a Continuous Wave signal. It is 360 a narrowband carrier transmitted for the duration of measurements 361 during the installation of a RCST. 363 2.2.17. Request Class 365 A Request Class (RC) is a representation of a Per Hop Behavior (PHB) 366 at the MAC layer. It defines a behavior of the MAC layer for a given 367 aggregation of traffic. This behavior includes a combination of 368 Capacity Categories associated to the RC and a Priority with respect 369 to the other RCs supported by a RCST. 371 2.2.18. Channel ID 373 Each Request Class is identified by a unique Channel_ID in the 374 communication between the RCST and the NCC. 376 2.2.19. ATM profile 378 The ATM profile is one of the two profiles for traffic burst format 379 on a DVB-RCS uplink. It is based on one or more concatenated ATM 380 cells, each of length 53 bytes, plus an optional prefix. 382 2.2.20. MPEG profile 384 The MPEG profile is one of the two profiles for traffic burst format 385 on the DVB-RCS uplink. It is based on a number of concatenated MPEG2- 386 TS packets, each of length 188 bytes. 388 2.2.21. PID pool 390 For the MPEG profile several RCs may be mapped within a pool of 391 several PIDs to allow cross-RC Section Packing [RFC4259]. Section 392 packing can be used on all PIDs and higher priority traffic can 393 always pre-empt lower priority streams. This reduces the need for 394 padding. 396 2.2.22. Capacity Categories 398 The TDMA timeslot allocation process for the DVB-RCS uplink supports 399 several capacity categories. 401 The Capacity Categories CRA, RBDC and A/VBDC, when authorized for a 402 RC, have to be configured from the NCC. These configuration 403 parameters are used to inform the RCST of the configuration of each 404 Category at the NCC side and thus help in Capacity Requests 405 computation. 407 The configuration of these parameters is performed for each RC. A 408 SatLabs option is defined that allows their configuration at the RCST 409 level in addition to configuration per RC. This option is denoted 410 RCST_PARA. 412 2.2.22.1. Continuous Rate Assignment (CRA) 414 CRA is a rate capacity that is provided in full in a continuous 415 manner to the RCST while required. 417 2.2.22.2. Rate-Based Dynamic Capacity (RBDC) 419 RBDC is rate capacity that is requested dynamically by an RCST. RBDC 420 capacity is provided in response to explicit requests from the RCST 421 to the NCC, such requests being absolute (i.e. corresponding to the 422 full rate currently being requested). Each request overrides all 423 previous RBDC requests from the same RCST, and is subject to a 424 maximum rate limit. 426 2.2.22.3. Volume-Based Dynamic Capacity (VBDC) 428 VBDC is volume capacity that is requested dynamically by an RCST. 429 VBDC capacity is provided in response to explicit requests from the 430 RCST to the NCC, such requests being cumulative (i.e. each request 431 adds to all previous requests from the same RCST). 433 2.2.22.4. Absolute Volume-Based Dynamic Capacity (AVBDC) 435 AVBDC is volume capacity that is requested dynamically by an RCST. 436 This capacity is provided in response to explicit requests from the 437 RCST to the NCC, such requests being absolute (i.e. this request 438 replaces the previous ones from the same RCST). 440 The combination of AVBDC and VBDC is seen as a single Capacity 441 Category, denoted A/VBDC. 443 A SatLabs Option is defined which allows AVBDC requests to be sent 444 periodically, as defined by the AVBDCrepTime parameter. This option 445 is denoted AVBDC_REP. 447 2.2.22.5. Population ID 449 This defines a group of RCSTs within a Network. 451 2.2.23. Start transponder 453 This is the satellite transponder on which the communication is 454 initiated from a RCST point-of-view when in the installation mode. 455 The parameters corresponding to this transponder (satellite orbital 456 position, frequency, etc.) are stored at the RCST as power-up 457 configuration data. 459 2.2.24. DVB-S 461 DVB-S is the Digital Video Broadcast over Satellite [ETSI-DVBS]. It 462 is a framework and set of associated standards published by ETSI for 463 the transmission of video, audio, and data, using the ISO MPEG-2 464 Standard [ISO-MPEG], over satellite links. 466 2.2.25. DVB-S2 and CCM/VCM/ACM 468 DVB-S2 is the Second Generation of the Digital Video Broadcast for 469 Satellite applications standard [ETSI-DVBS2]. It is a framework and 470 set of associated standards published by ETSI for the transmission of 471 video, audio and data. 473 BBFRAME: The main framing unit of the DVB-S2 protocol stack. 475 CCM: In CCM transmission mode, the forward link uses a constant set 476 of transmission parameters (FEC coding rate and modulation scheme) 477 for all receivers. 479 VCM: In VCM transmission mode, the forward link uses transmission 480 parameters which are variable on a BBFRAME-by-BBFRAME, but fixed on a 481 Receiver basis, according to fixed link and propagation conditions 482 for each Receiver. 484 ACM: In ACM transmission mode, the forward link uses transmission 485 parameters which are dynamically adjusted on a BBFRAME-by-BBFRAME and 486 Receiver-per-Receiver basis, according to actual link and propagation 487 conditions. In order to implement ACM, feedback from each Receiver 488 has to be provided by DVB-RCS return channel. 490 2.2.26. Interactive Network 492 This is another name for a DVB-RCS based satellite network. 494 2.3. MIB Module 496 The MIB module in this document uses the following OBJECT IDENTIFIER 497 values as already assigned by IANA under the smi-numbers registry: 499 +------------+---------------------------+ 500 | Descriptor | OBJECT IDENTIFIER value | 501 +------------+---------------------------+ 502 |dvbrcsMib |{ mib-2 transmission 239 } | 503 +------------+---------------------------+ 505 Table 1: Object Identifiers for the MIB 507 These values have been assigned for this MIB under the 'mib- 508 2.transmission' subtree. 510 3. Definitions 512 DVBRCS-MIB DEFINITIONS ::= BEGIN 514 IMPORTS 515 MODULE-IDENTITY, 516 Integer32, 517 IpAddress, 518 transmission, 519 OBJECT-TYPE 520 FROM SNMPv2-SMI -- [RFC2578] 521 TEXTUAL-CONVENTION, 522 DisplayString, 523 RowStatus 524 FROM SNMPv2-TC -- [RFC2579] 525 OBJECT-GROUP, 526 MODULE-COMPLIANCE 527 FROM SNMPv2-CONF; -- [RFC2580] 529 dvbrcsMIB MODULE-IDENTITY 530 LAST-UPDATED "200710301200Z" 531 ORGANIZATION "The SatLabs Group" 532 CONTACT-INFO 533 "The SatLabs Group 534 Web: www.satlabs.org 535 E-mail: info@satlabs.org" 536 DESCRIPTION 537 "DVB-RCS MIB subtree. 538 This MIB module applies to equipment that is a 539 Return Channel Satellite Terminal (RCST) defined in 540 the Digital Video Broadcasting Return 541 Channel via Satellite system (DVB-RCS) standard (ETSI EN 301 542 791 Digital Video Broadcasting (DVB); Interaction Channel 543 for Satellite Distribution Systems, European 544 Telecommunications Standards Institute (ETSI)). 545 It defines a set of MIB entities to characterise the 546 behaviour and performance of network layer entities 547 implementing DVB-RCS. 548 This MIB module is intended to be used by DVB-RCS equipment 549 following the SatLabs System Recommendations, defined by the 550 SatLabs Group and available at www.satlabs.org." 552 REVISION "200710301200Z" 553 DESCRIPTION 554 "Revision of this MIB module, following comments from ipdvb 555 WG." 556 ::= { transmission 239 } 558 =================================================================== 559 -- Textual Conventions 560 --=================================================================== 561 SatLabsOptionMap ::= TEXTUAL-CONVENTION 562 STATUS current 563 DESCRIPTION 564 "This textual convention enumerates the declaration of the 565 SatLabs defined options. (0) refers to the most significant 566 bit." 567 REFERENCE 568 "SatLabs System Recommendations version 2 available at 569 www.satlabs.org" 570 SYNTAX BITS { 571 mpegTrf(0), 572 coarseSync(1), 573 wideHop(2), 574 fastHop(3), 575 dynamicMfTdma(4), 576 routeId(5), 577 contentionSync(6), 578 qpskLow(7), 579 mod16Apsk(8), 580 mod32Apsk(9), 581 normalFec(10), 582 multiTs(11), 583 gsTs(12), 584 enhQoS(13), 585 pep(14), 586 http(15), 587 ftp(16), 588 dhcp(17), 589 dns(18), 590 avbdcRep(19), 591 chIdStrict(20), 592 rcstPara(21), 593 nlid(22), 594 snmpAll(23), 595 installLog(24), 596 fwdLinkStatus(25), 597 enhClassifier(26), 598 spare1(27), 599 spare2(28), 600 spare3(29), 601 spare4(30), 602 spare5(31) 603 } 605 --=================================================================== 606 -- object type definitions 607 --=================================================================== 608 dvbrcsMIBObjects OBJECT IDENTIFIER ::= {dvbrcsMIB 1} 609 dvbrcsConformance OBJECT IDENTIFIER ::= {dvbrcsMIB 2} 611 rcst OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 1} 612 fwdLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 2} 613 rtnLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 3} 615 rcstSystem OBJECT IDENTIFIER ::= {rcst 1} 616 rcstNetwork OBJECT IDENTIFIER ::= {rcst 2} 617 rcstInstall OBJECT IDENTIFIER ::= {rcst 3} 618 rcstQos OBJECT IDENTIFIER ::= {rcst 4} 619 rcstControl OBJECT IDENTIFIER ::= {rcst 5} 620 rcstState OBJECT IDENTIFIER ::= {rcst 6} 622 fwdConfig OBJECT IDENTIFIER ::= {fwdLink 1} 623 fwdStatus OBJECT IDENTIFIER ::= {fwdLink 2} 625 rtnConfig OBJECT IDENTIFIER ::= {rtnLink 1} 626 rtnStatus OBJECT IDENTIFIER ::= {rtnLink 2} 628 --=================================================================== 629 --- rcstSystem sub-tree object types 630 --=================================================================== 631 systemMibRevision OBJECT-TYPE 632 SYNTAX DisplayString 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "This object allows the SNMP agent to report the implemented 637 MIB module revision. 638 The supported REVISION of this module is reported." 639 ::= {rcstSystem 1} 641 --=================================================================== 642 -- Options declared according to the textual conventions 643 --=================================================================== 644 systemSatlabsOptions OBJECT-TYPE 645 SYNTAX SatLabsOptionMap 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "Indicates the options supported as defined in the SatLabs 650 System Recommendations version 2. 651 A value of 1 indicates that the respective option is 652 supported. The mapping to the options is to be understood 653 as described here.(0) refers to the most significant bit. 655 mpegTrf(0) -> MPEG_TRF 656 coarseSync(1) -> COARSE_SYNC 657 wideHop(2) -> WIDE_HOPP 658 fastHop(3) -> FAST_HOPP 659 dynamicMfTdma(4) -> Dynamic_MF_TDMA 660 routeId(5) -> ROUTE_ID 661 contentionSync(6) -> CONTENTION_SYNC 662 qpskLow(7) -> QPSKLOW 663 mod16Apsk(8) -> 16APSK 664 mod32Apsk(9) -> 32APSK 665 normalFec(10) -> NORMALFEC 666 multiTs(11) -> MULTITS 667 gsTs(12) -> GSTS 668 enhQoS(13) -> ENHQOS 669 pep(14) -> PEP 670 http(15) -> HTTP 671 ftp(16) -> FTP 672 dhcp(17) -> DHCP 673 dns(18) -> DNS 674 avbdcRep(19) -> AVBDC_REP 675 chIdStrict(20) -> CHID_STRICT 676 rcstPara(21) -> RCST_PARA 677 nlid(22) -> NLID 678 snmpAll(23) -> SNMPALL 679 installLog(24) -> INSTALL_LOG 680 fwdLinkStatus(25) -> FWDLINKSTATUS 681 enhClassifier(26) -> ENHCLASSIFIER 683 The support of specific options mandates the support of 684 specific objects and access levels." 685 REFERENCE 686 "SatLabs System Recommendation version 2 available 687 at www.satlabs.org" 688 ::= {rcstSystem 2} 690 systemLocation OBJECT-TYPE 691 SYNTAX DisplayString 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "Physical location of the ODU antenna expressed as 696 Longitude, Latitude and Altitude. The string 697 shall have 31 characters in the following format: 698 ,,,,,M 699 where x, y and z represents digits, 700 a=N or S, 701 b=E or W, 702 Reading the digits from left to right: 703 'x' 7 latitude digits; x digits 1-2 contain the degrees, 704 x digits 3-7 contain the minutes in decimal; 705 'y' 8 longitude digits; y digits 1-3 contain the degrees, 706 y digits 4-8 contain the minutes in decimal; 707 ''' 5 altitude digits; meters above sea level in decimal; 708 '.' is the decimal point; 709 ',' is the field separator; 710 'M' is the indicator for altitude meters. 712 This format is a modified subset of the NMEA 0183 713 (National Marine Electronics Association, Interface 714 Standard) format for Global Positioning System Fix Data." 715 ::= {rcstSystem 3} 716 systemOduAntennaSize OBJECT-TYPE 717 SYNTAX DisplayString 718 UNITS "cm" 719 MAX-ACCESS read-write 720 STATUS current 721 DESCRIPTION 722 "This object gives the diameter of the antenna. This value 723 shall be given in centimeters. It is defined at 724 installation. 725 The object can be used in conjunction with environmental 726 requirements. " 727 ::= {rcstSystem 4} 729 systemOduAntennaGain OBJECT-TYPE 730 SYNTAX Integer32 731 UNITS "x0.1 dBi" 732 MAX-ACCESS read-write 733 STATUS current 734 DESCRIPTION 735 "This field describes the antenna peak gain of the ODU and 736 shall be defined by the installer. The gain shall be given 737 in tenth of dBi for more flexibility, i.e. 46.5 dBi will be 738 represented by 465. Defined at installation." 739 ::= {rcstSystem 5} 741 systemOduSspa OBJECT-TYPE 742 SYNTAX Integer32 743 UNITS "x0.1 W" 744 MAX-ACCESS read-write 745 STATUS current 746 DESCRIPTION 747 "This field describes the Solid State Power Amplifier 748 installed in the ODU and shall be defined by the installer. 749 The power shall be given in tenth of a Watt, i.e. 0,5 W will 750 be represented by 5, 1 W by 10 and 2 W by 20. 751 Defined at installation." 752 ::= {rcstSystem 6} 754 systemOduTxType OBJECT-TYPE 755 SYNTAX DisplayString 756 MAX-ACCESS read-write 757 STATUS current 758 DESCRIPTION 759 "Describes the type of transmitter installed in the ODU." 760 ::= {rcstSystem 7} 762 systemOduRxType OBJECT-TYPE 763 SYNTAX DisplayString 764 MAX-ACCESS read-write 765 STATUS current 766 DESCRIPTION 767 "Describes the type of LNB installed in the ODU, with 768 information such as vendor type, output type (single, twin, 769 quad,...), etc." 770 ::= {rcstSystem 8} 772 systemOduRxBand OBJECT-TYPE 773 SYNTAX INTEGER { 774 oduHighRxBand (0), 775 oduLowRxBand (1) 776 } 777 MAX-ACCESS read-write 778 STATUS current 779 DESCRIPTION 780 "Describes whether High Band or Low Band is selected in 781 the LNB. Specifying High Band results in activation of a 782 18-26 kHz tone with 0.4-0.8 Vpp in the Rx IFL cable: 783 (0) - High Band 784 (1) - Low Band" 785 ::= {rcstSystem 9} 787 systemOduRxLO OBJECT-TYPE 788 SYNTAX Integer32 789 UNITS "x100 Hz" 790 MAX-ACCESS read-write 791 STATUS current 792 DESCRIPTION 793 "Frequency of LNB Local Oscillator (in 100 Hz)" 794 ::= {rcstSystem 10} 795 systemOduTxLO OBJECT-TYPE 796 SYNTAX Integer32 797 UNITS "x100 Hz" 798 MAX-ACCESS read-write 799 STATUS current 800 DESCRIPTION 801 "Frequency of Block Up-Converter Local Oscillator 802 (in 100 Hz)." 803 ::= {rcstSystem 11} 805 --=================================================================== 806 -- rcstInstall sub-tree object types 807 --=================================================================== 808 installAntennaAlignmentState OBJECT-TYPE 809 SYNTAX INTEGER { 810 antennaAlignmentStart (1), 811 antennaAlignmentDeny (2), 812 antennaAlignmentContinue(3), 813 antennaAlignmentStop (4), 814 antennaAlignmentSuccess (5), 815 antennaAlignmentFail (6) 816 } 817 MAX-ACCESS read-write 818 STATUS current 819 DESCRIPTION 820 "Indicates the alignment state of the antenna: 821 (1)-Start; 822 (2)-Deny; 823 (3)-Continue; 824 (4)-Stop; 825 (5)-Success; 826 (6)-Fail" 827 ::= {rcstInstall 1} 829 installCwFrequency OBJECT-TYPE 830 SYNTAX Integer32 831 UNITS "x100 Hz" 832 MAX-ACCESS read-write 833 STATUS current 834 DESCRIPTION 835 "Frequency at which the transmitted Continuous Wave carrier 836 (in 100 Hz). 837 Minimum required precision is 1 kHz." 838 ::= {rcstInstall 2} 840 installCwMaxDuration OBJECT-TYPE 841 SYNTAX Integer32 842 UNITS "seconds" 843 MAX-ACCESS read-write 844 STATUS current 845 DESCRIPTION 846 "Time after which the Continuous Wave carrier must be put 847 down (in seconds)" 848 ::= {rcstInstall 3} 850 installCwPower OBJECT-TYPE 851 SYNTAX Integer32 852 UNITS "x0.1 dBm" 853 MAX-ACCESS read-write 854 STATUS current 855 DESCRIPTION 856 "Power of the Continuous Wave carrier. 857 It is specified in tenth of dBm. This parameter allows for 858 fine (manual) tuning of the power setup. Minimum required 859 precision is 1 dBm. It must be configurable while CW signal 860 is on. Once the power has been properly adjusted, the power 861 setup is stored in rtnConfigDefIfLevel." 862 ::= {rcstInstall 4} 864 installCoPolReading OBJECT-TYPE 865 SYNTAX Integer32 866 UNITS "x0.1 dB" 867 MAX-ACCESS read-write 868 STATUS current 869 DESCRIPTION 870 "Co-Polarisation measured value during installation 871 procedure (in 0.1 dB)" 872 ::= {rcstInstall 5} 874 installXPolReading OBJECT-TYPE 875 SYNTAX Integer32 876 UNITS "x0.1 dB" 877 MAX-ACCESS read-write 878 STATUS current 879 DESCRIPTION 880 "Cross-Polarisation measured value during installation 881 procedure (in 0.1 dB)" 882 ::= {rcstInstall 6} 884 installCoPolTarget OBJECT-TYPE 885 SYNTAX Integer32 886 UNITS "x0.1 dB" 887 MAX-ACCESS read-write 888 STATUS current 889 DESCRIPTION 890 "Co-Polarisation target value during installation procedure 891 (in 0.1 dB)." 892 ::= {rcstInstall 7} 894 installXPolTarget OBJECT-TYPE 895 SYNTAX Integer32 896 UNITS "x0.1 dB" 897 MAX-ACCESS read-write 898 STATUS current 899 DESCRIPTION 900 "Cross-Polarisation target value during installation procedure 901 (in 0.1 dB)" 902 ::= {rcstInstall 8} 904 installStandByDuration OBJECT-TYPE 905 SYNTAX Integer32 906 UNITS "seconds" 907 MAX-ACCESS read-write 908 STATUS current 909 DESCRIPTION 910 "Time to wait in stand-by mode (in seconds)" 911 ::= {rcstInstall 9} 913 installTargetEsN0 OBJECT-TYPE 914 SYNTAX Integer32(0..315) 915 UNITS "x0.1 dB" 916 MAX-ACCESS read-write 917 STATUS current 918 DESCRIPTION 919 "This value describes the wanted Es/N0 value that enables 920 operation of the return link with the required error 921 performance. The values shall be given in tenth of dB and 922 the initial value shall be equal to 7 dB. The range shall be 923 from 0 dBm to 31.5 dBm with a precision of 0.1 dB." 924 DEFVAL { 70 } 925 ::= {rcstInstall 10} 927 --=================================================================== 928 -- rcstNetwork sub-tree object types 929 --=================================================================== 930 networkOamIpAddr OBJECT-TYPE 931 SYNTAX IpAddress 932 MAX-ACCESS read-write 933 STATUS current 934 DESCRIPTION 935 "OAM IP Address of the RCST. This object is used with both 936 IP and interfaces MIB-II subgroups. It uniquely determines 937 the interface through which OAM traffic passes. 938 The OAM IP address may be statically or dynamically 939 assigned. It is system dependent whether the OAM IP address 940 and the Traffic IP address are the same address." 941 ::= {rcstNetwork 1} 943 networkOamIpNetworkMask OBJECT-TYPE 944 SYNTAX IpAddress 945 MAX-ACCESS read-write 946 STATUS current 947 DESCRIPTION 948 "Network Mask for the OAM IP Address." 949 ::= {rcstNetwork 2} 951 networkOamIpAddrAssign OBJECT-TYPE 952 SYNTAX INTEGER { 953 oamIpAddressStatic (1), 954 oamIpAddressDynamic (2) 955 } 956 MAX-ACCESS read-write 957 STATUS current 958 DESCRIPTION 959 "Identifies whether the OAM IP address is statically 960 (1) or dynamically (2) assigned." 961 ::= {rcstNetwork 3} 963 networkLanIpAddress OBJECT-TYPE 964 SYNTAX IpAddress 965 MAX-ACCESS read-write 966 STATUS current 967 DESCRIPTION 968 "IP address of the LAN interface" 969 ::= {rcstNetwork 4} 971 networkLanIpMask OBJECT-TYPE 972 SYNTAX IpAddress 973 MAX-ACCESS read-write 974 STATUS current 975 DESCRIPTION 976 "Mask for the LAN interface" 977 ::= {rcstNetwork 5} 979 networkAirInterfaceDefaultGateway OBJECT-TYPE 980 SYNTAX IpAddress 981 MAX-ACCESS read-write 982 STATUS current 983 DESCRIPTION 984 "Default Gateway for the air interface" 985 ::= {rcstNetwork 6} 987 networkDnsServerIpAddress OBJECT-TYPE 988 SYNTAX IpAddress 989 MAX-ACCESS read-write 990 STATUS current 991 DESCRIPTION 992 "IP address of the DNS server in the NCC." 993 ::= {rcstNetwork 7} 995 networkNccMgtIpAddress OBJECT-TYPE 996 SYNTAX IpAddress 997 MAX-ACCESS read-write 998 STATUS current 999 DESCRIPTION 1000 "IP address of the management server in the NCC." 1001 ::= {rcstNetwork 8} 1003 networkConfigFileDownloadUrl OBJECT-TYPE 1004 SYNTAX DisplayString 1005 MAX-ACCESS read-write 1006 STATUS current 1007 DESCRIPTION 1008 "Full path name for the configuration file download. 1009 It includes the protocol type (tftp or ftp) and the 1010 associated server IP address or hostname. Hostname can 1011 only be used if DNS is supported by the RCST. 1012 The format of this parameter follows RFC 1738." 1013 ::= {rcstNetwork 9} 1015 networkInstallLogFileDownloadUrl OBJECT-TYPE 1016 SYNTAX DisplayString 1017 MAX-ACCESS read-write 1018 STATUS current 1019 DESCRIPTION 1020 "Full path of the installation log file to download. 1021 It includes the protocol type (tftp or ftp) and the 1022 associated server IP address or hostname. Hostname can 1023 only be used if DNS is supported by the RCST. The 1024 installation log file can be created on the installer's 1025 computer and downloaded to the RCST. 1026 The format of this parameter follows RFC 1738." 1027 ::= {rcstNetwork 10} 1029 networkConfigFileUploadUrl OBJECT-TYPE 1030 SYNTAX DisplayString 1031 MAX-ACCESS read-write 1032 STATUS current 1033 DESCRIPTION 1034 "Full path name for the configuration file upload. 1035 It includes the protocol type (tftp or ftp) and the 1036 associated server IP address or hostname. Hostname can 1037 only be used if DNS is supported by the RCST. 1038 The format of this parameter follows RFC 1738." 1039 ::= {rcstNetwork 11} 1040 networkLogFileUploadUrl OBJECT-TYPE 1041 SYNTAX DisplayString 1042 MAX-ACCESS read-write 1043 STATUS current 1044 DESCRIPTION 1045 "Full path of the event log file. It includes the protocol 1046 type (tftp or ftp) and the associated server IP address 1047 or hostname. Hostname can only be used if DNS is supported 1048 by the RCST. 1049 The format of this parameter follows RFC 1738." 1050 ::= {rcstNetwork 12} 1052 networkInstallLogFileUploadUrl OBJECT-TYPE 1053 SYNTAX DisplayString 1054 MAX-ACCESS read-write 1055 STATUS current 1056 DESCRIPTION 1057 "Full path of the installation log file. It includes the 1058 protocol type (tftp or ftp) and the associated server 1059 IP address or hostname. Hostname can only be used if DNS is 1060 supported by the RCST. The installation log file can be 1061 retrieved from the RCST by the NCC or by the installer 1062 via the LAN. 1063 The format of this parameter follows RFC 1738." 1064 ::= {rcstNetwork 13} 1066 --=================================================================== 1067 -- rtnConfig sub-tree object types 1068 --=================================================================== 1069 rtnConfigMaxEirp OBJECT-TYPE 1070 SYNTAX Integer32 1071 UNITS "x0.1 dBm" 1072 MAX-ACCESS read-write 1073 STATUS current 1074 DESCRIPTION 1075 "Maximum allowed EIRP in tenth of dBm on the return link." 1076 ::= {rtnConfig 1} 1078 rtnConfigDefIfLevel OBJECT-TYPE 1079 SYNTAX Integer32 1080 UNITS "x0.1 dBm" 1081 MAX-ACCESS read-write 1082 STATUS current 1083 DESCRIPTION 1084 "Default transmitted IF power level, specified in tenth of 1085 dBm, out of the IDU for sending a CSC burst at RCST reboot or 1086 power on. Applies to all signals transmitted by RCST (CW and 1087 traffic) immediately." 1088 ::= {rtnConfig 2} 1090 --=================================================================== 1091 -- rtnStatus sub-tree object types 1092 --=================================================================== 1093 rtnStatusEbN0 OBJECT-TYPE 1094 SYNTAX Integer32 1095 UNITS "x0.1 dB" 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "The EbN0 value reported for the return link, referenced to 1100 the regular SYNC burst transmission, in 0.1 dB units." 1101 ::= {rtnStatus 1} 1103 rtnStatusSFDuration OBJECT-TYPE 1104 SYNTAX Integer32 (250..7500) 1105 UNITS "0.1 ms" 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The duration of the currently applied return link super- 1110 frame structure, in tenths of milliseconds." 1111 ::= {rtnStatus 2} 1113 rtnStatusPayloadUnit OBJECT-TYPE 1114 SYNTAX INTEGER { 1115 unitATM (0), 1116 unitMPEG (1) 1117 } 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "Indicates if the payload unit used for the return link is 1122 ATM or MPEG." 1123 ::= {rtnStatus 3} 1125 --=================================================================== 1126 --- fwdConfig sub-tree object types 1127 -- 1128 ===================================================================== 1129 fwdStartTable OBJECT-TYPE 1130 SYNTAX SEQUENCE OF FwdStartEntry 1131 MAX-ACCESS not-accessible 1132 STATUS current 1133 DESCRIPTION 1134 "Lists Forward Links attachment points (e.g. different for 1135 installation and operation). 1136 The table describes the forward link parameters used for the 1137 start-up stream with the NCC." 1138 ::={fwdConfig 1} 1140 fwdStartEntry OBJECT-TYPE 1141 SYNTAX FwdStartEntry 1142 MAX-ACCESS not-accessible 1143 STATUS current 1144 DESCRIPTION 1145 "An entry in the Forward Link StartConfig table." 1146 INDEX { fwdStartIndex, fwdStartPopId } 1147 ::= { fwdStartTable 1 } 1149 FwdStartEntry ::= SEQUENCE { 1150 fwdStartIndex Integer32, 1151 fwdStartPopId Integer32, 1152 fwdStartFrequency Integer32, 1153 fwdStartPolar INTEGER, 1154 fwdStartFormat INTEGER, 1155 fwdStartRolloff INTEGER, 1156 fwdStartSymbolRate Integer32, 1157 fwdStartInnerFec INTEGER, 1158 fwdStartRowStatus RowStatus 1159 } 1161 fwdStartIndex OBJECT-TYPE 1162 SYNTAX Integer32 (1..8) 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "Index of the Forward Link StartConfig table." 1167 ::={fwdStartEntry 1} 1169 fwdStartPopId OBJECT-TYPE 1170 SYNTAX Integer32 (-1..65535) 1171 MAX-ACCESS read-create 1172 STATUS current 1173 DESCRIPTION 1174 "Population identifier associated with the start-up 1175 forward link: 1176 -1: any (auto) 1177 0-65535: specific StartPopId 1178 If 'any' is set, the RCST will assume membership of any 1179 announced population ID and will commence with logon in 1180 accordance with this assumption." 1181 ::={fwdStartEntry 2} 1183 fwdStartFrequency OBJECT-TYPE 1184 SYNTAX Integer32 1185 UNITS "x100 kHz" 1186 MAX-ACCESS read-create 1187 STATUS current 1188 DESCRIPTION 1189 "Frequency of the start transponder carrying a 1190 Network Information Table to which any RCST shall 1191 trigger to acquire forward link. Its value shall be given 1192 in multiple of 100 kHz." 1193 ::={fwdStartEntry 3} 1195 fwdStartPolar OBJECT-TYPE 1196 SYNTAX INTEGER { 1197 linearHorizontal (0), 1198 linearVertical (1), 1199 circularLeft (2), 1200 circularRight (3) 1201 } 1202 MAX-ACCESS read-create 1203 STATUS current 1204 DESCRIPTION 1205 "2-bit field giving the polarization of the start 1206 transponder carrying an Network Information Table 1207 to which any RCST shall trigger to acquire forward link: 1208 00: linear and horizontal 1209 01: linear and vertical 1210 10: circular left 1211 11: circular right" 1212 ::={fwdStartEntry 4} 1214 fwdStartFormat OBJECT-TYPE 1215 SYNTAX INTEGER { 1216 auto (-1), 1217 dvbs (0), 1218 dvbs2ccm (1), 1219 dvbs2acm (2) 1220 } 1221 MAX-ACCESS read-create 1222 STATUS current 1223 DESCRIPTION 1224 "Specifies the transmission format standard applied for the 1225 startup stream. The start transport stream carries a Network 1226 Information Table that the RCST uses for acquiring the 1227 forward link signaling. Supported values are: 1228 -1: unspecified (automatic format acquisition is 1229 assumed) 1230 0: DVB-S (support of this value is mandatory if DVB-S 1231 support is claimed) 1232 1: DVB-S2 with CCM (support of this value is mandatory 1233 if DVB-S2 CCM support is claimed) 1234 2: DVB-S2 with VCM or ACM (support of this value is 1235 mandatory if DVB-S2 ACM support is claimed) 1236 This allows the RCST to discriminate between CCM and VCM/ACM 1237 when selecting FL. 1238 The support of automatic format selection is optional. One 1239 Or several of the other format selections must be supported, 1240 according to the claimed SatLabs profile support." 1241 ::={fwdStartEntry 5} 1242 fwdStartRolloff OBJECT-TYPE 1243 SYNTAX INTEGER { 1244 autoRolloff (0), 1245 rolloff020 (1), 1246 rolloff025 (2), 1247 rolloff035 (3) 1248 } 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "Specifies the receive filter roll-off applied on the start 1253 transponder. The start transponder carries a Network 1254 Information Table that the RCST uses for acquiring the 1255 forward link signaling. 1256 Supported values are: 1257 0: any (auto) 1258 1: 0.20 1259 2: 0.25 1260 3: 0.35" 1261 ::={fwdStartEntry 6} 1263 fwdStartSymbolRate OBJECT-TYPE 1264 SYNTAX Integer32 1265 UNITS "x100 symbols/s" 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "Specifies the symbol rate on the start transponder 1270 carrying a Network Information Table to which any RCST 1271 shall trigger to acquire forward link. Its value shall be 1272 given in multiple of 100 symbols/s." 1273 ::={fwdStartEntry 7} 1275 fwdStartInnerFec OBJECT-TYPE 1276 SYNTAX INTEGER { 1277 autoFec (-1), 1278 fecRate1/2 (0), 1279 fecRate2/3 (1), 1280 fecRate3/4 (2), 1281 fecRate5/6 (3), 1282 fecRate7/8 (4), 1283 fecRate8/9 (5), 1284 fecRate3/5 (6), 1285 fecRate4/5 (7), 1286 fecRate9/10 (8), 1287 fecRate2/5 (9), 1288 fecRate1/3 (10), 1289 fecRate1/4 (11), 1290 noInnerCode (12) } 1291 MAX-ACCESS read-create 1292 STATUS current 1293 DESCRIPTION 1294 "Specifies the inner Forward Error Correction used on the 1295 start transponder carrying a Network Information Table 1296 to which any RCST shall trigger to acquire forward link. 1297 Supported values are: 1298 autoFec (-1), 1299 fecRate1/2 (0), 1300 fecRate2/3 (1), 1301 fecRate3/4 (2), 1302 fecRate5/6 (3), 1303 fecRate7/8 (4), 1304 fecRate8/9 (5), 1305 fecRate3/5 (6), 1306 fecRate4/5 (7), 1307 fecRate9/10 (8), 1308 fecRate2/5 (9), 1309 fecRate1/3 (10), 1310 fecRate1/4 (11), 1311 noInnerCode (12) 1312 The support of autoFec is optional." 1313 ::={fwdStartEntry 8} 1315 fwdStartRowStatus OBJECT-TYPE 1316 SYNTAX RowStatus 1317 MAX-ACCESS read-create 1318 STATUS current 1319 DESCRIPTION 1320 "Standard SNMP row status" 1321 DEFVAL { active } 1322 ::={fwdStartEntry 9} 1323 --=================================================================== 1324 -- fwdStatus sub-tree object types 1325 --=================================================================== 1326 fwdStatusPopId OBJECT-TYPE 1327 SYNTAX Integer32 (0..65535) 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "Population identifier applied at log-on: 1332 0-65535: specific StartPopId 1333 If the RCST was allowed to logon with any population, the 1334 RCST will report the base number of the announced 1335 population ID indicated by the RCS Map Table linkage 1336 descriptor used at logon." 1337 ::={fwdStatus 1} 1339 fwdStatusTable OBJECT-TYPE 1340 SYNTAX SEQUENCE OF FwdStatusEntry 1341 MAX-ACCESS not-accessible 1342 STATUS current 1343 DESCRIPTION 1344 "This table describes the current status of Forward Link 1345 interfaces." 1346 ::={fwdStatus 2} 1348 fwdStatusEntry OBJECT-TYPE 1349 SYNTAX FwdStatusEntry 1350 MAX-ACCESS not-accessible 1351 STATUS current 1352 DESCRIPTION 1353 "An entry in the Forward Link Status table. Each entry is 1354 associated with a physical interface. 1355 A RCST shall support at least one entry." 1356 INDEX { fwdStatusIndex, fwdStatusIfReference } 1357 ::= { fwdStatusTable 1 } 1359 FwdStatusEntry ::= SEQUENCE { 1360 fwdStatusIndex Integer32, 1361 fwdStatusIfReference Integer32, 1362 fwdStatusNetId Integer32, 1363 fwdStatusNetName DisplayString, 1364 fwdStatusFormat INTEGER, 1365 fwdStatusFrequency Integer32, 1366 fwdStatusPolar INTEGER, 1367 fwdStatusInnerFec INTEGER, 1368 fwdStatusSymbolRate Integer32, 1369 fwdStatusRolloff INTEGER, 1370 fwdStatusModulation INTEGER, 1371 fwdStatusFecFrame INTEGER, 1372 fwdStatusPilot INTEGER, 1373 fwdStatusBer Integer32, 1374 fwdStatusCnr Integer32, 1375 fwdStatusRxPower Integer32, 1376 fwdStatusRowStatus RowStatus 1377 } 1379 fwdStatusIndex OBJECT-TYPE 1380 SYNTAX Integer32 (1..8) 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "Index of the Forward Link Status table." 1385 ::={fwdStatusEntry 1} 1387 fwdStatusIfReference OBJECT-TYPE 1388 SYNTAX Integer32 (1..8) 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Cross reference to the interface table" 1393 ::={fwdStatusEntry 2} 1395 fwdStatusNetId OBJECT-TYPE 1396 SYNTAX Integer32 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "Interactive network identifier of the forward 1401 link (from RCS Map Table)" 1402 ::={fwdStatusEntry 3} 1404 fwdStatusNetName OBJECT-TYPE 1405 SYNTAX DisplayString 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "The name of the interactive network of the forward 1410 link (from RCS Map Table)" 1411 ::={fwdStatusEntry 4} 1413 fwdStatusFormat OBJECT-TYPE 1414 SYNTAX INTEGER { 1415 dvbs (0), 1416 dvbs2ccm (1), 1417 dvbs2acm (2), 1418 reservedFormat (3) 1419 } 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "Specifies the transmission format applied on the forward 1424 link. Supported values are (from RMT): 1425 0: DVB-S 1426 1: DVB-S2 using CCM 1427 2: DVB-S2 using VCM or ACM 1428 3: reserved" 1429 ::={fwdStatusEntry 5} 1431 fwdStatusFrequency OBJECT-TYPE 1432 SYNTAX Integer32 1433 UNITS "x100 kHz" 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "An estimate of the frequency of the forward link. Its value 1438 shall be given in multiple of 100 kHz." 1439 ::={fwdStatusEntry 6} 1441 fwdStatusPolar OBJECT-TYPE 1442 SYNTAX INTEGER { 1443 linearHorizontal (0), 1444 linearVertical (1), 1445 circularLeft (2), 1446 circularRight (3) 1447 } 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "2-bit field giving the polarization of the forward link 1452 (from RMT): 1453 00: linear and horizontal 1454 01: linear and vertical 1455 10: circular left 1456 11: circular right" 1457 ::={fwdStatusEntry 7} 1459 fwdStatusInnerFec OBJECT-TYPE 1460 SYNTAX INTEGER { 1461 unknown (-1), 1462 fecRate1/2 (0), 1463 fecRate2/3 (1), 1464 fecRate3/4 (2), 1465 fecRate5/6 (3), 1466 fecRate7/8 (4), 1467 fecRate8/9 (5), 1468 fecRate3/5 (6), 1469 fecRate4/5 (7), 1470 fecRate9/10 (8), 1471 fecRate2/5 (9), 1472 fecRate1/3 (10), 1473 fecRate1/4 (11), 1474 noInnerCode (12) 1475 } 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "Specifies the inner Forward Error Correction used on the 1480 forward link for transmission to the RCST. 1481 Supported values are: 1482 unknown (-1), 1483 fecRate1/2 (0), 1484 fecRate2/3 (1), 1485 fecRate3/4 (2), 1486 fecRate5/6 (3), 1487 fecRate7/8 (4), 1488 fecRate8/9 (5), 1489 fecRate3/5 (6), 1490 fecRate4/5 (7), 1491 fecRate9/10 (8), 1492 fecRate2/5 (9), 1493 fecRate1/3 (10), 1494 fecRate1/4 (11), 1495 noInnerCode (12) 1496 The RCST will report a value that has been used for transmission 1497 to the RCST within the most recent 60 seconds. 1498 If this is not relevant, the RCST will report 'unknown'." 1499 ::={fwdStatusEntry 8} 1501 fwdStatusSymbolRate OBJECT-TYPE 1502 SYNTAX Integer32 1503 UNITS "x100 symbols/s" 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "An estimate of the symbol rate of the forward link. 1508 Its value shall be given in multiple of 100 symbol/s." 1509 ::={fwdStatusEntry 9} 1511 fwdStatusRolloff OBJECT-TYPE 1512 SYNTAX INTEGER { 1513 undefRolloff (0), 1514 rolloff020 (1), 1515 rolloff025 (2), 1516 rolloff035 (3) 1517 } 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "An estimate of the roll-off applied on the forward link. 1522 Supported values are: 1523 0: undefined 1524 1: 0.20 1525 2: 0.25 1526 3: 0.35" 1528 ::={fwdStatusEntry 10} 1530 fwdStatusModulation OBJECT-TYPE 1531 SYNTAX INTEGER { 1532 unknown (0), 1533 mBPSK (1), 1534 mQPSK (2), 1535 m8PSK (3), 1536 m16APSK (4), 1537 m32APSK (5) 1538 } 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "Indicates the modulation on the forward link used for 1543 transmission to the RCST. 1544 0: unknown 1545 1: BPSK 1546 2: QPSK 1547 3: 8PSK 1548 4: 16APSK 1549 5: 32APSK 1550 The RCST will report a value that has been used for 1551 transmission to the RCST within the most recent 60 seconds. 1552 If this is not relevant, the RCST will report 'unknown'." 1553 ::={fwdStatusEntry 11} 1555 fwdStatusFecFrame OBJECT-TYPE 1556 SYNTAX INTEGER { 1557 unknown (0), 1558 shortframe (1), 1559 longframe (2) 1560 } 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "Indicates the frame length used on the forward link for 1565 transmission to the RCST. 1566 Supported values are: 1567 0: Unknown 1568 1: Short frame 1569 2: Normal frame 1570 The RCST will report a value that has been used for 1571 transmission to the RCST within the most recent 60 seconds. 1572 If this is not relevant, the RCST will report 'unknown'." 1573 ::={fwdStatusEntry 12} 1575 fwdStatusPilot OBJECT-TYPE 1576 SYNTAX INTEGER { 1577 unknown (0), 1578 pilotNotused (1), 1579 pilotUsed (2) 1580 } 1581 MAX-ACCESS read-only 1582 STATUS current 1583 DESCRIPTION 1584 "Indicates whether pilots are used on the forward link for 1585 transmission to the RCST. 1586 Supported values are: 1587 0: Unknown 1588 1: Pilots are not used 1589 2: Pilots are used 1590 The RCST will report a value that has been used for 1591 transmission to the RCST within the most recent 60 seconds. 1592 If this is not relevant, the RCST will report 'unknown'." 1593 ::={fwdStatusEntry 13} 1595 fwdStatusBer OBJECT-TYPE 1596 SYNTAX Integer32 1597 UNITS "exponent of 10" 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "Provides the RCST BER on the Forward Link in log10 units." 1602 ::={fwdStatusEntry 14} 1604 fwdStatusCnr OBJECT-TYPE 1605 SYNTAX Integer32 1606 UNITS "0.1 dB" 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "Provides the RCST CNR on the Forward Link in 0.1 dB units." 1611 ::={fwdStatusEntry 15} 1613 fwdStatusRxPower OBJECT-TYPE 1614 SYNTAX Integer32 1615 UNITS "0.1 dBm" 1616 MAX-ACCESS read-only 1617 STATUS current 1618 DESCRIPTION 1619 "Provides the power level of the Forward Link as received at 1620 the IDU, in 0.1 dBm units." 1621 DEFVAL { -500 } 1622 ::={fwdStatusEntry 16} 1624 fwdStatusRowStatus OBJECT-TYPE 1625 SYNTAX RowStatus 1626 MAX-ACCESS read-only 1627 STATUS current 1628 DESCRIPTION 1629 "Standard SNMP row status" 1630 DEFVAL { active } 1631 ::={fwdStatusEntry 17} 1633 =================================================================== 1634 -- rcstQos sub-tree object types 1635 --=================================================================== 1636 pktClassTable OBJECT-TYPE 1637 SYNTAX SEQUENCE OF PktClassEntry 1638 MAX-ACCESS not-accessible 1639 STATUS current 1640 DESCRIPTION 1641 "This table describes the packet classification used in the 1642 DVB-RCS terminal. The number of entries is specified by 1643 PktClassIndex. " 1644 ::={rcstQos 1} 1646 pktClassEntry OBJECT-TYPE 1647 SYNTAX PktClassEntry 1648 MAX-ACCESS not-accessible 1649 STATUS current 1650 DESCRIPTION 1651 "An entry in the packet classification table. One object type 1652 of each entry may have a value in the active range (a non- 1653 default value).The other object types are then assumed set to 1654 'inactive'. The entry with the lowest index value takes 1655 precedence when classifying a packet." 1656 INDEX { pktClassIndex } 1657 ::= { pktClassTable 1 } 1659 PktClassEntry ::= SEQUENCE { 1660 pktClassIndex Integer32, 1661 pktClassDscpLow Integer32, 1662 pktClassDscpHigh Integer32, 1663 pktClassDscpMarkValue Integer32, 1664 pktClassIPProtocol Integer32, 1665 pktClassIPSrcAddr IpAddress, 1666 pktClassIPSrcAddrMask IpAddress, 1667 pktClassIPDstAddr IpAddress, 1668 pktClassIPDstAddrMask IpAddress, 1669 pktClassSrcPortLow Integer32, 1670 pktClassSrcPortHigh Integer32, 1671 pktClassDstPortLow Integer32, 1672 pktClassDstPortHigh Integer32, 1673 pktClassVlanUserPri Integer32, 1674 pktClassPhbAssociation Integer32, 1675 pktClassRowStatus RowStatus 1676 } 1678 pktClassIndex OBJECT-TYPE 1679 SYNTAX Integer32 (1..64) 1680 MAX-ACCESS not-accessible 1681 STATUS current 1682 DESCRIPTION 1683 "Index automatically incremented by one at row creation." 1684 ::={pktClassEntry 1} 1686 pktClassDscpLow OBJECT-TYPE 1687 SYNTAX Integer32 (0..63) 1689 MAX-ACCESS read-create 1690 STATUS current 1691 DESCRIPTION 1692 "This object specifies the low value of a range of DiffServ 1693 Code Point (DSCP) values to which a packet is compared. 1694 A value of 0 is used to inactivate." 1695 DEFVAL { 0 } 1696 ::={pktClassEntry 2} 1698 pktClassDscpHigh OBJECT-TYPE 1699 SYNTAX Integer32 (0..63) 1700 MAX-ACCESS read-create 1701 STATUS current 1702 DESCRIPTION 1703 "This object specifies the high value of a range of DiffServ 1704 Code Point (DSCP) values to which a packet is compared. 1705 A value of 63 is used to inactivate." 1706 DEFVAL { 63 } 1707 ::={pktClassEntry 3} 1709 pktClassDscpMarkValue OBJECT-TYPE 1710 SYNTAX Integer32 (-1..63) 1711 MAX-ACCESS read-create 1712 STATUS current 1713 DESCRIPTION 1714 "This object is the DiffServ Code Point (DSCP) value used to 1715 mark the packet, -1 indicates no DSCP marking, possible DSCP 1716 marks values are (0..63)" 1717 DEFVAL { -1 } 1718 ::={pktClassEntry 4} 1720 pktClassIPProtocol OBJECT-TYPE 1721 SYNTAX Integer32 (-1..255) 1722 MAX-ACCESS read-create 1723 STATUS current 1724 DESCRIPTION 1725 "This object specifies the IP protocol to which a 1726 packet is compared. A value of 255 indicates inactive." 1727 DEFVAL { -1 } 1728 ::={pktClassEntry 5} 1730 pktClassIPSrcAddr OBJECT-TYPE 1731 SYNTAX IpAddress 1732 MAX-ACCESS read-create 1733 STATUS current 1734 DESCRIPTION 1735 "This object specifies the IP source address to which a 1736 packet is compared." 1737 ::={pktClassEntry 6} 1739 pktClassIPSrcAddrMask OBJECT-TYPE 1740 SYNTAX IpAddress 1741 MAX-ACCESS read-create 1742 STATUS current 1743 DESCRIPTION 1744 "This object specifies which bits of the IP source address 1745 will be matched. A mask of all zeros indicates that the 1746 selectivity is inactive." 1747 DEFVAL { '00000000'H } 1748 ::={pktClassEntry 7} 1750 pktClassIPDstAddr OBJECT-TYPE 1751 SYNTAX IpAddress 1752 MAX-ACCESS read-create 1753 STATUS current 1754 DESCRIPTION 1755 "This object specifies the IP destination address to which a 1756 packet is compared." 1757 ::={pktClassEntry 8} 1759 pktClassIPDstAddrMask OBJECT-TYPE 1760 SYNTAX IpAddress 1761 MAX-ACCESS read-create 1762 STATUS current 1763 DESCRIPTION 1764 "This object specifies which bits of the IP destination 1765 address will be matched. A mask of all zeros indicates that 1766 the selectivity is inactive." 1767 DEFVAL { '00000000'H } 1768 ::={pktClassEntry 9} 1770 pktClassSrcPortLow OBJECT-TYPE 1771 SYNTAX Integer32 (-1..65535) 1772 MAX-ACCESS read-create 1773 STATUS current 1774 DESCRIPTION 1775 "This object specifies the low range of the source 1776 port to which a packet is compared. A value of -1 indicates 1777 that the selectivity is inactive." 1778 DEFVAL { -1 } 1779 ::={pktClassEntry 10} 1781 pktClassSrcPortHigh OBJECT-TYPE 1782 SYNTAX Integer32 (-1..65535) 1783 MAX-ACCESS read-create 1784 STATUS current 1785 DESCRIPTION 1786 "This object specifies the high range of the source 1787 port to which a packet is compared. A value of -1 indicates 1788 that the selectivity is inactive." 1789 DEFVAL { -1 } 1790 ::={pktClassEntry 11} 1792 pktClassDstPortLow OBJECT-TYPE 1793 SYNTAX Integer32 (-1..65535) 1794 MAX-ACCESS read-create 1795 STATUS current 1796 DESCRIPTION 1797 "This object specifies the low range of the destination 1798 port to which a packet is compared. A value of -1 indicates 1799 that the selectivity is inactive." 1800 DEFVAL { -1 } 1801 ::={pktClassEntry 12} 1803 pktClassDstPortHigh OBJECT-TYPE 1804 SYNTAX Integer32 (-1..65535) 1805 MAX-ACCESS read-create 1806 STATUS current 1807 DESCRIPTION 1808 "This object specifies the high range of the destination 1809 port to which a packet is compared. A value of -1 indicates 1810 that the selectivity is inactive." 1811 DEFVAL { -1 } 1812 ::={pktClassEntry 13} 1813 pktClassVlanUserPri OBJECT-TYPE 1814 SYNTAX Integer32 (-1..7) 1815 MAX-ACCESS read-create 1816 STATUS current 1817 DESCRIPTION 1818 "This object specifies the VLAN User Priority to which a packet 1819 is compared. A value of -1 indicates that the selectivity is 1820 inactive." 1821 DEFVAL { -1 } 1822 ::={pktClassEntry 14} 1824 pktClassPhbAssociation OBJECT-TYPE 1825 SYNTAX Integer32 (0..63) 1826 MAX-ACCESS read-create 1827 STATUS current 1828 DESCRIPTION 1829 "Associate the filter entry to a specific PHB (refer to 1830 phbIdentifier)." 1831 ::={pktClassEntry 15} 1833 pktClassRowStatus OBJECT-TYPE 1834 SYNTAX RowStatus 1835 MAX-ACCESS read-create 1836 STATUS current 1837 DESCRIPTION 1838 "Standard SNMP row status" 1839 ::={pktClassEntry 16} 1841 --=================================================================== 1842 -----PhbMappingTable 1843 --=================================================================== 1844 phbMappingTable OBJECT-TYPE 1845 SYNTAX SEQUENCE OF PhbMappingEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "This table is a list of Per-Hop Behaviour (PHB) MIB entries. 1850 It describes the PHB mapping to the Request Class." 1851 ::={rcstQos 2} 1852 phbMappingEntry OBJECT-TYPE 1853 SYNTAX PhbMappingEntry 1854 MAX-ACCESS not-accessible 1855 STATUS current 1856 DESCRIPTION 1857 "An entry in the PHB mapping table." 1858 INDEX { phbIdentifier } 1859 ::= { phbMappingTable 1 } 1861 PhbMappingEntry ::= SEQUENCE { 1862 phbIdentifier Integer32, 1863 phbName DisplayString, 1864 phbRequestClassAssociation Integer32, 1865 phbMappingRowStatus RowStatus 1866 } 1868 phbIdentifier OBJECT-TYPE 1869 SYNTAX Integer32 (0..63) 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "Identification of the Per-Hop Behaviour (PHB) (0..63)." 1874 ::={phbMappingEntry 1} 1876 phbName OBJECT-TYPE 1877 SYNTAX DisplayString 1878 MAX-ACCESS read-create 1879 STATUS current 1880 DESCRIPTION 1881 "The name of the Per-Hop Behaviour (PHB)." 1882 ::={phbMappingEntry 2} 1884 phbRequestClassAssociation OBJECT-TYPE 1885 SYNTAX Integer32 (1..16) 1886 MAX-ACCESS read-create 1887 STATUS current 1888 DESCRIPTION 1889 "This object is an association of this Per-Hop Behaviour 1890 (PHB) to a Request class (by reference to a Request Class 1891 index)." 1892 ::={phbMappingEntry 3} 1893 phbMappingRowStatus OBJECT-TYPE 1894 SYNTAX RowStatus 1895 MAX-ACCESS read-create 1896 STATUS current 1897 DESCRIPTION 1898 "Standard SNMP row status" 1899 DEFVAL { active } 1900 ::={phbMappingEntry 4} 1902 --=================================================================== 1903 -- RequestClassTable 1904 --=================================================================== 1905 requestClassTable OBJECT-TYPE 1906 SYNTAX SEQUENCE OF RequestClassEntry 1907 MAX-ACCESS not-accessible 1908 STATUS current 1909 DESCRIPTION 1910 "This table is a list of Request class entries. This class 1911 describes the layer 2 QoS objects." 1912 ::={rcstQos 3} 1914 requestClassEntry OBJECT-TYPE 1915 SYNTAX RequestClassEntry 1916 MAX-ACCESS not-accessible 1917 STATUS current 1918 DESCRIPTION 1919 "An entry in the Request Class table." 1920 INDEX { requestClassIndex } 1921 ::= { requestClassTable 1 } 1923 RequestClassEntry ::= SEQUENCE { 1924 requestClassIndex Integer32, 1925 requestClassName DisplayString, 1926 requestClassChanId Integer32, 1927 requestClassVccVpi Integer32, 1928 requestClassVccVci Integer32, 1929 requestClassPidPoolReference Integer32, 1930 requestClassCra Integer32, 1931 requestClassRbdcMax Integer32, 1932 requestClassRbdcTimeout Integer32, 1933 requestClassVbdcMax Integer32, 1934 requestClassVbdcTimeout Integer32, 1935 requestClassVbdcMaxBackLog Integer32, 1936 requestClassAvbdcRepTime Integer32, 1937 requestClassRowStatus RowStatus 1938 } 1940 requestClassIndex OBJECT-TYPE 1941 SYNTAX Integer32 (1..16) 1942 MAX-ACCESS not-accessible 1943 STATUS current 1944 DESCRIPTION 1945 "Index of the Request Class table. A total of 16 entries are 1946 supported." 1947 ::={requestClassEntry 1} 1949 requestClassName OBJECT-TYPE 1950 SYNTAX DisplayString 1951 MAX-ACCESS read-write 1952 STATUS current 1953 DESCRIPTION 1954 "Name of the Request Class." 1955 ::={requestClassEntry 2} 1957 requestClassChanId OBJECT-TYPE 1958 SYNTAX Integer32 (0..15) 1959 MAX-ACCESS read-write 1960 STATUS current 1961 DESCRIPTION 1962 "Channel id of the Request Class." 1963 ::={requestClassEntry 3} 1965 requestClassVccVpi OBJECT-TYPE 1966 SYNTAX Integer32 (0..255) 1967 MAX-ACCESS read-write 1968 STATUS current 1969 DESCRIPTION 1970 "Defines VPI used for the Request Class (ATM profile)." 1971 ::={requestClassEntry 4} 1973 requestClassVccVci OBJECT-TYPE 1974 SYNTAX Integer32 (0..65535) 1975 MAX-ACCESS read-write 1976 STATUS current 1977 DESCRIPTION 1978 "Defines VCI used for the Request Class (ATM profile)." 1979 ::={requestClassEntry 5} 1981 requestClassPidPoolReference OBJECT-TYPE 1982 SYNTAX Integer32 (1..16) 1983 MAX-ACCESS read-write 1984 STATUS current 1985 DESCRIPTION 1986 "Reference to the Packet IDentifier (PID) pool applicable 1987 for the Request Class." 1988 ::={requestClassEntry 6} 1990 requestClassCra OBJECT-TYPE 1991 SYNTAX Integer32 1992 UNITS "bits/s" 1993 MAX-ACCESS read-write 1994 STATUS current 1995 DESCRIPTION 1996 "Define Continuous Rate Assignment (CRA) level for the 1997 Request Class in bit per second (b/s)." 1998 ::={requestClassEntry 7} 2000 requestClassRbdcMax OBJECT-TYPE 2001 SYNTAX Integer32 2002 UNITS "x2 kbits/s" 2003 MAX-ACCESS read-write 2004 STATUS current 2005 DESCRIPTION 2006 "Maximum Rate-Based Dynamic Capacity (RBDC) that can be 2007 requested for the Request Class, in number of 2 kbits/s" 2008 ::={requestClassEntry 8} 2010 requestClassRbdcTimeout OBJECT-TYPE 2011 SYNTAX Integer32 2012 UNITS "superframes" 2013 MAX-ACCESS read-write 2014 STATUS current 2015 DESCRIPTION 2016 "Persistence of the Rate-Based Dynamic Capacity (RBDC) 2017 request, expressed in superframes" 2018 ::={requestClassEntry 9} 2020 requestClassVbdcMax OBJECT-TYPE 2021 SYNTAX Integer32 2022 UNITS "ATM cells/MPEG packets" 2023 MAX-ACCESS read-write 2024 STATUS current 2025 DESCRIPTION 2026 "Max Volume-Based Dynamic Capacity (VBDC) that can be 2027 allocated to the Request Class, in payload units (one ATM 2028 cell or one MPEG packet) per superframe" 2029 ::={requestClassEntry 10} 2031 requestClassVbdcTimeout OBJECT-TYPE 2032 SYNTAX Integer32 2033 UNITS "superframes" 2034 MAX-ACCESS read-write 2035 STATUS current 2036 DESCRIPTION 2037 "Time after which the RCST considers that the pending 2038 requests are lost. The RCST may issue new request for that 2039 traffic. Volume-Based Dynamic Capacity (VBDC) Timeout is 2040 expressed in superframes." 2041 ::={requestClassEntry 11} 2043 requestClassVbdcMaxBackLog OBJECT-TYPE 2044 SYNTAX Integer32 2045 UNITS "bytes" 2046 MAX-ACCESS read-write 2047 STATUS current 2048 DESCRIPTION 2049 "Volume-Based Dynamic Capacity (VBDC) back Log per Request 2050 Class. (expressed in bytes)" 2051 ::={requestClassEntry 12} 2053 requestClassAvbdcRepTime OBJECT-TYPE 2054 SYNTAX Integer32 2055 UNITS "superframes" 2056 MAX-ACCESS read-write 2057 STATUS current 2058 DESCRIPTION 2059 "Optional parameter. Absolute Volume-Based Dynamic Capacity 2060 (VBDC) requests can be sent periodically, according to the 2061 value of that parameter, expressed in superframes." 2062 ::={requestClassEntry 13} 2064 requestClassRowStatus OBJECT-TYPE 2065 SYNTAX RowStatus 2066 MAX-ACCESS read-write 2067 STATUS current 2068 DESCRIPTION 2069 "Standard SNMP row status" 2070 DEFVAL { active } 2071 ::={requestClassEntry 14} 2073 --=================================================================== 2074 -- The table of PID pools 2075 --=================================================================== 2077 pidPoolTable OBJECT-TYPE 2078 SYNTAX SEQUENCE OF PidPoolEntry 2079 MAX-ACCESS not-accessible 2080 STATUS current 2081 DESCRIPTION 2082 "This table contains the Packet IDentifier (PID) pools. 2083 For MPEG profile several Request Classes may be mapped 2084 within a pool of several PIDs to allow Section Packing 2085 across Several Request Classes. 2086 A PID value may occur in more than one PID pool. Each PID 2087 value can effectively occur only once in each pool." 2088 ::={rcstQos 4} 2090 pidPoolEntry OBJECT-TYPE 2091 SYNTAX PidPoolEntry 2092 MAX-ACCESS not-accessible 2093 STATUS current 2094 DESCRIPTION 2095 "An entry in the PID list table." 2097 INDEX { pidPoolIndex, pidIndex } 2098 ::= { pidPoolTable 1 } 2100 PidPoolEntry ::= SEQUENCE { 2101 pidPoolIndex Integer32, 2102 pidIndex Integer32, 2103 pidValue Integer32, 2104 pidPoolRowStatus RowStatus 2105 } 2107 pidPoolIndex OBJECT-TYPE 2108 SYNTAX Integer32 (1..16) 2109 MAX-ACCESS not-accessible 2110 STATUS current 2111 DESCRIPTION 2112 "Index of the PID pool in the PID pool table." 2113 ::={pidPoolEntry 1} 2115 pidIndex OBJECT-TYPE 2116 SYNTAX Integer32 (1..16) 2117 MAX-ACCESS not-accessible 2118 STATUS current 2119 DESCRIPTION 2120 "Index of the PID entry within the PID pool." 2121 ::={pidPoolEntry 2} 2123 pidValue OBJECT-TYPE 2124 SYNTAX Integer32 (0..8191) 2125 MAX-ACCESS read-write 2126 STATUS current 2127 DESCRIPTION 2128 "Defines one of the PIDs to be used in a PID pool of 2129 pidPoolIndex. 2130 A PID value may occur in more than one PID pool. Each PID 2131 value can effectively occur only once in each pool." 2132 ::={pidPoolEntry 3} 2134 pidPoolRowStatus OBJECT-TYPE 2135 SYNTAX RowStatus 2136 MAX-ACCESS read-write 2137 STATUS current 2138 DESCRIPTION 2139 "Standard SNMP row status" 2140 DEFVAL { active } 2141 ::={pidPoolEntry 4} 2143 qosGlobalRbdcMax OBJECT-TYPE 2144 SYNTAX Integer32 2145 UNITS "x2 kbits/s" 2146 MAX-ACCESS read-write 2147 STATUS current 2148 DESCRIPTION 2149 "The global RBDC max is for information only and it is 2150 optional (expressed in number of 2 kbits/s)." 2151 ::={rcstQos 5} 2153 qosGlobalVbdcMax OBJECT-TYPE 2154 SYNTAX Integer32 2155 UNITS "ATM cells/MPEG packets" 2156 MAX-ACCESS read-write 2157 STATUS current 2158 DESCRIPTION 2159 "The global VBDC max is for information only and it is 2160 optional.(expressed in payload units/superframe)" 2161 ::={rcstQos 6} 2163 qosGlobalVbdcMaxBackLog OBJECT-TYPE 2164 SYNTAX Integer32 2165 UNITS "bytes" 2166 MAX-ACCESS read-write 2167 STATUS current 2168 DESCRIPTION 2169 "The global VBDC back log is used only if the VBDC back log 2170 is not configured in the Request class (expressed in 2171 bytes)." 2172 ::={rcstQos 7} 2174 qosGlobalAvbdcRepTime OBJECT-TYPE 2175 SYNTAX Integer32 2176 UNITS "superframes" 2177 MAX-ACCESS read-write 2178 STATUS current 2179 DESCRIPTION 2180 "The global AVBDC repetition time is optional (expressed in 2181 superframes)." 2182 ::={rcstQos 8} 2184 qosChannelIdStrictDispatching OBJECT-TYPE 2185 SYNTAX INTEGER { 2186 notStrict (0), 2187 strict (1) 2188 } 2189 MAX-ACCESS read-write 2190 STATUS current 2191 DESCRIPTION 2192 "Indicates whether the RCST will strictly follow RC 2193 association when signaled through Channel_ID in the TBTP: 2194 No strict association (0) 2195 Strict association (1)" 2196 ::={rcstQos 9} 2198 --=================================================================== 2199 -- rcstState sub-tree object types 2200 --=================================================================== 2201 rcstMode OBJECT-TYPE 2202 SYNTAX INTEGER { 2203 installation (0), 2204 operational (1) 2205 } 2206 MAX-ACCESS read-write 2207 STATUS current 2208 DESCRIPTION 2209 "Identifies the current mode of the RCST is and allows it to 2210 return to the installation mode when needed. Values for the 2211 RCST mode are: 2212 Installation (0) 2213 Operational (1)" 2214 ::={rcstState 1} 2216 rcstFaultStatus OBJECT-TYPE 2217 SYNTAX INTEGER { 2218 nofault (0), 2219 fault (1) 2220 } 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "Provide the fault status of the terminal. The fault status 2225 management is vendor specific. Values for the Fault Status 2226 are: 2227 no fault (0) 2228 fault (1)" 2229 ::={rcstState 2} 2231 rcstFwdLinkStatus OBJECT-TYPE 2232 SYNTAX INTEGER { 2233 notAcquired (0), 2234 acquired (1) 2235 } 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "Provides the status of the RCST Forward Link. Values for the 2240 Forward Link Status are: 2241 Not acquired (0) 2242 Acquired (1)" 2243 ::={rcstState 3} 2245 rcstRtnLinkStatus OBJECT-TYPE 2246 SYNTAX INTEGER { 2247 loggedOff (0), 2248 loggedOn (1) 2249 } 2250 MAX-ACCESS read-only 2251 STATUS current 2252 DESCRIPTION 2253 "Provides the status of the RCST Return Link. Values for the 2254 Return Link Status are: 2255 Logged-off (0) 2256 Logged-on (1)" 2257 ::={rcstState 4} 2259 rcstLogUpdated OBJECT-TYPE 2260 SYNTAX INTEGER { 2261 noUpdate (0), 2262 logfileUpdated (1) 2263 } 2264 MAX-ACCESS read-only 2265 STATUS current 2266 DESCRIPTION 2267 "Indicates the existence of an updated event log file: 2268 No update (0) 2269 Event Log file updated (1) 2270 The RCST should remove the Event Log file updated indication 2271 as the log file is fetched by the NCC." 2272 ::={rcstState 5} 2274 rcstCurrentSoftwareVersion OBJECT-TYPE 2275 SYNTAX DisplayString 2276 MAX-ACCESS read-only 2277 STATUS current 2278 DESCRIPTION 2279 "Current RCST software version." 2280 ::={rcstState 6} 2282 rcstAlternateSoftwareVersion OBJECT-TYPE 2283 SYNTAX DisplayString 2284 MAX-ACCESS read-only 2285 STATUS current 2286 DESCRIPTION 2287 "Alternate (backup/new) RCST software version." 2288 ::={rcstState 7} 2290 rcstActivatedConfigFileVersion OBJECT-TYPE 2291 SYNTAX DisplayString 2292 MAX-ACCESS read-only 2293 STATUS current 2294 DESCRIPTION 2295 "Version of the most recently activated configuration file. 2296 The version is vendor specific." 2297 ::={rcstState 8} 2299 rcstDownloadedConfigFileVersion OBJECT-TYPE 2300 SYNTAX DisplayString 2301 MAX-ACCESS read-only 2302 STATUS current 2303 DESCRIPTION 2304 "Version of the most recently downloaded configuration file. 2305 Version is vendor specific. If the value is different from 2306 rcstActivatedConfigFileVersion, it is pending for activation." 2307 ::={rcstState 9} 2309 --=================================================================== 2310 -- rcstControl sub-tree object types 2311 --=================================================================== 2312 ctrlRebootCommand OBJECT-TYPE 2313 SYNTAX INTEGER { 2314 idle (1), 2315 normal (2), 2316 alternate (3) 2317 } 2318 MAX-ACCESS read-write 2319 STATUS current 2320 DESCRIPTION 2321 "This variable shall force the RCST to reboot 2322 (1)- idle 2323 (2)- normal reboot (from current software load) 2324 (3)- reboot from alternate load (swap to alternate load 2325 before reboot)" 2326 DEFVAL {1} 2327 ::={rcstControl 1} 2329 ctrlRcstTxDisable OBJECT-TYPE 2330 SYNTAX INTEGER { 2331 idle (1), 2332 disable (2) 2333 } 2334 MAX-ACCESS read-write 2335 STATUS current 2336 DESCRIPTION 2337 "This variable shall force the RCST to stop transmission 2338 (transmit disabled as defined in SatLabs System 2339 Recommendations): 2340 (1)- idle 2341 (2)- initiate Tx Disabled" 2343 DEFVAL {1} 2344 ::={rcstControl 2} 2346 ctrlUserTrafficDisable OBJECT-TYPE 2347 SYNTAX INTEGER { 2348 idle (1), 2349 disable (2) 2350 } 2351 MAX-ACCESS read-write 2352 STATUS current 2353 DESCRIPTION 2354 "This variable shall disable user traffic (only RCST 2355 management traffic can be transmitted) 2356 (1)- idle 2357 (2)- disable user traffic" 2358 DEFVAL {1} 2359 ::={rcstControl 3} 2361 ctrlCwEnable OBJECT-TYPE 2362 SYNTAX INTEGER { 2363 off (1), 2364 on (2) 2365 } 2366 MAX-ACCESS read-write 2367 STATUS current 2368 DESCRIPTION 2369 "This variable will force the RCST to start transmission of 2370 CW, if the RCST is first set to the installation state, and 2371 is properly configured for CW transmission: 2372 (1)- off 2373 (2)- on" 2374 DEFVAL {1} 2375 ::={rcstControl 4} 2377 ctrlOduTxReferenceEnable OBJECT-TYPE 2378 SYNTAX INTEGER { 2379 off (1), 2380 on (2) 2381 } 2382 MAX-ACCESS read-write 2383 STATUS current 2384 DESCRIPTION 2385 "Enables activation and deactivation of 10 MHz reference 2386 clock in the Tx IFL cable: 2387 (1) off 2388 (2) on" 2389 DEFVAL {2} 2390 ::={rcstControl 5} 2392 ctrlOduTxDCEnable OBJECT-TYPE 2393 SYNTAX INTEGER { 2394 off (1), 2395 on (2) 2396 } 2397 MAX-ACCESS read-write 2398 STATUS current 2399 DESCRIPTION 2400 "Enables activation and deactivation of DC in the Tx IFL 2401 cable: 2402 (1) off 2403 (2) on" 2404 DEFVAL {2} 2405 ::={rcstControl 6} 2407 ctrlOduRxDCEnable OBJECT-TYPE 2408 SYNTAX INTEGER { 2409 off (1), 2410 on (2) 2411 } 2412 MAX-ACCESS read-write 2413 STATUS current 2414 DESCRIPTION 2415 "Enables activation and deactivation of DC in the Rx IFL 2416 cable: 2417 (1) off 2418 (2) on" 2419 DEFVAL {2} 2420 ::={rcstControl 7} 2422 ctrlDownloadFileCommand OBJECT-TYPE 2423 SYNTAX INTEGER { 2424 idle (1), 2425 config (2), 2426 installationLog (3) 2427 } 2428 MAX-ACCESS read-write 2429 STATUS current 2430 DESCRIPTION 2431 "This variable will initiate a RCST configuration file 2432 download process 2433 (1) idle 2434 (2) download RCST configuration file from TFTP/FTP server 2435 (3) download RCST installation log file from TFTP/FTP server 2436 (INSTALL_LOG Option)" 2437 DEFVAL {1} 2438 ::={rcstControl 8} 2440 ctrlUploadFileCommand OBJECT-TYPE 2441 SYNTAX INTEGER { 2442 idle (1), 2443 config (2), 2444 eventAlarm (3), 2445 installationLog (4) 2446 } 2447 MAX-ACCESS read-write 2448 STATUS current 2449 DESCRIPTION 2450 "This variable will initiate a RCST upload process 2451 (1) idle 2452 (2) upload RCST configuration file to TFTP/FTP server 2453 (3) upload RCST event/alarm log file to TFTP/FTP server 2454 (4) upload RCST installation log file to TFTP/FTP server 2455 (INSTALL_LOG Option)" 2456 DEFVAL {1} 2457 ::={rcstControl 9} 2459 ctrlActivateConfigFileCommand OBJECT-TYPE 2460 SYNTAX INTEGER { 2461 idle (1), 2462 activate (2) 2463 } 2464 MAX-ACCESS read-write 2465 STATUS current 2466 DESCRIPTION 2467 "Triggers the RCST to use the configuration file and update 2468 its parameters accordingly. Some RCST implementations may 2469 require a reboot for the parameters to take effect (vendor 2470 specific). 2471 (1) Idle 2472 (2) activate" 2473 DEFVAL {1} 2474 ::={rcstControl 10} 2476 ctrlRcstLogonCommand OBJECT-TYPE 2477 SYNTAX INTEGER { 2478 idle (1), 2479 logon (2) 2480 } 2481 MAX-ACCESS read-write 2482 STATUS current 2483 DESCRIPTION 2484 "This variable will initiate a RCST logon 2485 (1) idle 2486 (2) initiate RCST logon" 2487 DEFVAL {1} 2488 ::={rcstControl 11} 2490 ctrlRcstLogoffCommand OBJECT-TYPE 2491 SYNTAX INTEGER { 2492 idle (1), 2493 logoff (2) 2494 } 2495 MAX-ACCESS read-write 2496 STATUS current 2497 DESCRIPTION 2498 "This variable will initiate a RCST logoff 2499 (1) idle 2500 (2) initiate RCST logoff" 2501 DEFVAL {1} 2502 ::={rcstControl 12} 2504 --================================================================== 2505 -- conformance information 2506 --================================================================== 2507 rcstGroups OBJECT IDENTIFIER ::= {dvbrcsConformance 1} 2508 rcstCompliances OBJECT IDENTIFIER ::= {dvbrcsConformance 2} 2510 --================================================================== 2511 -- conformance statements 2512 --================================================================== 2513 rcstCompliance1 MODULE-COMPLIANCE 2514 STATUS current 2515 DESCRIPTION 2516 "The compliance statement for DVB-RCS terminals that are 2517 compliant with SatLabs System Recommendations version 2." 2519 MODULE -- this module 2521 MANDATORY-GROUPS {rcstSystemGroup, rcstInstallGroup, 2522 rcstNetworkGroup, rtnConfigGroup, fwdConfigGroup, fwdStatusGroup, 2523 rcstQosGroup, rcstStateGroup, rcstControlGroup} 2525 GROUP rcstExtSystemGroup 2526 DESCRIPTION "This group is mandatory for an RCST 2527 that claims to support the SNMPALL option." 2529 GROUP rcstExtNetworkGroup 2530 DESCRIPTION "This group is mandatory for an RCST 2531 that claims to support the SNMPALL option." 2533 GROUP rcstExtInstallGroup 2534 DESCRIPTION "This group is mandatory for an RCST 2535 that claims to support the INSTALL_LOG option." 2537 GROUP rcstDnsGroup 2538 DESCRIPTION "This group is mandatory for an RCST 2539 that claims to support the DNS option." 2541 GROUP rtnExtConfigGroup 2542 DESCRIPTION "This group is mandatory for an RCST 2543 that claims to support the SNMPALL option." 2545 GROUP fwdExtStatusGroup 2546 DESCRIPTION "This group is mandatory for an RCST 2547 that claims to support the FWDLINKSTATUS option." 2548 GROUP rcstEnhancedClassifierGroup 2549 DESCRIPTION "This group is mandatory for an RCST 2550 that claims to support the ENHCLASSIFIER option." 2552 GROUP rcstMpegQosGroup 2553 DESCRIPTION "This group is mandatory for an RCST 2554 that claims to support the MPEG option." 2556 GROUP rcstAvbdcRepQosGroup 2557 DESCRIPTION "This group is mandatory for an RCST 2558 that claims to support the AVBDC_REP option." 2560 GROUP rcstGlobalQosGroup 2561 DESCRIPTION "This group is mandatory for an RCST 2562 that claims to support the RCST_PARA option." 2564 GROUP rcstGlobalAvbdcRepQosGroup 2565 DESCRIPTION "This group is mandatory for an RCST 2566 that claims to support both the RCST_PARA option 2567 and the AVBDC_REP option." 2569 GROUP rcstStrictQosGroup 2570 DESCRIPTION "This group is mandatory for an RCST 2571 that claims to support the CHID_STRICT option." 2573 GROUP rtnStatusGroup 2574 DESCRIPTION "This group is mandatory for an RCST 2575 that claims to support the SNMPALL option." 2577 GROUP rcstExtControlGroup 2578 DESCRIPTION "This group is mandatory for an RCST 2579 that claims to support the SNMPALL option." 2581 OBJECT systemOduTxType 2582 MIN-ACCESS read-only 2583 DESCRIPTION "Write access required if the RCST does 2584 not provide the information." 2586 OBJECT systemOduRxType 2587 MIN-ACCESS read-only 2588 DESCRIPTION "Write access required if the RCST does 2589 not provide the information." 2591 OBJECT networkLanIpAddress 2592 MIN-ACCESS read-only 2593 DESCRIPTION "Write access only required if SNMPALL 2594 support is claimed." 2596 OBJECT networkLanIpMask 2597 MIN-ACCESS read-only 2598 DESCRIPTION "Write access only required if SNMPALL 2599 support is claimed." 2601 OBJECT pktClassDscpLow 2602 MIN-ACCESS read-only 2603 DESCRIPTION "Create access only required if 2604 ENHCLASSIFIER support is claimed." 2606 OBJECT pktClassDscpHigh 2607 MIN-ACCESS read-only 2608 DESCRIPTION "Create access only required if 2609 ENHCLASSIFIER support is claimed." 2611 OBJECT pktClassDscpMarkValue 2612 MIN-ACCESS read-only 2613 DESCRIPTION "Create access only required if 2614 ENHCLASSIFIER support is claimed." 2616 OBJECT phbIdentifier 2617 MIN-ACCESS read-only 2618 DESCRIPTION "Create access only required if SNMPALL 2619 support is claimed." 2621 OBJECT phbName 2622 MIN-ACCESS read-only 2623 DESCRIPTION "Create access only required if SNMPALL 2624 support is claimed." 2626 OBJECT phbRequestClassAssociation 2627 MIN-ACCESS read-only 2628 DESCRIPTION "Create access only required if SNMPALL 2629 support is claimed." 2631 OBJECT phbMappingRowStatus 2632 MIN-ACCESS read-only 2633 DESCRIPTION "Create access only required if SNMPALL 2634 support is claimed." 2636 OBJECT requestClassName 2637 MIN-ACCESS read-only 2638 DESCRIPTION "Write access only required if SNMPALL 2639 support is claimed." 2641 OBJECT requestClassChanId 2642 MIN-ACCESS read-only 2643 DESCRIPTION "Write access only required if SNMPALL 2644 support is claimed." 2646 OBJECT requestClassVccVpi 2647 MIN-ACCESS read-only 2648 DESCRIPTION "Write access only required if SNMPALL 2649 support is claimed." 2651 OBJECT requestClassVccVci 2652 MIN-ACCESS read-only 2653 DESCRIPTION "Write access only required if SNMPALL 2654 support is claimed." 2656 OBJECT requestClassPidPoolReference 2657 MIN-ACCESS not-accessible 2658 DESCRIPTION "Read-only access required if MPEG option 2659 is claimed. Write access only required if also SNMPALL 2660 support is claimed." 2662 OBJECT requestClassCra 2663 MIN-ACCESS read-only 2664 DESCRIPTION "Write access only required if SNMPALL 2665 support is claimed." 2667 OBJECT requestClassRbdcMax 2668 MIN-ACCESS read-only 2669 DESCRIPTION "Write access only required if SNMPALL 2670 support is claimed." 2672 OBJECT requestClassRbdcTimeout 2673 MIN-ACCESS read-only 2674 DESCRIPTION "Write access only required if SNMPALL 2675 support is claimed." 2677 OBJECT requestClassVbdcMax 2678 MIN-ACCESS read-only 2679 DESCRIPTION "Write access only required if SNMPALL 2680 support is claimed." 2682 OBJECT requestClassVbdcTimeout 2683 MIN-ACCESS read-only 2684 DESCRIPTION "Write access only required if SNMPALL 2685 support is claimed." 2687 OBJECT requestClassVbdcMaxBackLog 2688 MIN-ACCESS read-only 2689 DESCRIPTION "Write access only required if SNMPALL 2690 support is claimed." 2692 OBJECT requestClassRowStatus 2693 MIN-ACCESS read-only 2694 DESCRIPTION "Write access only required if SNMPALL 2695 support is claimed." 2697 OBJECT pidValue 2698 MIN-ACCESS not-accessible 2699 DESCRIPTION "Read-only access required if MPEG option 2700 is claimed. Write access only required if also SNMPALL 2701 support is claimed." 2703 OBJECT pidPoolRowStatus 2704 MIN-ACCESS not-accessible 2705 DESCRIPTION "Read-only access required if MPEG option 2706 is claimed. Write access only required if also SNMPALL 2707 support is claimed." 2709 ::= { rcstCompliances 1 } 2710 =================================================================== 2711 -- units of conformance 2712 -- 2713 ==================================================================== 2715 =================================================================== 2716 -- object groups for rcst system 2717 --=================================================================== 2718 rcstSystemGroup OBJECT-GROUP 2719 OBJECTS { 2720 systemMibRevision, 2721 systemLocation, 2722 systemOduTxType, 2723 systemOduRxType, 2724 systemSatlabsOptions 2725 } 2726 STATUS current 2727 DESCRIPTION "A collection of objects providing information 2728 applicable for basic device management support." 2729 ::= { rcstGroups 1 } 2731 rcstExtSystemGroup OBJECT-GROUP 2732 OBJECTS { 2733 systemOduAntennaSize, 2734 systemOduAntennaGain, 2735 systemOduSspa, 2736 systemOduRxBand, 2737 systemOduRxLO, 2738 systemOduTxLO, 2739 installCwPower 2740 } 2741 STATUS current 2742 DESCRIPTION "A collection of objects providing information 2743 applicable for extended device management support." 2744 ::= { rcstGroups 2 } 2746 ==================================================================== 2747 -- object groups for rcst installation 2748 -- 2749 ==================================================================== 2750 rcstInstallGroup OBJECT-GROUP 2751 OBJECTS { 2752 installAntennaAlignmentState, 2753 installCwFrequency, 2754 installCwMaxDuration, 2755 installCoPolReading, 2756 installXPolReading, 2757 installCoPolTarget, 2758 installXPolTarget, 2759 installStandByDuration, 2760 installTargetEsN0 2761 } 2762 STATUS current 2763 DESCRIPTION "A collection of objects providing information 2764 applicable for basic installation support." 2765 ::= { rcstGroups 3 } 2767 rcstExtInstallGroup OBJECT-GROUP 2768 OBJECTS { 2769 networkInstallLogFileDownloadUrl, 2770 networkInstallLogFileUploadUrl 2771 } 2772 STATUS current 2773 DESCRIPTION "A collection of objects providing extended 2774 device installation support." 2775 ::= { rcstGroups 4 } 2777 ==================================================================== 2778 -- object groups for rcst networking 2779 -- 2780 ==================================================================== 2781 rcstNetworkGroup OBJECT-GROUP 2782 OBJECTS { 2783 networkOamIpAddr, 2784 networkOamIpNetworkMask, 2785 networkLanIpAddress, 2786 networkLanIpMask, 2787 networkConfigFileDownloadUrl, 2788 networkConfigFileUploadUrl, 2789 networkLogFileUploadUrl 2790 } 2791 STATUS current 2792 DESCRIPTION "A collection of objects providing basic 2793 networking management support." 2794 ::= { rcstGroups 5 } 2796 rcstExtNetworkGroup OBJECT-GROUP 2797 OBJECTS { 2798 networkOamIpAddrAssign, 2799 networkAirInterfaceDefaultGateway, 2800 networkNccMgtIpAddress 2801 } 2802 STATUS current 2803 DESCRIPTION "A collection of objects providing extended 2804 networking management support." 2805 ::= { rcstGroups 6 } 2807 rcstDnsGroup OBJECT-GROUP 2808 OBJECTS { 2809 networkDnsServerIpAddress 2810 } 2811 STATUS current 2812 DESCRIPTION "IP address of the DNS server to be used to 2813 resolve URL's as needed." 2814 ::= { rcstGroups 7 } 2816 ================================================================== 2817 -- object groups for return link 2818 -- 2819 ================================================================== 2821 rtnConfigGroup OBJECT-GROUP 2822 OBJECTS { 2823 rtnConfigDefIfLevel 2824 } 2825 STATUS current 2826 DESCRIPTION "A collection of objects providing basic return 2827 link configuration support." 2828 ::= { rcstGroups 8 } 2830 rtnExtConfigGroup OBJECT-GROUP 2831 OBJECTS { 2832 rtnConfigMaxEirp 2833 } 2834 STATUS current 2835 DESCRIPTION "A collection of objects providing extended 2836 return link configuration support." 2837 ::= { rcstGroups 9 } 2839 rtnStatusGroup OBJECT-GROUP 2840 OBJECTS { 2841 rcstRtnLinkStatus, 2842 rtnStatusEbN0, 2843 rtnStatusSFDuration, 2844 rtnStatusPayloadUnit 2845 } 2846 STATUS current 2847 DESCRIPTION "A collection of objects allowing access to return 2848 link status." 2849 ::= { rcstGroups 10 } 2851 ================================================================== 2852 -- object groups for forward link 2853 -- 2854 ================================================================== 2856 fwdConfigGroup OBJECT-GROUP 2857 OBJECTS { 2858 fwdStartPopId, 2859 fwdStartFrequency, 2860 fwdStartPolar, 2861 fwdStartFormat, 2862 fwdStartRolloff, 2863 fwdStartSymbolRate, 2864 fwdStartInnerFec, 2865 fwdStartRowStatus 2866 } 2867 STATUS current 2868 DESCRIPTION "A collection of objects providing basic start 2869 forward link configuration support." 2870 ::= { rcstGroups 11 } 2871 fwdStatusGroup OBJECT-GROUP 2872 OBJECTS { 2873 fwdStatusPopId, 2874 fwdStatusIfReference, 2875 fwdStatusNetId, 2876 fwdStatusNetName, 2877 fwdStatusCnr, 2878 fwdStatusRowStatus 2879 } 2880 STATUS current 2881 DESCRIPTION "A collection of objects providing basic forward 2882 link status." 2883 ::= { rcstGroups 12 } 2885 fwdExtStatusGroup OBJECT-GROUP 2886 OBJECTS { 2887 fwdStatusFormat, 2888 fwdStatusFrequency, 2889 fwdStatusPolar, 2890 fwdStatusInnerFec, 2891 fwdStatusSymbolRate, 2892 fwdStatusRolloff, 2893 fwdStatusModulation, 2894 fwdStatusFecFrame, 2895 fwdStatusPilot, 2896 fwdStatusBer, 2897 fwdStatusRxPower, 2898 rcstFwdLinkStatus 2899 } 2900 STATUS current 2901 DESCRIPTION "A collection of objects providing extended 2902 forward link status." 2903 ::= { rcstGroups 13 } 2905 ================================================================== 2906 -- object groups for QOS 2907 -- 2908 ================================================================== 2910 rcstQosGroup OBJECT-GROUP 2911 OBJECTS { 2912 pktClassPhbAssociation, 2913 pktClassDscpLow, 2914 pktClassDscpHigh, 2915 pktClassDscpMarkValue, 2916 pktClassRowStatus, 2917 phbIdentifier, 2918 phbName, 2919 phbRequestClassAssociation, 2920 phbMappingRowStatus, 2921 requestClassName, 2922 requestClassChanId, 2923 requestClassVccVpi, 2924 requestClassVccVci, 2925 requestClassCra, 2926 requestClassRbdcMax, 2927 requestClassRbdcTimeout, 2928 requestClassVbdcMax, 2929 requestClassVbdcTimeout, 2930 requestClassVbdcMaxBackLog, 2931 requestClassRowStatus 2932 } 2933 STATUS current 2934 DESCRIPTION "A collection of objects providing basic access to 2935 QOS configuration data." 2936 ::= { rcstGroups 14 } 2938 rcstEnhancedClassifierGroup OBJECT-GROUP 2939 OBJECTS { 2940 pktClassIPProtocol, 2941 pktClassIPSrcAddr, 2942 pktClassIPSrcAddrMask, 2943 pktClassIPDstAddr, 2944 pktClassIPDstAddrMask, 2945 pktClassSrcPortLow, 2946 pktClassSrcPortHigh, 2947 pktClassDstPortLow, 2948 pktClassDstPortHigh, 2949 pktClassVlanUserPri 2950 } 2951 STATUS current 2952 DESCRIPTION "A collection of objects providing support for 2953 management of the enhanced classifier." 2954 ::= { rcstGroups 15 } 2956 rcstMpegQosGroup OBJECT-GROUP 2957 OBJECTS { 2958 requestClassPidPoolReference, 2959 pidValue, 2960 pidPoolRowStatus 2961 } 2962 STATUS current 2963 DESCRIPTION "A collection of objects providing access to MPEG 2964 related link QOS configuration data." 2965 ::= { rcstGroups 16 } 2967 rcstAvbdcRepQosGroup OBJECT-GROUP 2968 OBJECTS { 2969 requestClassAvbdcRepTime 2970 } 2971 STATUS current 2972 DESCRIPTION "A collection of objects providing access to 2973 AVDBC repeat related QOS configuration data." 2974 ::= { rcstGroups 17 } 2976 rcstGlobalQosGroup OBJECT-GROUP 2977 OBJECTS { 2978 qosGlobalRbdcMax, 2979 qosGlobalVbdcMax, 2980 qosGlobalVbdcMaxBackLog 2981 } 2982 STATUS current 2983 DESCRIPTION "A collection of objects providing access to 2984 global RCST QOS configuration data." 2985 ::= { rcstGroups 18 } 2987 rcstGlobalAvbdcRepQosGroup OBJECT-GROUP 2988 OBJECTS { 2989 qosGlobalAvbdcRepTime 2990 } 2991 STATUS current 2992 DESCRIPTION "A collection of objects providing access to 2993 global AVDBC repeat related QOS configuration data." 2995 ::= { rcstGroups 19 } 2997 rcstStrictQosGroup OBJECT-GROUP 2998 OBJECTS { 2999 qosChannelIdStrictDispatching 3000 } 3001 STATUS current 3002 DESCRIPTION "A collection of objects allowing management of 3003 strict channel ID dispatching." 3004 ::= { rcstGroups 20 } 3006 ================================================================== 3007 -- object groups for rcst state 3008 -- 3009 ================================================================== 3011 rcstStateGroup OBJECT-GROUP 3012 OBJECTS { 3013 rcstMode, 3014 rcstFaultStatus, 3015 rcstLogUpdated, 3016 rcstCurrentSoftwareVersion, 3017 rcstAlternateSoftwareVersion, 3018 rcstActivatedConfigFileVersion, 3019 rcstDownloadedConfigFileVersion 3020 } 3021 STATUS current 3022 DESCRIPTION "A collection of objects allowing access to RCST 3023 state." 3024 ::= { rcstGroups 21 } 3026 ================================================================== 3027 -- object groups for rcst control 3028 --================================================================== 3029 rcstControlGroup OBJECT-GROUP 3030 OBJECTS { 3031 ctrlRebootCommand, 3032 ctrlUserTrafficDisable, 3033 ctrlCwEnable, 3034 ctrlDownloadFileCommand, 3035 ctrlUploadFileCommand, 3036 ctrlActivateConfigFileCommand 3037 } 3038 STATUS current 3039 DESCRIPTION "A collection of objects allowing basic RCST 3040 control." 3041 ::= { rcstGroups 22 } 3043 rcstExtControlGroup OBJECT-GROUP 3044 OBJECTS { 3045 ctrlRcstTxDisable, 3046 ctrlOduTxReferenceEnable, 3047 ctrlOduTxDCEnable, 3048 ctrlOduRxDCEnable, 3049 ctrlRcstLogonCommand, 3050 ctrlRcstLogoffCommand 3051 } 3052 STATUS current 3053 DESCRIPTION "A collection of objects allowing extended RCST 3054 control." 3055 ::= { rcstGroups 23 } 3057 END 3059 4. Security Considerations 3061 Some of the readable objects in this MIB module (i.e., objects with a 3062 MAX-ACCESS other than not-accessible) may be considered sensitive or 3063 vulnerable in some network environments. 3065 SNMP versions prior to SNMPv3 did not include adequate security. Even 3066 if the network itself is secure (for example by using IPsec), even 3067 then, there is no control as to who on the secure network is allowed 3068 to access and GET/SET (read/change/create/delete) the objects in this 3069 MIB module. 3071 It is RECOMMENDED that implementers consider the security features 3072 provided by the SNMPv3 framework (see [RFC3410], section 8), 3073 including full support for the SNMPv3 cryptographic mechanisms (for 3074 authentication and privacy). 3076 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3077 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3078 enable cryptographic security. It is then a customer/operator 3079 responsibility to ensure that the SNMP entity giving access to an 3080 instance of this MIB module, is properly configured to give access to 3081 the objects only to those principals (users) that have legitimate 3082 rights to indeed GET or SET (change/create/delete) them. 3084 5. IANA Considerations 3086 This document includes no request to IANA. The assignment described 3087 in Section 2.2 has already been assigned under the smi-numbers 3088 registry. 3090 6. Acknowledgments 3092 The authors thank Gorry Fairhurst for advice in the preparation of 3093 this document. 3095 The authors recognize this document is a collective effort of the 3096 SatLabs Group (www.satlabs.org). 3098 7. References 3100 7.1. Normative References 3102 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3103 Requirement Levels", BCP 14, RFC 2119, March 1997 (BEST 3104 CURRENT PRACTICE). 3106 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3107 Schoenwaelder, Ed., "Structure of Management Information, 3108 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3110 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3111 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3112 STD 58, RFC 2579, April 1999. 3114 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3115 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 3116 1999. 3118 7.2. Informative References 3120 [ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology; 3121 Generic Coding of Moving Pictures and Associated Audio 3122 Information Systems", International Standardisation 3123 Organisation (ISO). 3125 [ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB 3126 Specifications for Data Broadcasting", European 3127 Telecommunications Standards Institute (ETSI). 3129 [ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); Modulation 3130 and Coding for DBS satellite systems at 11/12 GHz", 3131 European Telecommunications Standards Institute (ETSI). 3133 [ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB); 3134 Second generation framing structure, channel coding and 3135 modulation systems for Broadcasting, Interactive Services, 3136 News Gathering and other broadband satellite applications", 3137 European Telecommunications Standards Institute (ETSI). 3139 [ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB); 3140 Interaction Channel for Satellite Distribution Systems", 3141 European Telecommunications Standards Institute (ETSI). 3143 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3144 "Introduction and Applicability Statements for Internet- 3145 Standard Management Framework", RFC 3410, December 2002. 3147 [RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- 3148 Nocker, B., and H. Linder, "A Framework for Transmission of 3149 IP Datagrams over MPEG-2 Networks", RFC 4259, November 3150 2005. 3152 [SATLABS] SatLabs System Recommendations, version 2, December 3153 2006. Available at www.satlabs.org. 3155 8. Authors' Addresses 3157 Stephane Combes 3158 ESTEC 3159 European Space Agency 3160 Keplerlaan 1 - P.O. Box 299 3161 2200 AG Noordwijk ZH 3162 The Netherlands 3164 Email: stephane.combes@esa.int 3165 URL: telecom.esa.int 3167 Petter Chr. Amundsen 3168 VeriSat AS 3169 P.O Box 1 3170 1330 Fornebu 3171 Norway 3173 Email: pca@verisat.no 3174 URL: www.verisat.no 3176 Micheline Lambert 3177 Advantech Satellite Networks 3178 2341 boul. Alfred-Nobel 3179 Saint-Laurent (Montreal,)H4S 2A9 3180 Quebec, Canada 3182 Email: micheline.lambert@advantechamt.com 3183 URL: www.advantechsatnet.com 3184 Hans-Peter Lexow 3185 STM Norway 3186 Vollsveien 21 3187 1366 Lysaker 3188 Norway 3190 Email: hlexow@stmi.com 3191 URL: www.stmi.com 3193 9. Intellectual Property Statement 3195 The IETF takes no position regarding the validity or scope of any 3196 Intellectual Property Rights or other rights that might be claimed to 3197 pertain to the implementation or use of the technology described in 3198 this document or the extent to which any license under such rights 3199 might or might not be available; nor does it represent that it has 3200 made any independent effort to identify any such rights. Information 3201 on the procedures with respect to rights in RFC documents can be 3202 found in BCP 78 and BCP 79. 3204 Copies of IPR disclosures made to the IETF Secretariat and any 3205 assurances of licenses to be made available, or the result of an 3206 attempt made to obtain a general license or permission for the use of 3207 such proprietary rights by implementers or users of this 3208 specification can be obtained from the IETF on-line IPR repository at 3209 http://www.ietf.org/ipr. 3211 The IETF invites any interested party to bring to its attention any 3212 copyrights, patents or patent applications, or other proprietary 3213 rights that may cover technology that may be required to implement 3214 this standard. Please address the information to the IETF at 3215 ietf-ipr@ietf.org. 3217 10. Disclaimer of Validity 3219 This document and the information contained herein are provided on an 3220 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3221 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3222 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3223 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3224 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3225 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3227 11. Copyright Statement 3229 Copyright (C) The IETF Trust (2007). 3231 This document is subject to the rights, licenses and restrictions 3232 contained in BCP 78, and except as set forth therein, the authors 3233 retain all their rights. 3235 <<< RFC Ed Note: please remove the text below, prior to publications 3236 >>> 3238 Change Log. 3240 Rev -00 3242 * First draft, for comment by the community. 3244 Rev -01 3246 * Second draft, for comment by the community. 3248 The MIB module is renamed DVBRCS-MIB to reflect that it covers more 3249 than solely interface issues. 3251 The MIB has been updated with 3253 * a conformance section that captures the options 3255 * structural changes and corrections to achieve this 3257 * SYNTAX refinements where applicable 3259 * UNITS declarations where applicable 3261 Document reformatted to conform to I-D format conventions. 3263 Rev -02 3265 * Third draft, for comment by the community. 3267 Update following comments received from the ipdvb list (Gorry 3268 Fairhurst). 3270 <<>