Iplex Version 5.0 SNMP Guide

112-0116-02 Rev A
REFERENCE GUIDE Network Management & Monitoring iPlex Software Version 5.0
iPlex
www.tandbergtv.com
May, 2009
Published By TANDBERG 455 DeGuigne Drive Sunnyvale, CA 94085-3890 Copyright 1998-2007 by TANDBERG Television. All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Technical Publications: Lena Jacobson TANDBERG Television Engineering Department Restricted Rights This document contains proprietary and confidential information of TANDBERG Television. The contents of this document may not be disclosed to third parties, copied or duplicated in any form, in whole or 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 set forth in subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.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 is TANDBERG Television, 455 DeGuigne Drive, Sunnyvale, CA 94085-3890, USA. TANDBERG is a registered trademark of TANDBERG Television. All other names are trademarks of their respective owners. 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. GoAhead Software Licence Dolby Digital Trademark License Copyright 2001 GoAhead Software, Inc. All Rights Reser ved. Unless GoAhead otherwise instructs, the year 2001 is to be replaced with the year during which the release of the Original Code containing the notice is issued by GoAhead. If this year is not supplied with Documentation, GoAhead will supply it upon request. Dolby Laboratories encourages use of the Dolby Digital trademark to identify soundtracks that are encoded in Dolby Digital. This is an effective way to inform listeners of the soundtrack format, and the use of a standard logo promotes easy recognition in the market place. However, like any trademark, the Dolby Digital logo may not be used without permission. Dolby Laboratories therefore provides a standard trademark license agreement for companies who wish to use Dolby trademarks. This agreement should be signed by the company that owns the program material being produced. Recording studios or production facilities which provide audio production or encoding services for outside clients generally do not require a trademark license. If you would like more information on obtaining a Dolby trademark license, please contact Dolby Laboratories Licensing Corporation. Information on trademark licensing plus instructions for using the Dolby Digital trademark 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: tsa@dolby.com, http://www.dolby.com Technical Support For technical support, contact TANDBERG Television Customer Support through the World Wide Web (www.tandbergtv.com/services/skysupport_request.asp), via e-mail (fieldservice_americas@tandbergtv.com) or the Hot Line 1-877-475-9787. Document Number: 112-0116-02 Rev A
Contributors
Agency Compliance 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: 21CRF1040 Emissions: FCC Part 15 Class A, CISPR 22 Class A, EN55022 Class A, AS/NZ 3548 Immunity: 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-2 Telcordia: GR-63-CORE, GR-1089-CORE, SR-3580 NEBS Level 3 ETSI: EN300-019-1-1, EN300-019-1-2, EN300-019-1-3, EN300-132, EN300-386-2 TANDBERG Television iPlex equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at personal expense. 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 core H05VVF3G075 cord that has a minimum 0.75 square mm diameter conductors, provided with an IEC 320 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.
FCC Class A Compliance
Important Safety Information!
Power Cords The plug on the power supply cords are considered to be the equipment disconnect device and must be 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.
System Specifications
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
Contents
Cover, Notices, and Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Chapter 1: Introducing TANDBERG Television iPlex . . . . . . . . . . . . . . . . . . . . . 9
Introduction to the Network Management & Monitoring Guide . . . . . . 10 Other iPlex Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Contacting TANDBERG Television Customer Support . . . . . . . . . . . . . 11 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Support Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2: Network Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 13
Introduction to SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 SNMP-Related Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Network Management Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . 15

SNMP Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 SNMP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Conceptual Row Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Selecting an Instance-Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Creating the Conceptual Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Creating and Activating the Conceptual Row . . . . . . . . . . . . . . . . . . . . . . . . . 18
Conceptual Row Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
SNMPv3 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMPv3 Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMPv3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMPv3 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMPv3 Configuration and Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 19 20 20 21 21
SNMP MIB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Compiling MIBs in Network Management Applications . . . . . . . . . . . . . . . . . . . . . . 22
ROOT MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
MIBs supported on iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
iPlex Enterprise MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Mediaplex ASIIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Mediaplex ASIOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Mediaplex Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Mediaplex VLAN Management MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
iPlex Network Management & Monitoring Reference Guide
Mediaplex Software MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Mediaplex Program MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Mediaplex Element MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Mediaplex UDPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Mediaplex Program Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Mediaplex Stream Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Mediaplex Notification MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Mediaplex SME MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Mediaplex IP Route MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Mediaplex TS Stats MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Mediaplex RTPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Mediaplex RTPOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Mediaplex ATMIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Mediaplex ATMOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mediaplex Redundancy MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mediaplex Sensors MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mediaplex Chassis MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mediaplex SMD MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Mediaplex ATM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mediaplex FILEIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mediaplex GE MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mediaplex Alarms MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mediaplex Xrater MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Mediaplex SCM MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Mediaplex Encoder Audio MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Mediaplex ATM Routes MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Mediaplex MPE Routes MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Mediaplex TCPIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex Backhaul MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex XrtrIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex XrtrOut MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex Descriptors MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex Advanced Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Mediaplex Ports MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Spanning Tree MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Notificationv2 MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Log MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Config File Mgmt MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Notification Log MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 SNMP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 License MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 FileE Management MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Media Processor MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Security MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 xCoderIn MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 xCoderOut Mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 AVC Encoder MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 AVC xCoder In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 AVC xCoder Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Introduction to HP OpenView Integration . . . . . . . . . . . . . . . . . . . . . . . 38 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 TANDBERG Television HP OpenView Plug-in Components . . . . . . . . . 39 Monitoring iPlex from HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Monitoring a Specific iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Option Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening the Web GUI for HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Launching an SNMP Browser for a Specific iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . Obtaining a List of iPlex Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Graphs and Historical Data Gathering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 41 42 44 45 45 46 47 47
Appendix A: Monitoring iPlex Using SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 IP Address Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Basic Status Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Advanced Status Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Detecting Redundancy Flips between SCM Blades . . . . . . . . . . . . . . . . . . . 53 Monitoring Blade Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Active Alarm Table Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 ASI Rx Sync Loss and Regained Notifications . . . . . . . . . . . . . . . . . . . . . . . 58 ATM Link Up and Down Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Video Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Encoder Start and Stop Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Buffering Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Audio Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Encoder Sync Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 MCM CPU Temperature Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Mediaplex and iPlex Notification Version 2 (Trap) Definition and Usage (Release 3.0 or Later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
OK and Failure Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Up and Down Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inserted and Removed Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Video Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start and Stop Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sync Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Buffering Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU Temperature Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPU Utilization Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory Utilization Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redundancy Flip Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69 72 74 76 78 80 82 85 87 89 92 95 98
Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Encoder Video Data Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASIIn and ASIOut Video Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Other Ports Video Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Using the PORTS MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Monitoring Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 103 103 104 105
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Chapter 1
Introducing TANDBERG Television iPlex
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 Guides

In 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. CLI basics, conventions, and connection method. Command definitions. Show commands and Config commands. Hardware specifications. Basic concepts. Configuration scenarios. Web interface features and functions. Port configuration and statistics. Redundancy.
Command Line Interface Reference Guide, for information on

Web Interface User Guide, for information on

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 support 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 message and you will be contacted during regular business hours (see the Support Check List).
Contact Information
E-mail: Web: fieldservice_americas@tandbergtv.com http://www.tandbergtv.com/contactingsupport.ink
Support Check List

When contacting Customer Support, please provide the following information:
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?
11
12
Chapter 2
Network Management and Monitoring
13
Overview
TANDBERG Television iPlex video services router provides three ways for monitoring 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 standard web browser. However, the web interface cannot manage or configure multiple 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. TANDBERG Television provides the necessary software for integration with HP OpenView 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 SNMP
Simple Network Management Protocol (SNMP) is a widely used network monitoring and control protocol that passed data from SNMP agents to the management 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 standard 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 Specifications
RFC 1155 May 1990Structure 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 Management of TCP/IP-based Internets: MIB-II RFC 1155 May 1990 Definition of Managed Objects for the Ethernet-like Interface Types
Network Management Protocol Architecture

The 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 acknowledged 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 variables. Three general operations may be performed on scalar objects:
SNMP Formats
Get A management station retrieves a scalar object value from a managed station. 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.
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 number, 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 of an SNMP Message
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 and destination address and a community name. It then performs any encryption or 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 basic encoding.
NOTE In practice, authentication is rarely used.
16
SNMP Messages
Field version community Description SNMP version (RFC 1157 is version 1.) An SNMP agent paired with some arbitary set of SNMP application entities. NOTE The community name acts as a password to authenticate the SNMP message. Provides a unique ID to distinguish between outstanding requests. Indicates an exception occurred while processing a request. Values are as follows: noError (0), tooBig (1), noSuchName (2), badValue (3), readOnly (4), genErr (5) When error-status is nonzero, it may provide what variable caused an exception. NOTE A variable is an instance of a managed object. variablebindings A list of variable names and corresponding values. NOTE In some cases, such as GetRequest PDU, the values are null. enterprise agent-addr generic-trap A type of object generating trap; based on sysObjectID. The address of object generating 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). A specific trap code. Time elapsed between the last (re)initialization of the network entity and the generation of the trap; contains the value of sysUpTime. SNMP views management information as variables and their values. SNMP operations retrieve or modify the value of objects. A class or type of management information 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.
request-id error-status
error-index
specific-trap time-stamp
Conceptual Row Creation
17
Selecting an Instance-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 integer-valued SYNTAX clause might be defined for such a purpose, allowing a management 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 the Conceptual Row Creating and Activating the Conceptual 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. 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 stations knowledge of the agents capabilities, this determination can be made locally by the management 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 information 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 implementationspecific 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 operation fails with an error of inconsistentValue.
Conceptual Row Deletion
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 DES encryption. 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 security 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.
SNMPv3 Authentication
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 users authentication password 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 fingerprint 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 algorithms: 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 message. The encryption algorithm used is the CBC-DES Symmetric Encryption Protocol. An NMS converts the users privacy password to a secret key. This secret key is used to generate an initialization vector which is used to encrypt/decrypt the message data. This vector is stored in the SNMP message header. When the SNMP agent receives the SNMP message, it uses this initialization vector to decrypt the data. Much more detail on DES encryption is provided in RFC 2574.
19
SNMPv3 Configuration SNMPv3 Users
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. 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 usmUserTable is defined as follows: User Default User 1 Default User 2 Default User 3 MD5 SHA-1 MD5 Authentication Type Privacy Type DES DES None
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 authentication 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/passwords become known to another NMS, another NMS may send SNMPv3 messages to the SNMP agent which could change the configuration of the iPlex. Once an NMS knows user name/password information, it can use the authentication password and privacy password to generate the appropriate security information 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 authenticate/decrypt the messages. If the SNMP agent receives an SNMPv3 message from an unknown user, the message 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.
20
SNMPv3 Views
The vacmSecurityToGroupTable, the vacmAccessTable, and the vacmViewTreeTable 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.
SNMPv3 Configuration and 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 snmpwalk tool used is from the NETSNMP toolkit.
or
snmpwalk -v 3 -u user1 -l authNoPriv -a MD5 -A skystream 192.168.58.128 vlanMgmtInfoTable
snmpwalk -v 3 -u user2 -l authNoPriv -a MD5 -A skyStream 192.168.58.128 vlanMgmtInfoTable
Example
If there is one VLAN with IP address 172.30.1.1, the output would be as follows:
TandbergMediaplexMibObjects.TandbergMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vl anIpAddress.0 = IpAddress: 172.30.1.1 s k y S t r ea m M e d ia p l e x Vl a n M g mt O b j e ct s . v l an M g m t In f o T a bl e . v l an M g m t In f o E n tr y . v l a nS u b n e tM a s k . 0 = 255.255.255.0 skyStreamMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe1.0 = 0 (no) skyStreamMediaplexVlanMgmtObjects.vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe2.0 = 0 (no)
SNMP MIB Description

This 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 MIBs in Network Management Applications
You can load iPlex MIBs into SNMP management applications, such as HP OpenView, 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.
NOTE If you are referring to this guide for SNMP help for the iPlex, you should note that most MIBs use Mediaplex in their name, but are meant for use with both Mediaplex and iPlex.
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), skyStreamMediaPlex (7), skyStreamMediaPlexMibObjects (1), skyStreamMediaPlex....Objects ( ).
22
MIBs supported on 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. MIB Name SNMPv2-SMI.txt SNMPv2-TC.txt SNMPv2-MIB.txt ROOT MIB on page 22 SKYSTREAM-PRODUCTS-MIB.txt MEDIAPLEX-TC.txt IPV6-TC.txt For Details, See MIB only MIB only MIB only MIB only MIB only MIB only MIB only page 24 page 24 page 25 page 25 page 25 page 26 page 26 page 27 page 27 page 28 page 28 page 28 page 28 page 31 page 31 page 31 page 31 page 31 page 32 page 32 page 32 page 32 page 32 page 33 page 33 page 33 page 33
Index
Description
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
ASI In ASI Out Encoder VLAN Mgmt Software Program UDP Out Element UDP In Program Route Stream Route Notification SME IP Route TS Stats RTP In RTP Out ATM In ATM Out Redundancy Sensor Chassis SMD ATM FILEIn GE Alarms
skyStreamMediaPlexASIInObjects (1) skyStreamMediaPlexASIOutObjects skyStreamMediaPlexEncoderObjects skyStreamMediaPlexVlanMgmtObjects skyStreamMediaPlexSoftwareObjects skyStreamMediaPlexProgramObjects skyStreamMediaPlexUDPOutObjects skyStreamMediaPlexElementObjects skyStreamMediaPlexUDPInObjects skyStreamMediaPlexProgramRouteObjects skyStreamMediaPlexStreamRouteObjects skyStreamMediaPlexNotificationObjects skyStreamMediaPlexSmeObjects skyStreamMediaPlexIpRouteObjects skyStreamMediaPlexTsStatsObjects skyStreamMediaPlexRTPInObjects skyStreamMediaPlexRTPOutObjects skyStreamMediaPlexATMInObjects skyStreamMediaPlexATMOutObjects skyStreamMediaPlexRedundancyObjects skyStreamMediaPlexSensorsObjects (21) skyStreamMediaPlexChassisObjects skyStreamMediaPlexSmdObjects skyStreamMediaPlexATMObjects skyStreamMediaPlexFILEInObjects skyStreamMediaPlexGEObjects skyStreamMediaPlexAlarmsObjects
23
Index 29 30 31 32 33 34 35 36 38 39 40 41 42 43 44 45 46 47 48 49 50 51 53 59 61 62
Description SCM Encoder Audio ATM Route MPE Route TCP In Backhaul XRater In XRater Out Advanced Encoder Descriptors Ports Spanning Tree Notificationv2 Log Config File Mgmt Notification Log SNMP License File Management Media Processor xCoderIn xCoderOut Security AVC Encoder AVC xCoder In AVC xCoder Out
MIB Name skyStreamMediaPlexScmObjects skyStreamMediaPlexEncoderAudioObjects skyStreamMediaPlexAtmRouteObjects skyStreamMediaPlexMpeRouteObjects skyStreamMediaPlexTCPInObjects skyStreamMediaPlexBackhaulObjects skyStreamMediaPlexXRaterInObjects skyStreamMediaPlexXRaterOutObjects skyStreamMediaPlexAdvancedEncoderObjects skyStreamMediaPlexDescriptorsObjects skyStreamMediaPlexPortsObjects skystreamMediaPlexSpanningTreeObjects skyStreamMediaPlexNotificationV2Objects skyStreamMediaPlexLogObjects skyStreamConfigFileMgmtMIBObjects skyStreamMediaPlexNotificationLogObjects skyStreamMediaPlexSnmpObjects skyStreamMediaPlexLicenseObjects skyStreamMediaPlexFileMgmtObjects skyStreamMediaPlexMediaProcessorObjects skyStreamMediaPlexxCoderInObjects skyStreamMediaPlexxCoderOutObjects skyStreamMediaPlexSecurityObjects
For Details, See page 34 page 34 page 34 page 34 page 35 page 35 page 35 page 35 page 35 page 35 page 36 page 36 page 36 page 36 page 36 page 36 page 36 page 36 page 36 page 36 page 37 page 37 page 36 page 37 page 37 page 37
skyStreamMediaPlexAvcEncoderObjects skyStreamMediaPlexAvcXCoderInObjects skyStreamMediaPlexAvcXCoderOutObjects
iPlex Enterprise MIBs

You 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. 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.
Mediaplex ASIOut MIB
24
asiOutCATInfoTable
This 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 Encoder MIB Mediaplex VLAN Management MIB
skyStreamMediaPlexEncoderObjects This module defines the iPlex Encoder MIB objects. It also contains objects that allow get and set. The MIB does not support row creation and row deletion. 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 vlana multiple variable SNMP set request must be issued that contains the following variables and corresponding values: MIB Object vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanIpAddress.3 vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanSubnetMask.3 vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe1.3 vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanGe2.3 vlanMgmtInfoTable.vlanMgmtInfoEntry.vlanRowStatus.3 Value 172.30.1.1 255.255.255.0 1 (untagged) 0 (no) 4 (createAndGo)
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 Software MIB
skyStreamMediaPlexSoftwareObjects This MIB provides information about all software images present in aflash partition, and is available in softwareVersionInfoTable. MIB object softwareCurrentVersionNumber provides version information about current software.
25
This MIB also allows users to configure boot source using MIB objects softwareBootSource. If the boot source is TFTP MIB objects, softwareTftpIpAddress and softwareTftpFilename must be set appropriately.
Mediaplex Program MIB
skyStreamMediaPlexProgramObjects This MIB provides information about DVB programs available on specific output interface. The MIB also allows the creation 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).
pmtPidProgram PMT PID. Set only valid at creation/deletion time: integer (range 0...8191) pcrPidProgram PCR PID. Set only valid at creation/deletion time: integer (range 0...8191) programRowStatusSet 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: MIB Object programInfoTable.programInfoEntry.pcrPid.asiOut.3.1.200 programInfoTable.programInfoEntry.pmtPid.asiOut.3.1.200 programInfoTable.programInfoEntry.programRowStatus.asiOut.3.1.200 Value 40 41 4 (createAndGo)
To delete a specific program route from an output interface, the management application must set value destroy (6) for the programRowStatus MIB object.
Mediaplex UDPOut MIB
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 udpOutRowStatus = 6 (DESTROY).
NOTE UDPOut also has a table for generating CAT. See ASIOut.
26
Mediaplex Element MIB
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 interface. 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 values 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/1a multiple variable SNMP set request must be issued that contains the following variables and corresponding values: MIB Object elementInfoTable.elementInfoEntry.streamType.asiOut.1.1.20.100 elementInfoTable.elementInfoEntry.elementRowStatus.asiOut.1.1.20.100 Value 2 (MP2 Video) 4 (createAndGo)
To delete a specific program from a output interface using the management application, you must set the value destroy ( 6 ) for the elementRowStatus MIB object, with the index of the element, which is asiOut.1.1.20.100 shown above. You must specify udpInRowStatus.
Mediaplex UDPIn MIB
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, udpInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify udpInRowStatus = 6 (DESTROY).
27
Mediaplex Program Route MIB
skyStreamMediaPlexProgramRouteObjects A table of information about program routes. If you want to add a program route, you MUST use the index sequence { sourcePortType, sourceBladeNumber, sourceUnitNumber, destinationPortType, destinationBladeNumber, destinationUnitNumber, sourceProgramNumber, destinationProgramNumber } and MUST specify: destinationPMTPID, programRouteRowStatus = 4 (CREATEANDGO). If you want to delete a program route, you MUST use the same index sequence and MUST specify programRouteRowStatus = 6 (DESTROY). MIB Object Value 33 4 (createAndGo)
programRouteInfoTable.programRouteInfoEntry.destinationPMTPID.asiIn.1.1.asiOut.1.4.200.205 programRouteInfoTable.programRouteInfoEntry.programRouteRowStatus.asiIn.1.1.asiOut.1.4.200.205
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 Stream Route 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, destinationPortType, destinationBladeNumber, destinationUnitNumber, sourcePID, destinationPID } 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). MIB Object Value 4 (createAndGo)
streamRouteInfoTable.streamRouteInfoEntry.streamRouteRowStatus.asiIn.1.1.asiOut.1.4.256.512
You cannot modify the parameter of a stream route after creation. To delete a specific stream route from a output interface, the management application must set value destroy (6) for the streamRouteRowStatus MIB object.
Mediaplex Notification MIB Mediaplex SME MIB
skyStreamMediaPlexNotificationObjects This MIB defines traps generated by the iPlex. 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.
28
efInfoTable
The 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/1a multiple variable SNMP set request must be issued that contains the following variables and corresponding values: MIB Object efInfoTable.efInfoEntry.efName.1.1.0 efInfoTable.efInfoEntry.efMaxBitRate.1.1.0 efInfoTable.efInfoEntry.efRowStatus.1.1.0 Value ef1 100000 4 (createAndGo)
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.
afInfoTable
The afInfoTable allows you to create and configure a new AF discipline on a specific 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 createAndGo 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 createAndGo (4).
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/1a multiple variable SNMP set request must be issued that contains the following variables and corresponding values: MIB Object afInfoTable.afInfoEntry.afName.1.1.0 afInfoTable.afInfoEntry.afMinBitRate.1.1.0 afInfoTable.afInfoEntry.afMaxBitRate.1.1.0 afInfoTable.afInfoEntry.afRowStatus.1.1.0 afInfoTable.afInfoEntry.afQueueSize.1.1.0 Value af1 500 100000 4 (createAndGo) 100-500
To delete an AF discipline using the management application, you must set the value destroy (6) for the afRowStatus MIB object. You cannot modify the discipline attributes after creation.
beInfoTable
The beInfoTable allows you to create and configure a new BE discipline on a specific 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 createAndGo 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/1a multiple variable SNMP set request must be issued that contains the following variables and corresponding values: MIB Object beInfoTable.beInfoEntry.beName.1.1.0 beInfoTable.beInfoEntry.beQueueSize.1.1.0 beInfoTable.beInfoEntry.beRowStatus.1.1.10 Value be1 500 4 (createAndGo)
To delete a BE discipline using the management application, you must set the value destroy (6) for the beRowStatus MIB object. You cannot modify the discipline attributes after creation.
30
Mediaplex IP Route MIB
skyStreamMediaPlexIpRouteObjects This module defines the iPlex MIB for managing the IP routes. It has two tables indexed by IP address and netmask (create/destroy):
gatewayRoute Gateway. Set only valid at creation/deletion time. rowStatusIP route row status. Set only valid at creation/deletion time.
You must specify gateway and rowStatus to createAndGo (4). MIB Object ipRouteInfoTable.ipRouteInfoEntry.gateway.192.168.2.189.225.225.225.0 ipRouteInfoTable.ipRouteInfoEntry.rowStatus.192.168.2.189.225.225.225.0 Value 10.10.10.1 4 (createAndGo)
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 Stats MIB Mediaplex RTPIn MIB
skyStreamMediaPlexTsStatsObjects This MIB provides transport stream statistics for a specific input or output interface. This table does not support row creation and row deletion. 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 RTPOut MIB
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).
NOTE RTPOut also has a table for generating CAT. See ASIOut.
Mediaplex ATMIn MIB
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
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 ATMOut MIB
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 atmInRowStatus = 6 (DESTROY).
NOTE ATMOut also has a table for generating CAT. See ASIOut.
Mediaplex Redundancy MIB Mediaplex Sensors 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. 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. 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. skyStreamMediaPlexSmdObjects This module defines the iPlex SMD management 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.
Mediaplex Chassis MIB Mediaplex SMD MIB
smdInfoTable
This table allows you to add a new PID by configuring the following parameter:
pidRowStatus
You must use the index sequence: pidBladeNumber, pidUnitNumber, pidNumber and specify pidRowStaus createAndGo (4). To delete a PID, you must use the same index sequence and specify pidRowStatus destroy (6).
32
macInfoTable
This 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 macRowStatus 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. skyStreamMediaPlexFILEInObjects This module defines the iPlex MIB for managing the File In logical ports and has one table that allows creation and deletion. 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
Mediaplex FILEIn MIB
(DESTROY).
fileInInfoTable
To create a new FILEIn port, you MUST use the index sequence {bladeNumber, unitNumber} and MUST specify: packetizerType, fileInRowStatus = 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. skyStreamMediaPlexAlarmsObjects This module defines the iPlex Configurable Alarms MIB objects. The table contains get and set objects for the redundancy switch and PMCs, but does not support row creation or deletion. 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 XrtrOut MIBs.
Mediaplex Alarms MIB Mediaplex Xrater MIB
33
Mediaplex SCM MIB
skyStreamMediaPlexSCMObjects This module defines the iPlex SCM management MIB and contains objects that allow get and set. The MIB also has three tables indexed by IP address (create/destroy).
dnsServerRow StatusDNS server row status. Set only valid at creation/deletion time. syslogHostRowStatusSyslog host row status. Set only valid at creation/deletion time. ntpServerRowStatusNTP 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). MIB Object scmSyslogHostInfoTable.scmSyslogHostInfoEntry.syslogHostRowStatus.192.168.4.26
syslogHostRowStatus and set value to destroy (6).
Value 4 (createAndGo)
If you want to delete a syslog host, you must use the same index sequence, specify
Mediaplex Encoder Audio MIB Mediaplex ATM Routes 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. 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. rowStatusATM route row status. Set only valid at creation/deletion time.
You must specify atmVpi, atmVci, and set rowStatus to createAndGo (4). MIB Object atmRouteInfoTable.atmRouteInfoEntry.atmVpi.192.168.2.189.225.225.225.0.3.1. atmRouteInfoTable.atmRouteInfoEntry.atmVci.192.168.2.189.225.225.225.0.3.1. atmRouteInfoTable.atmRouteInfoEntry.rowStatus.192.168.2.189.225.225.225.0.3.1.
rowStatus and set value to destroy (6).
Value 0 50 4 (createAndGo)
If you want to delete a syslog host, you must use the same index sequence, specify
Mediaplex MPE Routes 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 interface slot number), interfaceUnitNumber (SME interface unit number) and
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 TCPIn MIB
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 Backhaul MIB
skyStreamMediaplexBackhaulObjects This module defines the iPlex MIB for Backhaul port creation and deletion. A table of information about Backhaul interfaces. If you want to create a new Backhaul port, you MUST use the index sequence { bladeNumber, unitNumber } and MUST specify backhaulRowStatus = 4 (CREATEANDGO). If you want to delete a Backhaul port, you MUST use the same index sequence and MUST specify backhaulRowStatus = 6 (DESTROY). skyStreamMediaPlexXRaterInObjects This module defines the Mediaplex-20 XraterIn mib objects. The MIB does not support row creation and row deletion. skyStreamMediaPlexXRaterOutObjects This module defines the Mediaplex20 XraterOut mib objects. The MIB does not support row creation and row deletion. 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 MIB Object pmtProgramDescriptorInfoTable.pmtProgramDescriptorInfoEntry.data.asiOut.1.4.3 pmtProgramDescriptorInfoTable.pmtProgramDescriptorInfoEntry.dataType.asiOut.1.4.3 pmtProgramDescriptorInfoTable.pmtProgramDescriptorInfoEntry.pmtProgramDescriptorRowStatus.asiOut.1.4.3 Value
"00 11 22" 1
Mediaplex XrtrIn MIB Mediaplex XrtrOut MIB Mediaplex Descriptors MIB
4 (createAndGo)
Mediaplex Advanced Encoder 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.
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. 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.
Spanning Tree MIB
Notificationv2 MIB Log MIB Config File Mgmt MIB
skyStreamMediaPlexNotificationV2Objects This module defines the notifications generated by the Skystream NMR platform. skyStreamMediaPlexLogObjects This module defines the MediaPlex log management MIB objects. skyStreamConfigFileMgmtMIBObjects This module facilitates writing of configuration 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. skyStreamMediaPlexNotificationLogObjects This module keeps track of the last notifications sent. It is a table with the last traps sent. skyStreamMediaPlexSnmpObjects This module defines the MediaPlex SNMP management MIB objects. 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. skyStreamMediaPlexFileMgmtObjects This module provides file management 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. skyStreamMediaPlexMediaProcessorObjects This module allows the configuration of Media Processors. Note that Media Processor support in Release 3.2 is at beta level. skyStreamMediaPlexSecurityObjects This module allows management of the security options in the device. Using this MIB, the SNMP manager can enable or
Notification Log MIB SNMP MIB License MIB
FileE Management MIB
Media Processor MIB Security MIB
36
disable the various network control interfaces, as well as manage the allowed network list.
NOTE This 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.
xCoderIn MIB
skyStreamMediaPlexCoderInObjects This module defines the iPlex xCoderIn MIB objects. It also contains objects that allow get and set. The MIB does not support row creation and row deletion. skyStreamMediaPlexCoderOutObjects This module defines the iPlex xCoderOut MIB objects and has a table for generating CAT. It also contains objects that allow get and set. 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. 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. 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, emmInRowStatus = 4 (CREATEANDGO). If you want to delete a port, you MUST use the same index sequence and MUST specify emmInRowStatus = 6 (DESTROY).
xCoderOut Mib
AVC Encoder MIB
AVC xCoder In
AVC xCoder Out
37
Introduction to HP OpenView Integration

Although 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 management tools such as Computer Associates Unicenter; however, at this point TANDBERG 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 Management
The 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 management 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 problems 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 Management
The goal of configuration management is to monitor network and system configuration information to track and manage the effects on network operation of various versions of hardware and software elements. Because all hardware and software elements may impose operational flaws that might affect network operation, such information is important in maintaining a smooth running network. Each network device has a variety of version information associated with it.
38
Performance Management
The 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 performance variables. If a performance threshold goes beyond set parameters, the network management system receives an alarm message. Performance management 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 variable such that exceeding thresholds indicates a network problem worthy of attention.
Most operation managers use HP OpenView and plug-ins provided by equipment vendors to monitor, troubleshoot, and provision heterogeneous networks. Following 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 Components

The iPlex HP OpenView plug-in provides the following functionality:
Map registration files that allow NNM to discover and identify new iPlex devices and displays iPlex icons in the topology map(s) Integrates TANDBERG Television-specific MIB files into OpenView MIB database
NOTE The TANDBERG Television MIBs are automatically complied and made available through HP OpenView.
Receives and classifies SNMP traps generated by the iPlex Provides menu registration files that allow users to start TANDBERG Television-specific applications
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 OpenView

HP 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 unmanaged 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 a Specific 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 Option Menu
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 iPlexlaunches the iPlex Web Graphical User Interface Telnet CLIlaunches the iPlex Command Line Interface SNMP Browserlaunches the SNMP MIB Browser Chassis Reportgenerates 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 Web GUI for HP OpenView
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 Telnet window to the iPlex. See the CLI Commands and Operation information in the CLI User Guide.
43
Launching an SNMP Browser for a Specific iPlex
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 List of 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 Interface Properties
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 normal.
Graphs and Historical 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
Appendix A
Monitoring iPlex Using SNMP
49
Overview
This 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 suggestions 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 supports 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
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.2 9.3 1.3.6.1.4.1.3511.3.7. 1.29 1.3.6.1.4.1.3511.3.7.1.2 9.6 1.3.6.1.4.1.3511.3.7.1.2 9.12 Value Description Primary iPlex SCM IP Address IP Address shared between iPlexes Backup iPlex SCM IP Address
Unique Table OID
Variable Name managementIpAddress virtualIpAddress
Syntax IpAddress IpAddress IpAddress
backupManagementIpAddress
51
Basic Status Polling

This 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 system 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 polling system knows that basic connectivity can be established. Failure clearly indicates a basic IP addressing failure, which could be caused by Networking Issues of a problem with the unit. 2 Perform an SNMP Get on the sysObjectID variable (see table below) this can be used to confirm that the device is indeed an iPlex. It also confirms that the SNMP subsystem within the device control layer is active and functional. Failure to get a response to this request could indicate that the SNMP subsystem is down and therefore needs attention or, in the case of 1 + 1 SCM redundancy, one of the SCM blades is actually having a problem. 3 Perform an SNMP Get on the sysUpTime variable (see table below) this can be monitored for an ever increasing value. If the value returned to zero or appeared to go backwards (other than during a wrap around), then this would indicate 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 1.3.6.1.2.1.1. 2 1.3.6.1.2.1.1. 3 Variable Name sysObjectID sysUpTime
Syntax OBJECT IDENTIFIER TimeTicks
Value - Description A unique OID: 1.3.6.1.4.1.3511.3.1.29 The time in 1/100ths of a second since the device booted last
52
Advanced Status Polling

More 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 x 1 redundancy. Determine a complete list of outstanding alarms for iPlex devices.
Detecting Redundancy Flips between SCM Blades

To determine whether redundancy switches have occurred between SCM blades, it is necessary for the polling device to be configured with 2 IP addresses. In addition, 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 address is the primary SCM in a 1 x 1 redundancy pair. If no valid IP address is returned, then this indicates the field cannot be read and the address being used for polling must therefore be that of the backup device. 2 Retain knowledge after the first poll sequence of which IP address is the primary. 3 Subsequent polls can now indicate if a redundancy switch has occurred since if the current primary fails to respond with a valid IP address and the previous backup IP Address does now respond with a valid IP Address, we know that a Redundancy switch occurred and that the pair may need attention.
Monitoring Blade Information Table

Monitoring 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-CHASSIS-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 enable a suitably written polling system to recognize any change or removal from a chassis. Two methods would exist here being dependent on the polling systems SNMP abilities. Once the chassisBladeCount is known, the polling routine can now 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 is an INDEX to returned OID for bladeType and bladeState and should therefore be parsed from the return OID value. It is assumed that the reader of this document is fully conversant with SNMP syntax and usage.
5 The polling routine can now track blades types and recognize changes. It can also determine if blades were removed and which blades they were and finally it can determine if any blades were changed. Any and all of this information could then be used to alarm/warn/inform a network operator about actual changes to a monitored system. 6 More sophisticated polling systems could also track the blade state if so desired, and track any changes by enhancing the polling routines ability to pass on more information to the user. Blade Status Polling MIB Parameters
MIB/Unique Table OID Variable Binding OID
1.3.6.1.4.1.3511.3.7.1.22. 2.1.1
Variable Name slotNumber
Syntax Integer
Value - Description This parameter is returned as an index and can be parsed from the responses to determine which blades are installed. This indicates the blade type for the indexed blade. MCM = 1 and SCM = 2 Allows you to discover whether the blade is okay. States are: offline(0), online(1), unreachable(2), uninitialized(3), synching(4), configuring(5)
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.2
bladeType
Integer
1.3.6.1.4.1.3511.3.7.1.22. 2.1.3
bladeState
Integer
Active Alarm Table Monitoring

Yet 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.
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 individual 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.
NOTE This table became available in Version 3.0 of iPlex software and did not exist in any form in older versions of software. The MIB file containing the information discussed here is the MEDIAPLEXNOTIFICATION-LOG-MIB. To access and retrieve the Active Alarm Table, follow the steps:
1 Perform an SNMP GET on currentActiveAlarmEntries. This value will inform the polling routine of the actual number of currently active alarms for the polled device. The actual value can then be used to form a loop count for how many instances of individual parameters to request. Two methods would exist here being dependent on the polling systems SNMP abilities. A system might use a loop and perform GET NEXTS based on the currentActiveAlarmEntries or create a single GET BULK for the number returned setting the MAX REPETITIONS field to the currentActiveAlarmEntries.
NOTE It is more efficient for polling routines to encapsulate several SNMP GET, GET NEXT or GET BULK commands into a single SNMP packet.
2 With the currentActiveAlarmEntries value it is now possible for GET NEXT or GET BULK requests to retrieve the entire table. 3 Once the data has been collected, it would be up to the requesting routine to format the data for displaying it to the user or use in whatever way deemed necessary by the application.
NOTE The aaIndex 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.
Active Alarm Table
55
MIB/Unique Table OID
Variable Binding OID

1.3.6.1.4.1.3511.3.7.1.45.5
Variable Name currentActiveAlarmEntries aaIndex
Syntax Integer Integer
Value - Description The currently active alarm count for a device This parameter is returned as an index and can be parsed from the responses to determine which blades are installed. This parameter is returned as an index and can be parsed from the responses to determine which blades are installed. Specific Notification type, see iPlex v2.0 Notification (Trap): Definition and Usage (Before Release 3.0) on page 58section for a complete list of Notifications available from iPlex . This could be any module in the system and is defined in the MEDIAPLEX-TC file. Slot number within a chassis. PMC Unit number when linked to hardware. Where more than one port exists within a Unit this field can be used to indicate which port is having problems otherwise it is unused. A textual description of the particular alarm
1.3.6.1.4.1.3511.3.7.145 .6.1.1
1.3.6.1.4.1.3511.3.7.145 .6.1.2
aaSequenceNumber
Integer
1.3.6.1.4.1.3511.3.7.145 .6.1.3
aaNotificationId
Integer
activeAlarmInfoTable 1.3.6.1.4.1.3511.3.7.1 45.6 1.3.6.1.4.1.3511.3.7.145 .6.1.4 aaModuleType Module _Type (Integer) Integer Integer
1.3.6.1.4.1.3511.3.7.145 .6.1.5 1.3.6.1.4.1.3511.3.7.145 .6.1.6 1.3.6.1.4.1.3511.3.7.145 .6.1.7
aaSlotNumber aaUnitNumber
aaSubUnitNumber
Integer
1.3.6.1.4.1.3511.3.7.145 .6.1.8
aaDescription
Octet String
56
1.3.6.1.4.1.3511.3.7.145 .6.1.9
aaSeverity
Integer
The severity of the trap. Severities can be modified by users for every trap the iPlex can generate 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 configuration 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 operation 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 Notifications

ASI 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 implementing 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

Variable Name notificationId interfaceName eventDetails
Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.12 .2
Syntax Integer String String
Value - Description
1 Sync loss for an ASI Input Interface String indicating the Interface that raised the trap 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 .3 1.3.6.1.4.1.3511.3.7.1.12 .4
ASI Sync Regained Notification

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
24 Sync Regained for an ASI Input Interface String indicating the Interface that raised the trap 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.3 1.3.6.1.4.1.3511.3.7.1.12.4
interfaceName eventDetails
ATM Link Up and Down Notifications

ATM Link Up and Link Down notifications can be used to indicate failures and recoveries. Although no severity is attached to the trap Link, Notifications in Version 2 are considered major alarms in iPlex, so as a suggestion anyone implementing 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.
ATM Link Up Notification

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
12 generated when ATM link is regained. String indicating the Interface that raised the trap 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.3 1.3.6.1.4.1.3511.3.7.1.12.4 interfaceName eventDetails
59
ATM Link Down Notification

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
11 generated when ATM card detects loss of link. String indicating the Interface that raised the trap String detailing the problem
Video Notifications
There 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 advancedEncoderVideoLoss, 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

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
13 Generated when the Encoder Video stream is ok String indicating the Interface that raised the trap String detailing the problem
60
Encoder Video Restart Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
14 Generated when an encoder video stream is restarted String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Advanced Encoder Video OK Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
20 Generated when the Advanced Encoder Video stream is ok String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Advanced Encoder Video Loss Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
21 Generated when the Advanced Encoder Video stream is lost String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Encoder Start and Stop Notifications

These 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.
61
In normal operation however it may prove useful to monitor for the stop notification, 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

Variable Name
notificationId interfaceName eventDetails
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
9 Encoder started String indicating the Interface that raised the trap 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.3 1.3.6.1.4.1.3511.3.7.1.12.4
Encoder Stop Notification

Variable Name
notificationId interfaceName eventDetails
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
10 Encoder stopped String indicating the Interface that raised the trap 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.3 1.3.6.1.4.1.3511.3.7.1.12.4
Advanced Encoder Start Notification

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
33 Advanced Encoder started String indicating the Interface that raised the trap String detailing the problem
62
Advanced Encoder Stop Notification

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
34 Advanced Encoder Stopped String indicating the Interface that raised the trap String detailing the problem
Buffering Notifications
Several 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 notification list these would be considered minor alarms.
ASI Transmit Buffer Underflow Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
6 Generated when an ASI Out PMC detects a buffer underflow situation occurs String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
ASI Transmit Buffer Overflow Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
7 Generated when an ASI Out PMC detects a buffer overflow situation occurs String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
63
Encoder Overflow Notification

Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
15 Generated when an Encoder PMC detects an overflow situation occurs String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Audio Notifications
These 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 Variable Name
notificationId
Unique Trap OID
Syntax Integer
Value - Description
18 Generated when an Audio Cable is connected to an Encoder String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Encoder Audio Input Disconnected Notification Variable Name
Unique Trap OID
Syntax Integer
Value - Description
19 Generated when an Audio cable is removed from an Encoder or when it is not installed at initialization String indicating the Interface that raised the trap 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
notificationId
1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
64
Advanced Encoder Audio Input Connected Notification Variable Name

notificationId
Unique Trap OID
Syntax Integer
Value - Description
22 Generated when an Audio Cable is connected to an Advanced Encoder String indicating the Interface that raised the trap String detailing the problem
1.3.6.1.4.1.3511.3.7.1.12.2 1.3.6.1.4.1.3511.3.7.1.12 1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Advanced Encoder Audio Input Disconnected Notification Variable Name
Unique Trap OID
Syntax Integer
Value - Description
23 Generated when an Audio cable is removed from an Encoder or when it is not installed at initialization String indicating the Interface that raised the trap 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
notificationId
1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
Encoder Sync Notification

There 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

Variable Name
notificationId
Unique Trap OID

1.3.6.1.4.1.3511.3.7.1.12.2
Value - Description
5 Generated when an Encoder loses sync String indicating the Interface that raised the trap String detailing the problem
65
MCM CPU Temperature Notifications

In 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 Variable Name
Unique Trap OID
Syntax Integer
Value - Description
29 Generated when an MCM CPU Temperature goes Above what is considered normal for the device String indicating the Interface that raised the trap 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
notificationId
1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
MCM CPU Temperature Within Notification Variable Name
Unique Trap OID
Syntax Integer
Value - Description
30 Generated when an MCM CPU Temperature goes back Within what is considered a normal range for the device String indicating the Interface that raised the trap 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
notificationId
1.3.6.1.4.1.3511.3.7.1.12.3 1.3.6.1.4.1.3511.3.7.1.12.4
String String
66
iPlex Notification List

Notification/Values asiRxSyncLoss/1 newStdParsed/2 newPatParsed/3 newPmtParsed/4 encoderSyncLoss/5 asiTxBufferUnderFlow/6 asiTxBufferOverFlow/7 portDeleted/8 encoderStart/9 encoderStop/10 atmLinkDown/11 atmLinkUp/12 encoderVideoOk/13 encoderVideoRestart/14 encoderOverflow/15 bladeUp/16 bladeDown/17 encoderAudioInputConnected/18 Description Sync loss for an ASI Input Interface Generated when a new STD table is parsed Generated when a new PAT table is parsed Generated when a new PMT table is parsed Generated when a standard Encoder loses Sync Generated whenever an ASIIn detects and buffer underflow condition exists Generated whenever an ASIIn detects and buffer overflow condition exists Generated whenever a port gets deleted by the user or the system Generated whenever an Encoder is started Generated whenever an Encoder stops Generated when an ATM module detects a loss of link Generated when an ATM module detects a link is up Generated when an Encoder Video stream is OK Generated when an Encoder gets restarted Generated when memory buffer overflow conditions exist on an encoder Generated after a blade is fully function and initialized Generated whenever a blade goes down Generated whenever the audio cable is detected on an encoder but not when the audio is in the composite SDI stream Suggested Severity Major Informational Informational Informational Major Minor Minor Informational Informational Minor Major Informational Informational Minor Minor Informational Major Informational continued
67
Notification/Values encoderAudioInputDisconnected/19
Description Generated when no encoder audio cable is detected which will occur at initialization if the encoder is using an SDI connect with embedded audio Generated when an advanced encoder video stream is OK Generated whenever an advanced encoder video stream is lost Generated whenever the audio cable is detected on an advanced encoder but not when the audio is in the composite SDI stream Generated when no advanced encoder audio cable is detected which will occur at initialization if the advanced encoder is using an SDI connect with embedded audio Generated when sync is detected at an ASI Input Generated whenever a failure is detected in an iPlex for fan bank 1 Generated when an iPlex fan bank 1 is OK Generated whenever a failure is detected in an iPlex for fan bank 2 Generated when an iPlex fan bank 2 is OK Generated when the MCM temperature goes above a predefined setting Generated when the MCM temperature goes back within normal operating parameters Generated when the lower carrier in an iPlex is removed the iPlex will however reboot Generated when the upper carrier in an iPlex is removed the iPlex will however reboot Generated whenever an Advanced Encoder is started Generated whenever an Advanced Encoder stops
Suggested Severity Minor
advancedEncoderVideoOk/20 advancedEncoderVideoLoss/21 advancedEncoderAudioConnected/ 22 advancedEncoderAudioDisconnected/23
Informational Major Informational Minor
asiSyncRegained/24 fanBank1Failure/25 fanBank1OK/26 fanBank2Failure/27 fanBank2OK/28 mcmCpuTemperatureAbove/29 mcmCpuTemperatureWithin/30 lowerCarrierPulledOut/31 upperCarrierPulledOut/32 advancedEncoderStart/33 advancedEncoderStop/34
Informational Major Informational Major Informational Major Informational Major Minor Informational 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 configuration 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 configuration can be achieved through the use of an iPlex Web GUI.
NOTE It is also possible through the Web GUI to configure the actual severity of each trap. Whether specific traps are discarded or forwarded, t is entirely the responsibility of the network operator. 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 systems. This section will concentrate on those notifications that may be worth monitoring 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 leaving the deletion and clearing of the alarm messages to be done by the user manually. 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 Notifications

Should 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.
69
OK Notification
Variable Name notificationId sequenceNumber moduleType slotNumber unitNumber subSlotNumber description severity
Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.42 .2 1.3.6.1.4.1.3511.3.7.1.42 .3
Syntax Integer Integer Integer Integer Integer Integer String Integer
Value - Description 1 Module is okay Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
70
Failure Notification
Unique Trap OID
Value - Description 2 Module has failed Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
71
Up and Down Notifications

Down 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
Unique Trap OID
Value - Description 3 Module detected in chassis Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.4 2.2 1.3.6.1.4.1.3511.3.7.1.4 2.3
Value - Description 4 Module has been removed or rebooted Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Minor Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9
73
Inserted and Removed Notifications

These 2 notifications are specifically targeted at blades. When a blade is detected in a chassis an INSERTED notification will be generated while a REMOVED notification 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
Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.42. 2 1.3.6.1.4.1.3511.3.7.1.42. 3
Value - Description 5 Module has been inserted Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7. 1.42
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
Unique Trap OID
Value - Description 6 Module has been removed Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1 .42
1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9
75
Video Notifications
There 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
1.3.6.1.4.1.3511.3.7.1.42.2 1.3.6.1.4.1.3511.3.7.1.42.3 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 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 unitNumber subSlotNumber description severity Integer Integer String Integer Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
Unique Trap OID
Variable Name
notificationId sequenceNumber moduleType slotNumber
Syntax
Integer Integer Integer Integer
Value - Description
7 Module detected in chassis Trap sequence number Module type Slot number where module is located
Video Start Notification

Unique Trap OID
Value - Description 8 Module has been removed or rebooted Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1.4 2
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
Video Loss Notification

Unique Trap OID
Value - Description 9 Module has been removed or rebooted Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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 Notifications

These 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
Unique Trap OID
Value - Description 12 Module has been started Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
78
Stop Notification
Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.42. 2 1.3.6.1.4.1.3511.3.7.1.42. 3
Value - Description 13 Module has been stopped Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
79
Sync Notifications
Sync 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 problem 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
Unique Trap OID
Value - Description 14 Module Sync Ok Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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
80
Sync Loss Notification

Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.4 2.2 1.3.6.1.4.1.3511.3.7.1.4 2.3 1.3.6.1.4.1.3511.3.7.1. 42 1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9 Variable Name notificationId sequenceNumber moduleType slotNumber unitNumber subSlotNumber description severity
Unique Trap OID
Value - Description 15 Module Sync Loss Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
81
Buffering Notifications
Buffer 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

Unique Trap OID
Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.42 .2 1.3.6.1.4.1.3511.3.7.1.42 .3 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
Value - Description 16 Module buffer underflow Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Minor Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
82
Buffer Overflow Notification

Unique Trap OID
Value - Description 17 Module buffer overflow Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Minor Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9
83
Buffer OK Notification
Unique Trap OID
Value - Description 18 Module buffer Ok Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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 Notifications
These notifications apply to the audio input port found on encoders and are generated whenever the audio cable is connected or removed. So clearly Audio Disconnected 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

Unique Trap OID
Value - Description 19 Module Audio Connected Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
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 Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.4 2.2 1.3.6.1.4.1.3511.3.7.1.4 2.3 1.3.6.1.4.1.3511.3.7.1. 42 1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9 Variable Name notificationId sequenceNumber moduleType slotNumber unitNumber subSlotNumber description severity
Unique Trap OID
Value - Description 20 Module Audio Disconnected Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
86
Link Notifications
Here a Link Up notification clears a Link Down notification.
Link Down Notification

Unique Trap OID
Value - Description 21 Module Link Down Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
87
Link Up Notification
Unique Trap OID
Value - Description 22 Module Link Up Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
1.3.6.1.4.1.3511.3.7.1. 42
1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9
88
CPU Temperature Notifications

There 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 notification will be generated. If the CPU then falls back to a nominal operating temperature, 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 temperature 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 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

Unique Trap OID
Value - Description 2000 Module CPU Temperature Ok Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
89
CPU Temperature Warning Notification

Unique Trap OID
Value - Description 2001 Module CPU Temperature Warning Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Minor Trap severity
90
CPU Temperature Critical Notification

Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.4 2.2 1.3.6.1.4.1.3511.3.7.1.4 2.3 1.3.6.1.4.1.3511.3.7. 1.42 1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8 1.3.6.1.4.1.3511.3.7.1.4 2.9 Variable Name notificationId sequenceNumber moduleType slotNumber unitNumber subSlotNumber description severity
Unique Trap OID
Value - Description 2002 Module CPU Temperature Critical Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
91
CPU Utilization Notifications

There 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 however the utilization continues to rise and hits the Critical level, a Critical notification 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 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.
CPU Utilization OK Notification

Unique Trap OID
Value - Description 2003 Module CPU Utilization Ok Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
92
CPU Utilization Warning Notification

Variable Binding OID 1.3.6.1.4.1.3511.3.7.1.4 2.2 1.3.6.1.4.1.3511.3.7.1.4 2.3 1.3.6.1.4.1.3511.3.7.1. 42 1.3.6.1.4.1.3511.3.7.1.4 2.4 1.3.6.1.4.1.3511.3.7.1.4 2.5 1.3.6.1.4.1.3511.3.7.1.4 2.6 1.3.6.1.4.1.3511.3.7.1.4 2.7 1.3.6.1.4.1.3511.3.7.1.4 2.8
1.3.6.1.4.1.3511.3.7.1.42.9
Unique Trap OID
Variable Name notificationId sequenceNumber moduleType slotNumber unitNumber subSlotNumber description

severity
Syntax Integer Integer Integer Integer Integer Integer String

Integer
Value - Description 2004 Module CPU Utilization Warning Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap
Minor Trap severity
93
CPU Utilization Critical Notification

Unique Trap OID
Value - Description 2005 Module CPU Utilization Critical Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
94
Memory Utilization Notifications

There are 3 notifications in this group. If the Memory Utilization goes to the warning 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 notification 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 utilization 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 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

Unique Trap OID
Value - Description 3000 Module Memory Utilization Ok Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Informational Trap severity
95
Memory Utilization Warning Notification

Unique Trap OID
Value - Description 3001 Module Memory Utilization Warning Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Minor Trap severity
96
Memory Utilization Critical Notification

Unique Trap OID
Value - Description 3002 Module Memory Utilization Critical Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
97
Redundancy Flip Notification

This notification has no cancelling event and is generated to indicate that redundant 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

Unique Trap OID
Value - Description 4000 Module has flipped from Trap sequence number Module type Slot number where module is located Unit number for indicated slot Additional port information for unit Textual description of this trap Major Trap severity
98
iPlex Notification List

Notification/Value OK/1 Failure/2 Up/3 Down/4 Inserted/5 Removed/6 Video OK/7 Video Start/8 Video Loss/9 Port Created/10 Port Deleted/11 Start/12 Stop/13 Sync OK/14 Sync Loss/15 Buffer Underflow/16 Buffer Overflow/17 Buffer OK/18 Audio Connected/19 Audio Disconnected/20 Link Down/21 Link Up/22 New STD Parsed/1000 New PAT Parsed/1001 New PMT Parsed/1002 A module is OK A module entered a failure mode A module has been detected in the chassis A module has removed from a chassis or rebooted A blade has been inserted into a chassis A blade has been removed from a chassis A module detects Video OK A module detects that Video Started A module detects that Video Stopped A port has been created A port has been deleted A module has started A module has stopped A module has detected gain of sync A module has detected loss of sync A buffer underflow problem has been detected A buffer Overflow has been detected The buffer system has returned to normal The Audio input has been connected to a module The Audio input has been disconnected from a module A module has detected a Link Down state A module has detected a Link Up state A new STD table was detected and Parsed A new PAT table was detected and Parsed A new PMT table was detected and Parsed Description Default Severity Informational Major Informational Minor Informational Informational Informational Informational Major Informational Informational Informational Major Informational Major Minor Minor Informational Informational Minor Major Informational No longer generated No longer generated No longer generated continued
99
Notification/Value CPU Temperature OK/ 2000 CPU Temperature Warning/2001 CPU Temperature Critical/2002 CPU Utilization OK/2003 CPU Utilization Warning/ 2004 CPU Utilization Critical/ 2005 Memory Utilization OK/ 3000 Memory Utilization Warning/3001 Memory Utilization Critical/3002 Redundancy Flip/4000
Description A modules CPU Temperature is OK A modules CPU Temperature has reached the Warning level A modules CPU Temperature has reached the Critical level A modules CPU Utilization is OK A modules CPU Utilization has reached the Warning level A modules CPU Utilization has reached the Critical level A modules Memory Utilization is OK A modules Memory Utilization has reached the Warning level A modules Memory Utilization has reached the Critical level A redundancy flip between redundant blades has occurred.
Default Severity Informational Minor Major Informational Minor Major Informational Minor Major Major
100
Performance Monitoring
Performance 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 MIB/Unique Table 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
Variable Name rateBps
Syntax Guage3 2
Value - Description This is the current rate that a specific PID is being received at.
Examples
To clarify how to track the data flowing through various port types, a few examples are given below.
Encoder Video Data 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.
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 discover 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-TSSTATS-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 configured threshold. This example does not recommend any specific tool for performing 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: Composed syntax: Status: Max access: Sequences: TsStatsInfoEntry TsStatsInfoEntry current not-accessible 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) 1: portType 2: bladeNumber 3: unitNumber 4: pid Information about a specific PID associated with an interface.
Indexes:
Description:
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 MEDIAPLEXTC 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 no longer present and should be alarmed to the system operator. Obviously, the polling mechanism should also have a method to clear any alarm when data is seen to go above the threshold again. Care should be exercised when reading MIB parameters as the dynamic nature of Mediaplex 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 value is 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 polling routine must be able to handle this. This very same method could be used to target an advanced encoder, in this case however the portType = 16.
ASIIn and ASIOut Video 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 problems 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 Other Ports 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 unitNumber 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 Port Type tcpIn udpIn rtpIn atmIn asiIn encoder fileIn udpOut rtpOut atmOut asiOut backhaul xraterIn xrateOut advEncoder xcoderIn xcoderOut 1 2 3 4 5 6 7 8 9 10 11 12 14 15 16 18 19 Value
Monitoring Using the 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 tables entry is:
Base syntax: PortsInfoEntry Composed syntax:PortsInfoEntry Status: current Max access: not-accessible Sequences: 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)
104
Indexes:
10: rateBps - Gauge32(66 - gauge32) 1: portType 2: portBladeNumber 3: portUnitNumber Information about specific ports.
Description:
The parameter of interest here is again rateBps but has a different OID, see table that follows.
Ports MIB Rate Parameter

MIB/Unique Table OID
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
Variable Name rateBps
Syntax Guage32
Value - Description This is the current rate that a specific PID is being received at.
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 Monitoring Points
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.
105
106
Index
A accounting management 38 Advanced Encoder MIB 35 afInfoTable 29 alarms 33 architecture 15 ASIIn 24 ASIOut 24 asiOutCATInfoTable 25 ATM 33 ATM Routes 34 ATMIn 31 ATMOut 32 authentication 19 AVC encoder 37 element 27 encoder 25 encoder audio 34 encryption DES 19
F fault management 38 FILEIn 33 fileInInfoTable 33 formats 16
G GE 33 graphs and historical data 47
B backhaul 35 beInfoTable 30
C chassis 32 conceptual rows 17 creating 18 deletion 18 instance identifier 18 config file MIB 36 configuration 20 configuration example 21 configuration management 38 creating conceptual rows 18
H HP Openview accounting management 38 configuration management 38 fault management 38 get list of components 45 graphs and data 47 intro 38 inventory report 45 monitoring a specific chassis 41 monitoring chassis 40 network interface properties 46 opening the Web GUI 42 performance management 39 SNMP browser for specific chassis 44 standard option menu 41 system alarms 47
D defining SNMP 15 DES encryption 19 description for MIBs 21 descriptors 35 documentation - other 10
I instance identifier 18 inventory report 45 IP Route 31
E efInfoTable 29
L list of components using HP Openview 45
Beta
Beta
107
log MIB 36
M macInfoTable 33 messages 17 MIB Advanced Encoder 35 alarms 33 ASIIn 24 ASIOut 24 ATM 33 ATM Routes 34 ATMIn 31 ATMOut 32 AVC encoder 37 backhaul 35 chassis 32 compiling in network management applications 22 config file 36 description and references 21 element 27 encoder 25 encoder audio 34 Enterprise 24 FILEIn 33 GE 33 IP Route 31 list of supported 23 log 36 MPE Routes 34 notification 28 notification log 36 notificationv2 36 ports 36 program 26 Program Route 28 Redundancy 32 root 22 RTPIn 31 RTPOut 31 SCM 34 sensors 32 SMD 32 SME 28
108
SNMP 36 software 25 spanning tree 36 stream route 28 TCPIn 35 TS Stats 31 UDPIn 27 UDPOut 26 user-created descriptors 35 VLAN Management 25 Xrater 33 XrtrIn 35 XrtrOut 35 monitoring a specific chassis using HP Openview 41 monitoring chassis using HP Openview 40 MPE Routes 34
N network interface properties 46 notification 28 notification log MIB 36 notificationv2 MIB 36
P performance management 39 ports MIB 36 privacy 19 private descriptors 35 program 26 Program Route 28
R Redundancy 32 references for MIBs 21 root MIB 22 RTPIn 31 RTPOut 31
S SCM 34 sensors 32
Beta
Beta
SMD 32 smdInfoTable 32 SME 28 SNMP architecture 15 concept row creation 17 conceptual row creation 17 definition 15 formats 16 messages 17 row creation 17 transmission of messages 16 v3 authentication 19 v3 configuration 20 v3 configuration example 21 v3 privacy 19 v3 quick overview 19 v3 users 20 v3 views 21 SNMP browser for chassis using Openview 44 SNMP message transmitting 16 SNMP MIB 36 SNMP specifications 15 software 25 spanning tree MIB 36 specifications for SNMP 15 standard option menu 41 stream route 28 system alarms 47
users 20
V views 21 VLAN Management 25
W Web GUI for HP Openview 42
X Xrater 33 XrtrIn 35 XrtrOut 35
T TCPIn 35 tech support checklist 11 overview 11 transmitting an SNMP message 16 TS Stats 31
U UDPIn 27 UDPOut 26 user-created descriptors 35
109
110
Beta
Beta

Iplex Version 5.0 SNMP Guide

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Iplex Version 5.0 SNMP Guide

Încărcat de

Drepturi de autor:

Formate disponibile

112-0116-02 Rev A

Agency Compliance and Cautions

FCC Class A Compliance

Important Safety Information!

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

Conceptual Row Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SNMP MIB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

MIBs supported on iPlex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

iPlex Enterprise MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iPlex Network Management & Monitoring Reference Guide

iPlex Network Management & Monitoring Reference Guide

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

iPlex Network Management & Monitoring Reference Guide

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

iPlex Network Management & Monitoring Reference Guide

Introduction to the Network Management & Monitoring Guide

Other iPlex Guides

Installation & Hardware Specifications Guide, for information on

Command Line Interface Reference Guide, for information on

Web Interface User Guide, for information on

iPlex Network Management & Monitoring Reference Guide

Contacting TANDBERG Television Customer Support

Support Check List

iPlex Network Management & Monitoring Reference Guide

iPlex Network Management & Monitoring Reference Guide

iPlex Network Management & Monitoring Reference Guide

Network Management Protocol Architecture

iPlex Network Management & Monitoring Reference Guide

Transmission of an SNMP Message

iPlex Network Management & Monitoring Reference Guide

Conceptual Row Creation

iPlex Network Management & Monitoring Reference Guide

Conceptual Row Deletion

iPlex Network Management & Monitoring Reference Guide

iPlex Network Management & Monitoring Reference Guide

SNMPv3 Configuration SNMPv3 Users

No authentication, no privacy Authentication with no privacy Authentication with privacy

iPlex Network Management & Monitoring Reference Guide

SNMPv3 Configuration and Example

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

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

SNMP MIB Description

iPlex Network Management & Monitoring Reference Guide

Compiling MIBs in Network Management Applications

SKYSTREAM-ROOT-MIB SKYSTREAM-PRODUCTS-MIB MEDIAPLEX-TC-MIB Other MIBs may be loaded in any order.

iPlex Network Management & Monitoring Reference Guide

MIBs supported on iPlex

iPlex Network Management & Monitoring Reference Guide

skyStreamMediaPlexAvcEncoderObjects skyStreamMediaPlexAvcXCoderInObjects skyStreamMediaPlexAvcXCoderOutObjects

iPlex Enterprise MIBs

Mediaplex ASIIn MIB

Mediaplex ASIOut MIB

iPlex Network Management & Monitoring Reference Guide

Mediaplex Encoder MIB Mediaplex VLAN Management MIB

vlanIpAddress vlanSubnetMask vlanGe1 vlanGe2 vlanRowStatus

Mediaplex Software MIB

iPlex Network Management & Monitoring Reference Guide

Mediaplex Program MIB

Mediaplex UDPOut MIB

iPlex Network Management & Monitoring Reference Guide

Mediaplex Element MIB

Mediaplex UDPIn MIB