User guide

Release Notes

SNMP Drivers

• [Ref. #31469] When iControl is connected to a large Kaleido system, using the

Kaleido-X SNMP plug-in to retrieve alarms may cause system performance issues as well as

an Out of Memory error.

Workaround:

When attempting to retrieve multiviewer alarms, you should use the

remote multiviewer GSM logging functionality on the Kaleido-X.

SNMP Driver Creator

• [Ref. #29447] In a system involving traps but no polling, the Device communication alarm

status may persist in a Pending state.

Streaming Infrastructure

• [Ref. #24503] It is possible to lose a stream (audio or video, ALMS or thumbnail from any card

that can stream) if a frame is moved from one Densité Manager to another on the same

Application Server.

Workaround:

Restart the Darwin Streaming Server.

Third Party Devices

• [Ref. #26991] The values of the two text alarms related to the ETL 2745 LNB power supply

(Firmware Revision, Polling Interval) are not properly updated.

Workaround:

Change these text alarms’ GSM contribution from Disabled to Passthrough.

•

[Ref. #25278] When connecting an Application Server to more than one ETL 2745 LNB power

supply, the first ETL 2745 device you connect to is accepted, but subsequent ETL devices

are refused. The error message is as follows:

The service on <IP address of the Application Server> is already running.

Workaround:

Connect no more than one ETL 2745 power supply to any one Application

Server. For example, if you require three ETL 2745 devices, connect each of them to their

own, separate Application Server.

•

[Ref. #21877] iControl supports the Tektronix MTM400 firmware version 3.0 and earlier. It is

NOT compatible with firmware version 3.1.

•

[Ref. #13242] If one transport stream frequency is wrong, the MTM400 service panel shows

no data on any transport stream.

•

[Ref. #12976] Support for the various input formats (QAM, QPSK, GigE) of the Tektronix

MTM400 is strongly tied to the Tektronix firmware version. For example, support for QPSK

Note: This and other issues can be avoided by observing proper syntax when

creating host names. Please refer to Restrictions on valid host names at

http://en.wikipedia.org/wiki/Hostname.