Luminato SNMP Monitoring Guide - nova-minsk.comforum.nova-minsk.com/file/Luminato/Luminato_SNMP_Monitoring_0… · 26/1/2011 · MIB Node(s) Comments mib-2 system Provides generic

CONFIGURATION GUIDE

26-Jan-11 1(24)

Luminato_SNMP_Monitoring_030.docx

Luminato SNMP Monitoring Guide

CONFIGURATION GUIDE

26-Jan-11 2(24)


TABLE OF CONTENT

1. General ......................................................................................................... 3 2. List of supported MIBs ................................................................................... 7 3. SNMP Setup ................................................................................................. 9 3.1. Download MIBs .......................................................................................... 9 3.2. Communities ............................................................................................ 10 3.3. Trap destinations ...................................................................................... 11 4. Alarms conception ....................................................................................... 12 5. Traps ........................................................................................................... 13 5.1. General .................................................................................................... 13 5.1.1. coldStart 13 5.1.2. heCommonAlarmEvent 14 6. Monitoring ................................................................................................... 15 6.1. General .................................................................................................... 15 6.2. Active ....................................................................................................... 16 6.3. Passive ..................................................................................................... 20 6.4. States ....................................................................................................... 21 6.5. Recommended polling strategy ................................................................ 21 7. Status codes ............................................................................................... 22

CONFIGURATION GUIDE

26-Jan-11 3(24)


1. GENERAL

The document describes how to setup and use SNMP Monitoring for Luminato to look at the state of the device.

Luminato supports SNMP versions 1 and 2c, and generates traps (see Traps).

It has implemented MIBs (see List of supported MIBs) and provides mechanisms to detect device state changes – when warnings/error/… raised and released (ex-ample when signal is lost and returned back).

This document does not describes how the SNMP working in general, how to use your MIB Browser nor management system.

Statuses can be seen via WebUI at main page:

CONFIGURATION GUIDE

26-Jan-11 4(24)


SNMP Monitoring provides equal view and traps using industry standard MIBs (for more information visit http://www.scte.org/):

http://www.scte.org/

CONFIGURATION GUIDE

26-Jan-11 5(24)


Your management system can monitor Luminato states using SNMP and traps.

EMS:

CONFIGURATION GUIDE

26-Jan-11 6(24)


OpenNMS:

CONFIGURATION GUIDE

26-Jan-11 7(24)


2. LIST OF SUPPORTED MIBS

MIB Node(s) Comments

mib-2 system Provides generic information on de-vice. Such are de-scription, id, up-time, hostname, management con-tact and location

TELESTE-COMMON-MIB elementInformation Minimal equivalent of mib-2/system

elementStatus Minor statuses of device

elementControl Provides control for trap destina-tions.

moduleInformation Information about modules

moduleStatus Temperature of modules

moduleControlTable Temperature control for modules

TELESTE-LUMINATO-MIB luminato/general Equivalent of mib-2/system.

Provides cumulative uptime

luminato/statusCode Lists possible status codes defini-tions

statusCodeDeviceTable

statusCodeModuleTable

statusCodeIntarfaceTable

statusCodeTransportStreamTable

statusCodeServiceTable

statusCodePidTable

Lists possible status codes definitions for device level, module and PSU level, Inter-face level, TS level, Service level and PID level of monitor-ing

SCTE-HMS-PROPERTY-MIB currentAlarmTable Provide list of cur-rently active warn-ings/errors

descretePropertyTable Keeps references to possible status codes.

Reserved for future

CONFIGURATION GUIDE

26-Jan-11 8(24)


MIB Node(s) Comments

needs to filter out unnecessary status codes from monitor-ing

SCTE-HMS-HE-COMMON-MIB heCommonLog Persistent log of monitoring events.

Major elements to use for monitoring marked bold in table.

CONFIGURATION GUIDE

26-Jan-11 9(24)


3. SNMP SETUP

3.1. Download MIBs

All actual MIBs can be downloaded from device (assumed that standard MIBs are available for you system\browser):

Navigate to Administration->Service page

Click ‘Download MIBs’ link

See picture:

CONFIGURATION GUIDE

26-Jan-11 10(24)


3.2. Communities

User can read SNMP OIDs and write available using up to 5 different communi-ties for read and write access.

Community can be configured via WebUI Administration->Services->Edit SNMP Settings page:

Default community are:

public (for read only access)

private (for write only access)

CONFIGURATION GUIDE

26-Jan-11 11(24)


3.3. Trap destinations

To be able receive traps form Luminato user must register IP(s) to where traps shall be send at the device.

Luminato supports up to 5 trap destination.

By default none of those are configured.

Those can be configured via WebUI Administration->Services->Edit SNMP Set-tings page:

Or via SNMP controlTrapReceiverTable (1.3.6.1.4.1.3715.99.1.3.5):

SNMP interface to trap destination definitions provide more advanced options.

By default it uses port 162 and ‘public’ community.

CONFIGURATION GUIDE

26-Jan-11 12(24)


4. ALARMS CONCEPTION

Device has set of functionality implemented internally by application, drivers, and others subsystems.

The states of functionality is represented according to product specific MIB(s) and\or by industry standard MIB(s).

Monitored states summarised in discretePropertyTable and propertyTable (see SCTE-HMS-PROPERTY-MIB).

When monitored functionality changes its states, its record in discreteProperty-Table or propertyTable changes state.

Records from discretePropertyTable and propertyTable which has alarm state are published in currentAlarmTable (see SCTE-HMS-PROPERTY-MIB).

When record in currentAlarmTable changes it state, added, or removed, new re-cord into heCommonLogTable (see SCTE-HMS-HE-COMMON-MIB) is inserted. If size of heCommonLogTable table became over limit, older records removed.

When new record inserted into currentAlarmTable the SNMP trap heCom-monAlarmEvent (see SCTE-HMS-HE-COMMON-MIB) is generated and send.

Luminato specific note: due to huge set of real monitored object Luminato pub-lish in discretePropertyTable only status codes with no references to real moni-tored objects.

CONFIGURATION GUIDE

26-Jan-11 13(24)


5. TRAPS

5.1. General

Luminato generates traps when device changes state of internal object. Manage-ment\Monitoring system should receive those to be aware of device problems.

5.1.1. coldStart

Trap coldStart is sent when SNMP subsystem is up and detects device boot up.

The trap has two additional bindings:

Device type (system object id)

Device name

The Luminato always reports sysObjectID.0 as 1.3.6.1.4.1.3715.17 (luminato)

CONFIGURATION GUIDE

26-Jan-11 14(24)


5.1.2. heCommonAlarmEvent

The heCommonAlarmEvent trap is described by SCTE MIBs.

Trap heCommonAlarmEvent is sent when device’s one of objects changed it state. The trap indicates object id, state, date and time, and text message.

Those fields are taken from record in heCommonLog which caused trap.

State heCommonDiscreteMinor(7) or heCommonDiscreteMajor(6) indicates that state arise.

State heCommonNominal(1) indicates that state of object returned to its nor-mal(nominal) state. It means that problem resolved.

Rest of values for state are reserved for analog parameters and currently not used.

CONFIGURATION GUIDE

26-Jan-11 15(24)


6. MONITORING

6.1. General

The general state of device can be seen on WebUI main page:

When status changes it state it is recorded in syslog as well.

The SNMP checks status changes with interval of 10 seconds.

It means that there absolutely no needs to poll SNMP with higher frequency.

Also it means that state which active less than 10 seconds and happened be-tween SNMP checks wont be indicated by SNMP.

CONFIGURATION GUIDE

26-Jan-11 16(24)


6.2. Active

When user\system wants to monitor device state actively it has to poll device not frequently than once per 10 seconds.

Summary of current alarm states can be seen via currentAlarmTable (1.3.6.1.4.1.5591.1.1.2):

Nominal states are not indicated in this table.

The verbal description for state you have to decide via statusCode tables.

CONFIGURATION GUIDE

26-Jan-11 17(24)


Example state:

sciInterfaceId.1.5.1.4097 (1.3.6.1.4.3715.17.2.4.1.1.1.5.1.4097)

sciInterfaceId indicates the state for interface level.

Checking indexing for sciInterfaceId:

CONFIGURATION GUIDE

26-Jan-11 18(24)


We can see that interfaceTypeId is 1 (means input):

Module is 5. Interface id is 1. Status code is 4097.

To get verbal description we may get row from statusCodeInterfaceTa-ble:

CONFIGURATION GUIDE

26-Jan-11 19(24)


The history of state changes can be seen via heCommonLogTable (1.3.6.1.4.1.5591.1.11.2.1.1.1.2.3):

The information on heCommonLogTable can be taken from heCommonLogLastIn-dex(1.3.6.1.4.1.5591.1.11.2.1.1.1.2.2.0) and heCommonLogNumberOfEn-tries(1.3.6.1.4.1.5591.1.11.2.1.1.1.2.1.0)

Advanced monitoring system may scan whole heCommonLogTable only when he-

CommonLogLastIndex or heCommonLogNumberOfEntries are changed. See Rec-ommended polling strategy.

CONFIGURATION GUIDE

26-Jan-11 20(24)


6.3. Passive

When user\system wants to monitor device state passively it has to register its IP at Luminato (see Trap destinations) and listen for traps.

This method is highly recommended as it lets to monitor many devices same time with no performance impact to monitoring system nor monitored device(s).

When user\monitoring system receives trap the trap can be decoder according to MIBs to detect what kind of even happens

Example:

We received a trap:

The device IP which send trap is 10.2.12.83

Its uptime is over 2 days (see Binding #1)

The trap is heCommonAlarmEvent (see Binding #2)

Decoding Binding #3 we can see:

o Trap send for module level

o Module ID is 7 – what is equal to PSU

o Status code is 6

o Additional value is 48

Trap was send due to raised state - Binding #5 indicated heCommonDis-creteMajor(6)

Binding #6 indicated date/time when even was recorded

Binding #7 has verbal description of trap

CONFIGURATION GUIDE

26-Jan-11 21(24)


The variables for this trap were taken from heCommonLogTable:

6.4. States

Status states may be:

heCommonDiscreteMinor(7)/caasDiscreteMinor(7) – for statuses level up to warning

heCommonDiscreteMajor(6)/caasDiscreteMajor(6) – for statuses level er-ror or critical

heCommonNominal(1) – for statuses which are not raised at moment.

Rest of states are reserved for analog parameters and currently not used.

6.5. Recommended polling strategy

Regular management system will not poll device but operates base on received traps.

If your management system has to poll device, the interval between polls shall be more than 10 seconds.

To monitor current state currentAlarmTable has to be polled. If verbal definition for state needed, value from one of statusCode tables shall be read.

More advanced system shall poll heCommonLogNumberOfEntries (1.3.6.1.4.1.5591.1.11.2.1.1.1.2.1.0) and heCommonLogLastIndex (1.3.6.1.4.1.5591.1.11.2.1.1.1.2.2.0),

and if any of those changed its value read heCommonLogTable (1.3.6.1.4.1.5591.1.11.2.1.1.1.2.3):

The whole table can be read

Or only new record(s) in heCommonLogTable can be read (base on previous and new values of heCommonLogLastIndex)

Avoid polling of all others tables!!!

CONFIGURATION GUIDE

26-Jan-11 22(24)


7. STATUS CODES

Code Level Text Comments

2 PID PID missing

3 Service Service missing

4 Module PID conflict

5 TS PID remapped

6 Chassis Module

Temperature too high

7 Chassis Module

Temperature too low

8 TS Manual table insertion failed

4096 Module Off

4097 Interface Signal missing

4098 TS No TS sync

4099 TS TS RX error

4100 TS TS input buffer overflow

4101 TS TS output buffer overflow

4102 Interface ASI link down Only for ASI input

4104 Module PID capacity exceeded

4105 Module PSI/SI capture capacity exceeded

4106 Module Out of service ID’s

4107 Chassis Module

License conflict limits features

4108 Module CA module missing

4109 TS PSI/SI insert capacity exceeded

4110 TS Overallocated multiplex

4111 Chassis Module

Unknown module

4112 Module PSU: Voltage too high Only for PSU (Module 7)

4113 Module PSU: Voltage too low Only for PSU (Module 7)

4114 Module PSU: Current too high Only for PSU (Module 7)

4115 Module PSU: Current too low Only for PSU (Module 7)

4129 Chassis Module

Device driver failure

4130 Chassis Module

Hardware failure

CONFIGURATION GUIDE

26-Jan-11 23(24)



4131 Chassis Fan failure

4132 Chassis Running on backup power

4133 Module PSU: Power supply overloaded Only for PSU (Module 7)

4134 Module Booting up

4135 Module Boot failed: retrying

4136 Module Boot failed

4137 Module Shutting down

4138 Module Connection lost

4139 Module Incompatible module disabled

4140 Module Boot failed: retrying

4141 Module Failed to boot (module)

4142 Chassis Rear I/O module failed

4145 Module UPC communication timeout Only for QAM and COFDM

4146 Module UPC PLL Lost Only for QAM and COFDM

4147 Module UPC too low input power Only for QAM and COFDM

4148 Module UPC too high input power Only for QAM and COFDM

4149 Module Calibration data missing Only for QAM and COFDM

4151 Module Descrambling failure

4153 Chassis Backup: Switched over to backup de-vice

4161 Interface Signal quality

4167 Module Booting

4168 Module Restarting

4171 Module FPGA input buffer overflow

4172 Module CPU input filter overflow

4173 Module SID conflict

4174 Module PID allocated from outside configured range

4175 Module Unsupported configuration Only for QAM and COFDM

4176 Module Frequency out of range Only for QAM and COFDM

4177 Module Output power out of range Only for QAM and COFDM

4178 Module Symbolrate out of range Only for QAM and COFDM

4179 Module Channel distance too narrow Only for QAM and COFDM

4180 Module Invalid configuration Only DVBS/DVBS2

CONFIGURATION GUIDE

26-Jan-11 24(24)



4181 Module Invalid puncture rate for selected modulation

Only DVBS/DVBS2

4182 Module LNB current Only DVBS/DVBS2

4183 Module Frequency offset Only DVBS/DVBS2/DVBT

4185 Module Restarting descrambling

4186 Module Rebooting CAM

4187 Chassis ECMG failure

4188 Chassis ECM stream failure

4189 Chassis EMM failure

4190 Chassis EMM stream failure

4191 Chassis ECMG not configured

4192 Chassis EMM not connected

4193 Chassis SCS not licensed

4194 Chassis ECMG switched so spare server

4195 Chassis Update boot loader available

4198 Chassis Failed to update stage 1 boot loader

4199 Chassis Failed to update stage 2 boot loader

4108 Chassis Application error

4203 Chassis Backup: Active backup

4205 Chassis Configuring module

Documents

Luminato SNMP Monitoring Guide - nova-minsk.comforum.nova-minsk.com/file/Luminato/Luminato_SNMP_Monitoring_0… · 26/1/2011 · MIB Node(s) Comments mib-2 system Provides generic