iPlex Version 5.0 SNMP Guide

REFERENCE GUIDE

Network Management & Monitoring iPlex

Software Version 5.0

iPlex

112-0116-02 Rev A

www.tandbergtv.com

May, 2009

Published By TANDBERG®

455 DeGuigne DriveSunnyvale, CA 94085-3890Copyright © 1998-2007 by TANDBERG Television.All rights reserved. No part of the contents of this book may be reproduced or transmitted in anyform or by any means without the written permission of the publisher.

Contributors Technical Publications: Lena JacobsonTANDBERG Television Engineering Department

RestrictedRights

This document contains proprietary and confidential information of TANDBERG Television. Thecontents of this document may not be disclosed to third parties, copied or duplicated in any form, in wholeor in part, without the prior written permission of TANDBERG Television.Use, duplication, or disclosure of the technical data contained in this document is subject to restrictions as setforth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement.Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer isTANDBERG Television, 455 DeGuigne Drive, Sunnyvale, CA 94085-3890, USA. TANDBERG is aregistered trademark of TANDBERG Television. All other names are trademarks of their respectiveowners. TANDBERG Television owns the following patents: U.S. Patent No. 6351474, 6351471,6292490, 6246701, 6195368, 6148082, 6111896, 6064676 and has additional U.S. patents pending.

GoAheadSoftwareLicence

Copyright © 2001 GoAhead Software, Inc. All Rights Reserved. Unless GoAhead otherwiseinstructs, the year 2001 is to be replaced with the year during which the release of the Original Codecontaining the notice is issued by GoAhead. If this year is not supplied with Documentation,GoAhead will supply it upon request.

Dolby DigitalTrademark

License

Dolby Laboratories encourages use of the Dolby Digital trademark to identify soundtracks that areencoded in Dolby Digital. This is an effective way to inform listeners of the soundtrack format, andthe use of a standard logo promotes easy recognition in the market place. However, like anytrademark, the Dolby Digital logo may not be used without permission. Dolby Laboratoriestherefore provides a standard trademark license agreement for companies who wish to use Dolbytrademarks. This agreement should be signed by the company that owns the program material beingproduced. Recording studios or production facilities which provide audio production or encodingservices for outside clients generally do not require a trademark license. If you would like moreinformation on obtaining a Dolby trademark license, please contact Dolby Laboratories LicensingCorporation. Information on trademark licensing plus instructions for using the Dolby Digitaltrademark and marking audio formats can also be found on-line at http://www.dolby.com.Dolby Laboratories Licensing Corporation, 100 Potrero Ave., San Francisco, CA 94520 USA.Phone: 415-558-0200, Fax: 415-863-1373, E-mail: [email protected], http://www.dolby.com

TechnicalSupport

For technical support, contact TANDBERG Television Customer Support through the World Wide Web (www.tandbergtv.com/services/skysupport_request.asp), via e-mail ([email protected]) or the Hot Line 1-877-475-9787.Document Number: 112-0116-02 Rev A

2

AgencyCompliance

and Cautions

Safety: UL 60950 Third Edition, CSA-C22.2 No. 950-95, EN60950, IEC 950, CB Certificate, AS/NZ 3260,TS 001, Laser Safety: 21CRF1040Emissions: FCC Part 15 Class A, CISPR 22 Class A, EN55022 Class A, AS/NZ 3548Immunity: EN61000-4-2, EN61000-4-3, EN61000-4-4, EN61000-4-5, EN61000-4-6, EN61000-4-11,EN61000-3-2, EN61000-3-3, EN300-386-2Telcordia: GR-63-CORE, GR-1089-CORE, SR-3580 NEBS Level 3ETSI: EN300-019-1-1, EN300-019-1-2, EN300-019-1-3, EN300-132, EN300-386-2

FCC Class ACompliance

TANDBERG Television iPlex equipment has been tested and found to comply with the limits for aClass A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to providereasonable protection against harmful interference when the equipment is operated in a commercialenvironment. This equipment generates, uses and can radiate radio frequency energy and, if notinstalled and used in accordance with the instruction manual, may cause harmful interference toradio communications. Operation of this equipment in a residential area is likely to cause harmfulinterference, in which case the user will be required to correct the interference at personal expense.

ImportantSafety

Information!

Please note the following:1 The TANDBERG Television iPlex is intended for indoor use only.2 In case of emergency, disconnect the power cords.3 If power cords are not provided:

- In the United States, use standard computer power cords (as specified below).- In Europe, for 230 volt operation, use a cord set marked “HAR” and consisting of a min 3 coreH05VVF3G075 cord that has a minimum 0.75 square mm diameter conductors, provided with an IEC320 receptacle and a male plug for the country of installation, rated 6A, 250V.

4 Do not block the equipment vents.

Read the following safety information thoroughly before installing this TANDBERG Television product. Failure to follow this safety information may lead to personal injury or damage to the equipment.

Power Supply

• This unit must be grounded.• The unit must be connected to a grounded outlet to comply with product safety standards.• Do not connect the power supply unit to an AC outlet without a ground connection.• All power cords must be disconnected before servicing.Power Cords

The plug on the power supply cords are considered to be the equipment disconnect device and mustbe approved for the country where it is used.For USA and Canada:

• The cord set must be UL-approved and CSA-certified.• The attachment plug must be an earth-grounding type with a NEMA 5-15P (15A 125V) plug

and a EN60320/IEC320 receptacle.

3

SystemSpecifications

• Dimensions (H x W x D): 23.50 X 17.40 X 1.75 in (59.69 x 44.20 x 4.45 cm)• Rack Mount: 1 Rack Unit: Standard 19 inch EIA rack• Weight: 24.5 lbs (11.14 kg) fully-configured• Shipping Weight: 39 lbs. (17.69 kg)• Airflow: 86 CFM normal operation 126 CFM maximum• Operating Temperature Range: 0° C to +40° C (+32° F to +104° F)• Short-term Operating Temperature Range: -5° C to +55° C (+23° F to 131° F)• Non-operating Temperature Range: -40° C to +70° C (-40° F to +158° F)• Operating Humidity: 7% to 95% Non-condensing• Non-Operating Humidity: 5% to 95% Non-condensing• Operating Altitude: to 13,123 ft (4000 meters)• Input Power Requirement: 100-240 V AC 47/63 Hz @ 3/6 Amps

4

ContentsCover, Notices, and Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1: Introducing TANDBERG Television iPlex . . . . . . . . . . . . . . . . . . . . . 9

Introduction to the Network Management & Monitoring Guide . . . . . . 10Other iPlex Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Contacting TANDBERG Television Customer Support . . . . . . . . . . . . . 11Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Support Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Network Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 13

Introduction to SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15SNMP-Related Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Network Management Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . 15

SNMP Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Conceptual Row Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Selecting an Instance-Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Creating the Conceptual Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Creating and Activating the Conceptual Row . . . . . . . . . . . . . . . . . . . . . . . . . 18

Conceptual Row Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SNMPv3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19SNMPv3 Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19SNMPv3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20SNMPv3 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SNMPv3 Configuration and Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SNMP MIB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Compiling MIBs in Network Management Applications . . . . . . . . . . . . . . . . . . . . . . 22

ROOT MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22MIBs supported on iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

iPlex Enterprise MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Mediaplex ASIIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Mediaplex ASIOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Mediaplex Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Mediaplex VLAN Management MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5

iPlex Network Management & Monitoring Reference Guide

Mediaplex Software MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Mediaplex Program MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Mediaplex Element MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Mediaplex UDPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Mediaplex Program Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mediaplex Stream Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mediaplex Notification MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mediaplex SME MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Mediaplex IP Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mediaplex TS Stats MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mediaplex RTPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mediaplex RTPOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mediaplex ATMIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Mediaplex ATMOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mediaplex Redundancy MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mediaplex Sensors MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mediaplex Chassis MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mediaplex SMD MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Mediaplex ATM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mediaplex FILEIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mediaplex GE MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mediaplex Alarms MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mediaplex Xrater MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Mediaplex SCM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Mediaplex Encoder Audio MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Mediaplex ATM Routes MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Mediaplex MPE Routes MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Mediaplex TCPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex Backhaul MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex XrtrIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex XrtrOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex Descriptors MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex Advanced Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Mediaplex Ports MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Spanning Tree MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Notificationv2 MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Log MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Config File Mgmt MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Notification Log MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36SNMP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36License MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36FileE Management MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Media Processor MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Security MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36xCoderIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37xCoderOut Mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37AVC Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37AVC xCoder In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37AVC xCoder Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6


Introduction to HP OpenView Integration . . . . . . . . . . . . . . . . . . . . . . . 38Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39TANDBERG Television HP OpenView Plug-in Components . . . . . . . . . 39Monitoring iPlex from HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Monitoring a Specific iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Standard Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Opening the Web GUI for HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Launching an SNMP Browser for a Specific iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Obtaining a List of iPlex Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Network Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Graphs and Historical Data Gathering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Appendix A: Monitoring iPlex Using SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

IP Address Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Basic Status Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Advanced Status Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Detecting Redundancy Flips between SCM Blades . . . . . . . . . . . . . . . . . . . 53Monitoring Blade Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Active Alarm Table Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

ASI Rx Sync Loss and Regained Notifications . . . . . . . . . . . . . . . . . . . . . . . 58ATM Link Up and Down Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Video Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Encoder Start and Stop Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Buffering Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Audio Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Encoder Sync Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65MCM CPU Temperature Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Mediaplex and iPlex Notification Version 2 (Trap) Definition and Usage (Release 3.0 or Later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7


OK and Failure Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Up and Down Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Inserted and Removed Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Video Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Start and Stop Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Sync Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Buffering Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Audio Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Link Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87CPU Temperature Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89CPU Utilization Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Memory Utilization Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Redundancy Flip Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Encoder Video Data Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ASIIn and ASIOut Video Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Monitoring Other Ports Video Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Monitoring Using the PORTS MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Other Monitoring Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8

Introducing TANDBERGTelevision iPlex

Chapter 1

9


Introduction to the Network Management & Monitoring Guide

Use this guide to help you understand features and tasks that can be performed with iPlex using SNMP.

Topics discussed in this guide include:

• How to contact technical support.

• SNMP formats

• SNMP messages

• SNMP conceptual row creation

• MIBs

• HP Openview information.

Other iPlex GuidesIn addition to this guide, you can also refer to the following guides:

• Installation & Hardware Specifications Guide, for information on

■ Hardware specifications.

■ Hardware installation and configuration.

■ Software installation and configuration.

• Command Line Interface Reference Guide, for information on

■ CLI basics, conventions, and connection method.

■ Command definitions.

■ Show commands and Config commands.

• Web Interface User Guide, for information on

■ Hardware specifications.

■ Basic concepts.

■ Configuration scenarios.

■ Web interface features and functions.

■ Port configuration and statistics.

■ Redundancy.

10


Contacting TANDBERG Television Customer Support

For information on TANDBERG Television support hours and how to contact TANDBERG Television support, please refer to the literature that came with your support contract. To contact TANDBERG Television about the purchase a sup-port contract, please refer to the contact information below.

Basic support is available to TANDBERG Television customers either by e-mail or on the Web (refer to contact information, below). Please send a detailed mes-sage and you will be contacted during regular business hours (see the “Support Check List”).

Contact Information

Support Check ListWhen contacting Customer Support, please provide the following infor-mation:• Your name, company name, e-mail address, and phone number.

• TANDBERG Television product name and version number.

• A complete network diagram with IP addresses.

• The name and version of the network software.

• If set-top boxes are involved, please brand and software version.

• Syslog entries for the period over which the problem occurred.

• iPlex Tech Support Dump.

• A full description of the problem

■ Did this problem occur just after making a network change?

■ Did this problem occur just after adding or removing hardware or software?

E-mail: [email protected]

Web: http://www.tandbergtv.com/contactingsupport.ink

11


12

Network Management andMonitoring

Chapter 2

13


OverviewTANDBERG Television iPlex video services router provides three ways for mon-itoring and management. These include the web-based graphical user interface, Command Line Interface (CLI) and SNMP (SNMP v1, v2c, and v3 supported).

The web interface provides the means for device configuration and monitoring. It is an element management application which provides the capability to configure a single iPlex. The web server is run on the Switch Controller Module (SCM) of the iPlex and therefore all that is required to access this interface is any PC with a stan-dard web browser. However, the web interface cannot manage or configure multi-ple iPlex devices concurrently.

In order to monitor and manage multiple iPlex video service routers from a central location, TANDBERG Television recommends the use of the SNMP. TAND-BERG Television provides the necessary software for integration with HP Open-View Network Node Manager monitoring system. The integration with HP OpenView is discussed in detail.

The first part of this chapter is an introduction to SNMP, followed by SNMP MIB description. The second part of the chapter is an introduction to HP OpenView Integration.

14


Introduction to SNMPSimple Network Management Protocol (SNMP) is a widely used network moni-toring and control protocol that passed data from SNMP agents to the manage-ment workstation used to oversee the network. SNMP agents are hardware or software processes reporting activity in each network device, such as a hub, router, or bridge. The agents return information contained in a Management Information Base (MIB), which is a data structure that defines what is obtainable from the device and what can be controlled.

SNMP is a set of standards for network management that was adopted as a stan-dard for TCP/IP-based internets in 1989. An upgrade to SNMP, known as SNMP version 2 (SNMPv2), was issued in 1995. Then, in 1998, SNMP version 3 was issued. This last set of standards defines a security capability for SNMP along with an architecture for future enhancements. SNMPv3 works in conjunction with the functionality provided in SNMPv2 and SNMPv1.

SNMP-Related SpecificationsRFC 1155 May 1990–Structure and Identification of Management Information for TCP/IP-based Internets

RFC 1155 May 1990 – A Simple Network Management Protocol (SNMP)

RFC 1155 May 1990 – Concise MIB Definitions

RFC 1155 May 1990 – Management Information Base for Network Managementof TCP/IP-based Internets: MIB-II

RFC 1155 May 1990 – Definition of Managed Objects for the Ethernet-like Inter-face Types

Network Management Protocol ArchitectureThe design of SNMP is for an application-level protocol that is part of the TCP/IP suite of protocols. It is meant to operate over the User Datagram Protocol (UDP). It is also meant to be a stand-alone management station, where a manager process controls access to a central MIB and provides an interface to the network manager. The manager process uses SNMP on top of UDP, IP, and the relevant protocols, such as Ethernet, FDDI, and X.25.

From a management station, three types of SNMP messages are issued on behalf of a management application: GetRequest, GetNextRequest, and SetRequest. The first two are variations of the get function. However, all three messages are acknowl-edged by the agent as a GetResponse message that is passed to the management application.

15


The only operations supported in SNMP are the alteration and inspection of vari-ables. Three general operations may be performed on scalar objects:

• Get – A management station retrieves a scalar object value from a managedstation.

• Set – A management station updates a scalar object value in a managed station.

• Trap – A managed station sends an unsolicited scalar object value to a management station.

SNMP Formats There is an exchange of information in SNMP between a management station and an agent in the form of a message. Each message includes an SNMP version num-ber, a community name used for the exchange, and one of five types of Protocol Data Units (PDU). The SNMP format is shown in the following diagram.

Transmission ofan SNMPMessage

An SNMP entity performs the following actions to transmit one of the five PDU types to another SNMP entity:

1 A PDU uses the ASN.1 structure in RFC 1157.

2 It then passes to an authentication service, along with the source anddestination address and a community name. It then performs any encryptionor authentication code required for this exchange, and returns a result.

3 The protocol entity then constructs a message that consists of a version field,the community name, and the result passed from the authentication service.

4 This new object passes to the transport service, after it receives basicencoding.

NOTEIn practice, authentication is rarely used.

16


SNMP Messages

Conceptual RowCreation

SNMP views management information as variables and their values. SNMP opera-tions retrieve or modify the value of objects. A class or type of management infor-mation is called an object or an object type. A specific instance from a class of management information is called an SNMP variable or an object of instance. The OBJECT-TYPE construct is used in MIB modules. The structure of management information requires that columnar objects be organized in conceptual tables.

When creating a conceptual row, there are four possible potential interactions: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and making the conceptual row available for use by the managed device.

Field Descriptionversion SNMP version (RFC 1157 is version 1.)community An SNMP agent paired with some arbitary set of SNMP application enti-

ties.

NOTEThe community name acts as a password to authenticate theSNMP message.

request-id Provides a unique ID to distinguish between outstanding requests.error-status Indicates an exception occurred while processing a request. Values are as

follows: noError (0), tooBig (1), noSuchName (2), badValue (3), readOnly (4), genErr (5)

error-index When error-status is nonzero, it may provide what variable caused an exception.

NOTEA variable is an instance of a managed object.

variablebindings A list of variable names and corresponding values.

NOTEIn some cases, such as GetRequest PDU, the values are null.

enterprise A type of object generating trap; based on sysObjectID.agent-addr The address of object generating trap.generic-trap A generic trap type. Values are as follows: coldStart (0), warmStart (1),

linkDown (2), linkUp (3), authentication-Failure (4), egpNeighborLoss (5), enterprise-Specific (6).

specific-trap A specific trap code.time-stamp Time elapsed between the last (re)initialization of the network entity and

the generation of the trap; contains the value of sysUpTime.

17


Selecting anInstance-Identifier

The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, a management station selects the identifier according to significant semantics, such as the destination address of a route.

The MIB module that defines the conceptual row provides one or more objects that provide assistance in determining an unused instant-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an inte-ger-valued SYNTAX clause might be defined for such a purpose, allowing a man-agement station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, adjacent retrievals of the object should be different.

Creating theConceptual Row

Once an unused instance-identifier had been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions.

Creating andActivating the

Conceptual Row

The management station must first determine the column requirements; that is, it must determine those column values for which it must or must not provide values. Depending on the complexity of the table and the management station’s knowl-edge of the agent’s capabilities, this determination can be made locally by the man-agement station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create.

Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the rowstatus column “createAndGo.”

When the agent processes the set operation, it verifies that it has sufficient infor-mation to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation that creates the conceptual row, and the implementation-specific defaults supplied by the agent. If there is sufficient information available, then the conceptual row is created, a “noError” response is returned, the status column is set to “active,” and no further interactions are necessary. If there is insufficient information, then the conceptual row is not created, and the set opera-tion fails with an error of “inconsistentValue.”

Conceptual RowDeletion

For deletion of conceptual rows, a management protocol set operation is issued that sets the instance of the status column to “destroy.” This request may be made regardless of the current value of the status column. If the operation succeeds, then all instances associated with the conceptual row are immediately removed.

18


SNMPv3

SNMPv3 Brief Overview

TIP SNMP v3 on iPlex supports DESencryption. See more on this:

SNMPv3 Authentication on page 19

A weak point of previous SNMP versions has been the lack of a solid, agreed upon, security scheme. Both SNMPv1 and SNMPv2c use only a community string as the security mechanism. A community string is an ASCII password which may be easily discovered.

SNMPv3 adds a security scheme which is based on the concept of multiple users. Each user has an associated ASCII user name, possibly an ASCII authentication password, and possibly an ASCII privacy password.

The authorization and privacy passwords are represented in human-readable form simply to make life easier for users. These passwords are converted to “secret key” values. Secret keys are long random strings of bytes that are used to generate secu-rity information for an SNMP message. This security information is then stored in the header of the SNMP message.

The following sections briefly explain how secret keys are used to generate security information.

SNMPv3Authentication

Message authentication refers to verifying who the SNMP message came from as well as whether the message has been modified enroute.

A Network Management System (NMS) converts the user’s authentication pass-word to a secret key. This secret key is used to generate a “fingerprint” of the SNMP message. This fingerprint is stored in the SNMP message header.

When the SNMP agent receives the SNMP message, it also calculates the finger-print using the same secret key. If the fingerprints match, the message has been authenticated.

The fingerprint is generated by using one of the following authentication algo-rithms: Message Digest 5 (MD5) or Secure Hash Algorithm (SHA-1). Both of these algorithms are described in detail in RFC 2574.

SNMPv3 Privacy Message privacy refers to the encryption of the data portion of the SNMP mes-sage. The encryption algorithm used is the CBC-DES Symmetric Encryption Pro-tocol.

An NMS converts the user’s privacy password to a secret key. This secret key is used to generate an initialization vector which is used to encrypt/decrypt the mes-sage data. This vector is stored in the SNMP message header.

When the SNMP agent receives the SNMP message, it uses this initialization vec-tor to decrypt the data.

Much more detail on DES encryption is provided in RFC 2574.

19


SNMPv3Configuration

Once SNMPv3 is selected and applied via config file or web interface, the SNMP agent will set up 3 default SNMPv3 users. See the following sections (SNMPv3 Users on page 20 and SNMPv3 Views on page 21) for more details.

SNMPv3 Users The usmUserTable (defined in RFC 2574) contains secret keys and other security information for each user name. When SNMPv3 is enabled, the SNMP agent adds 3 default users to the usmUserTable. When SNMPv1/v2c is enabled, the SNMP agent empties out the usmUserTable. When the usmUserTable is empty, any SNMPv3 message received from an NMS is rejected.

The “security level” of a user refers to the authentication and privacy level for the user. A user may have one of the following security levels:

• No authentication, no privacy

• Authentication with no privacy

• Authentication with privacy

The security level for each default user which the SNMP agent adds to the usmU-serTable is defined as follows:

The first default user will have a security level of MD5 authentication and DES privacy. The second default user will have a security level of SHA-1 authentication and DES privacy. The third default user will have a security level of MD5 authen-tication and no privacy.

It is important that the user name/password information for the default users be kept confidential between the NMS and the SNMP agent. If user names/pass-words become known to another NMS, another NMS may send SNMPv3 mes-sages to the SNMP agent which could change the configuration of the iPlex.

Once an NMS knows user name/password information, it can use the authentica-tion password and privacy password to generate the appropriate security informa-tion for an SNMPv3 message. It can then send SNMPv3 messages to the SNMP agent. The SNMP agent will use the secret keys stored for the user to authenti-cate/decrypt the messages.

If the SNMP agent receives an SNMPv3 message from an unknown user, the mes-sage is rejected. SNMPv1 and SNMPv2c messages will also be rejected. The only messages the SNMP agent will accept are ones which contain the appropriate security information pertaining to one of the default users.

An NMS may change the contents of the usmUserTable by sending an SNMPv3 message to the SNMP agent. For example, the NMS may delete a default user from the usmUserTable, it may change the password of an existing user, it may change the security level of an existing user, and so forth.

User Authentication Type Privacy Type

Default User 1 MD5 DES

Default User 2 SHA-1 DES

Default User 3 MD5 None

20


SNMPv3 Views The vacmSecurityToGroupTable, the vacmAccessTable, and the vacm-ViewTreeTable provide access control to the MIB. Each of these tables is described in RFC 2575.

It is possible to set up these “view tables” so that a specific user only has read or write access to a subset of the MIB.

When the SNMP agent adds the 3 default users to the usmUserTable, it also sets up the view tables so that each of these users has read and write access to all objects in the MIB.

SNMPv3Configurationand Example

To create SNMPv3 using the Web GUI (see Chapter 3: Using the Web GUI), the user must select: Configuration>SCM>SNMP, then create a user, assign a password, select the authentication protocol (SHA or MD5), and select a security level if you want encrypted messages.

A management application can send SNMPv3 request as shown below. The snmp-walk tool used is from the NETSNMP toolkit.

• snmpwalk -v 3 -u user1 -l authNoPriv -a MD5 -A skystream

192.168.58.128 vlanMgmtInfoTable

or

• snmpwalk -v 3 -u user2 -l authNoPriv -a MD5 -A skyStream

192.168.58.128 vlanMgmtInfoTable

ExampleIf there is one VLAN with IP address 172.30.1.1, the output would be as follows:

TandbergMediaplexMibObjects.TandbergMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanIpAddress.0 = IpAddress: 172.30.1.1

skyStreamMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanSubnetMask.0 =255.255.255.0

skyStreamMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe1.0 = 0 (no)

skyStreamMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe2.0 = 0 (no)

SNMP MIB DescriptionThis chapter describes the SNMP MIBs that manage the iPlex using SNMP. It also describes usage scenarios where applicable. Refer to the actual MIB files for exact MIB object names. All the iPlex MIBs conform to SMIv3 as described in RFC2578.

References [1] RFC1157 — A Simple Network Management Protocol (SNMP)

[2] RFC 2573, 2574, 2575 — SNMPv3 Framework

[3] RFC 2578 — Structure of Management Information Version 2 (SMIv2)

[4] NETSNMP toolkit (http://net-snmp.sourceforge.net/)

21


Compiling MIBsin Network

ManagementApplications

You can load iPlex MIBs into SNMP management applications, such as HP Open-View, MG-SOFT MIB compiler, NetSNMP. When loading the MIB files to an SNMP Manager, you must load them in the following order:

■ SKYSTREAM-ROOT-MIB

■ SKYSTREAM-PRODUCTS-MIB

■ MEDIAPLEX-TC-MIB

■ Other MIBs may be loaded in any order.

ROOT MIB The ROOT MIB defines the registration for TANDBERG Television SNMP manageable products. The illustration below shows the structure of the MIB tree.

The root of the MIB tree is “iso.” “skyStream” is located in the branch enterprise. “skyStreamMediaPlex” has the index 7 in the TANDBERG Television family of products. The indexes for this MIB are as follows: iso (1), org (3), dod (6), internet (1), private (4), enterprises (1), skyStream (3511), skyStreamMgmt (3), skyStream-MediaPlex (7), skyStreamMediaPlexMibObjects (1), skyStreamMedia-Plex....Objects ( ).

NOTEIf you are referring to this guide for SNMP help for the iPlex, youshould note that most MIBs use “Mediaplex” in their name, but aremeant for use with both Mediaplex and iPlex.

22


MIBs supportedon iPlex

The following table lists all of the MIBS supported by the iPlex and various OS releases. If you are loading these MIBS in management applications load the MIBs in the order specified. An overview is provided in this guide, but full details are provided in the MIB for each object. The index number references the respective iPlex Enterprise MIB.

Index Description MIB Name For Details, See

SNMPv2-SMI.txt MIB onlySNMPv2-TC.txt MIB onlySNMPv2-MIB.txt MIB onlyROOT MIB on page 22 MIB onlySKYSTREAM-PRODUCTS-MIB.txt MIB onlyMEDIAPLEX-TC.txt MIB onlyIPV6-TC.txt MIB only

1 ASI In skyStreamMediaPlexASIInObjects (1) page 242 ASI Out skyStreamMediaPlexASIOutObjects page 243 Encoder skyStreamMediaPlexEncoderObjects page 254 VLAN Mgmt skyStreamMediaPlexVlanMgmtObjects page 255 Software skyStreamMediaPlexSoftwareObjects page 256 Program skyStreamMediaPlexProgramObjects page 267 UDP Out skyStreamMediaPlexUDPOutObjects page 268 Element skyStreamMediaPlexElementObjects page 279 UDP In skyStreamMediaPlexUDPInObjects page 27

10 Program Route skyStreamMediaPlexProgramRouteObjects page 2811 Stream Route skyStreamMediaPlexStreamRouteObjects page 2812 Notification skyStreamMediaPlexNotificationObjects page 2813 SME skyStreamMediaPlexSmeObjects page 2814 IP Route skyStreamMediaPlexIpRouteObjects page 3115 TS Stats skyStreamMediaPlexTsStatsObjects page 3116 RTP In skyStreamMediaPlexRTPInObjects page 3117 RTP Out skyStreamMediaPlexRTPOutObjects page 3118 ATM In skyStreamMediaPlexATMInObjects page 3119 ATM Out skyStreamMediaPlexATMOutObjects page 3220 Redundancy skyStreamMediaPlexRedundancyObjects page 3221 Sensor skyStreamMediaPlexSensorsObjects (21) page 3222 Chassis skyStreamMediaPlexChassisObjects page 3223 SMD skyStreamMediaPlexSmdObjects page 3224 ATM skyStreamMediaPlexATMObjects page 3325 FILEIn skyStreamMediaPlexFILEInObjects page 3326 GE skyStreamMediaPlexGEObjects page 3327 Alarms skyStreamMediaPlexAlarmsObjects page 33

23


iPlex Enterprise MIBsYou must check each parameter in the MIB to see which ones you can get or set. The value is given at the end of each description.

Mediaplex ASIIn MIB skyStreamMediaPlexASIInObjects This module defines the iPlex ASIIn MIB objects. It also contains objects that allow get and set. The MIB does not support row creation and row deletion.

Mediaplex ASIOutMIB

skyStreamMediaPlexASIOutObjects This module defines the iPlex ASIOut MIB objects and has a table for generating CAT. It also contains objects that allow get and set.

29 SCM skyStreamMediaPlexScmObjects page 3430 Encoder Audio skyStreamMediaPlexEncoderAudioObjects page 3431 ATM Route skyStreamMediaPlexAtmRouteObjects page 3432 MPE Route skyStreamMediaPlexMpeRouteObjects page 3433 TCP In skyStreamMediaPlexTCPInObjects page 3534 Backhaul skyStreamMediaPlexBackhaulObjects page 3535 XRater In skyStreamMediaPlexXRaterInObjects page 3536 XRater Out skyStreamMediaPlexXRaterOutObjects page 3538 Advanced Encoder skyStreamMediaPlexAdvancedEncoderObjects page 3539 Descriptors skyStreamMediaPlexDescriptorsObjects page 3540 Ports skyStreamMediaPlexPortsObjects page 3641 Spanning Tree skystreamMediaPlexSpanningTreeObjects page 3642 Notificationv2 skyStreamMediaPlexNotificationV2Objects page 3643 Log skyStreamMediaPlexLogObjects page 3644 Config File Mgmt skyStreamConfigFileMgmtMIBObjects page 3645 Notification Log skyStreamMediaPlexNotificationLogObjects page 3646 SNMP skyStreamMediaPlexSnmpObjects page 3647 License skyStreamMediaPlexLicenseObjects page 3648 File Management skyStreamMediaPlexFileMgmtObjects page 3649 Media Processor skyStreamMediaPlexMediaProcessorObjects page 3650 xCoderIn skyStreamMediaPlexxCoderInObjects page 3751 xCoderOut skyStreamMediaPlexxCoderOutObjects page 3753 Security skyStreamMediaPlexSecurityObjects page 3659 AVC Encoder skyStreamMediaPlexAvcEncoderObjects page 3761 AVC xCoder In skyStreamMediaPlexAvcXCoderInObjects page 3762 AVC xCoder Out skyStreamMediaPlexAvcXCoderOutObjects page 37

Index Description MIB Name For Details, See

24


asiOutCATInfoTableThis table provides information about ASI Out CAT parameters. It is only valid if enableCATGeneration = true. If you want to create a new row, you must use the index sequence: bladeNumber, unitNumber, caSystemId, emmPid and you must specify: privateData, catRowStatus ‘createAndGo’ (4). To delete a port, you must use the same index sequence and set catInRowStatus to ‘destroy’ (6).

Mediaplex EncoderMIB

skyStreamMediaPlexEncoderObjects This module defines the iPlex Encoder MIB objects. It also contains objects that allow get and set. The MIB does not sup-port row creation and row deletion.

Mediaplex VLANManagement MIB

skyStreamMediaPlexVlanMgmtObjects This module defines the iPlex Vlan Management MIB objects.

The index used is the following sequence: vlan id

When creating a new VLAN, the management application must provide values for the following MIB objects:

■ vlanIpAddress

■ vlanSubnetMask

■ vlanGe1

■ vlanGe2

■ vlanRowStatus

The following is an example to create VLAN with VLAN ID 3, IP address 172.30.1.1, subnet mask of 255.255.255.0 and configure GE port1 (untagged) as a member of the vlan—a multiple variable SNMP set request must be issued that contains the following variables and corresponding values:

To delete a VLAN, the management application must set value ‘destroy’ (6) for the vlanRowStatus MIB object.

You can modify the four GE parameters of VLAN after creation.

Mediaplex SoftwareMIB

skyStreamMediaPlexSoftwareObjects This MIB provides information about all software images present in aflash partition, and is available in softwareVersion-InfoTable. MIB object softwareCurrentVersionNumber provides version information about current software.

MIB Object ValuevlanMgmtInfoTable.vlanMgmtInfoEntry.vlanIpAddress.3 172.30.1.1vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanSubnetMask.3 255.255.255.0vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe1.3 1 (untagged)vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe2.3 0 (no)vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanRowStatus.3 4 (create-

AndGo)

25


This MIB also allows users to configure boot source using MIB objects soft-wareBootSource. If the boot source is TFTP MIB objects, softwareTftpI-pAddress and softwareTftpFilename must be set appropriately.

Mediaplex ProgramMIB

skyStreamMediaPlexProgramObjects This MIB provides information about DVB programs available on specific output interface. The MIB also allows the cre-ation and removal of programs from output interfaces. It also contains objects that allow get and set.

The index used is the following sequence: port type, blade number, unit number, program number. The port type can be UDPOut, RTPOut, or any of the other logical ports. Each port type has a specific value. You can get this information by looking at the MIB.

The MIB also has one table indexed by port type, blade number, unit number, and program number (create/destroy).

• pmtPid—Program PMT PID. Set only valid at creation/deletion time: integer (range 0...8191)

• pcrPid—Program PCR PID. Set only valid at creation/deletion time: integer (range 0...8191)

• programRowStatus—Set only valid at creation/deletion time.

The following is an example to create a new program 200 from output interface ASIOut3/1 with PMT PID of 0x28 and PCR PID of 0x29:

To delete a specific program route from an output interface, the management application must set value ‘destroy’ (6) for the programRowStatus MIB object.

Mediaplex UDPOutMIB

skyStreamMediaPlexUDPOutObjects This module defines the iPlex MIB for managing UDPOut logical ports. The MIB allows creation and deletion of UDPOut logical interfaces.

If you want to create a new UDPOut port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface, udpoutRowStatus = 4 (CREATEANDGO). If you want to delete a UDPOut port, you MUST use the same index sequence and MUST specify udpOutRow-Status = 6 (DESTROY).

MIB Object ValueprogramInfoTable.programInfoEntry.pcrPid.asiOut.3.1.200 40programInfoTable.programInfoEntry.pmtPid.asiOut.3.1.200 41programInfoTable.programInfoEntry.programRowSta-tus.asiOut.3.1.200

4 (create-AndGo)

NOTEUDPOut also has a table for generating CAT. See ASIOut.

26


Mediaplex ElementMIB

skyStreamMediaPlexElementObjects This MIB provides information about elements present on specific programs on given interfaces. The MIB also allows the creation and removal of elements within specific programs on a output inter-face. It also contains objects that allow get and set.

The index used is the following sequence: port type, blade number, unit number, program number, element number. The port type can be udpOut, rtpOut, or any of the other logical ports. Each port type has a specific value, you can get this information by looking at the MIB.

When creating a new element, the management application must also provide val-ues for the following MIB objects:

• streamType

The following is an example to add a MPEG-2 video element with PID 0x64 to a program number 20 on output interface ASIOut1/1—a multiple variable SNMP set request must be issued that contains the following variables and corresponding values:

To delete a specific program from a output interface using the managementapplication, you must set the value ‘destroy’ (6) for the elementRowStatusMIB object, with the index of the element, which is asiOut.1.1.20.100 shownabove. You must specify udpInRowStatus.

Mediaplex UDPInMIB

skyStreamMediaPlexUDPInObjects This module defines the iPlex UDPIn MIB objects. This MIB allows creation and deletion of UDPIn logical interfaces.

If you want to create a new UDPIn port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface (UDPIn over ATM/SMD), portNumber, packetizerType, udpInRowSta-tus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify udpInRowStatus = 6 (DESTROY).

MIB Object ValueelementInfoTable.elementInfoEntry.streamType.asiOut.1.1.20.100 2 (MP2 Video)elementInfoTable.elementInfoEntry.elementRowSta-tus.asiOut.1.1.20.100

4 (createAndGo)

27


Mediaplex ProgramRoute MIB

skyStreamMediaPlexProgramRouteObjects A table of information about pro-gram routes. If you want to add a program route, you MUST use the index sequence { sourcePortType, sourceBladeNumber, sourceUnitNumber, destina-tionPortType, destinationBladeNumber, destinationUnitNumber, sourceProgram-Number, destinationProgramNumber } and MUST specify: destinationPMTPID, programRouteRowStatus = 4 (CREATEANDGO). If you want to delete a pro-gram route, you MUST use the same index sequence and MUST specify program-RouteRowStatus = 6 (DESTROY).

You cannot modify the parameters of a program route after creation.

To delete a specific program route from an output interface, the management application must set value ‘destroy’ (6) for the programRouteRowStatus MIB object.

Mediaplex StreamRoute MIB

skyStreamMediaPlexStreamRouteObjects A table of information about stream routes. If you want to add a stream route, you MUST use the index sequence { sourcePortType, sourceBladeNumber, sourceUnitNumber, destina-tionPortType, destinationBladeNumber, destinationUnitNumber, sourcePID, des-tinationPID } and MUST specify: streamRouteRowStatus = 4 (CREATEANDGO). If you want to delete a stream route, you MUST use the same index sequence and MUST specify streamRouteRowStatus = 6 (DESTROY).

You cannot modify the parameter of a stream route after creation.

To delete a specific stream route from a output interface, the management applica-tion must set value ‘destroy’ (6) for the streamRouteRowStatus MIB object.

MediaplexNotification MIB

skyStreamMediaPlexNotificationObjects This MIB defines traps generated by the iPlex.

Mediaplex SME MIB skyStreamMediaPlexSmeObjects This module defines the iPlex SME boot management MIB objects and has three tables that allow you to create or destroy values: efInfoTable, afInforTable, and beInfoTable. It also contains objects that allow get and set.

MIB Object ValueprogramRouteInfoTable.programRouteInfoEntry.destinationPMT-PID.asiIn.1.1.asiOut.1.4.200.205

33

programRouteInfoTable.programRouteInfoEntry.programRouteRowSta-tus.asiIn.1.1.asiOut.1.4.200.205

4 (create-AndGo)

MIB Object ValuestreamRouteInfoTable.streamRouteInfoEntry.streamRouteRowSta-tus.asiIn.1.1.asiOut.1.4.256.512

4 (createAndGo)

28


efInfoTableThe efInfoTable table allows you to add a new EF discipline by configuring the following parameters:

■ efName

■ efMaxBitRate

■ efRowStatus

You must use the index sequence: efBladeNumber, efUnitNumber, efIndex and specify efName, efMaxBitRate, efRowStaus ‘createAndGo’ (4).

The following is an example to create EF discipline, named ‘ef1’, with max-bit rate of 100 Kbps, and associate it with SME interface sme1/1—a multiple vari-able SNMP set request must be issued that contains the following variables and corresponding values:

To delete a EF discipline using the management application, you must set the value ‘destroy’ (6) for the efRowStatus.index MIB object. To delete the first discipline, the management application has to set efRowStatus to 6 (destroy).

You cannot modify the discipline attributes after creation.

afInfoTableThe afInfoTable allows you to create and configure a new AF discipline on a spe-cific SME interface.

The index represents the row of the AF discipline, Index 0 will represent the first discipline, Index 1 the second discipline, and so on.

To create a new AF discipline, the management application must use value cre-ateAndGo for afRowStatus column, no other values are supported.

When creating a new AF discipline, the management application must also provide values for the following MIB objects:

■ afName■ afMinBitRate■ afMaxBitRate■ afRowStatus■ afQueueSize

You must use the index sequence: afBladeNumber, afUnitNumber, afIndex and specify: afName, afMinBitRate, afMaxBitRate, afRowStatus ‘cre-ateAndGo’ (4).

MIB Object ValueefInfoTable.efInfoEntry.efName.1.1.0 “ef1”efInfoTable.efInfoEntry.efMaxBitRate.1.1.0 100000efInfoTable.efInfoEntry.efRowStatus.1.1.0 4 (createAndGo)

29


The following is an example to create AF discipline, named ‘af1’, with max-bit rate of 100 Kbps and min-bit rate of 500 bps, and associate it with SME interface sme1/1—a multiple variable SNMP set request must be issued that contains the following variables and corresponding values:

To delete an AF discipline using the management application, you must set the value ‘destroy’ (6) for the afRowStatus MIB object.


beInfoTableThe beInfoTable allows you to create and configure a new BE discipline on a spe-cific SME interface.

The index represents the row of the BE discipline, Index 0 will represent the first discipline, Index 1 the second discipline, and so on.

To create a new BE discipline, the management application must use value cre-ateAndGo for beRowStatus column, no other values are supported.

When creating a new BE discipline, the management application must also provide values for the following MIB objects:

■ beName

■ beQueueSize

■ beRowStatus

You must use the index sequence: beBladeNumber, beUnitNumber, beIndex and specify: beName, beQueueSize, beRowStatus ‘createAndGo’ (4).

The following is an example to create BE discipline, named ‘be1’ with queue size of 500 and associate it with SME interface sme1/1—a multiple variable SNMP set request must be issued that contains the following variables and corresponding values:

To delete a BE discipline using the management application, you must set the value ‘destroy’ (6) for the beRowStatus MIB object.


MIB Object ValueafInfoTable.afInfoEntry.afName.1.1.0 “af1”afInfoTable.afInfoEntry.afMinBitRate.1.1.0 500afInfoTable.afInfoEntry.afMaxBitRate.1.1.0 100000afInfoTable.afInfoEntry.afRowStatus.1.1.0 4 (create-

AndGo)afInfoTable.afInfoEntry.afQueueSize.1.1.0 100-500

MIB Object ValuebeInfoTable.beInfoEntry.beName.1.1.0 “be1”beInfoTable.beInfoEntry.beQueueSize.1.1.0 500beInfoTable.beInfoEntry.beRowStatus.1.1.10 4 (createAndGo)

30


Mediaplex IP RouteMIB

skyStreamMediaPlexIpRouteObjects This module defines the iPlex MIB for managing the IP routes. It has two tables indexed by IP address and netmask (cre-ate/destroy):

• gateway—Route Gateway. Set only valid at creation/deletion time.

• rowStatus—IP route row status. Set only valid at creation/deletion time.

You must specify gateway and rowStatus to ‘createAndGo’ (4).

If you want to delete a IP route, you must use the same index sequence, specify rowStatus and set value to ‘destroy’ (6).

Mediaplex TS StatsMIB

skyStreamMediaPlexTsStatsObjects This MIB provides transport stream sta-tistics for a specific input or output interface. This table does not support row cre-ation and row deletion.

Mediaplex RTPInMIB

skyStreamMediaPlexRTPInObjects This module defines the iPlex RTPIn MIB objects, and allows the creation and deletion of RTPIn logical interfaces.

If you want to create a new RTPIn port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface (RTPIn over ATM), portNumber, enableRTCP, rtpInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify rtpInRowStatus = 6 (DESTROY).

Mediaplex RTPOutMIB

skyStreamMediaPlexRTPOutObjects This module defines the iPlex MIB for managing RTPOut logical ports, and allows the creation and deletion of RTPOut logical interfaces.

If you want to create a new RTPOut port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface, enableRTCP, portNumber, rtpOutRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify rtpOutRowStatus = 6 (DESTROY).

Mediaplex ATMInMIB

skyStreamMediaPlexATMInObjects This module defines the iPlex ATMIn MIB objects, and allows the creation and deletion of RTPIn logical interfaces.

If you want to create a new ATMIn port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface

MIB Object ValueipRouteInfoTable.ipRouteInfoEntry.gateway.192.168.2.189.225.225.225.0 10.10.10.1ipRouteInfoTable.ipRouteInfoEntry.rowStatus.192.168.2.189.225.225.225.0 4 (create-

AndGo)

NOTERTPOut also has a table for generating CAT. See ASIOut.

31


(ATM interface name), atmInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify atmInRowStatus = 6 (DESTROY).

Mediaplex ATMOutMIB

skyStreamMediaPlexATMOutObjects This module defines the iPlex MIB for managing ATMOut logical ports, and allows the creation and deletion of ATMOut logical interfaces.

If you want to create a new ATMOut port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: attachedInterface (ATM interface name), atmInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify atmIn-RowStatus = 6 (DESTROY).

MediaplexRedundancy MIB

skyStreamMediaPlexRedundancyObjects This module defines the MIB for managing redundancy. It also contains objects that allow get and set. The MIB does not support row creation and row deletion.

Mediaplex SensorsMIB

skyStreamMediaPlexSensorsObjects This MIB provides information retrieved from hardware sensors in the chassis. Moreover, it provides information about the number of power supplies in a chassis, status of power supply, number of fan trays in a chassis, and status of each fan tray. It also provides instantaneous temperature and voltage reading from each hardware component in the system. This table does not support row creation or deletion.

Mediaplex ChassisMIB

skyStreamMediaPlexChassisObjects This MIB provides chassis inventory information and tables for blade, PMC, CPU, and buffers. It also contains objects that allow get and set. The MIB does not support row creation and row deletion.

Mediaplex SMD MIB skyStreamMediaPlexSmdObjects This module defines the iPlex SMD manage-ment MIB objects and has two tables that allow you to create or destroy values: smdPidInfoTable and smdMacInfoTable. It also contains objects that allow get and set.

smdInfoTableThis table allows you to add a new PID by configuring the following parameter:

■ pidRowStatus

You must use the index sequence: pidBladeNumber, pidUnitNumber, pidNum-ber and specify pidRowStaus ‘createAndGo’ (4).

To delete a PID, you must use the same index sequence and specify pidRowSta-tus ‘destroy’ (6).

NOTEATMOut also has a table for generating CAT. See ASIOut.

32


macInfoTableThis table allows you to add a new MAC address by configuring the following parameters:

■ macAddress

■ macRowStatus

You must use the index sequence: macBladeNumber, macUnitNumber, macIndex and specify: macAddress, and macRowStatus ‘createAndGo’ (4).

To delete a MAC address, you must use the same index sequence and specify mac-RowStatus ‘destroy’ (6)—only valid if enableMacFiltering = true.

Mediaplex ATM MIB skyStreamMediaPlexATMObjects This module defines the iPlex ATM MIB objects. It also contains objects that allow get and set. The MIB does not support row creation and row deletion.

Mediaplex FILEInMIB

skyStreamMediaPlexFILEInObjects This module defines the iPlex MIB for managing the File In logical ports and has one table that allows creation and dele-tion. It also contains objects that allow get and set.

If you want to create a new FILEIn port, you MUST use the index sequence{ bladeNumber, unitNumber } and MUST specify: packetizerType, fileInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify fileInRowStatus = 6 (DESTROY).

fileInInfoTableTo create a new FILEIn port, you MUST use the index sequence {bladeNum-ber, unitNumber} and MUST specify: packetizerType, fileInRowSta-tus = 4 (CREATEANDGO).

Mediaplex GE MIB skyStreamMediaPlexGEObjects This MIB provides information about all GE interfaces on the chassis. It is a table indexed by GE port number (1-2). This table contains get objects but does not support row creation or deletion.

Mediaplex AlarmsMIB

skyStreamMediaPlexAlarmsObjects This module defines the iPlex Config-urable Alarms MIB objects. The table contains get and set objects for the redun-dancy switch and PMCs, but does not support row creation or deletion.

Mediaplex XraterMIB

skyStreamMediaPlexXRaterObjects This module defines the Mediaplex-20 XRater MIB objects. The MIB does not support row creation and row deletion.

IMPORTANT The Xrater MIB is obsolete and is replaced by the XrtrIn and XrtrOutMIBs.

33


Mediaplex SCM MIB skyStreamMediaPlexSCMObjects This module defines the iPlex SCM manage-ment MIB and contains objects that allow get and set.

The MIB also has three tables indexed by IP address (create/destroy).

• dnsServerRow Status—DNS server row status. Set only valid at creation/deletion time.

• syslogHostRowStatus—Syslog host row status. Set only valid at creation/deletion time.

• ntpServerRowStatus—NTP server row status. Set only valid at creation/deletion time.

For example, if you want to add a new syslog host, you must use the index sequence syslogHostIpAddress and specify syslogHostRowStatus and set value to ‘createAndGo’ (4).

If you want to delete a syslog host, you must use the same index sequence, specify syslogHostRowStatus and set value to ‘destroy’ (6).

Mediaplex EncoderAudio MIB

skyStreamMediaPlexEncoderAudioObjects This module defines the iPlex Encoder Audio MIB (only valid for the Encoder Plus) and contains objects that allow get and set. The MIB does not support row creation and row deletion.

Mediaplex ATMRoutes MIB

skyStreamMediaPlexATMRouteObjects This module defines the iPlex MIB for managing the ATM routes. It has three tables indexed by IP address, netmask, interface slot number and interface unit number (create/destroy):

• atmVpi— Route VPI. Set only valid at creation/deletion time.

• atmVci— Route VCI. Set only valid at creation/deletion time.

• rowStatus—ATM route row status. Set only valid at creation/deletion time.

You must specify atmVpi, atmVci, and set rowStatus to ‘createAndGo’ (4).

If you want to delete a syslog host, you must use the same index sequence, specify rowStatus and set value to ‘destroy’ (6).

Mediaplex MPERoutes MIB

skyStreamMediaPlexMpeRouteObjects This module defines the iPlex MIB for managing the MPE routes. If you want to add an MPE route, you must use the index sequence: ipAddress, netMask, interfaceSlotNumber (SME inter-face slot number), interfaceUnitNumber (SME interface unit number) and

MIB Object ValuescmSyslogHostInfoTable.scmSyslogHostInfoEntry.syslogHostRowSta-tus.192.168.4.26

4 (createAndGo)

MIB Object ValueatmRouteInfoTable.atmRouteInfoEntry.atm-Vpi.192.168.2.189.225.225.225.0.3.1.

0

atmRouteInfoTable.atmRouteInfoEntry.atm-Vci.192.168.2.189.225.225.225.0.3.1.

50

atmRouteInfoTable.atmRouteInfoEntry.rowSta-tus.192.168.2.189.225.225.225.0.3.1.

4 (create-AndGo)

34


specify: pid, ipMapMac, macAddress, disciplineName, rowStatus to ‘createAndGo’ (4). If you want to delete a syslog host, you must use the same index sequence, specify rowStatus and set value to ‘destroy’ (6).

Mediaplex TCPInMIB

skyStreamMediaplexTCPInObjects This module defines the iPlex MIB for TCPIn port creation and deletion.

To create a new TCPIn port, you MUST use the index sequence {bladeNumber, unitNumber} and MUST specify: attachedInterface (GE), portNumber, packetizerType (M2T), tcpInRowStatus = 4 (CREATEANDGO). If you want to delete a TCPIn port, you must use the same index sequence and MUST specify tcpInRowStatus = 6 (DESTROY).

Mediaplex BackhaulMIB

skyStreamMediaplexBackhaulObjects This module defines the iPlex MIB for Backhaul port creation and deletion. A table of information about Backhaul inter-faces. If you want to create a new Backhaul port, you MUST use the index sequence { bladeNumber, unitNumber } and MUST specify backhaulRow-Status = 4 (CREATEANDGO). If you want to delete a Backhaul port, you MUST use the same index sequence and MUST specify backhaulRowStatus = 6 (DESTROY).

Mediaplex XrtrIn MIB skyStreamMediaPlexXRaterInObjects This module defines the Mediaplex-20 XraterIn mib objects. The MIB does not support row creation and row deletion.

Mediaplex XrtrOutMIB

skyStreamMediaPlexXRaterOutObjects This module defines the Mediaplex-20 XraterOut mib objects. The MIB does not support row creation and row dele-tion.

MediaplexDescriptors MIB

skystreamMediaPlexDescriptorsObjects This module defines the user-created descriptors MIB objects. See the MIB for details.

Example: To add a PMT program descriptor with tag 0x03, hex data 00 11 22 on output interface ASIOut1/4, an SNMP set request must be issued that contains the following variables and corresponding values

Mediaplex AdvancedEncoder MIB

skyStreamMediaPlexAdvancedEncoderObjects This module defines the iPlex Adavnced Encoder MIB objects. It also contains objects that allow get and set. The MIB does not support row creation and row deletion.

MIB Object ValuepmtProgramDescriptorInfoTable.pmtProgramDescriptorInfo-Entry.data.asiOut.1.4.3

"00 11 22"

pmtProgramDescriptorInfoTable.pmtProgramDescriptorInfo-Entry.dataType.asiOut.1.4.3

1

pmtProgramDescriptorInfoTable.pmtProgramDescriptorInfo-Entry.pmtProgramDescriptorRowStatus.asiOut.1.4.3

4 (create-AndGo)

35


Mediaplex Ports MIB skystreamMediaPlexPortsObjects This module provides details from all of the ports and interfaces present on the system. The Ports table and Interfaces table do not support row creation and row deletion.

Spanning Tree MIB skyStreamMediaPlexSpanningTreeObjects This module defines the spanning tree MIB objects. This is only valid if chassisType = iPlex (2). Use this MIB to start an instance of STP (spanning tree protocol) and set the priority for which bridge becomes the root. The range is 0x1 to 0xffff. The bridge ID is derived from the VLAN MAC address.

The portion about GE ports is only valid if enableDaemon = true. This table does not support row creation and row deletion.

Notificationv2 MIB skyStreamMediaPlexNotificationV2Objects This module defines the notifica-tions generated by the Skystream NMR platform.

Log MIB skyStreamMediaPlexLogObjects This module defines the MediaPlex log man-agement MIB objects.

Config File MgmtMIB

skyStreamConfigFileMgmtMIBObjects This module facilitates writing of con-figuration file of an SNMP Agent running iPlex software in the following ways: to and from the net, copying running configurations to startup configurations and vice-versa, and copying a configuration (running or startup) to and from the local file system.

Notification Log MIB skyStreamMediaPlexNotificationLogObjects This module keeps track of the last notifications sent. It is a table with the last traps sent.

SNMP MIB skyStreamMediaPlexSnmpObjects This module defines the MediaPlex SNMP management MIB objects.

License MIB skyStreamMediaPlexLicenseObjects This module provides the management of license keys, which are used to enable optional features. The module allows entering of new license keys, as well as inspection of the existing license keys.

FileE ManagementMIB

skyStreamMediaPlexFileMgmtObjects This module provides file manage-ment functions. Files can be listed, deleted, and copied to/from an FTP server. Configuration files, data files, log files and tech-support files can be managed using this module.

Media ProcessorMIB

skyStreamMediaPlexMediaProcessorObjects This module allows the config-uration of Media Processors. Note that Media Processor support in Release 3.2 is at beta level.

Security MIB skyStreamMediaPlexSecurityObjects This module allows management of the security options in the device. Using this MIB, the SNMP manager can enable or

36


disable the various network control interfaces, as well as manage the allowed net-work list.

xCoderIn MIB skyStreamMediaPlexCoderInObjects This module defines the iPlex xCoderIn MIB objects. It also contains objects that allow get and set. The MIB does not sup-port row creation and row deletion.

xCoderOut Mib skyStreamMediaPlexCoderOutObjects This module defines the iPlex xCoder-Out MIB objects and has a table for generating CAT. It also contains objects that allow get and set.

AVC Encoder MIB skyStreamMediaPlexAvcEncoderObjects This module defines the AVC Encoder MIB objects which enable to use either HD-SDI or SD interface. The MIB does not support row creation and row deletion. This MIB is used for both the dual-slot and single-slot versions of the encoder.

AVC xCoder In skyStreamMediaPlexAvcXCoderInObjects This module defines the iPlex AVC Transcoder In MIB objects, for both the single-slot and dual-slot versions of the card. It contains objects that allow get/set operations to configure the port. This MIB does not support row creation and deletion.

AVC xCoder Out skyStreamMediaPlexAvcXCoderOutObjects This module defines the iPlex AVC Transcoder Out MIB objects, for both the single-slot and dual-slot versions of the card. It contains objects that allow get/set operation, to configure the port, and has a table for generating CAT.

If you want to create a new EMMIn port, you MUST use the index sequence { bladeNumber, unitNumber } and MUST specify: packetizerType, emmInRowSta-tus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify emmInRowStatus = 6 (DESTROY).

NOTEThis MIB allows the SNMP manager to turn off support for SNMP altogether. If that operation is attempted, it will complete normally, but all further SNMP operations with the device will fail.

37


Introduction to HP OpenView IntegrationAlthough any network management system supporting SNMP can be used for monitoring and managing iPlex, TANDBERG Television has selected the HP OpenView platform as the primary network management system for integration with iPlex product lines. HP Openview is a leading network management system used for network monitoring and data gathering at many large service provider networks. Currently, there are many other capable and powerful network manage-ment tools such as Computer Associates Unicenter; however, at this point TAND-BERG Television has elected to integrate with HP OpenView and create plug-ins for this application. Other products may be considered in the future depending on market and customer demands.

Fault ManagementThe goal of fault management is to detect, log, and notify users of problems in order to keep the network running effectively. Because faults can cause downtime or unacceptable network degradation, fault management is perhaps the most widely implemented of the ISO network management elements. Fault manage-ment involves several steps:

1 Determination of the problem symptoms

2 Isolation of the problem

3 Fixing the problem (if possible)

4 Testing of all important subsystems

5 Recording the problem’s detection and resolution

Accounting Management The goal of accounting management is to measure network utilization parameters to regulate appropriate individual or group uses of the network. Such regulation minimizes network problems because network resources can be apportioned based on resource capacities. This maximizes the fairness of network access across all users.

Configuration ManagementThe goal of configuration management is to monitor network and system configu-ration information to track and manage the effects on network operation of vari-ous versions of hardware and software elements. Because all hardware and software elements may impose operational flaws that might affect network opera-tion, such information is important in maintaining a smooth running network. Each network device has a variety of version information associated with it.

38


Performance ManagementThe goal of performance management is to measure and make available various aspects of network performance and maintain it at an acceptable level. Example of performance variables that might be provided include network throughput, user response times, and line utilization. Management entities continually monitor per-formance variables. If a performance threshold goes beyond set parameters, the network management system receives an alarm message. Performance manage-ment involves the following steps:

1 Gather performance data on variables relevant to network administrators

2 Analyze the data to determine normal levels

3 Determine appropriate performance thresholds for each important variablesuch that exceeding thresholds indicates a network problem worthy ofattention.

Most operation managers use HP OpenView and plug-ins provided by equipment vendors to monitor, troubleshoot, and provision heterogeneous networks. Follow-ing are some of the highlights of HP OpenView Network Node Manager (NNM):

■ Auto-discovery of the network

■ Presentation of network topology with real-time update of device status

■ Performance monitoring using SNMP for the collection of historical data

■ Central location to collect network events

■ Ability to execute user specified actions when specific events occur

■ SNMP Browser

TANDBERG Television HP OpenView Plug-in ComponentsThe iPlex HP OpenView plug-in provides the following functionality:

■ Map registration files that allow NNM to discover and identify new iPlexdevices and displays iPlex icons in the topology map(s)

■ Integrates TANDBERG Television-specific MIB files into OpenView MIBdatabase

■ Receives and classifies SNMP traps generated by the iPlex

■ Provides menu registration files that allow users to start TANDBERGTelevision-specific applications

NOTEThe TANDBERG Television MIBs are automatically complied and made available through HP OpenView.

39


■ Allows users to launch iPlex Web GUI from the HP OpenView via menus,and from an button on the top menu of each map

■ Provides an install CD that installs the plug-in

Monitoring iPlex from HP OpenViewHP OpenView provides the capability to automatically discover network-attached devices. Having discovered the device, it is added to the HP OpenView network map(s). The operator can decide to either monitor the device, or keep it as unman-aged or unmonitored.

The installation of the TANDBERG Television iPlex plug-in software allows HP OpenView to correctly identify the device as a iPlex, and to add the correct icon to the maps, while associating the appropriate menu options to the device.

The screen below shows an actual view of an HP OpenView map containing four TANDBERG Television iPlexes. If the iPlex is operational and there are no errors detected, the icon would be green. A red icon signifies an error with the device.

40


Monitoring aSpecific iPlex

Double-click the central icon to see the TANDBERG Television nodes on the network.

Right-click a iPlex icon to display the following option menu:

Standard OptionMenu

This menu is a standard HP OpenView menu and allows the user to Open the contents of the selected iPlex. At the bottom of the menu are several options that are specific to the iPlex Plug-in:

• Browse iPlex—launches the iPlex Web Graphical User Interface

• Telnet CLI—launches the iPlex Command Line Interface

• SNMP Browser—launches the SNMP MIB Browser

• Chassis Report—generates a report on the selected iPlex chassis

41


Right-click one of these iPlex icons to again display standard HP Openview menu options. The example below shows two icons: a physical eth2 port, and a logical vlan_8 subgroup. If this is the last subgroup in the mapping, clicking Open will display the following message: “This object does not have a child submap...” From here you could create a new subgroup, if required.

Opening the WebGUI for HPOpenView

The user can access the Web GUI in two ways. Once you have selected a iPlex, you can launch the Web GUI by either clicking on the iPlex button on the top right side of the map menu, or by right-clicking the iPlex icon and selecting it from the menu.

42


It is also possible to open a direct Telnet or Command Line Interface connection to specific highlighted iPlex. To achieve this, right-click a iPlex icon, and then click the Telnet CLI option from the menu. The following screen shows an open Tel-net window to the iPlex. See the CLI Commands and Operation information in the CLI User Guide.

43


Launching anSNMP Browser

for a SpecificiPlex

Another option available through the standard HP OpenView options menu is to launch an SNMP browser for a specific iPlex device. This provides the means to query a iPlex for specific SNMP information available through the TANDBERG Television iPlex MIBs. The following figure shows a typical SNMP MIB Browser window.

44


Obtaining a Listof iPlex

Components

The user can view a list of Mediaplex modules in a chassis by selecting Chassis Report from the Mediaplex menu. Right-clicking the Mediaplex icon shows this option. The following figure shows an example of the output of the Mediaplex components.

Inventory Report It is also possible to display an inventory of all iPlex devices on the network. This option is available through HP OpenView Tools menu, as shown below: The inventory list four iPlexes on the network.

45


Network InterfaceProperties

The user can obtain information on a iPlex from the standard HP OpenView menus. For example, by highlighting the iPlex that you require information about, click the following options: Configuration>Network Configuration>Interface Properties. The resulting screen is shown below:

46


System Alarms The system alarm menu is a standard HP Openview Feature. The iPlex plug-in adds a TANDBERG Television Alarm indicator to it.

Click the SkyStream Alarms indicator, and the SkyStream Alarm Browser will launch, which reports on alarm severity: critical, major, minor, warming and nor-mal.

Graphs andHistorical Data

Gathering

HP OpenView in conjunction with compiled iPlex MIBs provides a good platform for historical data gathering and producing statistical graphs for each iPlex, or across a group of iPlexes. The data gathering and graphing functions are part of HP OpenView native features. Having selected the device or group of devices, you can access them directly through the HP OpenView menus.

47


An example of the type of statistical information that is available on iPlex is the CPU utilization of the MCM or the SCM. You can also obtain other statistical data, such as the amount of available memory, or SNMP traffic to and from the device through HP OpenView. The following screen is an example of the SNMP operations performed on iPlex. This is simply an example of the graphing function of HP OpenView, and as stated, you can produce many other graphs through the same capability.

48

Monitoring iPlex UsingSNMP

Appendix A

49


OverviewThis Appendix provides a practical guide to the MIB and traps and how to use them to monitor the status of chassis, blades, ports, and streams. This guide will assist customers in their understanding of iPlex MIB definition files and offer sug-gestions for how best to use the numerous variable and trap definitions included in the MIB files to monitor the health of an installed network of devices. iPlex sup-ports SNMPv2 and SNMPv3; in this document however we will assume that SNMPv2 is being used.

The areas covered include:

• IP Address Usage

• Basic Status Polling

• Advanced Status Polling

• Trap Definitions and Usage

• Performance Monitoring

50


IP Address Usage

In a standalone mode there is typically only 1 IP address configured which is the first entry in the table below. For a 1 x 1 redundancy configuration, 2 other IP Addresses could exist. An iPlex will respond to SNMP requests in a way that the current primary device will fully respond to SNMP requests while the backup device will only respond to certain SNMP requests. The MIB file containing this information is the MEDIAPLEX-SCM-MIB. The iPlex naming convention for the catchall chassis IP Address is used; see the table that follows.

IP Addresses

Unique Table OID Variable Binding OID Variable Name Syntax Value -

Description

1.3.6.1.4.1.3511.3.7.1.29

1.3.6.1.4.1.3511.3.7.1.29.3

managementIpAddress IpAd-dress

Primary iPlex SCM IP Address

1.3.6.1.4.1.3511.3.7.1.29.6

virtualIpAddress IpAd-dress

IP Address shared between iPlexes

1.3.6.1.4.1.3511.3.7.1.29.12

backupManagementIpAd-dress

IpAd-dress

Backup iPlex SCM IP Address

51


Basic Status PollingThis section covers the minimum polling requirements to determine the health of any Mediaplex or iPlex device.

It assumes that Trap monitoring is in place for the network and that all devices are correctly configured with Trap Forwarding Destination addresses. It also assumes that no Traps will be lost during transmission.

In Ip Addresses table, managementIpAddress entry indicates the primary SCM blade and the backupmanagementIpAddress entry indicates the current backup SCM blade. For simple polling systems it is perhaps best to allow a monitoring sys-tem to understand 2 IP Addresses and disregard the significance of each.

Therefore the suggestion for externally developed polling routines is to have the ability to monitor up to 2 IP Addresses, which would be manually configured to the polling system.

For each Address, the following operations are suggested to perform:

1 Ping each address to confirm basic IP connectivity – by doing this a pollingsystem knows that basic connectivity can be established. Failure clearlyindicates a basic IP addressing failure, which could be caused by NetworkingIssues of a problem with the unit.

2 Perform an SNMP Get on the sysObjectID variable (see table below) – thiscan be used to confirm that the device is indeed an iPlex. It also confirms thatthe SNMP subsystem within the device control layer is active and functional.Failure to get a response to this request could indicate that the SNMPsubsystem is down and therefore needs attention or, in the case of 1 + 1 SCMredundancy, one of the SCM blades is actually having a problem.

3 Perform an SNMP Get on the sysUpTime variable (see table below) – thiscan be monitored for an ever increasing value. If the value returned to zero orappeared to go backwards (other than during a wrap around), then this wouldindicate that an SCM has rebooted.

Both of the variables mentioned above are derived from the RFC1213-MIB file and are described in the following table.

Useful System Polling Objects

Unique Table OID

Variable Name Syntax Value - Description

1.3.6.1.2.1.1.2

sysObjec-tID

OBJECT IDENTI-FIER

A unique OID: 1.3.6.1.4.1.3511.3.1.29

1.3.6.1.2.1.1.3

sysUpTime TimeTicks The time in 1/100ths of a second since the device booted last

52


Advanced Status PollingMore experienced users can poll iPlex devices and obtain or derive other useful information from the response to a request as follows:

• Determine if a 1 x 1 redundancy switch has occurred between iPlex devices configured for 1 x1 redundancy.

• Determine a complete list of outstanding alarms for iPlex devices.

Detecting Redundancy Flips between SCM BladesTo determine whether redundancy switches have occurred between SCM blades, it is necessary for the polling device to be configured with 2 IP addresses. In addi-tion, it should either be given an understanding of primary and backup roles or be capable of discovering primary and backup roles. For the sake of this discussion, it will be assumed that the polling system starts with no understanding of primary or backup role state. In such a system the following would be required:

1 Try to read the managementIpAddress of the device (see “IP Addresses ”table) – If a valid IP address is returned, this indicates that the current addressis the primary SCM in a 1 x 1 redundancy pair. If no valid IP address isreturned, then this indicates the field cannot be read and the address beingused for polling must therefore be that of the backup device.

2 Retain knowledge after the first poll sequence of which IP address is theprimary.

3 Subsequent polls can now indicate if a redundancy switch has occurred sinceif the current primary fails to respond with a valid IP address and the previousbackup IP Address does now respond with a valid IP Address, we know that aRedundancy switch occurred and that the pair may need attention.

Monitoring Blade Information TableMonitoring the table will enable users to quickly track issues and effect remedies. In the iPlex, a single unit is comprised of 2 “virtual” blades internally, so if the MCM was seen to disappear, this would indicate a problem with a unit.

The key MIB file to be used for this type of monitoring is the MEDIAPLEX-CHAS-SIS-MIB (See Blade Status Polling MIB Parameters table) which contains all of the information of interest to the polling system. The best way to handle this table would be as follows:

4 Perform an SNMP GET on the chassisBladeCount variable – this will enablea suitably written polling system to recognize any change or removal from achassis. Two methods would exist here being dependent on the polling systemsSNMP abilities. Once the chassisBladeCount is known, the polling routine cannow perform GET, GET NEXT or GET BULK requests for the bladeType

53


and bladeState fields. It is not necessary to read the slotNumber field as this isan INDEX to returned OID for bladeType and bladeState and shouldtherefore be parsed from the return OID value. It is assumed that the readerof this document is fully conversant with SNMP syntax and usage.

5 The polling routine can now track blades types and recognize changes. It canalso determine if blades were removed and which blades they were and finallyit can determine if any blades were changed. Any and all of this informationcould then be used to alarm/warn/inform a network operator about actualchanges to a monitored system.

6 More sophisticated polling systems could also track the blade state if sodesired, and track any changes by enhancing the polling routines’ ability topass on more information to the user.

Blade Status Polling MIB Parameters

Active Alarm Table MonitoringYet another possible polling option for customers developing their own system monitor could be to have the ability to collect and display the current list of active alarms present in iPlex. This may be especially useful when a device is added to the polling system initially as at this point there is no historical information regarding the current state of the device being added. In this case a system might retrieve the table to determine the current state.

The table actually contains a list of the active traps that have been sent to listening devices configured in the trap destination table, so there is a direct correlation between the table entries, the information contained therein and the traps that were originally generated.

MIB/Unique Table OID

Variable Binding OID


bladeInfoTable 1.3.6.1.4.1.3511.3.7.1.22.2

1.3.6.1.4.1.3511.3.7.1.22.2.1.1

slotNumber Integer This parameter is returned as an index and can be parsed from the responses to deter-mine which blades are installed.

1.3.6.1.4.1.3511.3.7.1.22.2.1.2

bladeType Integer This indicates the blade type for the indexed blade. MCM = 1 and SCM = 2

1.3.6.1.4.1.3511.3.7.1.22.2.1.3

bladeState Integer Allows you to discover whether the blade is okay. States are: offline(0), online(1), unreachable(2), unini-tialized(3), synching(4), configur-ing(5)

54


By appropriate interpretation of this table it can be determined which blades, units and modules are in an error state, which would allow a polling system to display useful information to a network operator.

Other possibilities would be for the monitoring system to be able to display this list when requested by the user. All details regarding the interpretation of the indi-vidual entries can be found in the iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0) on page 58 section where all iPlex traps are discussed in detail.

The MIB file containing the information discussed here is the MEDIAPLEX-NOTIFICATION-LOG-MIB.

To access and retrieve the Active Alarm Table, follow the steps:

1 Perform an SNMP GET on currentActiveAlarmEntries. This value willinform the polling routine of the actual number of currently active alarms forthe polled device. The actual value can then be used to form a loop count forhow many instances of individual parameters to request. Two methods wouldexist here being dependent on the polling systems SNMP abilities. A systemmight use a loop and perform GET NEXTS based on thecurrentActiveAlarmEntries or create a single GET BULK for the numberreturned setting the MAX REPETITIONS field to thecurrentActiveAlarmEntries.

2 With the currentActiveAlarmEntries value it is now possible for GET NEXTor GET BULK requests to retrieve the entire table.

3 Once the data has been collected, it would be up to the requesting routine toformat the data for displaying it to the user or use in whatever way deemednecessary by the application.

Active Alarm Table

NOTE

This table became available in Version 3.0 of iPlex software and did not exist in any form in older versions of software.

NOTEIt is more efficient for polling routines to encapsulate several SNMPGET, GET NEXT or GET BULK commands into a single SNMPpacket.

NOTETheaaIndex and aaSequenceNumber fields are index values into the table and cannot be read directly but rather they need to be parsed from the returned OID's.

55


MIB/Unique Table OID Variable Binding OID Variable Name Syntax Value - Description

1.3.6.1.4.1.3511.3.7.1.45.5 currentAc-tiveAlarmEntries

Integer The currently active alarm count for a device

1.3.6.1.4.1.3511.3.7.145.6.1.1

aaIndex Integer This parameter is returned as an index and can be parsed from the responses to determine which blades are installed.

1.3.6.1.4.1.3511.3.7.145.6.1.2

aaSequenceNum-ber

Integer This parameter is returned as an index and can be parsed from the responses to determine which blades are installed.

activeAlarmInfoTable 1.3.6.1.4.1.3511.3.7.145.6

1.3.6.1.4.1.3511.3.7.145.6.1.3

aaNotificationId Integer Specific Notification type, see iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0) on page 58section for a complete list of Notifi-cations available from iPlex.

1.3.6.1.4.1.3511.3.7.145.6.1.4

aaModuleType Module_Type(Integer)

This could be any mod-ule in the system and is defined in the MEDIA-PLEX-TC file.

1.3.6.1.4.1.3511.3.7.145.6.1.5

aaSlotNumber Integer Slot number within a chassis.

1.3.6.1.4.1.3511.3.7.145.6.1.6

aaUnitNumber Integer PMC Unit number when linked to hard-ware.

1.3.6.1.4.1.3511.3.7.145.6.1.7

aaSubUnitNum-ber

Integer Where more than one port exists within a Unit this field can be used to indicate which port is having problems other-wise it is unused.

1.3.6.1.4.1.3511.3.7.145.6.1.8

aaDescription Octet String

A textual description of the particular alarm

56


1.3.6.1.4.1.3511.3.7.145.6.1.9

aaSeverity Integer The severity of the trap. Severities can be modi-fied by users for every trap the iPlex can gen-erate using the Web GUI.

57


iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0)

This section covers iPlex software before Version 3.0 release. iPlex generates SNMP traps to inform external devices about changes in operational conditions and configuration of a device. This section discusses each and every trap.

To be able to receive the traps, the user must configure a trap destination for each system monitoring tool that requires to be informed of alarm states. This configu-ration can be achieved through the use of a iPlex Web GUI.

All trap definition information for release before Release 3.0 can be found in the MEDIAPLEX-NOTIFICATIONS-MIB.

Trap reception applications can be written to receive and decode traps. Typical functions will generate and display color-coded alarms for display that indicate the severity of the condition that potentially just occurred. The information contained in any trap needs to be parsed to determine which port etc. is creating the trap. Version 1 notifications contain 3 simple elements:

• A Notification ID

• An Interface Name as a string.

• An Event details string.

Version 1 traps may or may not be paired: it may be that a trap can be generated for certain failures but no cancelling trap will be generated to indicate normal oper-ation as been restored. In these cases the software design may need to monitor other MIB variables in a device to determine that normal operation has been restored. Where traps do have clearing event to correctly link these paired traps, it will be necessary to parse and match the Interface Name for each.

These traps do not include within themselves any indication of severity so it will be up to the trap handler to determine what severity should be assigned to each of the traps a iPlex generates keeping in mind to parse, match and compare the Interface.

ASI Rx Sync Loss and Regained Notifica-tionsASI Sync Loss and Regained notifications can be used to indicate failures and recoveries. Although no severity is attached to the trap this is considered a major alarm in the newest version of traps in the iPlex, so as a suggestion anyone imple-menting these traps into an alarm handler may consider using a major severity as a start point. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

58


ASI Sync Loss Notification

ASI Sync Regained Notification

ATM Link Up and Down Notifications

ATM Link Up and Link Down notifications can be used to indicate failures andrecoveries. Although no severity is attached to the trap Link, Notifications inVersion 2 are considered major alarms in iPlex, so as a suggestion anyoneimplementing these traps into an alarm handler may consider using a majorseverity as a start point. Remember that it will be necessary to retrieve theinterfaceName field and parse the blade and port from this to track the portsthat go into alarm state and when they get a clear.

ATM Link Up Notification

Unique Trap OID Variable Binding OID Variable Name Syntax Value - Description

1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2

notifica-tionId

Integer 1 – Sync loss for an ASI Input Interface

1.3.6.1.4.1.3511.3.7.1.12.3

interface-Name

String String indicating the Interface that raised the trap

1.3.6.1.4.1.3511.3.7.1.12.4

eventDetails StringString detailing the problem


1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 24 – Sync Regained for an ASI

Input Interface

1.3.6.1.4.1.3511.3.7.1.12.3 interfaceNameString String indicating the Interface

that raised the trap

1.3.6.1.4.1.3511.3.7.1.12.4 eventDetails String String detailing the problem


1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 12 – generated when ATM link

is regained.




59


ATM Link Down Notification

Video NotificationsThere are 4 video notifications in Version 1 traps, 2 for the standard Encoder and 2 for the Advanced Encoder. The standard Encoder uses encoderVideoOk and encoderVideoRestart and while these are not serious alarms it may be useful to implement them into an alarm handler in some form of monitoring format, such that if an encoder were generating lots of Restart and Ok traps this would warrant looking into more deeply.

The Advanced Encoder uses advancedEncoderVideoOk and advancedEn-coderVideoLoss, clearly in this case the loss notification could be deemed a major alarm condition with the Advanced OK being a clear, while for a standard Encoder Restart could be a minor alarm with an OK being a clear. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

Encoder Video OK Notification


1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 11 – generated when ATM

card detects loss of link.





1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 13 – Generated when the

Encoder Video stream is ok




60


Encoder Video Restart Notification

Advanced Encoder Video OK Notification

Advanced Encoder Video Loss Notification

Encoder Start and Stop NotificationsThese 4 notifications are usually associated with Encoders and indicate when the device starts and stops, 2 of these apply to the standard Encoder and 2 apply to the Advanced Encoder. Care should be taken when using these as it is possible under Web GUI control to stop and start devices in general. Clearly if a user chooses to take such actio, it is not a real alarm state but merely the consequence of the action performed by the user.


1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 14 – Generated when an encoder video stream is restarted





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 20 – Generated when the Advanced Encoder Video stream is ok





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 21 – Generated when the Advanced Encoder Video stream is lost




61


In normal operation however it may prove useful to monitor for the stop notifica-tion, which is cleared by a start notification. As a start point therefore perhaps the default severity would be minor. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

Encoder Start Notification

Encoder Stop Notification

Advanced Encoder Start Notification


1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationId Integer 9 – Encoder started





1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationId Integer 10 – Encoder stopped





1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 33 – Advanced Encoder

started




62


Advanced Encoder Stop Notification

Buffering NotificationsSeveral buffer error notifications exist for ASI Out and encoder PMC modules. These notifications do not have cancelling events, but a monitoring system could use them to indicate possible error situations developing. In the Version 2 notifica-tion list these would be considered minor alarms.

ASI Transmit Buffer Underflow Notification

ASI Transmit Buffer Overflow Notification


1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 34 – Advanced Encoder

Stopped





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 6 – Generated when an ASI Out PMC detects a buffer underflow situation occurs





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 7 – Generated when an ASI Out PMC detects a buffer overflow situation occurs




63


Encoder Overflow Notification

Audio NotificationsThese 4 audio notifications are associated with Encoders and indicate when the device Audio is connected or disconnected. 2 of these apply to the standard Encoder and 2 apply to the Advanced Encoder. As a start point therefore perhaps the default severity would be minor. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

Encoder Audio Input Connected Notification

Encoder Audio Input Disconnected Notification


1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 15 – Generated when an Encoder PMC detects an overflow situation occurs





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 18 – Generated when an Audio Cable is connected to an Encoder





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 19 – Generated when an Audio cable is removed from an Encoder or when it is not installed at initialization




64


Advanced Encoder Audio Input Connected Notification

Advanced Encoder Audio Input Disconnected Notification

Encoder Sync NotificationThere is a single notification to indicate when an Encoder loses sync which would normally be determined a major alarm state. There is however no cancelling event although perhaps an Encoder Video OK trap might be used to clear the event. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

Link Down Notification


1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 22 – Generated when an Audio Cable is connected to an Advanced Encoder





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 23 – Generated when an Audio cable is removed from an Encoder or when it is not installed at initialization





1.3.6.1.4.1.3511.3.7.1.12

1.3.6.1.4.1.3511.3.7.1.12.2 notificationIdInteger 5 – Generated when an

Encoder loses sync




65


MCM CPU Temperature NotificationsIn Version 1 notifications, there are 2 traps to indicate that the temperature is Above or Within the normally expected range. In this instance an alarm handler could alarm on the Above alarm to a major state and clear on the reception of a Within event. Remember that it will be necessary to retrieve the interfaceName field and parse the blade and port from this to track the ports that go into alarm state and when they get a clear.

MCM CPU Temperature Above Notification

MCM CPU Temperature Within Notification


1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 29 – Generated when an MCM CPU Temperature goes Above what is considered normal for the device





1.3.6.1.4.1.3511.3.7.1.121.3.6.1.4.1.3511.3.7.1.12.2 notificationId

Integer 30 – Generated when an MCM CPU Temperature goes back Within what is considered a normal range for the device




66


iPlex Notification List

Notification/Values Description Suggested Severity

asiRxSyncLoss/1 Sync loss for an ASI Input Interface Major

newStdParsed/2 Generated when a new STD table is parsed Informa-tional

newPatParsed/3 Generated when a new PAT table is parsed Informa-tional

newPmtParsed/4 Generated when a new PMT table is parsed Informa-tional

encoderSyncLoss/5 Generated when a standard Encoder loses Sync Major

asiTxBufferUnderFlow/6 Generated whenever an ASIIn detects and buffer underflow condition exists

Minor

asiTxBufferOverFlow/7 Generated whenever an ASIIn detects and buffer overflow condition exists

Minor

portDeleted/8 Generated whenever a port gets deleted by the user or the system

Informa-tional

encoderStart/9 Generated whenever an Encoder is started Informa-tional

encoderStop/10 Generated whenever an Encoder stops Minor

atmLinkDown/11 Generated when an ATM module detects a loss of link

Major

atmLinkUp/12 Generated when an ATM module detects a link is up

Informa-tional

encoderVideoOk/13 Generated when an Encoder Video stream is OK

Informa-tional

encoderVideoRestart/14 Generated when an Encoder gets restarted Minor

encoderOverflow/15 Generated when memory buffer overflow con-ditions exist on an encoder

Minor

bladeUp/16 Generated after a blade is fully function and ini-tialized

Informa-tional

bladeDown/17 Generated whenever a blade goes down Major

encoderAudioInputConnected/18 Generated whenever the audio cable is detected on an encoder but not when the audio is in the composite SDI stream

Informa-tional

continued

67


Notification/Values Description Suggested Severity

encoderAudioInputDisconnected/19 Generated when no encoder audio cable is detected which will occur at initialization if the encoder is using an SDI connect with embed-ded audio

Minor

advancedEncoderVideoOk/20 Generated when an advanced encoder video stream is OK

Informa-tional

advancedEncoderVideoLoss/21 Generated whenever an advanced encoder video stream is lost

Major

advancedEncoderAudioConnected/22

Generated whenever the audio cable is detected on an advanced encoder but not when the audio is in the composite SDI stream

Informa-tional

advancedEncoderAudioDiscon-nected/23

Generated when no advanced encoder audio cable is detected which will occur at initializa-tion if the advanced encoder is using an SDI connect with embedded audio

Minor

asiSyncRegained/24 Generated when sync is detected at an ASI Input

Informa-tional

fanBank1Failure/25 Generated whenever a failure is detected in an iPlex for fan bank 1

Major

fanBank1OK/26 Generated when an iPlex fan bank 1 is OK Informa-tional

fanBank2Failure/27 Generated whenever a failure is detected in an iPlex for fan bank 2

Major

fanBank2OK/28 Generated when an iPlex fan bank 2 is OK Informa-tional

mcmCpuTemperatureAbove/29 Generated when the MCM temperature goes above a predefined setting

Major

mcmCpuTemperatureWithin/30 Generated when the MCM temperature goes back within normal operating parameters

Informa-tional

lowerCarrierPulledOut/31 Generated when the lower carrier in an iPlex is removed the iPlex will however reboot

Major

upperCarrierPulledOut/32 Generated when the upper carrier in an iPlex is removed the iPlex will however reboot

Minor

advancedEncoderStart/33 Generated whenever an Advanced Encoder is started

Informa-tional

advancedEncoderStop/34 Generated whenever an Advanced Encoder stops

Minor

68


Mediaplex and iPlex Notification Version 2 (Trap) Definition and Usage (Release 3.0 or Later)

This section covers iPlex software Version 3.0 or later. iPlex generates SNMP traps to inform external devices about changes in operational conditions and con-figuration of a device. The following section discusses each and every trap.

To be able to receive the traps, the user must configure a trap destination for each system monitoring tool that requires to be informed of alarm states. This configu-ration can be achieved through the use of an iPlex Web GUI.

Trap reception applications can be written to receive and decode traps. Typical functions will generate and display color-coded alarms that indicate the severity of the condition that potentially can occur. The information contained in any trap links directly to a device, blade and module; in some cases this also includes traps for logical elements. It is up to the developer of a system to determine which traps are kept and which are discarded; obviously, clearing traps to alarms are of use while other informational traps may be discarded as irrelevant to monitoring sys-tems. This section will concentrate on those notifications that may be worth mon-itoring and reacting to.

The simplest form of trap handler could receive all traps and generate messages based on the traps severity without regard for clearing traps that might arrive leav-ing the deletion and clearing of the alarm messages to be done by the user manu-ally.

A more sophisticated trap-receiving system might want to try to correlate alarm notifications with their clearing event. The remainder if this section will link together the alarm notifications and their clearing events even for the escalating alarm notifications that exist.

OK and Failure NotificationsShould failures be detected by iPlex operational software, then a Major Failure Notification will be issued to all configured trap destinations. For each failure that occurs, an OK Notification will be issued to clear the original failure.

NOTEIt is also possible through the Web GUI to configure the actualseverity of each trap. Whether specific traps are discarded orforwarded, t is entirely the responsibility of the network operator.

69


OK Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 1 – Module is okay

1.3.6.1.4.1.3511.3.7.1.42.3

sequence-Number

Integer Trap sequence number

1.3.6.1.4.1.3511.3.7.1.42.4

moduleType Integer Module type

1.3.6.1.4.1.3511.3.7.1.42.5

slotNumber Integer Slot number where module is located

1.3.6.1.4.1.3511.3.7.1.42.6

unitNumber Integer Unit number for indicated slot

1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber

Integer Additional port information for unit

1.3.6.1.4.1.3511.3.7.1.42.8

description String Textual description of this trap

1.3.6.1.4.1.3511.3.7.1.42.9

severity Integer Informational – Trap severity

70


14

Failure Notification


.3.6.1.4.1.3511.3.7.1.2

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2 – Module has failed

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNumber Integer Additional port information for unit

1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9

severity Integer Major – Trap severity

71


Up and Down NotificationsDown notifications are generated for modules when they have been rebooted or removed while the clearing OK will be generated when a module is detected in a chassis. Down is a minor notification by default.

Up Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 3 – Module detected in chas-sis

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


72


Down Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 4 – Module has been removed or rebooted

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNumber Integer Additional port informa-tion for unit

1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9

severity Integer Minor – Trap severity

73


Inserted and Removed NotificationsThese 2 notifications are specifically targeted at blades. When a blade is detected in a chassis an INSERTED notification will be generated while a REMOVED notifi-cation will be generated after a blade is removed or disappears from a chassis. By default both of these notifications are Informational, polling managers and trap receivers could however determine that a REMOVED trap be treated with a higher severity or indeed use the Web GUI to change the severity permanently. Obviously an INSERTED could be used as a clearing event, however it may be worth reading the Blade Status Polling MIB Parameters on page 54 to verify that a newly inserted blade is of the same type as the original blade that was removed.

Inserted Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 5 – Module has been inserted

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


74


Removed Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 6 – Module has been removed

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


75


1

1.2

Video NotificationsThere is a group of 3 notifications directly related to Video signals that could be used by an alarm monitoring system: these are Video OK, Video Start, and Video Loss. Should a monitoring system need these, then the Video OK and Video Start notifications can be taken to be cancelling events to Video Loss notifications.

Video OK Notification

Video Start Notification

Unique Trap OID Variable Binding OID


.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2 notificationId Integer 7 – Module detected in chassis

1.3.6.1.4.1.3511.3.7.1.42.3 sequenceNumber Integer Trap sequence number

1.3.6.1.4.1.3511.3.7.1.42.4 moduleType Integer Module type

1.3.6.1.4.1.3511.3.7.1.42.5 slotNumber Integer Slot number where module is located

1.3.6.1.4.1.3511.3.7.1.42.6 unitNumber Integer Unit number for indicated slot

1.3.6.1.4.1.3511.3.7.1.42.7 subSlotNumber Integer Additional port information for unit

1.3.6.1.4.1.3511.3.7.1.42.8 description String Textual description of this trap

1.3.6.1.4.1.3511.3.7.1.42.9 severity Integer Informational – Trap severity


3.6.1.4.1.3511.3.7.1.4

1.3.6.1.4.1.3511.3.7.1.42.2


1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


76


14

Video Loss Notification


.3.6.1.4.1.3511.3.7.1.2

1.3.6.1.4.1.3511.3.7.1.42.2


1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


77


Start and Stop NotificationsThese 2 notifications are usually associated with encoders and indicate when the device starts and stops. Care should be taken when using these as it is possible under Web GUI control to stop and start devices in general. Clearly if a user chooses to take such action it is not a real alarm stat, but merely the consequence of the action performed by the user. In normal operation however it may prove useful to monitor for the stop notification, which is cleared by a start notification.

Start Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 12 – Module has been started

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


78


Stop Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 13 – Module has been stopped

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


79


Sync NotificationsSync OK clears a Sync Loss notification, and the 2 notifications are important for monitoring ASI Input modules as one of the few ways to detect a problem that may be occurring on an ASI Input. Whenever Sync is Lost, this could be a prob-lem with either the equipment that feeds the ASI Input module or the module itself making it worthwhile for monitoring and alarming on.

Sync OK Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 14 – Module Sync Ok

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9

severity Integer Informational – Trap sever-ity

80


Sync Loss Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 15 – Module Sync Loss

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


81


Buffering NotificationsBuffer problems usually occur when a device is overwhelmed with data and cannot keep up. In the normal scheme of things, the problem usually clears up or perhaps is a sign of worse things to come. In the iPlex devices these notifications are set to the minor severity level. If a Buffer Underflow occurs, it will be cleared by a Buffer OK when conditions return to an optimum state for normal data flow. Buffer OK is also used to clear a Buffer Overflow condition. It is not possible to go from a Buffer Underflow state to a Buffer Overflow state without passing through the Buffer OK state.

Buffer Underflow Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 16 – Module buffer under-flow

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


82


Buffer Overflow Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 17 – Module buffer overflow

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


83


Buffer OK Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 18 – Module buffer Ok

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


84


Audio NotificationsThese notifications apply to the audio input port found on encoders and are gener-ated whenever the audio cable is connected or removed. So clearly Audio Discon-nected is cleared by an Audio Connected notification. If a system is running with embedded audio signals, the value of monitoring these notifications is reduced.

Audio Connected Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 19 – Module Audio Con-nected

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


85


Audio Disconnected Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 20 – Module Audio Discon-nected

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


86


Link NotificationsHere a Link Up notification clears a Link Down notification.

Link Down Notification

Unique Trap OIDVariable Binding

OIDVariable

Name Syntax Value - Description

1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 21 – Module Link Down

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


87


Link Up Notification


1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 22 – Module Link Up

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


88


CPU Temperature NotificationsThere are 3 notifications in this group. Typically the temperatures are read directly from the CPU, and whenever they reach a set warning level, the Warning notifica-tion will be generated. If the CPU then falls back to a nominal operating tempera-ture, a clearing OK notification will be sent. If however the temperature continues to rise and hits the Critical level, a Critical notification will be sent. If then the tem-perature begins to drop, the clearing notification will actually be a Warning notifi-cation to reiterate the fact that a CPU is still in warning state and then an OK would be sent when the normal operating temperature is reached. The users who monitor these functions might need to be aware that the Intel CPUs used in our devices may in fact shut down with excessive overheating and a unit will stop working completely. In this case there will be no clearing notifications sent, and either the users would need to manually remove the temperature alarms after the system comes back online or the monitoring software needs additional routines to be able to group alarms and generate probable causes.

CPU Temperature OK Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2000 – Module CPU Tem-perature Ok

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


89


CPU Temperature Warning Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2001 – Module CPU Tempera-ture Warning

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


90


CPU Temperature Critical Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2002 – Module CPU Tem-perature Critical

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


91


CPU Utilization NotificationsThere are 3 notifications in this group. If the CPU Utilization goes to the warning level then falls back to a nominal, a clearing OK notification will be sent. If how-ever the utilization continues to rise and hits the Critical level, a Critical notifica-tion will be sen. If then the utilization begins to drop, the clearing notification will actually be a Warning notification to reiterate the fact that a CPU is still in warning state and then an OK would be sent when the normal operating level is reached. The users who monitor these functions might need to be aware that if the CPU stays at critical levels for too long, there is the possibility that a CPU may reboot and software gets totally reloaded in which case clearing notifications will not be generated. In this case either the users would need to manually remove the utiliza-tion alarms after the system comes back online or the monitoring software needs additional routines to be able to group alarms and generate probable causes.

CPU Utilization OK Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2003 – Module CPU Utiliza-tion Ok

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


92


CPU Utilization Warning Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2004 – Module CPU Utili-zation Warning

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9 severity Integer Minor – Trap severity

93


CPU Utilization Critical Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 2005 – Module CPU Utiliza-tion Critical

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


94


Memory Utilization NotificationsThere are 3 notifications in this group. If the Memory Utilization goes to the warn-ing level and then falls back to a nominal, a clearing OK notification will be sent. If however the utilization continues to rise and hits the Critical level, a Critical notifi-cation will be sen. If then the utilization begins to drop, the clearing notification will actually be a Warning notification to reiterate the fact that the memory utiliza-tion is still in warning state, and then an OK would be sent when the normal oper-ating level is reached. The users who monitor these functions might need to be aware that if the memory utilization stays at critical levels for too long, there is the possibility that a CPU may reboot and software gets totally reloaded in which case clearing notifications will not be generated. In this case either the users would need to manually remove the utilization alarms after the system comes back online or the monitoring software needs additional routines to be able to group alarms and generate probable causes.

Memory Utilization OK Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 3000 – Module Memory Utilization Ok

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9

severity Integer Informational – Trap sever-ity

95


Memory Utilization Warning Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 3001 – Module Memory Utilization Warning

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


96


Memory Utilization Critical Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 3002 – Module Memory Uti-lization Critical

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


97


Redundancy Flip NotificationThis notification has no cancelling event and is generated to indicate that redun-dant blades have swapped roles from backup to primary. Whenever this occurs, it is worth indicating this to a user as it informs that something went wrong with the pairing blade and that perhaps more investigation is required.

Redundancy Flip Notification



1.3.6.1.4.1.3511.3.7.1.42

1.3.6.1.4.1.3511.3.7.1.42.2

notificationId Integer 4000 – Module has flipped from

1.3.6.1.4.1.3511.3.7.1.42.3

sequenceNum-ber


1.3.6.1.4.1.3511.3.7.1.42.4


1.3.6.1.4.1.3511.3.7.1.42.5


1.3.6.1.4.1.3511.3.7.1.42.6


1.3.6.1.4.1.3511.3.7.1.42.7

subSlotNum-ber


1.3.6.1.4.1.3511.3.7.1.42.8


1.3.6.1.4.1.3511.3.7.1.42.9


98


iPlex Notification List

Notification/Value Description Default Severity

OK/1 A module is OK Informational

Failure/2 A module entered a failure mode Major

Up/3 A module has been detected in the chassis Informational

Down/4 A module has removed from a chassis or reboo-ted

Minor

Inserted/5 A blade has been inserted into a chassis Informational

Removed/6 A blade has been removed from a chassis Informational

Video OK/7 A module detects Video OK Informational

Video Start/8 A module detects that Video Started Informational

Video Loss/9 A module detects that Video Stopped Major

Port Created/10 A port has been created Informational

Port Deleted/11 A port has been deleted Informational

Start/12 A module has started Informational

Stop/13 A module has stopped Major

Sync OK/14 A module has detected gain of sync Informational

Sync Loss/15 A module has detected loss of sync Major

Buffer Underflow/16 A buffer underflow problem has been detected Minor

Buffer Overflow/17 A buffer Overflow has been detected Minor

Buffer OK/18 The buffer system has returned to normal Informational

Audio Connected/19 The Audio input has been connected to a mod-ule

Informational

Audio Disconnected/20 The Audio input has been disconnected from a module

Minor

Link Down/21 A module has detected a Link Down state Major

Link Up/22 A module has detected a Link Up state Informational

New STD Parsed/1000 A new STD table was detected and Parsed No longer gener-ated

New PAT Parsed/1001 A new PAT table was detected and Parsed No longer gener-ated

New PMT Parsed/1002 A new PMT table was detected and Parsed No longer gener-ated

continued

99


Notification/Value Description Default Severity

CPU Temperature OK/2000

A modules CPU Temperature is OK Informational

CPU Temperature Warn-ing/2001

A modules CPU Temperature has reached the Warning level

Minor

CPU Temperature Criti-cal/2002

A modules CPU Temperature has reached the Critical level

Major

CPU Utilization OK/2003 A modules CPU Utilization is OK Informational

CPU Utilization Warning/2004

A modules CPU Utilization has reached the Warning level

Minor

CPU Utilization Critical/2005

A modules CPU Utilization has reached the Critical level

Major

Memory Utilization OK/3000

A modules Memory Utilization is OK Informational

Memory Utilization Warning/3001

A modules Memory Utilization has reached the Warning level

Minor

Memory Utilization Criti-cal/3002

A modules Memory Utilization has reached the Critical level

Major

Redundancy Flip/4000 A redundancy flip between redundant blades has occurred.

Major

100


Performance MonitoringPerformance monitoring though SNMP requires a user to be completely familiar with MEDIAPLEX MIB files as they contain many parameters that perhaps user would like to monitor.

Polling frequencies can be set by the user within the chosen software package used for the data collection. A good starting interval for polling would be 30 seconds. Care should be exercised here as polling too often may put an excessive load onto a system performing normal management operations.

Simple monitoring of SNMP MIB parameters usually involves reading specific parameters and storing for later use by graphing utilities the most appropriate parameters being bit rate and packet count entries.

More complex monitoring functions with threshold triggers could monitor error counters, and temperature and voltage variables; when thresholds are crossed, they generate alarm messages to the user.

In all cases and depending on the specifics of what is being monitored, a user will need minimum the blade and unit number for individual MIB table entries to be able to collect the data.

Other tables, specifically the Transport Streams MIB will also require a Port Type and PID entries as index values.

So to do any form of Performance monitoring, the user must first determine the current configuration of a system and most likely use a MIB Browser to discover what entries exist, and from this information create the performance polling data collection configurations.

One possible monitoring point would be the rateBps variables found in the MEDIAPLEX-TS-STATS-MIB file. Transport Stream Rate Parameter

ExamplesTo clarify how to track the data flowing through various port types, a few exam-ples are given below.

Encoder VideoData Monitoring

During the installation and commissioning of any system, all Transport Streams and Programs will be configured and routed, and the PID values may be defaulted as configured by the system or set by the user. In either case once the system is commissioned, it is reasonable to expect from an encoder point of view that values will not change once deployed.

MIB/Unique Table OID

Variable Binding OID


1.3.6.1.4.1.3511.3.7.1.15.1.1

1.3.6.1.4.1.3511.3.7.1.15.1.1.9

rateBps Guage32

This is the current rate that a specific PID is being received at.

101


So let us assume for this example that an encoder has been installed on blade 3 and occupies PMC position 2 out of the 4 available. The Program to be monitored is “1” and the video PID associated with this program is 0x12c hex or 300 decimal.

Now if you look at the MEDIAPLEX-ENCODER-MIB, you will quickly dis-cover that there are no rate variables that could be used for monitoring purposes, – so where are they? The answer is that they are located in the MEDIAPLEX-TS-STATS-MIB.

Two methods are available for monitoring an encoder port. The first might be to look for stop and start traps that are generated whenever the encoder stop or starts reception occurs.

The second might be to monitor the video receive rate through SNMP control and have the ability to alarm a monitoring system when the rate falls below some con-figured threshold. This example does not recommend any specific tool for per-forming the monitoring function; it can merely indicate how to target the variables required to successfully monitor a parameter.

To completely understand how to monitor the rateBps parameter it is necessary to understand the MEDIAPLEX-TS-STATS-MIB and SNMP. For this example, a section of the table is included here: Base syntax: TsStatsInfoEntryComposed syntax: TsStatsInfoEntryStatus: currentMax access: not-accessibleSequences: 1: portType - INTEGER(2 - int, int32) 2: bladeNumber - INTEGER(2 - int, int32) 3: unitNumber - INTEGER(2 - int, int32) 4: pid - INTEGER(2 - int, int32) 5: portName - DisplayString(4 - octets) 6: packetsProcessed - Counter32(65 - cntr32) 7: duplicatePackets - Counter32(65 - cntr32) 8: continuityCountErrors - Counter32(65 - cntr32) 9: rateBps - Gauge32(66 - gauge32)Indexes: 1: portType 2: bladeNumber 3: unitNumber 4: pid

Description: Information about a specific PID associated withan interface.

The above is a single entry in the table and the possible parameters that can exist therein.

You will notice that 4 of the parameters are index values and this means that they need to be given explicitly when targeting specific entries, and this is what we will do for this example.

In the example we know: the bladeNumber = 3, the unitNumber = 2, then we can get the video PID from the Web GUI – in this example it was found to be 0x12C but as an index, it must be specified in decimal which is 300. Now we need to find the portType value – all portType definitions can be found in the MEDIAPLEX-TC file, so for an encoder the portType = 6.

102


Now the polling system needs to be set to perform an SNMP GET for the correct parameter from the table. The assumption here is that the value must exist because this is a normally operational encoder.

Given the above information, it is possible to form a “targeted” GET request to read the full OID which now becomes:

rateBps.portType.bladeNumber.unitNumber.pid

Or

1.3.6.1.4.1.3511.3.7.1.15.1.1.9.portType.bladeNumber. unitNumber.pid

Or in this example:

1.3.6.1.4.1.3511.3.7.1.15.1.1.9.6.3.2.300

Now what remains is to set a threshold below which, as can be assumed, the input is nolonger present and should be alarmed to the system operator. Obviously, the pollingmechanism should also have a method to clear any alarm when data is seen to go abovethe threshold again.

Care should be exercised when reading MIB parameters as the dynamic nature ofMediaplex MIB data means that if the module stops, the program/stream will be deleted.Thus there are actually 2 possible results to the GET request: the first is that a valid valueis returned and that it merely slows down, the second is that perhaps the port/program/stream goes away in which case an error or no response will be returned, and the pollingroutine must be able to handle this.

This very same method could be used to target an advanced encoder, in this casehowever the portType = 16.

ASIIn and ASIOutVideo Monitoring

Both ASIIn and ASIOut modules can be monitored in the exact same way as in the encoder example above, the main difference being that ASI ports tend to be MPTS streams meaning that there are more programs to choose from. In this case other options present themselves from a monitoring point of view.

First, a port could be monitored for activity by selecting a single program and alarming when the video rate falls. For an ASIIn port, the user could also track SYNC LOSS traps as they indicate a problem for the port.

Second, it may be that the normal operation is handled through traps and perhaps specific programs, and PID values are monitored because a user is having prob-lems with these specifically within the MPTS.

Finally some users may actually monitor programs and retain the throughput rates for future use by graphing tools.

Whichever type of monitoring is chosen, the requirements are still the same when forming the index and the portType for ASIIn =5 and ASIOut = 11.

Monitoring OtherPorts Video Data

Clearly it is now possible to monitor ALL ports using the key technique: forming the correct index. When forming index values for hardware modules, the unit-Number is more easily understood and determined. For logical ports, the user must use the Web GUI to discover the ports of interest. It is possible for multiple UDP In or Out or Transrater In or Out to be created on a single blade, all being depen-

103


dent on other configurable parameters. It is therefore essential for a user to find the explicit entry to be monitored.

Port Types

Monitoring Usingthe PORTS MIB

The iPlex has another MIB that may prove useful as a monitoring point, and this is the MEDIAPLEX-PORTS-MIB. This MIB contains a total rateBps variable for an entire port, thus now it is not necessary to find a PID to form an index. The user merely needs the portType, portBladeNumber and portUnitNumber to form the correct index. The definition of the table’s entry is: Base syntax: PortsInfoEntryComposed syntax:PortsInfoEntryStatus: currentMax access: not-accessibleSequences: 1: portType - INTEGER(2 - int, int32) 2: portBladeNumber - Integer32(2 - int, int32) 3: portUnitNumber - Integer32(2 - int, int32) 4: portName - DisplayString(4 - octets) 5: portDescription - DisplayString(4 - octets) 6: portOnline - MediaPlexTruthValue(2 - int, int32) 7: portState - INTEGER(2 - int, int32) 8: packetizerType - INTEGER(2 - int, int32) 9: associatedPort - DisplayString(4 - octets)

Port Type Value

tcpIn 1

udpIn 2

rtpIn 3

atmIn 4

asiIn 5

encoder 6

fileIn 7

udpOut 8

rtpOut 9

atmOut 10

asiOut 11

backhaul 12

xraterIn 14

xrateOut 15

advEncoder 16

xcoderIn 18

xcoderOut 19

104


10: rateBps - Gauge32(66 - gauge32)Indexes: 1: portType 2: portBladeNumber 3: portUnitNumber

Description: Information about specific ports.

The parameter of interest here is again rateBps but has a different OID, see table that follows.

Ports MIB Rate Parameter

So for this parameter we would need to form an index as follows:

1.3.6.1.4.1.3511.3.7.1.40.1.1.10.portType.bladeNumber. unitNumber

Using the Encoder example above the index would become: -

1.3.6.1.4.1.3511.3.7.1.40.1.1.1.6.3.2

Other MonitoringPoints

There are several other points that could be monitored by a pooling system either for errors or normal throughput, the reader is directed to the following MIB files:MEDIAPLEX-UDPOUT-MIB

MEDIAPLEX-ATM-MIB

MEDIAPLEX-GE-MIB

MEDIAPLEX-TCPIN-MIB

MEDIAPLEX-BACKHAUL-MIB

All of these MIB definitions contain various counter variables that could be polled for both throughput and error information. The user should consult these MIB definitions for index requirements, obviously each MIB may be slightly different but the technique described above will still be valid.

MIB/Unique Table OID Variable Binding OID Variable

Name Syntax Value - Description

1.3.6.1.4.1.3511.3.7.1.40.2.1

1.3.6.1.4.1.3511.3.7.1.40.2.1.1.10

rateBps Guage32 This is the current rate that a specific PID is being received at.

105


106

Index
Aaccounting management 38Advanced Encoder
MIB 35afInfoTable 29alarms 33architecture 15ASIIn 24ASIOut 24asiOutCATInfoTable 25ATM 33ATM Routes 34ATMIn 31ATMOut 32authentication 19AVC encoder 37

Bbackhaul 35beInfoTable 30

Cchassis 32conceptual rows 17

creating 18deletion 18instance identifier 18

config file MIB 36configuration 20configuration example 21configuration management 38creating conceptual rows 18

Ddefining SNMP 15DES encryption 19description for MIBs 21descriptors 35documentation - other 10

EefInfoTable 29

element 27encoder 25encoder audio 34encryption

DES 19

Ffault management 38FILEIn 33fileInInfoTable 33formats 16

GGE 33graphs and historical data 47

HHP Openview

accounting management 38configuration management 38fault management 38get list of components 45graphs and data 47intro 38inventory report 45monitoring a specific chassis 41monitoring chassis 40network interface properties 46opening the Web GUI 42performance management 39SNMP browser for specific chassis 44standard option menu 41system alarms 47

Iinstance identifier 18inventory report 45IP Route 31

Llist of components using HP Openview 45

Beta Beta

107


log MIB 36

MmacInfoTable 33messages 17MIB

Advanced Encoder 35alarms 33ASIIn 24ASIOut 24ATM 33ATM Routes 34ATMIn 31ATMOut 32AVC encoder 37backhaul 35chassis 32compiling in network management appli-

cations 22config file 36description and references 21element 27encoder 25encoder audio 34Enterprise 24FILEIn 33GE 33IP Route 31list of supported 23log 36MPE Routes 34notification 28notification log 36notificationv2 36ports 36program 26Program Route 28Redundancy 32root 22RTPIn 31RTPOut 31SCM 34sensors 32SMD 32SME 28

SNMP 36software 25spanning tree 36stream route 28TCPIn 35TS Stats 31UDPIn 27UDPOut 26user-created descriptors 35VLAN Management 25Xrater 33XrtrIn 35XrtrOut 35

monitoring a specific chassis using HPOpenview 41monitoring chassis using HP Openview 40MPE Routes 34

Nnetwork interface properties 46notification 28notification log MIB 36notificationv2 MIB 36

Pperformance management 39ports MIB 36privacy 19private descriptors 35program 26Program Route 28

RRedundancy 32references for MIBs 21root MIB 22RTPIn 31RTPOut 31

SSCM 34sensors 32

Beta Beta 108


SMD 32smdInfoTable 32SME 28SNMP

architecture 15concept row creation 17conceptual row creation 17definition 15formats 16messages 17row creation 17transmission of messages 16v3 authentication 19v3 configuration 20v3 configuration example 21v3 privacy 19v3 quick overview 19v3 users 20v3 views 21

SNMP browser for chassis using Openview44SNMP message

transmitting 16SNMP MIB 36SNMP specifications 15software 25spanning tree MIB 36specifications for SNMP 15standard option menu 41stream route 28system alarms 47

TTCPIn 35tech support

checklist 11overview 11

transmitting an SNMP message 16TS Stats 31

UUDPIn 27UDPOut 26user-created descriptors 35

users 20

Vviews 21VLAN Management 25

WWeb GUI for HP Openview 42

XXrater 33XrtrIn 35XrtrOut 35

109


Beta Beta 110

Documents

iPlex Version 5.0 SNMP Guide