Luminato CLI Manual 15 1 PDF
Luminato CLI Manual 15 1 PDF
Luminato CLI Manual 15 1 PDF
LUMINATO
SW RELEASE 10.2.X - Document version 4.1
1 INTRODUCTION 27
1.1 GENERAL 27
2.1 OVERVIEW 30
4 SYSTEM ADMINISTRATION 39
4.1 OVERVIEW 39
4.3 PREPARATIONS 39
4.4.1 OVERVIEW 40
2
4.4.1.1 IP address 40
4.4.1.3 Hostname 41
4.4.1.4 Gateway 41
4.4.1.6 DHCP 41
4.4.1.7 VLAN 42
4.4.1.8 TTL 42
4.4.2 CONFIGURATION 42
4.4.2.2 Hostname 43
4.4.2.2.1 Assigning 43
4.4.2.2.2 Viewing 43
4.4.2.5.1 Adding 44
4.4.2.5.2 Removing 45
4.4.3.1 Ping 47
4.4.3.2 Traceroute 48
3
4.6 TIME AND DATE 49
4.6.3 CONFIGURING 50
4.6.3.2.2 Time 51
4
4.8.2 MANAGING LOCAL USER ACCOUNTS 57
4.8.3.1 Configuration 59
4.8.3.1.1 Connection 59
4.10.1.1 Adding 66
4.10.1.2 Removing 67
5
4.11.1.3 SNMP standards 69
4.12.1 PREREQUISITES 82
6
4.12.5 SOFTWARE REVERSION 84
4.14.1.1 Viewing 87
4.15.2 MANAGING 96
7
4.15.2.1 Uploading 97
4.15.2.2 Downloading 97
4.15.2.3 Deleting 98
8
4.17.3.4.2 Manual SDP fields – streamer level 106
9
4.18.6.1 Scrambling presets 115
10
4.18.7.3.10 Scrambling algorithm 127
11
4.18.12.3 Removing an EMM stream entry 138
12
5.3.2.3 SFP interface speed 151
13
5.4 INPUT INTERFACES 161
5.4.1.8.1 Warning timeout for missing input signal or input service 165
14
5.4.3.1 DVB-S/S2 input interface configuration 177
5.4.3.1.1 Entering DVB-S or DVB-S2 input interface level configuration mode 177
15
5.4.6 MULTISTANDARD RECEIVERS LRM-A, LRM-B 199
5.4.6.2 Entering multistandard receiver input interface level configuration mode 200
16
5.5.1.1 Passthrough service timeout 210
17
5.6.1.2 MPTS IP steaming 226
18
5.6.5.5 Updating the system keys 234
19
5.7.2 PRO-MPEG FEC ENCODER CONFIGURATION 241
5.9.6.3.2 Adding an external EPG source and entering external source level configuration mode 251
20
5.9.6.3.3 EPG information service mapping 257
5.9.6.6.1 Creating an EIT stream entry and entering stream configuration mode 266
21
6 SERVICE CONFIGURATION 273
22
6.10.3.1 Associating ECM streams to scrambled services 279
23
8.1.3.2 User configurable timeouts 303
24
8.3.2.2.1 Reasons for handover 314
8.3.3.1.7 Recovering back from backup device to the main device 318
8.3.4 RECOVERING BACK FROM THE BACKUP DEVICE TO THE MASTER DEVICE 323
8.3.7 USING 1+1 BACKUP TOGETHER WITH THE STREAM REDUNDANCY FEATURE 326
25
9.3 INTRUSION ALERT 328
26
1 INTRODUCTION
1.1 GENERAL
Luminato is a high density modular platform with advanced real-time stream processing for professional video head-ends.
The chassis accommodates up to six hot swappable and auto configurable modules, and a replaceable advanced power
supply module. Modules are internally switched for cable free interconnection and easy maintenance.
There are four fans, and two Gigabit Ethernet interfaces which can be equipped with SFP transceivers for IP payload traffic
purposes.
The module slots can be equipped with input modules receiving DVB-ASI/C/T/T2/S/S2 and IP streams, or output modules
transmitting ASI, QAM, COFDM and IP outputs, or with a processing module.
The platform is managed either locally or remotely via the embedded web user interface (web UI) and/or command line
interface (CLI). It is also possible to integrate to 3rd party management software via SNMP, CLI or XML.
System is designed for reliable 24/7 operation with low operating cost. For improved reliability, system supports several
redundancy features such as backup power supply, 1+1 HW backup, stream redundancy, several NTP server addresses and
spare Conditional Access System. Configuration management with configuration transfer tools, full configuration snapshot
and restore and reliable SW revert to previous SW with previous configuration ease up headend management.
27
1.2 APPLICATION EXAMPLES
The most basic Luminato application would be a “headend-in-a-box” where both service acquisition and service
multiplexing are done in a single chassis (Figure 2). This is a typical scenario in smaller hospitality networks (e.g. hotels and
hospitals).
An application requiring more advanced features would be a distributed and IP centric headend network, where a central
headend acquires services from various sources and creates multiplexes, transmitting them to several remote headends
through a backbone network (typically a layer 3 IP network) using multicast IP streams (Figure 3).
28
The Central Management Services are located in the central headend handling service acquisition and descrambling,
channel lineup and multiplex creation, content protection and IP streaming. Central headend chassis could contain for
example only receiving modules working as IP streamer and remote headend chassis only transmitting modules, working
as EdgeQAM. The video payload and management traffic may be e.g. separated using VLANs (Figure 4).
Remote headends could also include receivers for local service insertion of e.g. local DVB-T content (Figure 5).
29
2 ABOUT THE CLI
2.1 OVERVIEW
The Luminato’s Command-Line Interface (CLI) is the primary management interface available for the device users. It
enables users to configure, manage and monitor settings and status of the device. The CLI console can be accessed locally
via USB (universal serial bus) or via telnet or SSH (secure shell) through the Ethernet interfaces.
Luminato CLI is a straightforward command interface that follows the familiar syntax of many other communications
products. It provides a single line command editor with keyboard control sequences, command help, command
completion and a buffer for recently entered commands.
Convention Description
command line The whole command-line is displayed in black Consolas –font
on light blue background
Convention Description
{a [b|c]} Square brackets and vertical line within braces indicates an optional choice within a required keyword or
command.
30
The examples use the following conventions:
Convention Description
screen
The examples use white Consolas font on black background for representing on-screen information
displayed by the command-line interpreter.
boldface
screen The examples use Consolas bold font on black background for representing text that you must literally
type in.
<…> Angle brackets enclose characters that are not displayed on the screen such as control characters (<cr> =
carriage return, passwords etc.)
The first set of commands is available to all users. Most of these commands are used to show system status.
The other modes (configure modes) are available only to users with privileged access. These commands can be used to
configure the system or to adjust system performance.
Monitor –level users cannot enter to configure-modes at all and therefore cannot change configuration. Only show
commands are available.
Admin –level user has access to all commands listed in this manual.
To learn more about user groups and user management, see chapter
31
o To exit from global configuration mode and return to root mode, type in exit or end
• To enter interface configuration mode, type in an interface command (e.g. interface dvbs 1/1) from global
configuration mode.
o Prompt:
unnamed(iface-dvbs-input-1/1)#
• Generic
• Administration
o Terminal - terminal settings for existing connection
o Reboot commands
o Logging configuration
o Network settings
o User management
o Licenses
o SW update
o Configuration management
o File management
32
o Descrambling
o Input interfaces
o Output interfaces
o FEC codec
o Processing
o Redundancy
• Device monitoring - device operations, current status, alarms
Each group has show, configure and some other action-commands in common. show –commands are always available
if not stated otherwise (for example show user -command is available only to admin -users).
To obtain a brief description of the help system, enter the following command:
help
To see a complete list of every possible commands in their full format, enter the following command:
list
To see a list of all commands containing a specific character string, enter the following command add the target character
string behind the command:
unnamed#
33
2.4.1 TAB KEY
To automatically complete a partially-typed command, press the tab key:
unnamed# con<tab>
unnamed# configure
If the command-line interpreter is unable to uniquely identify a partially-typed command with the tab key function, it will
only complete the characters which are common to the multiple commands and display a list of all the commands starting
with the completed command fragment:
unnamed(configure)# co<tab>
configure copy
When no partial command has been typed in, the tab key will show a brief list of all commands available in the current
command mode. Pressing the tab key a second time will also reveal a short descriptive text for each available command in
the current command mode.
unnamed#<tab>
traceroute
unnamed#<tab>
34
passwd Change current user password
unnamed# ?<cr>
35
When a question mark is appended to the end of a partially typed command, the command-line interpreter will list all the
commands that start with the current fragment:
unnamed# co?
co
When a question mark is entered after a command (the command must be separated from the question mark by a space),
the command-line interpreter will list all the commands that may immediately follow the currently typed command, on
the same line:
Keystroke Result
Backspace Deletes one character left of cursor
Down arrow Scrolls forward through all commands in the history buffer after
recalling the commands using up arrow-key. Repeat keystroke to
recall successively more recent commands.
36
Keystroke Result
<CTRL> + D Deletes the character at the cursor
<CTRL> + K Deletes all characters from cursor position to the end of command
line
<CTRL> + N Scrolls forward through the list of recently executed commands.
(Equivalent to the down arrow)
Note: you have to first scroll backwards using <CTRL> + P or up
arrow before using this command
<CTRL> + P Scrolls backward through all commands in the history buffer
starting from the most recent one. (Equivalent to the up arrow)
<CTRL> + T Transpose the character to the left of the cursor with the character
located at the cursor
It is important to specify this as it can have varying effects depending on the context, such as:
• disabling a feature
• disabling a particular option of the feature
• restoring default settings
• removing a single entry which was previously configured
• Using copy/paste –method in order to setup large configuration may be unreliable depending on the terminal
software used. For transferring the whole configuration from another device, copy the running configuration file
using TFTP instead.
• Please take also into account the known issues documented in the current software release notes.
37
3 PREPARING FOR SYSTEM CONFIGURATION
Prior to the configuration process, it is assumed that Luminato has been removed from its delivery box, it installed it in a
rack, it has all needed interface modules (with possibly required Conditional Access modules in them) installed into its
module slots and also SFP modules installed into GE1 and/or GE2 slots, and all the relevant cables connected. It is also
assumed that the Luminato’s management interface has been configured and a management connection is established.
The Luminato chassis is delivered along with a USB Flash drive which contains all the necessary product manuals. Please
proceed with the manuals in the following order before proceeding forward to the next chapter:
1. ReleaseNotes_Luminato
2. Luminato_mechanicalinstallation
3. Luminato_powersupplymanual (if you ordered a PSU separately or if you intend using a backup
PSU)
Have the all the system level parameters (host name, IP address, signal frequencies etc.) ready in order to speed up the
configuration process. Also, note that Luminato has a feature based licensing mechanism, meaning some features require
a separate license key to unlock. Ensure you have acquired all the necessary licenses matching your application needs.
Typically, licenses are ordered together with the hardware, the desired features unlocked at factory. Licenses can be
ordered through your sales office.
38
4 SYSTEM ADMINISTRATION
4.1 OVERVIEW
This chapter introduces all commands related to administrative tasks such as logging server configuration, time and date
settings etc.
• 172.31.255.0/24
• 172.30.[1…23].0/24
• 172.30.[1…253].[1…23]/24
• 22
• 23
• 69
• 80
• 81
• 111
• 443
• 1200
• 1201
• 1202
• 2049
• 8061
• 8071
• 54300-54331
4.3 PREPARATIONS
4.3.1 TFTP SERVER INSTALLATION
The Luminato support two file transfer protocols: Trivial Transfer Protocol (TFTP) and Hypertext Transfer Protocol (HTTP).
The most used protocol is TFTP. In order to copy files to and from the device with TFTP, you will need a TFP server
application.
39
Hint: There are many TFTP free server application available on the Internet. Select one that supports transfers of over
20 MB in size and offers the best security features.
4.4.1 OVERVIEW
This section serves as brief refresher about the IP technology.
If you are familiar with the technology, feel free to jump to the next chapter
“4.4.2”.
4.4.1.1 IP ADDRESS
The IP (Internet Protocol) address functions both as an identifier and a logical address of any network device. The IP
addresses of hosts or network interfaces are assigned either dynamically or statically; the management interface the
Luminato supports both assignment methods.
The IPv4 standard RFC 491 defines the IP address as a 32-bit integer. The most common notation is the so called quad-
dotted decimal notation, where the address is divided in four groups of 8-bits each converted in decimal notation and
separated by periods, e.g. 192.168.1.2.
Some blocks of the IP space are reserved for a specific purpose; the following address blocks are defined and reserved as
private address spaces for private networks (RFC 1918):
• 10.0.0.0 - 10.255.255.255
• 172.16.0.0 - 172.31.255.255
• 192.168.0.0 - 192.168.255.255
Private addresses are not routed on the Internet, however if necessary they can be routed to the Internet through
Network Address Translation (NAT).
• 224.0.0.0 - 239.255.255.255
NOTE! Parts of the multicasting space have a special meaning and are reserved for multicast routing group
maintenance protocols: e.g. 224.0.0.0 – 224.0.0.255.
1. Network prefix: Designates the network address common to all hosts belonging to this specific network. This is
also sometimes referred to as the routing prefix.
2. Host identifier: A unique identifier assigned to a host within a given network.
40
The network mask is used to define which part of the IP address is the network prefix and host identifier. It consists of a
contiguous sequence of ‘1’s followed by ‘0’s. To extract the network prefix from an IP address, a bitwise AND operation
between the IP address and the network mask is performed.
Example:
Binary Dot-decimal
IP address 11000000.10101000.00000000.01100100 192.168.0.100
Network mask 11111111.11111111.11111111.00000000 255.255.255.0
Network prefix 11000000.10101000.00000000.00000000 192.168.0.0
4.4.1.3 H OSTNAME
Hostnames are human readable labels assigned to network hosts, which makes referring to a host easier than directly
using a host’s IP address. Translation of a hostname into an IP address and vice versa requires the usage of a DNS (Domain
Name System).
In the Luminato, the host name is shown as part of the command line prompt and included with the system log
information.
4.4.1.4 G ATEWAY
When a host needs to communicate to another host belonging to another network a gateway is required. Gateways are
router acting as access points from one network to another.
Whenever an IP datagram needs to be transferred from one host to another, the sender compares the network prefix of
its own IP address to the network prefix of the destination IP address. If a match occurs, no gateway is needed since both
hosts are in the same network; the datagram is delivered directly. On the other hand if a mismatch occurs, then the
sending host verifies its own IP routing table: if no route is found, the datagram is sent to the default gateway.
A special use-case is host-specific routing where host to host static routes are specified to allow more control over
network access and use.
4.4.1.6 DHCP
DHCP (Dynamic Host Configuration Protocol, RFC 2131) is an Internet standard protocol developed for automatic host
configuration. It is client-server model protocol, where DHCP-configured clients (the hosts) request IP configuration
parameters (typically, IP address, lease time, subnet mask, and default gateway) from a DHCP server. The DHCP server
then replies with the queried parameters and allocates a free IP address from its IP address database. Once the lease time
expired, the host must renew its IP address or acquire a new one.
41
4.4.1.7 VLAN
VLANs are used to separate OSI Layer 2 traffic into discrete broadcast domains in order to reduce broadcast traffic and
improve security.
4.4.1.8 TTL
TTL (Time-To-Live) is a mechanism introduced in to the IP, to limit the lifespan of datagrams circulating on IP networks.
The TTL is an 8-bit field in the IP header of the datagram. Each time a datagram is forwarded by a router, its TTL value is
reduced by 1. Once the TTL value reaches zero, the datagram is discarded and an ICMP error message is sent to the
sending host.
4.4.2 CONFIGURATION
The Luminato features two management ports labelled MGMT1 MGMT2. In order to configure the management IP
settings, you must be logged in as administrator. The procedure consists of two steps:
DocumentationTest# configure
DocumentationTest(configure)#
• Common: both ports acts as switching hub ports. MGMT2 will use MGMT1’s IP settings
Caution! With Common –mode selected, take care that both ports are not connected to same switch, as this could
result in an unpredictable loop. The connected networks must be totally separated.
The session example below shows how to add a second MAC address for MGMT2 in older chassis can be fixed in the CLI.
TestChassis# configure
TestChassis (config)# interface mgmt1
TestChassis (interface-mgmt1)# upgrade-management-mac-address COMMIT
Programming management MAC2: 00:90:50:03:DD:16
42
New management MAC2 set successfully. Please reboot to activate.
TestChassis (interface-mgmt1)# exitconfigure ip address
4.4.2.2 H OSTNAME
4.4.2.2.1 A SSIGNING
Assign to the Luminato a host name for easier chassis identification. Do not use any special characters or spaces in the
name: only alphanumeric characters from a to z in uppercase or lowercase, digits from 0 to 9, and hyphen (-) are allowed.
Syntax:
hostname <string>
Example:
4.4.2.2.2 V IEWING
To view the Luminato’s hostname:
Syntax:
show hostname
Example:
Syntax1:
Syntax2:
43
Keywords & Arguments:
Hint: Select dhcp if the device will be automatically allocated management IP parameters by a DHCP server, otherwise
insert the target static values for IP_ADDRESS, NETMASK, and GATEWAY in dot-decimal notation. Setting the GATEWAY
value to 0.0.0.0 results in a no gateway configuration.
Syntax1:
Syntax2:
4.4.2.5.1 A DDING
To add a static route entry into the Luminato’s management traffic routing table:
Syntax:
44
Keywords & Arguments:
Example:
4.4.2.5.2 R EMOVING
To remove a static route entry into the Luminato’s management traffic routing table:
Syntax:
no ip route <destination_ip_address>
Syntax:
Keywords:
Caution! You will lose the IP management connection upon disabling the management interface. Once the
management interface disabled, the only way to access the device settings through the CLI is the local management USB
port.
45
4.4.2.7 V IEWING THE IP SETTINGS
To view the configured IP settings of the management interfaces:
Syntax:
show ip [address|route]
Keywords:
Example:
DocumentationTest# show ip
!!! Management-port-mode : separate
Management 1 :
Status : active
DHCP : disabled
IP address : 10.2.14.216
Network mask : 255.255.252.0
Gateway : 10.2.15.254
MAC address : 00:90:50:04:db:1c
MTU : 1500
TX bytes : 625365722
RX bytes : 3251428450
Management 2 :
Status : active
DHCP : disabled
IP address : 172.16.1.216
Network mask : 255.255.224.0
Gateway : 172.16.1.1
MAC address : 00:90:50:04:db:1d
MTU : 1500
TX bytes : 4337528
RX bytes : 278785163
IP routing table
Destination NetMask Gateway Interface State
172.20.2.0 255.255.255.0 * mpass_1_3 Volatile
172.30.3.0 255.255.255.0 * mpass_1_3 Volatile
172.20.1.0 255.255.255.0 * mpass_1_2 Volatile
46
172.30.2.0 255.255.255.0 * mpass_1_2 Volatile
192.168.200.0 255.255.255.0 10.2.15.254 MGMT 1 Persiste
10.2.0.0 255.255.252.0 10.2.15.254 MGMT 1 Persiste
10.2.12.0 255.255.252.0 * MGMT 1 Volatile
10.3.0.0 255.255.248.0 10.2.15.254 MGMT 1 Persiste
172.16.0.0 255.255.224.0 * MGMT 2 Volatile
default 0.0.0.0 10.2.15.254 MGMT 1 Volatile
DocumentationTest#
NOTE! The ‘State’ column in the IP routing table refers to the type of route entry:
4.4.3.1 P ING
Ping is to test and troubleshoot problems in IP networks. It operates by sending a series of three ICMP echo requests to
the specified IP address and reports the round-trip time for each received ICMP echo reply along with any recorded packet
loss. The utility also offers a statistical summary of the received response packets. The TTL is 64 for the ICMP request,
meaning the ICMP echo request might pass a maximum of 64 routers.
Syntax:
Keywords:
source_interface Specify the interface through which the ping destination is reachable. {MGMT1|MGMT2}
47
Example:
4.4.3.2 T RACEROUTE
Traceroute is a networking utility to trace the route the IP packets from the Luminato follow to reach the target IP address
as well as to find out where routing breaks down if the target host is unreachable.
Router’s Traceroute functions by sending a sequence of series of three UDP datagrams to the target host. The sequence
begins with the first series of UDP packets having a TTL value of 1: as the first router is reached, the TTL value reaches zero
and an ICMP Time Exceeded datagram is sent to the Luminato. Traceroute records the IP source address of the ICMP
message (=the first router) and sends the next series UDP packets with a TTL value of 2. The first router forwards the
packets and the second router replies with an ICMP Time Exceeded message. Traceroute continues so on gradually
increasing the TTL and keeping track of the routers reached, until the target host is reached and an ICMP Echo Reply is
received.
To use traceroute:
Syntax:
traceroute <target_ip_address>
Example:
• one file containing the private key with the *.key filename extension
• one file containing the public certificate with the *.pem filename extension, including the whole
chain of trust
48
The PEM files must be manually uploaded to the Luminato user file folder and then the private key and the public
certificate must be enabled through the CLI. The PEM file must include the whole chain of trust.
Syntax:
Keyword:
Example – use private key file “my_key.key” and public certificate file “my_cert.pem”:
Hint: If you’re a Linux user, you may verify the certificates using the ‘openssl verify’ command on your workstation.
Syntax:
show date
Syntax:
show clock
Example:
49
Device local time: Sat, 08 Nov 2014 06:34:47 EET
Device system time: Sat, 08 Nov 2014 04:34:47 UTC
Example explanation:
The DST Mode indicates the current Daylight Saving Time –operation mode:
4.6.3 CONFIGURING
Enter the configuration mode:
DocumentationTest# configure
DocumentationTest(configure)#
Syntax:
50
NOTE! The Luminato does not have a battery backed-up clock, therefore actual time will be lost if the power shuts
down. It is recommended to use a NTP server for clock synchronization if real time clock is needed.
Syntax:
Hint: The time zone list is too long to be included in the present document. However, since the time zones are defined
in the CLI as command keywords, you may use the command auto-completion feature with the tab key to discover the
target time zone. Please note that command keywords are always case sensitive, this applies to the time zone names too.
Example:
4.6.3.2.2 T IME
To set the time and date of the local clock source:
Syntax:
Arguments:
51
4.6.3.3.1 DST TIME PERIOD
To manually define the DST time period:
Syntax:
Example - define custom daylight start at last Sunday of March 02:00 and custom daylight end at first Saturday of
October at 03:00:
Syntax:
Syntax:
52
Keyword & argument:
When several NTP servers are defined , a number of timestamps are polled from each specified server and the most
accurate is automatically selected.
NOTE!The accuracy and reliability of the NTP synchronization feature depends on the number of servers.
The internal clock settings are overridden by the timestamp obtained from the NTP server. The internal clock is used
whenever connection to all NTP servers has been lost.
The most common implemented model, and the one and only implemented in the Luminato, is the client-server model
where clients send time requests to a defined server or servers, and the server(s) replies with 64-bit timestamps. NTP
messages are transported using the UDP (User Datagram Protocol) on the fixed port 123.
The protocol is at its fourth version and is standardized by the IETF in RFC 5905.
Syntax:
Argument:
53
4.6.3.4.3 R EMOVING NTP SERVERS
To remove a NTP server entry:
Syntax:
no server <index>
Syntax:
show ntp
Example:
NTP servers
Server | IP address | Reachable | Sent pkts | Rcvd pkts
1 |172.16.0.1 |Yes |35661 |35661
2 |0.0.0.0 |No |0 |0
3 |0.0.0.0 |No |0 |0
Syntax:
configure terminal
Example:
54
4.7.2 SHOW SETTINGS
To see a summary of the terminal settings:
Syntax:
show terminal
Example:
Syntax:
Example:
NOTE! Some remote host applications do not require you to specify the screen length and can resolve the screen
length automatically. Configure this setting if the pagination doesn’t work correctly.
Syntax:
length <lines_per_screen>
Argument:
55
Example:
unnamed(terminal)#
Syntax:
Syntax:
[no] vt100-colour
Keyword:
In small-scale applications, such as hospitality, users are typically managed and stored locally on the Luminato.
In larger networks encompassing several main headends and sub-headends, user accounts are managed centrally on one
or several remote servers to reduce operational complexity and maintain a globally consistent security policy across the
network. Luminato supports LDAP (Lightweight Directory Access Protocol) for centralized user login authentication.
56
4.8.1 USER GROUPS
In the Luminato, each user account is assigned to a user group. The user group determines the access rights of a user
account. There are four user groups:
1. Admin group
• factory default:
o username: admin
o password: admin
• User has full access to all configurable parameters including administrative settings
2. Install group
• no usernames by default
• User has full access to all configurable parameters except administrative settings: cannot create/change admin-
users.
3. Oper group
• factory default:
o username: oper
o password: oper
• Access is limited only to configuration of services and view of network settings.
• User has no access to administrative settings or procedures like software upgrade.
4. Monitor group
• factory default
o username: guest
o password: guest
• Has read-only access for monitoring purposes only.
• Cannot change any settings.
DocumentationTest# configure
DocumentationTest(configure)#
Syntax:
show user
57
Example:
Syntax:
Example:
We create a monitor group user account with login name “lightUser” and password “resctricted”.
Syntax:
Example:
NOTE! The password needs to be entered twice to prevent mistyped password definition.
58
4.8.2.3.2 S PECIFIC USER
To change the password of a specific user account (available to admin and install group):
Syntax:
Example:
NOTE! Install group users cannot create or modify admin group user accounts.
Syntax:
no user <username>
Example:
When a user attempts to log into Luminato with LDAP remote user authentication enabled, the entered user credentials
are first matched against the user accounts stored locally in the Luminato: if no match occurs, the entered user credentials
are verified from the defined Directory System Agent (= the LDAP server) via an LDAP seach query using search
parameters preconfigured in Luminato’s configuration. These search parameters are configured by an admin level
Luminato local user.
4.8.3.1 C ONFIGURATION
Enter global configuration mode as described in chapter “Entering and exiting command modes”, p. 31.
4.8.3.1.1 C ONNECTION
4.8.3.1.1.1 SPECIFYING THE LDAP SERVERS
To specify a LDAP server:
Syntax:
59
Arguments:
Syntax:
Keyword:
Syntax:
1. Collect the server’s CA certificates (the whole chain of trust) into a single gzipped tar file. The filename extension
MUST be .tgz.
2. Upload the tar file to the target Luminato using the copy command or the web UI’s Filemanager.
To learn how to upload a file with the ‘copy’ –command, see chapter
“Uploading”, p. 97
3. Copy the tar file to Luminato’s SSL certificate directory using the copy <tar_file> ssl-certs command
4. Enable peer certificate verification in Luminato with the ldap tls-checkpeer command
60
To copy the tar file to Luminato’s SSL certificate directory:
Syntax:
Argument:
Syntax:
NOTE! Self-signed certificates will be rejected and will cause a verification failure.
Syntax:
Syntax:
4.8.3.1.1.4.3 P ASSWORD
To specify the password with which to bind to the DSA:
61
Syntax:
Syntax:
Syntax:
Argument:
Syntax:
62
4.8.3.1.2.3 LOGIN ATTRIBUTE
To specify which attribute corresponds to the user’s login name data in the DSA:
Syntax:
Keyword:
Syntax:
Example:
We want to search users that are classified in the DSA as Luminato administrators and that do not reside in Turku.
NOTE! The OR Boolean operator ‘|’ is not currently supported by the CLI. To circumvent this restriction, convert the
OR operations into AND operations by applying De Morgan’s law (!(|(A)(B)))=(&(!(A))(!(B)))
63
4.8.3.1.2.6 GROUP MEMBERSHIP ATTRIBUTE
In the Luminato, each user is assigned to a user group. The user group defines the access rights of a user. With LDAP login
authentication, the attribute that defines the user’s group membership information is queried. This attribute is by default
expected to be gidNumber.
The attribute value must contain a group ID number, or a textual group name. The allowed groups are admin (or 500),
install (or 501), oper (or 601) and monitor (or 602).
To specify which attribute corresponds to the user’s group membership information in the DSA:
Syntax:
Keyword:
Since this specific application of the LDAP is concerned with user login information, the entry queried should obviously
belong to an object class representing users. The expected objectClass when performing a search query is by default
posixAccount, but you can change the objectClass name in accordance with the schema used in your directory system. If
the specified objectClass is not found during the search query, the user login will fail.
Syntax:
Keyword:
NOTE! Ensure that the hostname of the Luminato is resolvable, otherwise the login will fail.
64
To enable or disable logins on a per-host basis:
Syntax:
Keyword:
Syntax:
Example:
Syntax:
show ldap
Example:
65
DocumentationTest(configure)#
Syntax:
reboot COMMIT
Syntax:
The Luminato supports detailed logging via syslog. However, the size of the internal log is limited by the available memory.
Therefore, the internal log is rotated so that only the latest log entries remain, when the log becomes full.
This limitation can be overcome by using an external syslog server. In the Luminato, you may specify up to four external
syslog servers.
4.10.1.1 A DDING
To add an external syslog server entry:
Syntax:
66
Arguments:
4.10.1.2 R EMOVING
To remove an external syslog server entry:
Syntax:
To enable/disable event logging based on event severity level and log storage location:
Syntax:
Arguments:
67
storage2 Second log storage location definition. {external|non-
volatile|volatile}
storage3 Third log storage location definition. {external|non-
volatile|volatile}
Example:
We want to store emergency -level syslog messages to non-volatile and volatile memory and external servers; notice -level
messages to volatile memory and no storage for information -level messages.
NOTE! Write-operations to flash memory reduce the lifetime of the component itself: avoid configuring frequently
occurring events (such as notice) to persistent (internal) logging.
68
4.11.1.2 SNMP ENTITIES
FIGURE 6: MANAGERS SEND QUERIES THROUGH PORT 161 AND THE AGENT RESPONDS THROUGH THE SAME PORT. THE AGENT SENDS TRAPS
THROUGH PORT 162 WHENEVER A TRAP GENERATING EVENT OCCURS IN THE MANAGED DEVICE.
In the SNMP, there are two types of entities: managers and agents. The managers (usually referred to as Network
Management Stations or NMSs) send queries to the agents (managed network devices such as Luminato). The agents may
either respond to NMS’s queries or send messages called traps whenever a trap generating event has occurred. In
practice, a NMS is a server running a network management software suite and the agent a piece of software in the
managed device.
Luminato supports SNMP versions 1 and 2c. SNMPv2c2 is an experimental community-based administrative framework
version of SNMPv2, where every message is associated to a community.
• The ro community string lets you read data values, but doesn’t let you modify the data. The default name is
‘public’.
• The rw community is allowed to read and modify data values. The default name is ‘private’.
69
Caution!In SNMPv1 and SNMPv2c, community strings are embedded as plain text within the SNMP messages and
traps, thus making the authentication vulnerable to packet sniffing!
In SNMP, managed object are hierarchically organized in a tree structure: the OID can be directly derived from this
structure. This permits to easily identify object dependencies.
Each node in the tree can be specified either in its textual or decimal form, each separated by dots. The top-most node is
called the root-node. Any node having sub-nodes is called a sub-tree and a node having no sub-node is called a leaf
node. The leaf nodes are usually monitored variables or parameters.
Figure 7, p.71, illustrates the MIB-tree for the OID of Teleste Corporation’s root node 1.3.6.1.4.1.3715 or textually
iso.org.dod.internet.private.enterprises.Teleste.
70
FIGURE 7: MIB-TREE STRUCTURE FOR OID 1.3.6.1.4.1.3715 (PATH ILLUSTRATED IN BLUE)
NOTE! Upon each SW release, new object definitions might have been inserted into the MIBs and/or some changes
might have occurred in the definitions. It is therefore good practice to keep your NMS object database up to date and
always download and recompile the MIBs after upgrading Luminato software.
Luminato provides 15 MIB files in one ZIP-file for easy downloading.Table 1 gives a brief description for each node of
interest contained in the provided MIB files. The complete definitions of all objects can be obtained by reading the MIB
files in any text- or MIB-editor.
TABLE 1: THE LUMINATO PROVIDED MIB FILES ALONG WITH A BRIEF EXPLANATION FOR EACH NODE OF
INTEREST.
71
MIB Node(s) of interest Comment
Contains the definition for trap
coldStart
1.3.6.1.2.1.interfaces(2) Provides information about the
MGMTx and GEx interfaces such
as, Mtu, physical address, speed
etc.
1.3.6.1.2.1.31.1.ifXTable(1) Provides statistical information
about the MGMTx and GEx
interfaces in form of various
counters such as multicast and
broadcast packets sent etc.
RFC1213-MIB 1.3.6.1.2.1.4.ipAddrTable(20) MGMT ports’ index, IP address
and netmask.
ENTITY-MIB 1.3.6.1.2.1.47.1.1.entPhysicalTable(1) Provides information about the
monitored physical entities such
as, module type, slot number,
serial number etc.
RFC1155-SMI Definition of SMI names,
datatypes and definition syntax
SNMPV2-TC Textual conventions for SMIv2
SCTE-ROOT 1.3.6.1.4.1.scteRoot(5591) Definition of the SCTE root and
scteRoot.scteHmsTree(1) HMS
SCTE-HMS- 1.3.6.1.4.1.5591.1.propertyIdent(1) Definition of the objects under
ROOTS 1.3.6.1.4.1.5591.1.insidePlantIdent(11) the SCTE HMS tree
1.3.6.1.4.1.5591.1.1.currentAlarmTable(2) currentAlarmTable is a sequence
of currentAlarmEntry providing a
list of currently active
warnings/errors.
1.3.6.1.4.1.5591.1.1.discretePropertyTable(3) Keeps references to possible
status codes.
Reserved for future needs to filter
out unnecessary status codes
from monitoring.
SCTE-HMS- 1.3.6.1.4.1.5591.1.11.headEndIdentMib(0) Defines the root OID for indoor
HEADENDID headend device MIBs
ENT-MIB
SCTE-HMS- 1.3.6.1.4.1.5591.1.11.2.1.1.1.2.heCommonLog A persistent list of events that
HE- Table(3) have been logged.
COMMON-
MIB
UCD-SNMP- 1.3.6.1.4.1.2021.laTable(10) CPU load 1, 5, 15 min averages
MIB
TELESTE- 1.3.6.1.4.1.[Category](3715).Luminato(17) Definition of proprietary data
ROOT-MIB 1.3.6.1.4.1.[Category](3715).common(99) types and root nodes
1.3.6.1.4.1.3715.99.1.3.elementInformation(1) Minimal equivalent of mib-
2.system
1.3.6.1.4.1.3715.99.1.elementStatus(2) Statuses of general nature such as
fan, HW, SW etc. status.
1.3.6.1.4.1.3715.99.1.3.controlTrapReceiverTa A table of the manager trap
ble(5) receiver addresses, ports and
72
MIB Node(s) of interest Comment
communities. The total number
of entries cannot exceed
controlMaxNumberTrapReceiver
s. An entry is deleted from this
table by setting its IP address to
'0.0.0.0'.
1.3.6.1.4.1.3715.99.2.moduleInformation(1) Provides information about
modules such as slot number,
HW-type, serial number etc.
1.3.6.1.4.1.3715.99.2.2.1.1.statusInternalTemp Provides modules’ temperature,
erature(3) in 0.1 C° units. Value is zero (0),
if temperature is not available.
1.3.6.1.4.1.3715.17.general(1) Equivalent of mib-2.system.
Provides cumulative uptime of
device.
1.3.6.1.4.1.3715.17.2.statusCodeDeviceTable(2 These tables describe possible
) status codes for objects on
1.3.6.1.4.1.3715.17.2.statusCodeModuleTable( various levels: device, module,
3) interface, TS, service and PID
1.3.6.1.4.1.3715.17.2.statusCodeInterfaceTabl level.The objects may represent
e(4) real objects or classes.
1.3.6.1.4.1.3715.17.2.statusCodeTransportStre
amTable(5) The monitoring system or user
1.3.6.1.4.1.3715.17.2.statusCodeServiceTable( shall not poll these tables to
6) detect object states. Use these
1.3.6.1.4.1.3715.17.2.statusCodePidTable(7) tables only to obtain the textual
description of the alarms.
73
MIB Node(s) of interest Comment
1.3.6.1.4.1.3715.17.3.ifExtTable(1) Provides information about the
names and numerical labels the
physical and logical interfaces.
Extract the MIB files from the mibs.zip file (Figure 8).
74
FIGURE 8: EXTRACTING THE MIB FILES.
Hint: Some of the provided MIB files point to other MIB files; most MIB compiler should be able to resolve the file-
dependencies automatically when compiling. However, if for some reason your compiler fails, try compiling the MIB files
one by one in the order stated in the order.txt file (included in the mibs.zip package).
DocumentationTest# configure
DocumentationTest(configure)#
To specify sysLocation:
Syntax:
75
Argument:
Syntax:
Argument:
Syntax:
Caution! In SNMPv1 and SNMPv2c, community strings are embedded as plain text within the SNMP messages and
traps, thus making the authentication vulnerable to packet sniffing!
If you need more severity levels or if you want to customize the severity level settings of individual alarms with
connections to modules/inputs/TS/services/PIDs, you may use one of the two featured proprietary extended trap
generation modes: general or specific.
76
When using the extended trap generation mode, you may disable the HMS trap generation mode if necessary.
NOTE! The extended trap generation modes are meant for advanced users only and therefore is implemented only
the CLI.
Syntax:
Keyword:
Syntax:
Keywords:
Syntax:
Keyword:
77
4.11.3.5 E XTENDED TRAP SEVERITY SETTINGS
Caution! This is an ‘advanced user’ feature, use with caution! Illogical or invalid severity settings may have in
unexpected results and may, for example, impair the 1+1 backup triggering functionality.
When using the extended trap generation mode, you may create sets of severity rules for specific status codes applied to
user defined parameters such as, module, interface, SID, PID etc.
NOTE! The new severity settings affect only general or specific extended traps.
Syntax:
• The priority_number, for example 500, is used to order rules. A smaller order number means a
higher priority in the severity rule table. Due to some technical restrictions, the used
priority_numbers should be of the same order of magnitude: for example within the range of 10-
99, 1000-9999, or 10000-99999.
• module defines which module(s) is/are affected by the severity rule
• reason defines which status code(s) is/are affected by the severity rule
• P defines which parameter(s), if any, is/are affected by the severity rule. P is defined by up to four
sub-parameters. P use, if applicable, the following general format:
o P = <module_type> <input/ouput_interface_index> <SID/PID>
module_type = {*|[not] {0|1}, where:
• 0 = input
• 1 = output
input/ouput_interface_index = {*|[not] {0…}}
SID/PID = {*|[not] {0…}}
o The actual parameters may be extrapolated by analyzing actual extended specific trap
content. For example, we can see from Figure 9 that P = 1 8 1580
78
FIGURE 9: EXTRAPOLATING PARAMETERS FROM AN ACTUAL EXTENDED SPECIFIC TRAP.
Syntax:
79
4.11.3.5.4 U SE EXAMPLE
We have a fresh installation and have no rules defined:
Then, for instance, we have a large number of PID Missing –events (by default a warning severity level event), but we
would like to see those only as notice.
Then, we would like to receive all PID Missing events from module 5 as error –level severity traps. This would be a more
specific rule, so its priority should be before 500; say 450.
80
| 500 | all | 2 - PID missing | |notice |
unnamed(configure)#
Last, if we would like to clean all others events, we could place the last rule which match anything and sets severity to
nominal.
unnamed(configure)# severity rule 999 module all reason all severity nominal
unnamed(configure)# show severity rules
| N | Module |Reason |Params |Severity |
| 420 | 5 | 2 - PID missing |* * 16 |alert |
| 430 | 5 | 2 - PID missing |1 2 |critical |
| 450 | 5 | 2 - PID missing | |error |
| 500 | all | 2 - PID missing | |notice |
| 999 | all |all | |nominal |
unnamed(configure)#
SNMP traps are generated based on internal events. Each of those events can be seen in the syslog. Every event belongs
to one of severity category: from high priority EMERGENCY to low priority DEBUG.
With the trap severity filter, you may choose which event severity level will generate traps in a similar way as the syslog’s
severity filter.
NOTE! coldStart traps will not be affected by the trap severity filters and will still be generated: only
heCommonAlarmEvent traps are affected.
Syntax:
Keyword:
81
4.11.3.7 T RAP DESTINATION ADDRESS
To be able to send traps, you must specify the IP destination address for the trap messages (the address of the NMS). The
command below works incrementally, you may specify up to five trap destinations by entering each address separately.
Syntax:
Example:
• Software upgrading is a licensed feature. The license specifies which (major) releases it entitles.
• Minor (maintenance) releases do not require separate licenses
• The software license is uniquely tied to the device, meaning that the product key may be used only
in one device.
• The software is located in the chassis’ mainboard: activating a new software requires a reboot of
the chassis, thus causing a pause in service delivery unless a 1 + 1 backup system is present.
• Upgrading to a software release which the software license does not entitle to use will cause the
software to enter to an Evaluation mode.
• Consult chapter 0 below for more information on license related procedures.
4.12.1 PREREQUISITES
Depending on the chosen protocol, you will need either a TFTP or HTTP server.
Example: Luminato ships from factory with version 7.2.2, so you are entitled to receive
all 7.x.x (and older) releases: 7.2.6, 7.4.2, 7.12.5 etc.
82
The software license specifies this MAJOR number (7 in the above example). The software compares the license specified
number to its own MAJOR version number. If the license number is equal or greater than the running software number,
the software will function normally. Otherwise the device will enter the Evaluation mode.
To verify the entitled SW release version, use the show license chassis
command as described in chapter “Viewing licenses”
Syntax:
show version
Example:
Syntax:
reboot This optional command reboots the Luminato automatically after software update
completion.
Example:
83
7/7 SW Update Completed Succesfully100
Software Update Succesful. Waiting for reboot to complete update
DocumentationTest(configure)#
NOTE! To activate the new software version, reboot the device. Use the optional ‘reboot’ keyword (see above) to
automatically reboot the device after SW update completion.
To learn how to reboot the device manually, see chapter “System reboot”
Syntax:
Caution! Reverting to old software version will also revert to old configuration (the last known configuration used
with old software) and the chassis will reboot, thus causing a pause in service delivery unless the 1 + 1 backup system is in
use. To learn more about 1 + 1 backup system see chapter “1+1 backup”
Typically, the proper set of licenses is ordered altogether with the hardware and is pre-installed at factory. However, as
your business grows, additional licenses may be needed, for example, if the quantity of needed scrambled services
exceeds what the current license allows. Some licenses, such as demo licenses, are expirable and will expire after a certain
time.
Syntax:
84
Example:
Syntax:
show licenses
Attach the above information into your email order and send it to our local sales representative.
Syntax:
85
Example:
All submodule running configurations are stored as separate files in Luminato’s non-volatile memory, organized at the
bottom level of a three level directory tree structure (Figure 10) by module type.
chassis
previous current
submodule submodule
submodule submodule
type "k" type "m"
type "a" type "b"
FIGURE 10: CONFIGURATION DIRECTORY TREE STRUCTURE. ERASING AT AN UPPER LEVEL WILL REMOVE ALL THE CONFIGURATION
FILES OF THE SUB LEVELS.
NOTE! There can be several different configuration files per slot. Luminato “remembers” the configurations of any
previous module type which have been plugged into the same slot.
The Luminato’s CLI running-config command extracts the running configuration information from the active
configuration file and outputs it as series of CLI commands, depending on the used command, either on screen or to a 8-
bit ASCII text file. The resulted configuration file may be copied, edited and run as a script file on any Luminato.
86
NOTE! The running-config file is only a representation of the actual running configuration; if you need a one-to-one
copy of the running configuration for configuration backup, you should use the configuration snapshot feature instead.
You may also take a configuration snapshot which is an exact copy of the running configuration. The generated file
contains not only the configuration files, but also all the files generated or uploaded by the user (captured tables, NIT
wizard generated table amongst other things). This file format is binary and not editable.
DocumentationTest# configure
DocumentationTest(configure)#
4.14.1.1 V IEWING
Hint: If your terminal application supports the copy & paste feature, you may select and copy directly from the
terminal application’s window the command lines of interest and paste them into a standard 8-bit ASCII text editor
(Notepad, vi, etc).
Caution! Depending on the terminal software used, using the copy & paste method may be unreliable for transferring
large number of lines in the running configuration. For transferring whole configuration from one device to another, the
copy running-config command should be used instead.
Syntax:
Example:
87
LAS-B
DocumentationTest#
Syntax:
show running-config
Example :
NOTE! To save document space, the session example below shows only a small portion of the show running-
config command output.
NOTE! Rows starting with an exclamation point ‘!’ are comment lines and are not executable command lines. Their
purpose is to provide additional information to the user and also to improve readability.
88
4.14.1.1.3 M ODULE RUNNING CONFIGURATION
To view the running configuration of a specific module:
Syntax:
Arguments:
Example:
NOTE! To save document space, the session example below shows only a fragment of the command output.
• by stream direction
• by input signal type
• by signal type and stream direction (applies to a few module type)
89
4.14.1.1.4.1 BY STREAM DIRECTION
To view the running configuration of a specific interface streaming to a specific direction:
Syntax:
Arguments:
Example:
Syntax:
Arguments:
90
Example:
Syntax:
Arguments:
Example:
91
packet-format udp
no low-packet-jitter-mode
!
!Processing configuration
!
mode service
ts-id 2001
network-id 0
original-network-id 0
network-name "Network1"
pid-allocation-mode follow
DocumentationTest#
Syntax:
Arguments:
Example:
NOTE! Removing the configuration of an active module will cause the module to be rebooted.
Syntax:
92
Argument:
NOTE! Removing the configuration of an active module will cause the module to be rebooted.
Syntax:
eraseconf COMMIT
NOTE! The whole Luminato will rebooted. The management IP settings will be preserved in order to not lose
management connection.
Syntax:
Arguments:
93
Example:
There are two alternate methods for importing the running-config file:
• regular: continuous scanning of changes in incoming PSI/SI tables is enabled during running-config file import,
which can be slow with large configurations
• boosted: continuous scanning of changes in incoming PSI/SI tables is disabled during running-config file import,
which can considerably speed up the import process with large configurations
Hint: When importing a configuration file, the configuration is appended to the existing running configuration: if you
wish to import without preserving the existing running configuration, you will need to return the device to its factory
default settings.
Syntax:
Arguments:
Example (abridged):
94
Executing row 4: !
Executing row 5: ! HOST configuration
Executing row 6: !
Executing row 7: configure
Executing row 8: hostname DocumentationTest
Executing row 9: !
Executing row 10: ! general cable configurations
Executing row 11: !
Executing row 12: configure
Executing row 13: cable rangingperiod 20
Executing row 14: cable T4timeoutmultiplier 1
Executing row 15: cable loadbalancer mode static
Executing row 16: !
Executing row 17: ! interface cable-downstream configuration
Executing row 18: !
Executing row 19: configure
Executing row 20: cable annex A
Executing row 21: interface cable-downstream 1 frequency 298000000
Executing row 22: interface cable-downstream 1 interleaver 128:1
Executing row 23: interface cable-downstream 1 modulation 256qam
Syntax:
Arguments:
NOTE! The configuration backup file is software version locked and is not compatible with any other software
versions than the one it was created with. For example, a snapshot created with SW revision 6.2.1 won’t work with 6.2.2.
Syntax:
factorydefaults COMMIT
95
Keyword:
NOTE! This command will remove all configuration files and management IP settings.
Caution! Perform a total reset to factory defaults only with a local management (USB) connection! Failing to comply
will result in lost management connection.
Syntax1:
dir
Syntax2:
show files
Example:
DocumentationTest# configure
DocumentationTest(configure)#
96
4.15.2.1 U PLOADING
To upload a file to the Luminato:
Syntax:
Arguments:
Example:
Here, we upload to the Luminato a file named issue_A.txt through TFTP server 192.168.0.98 and preserve the original
file name.
NOTE! The following special characters are not allowed in file names: #&;`|*?~<>^()[]{}$\
4.15.2.2 D OWNLOADING
To download a file from the Luminato:
Syntax:
Arguments:
97
Example:
Here, we download from the Luminato a file named x through TFTP server 192.168.0.98 and re-label the file as
mystery_file.txt.
NOTE! The following special characters are not allowed in file names: #&;`|*?~<>^()[]{}$\
4.15.2.3 D ELETING
To remove a file from the user file folder:
Syntax:
Arguments:
Example:
In order to be able to automatically route payload IP traffic between chassis in a multi-chassis environment, Luminato
needs to know which GE ports are interconnected via an external switch network. To this end, you must provide
interconnection information by assigning the GE ports to connection groups.
98
NOTE! Currently, only the Luminato EIT processing module LPE-A is able to use automatic payload routing for
interchassis EIT information traffic. LPE-A’s EIT information ingress and egress is performed via temporary ad-hoc IP
streaming, invisible to the user.
DocumentationTest# configure
DocumentationTest(configure)#
Syntax:
show group-chassis
Example:
Syntax:
Arguments:
99
Name Description Allowed values
password The login password associated to the specified login name <string>
IP_address The management IP address of target group member IPv4 address in dot-decimal notation
NOTE! You may insert several members at once by separating each entries with a comma, e.g. configure group-
chassis admin:[email protected], admin:[email protected], admin:[email protected]
Example:
We want to create a multichassis management group labelled “myGroup” and populate it with the localhost and host
10.2.14.217:
NOTE! Management port’s IP address cannot be modified if it is member of a multichassis management group. You
must first remove it from the group in order to be able to modify it.
To learn how to change the management port settings, see chapter “IP address, netmask & default gateway”.
Syntax:
Arguments:
NOTE! You may remove several members by giving a comma-separated IP address list of the target members, e.g.
configure no group-chassis myGroup 10.2.14.217,10.2.14.217
100
4.16.2.4 R EMOVING MANAGEMENT GROUPS
To remove a management group:
Syntax:
no group-chassis
Syntax:
Example:
We have a multichassis system with 2 chassis interconnected: 10.2.14.216 and 10.2.14.217. Their payload ports are
interconnected through GE1. We label this connection group myPayload1.
Syntax:
Example:
101
4.16.2.7 R EMOVING A PAYLOAD CONNECTION GROUP MEMBER
To remove a member from a connection group:
Syntax:
Example:
Syntax:
4.17.1 OVERVIEW
4.17.1.1 SAP
Session Announcement Protocol (SAP) is an IETF issued experimental protocol1 for advertising multicast sessions and
transmitting periodically session descriptions to a well-known multicast address and port. SAP listening applications
construct a guide of all advertised multicast sessions.
1 RFC 2974
102
4.17.1.2 SDP
The SAP typically uses the IETF standard Session Description Protocol (SDP)1. SDP is a protocol used for describing
multimedia sessions such as media type, format and all associated properties. The SDP session description is plain UTF-8
encoded text.
• Session level
• Media level
4.17.2 SAP AND SDP IN LUMINATO
With the SAP and SDP feature, the devices in the system can “see” a list of multicast streams that are available from other
devices: Luminato sends SAP messages to announce its SPTS/MPTS streams so that 3rd party equipment can see a list of
available streams. Luminato may also vice versa receive SAP messages to form a list of the advertised multicast sessions
making easier the creation of IP inputs and service routing.
In Luminato, the SAP multicast host group is defined at chassis level. SAP announcement can be globally enabled or
disabled on chassis level and overridden for each output IP stream separately.
Some of the announcement fields are automatically generated. In addition to the automatically generated SDP fields, you
may also insert manually additional SDP session description fields.
4.17.3 CONFIGURING
The configuration procedure consists of the following steps:
DocumentationTest# configure
DocumentationTest(configure)#
Syntax:
show sap
Example:
1 RFC 4566
103
4.17.3.2 G ROUP ADDRESS
The SAP messages are transmitted to and received from a multicast group address (SAP multicast host group). The factory
default address is 239.255.255.255.
Syntax:
Arguments:
Example:
NOTE! SAP multicast address should be within the same scope as the multicast sessions that are being announced to
ensure the recipients of the announcements are within the scope of the sessions the announcements describe.
The recommended SAP announcement interval may be calculated by using the following formula1:
Syntax:
1 RFC 2974
104
Example – interval 10 seconds:
Session-level section:
v=0
s=<session_name>
t=0 0
, where
interface_ip = IP address of the originator of the session (or virtual address if in use)
session_name = Service name for SPTS, Alias name for MPTS if exists, “Stream-
239.0.0.1:1234” if alias is empty.
service_type = always “video” for MPTS streams, “video” or “audio” for SPTS streams
In addition to the automatically generated SDP fields, you may also insert manually additional SDP fields.
105
NOTE! Chassis level additional fields are inserted into the SDP session description of all IP outputs in addition to the IP
stream level additional fields.
Syntax:
The SDP session description fields’ definitions fall out of scope of the present
document, refer to RFC 4566 for more detail.
Syntax:
The SDP session description fields’ definitions fall out of scope of the present
document, refer to RFC 4566 for more detail.
Syntax:
106
Keyword:
Syntax:
Syntax:
Example – restoring the chassis level SAP settings for interface 2/1.1:
107
4.17.3.7 E NABLING / DISABLING SESSION ANNOUNCEMENT RECEPTION
Luminato is able to receive SAP session announcements for easier service routing through the web UI.
Syntax:
Keyword:
NOTE! Technically, all inserted output modules join the user configured SAP multicast host group and are listening to
incoming SAP messages using an internal IP input hidden from the user. That is why at least one output module is
required in order to be able to use the SAP reception feature.
NOTE! In order to be able to receive SAP announcements with VLANs, you must first allocate module slot payload IP
addresses to the target VLANs. By default, the VLAN payload IP addresses are undefined right after VLAN creation.
The present chapter describes the compulsory procedures for setting up the CAS
connections for ECMs and EMMs, laying groundwork for service scrambling. The actual
procedures for service scrambling are introduced in chapter 6.10.3
108
4.18.1 DVB-CSA BASED CONDITIONAL ACCESS SYSTEMS
109
The EMM messages are issued much less frequently than ECMs and are subscriber specific; subscriber identification is
done through a smart card in the receiver. Without proper EMMG issued authorization the receiver won’t decrypt the
CWs and descramble the stream.
• LAS-B
• LQM-B
• LCM-A
• LCM-B
In the context of digital video distribution, AES scrambling is mainly used for service encryption in IPTV (Internet Protocol
TeleVision) distribution. Typically, the CAS architecture in IPTV distribution differs from the one in traditional digital video
broadcasting. The main difference is that the entitlement messages (EMMs) are not usually included in the transporting
stream: the authorization to decrypt services is typically negotiated directly with CAS servers.
Our AES implementation features three AES modes: CBC and two ECB variants. AES is intended to be used in CAS systems
based on ECMs and the SimulCrypt interface. Due to the complex nature of the subject, the detailed description AES
scrambling algorithms are not within the scope of the present document.
The SimulCrypt interface and ECMs are explained from chapters 0 to 0. See also
figure Figure 11.
110
To learn more details about AES, see the AES standard and the ISO/IEC 18033-3
standard.
Samsung LYNKTM DRM (Digital Rights Management) is a fully software-based digital conditional access CAS solution: the
LYNKTM DRM server resides in Luminato and does not require any additional hardware or separate chipsets.
Samsung LYNKTM DRM uses AES128-CBC encryption without padding. Once the embedded LYNKTM DRM server has been
enabled and the required licenses successfully activated, an ECMG and EMM stream will be automatically configured.
• Samsung’s LYNKTM DRM license key to allow the descrambling of LYNKTM DRM scrambled
services in STBs or TVs. Requires activation.
• online: requires Internet access from MGMT1 or MGMT2. The license activation key is
automatically retrieved from Samsung’s server.
• offline: requires activation key. The activation key is acquired from your Samsung’s sales
services.
• LAS-C
• LAS-D
• LRX-X
• LQM-A/C
• LIM-A
• LIC-A
111
4.18.3.3 TV OR STB SYSTEM REQUIREMENTS
Make sure your TV or STB system meet Samsung’s LYNKTM DRM requirements1:
Hardware:
Software:
4.18.3.4 C ONFIGURING
Enter the configuration mode:
Syntax:
[no] shutdown
Keywords:
Syntax:
1 Requirements subject to modifications. Consult Samsung’s tech support for up to date information.
112
NOTE! You will be able to activate the license only when the embedded LYNK DRM server has been enabled and fully
started.
To learn how to enable the server, see chapter “Enabling & disabling the server”
When requesting the license activation key from your Samsung contact person, you will need to provide him/her with the
HW unique key displayed with the show cas lynkdrm -command. The activation key links the hardware unique key to
the license key thus binding the license to this specific chassis.
NOTE! You will be able to to activate the license only when the embedded LYNK DRM server has been enabled and
fully started.
To learn how to enable the server, see chapter “Enabling & disabling the server”
Syntax:
Syntax:
Syntax:
Example:
113
Max Clients:
HW Unique Key: 4BAC51EF83BA6EA4
License Key:
Deactivation Key:
Message: License key is not supplied.(Activation key not verified)
DocumentationTest(lynkdrm)#
4.18.4 LUMINATO CAS INTEROPERABILITY
Luminato’s DVB SimulCrypt content protection solution is designed in accord with the DVB standards. Therefore all CA
system that is designed strictly according to these standards should be compatible with Luminato. Contact our customer
support services for latest list of tested CA systems.
NOTE! Both EMM TS packet and section formats are supported from release 3.1.23 onwards.
• Ensure that your Luminato and CA system ECM generator/EMM injector IP network settings are
properly configured.
• Have the following CA system related information available (usually provided by CA system
vendor):
o Super CAS ID
o Access criteria's
o SimulCrypt protocol version
o ECMG IP-address and port
o EMM client ID, data ID, port number and required EMM bandwidth.
o Data type
4.18.6 GENERAL CA SETTINGS
This chapter explains the configuration procedures for conditional access settings of general nature:
114
4.18.6.1 S CRAMBLING PRESETS
4.18.6.1.1 G ENERAL
As per ISO/IEC 13818-1 specification, packets may be scrambled either at PES (Packetized Elementary Stream) level or at
TS level. In Luminato, you may define which PES are scrambled either on stream type basis by selecting from one of the
predefined PES type ID sets1 or by defining the PID(s) of the target PES(s). In the UI, the PESs are referred to as
components.
4.18.6.1.2 C ONFIGURING
To make service scrambling configuration easier, output service scrambling is based on user-configurable presets. These
presets define which component types are scrambled for newly created output services.
NOTE! Changing the component scrambling presets does not change the settings of existing services, unless explicitly
applied to all scrambled services!
Syntax:
show presets
Example:
Syntax:
NOTE! You may specify several component types by entering them as a comma separated list (see the example
below).
1 The predefined type sets are based on the ISO/IEC 13818-1 stream type assignments
115
Keywords:
NOTE! If you entered the elementary stream type ID 6 (ES packets containing private data)1, subtitles, teletext and
AC3 audio will also be scrambled, since the elementary stream type of those streams is ES packets containing private data.
Example – scrambling preset to scramble video, non AC3 audio, teletext and ES ID 128 (=0x80):
Syntax:
Syntax:
1 ISO/IEC 13818-1
116
Keywords:
The Luminato proprietary Extended CP setting change the way the CP duration value is interpreted as minutes instead of
seconds, for example the default CP value 10 s will turn into 10 min.
Syntax:
Keyword:
DocumentationTest(cas)# extended-cp
DocumentationTest(cas)# ecmg 1 cp 1440
DocumentationTest(cas)#
Caution! Please bear in mind that the Extended CP violates the DVB standards and should be used with caution to
avoid any compatibility issues.
117
4.18.6.4 S CRAMBLING ALGORITHM
4.18.6.4.1 O VERVIEW
You may define the scrambling algorithm at three different levels:
This chapter shows how to define scrambling algorithm at chassis and module level.
To learn how to bypass the chassis and module level scrambling algorithm at
ECMG level, see chapter “Scrambling algorithm”
• DVB-CSA/TS:
o DVB-CSA V2 compliant TS level scrambling algorithm
o 64-bit keys
• AES-CBC (Figure 13):
o AES with chained cipher blocks. Each block of plaintext is XORed with the previous
ciphertext block before being encrypted. Each ciphertext block depends on all plaintext
blocks processed up to that point. If the payload is not a multiple of 16, the last short block
(n-bits long) is encrypted by encrypting the ciphertext of the last full block and XORing the
leftmost n-bits of the resulting ciphertext with the plaintext short block.
o the safest block cipher mode in Luminato
o 128-bit keys
118
FIGURE 13: AES-CBC
119
FIGURE 14: AES-ECB1
120
FIGURE 15: AES-ECB2
Caution! The disadvantage of ECB is that identical plaintext blocks are encrypted into identical ciphertext blocks; thus,
it does not hide data patterns well.
• AES-CBC-CISSA
• AES-CBC-IDSA
Syntax:
121
4.18.6.4.3 M ODULE LEVEL DEFAULT
To set the scrambling mode at module level:
Syntax:
NOTE! If you use the embedded LYNKTM DRM server and it has been enabled and the required licenses successfully
activated, an ECMG will be automatically configured and enabled; you do not need to configure one separately.
Syntax:
Arguments:
122
Example – Create an ECMG entry labelled MyECMG:
Syntax:
ecmg <1…8192>
Example – ECMG 1:
DocumentationTest(cas)# ecmg 1
DocumentationTest(ecmg 1)#
Syntax:
ip address <IP_address>:<port>
Arguments:
Example:
NOTE! CAS redundancy can be used only when the unit is configured to Standalone role, i.e. CAS redundancy will not
be used together with 1+1 backup configuration. In a 1+1 backup context, the Spare IP address and Spare port have a
special function.
123
4.18.7.3.3 C HANGING THE PRIMARY ECMG PORT NUMBER
To change the port number of the primary ECMG:
Syntax:
port <port>
Arguments:
Syntax:
Arguments:
NOTE! ECMG redundancy can be used only when the unit is configured to Standalone role: ECMG redundancy will not
be used together in a 1+1 backup configuration. In a 1+1 backup context, the spare IP address and spare port have a
different meaning.
Syntax:
124
Arguments:
Syntax:
super-cas-id <identifier>
Example:
4.18.7.3.7 C HANNEL ID
A channel represents an open TCP/UDP connection between an ECMG and the SCS. A single open connection can have
only one channel. The channel ID identifies uniquely such a channel.
Syntax:
channel-id {1…65535}
Example:
125
4.18.7.3.8 C RYPTO PERIOD
The Crypto Period (CP) is the period when a specific Control Word is being used by a scrambler.
To define the crypto period duration of the target ECMG (in seconds):
Syntax:
cp {1…65535}
Example – CP duration 10 s:
DocumentationTest(ecmg 1)# cp 10
DocumentationTest(ecmg 1)#
Hint: The recommended value is 10 s. Long CPs will result in less information overhead, but will also allow more time
for hacking.
NOTE! The DVB standards1 define the nominal_CP_duration parameter as a 16 bit unsigned integer n x 100 ms, so the
standard compliant maximum CP length is 6553,5 seconds.
To use CP durations longer than the maximum standard compliant CP duration limit, see chapter
“Extended crypto period”
Syntax:
version <ver>
126
Argument:
Caution! Please bear in mind that the Extended CP violates the DVB standards and should be used with caution to
avoid any compatibility issues.
Syntax:
scramble-mode {dvb-csa-ts|aes-cbc|aes-ecb1|aes-ecb2}
Syntax:
[no] shutdown
Keywords:
127
4.18.7.3.12 ECM STREAM PRIVATE BYTES
CAS private data may be conveyed in the PMT’s CA descriptor private_data_byte1. It is up to the implemented CAS if such
private information is to be used.
To insert ECM stream related private data in the CA descriptor (in hexadecimals) of all ECM streams originating from the
target ECMG:
Syntax:
privatebytes <string>
Example – insert CA private data ‘0x1234’ for all ECM streams from ECMG 1:
Syntax:
Syntax:
Uptime: 460
Connection counter: 1
Status: OK
128
Channel test sent: 23
Test reply: 23
Error reply: 0
Last error time:
Last error code: 0
Channel ID: 2
Protocol version: 3
Section ts packet flag: true
AC delay start: 0
AC delay stop: 0
Delay start: 0
Delay stop: 0
Transition delay start: 0
Transition delay stop: 0
ECM repeat period: 250
Max streams: 0
Min CP duration: 50
Lead CW: 1
CW per message: 2
Max comp time: 2000
Default cryptoperiod: 1440
DocumentationTest(cas)#
Lead CW and CW per message are CW_provision’s parameters. Their value depends totally on the chosen CAS
implementation and is to be considered as fixed: in Luminato there is one lead CW and two CWs per message. In practice,
this means that each ECM issued to Luminato always contains the CWs of the current and next CP (Error! Reference
source not found.).
Max streams depends on the CAS implementation, for example Irdeto CAS doesn’t provide information about the
maximum amount of streams (Error! Reference source not found.).
Min CP duration is a parameter depending on the CAS implementation decisions made by CAS vendors. This information is
conveyed to the SCS by the ECMG during channel setups to indicate the minimum amount of time the CW shall remain
active. This information is displayed in milliseconds.
Section TS packet flag defines the format of the ECM. Luminato’s ECMs are always in MPEG2 Transport Stream packet
format. All TS packets should be of 188 bytes length, any other packet length is considered as an error.
Channel test sent, Test reply and Error reply are channel_test message counters.
129
Last error code gives the error_status code of the last detected error. Some of these codes are defined by the ECMG
protocol standard, while codes ranging from 0x8000 to 0xFFFF are privately defined (consult Error! Reference source not
found. of the present manual and/or your CAS administrator to obtain the definitions of the codes within this range).
• ECM ID
• Access criteria
• CW group
• PMT private data descriptor (optional)
Syntax:
ecmg {1…8192}
Example – ECMG 1:
DocumentationTest(cas)# ecmg 1
DocumentationTest(ecmg 1)#
Syntax:
Arguments:
130
4.18.9.3 ECM ID
The ECM ID is used to uniquely identify an ECM stream within a Super CAS ID (=CA system).
Syntax:
ecm-id <identifier>
Argument:
Example:
Syntax:
ac <access_criteria>
Argument:
Example:
131
4.18.9.5 C ONTROL WORD GROUP
The Control Word group (CW group) is an internal data structure that regroups into one logical set the ECM streams that
will be requested simultaneously with the same CW. In a SimulCrypt configuration, several CASs (with different Super CAS
ID) may be used simultaneously to generate several ECM streams with one same CW.
Caution! In non-SimulCrypt configurations (only one CA system), it is highly recommended to use a unique CW group
(control world group) for every ECM stream. Using the same CW for two or more ECM streams, could have unwanted
effects. For example, if the end customer swapped from one scrambled service to another, the service could be visible for
a few seconds, even without authorization to this specific service.
Syntax:
cwg-id {1…4294967295}
Example:
To insert ECM stream related private data in the CA descriptor (in hexadecimals) to the target ECM stream:
Syntax:
privatebytes <string>
132
To enable/disable an ECM stream:
Syntax:
[no] shutdown
Keywords:
Syntax:
Example:
DocumentationTest(stream 1)#
4.18.11 REMOVING AN ECM STREAM ENTRY
To remove an ECM stream profile:
Syntax:
no stream {1…8192}
Example:
133
4.18.12 EMM GATEWAY CONFIGURATION
Luminato acts as a gateway between the EMMG and the multiplexer.
Syntax:
emmgw <index>
Argument:
Example:
DocumentationTest(cas)# emmgw 2
Please wait. Creating new emm gw entry
DocumentationTest(emmgw 2)#
Syntax:
port <port>
Arguments:
Example:
134
4.18.12.1.2 C HANNEL ID
A channel represents an open TCP connection between an EMMG and an EMM gateway. A single open connection can
have only one channel. The channel ID identifies uniquely such a channel.
Syntax:
channel {1…8192}
Example:
When configuring EMMGs in the CAS, consider that ETSI TS 103 197 v 1.5.1 states the following rules for selecting a unique
client ID:
• “in the case of EMMs or other CA related data, the two first bytes of the client_id should be equal to the two
bytes of the corresponding CA_system_id;”
• “in other cases a value allocated by DVB for this purpose should be used.”
Syntax:
client-id <string>
Example:
no channel {1…8192}
Example:
135
4.18.12.2 A DDING EMM STREAMS
Once an EMM channel has been configured, the next step is to create one or several EMM streams. The EMM
(Entitlement Management Message) stream(s) carry the subscription contents (subscriber authorization levels etc.) and
the encryption key used for encrypting and decrypting the control words. The EMMGs are clients and Luminato’s EMM
gateway is the server. EMMG initiates connections and stream creation and the gateway either accepts or rejects the
setup messages based on the configured parameters. Before an EMM stream can be created, a few parameters must be
specified:
• Data ID
• Data type
• EMM bandwidth allocation
• CAT private data descriptor (optional)
Syntax:
Syntax:
Arguments:
136
4.18.12.2.2.1 DATA ID
The data ID is allocated by the CAS and uniquely identifies an EMM stream of a given client ID. In Luminato, it specifies
which EMM streams are accepted by the selected EMM gateway.
Syntax:
data-id {0…65535}
Example – data ID 1:
Syntax:
datatype {any|emm|other|private}
Keywords:
137
To insert EMM stream related private data in the CA descriptor (in hexadecimals) of all EMM streams from the target
EMM stream:
Syntax:
privatebytes <string>
Syntax:
bandwidth <bitrate>
Argument:
Example:
Syntax:
no emm <stream_index>
Arguments:
138
Example:
139
5 INTERFACE CONFIGURATION
This section covers the configuration procedures of all physical interfaces for stream routing. After the module
configuration presented in this chapter has been performed, the modules are ready for service configuration.
FIGURE 16: SWING OPEN THE FRONT PANEL BY GENTLY PUSHING THE HIGHLIGHTED PARTS OF THE FRONT PANEL SIMULTANEOUSLY.
The chassis product type, hardware version number and serial number can be found from behind the front panel (Figure
17).
The interface modules have their serial number and HW-version stickers applied to the lower side PCB of the modules.
Hardware type
Hardware version
Serial number
140
To identify hardware with the CLI:
Syntax:
show modules
Argument:
Quadruple input:
• LAS-A
• LAS-C
• LRS-A
• LRS-C
• LRS-B
• LRT-A
141
DVB-T/T2 receivers (DVB Terrestrial/Terrestrial – second generation):
• LRT-B
• LRT-C
Dual input:
• LRT-H
Quad input:
• LRT-I
• LRC-A
• LRC-B
Multistandard receivers:
• LRM-A
• LRM-B
IP-to-IP descrambler:
• LIC-A
142
5.1.2 LUMINATO OUTPUT MODULES:
DVB-ASI transmitter (DVB Asynchronous Serial Interface):
Quadruple output:
• LAS-B
• LAS-D
QAM modulators:
Quadruple output:
• LQM-A
• LQM-B
• LQM-C
Dense QAM:
• LDM-A
COFDM modulators:
Dual/Quadruple output:
• LCM-A
• LCM-B
• LCM-I
IP to IP multiplexer:
Quadruple output:
• LIM-A
IP-to-IP scrambler:
• LPI-A
• LPF-A
• LPE-A
143
Application module
• LPC-A
• LPC-B
Bulk descrambler
• LAB-A
<slot_index_number>/<connector_index_number>.<stream_index_number>
Example:
Syntax:
Argument:
144
Example – enter configuration mode for module 1:
Once you have entered connector level interface configuration mode, the CLI will stay in this mode until you explicitly exit
this mode with either the exit or the end command.
Syntax:
Arguments:
Once you have entered stream level interface configuration mode, the CLI will stay in this mode until you explicitly exit
this mode with either the exit or the end command.
Syntax:
145
Arguments:
Any apparatus displaying such SI text fields, including set-top boxes in end-user premises, must decode the text fields in
order to display the appropriate glyphs. By default in Luminato, the output SI text fields (service name, service provider
name etc) are copied from the input(s) unchanged, meaning the character encoding scheme will also remain the same.
Locally inserted SI text fields and created with the Luminato’s PSI/SI –editor, will use the user definable
Syntax:
Argument:
146
Name Description Allowed values
encoding_format Defines the encoding format of the character set {0|1|2}
identifier:
0 = The character set identifier is not included
1 = The character set identifier is encoded using 1 byte
2 = The character set identifier is encoded using 3
bytes
Caution! The encoding format ‘0’ violates DVB standard unless Latin Alphabet ISO-6937+ charset is used.
Overriding the input SI character set will force the selected encoding scheme for the input SI text fields that don’t include
a valid coding identifier. The factory default charset for character set override in Luminato is ISO-6937+1. The complete list
of supported coding schemes can be found in Error! Reference source not found..
Syntax:
Argument:
147
Example – force input SI text fields to UTF-8:
• chassis default
• module default
• interface
Syntax:
[no] shutdown
Keyword:
NOTE! When user enables/disables an input interface, it will turn on/off reception from the input. When user enables
an output interface, it starts to stream out. It will also enable processing for that interface. Output interfaces are disabled
by default.
148
Example – create IP output 1/1.1 and enable streaming:
Hint: Devote some time to naming interfaces! For example, when having hundreds of IP inputs, having logical and
consistent interface aliases is well worth the effort.
To label an interface:
Syntax:
description <alias>
GE1 and GE2 ports supports various types of electrical and fibre SFP modules.
NOTE! It is highly recommended to always use SFP modules that have been certified by our labs as compatible with
Luminato. supplies SFP modules with guaranteed full compatibility; their order codes begin with “LSFP”.
149
For more details on SFP modules, refer to Luminato Chassis Specification
document.
Caution! Choose the payload operating mode carefully, well before starting service routing: changing the operating
mode afterwards may prove itself very difficult. For example, when changing separate networks to common network, all
the streams residing in user configured VLANs attached to payload port GE2 will stop streaming.
Syntax:
Keywords:
Caution! With Common network selected, take care that both ports are not connected to same switch, as this could
result in an unpredictable loop. The connected networks must be totally separated.
Syntax:
150
5.3.2.2 SFP INTERFACE OPERATING MODE
The GE1 and GE2 interfaces have two user selectable operating modes for the inserted SFP-modules: fiber and electrical.
Syntax:
mode {fiber|electrical}
Keywords:
Caution! Other setting than 1000 Mb/s may very easily lead to over allocation with video streams’ bitrates. Make
sure that all video streams’ bitrates configured to 100Mb/s or 10Mb/s do not exceed capacity of the Ethernet link.
Syntax:
speed {10|100|1000}
Keywords:
NOTE! Ensure that the target interface has a LSFP-A plugged in and that the operating mode is set to electrical.
151
5.3.3 MODULE PAYLOAD IP ADDRESS
Each module slot has two IP addresses for payload traffic, one associated to GE1 and the other to GE2. They are either a
receiver’s source port IP address for UPD/IP streaming or a modulator’s or multiplexer’s destination address for unicast
UDP/IP stream reception. The configuration procedures described below apply to all modules.
NOTE! Each user defined VLAN have also its own set of module payload IP addresses.
To learn how to enter module level configuration mode, see chapter “Entering
module level configuration mode”
• 172.31.255.0/24
• 172.30.[1…23].0/24
• 172.30.[1…253].[1…23]/24
• The following ports are reserved for internal use:
• 22
• 23
• 69
• 80
• 81
• 111
• 443
• 1200
• 1201
• 1202
• 2049
• 8061
• 8071
• 54300-54331
5.3.3.2 IP ADDRESS
To modify a module’s payload IP address:
Syntax:
152
Arguments:
Hint: The factory default GEx IP addresses are based on the module slot index using the following formulas: Default
GE1 IP address = 192.168.2.(100 + slot index). For example, the factory default GE1 IP address for a module in slot 1:
192.168.2.(100 + 1) = 192.168.2.101. Default GE2 IP address = 192.168.3.(100 + slot index).
Syntax:
NOTE! Virtual source addressing is not the same virtual IP addressing: the device own IP address remains unaltered
and won’t reply at its virtual source address!
153
This feature is necessary for example when your network firewall settings allow traffic from only one IP address per port.
It is also used in conjunction with SSM1 (Source-Specific Multicast) routing to relieve the source discovery burden on the
network.
Syntax:
virtual-ip-address <ip_address>
Syntax:
no virtual-ip-address
Syntax:
NOTE! Omitting the optional keyword ge1|ge2 will assign the default gateway to the target module’s payload port
GE1. The IP address 0.0.0.0 results in a no gateway configuration.
Example – Assign the default gateway 100.255.0.1 to module’s 1 payload interface GE1:
1 SSM requires support in last-hop routers and in the receiver's operating system and uses IGMPv3.
154
5.3.3.6 D EFAULT TRANSMISSION PROTOCOL
To select the module default transmission protocol:
Syntax:
packet-format {udp|rtp}
Example:
We wish to stream from payload address 192.168.40.1, in VLAN100, to 10.136.99.101, you’ll need to specify a route to
subnet 10.136.0.0/16 accessible through, say gateway 192.136.40.254. Then, the CLI session would look like this:
Example – remove 10.136.0.0/16 from the payload routing table of VLAN interface 100:
Syntax:
155
Argument & keyword:
Separating traffic types into distinct broadcast domains has several advantages; here are two to name a few:
You can select which payload ports are assigned to each configured VLAN. If the selected payload port’s operating mode is
separate, then either port GE1 or GE2 can be assigned to the VLAN. In common mode, both ports can be assigned to the
VLAN.
The payload IP interfaces of the attached Luminato modules may be assigned as members of any VLAN group. You must
specify the IP address of the member payload interfaces.
Syntax:
156
Argument and keywords:
NOTE! Upon VLAN streaming interface creation, all inserted modules are automatically added as members of the
created VLAN and are automatically allocated a unique payload IP address.
Syntax:
157
Index Description Allowed
values
internal
The create VLAN will be associated to the internal payload interface and traffic will
not be forwarded to payload ports GE1 and GE2.
netmask
IPv4 netmask in classful dot-decimal notation. The factory default netmask is
255.255.255.0.
NOTE! The payload IP address 0.0.0.0 disables the interface. This is useful if only one module is used in the target
VLAN and you wish to release the IP addresses assigned to the unused module interfaces.
NOTE! If you have assigned a virtual source IP address to a module, it will bypass this VLAN payload address.
158
Example – Assign IP address 192.168.4.1 to module 1’s VLAN payload interface 100:
Argument
To learn how to add a static route for the specified VLAN, refer to chapter “Static
payload port routing”
To learn how to remove a static payload port route, refer to chapter “Removing a
route”
Syntax:
Example:
159
DocumentationTest#
Syntax:
Argument:
160
To enable/disable the strict CBR output mode:
Syntax:
Keyword:
When Luminato’s link-level flow control is enabled, the embedded switch will emit pause frames through the GE ports
whenever the buffers are running out of memory. The transmitters at the other end of the link will then pause
transmitting for a short period of time.
NOTE! Link-level flow control must be also enabled on the end receiving end of the pause frames. Please consult the
user documentation of the transmitter to learn how to enable link-layer flow control receiving.
Syntax:
Keyword:
NOTE! This setting affects directly the triggering of 1 + 1 chassis redundancy. You MUST disable this option when
using stream redundancy and 1 + 1 chassis redundancy simultaneously.
161
To learn more about 1+ 1 chassis redundancy, see chapter
Syntax:
[no] critical
DocumentationTest(iface-ip-input-1/1.1)# no critical
DocumentationTest(iface-ip-input-1/1.1)#
Example – clear the statistical PID counters for DVBT-2 interface 2/1.1:
Syntax (IP input interface level configuration mode, RTP mode only):
Example – clear RTP peak jitter counter for IP input interface 4/1.1:
Syntax:
162
Arguments & keywords:
NOTE! The command below is a module level configuration command and affects all the input interfaces of the target
module.
To add/remove a SDT descriptor tag into/from the SDT descriptor forwarding list:
Argument:
NOTE! You may enter only one tag at a time. To specify several tags, you must enter each tag separately.
Example – forward the input SDT descriptors tagged as 0x86 and 0x87 in module 2:
163
5.4.1.6 S HARED TS RECEPTION
Sometimes, the incoming multiplex might be shared by two networks simultaneously. In some special applications, the
shared TS does not include any SDT nor NIT (Figure 19). The SDT information must be extracted from the SDTother of the so
called home TS, which also contains EIT schedule data.
In the illustration below (Figure 19), the received SDT and NIT data for TS5 in network 1 (=ONID 1) has to be extracted
from TS2, which is the home TS for ONID1. Similarly, in ONID2 the SDT and NIT data has to be extracted from TS4.
To support this particular application, Luminato offers the possibility to use the SDTother of another input TS (=physical
input) instead of the expected SDTactual.
NOTE! The Use SDT other –feature is for physical inputs residing in the same module, i.e. you cannot use the SDT
other of inputs residing in another module.
FIGURE 19: TS SHARING. IN THIS ILLUSTRATION, THE NETWORKS 1 AND 2 SHARE THE TS5. TS5 DOES NOT INCLUDE ANY NIT NOR SDT.
Syntax:
Arguments:
Example – for IP input 2/1.1, use the SDTother of input 2/1.2 instead of SDTactual:
164
DocumentationTest(iface-ip-input-2/1.1)#
Syntax:
Argument:
Example – IP input interface 2/1.1 shall use ISO-10646 as its character set for SI text fields without valid SI text field
encoding identifier when displayed in Luminato’s UI:
165
An input signal is considered missing when its PID bitrates are below the signal lost threshold for a period specified by the
warning timeout value.
An input service is considered missing when all its components’ PID bitrates are zero for a period specified by the warning
timeout value.
Argument:
Example:
We want to be notified about missing input services if all the ES PID bitrates of any service has been zero for 10 seconds in
module interface 2:
NOTE! In the example above, a signal lost –warning message will issued if all the PID bitrates have been below the
signal lost threshold for 10 seconds.
Syntax:
166
Argument:
Syntax:
Syntax:
NOTE! PID missing warning messages are only issued with manually filtered PIDs.
To set the PID missing warning timeout (module level interface configuration mode):
Syntax:
NOTE! TDT/TOT tables are typically updated every 30 seconds; therefore this setting must be more than TDT/TOT
interval to avoid unnecessary warnings.
167
Example:
We want to be notified about missing input PIDs in module interface 2 if the input PID bitrate has been zero for 40
seconds:
If you intend to descramble multiple services per CAM, you must acquire a Multi-Service Descrambling (MSD) license. If
the MSD feature is enabled, the amount of descrambled services and PIDs, as well as the maximum TS bitrate through the
CAM are limited by the CAM, not by Luminato. You may overcome these limitations by daisy chaining the CAMs.
Luminato receivers are continuously tested with professional CAMs from e.g. Aston, SMiT, DRECrypt, RosCrypt, SmarDTV
and Neotion, CA systems including (but not limited to) Conax, Viaccess, NDS Videoguard, Irdeto, AstonCrypt, DreCrypt,
Biss, Irdeto Cryptoworks. It is recommended to use these manufacturers’ modules to avoid problems with descrambling.
We actively follow these vendors’ latest developments with CA-modules.
Our coverage of supported CAMs is continuously growing. For the compatibility of a specific CAM from a manufacturer not
listed here, please contact Sales services, Product Management or Support.
NOTE! Luminato does not support descrambling of services that requires use of a CI+ module, as the CI+ technology is
intended for end customers. The main purpose of CI+ standard is to prevent illegal distribution and copying of content,
and the CI+ consortium does not currently certify professional receivers.
Luminato may descramble some services (typically SD1) with consumer CI+ modules, but it is not guaranteed. However,
Luminato supports Secure Pro CAMs that descramble the same services that are descrambled using CI+ modules in
consumer applications. For obtaining these Secure Pro CAMs, contact the content provider responsible for the encryption.
The upper CA-slot in a receiver module (LRS-A/C, LRT-A, LRT-B, LRC-A, LIC-A) is labelled as A, and the lower CA-slot as B
(Figure 20).
1 SD = Standard Definition
168
A
B
Syntax:
show cam
Example:
Syntax:
Example (abridged):
169
Timeout | 15 sec| 15 sec
ROUTING
Input|CAM A|CAM B
1/1.1| A |
1/2.1| | B
! CAM A
Module |Conax Aston Pro 2.1901
System ID |2816,2817,2818,2819,2820,2821,2822,2823
Manufacturer |2816
Manufacturer code |2816
Module identifier |Conax Aston Pro 2.1901,b00,b00,b00,b01,b02,b03,b04,b05,b06,b07
PIDs requested for descrambling|0
PIDs successfully descrambled |0
Failure actions since reboot |0
CA menu status |Closed
! CAM B
Module |Videoguard CA
System ID |2366
Manufacturer |51966
Manufacturer code |47806
Module identifier |Videoguard CA,cafe,babe,93e
PIDs requested for descrambling|0
PIDs successfully descrambled |0
Failure actions since reboot |0
CA menu status |Closed
!
5.4.1.9.2.3 CA-MODULE STATUS
To access the CAM basic information of an input module:
Syntax:
Example:
170
5.4.1.9.3 CAM ROUTING
The input TS which contains the services you wish to descramble must be routed through a CAM. A typical use case would
be to assign one CA-module per input TS, but in order to extend descrambling capacity both CA-module slots may be
assigned to a single input TS. At the same time, the second input can be used for receiving FTA (Free To Air = unscrambled)
services. Another reason for cascading two modules could be the use of CA-modules capable of descrambling different CA
systems in the received multiplex.
Argument:
Syntax:
The CI clock for RF inputs is automatically derived from the input signal bitrate. For IP inputs in LIC-A and receiver modules
with dual IP input capability (LRT-B/C/H/I, LRC-A/B), the default CI clock is at the DVB CI standard1 maximum of 9 MHz
1 ETSI EN 50221
171
which will result in a maximal bit rate of 72 Mb/s. You may set the CI clock manually if the CAM in use supports higher bit
rates or if the CAM is not DVB compliant and does not function at the default clock. However, the default CI clock value
should work with most CAMs without problems.
Syntax:
ci-clock
{7.0MHz|9.0MHz|9.4MHz|9.8MHz|10.3MHz|10.8MHz|11.4MHz|12.0MHz12.7MHz|13.5MHz|14.4MHz|15.4MHz|16.6MHz|
18.0MHz|19.6MHz|21.6MHz|24.0MHz}
Example – the CAM routed to IP interface 2/1.1 is capable of a maximum transfer bitrate of 96 Mb/s:
1. Restart descrambling
2. Reset CAM
3. Reset module
Each step of action is tried a set number of times before moving to the next step until success is met. You may set the
amount of retries for actions 1 and 2.
Syntax:
172
Keywords & argument:
cam- Reboots the CAM. Select the amount of retries, the default and recommended value is 1.
reset
off Disables the target failure action.
retries The amount of retries. {1…3}
5.4.1.9.5.2 ENABLING OR DISABLING THE REBOOT MODULE FAILURE ACTION
To enable or disable the reset module descrambling failure action:
Syntax:
Keyword:
Caution! This descrambling failure action is disabled by default as it will interrupt all service streaming of that
module. Use with caution!
Syntax:
Example – We want a delay of 60 seconds before each failure action in CAM A of module 2:
Syntax:
173
Example – reset the CAM present in CA -slot A of module 1:
• If multiple services are descrambled, and one or more of them are time-shared: set 2 for Restart
descrambling, Disabled for Reset CAM and Reset Module.
• If it has been proved that Restart descrambling has not helped recovering descrambling in case of a
specific time-shared service, Restart descrambling can be set as Disabled to speed up failure
recovery.
• If the descrambled services require different failure actions, it is recommended to divide the
services to different CAMs according to failure action.
• This way, those services that are not time-shared or recover well with CA_PMT update, do not
suffer from unnecessary CAM resets.
• Reset module should be enabled only in some very rare cases when Restart descrambling and Reset
CAM have been proven not to recover descrambling. This will reboot the whole receiver module,
not only the CAM, causing a break in all received services in the module.
174
5.4.2.1 DVB-ASI INPUT INTERFACE CONFIGURATION
There are no demodulation parameters to configure for ASI input interfaces. The configuration commands available are
those common to all input interfaces, for example:
• enabling/disabling interfaces
• labelling interfaces
• emphasizing missing input signals in status reports
Syntax:
Example – enter connector level configuration mode for ASI input 1/1:
175
5.4.3 SATELLITE RECEIVERS
FIGURE 22: LRS-C DUAL DVB-S/S2 RECEIVER WITH TWO CA-MODULE SLOTS
176
FIGURE 23: LRS-D QUADRUPLE DVB-S/S2 RECEIVER
Syntax:
177
Example – enter interface level configuration mode for DVB-S2 input 1/1:
Syntax:
Argument:
This shift in carrier frequency is called frequency offset in Luminato; i.e. the difference between the nominal frequency
and the actual received frequency. If the frequency offset becomes too large, carrier locking in the receiver’s automatic
frequency control might become unreliable. You set a warning limit for the frequency offset. Once the warning threshold
limit has been passed a warning message will be issued. By default, no warning message is issued.
Syntax:
1 Consult a satellite directory for the correct settings, for example: http://www.lyngsat.com/, http://www.satcodx.com/ or
http://en.kingofsat.net/.
178
Argument:
Syntax:
Argument:
Example – set the LO frequency for the DVB-S input interface 1/1 to 9750 MHz
1 Consult a satellite directory for the correct settings, for example: http://www.lyngsat.com/, http://www.satcodx.com/ or
http://en.kingofsat.net/.
179
To specify the symbol rate of the input satellite signal:
Syntax:
symbolrate {auto|<symbol_rate>}
Example – set the input symbol rate to 24500 ksym/s for DVB-S2 input interface 1/1:
5.4.3.1.6 D EMODULATION
The input signal’s modulation is automatically detected by default. The auto mode is recommended, but if the reception
conditions vary, it might be better to choose the fixed value to avoid automatic discovery. Choose a fixed value from
dropdown menu:
Syntax:
modulation {auto|QPSK|QPSK-high|8-PSK|8-PSK-high|16-APSK|32-APSK}
Keywords:
QPSK- Use this demodulation mode for QPSK signals with symbol rates above 47000 ksym/s.
high This mode is available in input interfaces x/1 and x/3.
8-PSK- Use this demodulation mode for 8-QPSK signals with symbol rates above 31500 ksym/s
high
NOTE! In APSK and high bitrate PSK modulation modes, the next input, x:2.1 or x:4.1, will be disabled.
180
5.4.3.1.7 DVB-S2 MULTIPLE INPUT STREAM RECEPTION
The DVB-S2 standard1 allows the transmission multiple input streams (MIS) using a single transponder. The carried TSs are
identified by their respective Input Stream Identifier (ISI) located in the base-band header.
When then received DVB-S2 signal contains multiple TSs, you must select the target input TS by providing the target ISI.
Syntax:
multistream-id {1…255}
NOTE! In order to be able to select the target ISI, the DVB-S2 frontend tuner must be configured to the correct
frequency and the PLL must be in locked status. DVB-S and DVB-S2 Single Input Stream (SIS) signals do not carry any
stream identifier information and the ISI will be zero.
Syntax:
no multistream-id
5.4.3.1.8.1.1 E NABLING
To specify the supply voltage fed to the target LNB:
Syntax:
181
5.4.3.1.8.1.2 D ISABLING
To disable the LNB feed :
Syntax:
no lnb voltage
Syntax:
Syntax:
Example – set high current –alarm limit to 400 mA for interface 1/1:
Syntax:
Example:
182
5.4.3.1.8.4 22 KHZ TONE
The DVB-S(2) input interfaces may configured to send a 22KHz tone through the connected coaxial cable. The usage 22
kHz tone depends on the used equipment for satellite reception (LNB, switches etc.). Originally the 22 kHz tone was used
for switching between satellite dishes, but nowadays it is usually used for band selection in the LNB.
NOTE! The 22 kHz tone is sent only if the LNB feed has been enabled.
Syntax:
Keyword:
Hint: The usage of the 22 Khz depends on the installed third party equipment, please refer to their user manuals.
Typically:
enabled = high band (11550 … 12750 MHz, LNB LO frequency is 10600 MHz)
5.4.3.1.9 D I SE Q C 1
DiSEqCTM is a communication protocol for use between satellite receivers and devices such as multi-dish switches.
Luminato DVB-S2 receiver modules support DiSEqCTM 1.0 and 1.2 (Module types: LRS-A/B/C/D).
You may issue DiSEqCTM commands through the CLI and create a failure-action DiSEqCTM macro. The command word
consists of three parts: framing, address and command. Also some commands require ancillary data byte.
183
5.4.3.1.9.1 ISSUING SINGULAR COMMANDS
To issue a DiSEqCTM command:
Syntax:
NOTE! DiSEqC accessories have different command instruction sets. Please consult your accessory manual for
supported commands.
Keywords:
LNB LNB
SMATV SMATV
184
cmd_name Description Allowed values
SetPosA Select satellite position A (or position C)
Example – reset any DiSEqCTM compatible device connected to the interface 1/1:
185
5.4.3.1.9.2 FAILURE-ACTION DISEQCTM MACRO
You may define a sequence of DiSEqCTM commands that will be automatically executed upon module startup and signal
loss (=signal missing flag is raised). When the signal goes missing a five second delay is inserted before executing this
macro. A meta-command labelled Delay allows you to insert a delay ranging from 10 to 2550 ms before or after any
command in the macro; this is useful for allowing enough time for time-consuming commands to complete before issuing
the next command.
Syntax:
NOTE! DiSEqC accessories have different command instruction sets. Please consult your accessory manual for
supported commands.
Keyword:
Example:
We want to make a failure-action DiSEqCTM macro that first resets any DiSEqCTM compatible device connected to the
interface 1/1, then, after a 100ms delay, power on any DiSEqCTM compatible device connected to the interface 1/1:
186
5.4.3.1.9.2.2 E XECUTING THE MACRO
You may execute at any time the failure-action DiSEqCTM macro manually. To execute the macro:
Syntax:
Example:
no diseqc
Syntax:
Keyword:
DocumentationTest(iface-dvbs2-input-1/1)#
187
5.4.3.1.9.3 RECOMMENDED DISEQC ACCESSORIES
DiSEqC multiswitches from following manufacturers have been tested with Luminato and found functional:
• Triax
• Maximum
• Digiality
• EMP-Centauri
• Televes
• Sunny
• Vizyon
• Edision
DiSEqC switches from the following manufacturers have been found incompatible:
Syntax:
Syntax:
no spectral inversion
Example – disable automatic input signal inversion for input interface 1/1:
188
5.4.4 TERRESTRIAL RECEIVERS
FIGURE 24: LRT-A DUAL DVB-T, LRT-B DUAL DVB-T/T2, LRT-C QUAD DVB-T/T2 MODULES WITH TWO CA-MODULE SLOTS
Syntax:
189
5.4.4.1.1.2 TUNING FREQUENCY
In most situations, frequency and channel bandwidth are the only mandatory information to provide for successful
broadcast DVB-T reception.
Syntax:
rf frequency <ch_frequency>
Argument:
Example – set DVB-T input interface 2/1 tuning frequency to 714 MHz:
Syntax:
modulation {auto|QPSK|16-QAM|64-QAM}
Example – poor weather disturbs automatic input modulation detection, set demodulation to 64QAM in input 2/1:
For the correct parameter settings, refer to terrestrial broadcaster web sites.
Syntax:
bandwidth {6MHz|7MHz|8MHz}
190
Example – set channel bandwidth of input interface 2/1 to 8 MHz:
The input signal’s transmission mode is automatically detected by default. If the receiver has trouble locking to the input
signal, you may try selecting the transmission mode manually.
Syntax:
Example - poor weather disturbs automatic input transmission mode detection, set transmission mode to 2k in input
2/1:
The input signal’s guard interval is automatically detected by default. If the receiver has trouble locking to the input signal,
you may try selecting the guard interval manually.
Syntax:
guard-interval {auto|1/16|1/32|1/4|1/8}
Example - poor weather disturbs automatic input guard interval detection, set guard interval to 1/8 in input 2/1
191
In Luminato, hierarchical signal reception is either enabled or disabled. The high priority stream is always selected.
Syntax:
[no] hierarchy
webtest-3(iface-dvbt-input-2/1)# no hierarchy
webtest-3(iface-dvbt-input-2/1)#
5.4.4.1.1.8 INNER CODING RATE
In DVB-T, FEC functionality is implemented through the use punctured convolutional coding. In hierarchical transmission,
two different code rates may be used for the high and low priority streams.
The input signal’s inner code rate is automatically detected by default for the high and low priority streams. If the receiver
has trouble locking to the input signal, you may try selecting the inner code rate manually.
To select the inner coding rate for high and low priority streams:
Syntax:
Keywords:
Example – set input interface 2/1 inner code rate to 1/2 for low priority streams:
Syntax:
192
Example – enter stream level interface configuration mode:
Syntax:
standard {dvbt|dvbt2}
Syntax:
Keyword:
Syntax:
Syntax:
193
5.4.4.1.2.4 TUNING FREQUENCY
In most situations, frequency and bandwidth are the only mandatory information to provide. If the receiver has trouble
locking into the input signal, you may try to select manually the other front end reception parameters.
Syntax:
rf frequency <ch_frequency>
Argument:
Example – set DVB-T2 input interface 2/1.1 tuning frequency to 205.5 MHz:
Syntax:
bandwidth {6MHz|7MHz|8MHz}
NOTE! This parameter can be set only when the input interface is in DVB-T operating mode.
DVB-T employs OFDM (Orthogonal Frequency-Division Multiplexing). It is a digital multicarrier modulation scheme, where
data is carried by a large amount of closely spaced carriers. In accordance with the DVB-T standard1, there are two modes
available: 2k and 8k. The 2k mode has 1 705 and the 8k mode 6 817 carriers per OFDM symbol. The respective
approximate carrier spacings are 1 116 Hz and 4 464 Hz.
194
The input signal’s transmission mode is automatically detected by default. If the receiver has trouble locking to the input
signal, you may try selecting the transmission mode manually.
Syntax:
Example - poor weather disturbs automatic input transmission mode detection, set transmission mode to 2k in DVB-T
input 2/1.1:
NOTE! This parameter can be set only when the input interface is in DVB-T operating mode.
Guard intervals were introduced to the DVB-T standard EN 300 744 to counter intersymbol interference (ISI). Such
interferences may be due to propagation delays, echoes and/or reflections.
The input signal’s guard interval is automatically detected by default. If the receiver has trouble locking to the input signal,
you may try selecting the guard interval manually.
Syntax:
guard-interval {auto|1/16|1/32|1/4|1/8}
Example - poor weather disturbs automatic input guard interval detection, set guard interval to 1/8 in input 2/1.1:
NOTE! This parameter can be set only when the input interface is in DVB-T operating mode.
DVB-T transmission may be hierarchical or non-hierarchical. In hierarchical transmission, two MPEG TS may be
transported with different levels of channel coding and modulation. The hierarchical streams are referred to high priority
and low priority streams.
Syntax:
hierarchy {hp|none/lp}
195
Example – select the low priority stream in hierarchical transmission, in DVB-T input interface 2/1.1:
The received DVB-T2 multiplex may be single PLP or multiple PLP. If the target DVB-T2 broadcast employs M-PLP (Multiple
Physical Pipe) technology, you have to choose the Data PLP ID manually from the drop-down menu to demodulate the
desired TS. If none is chosen the default data PLP ID will be the smallest ID number within the broadcast. Consult
terrestrial broadcast web sites for the correct ID.
Syntax:
plp-id {unset|0…255}
NOTE! The ‘unset’ keyword allows automatic data PLP ID selection with single-PLP DVB-T2 signals. Do not use this
keyword with M-PLP signals!
Syntax:
196
5.4.4.2.2 DC FEED
Syntax:
rf frequency <ch_frequency>
Argument:
Example – set ISDB-T input interface 6/1.1 tuning frequency to 205.5 MHz:
197
5.4.5 CABLE RECEIVERS
FIGURE 25: LRC-A DUAL AND LRC-B QUAD DVB-C RECEIVERS WITH TWO CA-MODULE SLOTS
Syntax:
198
Argument
Syntax:
rf frequency <ch_frequency>
Argument:
Example – set DVB-C input interface 1/1.1 tuning frequency to 242 MHz:
Refer to terrestrial broadcast web sites for the correct channel frequency.
• DVB-T/T2
• DVB-S/S2/S2X
• DVB-C
• ITU-T J.83 Annex B
• ISDB-Tb
199
The LRM-B is a dual input multistandard receiver with dual CI slots. It supports the following standards:
• DVB-S/S2/S2X
• DVB-T/T2 (requires separate license)
• DVB-C (requires separate license)
• ITU-T J.83 Annex B (requires separate license)
• ISDB-Tb (requires separate license)
Syntax:
Syntax:
200
5.4.6.2.1 DVB-T2
When the input standard dvb-t2 has been selected, the DVB-T/T2 signals are supported and automatically detected and
no further standard selection is necessary.
Once the input interface level configuration mode has been entered, the available commands are for most parts identical
to those of dedicated DVB-T/T2 modules such as the LRT-B and LRT-C. LRM has however a few additional commands
related to input signal level(s).
The commands are described in chapter “DVB-T/T2 receivers: LRT-B and LRT-C”
Syntax:
low-signal-level-alarm <threshold_level>
Argument:
When the signal –trigger is selected, the IP output is shut down when the input signal is considered as missing.
When the quality –trigger is selected, the IP output is shut down when its mapped input signal level goes below the ‘low
signal level’ -warning threshold by an user definable amount. The factory default triggering limit for output muting is when
the input signal level is 10 dB below the Low signal level -threshold level.
To learn how to adjust the Low signal level warning –threshold, refer to chapter
“5.4.5.3.1.1 Low signal level warning”
201
NOTE! The limit for output muting is only configurable through the CLI.
To prevent the affected interfaces from flapping from one state to another, a user-adjustable hysteresis is added to the
low-signal-level-alarm -threshold level before the muted IP output may be re-enabled.
5.4.6.2.1.2.2 C ONFIGURATION
The muting threshold and hysteresis for the low signal level trigger are module level settings.
Syntax:
Syntax:
low-signal-level-muting-threshold <limit>
Argument:
Example:
Syntax:
low-signal-level-alarm-hysteresis <hysteresis>
Argument:
202
Example:
The IP output 2/1.1 has been muted due to low input signal level. The low-signal-level-alarm has been set to 50
dBµV and the low-signal-level-alarm-hysteresis to 10 dB. The IP output 2/1.1 will re-enabled (unmuted) only
when the input signal level will reach 60 dBµV.
The muting triggers are enabled and disabled in IP output stream configuration mode.
Syntax:
Syntax:
Keywords:
quality The IP output is automatically shut down when its mapped input signal level goes below the -
‘low signal level’ -warning threshold by an amount defined by the low-signal-level-
muting-threshold value.
signal The IP output is automatically shut down when the input signal is considered as missing. -
5.4.6.2.2 DVB-S2X
When the input standard dvb-s2x has been selected, the DVB-S/S2/S2x standards are supported and automatically
detected.
5.4.6.2.2.2 CONFIGURATION
Once the input interface level configuration mode has been entered, the available commands are in most part identical to
those of dedicated DVB-S/S2 modules such as the LRS-C. There are three differences:
• The command for changing the channel centre frequency is different (see chapter “” below)
• Spectral inversion is not available
• The carrier frequency shift warning limit is not configurable
203
• You may specify the physical layer scrambling Gold sequence index or the PL scrambling initialization value
Syntax:
rf frequency <ch_frequency>
Argument:
In order for LRM to be able to lock onto the signal, the Gold sequence index n (or the PL scrambling initialisation value)
value must be known. The DVB standard default Gold codes are known and automatically detected by the LRM, but any
other arbitrary Gold sequence index values must be fed to the module.
To specify the Gold sequence index or the PL scrambling initialisation value (in receiver input configuration mode):
Syntax:
pls {none|gold|root}
Keywords:
5.4.6.2.3 DVB-C
Once the input standard dvb-c has been selected and the input interface level configuration mode has been entered, the
available commands are in most part identical to those of dedicated DVB-C modules such as the LRC-B. There is however
one difference: in DVB-C dedicated modules such as the LRC-B, the symbol rate was automatically detected; in the LRM-A,
the symbol rate must be specified (see the chapter “Symbol rate” below).
To learn how to specify the channel centre frequency, see chapter “Tuning
frequency”
204
5.4.6.2.3.1 SYMBOL RATE
The symbol rate is the amount of symbols being transmitted per second. The amount of bits being conveyed depends on
the used modulation.
Hint: The symbol rate is not specified by the DVB-C standard, but the roll-off factor of the square-root raised cosine
filters is fixed to 15 % from which can be derived the maximum symbol rate. Typically it is 6,9 MBaud for 8 MHz channel
raster applications.
Syntax:
symbolrate {0…999999999999}
To learn how to specify the channel centre frequency, see chapter “Tuning
frequency”
NOTE! The ITU-T Recommendation J83 Annex B specifies two symbol rate modes: 5.057 Msymbols/s 64-QAM (Mode
1) and 5.361 Msymbols/s 256-QAM (Mode 2).
Syntax:
symbolrate {0…999999999999}
5.4.6.2.5 ISDB-T B
Once the input standard isdb-t has been selected and the input interface level configuration mode has been entered,
the available commands are in most part identical to those of dedicated ISDB-Tb modules such as the LRT-H and LRT-I.
There is however one difference: in ISDB-T dedicated modules such as the LRT-H and the LRT-I, the channel bandwidth is
fixed to 6 MHz; in the LRM-A, the channel bandwidth must be manually specified (see the chapter “” below).
To learn how to specify the channel centre frequency, see chapter “Tuning
frequency”
205
5.4.6.2.5.1 CHANNEL BANDWIDTH
You must manually specify the input channel bandwidth.
Syntax:
bandwidth {6MHz|7MHz|8MHz}
Up to 120 IP inputs may be created in output modules1 and up to two in input modules (LRT-B/C/H/I, LRC-A/B, LRM-A, LIC-
A).
To receive an IP transport stream, you must create an IP input interface either for a GE payload port (=external streaming)
or for an internal VLAN (=internal streaming).
NOTE! You may create IP input interfaces only, if your chassis includes an output module or one of the following: LRT-
B/C/H/I, LRC-A/B an LIC-A
• Multicast:
o copies of a single IP packet are delivered to multiple recipients
o Class D IP Address range:
o 224.0.0.0 – 239.255.255.255
o Typically used to broadcast TV content to several users simultaneously such as with live TV broadcasts
o Reduces the server and network load
• Unicast:
o IP packets are delivered to a single recipient
o Typically used to deliver personalized content over an IP network such as a specific movie to a given user
(IPTV VOD)
o Consumes a lot of bandwidth since the same content must be streamed for each users separately
1Actually, the maximum amount of inputs is 128, but in the web UI 8 stream index are reserved for automatic internal routing. In the
CLI, such restriction does not apply.
206
5.4.7.2 C REATING AN IP INPUT INTERFACE AND ENTERING CONFIGURATION MODE
Syntax:
Arguments:
Syntax:
Arguments:
udp {<ip_address>|unicast}:<port>
unicast Unicast stream reception. IP address is the target module’s IP payload address.
207
Name Description Allowed
values
UDP_port Specifies the UDP source port for the transmitted streams by this module. {0…65535}
To learn how to change the IP payload address of an input interface, see chapter Module payload IP address
• External:
o GE1&GE2 ports
o User created VLANs assigned to the above mentioned GE1&GE2
• Internal:
o Internal payload interface labelled internal in the UI (technically it is a hardcoded VLAN
defined as internal, meaning its traffic is not forwarded by the GE1&GE2 ports)
o User created VLANs defined as internal (meaning their traffic is not forwarded by the
GE1&GE2 ports)
Syntax:
Keyword:
Syntax:
src-ip <ip_address>
Syntax:
no src-ip
208
5.4.7.4 R EMOVING AN IP INPUT INTERFACE
Syntax:
Syntax:
5.4.8.1 C ONFIGURATION
Take the following configuration steps:
2. Create IP inputs interfaces (up to two inputs may be created). If the input needs to be descrambled
before being multiplexed as QAM or COFDM, select Internal as the payload interface.
3. OPTIONAL: Assess the maximal bitrate of the IP input streams and set the CI clock accordingly (the
default value is 9 MHz resulting in a max bitrate of 72 Mb/s). This step is necessary only if the CAM
supports higher CI clock rates than 9 MHz and you intend to use the full byte transfer rate capacity
of the target CAM.
To learn how to set the CI clock, see chapter “CI clock setting for IP inputs”
5. Route the input services or the whole TS(s) to the target output interface
209
To learn how to route input services or TSs to output interfaces, see chapter
Service configuration
To learn more about the passthrough service timeout parameter and how to
configure it at chassis level, see chapter “Passthrough service timeout”
Syntax:
Syntax:
210
5.5.3 DVB-ASI OUTPUTS
The LAS-B/D ASI output modules have four multiplexers. You must define the multiplexers’ bandwidths. Each of the four
multiplexers has its own settings.
Up to two exact copies of any output multiplex can also be transmitted as IP streams; this is sometimes referred to as IP
mirroring. This is useful for copying a multiplex to another multiplexer in another location or just simply for monitoring
purposes.
Caution! With LAS-D, disabling an ASI-output mutes also any configured multiplex IP streaming (IP mirroring) of that
particular output.
Syntax:
211
5.5.3.1.2 M ULTIPLEX BANDWIDTH
To define the ASI output bandwidth expressed in bit/s:
Syntax:
bitrate <bit_rate>
Byte mode:
In this mode, the MPEG transport packets are transmitted as data bursts with each individual bytes separated by sync
bytes called K28.5 comma characters; extra stuffing is not used between packets.
Example: when an encoder is set at a total data rate of 27.9 Mb/s, the bytes are sent
every 289 ns with either 6 or 7 commas between each data byte. The total payload rate
is changed by sending a different number of sync bytes between each data byte.
TS packet mode:
In this mode, the MPEG transport packets are transmitted as blocks of contiguous data at a constant rate of 270 MHz
without sync bytes between individual payload data bytes. 188 byte packets last around 7 ms independent of the total
data rate. K28.5 commas are added between packets until the rate of 270 MHz can be maintained.
Example: when the total data rate is set at 28 Mb/s, packets are sent with 47 ms worth
of commas. Whereas 80 Mb/s and 155 Mb/s rates require 12 ms and 3 ms respectively
and anything over 200 Mb/s requires very few commas.
This mode is commonly used when payload rates reach above the 80 Mb/s level. At this data rate, the Byte mode does not
reduce the need for buffering capacity.
Syntax:
[no] packet-mode
1 EN 50083-9
212
5.5.4 QAM MODULATOR OUTPUTS
• The LQM modules have four QAM modulators and are ITU-T J.83 Annex A, B and C compliants
• The LDM modules have a flexible amount of QAM modulators; the available number modulators
depends on the purchased license. LDM modules are ITU-T J.83 Annex A and C as well as DOCSIS
CM-SP-DRFI-I13-130808 compliant
In LQMs the four modulators are in adjacent channels and share the same upconverter. When the Base frequency of the
first modulator is set, the frequencies of the other modulators follow the first one in incremental steps defined by the
Channel bandwidth. Each modulator may be enabled or disabled individually.
In LDMs, each QAM channel can be placed independently in the whole supported frequency range (refer to product
specification). The QAM modulators are are organized in groups of four, each group is assigned a modulation order and
symbol rate.
Up to two exact copies of any output multiplex can also be transmitted as IP streams; this is sometimes referred to as IP
mirroring. This is useful for copying a multiplex to another multiplexer in another location or just simply for monitoring
purposes.
213
5.5.4.1 QAM OUTPUT INTERFACE CONFIGURATION
The configuration of QAM modulators takes place at two levels: connector level and at multiplexer level.
Syntax:
Syntax:
qam-standard {dvbc|j83annexb}
Both DVB-C and J.83 Annex B standards use convolutional interleaving to protect the data against burst noise in the
communication channel by spreading burst errors in time. A burst noise in the channel can cause the corruption of several
consecutive bytes/symbols, but since the bytes/symbols are spread over time before transmission, deinterleaving at
reception will spread the errors over many Reed-Solomon (R-S) blocks thus moving the errors-per-R-S-blocks ratio within
range of the error correcting capability of the R-S decoder.
Technically the convolutional interleaver employs a commutator which position increments at the R-S symbol frequency,
connecting the R-S encoder output sequentially to a I paths which are shift registers. Each consecutive path has J symbols
more storage, hence the name ‘depth’. Each consecutive path adds J symbol period more delay, so that the last path, Ith
path, has (I-1) * J symbol periods of delay.
When the DVB-C format is in use, you cannot alter the interleaving settings since they are fixed to I=12 and J=17 by the
DVB-C standard EN 300 429. However, with J.83 Annex B selected, you must define the interleaver depth.
214
To configure the J.83 Annex B interleaver:
Syntax:
j83-interleaver {8/16|16/8|32/4|64/2|128/1|128/2|128/3}
NOTE! For optimal compatibility, use 128/1 (Level 1 interleaver) This setting affects all the modulators of the target
QAM-module and cannot be bypassed at modulator level.
Paths Interleaving depth Max. error burst length (µs) Interleaver latency (ms)
(I) (J) 64-QAM 256-QAM 64-QAM 256-QAM
128 1 94,92 65,98 4,018 2,793
64 2 47,46 32,99 1,993 1,386
32 4 23,73 16,49 0,981 0,682
16 8 11,86 8,25 0,475 0,330
8 16 5,93 4,12 0,221 0,154
128 2 189,8 132,0 8,036 5,586
128 3 284,8 197,9 12,06 8,379
5.5.4.1.1.1.3 LQM B ASE FREQUENCY
The base frequency is the lowest QAM modulator’s center frequency in LQMs: the three other modulators base their own
center frequency on this setting and the selected channel bandwidth. From this follows that the allowed base frequency
range depends on the channel bandwidth:
Syntax:
frequency <frequency>
• DVB-C: 7 or 8 MHz
• J.83 Annex B: 6 MHz
215
To set the channel bandwidth in Hz (channel raster):
Syntax:
offset <bandwidth>
NOTE! It is highly recommended to use the local standard compliant bandwidths to avoid any compatibility issues.
The available options depend on the chosen CATV standard (see above):
modulation {16-QAM|32-QAM|64-QAM|128-QAM|256-QAM}
Hint: Typically, 64-QAM is used. Higher order QAMs like 256-QAM allow more bits per symbols to be transmitted, but
also require better CNR in the HFC plant.
• DVB-C: the symbol rate is not specified by the standard, but the roll-off factor of the square-root
raised cosine filters is fixed to 15 % from which can be derived the maximum symbol rate. Typically
it is 6,9 MBaud for 8 MHz channel raster applications. Another common symbol rate is used in
head-ends where DVB-S signal is demodulated and re-transmitted in a DVB-C network unmodified
(except for the adapted PSI/SI tables). In this case, the symbol rate can be derived from the data
rate of the received DVB-S TS:
a) DVB-S_Data_rate = DVB-S_symbol_rate * Reed_Solomon * DVB-S_bits_per_symbol *
Code_rate:
a. For the typically used DVB-S symbol and code rates, 27,5 MBaud and 3/4:
Data_rate = 27,5 * 188/204 * 2 * 3/4 Mbit/s ≈ 38,015 Mbit/s
b) DVB-C_Symbol_rate = DVB-S_Data_rate * 1/Reed_Solomon * 1/ DVB-
C_bits_per_symbol
c) From a and b above follows, that for the typically used DVB-C modulation, 64-QAM:
Symbol_rate = 27,5 * 2 * 3/4 / 6 = 6,875 MBaud
• J.83 Annex B: symbol rate is set automatically according to the standard values: 5,057 MBaud with
QAM 64, 5,361 MBaud with QAM 256
216
To set the symbol rate for all carriers in sym/s:
Syntax:
symbolrate <symbol_rate>
Caution! When more than one QAM RF output is enabled, the entered value must be less than the [Channel
bandwidth / (1 + roll-off_factor)], otherwise the modulators will disturb each other.
Syntax:
Syntax:
rolloff {12|15|18}
NOTE! In J83 Annex B-mode, the roll-off is always set automatically to 25%.
Syntax:
NOTE! This setting affects all modulators of the target QAM-module and cannot be bypassed at modulator level.
217
5.5.4.1.1.1.10 E NABLING RF OUTPUT
To enable/disable carrier transmission:
[no] shutdown
Syntax:
Syntax:
frequency <frequency>
Syntax:
modulation {default|16-QAM|32-QAM|64-QAM|128-QAM|256-QAM}
Syntax:
symbolrate {default|<symbol_rate>}
Caution! When more than one QAM RF output is enabled, the entered value must be less than the [Channel
bandwidth / (1 + roll-off_factor)], otherwise the modulators will disturb each other.
218
To learn more about symbol rate and how to configure the default value, refer to
chapter 0 above
Syntax:
Syntax:
[no] shutdown
Luminato COFDM modulators are intended to be used in DVB-T over coax applications. They feature four modulators in
adjacent channels, sharing the same upconverter. When the base frequency of the first modulator is set, the frequencies
of the other modulators follow the first one in incremental steps defined by the channel bandwidth. Each modulator may
be enabled or disabled individually.
219
The amount of modulators depends on used modulation mode:
Typically, DVB-T receivers support both modes, therefore the 2K mode can be used to maximize the amount of available
modulators in module. For compatibility purpose 8K mode is available, but with a reduced amount of modulators.
To maximize the available bitrate, protective features of DVB-T modulation can be set to minimum in coaxial access
network. This is not a problem since DVB-T modulation offers more robust transmission over coax than comparable QAM
modulation.
Up to two exact copies of any output multiplex can also be transmitted as IP streams; this is sometimes referred to as IP
mirroring. This is useful for copying a multiplex to another multiplexer in another location or just simply for monitoring
purposes.
Caution! It is strongly advised to select the Transmission mode prior any other RF or IP configuration, since it will
cause the module to reboot in order to load the appropriate firmware
Syntax:
220
NOTE! The selected transmission mode affects the amount of modulators available: 4 modulators in 2k –mode and 2
modulators in 8k –mode!
Syntax:
Syntax:
frequency <frequency>
Syntax:
offset <bandwidth>
NOTE! It is highly recommended to use the local standard compliant bandwidths to avoid any compatibility issues.
221
5.5.5.1.2.1.3 C HANNEL OUTPUT LEVEL
The Power level defines the channel output level from the RF output interface. The available power level range depends
on amount of channels in use and the relative position of the modulators in use, see Table 4 below.
Syntax:
The guard interval is defined as the ratio of the guard interval duration to the duration of the useful part of the symbol
duration.
Syntax:
guard-interval {1/4|1/8|1/16|1/32}
Hint: The highest bitrate bandwidth is achieved using guard interval 1/32. Other alternatives may be used, if high
reflection in your coaxial network is suspected. Ideally, the guard interval should be slightly longer than the delay spread
of the channel.
modulation {QPSK|16-QAM|64-QAM}
222
5.5.5.1.2.1.6 D EFAULT INNER CODING RATE
In DVB-T transmission, FEC functionality is implemented through the use punctured convolutional coding. The code rate is
expressed as the ratio of useful bits per the total bits output by the inner convolutional coder, i.e. ratio of the input data
rate to output data rate.
Syntax:
Hint: The highest bitrate bandwidth in coax delivery is achieved using 7/8. However, this setting might not work
properly with all set top boxes. Changing to 5/6 may solve issues with certain set top boxes.
Syntax:
NOTE! This setting affects all modulators of the target QAM-module and cannot be bypassed at modulator level.
[no] shutdown
NOTE! Disabling COFDM -module’s RF-output does not affect multiplex IP streaming.
Syntax:
223
5.5.5.1.3.1 MODULATOR LEVEL COMMANDS
5.5.5.1.3.1.1 E NABLING / DISABLING THE MODULATOR
To enable/disable a modulator:
Syntax:
[no] shutdown
Syntax:
modulation {default|QPSK|16-QAM|64-QAM}
Syntax:
Hint: The highest bitrate bandwidth in coax delivery is achieved using 7/8. However, this setting might not work
properly with all set top boxes. Changing to 5/6 may solve issues with certain set top boxes.
Syntax:
guard-interval {default|1/4|1/8|1/16|1/32}
Hint: The highest bitrate bandwidth is achieved using guard interval 1/32. Other alternatives may be used, if high
reflection in your coaxial network is suspected. Ideally, the guard interval should be slightly longer than the delay spread
of the channel.
224
5.5.6 ISDB-TB OUTPUT: LCM-I
LCM-I is a quadruple ISDB-Tb modulator. ISDB-Tb (also known as ISDB-T International or SBTVD) is a digital television
broadcasting standard based on the Japanese ISDB-T standard. It is intended to be used in ISDB-T over coax applications. It
features four modulators in adjacent channels, sharing the same upconverter.
5.5.6.1 C ONFIGURING
The available commands for configuring the LCM-I are in most part identical to those of dedicated DVB-T output modules
such as the LCM-B. There are however two differences:
• The transmission mode is fixed to mode 1, i.e. FFT size 2k, and cannot be changed
• The modulation order is fixed to 64-QAM and cannot be changed
• Automatic SID allocation: the PID/SID allocation mode is by default set to SID mode and the SID values are
allocated using a different logic. The SID allocation range start value is rounded up to a value which is a multiple
of 32 and the allocated SID values are incremented in 33 step size.
IP output interfaces are always created in input modules (DVB-S2, DVB-T2, DVB-C, ISDB-T and FEC decoder). You may
create up to 120 IP streamers per input module.
NOTE! Since IP output creation is intended for MPEG streaming, some of the IP streamer settings are related to
service configuration and will be further discussed later in chapter “Service configuration”.
225
5.6.1 STREAM ROUTING STRATEGIES
User can choose between different strategies for stream routings.
NOTE! To assign multiple IP output streams per input connector, demultiplexing license is required.
Luminato supports both SPTS and MPTS IP streaming freely. Also stream copies can be created (demultiplexing licences
must be active).
• Multicast:
o copies of a single stream are delivered to multiple recipients
o Class D IP Address range:
224.0.0.0 – 239.255.255.255
o Typically used to broadcast TV content to several users simultaneously such as with live TV
broadcasts
o Advantages:
Reduces dramatically server and network load
Good when you are limited on server and network bandwidth and have a
relatively large client base
o Disadvantages:
Requires multicast support in your network devices
Complex network configuration
• Unicast:
o One-to-one content streaming: IP packets are delivered to a single recipient
o Typically used to deliver personalized content over an IP network such as a specific movie
to a given user (IPTV VOD)
226
o Advantages:
Easy to configure; doesn’t necessitate complex network configuring
Doesn’t require multicast support in your networking devices
Good solution if encoding with multiple bitrates (multi-bitrate streaming)
Client-Server point-to-point connection allows session protocols such as RTP,
which in turn will allow bi-directional communication, necessary for example in
VOD applications
o Disadvantages:
Consumes a lot of bandwidth since the same content must be streamed for each
users separately
Requires multicasting support in all your network devices
Complex network configuration
Internal streaming does not consume GE bandwidth; use it to preserve GE bandwidth when configuring stream
redundancy (stream backup).
To learn how to protect your streams with stream redundancy, see chapter 0
Syntax:
Arguments:
To specify the destination IP address and destination UDP port of the incoming stream:
udp <ip_address>:<port>
227
Arguments & keyword:
Syntax:
udp <ip_address>
Syntax:
udp <port>
5.6.2.4 TTL
TTL is an 8-bit field in the IP header, determining how long the IP packet can exist in the network before it is discarded.
The TTL value is reduced at each router passed: once this value reaches zero the packet is considered lost to prevent
undeliverable packets from circulating eternally and causing network congestion. Since TTL, is an 8-bit field its maximum
decimal value is 255. Typically the TTL is 5.
Syntax:
ttl {1…255}
ts-packets {1…7}
228
5.6.2.6 IP TRANSMISSION PROTOCOL
Select the desired transmission protocol for the IP mirror stream. There are two protocols:
NOTE! In order to be useful, RTP support is also needed in the receiving 3rd party equipment.
Syntax:
packet-format {default|udp|rtp}
NOTE! This command is not supported in LAS-A, LAS-B and LQM-B modules due to limited fpga resources.
229
Hint: In CBR mode, the output bitrate should be set high enough to allow some overhead for peak bitrates, hence
avoiding stream corruption. The peak versus average bitrate ratio can be remarkably high!
NOTE! In order to keep the outgoing IP stream strictly below the specified CBR limit, there is a special global setting
for the GE ports: CBR strict mode (disabled by default).
• External:
o GE1&GE2 ports
o User created VLANs assigned to the above mentioned GE1&GE2
• Internal:
o Internal payload interface labelled internal in the UI (technically it is a hardcoded VLAN
defined as internal, meaning its traffic is not forwarded by the GE1&GE2 ports)
o User created VLANs defined as internal (meaning their traffic is not forwarded by the
GE1&GE2 ports)
Syntax:
Keyword:
The receiver compares the received PCR value with its own 27 MHz clock counter value and the difference is used to
control the local 27 MHz clock through the use of a Phase Locked Loop (PLL).
230
PCR jitter is the variation over time of the delay in PCR –packet reception and may cause the PLL at the receiver to fall out
of lock. PCR jitter is caused by errors at PCR generation and regeneration and/or by timing shifts at transmission.
To learn how to configure how many TS packets are encapsulated in one IP packet, see chapter “TS packet encapsulation
count”
NOTE! The low PCR jitter mode is likely to cause some overhead in the output stream.
Syntax:
[no] low-packet-jitter-mode
Example - enable the low PCR jitter mode for IP output interface 1/1.1:
DocumentationTest(iface-ip-output-1/1.1)# low-packet-jitter-mode
DocumentationTest(iface-ip-output-1/1.1)#
5.6.3 REMOVING AN IP STEAMER
To remove an IP output interface from a submodule:
Syntax:
1 Correspond to the maximum amount of TS packets that can fit into an Ethernet frame.
231
5.6.4 IP-TO-IP MULTIPLEXER
The LIM-A is an IP-to-IP multiplexer and features four IP output interface. Each of the multiplexed IP output streams may
be duplicated as another IP output stream.
Syntax:
232
5.6.5.1 S YSTEM REQUIREMENTS
• A Pro:Idiom™ system license (obtained from Zenith Electronics LLC)
• A special Luminato software upgrade granting Pro:Idiom™ support (obtained on request from your local Teleste
Corporation’s sales representative)
• One or more LPI module for IP-to-IP multiplexing and Pro:Idiom™ scrambling
Syntax:
Syntax:
When Pro:Idiom™ scrambling is enabled, all services present in LPI’s output multiplex are scrambled.
NOTE! Up to eight services may be scrambled per LPI, any additional service will be multiplexed unscrambled. An
error status flag will be raised when the limit is exceeded and error message will be generated into the log.
233
5.6.5.5 U PDATING THE SYSTEM KEYS
Updating the Pro:Idiom™ system keys (“Fixed Keys”) present in the LPI module(s) is part of the key renewal procedure.
There are two possible reasons why key rewal might be necessary:
1. You might have chosen to use Fixed keys unique to your system
2. Your Pro:Idiom™ system security has been breached
Prior to updating your Pro:Idiom™ system keys, you must copy the file containing the new system keys to the target
Luminato chassis by using the copy -command.
NOTE! The key file must be named key.hex. If no file named key.hex is found, you will be unable to update the system
keys.
To learn how to upload a file to the Luminato chassis, see chapter “4.18.2.1
Uploading”
Once the key file has been copied, you may start updating the system keys residing in LPI’s memory.
Syntax:
Syntax:
Syntax:
Example:
234
5.6.6 OUTPUT MULTIPLEX’ IP MIRRORING
Up to two exact copies of any output multiplex can also be transmitted as IP streams; this is sometimes referred to as IP
mirroring. This is useful for copying a multiplex to another multiplexer in another location or just simply for monitoring
purposes. The procedure described below applies to all output modules1.
Syntax:
Syntax:
udp <ip_address>:<port>
Syntax:
udp <ip_address>
Syntax:
udp <port>
1 Due to technical restrictions, the discontinued ASI output module LAS-B, does not support IP streaming.
235
To specify the TTL of the outgoing packets:
Syntax:
ttl {1…255}
ts-packets {1…7}
NOTE! In order to be useful, RTP support is also needed in the receiving 3rd party equipment.
Syntax:
packet-format {default|udp|rtp}
NOTE! This command is not supported in LAS-A, LAS-B and LQM-B modules due to limited fpga resources.
236
5.6.6.2.7 P RIMARY STREAM PAYLOAD PORT
You have two types of payload interface:
• External:
o GE1&GE2 ports
o User created VLANs assigned to the above mentioned GE1&GE2
• Internal:
o Internal payload interface labelled internal in the UI (technically it is a hardcoded VLAN
defined as internal, meaning its traffic is not forwarded by the GE1&GE2 ports)
o User created VLANs defined as internal (meaning their traffic is not forwarded by the
GE1&GE2 ports)
Syntax:
Keyword:
NOTE! When the Null PID filter is enabled, the resulting IP stream will have a VBR (Variable Bit-Rate) and a CBR if
disabled. Some other device may require constant bitrate to support MPTS reception from IP network. In this case, Null
PID filter should be disabled. It is also worth noticing that null packets are removed only from the IP stream, not the
physical output!
Syntax:
[no] null-pid-filter
1 ISO/IEC 13818-1
237
5.6.6.2.9 R EMOVING A PRIMARY MULTIPLEX IP MIRROR STREAM
To remove a primary multiplex IP mirror steam:
Syntax:
no udp
Syntax:
Syntax:
Syntax:
Syntax:
Syntax:
NOTE! This command is not supported in LAS-A, LAS-B and LQM-B modules due to limited fpga resources.
238
5.6.6.3.6 D UPLICATE STREAM PAYLOAD PORT
To specify the payload interface in which the stream is present:
Syntax:
Keyword:
Syntax:
no duplicate-ip udp
The LPF-A is a dedicated Pro-MPEG FEC (forward error correction) processing module1. Depending on the purchased
license, the module operates either as a FEC encoder or as a FEC decoder, but not both at the same time. The amount FEC
channel is also license dependent.
Pro-MPEG CoP3 (SMPTE 2022) is an application layer forward error correction (AL FEC) protocol used in video streaming
over IP networks. To protect video streams against packet loss in IP networks, the Pro-MPEG FEC encoder sends
redundant FEC streams along with normal media streams. It makes it possible to recover lost, erroneous, delayed and
wrong order packets.
Pro-MPEG FEC is based on calculating exclusive-OR (=XOR) bitwise operations over multiple RTP packets. The stream to be
protected is called media stream which contains media packets. Media packets are arranged in a matrix with D packets in
239
a column and L packets in a row. XORs are calculated over each column and row of the matrix. See an example in Figure 31
below.
XOR
XOR
XOR
Column Depth (D) = 4
XOR
XOR
XOR
Media Media Media Media Row
Packet XOR Packet XOR Packet XOR Packet FEC
9 10 11 12 3
XOR
XOR
XOR
XOR
The resulting XORed media packets are called FEC packets, which are transmitted in separate FEC streams using UDP ports
relative to the media stream’s port N. Column FEC packets are transmitted in port N+2 and row FEC packets in port N+4.
Pro-MPEG FEC includes two modes: 1D and 2D. In 1D mode, only column FEC stream is transmitted. In 2D mode both
column and row FEC streams are transmitted. 2D mode provides stronger protection but bitrate overhead is higher.
Caution! It is strongly advised to select the Operation mode prior any other configuration of this module, since this
causes the module to reboot to load the appropriate firmware.
240
To set the operating mode of the FEC module to encoder:
Syntax:
• Overhead vs. delay: The size of the FEC matrix affects directly the overhead/delay –relationship. A
smaller matrix results into larger overhead but shorter delay. Similarly, a larger matrix results into
smaller overhead but longer delay.
• The packet dropping pattern: Column FEC stream corrects consecutive loss of packets, while row
FEC stream corrects non-consecutive loss of packets. This should be reflected in the FEC matrix
shape:
o if you experience mostly short bursts of packet drops, then the matrix should have more
rows than columns: L < D
o if you experience mostly long bursts of packet drops, then the matrix should have more
columns than rows: L > D
o if you experience mostly random length bursts of packet drops, then the matrix should be
square: L = D
241
• FEC column alignment induced latency:
o Block aligned arrangement uses a basic rectangle shape where all column FEC packets are
calculated almost at the same time in the end of matrix. To avoid bursts in transmission the
column FEC packets are delayed regularly distributed over the next matrix. This
arrangement ensures the most linear use of the bandwidth, but also means that the
latency due to FEC is twice (L x D). Due to the standard requirements1, if L > D in your
matrix settings, Block aligned arrangement is the only valid option.
o The Non-block aligned arrangement uses a parallelogram shape where column FEC packets
can be calculated and transmitted almost immediately after the last media packet it
belongs to. This permits to create a highly time-linear packet flow on the FEC stream and
242
can reduce latency and memory requirements in FEC decoder. Due to the standard
requirements1, this arrangement is available only when D > L.
Hint: Check the Pro-MPEG FEC overhead and estimated latency for the currently selected encoding parameters from
the stream quick-monitoring view.
1 SMPTE 2022-1-2007
243
5.7.2.3 D EFAULT P RO -MPEG FEC ENCODING MODE
To configure the module default FEC encoding settings:
Syntax:
Syntax:
Syntax:
• error burst length (how many consecutive Ethernet frames are corrupted)
• error burst probability expressed in ppm (parts-per-million)
NOTE! The packet error generation configuration is stored in volatile memory, and thus will be lost after module
reboot.
Syntax:
244
5.7.3.2 D ISABLING PACKET ERROR GENERATION
To disable packet error generation:
Syntax:
Syntax:
LPF-A is dedicated Pro-MPEG FEC processing module1. Depending on the purchased license, the module operates either as
a FEC encoder or as a FEC decoder, but not both at the same time. The amount FEC channel is also license dependent.
FEC decoder corrects missing media packet in received stream by XORing received media packets and FEC packets. Each
FEC packet can be used only once in fixing process. Thus, the maximum number of correctable errors in single matrix is
L+D (row packets + column packets). However, there are many uncorrectable error patterns with less than L+D errors. All
error patterns with less than 4 missing packets can be fixed.
245
Row Length (L) = 4
5
Media Media Row
Packet Packet FEC
2 3 1
3
Column Depth (D) = 4
7
Media Media Row
Packet Packet FEC
9 4 10 3
1
Media 2 Media Media Row
Packet Packet 6 Packet FEC
14 15 16 4
FEC decoder uses following procedure to reconstruct lost packets in Figure 33:
Caution! It is strongly advised to select the Operation mode prior any other configuration of this module, since this
causes the module to reboot to load the appropriate firmware.
246
To change the operating mode of the FEC module to decoder:
Syntax:
The LPE-A is an EPG (Electronic Program Guide) processing module for providing full EPG information (present/following
and schedule for actual and other transport streams).
EIT generation and playout is based on user configurable profiles, allowing you flexible control over the EIT playout rate
and playout schedule, and the definition of the output languages in order of priority, thus enabling optimized bandwidth
usage.
247
Non-functional ports 1000Base-T interfaces reserved for
XML-TV traffic
NOTE! None of the front panel interfaces is currently functional.
The input modules demultiplex the EITs and SDTs from input TSs and forward them to the EPG receiver as temporary
internal UDP/IP multicast streams and, if in multichassis configuration, as temporary external UDP/IP multicast streams.
The EIT processing module also accepts external UDP/IP TS and XMLTV as EPG data sources. The received EPG information
is then stored in two distinct databases (input EIT and XMLTV) located in the module’s flash memory (4GB). The
generation of the outgoing EITs is based on user configurable EPG generation profile assignments. These profiles affect the
EIT type, playout rate and schedule. Once generated, the EITs are then forwarded to the UDP/IP streamer which will
forward them as multicast streams to the proper output multiplexes.
248
synchronized such that if the SW version/revision numbers conflict, the EPG processing module’s functionalities will be
disabled.
To ensure that EPG processing module’s SW version do not conflict with that of Luminato, you should update the
Luminato system software when installing the EPG processing module for the first time. The minimum required software
version is 7.2.X.
See the chapter “Software update” to learn more about software upgrading
1. If the target chassis is a member of a multichassis configuration, define how the chassis payload ports are
interconnected for interchassis EIT payload streaming by creating multichassis connection groups.
2. If you use an external EPG source such as the [Category] Broadcast Manager or a XMLTV source, define the
source parameters.
3. Map the external EPG sources (XMLTV channels or EIT input) to output services
4. Define the IP multicast address range used for EIT streaming. Ensure that this allocated IP address and UDP port
ranges will not overlap with the other IP payload streams.
5. If necessary, configure new EIT output profiles or modify the default EIT output profile
6. Assign EIT output profiles to the target output multiplexes via the NIT editor.
Syntax:
249
Argument:
• MPEG-2 TS: Any MPEG-2 TS containing EIT, it could for example, the [Category] Broadcast
Manager. With this source type the EIT is received from Luminato’s GE port. You must define the IP
multicast address of the broadcasted EPG information stream. The incoming stream must be
UDP/IP and compliant to ISO/IEC 13818-1 and ETSI EN 300 468.
NOTE! Ensure that the EITs and SDTs are transmitted on ETSI EN 300 468 compliant PIDs: 0x0012 for EITs and 0x0011
SDTs.
• XMLTV: In XMLTV, the EPG information is stored in a XML file. With this source type you must
specify the URL(s) of the XMLTV source and how often the XML file is updated. The on-module E1
and E2 ports are used for retrieving the XMLTV files, make sure that at least one of the ports is
connected and has access to the requested URL.
5.9.6.3.1.1 IP ADDRESS
To configure the external EPG source interface IP address:
Syntax:
250
Arguments:
Syntax:
NOTE! Static name server configuration is only available when both external source interfaces E1 & E2 use the DHCP
addressing method.
5.9.6.3.1.3.1 A DDING
To specify the static DNS name servers’ IP addresses:
Syntax:
5.9.6.3.1.3.2 R EMOVING
To remove the static DNS name server entries:
Syntax:
no ip name-server
5.9.6.3.2 A DDING AN EXTERNAL EPG SOURCE AND ENTERING EXTERNAL SOURCE LEVEL CONFIGURATION MODE
To create a new external EPG source entry:
Syntax:
source <source_ID>
251
Arguments:
NOTE! This command will enter EPG external source configuration mode.
• MPEG-2 TS: Any MPEG-2 TS containing EIT, it could for example, the [Category] Broadcast Manager. With this
source type the EIT is received from Luminato’s GE port. You must define the IP multicast address of the
broadcasted EPG information stream. The incoming stream must be UDP/IP and compliant to ISO/IEC 13818-1
and ETSI EN 300 468.
NOTE! Ensure that the EITs and SDTs are transmitted on ETSI EN 300 468 compliant PIDs: 0x0012 for EITs and 0x0011
SDTs.
• XMLTV: In XMLTV, the EPG information is stored in a XML file. With this source type you must specify the URL(s)
of the XMLTV source and how often the XML file is updated. The on-module E1 and E2 ports are used for
retrieving the XMLTV files, make sure that at least one of the ports is connected and has access to the requested
URL.
Syntax:
type {ts|xmltv}
Syntax:
description <source_name>
Syntax:
[no] shutdown
252
Keyword:
5.9.6.3.2.4.1 IP ADDRESS
To specify the multicast IP address and UDP port of the incoming stream:
Syntax:
addr <IP_address>
Argument:
Syntax:
port <UDP_port>
Argument:
Syntax:
payload-port {ge1|ge2}
253
5.9.6.3.2.5.1 F ETCHING INTERVAL
To specify the time interval at which the EPG processing module will fetch the XMLTV files:
Syntax:
interval <fetch_interval>
Argument:
NOTE! Once the command entered, the EPG processing module will immediately start fetching the XMLTV file,
fetching XMLTV files at the specified interval until the Time of Day at which point the fetching cycle will start again.
Syntax:
timeofday <hh>:<mm>:<ss>
Arguments:
Syntax:
254
Arguments:
Syntax:
fetch-all-urls
Natolanka(source-4ef8d836-50a9-4145-96d7-c5744e7d6f3b)# fetch-all-urls
Natolanka(source-4ef8d836-50a9-4145-96d7-c5744e7d6f3b)#
5.9.6.3.2.5.5 R EMOVING AN URL FROM A XMLTV SOURCE
To remove an URL from a XMLTV source:
Syntax:
Arguments:
Example – remove URL “file://weekly_vh1-europe.music_tvprofil.net.xml” from source entry ‘MyXMLTV’ URL identifier
‘VH1’:
255
5.9.6.3.2.6 SOURCE MONITORING
You can monitor either all sources simultaneously or a single specific source.
Syntax:
Argument:
Example:
EPG Sources
Id |Type |Name |Address |Status
4ef8d836-50a9-4145-96d7-c5744e7d6f3b|xmltv|EPGS.com |Multiple urls (28) |Ok
1 |xmltv|Filee |file://epg_4.xml |Ok
2 |ts |VLAN_EIT |udp://229.1.9.102:11103;GE2 |Ok
Natolanka#
5.9.6.3.2.6.2 V IEWING SINGLE EPG SOURCE STATUS
To view the status of a single configured EPG source:
Syntax:
Arguments:
Example:
Id: 1
Url: file://epg_4.xml
256
Last update: 2015-06-08 00:00:28
Next update: 2015-06-09 00:00:00
Status: OK
Natolanka#
XMLTV channel descriptions do not include any ONID/TSID/SID information and must be mapped to the output services
either manually or semi-automatically by matching the XMLTV channel names with the output service names.
Syntax:
Arguments:
257
5.9.6.3.3.1.3 S OURCE TYPE
In order to fetch the EPG data from the correct database (XMLTV or EIT database), you need to define the source type.
This will affect which parameters that must be provided for pointing to the EPG data source found in the database.
Syntax:
type {eit|xmltv}
Syntax:
Keywords:
tsid The TSID (Transport Stream Identifier) of the EIT database entry.
sid The SID (Service Identifier) of the EIT database entry.
Example – in mapping entry ServiceMap1, point to service ‘ONID 1 TSID 4001 SID 100’ in the EIT database:
Syntax:
258
Arguments:
Example:
Define the input service for the mapping entry ServiceMap2. The source identifier is MyXMLTV. The URL identifier is VH1.
The XMLTV file is locally stored in Luminato’s chassis.
Syntax:
Arguments:
NOTE! Removing the mapping of an input EIT, will revert to default EPG data mapping mode, where the EIT is
automatically mapped from the MPEG-2 TS input(s) of the output service by matching the service input ONID/TSID/SID
(see chapters above).
259
Example – remove the EPG data map labelled ServiceMap2:
Syntax:
Syntax:
Arguments:
Example – allocate IP addresses for EIT streaming within range 239.114.240.0 - 239.114.255.255:
260
5.9.6.4.2 UDP PORT RANGE
To define the UDP port allocation range for EIT streaming:
Syntax:
Arguments:
Syntax:
Arguments:
261
5.9.6.5.1.1 PROFILE NAME
To give a profile a descriptive name:
Syntax:
description <profile_name>
Syntax:
pf repetition-rates {dvb-cs|dvb-t}
Syntax:
Keywords:
actual Information about the present and following events in the actual (currently tuned in) multiplex is
shown. For example, 2 MUXs are declared in the NIT: A and B. The IRD is tuned in to MUX A
which includes EIT p/f actual in its tables: present/following event information is shown for all
services in MUX A only.
other Information about the present and following events are included the EIT p/f Other and is shown
other tuned-in multiplexes. For example, 2 MUX are declared in the NIT; A and B. The IRD is
tuned in to MUX A which includes EIT p/f actual + other in its tables: present/following event
information is shown for all services in MUX A and MUX B.
5.9.6.5.1.3.2 B ANDWIDTH LIMIT
To limit the allocated bandwidth for p/f EIT transmission:
Syntax:
pf bandwidth <limit>
Argument:
262
Name Description Allowed values
limit Maximum bandwidth limit in Kbit/s. The target value depends on the amount of services {64000…10000000}
and the quantity of related SI information.
NOTE! Allocate enough bandwidth for large p/f EITs or the configured repetition rates won’t be respected.
Syntax:
Syntax:
263
5.9.6.5.1.5 SCHEDULE
The schedule EIT transmits information about further future events than EIT p/f as a list of events in chronological order.
5.9.6.5.1.5.1 C OVERAGE
To configure how many days ahead the EIT Schedule shall cover:
Syntax:
Syntax:
Argument:
NOTE! Allocate enough bandwidth for large schedule EITs or the configured repetition rates won’t be respected.
Hint: Plan carefully how many days the schedule EIT shall include and consider if EIT schedule other is really necessary:
the amount of data can be quite formidable and it can quickly consume your precious bandwidth.
Syntax:
schedule mode{cbr|vbr}
Keywords:
vbr VBR (Variable Bitrate) mode (default); the EIT schedule is transmitted at variable bitrate
(VBR) with the Maximum bandwidth as a limiting factor
264
5.9.6.5.1.5.4 E NABLING / DISABLING EIT S CHEDULE
To enable/disable EIT Schedule generation:
Syntax:
Keywords:
actual Information about the scheduled events in the actual (currently tuned in) multiplex is shown. For
example, 2 MUXs are declared in the NIT: A and B. The IRD is tuned in to MUX A which
includes EIT schedule actual in its tables: schedule event information is shown for all services in
MUX A only.
other Information about the scheduled events are included the EIT p/f Other and is shown other tuned-
in multiplexes. For example, 2 MUX are declared in the NIT; A and B. The IRD is tuned in to
MUX A which includes EIT schedule actual + other in its tables: schedule event information is
shown for all services in MUX A and MUX B.
5.9.6.5.1.5.5 R EPETITION RATES
The repetition rate is the minimum rate at which all sections of the EIT schedule tables are transmitted and is expressed as
intervals in seconds (s). Depending on the configured Maximum bandwidth and the amount of services and the quantity of
related SI information, the actual repetition rate may be higher.
Syntax:
Arguments:
Hint: To preserve bandwidth, events further in the future should have lower repetition rates than events closer to
present time
To see the recommended minimum repetition rates, see ETSI TS 101 211
265
5.9.6.6 C REATING EIT OUTPUTS MANUALLY
By default, the EIT multicast streams are automatically mapped to the output multiplexes behind curtains. However, in
typical IPTV applications the actual P/F data is included in the SPTS outputs, whereas the schedule EPG data is streamed in
separate IP outputs. To this end, the Luminato EPG processing module allows you to create EPG data output streams
manually.
5.9.6.6.1 C REATING AN EIT STREAM ENTRY AND ENTERING STREAM CONFIGURATION MODE
To create an EIT stream entry:
Syntax:
output-stream <stream_identifier>
5.9.6.6.1.1 NETWORK ID
In order to be able to generate correct EPG data, you must associate the EIT output stream to the same network as the
outputs containing the media streams (video, audio etc.).
Syntax:
network-id {1…65535}
Syntax:
profile <profile_ID>
Syntax:
[no] force-actual-ts
Syntax:
addr <IP_address>
266
5.9.6.6.1.5 UDP DESTINATION PORT
To specify the IP destination address of the output stream:
Syntax:
port <UDP_port>
Syntax:
Syntax:
Arguments
267
5.10 APPLICATION MODULE
The application module, LPC, is a full-fledged Ubuntu Linux computer which allows you to run self-developed or standard
Linux applications on the module.
The module itself is connected to the Luminato platform with gigabit capacity. This internal capacity may be used to
stream payload and management traffic from the LPC to other Luminato modules and vice versa.
There are numerous applications which can be run in the module such as internet radio and TV broadcasting, local file
streaming, stream monitoring and analysis, CAS and middleware server etc.
The present document provides instructions on how to configure the module’s external interface settings.
For instructions about application development on the LPC, consult the separate
document: Luminato LPC Developer’s Manual
268
5.11 VIEWRIGHT™ BULK DESCRAMBLER LAB-A
LAB-A is a module that allows cardless descrambling of up to streams protected with Verimatrix Video Content Authority
System (VCAS™).
The LAB-A acts as a ViewRight® client and negociates entitlements from the VCAS™ CSM server via a secure HTTPS
connection.
269
5.11.3 INTERFACES
The MicroSD slot is non-functional. The USB port is used for connecting the UniKey dongle. The E1 and E2 1000Base-T
ports are intended for connecting to the Verimatrix VCAS™ CSM.
5.11.4 PREPARATIONS
Before inserting the LAB-A module into the Luminato chassis, please ensure that the provided UniKey USB dongle has
been plugged into the USB port U1, if not plug the USB dongle into port U1.
Once the UniKey dongle in place, you may insert the LAB-A module into the chassis.
270
4. Configure LIM-A’s input streams
5. Enable descrambling for LIM-A’s input streams
6. Configure LIM-A’s output streams as you normally would
To learn how to update LAB-A’s software, please refer to the web UI manual
NOTE! If LAB-A is not in the same subnetwork as the VCAS™ CSM server, you must specify the default gateway which
has a route to the VCAS™ CSM server.It is also worth noting that if you wish to connect to the VCAS™ CSM server via a
payload interface (GE1 or GE2), the gateways for E1 and E2 must be set to 0.0.0.0.
LAB-A’s external interface configuration procedures are identical to those of the EPG processing module.
• IP address or FQDN
• port
5.11.8.1 IP ADDRESS
To specify the VCAS™ CSM server’s IP address:
Syntax:
5.11.8.2 P ORT
To specify the VCAS™ CSM server’s port:
Syntax:
271
5.11.9 AES CIPHER MODE SELECTION
In the bulk descrambling configuration, the AES block cipher mode for stream descrambling is configured in the LIM-A
modules. LIM-A supports several AES block cipher modes for stream descrambling:
• CBC
• CBC-CISSA
• CBC-IDSA
• ECB1
• ECB2
You may select the cipher modes explicitly or let LIM-A detect automatically the input stream’s cipher mode.
Syntax:
blk-descramble-mode {auto|aes-cbc-cissa|aes-cbc-idsa|aes-ecb1|aes-ecb2|aes-cbc}
NOTE! In order to be able to descramble an AES scrambled input stream, the selected cipher mode must match the
cipher mode used in the input stream encryption; hence we highly recommend choosing the automatic cipher mode
detection auto.
272
6 SERVICE CONFIGURATION
This chapter describes the service configuration related procedures.
It is assumed in this chapter that you have configured all the necessary
interfaces, if not revert to chapter Interface configuration.
First, we will introduce the operating principles and concepts of service configuration in Luminato and then subsequently
describe in higher detail the related configuration procedures and CLI commands.
Selective forwarding must be used when you want to scramble services or when you want to groom services with
component filters.
273
Hint: The main advantage of selective service forwarding is that advanced processing is possible. The downside is that
any SID change of a given program in the input may cause service loss at output and require reconfiguration of the input
SID of the affected program in the output.
Compared to the selective forwarding method, the stream processing options in promiscuous forwarding are far more
modest:
• Automatic SID and PID remapping through the usage SID and PID allocation rules
• TS level PID inclusion and exclusion
NOTE! The services forwarded with promiscuous forwarding cannot be processed (descrambling excluded); service
scrambling and service level PID filtering are impossible.
This forwarding method is not totally promiscuous strictly speaking: the input SI streams and unreferred PID streams are
filtered out since PSI/SI
Example:
configure
interface qam output 1/1.4
mode pid
274
passthrough pids %b.%c mode exclude
Add\Remove PID into filter for specific input or add PID with remapping into filter for specific input (only in include -
mode).
Example:
network-id <network_id>
original-network-id <network_id>
pid-allocation-mode {follow|component|sid}
Defines the PID –allocation mode. Available modes are: “SID mode”, “Component type mode” and “Input Follow Mode”.
network-name <string>
275
no passthrough services <%b.%c>
Enable\Disable passthrough from specific input connector. Connector can be located in the same module only.
Add specific service opt-out filter for specific input connector passthrough entry. Connector can be located in the same
module only.
NOTE: All services are passed through from the defined input by default.
By default, Luminato automatically forwards from the input TS EMM streams that have output ECM streams related to
them or injects CAS generated EMM streams to the output TS. This EMM stream handling mode is called legacy –mode.
EMM stream references are automatically inserted to the output CAT if the automatic CAT generation is enabled (default).
The manual-include mode enables you to have more control over the EMM play-out: you may manually include EMM
streams by adding EMM source references to the output interface. The EMM source reference may be either an input
interface or an EMM generator. Manual PID remapping is also possible.
Enter manual EMM stream inclusion level and select the EMM source type.
Enter or add a CAS reference, specify the reference index ranging from 1 to 1000.
[exclude-from-cat]
[output-pid {32…8190}]
276
Enter or add an input TS reference, specify a reference index ranging from 1 to 65535.
Set the filtered CAS ID in hexadecimal format (for example 0x01000000) and optionnally the EMM input PID filter. The
filters are inclusive.
[exclude-from-cat]
[output-pid {32…8190}]
Automatic EMM PID mapping (default) or map a specific PID ranging from 32 to 8190. ca-id is CA Client id in hexadecimal
format (for example 0x01000000).
no service <%user-selected-id>
Print an informational message when entering the service level, telling whether the user creates a new entry or enters an
existing entry.
shutdown
Enable/disable service
input <%b>.<%c>
277
Define the source of the service
output-sid <SID>
no manual-name
Define service name, SI-character encoding and SI-character encoding length in bytes. If encoding and length values are
not inserted default values are used.
6.10.1.1 O VERVIEW
As per ETSI TS 101 211 V1.12.1, service type information is conveyed in the mandatory service descriptor in the SDT and
the optional service list descriptor in the NIT. By default in Luminato, this information is parsed from the input and copied
to the output tables. However, sometimes this information may be wrong, for example when convert-ing a HD service into
a SD service using an external transcoder which is unable to up-date the SI tables. Another use case could be when
converting, for example, a digital television service to a digital radio sound service by removing the video stream via
component filtering.
Syntax:
type {auto|hdtv|radio|teletext|tv|<service_type_number>}
Argument:
Descramble the SID specified input service using the selected CAM if input service is scrambled.
278
6.10.2.3 C OMPONENT DESCRAMBLING
descramble sid <input_sid> components
{all|ac3|audio|other|subtitle|teletext|video|<stream_type>} [language]
Select a predefined component type code set determining which components associated to the specified SID are to be
descrambled1. The language option will descramble only the specified component type containing the specified language
code(s) in the service’s PMT. Specify the target ISO 639-2 language code(s), comma separated if several are specified.
6.10.3 SCRAMBLING
scramble
no scramble
base-pid %pid
always-in-tables
1 The predefined type sets are based on the ISO/IEC 13818-1 stream type assignments
279
no always-in-tables
critical
no critical
ca-mode {automatic|not-scrambled|may-be-scrambled}
Set scrambling status. Normally (=automatic), a scrambled input service has CA information associated to it in various
PSI/SI tables (e.g. the PMT’s and the CAT’s CA_descriptors and the SDT’s flag free_CA_mode1). By default, this information
is parsed from the input and copied to the output tables. However, sometimes this information shouldn’t be present in
the input in the first place. Such situation could occur for example when using an external decoder which is unable to
update the PSI/SI tables; in such case the CA information associated to services decoded this way would remain in the
input stream.
To address this problem, you may choose to override the input service’s CA information and drop all the CA descriptors
from the PMT and the mark the SDT’s flag free_CA_mode as ‘0’ (=not-scrambled).
Another situation where you might need to override the input service CA information is when you have an MPTS output
with some services whose scrambling status change over time and you need the output service’s free_CA_mode to be
always set to ‘1’ (=may-be-scrambled).
no manual-provider-name
Define service provider name, its SI-character encoding format and length
type auto
type <nnn>
Specify service type automatically, based on input service (default) or define specific service type. Number can be decimal
or hexadecimal
no generate eit
280
(Do not) generate EIT table for interface
pmt-pid auto
pmt-pid <pid>
pcr-pid auto
pcr-pid <pid>
sdt-eit-mode {automatic|off|present-following|schedule}
If default state is include then filter starts fully filled by components from incoming service
281
[no] component-filter {include|exclude} pid <nnnn> [output-pid <nnnn>]
Add\Remove include\exclude filter rule to include\exclude component(s) with type video, audio, AC-3 audio, subtitle,
teletext or specific type (decimal or hex). If specified all then all such components will be included\excluded. Other way
user might specify maximum amount of components to include and languages (defined via comma as three letter codes or
* for any). If no language is specified then “any” is assumed (equal to “*”).
pid-, tag- and ecm-ca-id -filters are supporting remapping but only for include rules.
no component-filter
An example of a component filter definition where the user explicitly defines which components to have in the service:
An example of component filter definition where the user explicitly defines which components not to have in the service:
generate sdt
generate nit
generate cat
282
generate pat interval <msec>
no generate pat
no generate sdt
no generate nit
no generate cat
SDT is inserted from the configured template file, with the exception that certain fields are added dynamically. Service
descriptor is added for each service if it does not exist in the template. For example: with this feature, it is possible to
insert a custom descriptor to a service.
Enable “TDT only” - table generation from the device local time with the default insertion interval.
Enable “TDT only” - table generation from the device local time with specified insertion interval.
Enable TDT- and TOT -table generation from the device local time with default insertion interval.
Enable TDT- and TOT- table generation from the device local time with specified insertion interval.
If only msec1 is set, TDT insertion interval = TOT insertion interval = msec1
If both msec1 and msec2 are set, TDT insertion interval = msec1 and TOT insertion interval = msec2
283
generate tdt-tot mode input <%b.%c>
Enable TDT and TOT table passthrough from the specified input: <module.connector>.
The next commands are inserting LTO (local-time-offset) descriptors into TOT table.
Manual LTO can be used to add time offset information for those additional countries which are not supported in
Luminato by default.
LTO and manually defined LTO are configured separately. So if you have LTO and manual LTO, and would like to remove it,
you have to disable both by two commands
Generate LTO -descriptor in TOT -table for specified county and its region id. The country code shall be three letters.
Example:
Disable generation of LTO -descriptor for specific country code and region ID
Adding manually defined LTO -descriptor for selected country and region.
Examples:
generate tdt-lto lto manual IND 1 2009-04-10 03:00:00 03:00 02:00 negative
generate tdt-lto lto manual IND 2 2009-04-10 03:00:00 04:00 03:00 negative
generate tdt-lto lto manual USA 5 2009-04-10 03:00:00 04:00 03:00 positive
Example:
284
Configuring EIT license commands
show running-config
All eit settings can be seen with the show running-config –commands.
psi-capture {pat|cat|sdt|tdt|tot}
To arrange the output PMT components according to specific language order preferences:
Syntax:
Argument:
285
configure pmt-language-order fin,swe
To remove the output PMT language order preferences:
Syntax:
configure no pmt-language-order
PSI/SI table proxying can be enabled or disabled. The automatic capture of the tables is triggered by changes in the input
tables (version and CRC check).
One of the main advantages of this feature is that even if the PSI/SI source fails, the lastly captured table will still remain
inserted to the output multiplex meaning no interruption in the PSI/SI streams.
Hint: Using full PID passthrough in conjunction with the PSI/SI table proxying –feature is highly recommended in IP
centric networks with centralized PSI/SI management. This will allow service and component changes carried out at the
central headend to be automatically propagated to remote headends with minimal configurational effort at the sub-
headends. Additionally, thanks to captured table insertion method, the output PSI/SI streams at the sub-headends will
remain intact even if the central PSI/SI system should fail.
Syntax:
Keywords:
286
7 DEVICE MONITORING
show modules
Example:
DVBT_chassis# show modules 1
MODULE
HW type: LRT-C quad DVB-T2 CA (ver. B12)
Serial: HL00471214
Uptime (Cumulative): 8 days 19:12:51 (50 days 06:42:55)
Payload bitrate: RX=0 kbps TX=119672200 kbps
Payload IP address: GE1=192.168.90.111 GE2=192.168.90.121
Payload UDP source port: GE1+GE2=2001
Payload MAC address: GE1+GE2=00:90:50:04:f4:5d
STATUS
OK
show status
Show general status for modules, alarm listing and active terminal sessions.
show uptime
Syntax:
Syntax:
287
7.2 CAS SYSTEM
show cas
Example:
288
NOTE: Maximum number of streams depends on the amount of supported scrambling channel licenses. The number of
active ECM streams denotes as well the number of used scrambling channel licenses.
Example:
289
7.3 ETHERNET INTERFACES
Ethernet interface:
Example:
Example:
7.4 TS INTERFACES
show interfaces {input|output} {1…6}
Show module status and info. Includes receiver/modulator overview and status.
290
show interfaces {1…6} ca-descriptor-mode
For module level (“ip input a”): show configured inputs/outputs and their status (“input/output page”)
For stream (a/b.c): stream summary: output/input page row info + pid/service mode setting(out only) + service names
(service mode only).
0 1 2 3 4 5 6 7
123456789123456789123456789123456789123456789123456789123456789123456789
IP input: 3/1.4 Description: blabla
291
(type specific info here)
Standard: DVB-S
Frequency: 12597 MHz
Frequency offset: -41365 Hz
292
LNB current: 0 %
------------------------------------------------------------------------
DVB-T type
------------------------------------------------------------------------
Lock status: LOCK
Signal strength: 20 %
SNR estimate: 5.9 dB
Post-Viterbi BER: 3.9e-4
Final BER: 0.0e-0
Transmission mode: 8k
Bandwidth: 8 MHz
Frequency: 12597 MHz
Frequency offset: -41365 Hz
Show RTP input monitoring info for module IP input. Not available for ip output interfaces or mirrored ip output
interfaces.
Example:
Status: OK
293
Reordered packets: 0
Discontinuities detected: 0
Incorrect sequence numbers: 0
Show all services for specified connector. Input services shown for Inputs and Outputs services shown for Outputs. For
each services, status, service name, SID, type (TV/radio), bitrate and CA-status: free/scrambled are shown.
Example:
Example 1:
COMPONENTS
PID |Type |PCR|ID |Bitrate | Language
1027|Subtitle (6)| |999| 0|fin
2321|Teletext (6)| |10 | 225|fin
512 | Video (2)| * |1 | 3652|
650 | Audio (4)| |11 | 237|spa
651 | Audio (4)| |15 | 173|dut
294
Service provider: YLE
PMT PID: 256
PCR PID: 512
Example 2:
COMPONENTS
PID |Type |PCR|ID |Bitrate | Language
61 | Video (2)| * |2 | 2657|
62 |Teletext (6)| |10 | 227|fin
64 |Subtitle (6)| |999| 0|fin
66 | Audio (4)| |21 | 237|eng
67 | Audio (4)| |25 | 174|dut
Service provider: YLE
PMT PID: 60
PCR PID: 61
Component filters: default include (0 include filter(s), 0 exclude filter(s))
Show all PIDs for specified connector. Not available for output interfaces or ip input interfaces.
Example:
295
in 1/1.1 |256 |29 | 16| 27
in 1/1.1 |512 |839 | 4151| 8285
in 1/1.1 |513 |840 | 2653| 8176
in 1/1.1 |514 |785 | 3322| 9078
in 1/1.1 |515 |896 | 2266| 2980
in 1/1.1 |516 |671 | 2750| 8217
in 1/1.1 |581 |141 | 223| 287
in 1/1.1 |8191 |0 | 2929| 8545
Add/remove manual PIDs for monitoring. Not available for output interfaces or ip input interfaces.
Clear pid counters for all pids or optionally for one pid.
Show FEC decoder monitoring info for module IP input. Available only for FEC decoder input interface.
Example:
Input
Source address: any
Destination VLAN: ge2
Destination address: 239.239.2.1
Destination port: 1000
Packet format: RTP
Output
Destination VLAN: ge2
Destination address: 239.239.3.1
Destination port: 1000
Packet format: RTP
Status: OK
Bitrate: 4244kbps
296
FEC column depth (D): 5
FEC row length (L): 4
Latency: 179 ms
FEC decoder statistics
Valid packets: 405259
Uncorrected packets: 0
Corrected packets: 0
Duplicate packets: 0
Reordered packets: 0
Discontinuities: 0
Incorrect sequence numbers: 0
Network jitter monitoring
Current jitter: 0.00 ms
Peak jitter: (3 seconds) 0.01 ms
Show FEC encoder monitoring info for module IP output. Available only for FEC encoder IP output interface.
Example:
Input
Source address: any
Destination VLAN: internal
Destination address: 239.3.1.0
Destination port: 2010
Packet format: RTP
Output
Destination VLAN: ge1
297
Destination address: 239.2.1.1
Destination port: 6010
Packet format: RTP
FEC encoder: enabled (module default settings)
Status: OK
Bitrate: 7018kbps
Example:
Input
Source address: any
Destination VLAN: ge2
Destination address: 239.239.1.1
Destination port: 1000
Packet format: RTP
Output
Destination VLAN: ge2
Destination address: 239.239.2.1
Destination port: 1000
Packet format: RTP
FEC encoder: enabled
Status: OK
Bitrate: 4249kbps
298
FEC overhead: 45 %
Latency: 99 ms
Clears all monitoring counters on every IP input on selected FEC decoder interface. Available only for FEC decoder
interface.
Clears monitoring counters on selected FEC decoder IP input. Available only for FEC decoder IP input interface.
Example:
Input
Source address: any
Destination VLAN: ge1
Destination address: 239.2.1.1
Destination port: 6010
Packet format: RTP
Output
Destination VLAN: internal
Destination address: 239.4.1.0
Destination port: 5010
Packet format: RTP
299
FEC decoder status
FEC mode: 2D - Column & Row
Column FEC port: 5012
Row FEC port: 5014
FEC column depth (D): 6
FEC row length (L): 10
Latency: 228 ms
FEC decoder statistics
Valid packets: 740095
Uncorrected packets: 0
Corrected packets: 1381
Duplicate packets: 0
Reordered packets: 0
Discontinuities: 0
Incorrect sequence numbers: 0
Network jitter monitoring
Current jitter: 0.00 ms
Peak jitter: (48 seconds) 0.01 ms
lumi-guide# configure
lumi-guide(configure)# interface ip input 4/1.6
lumi-guide(iface-ip-input-4/1.6)# clear stats fec counters
lumi-guide(iface-ip-input-4/1.6)# clear stats fec peak-jitter
lumi-guide(iface-ip-input-4/1.6)#
Syntax:
Syntax:
Example:
Syntax:
300
configure environment [no] voltage {device|backup} alarm
Example:
301
8 FAIL-SAFE REDUNDANCY FEATURES
Luminato provides several fail-safe features to ensure uninterrupted service delivery:
• PSU redundancy
• 1+1 chassis redundancy
• RF/ASI input redundancy
• IP input stream redundancy
Input redundancy is used to back up primary source of services with one or several redundant inputs and doesn't require
any separate backup device to work. Redundant inputs may be automatically activated in case the user defined
redundancy triggering criteria of the currently active inputs are met entirely or partially.
To learn how to back up physical inputs (RF & ASI), see chapter RF and ASI input
redundancy
302
8.1.2.1 H ARDWARE
Any Luminato module type.
8.1.2.2 S OFTWARE
Luminato SW 3.3.x or higher.
8.1.2.3 L ICENSES
The Input redundancy –features doesn’t require any separate license.
Input redundancy feature manual and automatic input switching. You are able to define a set of triggers used as
conditions before a redundant input is automatically activated. The redundant inputs can be monitored continuously,
periodically or never. The last two modes are intended for multicast inputs when IP bandwidth is limited.
Redundant inputs are organized in a priority order list, higher priority inputs being at the top the list. Switch to a lower
priority redundant input occurs whenever any redundancy triggering conditions are met in the currently active input.
Automatic recovery to highest priority input is possible when continuous or periodical input monitoring has been enabled.
If automatic recovery isn't enabled, recovery to higher priority inputs requires user intervention.
In a configuration where both input redundancy and hardware redundancy (1+1 backup) are active, you may mark the
primary input and its redundancies as critical inputs. Failure of critical redundant inputs causes a handover to the 1 +1
backup device, even though individual primary and redundant inputs would not be marked as critical inputs.
NOTE! If no triggering criterion has been selected, the redundant streams may only be activated manually.
303
• PID timeout: The timeout before PID missing –warning is reported and before redundant input is activated due to
this trigger.
• Recovery timeout: Defines how long is waited before automatic recovery is tried. The timeout is calculated from
the moment input status has been monitored OK. The next input is the one with highest priority and OK status.
If input Monitoring mode is set periodical, the disabled IP input is deactivated and IGMP leave is sent in case of multicast
input.
If a redundant input switch has occurred, the Redundancy activated –notification is shown in module syslog. A SNMP trap
is sent whenever a warning flag is raised.
NOTE! Signal and Service warnings are issued only, if the input stream or service is defined as critical and the input
stream doesn't have any working redundant inputs.
The stream status depends directly on the selected triggers and the triggering sensitivity settings (bitrate threshold and
timeout). Hovering the mouse over a status indicator will give additional information about current status (Error!
Reference source not found.). A SNMP trap is sent whenever a warning flag is raised.
Hint: To prevent the need of reconfiguration of end-user IRDs in case of redundancy input switching, it is
recommended to use as identical input streams as possible, with the exception of the aforementioned special use case of
test picture as redundant input.
304
NOTE! With RF and ASI input redundancy, the redundant inputs must reside within the same module. This restriction
may be overcome by converting the RF and ASI inputs to IP streams and using IP input redundancy.
Example:
In the sub-sequent examples, we will use the dual DVB-T/T2 input module LRT-B and tune in both tuners to 714 MHz.
Input 2/1.1 is designated as the intended primary input, so navigating to its configuration level will look like this:
Syntax:
Arguments:
Example:
First, we will define input 2/1.1 as the primary input and then we will assign input 2/2.1 to it as a redundant input.
305
Syntax:
Keywords:
NOTE! If no input switching trigger has been enabled, the redundant inputs may only be activated manually.
NOTE! If automatic recovery isn't enabled, recovery to higher priority inputs requires user intervention.
Example:
In our example, the only useful input switching trigger is signal. We also wish the redundant input to automatically
recover to the primary input when its status is OK.
306
DocumentationTest(iface-dvbt2-input-2/1.1)#
Syntax:
Syntax:
• chassis level: The recovery timeout acts as a default value for all modules
• module level: The recovery timeout acts as a default value for all inputs of the target module Can be set to a
custom value or to use the chassis level value. Custom values will override the chassis level value.
• input level: The recovery timeout affects only the target input. Can be set to a custom value or to use the
module level value. Custom values will override the module level value.
Syntax:
307
Syntax:
Keyword:
Syntax:
Keyword:
Example:
We want to set the automatic recovery timeout to 10 s for input 2/1.1 only.
Syntax:
Keyword:
308
Name Description Allowed
values
five minutes before the redundant input status is updated to OK and automatic recovery can
take place. This mode is useful only when using IP stream redundancy with the redundant
IP inputs being disabled.
Example:
Refer to chapters from 0 to 5.4.4.2 for more details on the Critical input –setting
for ASI and RF inputs.
If you intend using service redundancy trigger, the output services need to be configured as critical: non-critical lost
services won’t trigger a redundancy input switch.
Example:
DocumentationTest(iface-dvbt2-input-2/1.1)# critical
DocumentationTest(iface-dvbt2-input-2/1.1)#
8.1.5 IP INPUT REDUNDANCY
When backing up signals originating from different input modules or when using external backup IP streams, you need to
create IP input and IP output interfaces. One of the IP inputs is designated as primary stream and up to four IP inputs may
be assigned to it as redundant inputs. The recommended configuration procedure depends on the MPEG transport stream
type: SPTS or MPTS. With SPTS redundancy we strongly recommend using the Passthrough any SID –feature for easier
configuration. With MPTS the primary and redundant TSs should be exactly identical.
To learn how to configure IP input redundancy, please refer to the separate web
UI manual
309
Luminato features an emergency notification mechanism that allows you to force a single emergency notification input
stream to all output streaming interfaces when the user configurable emergency notification triggering conditions are
met.
NOTE! This chapter is intended as a brief description of all commands related to emergency notification streaming
To learn about emergency notification streaming in greater details, please refer to the separate web UI
user manual
To specify the destination UDP IP address and port of the emergency notification input stream:
Syntax:
To modify the destination UDP port of the emergency notification input stream:
Syntax:
To specify the source IP address of the emergency notification input stream in case of SSM:
Syntax:
To specify the payload port used for emergency notification stream reception:
Syntax:
To specify the service to use from the input emergency notification stream:
Syntax:
Syntax:
NOTE! When using the triggers ext1-io-down|ext1-io-up|ext2-io-down|ext2-io-up; make sure that the
target EXT port’s functional mode is set to emergency
310
See chapter 9.4.3
Syntax:
Syntax:
The backup Luminato stays in stand-by mode until a failure occurs in the main Luminato. When the main device identifies
a failure event or the main device is not responding, all payload outputs of the main device are shut down based on
dedicated hardware circuitry to ensure the switch-off of all streaming. The secondary Luminato then takes over the
stream processing operations.
Signal backup can be arranged if the devices in the 1+1 system have the same input signals from independent sources. If
the main device detects the loss of any input signal that is configured as critical and the 1+1 Backup system is activated, it
will react and pass control to the backup device.
Luminato’s stream redundancy feature is intended for more sophisticated signal redundancy configuration.
For more information about using 1+1 backup system for signal redundancy, see
chapter “Using Luminato 1+1 backup for signal redundancy”.
For more information about using 1+1 backup system simultaneously with the
stream redundancy feature, see chapter “Using 1+1 backup together with the Stream
redundancy feature”.
8.3.1.1 H ARDWARE
• Two identical device setups (i.e. two Luminato chassis with identical set of modules).
311
• Both chassis have to be of HW version B10 or higher so that they support GOE (global output
enable) signaling in the chassis.
• If LAS-A quad ASI input modules are present in the system, they need to be of HW version B13 or
higher.
• A LACCB1 cable to connect the two chassis into a 1+1 Backup system. Backup device senses the
heartbeat signal of the Main device via the LACCB cable.
NOTE! If a faulty module is replaced with a module of a more recent type, then both devices’ modules must be
updated to the same type. When ordering a replacement for a broken module, please inform our Repair service it is for a
1+1 backup system replacement.
8.3.1.2 S OFTWARE
• Configuration synchronization and backup control over IP Luminato: SW 6.2.x or higher
• Both chassis must have the same SW version and identical (synchronized) configurations at all time
8.3.1.3 L ICENSES
• Both chassis must have a 1 + 1 Backup license.
• Both chassis must have identical module licenses.
• If the chassis has no valid 1 + 1 Backup license, the 1+1 Backup feature won’t be available
8.3.1.4 CAS
When DVB-CSA scrambling is being used in a 1 + 1 backup system:
• Both units require their own separate ECMGs. Using the same ECMG could result in an ECM generator overload.
More so, there would be a possibility that CAS won’t accept connection to the second unit because the
parameters are the same. The ECMGs IP settings behave differently in a 1+1 backup context compared to a
standalone configuration: the Main device uses the ECMG’s IP settings and the Backup device uses the ECMG’s
spare IP settings.
• Both units need to create their own ECM streams, regardless of their current active/passive state
• Both units need to receive an EMM stream, regardless of their current active/passive state. This has to be
configured in both the CAS and Luminato.
• Contact your CAS –administrator to obtain the correct settings of the ECMGs and the EMM streams.
NOTE! Since the spare IP settings are used by the backup device, ECMG redundancy is not possible in 1+1 backup
context.
To learn more about the ECMG settings, see chapter “ECM generator
configuration”.
312
8.3.2 OPERATING PRINCIPLES
The Luminato 1+1 Backup system has two main functions:
Under normal circumstances (no backup handover triggering event detected), the Main chassis is active and the Backup
chassis passive. In case of a failure, all the functions of the primary chassis are switched over to the secondary chassis:
Main becomes passive and Backup turns active. Recovery from a handover must always be done manually even if
failure/signal loss situation would be resolved. If necessary you may switch over manually in either direction: from main to
backup and vice versa.
Starting from Luminato SW 6.2.X, the 1 + 1 Backup scheme features 1 + 1 device IP pairing for configuration
synchronization and easy device control over IP. In normal usage, the main device is active and configuration
modifications are done to this device. After configuration is done, you may synchronize the configuration of the active
main device to the passive backup device. The synchronization is performed through an IP connection using one of the
MGMT1 port. Once synchronized, the 1 + 1 backup system setup is ready.
When DVB-CSA scrambling is used in conjunction with the 1 + 1 Backup scheme, two ECMGs are required: one for the
main device and the other for the backup device. Both devices will be connected to the ECMGs, regardless of their current
state, active or passive.
Device activity can be changed manually either from the main or backup device by the Handover/Recover button. Active
state means all the outputs are switched on and passive switched off.
313
8.3.2.1 C HASSIS ROLES IN 1 + 1 BACKUP SYSTEMS
There are four Chassis roles available in a 1+1 Backup system:
• Disabled: The chassis is working as a backup device, but the heartbeat monitoring of the main device is inactive.
All outputs are switched off, which means that all changes made in the device configuration won’t be visible on
the live network.
• Main: The chassis is working as an active main unit in the 1+1 Backup configuration, the output status depends on
the current chassis’ state (active/passive). The main ECMG is connected to this device.
• Backup: The chassis is working as a passive backup unit in the 1+1 Backup configuration, ready to take control on
main device’s request or if the connection with the main device is lost, the output status depends on the chassis
state (active/passive). The spare ECMG is connected to this device.
• Standalone: The chassis is working as a standalone unit without any active 1+1 backup configuration. All outputs
are switched on, which means that all changes made in the device configuration will be visible on the live
network. Both the main and spare ECMGs are connected to this device. Connection failure to the main ECMG will
switch to the spare ECMG.
8.3.2.2 H ANDOVERS
Handovers can be divided into two categories depending on whether the handover is controlled or not:
• Controlled handovers are triggered either manually or automatically as the result of a module failure or a
critical signal missing status code in the main chassis. The active main device disables its payload output ports and
hands over the control to the backup device, thus entering a passive state.
• Uncontrolled handover are triggered by a failure in the mainboard, rear I/O card or PSU of the main device,
causing the main device to be unable to do a controlled to handover backup device. Main device’s heartbeat
signal is lost. Backup device notices that and forces main device’s outputs offline. Backup device enables its own
outputs and becomes active device.
314
o An incompatible module inserted into chassis.
o An unrecognized module inserted into chassis.
o Single SW process restart for selected processes
Single SW process restart raises alert status if it causes a break in output services
that is expected to be longer than the delay caused by a switchover to the backup
o A repeated SW process restart
3. A local DXI communication failure within the chassis
• Three consecutive failures in reading the system's status set
o Assumption is made that the internal messaging do not work and the system is in an
unstable state
4. A module is inserted and it is booted up
• Handover is done when a module has booted up and is registered to system setup, i.e. a module
type has been recognized and internal messages are sent to/from module
5. A module is removed
6. A critical signal missing status is active
7. A fail of critical signal redundancy
There are 2 reasons when a passive backup device takes over control of the active main device:
NOTE! Losing connection to an ECMG will not trigger a handover to the backup device. In this case, you have two
options: investigate and re-establish the connection to the ECMG, or manually switch over to the backup device. Make
sure the spare ECMG connection is up and running before doing so!
Only the EIT processing module in the active device will create routing for output streams and the output streams are
routed to both active and passive output modules.
The EPG database is synchronized from active to passive device once per day.
Caution! If internal IP inputs in modulators are defined as critical IP inputs, they will prevent the execution of the
restore/handover procedure. Do not configure any IP inputs as critical signals, if they are system internal interface!
315
Caution! 1+1 backup will react immediately to the loss of critical signal even though stream redundancy would be
present and thus overriding it altogether.
See chapter Using 1+1 backup together with the Stream redundancy feature.
8.3.3.1 T HE COMMANDS
Enter the configuration mode:
DocumentationTest# configure
DocumentationTest(configure)#
Syntax:
Keywords:
master The chassis is working as an active main unit in the 1+1 Backup configuration, the output -
status depends on the current chassis’ state (active/passive). The main ECMG is connected to
this device.
backup The chassis is working as a passive backup unit in the 1+1 Backup configuration, ready to -
take control on main device’s request or if the connection with the main device is lost, the
output status depends on the chassis state (active/passive). The spare ECMG is connected to
this device.
standalone The chassis is working as a standalone unit without any active 1+1 backup configuration. All -
outputs are switched on, which means that all changes made in the device configuration will
be visible on the live network. Both the main and spare ECMGs are connected to this device.
Connection failure to the main ECMG will switch to the spare ECMG.
Syntax:
316
Argument:
Syntax:
Argument:
manual- The IP connection to the redundancy paired device is enabled and manual configuration
sync synchronization is possible.
Syntax:
redundancy do synchronize
NOTE! Since synchronization requires a reboot of the passive device, it can take several minutes before the
synchronization process is over.
Syntax:
redundancy do abort-synchronize
317
Syntax:
redundancy do handover
Syntax:
redundancy do recovery
NOTE! If backup control over IP is disabled, you must first manually activate the passive the main device and then,
within a 5 second window, use the ‘redundancy do recovery’ command.
Syntax:
show redundancy
For more information about acquiring and managing licenses, see chapter
“License management”.
Connect the LACCB cable (length between the EXT I/O connectors of both devices. These connectors are located in the
PSU (Figure 54). If the devices are too far apart from each other, you may use the LACCA cable (length 2 m) (the cable
must be cross-connected as in Figure 53).
318
EXT 1 EXT 2 DC IN
Luminato 1 EXT
IO connector
EXT 1 EXT 2 DC IN
Luminato 2 EXT
IO connector
FIGURE 36: INTERCONNECTING 1+1 DEVICE PAIRS WITH THE LACCA CABLE.
To learn more about external inputs and outputs, EXT1 and EXT2, see chapter
Error! Reference source not found..
FIGURE 37: THE MAIN AND BACKUP DEVICES ARE CONNECTED WITH LACCB CABLES FOR 1 + 1 BACKUP SYSTEM’S HEARTBEAT DETECTION THROUGH
EXT IO CONNECTORS
Set each device’s role, master to one and backup to the other.
Disable the Backup control over IP functionality on both devices. Disabling temporarily this feature ensures that no
unintended IP traffic will occur during the configuration procedure.
319
Lumimato3(configure)# redundancy connection off
Lumimato3(configure)#
FIGURE 38: THE CHASSIS ROLE HAS BEEN SET TO MASTER AND BACKUP CONTROL OVER IP HAS BEEN DISABLED.
Fully configure (interface, service, content protection etc.) the (active) master device.
Once all configuration done, pair up the master and backup devices by providing the paired device’s MGMT IP address1 on
both devices.
320
FIGURE 39: BUILDING CONNECTION
Next, the compatibility of the paired devices is tested. If this test fails, the synchronization feature of the Main and Backup
devices won’t be available and a warning flag will be raised specifying the reason of failure. You must resolve the ultimate
cause of incompatibility in order to proceed.
FIGURE 40: SW VERSION COMPATIBILITY TEST HAS FAILED; UPGRADE THE SW TO THE SAME RELEASE VERSION.
NOTE! A HW incompatible flag might also be due to a device reboot during configuration synchronization.
321
FIGURE 41: AN IP ONNECTION HAS BEEN ESTABLISHED AND THE COMPATIBILITY TEST HAS PASSED
Once an IP connection has been established and the compatibility test has passed, the configuration may be synchronized.
NOTE! Synchronization is always done from active to passive device! If necessary, press the Handover to… or Recover
from… button to activate correct device before synchronization.
There are a few seconds to abort synchronization sequence before the passive device will reboot with the new
synchronized configuration.
Once synchronized, the 1+1 Backup system should be in normal state where the Main device is active (output ports are
streaming the network) and Backup device is passive (monitoring Main device with its output ports disabled).
322
NOTE! Since synchronization requires a reboot of the passive device, it can take several minutes before the
synchronization process is over.
8.3.4 RECOVERING BACK FROM THE BACKUP DEVICE TO THE MASTER DEVICE
When a handover to the backup device has occurred and you wish to recover back to the main device, first ensure that
you have removed the cause of failure and that the main device is ready.
NOTE! Remember that if you have replaced a module in the main chassis, it must be identical to the original and its
peer module in the backup device!
There are two distinct procedures depending on whether the backup control over IP feature is enabled or disabled:
OR
• use the redundancy do handover command in the backup (active) device
2. Backup control over IP is disabled :
1. open up a CLI session on both device with the terminal windows side by side
2. Type in the backup (active) device’s CLI terminal redundancy do handover WITHOUT pressing the
enter key at the end of the command-line.
3. Type in the master device’s CLI terminal redundancy do recovery and press return key at the end
of the command-line.
323
4. Within five seconds (from the previous step), press the return key in the backup device’s CLI terminal.
Failing to comply will result in no recovery from slave to master device and you will have to repeat the
procedure from the start.
The 1+1 Backup system should now be in normal state where the main device is active (output ports are streaming to the
network) and backup device is passive (monitoring the master device with its output ports disabled).
• Ensure the backup device is ready for taking over the control.
• Hand over the control manually to the backup device.
• The 1+1 Backup system should now be in a state where the main device is passive with its output
ports disabled and the backup device active with its output ports streaming to the network.
• Insert or remove module(s) to the main device.
• If possible, it is highly recommended to test the main device in a test environment before
connecting it to the live network:
1. Connect cables to the test environment.
2. Select the Standalone device role (output ports are activated)
3. Set up the configuration and verify the functionality of the new configuration in the test
environment.
4. Switch the device role back to Master.
5. Reconnect the Master device’s cables back to the live network. It remains in the passive.
• Select the Disabled device role to the Backup device and Standalone to the Master device.
• Insert or remove module(s) to/from the Backup device according to what is present in modified
Master device. Remember that identical hardware and licenses are required in both devices!
• Wait until the modules have booted up in the backup device and select Master role to the master
device.
• Select Backup role to the backup device.
• If synchronization over IP is active and the compatibility tests have passed, you may use the
redundancy do synchronize command.
• 1+1 Backup system should now be in normal state where the master device’s output ports are
streaming to the network and the backup device is monitoring the master device with its output
ports disabled.
The Luminato’s stream redundancy feature offers possibilities for more sophisticated signal redundancy configuration.
324
8.3.6.1 C ONFIGURING CRITICAL SIGNAL INPUT
Signal redundancy in 1+1 backup configuration can be achieved by setting the signal as critical. The 1+1 backup feature
reacts to loss of critical input signal, but does not react to loss of individual services.
The sensitivity to signal loss can be adjusted by using these parameters. The most sensitive setups are achieved if the
threshold bitrate is set close to input’s normal bitrate and timeout is set close to zero. Similarly, to prevent switchover to
backup chassis due to temporary changes, e.g., due to weather dependent reception conditions, one should set the
threshold bitrate to zero and increase the timeout to a value that is sufficiently long compared to temporary changes in
reception conditions.
Syntax:
Argument:
To override the module level signal lost threshold at a specific input interface:
Syntax:
To remove the input interface level signal lost warning threshold override:
325
Syntax:
Syntax:
Argument:
Instead, you should define the redundant stream to as critical. In this case, if primary stream is lost, redundant streams are
checked first before switching over to backup chassis. If none of the defined redundant streams are present and the
redundant stream is set as critical, the 1+1 Backup feature will hand over the control to the backup chassis.
326
9 EXTERNAL INPUTS AND OUTPUTS – EXT1 & EXT2
Luminato features external multipurpose I/O-pins, EXT1 & EXT2, for several factory or user defined applications. These
pins are located in the PSU/interface module.
NOTE! 1+1 Backup is a licensed feature, if you do not have this license, Standalone role will be the chassis’ default
role and the aforementioned backup roles won’t be accessible.
Syntax:
Connect a two-wire cable between backup power supply device and Luminato EXT1 or EXT2 connector
327
9.3 INTRUSION ALERT
Either or both connectors, EXT1 and EXT2, can be used as intrusion alert detectors. When this intrusion detection loop
breaks the alarm is set, this could be triggered by an opening door or window for example. Luminato detects when the
intrusion detection pin goes to high-Z state. Alarm status is set in the Luminato’s web UI Monitor view. A report to syslog
and an SNMP trap will be sent. This status will stay until removed manually from device by setting the EXT I/O ports’
functional mode to off.
• EXT1:
o Pin 1: Output voltage 19…19.7 V, max output current 50 mA. When using this pin as an output, short
circuiting to ground is prohibited! Input voltage 19…26V, input impedance 17 kΩ.
o Pin 2: Connected to ground.
328
• EXT2:
o Pin 3: Output voltage 19…19.7 V, max output current 50 mA. When using this pin as an output, short
circuiting to ground is prohibited! Input voltage 19…26V, input impedance 17 kΩ.
o Pin 4: Connected to ground.
NOTE! Luminato cannot set the I/O pins to high-Z state by itself.
Syntax:
Keywords:
Name Description
up signaling wire is pulled up
down signaling wire is set to high-Z
both signaling wire state changes
Syntax:
NOTE! Only the three most severe alert levels (emergency, critical and alert) will generate an SNMP trap.
329
sent from Luminato when the alarm conditions are met. SNMP monitoring is now able to detect any air conditioning
problems in the remote site.
Syntax:
Syntax:
330
10 TECH SUPPORT FILE
Whenever contacting Technical support, you should generate a tech support file which provides essential information
about your current setup.
Syntax:
331
TELESTE CORPORATION
P.O.Box 323
FI-20101 Turku, Finland
www.teleste.com
Publication Name
Copyright © 2014-2018 Teleste Corporation. All rights reserved. Teleste and the Teleste logo are registered trademarks of Teleste Corporation.
Other product and service marks are property of their respective owners.
Teleste reserves the right to make changes to any features and specifications of the products without prior notice. Although the information in this document has been
reproduced in good faith, the contents of this document are provided “as is”. Teleste makes no warranties of any kind in relation to the accuracy, reliability or contents
of this document, except as required by applicable law.