Tektronix MTM400 Programmer Manual

Programmer Manual

MTM400
MPEG Transport Stream Monitor

071-1375-02

This document applies to firmware version 2.3.8
and above.

www.tektronix.com

Copyright © Tektronix. All rights reserved. Licensed software products are owned by Tektronix or its subsidiaries or
suppliers, and are protected by national copyright laws and international treaty provisions.

Tektronix products are covered by U.S. and foreign patents, issued and pending. Information in this publication supercedes
that in all previously published material. Specifications and price change privileges reserved.

TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.

Contacting Tektronix

Tektronix, Inc.
14200 SW Karl Braun Drive
P.O. Box 500
Beaverton, OR 97077
USA

For product information, sales, service, and technical support:

H In North America, call 1-800-833-9200.

H Worldwide, visit www.tektronix.com to find contacts in your area.

Warranty 2

Tektronix warrants that this product will be free from defects in materials and workmanship for a period of one (1)
year from the date of shipment. If any such product proves defective during this warranty period, Tektronix, at its
option, either will repair the defective product without charge for parts and labor, or will provide a replacement in
exchange for the defective product. Parts, modules and replacement products used by Tektronix for warranty work
may be new or reconditioned to like new performance. All replaced parts, modules and products become the
property of Tektronix.

In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration
of the warranty period and make suitable arrangements for the performance of service. Customer shall be
responsible for packaging and shipping the defective product to the service center designated by Tektronix, with
shipping charges prepaid. Tektronix shall pay for the return of the product to Customer if the shipment is to a
location within the country in which the Tektronix service center is located. Customer shall be responsible for
paying all shipping charges, duties, taxes, and any other charges for products returned to any other locations.

This warranty shall not apply to any defect, failure or damage caused by improper use or improper or inadequate
maintenance and care. Tektronix shall not be obligated to furnish service under this warranty a) to repair damage
resulting from attempts by personnel other than Tektronix representatives to install, repair or service the product;
b) to repair damage resulting from improper use or connection to incompatible equipment; c) to repair any
damage or malfunction caused by the use of non-Tektronix supplies; or d) to service a product that has been
modified or integrated with other products when the effect of such modification or integration increases the time
or difficulty of servicing the product.

THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PRODUCT IN LIEU OF ANY
OTHER WARRANTIES, EXPRESS OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
TEKTRONIX’ RESPONSIBILITY TO REPAIR OR REPLACE DEFECTIVE PRODUCTS IS THE SOLE AND
EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF THIS WARRANTY.
TEKTRONIX AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHER TEKTRONIX OR THE VENDOR HAS
ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

Warranty 9(b)

Tektronix warrants that the media on which this software product is furnished and the encoding of the programs on
the media will be free from defects in materials and workmanship for a period of three (3) months from the date of
shipment. If any such medium or encoding proves defective during the warranty period, Tektronix will provide a
replacement in exchange for the defective medium. Except as to the media on which this software product is
furnished, this software product is provided “as is” without warranty of any kind, either express or implied.
Tektronix does not warrant that the functions contained in this software product will meet Customer’s
requirements or that the operation of the programs will be uninterrupted or error-free.

In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration
of the warranty period. If Tektronix is unable to provide a replacement that is free from defects in materials and
workmanship within a reasonable time thereafter, Customer may terminate the license for this software product
and return this software product and any associated materials for credit or refund.

THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PRODUCT IN LIEU OF ANY
OTHER WARRANTIES, EXPRESS OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
TEKTRONIX’ RESPONSIBILITY TO REPLACE DEFECTIVE MEDIA OR REFUND CUSTOMER’S
PAYMENT IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF
THIS WARRANTY. TEKTRONIX AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHER TEKTRONIX
OR THE VENDOR HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

Table of Contents

Introduction

MTM400 MIB

MIB Group Overview

System Structure

Preface iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Material iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SNMP and MIBs 1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTM400 SNMP Community 1−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTM400 SNMP Traps 1−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTM400 Web Server 1−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MIB Types 2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing MIB Objects 2−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Structure

Web Server URLs

System Information Group 4−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Box Event Group 4−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Box Log Group 4−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Settings 4−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

License Table 4−12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Interfaces Group 5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Events Group 5−24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG PIDs Group 5−27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Structure Group 2 5−34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Log Group 5−38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Trap Control 5−40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Configuration Group 5−41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Parameters Group 5−44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MPEG Record Group 5−47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration 6−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Schedules 6−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Recording 6−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging 6−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Service Logs 6−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TMCC Information 6−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MTM400 MPEG Transport Stream Monitor Programmer Manual

i

Table of Contents

List of Figures

Templates 6−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Licensing 6−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Debug Information 6−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controls 6−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table Information 6−9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PCR/PTS Information 6−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Repetition Information 6−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RF Card Information 6−13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2−1: Time stamp storage 2−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3−1: Overall MIB structure 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3−2: System structure 3−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3−3: MPEG structure 3−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4−1: System structure 4−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4−2: System information group structure 4−1. . . . . . . . . . . . . . . . . . .

Figure 4−3: Box event group structure 4−6. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4−4: Box log group structure 4−8. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−1: MPEG structure 5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−2: MPEG interfaces group structure 5−1. . . . . . . . . . . . . . . . . . . . .

Figure 5−3: MPEG interfaces table structure 5−2. . . . . . . . . . . . . . . . . . . . .

Figure 5−4: L-Band information group structure 5−7. . . . . . . . . . . . . . . . . .

Figure 5−5: QAM information group structure 5−12. . . . . . . . . . . . . . . . . . . .

Figure 5−6: MPEG events group structure 5−24. . . . . . . . . . . . . . . . . . . . . . .

Figure 5−7: MPEG PIDs group structure 5−27. . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−8: Structure group 2 structure 5−35. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−9: MPEG log group structure 5−38. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−10: MPEG configuration group 5−41. . . . . . . . . . . . . . . . . . . . . . . .

Figure 5−11: MPEG parameters group structure 5−44. . . . . . . . . . . . . . . . . . .

ii

MTM400 MPEG Transport Stream Monitor Programmer Manual

Preface

This document specifies the MTM400 MPEG Transport Stream Monitor remote
control and status monitoring interfaces available to a Management application.
Two interfaces are provided; SNMP and an HTTP Web-based interface.

The manual is organized into the following sections:

H Introduction

H MTM400 MIB

H MIB Group Overview

H System Structure

H MPEG Structure

H Web Server URLs

The following documents are also available on the Tektronix Web site
(www.tektronix.com):

H MTM400 MPEG Transport Stream Monitor User Manual

(Tektronix part number: 071-1224-xx)

Related Material

This manual provides operational information for the MTM400.

H MTM400 MPEG Transport Stream Monitor Technical Reference

(Tektronix part number: 071-1560-xx)

This manual provides product specifications, test parameters, configuration
file syntax, and hardware maintenance procedures.

The following URLs access the Web sites for the standards organizations listed
(the URLs listed were valid at the time of writing):

H MPEG−2 standards (International Organization for Standards)

http://www.iso.ch/

H DVB standards (European Technical Standards Institute)

http://www.etsi.org/

H ATSC standards (Advanced Television Systems Committee)

http://www.atsc.org/

MTM400 MPEG Transport Stream Monitor Programmer Manual

iii

Preface

H ISDB/ARIB standards (Association of Radio Industries and Businesses)

http://www.arib.or.jp/english/

H SCTE Society of Cable Television Engineers

http://www.scte.org/

iv

MTM400 MPEG Transport Stream Monitor Programmer Manual

Introduction

Introduction

SNMP and MIBs

This document specifies the MTM400 MPEG Transport Stream Monitor remote
control and status monitoring interfaces available to a Management application.
Two interfaces are provided; SNMP and an HTTP Web-based interface.

NOTE. The MTM400 Programmer Interface MIB file accompanying this
document contains entries not described in the manual. These entries should not
be used.

This document should be read in conjunction with the MTM400 User Manual.
The reader must be thoroughly familiar with the operation of the MTM400 and
have detailed knowledge of SNMP and HTTP.

Do not use multiple variable binding SET requests. Only single variable binding
SET requests should be used.

This document specifies the facilities provided by the MTM400 Simple Network
Management Protocol (SNMP) agent, which allows various parameters within
the MTM400 monitor to be viewed and set. This will allow you to develop
management applications that can control the MTM400 units across a network
using SNMP.

The MTM400 SNMP agent has been implemented as an extensible agent under
Nucleus, and as such conforms to SNMP v1. Nucleus SNMP is an embedded
implementation of SNMP.

The Simple Network Management Protocol (SNMP) is an Internet standard
protocol for remote management of entities on a network. It is defined in Internet
documents STD-15 (RFC1157) and STD-16 (RFC1155 and RFC1212). STD-15
defines the protocol operations; STD-16 defines the way in which information is
structured under SNMP (SMI - Structure of Management Information).

SNMP defines a way of structuring information in a hierarchy of objects
supporting both single objects and tables of objects, and making the information
available through a network protocol.

Each object can be one of four types, namely:

H Integer. Represents numerical values.

H OctetString. Represents byte streams.

MTM400 MPEG Transport Stream Monitor Programmer Manual

1−1

Introduction

H DisplayString. Represents printable strings.

H Object Identifier (OID). References other objects within SNMP.

There are essentially three types of operations that can be performed on each
object:

H Get. Retrieves the value of an object.

H GetNext. Retrieves the value of an object along with the OID of the next

object available.

H Set. Sets the value of an object.

The complete set of objects accessible through an SNMP agent is called the
Management Information Base (MIB). The MIB is a tree structure with MIB
objects at the leaves of the tree. Every branch and leaf of the tree is numbered
according to a scheme ultimately under the administration of either ISO or the
CCITT (or the ITU-T as they are now called). (The root of the tree has three
branches: branch 0 is owned by the CCITT, 1 by ISO and 2 is jointly owned by
ISO and the CCITT.) These organizations have delegated various branches of
this tree to other authorities. Everything of interest to SNMP is under the control
of the IANA (the Internet Assigned Numbers Authority), which owns the branch
named:

iso (1).org (3).dod (6).internet (1)

The strings of numbers identifying parts of the MIB tree are called Object
Identifiers (OIDs).

The Internet standard management sub-trees are all under

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

However the IANA also allocates numbers to other organizations. Companies
can obtain their own sub-trees under

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

This entire tree structure is called the MIB. A MIB module is a set of sub-sec­tions of this tree that form some coherent function or set of functions, usually
described in a single document and qualified with some other title, such as
RMON MIB.

NOTE. A MIB module is sometimes referred to as the MIB.

1−2

MTM400 MPEG Transport Stream Monitor Programmer Manual

A MIB Module is defined in a text file using ASN.1 (Abstract Syntax Notation
One). This is a language defined by OSI for describing arbitrary data structures.

For more detailed explanations of network management using SNMP, you can
refer to The Simple Book (Marshall T. Rose, Prentice Hall, ISBN
0-13-451659-1).

MTM400 SNMP Community

SNMP provides a simple mechanism for security, there are community strings to
govern read and write to the MIB; these function as passwords.

For the MTM400 the community string “public” is used for read and write
access.

MTM400 SNMP Traps

Introduction

SNMP provides a mechanism for a device to send a notification message to the
management system when an event occurs. This means that the management
system can poll the device less often and so reduce network traffic.

The important point to note here is that it does not mean that the management
system can stop polling the device. Traps are sent using the UDP network
protocol. This mechanism does not guarantee arrival of all packets; a trap
message can be lost.

Trap messages may be lost not only in the UDP transport layer, but inside the
device. The MTM400 takes steps to avoid flooding the network with traps; this
means some traps are discarded when there are a burst of error in a stream. A
trap should be thought of as a prompt to visit the device to discover status rather
than a mechanism to completely know the status.

You should not use trap messages alone to continually monitor the status of the
device. This will fail because although traps are issued when the device detects
an error and when the error condition clears, they are not issued when tests move
from an error state to not applicable, such as when the stream presentation is
changed.

To prevent a flood of trap messages on a network, the MTM400 has a throttling
mechanism. A flood of trap messages is to be avoided since this could hamper
the operator’s ability to use the network to understand and contain an error
condition. In the extreme case a flood of trap messages could cause the manage­ment system to fail.

On the MTM400, a maximum number of trap messages per second is defined.
This is in total, so, if a limit of 10 per second is set, this will yield 5 per second
if two managements are subscribed. Internally, there is a buffer for 100 traps so a

MTM400 MPEG Transport Stream Monitor Programmer Manual

1−3

Introduction

MTM400 Web Server

short burst can be accommodated without loosing messages. If the buffer
overflows, trap messages are discarded.

The implication of the preceding information is that network bandwidth, or trap
handling capability, is treated as a limited resource. To avoid wasting this
resource, steps are taken to ensure that any management system subscribed for
trap messages still requires these messages. So when a management system
subscribes to trap messages, this is only for a few minutes. The management
system must repeatedly resubscribe in order to continue to receive trap messages.
This provides protection in the case of a management system exiting improperly.

The MTM400 has a Web server interface on HTTP port 80. A number of URL’s
are supported and are used primarily for transferring bulk data, unsuited to
SNMP, to and from the MTM400.

A full list of supported Web server URLs is given in this manual (see Web Server
URLs section).

1−4

MTM400 MPEG Transport Stream Monitor Programmer Manual

MTM400 MIB

MTM400 MIB

MIB Types

Tektronix has been assigned the following root OID:

iso.org.dod.internet.private.enterprises.128

Under this OID Tektronix can define its own MIB for various products.

The MIB subtree for MTM400 is under the following OID:

iso.org.dod.internet.private.enterprises.tek(128).tvt(5).tvtproducts(1).

The tree is specified in the two ASN.1 text files: ADSYS.MIB defines the
structure of device specific elements and ADMPEG.MIB defines the structure of
the MPEG Interface specific elements.

The supplied MIB includes some items that do not apply to the MTM400,
because the MIB is common to several products.

The MTM400 MIB defines the following extra MIB types.

EVID

EvState

This type defines events that can occur within the MTM400. It is essentially a
WORD, where values 0x1xxx represent events that are generated by the
MTM400 box such as Clock and Battery errors. Values over and including
0x2000 represent events that are generated by specific MPEG Interfaces such as
Sync Lock or Continuity errors. The full list of these events can be found in the
MTM400 Technical Reference (Tektronix part number: 071-1560-xx).

This type represents the state of a given event which can be Green, Yellow or
Red. Green indicates that there is no error, yellow indicates that there has been
an error since this event was last reset, and red indicates that there is a persistent
error.

This is essentially a WORD. Green is defined as 0x1000, yellow as 0x2000 and
red as 0x3xxx, where
that the state is unknown (for example, during the settling time of a test), and
0x4000 means that the event is disabled. Two final values are also possible:
0x5000 is the maintenance state and 0x6000 is N/A (for example, SFN testing
when there is no SFN data).

xxx is the specific error number. A value of 0x0000 means

MTM400 MPEG Transport Stream Monitor Programmer Manual

2−1

MTM400 MIB

ÏÏ

ÏÏ

AlmValue

Simple Boolean

Log Index

Time Stamp

This specifies which alarms are activated when an event occurs. It is an integer
type and can take combinations of the following values:

0x00000001 = Audible Alarm
0x00000100, 0x00000200, .. , 0x00001000= Relay1, Relay2, .., Relay 5
0x00010000, 0x00020000, .. , 0x00040000= TTL1, TTL2, TTL3
0x00100000, 0x00200000 = Send Trap on; Raise, Clear

This enumerated type is used to represent a Boolean value.

This type represents an integer index into a log.

Time stamps are used in several MIB items to specify the time of events. Each
time stamp is stored as an eight-byte structure, which consists of an 11-bit signed
integer representing the UTC offset and a 53 bit signed integer representing the
UTC time. The UTC offset is the number of minutes that must be added to UTC
time to obtain the local time on the MTM400 unit. The UTC time is the number
of microseconds since midnight Greenwich Mean Time (GMT) January 1, 1970.

Figure 2−1 shows that the timestamp is actually stored with the UTC offset,
followed by the UTC Time in MSB format. However, the bytes are reversed
when the timestamp is presented as part of an Octet String through SNMP so
that the numbers are in LSB format. Care should be taken with byte 6 because it
contains both the UTC offset and UTC time.

UTC Offset

11 bits

Stored Format

SNMP Format

MSB LSB

76543210

01234567

LSB

Figure 2−1: Time stamp storage

UTC Time

53 bits

MSB

2−2

MTM400 MPEG Transport Stream Monitor Programmer Manual

Accessing MIB Objects

MTM400 MIB

This section describes how to access objects within the MTM400 MIB.

SNMP Access

Operations

Single Leaf Objects

Tables

The MTM400 SNMP agent fully supports the standard SNMP GetRequest,
GetNextRequest, and SetRequest PDU operations. This document specifies the
access permissions for each object within the MTM400 MIB using the following
conventions:

H ‘Get’ indicates that the GetRequest and GetNextRequest can be used.

H ‘Set’ indicates that the SetRequest can be used.

Single Leaf Objects are single-value elements whose values can be accessed
using the standard SNMP access operations by appending ‘0’ to the appropriate
OID specified in the MIB. For example, in order to access the program name
within the System Information Group, use the following OID:

‘…adsysProductName.0’.

The MTM400 MIB defines a number of tables. Tables normally contain objects
that can have multiple values, each referenced by appending the required row
number to the OID of the object specified in the MIB. Management applications
typically access values of objects within tables by first performing a GetNextRe­quest-PDU on the OID object that will return the OID of the first value.
Subsequent calls to the GetNextRequest operation will obtain the values for this
object within the table. When the operation returns the ‘No Such Name’ error,
this indicates that the last value has been reached.

Some tables within the MTM400 MIB are indexed by two or more values, so
accessing object values becomes a little more complex. For example, the Event
State Table is indexed by stream number and event id, so in order to reference a
specific value, the OID should be created by appending the stream number and
the event id to the OID specified for this object in the MIB. Consequently, in
order to access the EventState for an event on a specific stream, use the
following OID:

‘…mivevtEventState.<interface_no>.<eventid>’.

The GetNextRequest-PDU operation will return the OID of the next eventid,
until they have all been exhausted for that stream. At this point it will return the
next interface_no, and the first event_id on that interface (or ‘No Such Error’ if
no more interfaces exist to indicate that the end of the table has been reached).

MTM400 MPEG Transport Stream Monitor Programmer Manual

2−3

MTM400 MIB

When a table is defined within the MIB, each table leaf object is represented by
the following OID:

‘…<table_oid>.<table_entry_oid>.<table_leaf_object_oid>’.

The ‘table_entry_oid’s within the MTM400 MIB are always given the value 1,
and are not shown on the structure charts within this document because it would
complicate the diagrams. However, it should be recognized that these must be
included in the OIDs when referencing objects.

2−4

MTM400 MPEG Transport Stream Monitor Programmer Manual

MIB Group Overview

MIB Group Overview

The following sections define the groups of the MIB modules that make up the
MTM400 SNMP interface. There is a split between MPEG-related and non­MPEG-related objects, and so the groups have been separated into two MIB
modules. The System MIB module contains all non-MPEG-specific groups;
MPEG-specific groups are found in the MPEG MIB module. Figures 3−1 to 3−3
show the overall structure of the MTM400 MIB subtree.

Figure 3−1: Overall MIB structure

MTM400 MPEG Transport Stream Monitor Programmer Manual

3−1

MIB Group Overview

The system OID is:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).tek(128).tvt(5).tvtpr
oducts(1).adSystem(16)

Figure 3−2: System structure

For a complete description of the system structure, refer to the System Structure
section of this manual.

The MPEG OID is:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).tek(128).tvt(5).tvtpr
oducts(1).adMpeg(17)

Figure 3−3: MPEG structure

For a complete description of the MPEG structure, refer to the MPEG Structure
section of this manual.

3−2

MTM400 MPEG Transport Stream Monitor Programmer Manual

System Structure

System Structure

Figure 4−1: System structure

System Information Group

Figure 4−2 shows the structure of the System Information Group, which provides
access to attributes of the most general nature, such as the product name and the
installed software .

Figure 4−2: System information group structure

MTM400 MPEG Transport Stream Monitor Programmer Manual

4−1

System Structure

Product Name

DVB Region

For the MTM400 this is fixed as “MTM400”. This may be used to positively
identify an MTM400.

The format of this item is defined as:

Name: adsysProductName
OID: 1.3.6.1.4.1.128.5.1.16.1.1
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).

tek(128).tvt(5).tvtproducts(1).adSystem(16).adsysInfo(1).adsysProductNa

me(1)
Module: AD-SYSTEM-MIB
Parent: adsysInfo
Numerical syntax: Octets
Base syntax: OCTET STRING
Composed syntax: OCTET STRING
Status: mandatory
Max access: read-only
Description: A textual name unique to this product type

Obsolete - see MPEG Structure, MPEG Interfaces Table.

Screen Saver Timeout

N/A

4−2

MTM400 MPEG Transport Stream Monitor Programmer Manual

System Structure

Software Components

Global Maintenance Mode

A list of software components and performance metrics is present on this entity.

The format of this item is defined as:

Variable Type Use Access

aswIndex(1) Integer Table index. Get

aswName(2) Octet string Component name. Get

aswVersion(3) Octet string Component version. Get

The format of this item is defined as:

Name: adsysGlobalMaintenanceMode
OID: 1.3.6.1.4.1.128.5.1.16.1.5
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).

tek(128).tvt(5).tvtproducts(1).adSystem(16).adsysInfo(1).adsysGlobalMai

ntenanceMode(5)
Module: AD-SYSTEM-MIB
Parent: adsysInfo
Numerical syntax: Integer (32 bit)
Base syntax: INTEGER
Composed syntax: SimpleBoolean
Status: mandatory
Max access: read-write
Description: Setting this variable to true sets the whole box into global maintenance

mode. In this state, processing of events continues, but no alarms are

raised.

Standard

Config File Index

Delete Config File

Obsolete

N/A

N/A

MTM400 MPEG Transport Stream Monitor Programmer Manual

4−3

System Structure

Download Config File

Box Name

UTC Time

N/A

This value contains a configurable name for the box.

Name: adsysBoxName
OID: 1.3.6.1.4.1.128.5.1.16.1.11
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).

tek(128).tvt(5).tvtproducts(1).adSystem(16).adsysInfo(1).adsysBoxName(

11)
Module: AD-SYSTEM-MIB
Parent: adsysInfo
Numerical syntax: Octets
Base syntax: OCTET STRING
Composed syntax: OCTET STRING
Status: mandatory
Max access: read-write
Description: The name of the box

The UTC time of the box; that is, the number of seconds since midnight 1st
January 1970.

UTC Offset

Reset

Variable Type Use Access

adsysUTCTime (12) Integer The UTC time of the box. Get/Set

Number of minutes to add to UTC time to get to local time frame - this may be
negative.

Variable Type Use Access

adsysUTCOffset (13) Integer The UTC offset of the box. Get/Set

Setting this value to a hex value DE5B12A resets the device..

Variable Type Use Access

adsysReset (14) Integer Device reset.

Get has no meaning in this
context.

Get/Set

4−4

MTM400 MPEG Transport Stream Monitor Programmer Manual