Transport Area Working Group S. Combes
Internet-Draft P. Amundsen
Intended status: Informational M. Lambert
H-P. Lexow
SatLabs Group
Expires: February 2009 September 1, 2008
The DVB-RCS MIB
draft-combes-ipdvb-mib-rcs-04.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
This document may not be modified, and derivative works of it may not
be created, except to publish it as an RFC and to translate it into
languages other than English, or to extract section 4 as-is for
separate use.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on March 1, 2009.
Abstract
This document describes the MIB module for the Digital Video
Broadcasting Return Channel via Satellite system (DVB-RCS). It
defines a set of MIB entities to characterize the behavior and
performance of network layer entities deploying DVB-RCS.
Combes Expires March 1, 2009 [Page 1]
Internet-Draft DVB-RCS MIB September 2008
Table of Contents
1. Introduction...................................................3
2. Conventions used in this document..............................4
2.1. Abbreviations.............................................5
2.2. Glossary..................................................6
2.2.1. Star DVB-RCS network.................................6
2.2.2. Mesh DVB-RCS network.................................6
2.2.3. Transparent DVB-RCS network..........................6
2.2.4. Regenerative DVB-RCS network.........................6
2.2.5. DVB-RCS MAC layer....................................6
2.2.6. DVB-RCS Downlink.....................................6
2.2.7. DVB-RCS Uplink.......................................6
2.2.8. IDU..................................................6
2.2.9. ODU..................................................6
2.2.10. RCST................................................6
2.2.11. NCC.................................................6
2.2.12. Configuration file..................................6
2.2.13. Logfile.............................................6
2.2.14. InstallLogfile......................................6
2.2.15. Antenna alignment...................................6
2.2.16. CW frequency........................................6
2.2.17. Request Class.......................................6
2.2.18. Channel ID..........................................6
2.2.19. ATM profile.........................................6
2.2.20. MPEG profile........................................6
2.2.21. PID pool............................................6
2.2.22. Capacity Categories.................................6
2.2.23. Start transponder...................................6
2.2.24. DVB-S...............................................6
2.2.25. DVB-S2 and CCM/VCM/ACM..............................6
2.2.26. Interactive Network.................................6
3. MIB Module overview............................................6
3.1. Textual Conventions.......................................6
3.2. Structure of the MIB......................................6
3.3. Relationship to the Interfaces MIB Module.................6
3.4. MIB groups description....................................6
3.4.1. rcstSystem...........................................6
3.4.2. rcstNetwork..........................................6
3.4.3. rcstInstall..........................................6
3.4.4. rcstQos..............................................6
3.4.5. rcstControl..........................................6
3.4.6. rcstState............................................6
3.4.7. fwdLink (fwdConfig and fwdStatus groups).............6
3.4.8. rtnLink (rtnConfig and rtnStatus groups).............6
Combes Expires March 1, 2009 [Page 2]
Internet-Draft DVB-RCS MIB September 2008
4. Definitions....................................................6
5. Security Considerations........................................6
6. IANA Considerations............................................6
7. Acknowledgments................................................6
8. References.....................................................6
8.1. Normative References......................................6
8.2. Informative References....................................6
9. Authors' Addresses.............................................6
10. Intellectual Property Statement...............................6
11. Disclaimer of Validity........................................6
12. Copyright Statement...........................................6
1. Introduction
The SatLabs Group [SATLABS] is an international non-profit EEIG
(European Economic Interest Grouping) committed to large-scale
adoption and deployment of the Digital Video Broadcasting Return
Channel via Satellite (DVB-RCS) standard [ETSI-RCS]. SatLabs members
are service providers, satellite operators, system integrators,
terminal manufacturers and technology providers with an interest in
DVB-RCS.
Since its creation in 2001, the main goal of the SatLabs Group has
been to achieve interoperability between DVB-RCS terminals and
systems. Therefore, the Group has defined the SatLabs Qualification
Program that provides an independent certification process for DVB-
RCS Terminals based on System Recommendations defined by SatLabs. To
enhance products interoperability, beyond the physical and MAC layer
mechanisms defined in the DVB-RCS standard, SatLabs has expanded its
Recommendations in the field of DVB-RCS terminal management
[SATLABS]. As a part of this effort, SatLabs has specified a common
SNMP Management Information Base (MIB) for DVB-RCS terminals, which
is defined in this document.
A DVB-RCS terminal is denoted as a Return Channel Satellite Terminal
(RCST) in the remainder of this document. This consists of an Indoor
Unit (IDU) and an Outdoor Unit (ODU) connected through an Inter
Facility Link (IFL), usually a coaxial L-band interface. On the user
side, the IDU is connected to the user network through a Local Area
Network (LAN) interface (usually Ethernet). On the network side, the
ODU is connected via a satellite link (the Air Interface).
The DVB-RCS MIB is implemented in the IDU of an RCST. RCST
management can be performed either through the LAN interface (Local
management) or through the Air Interface (Remote management from the
Combes Expires March 1, 2009 [Page 3]
Internet-Draft DVB-RCS MIB September 2008
Network Control Center, NCC). RCST and NCC elements are shown on
Figure 1.
+------------+
| IP |
| End Host |
+-----+------+
|
- - - - - - - -|- - - - - - - - - - - - - - - -
| | LAN interface |
|
| +------+--------+ |
| Indoor Unit |
| | (IDU) | |
+------+--------+
| | |
Inter Facility Link (IFL)
| | |
+------+--------+
| | OutDoor Unit | |
| (ODU) |
| +------+--------+ |
|
| | Air Interface |
- - - - - - - |- - - - - - - - - - - - - - - -
RCST |
| +----------------+
+------->| Network Control|
| Center (NCC) |
+----------------+
FIGURE 1: RCST architecture
2. Conventions used in this document
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Combes Expires March 1, 2009 [Page 4]
Internet-Draft DVB-RCS MIB September 2008
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2.1. Abbreviations
AAL5 ATM Adaptation Layer Type 5
ACM Adaptive Coding and Modulation (defined in [ETSI-DVBS2])
ATM Asynchronous Transfer Mode
AVBDC Absolute Volume-Based Dynamic Capacity
BER Bit Error Ratio
BUC Block Up-Converter
CCM Constant Coding and Modulation
CNR Carrier to Noise Ratio
CRA Continuous Rate Assignment
CSC Common Signalling Channel
CW Continuous Wave (carrier frequency)
dBi deciBel (isotropic)
dBm deciBel (with respect to 1 mW)
DSCP DiffServ Code Point
ETSI European Telecommunications Standards Institute
Combes Expires March 1, 2009 [Page 5]
Internet-Draft DVB-RCS MIB September 2008
FEC Forward Error Correction
GS Generic Stream
GSE Generic Stream Encapsulation
IDU InDoor Unit
IFL Inter-Facility Link
LNB Low Noise Block
LO Local Oscillator
MAC Medium Access Control
MIB Management Information Base
MPEG Motion Pictures Expert Group
MPE Multi-Protocol Encapsulation
NCC Network Control Centre
OAM Operations and Management
ODU OutDoor Unit
PHB Per-Hop Behavior
PID Packet IDentifier (MPEG, used as Program Identifier in DVB)
QoS Quality of Service
RBDC Rate-Based Dynamic Capacity
RC Request Class
RCST Return Channel via Satellite Terminal (DVB-RCS Terminal)
Rx Receive
SDU Service Data Unit
SSPA Solid State Power Amplifier
TDM Time Division Multiplex
Combes Expires March 1, 2009 [Page 6]
Internet-Draft DVB-RCS MIB September 2008
TDMA Time Division Multiple Access
TS Transport Stream (as defined by MPEG)
Tx Transmit
VBDC Volume-Based Dynamic Capacity
VCI Virtual Channel Identifier (ATM)
VPI Virtual Path Identifier (ATM)
Vpp Volts peak-to-peak
2.2. Glossary
The terms in this document are derived either from DVB-RCS standard
specifications [ETSI-RCS] or from SatLabs System Recommendations
[SATLABS].
2.2.1. Star DVB-RCS network
This denotes a hub-and-spoke configuration where all communications
pass through a central hub, that usually also includes the NCC. Peer-
to-peer communication between RCSTs is possible, but through a double
satellite hop (this traffic has to pass through the hub).
2.2.2. Mesh DVB-RCS network
This denotes a mesh configuration that supports peer-to-peer
communications in a single satellite hop directly between RCSTs.
2.2.3. Transparent DVB-RCS network
This denotes a network using transparent satellite transponders. Star
or mesh network configurations can be supported. In the case of a
mesh configuration, RCSTs need to incorporate a TDMA receiver in
addition to the TDM receiver.
2.2.4. Regenerative DVB-RCS network
This denotes a network using regenerative satellite transponders,
i.e. including some On-Board Processing functionality allowing
demodulation and decoding of the uplink TDMA signals and re-multiplex
Combes Expires March 1, 2009 [Page 7]
Internet-Draft DVB-RCS MIB September 2008
the traffic on the downlink. Star or mesh network configurations can
be supported.
2.2.5. DVB-RCS MAC layer
The DVB-RCS MAC Layer represents the air interface of an RCST, as
defined in the DVB-RCS standard. The interface supports star and mesh
networks and is bi-directional.
2.2.6. DVB-RCS Downlink
The downlink is a DVB-RCS physical link based on TDM. It corresponds
to the forward link of a DVB-RCS transparent system or the downlink
of a DVB-RCS regenerative system. It is based on either the DVB-S or
DVB-S2 standard. In the DVB-RCS context, this interface is bi-
directional.
2.2.7. DVB-RCS Uplink
The DVB-RCS Uplink is based on TDMA. It corresponds to the return or
mesh link of a RCS transparent system or the uplink of a RCS
regenerative system. It is based on the DVB-RCS standard.
In the context of star transparent and mesh regenerative DVB-RCS
systems, this interface is uni-directional.
In the context of mesh transparent DVB-RCS systems, this interface is
bi-directional.
2.2.8. IDU
This is the indoor part of the RCST (including at least the power
supply, and usually also the modem and networking functions).
2.2.9. ODU
This is the outdoor part of the RCST (including at least the aerial,
and usually also the LNB and BUC).
2.2.10. RCST
This is the Satellite Terminal, installed on the customer premises.
It is composed of the IDU and ODU.
Combes Expires March 1, 2009 [Page 8]
Internet-Draft DVB-RCS MIB September 2008
2.2.11. NCC
The NCC provides Control and Monitoring Functions. It generates
control and timing signals for the operation of the DVB-RCS Network.
2.2.12. Configuration file
The configuration file is XML formatted file, storing configuration
parameters for the RCST and their values.
2.2.13. Logfile
The logfile is stored at the RCST. This is used to log particular
events that occurr on RCST side.
2.2.14. InstallLogfile
The Installlogfile is stored at the RCST. This logs particular events
that occur on RCST side, related to RCST installation phase.
2.2.15. Antenna alignment
This is the process to align the RCST antenna, part of the ODU, in
order to enable bi-directional communication (uplink, downlink) with
the satellite network.
2.2.16. CW frequency
The CW frequency is the frequency of a Continuous Wave signal. It is
a narrowband carrier transmitted for the duration of measurements
during the installation of a RCST.
2.2.17. Request Class
A Request Class (RC) is a representation of a Per Hop Behavior (PHB)
at the MAC layer. It defines a behavior of the MAC layer for a given
aggregation of traffic. This behavior includes a combination of
Capacity Categories associated to the RC and a Priority with respect
to the other RCs supported by a RCST.
2.2.18. Channel ID
Each Request Class is identified by a unique Channel_ID in the
communication between the RCST and the NCC.
Combes Expires March 1, 2009 [Page 9]
Internet-Draft DVB-RCS MIB September 2008
2.2.19. ATM profile
The ATM profile is one of the two profiles for traffic burst format
on a DVB-RCS uplink. It is based on one or more concatenated ATM
cells, each of length 53 bytes, plus an optional prefix.
2.2.20. MPEG profile
The MPEG profile is one of the two profiles for traffic burst format
on the DVB-RCS uplink. It is based on a number of concatenated MPEG2-
TS packets, each of length 188 bytes.
2.2.21. PID pool
For the MPEG profile several RCs may be mapped within a pool of
several PIDs to allow cross-RC Section Packing [RFC4259]. Section
packing can be used on all PIDs and higher priority traffic can
always pre-empt lower priority streams. This reduces the need for
padding.
2.2.22. Capacity Categories
The TDMA timeslot allocation process for the DVB-RCS uplink supports
several capacity categories.
The Capacity Categories CRA, RBDC and A/VBDC, when authorized for a
RC, have to be configured from the NCC. These configuration
parameters are used to inform the RCST of the configuration of each
Category at the NCC side and thus help in Capacity Requests
computation.
The configuration of these parameters is performed for each RC. A
SatLabs optional feature is defined that allows their configuration
at the RCST level in addition to configuration per RC. This feature
is denoted RCST_PARA.
2.2.22.1. Continuous Rate Assignment (CRA)
CRA is a rate capacity that is provided in full in a continuous
manner to the RCST while required.
2.2.22.2. Rate-Based Dynamic Capacity (RBDC)
RBDC is rate capacity that is requested dynamically by an RCST. RBDC
capacity is provided in response to explicit requests from the RCST
to the NCC, such requests being absolute (i.e. corresponding to the
full rate currently being requested). Each request overrides all
Combes Expires March 1, 2009 [Page 10]
Internet-Draft DVB-RCS MIB September 2008
previous RBDC requests from the same RCST, and is subject to a
maximum rate limit.
2.2.22.3. Volume-Based Dynamic Capacity (VBDC)
VBDC is volume capacity that is requested dynamically by an RCST.
VBDC capacity is provided in response to explicit requests from the
RCST to the NCC, such requests being cumulative (i.e. each request
adds to all previous requests from the same RCST).
2.2.22.4. Absolute Volume-Based Dynamic Capacity (AVBDC)
AVBDC is volume capacity that is requested dynamically by an RCST.
This capacity is provided in response to explicit requests from the
RCST to the NCC, such requests being absolute (i.e. this request
replaces the previous ones from the same RCST).
The combination of AVBDC and VBDC is seen as a single Capacity
Category, denoted A/VBDC.
2.2.22.5. Population ID
This defines a group of RCSTs within a Network.
2.2.23. Start transponder
This is the satellite transponder on which the communication is
initiated from a RCST point-of-view when in the installation mode.
The parameters corresponding to this transponder (satellite orbital
position, frequency, etc.) are stored at the RCST as power-up
configuration data.
2.2.24. DVB-S
DVB-S is the Digital Video Broadcast over Satellite [ETSI-DVBS]. It
is a framework and set of associated standards published by ETSI for
the transmission of video, audio, and data, using the ISO MPEG-2
Standard [ISO-MPEG], over satellite links.
2.2.25. DVB-S2 and CCM/VCM/ACM
DVB-S2 is the Second Generation of the Digital Video Broadcast for
Satellite applications standard [ETSI-DVBS2]. It is a framework and
set of associated standards published by ETSI for the transmission of
video, audio and data.
BBFRAME: The main framing unit of the DVB-S2 protocol stack.
Combes Expires March 1, 2009 [Page 11]
Internet-Draft DVB-RCS MIB September 2008
CCM: In CCM transmission mode, the forward link uses a constant set
of transmission parameters (FEC coding rate and modulation scheme)
for all receivers.
VCM: In VCM transmission mode, the forward link uses transmission
parameters which are variable on a BBFRAME-by-BBFRAME, but fixed on a
Receiver basis, according to fixed link and propagation conditions
for each Receiver.
ACM: In ACM transmission mode, the forward link uses transmission
parameters which are dynamically adjusted on a BBFRAME-by-BBFRAME and
Receiver-per-Receiver basis, according to actual link and propagation
conditions. In order to implement ACM, feedback from each Receiver
has to be provided by DVB-RCS return channel.
2.2.26. Interactive Network
This is another name for a DVB-RCS based satellite network.
3. MIB Module overview
This MIB module provides a set of objects required for the management
of SatLabs-compliant RCST. The specification is derived from the
parameters and protocols described in [SATLABS].
The MIB module in this document uses the following OBJECT IDENTIFIER
values as already assigned by IANA under the smi-numbers registry
[IANA]:
+------------+---------------------------+
| Descriptor | OBJECT IDENTIFIER value |
+------------+---------------------------+
|dvbrcsMib |{ mib-2 transmission 239 } |
+------------+---------------------------+
Table 1: Object Identifiers for the MIB
These values have been assigned for this MIB under the 'mib-
2.transmission' subtree.
Combes Expires March 1, 2009 [Page 12]
Internet-Draft DVB-RCS MIB September 2008
3.1. Textual Conventions
This MIB module defines new textual conventions for RCST indications
of SatLabs defined capabilities, including profiles, options and
optional features.
systemSatLabsProfileMap represents the SatLabs profiles supported as
defined in [SATLABS].
systemSatLabsOptionMap represents the SatLabs options supported as
defined in [SATLABS]. These are options that are used for the
certification of SatLabs terminals. They represent important
functionality, with impact on interoperability, and their support is
advertised with the RCST certification level.
systemSatLabsFeatureMap represents the SatLabs optional features
supported as defined in [SATLABS]. These represent minor features,
not necessary for interoperability. They are not used for the
certification of SatLabs terminals.
3.2. Structure of the MIB
This MIB module is structured into two top level groups:
o The dvbrcsMIBobjects group includes all the managed objects of the
DVB-RCS MIB.
o The dvbrcsConformance group includes the compliance statements for
DVB-RCS terminals that are compliant with [SATLABS]. The managed
objects are grouped into formal object groups (i.e. units of
conformance) according to the relation to specific SatLabs options
or features. The conformance statements (MODULE-COMPLIANCE
specification) are described within the rcstCompliance group while
the units of conformance are described within the rcstGroups
group.
The dvbrcsMIBobjects group is further structured into three groups:
rcst, fwdLink and rtnLink.
The rcst group covers management related to the RCST equipment. It is
structured into six groups:
o rcstSystem
Combes Expires March 1, 2009 [Page 13]
Internet-Draft DVB-RCS MIB September 2008
o rcstNetwork
o rcstInstall
o rcstQos
o rcstControl
o rcstState
The fwdLink group covers management information related to the RCST
forward link. It is structured into two groups:
o fwdConfig
o fwdStatus
The rtnLink group covers management information related to the RCST
return link. It is structured into two groups:
o rtnConfig
o rtnStatus
Tables within each of these groups cover different functions like
return link traffic management (packet classes, Request Classes, PID
pools) and forward links configuration and status.
Rows created automatically (e.g., by the device according to the
hardware configuration) may and generally will have a mixture of
configuration and status objects within them. Rows that are meant to
be created by the management station are generally restricted to
configuration (read-create) objects.
The MIB module finally includes a conformance section including
conformance groups and compliance statements.
3.3. Relationship to the Interfaces MIB Module
This section clarifies the relationship of this MIB module to the
Interfaces MIB [RFC2863]. Several areas of correlation are addressed
in the following. The implementer is referred to the Interfaces MIB
document in order to understand the general intent of these areas.
IANA has assigned three ifType labels for DVB-RCS. Each RCST MUST
support at least the three following interfaces:
Combes Expires March 1, 2009 [Page 14]
Internet-Draft DVB-RCS MIB September 2008
o dvbRcsMacLayer (239), -- DVB-RCS MAC Layer
DVB-RCS MAC Layer represents the air interface of a RCST, as
defined in [ETSI-RCS]. This interface supports star and mesh
networks and is bi-directional. Only star networks are considered
by the present MIB module.
o dvbTdm (240), -- DVB Satellite TDM
DVB-RCS Physical link based on Time Division Multiplexing. It
corresponds to the forward link of a RCS transparent system or the
downlink of a RCS regenerative system. It is based on either DVB-S
or DVB-S2 standard. Only transparent systems are considered by the
present MIB module.
In the DVB-RCS context, this interface is uni-directional (i.e.
forward link, or downstream).
o dvbRcsTdma (241), -- DVB-RCS TDMA
DVB-RCS Physical link based on Time Division Multiple Access. It
corresponds to the return or mesh link of a RCS transparent system
or the uplink of a RCS regenerative system. It is based on the DVB-
RCS standard.
In the context of star transparent and mesh regenerative DVB-RCS
systems, this interface is uni-directional.
In the context of mesh transparent DVB-RCS systems, this interface
is bi-directional.
Only star transparent systems are considered by the present MIB
module (i.e. return link, or upstream).
The protocol stack (as reflected in ifStackTable) will be as follows:
+--------------------------+
| IP |
+--------------------------+
| dvbRcsMacLayer |
+---------------+----------+
| dvbRcsTdma | dvbTdm |
+---------------+----------+
| MPEG/ATM | MPEG/GS |
+---------------+----------+
FIGURE 2: RCST protocol stack
GS (Generic Stream) is defined in [ETSI-DVBS2].
The additional Ethernet interface is used on the LAN side of the
RCST.
Combes Expires March 1, 2009 [Page 15]
Internet-Draft DVB-RCS MIB September 2008
An instance of ifEntry exists for each DvbTdm interface, for each
DvbRcsTdma (normally only one), and for each DvbRcsMac layer
(normally only one).
The interface counters relate to:
o dvbRcsMacLayer: DVB-RCS two-way MAC that counts aggregate DVB-RCS
SDU traffic (IP layer)
o dvbTdm: DVB-RCS TDM that counts either Generic Stream
Encapsulation(GSE) or Multi-Protocol Encapsulation (MPE) traffic,
as applicable for the specific configuration
. GSE is defined in [ETSI-GSE]
. MPE is defined in [ETSI-DAT]
o dvRcsTdma: DVB-RCS TDMA that counts either ATM Adaptation Layer 5
(AAL5) or MPE traffic, as applicable for a specific configuration
The ifStackTable [RFC2863] MUST be implemented to identify the
relationships among sub-interfaces.
The following example is a DVB-RCS star network with DVB-S and DVB-
RCS. As illustrated on Figure 3, it shows a DVB-RCS MAC interface
with one downstream and one upstream interfaces. In this network, ATM
encapsulation is used in the DVB-RCS uplink. Two ATM Logical Ports
are shown. DVB-S2 or DVB-S can be used in the downlink. MPEG can be
used as well instead of ATM Logical Ports.
+----------------------------------------------------------+
| IP Network Layer |
+------+----------------------------------+----------------+
| |
+------+-------+ +------------------+----------------+
| Ethernet LAN | | dvbRcsMacLayer |
+--------------+ +-------------+---------------------+
| |
+-------------+-----------+ +---+---+
| dvbRcsTdma | |dvbTdm |
+-----+-------------+-----+ +-------+
| |
+-----+-----+ +-----+-----+
|atm-logical| |atm-logical|
+-----------+ +-----------+
FIGURE 3: Example stacking
Combes Expires March 1, 2009 [Page 16]
Internet-Draft DVB-RCS MIB September 2008
As can be seen from this example, the dvbRcsMacLayer interface is
layered on top of the downstream and upstream interfaces, and the
upstream interface is layered on top of upstream ATM logical links.
In this example, the assignment of index values could be as follows:
ifIndex ifType Description
2 dvbRcsMacLayer (239) DVB-RCS MAC Layer
3 dvbRcsTdma (240) DVB-RCS TDMA Upstream
4 dvbTdm(241) DVB-RCS TDM Downstream
5 atm-logical(80) ATM Logical Port
6 atm-logical(80) ATM Logical Port
The corresponding ifStack entries would then be:
+--------------------+-------------------+
| IfStackHigherLayer | ifStackLowerLayer |
+--------------------+-------------------+
| 0 | 1 |
| 0 | 2 |
| 1 | 0 |
| 2 | 3 |
| 2 | 4 |
| 3 | 5 |
| 3 | 6 |
| 4 | 0 |
| 5 | 0 |
| 6 | 0 |
+--------------------+-------------------+
FIGURE 1: Example ifStack entries
3.4. MIB groups description
3.4.1. rcstSystem
The MIB objects in this group gather some basic information that
would allow anyone to trace the history - the life - of the RCST as
well as to get a complete description of its constitution on the
component point of view, including the SatLabs options/features
support statement. Many of the parameters will be defined at
installation.
Combes Expires March 1, 2009 [Page 17]
Internet-Draft DVB-RCS MIB September 2008
This group contains description parameters related to the RCST type
(ODU type) and location. These parameters are believed to stay
unchanged once it has been defined during installation. Modification
of hardware equipment, maintenance operations and geographical re-
location may require an update of those MIB objects. They are. Note
that rcstSystem.systemLocation object gives the location of the ODU
antenna, which is needed for network operation, while the
system.sysLocation (MIB-II SNMP OID) provides the location of the IDU
unit, which can not be used for the same purpose.
3.4.2. rcstNetwork
This group contains all the MIB objects related to network
parameters.
In this subgroup, two objects have been defined in order to
differentiate between control and user traffic and associate them
with a physical interface. Both rcstNetwork.networkLanIpAddress
(Traffic) and rcstNetwork.networkOamIpAddress (OAM) provide the value
of the IP address of, respectively, the user traffic and the control
and management traffic.
3.4.3. rcstInstall
This group contains all the information related to the RCST
installation and commissioning. Many parameters are believed to stay
unchanged once it has been defined during installation. Modification
of hardware equipment, maintenance operations and geographical re-
location may require an update of those MIB objects.
3.4.4. rcstQos
This group contains objects to configure the Quality of Service (QoS)
of the RCST by the NCC.
The pktClass table defines the packet classification for IP layer 3
classifications. Each pktClass entry is mapped to a phbEntry in the
phbMappingTable.
The phbMappingTable makes the relation between a packet
classification entry, a Per-Hop Behavior (PHB) identifier and a
Request class entry.
The requestClassTable defines all the layer 2 DVB-RCS QoS parameters.
Combes Expires March 1, 2009 [Page 18]
Internet-Draft DVB-RCS MIB September 2008
3.4.5. rcstControl
This MIB group contains objects a network manager can use to invoke
actions and tests supported by the RCST agent and to retrieve the
action/test results.
3.4.6. rcstState
This MIB group describes the fault state, software versions and
configuration file versions of the RCST.
3.4.7. fwdLink (fwdConfig and fwdStatus groups)
This MIB group contains parameters that enable the NCC to have access
to data about the forward link.
Configuration information is kept into the fwdLink.fwdConfig
subgroup. Status information is kept into the fwdLink.fwdStatus
subgroup.
The information of the fwdLink.fwdConfig.fwdStartTable are used for
the first time the RCST tries to acquire the forward link. All these
objects values are aligned with the Satellite Delivery System
Descriptor in the Network Information Table (NIT) table [ETSI-SI].
The objects in the fwdLink.fwdConfig.fwdStatusTable are aligned with
the satellite forward path descriptor form the RCS Map Table (RMT)
[ETSI-RCS] and with the Physical Layer (PL) Header [ETSI-DVBS2],
which specified the MODCOD (modulation and FEC rate) and the Type
(frame length short of long and the presence/absence of pilots).
3.4.8. rtnLink (rtnConfig and rtnStatus groups)
This MIB group contains parameters that enable the NCC to have access
to data about the return link.
Configuration information is kept into the rtnLink.rtnConfig
subgroup. Status information is kept into the rtnLink.rtnStatus
subgroup.
The RCST is only able to deal with one return link at a time. Hence,
there is no need to define a table to collect the different SNMP
objects, as it is done for the forward.
Combes Expires March 1, 2009 [Page 19]
Internet-Draft DVB-RCS MIB September 2008
4. Definitions
DVBRCS-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
Integer32,
IpAddress,
transmission,
OBJECT-TYPE
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION,
DisplayString,
RowStatus
FROM SNMPv2-TC -- [RFC2579]
OBJECT-GROUP,
MODULE-COMPLIANCE
FROM SNMPv2-CONF; -- [RFC2580]
dvbrcsMIB MODULE-IDENTITY
LAST-UPDATED "200807291200Z"
ORGANIZATION "The SatLabs Group"
CONTACT-INFO
"The SatLabs Group
Web: www.satlabs.org
E-mail: info@satlabs.org"
DESCRIPTION
"DVB-RCS MIB subtree.
This MIB module applies to equipment that is a
Return Channel Satellite Terminal (RCST) defined in
the Digital Video Broadcasting Return
Channel via Satellite system (DVB-RCS) standard (ETSI EN 301
791 Digital Video Broadcasting (DVB); Interaction Channel
for Satellite Distribution Systems, European
Telecommunications Standards Institute (ETSI)).
It defines a set of MIB entities to characterise the
behaviour and performance of network layer entities
implementing DVB-RCS.
This MIB module is intended to be used by DVB-RCS equipment
following the SatLabs System Recommendations, defined by the
SatLabs Group and available at www.satlabs.org."
Combes Expires March 1, 2009 [Page 20]
Internet-Draft DVB-RCS MIB September 2008
REVISION "200807291200Z"
DESCRIPTION
"Revision of this MIB module, following comments from ipdvb
WG."
::= { transmission 239 }
--===================================================================
-- Textual Conventions
--===================================================================
SatLabsProfileMap ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention enumerates the declaration of the
SatLabs defined terminal profiles. (0) refers to the most
significant bit."
REFERENCE
"SatLabs System Recommendations available at www.satlabs.org"
SYNTAX BITS {
dvbs(0),
dvbs2ccm(1),
dvbs2acm(2),
spare1(3),
spare2(4),
spare3(5),
spare4(6),
spare5(7),
spare6(8),
spare7(9),
spare8(10),
spare9(11),
spare10(12),
spare11(13),
spare12(14),
spare13(15),
spare14(16),
spare15(17),
spare16(18),
spare17(19),
spare18(20),
spare19(21),
Combes Expires March 1, 2009 [Page 21]
Internet-Draft DVB-RCS MIB September 2008
spare20(22),
spare21(23),
spare22(24),
spare23(25),
spare24(26),
spare25(27),
spare26(28),
spare27(29),
spare28(30),
spare29(31)
}
SatLabsOptionMap ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention enumerates the declaration of the
SatLabs defined options. (0) refers to the most significant
bit."
REFERENCE
"SatLabs System Recommendations available at www.satlabs.org"
SYNTAX BITS {
mpegTrf(0),
coarseSync(1),
wideHop(2),
fastHop(3),
dynamicMfTdma(4),
contentionSync(5),
qpskLow(6),
mod16Apsk(7),
mod32Apsk(8),
normalFec(9),
multiTs(10),
gsTs(11),
enhQoS(12),
pep(13),
http(14),
ftp(15),
dns(16),
chIdStrict(17),
nlid(18),
snmpMisc(19),
Combes Expires March 1, 2009 [Page 22]
Internet-Draft DVB-RCS MIB September 2008
spare1(20),
spare2(21),
spare3(22),
spare4(23),
spare5(24),
spare6(25),
spare7(26),
spare8(27),
spare9(28),
spare10(29),
spare11(30),
spare12(31)
}
SatLabsFeatureMap ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention enumerates the declaration of
the SatLabs specified compapatibility and configuration
features. (0) refers to the most significant bit."
REFERENCE
"SatLabs System Recommendations available at
www.satlabs.org"
SYNTAX BITS {
rcstPara(0),
installLog(1),
enhClassifier(2),
routeId(3),
spare1(4),
spare2(5),
spare3(6),
spare4(7),
spare5(8),
spare6(9),
spare7(10),
spare8(11),
spare9(12),
spare10(13),
spare11(14),
spare12(15),
spare13(16),
Combes Expires March 1, 2009 [Page 23]
Internet-Draft DVB-RCS MIB September 2008
spare14(17),
spare15(18),
spare16(19),
spare17(20),
spare18(21),
spare19(22),
spare20(23),
spare21(24),
spare22(25),
spare23(26),
spare24(27),
spare25(28),
spare26(29),
spare27(30),
spare28(31)
}
--===================================================================
-- object type definitions
--===================================================================
dvbrcsMIBObjects OBJECT IDENTIFIER ::= {dvbrcsMIB 1}
dvbrcsConformance OBJECT IDENTIFIER ::= {dvbrcsMIB 2}
rcst OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 1}
fwdLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 2}
rtnLink OBJECT IDENTIFIER ::= {dvbrcsMIBObjects 3}
rcstSystem OBJECT IDENTIFIER ::= {rcst 1}
rcstNetwork OBJECT IDENTIFIER ::= {rcst 2}
rcstInstall OBJECT IDENTIFIER ::= {rcst 3}
rcstQos OBJECT IDENTIFIER ::= {rcst 4}
rcstControl OBJECT IDENTIFIER ::= {rcst 5}
rcstState OBJECT IDENTIFIER ::= {rcst 6}
fwdConfig OBJECT IDENTIFIER ::= {fwdLink 1}
fwdStatus OBJECT IDENTIFIER ::= {fwdLink 2}
rtnConfig OBJECT IDENTIFIER ::= {rtnLink 1}
rtnStatus OBJECT IDENTIFIER ::= {rtnLink 2}
--===================================================================
Combes Expires March 1, 2009 [Page 24]
Internet-Draft DVB-RCS MIB September 2008
--- rcstSystem sub-tree object types
--===================================================================
systemMibRevision OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object allows the SNMP agent to report the implemented
MIB module revision.
The supported REVISION of this module is reported."
::= {rcstSystem 1}
--===================================================================
-- Options declared according to the textual conventions
--===================================================================
systemSatLabsProfilesDeclaration OBJECT-TYPE
SYNTAX SatLabsProfileMap
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the SatLabs profiles supported as defined in the
SatLabs System Recommendations. A value of 1 indicates that
the respective option is supported. The mapping to the
profiles is to be understood as described here. (0) refers
to the most significant bit.
dvbs(0) -> DVBS profile (DVB-S support)
dvbs2ccm(1) -> DVB-S2 CCM profile (CCM support)
dvbs2acm(2) -> DVB-S2 ACM profile (CCM, VCM and ACM
support)"
REFERENCE
"SatLabs System Recommendations available at www.satlabs.org"
::= {rcstSystem 2}
systemSatLabsOptionsDeclaration OBJECT-TYPE
SYNTAX SatLabsOptionMap
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the SatLabs options supported as defined in the
SatLabs System Recommendations. A value of 1 indicates that
Combes Expires March 1, 2009 [Page 25]
Internet-Draft DVB-RCS MIB September 2008
the respective option is supported. The mapping to the
options is to be understood as described here. (0) refers to
the most significant bit.
mpegTrf(0) -> MPEG_TRF
coarseSync(1) -> COARSE_SYNC
wideHop(2) -> WIDE_HOPP
fastHop(3) -> FAST_HOPP
dynamicMfTdma(4) -> Dynamic_MF_TDMA
contentionSync(5) -> CONTENTION_SYNC
qpskLow(6) -> QPSKLOW
mod16Apsk(7) -> 16APSK
mod32Apsk(8) -> 32APSK
normalFec(9) -> NORMALFEC
multiTs(10) -> MULTITS
gsTs(11) -> GSTS
enhQoS(12) -> ENHQOS
pep(13) -> PEP
http(14) -> HTTP
ftp(15) -> FTP
dns(16) -> DNS
chIdStrict(17) -> CHID_STRICT
nlid(18) -> NLID
snmpMisc(19) -> SNMPMISC
The support of specific options mandates the support of
specific objects and access levels."
REFERENCE
"SatLabs System Recommendation available at www.satlabs.org"
::= {rcstSystem 3}
systemSatLabsFeaturesDeclaration OBJECT-TYPE
SYNTAX SatLabsFeatureMap
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the optional compatibility features and minor
options supported as defined in the SatLabs System
Recommendations. A value of 1 indicates that the respective
feature is supported. The mapping to the features is to be
understood as described here. (0) refers to the most
Combes Expires March 1, 2009 [Page 26]
Internet-Draft DVB-RCS MIB September 2008
significant bit.
rcstPara(0) -> RCST_PARA feature
installLog(1) -> INSTALL_LOG feature
enhClassifier(2) -> ENHCLASSIFIER feature
routeId(3) -> ROUTE_ID feature
The support of specific features mandates the support of
specific objects and access levels."
REFERENCE
"SatLabs System Recommendation available at www.satlabs.org"
::= {rcstSystem 4}
systemLocation OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Physical location of the ODU antenna expressed as
Longitude, Latitude and Altitude. The string
shall have 31 characters in the following format:
<xxxx.xxx>,<a>,<yyyyy.yyy>,<b>,<zzzz.z>,M
where x, y and z represents digits,
a=N or S,
b=E or W,
Reading the digits from left to right:
'x' 7 latitude digits; x digits 1-2 contain the degrees,
x digits 3-7 contain the minutes in decimal;
'y' 8 longitude digits; y digits 1-3 contain the degrees,
y digits 4-8 contain the minutes in decimal;
''' 5 altitude digits; meters above sea level in decimal;
'.' is the decimal point;
',' is the field separator;
'M' is the indicator for altitude meters.
This format is a modified subset of the NMEA 0183
(National Marine Electronics Association, Interface
Standard) format for Global Positioning System Fix Data.
This location and the satellite position are used to
Combes Expires March 1, 2009 [Page 27]
Internet-Draft DVB-RCS MIB September 2008
calculate the RCST-satellite path delay.
Note: The system.sysLocation object of MIB-II provides physical
location of the IDU unit."
::= {rcstSystem 5}
systemOduAntennaSize OBJECT-TYPE
SYNTAX DisplayString
UNITS "cm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object gives the diameter of the antenna. This value
shall be given in centimeters. It is defined at
installation.
The object can be used in conjunction with environmental
requirements. "
::= {rcstSystem 6}
systemOduAntennaGain OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dBi"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This field describes the antenna peak gain of the ODU and
shall be defined by the installer. The gain shall be given
in tenth of dBi for more flexibility, i.e. 46.5 dBi will be
represented by 465. Defined at installation."
::= {rcstSystem 7}
systemOduSspa OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 W"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This field describes the Solid State Power Amplifier
installed in the ODU and shall be defined by the installer.
The power shall be given in tenth of a Watt, i.e. 0,5 W will
be represented by 5, 1 W by 10 and 2 W by 20.
Combes Expires March 1, 2009 [Page 28]
Internet-Draft DVB-RCS MIB September 2008
Defined at installation."
::= {rcstSystem 8}
systemOduTxType OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Describes the type of transmitter installed in the ODU."
::= {rcstSystem 9}
systemOduRxType OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Describes the type of LNB installed in the ODU, with
information such as vendor type, output type (single, twin,
quad,...), etc."
::= {rcstSystem 10}
systemOduRxBand OBJECT-TYPE
SYNTAX INTEGER {
oduHighRxBand (0),
oduLowRxBand (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Describes whether High Band or Low Band is selected in
the LNB. Specifying High Band results in activation of a
18-26 kHz tone with 0.4-0.8 Vpp in the Rx IFL cable:
(0) - High Band
(1) - Low Band"
::= {rcstSystem 11}
systemOduRxLO OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 Hz"
MAX-ACCESS read-write
STATUS current
Combes Expires March 1, 2009 [Page 29]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"Frequency of LNB Local Oscillator (in 100 Hz)"
::= {rcstSystem 12}
systemOduTxLO OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 Hz"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Frequency of Block Up-Converter Local Oscillator
(in 100 Hz)."
::= {rcstSystem 13}
systemIduPep OBJECT IDENTIFIER ::= {rcstSystem 14}
tcpPep OBJECT-TYPE
SYNTAX INTEGER{
disabled (0),
enabled (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Status and control of embedded TCP PEP.
0 - disabled or not implemented
1 - enabled "
::={ systemIduPep 1}
httpPep OBJECT-TYPE
SYNTAX INTEGER{
disabled (0),
enabled (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Status and control of embedded HTTP PEP.
0 - disabled or not implemented
1 - enabled "
Combes Expires March 1, 2009 [Page 30]
Internet-Draft DVB-RCS MIB September 2008
::={ systemIduPep 2}
--===================================================================
-- rcstNetwork sub-tree object types
--===================================================================
networkOamIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"OAM IP Address of the RCST. This object is used with both
IP and interfaces MIB-II subgroups. It uniquely determines
the interface through which OAM traffic passes.
The OAM IP address may be statically or dynamically
assigned. It is system dependent whether the OAM IP address
and the Traffic IP address are the same address."
::= {rcstNetwork 1}
networkOamIpNetworkMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Network Mask for the OAM IP Address."
::= {rcstNetwork 2}
networkOamIpAddressAssign OBJECT-TYPE
SYNTAX INTEGER {
oamIpAddressStatic (1),
oamIpAddressDynamic (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Identifies whether the OAM IP address is statically
(1) or dynamically (2) assigned."
::= {rcstNetwork 3}
networkLanIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
Combes Expires March 1, 2009 [Page 31]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION
"IP address of the LAN interface"
::= {rcstNetwork 4}
networkLanIpNetworkMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Mask for the LAN interface"
::= {rcstNetwork 5}
networkAirInterfaceDefaultGateway OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Default Gateway for the air interface"
::= {rcstNetwork 6}
networkDnsServers OBJECT IDENTIFIER ::= {rcstNetwork 7}
primaryDnsServerIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"IP address of the primary DNS server in the NCC."
::= { networkDnsServers 1}
secondaryDnsServerIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"IP address of the secondary DNS server in the NCC."
::= { networkDnsServers 2}
networkNccMgtIpAddress OBJECT-TYPE
SYNTAX IpAddress
Combes Expires March 1, 2009 [Page 32]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"IP address of the management server in the NCC."
::= {rcstNetwork 8}
networkConfigFileDownloadUrl OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Full path name for the configuration file download.
It includes the protocol type (tftp or ftp) and the
associated server IP address or hostname. Hostname can
only be used if DNS is supported by the RCST.
The format of this parameter follows RFC 1738."
::= {rcstNetwork 9}
networkInstallLogFileDownloadUrl OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Full path of the installation log file to download.
It includes the protocol type (tftp or ftp) and the
associated server IP address or hostname. Hostname can
only be used if DNS is supported by the RCST. The
installation log file can be created on the installer's
computer and downloaded to the RCST.
The format of this parameter follows RFC 1738."
::= {rcstNetwork 10}
networkConfigFileUploadUrl OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Full path name for the configuration file upload.
It includes the protocol type (tftp or ftp) and the
associated server IP address or hostname. Hostname can
only be used if DNS is supported by the RCST.
Combes Expires March 1, 2009 [Page 33]
Internet-Draft DVB-RCS MIB September 2008
The format of this parameter follows RFC 1738."
::= {rcstNetwork 11}
networkLogFileUploadUrl OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Full path of the event log file. It includes the protocol
type (tftp or ftp) and the associated server IP address
or hostname. Hostname can only be used if DNS is supported
by the RCST.
The format of this parameter follows RFC 1738."
::= {rcstNetwork 12}
networkInstallLogFileUploadUrl OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Full path of the installation log file. It includes the
protocol type (tftp or ftp) and the associated server
IP address or hostname. Hostname can only be used if DNS is
supported by the RCST. The installation log file can be
retrieved from the RCST by the NCC or by the installer
via the LAN.
The format of this parameter follows RFC 1738."
::= {rcstNetwork 13}
--===================================================================
-- rcstInstall sub-tree object types
--===================================================================
installAntennaAlignmentState OBJECT-TYPE
SYNTAX INTEGER {
antennaAlignmentStart (1),
antennaAlignmentDeny (2),
antennaAlignmentContinue(3),
antennaAlignmentStop (4),
antennaAlignmentSuccess (5),
antennaAlignmentFail (6)
}
Combes Expires March 1, 2009 [Page 34]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the alignment state of the antenna:
(1)-Start;
(2)-Deny;
(3)-Continue;
(4)-Stop;
(5)-Success;
(6)-Fail"
::= {rcstInstall 1}
installCwFrequency OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 Hz"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Frequency at which the transmitted Continuous Wave carrier
(in 100 Hz).
Minimum required precision is 1 kHz."
::= {rcstInstall 2}
installCwMaxDuration OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time after which the Continuous Wave carrier must be put
down (in seconds)"
::= {rcstInstall 3}
installCwPower OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dBm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"IDU TX output level when the IDU is configured to send CW.
The resolution is 0.1 dBm and the accuracy is +/- 1 dBm.
Combes Expires March 1, 2009 [Page 35]
Internet-Draft DVB-RCS MIB September 2008
Reconfiguration is applied immediately to a CW."
::= {rcstInstall 4}
installCoPolReading OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dB"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Co-Polarisation measured value during installation
procedure (in 0.1 dB)"
::= {rcstInstall 5}
installXPolReading OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dB"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Cross-Polarisation measured value during installation
procedure (in 0.1 dB)"
::= {rcstInstall 6}
installCoPolTarget OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dB"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Co-Polarisation target value during installation procedure
(in 0.1 dB)."
::= {rcstInstall 7}
installXPolTarget OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dB"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Cross-Polarisation target value during installation procedure
(in 0.1 dB)"
Combes Expires March 1, 2009 [Page 36]
Internet-Draft DVB-RCS MIB September 2008
::= {rcstInstall 8}
installStandByDuration OBJECT-TYPE
SYNTAX Integer32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Time to wait in stand-by mode (in seconds)"
::= {rcstInstall 9}
installTargetEsN0 OBJECT-TYPE
SYNTAX Integer32(0..315)
UNITS "x0.1 dB"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This value describes the wanted Es/N0 value that enables
operation of the return link with the required error
performance. The values shall be given in tenth of dB and
the initial value shall be equal to 7 dB. The range shall be
from 0 dBm to 31.5 dBm with a precision of 0.1 dB."
DEFVAL { 70 }
::= {rcstInstall 10}
--===================================================================
-- rcstQos sub-tree object types
--===================================================================
pktClassTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table describes the packet classification used in the
DVB-RCS terminal. The number of entries is specified by
PktClassIndex. "
::={rcstQos 1}
pktClassEntry OBJECT-TYPE
SYNTAX PktClassEntry
MAX-ACCESS not-accessible
Combes Expires March 1, 2009 [Page 37]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION
"An entry in the packet classification table. One object type
of each entry may have a value in the active range (a non-
default value).The other object types are then assumed set to
'inactive'. The entry with the lowest index value takes
precedence when classifying a packet."
INDEX { pktClassIndex }
::= { pktClassTable 1 }
PktClassEntry ::= SEQUENCE {
pktClassIndex Integer32,
pktClassDscpLow Integer32,
pktClassDscpHigh Integer32,
pktClassDscpMarkValue Integer32,
pktClassIpProtocol Integer32,
pktClassIpSrcAddress IpAddress,
pktClassIpSrcAddressMask IpAddress,
pktClassIpDstAddress IpAddress,
pktClassIpDstAddressMask IpAddress,
pktClassSrcPortLow Integer32,
pktClassSrcPortHigh Integer32,
pktClassDstPortLow Integer32,
pktClassDstPortHigh Integer32,
pktClassVlanUserPri Integer32,
pktClassPhbAssociation Integer32,
pktClassRowStatus RowStatus
}
pktClassIndex OBJECT-TYPE
SYNTAX Integer32 (1..64)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index automatically incremented by one at row creation."
::={pktClassEntry 1}
pktClassDscpLow OBJECT-TYPE
SYNTAX Integer32 (0..63)
MAX-ACCESS read-create
STATUS current
Combes Expires March 1, 2009 [Page 38]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"This object specifies the low value of a range of DiffServ
Code Point (DSCP) values to which a packet is compared.
A value of 0 is used to inactivate."
DEFVAL { 0 }
::={pktClassEntry 2}
pktClassDscpHigh OBJECT-TYPE
SYNTAX Integer32 (0..63)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the high value of a range of DiffServ
Code Point (DSCP) values to which a packet is compared.
A value of 63 is used to inactivate."
DEFVAL { 63 }
::={pktClassEntry 3}
pktClassDscpMarkValue OBJECT-TYPE
SYNTAX Integer32 (-1..63)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is the DiffServ Code Point (DSCP) value used to
mark the packet, -1 indicates no DSCP marking. Possible DSCP
marks values are (0..63)"
DEFVAL { -1 }
::={pktClassEntry 4}
pktClassIpProtocol OBJECT-TYPE
SYNTAX Integer32 (-1..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the IP protocol to which a
packet is compared. A value of 255 indicates inactive."
DEFVAL { -1 }
::={pktClassEntry 5}
pktClassIpSrcAddress OBJECT-TYPE
SYNTAX IpAddress
Combes Expires March 1, 2009 [Page 39]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the IP source address to which a
packet is compared."
::={pktClassEntry 6}
pktClassIpSrcAddressMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies which bits of the IP source address
will be matched. A mask of all zeros indicates that the
selectivity is inactive."
DEFVAL { '00000000'H }
::={pktClassEntry 7}
pktClassIpDstAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the IP destination address to which a
packet is compared."
::={pktClassEntry 8}
pktClassIpDstAddressMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies which bits of the IP destination
address will be matched. A mask of all zeros indicates that
the selectivity is inactive."
DEFVAL { '00000000'H }
::={pktClassEntry 9}
pktClassSrcPortLow OBJECT-TYPE
SYNTAX Integer32 (-1..65535)
Combes Expires March 1, 2009 [Page 40]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the low range of the source
port to which a packet is compared. A value of -1 indicates
that the selectivity is inactive."
DEFVAL { -1 }
::={pktClassEntry 10}
pktClassSrcPortHigh OBJECT-TYPE
SYNTAX Integer32 (-1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the high range of the source port to
which a packet is compared. A value of -1 indicates that the
selectivity is inactive."
DEFVAL { -1 }
::={pktClassEntry 11}
pktClassDstPortLow OBJECT-TYPE
SYNTAX Integer32 (-1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the low range of the destination
port to which a packet is compared. A value of -1 indicates
that the selectivity is inactive."
DEFVAL { -1 }
::={pktClassEntry 12}
pktClassDstPortHigh OBJECT-TYPE
SYNTAX Integer32 (-1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the high range of the destination
port to which a packet is compared. A value of -1 indicates
that the selectivity is inactive."
DEFVAL { -1 }
::={pktClassEntry 13}
Combes Expires March 1, 2009 [Page 41]
Internet-Draft DVB-RCS MIB September 2008
pktClassVlanUserPri OBJECT-TYPE
SYNTAX Integer32 (-1..7)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the VLAN User Priority to which a
packet is compared. A value of -1 indicates that the
selectivity is inactive."
DEFVAL { -1 }
::={pktClassEntry 14}
pktClassPhbAssociation OBJECT-TYPE
SYNTAX Integer32 (0..63)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Associate the filter entry to a specific PHB (refer to
phbIdentifier)."
::={pktClassEntry 15}
pktClassRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Standard SNMP row status"
::={pktClassEntry 16}
--===================================================================
-- PhbMappingTable
--===================================================================
phbMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF PhbMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is a list of Per-Hop Behaviour (PHB) MIB entries.
It describes the PHB mapping to the Request Class."
::={rcstQos 2}
Combes Expires March 1, 2009 [Page 42]
Internet-Draft DVB-RCS MIB September 2008
phbMappingEntry OBJECT-TYPE
SYNTAX PhbMappingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the PHB mapping table."
INDEX { phbIdentifier }
::= { phbMappingTable 1 }
PhbMappingEntry ::= SEQUENCE {
phbIdentifier Integer32,
phbName DisplayString,
phbRequestClassAssociation Integer32,
phbMappingRowStatus RowStatus
}
phbIdentifier OBJECT-TYPE
SYNTAX Integer32 (1..64)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Identification of the Per-Hop Behaviour (PHB) (1..64)."
::={phbMappingEntry 1}
phbName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The name of the Per-Hop Behaviour (PHB)."
::={phbMappingEntry 2}
phbRequestClassAssociation OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object is an association of this Per-Hop Behaviour
(PHB) to a Request class (by reference to a Request Class
index)."
::={phbMappingEntry 3}
Combes Expires March 1, 2009 [Page 43]
Internet-Draft DVB-RCS MIB September 2008
phbMappingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Standard SNMP row status"
DEFVAL { active }
::={phbMappingEntry 4}
--===================================================================
-- RequestClassTable
--===================================================================
requestClassTable OBJECT-TYPE
SYNTAX SEQUENCE OF RequestClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is a list of Request class entries. This class
describes the layer 2 QoS objects."
::={rcstQos 3}
requestClassEntry OBJECT-TYPE
SYNTAX RequestClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Request Class table."
INDEX { requestClassIndex }
::= { requestClassTable 1 }
RequestClassEntry ::= SEQUENCE {
requestClassIndex Integer32,
requestClassName DisplayString,
requestClassChanId Integer32,
requestClassVccVpi Integer32,
requestClassVccVci Integer32,
requestClassPidPoolReference Integer32,
requestClassCra Integer32,
requestClassRbdcMax Integer32,
Combes Expires March 1, 2009 [Page 44]
Internet-Draft DVB-RCS MIB September 2008
requestClassRbdcTimeout Integer32,
requestClassVbdcMax Integer32,
requestClassVbdcTimeout Integer32,
requestClassVbdcMaxBackLog Integer32,
requestClassRowStatus RowStatus
}
requestClassIndex OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of the Request Class table. A total of 16 entries are
supported."
::={requestClassEntry 1}
requestClassName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Name of the Request Class."
::={requestClassEntry 2}
requestClassChanId OBJECT-TYPE
SYNTAX Integer32 (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Channel id of the Request Class."
::={requestClassEntry 3}
requestClassVccVpi OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines VPI used for the Request Class (ATM profile)."
::={requestClassEntry 4}
requestClassVccVci OBJECT-TYPE
Combes Expires March 1, 2009 [Page 45]
Internet-Draft DVB-RCS MIB September 2008
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines VCI used for the Request Class (ATM profile)."
::={requestClassEntry 5}
requestClassPidPoolReference OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Reference to the Packet IDentifier (PID) pool applicable
for the Request Class."
::={requestClassEntry 6}
requestClassCra OBJECT-TYPE
SYNTAX Integer32
UNITS "bits/s"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Define Continuous Rate Assignment (CRA) level for the
Request Class in bit per second (bits/s)."
::={requestClassEntry 7}
requestClassRbdcMax OBJECT-TYPE
SYNTAX Integer32
UNITS "x2 kbits/s"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Rate-Based Dynamic Capacity (RBDC) that can be
requested for the Request Class, in number of 2 kbits/s"
::={requestClassEntry 8}
requestClassRbdcTimeout OBJECT-TYPE
SYNTAX Integer32
UNITS "superframes"
MAX-ACCESS read-create
STATUS current
Combes Expires March 1, 2009 [Page 46]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"Persistence of the Rate-Based Dynamic Capacity (RBDC)
request, expressed in superframes"
::={requestClassEntry 9}
requestClassVbdcMax OBJECT-TYPE
SYNTAX Integer32
UNITS "ATM cells/MPEG packets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum Volume-Based Dynamic Capacity (VBDC) that can be
allocated to the Request Class, in payload units (one ATM
cell or one MPEG packet) per superframe"
::={requestClassEntry 10}
requestClassVbdcTimeout OBJECT-TYPE
SYNTAX Integer32
UNITS "superframes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Time after which the RCST considers that the pending
requests are lost. The RCST may issue new requests for that
traffic. Volume-Based Dynamic Capacity (VBDC) Timeout is
expressed in superframes."
::={requestClassEntry 11}
requestClassVbdcMaxBackLog OBJECT-TYPE
SYNTAX Integer32
UNITS "bytes"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Volume-Based Dynamic Capacity (VBDC) back log per Request
Class (expressed in bytes)"
::={requestClassEntry 12}
requestClassRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
Combes Expires March 1, 2009 [Page 47]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION
"Standard SNMP row status"
DEFVAL { active }
::={requestClassEntry 13}
--===================================================================
-- The table of PID pools
--===================================================================
pidPoolTable OBJECT-TYPE
SYNTAX SEQUENCE OF PidPoolEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the Packet IDentifier (PID) pools.
For MPEG profile several Request Classes may be mapped
within a pool of several PIDs to allow Section Packing
across Several Request Classes.
A PID value may occur in more than one PID pool. Each PID
value can effectively occur only once in each pool."
::={rcstQos 4}
pidPoolEntry OBJECT-TYPE
SYNTAX PidPoolEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the PID pool table."
INDEX { pidPoolIndex, pidIndex }
::= { pidPoolTable 1 }
PidPoolEntry ::= SEQUENCE {
pidPoolIndex Integer32,
pidIndex Integer32,
pidValue Integer32,
pidPoolRowStatus RowStatus
}
pidPoolIndex OBJECT-TYPE
SYNTAX Integer32 (1..16)
Combes Expires March 1, 2009 [Page 48]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of the PID pool in the PID pool table."
::={pidPoolEntry 1}
pidIndex OBJECT-TYPE
SYNTAX Integer32 (1..16)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of the PID entry within the PID pool."
::={pidPoolEntry 2}
pidValue OBJECT-TYPE
SYNTAX Integer32 (0..8191)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines one of the PIDs to be used in a PID pool of
pidPoolIndex.
A PID value may occur in more than one PID pool. Each PID
value can effectively occur only once in each pool."
::={pidPoolEntry 3}
pidPoolRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Standard SNMP row status"
DEFVAL { active }
::={pidPoolEntry 4}
qosGlobalRbdcMax OBJECT-TYPE
SYNTAX Integer32
UNITS "x2 kbits/s"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Global maximum RBDC that can be requested for the RCST, in
Combes Expires March 1, 2009 [Page 49]
Internet-Draft DVB-RCS MIB September 2008
number of 2 kbits/s."
::={rcstQos 5}
qosGlobalVbdcMax OBJECT-TYPE
SYNTAX Integer32
UNITS "ATM cells/MPEG packets"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Global maximum VBDC that can be allocated to the RCST, in
payload units (one ATM cell or one MPEG packet) per
superframe."
::={rcstQos 6}
qosGlobalVbdcMaxBackLog OBJECT-TYPE
SYNTAX Integer32
UNITS "bytes"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Global VBDC back log at RCST level (expressed in bytes). It
is used only if the VBDC back log is not configured in the
Request class (expressed in bytes)."
::={rcstQos 7}
qosChannelIdStrictDispatching OBJECT-TYPE
SYNTAX INTEGER {
notStrict (0),
strict (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the RCST will strictly follow RC
association when signaled through Channel_ID in the TBTP:
(0)- no strict association
(1)- strict association"
::={rcstQos 8}
--===================================================================
-- rcstControl sub-tree object types
Combes Expires March 1, 2009 [Page 50]
Internet-Draft DVB-RCS MIB September 2008
--===================================================================
ctrlRebootCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
normal (2),
alternate (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable shall force the RCST to reboot
(1)- idle
(2)- normal reboot (from current software load)
(3)- reboot from alternate load (swap to alternate load
before reboot)"
DEFVAL {1}
::={rcstControl 1}
ctrlRcstTxDisable OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
disable (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable shall force the RCST to stop transmission
(transmit disabled as defined in SatLabs System
Recommendations):
(1)- idle
(2)- initiate Tx Disabled"
DEFVAL {1}
::={rcstControl 2}
ctrlUserTrafficDisable OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
disable (2)
}
MAX-ACCESS read-write
STATUS current
Combes Expires March 1, 2009 [Page 51]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"This variable shall disable user traffic (only RCST
management traffic can be transmitted)
(1)- idle
(2)- disable user traffic"
DEFVAL {1}
::={rcstControl 3}
ctrlCwEnable OBJECT-TYPE
SYNTAX INTEGER {
off (1),
on (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable will force the RCST to start transmission of
CW, if the RCST is first set to the installation state, and
is properly configured for CW transmission:
(1)- off
(2)- on"
DEFVAL {1}
::={rcstControl 4}
ctrlOduTxReferenceEnable OBJECT-TYPE
SYNTAX INTEGER {
off (1),
on (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Enables activation and deactivation of 10 MHz reference
clock in the Tx IFL cable:
(1) off
(2) on"
DEFVAL {2}
::={rcstControl 5}
ctrlOduTxDCEnable OBJECT-TYPE
SYNTAX INTEGER {
Combes Expires March 1, 2009 [Page 52]
Internet-Draft DVB-RCS MIB September 2008
off (1),
on (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Enables activation and deactivation of DC in the Tx IFL
cable:
(1) off
(2) on"
DEFVAL {2}
::={rcstControl 6}
ctrlOduRxDCEnable OBJECT-TYPE
SYNTAX INTEGER {
off (1),
on (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Enables activation and deactivation of DC in the Rx IFL
cable:
(1) off
(2) on"
DEFVAL {2}
::={rcstControl 7}
ctrlDownloadFileCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
config (2),
installationLog (3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable will initiate a RCST configuration file
download process
(1) idle
(2) download RCST configuration file from TFTP/FTP server
Combes Expires March 1, 2009 [Page 53]
Internet-Draft DVB-RCS MIB September 2008
(3) download RCST installation log file from TFTP/FTP server
(INSTALL_LOG Option)"
DEFVAL {1}
::={rcstControl 8}
ctrlUploadFileCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
config (2),
eventAlarm (3),
installationLog (4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable will initiate a RCST upload process
(1) idle
(2) upload RCST configuration file to TFTP/FTP server
(3) upload RCST event/alarm log file to TFTP/FTP server
(4) upload RCST installation log file to TFTP/FTP server
(INSTALL_LOG Option)"
DEFVAL {1}
::={rcstControl 9}
ctrlActivateConfigFileCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
activate (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Triggers the RCST to use the configuration file and update
its parameters accordingly. Some RCST implementations may
require a reboot for the parameters to take effect (vendor
specific).
(1) Idle
(2) activate"
DEFVAL {1}
::={rcstControl 10}
Combes Expires March 1, 2009 [Page 54]
Internet-Draft DVB-RCS MIB September 2008
ctrlRcstLogonCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
logon (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable will initiate a RCST logon
(1) idle
(2) initiate RCST logon"
DEFVAL {1}
::={rcstControl 11}
ctrlRcstLogoffCommand OBJECT-TYPE
SYNTAX INTEGER {
idle (1),
logoff (2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable will initiate a RCST logoff
(1) idle
(2) initiate RCST logoff"
DEFVAL {1}
::={rcstControl 12}
--===================================================================
-- rcstState sub-tree object types
--===================================================================
rcstMode OBJECT-TYPE
SYNTAX INTEGER {
installation (0),
operational (1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Identifies the current mode of the RCST is and allows it to
return to the installation mode when needed. Values for the
Combes Expires March 1, 2009 [Page 55]
Internet-Draft DVB-RCS MIB September 2008
RCST mode are:
Installation (0)
Operational (1)"
::={rcstState 1}
rcstFaultStatus OBJECT-TYPE
SYNTAX INTEGER {
nofault (0),
fault (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provide the fault status of the terminal. The fault status
management is vendor specific. Values for the Fault Status
are:
no fault (0)
fault (1)"
::={rcstState 2}
rcstFwdLinkStatus OBJECT-TYPE
SYNTAX INTEGER {
notAcquired (0),
acquired (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides the status of the RCST Forward Link. Values for the
Forward Link Status are:
Not acquired (0)
Acquired (1)"
::={rcstState 3}
rcstRtnLinkStatus OBJECT-TYPE
SYNTAX INTEGER {
loggedOff (0),
loggedOn (1)
}
MAX-ACCESS read-only
STATUS current
Combes Expires March 1, 2009 [Page 56]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"Provides the status of the RCST Return Link. Values for the
Return Link Status are:
Logged-off (0)
Logged-on (1)"
::={rcstState 4}
rcstLogUpdated OBJECT-TYPE
SYNTAX INTEGER {
noUpdate (0),
logfileUpdated (1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the existence of an updated event log file:
No update (0)
Event Log file updated (1)
The RCST should remove the Event Log file updated indication
as the log file is fetched by the NCC."
::={rcstState 5}
rcstCurrentSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current RCST software version."
::={rcstState 6}
rcstAlternateSoftwareVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Alternate (backup/new) RCST software version."
::={rcstState 7}
rcstActivatedConfigFileVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
Combes Expires March 1, 2009 [Page 57]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION
"Version of the most recently activated configuration file.
The version is vendor specific."
::={rcstState 8}
rcstDownloadedConfigFileVersion OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Version of the most recently downloaded configuration file.
Version is vendor specific. If the value is different from
rcstActivatedConfigFileVersion, it is pending for activation."
::={rcstState 9}
--===================================================================
-- fwdConfig sub-tree object types
--===================================================================
fwdStartTable OBJECT-TYPE
SYNTAX SEQUENCE OF FwdStartEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Lists Forward Links attachment points (e.g. different for
installation and operation).
The table describes the forward link parameters used for the
start-up stream with the NCC."
::={fwdConfig 1}
fwdStartEntry OBJECT-TYPE
SYNTAX FwdStartEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Forward Link StartConfig table."
INDEX { fwdStartIndex }
::= { fwdStartTable 1 }
FwdStartEntry ::= SEQUENCE {
Combes Expires March 1, 2009 [Page 58]
Internet-Draft DVB-RCS MIB September 2008
fwdStartIndex Integer32,
fwdStartPopId Integer32,
fwdStartFrequency Integer32,
fwdStartPolar INTEGER,
fwdStartFormat INTEGER,
fwdStartRolloff INTEGER,
fwdStartSymbolRate Integer32,
fwdStartInnerFec INTEGER,
fwdStartRowStatus RowStatus
}
fwdStartIndex OBJECT-TYPE
SYNTAX Integer32 (1..8)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of the Forward Link StartConfig table."
::={fwdStartEntry 1}
fwdStartPopId OBJECT-TYPE
SYNTAX Integer32 (-1..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Population identifier associated with the start-up
forward link:
-1: any (auto)
0-65535: specific StartPopId
If 'any' is set, the RCST will assume membership of any
announced population ID and will commence with logon in
accordance with this assumption."
::={fwdStartEntry 2}
fwdStartFrequency OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 kHz"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Frequency of the start transponder carrying a
Combes Expires March 1, 2009 [Page 59]
Internet-Draft DVB-RCS MIB September 2008
Network Information Table to which any RCST shall
trigger to acquire forward link. Its value shall be given
in multiple of 100 kHz."
::={fwdStartEntry 3}
fwdStartPolar OBJECT-TYPE
SYNTAX INTEGER {
linearHorizontal (0),
linearVertical (1),
circularLeft (2),
circularRight (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"2-bit field giving the polarization of the start
transponder carrying an Network Information Table
to which any RCST shall trigger to acquire forward link:
00: linear and horizontal
01: linear and vertical
10: circular left
11: circular right"
::={fwdStartEntry 4}
fwdStartFormat OBJECT-TYPE
SYNTAX INTEGER {
auto (-1),
dvbs (0),
dvbs2ccm (1),
dvbs2acm (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the transmission format standard applied for the
startup stream. The start transport stream carries a Network
Information Table that the RCST uses for acquiring the
forward link signaling. Supported values are:
-1: unspecified (automatic format acquisition is
assumed)
0: DVB-S (support of this value is mandatory if DVB-S
Combes Expires March 1, 2009 [Page 60]
Internet-Draft DVB-RCS MIB September 2008
support is claimed)
1: DVB-S2 with CCM (support of this value is mandatory
if DVB-S2 CCM support is claimed)
2: DVB-S2 with VCM or ACM (support of this value is
mandatory if DVB-S2 ACM support is claimed)
This allows the RCST to discriminate between CCM and VCM/ACM
when selecting FL.
The support of automatic format selection is optional. One
Or several of the other format selections must be supported,
according to the claimed SatLabs profile support."
::={fwdStartEntry 5}
fwdStartRolloff OBJECT-TYPE
SYNTAX INTEGER {
autoRolloff (0),
rolloff020 (1),
rolloff025 (2),
rolloff035 (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the receive filter roll-off applied on the start
transponder. The start transponder carries a Network
Information Table that the RCST uses for acquiring the
forward link signaling.
Supported values are:
0: any (auto)
1: 0.20
2: 0.25
3: 0.35"
::={fwdStartEntry 6}
fwdStartSymbolRate OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 symbols/s"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the symbol rate on the start transponder
Combes Expires March 1, 2009 [Page 61]
Internet-Draft DVB-RCS MIB September 2008
carrying a Network Information Table to which any RCST
shall trigger to acquire forward link. Its value shall be
given in multiple of 100 symbols/s."
::={fwdStartEntry 7}
fwdStartInnerFec OBJECT-TYPE
SYNTAX INTEGER {
autoFec (-1),
fecRate12 (0),
fecRate23 (1),
fecRate34 (2),
fecRate56 (3),
fecRate78 (4),
fecRate89 (5),
fecRate35 (6),
fecRate45 (7),
fecRate910 (8),
fecRate25 (9),
fecRate13 (10),
fecRate14 (11),
noInnerCode (12) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the inner Forward Error Correction used on the
start transponder carrying a Network Information Table
to which any RCST shall trigger to acquire forward link.
Supported values are:
autoFec (-1),
fecRate1/2 (0),
fecRate2/3 (1),
fecRate3/4 (2),
fecRate5/6 (3),
fecRate7/8 (4),
fecRate8/9 (5),
fecRate3/5 (6),
fecRate4/5 (7),
fecRate9/10 (8),
fecRate2/5 (9),
fecRate1/3 (10),
fecRate1/4 (11),
Combes Expires March 1, 2009 [Page 62]
Internet-Draft DVB-RCS MIB September 2008
noInnerCode (12)
The support of autoFec is optional."
::={fwdStartEntry 8}
fwdStartRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Standard SNMP row status"
DEFVAL { active }
::={fwdStartEntry 9}
--===================================================================
-- fwdStatus sub-tree object types
--===================================================================
fwdStatusPopId OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Population identifier applied at log-on:
0-65535: specific StartPopId
If the RCST was allowed to logon with any population, the
RCST will report the base number of the announced
population ID indicated by the RCS Map Table linkage
descriptor used at logon."
::={fwdStatus 1}
fwdStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF FwdStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table describes the current status of Forward Link
interfaces."
::={fwdStatus 2}
fwdStatusEntry OBJECT-TYPE
SYNTAX FwdStatusEntry
MAX-ACCESS not-accessible
Combes Expires March 1, 2009 [Page 63]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION
"An entry in the Forward Link Status table. Each entry is
associated with a physical interface.
A RCST shall support at least one entry."
INDEX { fwdStatusIndex }
::= { fwdStatusTable 1 }
FwdStatusEntry ::= SEQUENCE {
fwdStatusIndex Integer32,
fwdStatusIfReference Integer32,
fwdStatusNetId Integer32,
fwdStatusNetName DisplayString,
fwdStatusFormat INTEGER,
fwdStatusFrequency Integer32,
fwdStatusPolar INTEGER,
fwdStatusInnerFec INTEGER,
fwdStatusSymbolRate Integer32,
fwdStatusRolloff INTEGER,
fwdStatusModulation INTEGER,
fwdStatusFecFrame INTEGER,
fwdStatusPilot INTEGER,
fwdStatusBer Integer32,
fwdStatusCnr Integer32,
fwdStatusRxPower Integer32
}
fwdStatusIndex OBJECT-TYPE
SYNTAX Integer32 (1..8)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index of the Forward Link Status table."
::={fwdStatusEntry 1}
fwdStatusIfReference OBJECT-TYPE
SYNTAX Integer32 (1..8)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Cross reference to the interface table"
Combes Expires March 1, 2009 [Page 64]
Internet-Draft DVB-RCS MIB September 2008
::={fwdStatusEntry 2}
fwdStatusNetId OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Interactive network identifier of the forward
link (from RCS Map Table)"
::={fwdStatusEntry 3}
fwdStatusNetName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the interactive network of the forward
link (from RCS Map Table)"
::={fwdStatusEntry 4}
fwdStatusFormat OBJECT-TYPE
SYNTAX INTEGER {
dvbs (0),
dvbs2ccm (1),
dvbs2acm (2),
reservedFormat (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the transmission format applied on the forward
link. Supported values are (from RMT):
0: DVB-S
1: DVB-S2 using CCM
2: DVB-S2 using VCM or ACM
3: reserved"
::={fwdStatusEntry 5}
fwdStatusFrequency OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 kHz"
Combes Expires March 1, 2009 [Page 65]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the frequency of the forward link. Its value
shall be given in multiple of 100 kHz."
::={fwdStatusEntry 6}
fwdStatusPolar OBJECT-TYPE
SYNTAX INTEGER {
linearHorizontal (0),
linearVertical (1),
circularLeft (2),
circularRight (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"2-bit field giving the polarization of the forward link
(from RMT):
00: linear and horizontal
01: linear and vertical
10: circular left
11: circular right"
::={fwdStatusEntry 7}
fwdStatusInnerFec OBJECT-TYPE
SYNTAX INTEGER {
unknown (-1),
fecRate12 (0),
fecRate23 (1),
fecRate34 (2),
fecRate56 (3),
fecRate78 (4),
fecRate89 (5),
fecRate35 (6),
fecRate45 (7),
fecRate910 (8),
fecRate25 (9),
fecRate13 (10),
fecRate14 (11),
noInnerCode (12)
Combes Expires March 1, 2009 [Page 66]
Internet-Draft DVB-RCS MIB September 2008
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the inner Forward Error Correction used on the
forward link for transmission to the RCST.
Supported values are:
unknown (-1),
fecRate1/2 (0),
fecRate2/3 (1),
fecRate3/4 (2),
fecRate5/6 (3),
fecRate7/8 (4),
fecRate8/9 (5),
fecRate3/5 (6),
fecRate4/5 (7),
fecRate9/10 (8),
fecRate2/5 (9),
fecRate1/3 (10),
fecRate1/4 (11),
noInnerCode (12)
The RCST will report a value that has been used for transmission
to the RCST within the most recent 60 seconds.
If this is not relevant, the RCST will report 'unknown'."
::={fwdStatusEntry 8}
fwdStatusSymbolRate OBJECT-TYPE
SYNTAX Integer32
UNITS "x100 symbols/s"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the symbol rate of the forward link.
Its value shall be given in multiple of 100 symbol/s."
::={fwdStatusEntry 9}
fwdStatusRolloff OBJECT-TYPE
SYNTAX INTEGER {
undefRolloff (0),
rolloff020 (1),
Combes Expires March 1, 2009 [Page 67]
Internet-Draft DVB-RCS MIB September 2008
rolloff025 (2),
rolloff035 (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An estimate of the roll-off applied on the forward link.
Supported values are:
0: undefined
1: 0.20
2: 0.25
3: 0.35"
::={fwdStatusEntry 10}
fwdStatusModulation OBJECT-TYPE
SYNTAX INTEGER {
unknown (0),
mBPSK (1),
mQPSK (2),
m8PSK (3),
m16APSK (4),
m32APSK (5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the modulation on the forward link used for
transmission to the RCST.
0: unknown
1: BPSK
2: QPSK
3: 8PSK
4: 16APSK
5: 32APSK
The RCST will report a value that has been used for
transmission to the RCST within the most recent 60 seconds.
If this is not relevant, the RCST will report 'unknown'."
::={fwdStatusEntry 11}
fwdStatusFecFrame OBJECT-TYPE
SYNTAX INTEGER {
Combes Expires March 1, 2009 [Page 68]
Internet-Draft DVB-RCS MIB September 2008
unknown (0),
shortframe (1),
longframe (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the frame length used on the forward link for
transmission to the RCST.
Supported values are:
0: Unknown
1: Short frame
2: Normal frame
The RCST will report a value that has been used for
transmission to the RCST within the most recent 60 seconds.
If this is not relevant, the RCST will report 'unknown'."
::={fwdStatusEntry 12}
fwdStatusPilot OBJECT-TYPE
SYNTAX INTEGER {
unknown (0),
pilotNotused (1),
pilotUsed (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether pilots are used on the forward link for
transmission to the RCST.
Supported values are:
0: Unknown
1: Pilots are not used
2: Pilots are used
The RCST will report a value that has been used for
transmission to the RCST within the most recent 60 seconds.
If this is not relevant, the RCST will report 'unknown'."
::={fwdStatusEntry 13}
fwdStatusBer OBJECT-TYPE
SYNTAX Integer32
UNITS "exponent of 10"
Combes Expires March 1, 2009 [Page 69]
Internet-Draft DVB-RCS MIB September 2008
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides the RCST BER on the Forward Link in log10 units."
::={fwdStatusEntry 14}
fwdStatusCnr OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides the RCST CNR on the Forward Link in 0.1 dB units."
::={fwdStatusEntry 15}
fwdStatusRxPower OBJECT-TYPE
SYNTAX Integer32
UNITS "0.1 dBm"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides the power level of the Forward Link as received at
the IDU, in 0.1 dBm units."
DEFVAL { -500 }
::={fwdStatusEntry 16}
--===================================================================
-- rtnConfig sub-tree object types
--===================================================================
rtnConfigMaxEirp OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dBm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Max EIRP of the RCST given in resolution of 0.1 dBm,
applied when the IDU can itself set the necessary IDU TX
output level e.g. when using a BUC that has a power level
detector and provides sufficient feedback to the IDU."
::= {rtnConfig 1}
Combes Expires March 1, 2009 [Page 70]
Internet-Draft DVB-RCS MIB September 2008
rtnConfigDefIfLevel OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dBm"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"IDU TX output level applied in case the rtnConfigMaxEirp
cannot be used. The resolution is 0.1 dBm and the accuracy
is +/- 1 dBm."
::= {rtnConfig 2}
--===================================================================
-- rtnStatus sub-tree object types
--===================================================================
rtnStatusEbN0 OBJECT-TYPE
SYNTAX Integer32
UNITS "x0.1 dB"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The EbN0 value reported for the return link, referenced to
the regular SYNC burst transmission, in 0.1 dB units."
::= {rtnStatus 1}
rtnStatusSFDuration OBJECT-TYPE
SYNTAX Integer32 (250..7500)
UNITS "0.1 ms"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The duration of the currently applied return link super-
frame structure, in tenths of milliseconds."
::= {rtnStatus 2}
rtnStatusPayloadUnit OBJECT-TYPE
SYNTAX INTEGER {
unitATM (0),
unitMPEG (1)
}
MAX-ACCESS read-only
STATUS current
Combes Expires March 1, 2009 [Page 71]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION
"Indicates if the payload unit used for the return link is
ATM or MPEG."
::= {rtnStatus 3}
--==================================================================
-- conformance information
--==================================================================
rcstGroups OBJECT IDENTIFIER ::= {dvbrcsConformance 1}
rcstCompliances OBJECT IDENTIFIER ::= {dvbrcsConformance 2}
--==================================================================
-- conformance statements
--==================================================================
rcstCompliance1 MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for DVB-RCS terminals that are
compliant with SatLabs System Recommendations. "
MODULE -- this module
MANDATORY-GROUPS {rcstSystemGroup, rcstNetworkGroup,
rcstInstallGroup, rcstQosGroup, rcstControlGroup, rcstStateGroup,
fwdConfigGroup, fwdStatusGroup, rtnConfigGroup, rtnStatusGroup}
GROUP rcstExtSystemGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the SNMPMISC option."
GROUP rcstExtNetworkGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the SNMPMISC option."
GROUP rcstDnsGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the DNS option."
GROUP rcstExtInstallGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the INSTALL_LOG feature."
Combes Expires March 1, 2009 [Page 72]
Internet-Draft DVB-RCS MIB September 2008
GROUP rcstEnhancedClassifierGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the ENHCLASSIFIER feature."
GROUP rcstMpegQosGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the MPEG_TRF option."
GROUP rcstGlobalQosGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the RCST_PARA feature."
GROUP rcstStrictQosGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the CHID_STRICT option."
GROUP rcstExtControlGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the SNMPMISC option."
GROUP rtnExtConfigGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the SNMPMISC option."
GROUP rtnExtStatusGroup
DESCRIPTION "This group is mandatory for an RCST
that claims to support the SNMPMISC option."
OBJECT systemOduAntennaGain
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT systemOduTxType
MIN-ACCESS read-only
DESCRIPTION "Write access required if the RCST does
not provide the information."
OBJECT systemOduRxType
Combes Expires March 1, 2009 [Page 73]
Internet-Draft DVB-RCS MIB September 2008
MIN-ACCESS read-only
DESCRIPTION "Write access required if the RCST does
not provide the information."
OBJECT systemOduRxBand
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT systemOduRxLO
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT systemOduTxLO
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT pktClassDscpLow
MIN-ACCESS read-only
DESCRIPTION "Create access only required if
ENHCLASSIFIER support is claimed."
OBJECT pktClassDscpHigh
MIN-ACCESS read-only
DESCRIPTION "Create access only required if
ENHCLASSIFIER support is claimed."
OBJECT pktClassDscpMarkValue
MIN-ACCESS read-only
DESCRIPTION "Create access only required if
ENHCLASSIFIER support is claimed."
OBJECT phbName
MIN-ACCESS read-only
DESCRIPTION "Create access only required if SNMPMISC
support is claimed."
OBJECT phbRequestClassAssociation
MIN-ACCESS read-only
Combes Expires March 1, 2009 [Page 74]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION "Create access only required if SNMPMISC
support is claimed."
OBJECT phbMappingRowStatus
MIN-ACCESS read-only
DESCRIPTION "Create access only required if SNMPMISC
support is claimed."
OBJECT requestClassName
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassChanId
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassVccVpi
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassVccVci
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassPidPoolReference
MIN-ACCESS not-accessible
DESCRIPTION "Read-only access required if MPEG option
is claimed. Write access only required if also SNMPMISC
support is claimed."
OBJECT requestClassCra
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassRbdcMax
MIN-ACCESS read-only
Combes Expires March 1, 2009 [Page 75]
Internet-Draft DVB-RCS MIB September 2008
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassRbdcTimeout
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassVbdcMax
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassVbdcTimeout
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassVbdcMaxBackLog
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT requestClassRowStatus
MIN-ACCESS read-only
DESCRIPTION "Write access only required if SNMPMISC
support is claimed."
OBJECT pidValue
MIN-ACCESS not-accessible
DESCRIPTION "Read-only access required if MPEG option
is claimed. Write access only required if also SNMPMISC
support is claimed."
OBJECT pidPoolRowStatus
MIN-ACCESS not-accessible
DESCRIPTION "Read-only access required if MPEG option
is claimed. Write access only required if also SNMPMISC
support is claimed."
::= { rcstCompliances 1 }
Combes Expires March 1, 2009 [Page 76]
Internet-Draft DVB-RCS MIB September 2008
--==================================================================
-- units of conformance
--==================================================================
--==================================================================
-- object groups for rcst system
--==================================================================
rcstSystemGroup OBJECT-GROUP
OBJECTS {
systemMibRevision,
systemSatLabsProfilesDeclaration,
systemSatLabsOptionsDeclaration,
systemSatLabsFeaturesDeclaration,
systemLocation,
systemOduAntennaGain,
systemOduTxType,
systemOduRxType,
systemOduRxBand,
systemOduRxLO,
systemOduTxLO,
tcpPep,
httpPep
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable for basic device management support."
::= { rcstGroups 1 }
rcstExtSystemGroup OBJECT-GROUP
OBJECTS {
systemOduAntennaSize,
systemOduSspa
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable for extended device management support."
::= { rcstGroups 2 }
Combes Expires March 1, 2009 [Page 77]
Internet-Draft DVB-RCS MIB September 2008
--==================================================================
-- object groups for rcst networking
--==================================================================
rcstNetworkGroup OBJECT-GROUP
OBJECTS {
networkOamIpAddress,
networkOamIpNetworkMask,
networkLanIpAddress,
networkLanIpNetworkMask,
networkConfigFileDownloadUrl,
networkConfigFileUploadUrl,
networkLogFileUploadUrl
}
STATUS current
DESCRIPTION "A collection of objects providing basic
networking management support."
::= { rcstGroups 3 }
rcstExtNetworkGroup OBJECT-GROUP
OBJECTS {
networkOamIpAddressAssign,
networkAirInterfaceDefaultGateway,
networkNccMgtIpAddress
}
STATUS current
DESCRIPTION "A collection of objects providing extended
networking management support."
::= { rcstGroups 4 }
rcstDnsGroup OBJECT-GROUP
OBJECTS {
primaryDnsServerIpAddress,
secondaryDnsServerIpAddress
}
STATUS current
DESCRIPTION "IP addresses of the primary and secondary DNS
servers to be used to resolve URL's as needed."
::= { rcstGroups 5 }
--==================================================================
Combes Expires March 1, 2009 [Page 78]
Internet-Draft DVB-RCS MIB September 2008
-- object groups for rcst installation
--==================================================================
rcstInstallGroup OBJECT-GROUP
OBJECTS {
installAntennaAlignmentState,
installCwFrequency,
installCwMaxDuration,
installCwPower,
installCoPolReading,
installXPolReading,
installCoPolTarget,
installXPolTarget,
installStandByDuration,
installTargetEsN0
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable for basic installation support."
::= { rcstGroups 6 }
rcstExtInstallGroup OBJECT-GROUP
OBJECTS {
networkInstallLogFileDownloadUrl,
networkInstallLogFileUploadUrl
}
STATUS current
DESCRIPTION "A collection of objects providing extended
device installation support."
::= { rcstGroups 7 }
--==================================================================
-- object groups for QOS
--==================================================================
rcstQosGroup OBJECT-GROUP
OBJECTS {
pktClassDscpLow,
pktClassDscpHigh,
Combes Expires March 1, 2009 [Page 79]
Internet-Draft DVB-RCS MIB September 2008
pktClassDscpMarkValue,
pktClassPhbAssociation,
pktClassRowStatus,
phbName,
phbRequestClassAssociation,
phbMappingRowStatus,
requestClassName,
requestClassChanId,
requestClassVccVpi,
requestClassVccVci,
requestClassCra,
requestClassRbdcMax,
requestClassRbdcTimeout,
requestClassVbdcMax,
requestClassVbdcTimeout,
requestClassVbdcMaxBackLog,
requestClassRowStatus
}
STATUS current
DESCRIPTION "A collection of objects providing basic access to
QOS configuration data."
::= { rcstGroups 8 }
rcstEnhancedClassifierGroup OBJECT-GROUP
OBJECTS {
pktClassIpProtocol,
pktClassIpSrcAddress,
pktClassIpSrcAddressMask,
pktClassIpDstAddress,
pktClassIpDstAddressMask,
pktClassSrcPortLow,
pktClassSrcPortHigh,
pktClassDstPortLow,
pktClassDstPortHigh,
pktClassVlanUserPri
}
STATUS current
DESCRIPTION "A collection of objects providing support for
management of the enhanced classifier."
::= { rcstGroups 9 }
Combes Expires March 1, 2009 [Page 80]
Internet-Draft DVB-RCS MIB September 2008
rcstMpegQosGroup OBJECT-GROUP
OBJECTS {
requestClassPidPoolReference,
pidValue,
pidPoolRowStatus
}
STATUS current
DESCRIPTION "A collection of objects providing access to MPEG
related link QOS configuration data."
::= { rcstGroups 10 }
rcstGlobalQosGroup OBJECT-GROUP
OBJECTS {
qosGlobalRbdcMax,
qosGlobalVbdcMax,
qosGlobalVbdcMaxBackLog
}
STATUS current
DESCRIPTION "A collection of objects providing access to
global RCST QOS configuration data."
::= { rcstGroups 11 }
rcstStrictQosGroup OBJECT-GROUP
OBJECTS {
qosChannelIdStrictDispatching
}
STATUS current
DESCRIPTION "A collection of objects allowing management of
strict channel ID dispatching."
::= { rcstGroups 12 }
--==================================================================
-- object groups for rcst control
--==================================================================
rcstControlGroup OBJECT-GROUP
OBJECTS {
ctrlRebootCommand,
ctrlUserTrafficDisable,
ctrlCwEnable,
ctrlDownloadFileCommand,
ctrlUploadFileCommand,
Combes Expires March 1, 2009 [Page 81]
Internet-Draft DVB-RCS MIB September 2008
ctrlActivateConfigFileCommand
}
STATUS current
DESCRIPTION "A collection of objects allowing basic RCST
control."
::= { rcstGroups 13 }
rcstExtControlGroup OBJECT-GROUP
OBJECTS {
ctrlRcstTxDisable,
ctrlOduTxReferenceEnable,
ctrlOduTxDCEnable,
ctrlOduRxDCEnable,
ctrlRcstLogonCommand,
ctrlRcstLogoffCommand
}
STATUS current
DESCRIPTION "A collection of objects allowing extended RCST
control."
::= { rcstGroups 14 }
--==================================================================
-- object groups for rcst state
--==================================================================
rcstStateGroup OBJECT-GROUP
OBJECTS {
rcstMode,
rcstFaultStatus,
rcstFwdLinkStatus,
rcstLogUpdated,
rcstCurrentSoftwareVersion,
rcstAlternateSoftwareVersion,
rcstActivatedConfigFileVersion,
rcstDownloadedConfigFileVersion
}
STATUS current
DESCRIPTION "A collection of objects allowing access to RCST
state."
::= { rcstGroups 15 }
Combes Expires March 1, 2009 [Page 82]
Internet-Draft DVB-RCS MIB September 2008
--==================================================================
-- object groups for forward link
--==================================================================
fwdConfigGroup OBJECT-GROUP
OBJECTS {
fwdStartPopId,
fwdStartFrequency,
fwdStartPolar,
fwdStartFormat,
fwdStartRolloff,
fwdStartSymbolRate,
fwdStartInnerFec,
fwdStartRowStatus
}
STATUS current
DESCRIPTION "A collection of objects providing basic start
forward link configuration support."
::= { rcstGroups 16 }
fwdStatusGroup OBJECT-GROUP
OBJECTS {
fwdStatusPopId,
fwdStatusIfReference,
fwdStatusNetId,
fwdStatusNetName,
fwdStatusFormat,
fwdStatusFrequency,
fwdStatusPolar,
fwdStatusInnerFec,
fwdStatusSymbolRate,
fwdStatusRolloff,
fwdStatusModulation,
fwdStatusFecFrame,
fwdStatusPilot,
fwdStatusBer,
fwdStatusCnr,
fwdStatusRxPower
}
Combes Expires March 1, 2009 [Page 83]
Internet-Draft DVB-RCS MIB September 2008
STATUS current
DESCRIPTION "A collection of objects providing forward link
status."
::= { rcstGroups 17 }
--==================================================================
-- object groups for return link
--==================================================================
rtnConfigGroup OBJECT-GROUP
OBJECTS {
rtnConfigDefIfLevel
}
STATUS current
DESCRIPTION "A collection of objects providing basic return
link configuration support."
::= { rcstGroups 18 }
rtnExtConfigGroup OBJECT-GROUP
OBJECTS {
rtnConfigMaxEirp
}
STATUS current
DESCRIPTION "A collection of objects providing extended
return link configuration support."
::= { rcstGroups 19 }
rtnStatusGroup OBJECT-GROUP
OBJECTS {
rtnStatusPayloadUnit
}
STATUS current
DESCRIPTION "A collection of objects allowing access to return
link status."
::= { rcstGroups 20 }
rtnExtStatusGroup OBJECT-GROUP
OBJECTS {
rcstRtnLinkStatus,
rtnStatusEbN0,
Combes Expires March 1, 2009 [Page 84]
Internet-Draft DVB-RCS MIB September 2008
rtnStatusSFDuration
}
STATUS current
DESCRIPTION "A collection of objects allowing access to
extended return link status."
::= { rcstGroups 21 }
END
5. Security Considerations
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments.
SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure (for example by using IPsec), even
then, there is no control as to who on the secure network is allowed
to access and GET/SET (read/change/create/delete) the objects in this
MIB module.
It is RECOMMENDED that implementers consider the security features
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations
This document includes no request to IANA. The transmission and
ifType numbers described in Section 3 have already been assigned
under the smi-numbers registry.
Combes Expires March 1, 2009 [Page 85]
Internet-Draft DVB-RCS MIB September 2008
7. Acknowledgments
The authors thank Gorry Fairhurst for advice in the preparation of
this document.
The authors recognize this document is a collective effort of the
SatLabs Group (www.satlabs.org), in particular the many corrections
and suggestions brought by Juan Luis Manas.
Combes Expires March 1, 2009 [Page 86]
Internet-Draft DVB-RCS MIB September 2008
8. References
8.1. Normative References
[IANA] Internet Assigned Numbers Authority, "Internet Assigned
Numbers Authority", June 2008,
<http://www.iana.org/assignments/smi-numbers>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997 (BEST
CURRENT PRACTICE).
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information,
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April
1999.
[RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB",
RFC 2863, June 2000.
8.2. Informative References
[ISO-MPEG] ISO/IEC DIS 13818-1:2000, "Information Technology;
Generic Coding of Moving Pictures and Associated Audio
Information Systems", International Standardisation
Organisation (ISO).
[ETSI-DAT] EN 301 192, "Digital Video Broadcasting (DVB); DVB
Specifications for Data Broadcasting", European
Telecommunications Standards Institute (ETSI).
[ETSI-DVBS] EN 301 421 "Digital Video Broadcasting (DVB); Modulation
and Coding for DBS satellite systems at 11/12 GHz",
European Telecommunications Standards Institute (ETSI).
Combes Expires March 1, 2009 [Page 87]
Internet-Draft DVB-RCS MIB September 2008
[ETSI-DVBS2] ETSI EN 302 307 "Digital Video Broadcasting (DVB);
Second generation framing structure, channel coding and
modulation systems for Broadcasting, Interactive Services,
News Gathering and other broadband satellite applications",
European Telecommunications Standards Institute (ETSI).
[ETSI-GSE] ETSI TS 102 606 "Digital Video Broadcasting (DVB);
Generic Stream Encapsulation (GSE) Protocol", European
Telecommunications Standards Institute (ETSI).
[ETSI-RCS] ETSI 301 791 "Digital Video Broadcasting (DVB);
Interaction Channel for Satellite Distribution Systems",
European Telecommunications Standards Institute (ETSI).
[ETSI-SI] ETSI EN 300 468 "Digital Video Broadcasting (DVB);
Specification for Service Information (SI) in DVB Systems",
European Telecommunications Standards Institute (ETSI).
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC4259] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini-
Nocker, B., and H. Linder, "A Framework for Transmission of
IP Datagrams over MPEG-2 Networks", RFC 4259, November
2005.
[SATLABS] SatLabs System Recommendations. Available at
www.satlabs.org.
Combes Expires March 1, 2009 [Page 88]
Internet-Draft DVB-RCS MIB September 2008
9. Authors' Addresses
Stephane Combes
ESTEC
European Space Agency
Keplerlaan 1 - - P.O. Box 299
2200 AG Noordwijk ZH
The Netherlands
Email: stephane.combes@esa.int
URL: telecom.esa.int
Petter Chr. Amundsen
VeriSat AS
P.O Box 1
1330 Fornebu
Norway
Email: pca@verisat.no
URL: www.verisat.no
Micheline Lambert
Advantech Satellite Networks
2341 boul. Alfred-Nobel
Saint-Laurent (Montreal,)H4S 2A9
Quebec, Canada
Email: micheline.lambert@advantechamt.com
URL: www.advantechsatnet.com
Hans-Peter Lexow
STM Norway
Vollsveien 21
1366 Lysaker
Norway
Email: hlexow@stmi.com
URL: www.stmi.com
10. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
Combes Expires March 1, 2009 [Page 89]
Internet-Draft DVB-RCS MIB September 2008
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
11. Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
12. Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Combes Expires March 1, 2009 [Page 90]
Internet-Draft DVB-RCS MIB September 2008
<<< RFC Ed Note: please remove the text below, prior to publications
>>>
Change Log.
Rev -00
* First draft, for comment by the community.
Rev -01
* Second draft, for comment by the community.
The MIB module is renamed DVBRCS-MIB to reflect that it covers more
than solely interface issues.
The MIB has been updated with
* a conformance section that captures the options
* structural changes and corrections to achieve this
* SYNTAX refinements where applicable
* UNITS declarations where applicable
Document reformatted to conform to I-D format conventions.
Rev -02
* Third draft, for comment by the community.
Update following comments received from the ipdvb list (Gorry
Fairhurst).
Rev -03
* Fourth draft, for comment by the community.
Update following comments received from Martin Stiemerling and
complement/corrections from the SatLabs Group.
Rev -04
Combes Expires March 1, 2009 [Page 91]
Internet-Draft DVB-RCS MIB September 2008
* Fifth draft
Corrected read-write into read-create MAXACCESS for objects in
requestClassTable and pidPoolTable.
Minor updates to correct format of tables and some MIB comments.
<<<End of RFC Ed Note >>
Combes Expires March 1, 2009 [Page 92]
