mib IRD-2900_SNMP_Rev._4.6

IRD-2900 MIB

Simple Network Management Protocol

USER GUIDELINES SCOPUS DOCUMENTS (P/N 100988)

(REV. 4.6/SW V1.80/OCTOBER 2007)

Scopus Video Networks Ltd.

International Headquarters

Scopus Video Networks Inc.

Americas

10 Ha’amal St., Park Afek

Rosh Ha’ayin, 48092

Israel

3 Independence Way

Princeton, NJ 08540.

USA

Tel: (972) –3-9007777

Fax: (972) –3-9007888

Tel: (609)-987-8090

Fax: (609)-987-8095

Email: [email protected]

Web: www.scopus.net

Email: [email protected]

Web: www.scopususa.com

DOCUMENT HISTORY

VERSION DATE DETAILS

1.0 August 2005 Preliminary version

2.0 January 2006 Update with support for scAlarm and scTraps.

3.0 March 2006 Updated for SW v1.45.

3.5 June 2006 Updated for SW v1.55. Added support for tsTests and scTests.

4.0 September 2006 Updated for SW v1.60. Added support for scIrdStreamFiltering. .

4.5 June 2007 Update for SW v1.70 Added support for scFiles and

satellitePreferencesTable

© 2006 Scopus Video Networks, Ltd. All rights reserved.

Scopus Video Networks, Ltd. reserves the rights to alter the equipment specifications and descriptions in this

publication without prior notice. No part of this publication shall be deemed to be part of any contract or warranty

unless specifically incorporated by reference into such contract or warranty.

The information contained herein is merely descriptive in nature and does not constitute a binding offer for sale of the

product detailed herein.

File IRD-2900 SNMP Rev. 4.5.doc. Saved 11/26/2007 3:08:00 PM

IRD-2900 MIB


Scopus Documents (p/n 100988) Page 1

TABLE OF CONTENTS

Chapter 1. Overview........................................................1-1 1.1. Login to the MIB............................................................... 1-2 1.1.1. Community Settings ......................................................... 1-3

1.2. Standard MIB Introduction................................................. 1-4 1.2.1. Interfaces MIB.................................................................. 1-4 1.2.2. Entity MIB (entityMIB)....................................................... 1-5 1.2.3. Transport Stream Tests (tsTests)........................................ 1-5 1.2.4. Satellite Preferences Table (satellitePreferencesTable)........... 1-5

1.3. Scopus-Common MIB Introduction...................................... 1-6 1.4. IRD-2900 MIB Introduction................................................ 1-7

Chapter 2. MIB Implementation ......................................2-1 2.1. Standard MIB................................................................... 2-3 2.1.1. Interface MIB (interfaces and ifMIB).................................... 2-4 2.1.2. Entity MIB (entityMIB)....................................................... 2-9 2.1.3. Transport Stream Tests (tsTests)...................................... 2-15 2.1.4. Satellite Preferences Table (satellitePreferencesTable)......... 2-17

2.2. Scopus-Common MIB...................................................... 2-19 2.2.1. Agent (scAgent) ............................................................. 2-20 2.2.2. Alarms (scAlarms) .......................................................... 2-21 2.2.3. Traps (scTraps) .............................................................. 2-26 2.2.4. IP (scIp) ........................................................................ 2-30 2.2.5. Stream (scStream) ......................................................... 2-31 2.2.6. Scopus Tests (scTests) .................................................... 2-35 2.2.7. Scopus GPIO (scGpio) ..................................................... 2-41 2.2.8. File (scFile) .................................................................... 2-43

2.3. Notifications................................................................... 2-27 2.4. IRD-2900 MIB ................................................................ 2-47 2.4.1. Receiver Objects (scIrdReceiver) ...................................... 2-48 2.4.2. Stream Objects (scIrdStream).......................................... 2-56 2.4.3. Service Objects (scIrdService) ......................................... 2-61 2.4.4. Video Objects (scIrdVideo)............................................... 2-64 2.4.5. Audio Objects (scIrdAudio) .............................................. 2-70 2.4.6. Data Objects (scIrdData) ................................................. 2-73 2.4.7. CAS Objects (scCas) ....................................................... 2-76

Chapter 3. Configuration Procedure with MIB .................3-1 3.1. Error Tests Configuration- Counters, Alarms, and Traps......... 3-2 3.1.1. Error Counters ................................................................. 3-2 3.1.2. Alarms ............................................................................ 3-4 3.1.3. Traps .............................................................................. 3-5 3.1.4. Tests State Machine.......................................................... 3-8

3.2. Receiver Configuration ...................................................... 3-9

User Guidelines

Overview

Page 2 (Rev. 4.6/SW v1.80/October 2007)

3.2.1. Satellite Parameters.......................................................... 3-9 3.2.2. IP Parameters .................................................................3-20

3.3. Stream Configuration.......................................................3-31 3.3.1. Stream Ports...................................................................3-32 3.3.2. Synchronization ..............................................................3-34 3.3.3. Stream Type...................................................................3-36 3.3.4. ASI Mode .......................................................................3-36 3.3.5. Filters ............................................................................3-36

3.4. Service...........................................................................3-40 3.4.1. Service Configuration.......................................................3-40 3.4.2. Service Port Table ...........................................................3-47 3.4.3. Service Configuration.......................................................3-48 3.4.4. Setting Service Parameters...............................................3-50

3.5. Video Configuration .........................................................3-57 3.5.1. Video .............................................................................3-58 3.5.2. VBI................................................................................3-62 3.5.3. OSD...............................................................................3-67

3.6. Audio Configuration .........................................................3-74 3.6.1. General Parameters .........................................................3-75 3.6.2. Musicam.........................................................................3-78 3.6.3. Linear PCM .....................................................................3-81 3.6.4. Dolby Digital AC-3 ...........................................................3-84 3.6.5. AC-3 Pass-Through..........................................................3-87

3.7. Data Configuration ..........................................................3-88 3.7.1. High-Speed Data (HSD) ...................................................3-89 3.7.2. IP Data ..........................................................................3-90 3.7.3. Low-Speed Data (LSD).....................................................3-91

3.8. CAS Configuration ...........................................................3-93 3.8.1. BISS-E Clear SW Mode.....................................................3-94 3.8.2. BISS Mode 1...................................................................3-95 3.8.3. Even-Odd Mode...............................................................3-97 3.8.4. BISS-E Buried ID Mode ....................................................3-98 3.8.5. BISS-E Injected ID Mode................................................3-100

IRD-2900 MIB



LIST OF FIGURES

Figure 1-1: Signal Path in IRD-2900 ...................................................... 1-1 Figure 1-2: MIB Browser Connection...................................................... 1-2 Figure 2-1: IRD-2900 MIB Tree – General View....................................... 2-2 Figure 2-2: Interface Table (ifTable) ...................................................... 2-5 Figure 2-3: Service Port Configuration Table (scIrdServiceConfigPortTable) 2-6 Figure 2-4: Interface Stack Table (ifStackTable)...................................... 2-7 Figure 2-5: Interface Table (ifTable) ...................................................... 2-8 Figure 2-6: Physical Entity Table (entPhysicalTable) ................................ 2-9 Figure 2-7: Satellite Configuration Parameters (scIrdRcvSatelliteConfigTable)2-

10 Figure 2-8: Entity Physical Table (entPhysicalTable) ...............................2-11 Figure 2-9: Entity Alias Mapping Table (entAliasMappingTable) ................2-13 Figure 2-10: Entity Physical Table (entPhysicalTable) ...............................2-14 Figure 2-11: Interface Table (ifTable) .....................................................2-14 Figure 2-12: Tests Summary Table (tsTestsSummaryTable) ......................2-16 Figure 2-13: Satellite Preferences Table (satellitePreferencesTable)............2-18 Figure 2-14: Current Alarms Table (scAlarmsCurrentTable) .......................2-22 Figure 2-15: Alarm Configuration Table (scAlarmsConfTable).....................2-25 Figure 2-16: Traps Destination Table (scTrapsDestTable) ..........................2-26 Figure 2-17: Traps Log .........................................................................2-28 Figure 2-18: Scopus IP Table (scIpTable) ................................................2-30 Figure 2-19: PMT to Channel Process......................................................2-32 Figure 2-20: Scopus Tests Tree (scTests)................................................2-35 Figure 2-21: Scopus Tests Table (scTestsTable) .......................................2-37 Figure 2-22: Scopus Tests Summary (scTestsSummaryTable) and Transport

Stream Tests Summary (tsTestsSummaryTable) Tables Display2-39 Figure 2-23: Scopus GPIO Table (scGpioOutputConfTable) ........................2-41 Figure 2-24: File Operation Table (scFileOperationTable)...........................2-43 Figure 2-25: Files Table (scFilesTable) ....................................................2-46 Figure 2-26: IRD-2900 MIB Tree............................................................2-47 Figure 2-27: Satellite Configuration Table Parameters

(scIrdRcvSatelliteConfigTable).............................................2-49 Figure 2-28: Satellite Status Table Parameters (scIrdRcvSatelliteStatusTable)2-51 Figure 2-29: Satellite Preferences Table (scIrdRcvSatellitePreferencesTable)2-52 Figure 2-30: IP Configuration Table Parameters (scIrdRcvIpConfigTable) ....2-53 Figure 2-31: IP Port Configuration Table Parameters (scIrdRcvIpConfigPortTable)

.......................................................................................2-54 Figure 2-32: IP Status Table Parameters (scIrdRcvIpStatusTable) ..............2-55 Figure 2-33: Control Parameters group (scIrdStreamControlGroup)............2-57

User Guidelines

Overview


Figure 2-34: Information Table Parameter (scIrdStreamInfoTable).............2-58 Figure 2-35: Filtering Group Parameters (scIrdStreamFilteringGroup).........2-59 Figure 2-36: Filtering Service Table Parameters

(scIrdStreamFilteringServiceTable) ......................................2-60 Figure 2-37: Filtering PID Table Parameters (scIrdStreamFilteringPidTable) 2-60 Figure 2-38: Strategy Parameters (scIrdServiceStrategy) .........................2-61 Figure 2-39: Service Port Table Parameters (scIrdServiceConfigPortTable)..2-62 Figure 2-40: Channel Table (scIrdServiceConfigChannelTable)...................2-63 Figure 2-41: Video Configuration Table Parameters (scIrdVideoConfigTable)2-65 Figure 2-42: VBI Configuration Table Parameters (scIrdVbiConfigTable) .....2-66 Figure 2-43: OSD Configuration Table Parameters (scIrdOsdConfigTable) ...2-67 Figure 2-44: OSD Text Insertion Table Parameters

(scIrdOsdTextInsertionConfigTable) .....................................2-68 Figure 2-45: Video MPEG Header Table Parameters (scIrdVideoMpegHeaderTable)

.......................................................................................2-69 Figure 2-46: Audio Configuration Table Parameters (scIrdAudioConfigTable)2-70 Figure 2-47: HSD Configuration Table Parameters (scIrdHsdConfigTable) ...2-73 Figure 2-48: IP Data Table Parameters (scIrdIpDataConfigTable)...............2-74 Figure 2-49: Low-Speed Data Table Parameters (scIrdLsdConfigTable).......2-75 Figure 3-1: Test State Machine ..............................................................3-8 Figure 3-2: Physical Entity Table (entPhysicalTable) .................................3-9 Figure 3-3: Satellite Tables Tree ..........................................................3-10 Figure 3-4: LNB L.O. Frequency Parameters Group.................................3-11 Figure 3-5: LNB Information Tree Parameters Group ..............................3-12 Figure 3-6: Satellite Frequency Parameters Group..................................3-13 Figure 3-7: Satellite Rate Parameters Group.........................................3-14 Figure 3-8: Viterbi Error Correction Parameters Group............................3-15 Figure 3-9: Drift Compensation Parameters Group .................................3-16 Figure 3-10: Spectral Inversion Parameters Group...................................3-17 Figure 3-11: Satellite Signal Parameters Group .......................................3-19 Figure 3-12: Physical Entity Table (entPhysicalTable) ...............................3-20 Figure 3-13: IP Receiver Tables Tree ......................................................3-21 Figure 3-14: IP Receiver Configuration Table (scIrdRcvIpConfigTable) ........3-22 Figure 3-15: IP Port Configuration Table (scIrdRcvIpConfigPortTable).........3-22 Figure 3-16: IP Network Configuration Table (scIpTable) ..........................3-23 Figure 3-17: IP Configurations and Parameter Relations in IP Tables ..........3-24 Figure 3-18: Failover Errors ..................................................................3-25 Figure 3-19: Active Port interface Index Parameters Group .......................3-26 Figure 3-20: IP Definitions Parameters Group..........................................3-28 Figure 3-21: Stream Tree .....................................................................3-31 Figure 3-22: Stream Ports Parameters Group ..........................................3-33 Figure 3-23: Synchronization Parameters Group ......................................3-35 Figure 3-24: Stream Filtering Tree Structure ...........................................3-37

IRD-2900 MIB



Figure 3-25: Interface Table (ifTable) .....................................................3-40 Figure 3-26: Service Port Table (scIrdServiceConfigPortTable)...................3-41 Figure 3-27: Service Tree......................................................................3-41 Figure 3-28: Service Port Parameters Group............................................3-43 Figure 3-29: Service Channel and Port Indexes........................................3-45 Figure 3-30: Service Channel Parameters Group ......................................3-46 Figure 3-31: Service Port Table (scIrdServiceConfigPortTable)...................3-47 Figure 3-32: Interface Table – Index Source (ifTable – Instance, ifDescr, and

ifType) .............................................................................3-47 Figure 3-33: Stream Service Table (scStreamServiceTable).......................3-48 Figure 3-34: Set Service Description ......................................................3-49 Figure 3-35: Service Configuration – PCR PID Column (scIrdServiceConfigPortPid)

.......................................................................................3-50 Figure 3-36: Service Configuration – Channel Column

(scIrdServiceConfigPortChannel) .........................................3-51 Figure 3-37: Select Service Process........................................................3-52 Figure 3-38: Service Configuration – PCR Interface Index Column

(scIrdServiceConfigPortPcrIfIndex) ......................................3-54 Figure 3-39: Service Configuration – Preferred Language Column

(scIrdServiceConfigPortPrefLanguage)..................................3-55 Figure 3-40: Service Configuration – Page Column (scIrdServiceConfigPortPage)

.......................................................................................3-56 Figure 3-41: Video and VBI Tree ............................................................3-57 Figure 3-42: Video Tree ........................................................................3-58 Figure 3-43: Video Format Parameters Group..........................................3-59 Figure 3-44: Aspect-Ratio Parameters Group...........................................3-60 Figure 3-45: Lips Synchronization Parameters Group................................3-61 Figure 3-46: VBI Configuration Table (scIrdVbiConfigTable) ......................3-62 Figure 3-47: VBI Tree...........................................................................3-63 Figure 3-48: VBI Type Parameters Group................................................3-65 Figure 3-49: VBI Definitions Parameters Group........................................3-66 Figure 3-50: OSD Tree..........................................................................3-68 Figure 3-51: OSD Outputs Parameters Group ..........................................3-70 Figure 3-52: OSD Position Parameters Group ..........................................3-71 Figure 3-53: OSD Subtitle Mode Parameters Group ..................................3-73 Figure 3-54: Audio Tree ........................................................................3-74 Figure 3-55: General Parameters Group..................................................3-75 Figure 3-56: Decoding Mode Parameters Group .......................................3-76 Figure 3-57: Musicam Tree....................................................................3-78 Figure 3-58: MPEG Identity Parameters Group.........................................3-79 Figure 3-59: MPEG Rate Parameters Group .............................................3-80 Figure 3-60: Linear PCM Tree ................................................................3-81 Figure 3-61: Linear Identity Parameters Group ........................................3-82

User Guidelines

Overview


Figure 3-62: Linear Rate Parameters Group ............................................3-83 Figure 3-63: Dolby AC-3 Tree................................................................3-84 Figure 3-64: AC-3 Identity Parameters Group..........................................3-85 Figure 3-65: AC-3 Rate Parameters Group ..............................................3-86 Figure 3-66: AC-3 Pass Through Tree .....................................................3-87 Figure 3-67: Data Tree .........................................................................3-88 Figure 3-68: HSD Table (scIrdHsdConfigTable) ........................................3-89 Figure 3-69: IP Table (scIrdIpDataConfigTable) .......................................3-90 Figure 3-70: Low Speed Data Table Parameters (scIrdLsdConfigTable) .......3-91 Figure 3-71: CAS Tree..........................................................................3-93 Figure 3-72: BISS Clear Mode Parameters Group.....................................3-94 Figure 3-73: BISS Clear Mode Parameters Group.....................................3-96 Figure 3-74: BISS Even-Odd Mode Parameters Group ..............................3-97 Figure 3-75: BISS-E Buried ID Mode Parameters Group............................3-99 Figure 3-76: BISS-E Injected ID Mode Parameters Group ....................... 3-100

IRD-2900 MIB



TERMS AND ABBREVIATIONS

Table 1-1: IRD-2900 SNMP User Guidelines Terms and Abbreviations

TERM DESCRIPTION TERM DESCRIPTION

ASI Asynchronous Serial Interface PAT Program Association Table

ATSC Advanced Television Systems

Committee

PCM Pulse Code Modulation

BER Bit Error Rate PCR Program Clock Reference

C/V Composite Video interface PID Packet Identifier

CA Conditional Access PMT Program Mapping Table

CAS Conditional Access System SPTS Single-Protocol Transport Stream

CAT Conditional Access Table PSI Program Specific Information

CF Compact Flash (card) SI Service Information

DVB Digital Video Broadcast TBC Time Base Corrector

ES Elementary Stream TS Transport Stream

MPEG Motion Picture Expert Group UE Universal Encoder

IRD-2900 MIB


Scopus Documents (p/n 100988) Page 1-1

Chapter 1. OVERVIEW

The IRD-2900 professional MPEG-2 DVB and ATSC processing platform is a

flexible integrated-receiver decoder that receives and decodes: QPSK, IP, and

QAM data. Figure 1-1 illustrates the IRD process of receiving and decoding.

Figure 1-1: Signal Path in IRD-2900

The IRD receives a Transport Stream (TS) from one of its available sources:

QPSK, MPEG-over-IP, or ASI. The TS is then routed by the TS Router block

into the Master and Slave Decoder blocks. Each decoder decodes a single

program from the input stream. Decoder blocks generate digital audio-decoded

and video-decoded streams. These streams are directed to the Video Router

block that routes them to the relevant outputs. The Analog-Video-Outputs

block receives digital video signals, converts them into analog video signals,

and outputs the analog video. The Analog-and-Digital-Audio-Outputs block

receives the routed analog and digital audio signals and outputs digital or analog

audio according to the IRD-2900 audio channel configuration.

User Guidelines

Overview

Page 1-2 (Rev. 4.6/SW v1.80/October 2007)

1.1. LOGIN TO THE MIB NOTE

The images and illustrations in these guidelines were captured using a specific

MIB browser. Different browsers may have different screens and interfaces but

relevant MIB information (objects, OID, names, and so on) remains consistent.

Logging in to the IRD-2900 MIB is performed through connection to the unit. To

connect to the IRD-2900 unit through the MIB browser, perform the following:

1. Initialize the IRD-2900 unit until the front-panel displays the idle screen. For

information about initializing the unit, refer to the IRD-2900 User Manual

document, Chapters 2 and 3.

2. In the front-panel, press [Enter]. The Root menu is displayed.

3. Go to the Ethernet Management screen – Root��Configuration��Unit��

Ethernet Management Port. The screen displays the Ethernet port

definitions of the unit, such as: MAC address, IP address, Subnet mask, and

Default gateway.

4. Open the MIB Browser. In the IP address field, enter the unit’s IP address

and press [Enter] on the keyboard.

Figure 1-2: MIB Browser Connection

IRD-2900 MIB



5. Wait for an authorization message on the relevant section of the screen (in

Figure 1-2 it is the MG-Soft's Query Results section).

Once the message is displayed, the MIB is connected to the IRD-2900 unit.

NOTE

The IRD-2900 is not configured with a default IP address. Thus, in order to login

to the MIB, the user must first configure the unit IP definitions, and only then

can the user operate the IRD through MIB.

For information about setting the IP definitions, refer to the IRD-2900 User

Manual document, Chapter 4.3.8.3.

1.1.1. Community Settings

The MIB community settings must be set as follows:

• Read Community – public

• Set Community – private

Currently no other community settings are supported by the IRD-2900 MIB.

NOTE

The Read and Set community settings are affected by capital cases. Please note

that no capital case is required for the setting.

User Guidelines

Overview


1.2. STANDARD MIB INTRODUCTION The Scopus IRD MIB uses several standard MIB to define basic elements in the

unit. The most common MIB of such are the interface MIB tables and Entity MIB

(entityMIB).

The Scopus IRD-2900 MIB also uses the transport stream tests objects, located

under the DVB Standard MIB (tsTests). The Scopus tests for transport stream

and decoder errors rely on these tables and objects for error counters

information.

Most standard MIB in use are drawn from the mib-2 standard. The mib-2

standard branch is located under the following OID path:

iso(1).org(3).dod(6).internet(1).mgmt(1).mib-2(1).

Other standard MIB objects are located under the dvb standard branch (OID

path 1.3.6.1.4.1), and snmpV2 branch (OID path 1.3.6.1.6).

1.2.1. Interfaces MIB

The interfaces MIB define the interfaces in the unit. Scopus IRD MIB requires the

interface tables in order to define the IRD physical and logical interfaces. Thus,

once define, a network-management system (such as Scopus NMS) can identify

and locate each interface in the unit.

To do so, the Scopus IRD MIB supports two tables: the Interface table (ifTable

of interfaces MIB), and the Interface Stack table (ifStackTable from ifMIB).

The Interface table contains entries of all physical and logical interfaces of the

IRD-2900 unit.

Each entry consists of a number of objects detailed in the MIB. The ifTable gets

all the available information regarding output-decoding ports (such as Video-1,

Audio-3, and so on) as well as the physical interfaces (for example, the Ethernet

management port). the information includes: interface index number, interface

descriptor name, administrative status, and so on. For more information see

Section 2.1.1.1.

The Interface Stack table specifies the connectivity and relations between the

ports and interfaces, both physical and logical. The table displays a hierarchy of

higherLayer and lowerLayer, defining the location of the subject interface in the

unit’s hierarchy. For more information see Section 2.1.1.2.

IRD-2900 MIB



1.2.2. Entity MIB (entityMIB)

The Entity MIB defines the entities in the unit. The MIB tree is divided into four

groups – physical entities, logical entities, mapping entities, and general entities.

Each group contains tables and objects used to define the entities in question.

The Scopus IRD MIB supports two tables from within the entity MIB: the

Physical Entity table (entPhysicalTable) and the Entity Alias Mapping table

(entAliasMappingTable).

The Physical Entity table contains entries of all physical and logical components

that are installed in the IRD. The table entries detail components' information,

such as: component index number, component descriptor name, and so on. For

more information see Section 2.1.2.1.

The Entity Alias Mapping table connects between the physical and logical

components of the Physical Entity table and their equivalent interfaces described

in the Interface table (ifTable). For more information see Section 2.1.2.2.

1.2.3. Transport Stream Tests (tsTests)

The transport stream tests objects conclude of two tables – Tests Summary

table (tsTestsSummaryTable) and PID Tests table (tsTestsPIDTable). These

tables supply information and configuration of transport-stream error counters.

For more information see Section 2.1.3.

1.2.4. Satellite Preferences Table

(satellitePreferencesTable)

The Satellite Preferences Table (satellitePreferencesTable) provides

information regarding specific satellite measurement preferences. For more

information see Section 2-17.

User Guidelines

Overview


1.3. SCOPUS-COMMON MIB

INTRODUCTION The Scopus-Common MIB contains the specific MIB assigned for Scopus Video

Networks, Ltd. The MIB are divided into categories, each supporting a

configuration group pertaining to Scopus general products.

All Scopus-Common MIB are located under the following basic OID path:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scopusRoot(

4466).scopusProducts(1).ScopusCommonMIB(13)

The supported Scopus-Common MIB are categorized as follows:

• Scopus Common MIB Objects – Comprised of the following groups:

• Agent definitions

• Alarm definitions

• Trap definitions

• Configuration-files definitions

• IP definitions

• Tests Definitions

• GPIO definitions

• Stream definitions

• Scopus Common MIB Notifications – Comprised of the following trap

notifications:

• Going to reboot

• Alarm on

• Alarm off

• Settings changed

NOTE

Although the Scopus-Common MIB holds other objects, these lists detail the

objects and notifications supported and used by the IRD-2900 MIB and device.

IRD-2900 MIB



1.4. IRD-2900 MIB INTRODUCTION The Scopus IRD-2900 MIB presents the IRD-2900 configuration and status

objects. Most objects that exist in the MIB are also available through the IRD

Front Panel menus. The IRD-2900 MIB controls the IRD-2900 through the NMS

by getting and setting IRD object values.

All Scopus IRD-2900 MIB are located under the following basic OID path –

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scopusRoot

(4466).scopusProducts(1).scopusIRD(2)

The Scopus IRD-2900 MIB is comprised of eight main groups:

• Receiver – Satellite and IP receiver definitions

• Stream – Transport stream format and identity definitions, as well as filters

setting.

• Service – Service channels and service ports definitions

• Video – Video, VBI, and OSD definitions

• Audio – Analog and digital audio definitions

• Data – High-speed data, low-speed data, and IP-data definitions

• CAS – Conditional Access BISS definitions

NOTE

This IRD-2900 MIB version detailed in this manual is of software version 1.60

and compatible to IRD-2900 software version 1.70.

These user guidelines are comprised of the following chapters:

• MIB Implementation – Short description of the implemented MIB objects

for each category of the IRD-2900 MIB.

• Configuration Procedure – Details configuration processes in each of the

IRD-2900 MIB categories. This chapter also details services setups and

management.

IRD-2900 MIB



Chapter 2. MIB IMPLEMENTATION

This chapter details the implemented MIB objects and their usage for operating

the Scopus IRD-2900 MIB. These MIB allow the user to manage the IRD-2900

through SNMP.

This chapter details four MIB groups:

• Standard MIB – Details the standard MIB used for indexes and other

valuable information (such as element names and descriptions). This chapter

also presents the DVB standard transport stream tests (see Section 2.1).

• Scopus-Common MIB – Details all relevant objects in the Scopus-Common

MIB required for the IRD-2900 MIB operation, such as Agent, Alarms, Traps,

IP, Stream, Tests, and GPIO (see Section 2.1.4).

• Notifications – Details the notifications supported by the Scopus-IRD MIB

(see Section 2.2.8).

• Scopus IRD-2900 MIB – Details all IRD-2900 MIB tables and objects and

the implemented objects and functions (see Section 2.3).

User Guidelines

MIB Implementation


Figure 2-1 provides a general view of the implemented IRD-2900 MIB tree

with the relevant standard and Scopus-Common MIB required for the

operation of the IRD-2900 MIB and management of the decoder.

Figure 2-1: IRD-2900 MIB Tree – General View

IRD-2900 MIB



2.1. STANDARD MIB The following sections detail the Standard MIB tables used for support of

IRD-2900 MIB objects. The Standard MIB tables include the following groups

and tables:

• Interface MIB – Mapping the logical output-decoding ports and physical

interfaces of the unit. This group includes of the Interface table (ifTable)

and the Interface Stack table (ifStackTable). For details see Section 2.1.1.

• Entity MIB – Mapping the physical and logical components – the entiies of

the unit, and reference them to their equivalent interfaces from the ifTable.

This group includes of the Physical Entity table (entPhysicalTable) and

Alias Mapping table (entAliasMappingTable). For details see Section 2.1.2.

• Transport-Stream Tests MIB – Manage transport-stream error-counters,

used for the alarms and traps mechanism. This group includes the Tests

Summary table (tsTestsSummaryTable). For details see Section 2.1.3. the

Tests Summary table also has an augment from the Scopus MIB (see

Section 2.2.6.3).

• Satellite Preference Table (satellitePreferencesTable) – Manages the BER

(bit error rate) maximum rate for testing and alarm mechanism (see Section

2.1.4). This table also has an augment from the Scopus-IRD MIB (see

Section 2.3.1.1).

User Guidelines

MIB Implementation


2.1.1. Interface MIB (interfaces and ifMIB)

The interface MIB branch is used to define the identity and hierarchy order of

the physical and logical interfaces within the IRD-2900 unit. The Scopus IRD MIB

supports two interface MIB tables:

• Interface Table (ifTable) – From the interfaces MIB. This table sets the

definition objects of each interface (see Section 2.1.1.1).

• Interface Stack Table (ifStackTable) – From the ifMIB group. This table

manages the hierarchy of the interfaces compared to higher and lower layer

interfaces (see Section 2.1.1.2).

2.1.1.1. Interface Table (ifTable)

The Interface table in the interfaces MIB holds all physical and logical interfaces

in the IRD-2900 unit. This concludes of physical interfaces, such as ASI input

and outputs, Ethernet ports, video and audio interfaces, as well as logical

output-decoding port such as Video-1, Audio-3, VBI-2, and so on. The table is

concurrently complete with all the interfaces of the device.

The table lists all the interfaces in the unit and details relevant information

regarding the interfaces – such as index number, descriptive name, interface

type, administrative and operative statuses, various counters, and more.

As the Interface table displays the output-decoding ports available in the

IRD-2900, it displays entries holding the name and index number of the

output-decoding ports. Since most IRD-2900 MIB objects affect the output-

decoding ports, this table serves as the most common index source.

The ifTable index source is ifIndex.

OID Path: 1.3.6.1.2.1.2.2

IRD-2900 MIB



Figure 2-2: Interface Table (ifTable)

The interface table details the physical interfaces of the unit, such as:

outputs, inputs, Ethernet ports, and so on. The table also details the IRD's

output-decoding ports, used to map the service elementary streams. The

IRD-2900 output-decoding ports are divided as follows:

• Ethernet Management Port

• MPEG Transport Layer

• Output-decoding ports (such as Video-1, Audio-4, and so on)

• Receiver Port (QPSK or IP)

• ASI input and output ports

The Receiver and ASI ports are physical ports, while the MPEG transport layer

and the output-decoding ports are logical ports. The Ethernet Management Port

is both physical and logical.

User Guidelines

MIB Implementation


The ifIndex column displays the representing numbers of the output-decoding

ports for the MIB. The output-decoding port names are displayed in the ifDescr

column. The interface type (audio, audio output, transport layer and so on) is

detailed in the ifType column. The type is specified according to a standard

hexadecimal representing number.

An index number is a numeric reference to a specific interface. When defined as

index source of a MIB table, the index number is the Instance value of the row.

Te number represents a reference to the interface.

Figure 2-3 shows an example of the Service Port Configuration Table

(scIrdServiceConfigPortTable). The left-most column displays all instances of the

relevant output-decoding ports. The other columns display different service-port

object for each output-decoding port.

Figure 2-3: Service Port Configuration Table (scIrdServiceConfigPortTable)

Each instance number is an identification number of an output-decoding port. To

find the name of the output-decoding port, perform the following:

1. Refer to the index of the table, the ifIndex. To find the table-index source,

refer to the table entry properties display. table-entry objects usually have

the same name as the table, while ending with Entry and not Table (for

example, scIrdServcieConfigPortEntry).

2. Search the table for the requested instance number.

3. Check the information row for the interface descriptor and type (fDesct and

ifType columns). The highlighted index number, 1178992896, is the

instance of the Video-1 output-decoding port, highlighted in the ifTable

example (see previous Figure 2-2).

IRD-2900 MIB



2.1.1.2. Interface Stack Table (ifStackTable)

The Interface Stack table in the ifMIB group defines the hierarchy order of the

interfaces within the IRD-2900 unit.

Each row in the table displays a top-bottom relation between two interfaces. The

Instance value of each row is comprised of the two column values –

ifStackHigherLayer and ifStackLowerLayer – where the Higher Level object is the

top interface ifIndex number, and the Lower Layer object is the bottom interface

ifIndex number.

NOTE

In case there is no Higher or Lower layer interface, the object displays 0.

The index sources of the ifStackTable are:

• ifStackHigherLayer – An index value drawn from ifIndex

• ifStackLowerLayer– An index value drawn from ifIndex

OID Path: 1.3.6.1.2.1.31.1.2

Figure 2-4 displays the Interface Stack table. The highlighted row displays the

relation between two interfaces – 1178599680 and 1174470912.

Figure 2-4: Interface Stack Table (ifStackTable)

User Guidelines

MIB Implementation


In order to search for a verbal description of the interfaces, search the ifTable

for the ifIndex numbers stated before (see Figure 2-5).


After detecting the interfaces' indexes in the ifTable, check the ifDescr object of

each interface. This shows that the relation in which 11778599680 interface is

superior to 1174470912 interface means that MPEG transport-layer interface

is superior to ASI input interface.

IRD-2900 MIB



2.1.2. Entity MIB (entityMIB)

The Entity MIB define the identity of the physical and logical components within

the IRD-2900 unit, as well as the connection between the components and the

relevant interfaces from the ifTable. The Scopus IRD MIB supports two Entity

MIB tables:

• Physical Entity Table (entPhysicalTable) – This table sets the definition

objects of each component (see Section 2.1.2.1).

• Entity Alias Mapping Table (entAliasMappingTable) – This table defines

the connection between each component and it’s equivalent interface from

the ifTable (see Section 2.1.2.3).

2.1.2.1. Physical Entity Table (entPhysicalTable)

The Physical Entity table displays all IRD physical and logical components. The

table also displays each component’s name and index number. This table is used

as MIB index for the IRD-2900 MIB and Scopus-Common MIB objcts that affect

the components, such as the Satellite Configuration table (affecting the QPSK

Card component).

OID Path: 1.3.6.1.2.1.47.1.1.1

Figure 2-6: Physical Entity Table (entPhysicalTable)

User Guidelines

MIB Implementation


Some IRD-2900 MIB tables refer to the Physical Entity table as an index source.

The entPhysicalIndex column contains the index number of the components

(which is displayed and avaialble in the Instance column of Figure 2-6).

Each entry, representing a different component, details various information and

configuration objects, such as: component descriptor name, component location

and containement hierarchy, component class type, and so on.

A table that refers to the entPhysicalIndex as an index source displays the

component index number as reference to the component. For example see

Figure 2-7, displaying the Satellite Configuration table parameters.

Figure 2-7: Satellite Configuration Parameters (scIrdRcvSatelliteConfigTable)

The name column displays the table object names. An index number follows

each name (1392608928). The index number in this example is the QPSK

Card index number, drawn from the Physical Entity table (see previous Figure

2-6). This indicated that the displayed objects (and their set values) affects the

IRD QPSK Card component.

IRD-2900 MIB



2.1.2.2. Physical Entity Parameters and

Hierarchy

The Physical Entity table (entPhysicalTable) creates a hierarchy between the

different components of the unit. Much like the hierarchy order created by the

ifStackTable (see section 2.1.1.2), which creates top-bottom relations between

the interfaces, the Physical Entity table also creates a parent-child relation

between the components of the unit.

Figure 2-8: Entity Physical Table (entPhysicalTable)

Each component is identified by an index number (entPhysicalIndex).

The table than displays a verbal description of the component

(entPhysicalDescr). This is a string of characters providing a short description of

the component. The name object (entPhysicalName, left-most column of Figure

2-8) displays the same string.

The three columns between the entity's description and name are Contained

In, Class, and Relative Position (entPhysicalContainedIn, entPhysicalClass,

and entPhysicalRelPos). These parameters manage the hierarchy of the entities

by representing specific position information:

• Contained in (entPhysicalContainedIn) – Displays the entPhysicalIndex

number of the entity in which the component is contained in. for example,

the Power Supply component (entPhysicalIndex 318767104) is contained in

the Power Supply Slot (entPhysicalIndex 301989888). This creates a

constructive hierarchy of the components and parts assembling the encoder.

• Class (entPhysicalClass) – Displays the component's classification in the

unit. The class is the type of component – module, container, chassis, and

so on. The values are pre-defined by Scopus.

User Guidelines

MIB Implementation


• Relative Position (entPhysicalRelPos) – Displays the Components position

in its parent entity compared to its siblings.

A parent entity is the container of a given entity; for example, the power-

supply slot is the parent of the power supply entity. Sibling entities are

several entities sharing the same parent entity. For example, the Integrated

Decoder Shelf (index 16777216) holds all the slots in the unit making all

slot components siblings.

The relative position object details whether the specific entity, for example

the Fans Slot (entPhysicalIndex 570425344) is the first, second, or even

last slot in the shelf. In this case Fans Slot's relative position is 2, meaning it

is the second sibling.

In addition to these identity and hierarchy parameters, each board component in

the Physical Entity table has two addition information objects:

• Firmware Revision Number (entPhysicalFirmwareRev) – Serves as a part

number specifying the component's purpose. All components of similar use

have the same Firmware revision number, thus identified by Scopus for their

use.

• Serial Number (entPhysicalSerialNum) - Serves as a serial number of the

board. Each and every board installed in a Scopus unit has its own unique

serial number; this to identify between two similar-used boards.

These parameters are mostly used for technical support and are not commonly

used by the user.

These parameters are relevant for Board components only. They return null

value for any other component type.

IRD-2900 MIB



2.1.2.3. Entity Alias Mapping Table (entAliasMappingTable)

The Interface table (ifTable) and the Physical Entity table (entPhysicalTable)

contain indexes of the physical and logical components in the IRD-2900, some

whether referred to as interfaces or entities.

The Entity Alias Mapping table maps between interfaces and entities

representing the same component.

The index sources of the entAliasMappingTable are:

• entPhysicalIndex

• entAliasLogicalIndexOrZero – An index value drawn from the Logical Entity

table (entLogicalTable). Since the IRd-2900 MIB does not support this table,

this value always returns the value 0.

OID Path: 1.3.6.1.2.1.47.1.3.2

Figure 2-9: Entity Alias Mapping Table (entAliasMappingTable)

Figure 2-9 displays the Entity Alias Mapping table. The highlighted row displays

a the index of 1174798592.0, related to the ifIndex 1174798592.

User Guidelines

MIB Implementation


In order to find a verbal description of the entity and interface in question, see

the Physical Entity table and the Interface table (entPhysicalTable and ifTable).

Figure 2-10: Entity Physical Table (entPhysicalTable)


Figure 2-10 and Figure 2-11 display the Entity Physical table and the Interface

table, highlighted with the 1174798592 component. Both tables show that the

reference is to the Ethernet-1 management port.

In other words, the connection between the 1174798592.0 entity component

and 1174798592 interface component is the connection between the

Ethernet-1 entity and Ethernet-1 interface – they are the same component,

displayed and detailed in different tables.

IRD-2900 MIB



2.1.3. Transport Stream Tests (tsTests)

The transport stream tests create transport stream error counter with a wider

range of information than used before.

The transport stream tests MIB OID path is 1.3.6.1.4.1.2696.3.2.1.5.2.

The Transport Stream Tests branch holds the following object groups and tables:

• Tests Summary Table (tsTestsSummaryTable) – Details the transport-

stream tests counters and objects status (see Section 2.1.3.1).

• PIDs Tests Table (tsTestsPIDTable) – Details the PID tests counters and

objects status.

The test counters are enabled for supported-errors only. Since the IRD-2900

does not currently support any PID errors, this table currently returns blank.

The table will be supported in future software releases.

2.1.3.1. Tests Summary Table (tsTestsSummaryTable)

Tests Summary table provides access to the status of all the transport stream

tests performed by the device. The status relates to the transport stream as a

whole, therefore, in the case of PID tests, the table displays the worst result

across all PIDs. The result of each individual PID is presented in the PID Tests

table.

OID Path: 1.3.6.1.4.1.2696.3.2.1.5.2.2

NOTE

The transport stream tests tables display entries and information for errors

supported by the device. The IRD currently does not support PID errors.

Therefore the PID Tests table is not in use by the IRD-2900 MIB.

User Guidelines

MIB Implementation


The Tests Summary table instance is comprised of two indexes: the Test

Number (tsTestsSummaryTestNumber), and the Input Number

(tsTestsSummaryInput Number). These two values are set according to objects

from the table itself (columns two and three).

The input number index display an instance number representing the MPEG-

transport layer port of the counter. A verbal description of this instance value

can be found in the interface table (ifTable, see information in Section 2.1.1).

The test number index represents the type of error counter. The table displays

only entries for error counters supported by the IRD. A verbal description of this

instance can be found in the DVB Standard MIB files. The IRD-2900 MIB

supports the following TS test counters:

• tsSyncLoss (1010)

• continuityCountError (1040)

• transportError (2010)

• crcError (2020)

• pcrDiscontinuityError (2032)

• bufferError (3030)

For example, the first row of the table in Figure 2-12 displays the index of the

following objects:

• Input Number Index (index number 1178599680, drawn from the

interface table. this output-decoding port name – MPEG-transport layer –

can be found in the ifTable, Figure 2-2)

• Test Number Index (index number 1010, displayed in the

tsTestsSummaryTestNumber column)

Figure 2-12 displays the Test Summary table.

Figure 2-12: Tests Summary Table (tsTestsSummaryTable)

IRD-2900 MIB



The Tests table displays the following columns:

• tsTestsSummaryInputNumber – Serves as one of the table indexes. This

parameter holds the index number of the relevant interface which the error

counter regards to. The index is drawn from the ifTable.

• tsTestsSummaryTestNumber – Serves as one of the table indexes.

Contains the index number of the error counter type. Displays an N/A value,

as it is a table index.

• tsTestsSummaryState – Displays the current operation mode of the

counter. The available options are:

• Disable – Counter is disabled

• Pass – Counter does not reach threshold

• Fail – Counter reaches threshold. An alarm is raised.

• tsTestsSummaryEnable – Sets the counter operation modes – enable or

disable.

• tsTestsSummaryCounter – Displays the error counter value – how many

errors have been detected since the last reset of the counter.

• tsTestsSummaryCounterDiscontinuity – Displays the latest timestamp of

the counter reset.

• tsTestsSummaryCounterReset – Allows the user to reset the counter

immediately.

• tsTestsSummaryLatestError – Displays the timestamp of the last error

appearance (for a specific error counter).

• tsTestsSummaryActiveTime – Displays the duration of activity time of the

counter since the device has been powered up.

2.1.4. Satellite Preferences Table (satellitePreferencesTable)

The Satellite Preferences Table (satellitePreferencesTable) defines a

maximum rate for BER measurements preferences.

NOTE

Other preference measurement configurations are supported by the Scopus IRD

MIB (see Section 2.3.1.1)..

OID Path: 1.3.6.1.4.1.2696.3.2.1.8.100

User Guidelines

MIB Implementation


Table index: satellitePrefInputNumber

Figure 2-13 displays the Test Summary table.

Figure 2-13: Satellite Preferences Table (satellitePreferencesTable)

This table consists of the following objects:

• satellitePrefInputNumber – Displays the QPSK card number to which the

preferences apply. The information is drawn from the entityPhysicalTable

(see Section 2.1.2.1). This object also serves as the table's index source.

• satellitePrefBERMax – Defines the maximum limit on the BER (bit error

rate) before Viterbi measurement. If the BER value exceeds this limit an

alarm is raised.

2.1.5. Warm Start (warmStart)

This trap from the snmpTraps branch, which holds SNMPv2 traps and

notification. warmStart trap notify the user of a coming restart to the unit. In

warm-start the unit is reinitializing itself such that its configuration is unaltered.

OID path: 1.3.6.1.6.3.1.1.5.2.

IRD-2900 MIB



2.2. SCOPUS-COMMON MIB This chapter details implemented Scopus-Common MIB groups and objects

important for the alarms and traps MIB and tables specifically and IRD-2900

operation in general. This includes the following groups:

• Agent – Manages basic commands and configurations of the unit, such as

clock and reset (see section 2.2.1).

• Alarms – Manages unit's alarm status and configuration (see Section 2.2.2).

• Traps – Manages destination-hosts of unit's trap messages (see Section

2.2.3).

• IP – Sets the unit's IP address, subnet mask, and default gateway address

(see Section 2.2.4).

• Stream – Manages the unit's table configuration and status, as well as

holding all descriptors information (see Section 2.2.5).

• Tests – Manages the Scopus augmentation and new tables to optimize the

tests mechanism for Scopus' needs (see Section 2.2.6).

• GPIO – Allows the user to set GPIO dry-contact's activity (see Section

2.2.7).

• File – Manages the configuration and preset files of the device (see Section

2.2.8).

User Guidelines

MIB Implementation


2.2.1. Agent (scAgent)

The Scopus Agent MIB (scAgent) contains the various objects used to set basic

and general definitions of Scopus units. The IRD-2900 supports the following

objects:

• Date and Time (scAgentConfigDateAndTime) – see Section 2.2.1.1

• Restart (scAgentRestart) – see Section 2.2.1.2

OID Path: 1.3.6.1.4.1.4466.1.13.1.1

2.2.1.1. Date and Time (scAgentDateAndTime)

The Date and Time object sets the date and time information and serves as the

IRD-2900 internal clock counter

The IRD-2900 does not have an internal clock. Thus, when turning off the IRD,

there is no internal clock and date counter to keep track. This often cause

malfunctions for the traps and alarms.

To prevent this malfunction, the Scopus Agent MIB contains the Date and Time

object. When re-turning the IRD back on, the NMS sets the date and time

information from this MIB object.

OID Path: 1.3.6.1.4.1.4466.1.13.1.1.1

2.2.1.2. Restart (scAgentRestart)

The Restart object restarts the IRD. This object corresponds with the Front

Panel ‘Soft Reset’ command.

OID Path: 1.3.6.1.4.1.4466.1.13.1.1.7

IRD-2900 MIB



2.2.2. Alarms (scAlarms)

The Scopus Common Alarms MIB is comprised of two tables and three general

configuration objects. The objects in the branch are:

• Alarm General Configuration Parameters – Set general definitions that

apply to all alarms at once (see Section 2.2.2.1).

• Current Alarms Table (scAlarmsCurrentTable) – Displays the current

status information of all active alarms (see Section 2.2.2.2).

• Alarm Configuration Table (scAlarmsConfTable) – Sets the definition of

each supported alarm (see Section 2.2.2.3).

OID Path: 1.3.6.1.4.1.4466.1.13.1.4

2.2.2.1. Alarm General Configuration Parameters

The Alarms MIB support three general alarm configuration objects as follows:

• Alarms Enabled (scAlarmsEnabled) – Allows the user to enter a bit-mask to

enable or disable specific alarms of the unit. For more information see the

MIB file.

OID Path: 1.3.6.1.4.1.4466.1.13.1.4.10

• Automatic Reset (scAlarmsAutomaticReset) – Currently not available, will

be supported in future software releases.

OID Path: 1.3.6.1.4.1.4466.1.13.1.4.11

• Re-send Active (scAlarmsReSendActive) – Alerts all active alarms. This

command is used through the NMS, and when set to ‘True' it immediately

sends traps regarding all currently active alarms.

OID Path: 1.3.6.1.4.1.4466.1.13.1.4.12

User Guidelines

MIB Implementation


2.2.2.2. Current Alarms Table (scAlarmsCurrentTable)

The Current Alarms table displays the currently active alarms' status and other

information.

When an alarm is raised, a related entry is created in the Current Alarms table

and a scAlarmOn trap is sent. Once the alarm is cleared, the related entry is

removed from the Current Alarms table and a scAlarmOff trap is sent (for

information about the scAlarmOn and scAlarmOff traps, see Section 2.2.2.3).

OID Path: 1.3.6.1.4.1.4466.1.13.1.4.1

Figure 2-14 shows an example of the Current Alarms table.

Figure 2-14: Current Alarms Table (scAlarmsCurrentTable)

The alarms table instance is comprised of three indexes: a physical entity index

number (entPhysicalIndex), an interface index number (scAlarmIfIndexOrZero),

and an alarm type index number (scAlarmCurrentAlarmType). For example, the

highlighted row in Figure 2-14 displays the index of the following objects:

• SPN-27 Card (physical entity index number 1124073472, this entity name

can be found in the physical entity table, Figure 2-6).

• MPEG Transport Layer (interface index number 1178599680, displayed

in the scAlarmIfIndexOrZero column. The index number is drawn from the

ifTable. Specific interface details and information can be reviewed through

the ifTable according to the presented ifIndex)

• MPEG-2 synchronization loss alarms (index number 2, the alarm type

name is displayed in the scAlarmCurrentAlarmType column).

The various indexes of the alarm table allow the table to display several alarms

for the same element, or the same alarm occurring in several different elements.

IRD-2900 MIB



The table displays the following information:

• scAlarmIfIndexOrZero – Serves as one of the table indexes. This column

displays the index number of the interface affected by the alarm cause.

NOTE

If the alarm is not related to a port, such as hardwareFailure(3) alarm, this

column value is 0.

• scAlarmCurrentAlarmType – Serves as one of the table indexes. This

column displays the type of the alarm. Scopus IRD current version for Alarm

MIB supports the following alarms:

• mpeg2SyncLoss (2) – Rise on input TS synchronization loss.

• hardwareFailure (3) – Rise on general hardware failure.

• mpeg2InvalidPsi (5) – Rise if the transport stream lacks the PAT table.

• testTsBufferOverflow (6) – Rise if the TS test counter reaches a

threshold for transport stream overflow error. Test name: BufferError

(3030)

• testTsIndicator (7) – Rise if TS test counter reaches a threshold for a

transport stream indicator error. Test name: TransportError (2010)

• testContinuityCounter (8) – Rise if TS test reaches a threshold for

transport stream continuity error. Test name: ContinuityCountError

(1040)

• testCRC (9) – Rise if TS test counter reaches a threshold for a CRC

error. Test name: CRCError (2020)

• testPcrDiscontinuity (10) – Rise if TS test counter reaches a threshold

for PCR discontinuity error Test name: PcrDiscontinuityError (2032)

User Guidelines

MIB Implementation


• testDecoderBufferOverflow (11) – Rise if Scopus test counter

reaches a threshold for decoder overflow error. Test name:

decoderBufferOverflow (1)

• testDecoderBufferUnderflow (12) – Rise if Scopus test counter

reaches a threshold for decoder underflow error. Test name:

DecoderBufferUnderflow (2)

• testDecoderStreamError (13) – Rise if Scopus test counter reaches a

threshold for decoder stream error. Test name: DecoderStreamErrors (3)

• filteringCbrBitrateTooLow (32) – Rise if the configured CBR bit-rate is

lower than the actual bit-rate of the transmitted PIDs.

• satelliteBERTooHigh (40) – Rise if the satellite BER (Bit Error Rate)

exceeds the configured threshold. The BER threshold is configured from

the satellitePreferencesTable (see Section 1.2.4)

• satelliteEbN0TooLow (41) - Rise if the satellite Eb/N0 exceeds the

configured threshold. The Eb/N0 threshold is configured from the

scIrdRcvSatellitePreferenceTable (see Section 1.2.4).

• scAlarmCurrentTimeStamp – Displays the exact time of the alarm

occurrence.

NOTE

The alarm timestamp value is set according to the IRD. Yet, as the IRD does not

have an inner clock, this value may be incorrect. To keep the alarm timestamp

accurate, make sure that the Date and Time object (see Section 2.2.1.1) is set

accurately.

• scAlarmEntPhysicalIndex – Serves as one of the table indexes. Draws

information from the Physical Entity table (entPhysicalTable). This object

contains the index numbers of the physical component affected by the

displayed alarm's cause.

IRD-2900 MIB



2.2.2.3. Alarm Configuration Table (scAlarmsConfTable)

Alarm configuration allows the user to set the severity level of each alarm

available for the IRD-2900. The table also displays description information

regarding the alarm, useful for the traps log (see Section 2.2.3).

OID Path: 1.3.6.1.4.1.4466.1.13.1.4.2

Figure 2-15 shows an example of the Alarm Configuration table.

Figure 2-15: Alarm Configuration Table (scAlarmsConfTable)

The alarm table index is the scAlarmsConfALarmType object, drawn from the

table itself. The instance value (a number between 2-13) represents the type of

the entry alarm.

The table displays the following information:

• scAlarmsConfAlarmType – Serves as the table index. This column displays

the type of the alarm presented in the row.

• scAlarmConfSeverity – Allows the user to set the alarm severity level. The

available values are:

• critical (1)

• major (2)

• minor (3)

• info (4)

• scAlarmConfDescription – A character string detailing a verbal description

of the alarm type. This information is sent with the trap, as to entitle the

raised/canceled alarm with a more convenient name.

User Guidelines

MIB Implementation


2.2.3. Traps (scTraps)

Traps are sent by the device without manager intervention whenever a trap

event occurs (for example, a raised alarm). In order for the traps to reach the

destination host management station, the Traps Destination table

(scTrapsDestTable) must be configured (see Figure 2-16).

NOTE

Starting from SW v1.70, traps destination hosts can be configured from the

Web-Based Management and from the CLI (for information about these control

interfaces refer to the IRD-2900 User Manual).

OID Path: 1.3.6.1.4.1.4466.1.13.1.5.1

Figure 2-16: Traps Destination Table (scTrapsDestTable)

The table has two index sources:

• Destination IP Address (scTrapDestIpAddress) – Drawn from this table, it

is the IP address of the host

• Destination UDP Port (scTrapDestUdpPort) – Drawn from this table, it is

the UDP port number of the host.

The information displayed in the traps destination table is:

• scTrapDestIpAddress – Sets the IP address of the trap destination.

• scTrapDestUdpPort – Sets the port number of the trap destination.

• scTrapDestDescription – Optional object. Displays a string describing the

trap destination.

• scTrapDestCommunityString – Optional object. Displays a string

describing the community of the trap. This serves as a very preliminary sort

of security. This is mainly used by the NMS to identify the device that has

sent the trap.

IRD-2900 MIB



• scTrapDestRowStatus – Allows the user to create and delete table entries.

The supported actions are:

• active – Row status is active.

• createAndGo – Allows the operator to create a new row. The new row

status is Active.

• destroy – Allows the operator to delete a row from the table.

• scTrapDestEnableTraps – Sets the IP address of a trap for enabling or

disabling it.

2.2.3.1. Notifications

Notifications are MIB objects representing trap-events. The Scopus-Common

Notifications, as well as other standard notifications (such as snmpV2) are a

group of pre-defined trap-events. Scopus-IRD-MIB currently supports some

standard and Scopus-Common trap notifications.

The Scopus-IRD MIB supports the following trap notifications:

From the Standard MIB:

• Warm Start – for details see section 2.1.5.

From the Scopus-Common MIB:

• scGoingToReboot – Sends a trap before the device restarts itself.

• scAlarmOn – Sends a trap at an alarm registration

• scAlarmOff – Sends a trap at an alarm cancellation

• scSettingsChanged – Sends a trap 10 second after the most recent set-up

change. If there are several changes with differences of less than 10

seconds from one another, the trap is sent after the last change performed.

• scModuleInserted – Sends a trap at CAM insertion.

• scModuleRemoved – Sends a trap at CAM removal.

User Guidelines

MIB Implementation


When a trap event occurs the trap log screen is displayed, showing the

information of the trap (see Figure 2-17).

Figure 2-17: Traps Log

IRD-2900 MIB



The trap displays a notification about the alarm: the sending device, timestamp,

agent and manager addresses, community type, and binding.

Bindings are a list of informative objects referring to the trap. The first two

bindings are standard SNMPv2 objects:

• sysUpTime – How long does the system exist and is active.

• snmpTrapOID – Displays the type of the trap.

In addition to the standard SNMPv2 objects, the traps also send objects

configured by Scopus. These objects are:

• scAlarmCurrentTimestamp – Sends the timestamp of the trap event's

occurence.

• scAlarmEntPhysicalIndex – Sends the index number of the physical entity

affected by the alarm.

• scAlarmIfIndexOrZero – Sends the index number of the interface affected

by the alarm. If the alarm did not affect the interfaces, for example in the

case of a hardware alarm, this binding sends a 0 value.

• scAlarmConfAlarmType – Sends the alarm type.

• scAlarmConfSeverity – Sends the alarm severity level.

• scAlarmConfDescription – Sends the alarm description – a string of

characters describing the alarm name.

User Guidelines

MIB Implementation


2.2.4. IP (scIp)

The Scopus IP branch holds the Scopus IP table (scIpTable). The Scopus IP

table contains all the Ethernet objects for all Scopus products. All IRD-2900

Ethernet Management Port information is set through this table.

OID Path: 1.3.6.1.4.1.4466.1.13.1.9.1

Figure 2-18 shows an example of the Scopus IP table.

Figure 2-18: Scopus IP Table (scIpTable)

The table index is the ifIndex of the Ethernet ports.

The table presents the following objects:

• IP Address (scIpAddress) – Sets the Ethernet port's IP Address

• Subnet Mask (scIpSubnetMask) – Sets the Ethernet port's subnet mask

address

• Default Gateway (scIpDefaultGateway) – Sets the Ethernet port's default

gateway address.

NOTE

The Scopus IP branch also holds the Static Route's table (scIpStaticRouteTable).

This table is for the use of other Scopus devices and is not supported by the

IRD-2900.

IRD-2900 MIB



2.2.5. Stream (scStream)

The Scopus Stream MIB contains information related to the transport streams

and the received services.

The Scopus Stream MIB contains three active MIB groups relevant for IRD

service-management functions:

• MPEG-2 PSI (scMpeg2Psi) – Manages MPEG-2 tables such as PAT, PMT, and

so on (see Section 2.2.5.1)

• DVB SI (scDvbSi) – Manages DVB standard tables, such as SDT, BIT, and

so on (see Section 2.2.5.2)

• Descriptors (scStreamDescriptors) – Manages stream descriptors of all

standards (see Section 2.2.5.3).

OID Path: 1.3.6.1.4.1.4466.1.13.1.100

2.2.5.1. MPEG-2 PSI (scMpeg2Psi)

MPEG-2 PSI MIB contains PSI tables: PAT, PMT, CAT, and TDST.

MPEG-2 PSI MIB OID path is 1.3.6.1.4.1.4466.1.13.1.100.1

Programs and services are detailed through tables. There are various types of

tables, but Scopus refers to the MPEG-2 standard tables as first and basic

source. This is why the IRD, MIB, and NMS refer to the information in the MPEG

tables as the existing information and DVB tables’ information as additional, and

not vise-versa. Selecting a primary source is necessary because there are

occasional differences between the information in the MPEG and DVB tables, and

one standard must be set as primary source.

User Guidelines

MIB Implementation


The PAT (Program Association Table) MIB contains the program information.

This MIB contains the program number and the setting of the program number

when set to 0 (scMpeg2PsiPatProgramPmtOrNetP).

The PMT (Program Mapping Table) contains the program number and

information about the output-decoding ports in the program.

When a service is transmitted through the IRD, the PMT of each PAT, meaning

the elementary streams in each program, are identified and routed into a service

channel. Thus the elementary streams are identified as output-decoding ports

related to that specific service channel.

Figure 2-19 illustrates the transmission and conversion in the program of the

PMT into an output-decoding port in a service. For more information about

mapping-port-to-service see Section 3.4.4.2.

Program 1

Program 2

Program 3

PAT PMT Video Audio Audio

Video VBI

Audio Data

Service

Channel 1

Channel 2

Video-1 Audio-1 Audio-2

Video-2 VBI-2

Audio-3 Data-2

Figure 2-19: PMT to Channel Process

IRD-2900 MIB



2.2.5.2. DVB SI (scDvbSi)

The DVB SI MIB displays information related to the DVB tables.

DVB-SI MIB OID path is 1.3.6.1.4.1.4466.1.13.1.100.2

The DVB SI MIB tables are:

• NIT – Network Information Table

• BAT – Bouquets Association Table

• SDT – Service Definition Table

• EIT – Event Information Table

• TOT – Time Offset Table

• TDT – Time Description Table

• SIT – Service Information Table

All tables contain the following information:

• Network ID

• Version

• Section numbers

• Descriptors

• TS ID

• TS original network

• TS descriptors

In addition, each table contains its own table-specific objects.

User Guidelines

MIB Implementation


2.2.5.3. Descriptors (scStreamDescriptors)

The Stream Descriptors table display information for various descriptors from

both DVB and MPEG-2 tables. The IRD-2900 user can use the Descriptors tables

for service configuration purposes (see Section 3.4.3).

The table in use for service configuration is the Stream Service table

(scStreamServiceTable). The table gives index information and service name

description for the selected service. The important objects in the table are

scStreamServiceInstance and scStreamServiceProviderName.

OID Paths:

• ScStreamDescriptors – 1.3.6.1.4.1.4466.1.13.1.100.10

• ScStreamServiceTable – 1.3.6.1.4.1.4466.1.13.1.100.10.72

• ScStreamServiceInstance – 1.3.6.1.4.1.4466.1.13.1.100.10.72.1.6

• ScStreamServiceProviderName – 1.3.6.1.4.1.4466.1.13.1.100.10.72.1.9

The available descriptor tables are:

• scStreamVideoTable

• scStreamAudioTable

• scStreamHeirarchyTable

• scStreamRegistrationTable

• scStreamDataStreamAlignTable

• scStreamTargetBackgrGridTable

• scStreamVideoWindowTable

• scStreamCaTable

• scStreamIso639LanguageTable

• scStreamSystemClockTable

• scStreamProvateDataIndicatorTable

• scStreamNetworkNameTable

• scStreamServiceListTable

• scStreamSatelliteDeliverySysTable

• scStreamCableDeliverySysTable

• scStreamVbiDataTable

• scStreamVbiTeletextTable

• scStreamServiceTable

• scStreamCaIdTable

• scStreamTeletextTable

• scStreamLocalTimeOffsetTable

• scStreamSubtitlingTable

• scStreamTerrDeliverySysTable

• scStreamProvateDataSpecifierTable

• scStreamFrequencyListTable

• scStreamDataBroadcastTable

• scStreamDataBroadcastIdTable

• scStreamAc3Table

• scStreamGenericTable

IRD-2900 MIB



2.2.6. Scopus Tests (scTests)

Scopus Tests MIB serves as an augmentation for the tsTests MIB in the DVB

standard MIB. Scopus Tests MIB is composed of three tests tables and three

general configuration object for controlling the tests. The objects in the Scopus

Tests MIB are as follows:

• Reset All Counters – See Section 2.2.6.1

• Automatic Counters Reset Enabled – See Section 2.2.6.1

• Set All Intervals – See Section 2.2.6.1

• Tests Table – Se Section 2.2.6.2

• Tests Summary Table – See Section 2.2.6.3

• PID Table – See Section 2.2.6.4

OID Path: 1.3.6.1.4.1.4466.1.13.1.11

Figure 2-20: Scopus Tests Tree (scTests)

The following sections detail the Scopus Tests MIB objects.

User Guidelines

MIB Implementation


2.2.6.1. General Parameter

The Scopus Tests General Parameters allow the user to set all counters in the

Tests tables (both tsTests and scTests tables). The general parameters group

holds the following objects:

• Reset All Counters (scTestsResetAllCounters) –Allows the user to

immediately reset all error counters.

OID Path: 1.3.6.1.4.1.4466.1.13.1.11.1

• Automatic Counters Reset Enabled (scTestsAutomaticCountersReset

Enabled) – Sets the reset control mode of all counters. The reset can be

performed by either the user, using a given time interval, or by the NMS

application.

When this object is set to on, the counters are reset according to a user-

defined time interval (see Section 2.2.6.3).

When this object is set to off, the counter reset is within the responsibility of

the NMS application.

OID Path: 1.3.6.1.4.1.4466.1.13.1.11.2

• Set All Intervals (scTestsSetAllIntervals) – Allows the user to set all

counter intervals to a unanimous value.

OID Path: 1.3.6.1.4.1.4466.1.13.1.11.3

IRD-2900 MIB



2.2.6.2. Tests Table (scTestsTable)

The Scopus Tests table displays counter information and objects regarding the

hardware of the Scopus device.

The Scopus Tests table is based on the Transport Stream table from the DVB

standards, and together the two tables give all the counters information and

objects required to monitor all available errors in the device: the

tsTestsSummaryTable manages the stream errors, while the scTestsTable

manages all errors not related to stream, such as hardware errors.

The Scopus Tests table is already implemented with the augmentation objects

from the Scopus Tests Summary table – Threshold and Interval

(scTestsThreshold and scTestsInterval, for more information see Section

2.2.6.3).

OID Path: 1.3.6.1.4.1.4466.1.13.1.11.4

Figure 2-21 shows an example of the Scopus Tests table.

Figure 2-21: Scopus Tests Table (scTestsTable)

User Guidelines

MIB Implementation


The indexes of the table are the Scopus Tests Interface and the Scopus Test

Type values (scTestsIfIndex and scTestsType), both objects held within the

table. The instance of the table is comprised of both these indexes. For example,

in Figure 2-21, the highlighted row displays the index of the following objects:

• Video-1 Output-Decoding Port (interface-under-test index number

1178992896, displayed in the scTestsIfIndex column. The index number is

drawn from the ifTable)

• Test Type Number (index number 2, displayed and verbally described in

the scTestsType column)

The Tests table displays the following columns:

• scTestsIfIndex – Serves as one of the table indexes. Displays the name

and instance number of the output-decoding port under test. The

information in this column is drawn from the interface table (ifTable). The

interface name can be found in the ifTable.

• scTestsType – Serves as one of the table indexes. Displays the error type

of the counter both by number and name.

• scTestsSummaryState – Displays the current operation mode of the

counter. The available options are:

• disable – Counter is disabled

• pass – Counter does not reach threshold

• fail – Counter reaches threshold. Alarm is raised.

• scTestsSummaryEnable – Sets the counter operation modes – enable or

disable.

• scTestsCounter – Displays the error counter value – how many errors have

been detected since the last reset of the counter.

• scTestsCounterDiscontinuity – Displays the latest timestamp of the

raised error, and activity duration time.

• scTestsCounterReset – Allows the user to reset the counter immediately.

• scTestsLatestError – Displays the timestamp of the latest error

appearance (for a specific error counter).

• scTestsActiveTime – Displays the activity duration of the counter since the

device has been powered up.

• scTestsThreshold – Sets a maximum threshold value for the error counter.

If the counter reaches the set threshold, the relevant alarm is raised.

• scTestsInterval – Sets a reset interval when reset is user-defined. The

interval sets the period of time until the counter is reset to 0. For an alarm

to rise, the counter must reach the threshold within the given interval period

of time.

IRD-2900 MIB



2.2.6.3. Tests Summary Table (scTestsSummaryTable)

The Scopus Tests Summary table is an augmentation for the Transport Stream

Tests Summary table. The table adds the Threshold and Interval objects

(scTestsSummaryThreshold and scTestsSummaryInterval) to the table counters.

The Threshold object sets a threshold maximum value for the error counter.

When the counter reaches the given threshold, the relevant alarm is raised.

The Interval object sets a numeric seconds value for reset period. The error

counter resets back to 0 after the given period of time.

The error counter must reach the threshold within the interval period of time for

the alarm to rise. This mechanism prevents unnecessary or irrelevant raised

alarms incidents.

OID Path: 1.3.6.1.4.1.4466.1.13.1.11.5

Figure 2-22 shows an example of the Scopus Tests Summary table (top) with

the Transport Stream Tests Summary table (bottom).

Figure 2-22: Scopus Tests Summary (scTestsSummaryTable) and Transport Stream Tests Summary (tsTestsSummaryTable) Tables Display

User Guidelines

MIB Implementation


The table does not have any indexes. It is an augment of the Transport Stream

Tests table (tsTestsSummaryTable) and as such uses the tsTestsSummaryTable

instances. Figure 2-22 shows the scTestsSummaryTable (top table) and the

tsTestsSummaryTable (bottom table). Notice that the instances in both tables

are identical, displaying the interface index number and the counter type

instance number.

The table displays the following columns:

• scTestsSummaryThreshold – Sets a maximum threshold value for the

error counter. If the counter reaches the set threshold, the relevant alarm is

raised.

• scTestsSummaryInterval – Sets a reset interval when reset is

user-defined. The interval sets the period of time until the counter is reset to

0. For an alarm to rise, the counter must reach the threshold within the

interval given period of time.

2.2.6.4. PID Table (scTestsPidTable)

The Scopus PID table is an augmentation to the Transport Stream PID table

(tsTestsPIDTable). The Scopus PID table contains the Threshold and Interval

values for the TS PID table (for more information about these objects see

Section 2.2.6.3).

Scopus error counters and alarms do not support PID errors and alarms in the

current software version. Due to that, both TS PID table and Scopus PID table

are empty of information and are not available.

IRD-2900 MIB



2.2.7. Scopus GPIO (scGpio)

Scopus GPIO contains the Scopus GPIO Output Configuration table

(scGpioOutputConfTable).

The GPIO table allows the user to set the GPIO dry contact to a specific alarm

type, thus insuring that the dry contact is activated when the alarm is raised.

The GPIO can be configured with an interval (scGpioOutputConfFilterInterval).

The interval, a measured period of time in seconds, sets a minimum period of

time for the alarm to last before the GPIO is launched. This filter prevents the

GPIO to be launched for alarms that are solved quickly.

OID Path: 1.3.6.1.4.1.4466.1.13.1.12.1

Figure 2-23 shows an example of the Scopus GPIO table.

Figure 2-23: Scopus GPIO Table (scGpioOutputConfTable)

User Guidelines

MIB Implementation


The indexes of the table are the entPhysicalIndex and the GPIO Dry Contact

number (scGpioOutputConfDryContact). The instance of the table is comprised

of both these indexes. For example, in the first row of the table in Figure 2-23,

the indexes are the following:

• GPIO Physical Entity (entity index number 1124073472, drawn in the

entPhysicalTable, see Figure 2-6).

• GPIO Output Port Number (index number 1, drawn from this table, the

scGpioOutputConfSDryContact object).

The table displays the following columns:

• scGpioOutputConfDryContact – Serves as one of the table indexes.

Displays the GPIO output port number.

• scGpioOutputConfAlarms – Enables or disables the GPIO for specific

alarms.

• scGpioOutputConfFilterInterval – Sets an interval of time in seconds.

This period of time is a minimum time-limit for the alarm to last, before the

GPIO is launched.

• scGpioOutputConfNormallyOpen – Normally Open is a read-only object.

It displays the dry-contact’s status – True for normally open and False for

normally close.

NOTE

The IRD-2900 GPIO status is usually Normally Open ('True').

• scGpioOutputConfIsActive – Displays the current activation mode of the

GPIO dry contact – True for close and activated, False for open and inactive.

This object changes to True when a raised alarm starts up the dry-contact

mechanism.

IRD-2900 MIB



2.2.8. File (scFile)

The Scopus File branch (scFile) manages up to 10 setup configuration files of the

unit.

The File MIB OID: 1.3.6.1.4.1.4466.1.13.1.8.

This branch holds the following objects:

• Next Free Index (scFileOperatorNextFreeIndex) – Suggests the next free

index number for a new entry in the File Operation table

(scFileOperationTable). The suggestions begin from 1 and onward (2, 3, and

so on) where the suggested number is the first free value (meaning an index

number not in use in the Operations table).

• File Operation Table (scFileOperationTable) – Manages the configuration

files (see Section 2.2.8.1).

• Files Table () – Displays a list of the available configuration files according

to their configured file names (see Section 2.2.8.2).

2.2.8.1. File Operation Table

(scFileOperationTable)

The table manages the configuration files. The table allows the user to execute a

variety of file commands, such as export current configuration to a file, import

or load an existing set-up, and so on (see Figure 2-24).

NOTE

Note that each entry in the table is an action, not a file's list. This means that for

every new entry one must set a new index number, and destroying entries in

the table does not remove the configuration files from the database.

Figure 2-24: File Operation Table (scFileOperationTable)

User Guidelines

MIB Implementation


The table index is scFileOperationIndex.

The table presents the following objects:

• Index (scFileOperationIndex) – Displays the entry's index number. The

SNMP suggests the next available index number in the Next Free Index

object (scFileOperatorNextFreeIndex).

• File Name (scFileOperationFileName) – Sets the file name. The object also

allows selecting a file by its name (for actions such as load or remove).

• Type (scFileOperationType) – Sets the file operation type. The supported

operations are:

• importConfigurationFromFile (2) – Load existing configuration file

• exportServiceConfigToFile (9) – Save current configuration

• removeFile(10) – Delete existing configuration file.

• Status (scFileOperationStatus) – Displays the operation's current status.

The available options are:

• notStarted (1) – An action was selected. The action did not start yet.

• inProgress (2) – Action in progress

• finished (3) – Action completed successfully

• failed (4) – Action failed

• Error Code (scFileOperationErrorCode) – Displays the error code in case of

a failed operation status (scFileOperationStatus shows 'failed (4)'). Refer to

the MIB file for a full error code list.

• Error Description (scFileOperationErrorDescription) – Displays a verbal

description of the operation failure cause. If the operation succeeded, this

column is empty.

NOTE

Although all objects are writable when creating new entries, these objects

become read-only once the entry is created successfully. The only action

available for an existing entry is "destroy" from the Row Status object (scFile

OperationRowStatus).

IRD-2900 MIB



• Row Status (scFileOperationRowStatus) – Allows the user to create new or

delete entries in the table.

The IRD-2900 supports the following Row Status options:

• active (1) – The operation row status is active. This is a read-only status

and cannot be configured by the user.

• createAndGo (4) – A new operation row is created. When the file is

ready, it will automatically be set as 'active (1)'.

• destroy (6) – The selected operation row from the File Operation table

(scFileOperationTable) configuration file is deleted.

When executing a new operation, perform the following:

1. Create a new entry in the table, by prompting for an instance.

2. Enter a new row instance. Scopus recommends using the scFileOperation

NextFreeIndex value. To verify the instance structure, check the Entry

object properties information (scFileOperationEntry).

3. Set the configuration objects in the Entry setting window.

The following objects are mandatory information for creating a new entry:

• Operation Index Number (scFileOperationIndex) – Cannot be changed

after creation

• Row Status (scFileOperationRowStatus) – The row status' value must be

set to 'createAndGo' (4).

• File Name (scFileOperationFileName) – Sets a new file name when using

"export" command; selects the requested file when using "import" or

"remove" command. Cannot be changed after creation.

• Operation Type (scFileOperationType) – Selects the requested

command. Cannot be changed after creation.

User Guidelines

MIB Implementation


2.2.8.2. Files Table (scFilesTable)

The table allows viewing the configuration files. (see Figure 2-25).

Figure 2-25: Files Table (scFilesTable)

The table index is scFileName.

The table presents the following object:

• File Name (scFileName) – Displays all stored configurations' File name.

IRD-2900 MIB



2.3. IRD-2900 MIB The IRD-2900 MIB contains information and object settings relevant only to the

IRD-2900. Figure 2-26 illustrates the IRD-2900 MIB main objects.

Figure 2-26: IRD-2900 MIB Tree

User Guidelines

MIB Implementation


2.3.1. Receiver Objects (scIrdReceiver)

The Receiver MIB set the receiver information for satellite and IP receivers. This

MIB is also used for getting updated receiver definitions information. The

Receiver MIB consists of the following branches:

• Satellite Receiver branch see Section 2.3.1.1

• IP Receiver branch see section 2.3.1.2

2.3.1.1. Satellite Receiver (scIrdRcvSatellite)

The Satellite Receiver contains all configuration and status objects for satellite

settings and QPSK-transmission receiving. The branch consists of the following

tables:

• Satellite Configuration table – Configures the satellite objects.

• Satellite Status table – Monitors the satellite's status.

• Satellite Preferences Table – Sets the satellite preferences (augment to

satellitePrefernceTable).

The Satellite Receiver branch OID is 1.3.6.1.4.1.4466.1.2.10.1.1.1

IRD-2900 MIB



SATELLITE CONFIGURATION TABLE

(SCIRDRCVSATELLITECONFIGTABLE)

This table allows the user to set configuration objects of the satellite receiver,

such as LND definitions, frequency ranges, and so on. The index source of the

Satellite Configuration Table is entPhysicalIndex.

The Satellite Configuration table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.1.1. The

IRD must be equipped with a QPSK card to display this table.

Figure 2-27 shows an example of the Satellite Configuration table objects.

Figure 2-27: Satellite Configuration Table Parameters (scIrdRcvSatelliteConfigTable)

User Guidelines

MIB Implementation


The available objects are:

• scIrdRcvSatelliteConfigLnbLOType – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.1

• scIrdRcvSatelliteConfigLnbLOFreq – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.2

• scIrdRcvSatelliteConfigFreqRange – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.3

• scIrdRcvSatelliteConfigFrequency – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.4

• scIrdRcvSatelliteConfigSymbolRate – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.5

• scIrdRcvSatelliteConfigLnbPolarity – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.6

• scIrdRcvSatelliteConfigLnbBand – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.7

• scIrdRcvSatelliteConfigLnbToneMode – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.8

• scIrdRcvSatelliteConfigViterbiRate – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.9

• scIrdRcvSatelliteConfigSpecInv – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.10

• scIrdRcvSatelliteConfigDiSEqCType – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.11

• scIrdRcvSatelliteConfigDriftComp – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.12

• scIrdRcvSatelliteConfigModulation – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.13

• scIrdRcvSatelliteConfigRollOff – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.14

• scIrdRcvSatelliteConfigActivePort – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.15

• scIrdRcvSatelliteConfigPilots – 1.3.6.1.4.1.4466.1.2.10.1.1.1.1.1.16

NOTE

Several objects in the QPSK tables are valid for unit with DVB-S2 support. The

object are:

• scIrdRcvSatelliteConfigModulation

• scIrdRcvSatelliteConfigRollOff

• scIrdRcvSatelliteConfigPilots

IRD-2900 MIB



SATELLITE STATUS TABLE

(SCIRDRCVSATELLITESTATUSTABLE)

This table allows the user to view actual status information of the satellite

receiver. The index source of the Satellite Status table is entPhysicalIndex.

The Satellite Status table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.1.2. The IRD

must be equipped with a QPSK card to display this table.

Figure 2-28 shows an example of the Satellite Status table objects.

Figure 2-28: Satellite Status Table Parameters (scIrdRcvSatelliteStatusTable)


• scIrdRcvSatelliteStatusSpecInv – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.1

• scIrdRcvSatelliteStatusViterbiRate – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.2

• scIrdRcvSatelliteStatusEbN0 – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.3

• scIrdRcvSatelliteStatusLinkMargin – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.4

• scIrdRcvSatelliteStatusViterbiBer – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.5

• scIrdRcvSatelliteStatusSignalQualit – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.6

• scIrdRcvSatelliteStatusFrequencyTun – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.7

• scIrdRcvSatelliteStatusFrequencyOff – 1.3.6.1.4.1.4466.1.2.10.1.1.1.2.1.8

User Guidelines

MIB Implementation


SATELLITE PREFERENCES TABLE

(SCIRDRCVSATELLITEPREFERENCESTABLE)

This table allows the user to view real-time status information of the satellite

preferences. This table is an Augment of the Satellite Preferences table

(satellitePreferencesEntry).

The Satellite Status table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.1.3.1. The IRD

must be equipped with a QPSK card to display this table.

Figure 2-29 shows an example of the Satellite Preference table objects.

Figure 2-29: Satellite Preferences Table (scIrdRcvSatellitePreferencesTable)


• scIrdRcvSatellitePrefEbN0Min – 1.3.6.1.4.1.4466.1.2.10.1.1.1.3.1.1

IRD-2900 MIB



2.3.1.2. IP Receiver (scIrdRcvIp)

The IP Receiver branch sets objects and gets information of received IP

transmission and IP receiver ports. The branch consists of the following tables:

• IP Configuration table

• IP Port table

• IP Status table

The IP Receiver branch OID is 1.3.6.1.4.1.4466.1.2.10.1.1.4

IP CONFIGURATION TABLE

(SCIRDRCVIPCONFIGTABLE)

This table manages the IP receiver general configuration setting, such as delay,

active IP port, de-jitter, and so on. The index source of the IP Configuration

table is entPhysicalIndex.

The IP Configuration table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.4.1. The IRD

must be equipped with an MPEG-over-IP card to display this table.

Figure 2-30 shows an example of the IP Configuration table objects.

Figure 2-30: IP Configuration Table Parameters (scIrdRcvIpConfigTable)


• scIrdRcvIpConfigFec – 1.3.6.1.4.1.4466.1.2.10.1.1.4.1.1.1

• scIrdRcvIpConfigFailoverDelay – 1.3.6.1.4.1.4466.1.2.10.1.1.4.1.1.2

• scIrdRcvIpConfigActivePortIfIndex – 1.3.6.1.4.1.4466.1.2.10.1.1.4.1.1.3

• scIrdRcvIpConfigFaliover – 1.3.6.1.4.1.4466.1.2.10.1.1.4.1.1.4

• scIrdRcvIpConfigDJDelay – 1.3.6.1.4.1.4466.1.2.10.1.1.4.1.1.5

User Guidelines

MIB Implementation


IP PORT CONFIGURATION TABLE

(SCIRDRCVIPCONFIGPORTTABLE)

This table manages the IP receiver port configuration settings, such as

addresses, ports, links, and so on. The index source of the IP Port Configuration

table is ifIndex.

The IP Port Configuration table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.4.2. The

IRD must be equipped with an MPEG-over-IP card to display this table.

Figure 2-31 shows an example of the IP Port Configuration table objects.

Figure 2-31: IP Port Configuration Table Parameters (scIrdRcvIpConfigPortTable)


• scIrdRcvIpConfigMulticastAddress – 1.3.6.1.4.1.4466.1.2.10.1.1.4.2.1.1

• scIrdRcvIpConfigLocalPort – 1.3.6.1.4.1.4466.1.2.10.1.1.4.2.1.2

• scIrdRcvIpConfigLinkEnable – 1.3.6.1.4.1.4466.1.2.10.1.1.4.2.1.3

• scIrdRcvIpConfigFecColumnPort – 1.3.6.1.4.1.4466.1.2.10.1.1.4.2.1.4

• scIrdRcvIpConfigMulticast – 1.3.6.1.4.1.4466.1.2.10.1.1.4.2.1.5

IRD-2900 MIB



IP STATUS TABLE (SCIRDRCVIPSTATUSTABLE)

This table allows the user to view the status of the IP receiver ports and

transmission. The index source of the IP Status table is entPhysicalIndex.

The IP Port Configuration table OID is 1.3.6.1.4.1.4466.1.2.10.1.1.4.3. The

IRD must be equipped with an MPEG-over-IP card to display this table.

Figure 2-32 shows an example of the IP Status table objects.

Figure 2-32: IP Status Table Parameters (scIrdRcvIpStatusTable)


• scIrdRcvIpStatusConfiguration – 1.3.6.1.4.1.4466.1.2.10.1.1.4.3.1.1

• scIrdRcvIpStatusProtocol – 1.3.6.1.4.1.4466.1.2.10.1.1.4.3.1.2

• scIrdRcvIpStatusMpegPacketSize – 1.3.6.1.4.1.4466.1.2.10.1.1.4.3.1.3

• scIrdRcvIpStatusRxBitrate – 1.3.6.1.4.1.4466.1.2.10.1.1.4.3.1.4

User Guidelines

MIB Implementation


2.3.2. Stream Objects (scIrdStream)

The Stream MIB sets and gets information and object definitions of the transport

stream. This MIB define the transport stream identity and format.

Another branch to the IRD Stream is the filtering branch, allowing the user to

set stream-filtering definitions for better use of bandwidth.

The Stream MIB consists of the following branches:

• Control Group see Section 2.3.2.1

• Status Group see Section 2.3.2.2

• Error tables – The tables in this branch are obsolete and cannot be

displayed.

• Filtering see Section 2.3.2.4

IRD-2900 MIB



2.3.2.1. Control Group (scIrdStreamControlGroup)

This branch holds a group of parameter managing the identity and format of the

transport stream. They also set the behavior of output ports towards the TS. The

Control Group OID is 1.3.6.1.4.1.4466.1.2.10.1.2.1

Figure 2-33 shows an example of the Control Parameters group.

Figure 2-33: Control Parameters group (scIrdStreamControlGroup)


• scIrdStreamInputRate – 1.3.6.1.4.1.4466.1.2.10.1.2.1.1

• ScIrdStreamAsiOutputType – 1.3.6.1.4.1.4466.1.2.10.1.2.1.2

• scIrdStreamSync27MhzMode – 1.3.6.1.4.1.4466.1.2.10.1.2.1.3

• ScIrdStreamVcxoFixedValue – 1.3.6.1.4.1.4466.1.2.10.1.2.1.4

• ScIrdStreamInputSource – 1.3.6.1.4.1.4466.1.2.10.1.2.1.5

• ScIrdStreamType – 1.3.6.1.4.1.4466.1.2.10.1.2.1.6

• ScIrdStreamAsiMode – 1.3.6.1.4.1.4466.1.2.10.1.2.1.7

• ScIrdStreamIpOutputType – 1.3.6.1.4.1.4466.1.2.10.1.2.1.8

User Guidelines

MIB Implementation


2.3.2.2. Status Group (scIrdStreamStatusGroup)

The Status Group’s only object is the Information table

(scIrdStreamInfoTable). The index source of the Information table is ifIndex.

The Status Group Information table OID is 1.3.6.1.4.1.4466.1.2.10.1.2.2

Figure 2-34 shows an example of the Stream Information table (under the

Status Group object) objects.

Figure 2-34: Information Table Parameter (scIrdStreamInfoTable)

The available object is:

• scIrdStreamInfoRate – 1.3.6.1.4.1.4466.1.2.10.1.2.2.1.1.1

2.3.2.3. Errors (scIrdStreamErrors)

The Errors Objects consist of the Quality Errors table and the Decoder Errors

table. These tables' status is obsolete and they cannot be displayed. Alternate

error mechanism is available through the Alarms, Traps, and Tests (for more

details see Section 3.1).

IRD-2900 MIB



2.3.2.4. Stream Filtering (scIrdStreamFiltering)

The Stream Filtering branch sets the stream filtering configuration, either for

general stream filters or specific service or PID filters. The object consists of the

following groups and tables:

• Filtering Group

• Filtering Service table

• PID Filtering table

The Stream Filtering branch OID is 1.3.6.1.4.1.4466.1.2.10.1.2.4

FILTERING GROUP (SCIRDSTREAMFILTERINGGROUP)

This group sets the general definitions of the filtering mode and strategy. The

Filtering Group OID is 1.3.6.1.4.1.4466.1.2.10.1.2.4.1.

Figure 2-35 shows an example of the Filtering Group objects.

Figure 2-35: Filtering Group Parameters (scIrdStreamFilteringGroup)


• scIrdStreamFilteringMode – 1.3.6.1.4.1.4466.1.2.10.1.2.4.1.1

• scIrdStreamFilteringStrategy – 1.3.6.1.4.1.4466.1.2.10.12.4.1.2

• scIrdStreamFilteringBitRateMode – 1.3.6.1.4.1.4466.1.2.10.12.4.1.3

• scIrdStreamFilteringBitRate – 1.3.6.1.4.1.4466.1.2.10.12.4.1.4

• scIrdStreamFilteringClearServices – 1.3.6.1.4.1.4466.1.2.10.12.4.1.5

• scIrdStreamFilteringClearPids – 1.3.6.1.4.1.4466.1.2.10.12.4.1.6

User Guidelines

MIB Implementation


FILTERING SERVICE TABLE

(SCIRDSTREAMFILTERINGSERVICETABLE)

This table selects the services-to-filter by the stream-filtering. The index source

of the Filtering Service table is the scIrdStreamFilteringServiceId.

The Filtering Service table OID is 1.3.6.1.4.1.4466.1.2.10.1.2.4.2.

Figure 2-36 shows an example of the Filtering Service table objects.

Figure 2-36: Filtering Service Table Parameters (scIrdStreamFilteringServiceTable)


• scIrdStreamFilteringServcieId – 1.3.6.1.4.1.4466.1.2.10.1.2.4.2.1.1

• scIrdStreamFilteringServcieStatus – 1.3.6.1.4.1.4466.1.2.10.12.4.2.1.2

FILTERING PID TABLE

(SCIRDSTREAMFILTERINGPIDTABLE)

This table selects the PIDs-to-filter by the stream filtering. The index source of

the Filtering PID table is the scIrdStreamFilteringPid.

The Filtering PID table OID is 1.3.6.1.4.1.4466.1.2.10.1.2.4.3.

Figure 2-37 shows an example of the Filtering PID table objects.

Figure 2-37: Filtering PID Table Parameters (scIrdStreamFilteringPidTable)


• scIrdStreamFilteringPid – 1.3.6.1.4.1.4466.1.2.10.1.2.4.3.1.1

• scIrdStreamFilteringPidStatus – 1.3.6.1.4.1.4466.1.2.10.12.4.3.1.2

IRD-2900 MIB



2.3.3. Service Objects (scIrdService)

The Service MIB set and get information for the Service Channel and Service

Port definitions.

This MIB also contains the Service Strategy objects group, managing the

IRD-2900 unit behavior toward the stream.

The Service branch consists of the following groups:

• Strategy objects see Section 2.3.3.1

• Service Configuration see Section 2.3.3.2

2.3.3.1. Strategy (scIrdServiceStrategy)

The Strategy object OID is 1.3.6.1.4.1.4466.1.2.10.1.3.1

Figure 2-38 shows an example of the Strategy Object objects.

Figure 2-38: Strategy Parameters (scIrdServiceStrategy)


• scIrdServiceStrategyProgramAbsent – 1.3.6.1.4.1.4466.1.2.10.1.3.1.1

• scIrdServiceStrategyCas – 1.3.6.1.4.1.4466.1.2.10.1.3.1.2

User Guidelines

MIB Implementation


2.3.3.2. Service Configuration

(scIrdServiceConfig)

The Service Configuration branch contains all Service configuration objects, such

as service port control and channel definitions. This branch consists of the

following tables:

• Service Port table

• Service Channel table

The Service Configuration branch OID is 1.3.6.1.4.1.4466.1.2.10.1.3.2

SERVICE PORT TABLE

(SCIRDSERVICECONFIGPORTTABLE)

This table manages the transmitted service port definitions, such as service port

PID, related service channel, language, and so on. The index source of the

Service Port table is ifIndex.

The Service Port table OID is 1.3.6.1.4.1.4466.1.2.10.1.3.2.1

Figure 2-39 shows an example of the Service Port table objects.

Figure 2-39: Service Port Table Parameters (scIrdServiceConfigPortTable)


• scIrdServiceConfigPortPid – 1.3.6.1.4.1.4466.1.2.10.1.3.2.1.1.1

• scIrdServiceConfigPortChannel – 1.3.6.1.4.1.4466.1.2.10.1.3.2.1.1.2

• scIrdServiceConfigPortPcrIfIndex – 1.3.6.1.4.1.4466.1.2.10.1.3.2.1.1.3

• scIrdServiceConfigPortPrefLanguage – 1.3.6.1.4.1.4466.1.2.10.1.3.2.1.1.4

• scIrdServiceConfigPortPage – 1.3.6.1.4.1.4466.1.2.10.1.3.2.1.1.5

IRD-2900 MIB



CHANNEL TABLE

(SCIRDSERVICECONFIGCHANNELTABLE)

The index source of the Channel table is scIrdServiceConfigChannelNumber from

this table.

The Channel table OID is 1.3.6.1.4.1.4466.1.2.10.1.3.2.2

Figure 2-40 shows an example of the Channel table objects.

Figure 2-40: Channel Table (scIrdServiceConfigChannelTable)


• scIrdServiceConfigChannelNumber – 1.3.6.1.4.1.4466.1.2.10.1.3.2.2.1.1

• scIrdServiceConfigChannelServiceId – 1.3.6.1.4.1.4466.1.2.10.1.3.2.2.1.2

NOTE

Since the scIrdServiceConfigChannelNumber object serves as the table index

source, its column in this image displays Not Available. For the actual value

refer to the Instance column.

User Guidelines

MIB Implementation


2.3.4. Video Objects (scIrdVideo)

The Video MIB manage the setting and getting of the Video, VBI, and OSD

objects in the IRD-2900. The Video MIB consists of the following groups and

tables:

• Video Configuration branch see Section 2.3.4.1

• Video Status table see Section 2.3.4.2

2.3.4.1. Video Configuration (scIrdVideoConfig)

The Video Configuration branch contains all video, VBI, and OSD configuration

objects. The object consists of the following tables:

• Video Configuration table

• VBI Configuration table

• OSD Configuration table

• OSD Text Insertion Configuration table

The Video Configuration branch OID is 1.3.6.1.4.1.4466.1.2.10.1.4.1

IRD-2900 MIB



VIDEO TABLE (SCIRDVIDEOCONFIGTABLE)

This table manages the configuration settings of all the available video channels

in the unit, such as: format, interpolation, aspect ratio, and so on. The index

source of the Video table is ifIndex.

The Video table OID is 1.3.6.1.4.1.4466.1.2.10.1.4.1.1

Figure 2-41 shows an example of the Video Configuration table objects.

Figure 2-41: Video Configuration Table Parameters (scIrdVideoConfigTable)


• scIrdVideoConfigFormat – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.1

• scIrdVideoConfigInterpolation – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.2

• scIrdVideoConfigAspectRatio – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.3

• scIrdVideoConfigScreenBlank – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.4

• scIrdVideoConfigLipSyncMode – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.5

• scIrdVideoConfigLipSyncDelay – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.6

• scIrdVideoConfigPcrStcDelay – 1.3.6.1.4.1.4466.1.2.10.1.4.1.1.1.7

User Guidelines

MIB Implementation


VBI TABLE (SCIRDVBICONFIGTABLE)

This table manages all VBI configurations. The table is displays all supported VBI

types (such as CC, WSS, and so on) per each VBI channel. Other objects in the

table allow the user to set the VBI lines for the specific VBI type of the row. The

indexes for the VBI table are:

• ifIndex

• scIrdVbiType (from this table)

The VBI table OID is 1.3.6.1.4.1.4466.1.2.10.1.4.1.2

Figure 2-42 shows an example of the VBI table objects.

Figure 2-42: VBI Configuration Table Parameters (scIrdVbiConfigTable)


• scIrdVbiType – 1.3.6.1.4.1.4466.1.2.10.1.4.1.2.1.1

• scIrdVbiSource – 1.3.6.1.4.1.4466.1.2.10.1.4.1.2.1.2

• scIrdVbiLine1 – 1.3.6.1.4.1.4466.1.2.10.1.4.1.2.1.3

• scIrdVbiLine2 – 1.3.6.1.4.1.4466.1.2.10.1.4.1.2.1.4

IRD-2900 MIB



OSD TABLE (SCIRDOSDCONFIGTABLE)

This table allows the user to set OSD (On-Screen Display) definitions. The OSD

sets the Teletext or other subtitling definitions, such as position, subtitle type,

and so on. The index source of the OSD table is ifIndex.

The OSD table OID is 1.3.6.1.4.1.4466.1.2.10.1.4.1.3

Figure 2-43 shows an example of the OSD Configuration table objects.

Figure 2-43: OSD Configuration Table Parameters (scIrdOsdConfigTable)


• scIrdOsdMonitorOutput – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.1

• scIrdOsdBroadcastOutput – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.2

• scIrdOsdXPositionOffset – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.3

• scIrdOsdYPositionOffset – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.4

• scIrdOsdDvbSubtitleMode – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.5

• scIrdOsdTltxSubtitleMode – 1.3.6.1.4.1.4466.1.2.10.1.4.1.3.1.6

User Guidelines

MIB Implementation


OSD TEXT INSERTION TABLE

(SCIRDOSDTEXTINSERTIONCONFIGTABLE)

This table allows the user to set the visual definitions of the OSD – the text,

color, position, and so on. The index source of the OSD Text Insertion table is

ifIndex.

The Text Insertion table OID is 1.3.6.1.4.1.4466.1.2.10.1.4.1.4

Figure 2-43 shows an example of the Text Insertion table objects.

Figure 2-44: OSD Text Insertion Table Parameters (scIrdOsdTextInsertionConfigTable)


• scIrdOsdTextInsertionString – 1.3.6.1.4.1.4466.1.2.10.1.4.1.4.1.1

• scIrdOsdTextInsertionColor – 1.3.6.1.4.1.4466.1.2.10.1.4.1.4.1.2

• scIrdOsdTextInsertionXPosition – 1.3.6.1.4.1.4466.1.2.10.1.4.1.4.1.3

• scIrdOsdTextInsertionYPosition – 1.3.6.1.4.1.4466.1.2.10.1.4.1.4.1.4

• scIrdOsdTextInsertionEnable – 1.3.6.1.4.1.4466.1.2.10.1.4.1.4.1.5

IRD-2900 MIB



2.3.4.2. Video Status Table (scIrdVideoStatus)

The Video Status branch contains the Video MPEG Header table

(scIrdVideoMpegHeaderTable). This table monitors the video channels outputs

and actual setup values, such as: aspect ratio, rate code, buffer size, and so on.

The index source of the MPEG Header table is ifTable.

The Video Status MPEG Header table OID is 1.3.6.1.4.1.4466.1.2.10.1.4.2.1

Figure 2-45 shows an example of the Video Status table objects.

Figure 2-45: Video MPEG Header Table Parameters (scIrdVideoMpegHeaderTable)


• scIrdVideoMpegHorizontalSizeValue – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.1

• scIrdVideoMpegVerticalSizeValue – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.2

• scIrdVideoMpegAspectRatioInfo – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.3

• scIrdVideoMpegFrameRateCode – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.4

• scIrdVideoMpegBitRateValue – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.5

• scIrdVideoMpegVbvBufferSizeValue – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.6

• scIrdVideoMpegChromaFormat – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.

• scIrdVideoMpegStandardFormat – 1.3.6.1.4.1.4466.1.2.10.1.4.2.1.1.8

User Guidelines

MIB Implementation


2.3.5. Audio Objects (scIrdAudio)

The Audio MIB manage the setting and getting of Audio Channel objects in the

IRD-2900. The Audio MIB consists of the following tables and branches:

• Audio Configuration table see Section 2.3.5.1

• Audio Status branch see Section 2.3.5.2

2.3.5.1. Audio Configuration Table

(scIrdAudioConfigTable)

This table allows the user to set all audio channel definitions. This includes

general definitions as well as objects specifically designated to certain decoding

mode (for details see Section 3.6). The index source of the Audio table is

ifTable.

The Audio table OID is 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1

The corresponding operational sequence is Root��Configuration��Audio��

Audio #.

Figure 2-46 shows an example of the Audio table objects.

Figure 2-46: Audio Configuration Table Parameters (scIrdAudioConfigTable)

IRD-2900 MIB




• scIrdAudioAttenuation – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.1

• scIrdAudioDecodeMode – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.2

• scIrdAudioAnalogMode – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.3

• scIrdAudioAc3DownmixMode – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.4

• scIrdAudioAc3OperationalMode – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.5

• ScIrdAudioAc3PassThruSampleRate – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.6

• ScIrdAudioMute – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.7

• ScIrdAudioAVSync – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.8

• ScIrdAudioDigitalFormat – 1.3.6.1.4.1.4466.1.2.10.1.5.1.1.1.9

2.3.5.2. Audio Status (scIrdAudioStatus)

The Status branch contains all audio status data, dividing it between the

different decoder modes. The status object contains the following tables:

• MPEG Header table

• Linear Header table

• AC-3 Header table.

The Status Object OID is 1.3.6.1.4.1.4466.1.2.10.1.5.2

MPEG HEADER TABLE

(SCIRDAUDIOMPEGHEADERTABLE)

This table display status information regarding audio channels of Musicam

decoding mode. The index source of the MPEG Header table is ifIndex.

The MPEG Header table OID is 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1

The IRD audio decoding mode must be set to Musicam to display this table.


• scIrdAudioMpegId – 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1.1

• scIrdAudioMpegLayer – 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1.2

• scIrdAudioMpegBitRate – 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1.3

• scIrdAudioMpegSampleRate – 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1.4

• scIrdAudioMpegMode – 1.3.6.1.4.1.4466.1.2.10.1.5.2.1.1.5

User Guidelines

MIB Implementation


LINEAR HEADER TABLE

(SCIRDAUDIOLINEARHEADERTABLE)

This table display status information regarding audio channels of Linear PCM

decoding mode. The index source of the Linear Header table is ifTable.

The Linear Header table OID is 1.3.6.1.4.1.4466.1.2.10.1.5.2.2.1

The IRD audio decoding mode must be set to Linear-PCM to display this table.


• scIrdAudioLinearSampleRate – 1.3.6.1.4.1.4466.1.2.10.1.5.2.2.1.1

• scIrdAudioLinearBitsPerSample – 1.3.6.1.4.1.4466.1.2.10.1.5.2.2.1.2

• scIrdAudioLinearChannelId – 1.3.6.1.4.1.4466.1.2.10.1.5.2.2.1.3

• scIrdAudioLinearOutputMode – 1.3.6.1.4.1.4466.1.2.10.1.5.2.2.1.4

AC-3 HEADER TABLE (SCIRDAUDIOAC3HEADERTABLE)

This table display status information regarding audio channels of Dolby-AC3

digital decoding mode. The index source of the AC-3 Header table is ifTable.

The AC-3 Header table OID is 1.3.6.1.4.1.4466.1.2.10.1.5.2.3.1

The IRD audio decoding mode must be set to Dolby AC-3 to display this table.


• scIrdAudioAc3SampleRate – 1.3.6.1.4.1.4466.1.2.10.1.5.2.3.1.1

• scIrdAudioAc3BsMode – 1.3.6.1.4.1.4466.1.2.10.1.5.2.3.1.2

• scIrdAudioAc3BitRate – 1.3.6.1.4.1.4466.1.2.10.1.5.2.3.1.3

• scIrdAudioAc3AcMode – 1.3.6.1.4.1.4466.1.2.10.1.5.2.3.1.4

IRD-2900 MIB



2.3.6. Data Objects (scIrdData)

The Data MIB contain all high-speed data and IP-data object definitions. The

Data MIB consists of the follwoing tables:

• High-Speed Data table

• IP table

• Low-Speed Data table

2.3.6.1. HSD Table (scIrdHsdConfigTable)

This table manages the high-speed data configuration. The index source of the

HSD table is ifTable.

The HSD table OID is 1.3.6.1.4.1.4466.1.2.10.1.6.1.1

Figure 2-47 shows an example of the HSD table objects.

Figure 2-47: HSD Configuration Table Parameters (scIrdHsdConfigTable)


• scIrdHsdClockValue – 1.3.6.1.4.1.4466.1.2.10.1.6.1.1.1.1.

• scIrdHsdLayer – 1.3.6.1.4.1.4466.1.2.10.1.6.1.1.1.2.

• scIrdHsdBitOrder – 1.3.6.1.4.1.4466.1.2.10.1.6.1.1.1.3.

User Guidelines

MIB Implementation


2.3.6.2. IP Table (scIrdIpDataConfigTable)

This table sets the IP output interface definitions, such as: destination IP

address and port, source port, protocol, and so on. The index source of the IP-

Data table is ifTable.

The IP-Data table OID is 1.3.6.1.4.1.4466.1.2.10.1.6.1.2

Figure 2-48 shows an example of the IP Data table objects.

Figure 2-48: IP Data Table Parameters (scIrdIpDataConfigTable)


• scIrdIpDataDestinationIpAddress – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.1

• scIrdIpDataDestinationPort – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.2

• scIrdIpDataSourcePort – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.3

• scIrdIpDataNumberSendPackets – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.4

• scIrdIpDataProtocol – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.5

• scIrdIpDataMode – 1.3.6.1.4.1.4466.1.2.10.1.6.1.2.1.6

IRD-2900 MIB



2.3.6.3. LSD Table (scIrdLsdConfigTable)

This table manages the low-speed data definitions and settings. The index

source of the Low-Speed Data table is ifTable.

The Low-Speed Data table OID is 1.3.6.1.4.1.4466.1.2.10.1.6.1.3.

Figure 2-49 shows an example of the Low-Speed Data table objects.

Figure 2-49: Low-Speed Data Table Parameters (scIrdLsdConfigTable)


• scIrdLsdConfigBaudRate – 1.3.6.1.4.1.4466.1.2.10.1.6.1.3.1.1

• scIrdLsdConfigTransportLayer – 1.3.6.1.4.1.4466.1.2.10.1.6.1.3.1.2

User Guidelines

MIB Implementation


2.3.7. CAS Objects (scCas)

The CAS MIB contains the BISS objects and tables, allowing the user to set the

BISS scrambling mode and definitions.

2.3.7.1. BISS Objects (scIrdBISS)

The BISS objects allow the user to set objects and definitions regarding the BISS

conditional access definitions. The BISS objects contain the following branches:

• General parameters (outside of tables)

• Session Words table

• Even-Odd table.

GENERAL PARAMETERS

The CAS General objects set the general definitions of the BISS conditional

access. The general parameters are the following two objects:

• scIrdBISSMode – 1.3.6.1.4.1.4466.1.2.10.1.7.1.1

• scIrdBISSInjectedId – 1.3.6.1.4.1.4466.1.2.10.1.7.1.2

NOTE

Injected ID is displayed and available in the front-panel only when Encryption

Mode is set to BISS-E-Injected ID.

IRD-2900 MIB



SESSION WORDS TABLE

(SCIRDBISSSESSIONWORDSTABLE)

This table allows the user to set a session word for scrambling. Seesion words

are used by most BISS scrambling modes. For more information about the BISS

scrambling, see Section 3.8. This table The index source of the Session Words

table is scIrdServiceConfigChannelNumber from the Service Channel table (see

Section 2.3.3.2).

The Session Words table OID is 1.3.6.1.4.1.4466.1.2.10.1.7.1.3


• scIrdBISSSssionWord – 1.3.6.1.4.1.4466.1.2.10.1.7.1.3.1.1

NOTE

Session Word object is not available in the front-panel for Even-Odd Encryption

Mode.

EVEN-ODD TABLE (SCIRDBISSEVENODDTABLE)

This table sets the even-odd encryption keys, for odd-and-even srambling. The

index source of the Even-Odd table is scIrdServiceConfigChannelNumber from

the Service Channel table (see Section 2.3.3.2).

The Even-Odd table OID is 1.3.6.1.4.1.4466.1.2.10.1.7.1.4


• scIrdBISSEvenKey – 1.3.6.1.4.1.4466.1.2.10.1.7.1.4.1.1

• scIrdBISSOddKey – 1.3.6.1.4.1.4466.1.2.10.1.7.1.4.1.2

NOTE

Even-Odd objects are available in the front-panel for Even-Odd Encryption Mode

only.

IRD-2900 MIB



Chapter 3. CONFIGURATION PROCEDURE WITH

MIB This chapter details the configuration processes for IRD-2900 functionalities and

the influence of IRD objects on one another. The chapter also details the

configuration and state mechanism of the error tests.

The chapter is divided into nine sections:

• Error Tests Configuration – details the relations between the Counters,

Alarms, and Traps, creating together a complete test mechanism for the

IRD-2900 to inform the user of errors and alarms raised in the device (see

Section 3.1).

• Receiver – Details the Satellite and IP receiver object groups and the

influence of objects on one another in the group (see Section 3.2).

• Stream – Details the stream definition object groups and the influence of

objects on one another in the group (see Section 3.3).

• Service – Details the Service object groups and influence of objects on one

another in the group (see Section 3.4).

As the Service setting requires the user to search for information in various

sources such as the Scopus-Common MIB, these processes are details

separately in Sections 3.4.2 to 3.4.4.

• Video - Details the Video, VBI, and OSD definition object groups and the

influence of objects on one another in the group (see Section 3.5)

• Audio - Details the Audio definition object groups each audio decoding

mode and the influence of objects on one another in the group (see Section

3.6)

• Data - This section details the HSD, IP data, and LSD definition object

groups and the influence of objects on one another in the group (see Section

3.7).

• CAS – Allows the user to set conditional access for BISS scrambling modes

and definitions (see Section 3.8).

User Guidelines

Configuration Procedure with MIB


3.1. ERROR TESTS CONFIGURATION-

COUNTERS, ALARMS, AND TRAPS The IRD-2900, using the NMS and the MIB, manages a network of counters,

traps, and alarms, to detect every problem within stream, port, or hardware in

the decoder. This network is used by the user to monitor the status of the

IRD-2900 and be well alerted whenever an issue or problem comes up.

The network is comprised of three main mechanisms: Counters, Traps, and

Alarms. The following sections detail the main MIB tables and uses of each of

these mechanisms.

3.1.1. Error Counters

The error counters count appearances of error within a given amount of time.

Using the DVB Standards TS Tests tables and the Scopus augmentation and

other Tests tables, the error counters give the detailed information about the

requested error, and set a threshold for the counter for alarm raising purposes.

3.1.1.1. Transport Stream Tests (tsTests)

The TS Tests from the MIB DVB Standards are tests and counters for transport

stream errors. The TS Tests contain two tables – for transport stream errors

(tsTestsSummaryTable) and PID errors (tsTestsPIDTable).

The TS tests display detailed information regarding the counter, such as:

• Interface port instance number

• Error type

• Counter state and operation mode

• Counter current value

• Various timestamp values: last error occurrence and duration, counter

activity duration since reset, counter activity duration since device power-

up.

• Immediate reset option

This error information, however, does not allow the user to be informed when an

error occurs frequently enough to raise an alarm. Augments and additions were

created by Scopus, and inserted as the Scopus Tests.

IRD-2900 MIB



3.1.1.2. Scopus Tests (scTests)

The Scopus Tests are mainly augments and additions to the DVB Standard TS

Tests. The Scopus Tests are comprised of three main tables: Scopus Tests

(scTestsTable), Scopus Tests Summary (scTestsSummaryTable) and Scopus PID

Tests (scTestsPidTable).

Scopus Tests Summary and Scopus PID Tests are augmentations for the existing

TS Tests and PID Tests from the DVB Standard MIB. These tables contain the

Threshold and Interval objects.

• The Interval sets a period of time (in seconds) for the counter reset. The

counter must reset in a reasonable frequency for the error counter to detect

a frequent error and raise an alarm.

General objects in the Scopus Tests object can also set an interval for all

counters at once, or immediately reset all counters.

• The Threshold sets a maximum limit for the counter. If the counter reaches

the threshold value within the given interval time, the error is detected as

frequent and the relevant alarm is raised.

Scopus Tests is another table much like the TS Tests table, already implemented

with the Threshold and the Interval objects. The Scopus Tests table contains all

error counters that are not stream-related and are not defined in the DVB

Standards error counters.

3.1.1.3. Satellite Preferences Tests

The Satellite Preference tests are not counters, like the transport-stream tests.

These tables and objects set a maximum rate measurements for specific satellite

features, to ensure that these objects do not exceed requested limits.

The Satellite Preference tests are comprised of two tables: the global-MIB table

Satellite Preferences table (satellitePreferenceTable), and its Scopus-IRD MIB

augment, the receiver Satellite Preferences table (scIrdRcvSatellitePreference

Table).

The Satellite Preference tables set maximum levels for the following features:

• BER (bit error rate) – Maximum rate is set from the satellitePreferences

Table.

• Eb/N0 – Maximum rate is set from the scIrdRcvSatellitePreferencesTable.

User Guidelines



3.1.2. Alarms

When an error counter detects a frequent error, meaning the counter has

reached the given threshold before being reset, an alarm is raised. The alarms

mechanism is managed through the Scopus-Common MIB scAlarms with two

tables, Current Alarms (scAlarmsCurrentTable) and Alarms Configuration

(scAlarmsConfTable). Alarms can also be masked

3.1.2.1. Alarm Masking (scAlarmsEnabled)

Alarms can be masked as enabled or disabled. When an alarm is masked as

enable, the user will be informed as the alarm is raised. When an alarm is

masked as disabled, the system ignores it and the user won't be informed.

To mask an alarm, perform the following:

1. Access the Set Screen of the scAlarmsEnabled parameter.

2. To enable the alarm set the value to '1', to disable the alarm set the value to

'0'.

3.1.2.2. Alarms Configuration Table

(scAlarmsConfTable)

Every alarm can be set with certain objects, such as severity level and

descriptor. This setup is performed through the Alarms Configuration table.

The table displays each of the supported alarms and allows the user to define a

severity level for the alarm in the scAlarmsConfSeverity column. Pre-defined by

Scopus is the scAlarmsConfDescription column, displaying an easily read name

for the alarm, for log and trap purposes.

IRD-2900 MIB



3.1.3. Traps

When an alarm is raised, the user must be informed. The unit sends a trap

whenever an alarm occurs. The trap in configured with a destination IP and Port

location.

NOTE

Starting from SW v1.70, traps can also be configured through the IRD-2900's

Web-Based Management and the CLI. For more information about these

interfaces please refer to the IRD-2900 User Manual.

3.1.3.1. Trap Destination Table (scTrapDestTable)

The Trap Destination Table sets the destination objects of the trap. This table

defines the trap destination IP address and UDP port. The table also allows the

user to set a description of trap-receiver and a community string, for security

purposes. Last is the trap row status object, allowing the user to set the trap’s

operation mode, delete it, or create a new one.

User Guidelines



3.1.3.2. Creating and Deleting Trap Destinations

The traps destination table is a Read-Create table, dynamic and manageable by

the user. This means that the user can add and remove rows into the table, and

not just view it and change parameters in the existing rows.

Using the Row Status parameter (scTrapDescRowStatus) the user can remove

and create new rows, or trap notification destination, in the table.

NOTE

Traps are sent to all registered hosts listed in the Trap Destination table.

DELETE A ROW

In order to delete an existing row, perform the following:

1. Access the Set Screen of the Row Status parameter. Make sure to access the

Row Status of the row to be deleted.

2. Set the value of the Row Status to 'destroy(6)'.

CREATE A NEW ROW

In order to create a new row, perform the following:

1. Access the Set screen of the Row Status parameter.

NOTE

In the MG-Soft MIB browser, when creating a new row and accessing the set

screen of the Row Status, it is recommended not to select a specific row for

editing, simply close the window by clicking the ’X’ icon on the top-right corner.

IRD-2900 MIB



2. Set the new IP address and port values. Insert the values separated by

periods. For example, to enter the IP address 10.2.2.100 and port 162 enter

10.2.2.100.162.

NOTE

• 162 is the standard port for trap destinations. Nevertheless, Scopus devices

support other traps when requested.

• In the MG-Soft MIB browser, the OID field in the Set window displays the

OID of the object, a destination IP address, and port values (separates with

periods). If a specific row was not selected, the index displays the OID

followed by a 0. to set the new IP address and port values, delete the

existing values (or 0) and enter the new setting (numbers separated by

periods).

3. Set the parameter value to 'createAndGo(4)' to create a new active row.

The new row appears in the Trap Destination table with its configured IP

address, port number, and row status ('active(1)').

4. Set the community and description parameters (optional).

User Guidelines



3.1.4. Tests State Machine

Figure 3-1 illustrates the Error Test mechanism process.

Figure 3-1: Test State Machine

IRD-2900 MIB



3.2. RECEIVER CONFIGURATION

3.2.1. Satellite Parameters

The Satellite Receiver tables are available only when a QPSK card is installed in

the IRD-2900. The satellite receiver is composed of several elements, detailed in

the following sections.

Figure 3-2 shows an example of the Physical Entity table. The QPSK Card

component is marked to show its instance number.


User Guidelines



The Satellite table tree (see Figure 3-3) illustrates all Satellite Configuration and

Status table objects.

Figure 3-3: Satellite Tables Tree

IRD-2900 MIB



3.2.1.1. Active Port

The Active Port object (scIrdRcvSatelliteConfigActivePort) sets the active

satellite port.

The IRD-2900 QPSK card can hold up to four stream ports. The IRD-2900 can

support only one transport stream at a time. Setting the active port object

selects the satellite stream port from which the transport stream is received.

For OID information, see Section 2.3.1.1

3.2.1.2. LNB L.O. Definitions

This group is divided into two sub-groups, Frequency and Configuration.

The Frequency group sets the local oscillator frequency by defining its range and

value. The Configuration group sets the definitions of the LNB (Low Noise

Blocker) Local Oscillator. Figure 3-4 illustrates the LNB L.O. Frequency objects

group. For OID information, see Section 2.3.1.1.

Frequency Definitions:

• Type (scIrdRcvSatellietConfigLnbLOType) - Sets the LNB range.

• Frequency (scIrdRcvSatelliteConfigLnbLOFreq) - Sets the LNB L.O. (Local

Oscillator) frequency, that controls the reduced rate set by the LNB. The LNB

Local Oscillator defines this object’s range.

Figure 3-4: LNB L.O. Frequency Parameters Group

User Guidelines



Figure 3-5 illustrates the LNB L.O. Configuration objects group. For OID

information, see Section 2.3.1.1.

Configuration Definitions:

• LNB Polarity (scIrdRcvSatelliteConfigLnbPolarity) - Sets the polarization of

the receiving antenna by providing different voltage levels to the LNB. The

LNB Polarity object is a read-write object. The available values are:

• vertical (0) - Provides 13V voltage level to the LNB

• horizontal (1) – Provides 18V voltage level to the LNB

• off (2) - No voltage is supplied to the LNB. Use this option either:

When cascading IRDs using the loop-through connector on the QPSK

interface

When this voltage is supplied to the LNB by an external source.

• LNB Band (scIrdRcvSatelliteConfigLnbBand) - Sets the mode of sending 22

KHz signals. The LNB sends 22 KHz signals when using high-band L.O. The


• low (0) – 22 KHz signal sending is off. LNB uses low-band L.O.

• high (1) – 22 KHz signal sending is on. LNB uses high-band L.O.

• LNB Tone Mode (scIrdRcvSatelliteConfigLnbToneMode) - Sets the LNB tone

mode of operation. The LNB Tone Mode object is a read-write object. The


• modulated (0)

• unmodulated (1)

Figure 3-5: LNB Information Tree Parameters Group

IRD-2900 MIB



3.2.1.3. Transponder Frequency

This group sets the satellite transponder frequency. Figure 3-6 illustrates the

Transponder Frequency objects group. For OID information, see Section 2.3.1.1.

Transponder frequency definitions:

• Frequency range (scIrdRcvSatelliteConfigFreqRange) – Sets frequency

range

• Satellite Frequency (scIrdRcvSatelliteConfigFrequency) – Sets the

frequency value

Figure 3-6: Satellite Frequency Parameters Group

User Guidelines



3.2.1.4. Satellite Rate

This group of objects gets the information required for setting and calculating

the Symbol Rate value. Figure 3-7 illustrates the Satellite Rate objects group.

For OID information, see Section 2.3.1.1.

Satellite rate definitions:

• Symbol Rate (scIrdRcvSatelliteConfigSymbolRate) – Sets the satellite

symbol rate. The symbol rate must be set according to the satellite

transponder symbol rate. The symbol rate value can be acquired from the

satellite transponder or calculated using the bit rate information.

• Stream Bit Rate (scIrdStreamInfoRate) – Gets the stream bit rate (in

Kbps)

• Modulation (scIrdRcvSatelliteConfigModulation) – Sets the modulation type

of the receiver, thus setting the amount of different tones received by the

IRD. For regular QPSK receiver mode, modulation is always set to modQPSK.

For DSNG receiver mode, modulation can be set to any available option.

Figure 3-7: Satellite Rate Parameters Group

IRD-2900 MIB



3.2.1.5. Viterbi Error Correction

This group sets the object definitions of the Viterbi Errors Correction (VEC).

Figure 3-8 illustrates the Viterbi objects group. For OID information, see Section

2.3.1.1.

Viterbi definitions:

• Viterbi Error Correction Rate (scIrdRcvSatelliteConfigViterbiRate) – Sets

the rate of correction of the Viterbi-Coding scheme

• Viterbi Actual Rate (scIrdRcvSatelliteStatusViterbiRate) – Gets the actual

rate of the Viterbi Error correction

• Viterbi BER Error Correction (scIrdRcvSatellitestatusViterbiBer) - Gets the

error bits that the Viterbi Error correction did not correct. Bits errors are

caused by interference or loss of signal that cause the stream of bits to

disrupt. BER is measured by over 107 symbols.

The satellitePreferenceTable sets a maximum rate for the BER to prevent

exceeding a requested rate. For more information see Section 2.1.4

Figure 3-8: Viterbi Error Correction Parameters Group

User Guidelines



3.2.1.6. Drift Compensation

This group sets the object definitions for Drift Compensation. Figure 3-9

illustrates the Drift Compensation objects group. For OID information, see

Section 2.3.1.1.

Drift compensation definitions:

• Drift Compensation (scIrdRcvSatelliteConfigDriftComp) – Sets the mode of

operation of Drift Compensation. According to the selected mode of

operation, this object affects the values of the Frequency Tune and

Frequency Offset status objects.

• Frequency Tune (scIrdRcvSatelliteStatusFrquencyTun) – A read-only

object, gets the frequency of the incoming signal. This value may change

automatically and continuously depending on the Drift Compensation mode

of operation.

• Frequency Offset (scIrdRcvSatelliteStatusFrequencyOff) – A read-only

object, gets the frequency-offset value as was set in the Frequency object.

However, if Drift Compensation is set to ‘On’, in which case, the frequency-

offset value is 0.

Figure 3-9: Drift Compensation Parameters Group

IRD-2900 MIB



3.2.1.7. Spectral Inversion

This group sets and gets the Spectral Inversion object definitions. Figure 3-10

illustrates the Spectral Inversion objects group. For OID information, see Section

2.3.1.1.

Spectral inversion definitions:

• Spectral Inversion (scIrdRcvSatelliteConfigSpecInv) – Sets the Spectral

Inversion value

• Spectral Inversion (scIrdRcvSatelliteStatusSpecInv) – Gets the actual

value of the spectral inversion

Figure 3-10: Spectral Inversion Parameters Group

3.2.1.8. DiSEqC Type

This object sets the type of the Digital Satellite Equipment control

(scIrdRcvSatelliteConfigDiSEqCType).


The available values are:

• none (0) – No DiSEqC is defined

• diseqc-1 (1) – DiSEqC type is set to diSEqC 1

• diseqc-2 (2) – DiSEqC type is set to diSEqC 2

User Guidelines



3.2.1.9. Signal Status

This group provides signal quality, strength, and signal-to-noise ratio

information in the digital communication system. Figure 3-11I illustrates the

Signal objects group. For OID information, see Section 2.3.1.1.

Signal status definitions:

• EbN0 (scIrdRcvSatelliteStatusEbN0) - Gets a basic measure of the signal

strength by measuring the signal-to-noise ratio in the digital communication

system.

The scIrdRcvSatellitePreferenceTable sets a maximum rate for the EbN0 to

prevent exceeding a requested rate. For more information see Section

2.3.1.1.

• Link Margin (scIrdRcvSatelliteStatusLinkMargin) – Gets an estimated C/N

of received signals

• Signal Quality (scIrdRcvSatelliteStatusSignalQuality) - Gets a quality

indication of the received C/N signal

IRD-2900 MIB



Figure 3-11: Satellite Signal Parameters Group

3.2.1.10. Pilot

The Pilot object (scIrdRcvSatelliteConfigPilot) defines the pilot mode of the

received data.

In order to expedite carrier recovery, the standard allows two operating modes

for each modulation type: Pilot-less mode (meaning, no Pilot symbols are

inserted) and Piloted, where Pilot symbols are inserted to aid carrier

synchronization.


The available values are:

• off (0) – Sets the pilot mode to Pilot-less

• on (1) – Sets the pilot mode to Piloted

User Guidelines



3.2.2. IP Parameters

The IP Front-End interface options are available only when an IP Card (MPEG-

over-IP card) is installed in the IRD-2900. The Physical Entity table shows the IP

Card (MPEG-over-IP card) Instance number. Figure 3-12 is an example of the

Physical Entity table marking the IP Card component.


IRD-2900 MIB



Figure 3-13 illustrates the IP Receiver tables’ tree.

Figure 3-13: IP Receiver Tables Tree

The MPEG-over-IP card consists of two input ports and a general Receiver

Parameters controller that processes the input transport stream and sends it to

the decoding module. The MIB sets the controller and input objects using the

following tables:

• The Receiver General Parameters Controller in the MPEG-over-IP card

objects are set through the IP Configuration table (scIrdRcvIpConfigTable,

see Section 3.2.2.1).

• The IP Input Port objects are divided into two groups:

• IP Receiver - Sets the relevant multicast and transport stream objects

through the Port Configuration table (scIrdRcvIpConfigPortTable, see

Section 3.2.2.2)

• IP Network – Sets the network definition objects in the IP Network

table (scIpTable, see Section 3.2.2.2)

NOTE

All IP objects in the IRD-2900 front-panel are located under IP Receiver

Configuration Menu (for more information refer to section 3.3.1.2 in the IRD-

2900 User Manual).

User Guidelines



3.2.2.1. IP Receiver Configuration Table

The IP Configuration table (scIrdRcvIpConfigTable) sets the Receiver General

Parameters Controller definitions. This table defines the transport stream format

and gets the status of the transport stream.

Figure 3-14: IP Receiver Configuration Table (scIrdRcvIpConfigTable)

3.2.2.2. IP Input Port Tables

The IP Receiver Port tables manage the port and network objects of the IP

transmission. The IP Receiver port definitions are divided into two sub-tables:

• IP Port Configuration (scIrdRcvIpConfigPortTable) - Sets the relevant

multicast and transport stream objects.

Figure 3-15: IP Port Configuration Table (scIrdRcvIpConfigPortTable)

IRD-2900 MIB



• IP Network Configuration (scIpTable) – Sets network objects (IP Address,

Subnet Mask and so on)

Figure 3-16: IP Network Configuration Table (scIpTable)

NOTE

IP Network Configuration objects are set using the IP Configuration table

(scIpTable). This table is located in the Scopus-Common MIB (see Section

2.2.4).

The IP receiver objects are categorized into several groups, detailed in the

following sections.

The ifTable contains the index numbers of the IP Network table and the IP Port

table. The IP Network table contains network information of the IP Port, such as:

IP address, Subnet Mask, and Default Gateway. The IP Port table contains

information concerning source addresses and local ports. The information and

configuration of the two tables set the definitions of one of the two IP ports in

the IP Card.

The IP Card also contains general objects (found under the menu carrying this

title in the IRD front panel IP Menu). The general objects are set using the IP

Configuration. The index number of this table is the MPEG-over-IP card instance

number, extracted from the Physical Entity table.

The IP Card then compresses the information into a transport stream and sends

it for further decoding in the IRD.

User Guidelines



Figure 3-17 illustrates the IP Configuration and Port table object relations.

Figure 3-17: IP Configurations and Parameter Relations in IP Tables

IRD-2900 MIB



3.2.2.3. Failover Errors

This group sets the Failover error types and error delays of the Stream errors

and Port errors. Figure 3-18 illustrates the Failover Errors objects group. For OID


Failover errors definitions:

• Failover Delay (scIrdRcvIpConfigFailoverDelay) - Sets the failover delay

allowed in the IP transmission decoding

• Failover (scIrdRcvIpConfigFailover) – Sets the redundancy mode of

operation for case of failover. The object is a True/False object, where:

• TRUE – Enables the failover redundancy

• FALSE – Disables the failover redunadncy

Figure 3-18: Failover Errors

User Guidelines



3.2.2.4. Active Port

These objects set the Active Port instance number and serve as an index for the

Port Configuration table. Figure 3-19 illustrates the Active Port objects group.


Active port definitions:

• Active Port Interface Index (scIrdRcvIpConfigActivePortIfIndex) – Sets

and activates the primary port. Displays the instance number of the primary

port

• Port Table (scIrdRcvIpConfigPortTable) – Sets the instance number and

objects of the active port

NOTES

• The Active Port object manages the instance number of the primary port.

• The Active Port Interface Index is functionally equivalent to the

Operational Input object in the IP Receiver��General menu from the IRD

front-panel.

Figure 3-19: Active Port interface Index Parameters Group

IRD-2900 MIB



3.2.2.5. IP Definitions

The IP Definitions objects set the IP port definitions of the IRD-2900. Figure

3-20 illustrates IP Definitions objects group. For OID information, see Section

2.3.1.2.

IP definitions:

• Multicast (scIrdRcvIpConfigMulticast) – Determines the transport stream

source address type. The Multicast object is a True/False object, where:

• TRUE – Multicast is enabled. The IP address is set according to the

Multicast Address object (scIrdRcvIpConfigMulticastAddress)

• FALSE – Multicast is disabled. The transport stream is set as a unicast,

definition settings are managed through the Scopus-Common IP table

(scIpTable).

• Multicast Address (scIrdRcvIpConfigMulticastAddress) – Sets the multicast

address of the TS. This object is available only is Multicast object

(scIrdRcvIpConfigMulticast) is enabled (TRUE).

• IP Network Table (scIpTable) – The Scopus IP Network table sets the IP

definitions of the receiver when Multicast object (scIrdRcvIpConfigMulticast)

is disabled (FALSE).

• Local Port (scIrdRcvIpConfigLocalPort) - Sets the local UDP port number of

the incoming IP transmission

• Protocol (scIrdRcvIpStatusProtocol) – Displays the active protocol type. The

available protocol options are UDP or RTP.

User Guidelines



Figure 3-20: IP Definitions Parameters Group

IRD-2900 MIB



3.2.2.6. Forward Error Correction (FEC)

The FEC group allows the user to set the FEc mode of operation, as well as

define the FEC column port number. For OID information, see Section 2.3.1.2.

NOTE

The IRD-2900 IP front end FEC implementation complies with ProMPEG CoP3v2,

with the following limitations:

• Columns support only

• Maximum TS bit-rate: 20 Mbps

This is a matrix-based FEC that uses only the matrix columns for regeneration of

lost data.

FEC Definitions:

• FEC (scIrdRcvIpConfigFec) – Sets the forward error correction mode of

operation. FEC is a True/False object where:

• TRUE – enables the use of forward error correction

• FALSE – disables the use of forward error correction.

• FEC Column Port (scIrdRcvIpConfigFecColumnPort) – Sets the FEC column

UDP port. The possible values range from 0 to 65535.

NOTE

The default FEC Column port is set to N+2, where N is the value of the UDP

Destination port.

User Guidelines



3.2.2.7. Link Enable

The Link Enable object (scIrdRcvIpConfigLinkEnable) is used for setting the

operation mode of the selected MPEG-over-IP input. Link Enable is a True/False

object, where:

• TRUE – enables the MPEGoIP input

• FALSE – disables the MPEGoIP input


3.2.2.8. De-Jitter (DJ) Delay

The DJ-Delay object (scIrdRcvIpConfigDJDelay) sets the de-jitter delay of the

IRD-2900. The possible values range from 0 to 6500. For OID information, see

Section 2.3.1.2.

3.2.2.9. Configuration

The Configuration object (scIrdRcvIpStatusConfiguration) verifies the current

configuration setup match or mismatch to the unit hardware capabilities and

definitions. For OID information, see Section 2.3.1.2

IRD-2900 MIB



3.3. STREAM CONFIGURATION The Stream tables sets the transport stream object definitions and ASI port

definitions. This group also gets bit rate values and error counter updates of

stream and decoder functionalities as well as stream-quality errors. These menu

objects are categorized in several groups, as detailed in the following sections.

Figure 3-21 illustrates the Stream tree.

Figure 3-21: Stream Tree

NOTE

Errors branch is obsolete.

User Guidelines



3.3.1. Stream Ports

The Stream Ports group sets the ASI input and output port types. Figure 3-22

illustrates the ASI Port objects group. For OID information, see Section 2.3.2.

Stream port definitions:

• Input Rate (scIrdStreamInputRate) - Sets the transport stream minimum

or maximum bit rate available range. It also determines whether the

Common Interface (CI) is supported and can receive decrypted services. The

available options are:

• high-speed (0) – ASI input supports bit rates over 108 Mbps with PID

dropping.

• fast (1) – ASI input supports a bit rate of up to 108 Mbps. CI is not

supported in this mode.

• normal (2) – ASI input supports bit rates up to 72 Mbps. CI is

supported in this mode.

• ASI Output Type (scIrdStreamAsiOutputType) - Activates the port and

decryption operation. The available options are:

• decryption-on (0) – The transport stream passes through the Common

Interface, allowing cascading.

• decryption-off (1) – The transport stream passes through the ASI

output but not through the common interface. Cascading is unavailable.

• none (2) – The ASI output is disabled.

• filtering (3) – The transport stream that passes through the port is

filtered. Filtering definitions are set through the filtering branch

(scIrdStreamFiltering, see Section 3.3.5).

IRD-2900 MIB



• Input Source – Allows the user to set the IRD decoder input source. The


• Front-end (QPSK) (if applicable) – Selects the QPSK Receiver Front-

end Interface as the source for the input transport stream

• Front-end (IP) (if applicable) – Selects the IP Front-End Interface as

the source for the input transport stream

• ASI – Select the ASI digital input as the source for the input transport

stream

• Serial RS422 – Selects the RS-422 serial input as the source for the

input transport stream

• None - No input source is selected for the IRD-2900.

• IP Output Type – Determines the path of the internal transport stream. the

availbel options are:

• No Filtering– Transport stream passes through the IP output but is not

filtered.

• Filtering – Transport stream passes through the IP output and is

filtered.

• None – IP output is disabled. Transport stream does not pass through it.

Figure 3-22: Stream Ports Parameters Group

User Guidelines



3.3.2. Synchronization

The Synchronization group sets the mode of the 27MHz internal synchronization

clock. This object determines the source of the synchronization signal. Possible

sources of the synchronization signal are:

• PCR table

• Voltage Controlled Crystal Oscillator (VCXO)

• Genlock

Figure 3-23 illustrates the Synchronization objects group. For OID information,

see Section 2.3.2.

Synchronization definitions:

• Sync 27MHz Mode (scIrdStreamSync27MhzMode) - Sets the source and

information of internal clock synchronization. The available options are:

• pcr-sync (0) – Synchronization by the program clock recovered from

the PCR data

• fix-value-sync (1) – Running in ‘free mode’. Synchronization by a

signal from the VCXO (see scIrdStreamVcxoFixedValue)

• gen-lock-sync (2) – Synchronization by an external video signal (if

present)

• VCXO Fixed Value (scIrdStreamVcxoFixedValue) - Sets the VCXO fixed

value for Sync 27MHz Mode when in fix-value-sync mode

IRD-2900 MIB



Figure 3-23: Synchronization Parameters Group

User Guidelines



3.3.3. Stream Type

The stream Type object (scIrdStreamType) allows the user to set the stream

type, DVB or ATSC. For OID information, see Section 2.3.2.


• dvb (0) – Sets the stream type to DVB

• atsc (1) – Sets the stream type to ATSC

3.3.4. ASI Mode

The stream ASI Mode object (scIrdStreamAsiMode) allows the user to set the

ASI ports working mode. For OID information, see Section 2.3.2.


• burst (0)

• normal (1)

3.3.5. Filters

The stream filtering branch (scIrdStreamFiltering) allows the user to filter the

output decoded stream from unnecessary information. For OID information see

section 2.3.2.

The output decoded stream is composed of the decoded service as well as a

considerable amount of segments (null). These segments take a large part of

the band width and bit-rate, yet are not required for the stream and are

considered as useless items.

The filters allow the user to select the decoding filtering mode in a way that

narrows the numbers of segments in the stream, thus clearing the bandwidth

from useless information.

Fro example, on a 40Mb bandwidth stream, the decoded service can use

approximately 4Mb. The rest of the bandwidth – 36Mb – are null information,

segments. The stream filters can cut down all the segments, leaving the stream

clear with the 4Mb use of the decoded service only.

IRD-2900 MIB



The stream filtering branch is divided into three group and tables:

• Filtering Group (scIrdStreamFilteringGroup) – Holds a variety of general

objects, setting the basic definitions of the stream filter.

• Filtering Service Table (scIrdStreamFilteringServiceTable) – When filtering

according to a specific service, this table selects the service-to-filter.

• Filtering PID Table (scIrdStreamFiletringPidTable) – When according to

PIDs, this table selects the PIDs-to-filter.

Figure 3-24: Stream Filtering Tree Structure

User Guidelines



Stream Filtering definitions:

• Mode (scIrdStreamFilteringMode) – Sets the transmission mode of the

services, in reference to the selects services. The available options are:

• transmit (0) – The decoder transmits the selected services only.

• filter (1) – The decoder transmits all services but the selected ones.

• Strategy (scIrdStreamFilteringStrategy) – Sets the stream-filtering strategy

of operation. This strategy affects the transmitted services, selected

according to the transmission mode. The available options are:

• decoded-only (0) – The transmitted stream is not filtered and decoded

as usual.

• services (1) – The transmitted stream is filtered according to services.

The services can be selected through the Filtering Service table (scIrd

StreamFilteringServiceTable).

• pids (2) – The transmitted stream is filtered according to PIDs. The PIDs

can be selected through the Filtering PIDs table (scIrdStreamFiltering

PidTable).

• Bit-Rate Mode (scIrdStreamFilteringBitRateMode) – Selects the

transmission bit-rate mode. The available options are vbr (0) or cbr (1).

When filtering the stream in VBR (Variable Bit-Rate) mode, the stream must

be configured with a maximum available bit-rate sum (through the

scIrdStreamFilteringBitRate object). Thus, when filtering the stream from

segments, the total bit-rate can vary up to the maximum selected bit-rate in

the bit-rate object.

When filtering the stream in CBR (Constant Bit-Rate) mode, the stream

bit-rate use is constant. If the set bit-rate is higher than the total sum of the

filters-stream bit-rate, some of the segments will remain in the stream to fill

the bit-rate up to the constant set value.

• Bit-Rate (scIrdStreamFilteringBitRate) – Sets the maximum available

stream bit-rate. The value ranges from 500,000 to 72,000,000 bps.

• Clear Services (scIrdStreamFilteringClearServices) – Clears all selects

services from the services table.

• Clear PIDs (scIrdStreamFilteringClearPids) – Clears all selected PIDs from

the PIDs table.

IRD-2900 MIB



• Filtering Services Table (scIrdStreamFilteringServiceTable) – Selects

services-to-filter when filtering strategy is set to 'services (1)'. The table

presents the following objects:

• ID (scIrdStreamFilteringServcieId) – Selects the service-to-filter from

the transport-stream according to the service ID number.

• Status (scIrdStreamFilteringServiceStatus) – Allows the user to create

and drop entries from the table. The supported options are:

• active (1) – The service specified in the entry is supported and

active.

• createAndGo (4) – Add a new entry. The entry is immediately set

as 'active (1)'.

• destroy (6) – Drop the selected entry from the table.

• Filtering PIDs Table (scIrdStreamFilteringPidTable) – Selects PIDs-to-filter

when filtering strategy is set to 'pids (2)'. The table presents the following

objects:

• PID (scIrdStreamFilteringPid) – Selects the PIDs-to-filter from the

transport-stream according to the PID number.

• Status (scIrdStreamFilteringPidStatus) – Allows the user to create and

drop entries from the table. The supported options are:

• active (1) – The PID specified in the entry is supported and active.

• createAndGo (4) – Add a new entry. The entry is immediately set

as 'active (1)'.

• destroy (6) – Drop the selected entry from the table.

User Guidelines



3.4. SERVICE

3.4.1. Service Configuration The Service group manages the service channels and service port

configurations.

The Interface table (ifTable) displays each output-decoding port entry by name

(ifDescr column), Instance number (Instance), and its type (ifType). Figure 3-25

shows an example of the ifTable, highlighting the mentioned columns.


The Service Port table (scIrdServiceConfigPortEntry) details the ports and their

Channel alignments (see Figure 3-26). In this example, 513 is a PID assigned to

Port Video-1 (to know which port, compare the instance number with the

interface table instances and find the name of the port). Notice that PID number

513 is allocated to Video-1, which is configured to Channel-1 (see

scIrdServiceConfigPortChannel column).

IRD-2900 MIB



Figure 3-26: Service Port Table (scIrdServiceConfigPortTable)

The Service objects are divided into three groups: Strategy, Port, and

Channel. The object groups are illustrated in Figure 3-27 and detailed in the

following sections.

Figure 3-27: Service Tree

User Guidelines



3.4.1.1. Strategy

The Strategy group sets the functioning of the IRD in case of program absent or

stream cascading strategy. For OID information, see Section 2.3.3.1.

Strategy definitions:

• Program Absent (scIrdServiceStrategyProgramAbsent) - Sets the object

mode of operation. When a program number (sent in PAT) is missing in the

received stream, the Program Absent object defines the behaviour of the

IRD in such a case.


• goto-first (0) – Searches for the first program number in the transport

stream and attaches it to the service

• wait-user (1) – When the program number is missing, the service waits

for a user-defined program number

• CAS strategy (scIrdServiceStrategyCas) – defines which ES will be

decrypted by the CAM. It is possible to either instruct the IRD-2900 to

decrypt all the received ES, or allow it to decrypt only the ones that are

currently being decoded..


• decodedOnly (0) – the IRD decryps the decoded elementary streams

from the incoming transport stream.

• all (1) – The IRD decrypts all elementary streams in the incoming

transport stream.

IRD-2900 MIB



3.4.1.2. Service Port

This group of objects sets the output-decoding port definitions. Figure 3-28

illustrates the Service Port objects group. For OID information, see Section

2.3.3.2.

Service port definitions:

• Output-decoding port PID (scIrdServiceConfigPortPid) - Sets the Packet

Identifier of an output-decoding port in a service port.

• Port Channel (scIrdServiceConfigPortChannel) – Connect an output-

decoding port to a specific service channel. If an output-decoding port mode

is set to stand-alone, the value of this object is set to 0

• PCR interface index (scIrdServiceConfigPortPcrIfIndex) - Sets the interface

index number of the PCR port connected to a service port. If the PCR port is

not connected to a service port, the PCR IF index value is 0.

• Preferred language (scIrdServiecConfigPortPrefLanguage) - Sets the

preferred language for a service port.

• Page (scIrdServiceConfigPortPage) – Selects the Teletext or Subtitle page.

Figure 3-28: Service Port Parameters Group

User Guidelines



3.4.1.3. Service Channel

The Service Channel table contains the channel object definitions of the service.


Service channel definitions:

• Channel Number (scIrdServiceConfigChannelNumber) – Gets the channel

number, used for the service index. This object is not accessible but its pre-

inserted information is the index for the Instance column of the table.

• Service ID (scIrdServiceConfigChannelServiceId) – Sets the service ID

number. The service ID is the program number and is acquired from the PAT

in the transport stream.

Figure 3-29 illustrates the relations between the service channel and port tables.

The Service Channel table contains the service ID numbers in the allocated

channel entry.

The Service Port table details the output-decoding ports in the service channels.

The Channel column (scIrdServiceConfigPortChannel) allocates each output-

decoding port to its service channel.

The output-decoding port name is found in the Interface table. This name can be

located by comparing the instance number in the Port table to the instance

number in the Interface table. (ifTable and scIrdServiceConfigPortTable).

IRD-2900 MIB



Figure 3-29: Service Channel and Port Indexes

User Guidelines



Figure 3-30: Service Channel Parameters Group

NOTE

The Service ID is the Instance number of the requested program. The Program

name is located in “Stream Service” under the name “serviceDescr” (for

further information see Section 3.4.3).

The two services Channel numbers are 1 and 2, and correspond with the IRD

front-panel TV1 and TV2 channels. While the selection of the TV1/TV2 Select

presents the service list of the channel, the Channel table does not display

service information. Service information (such as: PID, Channel, PCR, and

preferred language) is displayed in the Service Port table (see Section 3.4.2). To

check the service name, access the Stream Service table

(scStreamServiceTable). For more information on accessing the table, see

Section 3.4.3.

IRD-2900 MIB



3.4.2. Service Port Table

The Service Port table (scIrdServiceConfigPortTable) displays the output-

decoding ports of the services and their Service Port information: PID, related

channel number, PCR Index number, and preferred language.

Figure 3-31: Service Port Table (scIrdServiceConfigPortTable)

The Service Port table displays the decoding PIDs of all output-decoding ports in

the active services. However, the table does not display the output-decoding

port names and types (such as Video-1, Audio-2, and so on). To view this

information, access the Interface table in Figure 3-32.

Figure 3-32: Interface Table – Index Source (ifTable – Instance, ifDescr, and ifType)

User Guidelines



The ifTable is the index source for the Service Port table. In the ifTable, find the

output-decoding port name according to its instance number. For more

information about the ifTable, see Section 2.1.1.

3.4.3. Service Configuration

The Channel table gets the channel number and sets a service to that channel.

When setting a service to the channel, the table does not display the Service

Name (unlike in the corresponding option in the IRD Front Panel) Rather, the

Service name can be found in the Stream Service table (scStreamServiceTable,

see Figure 3-33).

Figure 3-33: Stream Service Table (scStreamServiceTable)

The Stream Service table OID is 1.3.6.1.4.1.4466.1.13.1.100.10.72 –

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scopusRoot

(4466).scopusProducts(1).scCommonObjects(13).scStream(1)scStream

Descriptors(100)scStreamServiceTable(72).

This table displays the Service Name under scStreamServcieName and its

Service ID number under scStreamServiceIndex1. When setting a program,

select it by its name from the Name column and set the Instance number into

the Service Channel table, under Service ID

(scIrdServiceConfigChannelServiceId, see Figure 3-34).

IRD-2900 MIB



Figure 3-34: Set Service Description

User Guidelines



3.4.4. Setting Service Parameters

The following sections detail all Service Port table objects, their functions, and

setting options.

3.4.4.1. Setting a PID (scIrdServiceConfigPortPcrPid)

The PID is the Packet Identifier of an output-decoding port. It is a number that

identifies an output-decoding port in a specific Service. The PID value is

extracted from the Service PID. The Service PID values are drawn from the PMT

(Program Mapping Table), received in the input transport stream (see Figure

3-35).

Figure 3-35: Service Configuration – PCR PID Column (scIrdServiceConfigPortPid)

When changing the output-decoding port PID, the new PID can be any number

in the range of 0 to 1FFF, as long as it is taken from the PMT of the specific

program. This way the port still recognizes the output-decoding port as part of

the service and keeps it within the channel. When the PID is not taken from the

service PMT, the port cannot identify the output-decoding port and drops it from

the channel.

When setting the PID to a value that does not exist in the service and that is

different from the available values in the PMT, the user must set Mapping Object

to 0 (set column scIrdServiceConfigPortChannel in Port table). When the

mapping is set to 0, the output-decoding port is set as a stand-alone object,

IRD-2900 MIB



thus not connecting it to any service or channel and preventing the channel from

dropping the output-decoding port.

3.4.4.2. Mapping Port to Service (scIrdServiceConfigPortChannel)

This column determines the channel related to the service. The channel can be

set to Channel 1 or Channel 2 (if applicable) or to stand alone (0) when required

(see Section 3.4.4.1 for stand alone option). See Figure 3-36 for Channel column

display.

Figure 3-36: Service Configuration – Channel Column (scIrdServiceConfigPortChannel)

The IRD relates the service output-decoding ports (located in a PMT) to the

channel output-decoding ports (related to the specific channel).

Figure 3-37 illustrates the Select Service process. In this example, Program-1 is

selected to Channel 2.

User Guidelines



PAT

PMT (20)elementary streams

PMT (30)Service ID

Video ES (PID)

100

Audio ES (PID)

200

Video-1

Audio-1

Video-2 (Port)

100

Audio-3 (Port)

200

SDTService Description Table=

Service Name

Channel 1

Channel 2

PMT PID

Elementary

Stream PID

Service ID=1

Program 1

Program 2

Figure 3-37: Select Service Process

To indicate that this program is related to this channel the PMT holding the

Service ID number is located with the Channel 2 title.

The PMT holding the elementary streams is routed to the relevant output-

decoding ports in Channel 2, titled correspondingly to the channel: Video

becomes Video-2, Audio becomes Audio-3 and so on. The program still

recognizes these elementary streams by their constant PID.

The SDT contains the name of the program and is located in the Stream Service

table (scStreamServiceTable).

NOTE

The mapping column (scIrdServiceConfigChannel) indicates whether an output-

decoding port is related to Channel 1 or Channel 2, as the Service Port table

displays all output-decoding ports for both channels and services. The output-

decoding port can also be set as a stand-alone. This setting is used when the

IRD-2900 MIB



PID is not taken from the service PMT. In such case, the mapping column is set

to 0.

User Guidelines



3.4.4.3. PCR Interface Index (scIrdServiceConfigPortPcrIfIndex)

PCR is a synchronization clock between the decoder and the incoming stream

from the encoder. The PCR PID signal is located within the PMT table.

When the user decides to work without tables, for instance in stand-alone mode,

the stand-alone output-decoding port has no synchronization reference, as it is

not related to the PMT holding the PCR PID. In such cases, the user must relate

the output-decoding port with a PCR interface for synchronization reference.

To refer an output-decoding port to a PCR interface in the IRD-2900, set the

PCR Interface Index to the requested PCR interface (by setting it to the PCR

interface instance number). When PCR Interface Index object is set to 0, the

output-decoding port is not related to the IRD-2900 PCR and received

synchronization from the PCR PID in the PMT. See Figure 3-38 for PCR Interface

Index column display.

Figure 3-38: Service Configuration – PCR Interface Index Column (scIrdServiceConfigPortPcrIfIndex)

IRD-2900 MIB



3.4.4.4. Set a Preferred Language (scIrdServiceConfigPortPrefLanguage)

The Preferred Language object sets the language of the audio output-decoding

port in the service (see Figure 3-39).

Figure 3-39: Service Configuration – Preferred Language Column (scIrdServiceConfigPortPrefLanguage)

Three characters (composing a 24-bit string) represent the preferred language.

The representation of the language code in the MIB is through a specific

number. The numeric code is detailed in the ISO 639 Language Code.

When setting a new language for the service, the IRD searches the service PMT

for that language. If the required language cannot be found, the IRD changes

the Preferred Language definition to the first language that is found in the

service. Figure 3-41 illustrates the Video Configuration tree.

User Guidelines



3.4.4.5. Port Page

The Page object sets the page definitions for subtitles. The object selects the

requested subtitle page for the relevant elementary stream. See Figure 3-40 for

Page column display.

Figure 3-40: Service Configuration – Page Column (scIrdServiceConfigPortPage)

IRD-2900 MIB



3.5. VIDEO CONFIGURATION The Video Menu sets and monitors all video channel object definitions and VBI

object definitions. These menu objects are categorized into several groups, as

detailed in the following sections.

Figure 3-41: Video and VBI Tree

User Guidelines



3.5.1. Video

This group sets the video channels object definitions for video transmission.

Figure 3-42: Video Tree

IRD-2900 MIB



3.5.1.1. Format

This group sets the format objects of the video signal. The availability of these

objects depends on the video format, whether set to NTSC or PAL. Figure 3-43

illustrates the Format objects group. For OID information, see Section 2.3.4.

Format definitions:

• Format (scIrdVideoConfigFormat) – Sets the format of the video signal

(NTSC or PAL)

• Chroma Format (scIrdVideoMpegChromaFormat) – Sets the chrominance

definitions

• Standard Format (scIrdVideoMpegStandardFormat) - Gets the number of

rows in the incoming signal

Figure 3-43: Video Format Parameters Group

User Guidelines



3.5.1.2. Aspect Ratio

This group sets and monitors the video aspect ratio. Figure 3-44 illustrates the

Aspect Ratio objects group. For OID information, see Section 2.3.4.

Aspect-ratio definitions:

• Aspect Ratio (scIrdVideoConfigAspectRatio) – Sets the image’s height-to-

width ratio

• Aspect Ratio Information (scIrdVideoMpegAspectRatioInfo) – Gets the

aspect ratio’s current value

Figure 3-44: Aspect-Ratio Parameters Group

3.5.1.3. Screen Blank

The Screen Blank object sets the default image that is displayed when

transmission stops unexpectedly (scIrdVideoConfigScreenBlank). For OID

information, see Section 2.3.4.

IRD-2900 MIB



3.5.1.4. Lips Synchronizations

Lips synchronization sets and monitors the synchronization between video and

audio streams. Figure 3-45 illustrates the Synchronization objects group. For

OID information, see Section 2.3.4.

Lip-synchronization definitions:

• Lip-Sync Mode (scIrdVideoConfigLipSyncMode) - Sets the mode of

synchronization

• Lip-Sync Delay (scIrdVideoConfigLipSyncDelay) - Sets the delay limit

before synchronization is required

The synchronization between the system time clock and the IRD clock is defined

through the PCR SCT delay (scIrdVideoConfigPcrSctDelay).

Figure 3-45: Lips Synchronization Parameters Group

User Guidelines



3.5.2. VBI

This group sets the VBI definitions. The VBI Instance is composed of two

numeric values, separated by a decimal point and extracted from the ifTable and

scIrdVbiType object. The first number represents the VBI output-decoding port

(VBI-1 or VBI-2) and the second represents the VBI Type.

Figure 3-46 shows an example of the VBI table. The first nine rows represent

each VBI Type definition in VBI-1, while the other nine rows represent each VBI

type definitions in VBI-2. In the highlighted entry, VBI-1 is represented by the

number 1179189504.# (to confirm, access the table index, ifTable, and search

for the output-decoding port name allocated with the instance). The second

number is the VBI type, represented by #########.1 (for VBI type options,

refer to the MIB).

Figure 3-46: VBI Configuration Table (scIrdVbiConfigTable)

IRD-2900 MIB



Figure 3-46 illustrates the VBI table objects.

Figure 3-47: VBI Tree

User Guidelines



3.5.2.1. VBI Type

Sets the VBI type. Figure 3-48 illustrates the VBI Type objects group. For OID


VBI type definitions:

VBI Type (scIrdVbiType) - Sets the type of VBI. This number is also the options

number that is passed on as index values in the VBI Configuration table. The


• null (0)

• teletext (1)

• nabts (2) – North American

broadcast teletext specification

• vps (3) - Video Programme System

• wss (4) - Wide Screen Signaling

• cc (5) - Close Captioning

• amol (6) - Automated Measurements

Of Line-ups

• vits (7) - Vertical Interval Test Signals

• vitc (8) - Vertical Interval Time Code

• smc (9) - Sound Mode Control

• tvg (10) – TV Guide

• vi (11) - Video Index

IRD-2900 MIB



Figure 3-48: VBI Type Parameters Group

User Guidelines



3.5.2.2. VBI Definitions

Set the VBI source a insertion lines definitions. Figure 3-49 illustrates the VBI

Definitions objects group. For OID information, see Section 2.3.4.1.

VBI definitions:

• Source (scIrdVbiSource) - Source information available for a VBI type

selected in the table

• Line position – Sets the first line position (scIrdVbiLine1) and second line

position (scIrdVbiLine2) for each VBI type

Figure 3-49: VBI Definitions Parameters Group

IRD-2900 MIB



3.5.3. OSD

The OSD menu object allows the user to configure and set the OSD definitions.

The following sections detail the OSD object groups. Figure 3-50 illustrates the

OSD tree. For OID information, see Section 2.3.4.1.

User Guidelines



Figure 3-50: OSD Tree

3.5.3.1. Text Insertion Basic Definitions

The Text Insertion Basic Definitions group is composed of the OSD Text

Insertion table’s objects (scIrdOsdTextInsertionConfigTable). For OID

information, see Section 2.3.4.1

IRD-2900 MIB



Text Insertion Basic definitions:

• String (scIrdOsdTextInsertionString) – Writes the inserted text’s string of

characters

• Color (scIrdOsdTextInsertionColor) – Sets the inserted text’s displayed color

• X Position (scIrdOsdTextInsertionXposition) – Sets the text position in

pixels

• Y Position (scIrdOsdTextInsertionYPosition) – Sets the text position in pixel

• Enable (scIrdOsdTextInsertionEnable) – Sets the activation mode of the

Text Insertion

NOTE

For detailed information refer to the MIB file.

User Guidelines



3.5.3.2. Outputs Group

The output group contains the output mode objects. These objects allow the

user to set the monitor and broadcast outputs mode. Figure 3-51 illustrates the

OSD Outputs tree. For OID information, see Section 2.3.4.1

Outputs definitions:

• Monitor Output (scIrdOsdMonitorOutput) – Allows the user to enable or

disable the Monitor output activation mode in the rear panel.

• Broadcast Output (scIrdOsdBroadcastOutput) – Allows the user to enable

or disable the broadcast output activation mode in the rear panel.

Figure 3-51: OSD Outputs Parameters Group

IRD-2900 MIB



3.5.3.3. Position Offset Group

The Position Offset group contains the X and Y position objects. These objects

allow the user to set the horizontal and vertical offset of the OSD. Figure 3-52

illustrates the OSD Outputs tree. For OID information, see Section 2.3.4.1

Position Offset definitions:

• X Position Offset (scIrdOsdXPositionOffset) – Allows the user to set the

horizontal offset of the OSD. Valid range is between –300 to +300 pixels.

• Y Position Offset (scIrdOsdYPositionOffset) – Allows the user to set the

vertical offset of the OSD. Valid range is between –300 to +300 pixels.

Figure 3-52: OSD Position Parameters Group

User Guidelines



3.5.3.4. Subtitle Mode Group

The Subtitle Mode group contains the Teletext and DVB subtitle mode objects.

These objects allow the user to set the subtitle mode and type. Figure 3-53

illustrates the OSD Outputs tree. For OID information, see Section 2.3.4.1

Subtitle Mode definitions:

• DVB Subtitle Mode (scIrdOsdDvbSubtitleMode) – Allows the user to use

DVB subtitling mode. The object sets the subtitle operation mode. The


• Disable – Disables DVB Subtitling.

• No Page Filter – This is the IRD default setting.

• Use Page Filter – Use this option when more than one DVB subtitling

pages exist in the OSD PID. The Page Filter identifies the page that

contains actual subtitling data.

• Teletext Subtitle Mode (scIrdOsdTltxSubtitleMode) – Allows the user to

use TTX subtitling. The object also sets the subtitle operation mode. The


• Enable

• Disable

NOTE

Activating one subtitling mode automatically disables the other, as there can

only be one subtitling mode active at any given moment.

IRD-2900 MIB



Figure 3-53: OSD Subtitle Mode Parameters Group

User Guidelines



3.6. AUDIO CONFIGURATION The Audio Menu sets and monitors the audio channel information and gets the

status for each specified decoding mode. These menu objects are categorized

into several groups.

Figure 3-54 illustrates the Audio tables and objects tree.

Figure 3-54: Audio Tree

IRD-2900 MIB



3.6.1. General Parameters

This group of objects sets audio channel affects for all audio coding schemes.

Figure 3-55: General Parameters Group

3.6.1.1. Attenuation

The audio volume is set by the Attenuation object (scIrdAudioAttenuation). For


User Guidelines



3.6.1.2. Decoding Mode

This object enables the relevant status table according to the selected audio

decoding scheme. Figure 3-56 illustrates the Decoding Mode objects group. For


Decoding mode definitions:

• Decoder Mode (scIrdAudioDecodeMode) - Sets the decoding mode and

method. The available options are:

• musicam (0)

• dolby-ac3 (1)

• ac3-passthrou (2)

• linear-pcm (3)

• auto (4) – Output decoding mode is set according to the received input

decoding mode.

NOTE

Selecting a decoding mode enables the relevant status table. The status table

gets the status information regarding the decoding scheme.

Figure 3-56: Decoding Mode Parameters Group

IRD-2900 MIB



3.6.1.3. Mute

Muting an audio channel (through the scIrdAudioMute object) stops all audio

transmission of that channel. For OID information, see Section 2.3.5. the Mute

object is a true/false flag where:

• TRUE – Sets the mode to mute. Silences the analog audio signal in a

specific audio channel

• FALSE – Sets the mode to play, or un-mute. The current analog audio is

heard on a specific audio channel.

3.6.1.4. Synchronization

A/V Sync (scIrdAudioAVSync) – Synchronizes the audio and video outputs of a

channel. For OID information, see Section 2.3.5.

• TRUE – Synchronizes the audio with the video interface

• FALSE – Does not synchronize the audio with the video interface.

3.6.1.5. Digital Format

The Digital Format object (scIrdAudioDigitalFormat) sets the digital format of the

output audio – determining the method of extracting the audio from the stream.

For OID information, see Section 2.3.5.


• consumer (0) – The audio is extracted as a Consumer algorithm

• professional (1) – The audio is extracted using a more professional

algorithm.

User Guidelines



3.6.2. Musicam

This group sets and gets all analog Musicam, or MPEG, audio-output definitions.

Figure 3-57: Musicam Tree

IRD-2900 MIB



3.6.2.1. MPEG Identity

This group influences the MPEG Musicam identity when audio channel is set to

Musicam decoding mode. Figure 3-58 illustrates the MPEG Identity objects

group. For OID information, see Section 2.3.5.

MPEG identity definitions:

• Analog Mode (scIrdAudioAnalogMode) - Sets the output transmission mode

of the audio channel

• Mode (scIrdAudioMpegMode) - Gets the broadcasting mode of the channel

• MPEG ID (scAudioMpegId) – Gets the output MPEG ID

• Layer (scIrdAudioMpegLayer) – Gets the level of decoding

Figure 3-58: MPEG Identity Parameters Group

User Guidelines



3.6.2.2. Rate Information

This group influence the audio channel bit rate and sample rate. Figure 3-59

illustrates the MPEG Rate Information objects group. For OID information, see

Section 2.3.5.

Rate information definitions:

• Bit-Rate (scIrdAudioMpegBitRate) – Gets the audio channel bit-rate

• Sample rate (scIrdAudioMpegSampleRate) – Gets the audio channel sample

rate

Figure 3-59: MPEG Rate Parameters Group

IRD-2900 MIB



3.6.3. Linear PCM

This group sets and gets all Linear-PCM transmission data.

Figure 3-60: Linear PCM Tree

User Guidelines



3.6.3.1. Linear Identity

This group influences the Linear PCM identity when audio channel is set to Linear

decoding mode. Figure 3-61 illustrates the Linear Identity objects group. For


Linear identity definitions:

• Channel ID (scIrdAudioLinearChannelId) – Gets the Linear ID of the output

channel

• Output Mode (scIrdAudioLinearOutputMode) - Gets the output mode of the

audio output stream

Figure 3-61: Linear Identity Parameters Group

IRD-2900 MIB





illustrates the Linear Rate Information objects group. For OID information, see

Section 2.3.5.


• Sample Rate (scIrdAudioLinearSampleRate) – Gets the linear transmission

sample rate

• Bits-per-Sample (scIrdAudioLinearBitsPerSample) – Gets the Bit-per-

Sample ratio of the audio stream.

Figure 3-62: Linear Rate Parameters Group

User Guidelines



3.6.4. Dolby Digital AC-3

This group sets and monitors the AC-3 decoding mode objects and definitions.

Figure 3-63: Dolby AC-3 Tree

IRD-2900 MIB



3.6.4.1. AC-3 Identity

This group influences the Dolby AC-3 identity when audio channel is set to AC-3

decoding mode. Figure 3-64 illustrates the AC-3 Identity objects group. For OID

information, see Section 2.3.5.

AC-3 identity definitions:

• AC-3 Operational Mode (scIrdAudioAc3OperationalMode) - Sets the

operational AC-3 mode definition

• AC-3 Down Mix Mode (scIrdAudioAc3DownmixMode) - Sets the AC-3

Downmix mode definition

• AC-3 BS Mode (scIrdAudioAc3BsMode) – Gets the AC-3 BS mode definition

• AC Mode (scIrdAudioAc3AcMode) – Gets the AC-3 mode definition

Figure 3-64: AC-3 Identity Parameters Group

User Guidelines





illustrates the AC-3 Rate Information objects group. For OID information, see

Section 2.3.5.


• Sample Rate (scIrdAudioAc3SampleRate) – Gets the AC-3 sample rate

value

• Bit Rate (scIrdAudioAc3BitRate) – Gets the AC-3 bit rate value

Figure 3-65: AC-3 Rate Parameters Group

IRD-2900 MIB



3.6.5. AC-3 Pass-Through

This group sets the AC-3 Pass-Through definitions, such as sample rate (through

scIrdAudioAc3PassThruSampleRate). Figure 3-66 illustrates the AC-3 Pass

Through objects tree. For OID information, see Section 2.3.5.

Figure 3-66: AC-3 Pass Through Tree

User Guidelines



3.7. DATA CONFIGURATION The Data Menu object sets and monitors the IP and High-Speed data object

definitions. These menu objects are divided into several groups, detailed in the

following sections.

Figure 3-67: Data Tree

IRD-2900 MIB



3.7.1. High-Speed Data (HSD)

This group contains the object settings for High Speed Data transmission.

Figure 3-68: HSD Table (scIrdHsdConfigTable)

3.7.1.1. HSD Definitions

This group defines the High-Speed data information. For OID information, see

Section 2.3.6.1.

High-speed data definitions:

• Clock Value (scIrdHsdClockValue) – Sets the speed of the HSD clock, used

for synchronization.

• Layer (scIrdHsdLayer) – Sets the HSD transmission layer.

• Bit Order (scIrdHsdBitOrder) – Sets the send-format by determining

whether the LSB or the MSB is sent first

User Guidelines



3.7.2. IP Data

This group contains the information required for sending data transmission

through IP.

Figure 3-69: IP Table (scIrdIpDataConfigTable)

3.7.2.1. Address and Port Definitions

This group defines the IP data address and port information. For OID


Address and port definitions:

• Destination IP Address (scIrdIpDataDestinationIpAddress) – Sets the

destination IP-address definitions

• Destination Port Number (scIrdIpDataDestinationPort) – Sets the

destination IP-port number

• Source Port (scIrdIpDataSourcePort) – Sets the source IP port

• Port Type (scIrdIpDataProtocol) – Sets the type and protocol of the IP port

• Number Send Packets (scIrdIpDataNumberSendPackets) - Sets the

amount of packets per a transmitted datagram

3.7.2.2. Mode

Data Mode (scIrdIpDataMode) - Sets the Send mode of the IP-output transport

stream or IP data output. For OID information, see Section 2.3.6.2.

IRD-2900 MIB



3.7.3. Low-Speed Data (LSD)

This group is used for setting the IRD-2900 Low Speed Data port objects.

Figure 3-70: Low Speed Data Table Parameters (scIrdLsdConfigTable)

The IRD-2900 supports Low Speed Data output via RS232. It enables different

rates of transmission, as well as three levels of output-data filtering.

NOTES

• The IRD-2900 automatically directs PIDs with the MPEG-2 descriptor: private_data_indicator holding a value 15 with indicator value 0 for transmission through its Low Speed Data port.

• The minimum amount of data that can be transmitted through the LS Data port is the size of one PES payload.

The Low Speed Data table displays the following objects:

• Baud Rate (scIrdLsdConfigBAudrate) – Allows the user to select between

seven possible LS data transmission rates. The available transmission rates

are:

• 1200

• 2400

• 4800

• 9600

• 38400

• 57600

• 115200

NOTE

User Guidelines



The LS Data transmission Baud Rate settings must comply with the

corresponding encoder’s data-encapsulation rate

• Transport Layer (scIrdLsdConfigTansportLayer) – Sets the transport layer

level. The IRD-2900 supports three levels of low speed data transport layer,

determining the type of data to be transmitted via the LS Data port. The

possible levels are:

• ts-payload (2) - For outputting only the transport stream payload (the

TS header and the adaptation field are stripped)

• pes (3) - For outputting only the PES payload (the PES header is

stripped)

• dvb-streaming (4) - For outputting only DVB Asynchronous Data

Streaming according to the EN-301-192 standard (the first 3 bytes of the

PES_data_packet are stripped)

IRD-2900 MIB



3.8. CAS CONFIGURATION The CAS menu object sets and monitors the conditional access definitions. The

CAS menu enables the BISS scrambling, along with the different BISS modes

and their scrambling keys and definitions.

Figure 3-71: CAS Tree

User Guidelines



3.8.1. BISS-E Clear SW Mode

Sets the BISS scrambling mode to BISS-E Clear SW mode. Allows the user to

set the session word key in the Session Word table

(scIrdBISSSessionWordTable).

BISS-E Clear SW definitions:

• BISS Mode (scIrdBISSMode) – Sets the scrambling mode. The available

options are:

• Even-Odd

• BISS Mode 1

• BISS-E Clear SW

• BISS-E Injected ID

• BISS-E Buried ID

• Session Word (scIrdBISSSessionWordTable)– Allows the user to set the

session word key.

NOTE

The key can only be set, but not viewed.

Figure 3-72: BISS Clear Mode Parameters Group

IRD-2900 MIB



3.8.2. BISS Mode 1

Sets the BISS scrambling mode to BISS Mode-1. Allows the user to set the

session word key in the Session Word table (scIrdBISSSessionWordTable).

BISS Mode-1 definitions


options are:

• Even-Odd

• BISS Mode 1

• BISS-E Clear SW




session word key.

NOTE


User Guidelines



Figure 3-73: BISS Clear Mode Parameters Group

IRD-2900 MIB



3.8.3. Even-Odd Mode

Sets the BISS scrambling mode to Even-Odd mode. Allows the user to set the

even and odd keys in the Even-Odd table (scIrdBISSEvenOddTable).

Even-Odd definitions


options are:

• Even-Odd

• BISS Mode 1

• BISS-E Clear SW



• Even Odd Keys (scIrdBISSEvenOddTable)– Allows the user to set the even

and odd keys.

• Even Key (scIrdBISSEvenKey)

• Odd Key (scIrdBISSOddKey)

NOTE

The keys can only be set, but not viewed.

Figure 3-74: BISS Even-Odd Mode Parameters Group

User Guidelines



3.8.4. BISS-E Buried ID Mode

Sets the BISS scrambling mode to BISS-E Buried ID mode. Allows the user to

set the session word key in the Session Word table


BISS-E Buried ID definitions:


options are:

• Even-Odd

• BISS Mode 1

• BISS-E Clear SW




session word key.

NOTE


IRD-2900 MIB



Figure 3-75: BISS-E Buried ID Mode Parameters Group

User Guidelines



3.8.5. BISS-E Injected ID Mode

Sets the BISS scrambling mode to BISS-E Injected ID mode. Allows the user to

set the Injected ID key and the session word key in the Session Word table


BISS-E Injected ID definitions:


options are:

• Even-Odd

• BISS Mode 1

• BISS-E Clear SW



• Injected ID – Allows the user to set the Injected ID key.


session word key.

NOTE

The keys can only be set, but not viewed.

Figure 3-76: BISS-E Injected ID Mode Parameters Group

mib IRD-2900_SNMP_Rev._4.6

Documents

Transcript of mib IRD-2900_SNMP_Rev._4.6