CherryPicker® Application Platform

CAP-1000
Software Guide
v4.0
 Document Title: CAP-1000 Software Guide v4.0
Part No. 365-095-19245 x.2

Publication Date: 2/2014

ARRIS Trademarks, Copyright, and Other Proprietary Information

©ARRIS Enterprises, Inc. 2014. All rights reserved. No part of this publication may be reproduced in any form or by any
means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission
from ARRIS Enterprises, Inc. ("ARRIS"). ARRIS reserves the right to revise this publication and to make changes in content
from time to time without obligation on the part of ARRIS to provide notification of such revision or change.

MOTOROLA and the Stylized M logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC. and
are used by ARRIS under license. All other product or service names are the property of their respective owners.

LINUX
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU
General Public License is intended to guarantee your freedom to share and change free software--to make sure the
software is free for all its users. This General Public License applies to most of the Free Software Foundation's software
and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make
sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you
receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs;
and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny
you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the
rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them
these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for
this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they
have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributes of a
free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have
made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

ii ARRIS Enterprises, Inc.

 GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may
be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work,
and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language.
(Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The
act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a
work based on the Program (independent of having been made by running the Program). Whether that is true depends on
what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided
that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the
Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and
copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these
conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any
change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program
or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for
such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright
notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute
the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself
is interactive but does not normally print such an announcement, your work based on the Program is not required to print
an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the
Program, and can be reasonably considered independent and separate works in themselves, then this License, and its
terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same
sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this
License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of
who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent
is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the
Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the
terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to
be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative
is allowed only for non-commercial distribution and only if you received the program in object code or executable form with
such an offer, in accord with Subsection b above.)

CAP-1000 Software Guide v4.0 iii

 The source code for a work means the preferred form of the work for making modifications to it. For an executable work,
complete source code means all the source code for all modules it contains, plus any associated interface definition files,
plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component
itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the
source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights
under this License.

However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so
long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to
modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this
License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your
acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or
works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a
license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may
not impose any further restrictions on the recipients' exercise of the rights granted herein.You are not responsible for
enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent
issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of
this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy
simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not
distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License
would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable
under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to
apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity
of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system,
which is implemented by public license practices. Many people have made generous contributions to the wide range of
software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to
decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This
section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted
interfaces, the original copyright holder who places the Program under this License may add an explicit geographical
distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time.
Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or
concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License
which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or
of any later version published by the Free Software Foundation. If the Program does not specify a version number of this
License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write
to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving
the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

iv ARRIS Enterprises, Inc.

 NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM,
TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF
ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED
ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY OU OR
THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH
HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CAP-1000 Software Guide v4.0 v

 Caution
These servicing instructions are for use by qualified personnel only. To reduce the risk of electrical shock, do not perform
any servicing other than that contained in the Installation and Troubleshooting Instructions unless you are qualified to do
so. Refer all servicing to qualified service personnel.

WARNING: TO PREVENT FIRE OR SHOCK HAZARD, DO NOT EXPOSE THIS APPLIANCE TO RAIN OR MOISTURE.
THE APPARATUS SHALL NOT BE EXPOSED TO DRIPPING OR SPLASHING AND NO OBJECTS FILLED WITH
LIQUIDS, SUCH AS VASES, SHALL BE PLACED ON THE APPARATUS.

CAUTION: TO PREVENT ELECTRICAL SHOCK, IF THIS UNIT IS PROVIDED WITH A POLARIZED PLUG, DO NOT
CONNECT THE PLUG INTO AN EXTENSION CORD, RECEPTACLE, OR OTHER OUTLET UNLESS THE PLUG CAN
BE FULLY INSERTED WITH NO PART OF THE BLADES EXPOSED.

CAUTION: TO ENSURE REGULATORY AND SAFETY COMPLIANCE, USE ONLY THE PROVIDED POWER CABLES.

EQUIPMENT MUST BE CONNECTED TO PROTECTIVE EARTH.

vi ARRIS Enterprises, Inc.

 THIS EQUIPMENT HAS BEEN DESIGNED FOR CONNECTION TO AN IT POWER DISTRIBUTION SYSTEM WHEN
POWERED BY AC.

THIS DEVICE WHEN POWERED BY DC MUST BE PROTECTED BY A LISTED BRANCH CIRCUIT PROTECTOR
RATED MAXIMUM 25 A.

It is recommended that the customer install an AC surge arrestor in the AC outlet to which this device is connected. This is
to avoid damaging the equipment by local lightning strikes and other electrical surges.

FCC Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the Installation Manual, may cause harmful interference to radio communications.

Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be
required to correct the interference at his/her own expense. Any changes or modifications not expressly approved by
ARRIS Enterprises, Inc. could void the user’s authority to operate this equipment under the rules and regulations of the
FCC.

CAUTION: The power supply plug is intended to serve as a power disconnect device. The socket shall be installed near the
equipment and shall be easily accessible.

CANADIAN COMPLIANCE

This Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

FDA COMPLIANCE

Class I Laser Product. Complies with 21 CFR 1040.10 and 1040.11.

IEC COMPLIANCE

This product meets the IEC 60825-1 requirements for a CLASS 1 LASER PRODUCT.

International Declaration of Conformity

ARRIS Enterprises, Inc.

3871 Lakefield Drive

Suwanee, GA 30024, U.S.A.

declare under our sole responsibility that the CAP-1000 to which this declaration relates is in conformity with one or more
of the following standards:

EMC Standards

EN 55022 EN 55024 CISPR 22 CISPR 24 FCC Class A

Safety Standards

UL60950

following the provisions of the Directive(s) of the Council of the European Union:

EMC Directive 2004/108/EC Low Voltage Directive (LVD) 2006/95/EC

Restriction of Hazardous Substances Directive Waste Electrical and Electronic Equipment (WEEE)

2011/65/EU Directive 2002/96/EC

CAP-1000 Software Guide v4.0 vii

 CAP-1000 Series CMM TTT Chart
The Toxic and Hazardous Substance disclosure table and Environmentally Friendly Use Period (EFUP) Logo are
provided in accordance with Section 5&6 of the People’s Republic of China’s “Electronic Industry Marking Standard
for Control of Pollution Caused by Electronic Information Products”. The Toxic and Hazardous Substance disclosure
table and EFUP Logo cover all electronic information products (EIP) supplied by ARRIS Enterprises, Inc.

All parts named in this table with an “X” are in compliance with the European Union’s RoHS Legislation – “Directive
2002/95/EC of the European Parliament and of the Council of 27 January 2003 on the restriction of the use of certain
hazardous substances in electrical and electronic equipment.”

Caring for the Environment by Recycling

When you see this symbol on an ARRIS product, do not dispose of the product with residential or
commercial waste.

Recycling your ARRIS Equipment

Please do not dispose of this product with your residential or commercial waste. Some countries or
regions, such as the European Union, have set up systems to collect and recycle electrical and
electronic waste items. Contact your local authorities for information about practices established for
your region. If collection systems are not available, call ARRIS Customer Service for assistance.

viii ARRIS Enterprises, Inc.

 Contents

ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XXVII

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Getting Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii

CHAPTER 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
What’s New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
License Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Commercial Advertisement Loudness Mitigation (CALM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Basic Interoperable Scrambling System (BISS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Remote Authentication Dial-In User Service (RADIUS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
SCTE 18 Emergency Alert Service (EAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Service Description Table (SDT) Service Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
SNMP Support for Digital Program Insertion (DPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CAP-1000 Port Analyzer (CPAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
AGB240 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Video Captioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SNMP Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Single Program Transport Stream Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
MUX 3.0 EBIF Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Network Information Table (NIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

CHAPTER 2 Digital Video Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Digital Broadcast Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Digital Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Digital Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
MPEG-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

CAP-1000 Software Guide v4.0 ix

 MPEG-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
PID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
PSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Packetized Elementary Streams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Program Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DVB SI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
ATSC PSIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Bit Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Constant Bit Rate Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Variable Bit Rate Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Factors that Affect Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Available Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Picture Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Constant Bit Rate Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Variable Bit Rate Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Statistical Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Rate Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Rate Clamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Stream Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
High CBR to Lower CBR Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
CBR to VBR Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
High VBR to Lower VBR Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

CHAPTER 3 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Java Web Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Adobe Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Monitor Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
CAP-1000 Resource ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Upgrading the CAP-1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring Network Parameters for Initial System Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reconfiguring the CAP-1000 Management Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Starting the CherryPicker Element Manager for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Logging on to the CherryPicker Element Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Logging off the CherryPicker Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

CHAPTER 4 CherryPicker Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CherryPicker Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

x ARRIS Enterprises, Inc.

 Navigation Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Content Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Editing Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Applying and Discarding Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Editing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Sorting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Locked Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Hide Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Managing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Progress Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

CHAPTER 5 CAP-1000 System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Chassis Front . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Chassis Rear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Program Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Data Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Software Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Farmer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Tables and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Hardware Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

CHAPTER 6 Configuring the CAP-1000 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Viewing Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Setting the Device Time Format and Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Renaming the CAP-1000 as a Splicer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Managing NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Adding NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Synchronizing NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Deleting NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Setting the Injected BISS Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

CAP-1000 Software Guide v4.0 xi

 CHAPTER 7 Controlling and Upgrading the CAP-1000 Device . . . . . . . . . . . . . . . . . . . . . . . . . 83
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Device Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Planned System Reboot and Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Unexpected System Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Rebooting System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Restarting the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Restarting the Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Refreshing Program Headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
AGB240 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
UTC Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Creating Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Deleting Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Exporting Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Importing Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Connecting to Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Switching Managed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Using SNMP to Monitor CAP-1000 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
SNMP Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
SNMP Support for Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Trap Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
SNMP Support for Digital Program Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Recommended Practices for SNMP Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Obtaining the SNMP MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuring SNMP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Filtering Trap Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Upgrading the CherryPicker Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring GARP for CherryPicker Redundancy (CPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

CHAPTER 8 Managing Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
License Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Viewing the License Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Viewing Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Installing License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Transferring the License Guard and Data Flash Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Removing a License Guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Removing the Data Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Transferring the Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Using the Software License Key (SLK) Generator and Serial Number Repository . . . . . . . . . . . . . . . . . . 111
Accessing the SLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

xii ARRIS Enterprises, Inc.

 Using License Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

CHAPTER 9 Configuring Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configuring Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configuring RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configuring User Privileges for RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Testing RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Managing Digital Certificates and Private Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Importing a Digital Certificate and Private Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Restoring a Digital Certificate and Private Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

CHAPTER 10 Managing Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Default Admin Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Changing the Linux Root Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

CHAPTER 11 Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
1-Gigabit Ethernet Input Output Adapter (1G IOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
10-Gigabit Ethernet Input Output Adapter (10G IOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Small Form Factor Pluggable (SFP) Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Digital Signal Processor Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Physical Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Gigabit Ethernet Port States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Output Port States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Active Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Persistent Storage of Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Dynamic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Gratuitous ARP (GARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Routing Information Protocol (RIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Viewing Gigabit Ethernet Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Enabling Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Configuring Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Disabling Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Blocking Management Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Configuring Auto Negotiation and Link Speed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Configuring Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

CAP-1000 Software Guide v4.0 xiii

 Adding Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Deleting Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Using the CAP-1000 Port Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
CPAN Source Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
CPAN Destination Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Configuring CPAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

CHAPTER 12 Configuring ASI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
ASI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Video Input Output Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Active Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Viewing ASI Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Configuring ASI Output Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Configuring ASI Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Disabling ASI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

CHAPTER 13 Content Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Content Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Component Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Component Tree Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Component Tree Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Managing the Component Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Mux Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Mux Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Mux Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Showing/Hiding Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Dragging Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Grooming Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Grooming Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Grooming Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Grooming Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Drag-and-Drop Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Grooming Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Output Line Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Output Mux Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Tabular View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Output Line Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Output Mux Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

xiv ARRIS Enterprises, Inc.

 Timeline View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Selecting a Single Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Select a Context Menu Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Selecting a Range of Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Selecting Non-adjacent Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Canceling a Cell Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Copying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Filling UDP Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Filling IPv4 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Managing Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Ad Muxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Alarm Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

CHAPTER 14 Configuring Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Multiplex Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
SPTS and MPTS Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Multiplex Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
How Multiplexing Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Basic Interoperable Scrambling System (BISS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Scrambling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Session Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Injected BISS Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
BISS and Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Gigabit Ethernet Multiplex Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Maximum Number of Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Real-time Transport Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Time to Live (TTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Quality of Service Configuration (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
VLAN Tagging and Prioritization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
DiffServ and Type of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Bulk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Rate Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Multiplex Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Emergency Alert Service (EAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
MPEG Active and Standby Output Port States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Ad Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Optional SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Managing Gigabit Ethernet Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Detecting the Input Multiplex Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Creating Gigabit Ethernet Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

CAP-1000 Software Guide v4.0 xv

 Modifying Gigabit Ethernet Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Deleting Gigabit Ethernet Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Managing Gigabit Ethernet Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Creating Gigabit Ethernet Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Modifying Gigabit Ethernet Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Deleting Gigabit Ethernet Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Managing ASI Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Modifying ASI Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Clearing ASI Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Managing ASI Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Changing an ASI Input Multiplex to an ASI Output Multiplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Modifying ASI Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Configuring GPS Offset and Daylight Savings Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Configuring Optional SDT, Service Names, and Service Provider Names . . . . . . . . . . . . . . . . . . . . . . . . 274
Service Names and Service Provider Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Enabling Optional SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Disabling Optional SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

CHAPTER 15 Managing Tables and Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
DVB SI Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
ATSC PSIP Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Emergency Alert Message (EAM) Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Viewing Table Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Modifying STT, EIT, and ETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
STT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
ETT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
EIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Modifying STT, ETT, and EIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Modifying VCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
VCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
TVCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
CVCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Modifying VCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Managing Path SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Input Path SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Output Path SDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Enabling Path STD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Disabling Path STD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Creating Custom NIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Generating TOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Managing Output Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Viewing Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Renaming Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Managing Closed Captioning Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

xvi ARRIS Enterprises, Inc.

 CHAPTER 16 Managing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Example XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Input XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Output XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Device-level XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
XML Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Backwards Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Config Files Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Files Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Config Files Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Managing XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Importing XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Exporting XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Modifying XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Deleting XML Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Backing Up and Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

CHAPTER 17 Grooming Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Grooming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Grooming Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Supported Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Grooming License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Grooming Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Static Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Dynamic Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Passed PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Grooming Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Standard Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Custom Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Slate Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Grooming Definitions and Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Level-based Program Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Grooming Capabilities and Maximum Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Maximum Number of Elementary Streams per Groomed Program . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Maximum Number of Groomed Programs per Multiplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Maximum Number of Groomed Programs per Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Maximum Bandwidth Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

CHAPTER 18 Grooming Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Grooming Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

CAP-1000 Software Guide v4.0 xvii

 Grooming Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Bulk Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Grooming Programs Using Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Grooming Programs Using Tabular View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Grooming Programs and Creating an Output Multiplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Managing Grooming Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Adding Grooming Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Replacing Grooming Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Creating Grooming Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Deleting Grooming Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Grooming Encrypted Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Managing Output Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Program Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Output Program Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Adding Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Replacing Grooming Definitions for Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Deleting Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

CHAPTER 19 Grooming Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Grooming Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Stream Availability at Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
PID Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Audio Streams for the Visually Impaired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Grooming Elementary Streams using the Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Grooming Elementary Streams using the Tabular View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Managing Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Adding Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Replacing Grooming Definitions for Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Deleting Elementary Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Forcing Custom Grooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Enabling CALM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

CHAPTER 20 Grooming Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Standard Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Custom Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Managing Custom Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Uploading Custom Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Deleting Custom Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Grooming Files using the Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Grooming Files using the Tabular View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Deleting Groom Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

CHAPTER 21 Using Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

xviii ARRIS Enterprises, Inc.

 Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Recurring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Missed Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Managing Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Creating Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Modifying Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Deleting Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Applying Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Applying Multiple Trigger Events with Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Viewing Upcoming Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Viewing Action Definitions Associated with Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Removing Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Managing Missed Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Testing Trigger Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Manually Triggering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

CHAPTER 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders . . . . . . . . . . . . . . . 441
In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Enabling Rate Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Managing Stat Mux Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Stat Mux Pool Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Stat Mux Pool Maximums . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Stat Mux Pool Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Creating Stat Mux Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Modifying Stat Mux Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Deleting Stat Mux Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Managing Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Recoding Resource Reservation for Programs with MPEG-2 SD or HD Video . . . . . . . . . . . . . . . . 452
Recoding Resource Reservation for Programs with MPEG-4/AVC SD or HD Video . . . . . . . . . . . . 452
Audio Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Default Setting for Recoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Program Recoding Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Option Not to Recode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Rate Setting for Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Default Rate Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Rate Setting for Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Reserving, Releasing, or Dropping Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Software Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Changing Video Stream Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Missing Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Recoder Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Recoding and Digital Program Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Recoder Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Reserving Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Reserving Recoders in Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Reserving Recoders in Tabular View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Reserving Recoders in the Programs Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460

CAP-1000 Software Guide v4.0 xix

 Dropping Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Managing Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Personalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Viewing Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Viewing Cluster Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Optimizing Recoder Cluster Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Missing Recoders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Auditing Recoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

CHAPTER 23 Passing PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Passing PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Passing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Conditions for Passing PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Passing PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Deleting Passed PIDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

CHAPTER 24 Enabling Digital Program Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Digital Program Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Recoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
CUEI Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
How Digital Program Insertion Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Stream Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Video Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Audio Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Data Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Subtitles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
DPI and Network Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
SCTE 35 Cue Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
How Cue Insertion Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
CUEI Extra Output Streams and DPI Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
DPI Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Splicer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Number of Connections and Ad Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Response Time and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Ad Server Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
DPI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Ad Insertion License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
MPEG-4 AVC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Channel Naming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Port Naming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Splicer Naming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Synchronizing Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

xx ARRIS Enterprises, Inc.

 Out-of-Synchronization Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Verifying a Successful Ad Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492

CHAPTER 25 Enabling Emergency Alert Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Emergency Alert Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Emergency Alert Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Details Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
FIPS Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Alert Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Digital Program Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Enabling EAS on Input Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Enabling EAS on GigE Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Enabling EAS on ASI Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Enabling EAS on Output Multiplexes and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Passing EAS to Downstream Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

CHAPTER 26 Managing EBIF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Enhanced TV Binary Interchange Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
ETV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
EBIF Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Default Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
EBIF Pre- and Late-bind Ads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Extra Output Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
EBIF Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Timestamps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Transport Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Gigabit Ethernet Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Input Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Output Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
CPR and PRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
DPI and Network Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Network Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
DPI Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Ad Management Service and the Ad Decision Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Enabling or Disabling EBIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Enabling EBIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Disabling EBIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Configuring Device-level EBIF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Configuring Grooming-level EBIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Grooming Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Configuring EBIF for Ad Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522

CAP-1000 Software Guide v4.0 xxi

 Configuring EBIF for Primary Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Configuring EBIF for Backup Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Merging EBIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Merging Late-bind Ads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Merging Pre-bind Ads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Deleting EBIF Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Bypassing EBIF Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Managing Placeholders for ETV Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Adding Placeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Deleting Placeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544

CHAPTER 27 Configuring CherryPicker Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Redundancy Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Redundancy States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
CherryPicker Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
CR-DSP Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Failure Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Switchover Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
States for Primary CAP-1000 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Transition States for Backup CAP-1000 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Backup Group and Primary Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Configuring the Management Port for the Ad Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Configuring the Primary CAP-1000 for CPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Configuring Backup 1:1 Mode for CherryPicker Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Configuring Backup N:1 Mode for CherryPicker Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Forcing the Switch to a Backup CAP-1000 (Failover) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Forcing the Switch to a Primary CAP-1000 (Failback). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Auto Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Manual Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Upgrading the CherryPicker Software in Covering Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Configuring Link Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Enabling Link Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Disabling Link Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Synchronizing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

CHAPTER 28 Configuring Multiplex Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Multiplex Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Grooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Synchronization and Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Failback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Monitoring Backup Input Programs While Primary is Playing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

xxii ARRIS Enterprises, Inc.

 Configuring MRED on Output Multiplexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Forcing the Switch to Backup Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Forcing the Switch to Primary Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

CHAPTER 29 Configuring Program Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Program Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Stream Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Primary Source Program Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Backup Source Program Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Switchover Conditions for PRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Switchback Conditions for Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Error-free Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Alarm Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Configuring PRED in Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Configuring PRED in Tabular View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Managing Backup Streams and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Deleting Backup Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Deleting Backup Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Forcing the Switch to Backup Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Forcing the Switch in the Content Picking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Forcing the Switch in the Redundancy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Forcing the Switch to Primary Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Forcing the Switch in the Content Picking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Forcing the Switch in the Redundancy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

CHAPTER 30 Configuring Slate Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Backup Slate Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Rules for Selecting Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Switchover Conditions for Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Switchback Conditions for Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Error-free Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Error Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Managing Slate Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Uploading Slate Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Deleting Slate Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Configuring Slates (Second-level Backup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Configuring Device-Level Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Configuring Mux-Level Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Configuring Program-Level Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Deleting Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Deleting Slate Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Managing Action Definitions for Slates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Managing Action Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Deleting Slate Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Deleting Slate Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Forcing the Switch to Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

CAP-1000 Software Guide v4.0 xxiii

 Forcing the Switch in the Content Picking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Forcing the Switch in the Redundancy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Forcing the Switch to Primary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Forcing the Switch in the Content Picking Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Forcing the Switch in the Redundancy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615

CHAPTER 31 Configuring Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Virtual IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
AIP, CPR, and the RIP Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Enabling Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Toggling the Active AIP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Disabling Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

CHAPTER 32 Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Configuring Gigabit Ethernet Port Mirroring in the Network Window . . . . . . . . . . . . . . . . . . . . . . . 624
Configuring Port Mirroring in the Redundancy Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Disabling Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

CHAPTER 33 Configuring OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Link State Advertisements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
CherryPicker Redundancy Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Ad Insertion Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
OSPF Initialization and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
OSPF Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
OSPF Adjacencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
RFC Supported Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Optimizing OSPF Configuration in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
OSPF Fast Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
SPF Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
LSA Generation/Propagation Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
OSPF Implementation Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
CherryPicker Redundancy (CPR) Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Dual-home, Single-source Output Implementation with CPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Dual-home, Single-source Output Implementation with AIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Dual-home, Dual-source Output Implementation with AIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Dual-home, Multi-source Output Implementation with CPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
OSPF Reference Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653

CHAPTER 34 Analyzing Streams and Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

xxiv ARRIS Enterprises, Inc.

 Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Stream Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Component Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Input/Output Analysis Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
CALM Dialnorm Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Program Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Component Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Analysis Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Starting Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Stopping Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

CHAPTER 35 Managing Alarms and Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

In This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Alarms and Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Alarm States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Alarm Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Shared Input PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Alarms and Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Alarms Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Affected Node Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Alarm Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Context Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Settings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Other Alarms in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Managing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
When Alarm Sources are Deleted or Reconfigured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Viewing Raised Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Deleting Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Configuring Audible Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Using the Time Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Searching for Alarms by Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Configuring Alarm Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Scheduling How Alarms are Cleared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Changing Alarm Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Changing Alarm Debouncing Durations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Resetting Alarms to Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Synchronizing Alarm Settings Across Multiple CAP-1000 Systems . . . . . . . . . . . . . . . . . . . . . . . . . 692
Collecting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
Working with Managed Groups of CAP-1000 or AGB240 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Filter Events Based on Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Applying Settings to Managed Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

CAP-1000 Software Guide v4.0 xxv

xxvi ARRIS Enterprises, Inc.
 About This Guide

Purpose
The CAP-1000 Software Guide v4.0 explains how to configure, manage, and monitor a CAP-1000
device using the v4.0 software.

Audience
This guide is intended for service providers and operators who use the CAP-1000 to build high-
density digital video solutions for television service providers. Users should have a basic
understanding of digital video concepts, tools used in a headend environment, and computer
operations.

Related Documents
The following documents provide additional information on the CAP-1000:
• CAP-1000 Configuration Command Reference Guide
• CAP-1000 Error Code Reference Guide
• CAP-1000 Hardware Guide
• CAP-1000 Customer Release Update
• CAP-1000 SNMP MIB Reference Guide
• CAP-1000 XML Protocol Reference Guide

Language Support
The CAP-1000 GUI and documentation is available only in the English language.

CAP-1000 Software Guide v4.0 xxvii

 Getting Help

Getting Help
To get assistance with your product or solution, or to access learning materials, use one of the
following channels:
ARRIS Technical Assistance Center (TAC) provides access to technicians 24 hours a day, 7 days
a week for all products.
• Contact us via the phone: 888-944-HELP (888-944-4357) or 1-215-323-2345
• Contact us via the Web: http://www.arrisi.com/cc360
• Contact us via email: Tac.Helpdesk@ARRISI.com
DigitalCM provides access to software downloads and release notes at http://digitalcm.arrisi.com.
Learning Portal provides self-paced product training and course descriptions of instructor-led
training classes at http://www.arris.com/support/training. In many cases training can be given at
your location.

xxviii ARRIS Enterprises, Inc.

 CHAPTER 1
Introduction

In This Chapter
• Overview
• Hardware Components
• Specifications
• What’s New in This Release

Overview
The CAP-1000 is an IP-centric MPEG-2/MPEG-4 digital stream processor capable of high-quality
rate shaping, splicing, and multiplexing. It features field-replaceable processing modules, dual
hot-swappable power supplies, and fan trays, all in a single 1-RU chassis.

CAP-1000

CAP-1000 Software Guide v4.0 1

Chapter 1 Introduction Hardware Components

The CAP-1000 is a highly-programmable device that supports evolving technical standards and
emerging application needs through simple software upgrades, allowing customers to realize
continuous returns on their initial capital investment.

Hardware Components
The following illustration shows the main components of the CAP-1000.

A4LED A5LED ALED

FT 1 A1 A2 A3 A4 A5 A6 A7 A FT 2 FLTR

FT1LED FT2LED
VIO 1 B1 P0 1 P0 2 PM2LED B2 B
BLED
1 2 3 4

1 2 3 4

VIO 2 PM1LED GT AC 1 AC 2

CAP-1000 Components

Table 1-1 describes the CAP-1000 components.

Table 1-1 CAP-1000 Components

Name Description

A Input Output Adapter (IOA)

ALED IOA LEDs

A1 Reserved for future use. Not active. General Purpose

Input/Output port (Micro-D)

A2 License Guard

A3 Data Flash

A4 Ethernet port 1-2 (10-Gigabit SFP+)

A4LED Ethernet port 1-2 LEDs

A5 Ethernet port 3-4 (10-Gigabit SFP+)

A5LED Ethernet port 3-4 LEDs

A6 Ethernet port 5-8 (1-Gigabit SFP)

2 ARRIS Enterprises, Inc.

 Specifications

Table 1-1 CAP-1000 Components (continued)

A7 Ethernet ports 9-10 (electrical/RJ45)

B Digital Signal Processor module

BLED Digital Signal Processor LEDs

B1 Debug Serial port

B2 Ethernet port 1-2 (electrical/RJ45)

FT1 Fan tray (1)

FT1LED Fan tray (1) LED

FT2 Fan tray (2)

FT2LED Fan tray (2) LED

FLTR Filter assembly

VIO 1 Video Input Output card (1)

VIO 2 Video Input Output card (2)

PM 1 Power module (1) (DC version shown)

PM-1LED Power module (1) LEDs

PM 2 Power module (2) (AC version shown)

PM-2LED Power module (2) LEDs

GT Ground terminals

AC1 AC power receptacle (1)

AC2 AC power receptacle (2)

Specifications
Video
• MPEG-2 SD and HD streams
• MPEG-4/AVC, Main and High Profile (up to Level 4)
• HD: 1080i x 1920/1440, 30fps
• HD: 720p x 1280, 60fps
• NTSC: 480i x 544/528/480/352, 29.97fps
• PAL: 625i x 544/528/480/352, 25fps

CAP-1000 Software Guide v4.0 3

Chapter 1 Introduction Specifications

Audio
• Dolby Digital (AC-3) and Dolby Digital Plus (Enhanced AC-3)
• MPEG-2/AAC Layer I and II
• High-Efficiency Advanced Audio Coding (HE-AAC)

Control Console
• Browser-based CherryPicker Element Manager
• SNMP Support
• 4P4C serial console maintenance port
• RJ-45 Gigabit Ethernet port 1/9 and 2/1 for initial IP configuration

Input/Output Specifications

Table 1-2 Input/Output Specifications

Interface Formats ASI-BNC female (75 Ohms) MPEG-2 TS

Gigabit Ethernet Electrical 10/100/1000 Base-T
1-Gigabit Ethernet on Small Form Factor Pluggable (SFP) cage
10-Gigabit Ethernet on SFP+ cage

Input Data Rate per Port ASI –200 Mbps max

Output Data Rate per Port ASI –200 Mbps max

Debug Serial Port 4P4C Modular jack

Debug Ethernet Port RJ-45

Management Port 2/1 port for initial IP configuration

GPIO Port Reserved for future use. Not active.

15-pin Micro-D
Inputs—Ground to activate
Output—Pull to 12VDC max, 33mA max

Electrical / Mechanical Specifications

Table 1-3 CAP-1000 Electrical/Mechanical Specifications

Form Factor 1RU (1.75”) 19” rack mountable

AC Input Voltage 100 - 240 VAC, 50-60 Hz

DC Input Voltage -36 to -72 VDC

Power Consumption 3.5 Amps max, 350 W max

4 ARRIS Enterprises, Inc.

 What’s New in This Release

Table 1-3 CAP-1000 Electrical/Mechanical Specifications (continued)

Operating Temperature 0 to +50° C

Side Cooling Right to Left

Humidity 5-95% non-condensing

Emissions, Immunity, and Safety Emissions:

Certification EN 55022 (CISPR 22): 2010
FCC Part 15 Subpart B
Industry Canada ICES-003 Issue 4, February 7, 2004
VCCI V-3/2011.04 and V-4/2011.04
Class A Standards

Immunity:
EN-55024: 2010

Safety:
UL 60950-1 Second Edition
CAN/CSA C22.2 NO. 60950-1-07 Second Edition
IEC 60950-1: 2005
EN 60950-1: 2006 + A11: 2009

What’s New in This Release

This section describes the new features and functions in the CAP-1000 v4.0 software release.

License Mobility
The CAP-1000 v4.0 supports a new feature called “SLK license mobility.” This feature lets you
return SLK licenses back to your customer SLK pool for re-deployment to a different CAP-1000
system. The SLK license mobility function is an SLA option (p/n 504833-011-98) that must be
purchased and activated in the DigitalCM system. SLK license mobility is enabled at the customer
level for all CherryPicker devices and has unlimited use.
When processing a license mobility update, the CAP-1000 generates an acknowledgement code
which identifies the license that has been removed from the list of licensed features. This
acknowledgement code is then entered by the customer into the SLK web site. The SLK web site
will provide a code for the customer to enter into the CAP-1000 which will clear the
acknowledgement code from the CAP-1000 GUI and update the SLK customer database.

IMPORTANT The license mobility feature does not enable the sharing of mobile licenses between DM 6400 and
CAP-1000 systems. Mobile licenses are only applicable to specific CherryPicker systems; either DM 6400
or CAP-1000 units.

CAP-1000 Software Guide v4.0 5

Chapter 1 Introduction What’s New in This Release

NOTE The CAP-1000 can be downgraded to an earlier release, but it will retain the licenses that were in place
before the upgrade. If you need to use a CAP-1000 from an earlier release, use those license keys. Once a
“license revoke” has been applied, the system cannot be downgraded.

See section,“Using License Mobility,”on page 112 for more information.

Commercial Advertisement Loudness Mitigation (CALM)

The CAP-1000 supports volume leveling mandated by/pursuant to the Commercial Advertisement
Loudness Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters of
groomed AC-3 audio streams. When CALM is enabled for an AC3 live audio stream, you can edit
the Network dialnorm and DPI dialnorm values for each primary and backup stream. A
CAP1-SLK-CALM license is required to use this function.
See section,“Enabling CALM,”on page 402 for more information.

Basic Interoperable Scrambling System (BISS)

A CAP-1000 with a CR-DSP module supports BISS. A CAP1-SLK-BISS license is required to
use any mode of BISS. This feature provides encryption/decryption capabilities on the CAP-1000
platform to protect transmissions by using a “session word” established by the transmitting and
receiving parties prior to transmission.
The session word is entered into both the encoder and decoder for a specific multiplex. This
session word then forms part of the encryption of the digital TV signal and only receivers with the
correct word can decrypt the signal. The CAP-1000 can decrypt input MPTS or SPTS and encrypt
output MPTS or SPTS.
More stringent BISS encryption (Mode E) is also supported by the addition of an Injected
Identifier code. This code is embedded in the CAP-1000 at the device level and entered into the
encoder's BISS configuration. In this mode, the CAP-1000 can decrypt input MPTS or SPTS and
encrypt output MPTS or SPTS, using the same Injected Identifier for input and output of all
multiplexes.
Refer to section,“Basic Interoperable Scrambling System (BISS),”on page 231 and
section,“Setting the Injected BISS Identifier,”on page 80 for more information.

Slates
The CAP-1000 supports the use of slates that can be groomed to output in the event that both the
Primary CAP-1000 and Program Redundancy (PRED) sources are unavailable.
A slate can be a video file, a video file and audio file(s), or a video file and audio live stream(s).
For output programs or muxes that have a slate input source defined, the grooms can be forced to
switch from the Primary CAP-1000 to the slate source even though the primary source may not
have failed. A backup program can also have another program designated as the slate program for
a second-level backup.
See Chapter 30,“Configuring Slate Redundancy” for more information.

6 ARRIS Enterprises, Inc.

 What’s New in This Release

Remote Authentication Dial-In User Service (RADIUS)

The CAP-1000 supports RADIUS authentication and authorization for users logging into the GUI.
RADIUS enables the network administrator to use central authentication of login credentials.
Users' credentials (username/password) are kept in a single database on a RADIUS server instead
of on each device in the network. Each time a user tries to log into a device he/she is challenged for
valid credentials, which are then securely sent to the RADIUS server for authentication.
See section,“Configuring RADIUS,”on page 119 for more information.

SCTE 18 Emergency Alert Service (EAS)

The SCTE 18 Emergency Alert Messaging for Cable standard supports the broadcasting of
emergency alert information related to state- and local-level emergencies to digital receiving
devices. Software v4.0 lets you configure dedicated input multiplexes to receive EAS messages
from any number of EAS generators. A CAP1-SLK-EAS license is required to use this function.
Each dedicated input multiplex contains a details channel that supplies the audio/video service
pertaining to the alert. On reception of a SCTE 18 EAS, the program switches to the details
channel for the EAS generator. The EAS switchover to the details channel is controllable at a
program level for rate-shaped output multiplexes.
Refer to Chapter 25, “Enabling Emergency Alert Messaging,” for more information.

Service Description Table (SDT) Service Naming

The CAP-1000 supports the use of the Service Description Table (SDT) on non-DVB output
muxes on upstream devices (e.g. CAP-1000 / Cisco DCM). When the CAP-1000 is connected
downstream, it correctly detects the input mux type in the optional SDT tables at its input. To
enable this feature, the CAP-1000 ignores the SDT table when detecting the mux type. It uses the
NIT table instead to detect the mux type.
The CAP-1000 detects the Service Name in the SDT and uses it at the output so users do not have
to manually type in the name on the output. This helps to maintain consistency and eliminate
typing errors.
See section,“Service Names and Service Provider Names,”on page 275 for more information.

Alarm Handling
In Software v4.0, alarm handling has been redesigned to better view and manage alarms and
events for system operations. The CAP-1000 now reports on both alarms and normal events. A
raised alarm notifies a user when a normal or abnormal condition is occurring. An event notifies a
user of an incident that simply occurs.

CAP-1000 Software Guide v4.0 7

Chapter 1 Introduction What’s New in This Release

The CAP-1000 now reports on the severity levels: Critical, Major, Minor, Warning, Info, Event,
and Cleared. In addition, the new alarms function lets you:
• View, search, and sort raised alarms .
• View alarm details, such as a description of the alarm/normal event, time of occurrence,
affected nodes, and advice for resolving the issue.
• Filter alarms by severity level, DPI results, start and end date/time of occurrence, or supplied
search string.
• Clear alarms that are not automatically cleared by the system.
• Delete alarms.
• View alarm history, change the default values for clearing alarms, limit the number of alarms
and events that are collected, and configure debouncing durations for some alarms.
• View the input source for a selected alarm in the new “Affected Node” tree. The source of the
alarm can be one of the following: device, line, mux, program, or stream (PID).
• Collect alarm log files and export them for use by the Technical Assistance Center.
See Chapter 35,“Managing Alarms and Logs” for more information.

SNMP Support for Digital Program Insertion (DPI)

The CAP-1000 generates SNMP traps for every SCTE-35 table that is received on an input SCTE
35 PID. The stream must be a part of an input program that has its video groomed to an output
program that is connected to an ad server for DPI.
See section,“Using SNMP to Monitor CAP-1000 Devices,”on page 95 for more information.

CAP-1000 Port Analyzer (CPAN)

The CAP-1000 CPAN feature allows you to analyze either Gigabit Ethernet input or output traffic
from a separate dedicated port. CPAN sends a copy of all network traffic on one IOA port to a
network that is monitoring a connection on another IOA port. CPAN is supported on all ports of
the 1G IOA or 10G IOA modules.
See section,“Using the CAP-1000 Port Analyzer,”on page 154 for more information.

AGB240 Integration
The CherryPicker Element Manager (GUI) can fully manage any AGB240 device or a group of
AGB240 devices using the Single GUI Centralized Management (SGCM) function. The GUI
supports AGB240 Release 1.2.3.
See section,“Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices,”on page 87 for
more information.

8 ARRIS Enterprises, Inc.

 What’s New in This Release

Video Captioning
The CAP-1000 supports captioning of any online video that is closed captioned (CC) on TV. This
is an FCC requirement published August 25, 2011, referencing the “Twenty-First Century
Communications and Video Accessibility Act.”
See section,“Audio Streams for the Visually Impaired,”on page 382 for more information.

Open Shortest Path First (OSPF)

OSPFv2 is a dynamic routing protocol for use in Internet Protocol (IP) networks. On the
CAP-1000, OSPF is used to advertise the virtual IP addresses of the device when CherryPicker
Redundancy (CPR) or Ad Insertion Protection (AIP) is enabled.
OSPF can be selectively implemented on any Ethernet interface of the CAP-1000 running
software v3.3 (or higher). OSPF facilitates CPR failovers and virtual IP address (VIP) porting over
Layer 3 IP networks.
See Chapter 33,“Configuring OSPF” for more information.

SNMP Monitoring
Using the CAP-1000 SNMP Agent, you can now monitor CAP-1000 devices in a centralized
head-end environment, track unit operations, and generate traps and alarms. The SNMP Agent is
bundled with the CAP-1000 managed device.
See section,“Using SNMP to Monitor CAP-1000 Devices,”on page 95 for more information.

Single Program Transport Stream Grooming

In prior software releases, the CAP-1000 allowed the grooming of individual, elementary video
files to the output programs. In software v4.0, you can now upload elementary stream files,
extracted from Single Program Transport Streams (SPTS), via the GUI. The CAP-1000 extracts
the elementary streams and saves them to the Data Flash for subsequent custom file grooming to
the output.
See section,“Managing Custom Files,”on page 411 for more information.

MUX 3.0 EBIF Reporting

The CAP-1000 supports Enhanced TV Binary Interchange Format (EBIF) filtering at the device
and grooming levels. A CAP1-SLK-EBIF license is required to use this function. Whitelist and
blacklist filters are provided for controlling how EBIF applications are filtered. Filters at the
groom level have a higher priority than those at the device level.
The CAP-1000 also supports EBIF reporting in the form of the Internet Protocol Detail Records
(IPDR). These XML reports are compliant with the OC_Report_MUX_3_0_Final_Draft.xsd
schema defined by Cablelabs. The reports can read by an ETV Activity Reporting System (EARS)
system.

CAP-1000 Software Guide v4.0 9

Chapter 1 Introduction What’s New in This Release

See Chapter 26, “Managing EBIF,” for more information.

XML Configuration Files

All CAP-1000 systems require the use of one or more configuration files for correct operation in
different environments. Configuration files establish the initial configuration of the system. They
also enable the configuration of device-level, line-level, and multiplex-level components, such as
DVB, ATSC, MPEG-2, or MPEG-4 output multiplexes. Software v4.0 now supports configuration
files in XML format.

NOTE To maintain backward compatibility importing of text-based configuration files is also supported; however,
new configuration file commands added to the software post v4.0 can only be applied via an XML
Configuration file. A text-based equivalent of the command will not exist and will only be available in the
XML format.

See Chapter 16,“Managing Configuration Files” for more information.

Network Information Table (NIT)

You can create a custom Network Information Table (NIT) for use with the CAP-1000 running in a
Digital Video Broadcast (DVB) environment. The Network Information Table describes all
physical parameters of a DVB transmission channel, including the transmission path (terrestrial,
cable, or satellite), received frequency, type of modulation, error protection, and transmission
parameters. The NIT is also required for digital video broadcasting with DVB Simulcrypt.
See section,“Creating Custom NIT,”on page 298 for more information.

Time Offset Table (TOT)

The Time Offset Table (TOT) carries the UTC time, date, and the local time offset. The TOT is
transmitted in TS packets with a PID value of 0x0014. This is an optional table as per DVB
specifications.
The CAP-1000 can now generate the TOT on an output DVB multiplex using a Configuration file.
The repetition rate for TOT follows that of the Time and Date Table (TDT) currently implemented
by the software.
See section,“Generating TOT,”on page 301 for more information.

10 ARRIS Enterprises, Inc.

 CHAPTER 2
Digital Video Concepts

In This Chapter
• Digital Broadcast Service
• Digital Video
• Digital Compression
• MPEG-2
• MPEG-4
• Elementary Streams
• Transport Streams
• Packetized Elementary Streams
• Program Streams
• DVB SI
• ATSC PSIP
• Bit Rate
• Factors that Affect Services
• Bandwidth Management

Digital Broadcast Service

A digital broadcast service consists of the following major components:
• Networks—A collection of Moving Picture Experts Group (MPEG) Transport Stream (TS)
multiplexes transmitted on a single delivery system. For example, all digital channels on a
specific cable system.
• Multiplexes—A stream of all the digital data carrying one or more services within a single
physical channel.

CAP-1000 Software Guide v4.0 11

Chapter 2 Digital Video Concepts Digital Broadcast Service

• Services—A sequence of programs under the control of a broadcaster which can be broadcast
as part of a schedule. A bouquet is a collection of services marketed as a single entity.
• Components—One or more entities which together make up an event, such as video, audio,
and teletext.
The relationships among these items are illustrated below.

Digital Broadcast Service Model

12 Motorola, Inc.
 Digital Video

Digital Video
Digital video is a type of video recording system that works by using a digital, rather than analog,
representation of the video signal. Unlike analog video that degrades in quality from one
generation to the next, digital video does not. Each generation of digital video is identical to the
parent. Its characteristics include frame rate, spatial resolution, color resolution, and image quality.
• Aspect ratio—Standard television has a 4:3 aspect ratio - it is four units wide by three units
high. HDTV has a 16:9 aspect ratio, more like a movie screen.
• Resolution—The lowest standard resolution (SDTV) is the same as analog TV and will go up
to 704 x 480 pixels. The highest HDTV resolution is 1920 x 1080 pixels. HDTV can display
about ten times as many pixels as an analog TV set.
• Frame rate—A set's frame rate describes how many times it creates a complete picture on the
screen every second. DTV frame rates usually end in “i” or “p” to denote whether they are
interlaced or progressive. DTV frame rates range from 24p (24 frames per second,
progressive) to 60p (60 frames per second, progressive).
• Color resolution—The number of colors displayed on the screen at one time. One of the most
common video formats is called YUV, the color encoding system used for analog television
worldwide, including National Television System Committee (NTSC), Phase Alternating Line
(PAL), and SÉCAM (Séquentiel couleur à mémoire, French for “Sequential Color with
Memory”).
• Image quality—The characteristic of a video passed through a video transmission/processing
system. Digital technology improves picture quality and consistency through signal robustness
and forward error corrected (FEC) transmission, which enables adaptive equalization and the
removal of analog impairments, such as noise, ghosts, or distortions.

Digital Compression
Digital compression reduces storage space and transmission data rate necessary to store or transmit
information that is represented in a digital format. Digitizing video without compression takes
approximately five cable channels to show just one program. Since this method is not practical, a
standardized way of compressing video and audio was devised by the Moving Pictures Expert
Group. MPEG standards come in a variety of methods defined for specific uses. MPEG-2 was
developed specifically for broadcast-quality transmission.
When you look at two adjacent frames of film, most of the information in the first frame is
repeated in the second frame. Rather than record all of the information in both frames, MPEG
encoders record the first frame as a reference frame and then only record the information in the
second frame that differs from the first.

CAP-1000 Software Guide v4.0 13

Chapter 2 Digital Video Concepts Standards

Video Frame Compression

With respect to the digital compression, note that:

• Small areas of each frame have similar image, color, and intensity.
• Small areas of successive frames are similar, but displaced.
• Efficient data processing techniques can significantly reduce the amount of transmitted
information.
The first frame is encoded as a reference picture, called an I frame. The second frame is encoded
by storing only the new information. In the second frame, the background structure and clouds
remain unchanged; only the position of the rocket and exhaust fumes have changed. Since the rest
of the information can be inferred from the reference frame, the encoder saves space by not storing
redundant information. This means, however, that the second frame cannot be recreated at the
decoder without information from the reference frame.

Standards
The Moving Picture Experts Group (MPEG) is a working group of experts that was formed by ISO
and IEC to set standards for audio and video compression and transmission. The MPEG standards
consist of different parts. Each part covers a certain aspect of the whole specification.

MPEG-2
MPEG-2 is a standard for the generic coding of moving pictures and associated audio information.
It describes a combination of lossy video and audio compression methods which permit storage
and transmission of movies using currently available storage media and transmission bandwidth.
MPEG-2 is widely used as the format of digital television signals that are broadcast by terrestrial
(over-the-air), cable, ATSC, DVB, and direct broadcast satellite TV systems.

14 Motorola, Inc.
 Elementary Streams

MPEG-4
MPEG-4 is a standard used primarily to compress audio and visual digital data. Introduced in late
1998, it is the designation for a group of audio and video coding standards and related technology
agreed upon by the ISO/IEC MPEG under the formal standard ISO/IEC 14496.
H.264, MPEG-4 Part 10, or AVC (for Advanced Video Coding), is a digital video codec standard
that achieves very high data compression. H.264/MPEG-4 provides a significant improvement in
the rate-distortion efficiency, providing a factor of two in bit-rate savings compared with MPEG-2
video.
The CAP-1000 supports the H.264/MPEG-4 AVC format and enables standards-based Digital
Program Insertion (DPI) and splicing of programming in the H.264/MPEG-4 AVC format. It also
allows the coexistence of H.264/MPEG-4 AVC and MPEG-2 content within the same platform and
on the same ASI or IP-based network.

Elementary Streams
MPEG-2 streams are compressed, or encoded, as separate video and audio streams, called
elementary streams. An elementary stream is a collection of transport packets that comprise a
packetized elementary stream (PES) using one of the permitted MPEG-2 stream types. Each
transport stream consists of a set of elementary streams, each of which can contain either MPEG-
2/Dolby Digital AC3 encoded audio, MPEG-2 encoded video, or data encapsulated in an MPEG-2
stream.
The streams are encoded at bit rates determined by the encoder. The higher the bit rate, the more
information is stored. The more information that is stored, the better the video quality, but more
bandwidth is consumed. Each of these elementary streams has a packet ID (PID) that acts as a
unique identifier for that stream within the transport stream.
Because each stream is a continuous set of video frames or audio data, which is not suitable for
multiplexing, they are split into packets to make the multiplexing process easier to use. The result
of this split is the Packetized Elementary Stream (PES).

Transport Streams
Transport stream is a standard format for transmission and storage of audio, video, and data, and is
used in broadcast systems such as DVB and ATSC. The transport stream is specified in MPEG-2
Part 1, Systems (ISO/IEC standard 13818-1 or ITU-T Rec. H.222.0). Transport stream specifies a
container format encapsulating packetized elementary streams, with error correction and stream
synchronization features for maintaining transmission integrity when the signal is degraded.

Packet
A packet is the basic unit of data in a transport stream. It consists of a sync byte, whose value is
0x47, followed by three one-bit flags and a 13-bit Packet Identifier (PID). This is followed by a 4-
bit continuity counter. Additional optional transport fields may follow. The rest of the packet
consists of payload. Packets are 188 bytes in length.

CAP-1000 Software Guide v4.0 15

Chapter 2 Digital Video Concepts Transport Streams

PID
Each table or elementary stream in a transport stream is identified by a 13-bit PID. A
demultiplexer extracts elementary streams from the transport stream in part by looking for packets
identified by the same PID.

Programs
Transport stream has a concept of programs. Each single program is described by a Program Map
Table (PMT) which has a unique PID, and the elementary streams associated with that program
have PIDs listed in the PMT.
After the audio and video elementary streams are encoded, they are then multiplexed together to
create a Single Program Transport Stream (SPTS), known as a digital service. When multiple
services are multiplexed together, the result is a Multiple Program Transport Stream (MPTS).

Transport Stream

PSI
Program Specific Information (PSI) is metadata about a program (channel) and part of a MPEG
transport stream. The PSI data contains five tables:
• PAT (Program Association Table)
• CAT (Conditional Access Table)
• PMT (Program Map Table)
• NIT (Network Information Table)
• TDT (Time and Date Table)

16 Motorola, Inc.
 Packetized Elementary Streams

The PAT lists all programs available in the transport stream. Each of the listed programs is
identified by a 16-bit value called program_number. Each of the programs listed in PAT has an
associated value of PID for its PMT.
The PMTs provide information on each program present in the transport stream, including the
program_number, and list the elementary streams that comprise the described MPEG-2 program.
For each service in the multiplex, the PAT indicates the location of the PID values in the Transport
Stream packets for the corresponding PMT. The Transport Stream also supplies the location of the
NIT.

Program Association Table

With respect to the illustration, note that:

• PAT PID is always 0.
• Prog# column lists the MPEG Service numbers.
• PMT PID column lists the unique number that identifies the PMT.

Packetized Elementary Streams

The Packetized Elementary Stream (PES) is a specification in the MPEG-2 Part 1 (ISO/IEC
13818-1and ITU-T H.222.0) that defines the carrying of elementary streams in packets within
MPEG program stream and MPEG transport stream. The elementary stream is packetized by
encapsulating sequential data bytes from the elementary stream inside PES packet headers.
Transport streams and program streams are each logically constructed from PES packets. PES
packets are used to convert between transport streams and program streams.
A typical method of transmitting elementary stream data from a video or audio encoder is to first
create PES packets from the elementary stream data and then to encapsulate these PES packets
inside transport stream packets or program streams. The TS packets can then be multiplexed and
transmitted using broadcasting techniques, such as those used in an ATSC and DVB.

CAP-1000 Software Guide v4.0 17

Chapter 2 Digital Video Concepts Program Streams

The following illustration shows how the PAT, the PMT, and the PESs are related and the different
numerical identities for these programs:
• PAT links the Prog # (MPEG number) to the PMT number.
• PMT links the stream type (audio, video, and data) to the PES.
• PES table links the elementary streams to a PID.

Relationship among the PAT, PMTs, and PESs

Program Streams
A program stream (PS or MPEG-PS) is a container format for multiplexing digital audio, video,
and more. The PS format is specified in MPEG-1 Part 1 (ISO/IEC 11172-1) and MPEG-2 Part 1,
Systems (ISO/IEC standard 13818-1/ITU-T H.222.0). Program streams are created by combining
one or more Packetized Elementary Streams (PES), which have a common time base, into a single
stream.

18 Motorola, Inc.
 DVB SI

Program streams have variable size records and minimal use of start codes which would make over
the air reception difficult, but has less overhead. Program stream coding layer allows only one
program of one or more elementary streams to be combined into a single stream, in contrast to a
transport stream, which allows multiple programs.
MPEG-2 programs stream can contain MPEG-1 Part 2 video, MPEG-2 Part 2 video, MPEG-1 Part
3 audio (MP3, MP2, MP1), or MPEG-2 Part 3 audio. It can also contain MPEG-4 Part 2 video,
MPEG-2 Part 7 audio (AAC) or MPEG-4 Part 3 (AAC) audio.

DVB SI
Digital Video Broadcasting (DVB) is a suite of open standards for digital television maintained by
the DVB Project, an industry consortium with more than 300 members, and published by a Joint
Technical Committee (JTC) of European Telecommunications Standards Institute (ETSI),
European Committee for Electrotechnical Standardization (CENELEC), and European
Broadcasting Union (EBU). Digital television deployments in Europe and much of Asia, Africa,
and elsewhere use the DVB standards.
DVB Service Information (SI) tables provide network operation centers with the tools necessary to
offer programs and services across network streams that use the DVB system. The tables are added
to the MPEG-2 transport stream during encoding or multiplexing, and are used to de-multiplex and
describe data contained within the MPEG-2 transport stream. These tables work together with the
MPEG-2 Program Specific Information (PSI) tables to give the decoder access to all available
programming across an entire network.
The DVB SI tables provide the decoder with the necessary information to access all channels and
events available on an MPEG-2/DVB network. The CAP-1000 is used to pass through DVB tables
supplied by an external DVB generation system, or it can internally generate the data for a
DVB-compliant broadcast.

ATSC PSIP
The Advanced Television Systems Committee (ATSC) Program and System Information Protocol
(PSIP) is the ATSC digital television standard for carrying data about each channel. It defines
virtual channels and content ratings, as well as program guides with titles and descriptions. It also
sends the exact time referenced to UTC, the station ID, and conditional access information. PSIP is
defined in ATSC standard A/65A. Digital television deployments in North America, Taiwan, and
South Korea use the ATSC standard.
ATSC systems use a combination of the transport stream ID and the source ID to identify a
particular service. Depending on the value of the source ID, it may be unique only within the
current transport stream or it may be unique at a regional level (or at the network level for satellite
signals). This allows co-ordination of source IDs across different terrestrial networks.

CAP-1000 Software Guide v4.0 19

Chapter 2 Digital Video Concepts Bit Rate

PSIP is a collection of tables that allows the DTV transport stream to provide information about a
station's services and programming. Not all PSIP tables are required to be broadcast, but the FCC
requires that some tables must be carried in order for DTV ATSC receivers to work properly. PSIP
identifies the channel number and carries information on multiple program channels and how to
find them. Program-associated data, such as closed captioning and V-chip information, is
identified in PSIP tables.
PSIP helps viewers to receive programs and enables broadcasters to represent themselves to the
viewers. PSIP displays program information, station branding, and program promotional
information on the Electronic Program Guide (EPG) generated by the subscriber’s ATSC-ready or
TV set-top box.
Like DVB, ATSC includes system information and program data that allows navigation and access
to channels within the DTV transport stream, and provides necessary information for efficient
browsing and event selection; however, the format of ATSC service information is not compatible
with DVB service information.

Bit Rate
Bit rate refers to the number of bits per second (bps) at which the data in a video is being delivered.
MPEG-2 streams are compressed, or encoded, as separate video and audio streams, called
elementary streams. Streams are encoded at bit rates determined by the encoder. The higher the bit
rate, the more information is stored. The more information that is stored, the better the video
quality at the decoder, but the more bandwidth is consumed.

Constant Bit Rate Streams

Constant bit rate (CBR) streams are encoded at a set bit rate regardless of the amount of
information that needs to be stored. If there is not enough video information to fill the allotted
bandwidth, the encoder simply fills the rest of the stream with null packets. If there is too much
information for the given bit rate, quality is compromised.

Variable Bit Rate Streams

Variable bit rate (VBR) streams take into account the fact that some content is simple to encode,
requiring only a low bit rate, while other content requires a high bit rate to capture enough of the
relevant information. The encoder adjusts the bit rate to match the complexity of the content
within a set bit rate range. Variable bit rate streams do not use null packets to fill the stream to a
constant bit rate.

20 Motorola, Inc.
 Factors that Affect Services

Factors that Affect Services

Several factors impact the number and quality of services that can be carried on a given channel:
• Available bandwidth
• Desired picture quality
• CBR vs. VBR sources

Available Bandwidth
The first consideration is the available output bandwidth. In the United States, Japan, Taiwan, and
South Korea, channel bandwidth is generally 6 MHz per channel. In Europe and the rest of Asia,
channel bandwidth is generally 8 MHz per channel. Table 2-1 and Table 2-2 list both cable and
broadcast bandwidth specifications.
.
Table 2-1 Cable Bandwidth Specifications

Location Channel Bandwidth Modulation

US, Japan, Taiwan, and South Korea 6 MHz 64 QAM (26.94 Mbps)

256 QAM (38.77 Mbps)

Europe and the rest of Asia 8 MHz 64 QAM (38.77 Mbps)

256 QAM (51.1 Mbps)

Table 2-2 Broadcast Bandwidth Specifications

Location Channel Bandwidth Standard/Modulation

US and South Korea 6 MHz ATSC/8-VSB (19.39 Mbps)

Japan 6 MHz ISDB/OFDM (18 Mbps)

Europe and the rest of Asia 8 MHz DVB-T/COFDM (20~24 Mbps)

Picture Quality
With video compression, it is possible to squeeze an almost limitless number of streams into a
given bandwidth channel. The trade off, however, between the number of streams delivered and
picture quality is steep. The amount you can compress a stream without degrading the video
quality depends on a number of factors.

CAP-1000 Software Guide v4.0 21

Chapter 2 Digital Video Concepts Factors that Affect Services

Complexity of Video Content

Rate shaping, or recoding, is the process of dynamically reducing the bit rate of encoded video
content. One consideration when working with bit rates is the difficulty of the content. The more
items that are on the screen and moving, the more difficult it is for the image to be encoded. The
more information that the encoder needs to capture, the higher the bit rate must be to maintain the
video quality. Sporting events, for example, have many players on the field and many details
moving quickly in the background. Sporting events, therefore, typically require a higher bit rate.
Programs with relatively slow moving, simple content such as animation, can often be encoded at
far lower bit rates without significantly affecting the quality of the image.

Quality of Previous Encoding

The original source of the content, as well as the amount of compression prior to transmission, also
affects the amount of bit rate that can be reduced. Digital content has fewer artifacts from
conversion and can be more easily compressed, whereas content that has gone through several
conversions prior to transmission may degrade more quickly. If the content has been highly
compressed prior to transmission, more compression cannot be done without significantly
affecting the picture quality.

Number of Non-video Elements

Non-video elements, such as audio and data streams, are not recoded by the CAP-1000. Adding
non-video services to the multiplex reduces the bandwidth available for video content. The more
data that is multiplexed with a video stream in a given channel, the more the video needs to be
compressed.

Constant Bit Rate Sources

Constant bit rate streams are encoded at a static bit rate regardless of video complexity. The
following figure shows a stream that consumes 6 Mbps bandwidth.

Multiplexing CBR Streams

If you multiplex several CBR streams together using a service/program multiplexer, the resulting
stream is inefficient because it is padded with null packets.

22 Motorola, Inc.
 Bandwidth Management

Variable Bit Rate Sources

In variable bit rate streams, the bit rate is assigned according to the scene complexity.

Multiplexing VBR Streams

VBR streams are more efficient, especially when multiple VBR streams are multiplexed together.
The CAP-1000 accepts VBR streams at bit rates from 0 to 25 Mbps.

Bandwidth Management
The CAP-1000 enables you to convert video to a lower bit rate using different schemes:
• Statistical Multiplexing
• Rate Shaping
• Rate Clamping
• Stream Priorities
• High CBR to Lower CBR Conversion
• CBR to VBR Conversion
• High VBR to Lower VBR Conversion

Statistical Multiplexing
Statistical multiplexing is the process by which a number of variable bit rate streams are combined
together to make the most effective use of a constant bit rate channel. It is achieved by rate-
shaping multiple video streams simultaneously, and combining them into a constant bit rate
channel.

CAP-1000 Software Guide v4.0 23

Chapter 2 Digital Video Concepts Bandwidth Management

Statistical multiplexing enables operators to fully utilize previously wasted bandwidth. By

carefully re-bundling their SD programs to deliver the greatest number of programs in each analog
channel, operators can reclaim significant amounts of untapped or inefficiently used bandwidth.
For example, an operator delivering nine SD programs (averaging 4 Mbps each) in a channel
operating at 256 Quadrature Amplitude Modulation (QAM) is only using 36 Mbps of the available
38.8 Mbps – a waste of nearly 3 Mbps.

Grooming Multiplexes to Optimize Channel Bandwidth

Rate Shaping
Rate shaping reduces the instantaneous bit rate of a video program in real time using compressed
domain video manipulation techniques. Statistical multiplexing complements rate shaping, which
reduces the bandwidth requirements of individual HD and SD programs by up to 30 percent,
without affecting their picture quality.
Rate shaping converts constant bit rate programs to a variable bit rate based on the content of the
program itself. For example, a news broadcast with limited on-screen motion of an anchor-person
speaking consumes less space than a high-action sports program. VBR MPEG encoding
interpolates the images between key-frames, thereby reducing the amount of data that is
transmitted.
Furthermore, an operator can control the amount of bandwidth a program consumes and match it
to picture quality and delivery requirements. Rate shaping can also be performed on incoming
VBR programs to further reduce the amount of bandwidth consumed.

24 Motorola, Inc.
 Bandwidth Management

Rate Shaping Converts CBR Content to VBR with No Loss of Quality

By combining statistical multiplexing and rate shaping, an operator can increase the number of SD
programs delivered in each 256 QAM channel from 10 to 16 programs, which frees channels for
use by an HD service. For example, if the existing SD service is using ten analog channels, each
with eight to ten programs, re-bundling and rate shaping these programs reduces the bandwidth
requirement to seven channels and releases three channels for HD programs.
Statistical multiplexing and rate shaping can also be used to release bandwidth for HD. Operators
using the combination – with proper planning – can deliver three to four HD programs in a single
256 QAM channel. The result is a 50 to 100 percent increase in program usage, as compared to the
maximum of two programs that can be supported.

Rate Clamping
Rate clamping is a special case of rate shaping where the bit rate ceiling of a particular service is
limited. It is useful in xDSL or fixed bandwidth environments. It takes peaks that exceed the
designated bit rate and smoothly rate-shapes them. Rather than truncating the peak, the CAP-1000
recodes the stream slightly before and after the peak.

Compression of Bandwidth with Rate Clamping

CAP-1000 Software Guide v4.0 25

Chapter 2 Digital Video Concepts Bandwidth Management

The previous figure shows two points where the stream bit rate exceeds the 3 Mbps ceiling. The
peaks are smoothed, or rate clamped.

Stream Priorities
The CAP-1000 lets you set priorities for stream compression. By setting priorities, the CAP-1000
determines which streams are recoded and which streams are left alone. You can, for example, set
relative priority levels for each service. Services assigned a lower priority (1-5) are recoded before
services assigned a higher priority (6-10). Services assigned a Do Not Recode priority (11) are not
recoded. Hence, channels at a lower priority (1-5) sacrifice more bit rate than channels at a higher
priority (6-10).
Setting priorities is useful for controlling high bit rate streams that are crowding the output
multiplex. By reducing the priority of an input stream, the CAP-1000 reduces the bit rate first,
while preserving the bit rate of higher priority streams as much as possible.
This is useful in a multi-program VBR environment where the cumulative effect of each stream is
unpredictable. For example, an operator may deem it more acceptable to compress a children's
cartoon channel than a live sports event. Because the rate shaping is dynamic and applied on
demand, this preserves the quality of the input stream more efficiently than reducing the bit rate of
the entire stream by setting a maximum bit rate. However, the quality of the rate shaping is
dependent on the quality of the original content.

High CBR to Lower CBR Conversion

Constant bit rate streams are often encoded by service providers at predefined bit rates that may be
higher than necessary for good video quality. Once the service provider’s encoder captures the
video content, it adds null packets to the stream to maintain a constant bit rate.
When these constant bit rate streams arrive at your headend, you can use the CAP-1000 to strip the
null packets from these streams, saving bandwidth without compromising video quality. You can
strip some of the null packets and lower the bit rate to a variable bit rate, or you can strip all of the
null packets and reduce the bit rate to a constant bit rate.

CBR to VBR Conversion

With the CAP-1000, you can convert constant bit rate input to variable bit rate output to optimize
channel bandwidth.

26 Motorola, Inc.
 Bandwidth Management

CBR to VBR Conversion

As shown in the previous illustration, the CBR feed is compressed slightly at the point where the
combined bit rate of the feeds exceeds the available 27 Mbps in order to give bandwidth to higher
priority feeds. Because the bit rate of the feeds is changed, such that it varies across time, it
becomes a VBR stream.
If the CBR stream contains null packets, the CAP-1000 removes the null packets to reduce the bit
rate without affecting the video quality. If the CBR stream does not contain null packets, the
stream is recoded at a slightly lower bit rate until bandwidth is available.

High VBR to Lower VBR Conversion

Variable bit rate streams can also be re-encoded to a lower bit rate, when necessary, using the
CAP-1000 software. When the combined bit rates of the streams in a multiplex total more than the
available bandwidth, the CAP-1000 re-encodes the video portions of those streams.

Compression of Three VBR Streams

As shown in the previous illustration, if the available multiplex bandwidth is exceeded by 3

percent, then given that each of the three streams has been assigned an equal priority, each
program stream is compressed by approximately 1 percent (only during the period of time in
which the cumulative bit rate requirement exceeds the available bandwidth).

CAP-1000 Software Guide v4.0 27

Chapter 2 Digital Video Concepts Bandwidth Management

28 Motorola, Inc.
 CHAPTER 3
Getting Started

In This Chapter
• System Requirements
• CAP-1000 Resource ZIP
• Upgrading the CAP-1000
• Configuring Network Parameters for Initial System Access
• Starting the CherryPicker Element Manager for the First Time
• Logging on to the CherryPicker Element Manager
• Logging off the CherryPicker Element Manager

System Requirements
This section lists the requirements for running the CAP-1000. Software version 4.0 runs under
Linux 2.6.33.

Microsoft Windows
The CherryPicker Element Manager runs on hosts running Microsoft Windows 7® or Windows
8®.

Java Runtime Environment

The Java Runtime Environment (JRE) v1.6 (or higher) provides support to run the Java Web Start
application. The installer for the Java Runtime Environment is included on the Program Flash of
the CAP-1000.

Java Web Start

Java Web Start v1.6.0_20 (or higher) is an application that lets you access the CherryPicker
Element Manager that resides on the CAP-1000 via a browser window on your host computer.
Internet Explorer®10 is required. The installer for Java Web Start is included on the Program Flash
of the CAP-1000.

CAP-1000 Software Guide v4.0 29

Chapter 3 Getting Started CAP-1000 Resource ZIP

Adobe Reader
Adobe Reader v5.0 (or higher) is required to view the CAP-1000 Software Guide. The installer for
Adobe Reader is available on www.adobe.com.

Monitor Resolution
To display properly, the CherryPicker Element Manager requires a minimum monitor resolution of
1024 x 768 set to 16-bit colors or more.

CAP-1000 Resource ZIP

The CherryPicker Resource ZIP contains the following files:
• Software License Agreement (\cap4.0_build_xx\SoftwareLicense.pdf)
• Java Web Start 1.6.0_20 with Java Runtime Environment (JRE)
(\cap4.0_build_xx\webstart\jre-6u20-windows-i586.exe)
• TFTP Program (\cap4.0_build_xx\release\tftpd32.exe)
• CherryPicker Application Platform software v4.0 (\cap4.0_build_xx\release\cap4.0_build_xx)
• Documentation is no longer included as part of the CherryPicker Resource ZIP. Please refer to
section, “Getting Help,” on page xxviii for more information.

Upgrading the CAP-1000

Information about upgrading a CAP-1000 to the latest build is available in the Customer Release
Update. This document is provided on the CherryPicker Resource Zip file.

Configuring Network Parameters for Initial System Access

This section explains how to configure the network parameters for the CAP-1000 chassis. Setting
up the network parameters allows you to log in to CherryPicker Element Manager and perform
system configuration, management, and monitoring operations.
The CAP-1000 ships with the following default configuration:
• IP address of management (MGMT) port 2/1 set to 169.254.2.1
• Netmask set to 255.255.255.252
To make the initial connection to the CAP-1000, set the IP address of your PC to 169.254.2.2 and
the netmask to 255.255.255.252. Alternatively, some GigE ports on the CAP-1000 have default IP
addresses that can be used for initial system access, as described in the next section.

30 ARRIS Enterprises, Inc.

 Configuring Network Parameters for Initial System Access

10-Gigabit Ethernet Input Output Adapter

If your CAP-1000 has a 10-Gigabit Ethernet Input Output Adapter (10G IOA) module (six 1-GigE
ports plus four 10-GigE ports), the copper (RJ45) GigE ports 9 and 10 are configured as follows:
• IP address of port 1/9 set to 169.254.1.9
• IP address of port 1/10 set 169.254.1.10
• Netmask set to 255.255.255.0 for both ports

1-Gigabit Ethernet Input Output Adapter

If your CAP-1000 has a 1-Gigabit Ethernet Input Output Adapter (1G IOA) module (four GigE
ports), the default configuration for the GigE ports is as follows:
• IP address of ports 1/1, 1/2, 1/3, and 1/4 set to 169.254.1.1, 169.254.1.2, 169.254.1.3, and
169.254.1.4 respectively
• Netmask set to 255.255.255.0 for all four ports

Configuring Network Parameters

To configure network parameters:

1 Set the IP address and netmask of your local PC to 169.254.2.2 and 255.255.255.252, respectively.
2 Using an Ethernet cable, directly connect this local PC to the CAP-1000 Gigabit Ethernet
management port 2/1.

CAP-1000—Gigabit Ethernet Port 2/1

3 From this local PC, open a web browser, enter the CAP-1000 default IP address 169.254.2.1 in the
Address field, and then press Enter.

CAP-1000 Software Guide v4.0 31

Chapter 3 Getting Started Configuring Network Parameters for Initial System Access

The Software License Agreement (SLA) window opens.

Software License Agreement

To access the software running on a CAP-1000, you must accept the SLA. If you accept the
agreement, you can configure the IP address for the CAP-1000 and use the device. The SLA
window will not display at future boot ups. If you choose not to accept the agreement, you cannot
configure the IP address and the device is inaccessible.
4 To continue, click Accept.
The Network Setup window opens.
5 Enter the configuration parameters for each of the GigE ports that you want to enable.
6 Enter the Hostname for the CAP-1000.

32 ARRIS Enterprises, Inc.

 Configuring Network Parameters for Initial System Access

Network Setup (10G IOA Module Shown)

NOTE When the default IP address and netmask remain configured on management port 2/1, all GUI connections
are presented in the initial CherryPicker Application Platform Network Setup dialog.

7 Click Submit.

CAP-1000 Software Guide v4.0 33

Chapter 3 Getting Started Configuring Network Parameters for Initial System Access

Network Setup (10G IOA Module Shown)

8 Click Finish to complete the process.

You are now ready to connect to the CAP-1000 via the CherryPicker Element Manager using the
new network parameters.

Reconfiguring the CAP-1000 Management Ports

The CAP-1000 has a dedicated management (MGMT) port (2/1) on the Digital Signal Processor
(DSP) module that is designed to be used exclusively for management traffic such as GUI
connections, SNMP, Telnet/SSH, and SCTE messaging. While management may also be
conducted through the GigE video ports, using the management port for management activities
assures isolation from the video transport network.
The management port (2/1) defaults to 169.254.2.1 as described in the section, “Configuring
Network Parameters for Initial System Access,” in this chapter.

NOTE While newer versions of the DSP board have two physical management ports (2/1) and (2/2), they are a
bonded pair and share a single IP address. The second port (2/2) serves only as a redundant physical port.
Refer to the section, “Digital Signal Processor Module,” on page 135for information.

34 ARRIS Enterprises, Inc.

 Configuring Network Parameters for Initial System Access

To reconfigure the management port:

1 From the host PC where you run the CherryPicker Element Manager, open a browser.
2 In the Address field, enter the IP address for port 1/9 and press Enter.
The CAP-1000 Start Page opens.

CherryPicker Element Manager Start

3 Click Start CAP Element Manager.

4 If a Security Warning window opens, click Yes to proceed.
The Java window opens and Java is downloaded from the CAP-1000. At the completion of the
Java Web Start installation, the CherryPicker Application Platform Login window opens.
5 In the IP Address/Group menu, enter or select the IP address for the CAP-1000.

CherryPicker Application Platform Login

CAP-1000 Software Guide v4.0 35

Chapter 3 Getting Started Configuring Network Parameters for Initial System Access

6 Enter your User Name and Password.

IMPORTANT The default login user name is Admin with no password.

7 Click Go.
The CherryPicker Element Manager opens in the default view.
8 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
9 Under ID, go to 2/1.

NOTE The Link column shows the link speed and current status: Active 1000 Mbps (green), Active 100 Mbps
(blue), Active 10 Mbps (yellow), or Down (red).

10 Double click the IP address field and enter a value

11 Double click the Netmask field and enter a value.
12 Double click the Gateway field and enter a value.
13 Click Apply.

Network

14 Go to the next section, Starting the CherryPicker Element Manager for the First Time.

36 ARRIS Enterprises, Inc.

 Starting the CherryPicker Element Manager for the First Time

Starting the CherryPicker Element Manager for the First Time

To start the CherryPicker Element Manager for the first time:
1 From the host PC where you run the CherryPicker Element Manager, open a browser.
2 In the Address field, enter the IP address for port 2/1 and press Enter.

IMPORTANT For instructions on configuring the IP Address of the CAP-1000, refer to section, “Configuring Network
Parameters for Initial System Access,” on page 30.

3 If a Security Alert window opens, click Yes to proceed.

The CAP-1000 Start Page opens.

CherryPicker Element Manager Start

4 If JRE 1.6 is not installed on your client, do the following:

a Click Download Java Applications to download the Java Runtime Environment and Java
Web Start installation files.
b Download the file.
c Run the file.
5 In the License agreement window, do the following:
a Select the View License Agreement.
b Click Close.
c Click Install.
d When you see the message, “You have successfully installed Java,” click Close.
6 Restart your computer to enable the changes to take effect.

CAP-1000 Software Guide v4.0 37

Chapter 3 Getting Started Starting the CherryPicker Element Manager for the First Time

7 After your system reboots, log in and open a web browser.

8 In the Address field, enter the CAP-1000 IP address and press Enter.
The CAP-1000 Start Page opens.

CherryPicker Element Manager Start

9 Click Start CAP Element Manager.

10 If a Security Warning window opens, click Yes to proceed.
The Login window opens.

CherryPicker Application Platform Login

11 To log in to the CherryPicker Element Manager, refer to section, “Logging on to the

CherryPicker Element Manager,” on page 39.

38 ARRIS Enterprises, Inc.

 Logging on to the CherryPicker Element Manager

Logging on to the CherryPicker Element Manager

To log on:
1 Do one of the following:
• If you are logging in for the first time, enter the CAP IP Address in the field.
• If you have previously logged in, select the CAP-1000 IP address from the menu.

CherryPicker Application Platform Login

2 Enter your User Name and Password.

IMPORTANT The default login user name is Admin with no password.

3 Click Go.
The CherryPicker Element Manager opens in the default view.

CAP-1000 Software Guide v4.0 39

Chapter 3 Getting Started Logging off the CherryPicker Element Manager

Device

Logging off the CherryPicker Element Manager

The Logout function disconnects the CherryPicker Element Manager from the CAP-1000, but
leaves the software running on the CAP-1000. It is accessible from any tab in the CherryPicker
Element Manager. Be sure to save any parameters that you changed using the Apply button before
exiting the system.

To log out:
 In the menu bar at the top of the window, click Logout.

40 ARRIS Enterprises, Inc.

 Logging off the CherryPicker Element Manager

CherryPicker Element Manager—Logout

CAP-1000 Software Guide v4.0 41

Chapter 3 Getting Started Logging off the CherryPicker Element Manager

42 ARRIS Enterprises, Inc.

 CHAPTER 4
CherryPicker Element Manager

In This Chapter
• CherryPicker Element Manager
• Setup
• Content Picking
• Triggers
• Alarms
• Analysis
• Editing Operations

CherryPicker Element Manager

The CherryPicker Element Manager is a browser-based interface that enables you to remotely
configure, control, and monitor each CAP-1000 unit in your network.
The menu bar, located at the top of the window, provides information about the CherryPicker
Element Manager. The system panel lets you show a graphic representing the front and back CAP
configurations. The navigation tabs provide access to different system configuration, control, and
monitoring capabilities of the CAP-1000 system.
Content related to the selected tab appears in one or more panels below the navigation bar via
configuration tabs. The Status bar, located at the bottom of the window, provides up-to-date status
information on the CAP-1000 system.

CAP-1000 Software Guide v4.0 43

Chapter 4 CherryPicker Element Manager CherryPicker Element Manager

Title bar
Menu bar
Navigation tabs

Back/Front view

Configuration tabs

Status bar

CherryPicker Element Manager Components

Title Bar
The title bar, at the top of the window, shows the application name, the device IP address, and the
login user name.

Menu Bar
The menu bar, located at the top of the CherryPicker Element Manager, lets you access basic
functions.

Table 4-1 Menu Bar

Device Shows the currently selected device.

User Shows the name of the user logged in to the CAP-1000.

Groups Opens the Single GUI Centralized Management (SGCM) Groups dialog box.

Logs Provides different log and configuration files for TAC.

Help Provides information on how to access the PDF version of this guide to obtain help.

About Displays the software version information and license agreement.

Logout Logs off the CherryPicker Element Manager. When Logout is clicked, the main window closes
and the Login dialog opens.

44 ARRIS Enterprises, Inc.

 CherryPicker Element Manager

Navigation Tabs
Five navigation tabs provide access to the system configuration, control, and monitoring
capabilities of the CAP-1000.

Table 4-2 Navigation Tabs

Setup Configures the system (device, security, network, ASI ports, and recoders); configures Gigabit
Ethernet ports; manages product licenses; assigns permissions; and applies configuration files
to the CAP-1000.

Triggers Configures scheduled events in grooming operations. A scheduled event is a time-based event
generated as a single or reoccurring event.

Content Picking Configures multiplexes; grooms programs, elementary streams, and files; assigns recoders;
manages DPI; and configures program-level redundancy.

Alarms Lists, customizes, and manages CAP-1000 alarms.

Analysis Shows video and program analysis data in real time.

Status Bar
The status bar, located at the bottom of the CherryPicker Element Manager, provides real-time
status on the device.

Table 4-3 Status Bar

Critical An alarm that indicates that the system is unable to continue functioning (failure of
output card, loss of time reference signal at output, etc.). The total number of critical
alarms is shown. Clicking the alarm causes the Alarms window to open. See
Chapter 35, “Managing Alarms and Logs” for more information.
Major An alarm that indicates that major functionality has failed (one of the two I/O cards
failed or ad insertion is down while other functions are OK). The total number of major
alarms is shown. Clicking the alarm causes the Alarms window to open.

Minor An alarm that indicates that minor functionality may produce intermittent errors.
(number of spliced frames in ad insertion is not equal to requested number). The total
number of minor alarms is shown. Clicking the alarm causes the Alarms window to
open.

Input Mux Shows the number of active and inactive input multiplexes for this CAP-1000. See
Chapter 14, “Configuring Multiplexes” for more information.
Output Mux Shows the number of output multiplexes for this CAP-1000.

Groomed Programs Shows the number of groomed programs for this CAP-1000. See Chapter 17,
“Grooming Concepts” for more information.
CPR Indicates if this CAP-1000 is configured for CPR. The modes are: Independent,
Primary, Backup 1:1, or Backup N:1. See Chapter 27, “Configuring
CherryPicker Redundancy” for more information.

CAP-1000 Software Guide v4.0 45

Chapter 4 CherryPicker Element Manager Setup

Table 4-3 Status Bar (continued)

Date/Time/Zone Shows the date, time, and time zone for the specified location. See Chapter 6,
“Configuring the CAP-1000 Device” for more information.
Primary Indicates the CAP-1000 is operating in primary mode when configured for PRED. See
Chapter 29, “Configuring Program Redundancy” for more information.
Backup Indicates the CAP-1000 is operating in backup mode when configured for PRED.

HTTP Indicates the CAP-1000 is configured for HTTP communication.

HTTPS Indicates the CAP-1000 is configured for HTTPS communication. When HTTPS is
configured, users are required to accept the certificate issued by the Certificate
Authority before logging in to the CherryPicker Element Manager. See Chapter 9,
“Configuring Security” for more information.
Database Shows the status of the database on the Primary CAP-1000 in a CPR configuration.
Tool tips are provided to synchronize the database, if needed. See
section,“Synchronizing the Database,”on page 564 for information

Setup
The Setup window, which is accessed by clicking the Setup tab in the CherryPicker Element
Manager, lets you set up and configure the CAP-1000 device using the following sub tabs:
• System
• Licenses
• Permissions
• Redundancy
• Files

46 ARRIS Enterprises, Inc.

 Setup

Setup

System
Clicking Setup > System provides access to system-wide configuration functions for the
following components:
• Device
• GigE Network
• ASI
• Hardware
• Recoders
• Device Control

CAP-1000 Software Guide v4.0 47

Chapter 4 CherryPicker Element Manager Setup

System

Using this window, you can perform the following tasks:

• Identify the hardware components.
• View the system configuration.
• Configure secure communications and authentication.
• View the network configuration.
• Manage NTP servers.
• Configure static routes.
• View ASI port configuration.
• View, configure, and manage recoder use for optimal allocation.
• Reboot, restart, and disconnect the CAP-1000.
See Chapter 5, “CAP-1000 System Components” for more information.

48 ARRIS Enterprises, Inc.

 Setup

Licenses
Clicking Setup > Licenses displays the License window which lets you perform the following
tasks:
• View product licenses by type.
• Determine the total number of licenses in use, available licenses, and the expiration date.
• Enter license keys to enable functions or features of the CAP-1000.

Licenses

See Chapter 8, “Managing Licenses” for more information.

Permissions
Clicking Setup > Permissions displays the Permissions window which lets you perform the
following tasks:
• Control user accounts and permissions.
• Enable or disable user access to specific functions or features.
• Add or delete users.
• Manage user passwords.

CAP-1000 Software Guide v4.0 49

Chapter 4 CherryPicker Element Manager Setup

Permissions

See Chapter 10, “Managing Permissions” for more information.

Redundancy
Clicking Setup > Redundancy displays the Redundancy window, which lets you configure
redundancy options for the CAP-1000.

Redundancy

The different types of redundancy supported for the CAP-1000 are described in Table 4-4 on
page 51.

50 ARRIS Enterprises, Inc.

 Setup

Table 4-4 Redundancy Options

CherryPicker Redundancy (CPR) Enables a Backup CAP-1000 to replace a Primary CAP-1000 when the Primary
CAP-1000 fails. Two modes are supported: Backup 1:1 mode and Backup N:1
mode. In Backup 1:1 mode, a Backup CAP-1000 protects a single Primary CAP-
1000. In Backup N:1 mode, a Backup device protects one or more Primary CAP-
1000 devices.

Multiplex Redundancy (MRED) Enables program redundancy at the output multiplex level. When the source
for a single groomed program fails on a GigE or DVB-ASI output multiplex with
MRED enabled, all programs from the source multiplex are switched from the
Primary to the backup input multiplex. See Chapter 28, “Configuring
Multiplex Redundancy” for information.
Program Redundancy (PRED) Enables a backup program to replace an input program when a groomed input
program fails. PRED can be used in conjunction with CPR. For example, PRED
recovers from input stream failures, while CPR recovers from CAP-1000 and
local link failures.
Note: Redundancy settings at the program level are not configurable when
MRED is enabled for program grooming. See Chapter 29, “Configuring
Program Redundancy” for information.
Slates A slate can be defined at the device-level, multiplex level, or program level.
When defined at the device level, the second-level slate is active for every
output program of the device. When defined at the device or multiplex level,
two different file names are requested for two different video slate file
formats. A backup program can also have another program designated as the
slate program for a second-level backup. See Chapter 30, “Configuring
Slate Redundancy” for information
Ad Insertion Protection (AIP) Enables protection for unicast ad insertion input feeds. AIP can be used in
conjunction with PRED and output mux mirroring to provide link redundancy for
ad insertion. See Chapter 31, “Configuring Ad Insertion
Protection” for information.
Output Port Redundancy Mirroring is independent of CPR, but it can coexist with CPR to provide high
(Mirroring) availability for the CAP-1000. See Chapter 32, “Configuring Port
Mirroring” for information.

Files
Configuration files establish the configuration of the CAP-1000 lines (ports) and multiplexes.
Clicking Setup > Files displays the Files window which lets you perform the following tasks:
• View and update device-level, line-level, and multiplex-level XML configuration files
• View sample XML configuration files
• Import and export XML configuration files for device, line, and multiplex
• Back up and restore XML configuration files for device to or from a local PC
• Extract slate files from Single Program Transport Streams
• Upload slate files (M2V)

CAP-1000 Software Guide v4.0 51

Chapter 4 CherryPicker Element Manager Triggers

Files

See Chapter 16, “Managing Configuration Files” for more information.

Triggers
The CAP-1000 provides support for scheduled events in grooming operations. A scheduled event
is a time-based event generated as a single or reoccurring event. Clicking Triggers displays the
Triggers window which lets you perform the following tasks:
• Create, update, or delete triggering events.
• View upcoming event instances.
• View action definitions associated with each event.
• Test triggers before using them in a production environment.

Triggers

52 ARRIS Enterprises, Inc.

 Content Picking

Refer to Chapter 21, “Using Trigger Events,”for more information.

Content Picking
The Content Picking window provides access to multiplex configuration and grooming functions.

Mux
Clicking Content Picking > Mux displays the Mux window which lets you perform the following
tasks:
• Configure input and output multiplexes
• Configure MRED
• Import or export configuration files
• View table parameters
• View program parameters
• Configure the Emergency Alert System (EAS)
• Configure the Basic Interoperable Scrambling System (BISS)
• Enable Service Description Tables (SDT) in non-DVB multiplexes

Content Picking—Mux

See Chapter 14, “Configuring Multiplexes” for more information.

CAP-1000 Software Guide v4.0 53

Chapter 4 CherryPicker Element Manager Content Picking

Grooming
Clicking Content Picking > Grooming displays the Grooming window which lets you perform
the following tasks:
• Groom programs, elementary streams, and files by drag-and-drop
• Add, modify, or drop groomed programs, elementary streams, or files
• View grooming definitions, program intervals, and ad insertions
• View alarms for a groom
• Pass elementary stream or table PIDs
• Configure primary and backup streams for PRED
• Configure the CAP-1000 for digital program insertion (DPI)
• Enable closed captioning conversion (CCC)
• Enable Cue Insertion, Enhanced TV Binary Interchange Format (EBIF), and Commercial
Advertisement Loudness Mitigation (CALM) Act

Content Picking—Grooming

See Chapter 17, “Grooming Concepts” for more information.

54 ARRIS Enterprises, Inc.

 Alarms

Alarms
Clicking Alarms displays the Alarms window lets you view and manage alarms and events for
system operations. It provides an Alarms and Settings subtabs that let you view, configure, or
manage CAP-1000 alarms. Using the Alarms window, you can:
• View active alarms.
• Sort, filter, and find events.
• Clear alarms.
• View alarms history.
• Modify alarm settings.

Alarms

See Chapter 35, “Managing Alarms and Logs” for more information.

Analysis
Clicking Analysis displays the Analysis window which lets you perform the following tasks with
regard to streams and programs:
• View color-coded video stream data in current UTC time, including frame rate, frame size, and
average bit rate.
• View program analysis data in current UTC time, including video, audio, and data stream
information.

CAP-1000 Software Guide v4.0 55

Chapter 4 CherryPicker Element Manager Editing Operations

• View bit rates and other information about input and output elementary streams.
• View the recoder efficiency (lossy bit rate reduction over original input rate).
• Determine the aggregate mux rate and total mux rate for selected output multiplex.
• View recoder lossy and lossless reduction.
• View GigE line bit rates.

Analysis

See Chapter 34, “Analyzing Streams and Programs” for more information.

Editing Operations
This section reviews some of the basic editing operations that can be performed in the
CherryPicker Element Manager. Procedures related to specific editing operations are described in
subsequent chapters of this guide.

Applying and Discarding Changes

The Apply and Discard buttons appear in many windows of the CherryPicker Element Manager.
Clicking the Apply button applies changes made to one or more parameters and updates the
Controller. Clicking the Discard button restores all fields to their current values.

56 ARRIS Enterprises, Inc.

 Editing Operations

Apply and Discard Buttons

Depending on the window in which you are working, after clicking the Apply or Discard button, a
pop-up window asking you to confirm or cancel your selection displays.

Change Alert

Editing Parameters
Tables are used throughout the CherryPicker Element Manager to display parameters and other
information. Cells highlighted in teal represent content that you can edit. Gray color cells indicate
content that is not applicable to the selected parameter. Cells with a white background color
indicate read-only status.

CAP-1000 Software Guide v4.0 57

Chapter 4 CherryPicker Element Manager Editing Operations

Editing Parameters

Typically, you make changes to a table by editing the content in a cell or selecting a command
from a pop-up menu. When you edit content in a table, the status column for the selected item
displays an “Edit” icon. When you mark an item for deletion, the status column displays a
“Delete” icon.

Parameter Edited, Not Applied

58 ARRIS Enterprises, Inc.

 Editing Operations

Refer to Table 4-5 for a description of the icons.

Table 4-5 Edit Parameter Icons

Parameter has been edited, but modifications have not been applied.

Parameter has been marked for deletion, but the deletion has not been applied.

After applying or discarding the changes and confirming your choice, the icons are removed and
status column clears.

Sorting Data
You can sort columns in the tables by double clicking the column header. When sorting is
performed, the column header shows a triangle that represents the sorting direction.

Column Sorting

Locked Columns
The locked columns feature automatically “locks” panes to keep row and column labels visible as
you scroll, while rows or columns in the non-scrolled area remain visible. For example, the first
three columns of the Network panel remain “locked” on the left side when scrolling through
columns of information.

CAP-1000 Software Guide v4.0 59

Chapter 4 CherryPicker Element Manager Editing Operations

Locked Column

Hide Columns
Under the Network tab, a small icon on the far right of the window lets you hide table columns.

Show/Hide Columns

60 ARRIS Enterprises, Inc.

 Editing Operations

Filtering
Filtering is supported in the following windows of the CherryPicker Element Manager:
• Content Picking/Multiplex window
• Content Picking/Grooming tab
• Select Output Multiplex dialog
• Analysis window

Filter Button

The Filter button lets you filter the Component Tree based on a keyword. You filter the
Component Tree nodes using one or more input key words separated with spaces. If more than one
keyword has spaces, then use double quotes (“HBO One,” “HBO Two”). Nodes that match any of
key words are shown in the panel.

Managing Errors
When errors occur after an action, a dialog box opens and shows specific information regarding
each “failed” operation.

Errors

CAP-1000 Software Guide v4.0 61

Chapter 4 CherryPicker Element Manager Editing Operations

Error messages often guide you to the required resolution. For certain errors, additional
information can be obtained by clicking the underlined message text. Another dialog appears with
stack traces regarding this error. Errors must be corrected before an action can be applied.

Progress Indicator
It is common to observe some delay before an editing operation is complete with bulk operations.
As such, a progress bar displays after clicking the Apply button to provide some indication on
when the operation has completed.

Progress Indicator

During this time, the CherryPicker Element Manager is not accessible. When the changes have
been applied, the progress meter closes and the GUI is accessible again.

62 ARRIS Enterprises, Inc.

 CHAPTER 5
CAP-1000 System Components

In This Chapter
• System Components
• Software Hierarchy
• Hardware Profile

System Components
The default view of the CherryPicker Element Manager displays the front panel of the CAP-1000
chassis, along with a button for toggling between illustrations of the front and back chassis.

Show Back/
Show Front

CAP-1000 System Components

CAP-1000 Software Guide v4.0 63

Chapter 5 CAP-1000 System Components System Components

You can mouse over any component in the illustration to display its name. A hot spot is identified
with a green box around the selected component. Components that are not present or not
connected are indicated with a cross-hatch graphic in the picture. Clicking the hotspot causes
additional information about the component to display in the bottom panel of the CherryPicker
Element Manager.

CherryPicker Element Manager Hotspot

Hotspots are provided for the following components:

Chassis Front
• Fan trays
• 10G IOA
• Modem port
• GPIO port
• License Guard
• Data Flash
• Ethernet ports
• Power indicator
• Filter assembly
• DSP module

64 ARRIS Enterprises, Inc.

 System Components

• Debug Ethernet port

• Debug serial port

Chassis Rear
• VIO modules
• VIO ports
• Power modules
• AC receptacles

Operating System
The CAP-1000 Software v4.0 runs on Linux 2.6.33.5.

Program Flash
The Operating System and software programs are stored on the Program Flash of the CR-DSP
module. See section,“Digital Signal Processor Module,”on page 135 for more information on the
DSP module.

DSP Module

CAP-1000 Software Guide v4.0 65

Chapter 5 CAP-1000 System Components System Components

Data Flash
The Data Flash is required for proper operation of the CAP-1000. It is accessible from the IOA on
the front of the CAP-1000 and must be installed and present at all times. The Data Flash stores
variable data that is generated during operation of the system. Table 5-1 lists some of the Data
Flash directories.

Table 5-1 Data Flash Directories

Directory Contents

dataroot/Database Database files

dataroot/Log Log files

Security Security files

Data Flash

Missing Data Flash

If the Data Flash is not physically present, the CAP-1000 boots but the Controller does not start
and the CherryPicker Element Manager does not connect to the device. In this case, check for
presence of the Data Flash in the chassis.

Corrupt Data Flash

If the sysconfig file of the Data Flash is corrupted, the Controller runs with the default
configuration. A report is sent to /var/log/messages file. In this case, contact the ARRIS Technical
Assistance Center for help.

66 ARRIS Enterprises, Inc.

 Software Hierarchy

Software Hierarchy
The CAP-1000 software is organized into a hierarchy that provides the structure needed by the file
system to identify components and elements.

Controller
The root of the hierarchy is the Controller. The Controller is the transparent, software subsystem
that performs legacy system functions.
The CherryPicker software assigns an identification number (ID) to the Controller. The Controller
ID number and name represent the host name of the Controller. The host name is assigned based
on the value in sysconfig file.

Farmer
Each CherryPicker device includes one farmer. A farmer is a software subsystem that performs
functions specific to all the CherryPicker Devices. There can be only one farmer per CAP-1000
unit. One farmer is created on the CAP-1000 device when the software is launched. By default, the
name, “CherryPicker Manager” is assigned to a farmer. This name is used to match the “Splicer
Name” sent by an ad server. You can change the default name to suit your needs.

Splicer Name

CAP-1000 Software Guide v4.0 67

Chapter 5 CAP-1000 System Components Software Hierarchy

Ports
A CAP-1000 device contains a number of physical inputs (input ports) and physical outputs
(output ports) provided on DVB-ASI Video Input/Output (VIO) cards or the device Gigabit
Ethernet ports. The CAP-1000 can have up to two VIO cards on the rear panel. The VIO card is a
serial digital video interface. It has four BNC connectors supporting Serial Digital Video data.
Each BNC connector can be configured to support input or output traffic. VIO cards are optional
in the CAP-1000.
The CAP-1000 can operate without any cards, with one card, or with a maximum of two VIO
cards plugged into the device. Each port on the VIO card can be configured to be either a DVB-
ASI input or output. By default, all ports are configured as inputs.
Gigabit Ethernet ports can be viewed and configured in the Setup > System > Network window.

Network GigE Ports

The 10G IOA replaces the 1G IOA and now ships as the standard configuration on new systems.
The 10G IOA supports the following:
• Four Small Form Factor Pluggable (SFP+) cages for either 10-Gbps Ethernet (SFP+)
transceivers (copper or fiber) or 1-Gbps Ethernet (SFP) transceivers (fiber)
• Four Small Form Factor Pluggable (SFP) cages for 1-Gbps transceivers (copper or fiber)
• Two 10/100/1000 Base-T Ethernet ports (copper)
All of the ports come with auto negotiation and full-duplex support. Any of the ten ports can carry
MPEG traffic, manage the ports or handle both functions simultaneously.

68 ARRIS Enterprises, Inc.

 Software Hierarchy

NOTE The 10G IOA does not work with software versions prior to 3.3. With software versions 3.3 or above, the
10G IOA is backward compatible with all prior versions of CAP-1000 hardware and all deployed License
Guards and Data Flashes.

See Chapter 11, “Configuring the Network,” for more information.

ASI ports can be viewed and configured in the Setup > System > ASI window.

ASI Ports

For complete information on ASI ports, see Chapter 12, “Configuring ASI Ports”

Port Modes
A port is either Active or Not Responding. When a port is enabled, its parameters can be
configured, it can send data, and it can receive data. A port can be enabled or disabled manually.
Ports can be enabled as outputs only if a valid license is present.

Port Labels
The CherryPicker software assigns a default name to the input and output ports so operators can
easily identify a particular port by its label. The default name uses the following format:
<slot>/<port>, where <slot> is the slot label, namely 3 and 4, as seen on the VIO card on the back
of the device, and <port> is the port number, i.e., 1, 2, 3, etc.
The numbering scheme applies to all of the interfaces of the CAP-1000 device, starting from front
to back, top to bottom, and left to right.
The scheme does not apply to the service ports that are specifically labeled S1 and S2. The IOA on
the front is slot 1. The DSP is slot 2 and that only Management traffic is allowed on that port. The
serial port is behind a cover plate.

CAP-1000 Software Guide v4.0 69

Chapter 5 CAP-1000 System Components Software Hierarchy

Content Picking—Ports

You can view and modify port labels in the Grooming or Mux tabs in the Content Picking
window.

IP Ports
Table 5-2 lists the IP ports essential to the operation of the Cherrypicker Application Platform.

Table 5-2 IP Ports

Port Number Protocol Description Comments

21 TCP FTP server

22 TCP SSH and SFTP Secure log in

23 TCP Telnet Insecure log in

80 & 8080 TCP HTTP Insecure GUI

443 & 8443 TCP HTTPS Secure GUI

123 UDP NTP

161 UDP SNMP request/response User configurable

162 UDP SNMP trap User configurable (outbound only)

514 UDP Syslog EBIF reporting (outbound only)

70 ARRIS Enterprises, Inc.

 Software Hierarchy

Table 5-2 IP Ports (continued)

520 UDP RIP Outbound only

1812 UDP RADIUS authentication User configurable

1813 UDP RADIUS accounting User configurable

5168 & 6021 TCP SCTE-30/35 For Ad Insertion

6000 UDP CPR Health Monitor Heartbeat exchange

Multiplexes
A multiplex is a software component that combines elementary streams on a single medium and
enables the sharing of these resources for more efficient bandwidth allocation. Each input and
output port on the CAP-1000 may contain multiplexes.
The CherryPicker software assigns an ID to a multiplex. This ID is used as the default name. You
can enter a custom multiplex name when creating input or output multiplexes. Support for bulk
operations is also provided.
Whenever an output port is MPEG enabled, a multiplex may be defined for it. You create a
multiplex through the Content Picking > Mux window. Click the Create Output Mux button
and then apply a configuration file. When applying configuration file, the Program Association
Table (PAT) and Program Map Tables (PMTs) are created for the programs in this multiplex.

Content Picking—Multiplexes

See Chapter 14, “Configuring Multiplexes” for more information.

CAP-1000 Software Guide v4.0 71

Chapter 5 CAP-1000 System Components Hardware Profile

Tables and Programs

Each multiplex consists of tables and programs or services. The tables include the common PSI/SI
tables, as well as other multiplex-wide tables, as defined in the compression systems supported by
the CAP-1000. A program is a combination of elementary streams (such as video and audio) that
compose a media program (such as a television program). All the packets in a program stream
must share the same time reference System Time Clock (STC).
Each program consists of elementary streams, including MPEG-4/AVC video (SD or HD),
MPEG-2 video (SD or HD), audio (MPEG, Dolby Digital or AAC), and private data streams. The
CherryPicker software assigns an identification number (ID) to a program in order to associate the
program and its various attributes. The default name of a program is < line-name >_<program
ID>, for example, “1/4_14”. You can also assign a name to an output program.
You can view programs and elementary streams in the Content Picking > Mux, and groom them
in the Content Picking > Grooming.

Content Picking—Tables and Programs

Hardware Profile
This Hardware tab shows two panels: Hardware Information and SFP Information. The Hardware
Information panel displays the board name, serial number, printed circuit board (PCB) type, and
PCB revision for each board. The corresponding row in the table is highlighted when the front
panel or rear panel components are clicked. When a component is not installed in the chassis, the
hotspot label displays “Not Present” or “Not Connected” in the GUI.
The SFP Information panels shows detailed information about each small form-factor pluggable
(SFP) or SFP+ modules. The SFP is a hot-swappable, input/output module that plugs into a switch
port and supports multiple options for connectivity.
 From the CherryPicker Element Manager, click Setup > System > Hardware.

72 ARRIS Enterprises, Inc.

 Hardware Profile

Hardware Information

Table 5-3 Hardware Information

Hardware Profile

Slot Shows the slot number in which the module is installed.

Board Name Shows the module name.

Serial Number Shows the module serial number.

Type Identifies the PCB type.

Revision Identifies the revision version of the module.

SFP Information

ID Cage position from left to right.

Part Number Manufacturer’s SFP part number.

Vendor Manufacturer

Misc. Wavelength (e.g. 850nm) or twinax.

Qualified “YES” for ARRIS parts.

NOTE The CAP-1000 does not display SFP information for “legacy” IOA modules. Therefore, the SFP
Information pane will be empty for older IOA modules. The message, “A non-qualified SFP is discovered
for this port,” displays.

CAP-1000 Software Guide v4.0 73

Chapter 5 CAP-1000 System Components Hardware Profile

Even though there are more types of SFPs available for the 10G IOA, the CherryPicker Element
Manager only shows the following image whenever an SFP is plugged into first eight ports. The
SPF Information panel and tool tips inform you about the different types of SFPs that are installed
in the system.
For Ethernet connectors, if the cage is empty, a tool tip displays only the port ID such as, “Ethernet
Port 1/3.” When an SFP is plugged in, a tool tip displays all information about the selected SFP.

SFP

74 ARRIS Enterprises, Inc.

 CHAPTER 6
Configuring the CAP-1000 Device

In This Chapter
• Viewing Device Configuration
• Setting the Device Time Format and Zone
• Renaming the CAP-1000 as a Splicer
• Managing NTP Servers
• Setting the Injected BISS Identifier

Viewing Device Configuration

To view device configuration:
 From the CherryPicker Element Manager, click Setup > System > Device.

Device Parameters

CAP-1000 Software Guide v4.0 75

Chapter 6 Configuring the CAP-1000 Device Viewing Device Configuration

Table 6-1 Device Parameters

Name Shows the name of the Controller (which is the Linux hostname of the system). This
name cannot be changed by the user, except by changing the hostname.

Mode Indicates that the CAP-1000 platform is performing in Independent, Primary, Backup
1:1, or Backup N:1 mode. Setting the mode to something other than Independent is
configuring a CAP-1000 for CPR. Primary mode is not available without a CPR
license.

Version Shows the software version currently running.

Model Shows the CAP-1000 model.

RAM (MB) Shows the installed RAM (memory) on the device.

Splicer Name Shows the name of the CherryPicker function as a Splicer.

Time Format Shows the time format configured for the CAP-1000: 12-hour or 24-hour.

Time Zone Shows the time zone used for the CAP-1000.

Data Flash Size (MB) Shows the size of the Data Flash in megabytes.

Data Flash Utilization (%) Shows the percentage of the Data Flash that is currently in use.

Data Flash Threshold (%) Generates an alarm upon utilization.

License Guard Serial Number Shows the License Guard serial number for the system.

Injected BISS Identifier Shows a hexadecimal string that is entered (injected) into the Basic Interoperable
Scrambling System (BISS) unit by the Administrator. See section,“Basic
Interoperable Scrambling System (BISS),”on page 231 for more
information.

EBIF Enables EBIF at the output program level when the required license key is installed.
See Chapter 26, “Managing EBIF,” for more information.

Security Configures a secure connection. See section,“Configuring Access,”on

page 116 for more information
SNMP Manages the SNMP configuration. See section,“Using SNMP to Monitor
CAP-1000 Devices,”on page 95 for more information.
Path SDT Enables device tracking for all input programs. See section,“Managing Path
SDT,”on page 294 for information.

76 ARRIS Enterprises, Inc.

 Setting the Device Time Format and Zone

Setting the Device Time Format and Zone

To set the time format and zone:
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Double-click the Time Format field, select the option you want from the menu: 12 Hour or 24
Hour.

Time Format

3 Double-click the Time Zone field, select the option you want from the menu.

Renaming the CAP-1000 as a Splicer

The CAP-1000 is provided with a default name. If you perform ad insertion in your environment,
you must rename the CAP-1000 to use it as a splicer.

To rename a CAP-1000:
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Double-click the Splicer Name field and enter the name you want.

CAP-1000 Software Guide v4.0 77

Chapter 6 Configuring the CAP-1000 Device Managing NTP Servers

Splicer Name

Managing NTP Servers

The CAP-1000 allows synchronization from external Network Time Protocol (NTP) servers.
Typical NTP configurations utilize multiple redundant servers and diverse network paths to
achieve high accuracy and reliability. CAP-1000 supports up to five NTP servers.
When multiple servers are configured, the CherryPicker automatically selects the best time source
to synchronize. The software monitors the NTP sources to see how much drift is present between
the CAP-1000 clock and the NTP sources. If the NTP clock is significantly off (more than 15
milliseconds), a jitter alarm is raised.
Also note that time differences with connected ad servers are monitored. If the NTP clock is
significantly off (more than 15 milliseconds), a jitter alarm is raised. The IP address of the ad
server that has gone out of sync is displayed in an error message. The alarm automatically clears
when synchronization is restored.

Adding NTP Servers

To add an NTP server:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Under NTP Server IP Address, click Add.

78 ARRIS Enterprises, Inc.

 Managing NTP Servers

NTP Servers

3 Enter the IP Address of the NTP server.

4 Click Apply.
A warning message appears.

Warning

5 Click OK.

Synchronizing NTP Servers

To synchronize an NTP server:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Under NTP Server IP Address, click Sync.
A confirmation window opens.
3 Click OK.
An information window opens.

CAP-1000 Software Guide v4.0 79

Chapter 6 Configuring the CAP-1000 Device Setting the Injected BISS Identifier

4 Click OK.
If a server is found that is suitable for synchronization, the CAP-1000 is synchronized to this NTP
server. If multiple servers are found, the CAP-1000 selects the best time source with which to
synchronize.

NOTE The NTP server that is currently synchronized has a star (*) symbol next to the server IP address.

Deleting NTP Servers

To delete an NTP server:

1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Under NTP Server IP Address, do one of the following:
• To delete one NTP server, select the server and click Delete.
• To delete all NTP servers, click Delete All.
3 Click Apply.
A confirmation window opens.
4 Click OK.
5 Click Close.

Setting the Injected BISS Identifier

The CAP-1000 supports BISS for systems with a CR-DSP module. This feature provides
encryption/decryption capabilities on the CAP-1000 platform to protect transmissions by using a
“session word” established by the transmitting and receiving parties prior to transmission.
The session word is entered into both the encoder and decoder for a specific mux. This session
word then forms part of the encryption of the digital TV signal and only receivers with the correct
word can decrypt the signal. The CAP-1000 can decrypt input MPTS or SPTS and encrypt output
MPTS or SPTS. BISS is enabled in the Mux panel of the Content Picking window.
A session word can be a provided in the “clear,” in which case, it is a 12-digit hexadecimal string.
A session word can also be encrypted. In this case, it is a 16-digit hexadecimal string. When an
encrypted session word is used, the injected BISS ID is the decryption key.
The injected BISS ID is a secret key embedded at the device level. Only users with Config
permissions can enter the injected ID. The injected ID must be defined before an encrypted session
word can be defined for any mux.
A BISS license is required for entering injected identifier. The CAP-1000 does not support a
supplier’s buried identifier. See section,“Basic Interoperable Scrambling System (BISS),”on
page 231 for more information.

80 ARRIS Enterprises, Inc.

 Setting the Injected BISS Identifier

To set the Injected ID:

1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Click the Injected BISS Identifier field.

Injected BISS Identifier

3 In the pop-up window, enter the hexadecimal string that will be injected into the BISS unit. The
injected ID is mandatory to operate Mode E BISS.
4 Click OK.
The encrypted keyword show as asterisks (*) in the field.

CAP-1000 Software Guide v4.0 81

Chapter 6 Configuring the CAP-1000 Device Setting the Injected BISS Identifier

82 ARRIS Enterprises, Inc.

 CHAPTER 7
Controlling and Upgrading the
CAP-1000 Device
In This Chapter
• Device Control
• Rebooting System Software
• Restarting the Controller
• Restarting the Core
• Refreshing Program Headers
• Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices
• Using SNMP to Monitor CAP-1000 Devices
• Upgrading the Software
• Configuring GARP for CherryPicker Redundancy (CPR)

Device Control
The Device Control window is divided into two parts: Device Control and Software Update. The
Device Control part lets you restart the Controller and Core. The Controller is a Java process that
runs between the CherryPicker Element Manager interface and the Core. It manages program
scheduling and grooming. The Core is a software component that manages the “traffic” for input
and output streams. The CAP device is the CherryPicker Application Platform.
The Software Update part lets you update the software on the selected CAP-1000. You can also
view records for Update Status and Update History so you can track the result of an update.

CAP-1000 Software Guide v4.0 83

Chapter 7 Controlling and Upgrading the CAP-1000 Device Device Control

Device Control

Table 7-1 describes different options that are available for controlling the CAP-1000.

Table 7-1 Device Control

Device Control

Reboot Reboots the entire system which shuts down the Core, the Controller, processes,
and the Linux kernel. If a backup CAP-1000 has been configured, you have the
option to reboot to the backup device. See Chapter 27, “Configuring
CherryPicker Redundancy” for more information.
• Reboots cause interruption to output services for 1–2 minutes.
• After a reboot, alarms are recorded in the alarm log (alarm.log).
• Rebooting automatically triggers the database file (dbase.base) to be saved.
• During a reboot, the CAP-1000 does not output data on any port.
Reboots are necessary in the following circumstances:
• After updating software (required)
• During troubleshooting (as needed)
Reboots may also be used to accomplish any of the tasks that require a restart.
Note: This function is comparable to the Telnet “reboot” command.

Restart Controller Stops the Controller, logs you out, and then restarts the Controller. When the
Controller stops, Digital Program Insertion (DPI) is interrupted. The alarms are
recorded in the alarm log (alarm.log). This function can be used for troubleshooting
(as needed). Wait approximately 30 seconds before attempting to log in again.
When the Controller restarts, you are asked to log in again.
Note: This function is comparable to the Telnet “restartfarmer” command.

84 ARRIS Enterprises, Inc.

 Device Control

Table 7-1 Device Control (continued)

Restart Core Stops the Core, interrupts services, and then restarts the Core. You stay logged in
during this process. When the Core restarts, the Controller initializes the device,
and then sends grooming and other configuration settings that existed prior to the
restart to the CAP device. The CAP-1000 is not responsive until the Core restarts.
Core restarts are used during troubleshooting, as needed.
Note: This function is comparable to the Telnet “restartcore” command.

Refresh Refreshes the input stream descriptions. It updates synchronous/asynchronous

status, HD/SD status, and encrypted icon status with the current state. Refreshes
take 15-20 seconds to complete and may or may not interrupt output services.

Software Update

Update Server Selects a remote or local server to update. If more than one remote server is
available, use the IP Address field to select the server you want.

Update Source Directory Selects the source directory where the software build is saved.

Update Status Shows the status of the current software update.

Update History Shows the history of past software updates.

NOTE The CherryPicker software preserves the settings of the CAP-1000 device after a reboot, restart, warm boot,
farmer restart, or a Core restart, unless specified otherwise.

Planned System Reboot and Shutdown

A planned CAP-1000 reboot does not cause any loss of information, device configuration, or
grooming configuration.

Unexpected System Shutdown

An unexpected shutdown can be caused by turning off the power supply on the CAP-1000. The
CAP-1000 saves the database on a three-minute cycle. A power loss causes a loss of the device or
grooming configuration if it occurs within the three-minute window. An unexpected CAP-1000
shutdown does not cause any loss of information, device configuration, or grooming configuration
if no changes have occurred within the last three minutes.

NOTE You can also back up or restore the database. See section,“Backing Up and Restoring the Database,”on
page 320 for information.

CAP-1000 Software Guide v4.0 85

Chapter 7 Controlling and Upgrading the CAP-1000 Device Rebooting System Software

Rebooting System Software

To reboot:
1 From the CherryPicker Element Manager, click Setup > System > Device Control.
2 Click Reboot.
A confirmation window opens.

IMPORTANT If the CAP-1000 is a protected primary device in a CPR configuration, a window opens and asks for
confirmation to fail over to the backup CAP-1000. See section,“CherryPicker Redundancy,”on page 548
for more information.

3 Click OK.
You are logged off immediately.

Restarting the Controller

To restart:
1 From the CherryPicker Element Manager, click Setup > System > Device Control.
2 Click Restart Controller.
A confirmation window opens.
3 Click OK.
You are logged off immediately.

Restarting the Core

To restart:
1 From the CherryPicker Element Manager, click Setup > System > Device Control.
2 Click Restart Core.
A confirmation window opens.
3 Click Yes.
The Core software is restarted.

86 ARRIS Enterprises, Inc.

 Refreshing Program Headers

Refreshing Program Headers

To refresh:
1 From the CherryPicker Element Manager, click Setup > System > Device Control.
2 Click Refresh.

Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

This section explains how to use the Single GUI Centralized Management (SGCM) feature to
manage a group of CAP-1000s or AGB240 devices. Using the CherryPicker Element Manager,
you can control up to two AGB240 units per CAP-1000 device. You can also manage multiple
CAP-1000 devices.

NOTE The GUI supports AGB240 Release 1.2.3

Managed Groups
The collection of devices managed by the CherryPicker Element Manager is called a managed
group. Information about the group is stored on the client machine. You can create managed
groups and manage all the devices in a group from a single CherryPicker Element Manager.
Once configured, the CherryPicker Element Manager indicates the name of the managed group to
which it is connected in the window title bar. After logging in to a managed group, you can switch
between devices by selecting the device IP/name combination in the SGCM Device menu. Once
selected, you can perform regular operations related to the device.
Several instances of the CherryPicker Element Manager can run on a remote host at the same time,
each of which can control one or multiple CAP-1000 or AGB240 devices. A maximum of ten
devices can be controlled by a single GUI instance. In the case of a single GUI instance controlling
a single device, the RAM usage for the GUI cannot exceed 300 MB. In the case of a single GUI
instance controlling multiple devices, the RAM usage for the GUI cannot exceed 350 MB.

Constraints
The following constraints apply to managed groups.
• CAP-1000 devices and AGB240 devices can be in different managed groups.
• A managed group is a collection of CAP-1000 or a separate collection of AGB240 devices. A
group member is a single device. A managed group is associated with a remote host. A host
may have several managed groups.
• A single instance of the GUI can control multiple CAP-1000 or a separate collection of
AGB240 devices. The term “instance” refers to a process running on a host computer.
• Each managed group for a particular host must have a unique group name associated with the
group.

CAP-1000 Software Guide v4.0 87

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

• Each device in a managed group must have a user with the same user name, password, and
access options (HTTP vs. HTTPS) as defined for the group.
• A managed group must have at least one group member.
• One device may belong to several managed groups. Managed group members are identified by
their IP addresses.
• All devices in a managed group must run the same version of software; however, a single
device can run different patches corresponding to the same software version.
• Each GUI instance controlling one or multiple devices runs in a single window.
• Software upgrades must be done separately for each member of a managed group.
• If a configuration file residing on a device in a managed group is edited, then the modified file
can be stored only on the device from which it came.

AGB240 Devices
When connected to an AGB240 device, the CherryPicker Element Manager provides support for
the following AGB240 controls:
• Configure the AGB240 device
• View status information
• Retrieve status and event logs
• Upload new firmware to the AGB240
• Provisioning the device

UTC Time
The UTC time displayed in the CherryPicker Element Manager corresponds to the UTC time of
the CAP-1000 or AGB240 device that is controlled by it.

Creating Managed Groups

To create a managed group:

1 From the CherryPicker Element Manager, click Groups in the menu bar.

NOTE Example illustrations show the CAP-1000 device.

88 ARRIS Enterprises, Inc.

 Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

Groups

The SGCM Group Dialog opens.

SGCM Group

2 To add a group, do the following:

a Click Add Group.
A group, CAP_GROUP_0 is added to the Groups column.

CAP-1000 Software Guide v4.0 89

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

SGCM Group

b Click Apply.
c Repeat steps for each group you want to add.
3 To add members to the group, do the following:
a Under Groups, select the group you want.
b Under Group Members, click Add Member.

SGCM Group

c Double-click the IP Address field and enter the IP address for the CAP-1000.
d Click Apply.
e Repeat steps for each member you want to add to the managed group.

90 ARRIS Enterprises, Inc.

 Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

4 Click Close.

Deleting Managed Groups

To delete a managed group:

1 From the CherryPicker Element Manager, click Groups in the menu bar.
The SGCM Group Dialog opens.

SGCM Group

2 To delete a group, do the following:

a Under Groups, select the group you want.
b Click Delete Group.
All members of the group are also deleted.
3 To delete a group member, do the following:
a Under Groups, select the group you want.
b Under Group Members, select the member you want and click Delete Member.
4 Click Apply.
5 Click Close.

CAP-1000 Software Guide v4.0 91

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

Exporting Managed Groups

To export a managed group:

1 From the CherryPicker Element Manager, click Groups in the menu bar.
The SGCM Group Dialog opens.
2 Under Groups, select the group(s) you want.

SGCM Group

3 Click Export Groups.

The Save dialog opens.
4 Select a location on your local client to save the .xml file with a name of your choice.
5 Click Save.

Importing Managed Groups

When importing managed groups, the imported groups are merged with the existing groups in the
SGCM Groups dialog.

To import a managed group:

1 From the CherryPicker Element Manager, click Groups in the menu bar.
The SGCM Group Dialog opens.
2 Click Import Groups.
The Open dialog opens.
3 Navigate to the location on your local client where the .xml file is saved.
4 Select the file you want.

92 ARRIS Enterprises, Inc.

 Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

5 Click Open.
6 Click Apply.
7 Click Close.

Connecting to Managed Groups

To connect to a managed group:
1 From the host PC where you run the CherryPicker Element Manager, open a browser.
2 In the Address field, enter the IP address for the CAP-1000 and press Enter.
A Download dialog opens.
3 Click Download and let the download finish.
4 When you see the Login window, select the managed group you want from the IP Address/Group
menu.

CherryPicker Application Platform Login

5 Enter a User Name, Password, and then click Go.

The SCGM Groups window opens. The Connection status (red or green), IP address, Group Name,
and Status (Disconnected or Connected) parameters display.

CAP-1000 Software Guide v4.0 93

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SGCM to Manage Groups of CAP-1000 or AGB240 Devices

SGCM Group

6 To connect to CAP-1000 devices in a group with a Status of Disconnected, select the group and
then click Reconnect Now.
7 Click Show.
The CherryPicker Element Manager launches.

Switching Managed Devices

After you have connected to a managed group, you can switch among managed CAP-1000s or
AGB240 units by selecting the device name in Device menu at the top of the CherryPicker
Element Manager. Devices with a green box are enabled and available to use. Devices with a red
box are not available to use.

Device Menu

94 ARRIS Enterprises, Inc.

 Using SNMP to Monitor CAP-1000 Devices

Using SNMP to Monitor CAP-1000 Devices

The Simple Network Management Protocol (SNMP) is an application–layer protocol defined by
the Internet Architecture Board (IAB) in RFC1157 for exchanging management information
between network devices.
Using the CAP-1000 SNMP Agent, you can monitor CAP-1000 devices in a centralized head-end
environment, track unit operations, and generate traps and alarms. The SNMP Agent is bundled
with the CAP-1000 managed device.
Refer to the CAP-1000 SNMP MIB Reference Guide v4.0 for more information.

SNMP Managers
The CAP-1000 SNMP Agent operates with the following SNMP Managers:
• SNMPc
• AdventNet
• Spectrum

Backward Compatibility
The CAP-1000 MIB provided with software v4.0 is backward compatible with software v2.0 and
v3.0. The CAP-1000 MIB is not backward compatible with the NCP MIB used in legacy devices.

SNMP Support for Fault Management

The CAP-1000 provides SNMP support for fault management as follows:
• Traps are generated for all system restarts, interruptions, rising alarms, and falling alarms.
They contain attributes indicating if the trap is related to a DPI feed.
• An alarm trap contains all information defined for an entry in the alarm log.
• Users can choose the alarms that generate traps as follows:
• Severity filter—The SNMP Minimum Severity Filter controls which alarms generate
SNMP traps. An alarm that is as severe as or more severe than the configured value
generates a trap. An alarm less severe than the configured value does not generate a trap.
By default, the SNMP Minimum Severity Filter is set to Event.
• Alarm code trap filter—A new SNMP Alarm Code Trap Filter lets you filter on all alarm
codes. You can deselect an alarm code to prevent alarms with that code from sending
traps.
• Trap filter combinations—The SNMP trap filters are all combined to give the resulting
filter. An alarm must satisfy all SNMP trap filters to generate a trap.
See Chapter 35, “Managing Alarms and Logs,” for more information.

CAP-1000 Software Guide v4.0 95

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SNMP to Monitor CAP-1000 Devices

Trap Throttling
You can control the maximum rate at which traps are dispatched to a given trap listener. This
function is controlled by two parameters: Max Traps Per Second (Trap Rate in the GUI) and Max
Queue Size (Queue Size in the GUI).
The Max Traps Per Second parameter defines the maximum rate at which traps are sent to the
listener. If the value of this parameter is 0, then Trap Throttling is disabled, and all traps that satisfy
the trap filters for the listener are dispatched to the listener. The default value of Max Traps Per
Second is 0 for backward compatibility.
The Max Queue Size parameter defines the maximum size of the trap queue. One Trap Throttle
Queue exists per trap listener and every trap that passes the trap filters is placed in the queue. The
queue is emptied at a maximum rate of Max Traps Per Second as the traps in the queue are
removed from the queue and sent to the trap listener. If the queue becomes full because alarms
occur at a rate faster than the queue is emptied for a sustained period, then new traps are discarded.
The default value for Max_Queue_Size is 1000.

SNMP Support for Digital Program Insertion

The CAP-1000 generates SNMP traps for every SCTE-35 table that is received on an input SCTE
35 PID. The stream must be a part of an input program that has its video groomed to an output
program that is connected to an ad server.
Only SCTE 35 tables that contain the command “splice insert” will generate alarms and traps. The
other SCTE 35 commands (splice null, bandwidth reservation, time signal, or splice schedule) will
not generate alarms and traps.

Recommended Practices for SNMP Managers

This section lists recommended SNMP programming practices for SNMP Managers to ensure
compatibility with the CAP-1000 MIB.
• Access to an object must be based on the object OID.
• The SNMP Manager should always confirm that the results of the get, get-next, and set
operations return the same OID as was requested. This will prevent the SNMP Manager from
incorrectly interpreting the response if the number of objects or the columns in a table is
different between the SNMP Manager's MIB and the SNMP Agent's MIB.
• The SNMP Manager should be able to handle the obsolete variables and noSuchName error
responses, both of which may indicate that the features are not supported by the SNMP
Agent's MIB.
• It is recommended that the SNMP Manager use the get-next operation to discover the number
of rows in a table, and then use the explicit limit for the number of columns derived from the
MIB to traverse a row. This recommendation will reduce the possibility of errors in the
response messages when there is a discrepancy between the MIB version of the SNMP
Manager and the SNMP Agent.

96 ARRIS Enterprises, Inc.

 Using SNMP to Monitor CAP-1000 Devices

Obtaining the SNMP MIB

The CAP-1000 Management Information Base (MIB) file is named cap.mib. It is installed on the
CAP-1000 device as a part of the normal installation. The base MIB file, along with other MIBs,
are located in the /usr/cp/lib/ directory. You can also access the cap.mib file through the
CherryPicker Element Manager SNMP Support window.
During installation or upgrade of the CAP-1000, the MIB file is not automatically transferred to a
remote host. If you want to download a MIB from the CAP-1000 device, use the following
procedure.

To obtain the MIB file:

1 Open a web browser window.
2 In the URL address field, enter the address for SNMP Support:

http://<cap_ip_address>/snmp.html

where <cap_ip_address> is the IP address of the CAP-1000 device where the MIB file is located.
3 Press Enter.
The SNMP Support window opens.

View SNMP MIB File

4 To view the MIB, click the View SNMP MIB file button.
5 To save the MIB, right-click the button, select the Save Target As option, and save it to your
desktop.
6 Compile the MIB using a command-line MIB compiler engine or a MIB compiler front-end GUI.

CAP-1000 Software Guide v4.0 97

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SNMP to Monitor CAP-1000 Devices

Configuring the SNMP Agent

To configure the SNMP Agent:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the SNMP link.

SNMP

The Manage SNMP Configuration dialog opens.

98 ARRIS Enterprises, Inc.

 Using SNMP to Monitor CAP-1000 Devices

Manage SNMP Configuration

3 To enable the SNMP Agent, select the SNMP Agent On option.

This option enables the SNMP Agent.
4 To include the Mystro MIB, select the Include Mystro MIB option.
5 In the SNMP Port field, enter the port on which the SNMP Agent will listen.
6 Click Apply.
7 Click OK.

Configuring SNMP Traps

SNMP traps enable an Agent to notify the management station of significant events by way of an
unsolicited SNMP message.

To configure SNMP traps:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the SNMP link.
The Manage SNMP Configuration dialog opens.
3 In the Trap Listeners panel, complete the parameters, as needed.

CAP-1000 Software Guide v4.0 99

Chapter 7 Controlling and Upgrading the CAP-1000 Device Using SNMP to Monitor CAP-1000 Devices

Table 7-2 Trap Listeners

Parameter Description

SNMP Trap Port Defines the remote port where the SNMP Agent sends traps.

IP Address Defines the IP address for the trap listener name.

Trap Rate Defines the maximum rate at which traps are sent to the listener. If this parameter is 0,
then trap throttling is disabled and all traps that satisfy the trap filters for the listener
are dispatched to the listener. The default value is 0 for backward compatibility.

Queue Size Defines the maximum size of the trap queue. There is one trap throttle queue per trap
listener. Every trap that passes the trap filters is placed in the queue. The queue is
emptied at a maximum rate set for Trap Rate, as the traps in the queue are removed
from the queue and sent to the trap listener. If the queue becomes full because alarms
occur at a rate faster than the queue is emptied, then new traps are discarded. The
default is 1000.

Minimum Severity Controls which alarms generate SNMP traps. An alarm that is as severe as, or more
severe than, the configured value generates a trap. An alarm that is less severe than
the configured value does not generate a trap. By default is set to Event.

4 Click Apply.
5 Click OK.

Configuring SNMP Security

Access to an SNMP Agent is controlled by “community strings” that function as passwords. It is
used to authenticate messages that are sent between the management station and the device (the
SNMP Agent). Most implementations use “public” as a standard community string for read-only
access. The default community-string for read-write is “private,” but it is a good idea to change it
for security reasons.
You can also restrict SNMP communications for the Agent, allowing it to communicate with only
a specified list of SNMP management systems. Because the SNMP protocol provides minimal
security, you should use SNMP only on trusted networks.

To configure SNMP security:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the SNMP link.
The Manage SNMP Configuration dialog opens.
3 To add read community names, do the following:
a Under Read Community Names, click Add.
b Enter a read community name.
c Repeat this step for each read community name you want to add.

100 ARRIS Enterprises, Inc.

 Using SNMP to Monitor CAP-1000 Devices

4 To delete read community names, do the following:

a Under Read Community Names, select the name you want to delete.
b Click Delete.
c Repeat this step for each read community name you want to delete.
5 To add read-write community names, do the following:
a Under Read-Write Community Names, click Add.
b Enter a read-write community name.
c Repeat this step for each read-write community name you want to add.
6 To delete read-write community names, do the following:
a Under Read-Write Community Names, select the name you want to delete.
b Click Delete.
c Repeat this step for each read-write community name you want to delete.
7 Do one of the following:
• To accept SNMP packets from any host, select the Accept SNMP Packets from Any Host
option.
In this context, no SNMP packets are rejected on the basis of the name or address of the source
host or the list of acceptable hosts.
• To select SNMP packets from a specific host, click Add and enter the IP address for the hosts
you want.
In this context, SNMP packets are received from any host in the list. This option provides a
higher level of security than using a community name.
8 Click Apply.
9 Click OK.

Filtering Trap Codes

You can filter trap codes for specific trap listeners.

To filter trap codes:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the SNMP link.
The Manage SNMP Configuration dialog opens.
3 To filter a trap code, do the following:
a Under Trap Enabled Codes, find the alarm you want.
b Select the Trap Listener(s) on which you want the trap code enabled. The columns, #1, #2, #3,
and #4 correspond to the IP addresses in the Trap Listeners section.

CAP-1000 Software Guide v4.0 101

Chapter 7 Controlling and Upgrading the CAP-1000 Device Upgrading the CherryPicker Software

c Click Apply.
4 To disable filtering, do the following:
a Under Trap Enabled Codes, find the trap code you want.
b Clear the Trap Listener(s) on which you want the trap code disabled. The columns, #1, #2, #3,
and #4 correspond to the IP address in the Trap Listeners section.
c Click Apply.
5 Click OK.

Upgrading the CherryPicker Software

In most cases, the latest CherryPicker software is already installed on the CAP-1000 from the
factory. In cases where the software version is earlier than v4.0, or a software reinstall is required,
the following procedure should be used.

NOTE You can upgrade the CAP-1000 software using the upgradeOperation, upgradeServerIpAddress, and
upgradeSoftwareDirectory nodes in the CAP-1000 MIB. You cannot; however, reboot the CAP-1000 via
SNMP which is required to finish the upgrade.You do so through the Reboot function. See
section,“Rebooting System Software,”on page 86 for information.

Before You Begin

IMPORTANT Before installing the CherryPicker software, review the following important guidelines:

• Please perform all steps of the upgrade procedure during a regularly-scheduled maintenance
operation. This includes installing the software and rebooting the unit.
• The procedure requires that the CherryPicker hardware be rebooted to complete the software
upgrade or installation process. During this time, streams will not be out put until the reboot is
complete.
• When a Backup CAP-1000 is in Covering mode while configured for CherryPicker
Redundancy (CPR), you cannot perform software updates using the GUI, command line
prompt, or SNMP. To work around this issue, go to the section,“Upgrading the CherryPicker
Software in Covering Mode,”on page 561for more information.
• If an ad server is used, you must stop the ad server before upgrading the CherryPicker
software. After the upgrade process has completed, restart the ad server.
• After upgrading the CAP-1000 to software v4.0 (cap4.0_build_X), the GARP option is
disabled on the management port with a VIP address. This can cause the primary CAP to lose
a connection to an ad server. To enable GARP, see section,“Configuring GARP for
CherryPicker Redundancy (CPR),”on page 103 for information.

102 ARRIS Enterprises, Inc.

 Configuring GARP for CherryPicker Redundancy (CPR)

Upgrading the Software

The current software build displays in the Software Update panel of the Device Control tab. Use
this panel to upgrade the CAP-1000 units at your site.

To upgrade software:
1 Connect to the Primary CAP-1000.
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Under Software Update, enter the required information.
3 Select a Remote or Local CAP-1000 server to update.
4 If you selected a Remote server, enter the IP Address.
5 Click Browse and go to the source directory where the software build is located.
6 Click Start Update.
7 Select the Update Status tab for information about the update.

Configuring GARP for CherryPicker Redundancy (CPR)

By default, GARP is disabled after upgrading a CAP-1000 to software v4.0. When using CPR with
a virtual IP address, you must enable GARP so CPR works correctly. After upgrading the
CAP-1000, use the following procedure to ensure that the router has the correct virtual IP MAC
address. This procedure assumes that the Primary CAP-1000 is active.

To configure GARP:
1 Connect to the Primary CAP-1000.
2 In the CherryPicker Element Manager, go to Setup > Redundancy.
3 Select the GARP option for all interfaces with a Virtual IP.

CAP-1000 Software Guide v4.0 103

Chapter 7 Controlling and Upgrading the CAP-1000 Device Configuring GARP for CherryPicker Redundancy (CPR)

CherryPicker Redundancy

4 Perform a Fail Over.

5 After the failover has completed, perform a Fail Back.
This action triggers the Primary CAP-1000 to send a Gratuitous ARP to the router.

104 ARRIS Enterprises, Inc.

 CHAPTER 8
Managing Licenses

In This Chapter
• Licenses
• Viewing the License Guard
• Viewing Licenses
• Installing License Keys
• Transferring the License Guard and Data Flash Cards
• Using the Software License Key (SLK) Generator and Serial Number Repository

Licenses
Many CAP-1000 software features are enabled by entering a unique license key. Depending on
what package you purchase, a set of license keys is pre-programmed prior to the shipment of your
CAP-1000. As you decide to expand the capabilities of your system, you can obtain additional
license keys to enable other features.
Two types of licenses are available for use: production and trial. Production licenses are intended
to be used for normal operation. Only one production license per feature can exist in a CAP-1000.
A production license covers all CAP-1000 channels enabled for this feature. A production license
has no expiration date. A trial license is intended for limited use. A trial license has an expiration
date, defined as year, month, and day. A trial license expires after midnight of the expiration date.
A production and a trial license for the same feature cannot exist on the same CAP-1000 at the
same time. That is, if a system has a production license for a feature, then installing a trial license
for this feature deletes the production license. If a system has a trial license for a feature, then
installing a production license deletes this trial license. If you have an expired trial license, please
contact the ARRIS Technical Assistance Center for help.

NOTE If you purchased your CAP-1000 through ARRIS, contact the Technical Assistance Center (TAC) to
purchase additional license keys. If you purchased your CAP-1000 through a reseller, contact your reseller
to purchase additional license keys.

CAP-1000 Software Guide v4.0 105

Chapter 8 Managing Licenses Viewing the License Guard

License Mobility
The CAP-1000 v4.0 supports a new feature called “SLK license mobility.” This feature lets you
return SLK licenses back to your customer SLK pool for re-deployment to a different CAP-1000
system. The SLK license mobility function is an SLA option (p/n 504833-011-98) that must be
purchased and activated in the DigitalCM system. SLK license mobility is enabled at the customer
level for all CherryPicker devices and has unlimited use.
When using the license mobility feature, a revoke key will be generated in SLK which need to be
applied to the unit. Once applied, the CAP-1000 generates an acknowledgement code which
identifies the license that has been removed or reduced from the list of licensed features. This
acknowledgement code is then entered by the customer into the SLK web site which will then
return the license inventory to the customer's SLK inventory pool.

IMPORTANT The license mobility feature does not enable the sharing of mobile licenses between DM 6400 and
CAP-1000 systems. Mobile licenses are only applicable to specific CherryPicker systems; either DM 6400
or CAP-1000 units.

NOTE The CAP can be downgraded to an earlier release, but it will retain the licenses that were in place before the
upgrade. If you need to use a CAP-1000 from an earlier release, use those license keys. Once a “license
revoke” has been applied, the system cannot be downgraded.

Viewing the License Guard

License keys are derived from a License Guard card that plugs into the front of the CAP-1000.

License Guard

Each License Guard has a unique 12-character serial number that lets you license features for the
CAP-1000. You can view the License Guard serial number in the System > Licenses window of
the CherryPicker Element Manager.

106 ARRIS Enterprises, Inc.

 Viewing Licenses

License Guard Serial Number

In case of a system failure, you can move the License Guard and Data Flash cards to a different
CAP-1000. The new device then assumes the “personality” of the failed devices, including the
number of channels enabled for a particular feature. See section,“Transferring the License Guard
and Data Flash Cards,”on page 109 for more information.

Viewing Licenses
The license keys are stored on the Data Flash. You can view the license keys in the License
window of the CherryPicker Element Manager. The following information displays for each
license:
• License type
• License key
• Number of channels enabled and used, if applicable.
• License expiration date (for trial licenses only)
It is also possible that an acknowledgement code will display as well.

To view licenses:
 From the CherryPicker Element Manager, click System > Licenses.

CAP-1000 Software Guide v4.0 107

Chapter 8 Managing Licenses Installing License Keys

Licenses

Table 8-1 License Parameters

Type Shows the licensed feature or function.

License Key Shows the license key string consisting of 26 contiguous characters made of letters
and numbers (with no spaces).

Total Shows the total number of licenses for the feature or function.

Available Shows the number of available licenses for the feature or function.

Expiration Date Shows the expiration date for the license.

License Guard Shows the unique License Guard number consisting of a 12-character serial
number generated by ARRIS. You need to supply ARRIS with the License Guard
serial number for a license to be issued.
In case of a system failure, you can move the License Guard and Data Flash cards
to a different CAP-1000. This device assumes the “personality” of the failed device,
including the number of channels enabled for a particular feature.

Acknowledgement Code Shows the system-generated acknowledgement code that identifies the license
that has been removed from the list of licensed features or has its quantity
reduced. Used when processing a license mobility update.

Installing License Keys

You can install CAP-1000 license keys if you have Administration management permissions. See
Chapter 10, “Managing Permissions” for more information.

To install a license key:

1 From the CherryPicker Element Manager, click System > Licenses.
2 In the Enter a New License Key field, enter the license key provided to you by ARRIS.

108 ARRIS Enterprises, Inc.

 Transferring the License Guard and Data Flash Cards

Enter a New License Key

3 Click Apply License.

The CAP-1000 verifies if the license is valid.
• If the license is valid, the feature or function is enabled for use.
• If a license for the feature already exists on the device, a message pops up asking you to
confirm overwriting the existing license.
• If the license is invalid, an error message is displayed.
Review the message and try to resolve the problem. If necessary, contact the ARRIS Technical
Assistance Center for help.

Transferring the License Guard and Data Flash Cards

The License Guard contains a serial number that corresponds to the licenses installed on the Data
Flash. The 1-GB Data Flash compact flash is shipped with the chassis. In case of a CAP-1000
failure, the License Guard and Data Flash cards can be moved to a different device, thus enabling
the license keys on the replacement CAP-1000.

Removing a License Guard

When the License Guard is physically removed from the CAP-1000 device, the following actions
are triggered:
• The Controller generates an alarm, 50114047, “License Guard Not Present.” The severity is
critical and a timer of 30 minutes is triggered by the software.
• If, within 30 minutes, the same License Guard is plugged back into the CAP-1000, the timer is
removed, and nothing is affected. An alarm, 50114047, “License Guard Not Present,” is
cleared and a normal event log is reported with the License Guard serial number.

CAP-1000 Software Guide v4.0 109

Chapter 8 Managing Licenses Transferring the License Guard and Data Flash Cards

• If, within 30 minutes, a different License Guard is plugged into the CAP-1000, the timer is
removed and all existing licenses are removed from the device. You are required to obtain new
software license keys for the License Guard that has been plugged in. You also need to
reconfigure the CAP-1000 device.
• If 30 minutes have passed and no License Guard is plugged in, the CAP-1000 stops the MPEG
traffic on all the output multiplexes. It also disables any potential CherryPicker Redundancy
(CPR) protection from a backup device, and prevents you from restarting the MPEG traffic.
When the same License Guard is plugged back into the device, the MPEG traffic resumes, as
well as the CPR protection, if any. The license file of the device is not modified.

Removing the Data Flash

Ensure that the CAP-1000 is powered off before removing the Data Flash.

WARNING Removing the Data Flash while the CAP-1000 is powered on may corrupt the Data Flash.

Transferring the Cards

Before transferring the License Guard and Data Flash cards in the replacement CAP-1000, ensure
that the serial numbers printed on the License Guard and Data Flash match before installing them
in the chassis. The License Guard contains a serial number that corresponds to the licenses
installed on the Data Flash. The serial numbers on the License Guard and Data Flash must be
identical, and both must be installed in the same chassis.

To transfer the License Guard and Data Flash cards:

1 On the failed CAP-1000, do the following:
a Unplug both power cords to power down the failed chassis.
b Remove the License Guard and Data Flash cards from the front panel of the failed CAP-1000.

110 ARRIS Enterprises, Inc.

 Using the Software License Key (SLK) Generator and Serial Number Repository

License Guard

Data Flash

CAP-1000 Front Panel

2 On the replacement CAP-1000, do the following:

a Unplug both power cords to power down the replacement chassis.
b Insert the License Guard in the License Guard slot. Both sides of the License Guard can be
used. If one side of the License Guard does not work, remove it and insert it upside-down into
the License Guard slot.
c Insert the Data Flash card in the Data Flash card slot.
d Power on the replacement CAP-1000.

WARNING Do not power up the CAP-1000 without the License Guard and Data Flash installed. The system does
not operate correctly without access to the License Guard and Data Flash.

e When the CAP-1000 has rebooted, log in to the CherryPicker Element Manager.

Using the Software License Key (SLK) Generator and Serial Number
Repository
The ARRIS SLK Generator and Serial Number Repository are used to:
• Generate product licenses.
• Manage serial numbers and software license inventory pools.
• Look up previously-generated software licenses and orders.

CAP-1000 Software Guide v4.0 111

Chapter 8 Managing Licenses Using the Software License Key (SLK) Generator and Serial Number Repository

• Transfer a Data Flash serial number (DFSN) or license inventory.

• Use License Mobility
To use the SLK, you need to register with the SLK web site.

Accessing the SLK

To access the SLK:
1 Open a browser window on your client PC.
2 Enter the following URL in the address bar and then press Enter:
http://slk.arrisi.com
The SLK Login window opens.

SLK Login

From this window you can:

• Register to request access to SLK.
• Request a password reset.
• Download the User Guide.
Comprehensive online help is provided on this site.

Using License Mobility

The CAP-1000 v4.0 (or greater) systems now support a new feature called “SLK license mobility.”
This feature lets you return SLK licenses back to your customer SLK pool for re-deployment to a
different CAP-1000 system.

112 ARRIS Enterprises, Inc.

 Using the Software License Key (SLK) Generator and Serial Number Repository

The following list describes the functions of a mobile license:

• When processing a license mobility update, the CAP-1000 generates an acknowledgement
code that identifies the license that has been removed from the list of licensed features. This
code is displayed in the Accounts window of the GUI. In the event that a license update fails,
you can reload the same license mobility update again.
• To return the CAP-1000 to its factory condition, you can reset the license mobility updates and
purge them from the system. Once the license mobility keys are applied, then the license
mobility updates cannot be purged.
• Temporary licenses are not affected by the license mobility function. These licenses cannot be
reclaimed.
• When a CAP-1000 is configured for CherryPicker Redundancy (CPR), the license mobility
function is enabled on the active Primary CherryPicker system as well as a covering Backup
system.
• The new license format is incompatible with the legacy license format. You cannot downgrade
a CAP-1000 to an earlier release and use those license keys.
• When a new license is generated using the SLK, no existing licenses are altered.

Related Documentation
Complete information on using the SLK and SLK License Mobility is provided as follows:
• 365-095-21564 SLK Generating a Permanent License
• 365-095-22051 Using SLK License Mobility
You can access these documents on ARRIS DigitalCM at http://digitalcm.arrisi.com.
The following document is also available:
• 577420-001 Accessing SLK
Refer to Getting Help for information on contacting the Technical Assistance Center (TAC).

CAP-1000 Software Guide v4.0 113

Chapter 8 Managing Licenses Using the Software License Key (SLK) Generator and Serial Number Repository

114 ARRIS Enterprises, Inc.

 CHAPTER 9
Configuring Security

In This Chapter
• Security Options
• Configuring Access
• Configuring RADIUS
• Managing Digital Certificates and Private Keys

Security Options
The following table describes the configurable security options for the CAP-1000:

Table 9-1 Security Options

Secure Shell (SSH) Provides a more secure version of Telnet. By employing SSH instead of Telnet, you can
ensure that all session data sent between the client and the server is encrypted to
prevent snooping of passwords and other important data.

Secure HTTP (HTTPS) Utilizes encryption to protect all GUI session data transmitted over the network
between the CherryPicker Element Manager and the CAP-1000.

Secure FTP (SFTP) Uses SSH to transfer files via the File Transport Protocol (FTP). Unlike standard FTP, it
encrypts both commands and data, thus preventing passwords and sensitive
information from being transmitted over the network.

Remote Authentication Allows the network administrator to use central authentication of login credentials. In
Dial-In User Service other words, users’ credentials (username/password) are kept in a single database on a
(RADIUS) RADIUS server instead of on each device in the network. Each time a user tries to log
into a device he/she is challenged for valid credentials, which are then securely sent to
the RADIUS server for authentication.

You configure security settings through the Device window of the CherryPicker Element Manager.

CAP-1000 Software Guide v4.0 115

Chapter 9 Configuring Security Configuring Access

Security

Configuring Access
Encryption is the most effective way to achieve data security between a client and a CAP-1000. It
protects cleartext user names, passwords, and messages transmitted during remote sessions with a
CAP-1000. See Table 9-2 for a list of options that are available for configuring access.

Table 9-2 Access Parameters

Telnet A terminal emulation program for TCP/IP networks, such as the Internet. To start a Telnet session,
you must log in to a server by entering a valid user name and password. The user name and
password are unencrypted.

FTP File Transfer Protocol, a protocol used to exchange files over the Internet. It can be used to upload
files from a CAP-1000 to an FTP server, or vice versa. To start an FTP session, you must log in to a
server by entering a valid user name and password. The user name and password are unencrypted.

SSL Secure Sockets Layer, a protocol used to transmit private documents over the Internet. SSL uses a
cryptographic system that uses two keys to encrypt data—a public key known to everyone and a
private or secret key known only to the recipient of the message. By convention, URLs that require
an SSL connection start with HTTPS instead of HTTP.

SFTP Secure FTP, a program that uses a secure shell (SSH) to transfer files. Unlike standard FTP, it
encrypts both commands and data, thus preventing passwords and sensitive information from
being transmitted in the clear over the network. On the CAP-1000, SSH listens to port 22 on the
management interface (10/100Ethernet) only. When the CAP-1000 is configured to run SSH, the
following ports are closed: Telnetd, port 23, ftpd, and port 21.

116 ARRIS Enterprises, Inc.

 Configuring Access

Table 9-2 Access Parameters (continued)

HTTP Hyper Text Transfer Protocol, a protocol used to transfer files from a Web server onto a browser in
order to view a Web page that is on the Internet. Unlike FTP, where entire files are transferred from
one device to another and copied into memory, HTTP only transfers the contents of a web page
into a browser for viewing.
When HTTP is configured, an open lock icon is added to the status bar on the CherryPicker Element
Manager.

HTTPS HTTPS is a URI scheme used to indicate a secure HTTP connection. It is syntactically identical to
the http:// scheme normally used for accessing resources using HTTP. Using an HTTPS URL
indicates that HTTP is to be used, but with a different default TCP port (443) and an additional
encryption/authentication layer between the HTTP and TCP.
When HTTPS is configured:
• Users are required to accept the certificate issued by the Certificate Authority before logging in
to the CherryPicker Element Manager.
• A closed lock icon is added to the status bar on the CherryPicker Element Manager.

The following illustration shows a CAP-1000 configured for HTTPS. Note the Lock icon, which
represents a secure, HTTPS connection.

HTTPS Connection

CAP-1000 Software Guide v4.0 117

Chapter 9 Configuring Security Configuring Access

To configure access:
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the Security link on the right side of the Device panel.

Secure Connection Configuration

Data (including passwords) are not encrypted between a client and the CAP-1000.

Data (including passwords) are encrypted between a client and the CAP-1000.

Messages are not encrypted between a client and the CAP-1000.

Messages are encrypted between a client and the CAP-1000. The HTTP port is also open for
outside access, but it redirects the request to HTTPS port 443.
When the Controller is in HTTPS mode, the HTTP port is still open to the 127.0.0.1 loopback
interface for the Diagnostic Interface (DI) command support. The loopback address, 127.0.0.1,
is used to test the basic network setup of the system.

118 ARRIS Enterprises, Inc.

 Configuring RADIUS

3 Under Security, select the options you want.

4 Click Apply.
A confirmation window opens.

Confirmation

5 Click Yes.
To immediately apply the changes, restart the Controller.

Configuring RADIUS
Remote Authentication Dial-In User Service (RADIUS) allows the network administrator to use
central authentication of login credentials. When enabled, RADIUS authentication is used as the
primary authentication method. Users need only one password to log in to the GUI.

NOTE RADIUS only works with the CherryPicker Element Manager. It is not supported for Telnet or SSH.

The CAP-1000 functions as a RADIUS client to the existing RADIUS server(s) in the
environment. It supports up to two RADIUS servers, one primary, and one backup. If the primary
server is not reachable, and another server is specified, the CAP-1000 will use the backup server
for authentication. A shared secret is required between each server and client, which is obtained
from the RADIUS server administrator.
To enable RADIUS, you specify the primary and backup RADIUS servers to use in the
CherryPicker Element Manager.
To configure RADIUS:
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the Security link on the right side of the Device panel.

CAP-1000 Software Guide v4.0 119

Chapter 9 Configuring Security Configuring RADIUS

Secure Connection Configuration

Table 9-3 RADIUS Settings

Authentication Servers

Enabled Enables RADIUS on the authentication (primary) servers.

Local Fall Back When enabled, the CAP-1000 can authenticate users by checking credentials stored on
the device itself. In the event that the network connection to the RADIUS servers are
down, users can still log in. When Local Fallback is disabled and all RADIUS servers are
unreachable, users cannot be authenticated and cannot log in.

Retries Enter the maximum number of attempts a user can make to contact the RADIUS server
before timing out. Valid values are from 1 to 10. The default is 3.

IP Address Enter the IP address for the RADIUS server.

Port If no port is entered, the default value of 1812 is used.

Timeout Enter the maximum amount of time (in seconds) to establish contact with the RADIUS
server before timing out. Valid values are from 1 to 1000.

Shared Secret Enter a text string that serves as the shared secret (encryption key) between the
CAP-1000 and the RADIUS accounting server.
• You can use any standard alphanumeric and special characters.
• You must use the same case-sensitive shared secret on both RADIUS servers.

Test Validates whether the entries refer to a RADIUS server.

120 ARRIS Enterprises, Inc.

 Configuring RADIUS

Table 9-3 RADIUS Settings (continued)

Accounting Servers

IP Address Enter the IP address for the RADIUS accounting server. RADIUS accounting is used for
logging the date and time when users log in and log out. It is not used for
authentication.

Port If no port is entered, the default value of 1812 is used.

Timeout Enter the maximum amount of time (in seconds) to establish contact with the RADIUS
server before timing out. Valid values are from 1 to 1000.

Shared Secret Enter a text string that serves as the shared secret (encryption key) between the
CAP-1000 and the RADIUS accounting server.
• You can use any standard alphanumeric and special characters.
• You must use the same case-sensitive shared secret on both RADIUS servers.

Test Validates whether the entries refer to a RADIUS server.

3 Enter the primary and backup server parameters you want.

4 Click OK.
A RADIUS icon displays in the Status bar when a user is logged in with RADIUS
authentication.

NOTE When you enable or disable RADIUS, the Controller logs off all users after a 30-second delay. A warning
message displays informing the users that they will be logged off the GUI/XML in 30 seconds.)

Configuring User Privileges for RADIUS

To use RADIUS authentication with a CAP-1000, you need to configure a dictionary file on the
RADIUS server. This file contains the attribute for assigning privilege levels per user. The
following is an example of a vendor dictionary file used on a FreeRADIUS server
(http://freeradius.org):

VENDOR Motorola 161

BEGIN-VENDOR Motorola
ATTRIBUTE Motorola-CAP-User-Access-Level 111 integer
VALUE Motorola-CAP-User-Access-Level Motorola-Administrator 15
VALUE Motorola-CAP-User-Access-Level Motorola-Operator 7
VALUE Motorola-CAP-User-Access-Level Motorola-Monitor 0
END-VENDOR Motorola

CAP-1000 Software Guide v4.0 121

Chapter 9 Configuring Security Managing Digital Certificates and Private Keys

When using RADIUS for user authentication, the RADIUS attribute, “Motorola-CAP-User-
Access-Level,” allows for three possible permission levels:
• Motorola-Administrator
• Motorola-Operator
• Motorola-Monitor
These levels are associated with user access to tabs in the GUI. Refer to the following table for
more information.

Table 9-4 Permission Roles

Radius Motorola-CAP-User-Access-Level Attribute Value CAP-1000 User Permission Role

Motorola-Administrator Admin, Config, Grooming, Alarm, Analysis

Motorola-Operator Config, Grooming, Alarm, Analysis

Motorola-Monitor Analysis

Testing RADIUS
The Test button on the Secure Connection Configuration window verifies if the CAP-1000 can
communicate with a RADIUS server. The result can be:
• The RADIUS server IP address is valid.
• The RADIUS server IP address is invalid or the server is down.
It is important that you validate the RADIUS server before saving the settings by clicking OK. If
RADIUS authentication is set to the Required mode and both the primary and backup RADIUS
servers are not responding, users cannot log in. To recover, you must get the RADIUS server
online and running again, or fix network connection issues, if any.

IMPORTANT It is recommended that you keep “Local Fallback” enabled on the Secure Connection Configuration dialog
box until you confirm that you can log in using your RADIUS credential.

Managing Digital Certificates and Private Keys

Public-key cryptography is a form of cryptography in which the key used to encrypt a message
differs from the key used to decrypt it. In public key cryptography, a user has a pair of
cryptographic keys—a public key and a private key.
The private key is kept secret, while the public key can be widely distributed. Incoming messages
must be encrypted with the recipient's public key and can only be decrypted with the
corresponding private key. Certificates are signed by the Certificate Authority (CA) that issues
them.

122 ARRIS Enterprises, Inc.

 Managing Digital Certificates and Private Keys

This section explains how to import or restore the digital certificate and private key. For
information on obtaining a digital certificate and private key, please contact your CA.

Importing a Digital Certificate and Private Key

To import the digital certificate and private key:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the Security link on the right side of the Device panel.
3 Click Change Certificate and Private Key.

Change Certificate and Private Key

4 Under Certificate, do the following:

a Click the folder icon and navigate to the location where the certificate is saved.
b Select the file and click Open.
The file is imported into the window.

CAP-1000 Software Guide v4.0 123

Chapter 9 Configuring Security Managing Digital Certificates and Private Keys

NOTE If you make an error, click the Note icon to clear the certificate.

5 Under Private Key, do the following:

a Click the folder icon and navigate to the location where the private key is saved.
b Select the file and click Open.
The file is imported into the window.

NOTE If you make an error, click the Note icon to clear the private key.

6 Click OK to submit the new certificate and private key.

The Secure Connection Configuration window opens.
7 Click Apply to send the request to the CAP-1000 and enable the change.

Restoring a Digital Certificate and Private Key

Use this procedure to restore an existing digital certificate and private key previously imported
into the CAP-1000.

To restore a digital certificate and private key:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the Security link on the right side of the Device panel.
3 Click Change Certificate and Private Key.

124 ARRIS Enterprises, Inc.

 Managing Digital Certificates and Private Keys

Change Certificate and Private Key

4 Click Set Default.

The Change Certificate and Private Key window closes returning you to the Secure Connection
Configuration window.
5 Click Apply to send the request to the CAP-1000 and enable the change.

CAP-1000 Software Guide v4.0 125

Chapter 9 Configuring Security Managing Digital Certificates and Private Keys

126 ARRIS Enterprises, Inc.

 CHAPTER 10
Managing Permissions

In This Chapter
• Permissions
• Default Admin Account
• Adding Users
• Deleting Users
• Changing the Linux Root Account
• Changing User Passwords

Permissions
Users with Administrator rights can manage user access to CAP-1000 features and functions
through the CherryPicker Element Manager. Permissions are granted or denied based on options
selected in the Permissions window.

Permissions

Table 10-1 identifies the permissions that are granted to the roles. Permissions are based on access
to windows in the CherryPicker Element Manager. A check mark indicates that the role can
modify parameters on the specified tab and window. Users without specific role assignments can
view windows in the CherryPicker Element Manager, but cannot modify parameters in those
windows.

CAP-1000 Software Guide v4.0 127

Chapter 10 Managing Permissions Default Admin Account

Table 10-1 Permissions

Role Setup Triggers Content Picking Alarms Analysis

System Licenses Permissions Redundancy Files Triggers Mux Grooming Active History Settings Viewing

Admin X

Config X X X X X

Grooming X X

Alarm Mgt X X X

Analysis X

Table 10-2 lists the responsibilities associated with a specific role.

Table 10-2 Roles and Responsibilities

Role Responsibility

Admin Allows CAP-1000 users, user names, passwords, or privileges to be assigned or

revoked.

Config Allows new licenses to be added and database items to be configured (such as
redundancy, multiplexes, and ports). Without this privilege, the Apply Changes and
Restore Changes buttons are disabled; editable fields are read-only; the Files window
cannot be viewed; multiplexes cannot be created, updated, or deleted; and device
controls are disabled. Also enables the configuration of BISS injected identifiers at the
device level.

Grooming Allows grooming of programs, elementary streams, and files using the Grooming tab.
Also enables the configuration of BISS injected identifiers at the device level.

Alarm Management Allows alarms to be cleared and alarm settings to be modified.

Analysis Allows the Analysis window to be viewed.

Default Admin Account

ARRIS provides a default Administrator account so you can gain access to the CAP-1000 on first
launch. The default user name is Admin (it is case sensitive) with no password. For security
purposes, please change the password to the default Admin account.

WARNING Do not remove the default “admin” account. You can only restore the default “admin” account by
resetting the database files.

128 ARRIS Enterprises, Inc.

 Adding Users

Adding Users
To add a user:
1 From the CherryPicker Element Manager, click Setup > Permissions.
2 Click Add User.

Add User

NOTE If an access option is not checked, the user is able to access the CherryPicker Element Manager window and
view settings, but cannot modify any settings.

3 Enter the User Name and Password.

Blanks are not allowed. The parameters are case sensitive.
4 Click OK.
5 Select the access options you want to grant to this user.
6 Click Apply.

Deleting Users
To delete a user:
1 From the CherryPicker Element Manager, click Setup > Permissions.
2 Select the user you want to delete.
3 Click Delete User.
A confirmation window opens.
4 Click Yes.

CAP-1000 Software Guide v4.0 129

Chapter 10 Managing Permissions Changing the Linux Root Account

Changing the Linux Root Account

Only one Linux user account can exist on a CAP-1000 running Software v4.0. This is the super-
user account with a user name of root. The root account is protected by a password. The root user
can change this password by executing the passwd command. The default password is terayon.
The password file, passwd, is stored on the Data Flash in the Security folder.

Changing User Passwords

To change a user password:
1 From the CherryPicker Element Manager, click Setup > Permissions.
2 Select the user you want to modify.
3 Click Change Password.

Change Password

4 Enter the new password.

A blank password is not allowed. The parameters are case sensitive.
5 Click OK.

NOTE Be sure to inform the user when his or her password has been changed.

130 ARRIS Enterprises, Inc.

 CHAPTER 11
Configuring the Network

In This Chapter
• Gigabit Ethernet Ports
• Digital Signal Processor Module
• Physical Interfaces
• Gigabit Ethernet Port States
• Protocols
• Viewing Gigabit Ethernet Port Configuration
• Enabling Gigabit Ethernet Ports
• Configuring Gigabit Ethernet Ports
• Disabling Gigabit Ethernet Ports
• Blocking Management Traffic
• Configuring Auto Negotiation and Link Speed
• Configuring Static Routes
• Using the CAP-1000 Port Analyzer

Gigabit Ethernet Ports

You can identify the GigE ports in the Setup > System > Network tab of the CherryPicker
Element Manager. The ports appear on the front panel of the CAP-1000. Specific information
about the GigE ports appears on the Network tab of the CherryPicker Element Manager. Use the
scroll bar in the Network tab to see all parameters for GigE ports.
The CAP-1000 can be configured with a 10-Gigabit Ethernet Input Output Adapter (10G IOA)
module (six 1-GigE ports plus four 10-GigE ports) or the older 1-Gigabit Ethernet Input Output
Adapter (1G IOA) module (four 1-GigE ports).

CAP-1000 Software Guide v4.0 131

Chapter 11 Configuring the Network Gigabit Ethernet Ports

Network GigE Ports

1-Gigabit Ethernet Input Output Adapter (1G IOA)

The legacy 1G IOA has four bi-directional Gigabit Ethernet ports. Each port can use either an
optical or an electrical connector, but not both at the same time. The GigE ports can carry MPEG
traffic and management simultaneously.

10-Gigabit Ethernet Input Output Adapter (10G IOA)

The newer 10G IOA has four SFP+ cages for either 10-Gbps (SFP+) or 1-Gbps SFP, four 1-Gbps
SFP cages (copper or fiber), and two 1-Gbps RJ45 ports. All of the ports come with auto-
negotiation and full-duplex support.
Ports 1/1 to 1/4 can be configured as fiber (SFP or SFP+ Ethernet transceiver) or copper (Twinax /
SFP+ Direct Attach), but do not support copper (RJ-45) SFP modules. Ports 1/5 to 1/8 can be
configured as fiber or copper (SFP). Ports 1/9 and 1/10 are copper only. All ten ports can carry
MPEG traffic and management simultaneously.

132 ARRIS Enterprises, Inc.

 Gigabit Ethernet Ports

10G IOA

Small Form Factor Pluggable (SFP) Transceivers

On the 10G IOA, the CAP-1000 validates the usage of the SFP transceivers. When the SFP
transceiver, installed in any cages of the 10G IOA, does not match Table 11-1, an alarm is
reported. If the invalid SFP is detected at the time of enabling the line in the GUI, the request to
enable the line is accepted, but a dialog box and a warning message notify you that the use of this
SFP may affect service.
When a 10-Gigabit SFP transceiver is plugged into a 1-Gbps port (1/5 to 1/8) the link is not
established and an alarm is reported. When a 1-Gbps copper SFP transceiver is plugged in a 10-
Gbps (1/1 to 1/4), the link is not established and an alarm is reported. Table 11-1 lists the supported
configurations for the SFP transceiver types.

Table 11-1 SFP Transceiver Types

Interface Board type 10-GigE Fiber 10-GigE Copper 1-GigE Fiber 1-GigE Copper

1/1 - 1/4 IOA NA NA Yes Yesa

1/1 - 1/4 10G IOA Yes Yes Yes No
1/5 - 1/8 10G IOA No No Yes Yes
1/9 - 1/10 10G IOA NA NA NA NA
bond0 DSP NA NA NA NA
a. The IOA supports copper on 1/1 to 1/4 via an RJ45 connection. The SFPs that plug into the cages;
however, are strictly optical.

For Ethernet connectors, if the cage is empty, a tool tip displays the port ID, such as Ethernet 1/3.
When SFP is plugged in, the tool tip displays all information about this SFP (such as the example
below).

CAP-1000 Software Guide v4.0 133

Chapter 11 Configuring the Network Gigabit Ethernet Ports

10GE IOA with SFP

In the Setup > System > Network tab, there are 10 ports on the 10G IOA. The total number of
ports may be 11 or 12, depending on the type of DSP module that is installed. The CR-DSP has
two 10/100 ports, while the older DSP module has only one 10/100 port. For the CR-DSP module,
the ports are 2/1 and 2/2.

Connector Types

On this tab, the Type column lists the connector types: Optical, Optical+, Electrical or No SFP.
Ports 1/1 through 1/4 are capable of 10-Gbps and 1-Gbps speed. Ports 1/5 through 1/10 are capable
of 1-Gbps speed. Ports 1/1 through 1/8 require an SFP module to function. When there is no SFP
plugged into the cage, all cells for this port are read-only. The Auto Neg and Link Speed functions
are disabled.

134 ARRIS Enterprises, Inc.

 Digital Signal Processor Module

When operating at different speeds, the following link status is shown:

Icon Speed

10G bps

1G bps

100Mbps

10Mbps

Link down

Digital Signal Processor Module

The CAP-1000 is configured with either a DSP module or a CR-DSP module. The DSP module
contains one management port (2/1). The CR-DSP module contains two physical management
ports (2/1) and (2/2). These ports function as a bonded pair and share a single IP address. The
second port (2/2) serves only as a redundant physical port. The management port handles traffic
such as SCTE 30 and CPR heartbeat and is not intended to support MPEG traffic.

DSP Module

Port 2/1 is configured with an IP address of 169.254.2.1, a netmask of 255.255.255.252, and a

gateway of 169.254.2.2. Port 2/2 has the same configuration as 2/1. If you update the IP, Netmask,
or Gateway parameters, the DSCP, Default Gateway, Virtual IP, Virtual Netmask, Routing Metric
Backup, or Monitor Link options become editable. All other parameters remain disabled.

CAP-1000 Software Guide v4.0 135

Chapter 11 Configuring the Network Digital Signal Processor Module

CR-DSP Module

You can view details about the DSP module on the Setup > System > Hardware window.

Bonded Ports
The CR DSP board has two physical management ports (2/1) and (2/2) that function as a bonded
pair and share a single IP address. During monitoring, the second port link remains in standby
mode. When Linux detects that the first port link is down, the second port takes over the IP address
and MAC of the first port.

Bonded Ports

Active port bonding is indicated in gray highlight on the Setup > System > Network window of
the CherryPicker Element Manager. By default, port bonding is configured so you do not need to
configure the second port separately.
The CR-DSP board is capable of encryption without software support.

136 ARRIS Enterprises, Inc.

 Physical Interfaces

Physical Interfaces
The physical interfaces for the GigE ports are:
• 1000BASE-T for the electrical ports.
• 1000BASE-SX and 1000BASE-LX for the four optical ports of the IOA and four fiber SFP
cages on the 10G IOA.
• 10GBASE-SR/SW and 10GBASE-LR/LW (depending on the SFP+ Ethernet transceivers) for
four 10-GigE optical ports of the 10G IOA (the four fiber SFP+ cages).
Each signal input is represented by the Receive (Rx) part of a bi-directional physical port, and each
signal output is represented by the Transmit (Tx) part of a bi-directional physical port. The
interface type for the GigE input or output is Gigabit Ethernet.
In copper mode, the GigE layer supports 10 Mbps, 100 Mbps or 1000 Mbps operations on the
electrical ports of the 1G IOA or 10G IOA. The DSP management ports are restricted to 10/100
Mbps.
The fiber mode is fixed to 1000 Mbps for the 1G IOA, as well as the four SFP cages (ports 1/5 to
1/8) of the 10G IOA, (setting is set to “1G” for fiber only). The four fiber SFP+ cages of the 10G
IOA can be either 1000 Mbps with an SFP Ethernet transceiver or 10000 Mbps with an SFP +
Ethernet transceiver. The speed values are not configurable by the user. Auto negotiation is set to
On or Off based on link speed.
The IP layer (hardware and Ethernet driver) can handle valid non-MPEG IP frames in a manner
compliant with RFC 791. The following restrictions apply:
• Only non-MPEG IP protocols are supported: TCP, ICMP, and IGMP.
• Only the following UDP protocols are supported: SNMP, TFTP, DNS, and ARP.

Interoperability
The CAP-1000 is certified to with the following external devices:
• Switches and Routers—Cisco Catalyst 6500 Series switches (WS-C6506, WS-C6509, WS-
C6508-NEB, WC-C6513), Cisco 10720 Internet Router, Foundry Networks BigIron 8000
switch.
• Signal Source and Destination devices—Sencore MPEG/IP Analyzer, nCube video server,
Harmonic BNG 6000, Harmonic NSG 8100/8200 (destination device), Internet Photonics
LightStack MX (destination device), Motorola SEM (High Density
Encryptor/Modulator/Upconverter).

CAP-1000 Software Guide v4.0 137

Chapter 11 Configuring the Network Gigabit Ethernet Port States

Gigabit Ethernet Port States

This section provides information on GigE port states, connections, and configuration options.

LED Indicators
Two LEDs are provided on top of each connector of the adaptor and the DSP ports.

Fiber
For fiber configurations, the left LED blinks green when the port is selected but no link has been
established. When the left LED is steady green, it indicates that the port is connected. The right
yellow LED displays the port activity.
When the left LED on 1-Gbps ports is steady green, it indicates that the port is connected. The
right yellow LED displays the port activity.
For Fiber on 10-Gbps ports, bi-color green/yellow LEDs are placed on the side of each dual SFP+
cage for link and activity feedback. Each LED reports information for one optic transceiver and
will toggle at a rate of 120ms on 120ms off when packets are detected (activity) and stay on for
link status. The yellow color is used when the port is configured for 10-Gbps with SFP+
transceiver. The green color is used when the port is configured for 1-Gbps with SFP transceiver.

Copper
The LED pulses orange on/off when the port is selected, but no link has been established. The right
yellow LED displays the port activity. For the 10G IOA ports, two LEDS are associated with each
connector. In the case of 10-Gbps ports, there is only one bi-color LED per port. The bi-color left
LED is orange when a link has been established at either 10- or 100-Mbps and green when a link
has been established at 1000 Mbps. The right yellow LED displays the port activity.

Output Port States

When enabled, the GigE output port is in either the Standby state or the Active state. The default
MPEG output state is active.
In the standby state, all multiplexes and grooming configuration that existed in that output port
prior to the switch to this state are preserved. The output port does not send any MPEG packets.
However, it is able to send regular, non-MPEG Ethernet packets (such as various IP protocol
management packets, etc.). All operations available for a normal output, such as creation and
deletion of multiplexes, grooming and dropping of groomings, are allowed for a standby port.
When in the Active state, the output port transmits MPEG packets. The transition from the standby
state to the Active state automatically restores the configuration and grooming activities of all the
multiplexes that exist in this output port. The process of switching to the standby (or back to
active) state takes the maximum of one second.

NOTE Management traffic is not affected when the MPEG output traffic toggles between active and standby.

138 ARRIS Enterprises, Inc.

 Gigabit Ethernet Port States

Active Ports
A GigE port is active when the CAP-1000 hardware declares that the “link is up” (i.e., auto-
negotiation has been completed). An active line does not necessary have any incoming MPEG
streams or management traffic. When a CAP-1000 system is new and the GigE ports are not
configured/enabled, the CAP-1000 comes up in GigE copper mode with auto negotiation enabled.
You can then plug in a cable and get a link light.

Connections
The CAP-1000 automatically detects the connections and displays them in numerical order based
on their slot ID and configuration. A default name is assigned to the port using the <slot>/<port>
format where:
• <slot> is the slot label, 1, 2, 3, or 4.
• <port> is the port number, such as 1, 2, 3, etc.
You can change the port name.

Persistent Storage of Port Configuration

The IP related configuration parameters and the transceiver type will be stored in two files:
• sysconfig on the data flash in /dataflash/sysconfig.
• vipconfig on the data flash in /data/vipconfig.
The information is retained when the GigE port is disabled and grayed out in the GUI. The user
does not have to re-enter the values when re-enabling the port. When a GigE port's IP, netmask, or
gateway are changed, the previous information is retained as well.

Dynamic Configuration
You can make configuration changes to a GigE port without the need to reboot the CAP-1000.
When you apply a configuration change to a GigE port, a warning opens and informs you that a
brief interruption in services occurs.

Warning

If you decide to apply the changes, the CAP-1000 verifies the configuration. If the configuration is
verified, it is applied to the port. If a problem occurs, an error message displays and describes the
error that must be corrected. The problem must be corrected before the port can be configured.

CAP-1000 Software Guide v4.0 139

Chapter 11 Configuring the Network Protocols

Protocols
The CAP-1000 supports GARP, RIP, and OSPF protocols. RIP and OSPF are mutually exclusive.
GARP can work with either RIP and OSPF, or with no routing protocol selected. You can choose
which protocols to use with the CAP-1000.

Gratuitous ARP (GARP)

Software v4.0 uses the Address Resolution Protocol (ARP) to map a logical IP address of a host to
the physical MAC address of that host. ARP messages are sent whenever a Unicast output
multiplex connection is created. ARP messages may also be sent to a connected destination to
update the ARP cache. The CAP-1000 also provides a check box on the System > Setup >
Network tab which enables GARP by default on a selected port when the virtual IP address is
updated. When disabled in the CherryPicker Element Manager, ARP messages are not sent when
triggered by CPR and AIP implementations for virtual IP address changes and migrations.

GARP

IMPORTANT After upgrading the CAP-1000 to software v4.0, the GARP option is disabled on the management port for
the VIP address. Manually enable the GARP option on the Setup > System > Network tab in the GUI and
restart the controller via the Setup > System > Device Control > Restart Controller button. By default,
GARP is enabled for MPEG ports.

140 ARRIS Enterprises, Inc.

 Protocols

Routing Information Protocol (RIP)

RIP is a distance-vector routing protocol, which employs the hop count as a routing metric. RIP
prevents routing loops by implementing a limit on the number of hops allowed in a path from the
source to a destination. The term, distance vector, refers to the fact that the protocol manipulates
vectors (arrays) of distances to other nodes in the network.
The maximum number of hops allowed for RIP is 15. This hop limit, however, also limits the size
of networks that RIP can support. A hop count of 16 is considered an infinite distance and used to
deprecate inaccessible, inoperable, or otherwise undesirable routes in the selection process. RIP
uses the User Datagram Protocol (UDP) as its transport protocol, and is assigned the reserved port
number 520.

NOTE The RIP Metric Backup parameter applies when the virtual IP is used on the Backup CAP-1000. Multicast
fencing down stream of the Primary and Backup devices can be implemented by using different values on
the RIP Metric (value used from the Primary) and the RIP Metric Backup (value used from the backup).

The RIP Metric value is sent out on the interface of the primary CAP-1000 when a primary IS NOT covered
by the backup. A value of 0 indicates no RIP is sent. A RIP value should only be used if the OSPF value is
false.

RIP Routing Protocol

The CAP-1000 supports RFC 2453 RIPv2 and sends RIP announcements to the IP multicast
address of 224.0.0.9. You configure the RIP option on the System > Setup > Network tab.

CAP-1000 Software Guide v4.0 141

Chapter 11 Configuring the Network Protocols

Open Shortest Path First (OSPF)

In addition to RIP, the CAP-1000 now supports the Open Shortest Path First (OSPF) based on
RFC2328 OSPF v2. On the CAP-1000, OSPF is used to advertise the virtual IP addresses of the
device when CherryPicker Redundancy (CPR) or Ad Insertion Protection (AIP) is enabled.
You can enable or disable OSPF on any Ethernet interface of the CAP-1000. You can also
configure the OSPF functionality in the CAP-1000 on a per GigE output port basis, including the
management port on the DSP or CR-DSP modules.
Each network port on the primary that has enabled OSPF as the routing protocol must have the
OSPF routing protocol on the corresponding backup network port. The OSPF option is available
on the System > Setup > Network tab.

OSPF Routing Protocol

Go to Chapter 33, “Configuring OSPF,” for complete information on how to configure OSPF for
your site.

NOTE OSPF and RIP are mutually exclusive on the interfaces. You can choose which protocol to use in the
CherryPicker Element Manager (GUI) on the GigE output ports.

142 ARRIS Enterprises, Inc.

 Viewing Gigabit Ethernet Port Configuration

Viewing Gigabit Ethernet Port Configuration

To view GigE port configuration:
 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel. Use the horizontal scroll bar to display all
available parameters.

Gigabit Ethernet Port Parameters

The following table describes the GigE port parameters in the CherryPicker Element Manager.

Table 11-2 Gigabit Ethernet Port Parameters

ID Shows the default ID assigned to the port in the format: <slot>/<port>.

Link Shows the link status and link speed for ports on either the 1G IOA or 10G IOA.
Mouse over the colored indicators to get a tool tip with the link speed.

—Active (green)
—Active (blue)
—Active (yellow)
—Active (orange)
—Inactive (red)
—Bonded (gray ports).

CAP-1000 Software Guide v4.0 143

Chapter 11 Configuring the Network Viewing Gigabit Ethernet Port Configuration

Table 11-2 Gigabit Ethernet Port Parameters (continued)

Port Enable Activates a GigE port for management traffic that is independent from MPEG
traffic. When disabled, all cells to the right are grayed out.

MPEG Enable Activates a GigE port for MPEG traffic (creating input and output multiplexes) that
is independent from management traffic. When a port is disabled for MPEG traffic,
all multiplexes associated with that port are deleted.

Block Mgmt Traffic When selected, this option disables management traffic such as FTP or telnet.

Name Shows the default name assigned to the port in the format: <slot>/<port>, or a
user-specified name.

IP Specifies a static IP address for this port (1.1.1.1 to 223.255.255.355). The allowed
range of IP addresses is from 0.0.0.0 to 223.255.255.255, with the following
exceptions:
• Address 0.0.0.0 can not be used. This address is not a valid Internet address and
it is also used by the hardware as the host address after hardware is initialized.
• Address 127.X.X.X is not a valid IP address. It is used as the loop back address
for troubleshooting and network testing.
• The default value is an empty string. It may be also represented as an all-0
address in some interfaces where an empty string cannot be used.

Netmask Specifies a net mask address for this port. The allowed set of Netmask values is
from 128.0.0.0 to 255.255.255.252. The default value is an empty string.
Note: The netmask may also be represented as an all “0” address for those
interfaces in which an empty string cannot be used.

Default Gateway If selected, the CAP-1000 uses the gateway on this port as the default gateway for
entire device. Only one port can be selected. The default gateway is also displayed
in the upper-left corner of the Network panel.

Gateway Shows the gateway to which this GigE port is connected. The allowed range is from
0.0.0.0 to 223.255.255.255. The default value is an empty string.

MAC Address Specifies the Media Access Control addresses for the five configurable ports. This
address is set at manufacturing time and is reported to the software by the driver.
This parameter is read-only.

Virtual IP Specifies a virtual IP address for the port: for example, the port to be used with
CherryPicker Device Redundancy (CPR).
Note: Selection of the virtual IP port option is only available if virtual IPs have been
assigned. Virtual IP assignment is not a requirement for using port mirroring. If it is
used in conjunction with the AIP feature, however, one virtual IP is available. See
Chapter 27, “Configuring CherryPicker Redundancy” or Chapter 31,
“Configuring Ad Insertion Protection”for information.
Virtual Netmask Specifies the virtual netmask to be used with the Virtual IP parameter.

GARP Specifies a gratuitous ARP for a Virtual IP address. GARP can only be enabled
whenever virtual IP and virtual netmask are defined.

144 ARRIS Enterprises, Inc.

 Viewing Gigabit Ethernet Port Configuration

Table 11-2 Gigabit Ethernet Port Parameters (continued)

DSCP Enables the CAP-1000 to mark outgoing elementary stream packets to use Quality
of Service (QoS) mechanisms implemented on your network. The range for the
Differentiated Services Code Point (DSCP) is 0 to 63. The default value is 0 (Best
Effort). See section,“Gigabit Ethernet Multiplex Options,”on page 235
for more information.

Routing Protocol Lists the routing protocols you can enable: RIP, OSPF or None. This option is grayed
out when the port is network disabled. If you configure the Virtual IP and Virtual
Netmask options, then OSPF appears in the list. Otherwise, only RIP and None
display.

Routing Metric Sets the IPv4 internet working protocol for use with the RIP metric options. The
options are 1-15. You can edit this parameter when the Routing Protocol is not set
to None. A value of 0 indicates no RIP is sent.

Router ID Sets the Router ID with a 32-bit number. When the Router ID is unset, use the
highest IP interface address belonging to the route. (Unset meaning not yet defined
via the GUI or cleared after setting a previous definition). Otherwise, you can set
the Router ID with dotted octets. Blanks are not allowed. This option is supported
when the OSPF, Virtual IP, and Netmask options are set.

Area ID Sets the IPv4 address that serves as the backbone. The Backbone has a reserved
Area ID of 0.0.0.0.

Type Specifies the GigE input port as electrical or optical. If an optical transceiver is
installed, you can select either the electrical or the optical transceiver, but not both.
The 10G IOA can have Electrical, Optical, Optical +, or No SFP. The default is
electrical transceiver.

Auto Neg Works with the Speed parameter. Automatically negotiates port speeds for GigE
ports. The Auto Neg mode is enabled or disabled based on Link Speed.

Link Speed Sets the link speed for the GigE input ports.
• On the 1G IOA the Link Speed is: Auto, 10 Mbps, 100 Mbps, 1000 Mbps for
copper mode and 1000 Mbps for fiber mode.
• On the 10G IOA module, the Link Speed is: Auto, 10 Mbps, 100 Mbps, 1000
Mbps for the two copper ports (1/9/and 1/10) and 1000 Mbps for ports 1/5 to
1/8. For ports 1/1 to 1/4, the Link Speed is detected using the transceiver type
and there is no selection available to the user.

IGMP Indicates if the CAP-1000 is operating in the IGMPv2 or IGMPv3 mode. The IGMPv2
and IGMPv3 cannot coexist on the same network; if any device on the network is
using IGMPv2, all IGMPv3 devices fall back to IGMPv2 compatible mode.
Note: IGMPv3 allows for the inclusion or exclusion of multiple source IP addresses.
The CAP-1000 only supports the inclusion of a single source IP per input multiplex.
For additional source IP address using the same multicast IP, you need to create
additional input multiplexes and specify a single source IP address for each one.

CAP-1000 Software Guide v4.0 145

Chapter 11 Configuring the Network Viewing Gigabit Ethernet Port Configuration

Table 11-2 Gigabit Ethernet Port Parameters (continued)

MPEG Out Specifies the output port state for MPEG video. This option is editable when MPEG
Enable is selected The options are:
• Active—Output port operates normally and transmits MPEG packets. This is the
default setting.
• Standby—All multiplexes and grooming that exist at the output port prior to the
switch to this state are preserved. The output port does not send any MPEG
packets, however, it is still able to send regular, non-MPEG Ethernet packets
(such as various IP protocol management packets, etc.). All operations available
for a normal output, such as creation and deletion of multiplexes or grooming
and dropping of grooming, are allowed for a standby port.

Packet Specifies the number of packets for MPEG packets per UDP datagram.

MPEG Source IP Origin Specifies the origin of MPEG packet source IP Address. Without port mirroring or
primary port of mirroring, the following three choices are available:
• Current Port IP Address
• Current Port Virtual IP Address
• Custom IP Address
For mirror ports, the following five choices are available:
• Current Port IP Address
• Current Port Virtual IP Address
• Custom IP Address
• Primary Port IP Address
• Primary Port Virtual IP Address

MPEG Source IP Specifies the MPEG packet source IP address. This option is only enabled for
editing when the MPEG Source IP origin column is set to Custom IP address.

Peer Port Selects a redundant port for Ad Insertion Protection (AIP). The combo box displays
None or the port name.

Mirror Of Makes this port a mirror port of specified port. The choices are “<None>” and/or
the port IDs. For example, choosing “1/1” means the current port becomes a mirror
of port 1/1.

AIP Enable Enables or disables AIP on the selected port. At least two paired ports are required.
The available ports can be 1, 2, 3, or 4. See section,“Configuring Ad Insertion
Protection,”on page 617 for more information.
Active AIP Port Indicates if this port is active or not. The options are Yes or No. The Active AIP port
requires a valid virtual IP address and netmask. During normal operation, if an
active port goes down, the device automatically changes the backup port to be
active port.

Routing Metric Backup Sets the RIP metric based on the Routing Protocol option. The options are 1-15. You
can edit this parameter when the Routing Protocol is not set to None. A value of 0
indicates no RIP is sent. A RIP value should only be used if the OSPF value is false.

146 ARRIS Enterprises, Inc.

 Enabling Gigabit Ethernet Ports

Table 11-2 Gigabit Ethernet Port Parameters (continued)

Monitor Link Enables link monitoring for CPR support. When enabled, this GigE port is tested for
failure when the Primary CAP-1000 is in a Protected state. If the port fails, a
failover is triggered. See section,“Configuring Link Monitoring,”on
page 562 for more information.
Combine Peer Port Combines peer ports on the IOA for determining failover in a CPR configuration. If
this option is selected, Monitor Link and Combine Peer Port check boxes are
automatically selected for the Peer Port option.
Enabling this option treats the paired ports as a single port for failure detection
purposes. Both ports must fail before a failover occurs.
The Combine Peer Port option works without AIP.

Enabling Gigabit Ethernet Ports

Each Ethernet port can be enabled or disabled by selecting or clearing the Port Enable check box.
A separate check box, MPEG Enable, is used to allow MPEG traffic. The Port Enable check box
works in concert with the MPEG Enable check box.
When Port Enable is selected with RIP, MPEG Enable is also selected. Conversely, when Port
Enable is cleared (unchecked), MPEG Enable is also cleared. When the Port Enable check box is
selected, you can separately disable MPEG traffic by clearing the MPEG Enable check box. If the
Port Enable check box is cleared, all cells to the right are grayed out. When Port Enable is selected
with OSPF, MPEG Enable is disabled.
You cannot change the IP address of the port to which the CherryPicker Element Manager is
currently connected without disconnecting from the GUI. Any attempt to do so causes a warning
message to appear.

Warning

To enable a GigE port:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Identify the Ethernet port you want to enable.
3 Under Port Enable, select the check box.
4 To enable MPEG traffic on the port, select the MPEG Enable check box.

CAP-1000 Software Guide v4.0 147

Chapter 11 Configuring the Network Disabling Gigabit Ethernet Ports

5 Click Apply.
An alert message opens.
6 Click Yes to continue.
The parameters are updated.

Configuring Gigabit Ethernet Ports

Before configuring the Gigabit Ethernet module, have the following information available:
• IP address
• Netmask address
• Gateway address
• Protocol
• Transceiver type (either electrical/copper or optical/fiber)
You need this information to configure the GigE module. If you do not know this information,
contact your system administrator for assistance.

To configure a GigE port:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Select the Ethernet port you want to configure.
3 Double-click the parameter you want and enter the required information.
Refer to Table 11-2 on page 143 for a description of the parameters.
4 Click Apply.
5 Click Yes to continue.
The parameters are updated.

Disabling Gigabit Ethernet Ports

When MPEG traffic is disabled, you cannot create any input or output multiplexes. The input port
in the Content Picking window displays an input port icon with red line strike thru (just like
disabled output ports).

IMPORTANT When MPEG traffic is disabled, all associated multiplexes (input and output) are removed.

148 ARRIS Enterprises, Inc.

 Blocking Management Traffic

To disable a GigE port:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Scroll the bottom panel until the Port Enable column appears.
3 Identify the port you want to disable.
4 Clear the Port Enable check box.
When a port is disabled, other parameters are grayed out and not available for use.
5 Click Apply.
6 Click Yes to continue.
The GigE port is disabled.

Blocking Management Traffic

You can activate a GigE port for management traffic and for MPEG traffic independently. You can
also restrict management traffic for individual ports. To that purpose, three columns are displayed
in the GUI to separate control port/interface activation, allowing the MPEG traffic on the port (i.e.
creating input or output multiplexes) and restricting management traffic on the port (FTP, TFTP,
SFTP, SSH, Telnet and SNMP are blocked).
The port/interface column is called Port Enable, the MPEG traffic is called MPEG Enable, and the
restriction of the management traffic is called Block Mgmt Traffic.
When management traffic is blocked on the connection, the ports that are not used to support
CherryPicker Redundancy (CPR) traffic are closed. See Chapter 27, “Configuring CherryPicker
Redundancy,” for more information.

To block management traffic:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Select the Ethernet port you want to block.
3 In the Block Mgmt Traffic parameter, select the check box next to the port you want to block.
4 Click Apply.
5 Click Yes to continue.
The parameters are updated.

CAP-1000 Software Guide v4.0 149

Chapter 11 Configuring the Network Configuring Auto Negotiation and Link Speed

Configuring Auto Negotiation and Link Speed

By default, the CAP-1000 automatically negotiates port speeds for GigE input and output ports.
This feature is referred to as “auto negotiation.” To increase compatibility with peer devices that
may not implement auto negotiation correctly, you can choose to manually disable this feature.
You can dynamically configure the port speed at any time after the GigE ports are enabled,
providing that the transceiver type is set to electrical mode. The valid port speeds for a copper link
are 10 Mbps, 100 Mbps, or 1000 Mbps. When the transceiver is in optical mode, the link speed is
1000 Mbps.
Two parameters on the Network tab are associated with auto negotiation: Link Speed and Link
Status. The Link Status reports the Link Speed. This information is useful when the link is
configured to “Auto.” The valid range of values for the Link Speed is: Auto, 10 Mbps, 100 Mbps,
1000 Mbps for copper mode, and 1000 Mbps for fiber mode.
On the 10G IOA, the Link Speed is: Auto, 10 Mbps, 100 Mbps, and 1000 Mbps for the two copper
ports (1/9/and 1/10) and 1000 Mbps for ports 1/5 to 1/8. The ports, 1/1 to 1/4, support SFP 1000
Mbps (fiber) and SFP+ 10000 Mbps. The Link Speed is detected using the transceiver type. The
fiber mode supports only 1000 Mbps and is restricted to SFP+ GigE ports on the 10G IOA.
When a transceiver's capability does not support the configured settings, the CAP-1000 does not
bring up the link. You need to correct the settings or plug in a transceiver with capabilities that
match the settings.
By default, the CAP-1000 sets the Link Speed to Auto and Auto Neg is off. The CAP-1000 allows
you to set the Link Speed to 1000 Mbps and deselect the Auto Neg parameter. When doing so, the
CherryPicker Element Manager displays a warning message informs you that this configuration
might not work in some environments and is not recommended. The Link Speed values are Auto,
10, 100, and 1000.
The following table lists the valid parameters for auto negotiation for the 1G IOA and 10G IOA.

Table 11-3 GigE Line Validation

Port ID Board Type Connector Type Auto Neg Link Speed Default

1/1 - 1/4 IOA Copper cage On Auto, 10, 100, 1000 Link Speed Auto, Auto Neg On

1/1 - 1/4 IOA Copper cage Off 10, 100 There are no defaults with Auto Neg
Off.

1/1 - 1/4 IOA SFP Fiber On 1000 Link Speed 10000, Auto Neg Off

1/1 - 1/4 1IOA SFP Fiber Off 1000 There are no defaults with Auto Neg
Off.

bond0 DSP Copper cage On Auto, 10, 100 Link Speed 1000, Auto Neg On

bond0 DSP Copper cage Off 10, 100 There are no defaults with Auto Neg
Off.

1/1 - 1/4 10G IOA SFP Fiber On 1000 Link Speed 10000, Auto Neg On

150 ARRIS Enterprises, Inc.

 Configuring Auto Negotiation and Link Speed

Table 11-3 GigE Line Validation (continued)

Port ID Board Type Connector Type Auto Neg Link Speed Default

1/1 - 1/4 10G IOA SFP Fiber Off 1000 There are no defaults with Auto Neg
Off.

1/1 - 1/4 10G IOA SFP + Fiber Off 1000 Link Speed 10000, Auto Neg Off

1/1 - 1/4 10G IOA Twinax Off 1000 Link Speed 10000, Auto Neg Off

1/5 - 1/8 10G IOA SFP Copper On 1000 Link Speed 1000, Auto Neg On

1/5 - 1/8 10G IOA SFP Copper Off 1000 Not allowed

1/5 - 1/8 10G IOA SFP Fiber On 1000 Link Speed 1000, Auto Neg On

1/5 - 1/8 10G IOA SFP Fiber Off 1000 There are no defaults with Auto Neg
Off.

1/9 - 1/10 10G IOA Copper cage On Auto, 10, 100, 1000 Link Speed Auto, Auto Neg On

1/9 - 1/10 10G IOA Copper cage Off 10, 100 There are no defaults with Auto Neg
Off.

To configure auto negotiation and link speed:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Select the Ethernet port you want to configure.
3 In the Auto Neg parameter, select “On.”
Use the scroll bar to display all parameters.
4 In the Link Speed parameter, select one of the following options from the menu:
• Auto
• 10
• 100
• 1000
The options vary depending on the IOA module as well as the SFP installed on the CAP-1000.

NOTE You cannot set the speed to 1000 Mbps, and disable the Auto Neg parameter. If you set the speed to 1000
Mbps or Auto, the Auto Neg parameter is automatically set.

5 Click Apply.
6 Click Yes to continue.
The parameters are updated.

CAP-1000 Software Guide v4.0 151

Chapter 11 Configuring the Network Configuring Static Routes

Configuring Static Routes

A static route is a hard-coded path in a router or host that specifies how the router/host accesses a
certain subnet by using a specific path. It provides a means of explicitly defining the next hop from
a router/host to a particular destination. The CAP-1000 supports one gateway per Gigabit Ethernet
interface. Static routes are persistent across reboots.
To make static routes persistent, a Data Flash file named static-routes is used to store permanent
static routes per each ports. This file is reloaded by the boot scripts when the CAP-1000 is
rebooted. This file contains one static route entry per line, ethx IP address A.B.C.D
netmask A.B.C.D gw A.B.C.D, in a standard ASCII text file where:
• ethx represents the GigE port to which the route is applied: 0-3 for the IOA and egiga1 for the
management port on the DSP module.
• net A.B.C.D (dot notation) is the network of the route.
• netmask A.B.C.D (dot notation) is the netmask of the route.
• gw A.B.C.D (dot notation) is the gateway IP address.
When you add, edit, or delete the static routes using the CherryPicker Element Manager, the static-
routes file is modified accordingly.

Adding Static Routes

To add a static route:

1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Click the Static Routing link on the right side of the panel.

Static Routing

152 ARRIS Enterprises, Inc.

 Configuring Static Routes

A dialog box opens.

Create/View/Edit Static Routes

3 Click Add (green + button).

Create/View/Edit Static Routes

4 In the Network, Netmask, and Gateway fields, enter the static route parameters.
5 In the Port ID field, select the ID you want from the menu.
The IP address is entered automatically for you.
6 Click Apply.
7 Click OK.

Deleting Static Routes

You can delete a static route as long as it is not in use.

To delete a static route:

1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Click the Static Routing link on the right side of the panel.
A dialog box opens.

CAP-1000 Software Guide v4.0 153

Chapter 11 Configuring the Network Using the CAP-1000 Port Analyzer

Create/View/Edit Static Routes

3 Select the static route you want to delete.

4 Click Delete (red - button).
5 Click Apply.
6 Click OK.

Using the CAP-1000 Port Analyzer

The CAP-1000 Port Analyzer (CPAN) feature lets you analyze either Gigabit Ethernet input or
output traffic from a separate dedicated port. CPAN sends a copy of all network traffic on one IOA
port to a network that is monitoring a connection on another IOA port. CPAN is supported on all
the ports for the 1G IOA or 10G IOA.
To use CPAN, this port must be disabled on the network. Only one CPAN destination port is
allowed per CAP-1000 device.

CPAN Source Ports

A source port (the port that is monitored) can have only one corresponding monitoring destination
CPAN port. It cannot function as a CPAN destination port at the same time.
A source port can be monitored for ingress traffic (Any traffic that enters the CAP-1000 through
that port) or egress traffic (Any traffic that leaves the CAP-1000 out of that port). It is either
ingress or egress traffic, but not both at the same time. CPAN configurations are persistent through
reboots.

CPAN Destination Port

A destination port can monitor one source port at a time. Only one CPAN destination port is
allowed at a time per device. To be specified as a CPAN destination port, the port must be unused.
When the CPAN covers a port other than a 10 GigE port, a CPAN destination port is automatically
set to 1000 Mbps / Full. When covering a 10 GigE port with a 10 GigE SFP transceiver, the port is
automatically set to 10 Gbps / Full).

154 ARRIS Enterprises, Inc.

 Using the CAP-1000 Port Analyzer

A port configured as a CPAN destination port has a dedicated LED code. When a link is down, the
CPAN port has two LEDs that blink at 1Hz. When a CPAN link is up, the two LEDs blink
alternately.

Limitations
The following limitations apply to CPAN:
• SNMP is not supported.
• CPAN destination ports do not appear in program- or device-level analyses on the Analysis
tab.
• CPAN does not apply to management ports. These ports cannot be used as source or
destination ports.
• If CPAN is configured on a Primary device in CPR, it is not supported on a Protecting Backup.
device. When CPR fails over, the CPAN configuration is preserved on the Primary device, but
the Backup device does not “inherit” the primary CPAN configuration. If a Backup device has
been configured with CPAN, the CPAN setup on a Covering Backup is not applied to the
Primary devices during failbacks.
• When a port is configured as a CPAN destination port, the CAP-1000 displays the port as
CPAN. With the exception of reverting the port from a CPAN destination port to a regular port,
no other configuration, multiplex operations, or grooming operations are allowed on this port.
• CPAN is not supported on DVB-ASI ports.

Errors
Frames with Ethernet CRC errors or analog errors are discarded from the CPAN port and not
duplicated from the source. They are dropped at the MAC level. Received frames with errors are
not dropped by the CPAN EMAC core. Incorrect frames are transmitted with a “PHY” error status.
When the CPAN source and destination port operate at different speeds, the CAP-1000 posts a
warning message, “Results are not guaranteed when CPAN source and destination ports operate at
different speeds.”

Configuring CPAN

WARNING The CAP-1000 reboots when enabling or disabling CPAN on a unit that a 10G IOA.

To configure:
1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Clear (uncheck) the Port Enabled check box for the CPAN port.
3 Click the Port Analyzer link on the right side of the panel.

CAP-1000 Software Guide v4.0 155

Chapter 11 Configuring the Network Using the CAP-1000 Port Analyzer

The Port Analyzer Settings dialog box opens. If CPAN is enabled, this information is shown in the
dialog box.

Port Analyzer Settings

Table 11-4 Port Analyzer Settings

Direction Configures the port for ingress (input) or egress (output) monitoring.

CPAN Source Selects the source port.

CPAN Destination Selects the destination port

Auto Neg Toggle to enable or disable auto negotiation.

Speed When Auto Neg is enable, the Speed menu is enabled. Select the speed you want for
the port.

Enable CPAN Toggle to enable or disable CPAN.

4 Enter the required information.

Once enabled, the dialog box closes and the corresponding port under the Network tab is
highlighted in orange in the ID cell.

156 ARRIS Enterprises, Inc.

 Using the CAP-1000 Port Analyzer

CPAN

CAP-1000 Software Guide v4.0 157

Chapter 11 Configuring the Network Using the CAP-1000 Port Analyzer

158 ARRIS Enterprises, Inc.

 CHAPTER 12
Configuring ASI Ports

In This Chapter
• ASI Ports
• Viewing ASI Port Configuration
• Configuring ASI Output Ports
• Configuring ASI Input Ports
• Disabling ASI Ports

ASI Ports
This chapter explains how to view, configure, and manage asynchronous serial interface (ASI)
ports on Video input/output (VIO) cards. DVB-ASI is a serial video communications standard
defined by the DVB consortium for use in transporting MPEG-2 encoded video streams. The
standard is most commonly used to connect cable head-end equipment that transports MPEG-2
streams.
A CAP-1000 device consists of a number of physical inputs (or input ports) and physical outputs
(or output ports). Each ASI physical port can be configured as one of the following types:
• Input port (default)
• Primary output port
The ASI ports can be identified in the Setup > System tab of the CherryPicker Element Manager.
The ports appear on the rear panel of the CAP-1000. Specific information about the ASI ports
appear on the ASI subtab of the CherryPicker Element Manager.
Whenever a DVB-ASI output is enabled, a multiplex must be defined for such output. Refer to
section,“Managing ASI Input Multiplexes,”on page 265 for more information.

NOTE DVB-ASI mirrored output ports are not supported.

CAP-1000 Software Guide v4.0 159

Chapter 12 Configuring ASI Ports ASI Ports

ASI Ports

Video Input Output Module

The CAP-1000 supports DVB-ASI through the use of an optional Video Input Output (VIO)
module. When present, each port of the VIO module can be configured as an ASI primary input or
an output. By default, all ports are configured as inputs. The VIO module supports 188 and 204
bytes per MPEG input transport packet. You can view details on the VIO module on the Setup >
System > Hardware window.

VIO Modules

160 ARRIS Enterprises, Inc.

 Viewing ASI Port Configuration

NOTE The VIO module is optional in the CAP-1000. The CAP-1000 can operate without any VIO cards plugged
into the device.

LEDs
The LEDS will reflect the configuration and status of the VIO ports. Each VIO port has two LEDs.
The top LED represents the left port. The bottom LED represents the right port. When the LED is
green, then the VIO port is configured as an input and is receiving MPEG TS packets. When the
LED is Steady Amber, the port is configured as an output. Blinking Amber indicates an Internal
Hardware error.

NOTE SDI input modes on the VIO card are NOT supported in this release.

Connections
The CAP-1000 automatically detects the connections and displays them in numerical order based
on their slot ID and configuration. A default name is assigned to the port using the following
format: <slot>/<port> where:
• <slot> is the slot label, namely, 3 and 4, as seen on the VIO card on the back of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
You can change the port name.

NOTE The same output name can be carried by several output ports.

Active Lines
An ASI input port is either “Active” or “Not Responding.” An ASI line is active when the
CAP-1000 hardware declares that the line is active. An active line does not necessary have any
incoming MPEG streams or management traffic. When a system is new out of the box, the ASI
lines are not configured/enabled. You must plug in a cable and get an active port.

Viewing ASI Port Configuration

The CAP-1000 supports either four or eight BNC connectors, depending on whether one or two
VIO modules are installed. Each port is programmable as an input or an output.

To view ASI port configuration:

 From the CherryPicker Element Manager, click Setup > System > ASI.
ASI port parameters display in the bottom panel.

CAP-1000 Software Guide v4.0 161

Chapter 12 Configuring ASI Ports Viewing ASI Port Configuration

ASI Port Parameters

Table 12-1 ASI Port Parameters

Link Shows the port status:

—Active (green)
—Down (red)

Type Shows the port configuration: Input or Output.

Note: For input ports, only the Type and Name columns are editable. When an input
port is changed to an output port, all columns beyond the Mode column are
enabled.

ID Shows the default ID assigned to the port in the format: <slot>/<port>.

Name Shows the default name assigned to the port in the format: <slot>/<port>, or a
user-specified name.

Mode Shows the output port mode:

• 64 QAM (6 Mhz)
• 256 QAM (6 Mhz)
• 64 QAM (8 Mhz)
• 256 QAM (8 Mhz)
• ATSC
• Disabled
• Custom
Note: For Custom mode, all rate columns are editable. For all QAM modes, the Total
Rate column is read-only, and the other columns are editable. For ATSC mode, the
Inter Byte Gap and Byte Per Packet columns are read-only.

162 ARRIS Enterprises, Inc.

 Configuring ASI Output Ports

Table 12-1 ASI Port Parameters

Total Rate (Mbps) Shows the total rate for the output port in megabits per second. This parameter is
read-only for QAM and ATSC modes.

Res Rate (Mbps) Shows the reserved rate for output ports.

Avail Rate (Mbps) Shows the available rate for output ports.

Inter Byte Gap Shows the Inter Byte Gap (0, 1, 2, 3) for output ports. This parameter is disabled for
ATSC mode. The default value is 0.

Byte Per Packet Shows the Bytes Per Packet (188 or 204) for output ports. This parameter is read-
only for ATSC mode.

Configuring ASI Output Ports

By default, an ASI port is configured as an input.

WARNING Before changing the port type from input to output, you must disconnect the feed connected to this
port. Otherwise, the cable driver may be damaged. The CherryPicker Element Manager warns you
before this type change takes place.

When an input port is changed to an output, the following actions occur:

• All streams groomed or passed from this input are dropped.
• All tables are refreshed.
• The user-selected Configuration file is applied.
• The CherryPicker Element Manager issues a warning before the operation is completed that
all the groomed streams are dropped. You are instructed to disconnect the feed on the input to
prevent potential cable damage.
• No alarms are generated.
When a port is configured as a primary output port, you can define the output mode parameters
defined in the Table 12-2. These rates are maintained with the accuracy of +/- 2.5 ppm. The total
line rate in this table is fixed for all output modes, except for the custom mode. The default output
mode is disabled.

Table 12-2 ASI Output Port Configuration

Label
Total MPEG Line Rate (Mbps)
Default Total Reserved Rate
Range Default (Mbps)

QAM64 (6 MHz) 26.97035 26.97 0.5

QAM256 (6 MHz) 38.81070 38.811 0.8107

CAP-1000 Software Guide v4.0 163

Chapter 12 Configuring ASI Ports Configuring ASI Output Ports

Table 12-2 ASI Output Port Configuration (continued)

QAM64 (8 MHz) 38.44047 38.44 0.7

QAM256 (8 MHz) 51.25396 50.68 1.0

ATSC 19.392658 19.393 0.1

Custom 0.5425 - 214 (*) 20 0.1

Disabled N/A N/A N/A

Notes:
(*) The actual maximum rate depends on the selected inter-byte gap (IBG) and is given by the following expression:
214/ (IBG+1), Mbps. 214 Mbps is the Maximum capacity of a DVB-ASI line.
The minimum output rate is 0.5.

With respect to these ASI parameters, please note the following:

• For custom mode, all rate columns are editable.
• For all QAM modes, the Total Rate column is read only; all other columns are editable.
• For ATSC mode, the Inter Byte Gap and Byte Per Packet columns are read only.
• For input ports, only the Type and Name columns are editable.
• When an input port is changed to output, all columns after the Mode column are enabled.

To configure an ASI output port:

1 From the CherryPicker Element Manager, click Setup > System > ASI.
ASI port parameters display in the bottom panel.
2 Locate the ASI port with the status of Not Responding that you want to configure.
3 Under Type, select Output from the menu.

164 ARRIS Enterprises, Inc.

 Configuring ASI Output Ports

Output Port Type

4 Double-click the Mode parameter.

5 Select a mode for the output port:
• 64 QAM (6 Mhz)
• 256 QAM (6 Mhz)
• 64 QAM (8 Mhz)
• 256 QAM (8 Mhz)
• ATSC
• Custom
6 Configure any other applicable port parameters you want.
Refer to Table 12-1 on page 162 for a description of the parameters.
7 Click Apply.
An information window opens.

Information

CAP-1000 Software Guide v4.0 165

Chapter 12 Configuring ASI Ports Configuring ASI Input Ports

WARNING Ensure that the feed is disconnected from the port before continuing.

8 Review the messages and then click OK.

The Import Configuration File window opens.

Import Configuration File

9 Select the Other option.

NOTE Only configuration files in the /usr/cp/Config directory are displayed.

10 Select the file you want to apply.

The file name appears in the Current Configuration File field.
See Chapter 16, “Managing Configuration Files” for more information.
11 Click OK.
The ASI port is updated.
12 Reconnect the feed to the ASI port.
13 After configuring the ASI output port, you also need to define a multiplex for the output. Refer to
Chapter 14, “Configuring Multiplexes” for more information.

Configuring ASI Input Ports

When an output port is changed to an input, the following actions occur:
• All streams groomed or passed to this output are dropped.
• All tables are refreshed.
• The CherryPicker Element Manager issues a warning before the operation is completed that
all the groomed or passed streams are deleted.
• No alarms are generated.
• The CAP-1000 counts the input ports in the Active and Input Mux: Inactive counters in the Status bar.

166 ARRIS Enterprises, Inc.

 Disabling ASI Ports

To configure an input ASI port:

1 From the CherryPicker Element Manager, click Setup > System > ASI.
ASI port parameters display in the bottom panel.
2 Locate the ASI port you want to configure.
3 Under Type, select Input from the menu.
4 Click Apply.
An information window appears.

Information

5 Review the messages and then click OK.

The ASI port is updated. All parameters, except for Name, are disabled.

Disabling ASI Ports

You can disable a primary output port, but not an input port. When an ASI primary output port is
disabled, the following actions occur:
• All the groomed or passed tables and programs are deleted.
• The disabled port continues to send the DVB-ASI “comma” symbols, but no MPEG packets,
including the null packets, are sent.
• When re-enabled, the disabled primary port becomes an active primary output port.

To disable an ASI port:

1 From the CherryPicker Element Manager, click Setup > System > ASI.
ASI port parameters display in the bottom panel.
2 Select the active ASI port you want to disable.
3 Double-click the Mode parameter.
4 Select Disabled.

CAP-1000 Software Guide v4.0 167

Chapter 12 Configuring ASI Ports Disabling ASI Ports

Disabled Mode

5 Click Apply.
An information window opens.

Information

6 Review the messages and then click OK.

The ASI port is disabled.

168 ARRIS Enterprises, Inc.

 CHAPTER 13
Content Picking

In This Chapter
• Content Picking
• Component Tree
• Mux Window
• Grooming Window
• Diagram View
• Tabular View
• Timeline View
• Context Menu
• Keyboard Shortcuts
• Managing Panels
• Filtering
• Ad Muxes
• Alarm Reporting

Content Picking
Clicking Content Picking > Mux displays the Mux window which lets you configure input and
output multiplexes.

CAP-1000 Software Guide v4.0 169

Chapter 13 Content Picking Content Picking

Content Picking—Mux

Clicking Content Picking > Grooming displays the Grooming window where you groom
programs, elementary streams, and files.

Content Picking—Grooming

170 ARRIS Enterprises, Inc.

 Component Tree

Component Tree
The Component Tree, located on the left side of the window, provides a hierarchical display of
hardware components and inputs that can be groomed. Each component is depicted as a node of
the Tree.
When the Mux tab is selected, the Tree displays the CAP-1000 device, ports, multiplexes,
programs, streams, tables, and stat mux pools (SMP). Selecting one of these nodes causes related
information to display in the right panel. When the Grooming tab is selected, the Component Tree
displays inputs for use in grooming.

Content Picking—Component Tree

The Component Tree has a separate scroll bar to display all nodes in the Tree.

Component Tree Nodes

Table 13-1 describes the nodes in the Component Tree.

Table 13-1 Component Tree Nodes

Node Description

Active CAP-1000 device

Note: When Controller is inactive (disconnected from Core), the node label is “not responding.”

Active Gigabit Ethernet (GigE) input port

CAP-1000 Software Guide v4.0 171

Chapter 13 Content Picking Component Tree

Table 13-1 Component Tree Nodes (continued)

Node Description

Active Gigabit Ethernet (GigE) output port

Active ASI input port

Active ASI output port

Active multiplex

Mirrored output multiplex

Force to backup program

Force to slate

Program placeholder created by a configuration file

Groomed program

Groomed backup program

Groomed program with an encrypted stream

Encrypted program is forced to backup

Video stream

Audio stream

Data stream (such as EBIF or EISS)

Multiple tables

Stat mux pool (SMP)

Table

Standard or custom video files such as MPEG-4 file, MPEG-2 file, black file, colorbars, or slates.

172 ARRIS Enterprises, Inc.

 Component Tree

Component Tree Hierarchy

Device
The root of the hierarchy is the CAP-1000 device.

ASI Ports
The CAP-1000 consists of a number of physical inputs and outputs that are referred to as ports or
lines. An ASI port is a connection on a VIO card. VIO cards are optional in the CAP-1000. The
CAP-1000 supports the digital video broadcast asynchronous serial interface (DVB-ASI) video
card with four- or eight-BNC connectors.
The CAP-1000 is able to operate without any VIO cards plugged into the device. When a VIO card
is present, you can configure each port as an ASI input or output. By default, all ports are
configured as inputs.
Each VIO port has two LEDs. The LEDs on the ports indicate the configuration and status of the
VIO ports. The top LED represents the left port. The bottom LED represents the right port. When
the LED is green, then the VIO port is configured as an input and is receiving MPEG TS packets.
When the LED is Steady Amber, the port is configured as an output. Blinking Amber indicates an
internal hardware error.
An input ASI port is either “Active” or “Not Responding.” When a port is active, it can send data,
and it can receive data. When a port is down, it cannot send or receive data.
The CAP-1000 assigns a default name to the port so it is easily identified in the software interface.
The default name uses the following format: <slot>/<port> where:
• <slot> is the slot label, namely, 3 and 4, as seen on the VIO card on the back of the CAP-1000.
• <port> is the port number, such as 1, 2, or 3.
The numbering applies to all of the interfaces of the CAP-1000 device, starting from front to back,
top to bottom, and left to right.

Gigabit Ethernet Ports

The CAP-1000 supports a 1-Gigabit Ethernet Input Output Adapter (1G IOA) or a 10-Gigabit
Ethernet Input Output Adapter (10G IOA). The 1G IOA and the 10G IOA are exclusive and a
system can only contain one of them.
The 1G IOA has four bi-directional Gigabit Ethernet ports. A port can use either an optical or an
electrical connector, but not both at the same time. The physical interface for the electrical
connection is 10/100/1000BaseT. The physical interface for the optical connection are 1000BASE-
SX or 1000BASE-LX.
The CAP-1000 provides management and MPEG packet traffic via any of the four ports on the
IOA. A port can carry MPEG traffic or it can used as a management port (or both simultaneously).
The ten ports on the 10G IOA can be used for MPEG traffic input or outputs.

CAP-1000 Software Guide v4.0 173

Chapter 13 Content Picking Component Tree

A GigE port is either “Enabled” or “Disabled.” When a port is enabled, its parameters can be
configured, it can send data, and it can receive data. When a port is disabled, it cannot be
configured, nor can it send or receive data.
On the 1G IOA, the Link Speed is set to: Auto, 10 Mbps, 100 Mbps, 1000 Mbps for copper mode
and 1000 Mbps for fiber mode. On the 10G IOA module, the Link Speed is: Auto, 10 Mbps, 100
Mbps, 1000 Mbps for the two copper ports (1/9/and 1/10) and 1000 Mbps for ports 1/5 to 1/8. For
ports 1/1 to 1/4, the Link Speed is detected using the transceiver type and there is no selection
available to the user. If the GigE line is down, the status is “Not Responding.”
The CAP-1000 automatically detects the connections and displays them in numerical order based
on their slot ID and configuration. A default name is assigned to the port using the following
format: <slot>/<port>.

Multiplexes
Each input and output port consists of multiplexes. A multiplex is a standard MPEG transport
stream. The CAP-1000 assigns an internal ID to a multiplex. A default name, Mux_<ID> is
assigned to the multiplex. For example, Mux_0004. You can edit this name, if required.

Tables and Programs

Each multiplex consists of tables and programs. The tables include the common Program Specific
Information (PSI) tables, as well as other multiplex-wide tables, as defined in the compression
systems supported by the CAP-1000.
PSI is metadata about a program (channel) and part of a MPEG transport stream. The PSI data
contains five tables:
• Program Association Table (PAT)
• Conditional Access Table (CAT)
• Program Map Table (PMT)
• Network Information Table (NIT)
• Time and Date Table (TDT) and Time Offset Table (TOT)
PSI is carried in the form of a table structure. The table structure can span multiple transport
stream packets. Adaptation field also occurs in TS packets carrying PSI data. The PSI data is never
scrambled so that the decoder at the receiving end can easily identify the properties of the stream.
Each table (or elementary stream) in a transport stream is identified by a 13-bit packet ID (PID).
The PAT, CAT and TDT tables are associated with predefined PID. Multiple, independent PMT
tables may exist in a stream, such as user-defined PID numbers (PES packets). PMT table PIDs are
defined in the PAT, and are the only PIDs defined there (PES PIDs are defined in the PMT).
Each table has predefined structure.
The default name of a program is
<LineID>_<Program_Number>_[<extracted_input_program_name>]. For example, 1/1_20.

174 ARRIS Enterprises, Inc.

 Component Tree

The <extracted_input_program_name> is used only in the case where the CAP-1000 software can
extract the input program name from the source. For example, 3/3_12_CNN. The CAP-1000
software allows up to 95 groomed programs per output transport multiplex.
For the special case of SCTE 18, the CAP-1000 creates a blank Emergency Alert Message (EAM)
table entry for every input multiplex.

Elementary Streams
Each program consists of one or more elementary streams including video, audio, and data
streams. An input program may have an arbitrary number of elements (up to the MPEG limits).
An output program can also have only audio and data streams. In this case, the maximum number
of streams per program depends on many factors, including the total number of filtered input PIDs,
the multiplex type, the number of passed tables, and the number of programs. The maximum
number is 4096. This is a per-device limit.

Files
In addition to programs and elementary streams, it is also possible to groom a file to the output. A
file refers to a custom MPEG-2 slate, MPEG-4 slate, black file, colorbars, or a custom audio file.
You can use any valid MPEG video file, such as PAL colorbars, a station logo, or an intermission
announcement (such as, “Please Standby”), and groom it to an output program of your choice
using the CherryPicker Element Manager.

Slates
In case of a backup failure. the CAP-1000 supports a combination of a video file only, video file
and audio files, or video files and audio live streams to be custom groomed as a single output
program. This is referred to as a “custom slate program.” A slate can be defined at the device-,
multiplex-, or program-level. The custom video and audio files are stored on the Data Flash.

Ad Mux
Buttons that lets you show or hide multiplexes that are streaming ads.

Managing the Component Tree

You can view the Component Tree in collapsed or expanded mode. It is also possible to select
individual nodes and expand them for greater detail. For example, moving the mouse pointer over
a node causes a pop-up label to display the name of the node.

To manage the Component Tree:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 To expand a node, click .
3 To collapse a node, click .
4 To identify a node, move the mouse over the node.

CAP-1000 Software Guide v4.0 175

Chapter 13 Content Picking Mux Window

A tool tip for the selected node pops up. If a program is selected, the tool tip shows the program
level descriptors (if any). If a elementary stream is selected, the tool tip shows the stream level
descriptors (if any).

Content Picking—Component Tree Tool Tip

Mux Window
The Mux window is accessed by clicking Content Picking > Mux in the CherryPicker Element
Manager. This window lets you:
• Create, delete, and modify input and output multiplex configurations for GigE multiplexes
• Import, export, edit, and apply configuration files for GigE multiplexes
• Modify input and output multiplex configurations for ASI multiplexes
• Delete output programs for both GigE and ASI multiplexes
• Assign recoders to output programs on GigE and ASI multiplexes
• Define and manage stat mux pools (SMP)
• Define and manage PSIP for ATSC output multiplexes, and configure TVCT or CVCT for
each program
• Define NIT and TOT tables for DVB output multiplexes

176 ARRIS Enterprises, Inc.

 Mux Window

Mux Panels
The Mux window contains the following panels:
• Component Tree
• Input/Output mux panels
• Programs/Tables panels

Component Tree
Input/
Output Mux
panels

Programs/
Tables panels

Mux

Table 13-2 Mux Panels

Component Tree Provides a hierarchical display of hardware components and inputs that can be
groomed through a CAP-1000. Each component is depicted as a node of the Tree. See
section,“Component Tree,”on page 171 for more information.

Ad Mux • Show—Shows output multiplexes that are streaming content from an ad server.
• Hide—Hides output multiplexes that are streaming content from an ad server.
See Chapter 24, “Enabling Digital Program Insertion,” for more information.

Input Mux When a GigE or ASI input multiplex is selected in the Component Tree, information
about the corresponding mux appears in the Input Mux panel on the right side of the
window. The columns in this panel can be sorted in ascending or descending
alphabetical or numeric order. See Chapter 14, “Configuring Multiplexes” for
more information.

Output Mux When a GigE or ASI output multiplex is selected in the Component Tree, information
about the corresponding mux appears in the Output Mux panel on the right side of the
window. The columns in this panel can be sorted in ascending or descending
alphabetical or numeric order. See Chapter 14, “Configuring Multiplexes” for
more information.

CAP-1000 Software Guide v4.0 177

Chapter 13 Content Picking Mux Window

Table 13-2 Mux Panels (continued)

Programs Shows programs (groomed or not groomed) on a selected output mux. Shows programs
in a mux when an input mux is selected. See Chapter 18, “Grooming Programs”
for more information.

Tables Shows PSI/SI/PSIP tables in the selected input or output mux. See Chapter 14,
“Configuring Multiplexes” for more information.

Selecting a port node in the Component Tree causes the Mux panel to display on the right. This
panel shows a list of muxes for the selected GigE or ASI port. The view is split in two parts; the
top part shows the list of muxes and bottom part shows the programs and tables associated with the
mux.

Content Picking—Output Mux Panel

NOTE The input line and output line correspond to the same physical port, but they are displayed separately in the
Component Tree to let you manage inputs and outputs separately.

Information that displays in the Multiplex panel differs, depending on whether the selected node is
a GigE or an ASI port. See Chapter 14, “Configuring Multiplexes” for a description of these
multiplex parameters.

Mux Toolbar
The toolbar provides functions for importing, exporting, and editing the configuration file for a
selected input or output mux. This feature is supported for both GigE and ASI ports and their
muxes.

178 ARRIS Enterprises, Inc.

 Mux Window

Table 13-3 Mux Toolbar

Icon Description

Imports the configuration file for the selected mux.

Exports a configuration file to the selected mux.

Opens the configuration file for viewing or editing the selected output
mux.

See Chapter 16, “Managing Configuration Files,” for more information on configuration files.

Showing/Hiding Columns
The Show/Hide Columns icon ( ) in the upper right corner of the Mux window enables you to
manage columns in the Component Tree.

To show/hide columns:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Click the Show/Hide Columns icon.

Content Picking—Show/Hide Columns

CAP-1000 Software Guide v4.0 179

Chapter 13 Content Picking Grooming Window

3 Do one of the following:

• To clear all check boxes, click Clear.
• To hide a column, clear the check box.
• To display a column, select the check box.
• To use the default settings, click Default.
4 Close the window.

Dragging Columns
You can reposition columns by holding down the left mouse button while clicking on a table
header.

Content Picking—Dragging Columns

Grooming Window
The Grooming window is accessed by clicking Content Picking > Grooming in the CherryPicker
Element Manager. It enables you to perform the following tasks:
• Groom one or more programs, elementary streams, files, or slates by drag and drop
• Groom and create output multiplexes and/or programs at the same time
• Configure definitions for static grooming
• Configure definitions for dynamic grooming with start date/times and end date/times
• Recode programs for rate shaping
• Add or drop grooming definitions

180 ARRIS Enterprises, Inc.

 Grooming Window

• Add or delete programs

• Add or delete elementary streams or files in grooms
• Configure backup streams for failover support
• Enable or disable triggering events for grooming definition
• Manage alarms for an output multiplex or output program
• View, filter, delete, and clear alarms

Grooming

When the Grooming window is displayed, the Component Tree shows muxes with MPEG traffic.

CAP-1000 Software Guide v4.0 181

Chapter 13 Content Picking Grooming Window

Grooming Menu Bar

The menu bar at the top of the window provides commands and options for managing a groom
operation. Table 13-4 describes the component of the menu bar.

Grooming Menu Bar

Table 13-4 Grooming Menu Bar

Output Line Select the output port.

Output Mux Selects the output mux(es). The options are: All Muxes, All SPTS Muxes, All MPTS
Muxes, or a specific mux. The contents of the Output panel changes, depending on the
selection.

Programs Shows the number of program placeholders in the Output panel.

Groomed Shows the number of groomed programs in the Output panel.

Grooming Views
The Grooming window provides three views, which are used to perform different grooming tasks.
The views are:
• Diagram
• Tabular
• Timeline
The views are accessed by clicking a View button in the Grooming window.

Grooming Views

182 ARRIS Enterprises, Inc.

 Grooming Window

Table 13-5 Grooming View Buttons

Displays the Diagram view with enables multiple drag-and-drop grooming of programs, elementary
streams, or files to an output multiplex or output program in diagram.

Displays the Tabular view which enables multiple drag-and-drop grooming of programs, elementary
streams, or files to an output multiplex or output program in tabular view.

Displays the Timeline view which shows programs groomed to a specific multiplex over a given time
interval.

Grooming Icons
Table 13-6 describes the icons that can appear in Grooming window.

Table 13-6 Grooming Icons

Icon Description

Parameter selected for deletion, but not applied

Parameter edited, but not applied

Active Ethernet input port

Active Ethernet output port

Active ASI input port

Active ASI output port

Active multiplex

Output program placeholder

Mirrored output multiplex

Force to backup program

Force program or encrypted program to slate

Groomed program currently playing

CAP-1000 Software Guide v4.0 183

Chapter 13 Content Picking Grooming Window

Table 13-6 Grooming Icons (continued)

Icon Description

Groomed program not playing (scheduled to be played in the future)

Program forced to backup via PRED

Groomed encrypted program currently playing

Groomed encrypted program not playing (scheduled to be played in the future)

Encrypted groomed program auto-switched to backup via PRED

Groomed program manually forced to backup via PRED or Multiplex Redundancy (MRED)

Encrypted groomed program manually switched to backup via PRED or MRED

Ad server is not connected

Ad server is connected and an ad is playing

Output program is connected to an ad server

Video stream

Audio stream

Data stream (such as EBIF or EISS)

Tables

Stat mux pool

Table

Slate is defined ,but there no groom on the output program (gray)

Slate is defined and the groom exists on the output program (red)

Slate is defined, a groom exists on the output program, and the slate is playing (orange). This icon
displays when the primary or backup file groom is currently playing slate.

184 ARRIS Enterprises, Inc.

 Grooming Window

Table 13-6 Grooming Icons (continued)

Icon Description

PIDs have not been passed (container is empty).

PIDs have been passed

Drag-and-Drop Grooming
When a specific multiplex is selected in the Output Mux menu, the “Drag Input Here” bar appears
in the window. Use this bar to groom programs to a specific output mux.

Grooming Drag and Drop

This function is available in the Diagram and Tabular Views.

Grooming Tool Tips

Hovering the mouse pointer over the Grooming Definitions, Program Intervals, Alarms, Primary
Streams, Backup Streams, or Slate Component panels displays a yellow, pop-up tool tip with help
for performing a procedure.

CAP-1000 Software Guide v4.0 185

Chapter 13 Content Picking Diagram View

Grooming Pop-up Tool Tip

Diagram View
Clicking in the Groom window displays the Diagram view. This view contains the
following panels:
• Component Tree
• Output
• Properties
• Grooming Definitions/Program Intervals/Alarms
• Primary Streams/Backup Streams/Slate Component
• Streams/Tables
When working with programs, elementary streams, or files, the Grooming Definitions/Program
Intervals/Alarms, Primary Streams/Backup Streams/Slate Component, and Streams/Tables panels
display in this view.

186 ARRIS Enterprises, Inc.

 Diagram View

Component Tree

Output panel

Properties panel

Grooming
Definitions/Program
Intervals/Alarms panels

Primary Streams/Backup
Streams/Slate Component
panels

Descriptors panel

Diagram View for Primary Streams/Backup Streams/Slate Component

When working with passed PIDs or tables, the Streams/Tables panels display under the Grooming
Definitions panel.

CAP-1000 Software Guide v4.0 187

Chapter 13 Content Picking Diagram View

Component Tree

Output panel

Properties panel

Grooming
Definitions/Program
Intervals/Alarms
panels

Streams/Tables
panels

Diagram View for Streams/Tables

The panels are described in Table 13-7.

Table 13-7 Diagram View Panels

Component Tree Provides a hierarchical display of hardware components and inputs that can be
groomed through a CAP-1000. Each component is depicted as a node of the Tree. See
“Component Tree” for more information.
Output Selects the output multiplex or program for groomed programs, elementary streams, or
files. Also indicates if a backup program has been specified, a recoder has been
reserved, or ad insertion has been configured for the program. See Chapter 18,
“Grooming Programs” or Chapter 19, “Grooming Elementary Streams”
for more information.

Properties Configures the groomed program or elementary stream.

Drag Input Here Creates and grooms programs via drag-and-drop for a selected mux. If you do not want
to create a new program, then drag and drop an input to an existing output program.

Grooming Definitions Shows grooming ID, Type, Description, Level, and ETV Filter definitions for the selected
groom.

Program Intervals Shows the program (including ads) playing now and scheduled in the future.

188 ARRIS Enterprises, Inc.

 Diagram View

Table 13-7 Diagram View Panels (continued)

Alarms Shows current alarms with controls for filtering so that only some alarms are shown.
Enables you to clear and delete alarms. See Chapter 35, “Managing Alarms
and Logs,” for more information.
Primary Streams/Backup Shows the programs, elementary streams, or files groomed to output for primary or
Streams backup streams (if configured for redundancy). See Chapter 29, “Configuring
Program Redundancy”for more information.
Slate Component Shows details about a slate stream (MPEG-2 video, MPEG-4-video, or MPEG-4 audio) if
defined.

Descriptors Displays the stream-level descriptors for the selected grooming component. Stream
level descriptors are passed through from the input elementary stream to the output
elementary stream. You can add or delete descriptors for extra output streams.

Streams/Tables Shows elementary streams associated with PID passing. Tables show common PSI/SI
tables associated with PID passing. See Chapter 23, “Passing PIDs” for more
information.

Output Line Menu

The panels in the Diagram view change, depending on the option you select from the Output Line
menu. Selecting a specific output line (port) displays muxes associated with that port.

Output Line Menu

Output Mux Menu

The panels in the Diagram view change, depending on the option you select from the Output Mux
menu. If you select the All Muxes, All STPS Muxes, or All MPTS Muxes option, all multiplexes
for that selection display in the Output panel, along with program placeholders, if any, that are
associated with a configuration file.

CAP-1000 Software Guide v4.0 189

Chapter 13 Content Picking Diagram View

Output Mux Menu—All Muxes

If you select a specific multiplex, the Output, Grooming Definitions/Program Intervals/Alarms,

Primary Streams/Backup Streams/Slate Component, and Descriptor panels display for that mux.

Output Mux Menu—Specific Mux

Actions
With the Diagram view, you can drag an input program, elementary stream, or file from the
Component Tree and drop it on an output multiplex, groomed program, or program placeholder in
the Output panel. This action adds the program, stream, or file to the grooming definition.

190 ARRIS Enterprises, Inc.

 Diagram View

Drag-and-Drop Grooming

When the groom operation is in process, and has not yet been applied, the Edit ( ) icon appears
in the Output panel. This icon indicates that your selections have not yet been applied. When you
click the Apply button your changes are applied and the icon is removed.
If you later change your mind about the groom, you can delete it from the Program by right-
clicking the Program icon and selecting Delete Program or Delete Grooming Definition(s) from
the Grooming Context menu. Similarly, you can delete a slate using the Delete Slate Definition
command. See section,“Context Menu,”on page 213 for more information.

CAP-1000 Software Guide v4.0 191

Chapter 13 Content Picking Diagram View

Grooming Context Menu

Alternatively, you can discard your changes by clicking the Discard button. When you do so, the
Delete ( ) icon appears. When you click the Apply button, the icon is removed.

Parameters
You can configure parameters for grooming operations in the Diagram view. For example, you can
configure the start/end date and time for a grooming definition. All parameters displayed in green
highlight are configurable.

192 ARRIS Enterprises, Inc.

 Diagram View

Date/Time Properties

NOTE The parameters that display in the Diagram view differ depending on whether you select All Muxes, All
SPTS Muxes, All MPTS Muxes, or a specific Mux. The following illustration shows parameters for a
specific mux.

Table 13-8 Diagram View Grooming Parameters

Output Panel

Mux Info Shows the name assigned to the multiplex.

Primary Shows the primary program name.

Backup Indicates if a program has been configured for backup, if any.

Slate Indicates if a slate has been configured for backup, if any.

DPI Indicates if digital program insertion (DPI) is active

Service Name Specifies the name of the output program.

Program Number Shows the program number assigned by the CAP-1000.

CAP-1000 Software Guide v4.0 193

Chapter 13 Content Picking Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Recoder Indicates if a recoder has been assigned. The options are:

• No
• HD MPEG-2
• SD MPEG-2
• HD MPEG-4/AVC
See section,“Managing Recoders,”on page 451 for more information.

EBIF Enables EBIF at the output program level when the required license key is
installed. See Chapter 26, “Managing EBIF” for more information.

CCC Enables the CAP-1000 to carry closed captioning conversion (CCC) information
in SD or HD MPEG-2 user video streams for DTV. See section,“Managing
Closed Captioning Conversion,”on page 306 for more information.
CALM Enables volume leveling via the Commercial Advertisement Loudness
Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters
of groomed AC-3 audio streams. See section,“Enabling CALM,”on
page 402 for more information.
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.

Properties Panel

Date/Time Shows the start/end date and time for the grooming definition. These
properties can only be configured when creating a new groom. The properties
cannot be configured after a program is groomed and changes have been
applied.

Start Shows the start date and time for a groom.

End Shows the end date and time for a groom.

Recoding Shows recoding properties for the selected grooming definition.

Min Bit Rate (Mbps) Specifies a video bit rate floor that the CAP-1000 is not to drop below when
recoding video streams (in megabits per second). See section,“Managing
Recoders,”on page 451 for more information.
Max Bit Rate (Mbps) Specifies a video bit rate ceiling that the CAP-1000 is not to go above when
recoding video streams (in megabits per second).

Priority Specifies the degree of recoding for a recodable video stream. The priority
levels characterize the relative amount of recoding that will be done for
various video streams in a multiplex and is used to control the rate of the
multiplex.
Ten priority levels are defined. Level 1 indicates the lowest priority stream
(maximum amount of recoding) and Level 10 indicating the highest priority
stream (minimum amount of recoding), with increments of 1. The priory levels
can be modified at any time, even after a program is created and a stream is
being passed to the output.

194 ARRIS Enterprises, Inc.

 Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Backup Configures backup streams for failover support. See Chapter 29,
“Configuring Program Redundancy” for information.
Error Period Specifies the length of time during which the primary cannot recover from
error. If the primary cannot recover by the end of the interval, switching to
backup occurs. If the primary can recover, no switching occurs. The options
are: Min 1 second (in 1 second increments) / Max 100 seconds. The default is
2 seconds.

Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup program to
switch over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup program to
switch over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup program to switch over if any video
stream underflows.
• First Audio Only—enables the backup program to switch over if the first
audio stream underflows.

Switch on Underflow Configures primary to backup switchovers. The options are:

• Immediate—switching to backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Auto Switchback Specifies whether the backup program switches back to the primary program
when the error condition ends.
• True—switches back to the primary program when the error condition
ends.
• False—continues playing out the backup program after the error condition
ends.

Error Free Period Specifies the length of time in which the primary program must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
program. The CAP-1000 remains with the backup program instead. The
options are: Min 7 seconds / Max 100 seconds. The default is 12 seconds (in
1-second increments). The longer the period of time, the more certain you can
be that the primary program is error free.

Slate Level Shows the grooming level for a slate.

Slate Error Period Specifies the length of time during which the primary slate cannot recover
from error. If the primary cannot recover by the end of the interval, switching
to the backup slate occurs. If the primary can recover, no switching occurs.
The options are: Min 1 second (in 1 second increments) / Max 100 seconds.
The default is 10 seconds.

CAP-1000 Software Guide v4.0 195

Chapter 13 Content Picking Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Slate Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup slate to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup slate to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup slate to switch over if any video stream
underflows.
• First Audio Only—enables the backup slate to switch over if the first audio
stream underflows.

Slate Switch on Underflow Configures backup to primary slate switchovers. The options are:
• Immediate—switching to the backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Slate Auto Switch Back Specifies whether the backup slate switches back to the primary slate when
the error condition ends.
• True—switches back to the primary slate when the error condition ends.
• False—continues playing out the backup slate after the error condition
ends.

Slate Error Free Period Specifies the length of time in which the primary slate must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
slate. The CAP-1000 remains with the backup slate instead. The options are:
Min 7 seconds / Max 100 seconds. The default is 12 seconds (in 1-second
increments). The longer the period of time, the more certain you can be that
the primary slate is error free.

Service Properties The Service Properties are only enabled for grooming DVB programs. If you are
grooming MPEG-2 streams or DigiCipher II streams, these properties are
disabled. If you do not enter anything, then the input Service Provider Name
and Service Name are used.

Service Provider Name Shows the Service Provider Name passed from the input (if the input has a
Service Provider Name in the DVB SDT). You can override this name in the
output SDT.

Service Name Shows the Service Name passed from input (if the input has a Service Name
in the DVB SDT). You can override this name in the output SDT.

Grooming Definitions Panel

ID Shows the default grooming definition ID.

Type Shows the specified grooming type.

196 ARRIS Enterprises, Inc.

 Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Description Specifies a description for the groom.

Level Shows the grooming level. The value is 0 for static grooms and 1 (or above) for
scheduled grooms.

Status Indicates if the grooming definition is valid.

Use Trigger Enables grooming input programs based on a schedule. Automatically enabled
for drag-and-drop grooms.If no triggering event has been defined, an error
window opens. See Chapter 21, “Using Trigger Events” for more
information.

Trigger(s) Selects the pre-configured trigger for this groom. At least one event is
required to complete this action.

Duration Specifies the duration of the triggering event.

CUE Insertion Enables or disables the insertion of CUE streams per SCTE 35. When CUE
Insertion is enabled, an extra output stream is automatically added in the GUI,
and the original (network) cue stream is prevented from being output. See
section,“SCTE 35 Cue Insertion,”on page 483 for more information.

Pass Streams Enables encrypted streams to be passed or groomed. Pass Streams is enabled
by default.

Program Descriptors Specifies how to handle program descriptors: at the output:

• Do Not Pass—Does not pass the program descriptors to output.
• Auto Pass Exclude CA—Passes the program descriptors, but exclude
Conditional Access (CA) at output.
• Auto Pass Include CA—Passes the program descriptors and CA at output.
• Custom—Adds a custom program descriptor tag. Only programs with this
tag are passed to output.
• Edit Custom—Edits the program descriptors.

Program Intervals Panel

Start Time Shows the specified start date and time.

End Time Shows the specified end date and time.

ID Shows the default grooming definition ID.

Description Shows the description of the associated grooming definition. By default, for
program grooming, the description is the input program's name. For custom
grooming, the description is “Custom.”

Input Line Shows the input line for the groom.

Mux Shows the multiplex for the groom.

Program For program grooming, shows the input program's name. For custom
grooming, shows the groomed input pids and their type.

CAP-1000 Software Guide v4.0 197

Chapter 13 Content Picking Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Alarms

Show • Critical—Filters on a service-affecting condition has occurred and an

immediate corrective action is required. Such a severity can be reported,
for example, when a managed object becomes totally out of service and its
capability must be restored.

• Major—Filters on a service-affecting condition has developed and an

urgent corrective action is required. Such a severity can be reported, for
example, when there is a severe degradation in the capability of the
managed object and its full capability must be restored.

• Minor—Filters on the existence of a non-service affecting fault condition

and that corrective action should be taken in order to prevent a more
serious (for example, service affecting) fault. Such a severity can be
reported, for example, when the detected alarm condition is not currently
degrading the capacity of the managed object.

• Warning—Filters on the detection of a potential or impending service

affecting fault, before any significant effects have been felt. Action should
be taken to further diagnose (if necessary) and correct the problem in order
to prevent it from becoming a more serious service affecting fault.

• Info—Filters on additional information is available for this event.

• Event—Filters on a normal occurrence that does not represent a condition

or requires user attention. An event is not raised or cleared; it simply
occurs. It does not have a raised/cleared statu, nor does it have a Cleared
Time or a Cleared User indicator. An event is not de-bounced.

• Raised Only—Filters on raised alarms.

• DPI Splice Results—Filters on digital program insertion splice results.

• Collapse—Toggles alarm descriptions.

• Include PID Alarms—Filters on packet identifier (PID) alarms.

Time Filter Filters on the supplied start and end date/time.

Search Description Filters on a string.

Primary Streams/Backup Streams

Type Shows a video, audio, or data graphic.

Line Shows the output port for the elementary stream.

Mux Shows the output multiplex for the elementary stream.

Program Shows the program name.

Input PID Shows the input PID number assigned in the packet header of an MPEG
stream that identifies the transport stream to which the packet belongs.

198 ARRIS Enterprises, Inc.

 Diagram View

Table 13-8 Diagram View Grooming Parameters (continued)

Network Rule Determines which data streams are kept or dropped from primary or backup
programs based on Network rules. During DPI, the Network rules are not used,
but the DPI rules are used. See Chapter 26, “Managing EBIF,” for more
information.

NW EBIF Priority Determines how the CAP-1000 handles merged network EBIF input streams
when packets are received at the same time. You can assign integer priorities
to merged inputs in custom grooming. A higher integer signifies a higher
priority. See Chapter 26, “Managing EBIF,” for more information.

DPI Rule Determines how an output data stream is handled during DPI. See Chapter
24, “Enabling Digital Program Insertion” for more information.
DPI EBIF Priority Determines how the CAP-1000 handles merged EBIF input streams when
packets are received at the same time. You can assign integer priorities to
merged inputs in custom grooming. A higher integer signifies a higher priority.
See Chapter 26, “Managing EBIF,” for more information.

Output PID Specifies the PID number assigned in the packet header of an MPEG stream
that identifies the transport stream to which the packet belongs. Select Auto
to automatically assign the output PID.

Network Dialnorm Selects the value for the primary and backup AC3 live audio stream.
• Default value is no change (absolute 0)
• Absolute values are 1 to 31
• Relative values are -1 to +30
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.
See section,“Enabling CALM,”on page 402 for more information.

DPI Dialnorm Selects the value for an AC3 live audio stream used in Digital Program
Insertion (DPI).

Slate Component

Type Displays the stream type: MPEG- 2 Video, MPEG-4 Video, or MPEG-4 Audio.

Line Shows the line name for the slate.

Mux Shows the mux name for the slate. This field is empty if row is representing
file.

Program Shows the program name for the slate. Program Name.

File Shows the file name. this field is empty for live audio.

Input PID Shows the input Packet Identifier (PID).

Descriptors Panel

Type Shows the descriptor type for a selected stream in the Primary/Backup
Streams Panel.

CAP-1000 Software Guide v4.0 199

Chapter 13 Content Picking Tabular View

Table 13-8 Diagram View Grooming Parameters (continued)

Description Provides more information about the descriptor. For example, in the case of an
ISO 639 Language descriptor, it contains the name of the language, such as
English. In the case of an ETV registration descriptor, the Type is Registration
and the Description is ETV1.

Tag (Hex) Shows the tag in hexadecimal format.

Length Shows the data length value.

Hex Value Shows the descriptor in hexadecimal format. For example, the entire
descriptor in hexadecimal looks like this: 0a04656e6700.
• Name: ISO 639 Language
• Tag in hex: 0
• Length in hex: 04
• Data in hex: 656e6700
• Data in ASCII: eng
Hex 65 is an ASCII ‘e’, hex 6e is an ASCII ‘n’, hex 67 is an ASCII ‘g’, and hex 00
is not a printable ASCII character so it is represented by ‘.’

ASCII Value Shows the descriptor in ASCII format.

Tabular View
Clicking in the Grooming window displays the Tabular view. This view contains the
following panels:
• Component Tree
• Output Mux
• Program
• Primary Streams/Backup Streams/Slate Component
• Streams/Tables

Panels
When working with programs, elementary streams, or files, the Program, Primary Streams/Backup
Streams/Slate Component, and Streams/Table panels display in the window.

200 ARRIS Enterprises, Inc.

 Tabular View

Component Tree

Output panel

Properties panel

Primary Streams/
Backup Streams/Slat
Component panels

Descriptors panel

Tabular View for Primary Streams/Backup Streams/Slate Component

When working with passed PIDs or tables, the Streams/Tables panels display at the bottom of the
window.

CAP-1000 Software Guide v4.0 201

Chapter 13 Content Picking Tabular View

Component Tree

Output panel

Streams/Tables
panels

Tabular View for Streams/Tables

The panels are described in Table 13-7.

Table 13-9 Tabular View Panels

Component Tree Provides a hierarchical display of hardware components and inputs that can be
groomed through a CAP-1000. Each component is depicted as a node of the Tree. See
“Component Tree” for more information.
Output Selects the output multiplex or program for groomed programs, elementary streams, or
files. Also indicates if a backup program has been specified, a recoder has been
reserved, or ad insertion has been configured for the program. See Chapter 18,
“Grooming Programs” or Chapter 19, “Grooming Elementary Streams”
for more information.

Properties Shows the groomed program properties. This panel is only displayed when the All
Muxes, All MTPS Muxes, or All STPS Muxes option is selected in the Output Mux
menu.

Drag Input Here Creates and grooms programs via drag-and-drop for a selected mux. If you do not want
to create a new program, then drag and drop an input to an existing output program.

Primary Streams/Backup Shows the programs, elementary streams, or files groomed to output for primary or
Streams backup streams (if configured for redundancy). See Chapter 29, “Configuring
Program Redundancy”for more information.
Slate Component Shows details about a slate stream (MPEG-2 video, MPEG-4-video, or MPEG-4 audio) if
defined.

202 ARRIS Enterprises, Inc.

 Tabular View

Table 13-9 Tabular View Panels (continued)

Descriptors Displays the stream-level descriptors for the selected grooming component. Stream
level descriptors are passed through from the input elementary stream to the output
elementary stream. You can add or delete descriptors for extra output streams.

Streams/Tables Shows elementary streams associated with PID passing. Tables show common PSI/SI
tables associated with PID passing. See Chapter 23, “Passing PIDs” for more
information.

Output Line Menu

The panels in the Tabular view change, depending on the option you select from the Output Line
menu. Selecting a specific output line (port) displays muxes associated with that port.

Output Line Menu

Output Mux Menu

The panels of the Tabular view change depending on the option you select from the Output Mux
menu. If you select the All Muxes, All STPS Muxes, or All MPTS Muxes option, all multiplexes
for that selection display in the Output panel, along with program placeholders, if any, that are
associated with a configuration file.

CAP-1000 Software Guide v4.0 203

Chapter 13 Content Picking Tabular View

Output Mux Menu—All Muxes

If you select a specific mux, information for that mux appears in the panels.

Output Mux Menu—Specific Mux

204 ARRIS Enterprises, Inc.

 Tabular View

Actions
With the Tabular view, you can drag an input program, elementary stream, or file from the
Component Tree and drop it on an output multiplex, groomed program, or program placeholder in
the Output panel. This action adds the program, stream, or file to the grooming definition.

Drag-and-Drop Grooming

When the groom operation is in process, and has not yet been applied, the Edit ( ) icon appears
in the Output panel. This icon indicates that your selections have not yet been applied. When you
click the Apply button your changes are applied and the icon is removed.
If you later change your mind about the groom, you can delete it from the Program by right-
clicking the Program icon and selecting Delete Program or Delete Grooming Definition(s) from
the Grooming Context menu. Similarly, you can delete a slate by selecting the Delete Slate
Definition command. See section,“Context Menu,”on page 213 for more information.

CAP-1000 Software Guide v4.0 205

Chapter 13 Content Picking Tabular View

Grooming Context Menu

Alternatively, you can discard your changes by clicking the Discard button. When you do so, the
Delete ( ) icon appears. When you click the Apply button, the icon is removed.

Parameters
You can configure parameters for grooming operations in the Tabular view. For example, you can
configure the start/end date and time for a grooming definition. All parameters displayed in green
highlight are configurable.

NOTE The parameters that display in the Tabular view differ depending on whether you select All Muxes, All
SPTS Muxes, All MPTS Muxes, or a specific Mux. The following illustration shows parameters for a
specific mux.

206 ARRIS Enterprises, Inc.

 Tabular View

Date/Time Properties

Table 13-10 Tabular View Grooming Parameters

Output Panel

Mux Info Shows the name assigned to the multiplex.

Primary Shows the primary program name.

Backup Indicates if a program has been configured for backup, if any.

Slate Indicates if a slate has been configured for backup, if any.

DPI Indicates if digital program insertion (DPI) is active

Service Name Specifies the name of the output program.

Program Number Shows the program number assigned by the CAP-1000.

Recoder Indicates if a recoder has been assigned. The options are:

• No
• HD MPEG-2
• SD MPEG-2
• HD MPEG-4/AVC
See section,“Managing Recoders,”on page 451 for more information.

EBIF Enables EBIF at the output program level when the required license key is
installed. See Chapter 26, “Managing EBIF” for more information.

CAP-1000 Software Guide v4.0 207

Chapter 13 Content Picking Tabular View

Table 13-10 Tabular View Grooming Parameters (continued)

CCC Enables the CAP-1000 to carry closed captioning conversion (CCC) information
in SD or HD MPEG-2 user video streams for DTV. See section,“Managing
Closed Captioning Conversion,”on page 306 for more information.
CALM Enables volume leveling via the Commercial Advertisement Loudness
Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters
of groomed AC-3 audio streams. See section,“Enabling CALM,”on
page 402 for more information.
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.

Properties Panel

Program Number Shows the program number assigned by the CAP-1000.

Slate Error Period Specifies the length of time during which the primary slate cannot recover
from error. If the primary cannot recover by the end of the interval, switching
to the backup slate occurs. If the primary can recover, no switching occurs.
The options are: Min 1 second (in 1 second increments) / Max 100 seconds.
The default is 10 seconds.

Slate Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup slate to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup slate to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup slate to switch over if any video stream
underflows.
• First Audio Only—enables the backup slate to switch over if the first audio
stream underflows.

Slate Switch on Underflow Configures backup to primary slate switchovers. The options are:
• Immediate—switching to the backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Slate Auto Switch Back Specifies whether the backup slate switches back to the primary slate when
the error condition ends.
• True—switches back to the primary slate when the error condition ends.
• False—continues playing out the backup slate after the error condition
ends.

208 ARRIS Enterprises, Inc.

 Tabular View

Table 13-10 Tabular View Grooming Parameters (continued)

Slate Error Free Period Specifies the length of time in which the primary slate must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
slate. The CAP-1000 remains with the backup slate instead. The options are:
Min 7 seconds / Max 100 seconds. The default is 12 seconds (in 1-second
increments). The longer the period of time, the more certain you can be that
the primary slate is error free.

Primary Streams/Backup Streams

Type Shows a video, audio, or data graphic.

Line Shows the output port for the elementary stream.

Mux Shows the output multiplex for the elementary stream.

Program Shows the program name.

Input PID Shows the input PID number assigned in the packet header of an MPEG
stream that identifies the transport stream to which the packet belongs.

Network Rule Determines which data streams are kept or dropped from primary or backup
programs based on Network rules. During DPI, the Network rules are not used,
but the DPI rules are used. See Chapter 26, “Managing EBIF,” for more
information.

NW EBIF Priority Determines how the CAP-1000 handles merged network EBIF input streams
when packets are received at the same time. You can assign integer priorities
to merged inputs in custom grooming. A higher integer signifies a higher
priority. See Chapter 26, “Managing EBIF,” for more information.

DPI Rule Determines how an output data stream is handled during DPI. See Chapter
24, “Enabling Digital Program Insertion” for more information.
DPI EBIF Priority Determines how the CAP-1000 handles merged EBIF input streams when
packets are received at the same time. You can assign integer priorities to
merged inputs in custom grooming. A higher integer signifies a higher priority.
See Chapter 26, “Managing EBIF,” for more information.

Output PID Specifies the PID number assigned in the packet header of an MPEG stream
that identifies the transport stream to which the packet belongs. Select Auto
to automatically assign the output PID.

Network Dialnorm Selects the value for the primary and backup AC3 live audio stream.
• Default value is no change (absolute 0)
• Absolute values are 1 to 31
• Relative values are -1 to +30
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.
See section,“Enabling CALM,”on page 402 for more information.

DPI Dialnorm Selects the value for an AC3 live audio stream used in Digital Program
Insertion (DPI).

CAP-1000 Software Guide v4.0 209

Chapter 13 Content Picking Tabular View

Table 13-10 Tabular View Grooming Parameters (continued)

Slate Component

Type Displays the stream type: MPEG- 2 Video, MPEG-4 Video, or MPEG-4 Audio.

Line Shows the line name for the slate.

Mux Shows the mux name for the slate. This field is empty if row is representing
file.

Program Shows the program name for the slate. Program Name.

File Shows the file name. this field is empty for live audio.

Input PID Shows the input Packet Identifier (PID).

Descriptors Panel

Type Shows the descriptor type for a selected stream in the Primary/Backup
Streams Panel.

Description Provides more information about the descriptor. For example, in the case of an
ISO 639 Language descriptor, it contains the name of the language, such as
English. In the case of an ETV registration descriptor, the Type is Registration
and the Description is ETV1.

Tag (Hex) Shows the tag in hexadecimal format.

Length Shows the data length value.

Hex Value Shows the descriptor in hexadecimal format. For example, the entire
descriptor in hexadecimal looks like this: 0a04656e6700.
• Name: ISO 639 Language
• Tag in hex: 0
• Length in hex: 04
• Data in hex: 656e6700
• Data in ASCII: eng
Hex 65 is an ASCII ‘e’, hex 6e is an ASCII ‘n’, hex 67 is an ASCII ‘g’, and hex 00
is not a printable ASCII character so it is represented by ‘.’

ASCII Value Shows the descriptor in ASCII format.

210 ARRIS Enterprises, Inc.

 Timeline View

Timeline View
Clicking in the Grooming window displays the Timeline view. This view is divided into
three panels:
• Component Tree
• Output Mux
• Program Interval Detail

Component Tree

Schedule panel

Current Date/Time

Program Interval
Detail panel

Timeline View

Panels
The panels are described in Table 13-11.

Table 13-11 Timeline View Panels

Component Tree Provides a hierarchical display of hardware components and inputs that can be
groomed through a CAP-1000. Each component is depicted as a node of the Tree. See
“Component Tree” for more information.
Schedule Shows the playout schedule for groomed programs.

Current Date/Time Represents the current date/time with a vertical black bar in the time grid.

Program Interval Detail Shows the start time/end time and other parameters for the selected program.

CAP-1000 Software Guide v4.0 211

Chapter 13 Content Picking Timeline View

Actions
The Timeline view is used to perform the following functions:
• View the grooming schedule for all output programs of a given output line.
• Change the displayed date and time interval by week, day, half day, quarter day, or hour.
• Restore the current date and time position in the view.
• Adjust the start time of view.
• Select different output lines and multiplexes and view their respective grooming schedule.
• Observe the results of testing triggering events

Properties
The Timeline view shows the program schedule (time grid) for all programs groomed to a specific
output multiplex in a given time interval. the time grid is representative of an Electronic Program
Guide. The input programs are placed in their scheduled order, including scheduled drops and
black file insertions. The current time is represented as a black line across the time grid.
A number of controls are provided on top of the schedule panel. A calendar component, used to
select viewing date, is activated by clicking the Start Date / Time button. The Time Scale menu is
used to select granularity from one hour to one week. The default granularity shows a full day
program in one-hour increments.

Timeline View—Time Scale

In this view, you can select different multiplexes by using the Output Line menu or the Output
Mux menu. You can also create an input or output mux by clicking the Create Input Mux button or
the Create Output Mux button, respectively.

212 ARRIS Enterprises, Inc.

 Context Menu

When a new output mux is selected, the schedules associated with each program interval display
as color bars organized by program order. Each program interval is represented by a color bar.
When any interval is clicked, all program intervals that belong to this output program are
displayed in the program interval table in the lower pane.
You can also adjust the horizontal and vertical scroll bar so view different parts of schedule within
the entire range.
When you select a time scale from the Time Scale menu, the following information displays:
• The end time and time grid unit is changed, but start time remains to be the same.
• Click the Start Date/Time button and select a calendar day and time. The change is
immediately reflected on the view.
• Click the Now button to restore the current position of time (of the device) into view.

Timeline View—Date/Time

Context Menu
Separate Context menus are provided for elements in the Content Picking window: Component
Tree, Mux tab, and Grooming tab. Selecting an element and clicking the right mouse button causes
a Context menu to appear. Actions that are supported for the selected element are boldface.
Actions that are not applicable to the selected element are grayed out. The Cancel option discards
changes not yet applied.

CAP-1000 Software Guide v4.0 213

Chapter 13 Content Picking Context Menu

Context Menu

Table 13-12 describes the commands that can appear in the Context menu.

Table 13-12 Context Menu

Component Tree

Edit Name Edits the name of the selected feed, mux, or program.

Show Groomed To Highlights the groomed program in the Output panel of the Grooming tab.

Mux Tab

Manual Override • Primary—Forces all programs that are currently switched to backup or slate to
be re-groomed as primary in a program redundancy (PRED) failover scenario.
• Backup—Manually switches to backup streams if backup programs have been
defined in a PRED scenario. Forces all programs that are currently switched to
primary to be re-groomed as backup. You can also manually switch a program to
backup, even if the backup is not defined. When a backup is defined at a later
time, the program is switched (forced) to backup at that time.
• Slate—Manually switches to a slate if backup slates have been defined in a
PRED scenario. You can also manually switch a program to a slate, even if the
backup is not defined. When a slate is defined at a later time, the program is
switched (forced) to slate at that time.
See Chapter 29, “Configuring Program Redundancy”for more
information.

Create Stat Mux Pool Creates a stat mux pool. See section,“Managing Stat Mux Pools,”on
page 445 for more information.

214 ARRIS Enterprises, Inc.

 Context Menu

Table 13-12 Context Menu (continued)

Copy Down Copies the selected content to adjacent rows. See section,“Copying
Parameters,”on page 218 for more information.
Fill Decrement Automatically fills in numbers in adjacent rows cells based on a number in the
source cell. Applies to GigE input multiplexes.

Fill Increment Automatically fills in numbers in adjacent rows cells based on a number in the
source cell. The numbers are incremental. Applies to GigE input multiplexes.

IPv4 Decrement Automatically fills in numbers in adjacent rows cells based on a number in the
source cell. Applies to multicast IP address for GigE input multiplexes.

IPv4 Increment Automatically fills in numbers in adjacent rows cells based on a number in the
source cell. The numbers are incremented according to the following pattern:
• 0.0.0.X
• 0.0.X.0
• 0.X.0.0
• X.0.0.0
Applies to multicast IP address for GigE input multiplexes.

PSIP Modifies STT/EIT/STT tables for an output mux loaded with an ATSC configuration
file. See Chapter 15, “Managing Tables and Output Programs” for more
information.

NIT Creates a Network Information Table (NIT) for DVB multiplexes. See
section,“Creating Custom NIT,”on page 298 for information.

TOT Generates a Time Offset Table (TOT) for DVB multiplexes. See
section,“Generating TOT,”on page 301 for information.

Suspend BISS Suspends encryption/decryption while maintaining the Basic Interoperable

Scrambling System (BISS) definition.
Note: This function is only available on CAP-1000 devices with a CR-DSP module.

Delete Deletes the current selections.

Delete Inactive Deletes selected muxes if labeled <mux name>[Inactive] in the Component tree.

Cancel Cancels modifications without applying them.

Clear Clears the current program on an ASI input mux that is disconnected.

Grooming Tab

Add Program Adds a program to an output mux.

Add Grooming Definition Adds a grooming definition to the selected program. Only enabled if an input is
selected in Component Tree.

Delete Program Deletes the selected output programs from the groom.

Delete Grooming Deletes all definitions for selected output program.

Definition(s)

CAP-1000 Software Guide v4.0 215

Chapter 13 Content Picking Context Menu

Table 13-12 Context Menu (continued)

Delete Slate Definition Deletes the slate definition for a backup program.

Delete Backup Definition Deletes the grooming definitions for a backup program.

Set Recorder Sets MPEG-2, MPEG-4, MPEG-4/AVC HD, or no recoder.

Manual Override • Primary—Forces all programs that are currently switched to backup or slate to
be re-groomed as primary in a program redundancy (PRED) failover scenario.
• Backup—Manually switches to backup streams if backup programs have been
defined in a PRED scenario. Forces all programs that are currently switched to
primary to be re-groomed as backup. You can also manually switch a program to
backup, even if the backup is not defined. When a backup is defined at a later
time, the program is switched (forced) to backup at that time.
• Slate—Manually switches to a slate if backup slates have been defined in a
PRED scenario. You can also manually switch a program to a slate, even if the
backup is not defined. When a slate is defined at a later time, the program is
switched (forced) to slate at that time.
See Chapter 29, “Configuring Program Redundancy”for more
information.

Show Inputs Identifies the input to the output groom in the Component Tree.

Undo Undoes changes made to the selected row.

Grooming Definitions Panel

Add Grooming Definition Adds a grooming definition to the selected program. Only enabled if an input is
selected in Component Tree.

Delete Grooming Definition Deletes the grooming definitions for selected output program.

Manual Trigger Enables the manual triggering of events.

Define Drop Groom Defines the conditions under which a groom is dropped.

EBIF Configures Enhanced TV Binary Interchange Format (EBIF) filtering on the selected
grooming definition. An EBIF license per-program basis is required to apply the
filtering. See Chapter 26, “Managing EBIF,” for more information.

Primary Streams/Backup Streams Panel

Delete Deletes the selected streams.

Add Input Stream Adds a PID for a stream that is not available at input at the time of the grooming,
but will follow later. See section,“Forcing Custom Grooms,”on page 401
for more information.

Add Output Stream Adds Enhanced Television (ETV) data streams to a groom operation. To add ETV
streams, you define extra output data stream placeholders in the groomed output
program, including stream types and descriptors. This allows data streams in ads,
such as ETV data streams, to be spliced into a groomed output program (similar to
ads spliced into a network-groomed output program). See section,“Managing
Placeholders for ETV Streams,”on page 541 for more information.

216 ARRIS Enterprises, Inc.

 Keyboard Shortcuts

Table 13-12 Context Menu (continued)

Slate Component Panel

Deletes Deletes the selected slate from the grooming definition. See Chapter 20,
“Grooming Files,” for more information.
Descriptors Panel

Delete Deletes a selected descriptor on extra output stream.

Add Descriptor Adds a descriptor to an extra output stream.

Program Intervals Panel

Drop Interval Drops the selected program interval that was active or scheduled to be activated.

EBIF Configures Enhanced TV Binary Interchange Format (EBIF) filtering on the selected
program interval. An EBIF license per-program basis is required to apply the
filtering. See Chapter 26, “Managing EBIF,” for more information.

Alarms

Clear Clears the selected alarm and removes it from the panel. See Chapter 35,
“Managing Alarms and Logs,” for more information.
Delete Deletes the selected alarm and removes it from the panel. Raised alarms are
automatically cleared before being deleted.

Keyboard Shortcuts
A number of keyboard shortcuts are available to help you work faster in the Content Picking
window.

Selecting a Single Cell

Click the cell.

Select a Context Menu Command

Right-click the cell.

Selecting a Range of Cells

Click the first cell in the range, and then hold down SHIFT while you click the last cell in the
range.

Selecting Non-adjacent Rows

Select the first row or range of rows, and then hold down CTRL while you select the other rows or
ranges.

CAP-1000 Software Guide v4.0 217

Chapter 13 Content Picking Keyboard Shortcuts

Content Picking—Non-adjacent Rows

Canceling a Cell Selection

Click any cell on the window.

Copying Parameters
The Copy Down menu command lets you duplicate the first field value in a selected cell and then
apply it to all connected cells that are subsequently selected.
The following input multiplex parameters are modifiable using Copy Down bulk operations:
• UDP Connection
• IP Address
• UDP Port
• Source IP filter
• Multiplex type

218 ARRIS Enterprises, Inc.

 Keyboard Shortcuts

Content Picking—Input Muxes Copy Down

The following output multiplex parameters are modifiable using Copy Down bulk operations:
• UDP Connection
• Protocol
• Name
• Mode
• Total Rate
• Padding
• Tagging
• VLAN ID
• VLAN priority

To use copy down:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 In the Mux panel on the right side of the window, choose the value you want for the first cell.
3 Drag the mouse down the column to select the range of cells.
4 Right-click the mouse button.
5 Select Copy Down from the Context menu.

CAP-1000 Software Guide v4.0 219

Chapter 13 Content Picking Keyboard Shortcuts

For example, to set all 15 cells in the Mux panel to be a multiplex UDP connection, under UDP
Connection, set the first row in the range to be multicast, select all 15 rows, right-click the mouse
button, and then select Copy Down. Clicking this menu command sets all 14 items below the first
item to the value of the first item.

Filling UDP Port Parameters

The Fill Increment operation automatically increments in numbers in adjacent rows cells based on
a number in the source cell. The Fill Decrement operation automatically decrements in numbers in
adjacent rows cells based on a number in the source cell. The UDP port parameter for input and
output GigE multiplexes is modifiable using Fill Increment or Fill Decrement bulk operations.

To use fill UDP port parameters:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 In the Mux panel on the right side of the window, scroll to the parameter you want.
3 Select the source row.

Content Picking—Fill UDP Port

4 Press SHIFT and drag the mouse down through the range of rows.
5 Click the right mouse button.
6 Select Fill Decrement or Fill Decrement from the Context menu.

220 ARRIS Enterprises, Inc.

 Keyboard Shortcuts

Content Picking—Fill UDP Port

7 Release the mouse button.

Filling IPv4 Parameters

The bulk operation for the Internet Protocol version 4 (IPv4) parameter applies to multicast IP
address for GigE multiplexes. This operation automatically fills in numbers in adjacent rows cells
based on a number in the source cell. The numbers are incremented according to the following
pattern:
• 0.0.0.X
• 0.0.X.0
• 0.X.0.0
• X.0.0.0
The IP Address parameter for input multiplexes is modifiable using the IPv4 increment or IPv4
Decrement bulk operations. The Destination IP parameter for output multiplexes is modifiable
using the IPv4 increment or IPv4 Decrement bulk operations.

To use fill IPv4:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 In the Mux panel on the right side of the window, scroll to the parameter you want.
3 Select the source row.

CAP-1000 Software Guide v4.0 221

Chapter 13 Content Picking Keyboard Shortcuts

Content Picking—Fill IPv4

4 Press SHIFT and drag the mouse down through the range of rows.
5 Click the right mouse button.

Content Picking—Fill IPv4

6 Select IPv4 Increment or IPv4 Decrement from the Context menu and then choose the
numbering scheme you want.

222 ARRIS Enterprises, Inc.

 Managing Panels

7 Release the mouse button.

Managing Panels
You can open, close, resize, or scroll the panels in the Mux and Grooming tabs. Up and Down
arrows on the panels enable you to open or close the panels, respectively. Scroll bars let you scroll
the contents of a panel left, right, up, or down.

To manage panels:
1 In the CherryPicker Element Manager, click Mux or Grooming.

NOTE Example illustration shows the Diagram view of the Grooming tab.

Panel Control

2 To open one panel, click or .

3 To close one panel click or .
4 To resize adjacent panels, drag the bar separating the panels up or down or left or right
.
5 To scroll the contents of the panel left or right, click .
6 To scroll the contents of a panel up or down, click .

CAP-1000 Software Guide v4.0 223

Chapter 13 Content Picking Filtering

Filtering
The Filter button lets you filter the Content Picking Tree based on a keyword. You filter the
Component Tree nodes using one or more input key words separated with spaces. If more than one
keyword has spaces, then use double quotes (“HBO One” “HBO Two”). Nodes that match any of
key words are shown in the panel.

NOTE The Filtering function is also available in the Select Output Multiplex dialog box and the Analysis window.

To filter:
1 In the CherryPicker Element Manager, click Mux or Grooming.

NOTE Example illustration shows the Diagram view of the Grooming tab.

2 In the Filter field, enter the keyword.

Specify two or more keywords by separating each entry with space. Enclose words that contain
spaces in double quotes. For example, “HBO One” or “HBO Two.”
3 Press Enter or click Go to submit the request.

Filter

224 ARRIS Enterprises, Inc.

 Ad Muxes

To clear the results:

1 Clear the keyword in Filter field.
2 Press Enter or click Go to submit the request.

Ad Muxes
Use the Ad Mux option to show or hide multiplexes playing ads in the Component tree.

Content Picking—Grooming

Alarm Reporting
The alarm reporting function in the Content Picking window indicates when an alarm is detected
on a “source.” The source path of the alarm corresponds to the output program selected in the
output program list above the Alarms tab. The source can be one of the following:
• Device
• Line (port)
• Multiplex
• Program
• Tables (part of the multiplex to which they belong)
• Stream
• Ad server IP address

CAP-1000 Software Guide v4.0 225

Chapter 13 Content Picking Alarm Reporting

• DPI channel name

• Primary CAP-1000 IP address

Alarms

Wherever an alarm is displayed for a selected output program in the Content Picking window, the
highest severity level of any alarm for that node, or at any of its child nodes, is indicated by a
severity color. When no alarms exist under a node, no severity color is displayed for that node.
Table 13-13 describes the severity values for alarms in the Content Picking window.

Table 13-13 Severity Values

Alarm Icon Description

Critical Red—Indicates that a service affecting condition has occurred and an immediate
corrective action is required. Such a severity can be reported, for example, when a
managed object becomes totally out of service and its capability must be restored.

Major Orange—Indicates that a service affecting condition has developed and an urgent
corrective action is required. Such a severity can be reported, for example, when there
is a severe degradation in the capability of the managed object and its full capability
must be restored.

Minor Yellow—Indicates the existence of a non-service affecting fault condition and that
corrective action should be taken in order to prevent a more serious (for example,
service affecting) fault. Such a severity can be reported, for example, when the
detected alarm condition is not currently degrading the capacity of the managed
object.

226 ARRIS Enterprises, Inc.

 Alarm Reporting

Table 13-13 Severity Values (continued)

Alarm Icon Description

Warning Cyan—Indicates the detection of a potential or impending service affecting fault,

before any significant effects have been felt. Action should be taken to further
diagnose (if necessary) and correct the problem in order to prevent it from becoming a
more serious service affecting
fault.

Info Gray—Indicates additional information is available for this event.

Cleared Green—Indicates the clearing of one or more previously reported alarms. This alarm
clears all alarms for this managed object that have the same Alarm type.

Event No Color—Indicates a normal occurrence that does not represent a condition or

requires user attention. An event is not raised or cleared; it simply occurs. It does not
have a raised/cleared statu, nor does it have a Cleared Time or a Cleared User
indicator. An event is not de-bounced.

After you identify a source object and its alarm, refer to Chapter 35, “Managing Alarms and Logs”
for information on managing the alarm.

CAP-1000 Software Guide v4.0 227

Chapter 13 Content Picking Alarm Reporting

228 ARRIS Enterprises, Inc.

 CHAPTER 14
Configuring Multiplexes

In This Chapter
• Multiplexes
• Basic Interoperable Scrambling System (BISS)
• Loopbacks
• Gigabit Ethernet Multiplex Options
• Managing Gigabit Ethernet Input Multiplexes
• Managing Gigabit Ethernet Output Multiplexes
• Managing ASI Input Multiplexes
• Managing ASI Output Multiplexes
• Configuring GPS Offset and Daylight Savings Time
• Configuring Optional SDT, Service Names, and Service Provider Names

Multiplexes
Multiplexing refers to the process of interleaving audio and video into one, coherent transport
stream. Software that produces a transport stream is called a multiplex or mux. In digital
television, several variable bit rate data streams are multiplexed together to form fixed bit rate
transport stream by means of statistical multiplexing. This makes it possible to transfer several
video and audio channels simultaneously over the same frequency channel together with various
services.

Multiplex Types
Using the CherryPicker Element Manager, you can configure GigE and ASI input and output
multiplexes, providing the respective modules are installed in the CAP-1000 device.
An input multiplex is a transport stream from a service provider that contains one or more multiple
program services, each composed of elementary video, audio, and data streams. An input
multiplex is required to enable the CAP-1000 to receive MPEG transport streams. Each CAP-1000
can handle up to 900 input multiplexes.

CAP-1000 Software Guide v4.0 229

Chapter 14 Configuring Multiplexes Multiplexes

SPTS and MPTS Multiplexes

An output multiplex is a single transport stream containing multiplexed program services for
distribution to subscribers. An output multiplex is required to enable the CAP-1000 to send MPTS
or SPTS MPEG transport streams.
A SPTS is formed by multiplexing Transport Stream (TS) packets from one or more Packetized
Elementary Stream (PES) and/or private section sources. Two or more SPTS may be combined to
form) a service multiplex (also known as an MPTS in the MPEG-2 Systems standard, and a digital
television standard multiplexed bit stream in this SCTE standard). Program Specific Information
(PSI) identifies programs and the components of programs.
Each input and output port in the CAP-1000 can include a multiplex. A GigE output line may have
zero to many output muxes. Some GigE lines can be used for input muxes only. Whenever a DVB-
ASI output is enabled, you must define a multiplex for it. Multiple multiplexes can be defined on
GigE ports.
The software assigns an identification number to a multiplex in order to associate the multiplex
and its various attributes. The default name is Mux_<ID>. You can also assign your own unique
name to a multiplex.

Multiplex Components
Each multiplex consists of tables and programs or stat mux pools, with each pool containing tables
and programs. The tables include the common PSI/SI tables, as well as other multiplex-wide tables
as defined in the compression systems supported by the software.
The software assigns an ID to a program to associate the program and its various attributes.The
default name of a program is < line-name >_<program ID>, for example, “1/4_14.” You can also
assign a name to an output program.
You create a multiplex by applying a configuration file using the CherryPicker Element Manager.
In the case of a configuration file command, a PAT and a PMT are created for the programs in this
multiplex. No elementary streams defined in the PMTs are output until streams are actually
groomed to the output program.
In addition, you can export output muxes to an Excel spreadsheet should you need the information.

How Multiplexing Works

A headend, central office, or satellite uplink facility receives upstream video-on-demand requests
and MPEG transport streams containing video program data. The video data is packetized into
TCP/IP or UDP/IP packets and LAN packets and routed through a switch to one or more
CAP-1000 multiplexes. Each CAP-1000 multiplex receives LAN packets, depacketizes the MPEG
data, partially or fully decompresses the data, and then recompresses the data to another smaller
bandwidth. From here, the data is repacketized into MPEG packets or TCP/IP or UDP/IP packets.

230 ARRIS Enterprises, Inc.

 Basic Interoperable Scrambling System (BISS)

The repacketized TCP/IP or UDP/IP packets are transmitted directly to customers as TCP/IP or
UDP/IP packet data. MPEG packets generated by the CAP-1000 multiplex are, optionally,
encapsulated in LAN packets. Then, they are depacketized back to MPEG packets and transmitted
to the appropriate transmitter or modem for transmitting to customers. Internet data and data from
application servers can also be transmitted to customers through the CAP-1000 multiplexes or a
downstream modem, and upstream data can be received through a modem.

Basic Interoperable Scrambling System (BISS)

The CAP-1000 supports the Basic Interoperable Scrambling System (BISS) for systems with a
CR-DSP module. This feature provides encryption capabilities on the CAP-1000 platform to
protect the transmission by a “session word” that is agreed by the transmitting and receiving
parties prior to transmission.
The session word is entered into both the encoder and decoder for a specific mux. This session
word then forms part of the encryption of the digital TV signal and only receivers with the correct
word can decrypt the signal. The CAP-1000 can decrypt input MPTS or SPTS and encrypt output
MPTS or SPTS. BISS is enabled in the Mux panel of the Content Picking window.
A session word can be a provided in the "clear," in which case, it is a 12-digit hexadecimal string.
A session word can also be encrypted. In this case, it is a 16-digit hexadecimal string. When an
encrypted session word is used, the Injected BISS Identifier is the decryption key.
The injected BISS ID is a hexadecimal string that is a secret key embedded at the device level.
Only users with Config permissions can enter the injected ID. The injected ID must be defined
before an encrypted session word can be defined for any mux.
BISS is enabled in the Mux panel of the Content Picking window.

BISS Mode and Session Word

CAP-1000 Software Guide v4.0 231

Chapter 14 Configuring Multiplexes Basic Interoperable Scrambling System (BISS)

BISS is only available on CAP-1000 devices hosting a CR-DSP module. BISS has an impact on
system performance.

Scrambling
BISS scrambles every groomed or non-encrypted output stream passed from the output multiplex
(all components except for tables). For inputs, BISS encrypted elementary streams contained in the
multiplex are decrypted when BISS is enabled at the input multiplex level or at the device level.
The function works on both GigE and ASI ports. BISS does not apply to ad insertion multiplexes
and it does not apply to video or audio files stored on the device.

NOTE Encrypted input is prohibited from being groomed to a BISS output mux.

There are some restrictions that prevent defining a mux for BISS scrambling. If the device does
not have a CR-DSP module, a DCII mux type, a defined loopback, or passed/encrypted streams,
you cannot mark the mux for BISS scrambling.

Session Words
Users with Config permissions can configure session words for specific input and output
multiplexes. The session words are activated at the multiplex level using the GUI. The session
word is a hexadecimal string that is entered by the user with Config permissions. After the session
word has been specified, asterisks are displayed instead of the session word values in the GUI
fields.
A user cannot change a specific session word more than ten times in a five-minute period. A
minimum waiting period of 10 seconds between changes is also enforced.

NOTE The CAP-1000 only supports sessions words that are defined in configuration files via the GUI. The
exported session word value is encrypted and cannot be altered. Altering the session word causes encryption
or decryption to fail when configuration files are imported.

Bulk operation for assigning session words to multiplexes is supported.

Modes
Three modes of BISS are provided:
• Disable BISS (Mode 0) scrambling is disabled. In this mode, there are no CA descriptors in
the PMT and no CAT added to the mux.
• Enable BISS (Mode 1) protects transmissions with a 12-digit hexadecimal session word that is
agreed by the transmitting and receiving parties prior to transmission. The session word is
entered into the encoder and decoder of the mux. This session word forms part of the
encryption of the digital TV signal and any receiver with BISS support and the correct session
word can decrypt the signal.

232 ARRIS Enterprises, Inc.

 Loopbacks

• Enable BISS (Mode E) (for encrypted) keeps clear session words from leaking out and limits
decryption to devices using the same injected ID.

Injected BISS Identifier

The injected BISS ID is a hexadecimal string that is a secret key embedded at the device level.
Only users with Config permissions can enter the injected ID. The injected ID must be defined
before an encrypted session word can be defined for any mux.
A BISS license is required for entering injected identifier. The CAP-1000 does not support a
supplier’s buried identifier.
The Injected BISS ID is entered in the Setup > System > Device window. See section,“Setting the
Injected BISS Identifier,”on page 80 for more information.

BISS and Redundancy

BISS is supported in Backup 1:1 and Backup N:1 CPR when the primary and the backup host
contain a CR-DSP module. The backup device inherits the BISS device or multiplex settings of the
primary devices for input and output multiplexes. A covering backup device with a CR-DSP
module, and BISS enabled on one or more muxes, will prevent a fail back from occurring when the
primary device hosts a DSP module (not supporting BISS).
In multiplex redundancy, the primary and backup multiplexes can have different BISS settings.
Mirrored output multiplexes on mirrored ports take the BISS settings of the primary port
multiplexes. The BISS settings on the mirrored mux cannot be altered.

Loopbacks
The CAP-1000 enable loopbacks GigE and ASI output multiplexes. The loopback feature allows
every regular or rate-shaped, ad-inserted output multiplex to be treated as an input multiplex under
the same line. When programs are groomed to a primary output multiplex, the groomed programs
are automatically made available on the loopback multiplex (on the corresponding input line) as
inputs.
When creating an output mux, use the Loopback option on the Create Output Mux dialog box to
enable or disable loopbacks.

CAP-1000 Software Guide v4.0 233

Chapter 14 Configuring Multiplexes Loopbacks

Create Output Multiplex (Basic)—Loopback

You can enable loopbacks after the multiplex has been created by using the Loopback option in the
Content Picking window. In addition, you can enable loopbacks when converting an ASI input line
to ASI output line.

LoopBack Option

234 ARRIS Enterprises, Inc.

 Gigabit Ethernet Multiplex Options

You can groom loopback input programs to any CAP-1000 output program, other than the
multiplex from which it originated, using any grooming modes (i.e., program, elementary stream,
custom grooming).
You remove loopbacks on output muxes by clicking the Clear Loopback button. When the
loopback is cleared, the CAP-1000 drops all programs and tables in the loopback input multiplex.
The Clear Loopback button is active only when active programs are available at the input.
The loopback input multiplex is assigned a different ID than the output multiplex from which it
was looped. The loopback input multiplex has the same IP:Port as the output multiplex from which
it was looped. Loopback multiplexes are indicated by the label [Loopback] in the Configuration
tree.
The loopback function is supported on non-mirrored output multiplexes for GigE and ASI
interfaces. Loopbacks are also supported for PRED, MRED, and Unicast multiplexes. It is not
supported on mirror multiplexes or Basic Interoperable Scrambling System (BISS), a satellite
signal scrambling system.
Stream analysis values for loopback multiplexes, such as total multiplex rate, aggregate rate, frame
rate, frame size, and average program bit rate, are similar to those of regular input multiplexes.
There is no GigE bit rate increase for multiplexes with loopback. The bandwidth is reported at the
port and device level in the Analysis window.

Gigabit Ethernet Multiplex Options

This section lists some of the supported features for input and output multiplexes. Please review
these features before configuring a multiplex.

Maximum Number of Output Multiplexes

• The maximum number of output multiplexes you can create is 384 per port and 384 per
device.
• The maximum number of SPTS muxes with recoded MPEG-2 SD programs that can be
created with loopbacks enabled is 384.
• The maximum number of SPTS muxes with recoded MPEG-2 SD programs that can be
created with loopbacks enabled is 192 muxes. This includes loopback programs groomed to
another 192 SPTS with MPEG-2 SD recoders assigned.

Real-time Transport Protocol Configuration

The CAP-1000 supports the configuration of GigE multiplexes with Real-time Transport Protocol
(RTP) headers. RTP headers are enabled through the input and output multiplex nodes of the
CherryPicker Element Manager. RTP is an Internet Protocol standard that specifies a way for
programs to manage the real-time transmission of multimedia data over unicast or multicast
network services. It typically runs on top of the User Datagram Protocol (UDP).

CAP-1000 Software Guide v4.0 235

Chapter 14 Configuring Multiplexes Gigabit Ethernet Multiplex Options

Create Output Mux (Advanced)—RTP

RTP differs from transport protocols like TCP in that it does not offer any form of reliability or a
protocol-defined flow/congestion control; however, it does provide the necessary functions for
adding reliability and flow/congestion control.
RTP combines its data transport with a control protocol (RTCP), which makes it possible to
monitor data delivery for large multicast networks. Monitoring allows the receiver to detect if
there is any packet loss and to compensate for any delay jitter.
An RTP header contains a timestamp that is used to recover and restore packet timing between a
network sender and receiver. Information in the RTP header tells the receiver how to reconstruct
the data and describes how the codec bit streams are packetized. The timestamp also facilitates the
troubleshooting of problems caused by excessive network delays.

Time to Live (TTL)

Both unicast and multicast broadcasts include a “time to live” feature. As a data packet passes
through a router, its time to live decreases by 1. When the value reaches 0, the router discards the
data packet. For example, when you set up a multicast broadcast, you specify a time to live of 0 to
255 in the multicast time to live field or the server destination file's multicastTTL property. The
larger the value, the greater the distance a packet travels. The default value of 128 typically keeps
multicast packets within an internal network.

236 ARRIS Enterprises, Inc.

 Gigabit Ethernet Multiplex Options

Create Output Mux (Advanced)—TTL

Quality of Service Configuration (QoS)

The CAP-1000 supports Quality of Service (QoS), a mechanism that allows service providers to
offer different classes of service to customers. It enables a network to service an application
efficiently, without affecting its function or performance. QoS includes a set of techniques to
manage:
• Bandwidth—the width of the transport stream.
• Delay—the length of the transport stream.
• Jitter —the variation in the transport stream.
• Packet Loss—a leak in the transport stream.
QoS can be configured in both Layer 2 and Layer 3 Ethernet transport.

CAP-1000 Software Guide v4.0 237

Chapter 14 Configuring Multiplexes Gigabit Ethernet Multiplex Options

Create Output Mux (Advanced)—QoS

VLAN Tagging and Prioritization

The CAP-1000 supports both packet prioritization (802.1p) and Virtual LANs (802.1q). When a
GigE primary/mirror output multiplex is created, you can tag MPEG audio and video traffic over
User Datagram Protocol (UDP) using IEEE traffic-class mappings.
The most common service offered is Layer 2 Ethernet transport. This means that the service
provider offers Ethernet (at Layer 2 of the OSI model) as the transport mechanism. When
providing this kind of service, Virtual local area network (VLAN) tagging (IEEE 802.1Q/p) uses
QoS.
The IEEE 802.1q specification establishes a standard method for tagging Ethernet frames. The
IEEE 802.1p specification is an extension of 802.1q and allows for traffic prioritization by
grouping traffic into classes such as streaming video, voice, etc.

238 ARRIS Enterprises, Inc.

 Gigabit Ethernet Multiplex Options

Create Output Mux (Advanced)—VLAN Tagging

DiffServ and Type of Service

Differentiated Services Code Point (DSCP) or DiffServ is a method of trying to guarantee quality
of service on network devices that operate on Layer 3 information. It is a mechanism for deciding
which packets to delay or drop at the expense of others when there is not enough network capacity.
The range for DSCP is 0 to 63. The default value is 0 (Best Effort).
DiffServ operates on the principal of traffic classification, where each data packet is placed into a
limited number of traffic classes, rather than differentiating network traffic based on the
requirements of an individual flow. Each router on the network is configured to differentiate traffic
based on its class. Each traffic class can be managed differently, insuring preferential treatment for
higher priority traffic on the network.
DiffServ relies on a mechanism to classify and mark packets as belonging to a specific class.
DiffServ aware routers implement Per-Hop Behaviors (PHBs), which define the packet forwarding
properties associated with a class of traffic. Different PHBs may be defined to offer, for example,
low-loss, low-latency forwarding properties or best-effort forwarding properties.
DSCP is established by configuring the Type of Service (ToS) mechanism in the CherryPicker
Element Manager. This prioritizes packets within a queue. Packets with a higher priority value are
transmitted before others. It also establishes routing criteria. These fields are: Delay, Throughput,
and Reliability.
ToS is supported on GigE modules. A mirrored GigE multiplex can have a different ToS value
than the original multiplex. ToS values can also be dynamically changed on a GigE multiplex.

CAP-1000 Software Guide v4.0 239

Chapter 14 Configuring Multiplexes Gigabit Ethernet Multiplex Options

Create Output Mux (Advanced)—DSCP

Bulk Operations
The CherryPicker Element Manager supports single or bulk creation of input and output GigE
multiplexes. When creating input or output multiplexes, a Bulk Option is provided in the
Multiplex Creation dialog box.
When selected, this option lets you perform bulk operations on either the last octet of the IP
address of the multiplex (the UDP port is unchanged in this case) or the last UDP port to used (the
IP address is unchanged in this case). The system creates as many multiplexes as needed to fill the
specified range, from the starting last octet of the IP address to the last one specified in the range,
or from the starting UDP port to the last one specified in the range.

240 ARRIS Enterprises, Inc.

 Gigabit Ethernet Multiplex Options

Create Output Multiplex (Basic)—Bulk Option

The CherryPicker Element Manager also supports bulk editing of the input or output multiplex
parameters using the Context menu. When you select multiple rows in the Output Mux panel, three
different actions can be applied to a group of multiplex parameters. These actions are: Copy Down
(duplicating the first field value to all cells), Fill Increment (increment the field values starting
from the value of the first field), and Fill Decrement (decrement the field values starting from
value of the first field). Refer to section,“Copying Parameters,”on page 218, section,“Filling UDP
Port Parameters,”on page 220, and section,“Filling IPv4 Parameters,”on page 221 for more
information.

Rate Shaping
Rate shaping is the process of changing or altering the bit rate of the service to a lower bit rate to
squeeze more programs and/or services into the available bandwidth. See for section,“Enabling
Rate Shaping,”on page 442 complete information.

CAP-1000 Software Guide v4.0 241

Chapter 14 Configuring Multiplexes Gigabit Ethernet Multiplex Options

Create Output Multiplex (Basic)—Rate Shaping

Multiplex Mirroring
Mirroring cannot be enabled on a per output multiplex basis; however, when GigE port mirroring
is enabled, the CAP-1000 automatically creates a mirrored output multiplex for every primary
output multiplex that is created. When port mirroring is enabled, the CAP-1000 puts the mirrored
port in standby mode and creates a mirrored output multiplex for each primary output mux already
created on that GigE port. See Chapter 32, “Configuring Port Mirroring” for more information.

Emergency Alert Service (EAS)

The SCTE 18 standard, Emergency Alert Messaging for Cable, supports the broadcasting of
emergency alert information related to state and local-level emergencies to digital receiving
devices. The CAP-1000 lets you configure dedicated input multiplexes to receive EAS messages
from any number of EAS generators. Each dedicated input multiplex contains a details channel
that supplies the audio/video service pertaining to the alert. On reception of an SCTE 18 EAS, the
program switches to the details channel for the EAS generator. The EAS switchover to the details
channel is controllable at a program level for rate-shaped output multiplexes. Refer to Chapter 25,
“Enabling Emergency Alert Messaging,” for more information.

242 ARRIS Enterprises, Inc.

 Gigabit Ethernet Multiplex Options

MPEG Active and Standby Output Port States

You can put an enabled GigE MPEG output port into either a standby state or an active state. The
default MPEG output state is active.

NOTE The output port state applies to the entire output part of a physical GigE port on the 1G IOA or 10G IOA. It
does not affect the corresponding input port.

When in the standby state, all the multiplexes and grooming configuration that had existed on that
output port, prior to switching states, are preserved. The output port will not send any MPEG
packets. However, the port will continue to send regular, non-MPEG Ethernet packets (such as
various IP protocol management packets, etc.). All operations available for a normal output, such
as creating muxes, deleting muxes, creating grooms, or dropping grooms, are allowed on a standby
port.
When in the active state, the output port continues to operate in a normal way transmitting MPEG
packets. Transition from the standby state to the active state automatically restores the
configuration and grooming activities for all multiplexes that existed on this output port.
The process of switching to the standby (or back to active) state takes about one second.

IMPORTANT Management traffic is not affected when the MPEG output traffic toggles between active and standby states.

Ad Mux
The Configuration tree for the Content Picking window contains an option to show or hide output
multiplexes that are streaming content from an ad server. See Chapter 24, “Enabling Digital
Program Insertion,” for more information on working with ad servers.

CAP-1000 Software Guide v4.0 243

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Input Multiplexes

Ad Mux

Optional SDT
The CAP-1000 supports the use of SDT functionality on non-DVB output muxes on upstream
devices (e.g. CAP-1000 / Cisco DCM). When the CAP-1000 is connected downstream, it correctly
detects the input mux type in the optional SDT tables at its input. To enable this feature, the
CAP-1000 ignores the SDT table when detecting the mux type. It uses the NIT table instead to
detect the mux type.
You can also use the Optional SDT function to set the Service Name and Service Provider Name.
See section,“Configuring Optional SDT, Service Names, and Service Provider Names,”on
page 274 for information.

Managing Gigabit Ethernet Input Multiplexes

This section covers the following topics:
• Detecting the Input Multiplex Type
• Creating Gigabit Ethernet Input Multiplexes
• Modifying Gigabit Ethernet Input Multiplexes
• Deleting Gigabit Ethernet Input Multiplexes

244 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Input Multiplexes

Detecting the Input Multiplex Type

By default, the CherryPicker Element Manager automatically detects the type of input multiplexes
on your CAP-1000. An input multiplex can be one of the following types:
• Auto
• MPEG-2
• DigiCipher II
• DVB
• ATSC
The CAP-1000 automatically detects the multiplex type based on the following parameters:
• If the input mux contains CAT with a GI CA system ID, then the detected type is DigiCipher
II.
• If the input mux contains MGT, then the detected type is ATSC.
• If the input mux contains SDT, then the detected type is DVB.
• If the PMT entry for program 0 points to 0x0010 (16) or the input mux has an NIT (PID 16) or
an SDT (PID 17), then the detected type is DVB.
• If the transport stream does not meet any of the other conditions, then the detected type is
MPEG-2.
• If the input mux has never been active, the type is MPEG-2.
Setting the Multiplex Type to Auto causes the mux type to be detected automatically and displayed
in the Detected Type field. You can override the detected type by setting the Multiplex Type to
MEPG2, DCII, ATSC, or DVB, in which case automatic detection is disabled.

Input Mux—Multiplex Type and Detected Type

CAP-1000 Software Guide v4.0 245

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Input Multiplexes

Overriding the Multiplex Type enables you to control how elementary streams with type code 128
and 129 are interpreted. After selecting the input mux type using the Multiplex Type option,
elementary streams with type code of 128 and 129 are treated according to the specifications in
Table 14-1.

Table 14-1 Stream Types

Stream Type MPEG2 DCII DVB ATSC

128 Video or Data (1) Video or Data (2) Data Video or Data (1)

129 or 6 Dolby Digital Plus Audio Dolby Digital Plus Dolby Digital Plus Audio Dolby Digital Plus Audio
or Dolby Digital Audio or Audio or Dolby Digital or Dolby Digital Audio or Dolby Digital Audio or
Data (3-8) Audio (3-8) or Data (3-8) Data (3-8)

If a type 128 stream contains a DCII extended video descriptor (tag 0x83), then the stream is
treated as video unless there is an MPEG2 or AVC video stream before it in the PMT, in which
case, the stream is interpreted as data. A type 128 stream with no DCII extended video descriptor
is treated as data.
1 A type 128 stream is treated as video regardless of any descriptors, unless there is an MPEG2
or AVC video stream before it in the PMT, in which cases the stream is interpreted as data.
2 If the mux type is DVB and the stream type is 6 or 129 and the DVB AC3 descriptor (tag
0x6A) or the DVB AC3 Plus descriptor (tag 0x7A) is present and the descriptor contains a
BSID (bit stream ID) greater than 8, then the stream is treated as AC3+.
3 If the mux type is DVB and the stream type is 6 or 129 and the DVB AC3 or AC3+ descriptor
is present and the descriptor contains a BSID less than or equal to 8, then the stream is treated
as AC3.
4 If the mux type is ATSC, DCII, or MPEG2 and the stream type is 129 and the ATSC AC3
Audio descriptor (tag 0x81) is present and the descriptor contains a BSID greater than 8, then
the stream is treated as AC3 Plus.
5 If the mux type is ATSC, DCII, or MPEG2 and the stream type is 129 and the ATSC AC3
Audio descriptor (tag 0x81) is present and the descriptor contains a BSID less than or equal to
8, then the stream is treated as AC3.
6 If the mux type is DCII and the AC3 Audio descriptor is not present, then the stream is treated
as AC3.
7 If none of the conditions above is met, then the stream is treated as data.

246 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Input Multiplexes

Creating Gigabit Ethernet Input Multiplexes

An input multiplex must be created to allow the CAP-1000 to receive a single IP/UDP
encapsulated MPEG Transport Stream (MPTS or SPTS). The creation of GigE input muxes is
restricted to the IOA ports. The maximum number of input multiplexes you can create is 900. The
same limit applies to both a single input port and a device as a whole.
If you want to apply EBIF filtering to output programs, ensure that you create an input multiplex
that accepts EISS streams and EBIF applications. See Chapter 26, “Managing EBIF,” for more
information.

IMPORTANT Before you can configure an input multiplex, the associated port must be enabled for MPEG traffic. See
Chapter 32, “Configuring Port Mirroring” for more information.

To create Gigabit Ethernet input multiplexes:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Click Create Input Mux.

Create Input Multiplex

CAP-1000 Software Guide v4.0 247

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Input Multiplexes

Table 14-2 Gigabit Ethernet Input Multiplex Parameters

Mux Name Shows the default name, Mux_ID, generated by the Controller or enter a user-
specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on the back
of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends a
sequential number to the name.

Input Line Selects the input port for the input multiplex.

UDP Connection Selects Unicast or Multicast.

• Unicast—Receives IP streams once into a network, but can be received only at a
single endpoint.
• Multicast—Receives IP packet flows once into a network, but can be received
by as many endpoints are required. Each endpoint must join the multicast group
by issuing an IGMP join request.

IP Address Enters the IP address for the unicast or multicast connection. For multicast
connections, enter the multicast IP address (valid range is 224.0.0.0 to
239.255.255.255).

UDP Port Enters the UDP port associated with the incoming stream from the host.

Bulk Option To create multiple input multiplexes at one time using consecutive numbering for
either IP addresses or ports, select this option.

• Number of Mux—Enter the last number for the range of UDP ports. This option
creates multiple input multiplexes with the same last port number and IP
address.

• Port Increment—Select this option to create multiple input multiplexes with the
same last port number and IP address.

• Last Octet Increment—Enter the last octet for the range of IP addresses.

Source IP Filter The input port can support multiple incoming multicast streams using the same IP
multicast, but different source IP addresses. To enable the CAP-1000 to un-filter
multicast traffic based on source IP address and UDP, a source IP filter can be
specified.
• To filter multicast traffic based on an IP address, specify the IP address of the
device that provides the Ethernet MPEG input to the device.
• A blank field indicates that there is no filtering based on IP address.
Note: The Source IP Filter can be specified only for a Ethernet multicast input
multiplex. A Source IP Filter cannot be specified for a Ethernet unicast input
multiplex.

248 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Input Multiplexes

Table 14-2 Gigabit Ethernet Input Multiplex Parameters (continued)

Mux Type Shows the input mux type for the input port. The options are:
• Auto
• MPEG-2
• DigiCipher II
• DVB
• ATSC

3 Enter the required information.

4 Click OK.
The input multiplex you created appears in the Mux panel of the Content Grooming window.

Gigabit Ethernet Input Multiplex

The status of the mux is “inactive” until it starts receiving input.

Modifying Gigabit Ethernet Input Multiplexes

To modify a Gigabit Ethernet input multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the GigE input multiplex you want.
4 In the GigE Input Muxes panel, select the parameter you want to edit.

CAP-1000 Software Guide v4.0 249

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Input Multiplexes

Gigabit Ethernet Input Multiplex

Table 14-3 Gigabit Ethernet Input Multiplex Parameters

ID Shows the input multiplex ID.

Name Shows the default name, Mux_ID, generated by the Controller or enter a user-
specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on the back
of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends a
sequential number to the name.
Note: You can rename a selected the mux in the Component Tree, by using the Edit
Name command in the Context menu.

UDP Connection Select Unicast or Multicast.

• Unicast—Receives IP streams once into a network, but can be received only at a
single endpoint.
• Multicast—Receives IP packet flows once into a network, but can be received
by as many endpoints are required. Each endpoint must join the multicast group
by issuing an IGMP join request.

IP Address For multicast connections, enter the multicast IP address (valid range is 224.0.0.0 to
239.255.255.255).

UDP Port Enter the UDP port associated with the incoming stream from the host.

250 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Input Multiplexes

Table 14-3 Gigabit Ethernet Input Multiplex Parameters (continued)

Source IP Filter The input port can support multiple incoming multicast streams using the same IP
multicast, but different source IP addresses. To enable the CAP-1000 to un-filter
multicast traffic based on source IP address and UDP, a source IP filter can be
specified.
• To filter multicast traffic based on an IP address, specify the IP address of the
device that provides the Ethernet MPEG input to the device.
• A blank field indicates that there is no filtering based on IP address.
Note: The Source IP Filter can be specified only for a Ethernet multicast input
multiplex. A Source IP Filter cannot be specified for a Ethernet unicast input
multiplex.

Multiplex Type Sets the input mux type for the input port. The options are:
• Auto
• MPEG-2
• DigiCipher II
• DVB
• ATSC

Detected Type Setting the Multiplex Type to Auto causes the mux type to be detected
automatically and displayed in the Detected Type field. You can override the
detected type by setting the Multiplex Type to MEPG2, DCII, ATSC, or DVB, in which
case automatic detection is disabled.
See section,“Detecting the Input Multiplex Type,”on page 245 for more
information.

Last Import Shows the name of the XML Configuration file imported to this mux. See Chapter
16, “Managing Configuration Files,” for more information.
Last Export Shows the name of the XML Configuration file exported from this mux.

DPI API Version DPI API Version is blank for all input muxes created by a user. A DPI input mux is
created by the CAP-1000 in response to an Init_Request made by an ad server (API
Standard ANSI/SCTE 30 2005 [DPI30]). This version is either ANSI/SCTE 30 Version
0 or 1.

EBIF Filter Bypass Excludes this input multiplex from EBIF filters (i.e. there is no filtering applied to any
EBIF data coming from this input multiplex). See Chapter 26, “Managing
EBIF” for more information.
Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this option.
See section,“Emergency Alert Service (EAS),”on page 242 and
Chapter 25, “Enabling Emergency Alert Messaging,” for more
information.

EAS Type Indicates if Emergency Alert Service (EAS) alerts are delivered using in-band
signaling or out-of-band signaling. For in-band signaling, the CAP-1000 receives
EAS alerts on any input multiplex from any number of input generators.

CAP-1000 Software Guide v4.0 251

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Input Multiplexes

Table 14-3 Gigabit Ethernet Input Multiplex Parameters (continued)

Details Channel Same Mux When this option is selected (checked), the EAS received on this mux is switched to
the selected details channel and program for playout.

Details Line Shows the IP address and port for the EAS input mux.

Details Mux Shows the details channel for use when the receiving device is navigating using
out-of-band service information (SI). In the case that out-of-band SI is not available,
the channel reference is through major/minor channel number.

Details Channel Shows the audio/video service and program pertaining to the alert.

Retain Program Names When this option is selected (checked), the program names are retained if the input
multiplex changes. The program names can be changed using the GUI or the
Configuration file. If the program names are changed, the Controller cannot change
the program names on the Service Description Table (SDT), Source Name Table
(SNT), or Virtual Channel Table (VCT) updates. In this case, the Controller takes the
default names without the SDT, SNT, or VCT updates. When this option is cleared
(unchecked), all the program names revert back to the default names.

BISS Mode Selects a Basic Interoperable Scrambling System mode when a BISS license is
installed:
• BISS (Mode 0)—Unscrambled (clear).
• BISS (Mode 1)—Scrambled with a session word (SW).
• BISS (Mode E)—Scrambled with an encrypted session word (ESW).
Note: Usages requires a CR-DSP module.
To set the Injection ID, see section,“Setting the Injected BISS
Identifier,”on page 80 for information.
Session Word Sets the type of BISS encryption to use. This field becomes editable when the BISS
Mode changes to Mode 1 or Mode E.
• Mode 1—A 12-digit hexadecimal session key. that is agreed by the transmitting
and receiving parties prior to transmission. The key is entered into both the
encoder and decoder. It then forms part of the encryption of the digital TV signal
and any receiver with BISS support with the correct key will decrypt the signal.
• Mode E—(E for encrypted) A 16-digit hexadecimal code, which is entered as a
session key. This session key is then mathematically combined internally to
calculate a BISS1 key that can decrypt the signal.

5 Enter the required information.

6 Click Apply.
A configuration window opens.
7 Click Yes.

252 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Input Multiplexes

Deleting Gigabit Ethernet Input Multiplexes

You can delete active or inactive input muxes. An active mux is labeled <mux name> in the
Component Tree. An inactive mux is labeled <mux name>[Inactive] in the Component tree.

NOTE You are not allowed to delete a DPI input mux. The CAP-1000 deletes the DPI input mux when it closes the
associated SCTE30 TCP/IP connection.

To delete a Gigabit Ethernet input multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the GigE input multiplex you want to delete.
4 In the GigE Input Muxes panel, select the multiplex ID under the ID column.
5 Do on of the following:
6 To delete an active mux, select Delete from the Context menu.
7 To delete an inactive mux, select Delete Inactive from the Context menu.

Gigabit Ethernet Input Multiplex

CAP-1000 Software Guide v4.0 253

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

A confirmation window opens.

WARNING All grooms associated with this multiplex are deleted.

8 Click Yes.

Managing Gigabit Ethernet Output Multiplexes

This section provides the following topics:
• Creating Gigabit Ethernet Output Multiplexes
• Modifying Gigabit Ethernet Output Multiplexes
• Deleting Gigabit Ethernet Output Multiplexes

Creating Gigabit Ethernet Output Multiplexes

An output multiplex must be created in order to allow a CAP-1000 to send MPEG transport
streams. The creation of GigE output muxes is restricted to the IOA ports. The maximum number
of output multiplexes you can create is 384 per port and 384 per device.

NOTE It is assumed that all 384 output multiplexes are used when the CAP-1000 is demultiplexing MPTS to SPTS.
In this case, you can configure 384 SPTS multiplexes on the output of the device. When not used as a de-
multiplexer, it is expected that the maximum number of output multiplexes will be 256 SPTS or MPTS.
When enabling 384 multiplexes and grooming 384 streams, PRED, DPI, and rate shaping cannot be used on
the device.

To create Gigabit Ethernet output multiplexes:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Click Create Output Mux.
The Create Output Mux dialog opens with the Basic tab selected.

254 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Output Multiplexes

Create Output Multiplex (Basic)

Table 14-4 Gigabit Ethernet Output Multiplex Parameters (Basic)

Mux Name Shows the default name, Mux_ID, generated by the Controller or enter a
user-specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on
the back of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends
a sequential number to the name.

Enable Loopback Enables or disables loopbacks on the selected output mux. This feature
allows every regular or rate-shaped, ad-inserted output multiplex to be
treated as an input multiplex under the same line. See
section,“Loopbacks,”on page 233 for more information.

Output Line Select the output line for this mux.

CAP-1000 Software Guide v4.0 255

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

Table 14-4 Gigabit Ethernet Output Multiplex Parameters (Basic) (continued)

UDP Connection Select Unicast or Multicast.

• Unicast—Receives IP streams once into a network, but can be received
only at a single endpoint.
• Multicast—Receives IP packet flows once into a network, but can be
received by as many endpoints are required. Each endpoint must join the
multicast group by issuing an IGMP join request.

IP Address Enter the IP address for the unicast or multicast connection. For multicast
connections, enter the multicast IP address (valid range is 224.0.0.0 to
239.255.255.255).

UDP Port Enter the UDP port associated with the incoming stream from the host.

Transport Stream ID Enter the MPEG transport stream ID for this multiplex or select Use Config
File TSID.

Bulk Option To create multiple output multiplexes at one time using consecutive
numbering for either IP addresses or ports, select this option.

• Number of Mux—Enter the last number for the range of UDP ports. This
option creates multiple output multiplexes with the same last port
number and IP address.

• Port Increment—Select this option to create multiple input multiplexes

with the same last port number and IP address.

• Last Octet Increment—Enter the last octet for the range of IP addresses.
See section,“Bulk Operations,”on page 240 for more information.

Padding Constant bit rate (CBR) streams are encoded at a set bit rate regardless of
the amount of information that needs to be stored. If there is not enough
video information to fill the allotted bandwidth, the encoder simply fills the
rest of the stream with null packets. Do one of the following:
• To enable padding, select Null Packet.
• To disable padding, select None.
Note: Variable bit rate streams do not use null packets to fill the stream to a
constant bit rate.

Mode Select one of the following:

• 64 QAM (6 MHz)
• 256 QAM (6 MHz)
• 64 QAM (8 MHz)
• 256 QAM (8 MHz)
• Custom
Selecting one of these options affects the Total Rate and Reserved Rate
parameters. See section,“Enabling Rate Shaping,”on page 442 for
more information.

Total Rate (Mbps) If you selected Custom for the Mode option, set the Total Rate you want.

256 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Output Multiplexes

Table 14-4 Gigabit Ethernet Output Multiplex Parameters (Basic) (continued)

Res Rate (Mbps) If you selected Custom for the Mode option, set the Reserved Rate you
want.

Current File Shows the current configuration file assigned to the output mux. To select a
new file, click the option you want. Only configuration files in the
/usr/cp/Config directory are displayed. See Chapter 16, “Managing
Configuration Files” for more information.

3 Enter the required information.

4 Select the Advanced tab.

Create Output Mux (Advanced)

Table 14-5 Gigabit Ethernet Output Multiplex Parameters (Advanced)

Protocol For unicast connections, this field specifies how the destination MAC
address is determined (either automatically using ARP or manually by
entering the MAC address).

RTP Select Enable to apply RTP headers to MPEG-2 transport streams and allow
the reconstruction of sender's packet sequence and detection of lost packets.
See section,“Real-time Transport Protocol Configuration,”on
page 235 for more information.
Note: A mirror GigE mux must use the same RTP setting as the primary.
Enabling or disabling the RTP header can be changed dynamically.

CAP-1000 Software Guide v4.0 257

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

Table 14-5 Gigabit Ethernet Output Multiplex Parameters (Advanced) (continued)

QoS Layer 2 Configures Quality of Service (QoS) at Layer 2 (data link) in the Open Systems
Interconnection (OSI) model. See section,“Quality of Service
Configuration (QoS),”on page 237 for more information.
Tagging Select Enable to allow the reception and transmission of 802.1Q virtual local
area network (VLAN) tagged frames for MPEG audio/video traffic carried
over UDP. The default is Disable. See section,“VLAN Tagging and
Prioritization,”on page 238 for more information.
VLAN (802.1Q) To identify the VLAN, enter a value to tag client traffic. The valid range for
the VLAN ID is 1 to 4094. The default VLAN ID is 0 (no VLAN).

Priority (802.1p) To enable some tagged frames to be forwarded ahead of others within a
switched Ethernet network, select a VLAN priority from 0 (lowest priority) to
7 (highest priority). The default priority value is Video (5). The valid values
are:
• Best Effort (0)
• Background (1)
• Spare (2)
• Excellent Effort (3)
• Controlled Load (4)
• Video (5)
• Voice (6)
• Network (7)

QoS Layer 3 Configures QoS at Layer 3 (network link) in the OSI model. See
section,“Quality of Service Configuration (QoS),”on page 237
for more information.

TTL Time-to-Live (TTL) specifies the number of routing hops a packet takes before
it is dropped from a Pro-MPEG FEC multiplex. The default is 128. The range is
1 to 255. This parameter is restricted to VIO adapter ports. See
section,“Time to Live (TTL),”on page 236 for more information.

Diffserv Codepoint (DSCP) Enables the CAP-1000 to mark outgoing elementary stream packets to use
Quality of Service (QoS) mechanisms implemented on your network. The
range for the Differentiated Services Code Point (DSCP) is 0 to 63. The
default value is 0 (Best Effort).

Precedence Specifies the level of service (relative importance) a packet receives on the
network:
0—Routine
1—Priority
2—Immediate
3—Flash
4— Flash Override
5—CRITIC/ECP (critical/emergency call processing)
6—Internetwork Control
7—Network Control

258 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Output Multiplexes

Table 14-5 Gigabit Ethernet Output Multiplex Parameters (Advanced) (continued)

The precedence values serve to differentiate among the various stream

flows based on the relative importance of the individual streams. When the
CAP-1000 implements precedence-ordered queue service, it ensures that a
packet with a certain priority is not transmitted until and unless all packets
with higher precedence values are transmitted. Similarly, the lower-layer
precedence mapping ensures that the packet priority is maintained at the
link level as well.

Delay A read-only parameter based on the DSCP selection.

• Normal—normal delay.
• Low—minimize delay.

Throughput A read-only parameter based on the DSCP selection.

• Normal—normal throughput.
• High—maximize throughput.

Reliability A read-only parameter based on the DSCP selection.

• Normal—normal reliability.
• High—maximize reliability.

5 Enter the required information.

6 Click OK.

Modifying Gigabit Ethernet Output Multiplexes

To modify a Gigabit Ethernet output multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the GigE output multiplex you want to modify.
4 In the GigE Output Muxes panel, select the parameter you want to edit.

CAP-1000 Software Guide v4.0 259

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

Gigabit Ethernet Output Multiplex

Table 14-6 Gigabit Ethernet Output Multiplex Parameters

ID Displays the read-only identifier for this multiplex.

Primary/Mirror ID Shows the ID of the primary port.

Name Shows the default name, Mux_ID, generated by the Controller or enter a
user-specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on
the back of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends
a sequential number to the name.
Note: You can rename a selected the mux in the Component Tree, by using
the Edit Name command in the Context menu.

Transport Stream ID Enter the MPEG transport stream ID for this multiplex.

UDP Connection Select Unicast or Multicast.

Destination IP Enter the Destination IP Address (of the edge QAM device or ingest device
for network PVR).

UDP Port Enter the UDP port associated with the destination Ethernet host (0 through
65535). Unless required by the downstream device, it is not recommended to
use UDP ports in the 0–1023 range.

Protocol For unicast connections, this field specifies how the destination MAC
address is determined (either automatically using ARP or manually by
entering the MAC address).

260 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Output Multiplexes

Table 14-6 Gigabit Ethernet Output Multiplex Parameters (continued)

MAC Address Specifies the Media Access Control addresses for the five configurable
ports.

Table Type Displays the table type.

Mode Select one of the following:

• 64 QAM (6 MHz)
• 256 QAM (6 MHz)
• 64 QAM (8 MHz)
• 256 QAM (8 MHz)
• Custom
Selecting one of these options affects the Total Rate and Reserved Rate
parameters. See section,“Enabling Rate Shaping,”on page 442 for
more information.

Total Rate (Mbps) Enter the total line rate. This option is read-only for all QAM and ATSC
modes. If you selected Custom for the Mode option, set the Total Rate you
want.

Res Rate (Mbps) If you selected Custom for the Mode option, set the Reserved Rate you
want.

Avail Rate (Mbps) Enter the available rate in Mbps. The default value is Total Rate.

Padding Constant bit rate (CBR) streams are encoded at a set bit rate regardless of
the amount of information that needs to be stored. If there is not enough
video information to fill the allotted bandwidth, the encoder simply fills the
rest of the stream with null packets. Do one of the following:
• To enable padding, select Null Packet.
• To disable padding, select None.
Note: Variable bit rate streams do not use null packets to fill the stream to a
constant bit rate.

Last Import Shows the name of the XML Configuration file imported to this mux. See
Chapter 16, “Managing Configuration Files,” for more information.
Last Export Shows the name of the XML Configuration file exported from this mux.

VLAN ID To identify the VLAN, enter a value to tag client traffic. The valid range for
the VLAN ID is 1 to 4094. The default VLAN ID is 0 (no VLAN).

CAP-1000 Software Guide v4.0 261

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

Table 14-6 Gigabit Ethernet Output Multiplex Parameters (continued)

VLAN Priority To enable some tagged frames to be forwarded ahead of others within a
switched Ethernet network, select a VLAN priority from 0 (lowest priority) to
7 (highest priority). The default priority value is Video (5). The valid values
are:
• Best Effort (0)
• Background (1)
• Spare (2)
• Excellent Effort (3)
• Controlled Load (4)
• Video (5)
• Voice (6)
• Network (7)

DSCP Enables the CAP-1000 to mark outgoing elementary stream packets to use
Quality of Service (QoS) mechanisms implemented on your network. The
range for the Differentiated Services Code Point (DSCP) is 0 to 63. The
default value is 0 (Best Effort). See section,“Quality of Service
Configuration (QoS),”on page 237 for more information.
RTP Select Enable to apply RTP headers to MPEG-2 transport streams and allow
the reconstruction of sender's packet sequence and detection of lost packets.
Note: A mirror GigE mux must use the same RTP setting as the primary.
Enabling or disabling the RTP header can be changed dynamically.

TTL Time-to-Live (TTL) specifies the number of routing hops a packet takes before
it is dropped from a Pro-MPEG FEC multiplex. The default is 128. The range is
1 to 255. This parameter is restricted to VIO adapter ports. See
section,“Time to Live (TTL),”on page 236 for more information.

Mux Redundancy Select this option to enable MRED. Refer to Chapter 28, “Configuring
Multiplex Redundancy” for more information.
Primary Input Mux Select the input multiplex containing the groomed primary programs.

Error Period Specifies the length of time during which the primary cannot recover from
error. If the primary cannot recover by the end of the interval, switching to
backup occurs. If the primary can recover, no switching occurs. The options
are: Min 1 second (in 1 second increments) / Max 100 seconds. The default is
2 seconds.

262 ARRIS Enterprises, Inc.

 Managing Gigabit Ethernet Output Multiplexes

Table 14-6 Gigabit Ethernet Output Multiplex Parameters (continued)

Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup program to
switch over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup program to
switch over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video
or the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup program to switch over if any video
stream underflows.
• First Audio Only—enables the backup program to switch over if the first
audio stream underflows.

Switch on Underflow‘ • Immediate—Specifies that switching to the backup input multiplex

should occur immediately.
• After Alarm Interval—Specifies that switching to the backup input
multiplex should occur after the alarm interval.

Backup Input Mux Select the backup multiplex containing the groomed backup programs.

Auto Switch Back Select to automatically switch back to the primary program when it is
restored.

Error Free Period Specifies the length of time in which the primary program must be error-free
before a switch is made back to the primary source. If errors are detected
and they cannot be resolved, the CAP-1000 does not switch back to the
primary program. The CAP-1000 remains with the backup program instead.
The options are: Min 7 seconds / Max 100 seconds. The default is 12
seconds (in 1-second increments). The longer the period of time, the more
certain you can be that the primary program is error free.

Loopback Enables or disables loopbacks on the selected output mux. This feature
allows every regular or rate-shaped, ad-inserted output multiplex to be
treated as an input multiplex under the same line. See
section,“Loopbacks,”on page 233 for more information.

Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this
option.
See section,“Emergency Alert Service (EAS),”on page 242 and
Chapter 25, “Enabling Emergency Alert Messaging,” for more
information.

State Code Selects a state code. Configures Federal Information Processing Standard
(FIPS) location codes for the Emergency Alert System (EAS).

Country Sub Division Selects a county sub-division.

County Code Selects a county code.

CAP-1000 Software Guide v4.0 263

Chapter 14 Configuring Multiplexes Managing Gigabit Ethernet Output Multiplexes

Table 14-6 Gigabit Ethernet Output Multiplex Parameters (continued)

MPEG Out Puts this GigE MPEG output mux (Tx) on standby. See section,“MPEG
Active and Standby Output Port States,”on page 243 for more
information.

BISS Mode Selects a Basic Interoperable Scrambling System mode when a BISS license
is installed:
• BISS (Mode 0)—Unscrambled (clear).
• BISS (Mode 1)—Scrambled with a session word (SW).
• BISS (Mode E)—Scrambled with an encrypted session word (ESW).
Note: Usages requires a CR-DSP module.
To set the Injection ID, see section,“Setting the Injected BISS
Identifier,”on page 80 for information.
Session Word Sets the type of BISS encryption to use. This field becomes editable when
the BISS Mode changes to Mode 1 or Mode E.
• Mode 1—A 12-digit hexadecimal session key. that is agreed by the
transmitting and receiving parties prior to transmission. The key is
entered into both the encoder and decoder. It then forms part of the
encryption of the digital TV signal and any receiver with BISS support
with the correct key will decrypt the signal.
• Mode E—(E for encrypted) A 16-digit hexadecimal code, which is entered
as a session key. This session key is then mathematically combined
internally to calculate a BISS 1 key that can decrypt the signal.

SDT Enables the use of Service Description Tables in non-DVB multiplexes for
naming services. This option is only available for muxes that use non-DVB
configuration files. See section,“Configuring Optional SDT, Service
Names, and Service Provider Names,”on page 274 for more
information.
Note: When the Path SDT feature is enabled, the Optional SDT feature is
disabled. See section,“Managing Path SDT,”on page 294 for more
information.

5 Enter the required information.

6 Click Apply.
A confirmation window opens.
7 Click Yes.

Deleting Gigabit Ethernet Output Multiplexes

To delete a Gigabit Ethernet output multiplex:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 In the Output panel, select the GigE output multiplex you want to delete.
3 Select Delete from the pop-up Context menu.

264 ARRIS Enterprises, Inc.

 Managing ASI Input Multiplexes

Gigabit Ethernet Output Multiplex

A confirmation window opens.

WARNING All grooms associated with this multiplex are deleted.

4 Click Yes.
5 Click Apply.

Managing ASI Input Multiplexes

This section contains the following topics:
• Modifying ASI Input Multiplexes
• Clearing ASI Input Multiplexes

IMPORTANT You cannot create or delete ASI multiplexes. An ASI input mux is created for the ASI connection even when
no cable is connected. In this case, the mux type is undetermined and the list of tables under the mux is
empty.

Modifying ASI Input Multiplexes

To modify an ASI input multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Mux.

CAP-1000 Software Guide v4.0 265

Chapter 14 Configuring Multiplexes Managing ASI Input Multiplexes

2 Expand the Component Tree.

3 In the Component Tree, select the ASI input multiplex you want.

ASI Input Multiplex

4 In the ASI Input Muxes panel, select the parameter you want to edit.

ASI Input Multiplex

266 ARRIS Enterprises, Inc.

 Managing ASI Input Multiplexes

Table 14-7 ASI Input Multiplex Parameters

ID Shows the input multiplex ID.

Name Shows the default name, Mux_ID, generated by the Controller, or enter a user-
specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on the back
of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends a
sequential number to the name.
Note: You can rename a selected the mux in the Component Tree, by using the Edit
Name command in the Context menu.

Transport Stream ID Shows the transport stream ID on this multiplex.

Multiplex Type Sets the input mux type for the input port. The options are:
• Auto
• MPEG-2
• DigiCipher II
• DVB
• ATSC

Detected Type Setting the Multiplex Type to Auto causes the mux type to be detected
automatically and displayed in the Detected Type field. You can override the
detected type by setting the Multiplex Type to MEPG2, DCII, ATSC, or DVB, in which
case automatic detection is disabled.
See section,“Detecting the Input Multiplex Type,”on page 245 for more
information.

Last Import Shows the name of the XML Configuration file imported to this mux. See Chapter
16, “Managing Configuration Files,” for more information.
Last Export Shows the name of the XML Configuration file exported from this mux.

DPI API Version DPI API Version is blank for all input muxes created by a user. A DPI input mux is
created by the CAP-1000 in response to an Init_Request made by an ad server (API
Standard ANSI/SCTE 30 2005 [DPI30]). This version is either ANSI/SCTE 30 Version
0 or 1.

EBIF Filter Bypass Excludes this input multiplex from EBIF filters (i.e. there is no filtering applied to any
EBIF data coming from this input multiplex). See Chapter 26, “Managing
EBIF” for more information.
Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this option.
See section,“Emergency Alert Service (EAS),”on page 242 and
Chapter 25, “Enabling Emergency Alert Messaging,” for more
information.

CAP-1000 Software Guide v4.0 267

Chapter 14 Configuring Multiplexes Managing ASI Input Multiplexes

Table 14-7 ASI Input Multiplex Parameters (continued)

EAS Type Indicates if Emergency Alert Service (EAS) alerts are delivered using in-band
signaling or out-of-band signaling. For in-band signaling, the CAP-1000 receives
EAS alerts on any input multiplex from any number of input generators.

Details Channel Same Mux When this option is selected (checked), the EAS received on this mux is switched to
the selected details channel and program for playout.

Details Line Shows the IP address and port for the EAS input mux.

Details Mux Shows the details channel for use when the receiving device is navigating using
out-of-band service information (SI). In the case that out-of-band SI is not available,
the channel reference is through major/minor channel number.

Details Channel Shows the audio/video service and program pertaining to the alert.

Retain Program Names When this option is selected (checked), the program names are retained if the input
multiplex changes. The program names can be changed using the GUI or the
Configuration file. If the program names are changed, the Controller cannot change
the program names on the Service Description Table (SDT), Source Name Table
(SNT), or Virtual Channel Table (VCT) updates. In this case, the Controller takes the
default names without the SDT, SNT, or VCT updates. When this option is cleared
(unchecked), all the program names revert back to the default names.

BISS Mode Selects a Basic Interoperable Scrambling System mode when a BISS license is
installed:
• BISS (Mode 0)—Unscrambled (clear).
• BISS (Mode 1)—Scrambled with a session word (SW).
• BISS (Mode E)—Scrambled with an encrypted session word (ESW).
Note: Usages requires a CR-DSP module.

Session Word Sets the type of BISS encryption to use. This field becomes editable when the BISS
Mode changes to Mode 1 or Mode E.
• Mode 1—A 12-digit hexadecimal session key. that is agreed by the transmitting
and receiving parties prior to transmission. The key is entered into both the
encoder and decoder. It then forms part of the encryption of the digital TV signal
and any receiver with BISS support with the correct key will decrypt the signal.
• Mode E—(E for encrypted) A 16-digit hexadecimal code, which is entered as a
session key. This session key is then mathematically combined internally to
calculate a BISS 1 key that can decrypt the signal.

5 Enter the required information.

6 Click Apply.
A configuration window opens.
7 Click Yes.

268 ARRIS Enterprises, Inc.

 Managing ASI Output Multiplexes

Clearing ASI Input Multiplexes

When connecting a new ASI input port or changing from one source to another, it is important to
clear the ASI input multiplex. When the CAP-1000 loses an input it, it assumes that a new input is
the same as the last. This is done so that services can be recovered more quickly if a port goes
down.

To clear an ASI input multiplex:

1 Disconnect the physical input port.
2 From the CherryPicker Element Manager, click Content Picking > Mux.
3 Expand the Component Tree.
4 In the Component Tree, select the ASI Input Multiplex node you want to clear.
The port status should be “Not Responding.”
5 In the ASI Input Muxes panel, select the multiplex ID under the ID column.
6 Select Clear from the pop-up Context menu.
This action erases all previously stored data associated with the input port and updates the software
with the new input settings.
7 Reconnect the port to acquire the new data.

Managing ASI Output Multiplexes

This section covers the following topics:
• Changing an ASI Input Multiplex to an ASI Output Multiplex
• Modifying ASI Output Multiplexes

IMPORTANT You cannot create or delete ASI multiplexes. By default, ASI multiplexes are automatically created when a
physical cable for the card is connected to the CAP-1000.

Changing an ASI Input Multiplex to an ASI Output Multiplex

To change an ASI input multiplex to an output:
From the CherryPicker Element Manager, click Setup > System > ASI.
Select the port you want to change.
In the Type parameter, select Output.
1 Click Apply.
A configuration window opens.
2 Click Yes.

CAP-1000 Software Guide v4.0 269

Chapter 14 Configuring Multiplexes Managing ASI Output Multiplexes

Modifying ASI Output Multiplexes

To modify an ASI output multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the ASI output multiplex you want.
4 In the ASI Output Muxes panel, select the parameter you want to edit.

ASI Output Multiplex

Table 14-8 ASI Output Multiplex Parameters

ID Displays the read-only identifier for this multiplex.

Name Shows the default name, Mux_ID, generated by the Controller, or enter a user-
specified name.
• <slot> is the slot label, namely, 3 and 4, as seen on the Ethernet card on the back
of the CAP-1000.
• <port> is the port number, such as 1, 2, 3, etc.
If multiple muxes are created using a bulk operation, the CAP-1000 appends a
sequential number to the name.
Note: You can rename a selected the mux in the Component Tree, by using the Edit
Name command in the Context menu.

Transport Stream ID Displays the output multiplex transport stream ID.

Table Type Displays the table type.

270 ARRIS Enterprises, Inc.

 Managing ASI Output Multiplexes

Table 14-8 ASI Output Multiplex Parameters (continued)

Last Import Shows the name of the XML Configuration file imported to this mux. See Chapter
16, “Managing Configuration Files,” for more information.
Last Export Shows the name of the XML Configuration file exported from this mux.

Mux Redundancy Select this option to enable MRED. Refer to Chapter 28, “Configuring
Multiplex Redundancy” for more information.
Primary Input Mux Select the input multiplex containing the groomed primary programs.

Error Period Specifies the length of time during which the primary cannot recover from error. If
the primary cannot recover by the end of the interval, switching to backup occurs. If
the primary can recover, no switching occurs. The options are: Min 1 second (in 1
second increments) / Max 100 seconds. The default is 2 seconds.

Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream. The
options are:
• Any Video/Audio Stream Underflow—enables the backup program to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup program to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or the
first audio stream underflows. The first audio is the first audio elementary
stream in PMT of output program.
• Video Only—enables the backup program to switch over if any video stream
underflows.
• First Audio Only—enables the backup program to switch over if the first audio
stream underflows.

Switch on Underflow • Immediate—Specifies that switching to the backup input multiplex should occur
immediately.
• After Alarm Interval—Specifies that switching to the backup input multiplex
should occur after the alarm interval.

Backup Input Multiplex Selects the backup multiplex containing the groomed backup programs.

Auto Switch Back Automatically switches back to the primary program when it is restored.

Error Free Period Specifies the length of time in which the primary program must be error-free before
a switch is made back to the primary source. If errors are detected and they cannot
be resolved, the CAP-1000 does not switch back to the primary program. The CAP-
1000 remains with the backup program instead. The options are: Min 7 seconds /
Max 100 seconds. The default is 12 seconds (in 1-second increments). The longer
the period of time, the more certain you can be that the primary program is error
free.

Loopback Enables or disables loopbacks on the selected output mux. This feature allows
every regular or rate-shaped, ad-inserted output multiplex to be treated as an input
multiplex under the same line. See section,“Loopbacks,”on page 233 for more
information.

CAP-1000 Software Guide v4.0 271

Chapter 14 Configuring Multiplexes Managing ASI Output Multiplexes

Table 14-8 ASI Output Multiplex Parameters (continued)

Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this option.
See section,“Emergency Alert Service (EAS),”on page 242 and
Chapter 25, “Enabling Emergency Alert Messaging,” for more
information.

State Code Selects a state code. Configures Federal Information Processing Standard (FIPS)
location codes for the Emergency Alert System (EAS).

Country Sub Division Selects a county sub-division.

County Code Selects a county code.

MPEG Out Puts this ASI MPEG output mux (Tx) on standby. See section,“MPEG Active
and Standby Output Port States,”on page 243 for more information.
BISS Mode Selects a Basic Interoperable Scrambling System mode when a BISS license is
installed:
• BISS (Mode 0)—Unscrambled (clear).
• BISS (Mode 1)—Scrambled with a session word (SW).
• BISS (Mode E)—Scrambled with an encrypted session word (ESW).
Note: Usages requires a CR-DSP module.

Session Word Sets the type of BISS encryption to use. This field becomes editable when the BISS
Mode changes to Mode 1 or Mode E.
• Mode 1—A 12-digit hexadecimal session key. that is agreed by the transmitting
and receiving parties prior to transmission. The key is entered into both the
encoder and decoder. It then forms part of the encryption of the digital TV signal
and any receiver with BISS support with the correct key will decrypt the signal.
• Mode E—(E for encrypted) A 16-digit hexadecimal code, which is entered as a
session key. This session key is then mathematically combined internally to
calculate a BISS 1 key that can decrypt the signal.

SDT Enables the use of Service Description Tables in non-DVB multiplexes for naming
services. This option is only available for muxes that use non-DVB configuration
files. See section,“Configuring Optional SDT, Service Names, and
Service Provider Names,”on page 274 for more information.
Note: When the Path SDT feature is enabled, the Optional SDT feature is disabled.
See section,“Managing Path SDT,”on page 294 for more information.

5 Enter the required information.

6 Click Apply.
A configuration window opens.
7 Click Yes.

272 ARRIS Enterprises, Inc.

 Configuring GPS Offset and Daylight Savings Time

Configuring GPS Offset and Daylight Savings Time

You can specify if Daylight Savings Time (DST) is observed at a headend for a specific multiplex,
and if so, when the DST starts and ends. By default, DST is not observed. If DST is observed, you
must specify the current GPS UTC offset (13 seconds as of January 2001) and when it takes effect.

NOTE The GPS offset feature is only available when an ATSC configuration file is loaded on the CAP-1000. When
the file is loaded, additional parameters appear for the output multiplex.

To configure GPS offset and DST:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the output multiplex you want.
4 In the Output Muxes panel, select an active GigE or ASI output multiplex with an ATSC
Configuration file as identified in the Last Export column.

Gigabit Ethernet Output Multiplex—ATSC Configuration File

5 Select PSIP from the pop-up Context menu.

CAP-1000 Software Guide v4.0 273

Chapter 14 Configuring Multiplexes Configuring Optional SDT, Service Names, and Service Provider Names

Modify STT/EIT/ETT

6 Enter the GPS UTC offset in seconds

7 To enable DST, do the following:
a Select the Daylight Savings option.
b Enter the Start/End date and time in UTC format.
8 Click OK.

Configuring Optional SDT, Service Names, and Service Provider

Names
The CAP-1000 supports the use of the Service Description Table (SDT) on non-DVB output
muxes on upstream devices (e.g. CAP-1000 / Cisco DCM). When the CAP-1000 is connected
downstream, it correctly detects the input mux type in the optional SDT tables at its input. To
enable this feature, the CAP-1000 ignores the SDT table when detecting the mux type. It uses the
NIT table instead to detect the mux type.
Two modes are available for configuring “Optional SDT” on new or existing non-DVB output
multiplexes:
• Enable /disable the Optional SDT flag in the Configuration file. If the flag is not in the
Configuration file, Optional SDT is disabled for the output mux. This is the default option.

274 ARRIS Enterprises, Inc.

 Configuring Optional SDT, Service Names, and Service Provider Names

If you export or import a Configuration file that has the Optional SDT, Service Names, and
Service Provider Name flags, the CAP-1000 retains these settings in the file.
See Chapter 16, “Managing Configuration Files,” for more information.
• Enable/disable the STD check box on the GigE or ASI Output Multiplex panel in the Mux tab
of the Content Picking window.
You can enable or disable Optional SDT at any time. Once enabled, the input SDT, if present, is
passed to the output SDT for output programs currently groomed from that input. If the input SDT
is not present, the CAP-1000 does not add the entry for the output program in the output SDT
table. You can enter the Service Name and Service Provider Name for those output programs so
the CAP-1000 will add them to the output SDT.
The default rate for Optional SDT tables is 1800 milliseconds. You can configure this rate in the
Configuration file.

NOTE When the Path SDT feature is enabled, the Optional SDT feature is disabled.

Service Names and Service Provider Names

When Optional SDT is enabled for a non-DVB output mux, you can enter the Service Name and
Service Provider Name for the grooms. If the output program for a program or custom groom has
video, the output SDT for the program will follow the input SDT associated with the input video
PID. If the output program does not have video, the output SDT will follow the input SDT
associated with the first component in the groom. During ad insertion, the output SDT always
follows the input SDT associated with the current network input.
The Service Name is displayed for each input program in non-DVB input muxes in the
Configuration tree. The CAP-1000 will not replace the service name with the input program name
(either the default names, the short name from ATSC VCT table, or the name from the DCII source
name table). The SERVICE NAME is appended to the end of the program label.

Redundancy
In a CherryPicker Redundancy (CPR) configuration, the mux settings for Optional SDT and user-
provided Service Names/Service Provider Names are automatically virtualized in the CAP-1000.
In either a program (PRED) or multiplex (MRED) configuration, the Service Name and Service
Provider Name in the output SDT table follow the backup input.

Restrictions
If you enable Optional SDT for a new output mux and SDT PID 17 is used in a Configuration file,
the output mux fails with PID conflict error. If SDT PID 17 is in use or reserved for an output
program or a different table in the output mux, you cannot enable Optional SDT.
If you enable Optional SDT for a new output mux and then apply a Configuration file, the mux
creation fails.

CAP-1000 Software Guide v4.0 275

Chapter 14 Configuring Multiplexes Configuring Optional SDT, Service Names, and Service Provider Names

When Optional SDT is disabled for the output mux, all user-supplied Service Names or Service
Provider Names are lost.

Enabling Optional SDT

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the non-DVB GigE or ASI output multiplex you want to modify.
4 In the Output Muxes panel, select the SDT check box.

Optional SDT

5 Click Apply.
6 Click Content Picking > Grooming.
7 In the Output Mux menu, select the non-DVB GigE or ASI mux you just configured for SDT.
Verify that you have selected a non-DVB mux in the Table Type or Last Import (Configuration
file) columns.
8 (Optional) In the Properties panel on the right, edit the Service Name and Service Provider Name
fields with the names you want.
• Service Provider Name—Shows the Service Provider Name passed from the input (if the
input has a Service Provider Name in the DVB SDT). You can override this name in the output
SDT.
• Service Name—Shows the service name passed from input (if the input has a Service Name
in the DVB SDT). You can override this name in the output SDT.

276 ARRIS Enterprises, Inc.

 Configuring Optional SDT, Service Names, and Service Provider Names

Properties

9 Click Apply.

Disabling Optional SDT

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the non-DVB GigE or ASI output multiplex you want to modify.
4 In the Output Muxes panel, clear the SDT check box.
5 Click Apply.

CAP-1000 Software Guide v4.0 277

Chapter 14 Configuring Multiplexes Configuring Optional SDT, Service Names, and Service Provider Names

278 ARRIS Enterprises, Inc.

 CHAPTER 15
Managing Tables and Output
Programs
In This Chapter
• Tables
• Viewing Table Parameters
• Modifying STT, EIT, and ETT
• Modifying VCT
• Managing Path SDT
• Creating Custom NIT
• Generating TOT
• Managing Output Programs
• Managing Closed Captioning Conversion

Tables
Each multiplex consists of tables and programs. Tables are groups of structured information that
describe programs, program components, or other information that is related to the delivery and
decoding of programs. Selecting the Tables tab for an output multiplex in the CherryPicker
Element Manager lets you view information about MPEG, DVB PSI, and ATSC PSIP tables.

CAP-1000 Software Guide v4.0 279

Chapter 15 Managing Tables and Output Programs Tables

Tables

DVB SI Tables
The DVB Service Information (SI) data is structured into four types of tables. The tables are
transmitted in sections.

280 ARRIS Enterprises, Inc.

 Tables

Table Organization for Service Information (SI)

Table 15-1 PSI Tables

Program Association Table (PAT) For each service in the multiplex, the PAT indicates the location (the Packet
Identifier (PID) values of the Transport Stream (TS) packets) of the
corresponding Program Map Table (PMT). It also gives the location of the
Network Information Table (NIT).

Conditional Access Table (CAT) Provides information on the CA systems used in the multiplex; the information
is private (not defined within the present document) and dependent on the CA
system, but includes the location of the EMM stream, when applicable.

Program Map Table (PMT) Identifies and indicates the locations of the streams that make up each
service, and the location of the Program Clock Reference (PCR) fields for a
service.

Network Information Table (NIT) Provides information about the physical network.

CAP-1000 Software Guide v4.0 281

Chapter 15 Managing Tables and Output Programs Tables

Table 15-1 PSI Tables (continued)

Program Association Table (PAT) For each service in the multiplex, the PAT indicates the location (the Packet
Identifier (PID) values of the Transport Stream (TS) packets) of the
corresponding Program Map Table (PMT). It also gives the location of the
Network Information Table (NIT).

Bouquet Association Table (BAT) Provides information regarding bouquets. As well as giving the name of the
bouquet, it provides a list of services for each bouquet.

Service Description Table (SDT) Contains data describing the services in the system such as the names of
services and the service provider.

Event Information Table (EIT) Contains data concerning events or programs such as event name, start time,
duration, etc. The use of different descriptors allows the transmission of
different kinds of event information for different service types.

Running Status Table (RST) Gives the status of an event (running/not running). The RST updates this
information and allows timely automatic switching to events.

Time and Date Table (TDT) Gives information relating to the present time and date. This information is
given in a separate table due to the frequent updating of this information.

Time Offset Table (TOT) Gives information relating to the present time and date and local time offset.
This information is given in a separate table due to the frequent updating of
the time information.

Stuffing Table (ST) An optional DVB-SI table that authorizes the replacement of complete tables
due to invalidation at a delivery system boundary, such as a cable headend.

ATSC PSIP Tables

The Program and System Information Protocol (PSIP) is a small collection of hierarchically
arranged tables designed to operate within every Transport Stream for terrestrial broadcast of
digital TV. Its purpose is to describe the information at the system and event levels for all virtual
channels carried in a particular Transport Stream.
Whenever an output multiplex is configured as an ATSC multiplex, the CAP-1000 inserts the PSIP
tables into the multiplex, regardless if they are present at the groomed inputs or not. The device
preserves the general input PSIP information, but may modify the numerical value to make the
output table compliant with the PSIP standards (for example, the channel major and minor
numbers may have to be changed).

282 ARRIS Enterprises, Inc.

 Tables

Table Hierarchy for the Program and System Information Protocol (PSIP)
This section describes tables that shall be applicable to terrestrial (over-the-air) and cable signals.
Some PSIP tables apply to terrestrial broadcast, some apply to cable, and others apply to both.

Terrestrial Broadcast
The following PSIP data is included in all ATSC-compliant transport streams that are transmitted
via terrestrial broadcast. Every digital Transport Stream in terrestrial broadcast must include the
STT, the RRT, the TVCT, the MGT, and the first four Event Information Tables (EIT-0, EIT-1,
EIT-2, and EIT-3). All other EITs, as well as the ETTs, are optional.

CAP-1000 Software Guide v4.0 283

Chapter 15 Managing Tables and Output Programs Tables

Table 15-2 Terrestrial Broadcast PSIP Tables

Terrestrial Virtual Channel Table Defines, at a minimum, MPEG-2 programs embedded in the Transport Stream
(TVCT) in which the TVCT is carried.

Master Guide Table (MGT) Defines the type, packet identifiers, and versions for all the other PSIP tables
in this Transport Stream, except for the System Time Table (STT).

Rating Region Table (RRT) Defines the TV parental guideline system referenced by any content advisory
descriptor carried within the Transport Stream.

System Time Table (STT) Defines the current date and time of day.

Event Information Table (EIT) The first four Event Information Tables (EIT-0, EIT-1, EIT-2 and EIT-3) describes
12 hours of events (TV programs), each with a coverage of 3 hours, and
includes all of the virtual channels listed in the TVCT.

Cable
The following PSIP data is included in all ATSC-compliant transport streams that are transmitted
via cable. The required tables for a cable system are the STT, the RRT, the CVCT, and the MGT.

Table 15-3 Cable PSIP Tables

Cable Virtual Channel Table Defines, at a minimum, the virtual channel structure for the collection of
(CVCT) MPEG-2 programs embedded in the Transport Stream in which the CVCT is
carried.

Master Guide Table (MGT) Defines the type, packet identifiers, and versions for all of the other PSIP
tables included in this Transport Stream except for the System Time Table
(STT).

Rating Region Table (RRT) Defines the TV parental guideline system referenced by any content advisory
descriptor carried within the Transport Stream.

System Time Table (STT) Defines the current date and time of day.

When grooming by program, elementary stream, or file to a particular output, the CAP-1000
automatically creates the output PAT (if one does not exist already). For DVB-compliant
multiplexes, the CAP-1000 automatically creates NIT, SDT, EIT and TDT. For ATSC, the
CAP-1000 automatically creates STT, MGT and RRT. You need to create the TVCT/CVCT tables.

Emergency Alert Message (EAM) Table

For the special case of SCTE 18, the CAP-1000 creates a blank Emergency Alert Message (EAM)
table entry for every input multiplex. This function provides the ability to pass the SCTE 18 table
to the output multiplexes of the device. To groom or pass an incoming SCTE 18 stream to an
ATSC output multiplex, both MGT and SCTE 18 are carried on the same 0x1FFB output PID. The
GUI displays EAM 216 (Ext 7) (PID 8187) node under Tables node for every input multiplex. See
Chapter 25, “Enabling Emergency Alert Messaging,” for more information.

284 ARRIS Enterprises, Inc.

 Viewing Table Parameters

Viewing Table Parameters

To view table parameters:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the Table you want.
4 At the bottom of the window, click Tables.
Information about a specific table displays in the Tables panel.

Tables

Modifying STT, EIT, and ETT

You can modify the STT, EIT, and ETT tables for an ATSC output mux.

NOTE This feature is only available when an ATSC configuration file is loaded on an output multiplex. When the
file is loaded, additional parameters appear for the output multiplex. See Chapter 16, “Managing
Configuration Files” for more information.

CAP-1000 Software Guide v4.0 285

Chapter 15 Managing Tables and Output Programs Modifying STT, EIT, and ETT

STT
The System Time Table carries time information needed for any application requiring
synchronization. To convert GPS into local time, the receiver needs to store a time offset (from
GPS to local time) in local memory and an indicator as to whether daylight savings is observed.
Because GPS is transmitted in the PSIP, a mechanism is needed to indicate when the receiver
should switch into (or out of) daylight savings time at the appropriate local time. Once all the
receivers have transitioned at their local times, the entire system can be shifted into daylight
savings time. This is accomplished by setting of the Daylight Savings parameter in the STT.

ETT
The Extended Text Table contains Extended Text Message (ETM) streams that provide detailed
descriptions of virtual channels (channel ETM) and events (event ETM). For example, an ETM
may represent a description in several different languages.

EIT
The Event Information Table contains information (titles, start times, etc.) for events on defined
virtual channels. Its purpose is to list all events for those channels that appear in the VCT for a
given time window.
The EITs are sequentially and chronologically organized from EIT-0 to EIT-127. The first table
(EIT-0), corresponds to the currently valid list of events. The second table (EIT-1) corresponds to
the next time window, and so on.
During remultiplexing, EIT tables that originally existed in separate transport streams can be
multiplexed into a common Transport Stream, or vice versa. For this reason, it is convenient to
synchronize the start times and durations of the EITs. Consequently, the next three synchronization
rules must be followed when EIT tables are prepared:
• Each EIT has a duration of 3 hours.
• Start times for EITs are restricted to 0:00 (midnight), 3:00, 6:00, 9:00, 12:00 (noon), 15:00,
18:00 and 21:00. All of these times are UTC.
• EIT-0 lists all of the available events for the current 3-hour time segment. EIT-1 lists all of the
available events for the next 3-hour time segment, and likewise, non-overlapping sequential
time windows are allocated for all of the other EITs.
PSIP supports up to 128 EITs, each of which provides the event information for a certain time
span. For terrestrial broadcast, at least the first four EITs must be included in the Transport Stream.

286 ARRIS Enterprises, Inc.

 Modifying STT, EIT, and ETT

Modifying STT, ETT, and EIT

To modify STT, ETT, and EIT:

NOTE The GPS offset feature is only available when an ATSC configuration file is loaded on the CAP-1000. When
the file is loaded, additional parameters appear for the output multiplex.

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the output multiplex you want.
4 In the Output Muxes panel, select an active GigE or ASI output multiplex with an ATSC
Configuration file.
Configuration files are listed under the Table Type column.

Gigabit Ethernet Output Multiplex—ATSC Configuration File

5 Select PSIP from the pop-up Context menu.

CAP-1000 Software Guide v4.0 287

Chapter 15 Managing Tables and Output Programs Modifying STT, EIT, and ETT

Modify STT/EIT/ETT

Table 15-4 Modifying EIT/ETT Tables Parameters

STT

GPS Offset (seconds) Defines the current offset in whole seconds between GPS and UTC time
standards.

Daylight Savings Indicates whether to observe Daylight Savings Time (DST).

Start Sets the start of DST in MM/DD/YYYY and HH:MM AM/PM.

End Sets the end of DST in MM/DD/YYYY and HH:MM AM/PM.

EIT

Tables passed Min 0 / Max 8.

EIT 0 interval Min 16 / Max 500 ms. The default cycle time is 0–0.295 seconds.

EIT 1 interval Min 16 / Max 3000 ms. The default cycle time is 1–0.294 seconds.

EIT 2 (and greater intervals) Min 16 / Max 60000 ms. The default cycle time is 59.94 minute.

ETT

Pass Channel table Sets channel table to pass to output.

Event Tables passed Min 0 / Max 8.

ETT Tables intervals Interval applied to both channel and event ETT tables. Min 16 / Max 60000.

288 ARRIS Enterprises, Inc.

 Modifying VCT

6 Make any required changes.

7 Click OK.

Modifying VCT
The CAP-1000 generates the Virtual Channel Tables (VCT) at the output of a multiplex designated
as an ATSC multiplex. You can modify the VCT, Terrestrial Virtual Channel Table (TVCT), and
Cable Virtual Channel Table (CVCT) as needed.

NOTE This feature is only available when an ATSC configuration file is loaded on an output multiplex. When the
file is loaded, additional parameters appear for the output multiplex. See Chapter 16, “Managing
Configuration Files” for more information.

VCT
The VCT contains a list of attributes for virtual channels carried in the transport stream. The basic
information contained in the VCT table body includes transport stream ID, channel number (major
and minor), short channel name, program number, access-controlled flag, location field for
extended text messages, and service type. Additional information can be carried by descriptors
which may be placed in the descriptor loop after the basic information.

TVCT
The CAP-1000 generates this table at the output of a multiplex designated as an ATSC multiplex.
No TVCT is generated until at least one program is groomed and the TVCT parameters have been
provided via the GUI. The maximum cycle time is 400 milliseconds.
The TVCT defines basic information about virtual channels in the transport stream and optionally,
other transport streams. For terrestrial stations, a TVCT is a mandatory PSIP table that lists all the
virtual channels available in an ATSC transport stream, and optionally, virtual channels available
in other ATSC transport streams.

CVCT
The CAP-1000 generates this table at the output of a multiplex designated as an ATSC multiplex.
No CVCT is generated until at least one program is groomed and the CVCT parameters have been
provided via the GUI. The maximum cycle time is 400 milliseconds.
When a broadcaster wants to use different channel labeling or numbering (or both) between cable
and terrestrial broadcast, or when a broadcaster has coordinated consistent channel labeling and
numbering with all local cable operators carrying that multiplex, the CVCT may be used.
When both CVCT and TVCT are present in a transport stream, receiving devices are expected to
use the TVCT to navigate services received via terrestrial broadcast and the CVCT to navigate
services received via cable.

CAP-1000 Software Guide v4.0 289

Chapter 15 Managing Tables and Output Programs Modifying VCT

Modifying VCT

To modify VCT:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the GigE or ASI Output Multiplex you want.
3 In the GigE or ASI Output Muxes panel, click the Programs tab at the bottom of the window and
select the program you want.
4 Click VCT from the pop-up Context menu.

VCT

290 ARRIS Enterprises, Inc.

 Modifying VCT

Modify VCT

5 Click the CVCT and/or TVCT option.

Additional parameters appear.

CAP-1000 Software Guide v4.0 291

Chapter 15 Managing Tables and Output Programs Modifying VCT

Modify VCT

Table 15-5 Modify VCT Parameters

Program Number A 16-bit integer number that associates the virtual channel being defined here with
the MPEG-2 PROGRAM ASSOCIATION and TS PROGRAM MAP tables.

Short Name The name of the virtual channel, represented as a sequence of one to seven 16-bit
code values interpreted in accordance with the UTF-16 representation of Unicode
character data.

Major Channel A 10-bit number representing the “major” channel number associated with the
virtual channel being defined in this iteration of the “for” loop. Each virtual channel
shall be associated with a major and a minor channel number. The major channel
number, along with the minor channel number, act as the user’s reference number
for the virtual channel. Enter 0–999. This is a required field.
Note: For TVCT, the valid major numbers are from 1 to 99.

Minor Channel A 10-bit number in the range 0 to 999 that represents the “minor” or “sub”- channel
number. This field, together with major_channel_number, performs as a two-part
channel number, where minor_channel_number represents the second or right-
hand part of the number. Enter 0–999. This is a required field.

292 ARRIS Enterprises, Inc.

 Modifying VCT

Table 15-5 Modify VCT Parameters (continued)

One Part Channel A 10-bit field representing a one-part virtual channel number associated with the
virtual channel defined in this iteration of the “for” loop. One-part numbers range
from 0 to 16,383.

Modulation Mode An 8-bit integer number indicating the modulation mode for the transmitted carrier
associated with this virtual channel. For digital signals, the standard values for
modulation mode (values below 0x80) indicate transport framing structure, channel
coding, interleaving, channel modulation, forward error correction, symbol rate, and
other transmission-related parameters, by means of a reference to an appropriate
standard.

Carrier Frequency The recommended value for these 32 bits is zero. Use this field to identify carrier
frequency is allowed, but is deprecated. After January 1, 2010, these 32 bits shall
be set to zero.

Transport Stream ID Displays the Mux ID of this program.

ETM Location A 2-bit field that specifies the existence and the location of an Extended Text
Message (ETM). The default 0 (no ETT) / 1 (ETT).

Access Controlled A 1-bit Boolean flag indicating that events associated with this virtual channel may
be access controlled. When set to ‘0’, event access is not restricted. The default
value is 0.

Hidden A 1-bit Boolean flag indicating that the virtual channel cannot be accessed directly
through the virtual channel number. Hidden virtual channels are skipped when the
user is channel surfing, and appear as if undefined, if accessed by direct channel
entry. Typical applications for hidden channels are test signals and NVOD services.
Select 0 or 1. The default value is 0.

Path Select A 1-bit field that associates the virtual channel with a transmission path. For the
cable transmission medium, path_select identifies which of two physical input
cables carries the Transport Stream associated with this virtual channel. Select 0 or
1. The default value is 0.

Out of Band A Boolean flag indicating that the virtual channel defined in this iteration of the
“for” loop is carried on the cable on the out-of-band physical transmission channel.
When clear, the virtual channel is carried within a tuned multiplex. Select 0 or 1.
The default value is 0.

Hide Guide A Boolean flag indicating that the virtual channel and its events may appear in EPG
displays. Typical applications for hidden channels with the hide_guide bit set to ‘1’
are test signals and services accessible through application-level pointers. Select 0
or 1. The default value is 0.

Service Type A 6-bit enumerated type field that identifies the type of service carried in this
virtual channel.
• 0x02—ATSC_digital_television - a groomed program contains a video
elementary stream. It MAY also have audio and/or data streams.
• 0x03—ATSC_audio_only - a groomed program contains no video but has one or
more audio streams. It MAY also have data streams.
• 0x04—ATSC_data_broadcast_service - a groomed program contains no video
and audio, but has one or more data streams.

CAP-1000 Software Guide v4.0 293

Chapter 15 Managing Tables and Output Programs Managing Path SDT

Table 15-5 Modify VCT Parameters (continued)

Source ID A 16-bit unsigned integer number that identifies the programming source
associated with the virtual channel. In this context, a source is one specific source
of video, text, data, or audio programming. The Source ID is set to the output
program number.

Descriptors Zero or more descriptors, as appropriate, may be included. TVCT and the CVCT
descriptors signal the combination of components (stream types, etc.) associated
with a particular virtual channel. Each instance of the descriptor identifies the set
of stream types that, if supported in a receiving device, allows that device to
properly render and present all programming on the channel.
Note: For TVCT, a Service Location Descriptor is automatically added (and cannot
be deleted). It appears in the Descriptors box after the VCT dialog is reopened.

6 Make any required changes and click OK.

7 Click Apply.

NOTE The CVCT values can be modified at any time, but the new values do not take effect until the next grooming
event.

Managing Path SDT

The CAP-1000 can now read incoming SDT in input multiplexes, append a user-specified ID for
the device, and output the modified SDT in non-DVB output multiplexes. Referred to as “Path
SDT” in the GUI, the CAP-1000 uses the SDT table for tracking the path of multicast-video in the
network.
The implementation uses the DVB standard Service Description Table (SDT). Each device on the
network is given a unique device ID. Each service has the device ID appended to its Path SDT
entry. For example, give a device ID of CAP1000.CMC1. Each service has the device ID
appended to its Path SDT entry. The CAP-1000 “reads” the incoming SDT in input multiplexes,
appends a user-specified device ID, and outputs the modified SDT in non-DVB output muxes.
If the input source does not have a Path SDT set, the device ID is out put as the Path for that
service: CAP1000.CMC1.
• If the input source already had a Path set, the device ID is appended (with a pipe “|” separator)
to the Path for that service: 10096.Apex Neews.SD.QSD6.CMC|CAP1000.CMC1.
• Additional devices will continue to append their device ID to the Path as the signal flows
through the network.
This feature is supported for all devices, including encoders, multiplexers, QAMs, etc.
The Path SDT Configuration dialog is used to indicate the SDT table for tracking the path of
multicast-videos in the network. The Path SDT is available on the System > Setup > Device tab.
To differentiate the Path SDT from regular DVB SDT, a special value, 0xFFFF is put in the
original_network_id field to indicate that the SDT table is a Path SDT table.

294 ARRIS Enterprises, Inc.

 Managing Path SDT

NOTE When the Path SDT feature is enabled, the Optional SDT feature is disabled. See section,“Configuring
Optional SDT, Service Names, and Service Provider Names,”on page 274 for more information.

Input Path SDT

When the Path SDT feature is enabled, the Path SDT tables are monitored for all input muxes. If
Path SDT tables are present, they are displayed under the Tables node in the input Tree of the GUI
with the label SDT (Path). When the Path SDT feature is not enabled, the Path SDT tables are not
monitored for the input muxes. Even if a Path SDT is present in the input mux, it won't be
displayed in the GUI.
When you enable the Path SDT feature, the CAP-1000 monitors the Path SDT for all input muxes.
When you disable this feature, the CAP-1000 stops monitoring the Path SDT for all input muxes.
The existing Path SDT tables are removed from the Tables node in the input Tree

Output Path SDT

When a groom is added that uses PID 17 for an output elementary stream, a configuration file is
loaded for an output mux with PID 17 as a PMT PID (in PMT command), or an elementary stream
PID (in groom commands) is added when Path SDT is enabled, the groom or the configuration
command is rejected. The CAP-1000 prevents the use of PID 17 as an output elementary stream
PID if the output PID is set to AUTO in the initial groom or more components are added to the
groom later due to input PMT updates.
For a program groom or custom groom, if the output program has a video stream, then the path in
the output SDT for this program follows the input path (in input Path SDT) for the input program
associated with the output video stream.
If the groom doesn't have video stream, the output program follows the input path for the input
program associated with the first component in the groom. If there is no Path SDT table in the
input mux belonging to the input program, or the Path SDT table doesn't have an entry for the
input mux, the output SDT is generated with the input program name followed by the delimiter
and device ID.

NOTE It is your responsibility to modify the input program names based on your standard naming convention and
to check “retain input program name” for the input program.

For a File groom, there is no input Path SDT. The path is generated in the output Path SDT. The
path includes the file name followed by the delimiter and device ID. The Path SDT feature is not
supported for Passed PIDs.
When you enable the Path SDT feature, the CAP-1000 follows the input Path SDT tables and
outputs the Path SDT tables. If you disable the feature, the CAP-1000 stops outputting the Path
SDT tables. There will not be any PAT or PMT update for the output muxes in these cases. When
the Path SDT feature is enabled, the input Path SDT cannot be passed to output Passed PIDs.
The default rate for the Output Path SDT tables is approximately 1800 milliseconds. It can be also
be configured via the configuration file.

CAP-1000 Software Guide v4.0 295

Chapter 15 Managing Tables and Output Programs Managing Path SDT

Exception Handling
The maximum length for a path (Service Name) is 252 characters in a service descriptor (in DVB
service descriptor the maximum descriptor_length is 255, minus 3 bytes for service_type,
service_provider_name_length and service_name_length respectively). If there is not enough
room for the CAP-1000 to append the delimiter and device ID in the path (the input path or the
input program/file name + the delimiter + device ID exceeds 252 characters), the delimiter is
appended to indicate there is a problem.
This delimiter is only appended f there is room for the delimiter character |. If some SDT tables,
other than the Path SDT, is injected into a non-DVB mux by another device, the CAP-1000 detects
the input mux as DVB type because it has SDT.

NOTE It is your responsibility to force the input mux to a non-DVB type if needed. In this case, the input mux
cannot carry the Path SDT.

Digital Program Insertion

Ad muxes cannot carry Path SDT. For the duration of the ads, the path in the output Path SDT
follows the network input. The CAP-1000 will not generate a new path in the output Path SDT:

Program Redundancy and Multiplex Redundancy

When an output program is switched to the backup input, the output Path SDT follows the backup
input for both Program Redundancy (PRED) and Multiplex Redundancy (MRED).

EAS/SCTE 18 Program Switching

When an output program is switched to an EAS details channel, the path in output Path SDT
follows the EAS details channel. If there is no Path SDT present in the input mux containing the
EAS details channel, the CAP-1000 generates a new Path SDT table.

CherryPicker Redundancy
The flag to enable or disable the Path SDT feature and the device ID are not virtualized on the
backup device because the device ID is device specific.

Output MUX Configuration File

In previous CAP-1000 releases, PID 17 is used in the default MPEG2 DCII and MusicChoice
output mux configuration files. The configuration files will be rejected if the Path SDT feature is
enabled. Anew default DCII and MusicChoice configuration files without PID 17,
MPEG2_GI_PathSDT_ConfigFile.txt, is provided:

296 ARRIS Enterprises, Inc.

 Managing Path SDT

Enabling Path STD

To enable Path STD:

1 From the CherryPicker Element Manager, click Setup > System > Device.

Path SDT

2 Click the Path SDT link.

Path SDT Configuration

3 Click the Enable Path SDT for Non-DVB output multiplexes.

4 Enter the Device ID.
When the feature is enabled and the value of 0xFFFF is encountered in the original_network_id
field in the SDT tables, the CAP-1000 automatically displays the path (if available) for all input
programs (not the output programs).
5 Click Apply.

CAP-1000 Software Guide v4.0 297

Chapter 15 Managing Tables and Output Programs Creating Custom NIT

Disabling Path STD

To disable Path STD:

1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Click the Path SDT link.
3 Clear the Enable PATH SDT for Non-DVB output multiplexes option.
4 Click Apply.

Creating Custom NIT

This section explains how to create a custom Network Information Table (NIT) for use with the
CAP-1000 running in a Digital Video Broadcast (DVB) environment. The Network Information
Table describes all physical parameters of a DVB transmission channel, including the transmission
path (terrestrial, cable, or satellite), received frequency, type of modulation, error protection, and
transmission parameters.
The NIT is required for digital video broadcasting with DVB Simulcrypt. To create a custom NIT,
you input information relating to the physical organization of the multiplexes and Transport
Streams carried on a given network. It is assumed that you have access to the NIT data required to
configure the table.

NOTE This section does not explain the network descriptors, Transport Stream descriptors, semantics, or syntax
needed to configure the NIT. For complete information, refer to the document, ETSI EN 300 468 V1.5.1
(2003-05) Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB Systems.

NOTE This feature is only supported on multiplexes configured with a DVB configuration file.

To create a NIT:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the DVB GigE or ASI Output Multiplex you want.
3 Click NIT from the pop-up Context menu.

298 ARRIS Enterprises, Inc.

 Creating Custom NIT

Gigabit Ethernet Output Multiplex

The Network Information Table window opens.

CAP-1000 Software Guide v4.0 299

Chapter 15 Managing Tables and Output Programs Creating Custom NIT

Network Information Table

The CAP-1000 will generate an NIT based on the descriptors you enter and automatically add the
derived NIT data into the DVB configuration file. The following table describes the different
descriptors that can be used within the Service Information (SI).

Table 15-6 Network and Transport Stream Descriptors

Descriptor Description

Network Descriptors

Network Name Descriptor Provides the network name in text form.

Multilingual Network Name Descriptor Provides the network name in text form in one or more languages.

Linkage Descriptor Identifies a service that can be presented if the consumer requests for
additional information related to a specific entity described by the SI
system. The location of the linkage descriptor in the syntax indicates the
entity for which additional information is available. For example, a
linkage descriptor located within the NIT shall point to a service
providing additional information on the network.

Stuffing Descriptor Provides a means of invalidating previously coded descriptors or

inserting dummy descriptors for table stuffing.

300 ARRIS Enterprises, Inc.

 Generating TOT

Table 15-6 Network and Transport Stream Descriptors (continued)

Descriptor Description

Private Descriptor Provides a private descriptor tag and description.

Transport Stream ID

Service List Descriptor Provides a means of listing the services by service_id and service type
within a TS.

Satellite Delivery System Descriptor Provides satellite delivery system information, such as frequency, orbital
position, and polarization.

Cable Delivery System Descriptor Provides cable delivery system information, such as frequency and
modulation.

Terrestrial Delivery System Descriptor Provides cable delivery system information, such frequency and
bandwidth.

Stuffing Descriptor Provides a means of invalidating previously coded descriptors or

inserting dummy descriptors for table stuffing.

Frequency List Descriptor Gives the complete list of additional frequencies for a certain multiplex
which is transmitted on multiple frequencies.

Private Descriptor Provides a private descriptor tag and description.

Logical Channel Number Descriptors Provides the logical channel number for a service. This number could be
used by TV Headend to populate the Channel Number based on this
number.

4 Configure the parameters as needed.

5 Repeat steps, as necessary, to configure additional Transport Stream IDs.
Information in this table is presented in a tree format with buttons for expanding or collapsing the
individual panels.
6 When you are finished, click OK.
The NIT table is automatically created and applied to the DVB configuration file.

Generating TOT
The Time Offset Table (TOT) carries the UTC time, date, and the local time offset. The TOT is
transmitted in TS packets with a PID value of 0x0014. This is an optional table as per DVB
specifications.
The CAP-1000 can generate the TOT on an output DVB multiplex using a Configuration file. The
repetition rate for TOT follows that of the Time and Date Table (TDT) currently implemented by
the software. The repetition rate is in the range of 16 milliseconds and 30 seconds. The default
repetition rate of TOT is 28 seconds.

CAP-1000 Software Guide v4.0 301

Chapter 15 Managing Tables and Output Programs Generating TOT

NOTE This feature is only supported on multiplexes configured with a DVB configuration file.

To generate a TOT:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the DVB GigE or ASI Output Multiplex you want.
3 Click TOT from the pop-up Context menu.

Gigabit Ethernet Output Multiplex

The Time Offset Table window opens.

Time Offset Table

302 ARRIS Enterprises, Inc.

 Managing Output Programs

4 Configure the parameters as needed.

5 Click OK.

Managing Output Programs

Programs are container formats for multiplexing audio, video, and data elementary streams.
Programs are created by combining one or more Packetized Elementary Streams (PES), which
have a common time base, into a single stream.
For viewers and listeners of electronic media, a program or program service is something that one
watches, with a start time, an end time, a duration and maybe even a title or selections within the
program. A digital program on the other hand, is a linear service that provides, for a certain length
of time, one or more audio-visual events.
An MPEG-2 Program Stream, by definition, carries one program. An MPEG-2 Transport Stream
can carry one (a Single Program Transport Stream) or more (a Multiple Program Transport
Stream) independent or associated programs.
You can view, rename, and configure recoders for output programs. Refer to section,“Reserving
Recoders,”on page 457 for information on recoders.

Viewing Output Programs

To view a program:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the GigE or ASI Output Multiplex you want.
3 In the GigE or ASI Output Muxes panel, click the Programs tab at the bottom of the window and
select the program you want.
.

Output Program

CAP-1000 Software Guide v4.0 303

Chapter 15 Managing Tables and Output Programs Managing Output Programs

Information about a specific program displays in this panel.

Table 15-7 Output Program Parameters

Program Number Shows the ID assigned to the program.

Name Shows the default name assigned to the program in the format
< line-name >_<program ID>, for example, “1/4_14”.
Note: You can change the name using the Program tab or the Edit Name
command in the Context menu.

PMT PID Shows the Program Map Tables (PMT) ID number.

PCR PID Shows the Program Clock Reference for the Packet Identifier. The PCR parameter
sets the PCR PID and interval.

Recoder Assigns a recoder to the selected program. The options are: None, MPEG-2 SD,
MPEG-2 HD, and MPEG-4/AVC HD.

EBIF Enabled Enables EBIF at the output program level when the required license key is
installed. See Chapter 26, “Managing EBIF” for more information.

Closed Captioning Conversion Enables the CAP-1000 to carry closed captioning (CC) information in SD or HD
MPEG-2 user video streams for DTV. See section,“Managing Closed
Captioning Conversion,”on page 306 for more information.
CALM Enables volume leveling via the Commercial Advertisement Loudness Mitigation
(CALM) Act FCC regulation by modifying the dialnorm parameters of groomed AC-3
audio streams. See section,“Enabling CALM,”on page 402 for more
information.
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file grooms
with live audio.

EAS Alert Priority Sets the priority for this mux to process emergency alerts. The valid value are:
Alert Disabled, High (11), Default, Test Message (0) Low (3), Medium (7), High (11)
and Maximum (15).
Note: If an EAS alert is received and Digital Program Insertion (DPI) is configured
to splice an ad, DPI is interrupted, the splice is prevented, and the alert is allowed
to play out. If an EAS alert is received while DPI is active, DPI is interrupted, the
splice fails, and the alert is allowed to play out.

CVCT Major Shows the major_channel_number (if not using a one-part channel number) when
a program is created. You can modify the major_channel_number when a program
is groomed into an already existing output program placeholder. The valid major
numbers are from 0 to 999.

CVCT Minor Shows the minor_channel_number (if not using a one-part channel number) when
a program is created. You can modify the minor_channel_number when a program
is groomed into an already existing output program placeholder. Otherwise, the
existing minor number will be preserved. The valid minor numbers are from 0 to
999.

304 ARRIS Enterprises, Inc.

 Managing Output Programs

Table 15-7 Output Program Parameters (continued)

TVCT Major Shows the major_channel_number when a program is created. You can modify the
major_channel_number when a program is groomed into an already existing
output program placeholder. The valid major numbers are from 1 to 99.

TVCT Minor Shows the minor_channel_number when a program is created. You can modify the
minor_channel_number when a program is groomed into an already existing
output program placeholder. Otherwise, the existing minor number will be
preserved. The valid minor numbers are from 0 to 999.

Renaming Output Programs

Two options are available to rename programs.

Using the Program Tab

To rename a program:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the GigE or ASI Output Multiplex you want.
3 In the GigE or ASI Output Muxes panel, click the Programs tab at the bottom of the window and
select the program you want.
4 Under Name, edit the name you want.
.

Program Name

5 Click Apply.

CAP-1000 Software Guide v4.0 305

Chapter 15 Managing Tables and Output Programs Managing Closed Captioning Conversion

Using the Context Menu

To rename a program:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the output program you want.
3 Right-click the program, select Edit Name, and enter a new name.
4 Release the mouse button.

Managing Closed Captioning Conversion

You can enable the CAP-1000 to translate Closed Captioning Conversion (CCC) information in
SD or HD MPEG-2 user video streams for DTV. You can apply CCC to an output mux or output
program. If you choose to do so, the CAP-1000 translates the CCC video user data as follows:
• If no CCC data is carried, the video user data is not changed.
• If the video has SCTE 20, then CAP-1000 translates SCTE 20 into SCTE 21 and sends both to
the output.
• If the video has SCTE 21, then CAP-1000 translates SCTE 21 into SCTE 20 and sends both to
the output.
If you choose not to enable this feature, the CAP-1000 does not translate the CCC video user data
and it is passed as is.

IMPORTANT The CAP-1000 supports the Twenty-First Century Communications and Video Accessibility Act. (Public
Law 111-260). Use of this feature is depended on the capabilities of the upstream encoder.

To enable CCC at the output mux level while grooming, see Chapter 18, “Grooming Programs,”
and Chapter 19, “Grooming Elementary Streams,” for more information.

To manage CCC on output programs:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree and select the GigE or ASI Output Multiplex you want.
3 In the GigE or ASI Output Muxes panel, click the Programs tab at the bottom of the window and
select the program(s) you want.
4 Under Closed Captioning Conversion, do one of the following:
• To pass CCC data, select the Enable option.
• To prevent CCC data from being passed, clear the option.

306 ARRIS Enterprises, Inc.

 Managing Closed Captioning Conversion

Closed Captioning Conversion—Output Program

5 Click Apply.
6 Click Yes.

CAP-1000 Software Guide v4.0 307

Chapter 15 Managing Tables and Output Programs Managing Closed Captioning Conversion

308 ARRIS Enterprises, Inc.

 CHAPTER 16
Managing Configuration Files

In This Chapter
• Configuration Files
• Example XML Configuration Files
• Config Files Window
• Managing XML Configuration Files
• Backing Up and Restoring the Database

Configuration Files
All CAP-1000 systems require the use of one or more configuration files for correct operation in
different environments. Configuration files establish the initial configuration of the system. They
also enable the configuration of device-level, line-level, and multiplex-level components, such as
DVB, ATSC, MPEG-2, or MPEG-4 output multiplexes. Software v4.0 now supports configuration
files in XML format.

NOTE To maintain backward compatibility importing of text-based configuration files is also supported; however,
new configuration file commands added to the software post v4.0 can only be applied via an XML
Configuration file. A text-based equivalent of the command will not exist and will only be available in the
XML format.

You can view, edit, load, import, export, and remove configuration files using the Files window in
the CherryPicker Element Manager. The configuration files that are currently in use are stored in
the /usr/cp/Config directory of the CAP-1000.

Example XML Configuration Files

Example XML configuration files are provided with the CAP-1000 software. You can customize
them for use with your operations center. These files are stored on the Program Flash in the
/usr/cp/ConfigExamples directory and can be accessed through the Files window.

CAP-1000 Software Guide v4.0 309

Chapter 16 Managing Configuration Files Configuration Files

The following table describes a subset of these files.

Table 16-1 XML Configuration Files

File Name Description

ATSC_ConfigFile Configuration compliant with the ATSC Advanced Television Standard.

DVBSI_16SD_ConfigFile Supports DVB SI tables, derived from the legacy DVBSI_ConfigFile.txt. Contains
16 programs with MPEG-2 SD recoding resources.

MPEG2_16SD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy MPEG2_ConfigFile.txt. Contains 16 programs with
MPEG-2 SD recoding resources.

MPEG2_3HD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy “MPEG2_ConfigFile.” Contains three programs with
MPEG2-HD recoding resources.

MPEG2_4HD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy MPEG2_ConfigFile.txt. Contains four programs with
MPEG-2 HD recoding resources.

MPEG2_64SD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy MPEG2_ConfigFile.txt. Contains 64 programs with
MPEG-2 SD recoding resources.

MPEG2_GI_ConfigFile Configuration for Motorola head-ends, derived from the legacy MPEG2_GI
ConfigFile.txt. Contains 16 programs with MPEG-2 SD recoding resources.

MPEG2_MusicChoice_ConfigFile Modification of the MPEG2_ConfigFile.txt file above to support Music Choice still
video streams.

MPEG4_16HD_ConfigFile Basic MPEG-4/AVC configuration, as defined in the 14496-rev10 series of

standards, derived from the legacy MPEG2_ConfigFile.txt. Contains 16 programs
with MPEG-4/AVC-HD recoding resources.

MPEG4_8HD_ConfigFile Basic MPEG-4/AVC configuration, as defined in the 14496-rev10 series of

standards, derived from the legacy MPEG2_ConfigFile.txt. Contains eight
programs with MPEG-4/AVC-HD recoding resources.

SPTS_MPEG2_HD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy MPEG2_ConfigFile.txt. Contains one program with
MPEG-2 HD recoding resource.

SPTS_MPEG2_SD_ConfigFile Basic MPEG configuration, as defined in the ISO/IES 13181 series of standards,
derived from the legacy MPEG2_ConfigFile.txt. Contains one program with
MPEG-2 SD recoding resource.

SPTS_MPEG4_HD_ConfigFile Basic MPEG-4/AVC configuration, as defined in the 14496-rev10 series of

standards, derived from the legacy MPEG2_ConfigFile.txt. Contains one program
with MPEG-4/AVC-HD recoding resources.

310 Motorola, Inc.

 Configuration Files

Input XML Configuration Files

In software release 4.0, the input configuration file is in XML format. In the XML configuration
file, the input information is separate from the output multiplex configuration files. This allows
you to create one input configuration file for a CAP-1000 and export it to other devices. Thus, you
can create and configure several input GigE multiplexes at once.
The following functions apply:
• The GUI provides an option to export and import a configuration file at the input line level and
the input mux level. The default file name is inputLine_<lineID>_Config.xml or
inputmux_<muxID>_Config.xml.
• During export, an XML configuration file is created. It contains the information for the target
object (line or multiplexes), all of its children (multiplexes or programs), and grandchildren
(programs or elementary streams), if they exist.
• The XML export/import function is not supported for ad insertion multiplexes, ports restricted
to management traffic (MPEG not enabled), or the management ports.
• The information for the input ASI/GigE line is: ID, Name.
• The information for the input ASI multiplex is: Id, Name, Mux Type and Retain-
Program-Name.
• The information for the input GigE multiplex is: ID, Name, Mux type, Retain-
Program-Name, Multicast IP Address, UDP Port and Source IP Address
Filtering.
• The information for the input program name is: ID, Name, PMT PID and PCR PID. PMT
PID and PCR PID are applicable only for user-added program.
• The information for the input elementary stream is: Elementary PID, Stream Type and
Descriptor. This information is applicable only to user-added programs, but it is not
mandatory to specify streams for the extra input program.
When you import a configuration file at the line level, the following changes are made:
• The name of line is updated.
• For the input ASI line, the mux information is updated. Hereafter, the ID is never updated.
• For the input GigE line, if a multiplex does exist (matching multicast IP, UDP Port, and Source
IP), the multiplex information is updated. Otherwise, a new multiplex is created.
• A user-added program is created with specified elementary stream(s).
• The name of programs in the Transport Stream is updated if its ID matches the program ID in
the input XML configuration file.
When you import a configuration file at the multiplex level, the following changes are made:
• All information for the multiplex is updated.
• A user-added program is created with its specified elementary stream(s).

CAP-1000 Software Guide v4.0 311

Chapter 16 Managing Configuration Files Configuration Files

• The name of the programs in the Transport Stream is updated if its ID matches the program ID
in the input XML configuration file.

IMPORTANT When you load an input line XML configuration file, the CAP-1000 appends the new configuration to the
existing configuration file.

Output XML Configuration Files

You can create multiple GigE output multiplexes by loading an output line configuration file onto
a CAP-1000 device. This allows you to create an output configuration file on one CAP-1000 and
export it to other devices. Thus, you can create and configure several output GigE multiplexes at
once.
The following functions apply:
• The GUI provides an option to export and import a configuration file at the output line level
and the output mux level. The default file name is outLine_<lineID>_Config.xml or
outputmux_<muxID>_Config.xml.
• During an export at the output line level or the multiplex level, an XML configuration is
created. It contains the information for the target object (output line or multiplex), all of its
children (multiplexes or programs), grandchildren (programs or elementary streams or
placeholders), and grooming actions, if any exists.
• The XML export/import function is not supported for ad insertion multiplexes, ports restricted
to management traffic (MPEG not enabled), or the management ports.
• The information for GigE output line is: ID, Name, MPEG Output, MonitorLink,
CombinePeerPort, MPEGSourceIP_Origin, MPEGSourceIP, and NumMPEGinUDP.
• The information for ASI output line is: ID, Name, MPEG OutputMode,
TotalReservedRate, TotalLineRate, TotalAvailableRate, InterByteGap,
and Bytes per Packet.
• With output lines, multiplexes, SMPs, groom actions, and groom definitions are exported, if
they exist.

IMPORTANT When you load an output line XML file, the CAP-1000 deletes the entire existing configuration under the
line (multiplexes, groom actions) and adds the configuration in the configuration file.

Device-level XML Configuration Files

Software version 4.0 now supports XML file functions at the device level (CAP-1000) and
provides backup and restore options.
The backup option lets you:
• Download the compressed backup file to a local machine.
• Export all input and output lines.

312 Motorola, Inc.

 Configuration Files

The restore option lets you:

• Upload the compressed file from a local machine.
• Transfer the file to the CAP-1000.
• Load the configurations present as part of the compressed file.

XML Validation
If an XML file contains syntax errors, the CAP-1000 rejects the complete file. Prior to applying a
configuration file, the CAP-1000 performs a three-phase validation check of the configuration file:
1 Syntax validation which involves schema validation only.
2 Semantic validation which involves validation of range only.
3 Minimal functional validation which involves validation for the existence of inputs only.

Backwards Compatibility
In software release 4.0, the configuration file is in XML format. To maintain backward
compatibility, you can import old configuration files (text files). All existing configuration file
commands can use files in .txt and .xml format.
The following functions apply:
• Use of the ConfigFile -s command supports only string based commands. It does not support
XML commands.
• The CAP-100 can read and import old text configuration files that were exported by output
multiplexes in previous software releases.
• All the configuration files under the ConfigExamples directory are converted to XML and
made available as part of the build.
• When the CAP-1000 is upgraded, all output line information is converted to XML using the
outputLine_<lineID>_Config.xml naming convention. This file contains the
information for the target object (output line), all of its children (muxes or programs),
grandchildren (elementary streams or placeholders), and groom actions if exist.
• When the CAP-1000 is downgraded, exported XML files are retained.

Related Documentation
If you use text-based configuration files, refer to the CAP-1000 Configuration Command
Reference Guide for additional information on configuration commands, syntax, parameters, and
examples for the ConfigFile.txt files.
If you use XML-based configuration files, refer to the CAP-1000 XML Protocol Reference Guide
for a description of the XML schema and categories used in files.

CAP-1000 Software Guide v4.0 313

Chapter 16 Managing Configuration Files Config Files Window

Config Files Window

Configuration files establish the configuration of the CAP-1000 lines (ports) and multiplexes.
Clicking Setup > Files displays the Files window which lets you perform the following tasks:
• View and update device-level, line-level, and multiplex-level XML configuration files
• View sample XML configuration files
• Import and export XML configuration files for device, line, and multiplex
• Back up and restore XML configuration files for device to or from a local PC
• Extract slate files from Single Program Transport Streams
• Upload slate files (M2V)

Files

For information on slate files, refer to section,“Managing Slate Files,”on page 600.

Files Header
The Files header lets you select the Files view or the Slate Files view. The following table
describes the icons in the toolbar.

Table 16-2 Files Header

Shows the XML Config Files view for managing configuration files.

Shows the Slate Files view and lets you upload custom files for grooming. See Chapter 30,
“Configuring Slate Redundancy” for information.

314 Motorola, Inc.

 Config Files Window

Config Files Toolbar

The Files toolbar provides editing tools for managing configuration files. The following table
describes the icons in the toolbar.

Table 16-3 Config Files Toolbar

Displays the Configuration tree in the left panel.

Imports an XML configuration file.

Exports an XML configuration file.

Backs up the CAP-1000 device configuration file to a local PC.

Restores the C AP-1000 device configuration file from a local PC. The current file is overwritten.

Opens the Load Configuration File window enabling you to select a file to load.

Opens the example configuration files that you can edit for your own use.

Closes the configuration file.

Saves the configuration file.

Saves the configuration file to the Data Flash.

Deletes the configuration file.

Validates the XML in the configuration file as follows:

• Syntax validation which involves schema validation only.
• Semantic validation which involves validation of range only.
• Functional validation for existence of inputs when file is loaded.

CAP-1000 Software Guide v4.0 315

Chapter 16 Managing Configuration Files Managing XML Configuration Files

Managing XML Configuration Files

This section explains how to import, export, modify, back up, restore, and delete configuration
files.

NOTE You can read configuration files using Excel 2007 and Excel 2003 Professional Version. Editing XML files
might cause Excel parser errors. It is recommended that attribute names not be expended to two lines. When
exporting XML files, each file contains a warning describing this restriction.

Importing XML Configuration Files

A configuration file is used to customize the CAP-1000 for DVB, ATSC, MPEG-2, or MPEG-4
output multiplexes. Each output multiplex has a configuration file associated with it. When
creating an output multiplex, you can import and apply a configuration file to the multiplex, or you
can export a configuration file already associated with the multiplex.

NOTE Scheduled events are not supported in the configuration file.

To import a configuration file:

1 From the CherryPicker Element Manager, click Setup > Files.
2 Click XML Config Files.
3 Click Show Tree.
4 Select the component you want.
5 Click Import XML File.
A Warning window opens.
6 Click OK.

Open Configuration File

316 Motorola, Inc.

 Managing XML Configuration Files

NOTE Only configuration files in the /usr/cp/Config directory are displayed.

7 Do the following:
a Select MPEG-2, MPEG-3, ATSC, DVB, or Other.
b Select the configuration file you want to import.
c Click OK.
Depending on the changes you make, a warning window opens.
8 Click Yes to apply the changes.

Exporting XML Configuration Files

To export a configuration file:

1 From the CherryPicker Element Manager, click Setup > Files.
2 Click XML Config Files.
3 Click Show Tree.
4 Select the component you want.
5 Click Export XML File.

Enter File Name

6 Click OK.
Depending on the changes you make, a warning window opens.
7 Click Yes to apply the changes.

Modifying XML Configuration Files

The Config File window provides a set of toolbar buttons located on the left upper corner of the
panel. They provide Open, Open Example, Save, Save As, Refresh, Restore, and Close operations.
When a configuration file is opened, the upper right corner displays file name and file type.
The general guidelines for modifying the configuration file are as follows:
• Do not put spaces or blank lines above a command line.
• Do not put carriage returns in the middle of a line.
• All numbers are in decimal.

CAP-1000 Software Guide v4.0 317

Chapter 16 Managing Configuration Files Managing XML Configuration Files

• All tables are decimal.

• All flags are case sensitive.
• Comment lines begin with a pound sign (#).

To modify a configuration file:

1 From the CherryPicker Element Manager, click Setup > Files.
2 Click XML Config Files.
3 Click Show Tree.
4 Select the component you want.
5 To open a file, do the following:
a Click Open File.
b Select MPEG-2, MPEG-3, ATSC, DVB, or Other.

Open Configuration File

NOTE Only configuration files in the /usr/cp/Config directory are displayed.

c Select the configuration file you want and click OK.

6 To open an example file, do the following:
a Click Open File Example.
b Select a file.

318 Motorola, Inc.

 Managing XML Configuration Files

Open Example Configuration File

c Click OK.
The file appears in the Files window.
7 Edit the line that controls the parameter that you want to change.
8 To validate the file, do the following:
a Click Validate XML.
b Correct any errors, if found.
c Click OK.
d Validate the file again.
9 To save the file, click Save.
10 To save the file using a different name, do the following:
a Click Save as.
b Enter a new name for the .txt file.
c Click OK.
The file is saved to the Data Flash directory: /usr/cp/Config.
11 To apply the changes to the multiplex, click Apply.
12 To close the file, click Close.

CAP-1000 Software Guide v4.0 319

Chapter 16 Managing Configuration Files Backing Up and Restoring the Database

Deleting XML Configuration Files

To delete:
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click Delete Configuration Files.
3 Select the file you want.
4 Click OK.
An Information window opens.
5 Click OK.

Backing Up and Restoring the Database

You can backup or restore the device configuration in the Files tab.

Backing Up the Database

To back up:
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click XML Config Files.
3 Click Show Tree.
4 Select the CAP-1000 device (root node).
5 Click Backup Device.
The Select Folder to Save window opens.

Select Folder to Save

6 Use the icons in the window to navigate to a directory in which to save the file.
7 Click Save.
An Information window opens.

320 Motorola, Inc.

 Backing Up and Restoring the Database

Information

8 Click OK.

Restoring the Database

To restore:
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click XML Config Files.
3 Click Show Tree.
4 Select the CAP-1000 device (root node).
5 Click Restore Device.
A warning window opens.
6 Click OK.
The Open window opens.

Open

7 Use the icons in the window to navigate to a directory where the zip file is saved.
8 Click OK.
A message, “Restoring Configuration” displays. When the operation completes, an Information
window opens.
9 Click OK.

CAP-1000 Software Guide v4.0 321

Chapter 16 Managing Configuration Files Backing Up and Restoring the Database

322 Motorola, Inc.

 CHAPTER 17
Grooming Concepts

In This Chapter
• Grooming
• Grooming Types
• Grooming Sources
• Grooming Definitions and Levels
• Grooming Capabilities and Maximum Usage

Grooming
Grooming is the process of taking program content in digital form, whether from satellite or
terrestrial broadcast, and adding or dropping programs to best adapt them to meet available
bandwidth and the viewing preferences of the local subscriber base.
Signals are received from the video sources, decrypted and passed to groomers as an SPTS or an
MPTS. Grooming allows you to “cherry pick” channels from a range of content sources in the
MPTS and to distribute only those that are desired for a particular channel lineup.
A key element in this efficient transmission is the recoding of video streams to satisfy the output
bit rate constraints. In the process of grooming, the content of a groomed elementary stream does
not change, unless the stream is recoded.
Grooming enables you to choose which programs from incoming streams to preserve, discard
unwanted programs, and switch programming lineups dynamically. Operator-provided content
from local sources can also be seamlessly integrated into the digital services offering.
Grooming provides an effective means of delivering MPEG-2, MPEG-4 SD, and HD video with
great efficiency and operator control. It is based on statistically multiplexing variable bit rate
programs within each 6 MHz channel, performing rate shaping to dynamically reduce bit rates of
individual programs when necessary to fit capacity, and periodically re-setting channel line-ups for
optimal grooming performance.
Grooming is performed in the Grooming tab of the CherryPicker Element Manager.

CAP-1000 Software Guide v4.0 323

Chapter 17 Grooming Concepts Grooming

CherryPicker Element Manager—Grooming

Grooming Definitions
A grooming definition refers to the switching of a particular input element (DVB-ASI, GigE port
from an IOA or a video file) to an output (DVB-ASI or GigE port from IOA). A grooming
definition is characterized, as a minimum, by the following attributes:
<grooming definition> = <source> <destination> <start time> <end time>
where:
• <source> can be an input program or an input elementary stream, depending on the type of
grooming.
• <destination> can be an output multiplex or an output program, depending on the type of
grooming.
• <start time> and <end time> are the beginning and the end of the grooming definition.
A grooming definition can also include other attributes, such as an indication if a stream can be
recoded.

324 ARRIS Enterprises, Inc.

 Grooming Types

Supported Streams
With the CAP-1000, you can groom the following types of streams (or programs carrying these
streams) from a DVB or GigE input and groom it to output. Both encrypted and clear streams are
supported.
• Advanced Audio Coding (AAC)
• Dolby Digital (AC-3)
• Dolby Digital Plus (Enhanced AC-3)
• Enhanced TV (ETV) streams
• MPEG-4/AVC video (SD or HD)
• MPEG-2 video (SD or HD)
• High-Efficiency Advanced Audio Coding (HE-AAC) version 1 and version 2
• Private data streams

Grooming License
No licenses are needed to define a groom or to create an output program on the current software
release. Passing of any tables or streams is always available. EBIF/ETV; however, do require
licenses.

Grooming Types
The CAP-1000 supports static and dynamic grooms of programs, elementary streams, and files.

Static Grooming
Static grooming is the ability to groom programs, elementary streams, and files that are not
constrained with start time/date and end time/dates. When a program is configured for a static
groom, the CAP-1000 immediately generates the program interval based on conditions defined in
the CherryPicker Element Manager. Thus, a static groom is immediate and plays out forever,
unless it is dropped or replaced by another groom.

Dynamic Grooming
Dynamic grooming is the ability to groom programs, elementary streams, and files with start
time/date and end time/date constraints. It is the process of selecting digital streams from pre-
multiplexed input transport streams for distribution by time slots (as opposed to distributing
streams constantly, without changes over time). Thus, when dynamic grooming is performed, the
transport stream programs change over time based on a specified schedule.
The CAP-1000 also provides support for time-based events generated as a single or reoccurring
event. You create scheduled events in the Triggers tab of the CherryPicker Element Manager.

CAP-1000 Software Guide v4.0 325

Chapter 17 Grooming Concepts Grooming Sources

Triggers
Refer to Chapter 21, “Using Trigger Events,”for more information.

Passed PIDs
Passed packet identifiers (PIDs) represent a special case of grooming. Passed PIDs are static; you
cannot apply start date/time or end date/time constraints. In this type of grooming, the input
transport packets are simply passed to the output. The passed input streams are not changed,
except for the possible change in the PID. Passed streams are given the highest priority (the
minimum delay) in processing. Refer to Chapter 23, “Passing PIDs” for more information.

NOTE PID sharing is not supported.

Grooming Sources
The CAP-1000 enables you to groom using the following sources:
• Programs
• Elementary Streams
• Standard Files
• Custom Files
• Slate Files

326 ARRIS Enterprises, Inc.

 Grooming Sources

Programs
A program is a container format for multiplexing digital audio, video and more. The PS format is
specified in MPEG-1 Part 1 (ISO/IEC 11172-1) and MPEG-2 Part 1, Systems (ISO/IEC standard
13818-1[6]/ITU-T H.222.0[4][5]). Programs are created by combining one or more Packetized
Elementary Streams (PES), which have a common time base, into a single stream.
In program grooming, all elementary streams identified in the PMT for the groomed input program
are routed to the specified output multiplex. The specification of the output program is optional. If
the output program is not given, the CAP-1000 automatically creates an output program (PMT and
a change in PAT).
With program grooming, a specified program can be un-groomed (dropped) from an output. In this
case, the elementary streams associated with this program is not transmitted to the output. The
PMT and the PIDs associated with the un-groomed program, however, are preserved as a
placeholder for a potential future grooming event with the same PMT/PIDs. In addition, a
specified program can also be deleted from an output. The associated PMT is deleted in this case
as well. See Chapter 18, “Grooming Programs” for more information.

Elementary Streams
The CAP-1000 supports grooming by elementary stream (also known as custom grooming). You
can select a particular video, audio, or private data elementary stream from an input and groom it
to an output program or an output. The same input elementary stream can be included in multiple
output programs. The same elementary streams can be groomed up to 30 different output programs
in different output multiplexes.
You can also add input elementary stream “placeholders” to a groom in anticipation that the
elementary stream will appear in the future. You need only supply the PID for the unknown stream
that is to follow in the grooming operation. See Chapter 19, “Grooming Elementary Streams” for
more information.

Audio Streams for the Visually Impaired

One popular use of custom grooming is to select a secondary audio stream to be distributed as the
first audio stream. Subscribers are then able to watch shows in their primary language without
needing SAP-enabled televisions.
Software release 4.0 adds support for audio streams for the visually impaired. An AD stream is an
audio stream that contains verbal narrative descriptions of what is occurring in the program, mixed
with the normal audio sound track in the intervals between stretches of dialog.

Encrypted Streams
The CAP-1000 supports the grooming or passing of encrypted streams. You can easily pass an
encrypted program or an elementary stream using drag-and-drop in the Groom window. The
CAP-1000 automatically selects the Pass Streams mode when at least one of the input streams is
encrypted. The encryption status of all streams is refreshed every ten minutes in the Component
Tree of the Content Picking > Grooming window. See section,“Grooming Encrypted
Streams,”on page 372 for more information.

CAP-1000 Software Guide v4.0 327

Chapter 17 Grooming Concepts Grooming Definitions and Levels

Standard Files
The CAP-1000 provides a set of standard files on the RAM disk for you to groom to an output
program on a DVB-ASI or a GigE multiplex. These file include PAL and NTSC MPEG-2, and
MPEG-4/AVC. See Chapter 20, “Grooming Files” for more information.

Custom Files
The CAP-1000 supports the grooming of custom video and audio files. You upload these files to
the Data Flash for use in grooming operations. See Chapter 20, “Grooming Files” for more
information.

Slate Files
You can groom slate files to output in the event that both primary and backup (PRED) sources are
unavailable. For output programs or muxes that have a slate input source defined, the grooms can
be forced to switch from the primary to the slate source, even though the primary source may not
have failed. Forcing the groom can be done at the device level, the mux level, or individual output
program level. When the forced to slate option is requested, the state is remembered for future
grooms. For those output programs that have no slate input source specified, the request is ignored.
The slate files are referred to as custom slate programs. They can be a video file, a video file and
audio file(s), or a video file and audio live stream(s). These files are stored on the Data Flash. See
Chapter 30, “Configuring Slate Redundancy” for information.

Grooming Definitions and Levels

When you create a groom in the Grooming tab of the CherryPicker Element Manager, information
about the groom is depicted in the Grooming Definition panel.
The Grooming Definitions panel shows the Grooming ID, Type, Description, and Level. A static
groom, which plays out “Now” until “Forever (or until it is replaced by another static groom) is
assigned to Level 0.

328 ARRIS Enterprises, Inc.

 Grooming Definitions and Levels

Static Groom

A dynamic groom, which has a start and end date/time, is assigned to Level 1 or higher.

Dynamic Groom

CAP-1000 Software Guide v4.0 329

Chapter 17 Grooming Concepts Grooming Definitions and Levels

Programs with the highest level are played out first. You add additional “Levels” using the Select
Grooming Definition window which appears when you drag-and-drop multiple programs on a new
or existing program.

Select Grooming Definition

When configuring dynamic grooms, you can assign a start date/time and an end date/time. You can
add multiple grooming definitions with overlapping program intervals or action definitions that
use different levels. See Chapter 18, “Grooming Programs” for more information.

Level-based Program Switching

The CAP-1000 supports priority or level-based program switching. You can define multiple levels
of grooming activity on an output program. The highest level has the highest priority and will be
the first program output. This feature can be used for regionalization/localization of content and
Emergency Alert System (EAS) switching.

330 ARRIS Enterprises, Inc.

 Grooming Capabilities and Maximum Usage

#2 g e d ,

#2 g e d ,
#1 g e d r,

#1 g e d r,
rri e om

rri er om
n re e

n e e
rri e rev

rri er rev
cu igg ro

cu igg ro
nt

nt
n re
re tr p g

re tr p g

n e
nt

nt
ve

ve
cu igg fo

cu igg fo

ve
ve
re tr m

re tr m
ro

ro
o

o
D

D
ro

ro
G

G
m tio ith
na ra w

t
ic n,
en
dy du oom

ev
r
G Local Local
Level 5

Level 1 Regional

Level 0 National

Output National Regional Local Regional Local National

Level-based Program Switching

The switch will groom the primary input of the new groom, unless the device is forced to backup,
or the primary input program is missing. If Digital Program Insertion (DPI) is active, the ads play
out completely and then the program is switched back to the network.
See Chapter 18, “Grooming Programs” for more information.

Grooming Capabilities and Maximum Usage

This section summarizes the grooming capabilities of the CAP-1000. The following topics are
covered:
• Maximum Number of Elementary Streams per Groomed Program
• Maximum Number of Groomed Programs per Multiplex
• Maximum Number of Groomed Programs per Device
• Maximum Bandwidth Usage

Maximum Number of Elementary Streams per Groomed Program

Up to 510 components can be mixed to create an individual output program. The maximum
number of elementary streams per output multiplex is 512, including the PAT and at least one PMT
for the program, which would leave 510 elementary streams maximum per program.
The maximum number of elementary streams per output program is limited by the following:
• An output program may have none or one groomed MPEG-4/AVC video stream.

CAP-1000 Software Guide v4.0 331

Chapter 17 Grooming Concepts Grooming Capabilities and Maximum Usage

• An output program may have none or one groomed MPEG-2 video stream.
• An output program may not have one groomed MPEG-2 video stream and one groomed
MPEG-4/AVC video stream.
• An output program may have none or a variable number of non-video (e.g., audio and private
data) streams. The maximum number of non-video streams per program depends on many
factors, including: the total number of filtered input PIDs (4096), the multiplex type (e.g. DVB
or DCII), the number of passed tables and the number of programs. The maximum number is
capped by the maximum number of elementary streams per multiplex (512).
• An output program may have extra output stream placeholders to support ETV data streams,
including stream types and descriptors.

NOTE All these values are capped by other resources of the device (memory and CPU), thus, if any other resource
maximum usage is reached, these numbers will not be obtained.

Maximum Number of Groomed Programs per Multiplex

The CAP-1000 allows up to 95 programs per output transport multiplex. If the total number of
groomed programs exceeds the device capabilities, an alarm is generated. Note that the actual
maximum number in a particular system may be smaller, depending on the grooming
configuration of CAP-1000. This limitation applies to the passed programs as well, regardless of
whether the passed programs carry video, audio, or any other data.

Maximum Number of Groomed Programs per Device

The CAP-1000 allows up to 2048 output PIDs or 384 output programs per CAP-1000. You can
view the number of groomed programs on a CAP-1000 in the CherryPicker Element Manager.
This information displays in the status bar at the bottom of the window.

Grooming—Number of Groomed Programs

Table 17-1 summarizes the maximum number of elementary streams and output programs that can
be groomed per multiplex and CAP-1000 device.

Table 17-1 Maximum Streams/Programs per Multiplex and Device

Component Maximum Value

Maximum number of programs per CAP-1000 device 384 SD MPEG-2 @ 3.75Mbps (including audio) average.

Maximum number of output PIDs per CAP-1000 device 2048

332 ARRIS Enterprises, Inc.

 Grooming Capabilities and Maximum Usage

Table 17-1 Maximum Streams/Programs per Multiplex and Device (continued)

Maximum number of programs per multiplex 95

Maximum number of elementary streams per multiplex 512

Maximum number of non-video elementary streams 416 (where 416 = 512 minus 96). The maximum number of
groomed per multiplex non-video streams per program depends on many factors,
including the total PIDs (4096), the multiplex type (e.g.
DVB or DCII), the number of passed tables, the number of
programs, device RAM, and output bit rate limits.

Maximum number of video elementary streams groomed One MPEG-2 or MPEG-4 video stream.
per program

Maximum Bandwidth Usage

Table 17-2 summarizes the maximum number of input and output programs and bandwidth usage
that can be groomed per CAP-1000 device. All programs are SD MPEG-2.

Table 17-2 Maximum Input/Output Programs per Device

Maximum Number of Average Bit Rate per Maximum Bandwidth Description

Programs Program

384 3,750,000 1,440,000 Primary input programs

384 3,750,000 1,440,000 PRED input programs

384 3,750,000 1,440,000 DPI input programs

384 3,750,000 1,440,000 Output programs

You can also rate shape output programs and assign recoders to manage bandwidth usage. See
Chapter 22, “Configuring Rate Shaping, Stat Mux Pools, and Recoders” for more information.

CAP-1000 Software Guide v4.0 333

Chapter 17 Grooming Concepts Grooming Capabilities and Maximum Usage

334 ARRIS Enterprises, Inc.

 CHAPTER 18
Grooming Programs

In This Chapter
• Programs
• Grooming Programs Using Diagram View
• Grooming Programs Using Tabular View
• Grooming Programs and Creating an Output Multiplex
• Managing Grooming Definitions
• Grooming Encrypted Streams
• Managing Output Programs
Refer to Chapter 17, “Grooming Concepts” for a review of basic grooming concepts and a
discussion of grooming capabilities and maximum usages. See Chapter 13, “Content Picking” for
a review of the Content Picking window components, panels, menus, and icons.

Programs
Program grooming is the process of selecting one or more input programs and grooming them to
an output program or an output multiplex.

Grooming Functions
You perform program grooming in the Diagram view or Table views of the Content Picking >
Grooming tab. This window lets you:
• Groom one or more programs by drag and drop
• Groom and create output multiplexes at the same time
• Define grooms with start/end dates and times
• Recode programs for rate shaping
• Add or drop grooming definitions
• Add or delete programs
• Configure backup streams for failover support

CAP-1000 Software Guide v4.0 335

Chapter 18 Grooming Programs Programs

Program Grooming

Grooming Functions
The following program grooming functions are supported in the Grooming tab:
• Groom one or more input programs to one or more MPTS multiplexes.
• Groom one or multiple input programs from a single MPTS input multiplex into one or
multiple output programs of a single output MPTS multiplex.
• Groom one or more input programs (SPTS) multiplexes to one or multiple output programs of
a single output MPTS multiplex. The input SPTS multiplexes have to belong to the same GigE
port.
• Groom one or multiple input SPTS multiplexes to one or multiple output SPTS multiplexes.
The output SPTS multiplexes have to belong to the same GigE port and the input SPTS
multiplexes have to belong to the same GigE port. The input and output GigE ports can be
either the same or be different.
• Groom one or multiple input programs to one or multiple output SPTS multiplexes and create
an output multiplex at the same time.

336 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

• Groom backup programs by dragging the backup programs to the PRED placeholder.

Bulk Operations
The CAP-1000 supports the following bulk grooming operations using the Grooming tab in the
Content Picking window:
• Grooming of one or multiple input programs from a single MPTS input multiplex into one or
multiple output programs of a single output MPTS multiplex.
• Grooming of one or multiple input programs from a single MPTS input multiplex into one or
multiple output SPTS multiplexes. Note that the output SPTS multiplexes must belong to the
same GigE port.
• Grooming of one or multiple input SPTS multiplexes into one or multiple output programs of
a single output MPTS multiplex. Note that the input SPTS multiplexes have to belong to the
same GigE port
• Grooming of one or multiple input SPTS multiplexes into one or multiple output SPTS
multiplexes. Note that the output SPTS multiplexes have to belong to the same GigE port. The
input SPTS multiplexes MAY belong to different GigE ports. The input and output GigE ports
can be either the same or be different.

NOTE Grooming of one or multiple input MPTS multiplexes into one or multiple output MPTS multiplexes is not
supported.

When grooming to output SPTS or MPTS multiplexes, program redundancy is provided by

dragging the backup programs to the PRED redundancy place holder.

Grooming Programs Using Diagram View

You can groom one or more input programs to an output mux, a previously groomed program
( ), or a program placeholder ( ) created by a configuration file.

To groom programs:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes for the selected output port display in the Output
panel, along with program placeholders, if any, that are associated with the configuration file.

CAP-1000 Software Guide v4.0 337

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

Output Mux Menu

5 Expand the Component Tree.

6 In the Input panel, select one or more input programs from the Tree.

NOTE To add to any existing streams in a previously groomed program, select the streams you want in the Tree,
press CTRL, and then drag them to the output you want.

338 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

Input Program

7 Do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected input programs and drop them on a program placeholder
or a groomed program for the output mux(es) you want.

CAP-1000 Software Guide v4.0 339

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Drag and Drop to Output Mux

• If you selected a specific multiplex for the Output Mux menu, drag the selected input
programs and drop them on a program placeholder, a groomed program, or in the Drop Input
Here area.

340 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

Drop Input Here

8 Release the mouse button.

The programs are added to the Grooming Definition panel and the Primary Streams panel at the
bottom of the window. The Edit icon appears in the Output panel and in the Grooming definitions
panel because the changes have not yet been applied.

IMPORTANT If you want to create a dynamic groom, do not click Apply yet.

9 (Optional) To configure a start date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Now field for the Start parameter.
The Select Start Date/Time window opens.

CAP-1000 Software Guide v4.0 341

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Select Start Date/Time

b Clear the Now option.

c Select a Start Date using the calendar.
d Select the start time using the Start Time menu.
e Click OK.
10 (Optional) To configure an end date and time, do the following:
a In the Properties panel, double-click the Forever field for End parameter.
The Select End Date/Time window opens.

Select End Date/Time

b Clear the Forever option.

c Select an End Date using the calendar.

342 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

d Select the end time using the End Time menu.

e Click OK.
11 To configure any other parameters, select the parameter you want, and then enter the required
information. Use the scroll bar to scroll hidden columns into view.

Diagram View

See Table 18-1 for a description of parameters that can appear in the Diagram view when you
groom a program.

NOTE The parameters that display in the Diagram view differ depending on whether you select All Muxes, All
SPTS Muxes, All MPTS Muxes, or a specific Mux. The following table shows parameters for a specific
mux.

Table 18-1 Diagram View Grooming Parameters

Output Panel

Mux Info Shows the name assigned to the multiplex.

Primary Shows the primary program name.

Backup Indicates if a program has been configured for backup, if any.

CAP-1000 Software Guide v4.0 343

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Slate Indicates if a slate has been configured for backup, if any.

DPI Indicates if digital program insertion (DPI) is active

Service Name Specifies the name of the output program.

Program Number Shows the program number assigned by the CAP-1000.

Recoder Indicates if a recoder has been assigned. The options are:

• No
• HD MPEG-2
• SD MPEG-2
• HD MPEG-4/AVC
See section,“Managing Recoders,”on page 451 for more information.

EBIF Enables EBIF at the output program level when the required license key is
installed. See Chapter 26, “Managing EBIF” for more information.

CCC Enables the CAP-1000 to carry closed captioning conversion (CCC) information
in SD or HD MPEG-2 user video streams for DTV. See section,“Managing
Closed Captioning Conversion,”on page 306 for more information.
CALM Enables volume leveling via the Commercial Advertisement Loudness
Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters
of groomed AC-3 audio streams. See section,“Enabling CALM,”on
page 402 for more information.
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.

Properties Panel

Date/Time Shows the start/end date and time for the grooming definition. These
properties can only be configured when creating a new groom. The properties
cannot be configured after a program is groomed and changes have been
applied.

Start Shows the start date and time for a groom.

End Shows the end date and time for a groom.

Recoding Shows recoding properties for the selected grooming definition.

Min Bit Rate (Mbps) Specifies a video bit rate floor that the CAP-1000 is not to drop below when
recoding video streams (in megabits per second). See section,“Managing
Recoders,”on page 451 for more information.
Max Bit Rate (Mbps) Specifies a video bit rate ceiling that the CAP-1000 is not to go above when
recoding video streams (in megabits per second).

344 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Priority Specifies the degree of recoding for a recodable video stream. The priority
levels characterize the relative amount of recoding that will be done for
various video streams in a multiplex and is used to control the rate of the
multiplex.
Ten priority levels are defined. Level 1 indicates the lowest priority stream
(maximum amount of recoding) and Level 10 indicating the highest priority
stream (minimum amount of recoding), with increments of 1. The priory levels
can be modified at any time, even after a program is created and a stream is
being passed to the output.

Backup Configures backup streams for failover support. See Chapter 29,
“Configuring Program Redundancy” for information.
Error Period Specifies the length of time during which the primary cannot recover from
error. If the primary cannot recover by the end of the interval, switching to
backup occurs. If the primary can recover, no switching occurs. The options
are: Min 1 second (in 1 second increments) / Max 100 seconds. The default is
2 seconds.

Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup program to
switch over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup program to
switch over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup program to switch over if any video
stream underflows.
• First Audio Only—enables the backup program to switch over if the first
audio stream underflows.

Switch on Underflow Configures primary to backup switchovers. The options are:

• Immediate—switching to backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Auto Switchback Specifies whether the backup program switches back to the primary program
when the error condition ends.
• True—switches back to the primary program when the error condition
ends.
• False—continues playing out the backup program after the error condition
ends.

CAP-1000 Software Guide v4.0 345

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Error Free Period Specifies the length of time in which the primary program must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
program. The CAP-1000 remains with the backup program instead. The
options are: Min 7 seconds / Max 100 seconds. The default is 12 seconds (in
1-second increments). The longer the period of time, the more certain you can
be that the primary program is error free.

Slate Level Shows the grooming level for a slate.

Slate Error Period Specifies the length of time during which the primary slate cannot recover
from error. If the primary cannot recover by the end of the interval, switching
to the backup slate occurs. If the primary can recover, no switching occurs.
The options are: Min 1 second (in 1 second increments) / Max 100 seconds.
The default is 10 seconds.

Slate Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup slate to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup slate to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup slate to switch over if any video stream
underflows.
• First Audio Only—enables the backup slate to switch over if the first audio
stream underflows.

Slate Switch on Underflow Configures backup to primary slate switchovers. The options are:
• Immediate—switching to the backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Slate Auto Switch Back Specifies whether the backup slate switches back to the primary slate when
the error condition ends.
• True—switches back to the primary slate when the error condition ends.
• False—continues playing out the backup slate after the error condition
ends.

Slate Error Free Period Specifies the length of time in which the primary slate must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
slate. The CAP-1000 remains with the backup slate instead. The options are:
Min 7 seconds / Max 100 seconds. The default is 12 seconds (in 1-second
increments). The longer the period of time, the more certain you can be that
the primary slate is error free.

346 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Service Properties The Service Properties are only enabled for grooming DVB programs. If you are
grooming MPEG-2 streams or DigiCipher II streams, these properties are
disabled. If you do not enter anything, then the input Service Provider Name
and Service Name are used.

Service Provider Name Shows the Service Provider Name passed from the input (if the input has a
Service Provider Name in the DVB SDT). You can override this name in the
output SDT.

Service Name Shows the Service Name passed from input (if the input has a Service Name
in the DVB SDT). You can override this name in the output SDT.

Grooming Definitions Panel

ID Shows the default grooming definition ID.

Type Shows the specified grooming type.

Description Specifies a description for the groom.

Level Shows the grooming level. The value is 0 for static grooms and 1 (or above) for
scheduled grooms.

Status Indicates if the grooming definition is valid.

Use Trigger Enables grooming input programs based on a schedule. Automatically enabled
for drag-and-drop grooms.If no triggering event has been defined, an error
window opens. See Chapter 21, “Using Trigger Events” for more
information.

Trigger(s) Selects the pre-configured trigger for this groom. At least one event is
required to complete this action.

Duration Specifies the duration of the triggering event.

CUE Insertion Enables or disables the insertion of CUE streams per SCTE 35. When CUE
Insertion is enabled, an extra output stream is automatically added in the GUI,
and the original (network) cue stream is prevented from being output. See
section,“SCTE 35 Cue Insertion,”on page 483 for more information.

Pass Streams Enables encrypted streams to be passed or groomed. Pass Streams is enabled
by default.

Program Descriptors Specifies how to handle program descriptors: at the output:

• Do Not Pass—Does not pass the program descriptors to output.
• Auto Pass Exclude CA—Passes the program descriptors, but exclude
Conditional Access (CA) at output.
• Auto Pass Include CA—Passes the program descriptors and CA at output.
• Custom—Adds a custom program descriptor tag. Only programs with this
tag are passed to output.
• Edit Custom—Edits the program descriptors.

CAP-1000 Software Guide v4.0 347

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Program Intervals Panel

Start Time Shows the specified start date and time.

End Time Shows the specified end date and time.

ID Shows the default grooming definition ID.

Description Shows the description of the associated grooming definition. By default, for
program grooming, the description is the input program's name. For custom
grooming, the description is “Custom.”

Input Line Shows the input line for the groom.

Mux Shows the multiplex for the groom.

Program For program grooming, shows the input program's name. For custom
grooming, shows the groomed input pids and their type.

Alarms

Show • Critical—Filters on a service-affecting condition has occurred and an

immediate corrective action is required. Such a severity can be reported,
for example, when a managed object becomes totally out of service and its
capability must be restored.

• Major—Filters on a service-affecting condition has developed and an

urgent corrective action is required. Such a severity can be reported, for
example, when there is a severe degradation in the capability of the
managed object and its full capability must be restored.

• Minor—Filters on the existence of a non-service affecting fault condition

and that corrective action should be taken in order to prevent a more
serious (for example, service affecting) fault. Such a severity can be
reported, for example, when the detected alarm condition is not currently
degrading the capacity of the managed object.

• Warning—Filters on the detection of a potential or impending service

affecting fault, before any significant effects have been felt. Action should
be taken to further diagnose (if necessary) and correct the problem in order
to prevent it from becoming a more serious service affecting fault.

• Info—Filters on additional information is available for this event.

• Event—Filters on a normal occurrence that does not represent a condition

or requires user attention. An event is not raised or cleared; it simply
occurs. It does not have a raised/cleared statu, nor does it have a Cleared
Time or a Cleared User indicator. An event is not de-bounced.

• Raised Only—Filters on raised alarms.

• DPI Splice Results—Filters on digital program insertion splice results.

• Collapse—Toggles alarm descriptions.

348 ARRIS Enterprises, Inc.

 Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

• Include PID Alarms—Filters on packet identifier (PID) alarms.

Time Filter Filters on the supplied start and end date/time.

Search Description Filters on a string.

Primary Streams/Backup Streams

Type Shows a video, audio, or data graphic.

Line Shows the output port for the elementary stream.

Mux Shows the output multiplex for the elementary stream.

Program Shows the program name.

Input PID Shows the input PID number assigned in the packet header of an MPEG
stream that identifies the transport stream to which the packet belongs.

Network Rule Determines which data streams are kept or dropped from primary or backup
programs based on Network rules. During DPI, the Network rules are not used,
but the DPI rules are used. See Chapter 26, “Managing EBIF,” for more
information.

NW EBIF Priority Determines how the CAP-1000 handles merged network EBIF input streams
when packets are received at the same time. You can assign integer priorities
to merged inputs in custom grooming. A higher integer signifies a higher
priority. See Chapter 26, “Managing EBIF,” for more information.

DPI Rule Determines how an output data stream is handled during DPI. See Chapter
24, “Enabling Digital Program Insertion” for more information.
DPI EBIF Priority Determines how the CAP-1000 handles merged EBIF input streams when
packets are received at the same time. You can assign integer priorities to
merged inputs in custom grooming. A higher integer signifies a higher priority.
See Chapter 26, “Managing EBIF,” for more information.

Output PID Specifies the PID number assigned in the packet header of an MPEG stream
that identifies the transport stream to which the packet belongs. Select Auto
to automatically assign the output PID.

Network Dialnorm Selects the value for the primary and backup AC3 live audio stream.
• Default value is no change (absolute 0)
• Absolute values are 1 to 31
• Relative values are -1 to +30
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.
See section,“Enabling CALM,”on page 402 for more information.

DPI Dialnorm Selects the value for an AC3 live audio stream used in Digital Program
Insertion (DPI).

CAP-1000 Software Guide v4.0 349

Chapter 18 Grooming Programs Grooming Programs Using Diagram View

Table 18-1 Diagram View Grooming Parameters (continued)

Slate Component

Type Displays the stream type: MPEG- 2 Video, MPEG-4 Video, or MPEG-4 Audio.

Line Shows the line name for the slate.

Mux Shows the mux name for the slate. This field is empty if row is representing
file.

Program Shows the program name for the slate. Program Name.

File Shows the file name. this field is empty for live audio.

Input PID Shows the input Packet Identifier (PID).

Descriptors Panel

Type Shows the descriptor type for a selected stream in the Primary/Backup
Streams Panel.

Description Provides more information about the descriptor. For example, in the case of an
ISO 639 Language descriptor, it contains the name of the language, such as
English. In the case of an ETV registration descriptor, the Type is Registration
and the Description is ETV1.

Tag (Hex) Shows the tag in hexadecimal format.

Length Shows the data length value.

Hex Value Shows the descriptor in hexadecimal format. For example, the entire
descriptor in hexadecimal looks like this: 0a04656e6700.
• Name: ISO 639 Language
• Tag in hex: 0
• Length in hex: 04
• Data in hex: 656e6700
• Data in ASCII: eng
Hex 65 is an ASCII ‘e’, hex 6e is an ASCII ‘n’, hex 67 is an ASCII ‘g’, and hex 00
is not a printable ASCII character so it is represented by ‘.’

ASCII Value Shows the descriptor in ASCII format.

See section,“Grooming Window,”on page 180 for a complete description of window components,
icons, and menus.
12 Click Apply.
A warning window opens.
13 Click Yes.

350 ARRIS Enterprises, Inc.

 Grooming Programs Using Tabular View

Grooming Programs Using Tabular View

You can groom one or more input programs to an output mux, a previously groomed program
( ), or a program placeholder ( ) created by a configuration file.

To groom programs:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes for the selected output port display in the Output
panel, along with program placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

Output Mux Menu

5 Expand the Component Tree.

6 In the Input panel, select one or more input programs from the Tree.

CAP-1000 Software Guide v4.0 351

Chapter 18 Grooming Programs Grooming Programs Using Tabular View

NOTE To replace any existing streams in a previously groomed program, select the streams you want in the Tree,
press CTRL, and then drag them to the output you want.

Input Programs

7 Do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected input programs and drop them on the output mux(es)
you want.

352 ARRIS Enterprises, Inc.

 Grooming Programs Using Tabular View

Drag and Drop to Output Muxes

• If you selected a specific multiplex for the Output Mux menu, drag the selected input
programs and drop them on a program placeholder, a groomed program, or in the Drop Input
Here area.

CAP-1000 Software Guide v4.0 353

Chapter 18 Grooming Programs Grooming Programs Using Tabular View

Drop Input Here

8 Release the mouse button.

NOTE If you added the programs to a previously groomed program, the Select Component window opens. To
replace the program, go to section,“Replacing Grooming Definitions for Output Programs,”on
page 375. To groom a backup program, go to Chapter 29, “Configuring Program Redundancy”. To
groom a slate, go to section,“Configuring Slates (Second-level Backup),”on page 603.

The programs are added to the Grooming Definition panel and the Primary Streams or Backup
Streams panel at the bottom of the window. The Edit icon appears in the Output panel and in the
Grooming definitions panel because the changes have not yet been applied.

IMPORTANT If you want to create a dynamic groom, do not click Apply yet.

9 (Optional) To configure a start date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Now field for the Start Time parameter.
The Select Start Date/Time window opens.

354 ARRIS Enterprises, Inc.

 Grooming Programs Using Tabular View

Select Start Date/Time

b Clear the Now option.

c Select a Start Date using the calendar.
d Select the start time using the Start Time menu.
e Click OK.
10 (Optional) To configure an end date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Forever field for End Time parameter.
The Select End Date/Time window opens.

Select End Date/Time

b Clear the Forever option.

c Select an End Date using the calendar.

CAP-1000 Software Guide v4.0 355

Chapter 18 Grooming Programs Grooming Programs Using Tabular View

d Select the end time using the End Time menu.

e Click OK.
11 To configure any other parameters, go to a row you want in the Output panel of the Table view. In
the applicable cell, select the parameter you want to configure, and then enter the required
information. Use the scroll bar to scroll hidden columns into view.

Tabular View

See Table 18-2 for a description of parameters that can appear in the Tabular view when you
groom a program.

NOTE The parameters that display in the Tabular view differ depending on whether you select All Muxes, All
SPTS Muxes, All MPTS Muxes, or a specific Mux. The following table shows parameters for a specific
mux.

Table 18-2 Tabular View Grooming Parameters

Output Panel

Mux Info Shows the name assigned to the multiplex.

Primary Shows the primary program name.

Backup Indicates if a program has been configured for backup, if any.

Slate Indicates if a slate has been configured for backup, if any.

356 ARRIS Enterprises, Inc.

 Grooming Programs Using Tabular View

Table 18-2 Tabular View Grooming Parameters (continued)

DPI Indicates if digital program insertion (DPI) is active

Service Name Specifies the name of the output program.

Program Number Shows the program number assigned by the CAP-1000.

Recoder Indicates if a recoder has been assigned. The options are:

• No
• HD MPEG-2
• SD MPEG-2
• HD MPEG-4/AVC
See section,“Managing Recoders,”on page 451 for more information.

EBIF Enables EBIF at the output program level when the required license key is
installed. See Chapter 26, “Managing EBIF” for more information.

CCC Enables the CAP-1000 to carry closed captioning conversion (CCC) information
in SD or HD MPEG-2 user video streams for DTV. See section,“Managing
Closed Captioning Conversion,”on page 306 for more information.
CALM Enables volume leveling via the Commercial Advertisement Loudness
Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters
of groomed AC-3 audio streams. See section,“Enabling CALM,”on
page 402 for more information.
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.

Properties Panel

Program Number Shows the program number assigned by the CAP-1000.

Slate Error Period Specifies the length of time during which the primary slate cannot recover
from error. If the primary cannot recover by the end of the interval, switching
to the backup slate occurs. If the primary can recover, no switching occurs.
The options are: Min 1 second (in 1 second increments) / Max 100 seconds.
The default is 10 seconds.

CAP-1000 Software Guide v4.0 357

Chapter 18 Grooming Programs Grooming Programs Using Tabular View

Table 18-2 Tabular View Grooming Parameters (continued)

Slate Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup slate to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup slate to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video or
the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup slate to switch over if any video stream
underflows.
• First Audio Only—enables the backup slate to switch over if the first audio
stream underflows.

Slate Switch on Underflow Configures backup to primary slate switchovers. The options are:
• Immediate—switching to the backup occurs immediately.
• After Interval—switching to backup occurs after the specified alarm
interval.

Slate Auto Switch Back Specifies whether the backup slate switches back to the primary slate when
the error condition ends.
• True—switches back to the primary slate when the error condition ends.
• False—continues playing out the backup slate after the error condition
ends.

Slate Error Free Period Specifies the length of time in which the primary slate must be error-free
before a switch is made back to the primary source. If errors are detected and
they cannot be resolved, the CAP-1000 does not switch back to the primary
slate. The CAP-1000 remains with the backup slate instead. The options are:
Min 7 seconds / Max 100 seconds. The default is 12 seconds (in 1-second
increments). The longer the period of time, the more certain you can be that
the primary slate is error free.

Primary Streams/Backup Streams

Type Shows a video, audio, or data graphic.

Line Shows the output port for the elementary stream.

Mux Shows the output multiplex for the elementary stream.

Program Shows the program name.

Input PID Shows the input PID number assigned in the packet header of an MPEG
stream that identifies the transport stream to which the packet belongs.

Network Rule Determines which data streams are kept or dropped from primary or backup
programs based on Network rules. During DPI, the Network rules are not used,
but the DPI rules are used. See Chapter 26, “Managing EBIF,” for more
information.

358 ARRIS Enterprises, Inc.

 Grooming Programs Using Tabular View

Table 18-2 Tabular View Grooming Parameters (continued)

NW EBIF Priority Determines how the CAP-1000 handles merged network EBIF input streams
when packets are received at the same time. You can assign integer priorities
to merged inputs in custom grooming. A higher integer signifies a higher
priority. See Chapter 26, “Managing EBIF,” for more information.

DPI Rule Determines how an output data stream is handled during DPI. See Chapter
24, “Enabling Digital Program Insertion” for more information.
DPI EBIF Priority Determines how the CAP-1000 handles merged EBIF input streams when
packets are received at the same time. You can assign integer priorities to
merged inputs in custom grooming. A higher integer signifies a higher priority.
See Chapter 26, “Managing EBIF,” for more information.

Output PID Specifies the PID number assigned in the packet header of an MPEG stream
that identifies the transport stream to which the packet belongs. Select Auto
to automatically assign the output PID.

Network Dialnorm Selects the value for the primary and backup AC3 live audio stream.
• Default value is no change (absolute 0)
• Absolute values are 1 to 31
• Relative values are -1 to +30
Note: This option does not apply to file grooms with live AC3 audio, including
slates with live audio, primary file grooms with live audio, or backup file
grooms with live audio.
See section,“Enabling CALM,”on page 402 for more information.

DPI Dialnorm Selects the value for an AC3 live audio stream used in Digital Program
Insertion (DPI).

Slate Component

Type Displays the stream type: MPEG- 2 Video, MPEG-4 Video, or MPEG-4 Audio.

Line Shows the line name for the slate.

Mux Shows the mux name for the slate. This field is empty if row is representing
file.

Program Shows the program name for the slate. Program Name.

File Shows the file name. this field is empty for live audio.

Input PID Shows the input Packet Identifier (PID).

Descriptors Panel

Type Shows the descriptor type for a selected stream in the Primary/Backup
Streams Panel.

Description Provides more information about the descriptor. For example, in the case of an
ISO 639 Language descriptor, it contains the name of the language, such as
English. In the case of an ETV registration descriptor, the Type is Registration
and the Description is ETV1.

CAP-1000 Software Guide v4.0 359

Chapter 18 Grooming Programs Grooming Programs and Creating an Output Multiplex

Table 18-2 Tabular View Grooming Parameters (continued)

Tag (Hex) Shows the tag in hexadecimal format.

Length Shows the data length value.

Hex Value Shows the descriptor in hexadecimal format. For example, the entire
descriptor in hexadecimal looks like this: 0a04656e6700.
• Name: ISO 639 Language
• Tag in hex: 0
• Length in hex: 04
• Data in hex: 656e6700
• Data in ASCII: eng
Hex 65 is an ASCII ‘e’, hex 6e is an ASCII ‘n’, hex 67 is an ASCII ‘g’, and hex 00
is not a printable ASCII character so it is represented by ‘.’

ASCII Value Shows the descriptor in ASCII format.

See section,“Grooming Window,”on page 180 for a complete description of window components,
icons, and menus.
12 Click Apply.
13 Click Yes.

Grooming Programs and Creating an Output Multiplex

It is possible to groom one or multiple input programs to one or multiple output SPTS multiplexes
and create an output multiplex at the same time.

To groom programs and create an output multiplex:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .
3 In the Output Mux menu, select All SPTS Muxes.
4 Expand the Component Tree.
5 In the Input panel, select one or more input programs from the Tree.
6 Drag the selected input programs and drop them in the Drop Input Here area.

NOTE Example illustrations show the Diagram view.

360 ARRIS Enterprises, Inc.

 Grooming Programs and Creating an Output Multiplex

Grooming Diagram View

The Create Output Multiplex window opens.

CAP-1000 Software Guide v4.0 361

Chapter 18 Grooming Programs Managing Grooming Definitions

Create Output Multiplex

7 To configure the output multiplex, go to Chapter 14, “Configuring Multiplexes” for information.
8 To configure grooming properties, go to section,“Grooming Programs Using Diagram View,”on
page 337 or section,“Grooming Programs Using Tabular View,”on page 351.
9 Click Apply.
A warning window opens.
10 Click Yes.

Managing Grooming Definitions

The Context menu in the Output panel of the Grooming window provides a convenient method for
managing grooming definitions. The following topics are covered:
• Adding Grooming Definitions
• Replacing Grooming Definitions
• Creating Grooming Definitions
• Deleting Grooming Definitions

362 ARRIS Enterprises, Inc.

 Managing Grooming Definitions

Adding Grooming Definitions

The Add Grooming Definition function adds an empty row to the Grooming Definition panel
where you can configure new, non-overlapping intervals for a dynamic groom.

To add a grooming definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All option, all multiplexes display in the Output panel, along with program placeholders,
if any, that are associated with the configuration file.
If you select the All SPTS or All MPTS option, only those output multiplexes display in the
Output panel, along with program placeholders, if any, that are associated with the configuration
file. If you select a specific multiplex, program placeholders, if any, display in the panel.
4 In the Output panel, right-click the program you want and select Add Grooming Definition from
the Context menu.

NOTE Example illustrations show the Diagram view.

Add Grooming Definition

A new row is added to the Grooming Definitions panel.

CAP-1000 Software Guide v4.0 363

Chapter 18 Grooming Programs Managing Grooming Definitions

Add Grooming Definition

5 Select the new row.

6 To configure a start date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Now field for the Start Time parameter.
The Select Start Date/Time window opens.

Select Start Date/Time

364 ARRIS Enterprises, Inc.

 Managing Grooming Definitions

b Clear the Now option.

c Select a Start Date using the calendar.
d Select the start time using the Start Time menu.
e Click OK.
7 (Optional) To configure an end date and time, do the following:
a In the Properties panel, double-click the Forever field for End Time parameter.
The Select End Date/Time window opens.

Select End Date/Time

b Clear the Forever option.

c Select an End Date using the calendar.
d Select the end time using the End Time menu.
e Click OK.
8 To configure any other parameters, select the parameter you want, and then enter the required
information. Use the scroll bar to scroll hidden columns into view.
9 Click Apply.
10 Click Yes.

CAP-1000 Software Guide v4.0 365

Chapter 18 Grooming Programs Managing Grooming Definitions

New Grooming Definition

11 Repeat step 4 through step 10 to add more, non-overlapping grooming definitions. The static
definition (Level 0) play outs before the dynamic grooms (Levels 1, 2, 3, etc).

Replacing Grooming Definitions

The Select Grooming Definition function lets you replace an existing grooming definition on a
dynamic groom with a new one. This function is only available when there is more than one
existing groom definition for the output program.

To replace a grooming definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

366 ARRIS Enterprises, Inc.

 Managing Grooming Definitions

4 Expand the Component Tree.

5 In the Input panel, select an input program from the Tree.

NOTE Example illustrations show the Diagram view.

Input Program

6 Drag the selected input program and drop it on a program configured for a dynamic groom in the
Output panel.

Select Grooming Definition

7 Select the grooming definition that you want.

CAP-1000 Software Guide v4.0 367

Chapter 18 Grooming Programs Managing Grooming Definitions

8 Click OK.
9 Click Apply.
10 Click Yes.
The grooming definition is replaced to the Grooming Definitions panel.

Creating Grooming Definitions

The Select Grooming Definition function lets you create a new grooming definition and add it to
existing grooming definitions for a dynamic groom. This function is only available when there is
more than one existing groom definition for the output program.

To create a grooming definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 Expand the Component Tree.
5 In the Input panel, select an input program from the Tree.

NOTE Example illustrations show the Diagram view.

368 ARRIS Enterprises, Inc.

 Managing Grooming Definitions

Input Program

6 Drag the selected input program and drop it on a program configured for a dynamic groom in the
Output panel.

Select Grooming Definition

7 Click Create New.

The grooming definition is added to the Grooming Definitions panel.
8 In the Properties panel, configure the Start/End and Date/Time parameters. to add more, non-
overlapping grooming definitions. The static definition (Level 0) play outs before the dynamic
grooms (Levels 1, 2, 3, etc).

CAP-1000 Software Guide v4.0 369

Chapter 18 Grooming Programs Managing Grooming Definitions

9 Click Apply.
10 Click Yes.
The new grooming definition appears in the Grooming Definitions panel.

New Grooming Definition

Deleting Grooming Definitions

When a grooming definition is no longer needed, you can delete it with the Delete Grooming
Definition(s) command. Since each output program may have multiple groom definitions, the
definitions can be removed individually, or all definitions may be removed with a single request.
The Delete Grooming Definition(s) can be used for any program groom, custom groom, or file
groom; however, it cannot be used for a PID pass groom.

To delete a grooming definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.

370 ARRIS Enterprises, Inc.

 Managing Grooming Definitions

If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 In the Grooming Definition panel, right-click the program(s) you want to delete and select Delete
Grooming Definition(s) from the Context menu.

NOTE Example illustrations show the Diagram view.

Delete Grooming Definition

5 Click Apply.
6 Click Yes.
The grooming definition is removed.

CAP-1000 Software Guide v4.0 371

Chapter 18 Grooming Programs Grooming Encrypted Streams

Grooming Encrypted Streams

The CAP-1000 supports the grooming of clear and encrypted streams. Encryption is a method of
protecting Entitlement Management Messages (EMM) and Entitlement Control Messages (ECM)
by cryptographic methods. The Grooming tab of the CherryPicker Element Manager displays the
ECM and EMM Packet Identifiers (PIDs) under the programs they are associated with (for both
input and output programs). ECM tables which are associated with streams are also shown under
the program. The input ECM and EMM PIDs are extracted from the input Program Map Table
(PMT) and the input Conditional Access Tables (CAT) tables, respectively.
You can pass an encrypted program or an elementary stream using drag-and-drop. There is no
distinction between passing clear streams or encrypted streams. The CAP-1000 automatically
selects the Pass mode when at least one of the input streams is encrypted.
Although the CAP-1000 automatically defaults to “passing” for encrypted streams, you have the
option to use the “grooming” mode instead of passing.
When the input program is encrypted and the streams are passed, the CAP-1000 passes the
required ECMs to the output. The output ECM PIDs are referred in the Conditional Access (CA)
descriptors of the output PMT.
The CAP-1000 also passes the required EMM streams. If the EMM PIDs are passed, the CAP-
1000 generates the CAT table. The CAT table contains the CA descriptors that refer to the EMM
PIDs. If the input CAT table changes, the changes are followed to the output.
When the input program is clear and you groom the input program, the ECM will not be groomed
to the output program.
The grooming of encrypted streams is not compatible with DPI, cue insertion, or EBIF passing and
merging.

Managing Output Programs

This section explains how to manage output programs during groom operations. The following
topics are covered:
• Program Components
• Adding Output Programs
• Replacing Grooming Definitions for Output Programs
• Deleting Output Programs
See Chapter 15, “Managing Tables and Output Programs” for more information.

372 ARRIS Enterprises, Inc.

 Managing Output Programs

Program Components
An output program consists of elementary streams that can include the following types:
• Advanced Audio Coding (AAC)
• High-Efficiency Advanced Audio Coding (HE-AAC)
• Dolby Digital (AC-3)
• Dolby Digital Plus (Enhanced AC-3)
• MPEG-4/AVC video (HD)
• MPEG-2 video (SD or HD)
• Private data streams

Output Program Icons

Table 18-3 describes the output program icons.

Table 18-3 Output Program Icons

Icon Description

Indicates an output program placeholder.

Indicates a groomed program currently playing.

Indicates an output multiplex is forced to backup.

Indicates a groomed program not playing (scheduled to be played

in the future).

Indicates a program forced to backup via PRED.

Indicates a groomed encrypted program currently playing.

Indicates a groomed encrypted program not playing (scheduled

to be played in the future).

Indicates an encrypted groomed program auto-switched to

backup via PRED.

Indicates a groomed program manually forced to backup via

PRED or Multiplex Redundancy (MRED).

Indicates an encrypted groomed program manually switched to

backup via PRED or MRED.

Indicates a slate defined.

CAP-1000 Software Guide v4.0 373

Chapter 18 Grooming Programs Managing Output Programs

Table 18-3 Output Program Icons (continued)

Icon Description

Indicates a file groom currently playing

Indicates a file groom scheduled to play in the future

Adding Output Programs

To add a program:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 Expand the Component Tree.
5 In the Output panel, right-click the multiplex, groomed program, or program placeholder you
want, and then select Add Program from the Context menu.

NOTE Example illustrations show the Diagram view.

374 ARRIS Enterprises, Inc.

 Managing Output Programs

Add Program

A new program placeholder is added to the list of programs in the Output panel.
6 Click Apply.
7 Click Yes.

Replacing Grooming Definitions for Output Programs

You can replace grooming definitions associated with a multiplex or previously groomed primary
program, backup program, or slate.

To replace a grooming definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

CAP-1000 Software Guide v4.0 375

Chapter 18 Grooming Programs Managing Output Programs

4 Expand the Component Tree.

5 In the Input panel, select one or more programs from the Tree.
6 Do one of the following:
• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected streams and drop them on the output muxes you want.
• If you selected a specific multiplex for the Output Mux menu, drag the selected streams and
drop them on a groomed program, or in the Drop Input Here area.
7 Release the mouse button.
8 Select Drop to Primary, Drop to Backup, or Drop to Slate (if configured).

Select Component

9 Click OK.
10 Click Apply.
11 Click Yes.

Deleting Output Programs

Deleting a program removes it from the groom and removes the grooming definitions associated
with the output programs.

To delete an output program:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 In the Output panel, right-click the program you want, and then select Delete Program from the
Context menu.

376 ARRIS Enterprises, Inc.

 Managing Output Programs

NOTE Example illustrations show the Diagram view.

Delete Program

5 Click Apply.
6 Click Yes.

CAP-1000 Software Guide v4.0 377

Chapter 18 Grooming Programs Managing Output Programs

378 ARRIS Enterprises, Inc.

 CHAPTER 19
Grooming Elementary Streams

In This Chapter
• Elementary Streams
• Audio Streams for the Visually Impaired
• Grooming Elementary Streams using the Diagram View
• Grooming Elementary Streams using the Tabular View
• Managing Elementary Streams
• Forcing Custom Grooms
• Enabling CALM
Refer to Chapter 17, “Grooming Concepts” for a review of basic grooming concepts and a
discussion of grooming capabilities and maximum usages. See Chapter 13, “Content Picking”for a
review of the Content Picking window components, panels, menus, and icons.

Elementary Streams
An elementary stream (ES), as defined by MPEG communication protocol, is usually the output of
an audio or video encoder. ES contains only one kind of data, e.g. video, audio, or data. An
elementary stream is often referred to as video, audio, or data bitstreams or streams. The format of
the elementary stream depends upon the codec or data carried in the stream, but will often carry a
common header when packetized into a packetized elementary stream.
Custom grooming is the process of selecting one or more elementary streams and grooming them
to an output program or an output multiplex. Custom grooming can include:
• one video stream
• any number of audio streams
• any number of data streams
• a black video file and one or more muted audio files

CAP-1000 Software Guide v4.0 379

 Elementary Streams

Custom Grooming

Stream Availability at Input

To successfully perform custom grooming, at least one valid stream must be present. Streams that
are not available at input are groomed when they show up at a later time. For example, it is
possible to custom groom elementary streams that are not present at the input, as well as those that
are currently not available in the input PMT, and then perform a “PID following” later when the
unavailable elementary streams become available. At least one stream to be groomed must be
available at the input. The CAP-1000 grooms the available elementary streams and remembers the
non-existent streams. This function is referred to “force custom groom.” Refer to section,“Forcing
Custom Grooms,”on page 401 for more information.
For non-existent PIDs the Controller gets the stream types and descriptors when the streams show
up at the input the first time. After this point, the custom grooming is triggered by PMT changes,
using the current PMT, the new PMT, and your grooming settings.

PID Sharing
A shared PID indicates that two or more elementary streams (in different programs) from an
upstream device use the same PID in an input mux. The nomenclature, [Shared], appears next to
the program and elementary streams that are shared in the Input panel of the Content Picking
window.

CAP-1000 Software Guide v4.0 381

Chapter 19 Grooming Elementary Streams Audio Streams for the Visually Impaired

PID Sharing

NOTE PID sharing does not apply to the passed streams.

Audio Streams for the Visually Impaired

Software release 4.0 adds support for audio streams for the visually impaired. An AD stream is an
audio stream that contains verbal narrative descriptions of what is occurring in the program, mixed
with the normal audio sound track in the intervals between stretches of dialog.
There are two types of AD streams: broadcast-mixed AD streams and receiver-mixed AD streams.
A broadcast-mixed AD stream is one in which the AD content is mixed with normal audio content
before the program is distributed (i.e., before it arrives at the set-top box and before it arrives at the
CAP-1000). A receiver-mixed AD stream is one that contains only AD content. A receiver-mixed
AD stream is mixed with a normal audio stream of the same audio codec and same language by the
STB to produce a complete AD stream. This stream is equivalent to a broadcast-mixed AD stream.
The CAP-1000 identifies a broadcast-mixed AD stream by adding the string, “Visually Impaired
Broadcast Mixed,” to the stream description in the GUI. The CAP-1000 identifies a receiver-
mixed AD stream by adding the string, “Visually Impaired Receiver Mixed,” to the GUI.

382 ARRIS Enterprises, Inc.

 Audio Streams for the Visually Impaired

Visually Impaired Broadcast Mixed

In a DVB multiplex, an AC3 Descriptor must be present in the PMT entry to identify the AD audio
stream. In a non-DVB mux, an AC3 or E-AC3 audio stream is described by an ATSC audio
descriptor in the PMT.
The CAP-1000 also checks whether an audio stream is an AD stream for PID following. When the
input PID of an AD stream changes, the new input AD stream is matched with the an output PID
of an AD stream of the same codec and language.
In prior software releases, the CAP-1000 always spliced an audio stream from and ad to replace
every audio stream in the network. Consequently the DPI rule for an audio stream was “Splice.” In
software release 4.0, however, the CAP-100 drops the network stream instead of splicing in an
audio stream from the ad. Consequently, the DPI rule for a receiver-mixed audio stream is Drop
instead of Splice.

CAP-1000 Software Guide v4.0 383

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Diagram View

Grooming Elementary Streams using the Diagram View

You can groom an elementary stream to an output mux, a previously groomed program ( ), or a
program placeholder ( ) created by a configuration file.

To groom an elementary stream:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes for the selected output port display in the Output
panel, along with program placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

Output Mux Menu

4 Expand the Component Tree.

5 In the Input panel, select one or more elementary streams from the Tree.

NOTE To replace any existing streams in a previously groomed program, select the stream from the Tree and then
press CTRL.

384 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Diagram View

Elementary Streams

6 Do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected streams and drop them on a program placeholder or a
groomed program for the output mux(es) you want.

CAP-1000 Software Guide v4.0 385

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Diagram View

Drag and Drop to Output Program

• If you selected a specific multiplex for the Output Mux menu, drag the selected streams and
drop them on a program placeholder, a groomed program, or in the Drop Input Here area.

Drop Input Here

7 Release the mouse button.

386 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Diagram View

The stream is added to the Grooming Definition panel and the Primary Streams/Backup Streams
panel at the bottom of the window.

Groomed Elementary Streams Before Apply

8 (Optional) To configure a start date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Now field for the Start parameter.
The Select Start Date/Time window opens.

Select Start Date/Time

b Clear the Now option.

CAP-1000 Software Guide v4.0 387

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Diagram View

c Select a Start Date using the calendar.

d Select the start time using the Start Time menu.
e Click OK.
9 (Optional) To configure an end date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Forever field for End parameter.
The Select End Date/Time window opens.

Select End Date/Time

b Clear the Forever option.

c Select an End Date using the calendar.
d Select the end time using the End Time menu.
e Click OK.
10 To configure any other parameters, select the parameter you want, and then enter the required
information. Use the scroll bar to scroll hidden columns into view

388 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Diagram View

Diagram View

See Table 18-1 on page 343 for a description of parameters that can appear in the Diagram view
when you groom elementary streams.

NOTE The parameters change depending on your selection in the Output Mux menu.

See section,“Grooming Window,”on page 180 for a complete description of window components,
icons, and menus.
11 Click Apply.
12 Click Yes.

CAP-1000 Software Guide v4.0 389

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Tabular View

Custom Groom—Elementary Streams

Grooming Elementary Streams using the Tabular View

You can groom an elementary stream to an output mux, a previously groomed program ( ), or a
program placeholder ( ) created by a configuration file.

To groom an elementary stream:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes for the selected output port display in the Output
panel, along with program placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

390 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Tabular View

Output Mux Menu

4 Expand the Component Tree.

5 In the Input panel, select one or more elementary streams from the Tree.

NOTE To replace any existing streams in a previously groomed program, select the stream from the Tree and then
press CTRL.

CAP-1000 Software Guide v4.0 391

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Tabular View

Elementary Streams

6 Do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected streams and drop them on the output mux you want.

392 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Tabular View

Drag and Drop to Output Mux

• If you selected a specific multiplex for the Output Mux menu, drag the selected streams and
drop them on a program placeholder, a groomed program, or in the Drop Input Here area.

Drop Input Here

CAP-1000 Software Guide v4.0 393

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Tabular View

7 Release the mouse button.

NOTE If you added the programs to a previously groomed program, the Select Component window opens. To
replace the program, go to section,“Replacing Grooming Definitions for Elementary Streams,”on
page 399. To groom a backup program, go to Chapter 29, “Configuring Program Redundancy”. To
groom a slate, go to section,“Configuring Slates (Second-level Backup),”on page 603.

The programs are added to the Grooming Definition panel and the Primary Streams or Backup
Streams panel at the bottom of the window. The Edit icon appears in the Output panel and in the
Grooming definitions panel because the changes have not yet been applied.

IMPORTANT If you want to create a dynamic groom, do not click Apply yet.

8 (Optional) To configure a start date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Now field for the Start parameter.
The Select Start Date/Time window opens.

Select Start Date/Time

b Clear the Now option.

c Select a Start Date using the calendar.
d Select the start time using the Start Time menu.
e Click OK.
9 (Optional) To configure an end date and time for a dynamic groom, do the following:
a In the Properties panel, double-click the Forever field for End parameter.
The Select End Date/Time window opens.

394 ARRIS Enterprises, Inc.

 Grooming Elementary Streams using the Tabular View

Select End Date/Time

b Clear the Forever option.

c Select an End Date using the calendar.
d Select the end time using the End Time menu.
e Click OK.
10 To configure any other parameters, go to a row you want in the Output panel of the Table view. In
the applicable cell, select the parameter you want to configure, and then enter the required
information. Use the scroll bar to scroll hidden columns into view.

CAP-1000 Software Guide v4.0 395

Chapter 19 Grooming Elementary Streams Grooming Elementary Streams using the Tabular View

Tabular View

See Table 18-2 on page 356 for a description of parameters that can appear in the Tabular view
when you groom a program.

NOTE The parameters change depending on your selection in the Output Mux menu.

See section,“Grooming Window,”on page 180 for a complete description of window components,
icons, and menus.
11 Click Apply.
12 Click Yes.

396 ARRIS Enterprises, Inc.

 Managing Elementary Streams

Custom Groom—Elementary Streams

Managing Elementary Streams

This section explains how to work with individual elementary streams. The following topics are
covered:
• Adding Elementary Streams
• Replacing Grooming Definitions for Elementary Streams
• Deleting Elementary Streams

Adding Elementary Streams

You can add elementary streams associated to a multiplex or previously groomed program. Only
one video stream can be associated with a grooming definition.

To add elementary streams:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.

CAP-1000 Software Guide v4.0 397

Chapter 19 Grooming Elementary Streams Managing Elementary Streams

The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 Expand the Component Tree.
5 In the Input panel, select one or more elementary streams from the Tree and press CTRL.
6 Do one of the following:
• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected streams and drop them on the output mux you want.
• If you selected a specific multiplex for the Output Mux menu, drag the selected streams and
drop them on a groomed program, or in the Drop Input Here area.
7 Release the mouse button.
8 If the streams are added to a previously groomed program, do the following:
9 Select Drop to Primary or Drop to Backup (if configured).

Select Component

a Click OK.
The streams are added to the Grooming Definition panel and the Primary Streams or Backup
Streams panel at the bottom of the window.
10 Click Apply.
11 Click Yes.

398 ARRIS Enterprises, Inc.

 Managing Elementary Streams

Replacing Grooming Definitions for Elementary Streams

You can replace elementary streams associated with a multiplex or previously groomed program.
Only one video stream can be associated with a grooming definition.

To replace grooming definitions:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 Expand the Component Tree.
5 In the Input panel, select one or more elementary streams from the Tree.
6 Do one of the following:
• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected streams and drop them on the output muxes you want.
• If you selected a specific multiplex for the Output Mux menu, drag the selected streams and
drop them on a groomed program, or in the Drop Input Here area.
7 Release the mouse button.
8 Select Drop to Primary or Drop to Backup (if configured).

Select Component

9 Click OK.
10 Click Apply.
11 Click Yes.

CAP-1000 Software Guide v4.0 399

Chapter 19 Grooming Elementary Streams Managing Elementary Streams

Deleting Elementary Streams

To delete an elementary stream:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output panel, click the program you want.

4 Expand the Primary Streams/Backup Streams panel at the bottom of the window.
5 Right-click the stream you want, and then select Delete from the Context menu.

NOTE Example illustrations show the Tabular view.

Delete

6 Click OK.
7 Click Apply.
8 Click Yes.
The stream is deleted from the list of streams in the Primary Streams panel.

IMPORTANT If you delete all streams associated with a groomed program, the groom is removed from output and the
groomed program icon ( ) changes to a program placeholder icon ( ).

400 ARRIS Enterprises, Inc.

 Forcing Custom Grooms

Forcing Custom Grooms

You can groom a stream if the type is unknown and the stream is not included in the input PMT at
input at the time of the grooming. You need only supply the PID for the currently unavailable
stream that is to follow in the grooming operation.

To force a custom groom:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output panel, click the program you want.

4 Expand the Primary Streams/Backup Streams panel at the bottom of the window.
5 Right-click a row and then select Input Stream from the Context menu.

NOTE Example illustrations show the Tabular view.

Add Input Stream

6 In Input PID cell, enter the PID for the stream.

NOTE The 0 indicates that this is an elementary stream that does not exist in the input at the time of grooming.

CAP-1000 Software Guide v4.0 401

Chapter 19 Grooming Elementary Streams Enabling CALM

Add Input PID

7 Click Apply.
8 Click Yes.

Enabling CALM
The CAP-1000 supports volume leveling mandated by/pursuant to the Commercial Advertisement
Loudness Mitigation (CALM) Act FCC regulation by modifying the dialnorm parameters of
groomed AC-3 audio streams. You can edit the Network Dialnorm and DPI Dialnorm values for
each primary and backup AC3 live audio stream. A license is required to use this function.
If no valid license is installed, the dialnorm adjustment fields are disabled in the GUI. In this case,
the CAP-1000 rejects the application of the dialnorm modifications and reports an alarm.

Functions
• Dual mono streams—the CAP-1000 automatically adjusts the dialnorm 2 parameter. The same
adjustment values are applied to both dialnorm and dialnorm2 parameters.
• DPI stream matching—the CAP-1000 uses the DPI dialnorm value configured for the network
stream that is matched, even in the cases where an English ad stream is matched to a network
Spanish stream
• Encrypted streams—The dialnorm function does not apply to encrypted streams groomed in
PASS mode. If an encrypted stream is groomed in GROOM mode, then the dialmode
parameters are applied when the stream becomes clear.

402 ARRIS Enterprises, Inc.

 Enabling CALM

• CherryPicker redundancy (CPR)—All dialnorm settings for the primary CAP-1000 units are
virtualized so the backup CAP-1000 inherits the same settings as the primary units.
• Multiple redundancy (MRED)—The dialnorm settings of the primary AC3 elementary
streams apply to the audio elementary streams of the backup multiplex.
• Program redundancy (PRED)—Backup AC3 audio elementary streams can have different
dialnorm parameters from the primary audio streams for a program. The GUI provides
separate options to set the values for the backup audio stream.
• Analysis—The input dialnorm values of the source audio elementary streams are reported in
the Analysis window (dialnorm2 is ignored).

Limitations
• Dialnorm values cannot be modified when grooming audio files.
• CALM does not apply to file groom with live AC3 audio, including slate with live audio,
primary file grooms with live audio, and backup file grooms with live audio.
• When upgrading a CAP-1000 from a previous software release, the default dialnorm for AC3
output audio streams are set to a null offset for both network and ads.

To enable CALM:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output panel, click the program you want.

4 Select the CALM option.

CAP-1000 Software Guide v4.0 403

Chapter 19 Grooming Elementary Streams Enabling CALM

CALM Option

5 Click Apply.
6 Click Yes.
7 Go the Primary Streams/Backup Steams panel.
8 Select the AC3 live audio stream.
9 In the Network Dialnorm, select the value for the primary/backup audio stream:
• Default value is no change (0)
• Added values are 1 to 31
• Relative values are -1 to +30

NOTE This option does not apply to file grooms with live AC3 audio, including slates with live audio, primary file
grooms with live audio, or backup file grooms with live audio.

10 In the DPI Dialnorm, select the value for the audio stream used in Digital Program Insertion
(DPI), if configured.
See Chapter 24, “Enabling Digital Program Insertion” for more information.

404 ARRIS Enterprises, Inc.

 Enabling CALM

Dialnorm Options

11 Click Apply.
12 Click Yes.

CAP-1000 Software Guide v4.0 405

Chapter 19 Grooming Elementary Streams Enabling CALM

406 ARRIS Enterprises, Inc.

 CHAPTER 20
Grooming Files

In This Chapter
• Files
• Managing Custom Files
• Grooming Files using the Diagram View
• Grooming Files using the Tabular View
• Deleting Groom Definitions
Refer to Chapter 17, “Grooming Concepts” for a review of basic grooming concepts and Chapter
13, “Content Picking”for a review of the Content Picking window components, panels, menus, and
icons.

Files
The CAP-1000 lets you groom standard files provided on the RAM disk or custom audio and
video files that you upload to the Data Flash.

Standard Files
The CAP-1000 provides standard files that you can you to groom to an output program on a DVB-
ASI or a GigE multiplex. These files include PAL and NTSC MPEG-2, and MPEG-4/AVC.
Standard files can only be groomed, they cannot be passed. Standard files are kept on the RAM
disk. They are extracted from the software after a system reboot.
The stream type for the system-provided video and audio files is determined from the file name
suffix. Video files with a suffix of "4AVC" are type AVC (27). All other video files are type
MPEG2 (2). An audio file with a suffix of "ac3" is a type AC3 audio (129), a suffix of "m2a" is
MPEG2 audio (4), and a suffix of "aac" is an AAC audio (15).
The CherryPicker Element Manager displays these files in the “Standard Files” node of the
Component Tree.

CAP-1000 Software Guide v4.0 407

Chapter 20 Grooming Files Files

Standard Files

NOTE The DPI Rule column for files is read-only and set to “Splice” for file-groomed video and audio streams.
The DPI Rule for an extra output stream is read-only and set to “Splice.” See Chapter 24,“Enabling
Digital Program Insertion” for more information.

Video Files
The following MPEG-2 and MPEG-4/AVC black video files of various resolutions and frame rates
are supplied in the CAP-1000 in the directory /usr/cp/video for your use.

Table 20-1 Standard Video Files

black (MPEG-2) black_544x480_29.97i (MPEG-2)

black_1280x720_50p (MPEG-2) black_544x480_29.97i.4AVC (MPEG-4/AVC)

black_1280x720_50p.4AVC (MPEG-4/AVC) black_544x576_25i (MPEG-2)

black_1280x720_59.94p (MPEG-2) black_544x576_25i.4AVC (MPEG-4/AVC)

black_1280x720_59.94p.4AVC (MPEG-4/AVC) black_640x480_59.94p (MPEG-2)

black_1440x1088_25i (MPEG-2) black_704x480_29.97i (MPEG-2)

black_1440x1088_25i.4AVC (MPEG-4/AVC) black_704x480_29.97i.4AVC (MPEG-4/AVC)

black_1440x1088_29.97i (MPEG-2) black_704x576_25i (MPEG-2)

black_1440x1088_29.97i.4AVC (MPEG-4/AVC) black_704x576_25i.4AVC (MPEG-4/AVC)

408 ARRIS Enterprises, Inc.

 Files

Table 20-1 Standard Video Files (continued)

black_1920x1088_25i (MPEG-2) black_720x480_29.97i (MPEG-2)

black_1920x1088_25i.4AVC (MPEG-4/AVC) black_720x480_29.97i.4AVC (MPEG-4/AVC)

black_1920x1088_29.97i (MPEG-2) black_720x576_25i (MPEG-2)

black_1920x1088_29.97i.4AVC (MPEG-4/AVC) black_720x576_25i.4AVC (MPEG-4/AVC)

black_192x192_25i.4AVC (MPEG-4/AVC) black_96x96_25i.4AVC (MPEG-4/AVC)

black_192x192_29.97i.4AVC (MPEG-4/AVC) black_96x96_29.97i.4AVC (MPEG-4/AVC)

black_352x480_29.97i (MPEG-2) black_hd.4AVC (MPEG-4/AVC, resolution 1920x1088)

black_352x480_29.97i.4AVC black_pal.4AVC (MPEG-4/AVC)

black_352x576_25i (MPEG-2) black.4AVC (MPEG-4/AVC)

black_352x576_25i.4AVC black.ntsc (MPEG-2)

black_480x480_29.97i (MPEG-2) black.pal (MPEG-2)

black_480x480_29.97i.4AVC (MPEG-4/AVC) colorbars_pal.4AVC (MPEG-4/AVC)

black_480x576_25i (MPEG-2) colorbars.4AVC (MPEG-4/AVC)

black_480x576_25i.4AVC (MPEG-4/AVC) colorbars.ntsc (MPEG-2)

black_528x480_29.97i (MPEG-2) colorbars.pal (MPEG-2)

black_528x480_29.97i.4AVC (MPEG-4/AVC) black_544x480_29.97i (MPEG-2)

black_528x576_25i (MPEG-2) black_544x480_29.97i.4AVC (MPEG-4/AVC)

black_528x576_25i.4AVC (MPEG-4/AVC) black_544x576_25i (MPEG-2)

black_704x576_25i (MPEG-2) black_544x576_25i.4AVC (MPEG-4/AVC)

black_704x576_25i.4AVC (MPEG-4/AVC) black_640x480_59.94p (MPEG-2)

black_720x480_29.97i (MPEG-2) black_704x480_29.97i (MPEG-2)

black_720x480_29.97i.4AVC (MPEG-4/AVC) black_704x480_29.97i.4AVC (MPEG-4/AVC)

NOTE It is assumed that the vertical resolution in NTSC is 480 and 576 in PAL.

You can use any valid MPEG video file stored on the CAP-1000 RAM disk in the /usr/cp/video
directory. The name of the video file must use only alphanumeric characters and must not contain
spaces. Audio is not groomed when using the “groom to black” feature.

CAP-1000 Software Guide v4.0 409

Chapter 20 Grooming Files Files

Audio Files
The following audio files are placed by default in the CAP-1000 in the directory /usr/cp/audio:
• muted.aac
• muted.ac3
• muted.m2a
• muted.5.1.ac3
You can stream audio stream from live input multiplexes, either from DVB-ASI lines or
multiplexes on a GigE line.

Custom Files
In prior software releases, the CAP-1000 allowed the grooming of individual, elementary video
files to the output programs. In software v4.0, you can now upload elementary stream files,
extracted from Single File Transport Streams (SPTS), via the GUI. The CAP-1000 extracts the
elementary streams and saves them to the Data Flash for subsequent custom file grooming to the
output.
You can groom “custom files” such as a single video file and one or more audio streams (either
from a live multiplex or from a file) to an output program on a DVB-ASI output line or a GigE
multiplex.
When grooming custom files, you can select only one video file. If you select one video file and
then select a different one, the second file replaces the first in the grooming selection. A video file
is required for the program. When a video file is present for grooming, it always appears as the
first file in the GUI. At least one file is required (a file groom must have at least one input file). A
file can only be groomed, not passed.
You can select and groom multiple audio files. Different audio files are allowed in the Selected
Files list. No audio files are required. You can also select audio stream from live input multiplexes,
either from DVB-ASI lines or multiplexes on a GigE line.
The storage of custom files is persistent and survive a system reboot. These files are also copied to
the Backup device when the CAP-1000 is configured for CherryPicker Redundancy (CPR) and
can be used by the Backup device when in “Covering” mode.
To support ETV data streams, you can add extra output stream placeholders in the output program
and add descriptors to any of the output streams. You cannot; however, define descriptors for video
and audio streams groomed from live feeds,
After the files have been uploaded to the CAP-1000, the CherryPicker Element Manager displays
them as “Custom Video Files” and “Custom Audio Files” in the Component Tree.

410 ARRIS Enterprises, Inc.

 Managing Custom Files

Custom Files

Managing Custom Files

You can upload custom files from a client PC. Custom MPEG video files are stored in the
/usr/cp/video/custom directory on the Data Flash. Audio files are placed in the
/usr/cp/audio/custom directory. The name of the custom file must use only alphanumeric
characters and must not contain spaces.

Uploading Custom Files

To upload:
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click Slate Files.

CAP-1000 Software Guide v4.0 411

Chapter 20 Grooming Files Managing Custom Files

Custom Files

3 In the Select File panel, use the icons in the window to navigate to a directory where the custom
files are saved.
4 Under Name, select the file you want.
The file name appears in the File Name field.

NOTE You can filter by file types using the Files of Type menu.

5 Click Import Streams.

The video or audio file is extracted and appears in the Elementary Streams panel.

412 ARRIS Enterprises, Inc.

 Managing Custom Files

Custom File

6 In the Elementary Streams panel, select the stream.

7 Click Upload.
The video or audio file is uploaded to the appropriate directory on the CAP-1000.

CAP-1000 Software Guide v4.0 413

Chapter 20 Grooming Files Managing Custom Files

Custom File

8 From the CherryPicker Element Manager, click Content Picking > Grooming.
9 From View, click .
10 Expand the Component Tree.
11 Expand the Standard Files, Custom Video Files, or Custom Audio Files node.
The file(s) you uploaded is shown in the tree.

414 ARRIS Enterprises, Inc.

 Managing Custom Files

Custom Video File

Deleting Custom Files

You can delete video or audio files stored on the Data Flash to regain space. The total amount of
available space is shown in the Space Available Below Data Flash Alarm Threshold field in the
Custom Files window.
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click Slate Files.
3 In the Device panel, select the video file or audio file you want to delete.
4 Click Delete.
The file is immediately deleted from the Data Flash.

CAP-1000 Software Guide v4.0 415

Chapter 20 Grooming Files Grooming Files using the Diagram View

Grooming Files using the Diagram View

You can groom a file to an output mux, a previously groomed program ( ), or a program
placeholder ( ) created by a configuration file.

To groom a file:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

Output Mux Menu

4 Expand the Component Tree.

5 Expand the Standard Files, Custom Video Files, or Custom Audio Files node.
6 In the Component Tree, select one or more files from the Tree.

416 ARRIS Enterprises, Inc.

 Grooming Files using the Diagram View

Standard File

7 Do one of the following:

• If you selected the All, All SPTS Muxes, or All MPTS Muxes option from the Output Mux
menu, drag the selected file(s) and drop it on a program placeholder or a groomed program for
the output mux(es) you want.

CAP-1000 Software Guide v4.0 417

Chapter 20 Grooming Files Grooming Files using the Diagram View

Drag and Drop to Output Mux

• If you selected a specific multiplex for the Output Mux menu, drag the selected file(s) and
drop it on a program placeholder, a groomed program, or in the Drop Input Here area.

Drop Input Here

418 ARRIS Enterprises, Inc.

 Grooming Files using the Tabular View

8 Release the mouse button.

The file(s) is added to the Grooming Definitions panel and Primary Streams/Backup Streams panel
at the bottom of the window.
9 Click Apply.
10 Click Yes.

Grooming Files using the Tabular View

You can groom a file to an output mux, a previously groomed program ( ), or a program
placeholder ( ) created by a configuration file.

To groom a file:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differ depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

CAP-1000 Software Guide v4.0 419

Chapter 20 Grooming Files Grooming Files using the Tabular View

Output Mux Menu

4 Expand the Component Tree.

5 Expand the Standard Files, Custom Video Files, or Custom Audio Files node.
6 In the Input panel, select one or more files from the Tree.

420 ARRIS Enterprises, Inc.

 Grooming Files using the Tabular View

Custom File

7 Do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected file(s) and drop it on the output mux you want.

CAP-1000 Software Guide v4.0 421

Chapter 20 Grooming Files Grooming Files using the Tabular View

Drag and Drop to Output Mux

• If you selected a specific multiplex for the Output Mux menu, drag the selected file(s) and
drop it on a program placeholder, a groomed program, or in the Drop Input Here area.

NOTE If you added the programs to a previously groomed program, the Select Component window opens. To
replace the program, go to section,“Replacing Grooming Definitions for Elementary Streams,”on
page 399. To groom a backup program, go to Chapter 29, “Configuring Program Redundancy”. To
groom a slate, go to section,“Configuring Slates (Second-level Backup),”on page 603.

422 ARRIS Enterprises, Inc.

 Grooming Files using the Tabular View

Drop Input Here

a Click Apply.
b Click Yes.
The custom file appears in the Output panel.

Custom File Groom

CAP-1000 Software Guide v4.0 423

Chapter 20 Grooming Files Deleting Groom Definitions

Deleting Groom Definitions

To delete a groom definition:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
4 Do one of the following:
• In the Output panel, select the Standard File, Custom Video File, or Custom Audio File you
want. Expand the Primary Streams/Backup Streams panel at the bottom of the window. Right-
click the file you want and select Delete from the Context menu.
• In the Output panel, select the Standard File, Custom Video File, or Custom Audio File you
want. Right-click the file you want and select Delete Groom Definition from the Context
menu.

NOTE Example illustrations show the Diagram view.

Delete Standard Grooms

5 Click Apply.
6 Click Yes.

424 ARRIS Enterprises, Inc.

 CHAPTER 21
Using Trigger Events

In This Chapter
• Trigger Events
• Managing Trigger Events
• Applying Trigger Events
• Applying Multiple Trigger Events with Levels
• Viewing Upcoming Events
• Viewing Action Definitions Associated with Events
• Removing Trigger Events
• Managing Missed Events
Refer to Chapter 17, “Grooming Concepts” for a review of basic grooming concepts and Chapter
13, “Content Picking”for a review of the Content Picking window components, panels, menus, and
icons.

Trigger Events
The CAP-1000 provides support for trigger events in grooming operations. A scheduled event is a
time-based event generated as a single or reoccurring event. Clicking Triggers displays the
Triggers window which lets you perform the following tasks:
• Create, delete or update trigger events
• View upcoming event instances
• View action definitions associated with each event
• Import triggers from a file
• Export triggers to a file
The use of scheduled triggers (based on time), including recurring events, is supported for
program, custom, and file grooming.

CAP-1000 Software Guide v4.0 425

Chapter 21 Using Trigger Events Trigger Events

Triggers

To use a trigger in a groom, you must create the trigger before it can be applied to the groom.
Triggers are applied in the Content Picking > Grooming window when you create a groom.

Grooming

426 ARRIS Enterprises, Inc.

 Managing Trigger Events

Trigger Events
By default, the CAP-1000 assigns a unique ID to the trigger event. You can assign a unique ID and
a description for the trigger event in the Triggers tab. The ID is the mechanism used to associate a
trigger event with an action at a later time. Before an unexpired event definition can be deleted, a
check is made to ensure that it is not the last event associated with an action. If it is, you can delete
it or the remove the trigger event from the groom.

Recurring Events
A recurring event is a special type of event that defines rules to generate events on a periodic basis
(time). You can define the recurring period. The period is expressed in units of minute, day, week,
and month as follows:
• Minute allows for “every N” minutes.
• Day allows for “every N” days or “every weekday.”
• Week allows for “every N” weeks on a selection of specific “days of the week.”
• Month allows for “every N” months or selection of specific “months of the year.”
All recurring periods begin from the defined initial start time. No events are generated for periods
computed prior to the system time when the definition is recorded. No events are generated for
missed periods due to the Controller not running.

Missed Events
You can use different methods to work through a missed event. One method is to use the “Test”
button for the event definition. If the button is activated, an emulated event with the same ID as the
event definition is generated. Another method is to enable a manual trigger when defining a
groom.

Managing Trigger Events

Creating Trigger Events

To create a trigger event:
1 From the CherryPicker Element Manager, click Triggers.

CAP-1000 Software Guide v4.0 427

Chapter 21 Using Trigger Events Managing Trigger Events

Triggers

Table 21-1 Triggers

Triggering Event Definitions Displays the events for a groom.

Event Definition Icons Provides icons for managing event definitions.

Creates an event definition.

Deletes an event definition.

Tests an event definition.

Edit Status Icons Displays an icon that represents the status of an edited event:

Event has been modified, but modifications have not been applied.

Event has been marked for deletion, but the deletion has not been applied.

Event has been added, but the addition has not been applied.

Empty No changes made.

ID System-supplied default for this event: New Trigger1. Only editable during event
creation.

Description User-supplied description for this event.

Start Date/Time Specifies the start date and time for the event.

428 ARRIS Enterprises, Inc.

 Managing Trigger Events

Table 21-1 Triggers (continued)

Ending Condition Specifies how the event should end. The options are:
• Until Date/Time—Specifies the end date and time for this event.
• Repeat N Times—Specifies the number of times to repeat this event. The range
is 1- 999.
• None (Forever)—Repeats this event until conditions for ending it according to
the groom are met, such as another groom event.

Recurrence Specifies the type of recurrence for the event. The options are: Minute, Day, Week,
or Month. When the information is too long to fit in a cell, a tool tip is provided
when the mouse cursor moves over the cell.

Action Count Shows the number of actions associated with the event.

Expired When checked, indicates the event has expired. Read-only.

Associated Actions Displays action definitions associated with selected trigger events. These
definitions are created from grooms. To display the Associated Actions, select a
Trigger Event Definition with an Action in the Triggers tab.

ID Shows the action definition ID from the groom.

Type Shows the type of action.

Duration Shows the duration for this action definition specified in the groom.

Target Shows the line (port), multiplex, and program for which this action is defined.

Preview Shows next ten occurrences of selected trigger event from event table. It is
automatically updated whenever you change the recurring conditions.

2 In the icon bar, click Create ( ).

A new trigger is added to the Triggering Event Definition table.
3 Enter a Description for this event.
4 Select a Start Date/Time for this event and then click OK.

CAP-1000 Software Guide v4.0 429

Chapter 21 Using Trigger Events Managing Trigger Events

Enter Date and Time

5 In the Ending Condition menu, do one of the following:

• Select Until Date and Time and select the ending date and time for this event and then click
OK.

Enter Date and Time

• Select Repeat N Times and enter the number of times to repeat this event and then click OK.

Repeat N Times

430 ARRIS Enterprises, Inc.

 Managing Trigger Events

• Choose None to repeat this event until conditions for ending it according to the groom are met,
such as another groom event, and then click OK.
6 In the Recurrence menu, select one of the following options:
• Select Minute, enter the minutes by which the event recurs, and click OK.

Input

• Select Day, select the day(s) by which the event recurs, and click OK.

Day Type Options

• Select Week, select the week(s) by which the event recurs, and click OK.

Week Type Options

• Select Month and do one of the following:

aSelect Recur Month and enter the number of months over which the event recurs.
bSelect Recur On and choose the specific months on which the event recurs.

CAP-1000 Software Guide v4.0 431

Chapter 21 Using Trigger Events Managing Trigger Events

cClick OK.

Month Type Options

Your selection shows in the Recurrence cell.

7 Click Apply.

Modifying Trigger Events

To modify a trigger event:
1 From the CherryPicker Element Manager, click Triggers.
2 In the Triggering Event Definitions panel, select the trigger you want.
3 Change the parameter you want.
4 Click Apply.
5 Click OK.

Deleting Trigger Events

To delete a trigger event:

1 From the CherryPicker Element Manager, click Triggers.
2 In the Event Triggering Definitions panel, select the event you want to delete.
3 In the icon bar, click Create ( ).
4 Click Yes.
5 Click OK.

432 ARRIS Enterprises, Inc.

 Applying Trigger Events

Applying Trigger Events

To apply a trigger event:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Groom a program or elementary stream.

See Chapter 18, “Grooming Programs” or Chapter 19, “Grooming Elementary Streams” for more
information.
4 In the Grooming Definitions panel, select the grooming definition you want.
5 Select the Use Trigger option.
6 Select the Triggers cell.

Select Triggers

7 Select the trigger(s) to apply to this grooming definition.

8 Click OK.
The trigger is associated with the grooming definition.

CAP-1000 Software Guide v4.0 433

Chapter 21 Using Trigger Events Applying Multiple Trigger Events with Levels

Grooming with a Trigger

9 Click Apply.
10 Click Yes.

Applying Multiple Trigger Events with Levels

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Groom a program or elementary stream.

See Chapter 18, “Grooming Programs” or Chapter 19, “Grooming Elementary Streams” for more
information.
4 In the Grooming Definitions panel, select the grooming definition you want.
5 In the Content menu, select Add Grooming Definition.
6 Select the Use Trigger option.
7 Select the Triggers cell.

434 ARRIS Enterprises, Inc.

 Applying Multiple Trigger Events with Levels

Select Triggers

8 Select the trigger(s) to apply to this grooming definition.

9 Click OK.
The trigger is associated with the grooming definition. The CAP-1000 automatically assigns a
trigger Level to the grooming definition.

Grooming with Triggers

NOTE Refer to the Duration column. When the action is triggered, this column identifies how long the groom will
play. It defaults to forever, but can be limited by time.

10 Click Apply.
11 Click Yes

CAP-1000 Software Guide v4.0 435

Chapter 21 Using Trigger Events Viewing Upcoming Events

Viewing Upcoming Events

You can view upcoming events selecting an event from table. The Preview pane displays
timestamps for up to the next 10 occurrences of the event.
1 From the CherryPicker Element Manager, click Triggers.
2 In the Triggering Event Definitions panel, select the trigger you want.
The upcoming events show in the Preview panel.

Preview

Viewing Action Definitions Associated with Events

To view action definitions associated with events, select an event from table. The action table
automatically refreshes to indicate the associated action definitions.
1 From the CherryPicker Element Manager, click Triggers.
2 In the Triggering Event Definitions panel, select the trigger you want.
The associated action shows in the Associated Actions panel.

436 ARRIS Enterprises, Inc.

 Removing Trigger Events

Associated Actions

Removing Trigger Events

To remove a trigger event:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Grooming Definitions panel, select the grooming definition you want.
4 Clear the Use Trigger option.
5 Click Apply.
6 Click Yes.

Managing Missed Events

You can use different methods to work through a missed event. One method is to use the “Test”
button for the event definition. If the button is activated, an emulated event with the same ID as the
event definition is generated. Another method is to enable a manual trigger when defining a
groom.

Testing Trigger Events

At least one action must be associated with an event to test it. You can, however, use the Preview
pane to determine when up to the next 10 occurrences of the event will be generated. Refer to
section,“Viewing Upcoming Events,”on page 436 for more information.

CAP-1000 Software Guide v4.0 437

Chapter 21 Using Trigger Events Managing Missed Events

To test a trigger event:

1 From the CherryPicker Element Manager, click Triggers.
2 In the Triggering Event Definitions panel, select the event you want to test.

Test

The event must have an Action Count of 1 or greater to test the event.
3 In the icon bar, click Test ( ).
Clicking this button sends a request to the Controller to simulate real event. You can view the
grooms that were activated by the simulated event in the grooming Views.

438 ARRIS Enterprises, Inc.

 Managing Missed Events

Timeline View of Event Test

Manually Triggering Events

To manually trigger an event:

1 From the CherryPicker Element Manager, click Triggers.
1 Create the triggering event.
Go to section,“Creating Trigger Events,”on page 427 for information.
2 From the CherryPicker Element Manager, click Content Picking > Grooming.
3 Groom a program.
4 Groom a program or elementary stream.
See Chapter 18, “Grooming Programs” or Chapter 19, “Grooming Elementary Streams” for more
information.
5 In the Grooming Definitions panel, select the grooming definition you want.
6 Double-click the Triggers cell.

CAP-1000 Software Guide v4.0 439

Chapter 21 Using Trigger Events Managing Missed Events

Select Triggers

7 Select Allow Manual Trigger Operation to enable manual triggering of the event.
8 Click OK.
The trigger is associated with the grooming definition.
9 Click Apply.
10 Click Yes.
11 In the Grooming Definitions panel, right-click the grooming definition.
12 Select Manual Trigger.

Manual Trigger

440 ARRIS Enterprises, Inc.

 CHAPTER 22
Configuring Rate Shaping, Stat Mux
Pools, and Recoders
In This Chapter
• Overview
• Enabling Rate Shaping
• Managing Stat Mux Pools
• Managing Recoders
• Reserving Recoders
• Dropping Recoders
• Managing Clusters
• Missing Recoders
• Auditing Recoders

Overview
Rate shaping is the process of changing or altering the bit rate of the service to a lower bit rate to
squeeze more programs and/or services into the available bandwidth. Rate shaping is supported for
the following CAP-1000 components:
• Single Program Transport Stream (SPTS) and Multi-program Transport Stream (MPTS)
multiplexes
• Stat Mux Pools (SMP)
• MPEG-2 TS packetized elementary video stream
• MPEG-4/Advanced Video Coding (AVC) TS packetized elementary video stream
Rate shaping in the CAP-1000 is achieved through the use of recoders. Recoding resources are
supplied by the DSP module. The CAP-1000 can recode groomed MPEG-4/AVC, MPEG-2 SD,
and MPEG-2 HD video streams to meet the given constraints on the output rate of a video stream,
a program, or an output multiplex. Moreover, since software release 3.1, MPEG-2 rate shaping has
been improved by allowing Macroblock-based quantizer scale selection.

CAP-1000 Software Guide v4.0 441

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Enabling Rate Shaping

Enabling Rate Shaping

You can configure the GigE output multiplex to take advantage of the CAP-1000’s ability to
process elementary input streams to change the bit rate. To enable rate shaping of all groomed
elementary streams on a given output mux, rather than for a single program, you configure the
“rate-shape” parameters in the Create Output Multiplex (Basic) dialog.

Create Output Multiplex (Basic)—Rate-shape Parameters

NOTE For backward compatibility, when upgrading from a previous software version which only supports the
Total Rate, the setting is changed to Custom, the Reserved Rate is set to 0, and the Available Rate equals the
total rate.

The parameters for configuring a rate-shaped GigE multiplex are defined in Table 22-1.

442 ARRIS Enterprises, Inc.

 Enabling Rate Shaping

Table 22-1 GigE Output Mux Modes

Total Rate (Mbps)

Mode Range Default Default Total Reserved Rate (Mbps)

QAM64 (6 MHz) 26.97035 26.97035 0.5

QAM256 (6 MHz) 38.81070 38.81070 0.8107

QAM64 (8 MHz) 38.44047 38.44047 0.7

QAM256 (8 MHz) 51.25396 51.25396 1.0

ATSC 19.392658 19.392658 0.1

Custom 0.5425 - 1000 20.0 0.1

If you select the 64 QAM (6MHz), 256 QAM (6MHz), 64 QAM (8MHz), or 256 QAM (8MHz)
Mode, the Total Rate (Mbps) and Res Rate (Mbps) parameters are automatically calculated for
you. If you select the Custom Mode, enter the Total Rate and Res Rate parameters according to
those listed in Table 22-1.

To enable rate shaping on GigE output multiplexes:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Click Create Output Mux.
The Create Output Mux dialog opens with the Basic tab selected.

CAP-1000 Software Guide v4.0 443

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Enabling Rate Shaping

Create Output Multiplex (Basic)

3 To create multiple rate-shaped output multiplexes, do the following:

a Under UDP Connection, select Multicast.
b Select Bulk Option.
c Select End Port or Last Octet (End IP) and enter the value you want.
d To configure the transport stream ID, do one of the following:
• To increment the transport stream ID on the next multiplex by 1, select Transport Stream
ID Increment.
• To specify the transport stream ID you want, enter the MPEG Transport Stream ID for
this multiplex.
• To use the transport stream ID from the configuration file, select Use Config File TSID.

444 ARRIS Enterprises, Inc.

 Managing Stat Mux Pools

4 To configure Padding, do one of the following:

• To enable padding, select Null Packet. This option ensures that streams are encoded at a set
bit rate regardless of the amount of information that needs to be stored. If there is not enough
video information to fill the allotted bandwidth, the encoder simply fills the rest of the stream
with null packets.
• To disable padding, select None. Variable bit rate streams do not use null packets to fill the
stream to a constant bit rate.
5 Select the Mode you want. Select one of the following:
• 64 QAM (6 MHz)
• 256 QAM (6 MHz)
• 64 QAM (8 MHz)
• 256 QAM (8 MHz)
• Custom
See Table 22-1 on page 443 for more information.
Selecting one of these options affects the Total Rate and Reserved Rate parameters.
6 If you selected Custom for the Mode option, set the Total Rate and Reserved Rate you want.
7 Configure any other parameters you want.
8 See section,“Creating Gigabit Ethernet Output Multiplexes,”on page 254 for more information.
9 Click OK.

Managing Stat Mux Pools

The CAP-1000 allows you to group several output programs in a GigE or ASI output multiplex
and set a maximum total bit rate for the group as a whole. This group of output programs is
referred to as a stat mux pool (SMP). These pools facilitate content distribution from a central
headend to hubs where multiple transport streams can be distributed using one physical output
channel. SMPs use the same multicast UDP connection.
Every program in a stat mux pool can only belong to one stat mux pool. The same program cannot
belong to two different pools simultaneously. All programs within the same PID shared program
pool must belong to the same SMP. Once created, you can groom programs to the output program
associated with the stat mux pool.

CAP-1000 Software Guide v4.0 445

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Stat Mux Pools

Stat Mux Pool Rates

The total rate of a SMP includes the rates of all the elementary streams in the pool. The following
streams are not included in the total rate:
• PSI stream defined in the basic MPEG standard (PAT, PMT, CAT, NIT, and TSDT)
• SI streams defined in the DVB standard (SDT, EIT, TDT, BAT, RST, TOT, ST)
• Additional PSIP streams (STT, MGT, CVCT, RRT, EIT, ETT)
The total output reserved rate may not exceed the difference between the total multiplex rate and
the sum of the pool maximum total rates.
You must specify a rate when a pool is created. The default value for the total rate is 20 and
reserved rate is 0.1. When a pool rate is first specified or modified, the software checks the total of
all pool rates to make sure that this sum does not exceed the total available rate for this multiplex.
You can modify the rates at any time. Modifying the pool rate could cause service interruption in
another pool belonging to the same multiplex. However, no service interruption occurs in pools
belonging to a different multiplex.
The total rate in one pool may be different form the total rates in other pools in the same multiplex.
Changing the maximum rate value set for one pool does not affect settings for the rates in other
pools.

Stat Mux Pool Maximums

A maximum of eight pools can be created per multiplex. The total number of SMPs per CAP-1000
device is 256.

Stat Mux Pool Names

The pool name is mandatory. If you do not assign the name, the software automatically creates a
name for the pool. The name of a pool must be different from the name of any other pool or any
program in the multiplex where the pool is created. The default name for the pool is:
<mux_name>_Pool_<#> where mux_name is the name of the multiplex in which the pool resides
and # is the SMP index in that multiplex.

Creating Stat Mux Pools

To create a stat mux pool:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the GigE or ASI output multiplex you want.

NOTE Illustrations in this example show a GigE output multiplex.

446 ARRIS Enterprises, Inc.

 Managing Stat Mux Pools

4 In the GigE Input Muxes panel, select the multiplex ID under the ID column.
5 Select Create Stat Mux Pool from the pop-up Context menu.

Mux

A warning message opens.

6 Click Yes.
The SMP is added to the lower panel.

CAP-1000 Software Guide v4.0 447

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Stat Mux Pools

Stat Mux Pool

Table 22-2 Stat Mux Pool Parameters

ID Shows the ID assigned to the stat mux pool.

Name Enter a name for the stat mux pool. Default name is <mux_name>_Pool_<#>.

Mode Select one of the following:

• 64 QAM (6 MHz)
• 256 QAM (6 MHz)
• 64 QAM (8 MHz)
• 256 QAM (8 MHz)
• Custom
Note: Selecting one of these options affects the Total Rate and Reserved
Rate parameters.

Total Rate (Mbps) • If you select 64 QAM (6 MHz) mode, the Total Rate is 26.9705.
• If you select 64 QAM (8 MHz) mode, the Total Rate is 38.4407.
• If you select 256 QAM (6 MHz) mode, the Total Rate is 38.8107.
• If you select 256 QAM (8 MHz) mode, the Total Rate is 55.25316.
• If you select ATSC mode, the Total Rate is 19.392658.
• If using Custom Mode, enter the maximum total bit rate for the SMP.

448 ARRIS Enterprises, Inc.

 Managing Stat Mux Pools

Table 22-2 Stat Mux Pool Parameters (continued)

Reserved Rate (Mbps) • If you select 64 QAM (6 MHz) mode, the Reserved Rate is 0.5.
• If you select 64 QAM (8 MHz) mode, the Reserved Rate is 0.7.
• If you select 256 QAM (6 MHz) mode, the Reserved Rate is 0.8107.
• If you select 256 QAM (8 MHz) mode, the Reserved Rate is 1.
• If you select ATSC mode, the Reserved Rate is 0.1
• If using Custom Mode, enter an overhead bit rate for SI and PSI tables that
may be added downstream.

Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this
option.
See Chapter 25, “Enabling Emergency Alert Messaging,” for
more information.

State Code Selects a state code. Configures Federal Information Processing Standard
(FIPS) location codes for the Emergency Alert System (EAS).

Country Sub Division Selects a county sub-division.

County Code Selects a county code.

7 In the Stat Mux Pool panel, do the following:

a Modify the Name, if required.
b Modify the Total Rate (Mbps) and Reserved Rate (Mbps) parameters.
8 Configure any other parameters you want.
9 Click Apply.
The SMP is added to the Component Tree.

CAP-1000 Software Guide v4.0 449

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Stat Mux Pools

Stat Mux Pool

Modifying Stat Mux Pools

You may add or delete programs in a SMP as follows:
• When a new program is created, it can be assigned to an already existing pool.
• A program can be groomed to a program placeholder already existing in a pool.
• A groomed program in a pool can be dropped.
• A program in a pool can be deleted. The deleted program is removed from the output
multiplex.

To modify a stat mux pool:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the output multiplex you want.
4 In the GigE Input Muxes panel, select the multiplex you want.
5 In the Stat Mux Pool panel, select the SMP you want.
6 Modify the Name. Total Rate (Mbps), or Reserved Rate (Mbps) parameters.
7 Modify any other parameters you want.
8 Click Apply.

450 ARRIS Enterprises, Inc.

 Managing Recoders

Deleting Stat Mux Pools

When an SMP is deleted, all the programs in that pool are deleted.

To delete a stat mux pool:

1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the output multiplex you want.
4 In the GigE Input Muxes panel, select the multiplex you want.
5 In the Stat Mux Pool panel, select the SMP you want.
6 Select Delete from the pop-up Context menu.
If the SMP contains passed PIDs, the Select Stat Mux Pool Delete Preference window opens.
7 To preserve the passed streams, select the Preserve Pass PIDS option.
8 Click OK.
9 Click Apply.

Managing Recoders
An MPEG-2 recoder (a combination of hardware and software) is capable of rate shaping one
standard definition (SD) MPEG-2 video stream. High Definition (HD) MPEG-2 video streams
require four recoders. Assigning one HD MPEG-2 stream removes four SD recoders from the pool
of available recoders.
An MPEG-4 recoder (also a combination of hardware and software) is capable of rate shaping one
SD or HD MPEG-4/AVC video stream. There is no differentiation between SD or HD for
MPEG-4/AVC, like there is with MPEG-2. Assigning one MPEG-4 recoder removes 16 recoders
from the pool of available recoders.
The CAP-1000 can recode groomed MPEG-4/AVC, MPEG-2 SD, and MPEG-2 HD video streams
to meet the given constraints on the output bit rate of a video stream, a program, or an output
multiplex.

Licenses
Use of a recoder requires a license. The recoding resource assignment is based on license
availability and resource availability. When temporary recoding licenses expire, the programs are
handled as follows:
• For MPEG-2, the recoder is dropped and the SD/HD programs are dropped or ungroomed.
• For MPEG-4, the recoder is dropped, but the programs are still groomed.
See Chapter 8, “Managing Licenses,” for more information.

CAP-1000 Software Guide v4.0 451

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Recoders

Recoding Resource Reservation for Programs with MPEG-2 SD or HD Video

Recoders are not required for MPEG-2 services. The CAP-1000 automatically assigns MPEG-2
recoders if available. The CAP-1000 supports a maximum of 384 MPEG-2 recoders. These 384
MPEG-2 recoders can support 384 MPEG-2 SD video streams, or 96 MPEG-2 HD video streams.
For MPEG-2 SD or HD streams recoding, resources are automatically assigned using the
following rules:
• Automatic recoder assignment applies to MPEG-2 MP@ML or MPEG-2 MP@HL streams,
for both CBR and VBR, and does not affect the maximum number of MPEG-2 streams that
can be processed by the CAP-1000 (384 SD / 96 HD).
• Automatic recoder assignment does not apply to low-delay streams, passed streams (clear or
encrypted), file grooming, 4:2:2 profile streams, half-horizontal resolution streams (below 352
pixels), or streams with low-video bit rate (less than or equal to 1 Mbps). This includes
MusicChoice streams.
• Recoding resources are not automatically assigned to any passed streams (clear or encrypted),
or video profiles other than 4:2:0. When streams are passed, if an incorrect recoder type is
detected (MPEG-4 recoder assigned and input stream is MPEG-2). If there is no conflict, the
existing recoder is retained. For profile 4:2:2, the existing recoder is also retained.
• When streams are encrypted and require recoding resources (which may later become clear),
you must select a recoding option: MPEG-2 SD/HD or MPEG-4.
• A dynamic input change (i.e., IRD switches from MPEG-2 to MPEG-4) raises an alarm.
• When applying an output configuration file or DI grooming command, the recoder assignment
contained in the PMT will be followed. If there are no recoding licenses or resources available,
the grooming command in the configuration file is dropped.

Recoding Resource Reservation for Programs with MPEG-4/AVC SD or HD

Video
The MPEG-4/AVC stream type must be Main Profile, Level 1 to 4 (see Annex A of ISO/IEC
14496-10). Context-adaptive binary arithmetic coding (CABAC) and input and output and
Context-adaptive variable-length coding input only are supported. Constant bit rate (CBR) and
variable bit rate (VBR) video streams are supported.
For MPEG-4/AVC streams SD or HD streams recoding resources are assigned using the following
rules:
• You have the option to designate each output program video as either recodable, by assigning
HD MPEG-4/AVC resources, or non-recodable, by assigning No Recoder. This designation
applies only to the video stream in this program. The same HD MPEG-4 AVC recoder type is
assigned for MPEG-4 SD or HD stream.
• If the program is designated as recodable, a recoding resource is reserved and assigned to the
video stream of this program. Otherwise, the video stream bypasses the recoding resource.

452 ARRIS Enterprises, Inc.

 Managing Recoders

NOTE Recoding resource reservation is done when a program is created or groomed, and can be later modified by
changing the resource assignment.

• When a program has a recoding resource type that does not match the video stream type or no
recoder is assigned, the CAP-1000 automatically assigns the proper recoder type for the
MPEG-4/AVC video stream type and profile (HD or SD).

NOTE Grooming without a video elementary stream does not automatically assign a recoder to the program.
Grooming from a file does not automatically assign a recoder to the program.

Audio Streams
Audio streams (MPEG, Dolby Digital, Dolby Digital Plus, AAC, or HEAAC) and other non-video
elementary streams cannot be recoded.

Default Setting for Recoding

The default recoding setting is No Recoder. When a program is created by means of grooming to
the output mux, then a recoder is automatically assigned.

Program Recoding Priority

You can set a recoding-related attribute during a groom. The degree of recoding for a recodable
video stream is determined by the priory level. The priority levels characterize the relative amount
of recoding that will be done for various video streams in a multiplex and is used to control the rate
of the multiplex.
Ten priority levels are defined, with level 1 indicating the lowest priority stream (maximum
amount of recoding) and level 10 indicating the highest priority stream (minimum amount of
recoding), with increments of 1. The default recoding priority level is set to 5 (medium priority).
You can modify the priority levels at any time, even after a program is created and a stream is
being passed to the output. When the recoder is assigned to the output program, the recoding
priority is a property of the groom.

Option Not to Recode

You have the option to select the Do Not Recode parameter for a recodable video stream. This is
priority level 11. The stream will not pass through a recoding resource and the quant tables will not
be changed. You can modify the Do Not Recode parameter at any time, even after a program is
created and a stream is being passed to the output.

CAP-1000 Software Guide v4.0 453

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Recoders

Rate Setting for Video

The degree of video recoding can also be controlled by setting the target minimum and maximum
rates. The CAP-1000 will maintain the rate of the video between these two limits. Note that the
maximum or minimum rate will be maintained only if the input video rate is above the
corresponding maximum or minimum rate. You can modify the minimum and maximum rate
settings at any time. No service interruption will occur due to the modification of these settings.

NOTE Rate setting is a groom-specific property. It can vary based on the active groom.

Default Rate Level

The default levels for the video rate is as follows:
• minimum rate = 0.5425 Mbps
• maximum rate = 20Mbps
You can modify these rates from 0.5425 up to 60 Mbps.

Rate Setting for Outputs

The CAP-1000 maintains the target output rate for each output multiplex at the total available rate
for that line. The software will add null packets, as needed, to maintain the specified output
multiplex rate. The target rate for an output multiplex will override the target rates defined for
video streams in this output.

Reserving, Releasing, or Dropping Recoders

If the program is designated as recodable, a recoding resource is reserved and assigned to the video
stream for the program; otherwise, the video stream bypasses the recoding resource. Recoding
resource assignment is specified when a program is created. You can change the recoder option at
a later time, if required.
You can also remove recoding resources from their designated output program by changing the
resource assignment to the No Recoder option. In doing so, the groom is dropped and then re-
groomed.
If a recoder type is changed, the groom is dropped then regroomed (not just removed). You can
remove the recoding resource from the designated output program by changing the resource
assignment to No Recoder.
A recoding resource associated with an output program is automatically released when the
program is deleted. When a recoding resource is released, the associated license is also released.
If any ad server is connected to this program, the connection is lost and re-established after some
variable duration (depending on the ad server's manufacturer).
Dropping a groom does not remove the recoders that were automatically assigned, only deleting
the program will drop them.

454 ARRIS Enterprises, Inc.

 Managing Recoders

Software Upgrades
During upgrades from previous software versions, existing grooms without recoding resources
will behave the same as before the update.

Changing Video Stream Types

When there is a video stream type change reported in the PMT, (MPEG-2 to MPEG-4 or SD/HD
changes on the same video type), the recoder assignment will not change, This ensures that, when
the input program comes back to its original type, the video service is restored.

NOTE There will be an alarm when the video stream type does not match the recoder type.

Missing Recoders
The CAP-1000 issues a warning message if a groomed program needs a recoder and a recoder is not
assigned. See for section,“Missing Recoders,”on page 466 more information.

Recoder Limitations
Recoder resource usage is not shared across all chips. If a resource is not used on one chip, it
cannot be cumulatively added to other available resources on other chips. For example, if you use
two resources on one chip (out of four total) and two resources on another chip (out of four total),
you cannot add the remaining four resources together to enable one HD recoder. You can enable
only four SD recoders.
Table 22-3 shows of the number of programs that can be groomed or recoded per CAP-1000
device.

Table 22-3 Recoded Program Limitations per CAP-1000

Video Stream Type Recoders per Device Grooming With Recoder per Device Grooming without Recoder per
(4xDSP Module) (4xDSP Module) Device (CPU Module and 4xDSP
Module)

MPEG-2 HD 96 96 rate-shaped programs. 96 programs.

MPEG-2 SD 384 • 384 rate-shaped programs with PRED • 384 programs without PRED, DPI, or
including 230 of them with DPI (77 rate-shaping.
simultaneous). • 256 programs with PRED and DPI.
• 384 without PRED and DPI.

MPEG-2-PIP (Picture in 384 384 rate-shaped programs with PRED • 384 program without PRED, DPI, or
Picture) including 230 programs with DPI (77 rate-shaping.
simultaneous).
• 256 programs with PRED and DPI.
384 without PRED and DPI.

CAP-1000 Software Guide v4.0 455

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Recoders

Table 22-3 Recoded Program Limitations per CAP-1000 (continued)

MPEG-4/AVC HD 16 16 rate-shaped programs with PRED and 192 programs.

DPI.

MPEG-4/AVC SD 16 (uses HD recoder) 16 rate-shaped programs (using an HD • 384 programs without PRED, DPI, or
recoder) with PRED and DPI. rate-shaping.
• 256 programs with PRED and DPI.

MPEG-4/AVC-PIP 16 16 rate-shaped programs with PRED and • 384 programs without PRED, DPI, or
DPI. rate-shaping.
• 256 programs with PRED and DPI.

IMPORTANT These resources are exclusive, not cumulative. For example, if 16 MPEG-4/AVC steams are recoded, then
no other stream can be recoded on the device. If 96 MPEG-2 HD streams are groomed, then no other
grooming can occur.

Recoding and Digital Program Insertion

To ensure seamless splicing of output programs during DPI, you must assign recoders to all output
programs on the output multiplex. Failure to do so can result in rate clamping on the entire output
multiplex, underflows on output programs, and DPI failure. See Chapter 24, “Enabling Digital
Program Insertion” for more information.

Recoder Efficiency
Recoder efficiency is reported in terms of the following:
• Lossy reduction—This reduction signifies the actual reduction in picture. For example, the
size of the original picture size minus recoded picture size (after removal of bit stuffing).
• Lossless reduction—This reduction reports the percentage of stuffing bits removed by the
recoder.
Refer to Chapter 34, “Analyzing Streams and Programs,”for more information.

456 ARRIS Enterprises, Inc.

 Reserving Recoders

Reserving Recoders
This section explains how to reserve recoders using the Diagram view, the Tabular view, or the
Programs panel in the Content Picking window.

Reserving Recoders in Diagram View

To reserve a recoder:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Navigation Tree, select the output multiplex you want.
4 In the Output panel, select the output program you want.
5 In the Context menu, select Set Recoder.

NOTE Example illustrations show the Diagram view.

Grooming Diagram View

CAP-1000 Software Guide v4.0 457

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Reserving Recoders

6 Select the recoder option you want. The recoder options are:
• MPEG-2 SD
• MPEG-2 HD
• MPEG-4/AVC HD
• None
The default recoding option is None (recoder not reserved). If the program is designated as
recodable, a recoding resource is reserved and assigned to the video stream for the program.
Otherwise, the video stream bypasses the recoding resource. Recoding resource reservation is
assigned when a program is created and can be modified by changing the resource assignment.
Audio streams (MPEG, Dolby Digital, or AAC) and other non-video elementary streams cannot be
recoded.

Grooming Diagram View

7 In the Recoding section of the Properties panel, do the following:

a Select the Min Video Bit Rate (Mbps)—The video bit rate floor that the CAP-1000 is not to
drop below when recoding video streams.
b Select the Max Video Bit Rate (Mbps)—The video bit rate ceiling that the CAP-1000 is not
to go above when recoding video streams.

458 ARRIS Enterprises, Inc.

 Reserving Recoders

c Select the Priority for recording the output program:

Level 1 indicates the lowest priority stream (maximum amount of recoding) and Level 10
indicating the highest priority stream (minimum amount of recoding), with increments of 1.
The priory levels can be modified at any time, even after a program is created and a stream is
being passed to the output.
8 Click Apply.
9 Click Yes.

Reserving Recoders in Tabular View

To reserve a recoder:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Navigation Tree, select the output multiplex you want.
4 In the Output panel, select the output program you want.
5 In the Context menu, select Set Recoder.
6 Select the recoder option you want.
7 In the Properties panel, scroll the panel until you see the Priority column.

Grooming Tabular View

CAP-1000 Software Guide v4.0 459

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Reserving Recoders

8 From the Priority menu, select the priority for recording the output program:
Level 1 indicates the lowest priority stream (maximum amount of recoding) and Level 10
indicating the highest priority stream (minimum amount of recoding), with increments of 1. The
priory levels can be modified at any time, even after a program is created and a stream is being
passed to the output.
9 In the Min Bit Rate cell, enter the video bit rate floor that the CAP-1000 is not to drop below
when recoding video streams.
10 In the Max Bit Rate cell, enter the video bit rate ceiling that the CAP-1000 is not to go above
when recoding video streams.
11 Click Apply.
12 Click Yes.

Reserving Recoders in the Programs Panel

To reserve a recoder:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the output multiplex you want.
4 At the bottom of the window, click Programs.
5 In the Programs panel, right-click the output program you want.
6 In the Recoder column, set the resource you want to apply from the menu.

Grooming—Reserve Recoders for Programs

460 ARRIS Enterprises, Inc.

 Dropping Recoders

7 Click Apply.
8 Click Yes.

Dropping Recoders
To drop a recoder:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .
3 In the Navigation Tree, select the output multiplex you want.
4 In the Output panel, select the groomed program you want.
5 In the Context menu, select No Recoder.
6 Click Apply.
7 Click Yes.

Managing Clusters
Recoding resources are supplied by the DSP module. Based on the recoding resources you assign
to a program, the Controller initializes the CAP-1000 with recoder cluster “personalities.” At
startup, these clusters are not initialized and cannot perform any recoding action. Based on the type
of recoding resource assigned to the programs, the Controller downloads the proper firmware into
the clusters, setting each clusters with recoding capabilities.
If a cluster becomes fragmented—where recoding resources are available but not used—you can
change the recoding type for a cluster by transferring its resources to other clusters of the same
recoding resource type.

Personalities
A cluster supports one of two recoding personalities, either MPEG-4/AVC video recoding or
MPEG-2 video recoding, as follows:
• Up to 4 MPEG-4/AVC HD or SD video streams per cluster
• Up to 96 MPEG-2 SD streams or up to 24 MPEG-2 HD streams per cluster

NOTE Audio streams (MPEG, Dolby Digital, Dolby Digital Plus, AAC, or HE-AAC) and other non-video
elementary streams cannot be recoded.

CAP-1000 Software Guide v4.0 461

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Clusters

Viewing Clusters
Using the CherryPicker Element Manager, you can view the following information about clusters:
• Cluster personality (either MPEG-4/AVC or MPEG-2 recoding)
• Total number of recoding resources per cluster (either 4 HD-MPEG-4/AVC or 24 SD/24 HD
MPEG-2)
• Total number of available recoding resources on the cluster
• Total number of assigned recoding resources on the cluster
• Fragmentation of recoding resources on the cluster

To view clusters:
 From the CherryPicker Element Manager, click Setup > System > Recoders.

Cluster Management

462 ARRIS Enterprises, Inc.

 Managing Clusters

Table 22-4 Cluster Management Information

Recoder Cluster Allocation

Cluster ID Shows the ID of the DSP-FPGA cluster.

Recoding Indicates if the recoder is in service.

Total SD/HD Shows the total number of Standard Definition (SD) and High Definition (HD)
recoders.

Used SD/HD Shows the total number of used SD and High Definition HD recoders.

Available SD/HD Shows the number of available SD and HD recoders.

Device Resources

Resource Shows the hardware resource type.

Capability Shows the number of hardware resources that are licensed for use.

Used Shows the number of hardware resources that are in use.

Available Shows the number of hardware resources that are available for use.

Viewing Cluster Details

To view cluster details:

1 From the CherryPicker Element Manager, click Setup > System > Recoders.
2 Click the Cluster Management link.

Cluster Management

CAP-1000 Software Guide v4.0 463

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Managing Clusters

3 Identify the cluster you want and click Show Details.

Cluster Details

Table 22-5 Cluster Detail Information

Recoding Shows the recoding type: MPEG-2 (SD or HD) or MPEG-4(AVC-SD or AVC-HD).

Output PID Shows output PID number assigned in the packet header of an MPEG stream that
identifies the transport stream to which the packet belongs.

Program Shows the default program name.

Program Name Shows the user-assigned program name.

Mux Shows the output multiplex for the program.

Line Shows the output port for the program.

A pop-up menu for a selected program lets you drop or cancel recoder assignment.
4 If you made edits to this window, click Apply.

Optimizing Recoder Cluster Allocations

The Cluster Management dialog provides a map of cluster utilizations showing where resources
can be compacted. If you choose to reallocate recoder resources to other clusters, programs are re-
groomed, video output is affected, and a brief interruption in service occurs.

To optimize:
1 From the CherryPicker Element Manager, click Setup > System > Recoders.
2 Click the Cluster Management link.

464 ARRIS Enterprises, Inc.

 Managing Clusters

3 Review the information in the Recoder Cluster Allocation after Optimization section.
The Cluster Management window opens and shows a list of affected programs for the
defragmentation request. The table lists includes line names, multiplex names, and program
names. This window also displays additional details about the gain made if you decide to
defragment the cluster.

Cluster Management

4 To make the recommended changes, click Apply.

A warning message opens.

Cluster Management Warning

5 Click Yes.
When the process completes, a message window opens.

CAP-1000 Software Guide v4.0 465

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Missing Recoders

Cluster Management

6 Click OK.

Missing Recoders
The missing recoder feature provides warnings when a user applies changes to a groom and a
recoder is missing on any of the output programs in the groom.
A warning window opens whenever the following conditions are met:
• The output program does not have a recoder assigned to it and the input for groom contains a
non-still picture video stream input.
• The output program does not have a recoder assigned to it and the Pass Stream option is not
selected.

NOTE The Pass Stream option appears on the Grooming Definition panel of the Content Picking > Grooming
window. This option lets you pass or groom encrypted streams. Pass Stream is enabled by default.

• The output program does not have a recoder assigned to it and the input for the groom contains
a non-file.
• The output program does not have a recoder assigned to it and the input for the groom contains
a non-profile 4:2:2.
If you see a warning or error message, reassign the recoders and reapply them to the groom.

Auditing Recoders
The Recoder Audit window provides information about grooms without a valid recoder and
enables you to assign a correct recoder to the output program.

To audit recoders:
1 From the CherryPicker Element Manager, click Setup > System > Recoders.
2 Click the Recoder Audit link.

466 ARRIS Enterprises, Inc.

 Auditing Recoders

Recoder Audit

The Recoder Audit window opens.

Recoder Audit

This window displays the information about grooms that are without valid recoders.
3 Under Grooms without Valid Recoder, select the groom you want.
4 From the Recoding menu, assign a correct recoder to output program.
5 Click Apply.
6 Click OK.

CAP-1000 Software Guide v4.0 467

Chapter 22 Configuring Rate Shaping, Stat Mux Pools, and Recoders Auditing Recoders

468 ARRIS Enterprises, Inc.

 CHAPTER 23
Passing PIDs

In This Chapter
• PIDs
• Passing PIDs
• Deleting Passed PIDs

PIDs
A digital TV signal is transmitted as a stream sequence of MPEG-2 data packaged into a transport
stream. Each table or elementary stream in a transport stream is identified by a 13-bit packet ID
(PID). A demultiplexer extracts elementary streams from the transport stream in part by looking
for packets identified by the same PID.
Because MPEG streams carry multiple programs, program allocation tables (PAT) and program
mapping tables (PMT) are transmitted along with the programs. These program tables provide a
list of programs and their associated PIDs for specific programs which allows the MPEG
receiver/decoder to select and decode the correct packets for that specific program. The CAP-1000
can pass tables and elementary streams through the CherryPicker Element Manager as well as
more than 95 PIDs.

Passing PIDs
PID passing is a special case of grooming. PID passing enables you to transmit input programs
through the CAP-1000 without performing rate shaping on those programs. The passed programs
are output without any changes to the bit rate (the passed program joins the output transport stream
in the same condition, at the same bit rate, as it entered the CAP-1000).
No PMT is generated for this output program; it simply serves as a container under which all PIDs
to be passed are collected. When the collection of PIDs is to be changed, either by addition or
deletion, the new collection is submitted as an update request.
You can pass (transmit) a specific input elementary stream PID (i.e., MPEG-4/AVC video,
MPEG-2 video, and audio private data) to a specific output multiplex. Passed streams are given the
highest priority (the minimum delay) in processing. Like a custom groom, there can be multiple
input source elements in the request.

CAP-1000 Software Guide v4.0 469

Chapter 23 Passing PIDs PIDs

Pass PIDs

A single row in the Input/Output mux panels shows a Passed PIDs icon for the multiplex. When
you click on the row, the bottom table will provide the information about the streams and tables for
the Passed PIDs.

Passing Tables
For tables, you can pass the same PID multiple times as long as the combination of PID, table ID,
and table extension ID is unique.

Conditions for Passing PIDs

During PID passing, the following conditions apply:
• The same input PID can be passed to multiple output multiplexes. If an elementary stream
with the same PID as the passed PID exists in the output multiplex, this PID cannot be passed.
• The maximum number of output passed streams is 300 per device. The same limit applies to
each output multiplex, with the per-device limit overriding the per-multiplex limit.
• A passed stream can be deleted from an output multiplex. If the same input PID is passed to
several output multiplexes, only the PID for the specified multiplex is deleted.
• If an input stream is groomed, it cannot be passed to the output.
• No output PSI/SI tables are modified or created to reflect the passed streams.
• You can choose not to include the passed PMT in the output PAT.

470 ARRIS Enterprises, Inc.

 Passing PIDs

• All the passed streams must be in one, and only one, stat mux pool (SMP). By default, they are
added to the first SMP.

Output Mux with Pass PIDs

• If the SMP with passed streams is deleted, you can either delete the passed streams, or
preserving them and move them to one of the remaining SMPs.
• If the SMP with passed streams is deleted, and you do not move the passed PIDs to a specific
remaining SMP, or if there are no passed streams in that deleted SMP, the “place holder” for
the future passed PIDs is moved to the remaining SMP (with the smallest ID). The SMP ID is
an internal identification number assigned by the CAP-1000.
• When the last SMP is deleted, you have the option to continue passing the streams. In this
case, all passed PIDs are added to the output multiplex.

Passing PIDs
To pass a PID to an output multiplex:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.

CAP-1000 Software Guide v4.0 471

Chapter 23 Passing PIDs Passing PIDs

If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

NOTE Example illustrations show the Diagram view.

4 In the Component Tree, select the stream or table you want.

NOTE If an input stream is groomed, it cannot be passed to the output. This is because passed streams are treated as
asynchronous streams, regardless of their type, whereas in regular grooming, the stream type is preserved.

5 For streams, do one of the following:

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected stream and drop it on a Passed PID placeholder for the
output mux(es) you want.
• If you selected a specific multiplex for the Output Mux menu, drag the selected stream and
drop it on the Passed PID.

Streams PID Pass

6 For tables, do one of the following:

• If you selected a specific multiplex for the Output Mux menu, drag the selected table and
drop it on the Passed PID.

472 ARRIS Enterprises, Inc.

 Passing PIDs

• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected table and drop it on a Passed PID placeholder for the
output mux(es) you want.

Drop Input Here

• To pass all table extensions, drag the selected tables (with the table IDs you want) and drop
them on a Passed PID placeholder for the output mux. Select the All for Table Extension cell
in the Table tab.
• To pass all tables for an input PID, drag the selected tables (with the table IDs you want) and
drop them on a Passed PID placeholder for the output mux. Select All for Table ID and Table
Extension Cell in the Table tab.
• To pass a specific table ID and extension ID, drag the table (with table ID you want), and drop
them on a Passed PID placeholder for the output mux.
7 Release the mouse button.
8 Click Apply.
9 Click OK.
The passed PID is added to the Grooming Definitions panel. To view the stream or table, click the
Streams or Tables tab.

CAP-1000 Software Guide v4.0 473

Chapter 23 Passing PIDs Passing PIDs

Table 23-1 Streams/Tables Information

Streams

Type Shows the stream type. For example, video, audio, or data stream.

Line Shows the input line for the stream.

Mux Shows the input mux for the stream.

Program Shows the program name.

Input PID Shows the input PID ID.

Output PID Selects the output PID for the table. Auto assigns a PID to this table.

Tables

Type Shows the table type.

Line Shows the input line for the table.

Mux Shows the input mux for the table.

Table Name Shows the table name.

Table ID Shows the table ID.

Table Extension Shows the table extension.

Input PID Shows the input PID for the table.

Output PID Selects the output PID for the table. Auto assigns a PID to this table.

Refer in PAT By default, the new PMT will be included in the PAT and the DVB NIT table. Select
False to remove the PAT.

474 ARRIS Enterprises, Inc.

 Deleting Passed PIDs

Table PID Pass

Deleting Passed PIDs

To delete a passed PID:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

NOTE Example illustrations show the Diagram view.

4 Under the Output panel, click the Streams or Tables tab (whichever is appropriate).
5 Right-click the stream you want and select Delete.

CAP-1000 Software Guide v4.0 475

Chapter 23 Passing PIDs Deleting Passed PIDs

Delete

6 Click Apply.
7 Click Yes.

476 ARRIS Enterprises, Inc.

 CHAPTER 24
Enabling Digital Program Insertion

In This Chapter
• Digital Program Insertion
• Stream Matching
• DPI and Network Rules
• SCTE 35 Cue Insertion
• DPI Functions
• DPI Requirements
• Synchronizing Equipment
• Verifying a Successful Ad Server Connection

Digital Program Insertion

Digital Program Insertion (DPI) is the digital splicing of ads into network programs. The
CAP-1000 functions as the CAP-1000 in a DPI solution and is compliant with the SCTE 30 2005
“Digital Program Insertion Splicing API” [ANSI/SCTE 30], SCTE 35 2001 “Digital Program
Insertion Cueing Messages for Cable” [ANSI/SCTE 35], and the application guide, “ANSI/SCTE
67 2006 Digital Program Insertion Cueing Message for Cable -Interpretation for SCTE 35”
[ANSI/SCTE 35].
DPI depends on digital cue tones that are inserted into the program stream by the service provider
at the service origination (uplink) using the SCTE 35 messaging structure to signal a reserved spot
(known as an ad avail) for insertion of a local advertisement over a national ad.
The CAP-1000 extracts the SCTE 35 messages, which signal the timing and duration of each avail,
and delivers this information to the ad server over TCP/IP using the SCTE 30 protocol. The ad
server, in turn, determines which ads to play out based on its play list, which is typically integrated
with a traffic and billing system, and the CAP-1000 inserts the scheduled ads into the network
program.

CAP-1000 Software Guide v4.0 477

Chapter 24 Enabling Digital Program Insertion Digital Program Insertion

Single Server / Single Splicer Configuration

Recoding
You need to assign a recoder to all programs on the output multiplex. This action is required to
achieve seamless DPI splicing on any of the output programs within the multiplex. If you decide to
run DPI on a single output program, you must assign recorders to all output programs in the
multiplex.

NOTE Assigning a recoder to just one program in the multiplex will not help with seamless splicing. The statistical
remultiplexing method does not apply to a single output program, but to the entire multiplex. So, if the ad
that splices to the individually-recoded output program has a larger bit rate than the network, rate clamping
on the entire output multiplex might occur, the output programs will underflow, and DPI might fail.

See section,“Managing Recoders,”on page 451 for more information.

Ad Insertion Protection
The CAP-1000 supports Ad Insertion Protection (AIP) for ad input feeds. When this feature is
configured, AIP causes the unicast ad insertion multiplex to switch from a failed GigE port to the
peer port. To configure AIP, see Chapter 31, “Configuring Ad Insertion Protection” for
information.

478 ARRIS Enterprises, Inc.

 Digital Program Insertion

Output Programs
The following actions are allowed at any time for an output program with a connection to an ad
server:
• Grooming the output program
• Applying a configuration file to the multiplex with this output program
• Dropping the output program
• Deleting the output program
• Disabling the output multiplex with this output program
In the case of grooming, dropping, or deleting the output program, the current (and all scheduled)
ads for this output program are aborted (other programs in the same output multiplex with ad
server connections are not affected) and the connection is closed.
In the case of applying a configuration file or disabling the output multiplex, the current (and all
scheduled) ads for all output programs in this multiplex are aborted and the connection is closed.

CUEI Messages
The CAP-1000 supports the grooming of programs carrying cue messages. The CUEI registration
descriptor will be copied to the output PMT from the corresponding input PMT. If groomed, the
CUEI streams will have the stream type = 134 in the output PMT. The CAP-1000 ensures that the
groomed CUEI stream is the one that belongs to the video stream that is groomed to the output.
Cue message originators are required to send a cue message at least four seconds in advance of the
ad avail.

How Digital Program Insertion Works

This section describes what happens behind the scenes during digital ad insertion.
1 The ad server opens a TCP/IP connection to the CAP-1000.
2 An ad server sends an Init_Request to the CAP-1000. The Init_Request identifies the output
program (by name) into which the ads will be inserted. It also tells the CAP-1000 which card,
physical port, IP address, and IP port it expects the CAP-1000 to use to receive ads from the
server.
3 The CAP-1000 uses the information in the Init_Request to create ad input muxes to receive the
the ads streamed out by the server. The CAP-1000 then sends an Init_Response to the ad
server to notify the ad server that the Init_Request has succeeded.
4 The cue messages are detected in the primary (network) input program that is groomed to the
output program named in the Init_Request.The CAP-1000 detects an SCTE 35 cue message in
the primary (network) input program and forwards the cue message to the ad server in a
Cue_Request message.
5 The ad server responds to the CAP-1000 with a Cue_Response message to notify the
CAP-1000 that it received the Cue_Request.

CAP-1000 Software Guide v4.0 479

Chapter 24 Enabling Digital Program Insertion Stream Matching

6 Three seconds or more prior to the time at which the ad is to be inserted, the ad server sends a
Splice_Request to the CAP-1000. This request contains the PIDs, stream types, stream
descriptors of the ad elementary stream, the time the ad should begin, and the duration of the
ad.
7 The CAP-1000 schedules the ad insertion.
8 The CAP-1000 returns a Splice_Response to the ad server to notify the ad server that the
Splice_Request succeeded.
9 300-600 milliseconds prior to the time at which the ad is to start, the ad server starts streaming
the ad program to the CAP-1000.
10 When the CAP-1000 splices into the ad, it sends a Splice Complete_Response (splicein) to the
CAP-1000.
11 When the CAP-1000 splices out of the ad, it sends a Splice Complete_Response (spliceout) to
the ad server containing the ad duration and average bit rate.
The steps starting with the Splice_Request and ending with the Splice Complete_Response
(spliceout) are repeated for every ad in the avail. At the end of the avail, the CAP-1000 splices
back to the network.

Stream Matching
A successful ad splice requires only video and audio streams to be matched. Data streams are
optional. The network video and audio streams must be matched. The ad streams do not need to be
matched.
The number and the type of video and audio elementary streams played during an ad insertion
must be the same as the number and type of video and audio elementary streams in the
corresponding network program for a successful splice.
To insert ads into an output program, the CAP-1000 performs stream matching between the
elementary streams in the ad and the elementary streams defined in the output program PMT. For
the ad insertion to succeed, the ad must contain all of the elementary streams needed to match the
desired streams in the network program. These streams include one video stream and one or more
audio streams. One or more data streams (for example, ETV requires two data streams) are
optional.

Video Streams
The network program has one video stream groomed. That video stream must be MPEG-1,
MPEG-2, or MPEG-4/AVC. If the network program video type is MPEG-4/AVC, then the video
insertion stream must have an MPEG-4/AVC type. If the network program video type is MPEG-1
or MPEG-2, then the video insertion stream type must be either MPEG-1 or MPEG-2. MPEG-2
ads are accepted on MPEG-1 networks and vice versa. DigiCipher 2 video is treated as MPEG-2
video. The matching rules for video streams are defined in Table 24-1.

480 ARRIS Enterprises, Inc.

 Stream Matching

Table 24-1 Video Stream Matching

Ad Video/Network Video MPEG-1 MPEG-2 (DC-II) MPEG-4/AVC

MPEG-1 Match Match Mismatch

MPEG-2 (DC-II) Match Match Mismatch

MPEG-4/AVC Mismatch Mismatch Match

Stream matching is done one stream at a time. For each stream in the network program, the
CAP-1000 searches for a matching stream in the ad. If the video stream in the network cannot be
matched, the ad is not spliced. The CAP-1000 returns the “Splice Failed - Unknown Failure” result
code (108) in the Splice_Response message.

Audio Streams
Two criteria are used to match audio streams, the stream type (MPEG-2 layer 2, Dolby Digital, or
AAC) and the language. In matching audio elementary streams, the first matching criterion is the
audio stream type. The audio stream type in the insertion must be the same as the audio type in the
network program. That is, if the network plays MPEG audio, then the ad should also have an audio
stream of the MPEG type. However, MPEG-1 audio and MPEG-2 audio are interchangeable.
After the audio stream type criterion is satisfied, the language descriptor is used to match the
streams. For example, if both the network and the ads have two MPEG audio streams, one with an
English language descriptor and another with a Spanish language descriptor, then the English
stream in the ad is matched with the English stream in the network and the Spanish stream in the
ad is matched with the Spanish stream in the network.
If, after matching the type and the language of the audio streams, there are still unmatched audio
streams in the network program, then the unmatched streams in the network program are matched
with the first audio stream in the ad with the correct stream type.

Data Streams
The CAP-1000 lets you control which network data streams are spliced, kept, or dropped during
DPI. You set DPI rules for data streams on both primary and backup programs. Network video and
audio streams are spliced according to the component matching algorithm, as described above.

Subtitles
Subtitle data streams are an exception to the requirement that all of the descriptors of the data
stream must match all of the descriptors of the network stream. In the case of subtitle streams, the
CAP-1000 searches for an exact match including all descriptors. If a match is not found, then the
CAP-1000 searches for a subtitle stream with matching language descriptors. If no matching
language descriptors exist, then the CAP-1000 cannot make a match.

CAP-1000 Software Guide v4.0 481

Chapter 24 Enabling Digital Program Insertion DPI and Network Rules

There are two types of subtitle streams. An SCTE subtitle stream has a stream type of 0x82 and
must have a language descriptor present to be considered a subtitle stream. A DVB subtitle stream
has stream type 0x06 and must have descriptor 0x59 present. If a stream does not match either of
these criteria, then it is not considered a subtitle stream.

DPI and Network Rules

DPI rules control the insertion of data streams during an ad. For each network data stream, you
select one of the DPI rules in Table 24-2.

Table 24-2 DPI Rules

Keep Causes a network data stream to be groomed to the output during an ad stream, whether there is
a matching ad stream or not. You cannot set the rule for cue streams. For teletext streams, the
default rule is Keep, but you can set the rule to any other value.

Drop Drops the network data stream from the output program during ads, regardless of whether the ad
contains a data stream that matches the network data stream. The PID remains in the output PMT,
but it is a placeholder, as the output stream has no content.
• If a custom grooming includes a forced stream that shows up at the input as an EBIF or an EISS
stream, the stream is dropped from the network and an alarm is raised.
• Combinations of DPI rules and network rules that require the CAP-1000 to merge the network
EBIF with the ad EBIF are rejected.
• In the case of a receiver-mixed audio stream in the network, the CAP-1000 drops the network
stream instead of splicing in an audio stream from the ad. Consequently, the DPI rule for a
receiver-mixed audio stream is Drop instead of Splice.

Splice/Keep Causes a network data stream that is matched by an ad to be spliced by the ad. If there is no
matching ad stream, the network stream is kept.

Splice/Drop Causes a network data stream that is matched by an stream to be spliced by the ad stream. If
there is no matching ad stream, then the network stream is dropped. If the network stream is
dropped, then its PID remains in the output PMT, but it is a placeholder PID, as the stream has no
content when the ad plays. This is the default DPI rule for non-cue and non-teletext data streams.

Remove Applies only to cue streams. This rule is automatically applied to a groomed SCTE 35 cue stream
when Cue Insertion is enabled for the groom. You cannot change this rule, but you can disable Cue
Insertion, in which case the rule changes to Keep.
Remove signifies that the cue stream will not be included in the groom and will not have a PID in
the output PMT. It is used to remove a cue stream from a program groom when Cue Insertion is
enabled. Refer to section,“SCTE 35 Cue Insertion,”on page 483 for more information.

Insert Applies only to a cue stream as an Extra Output Stream. When Cue Insertion is enabled for a
groom, a CUEI Extra Output Stream with stream type 134 is automatically created with the Insert
rule. This rule signifies that an SCTE 35 cue table will be inserted in the Extra Output Stream
whenever an ad is inserted in the output stream. Refer to section,“SCTE 35 Cue
Insertion,”on page 483 for more information.

NOTE The network rules are not applicable to file grooming or PASS PID.

482 ARRIS Enterprises, Inc.

 SCTE 35 Cue Insertion

You use the Primary Streams and Backup Streams panels in the Diagram view of the Grooming tab
to configure the DPI Rule parameters.

SCTE 35 Cue Insertion

Cue insertion is the ability to insert an SCTE 35 cue table into an output program whenever an ad
is inserted into the output program in response to an SCTE 30 Splice Request. The CAP-1000
supports the grooming of programs and elementary streams that carry SCTE 35 cue messages.
A cue stream carries splice information tables. A splice information table is used to notify
downstream devices of splice events, such as a network break or a return from a network break.
The splice information tables that pertain to a given program are carried in one or more PID(s)
referred to by that program’s Program Map Table (PMT). In this way, splice event notification can
pass through most transport stream remultiplexers without the need for special processing.
The CAP-1000 grooms both encrypted and non-encrypted splice information tables. In the process
of grooming a splice information table, the CAP-1000 does not encrypt or decrypt the table, but
passes it to the output in the same form as it comes in.

NOTE The CAP-1000 does not support sending a cue message to the ad server if the cue message is encrypted.

The last cue table time is displayed in the Configuration Tree as part of the information about an
input cue elementary stream. The time reported is the arrival time of the cue table, not the splice
time within the cue table. The arrival time is the time at which the CAP-1000 received the cue
table in the input.

CAP-1000 Software Guide v4.0 483

Chapter 24 Enabling Digital Program Insertion SCTE 35 Cue Insertion

CUEI

The last cue table time is reported for an input cue stream only if the video stream in the same
input program as the cue stream is groomed to at least one output program that is connected to an
ad server.
After a cue table time is reported, it remains unchanged as part of the cue stream information, even
if the associated input video stream is no longer groomed to any output program connected to an
ad server. This information can be useful because some ad servers tend to disconnect and
reconnect in certain circumstances, and it is better if the last cue table time does not disappear
when this occurs.
The PMT of an output program with Cue Insertion enabled has an SCTE 35 Registration
descriptor defined at the program level. This descriptor has tag 0x05 and format ID CUEI.
Cue Insertion is enabled or disabled in the Grooming window by means of a check box for the
groom definition. When Cue Insertion is enabled, an extra output stream is automatically added in
the GUI, and the original (network) cue stream is prevented from being output.

484 ARRIS Enterprises, Inc.

 SCTE 35 Cue Insertion

CUEI Extra Output Stream

Applications
One application of Cue Insertion is the ability to support “addressable advertising,” also known as
“targeted advertising.” In this application, the inserted cue table allows a downstream device,
usually a set-top box, to determine the start time and duration of each ad in the avail and substitute
a higher-value ad for the ad inserted by the splicer.
Another application of Cue Insertion is the replacement of DTMF analog cue tones by SCTE 35
digital cue tones. In this application, a sequence of DTMF tones in an analog program is decoded
by a device that transmits the information in the DTMF tones to an ad server. When cue insertion
is enable, the ad server uses this information to command the splicer to keep digital cue tones into
an output program.

How Cue Insertion Works

Cue insertion is an enhancement to DPI. It occurs only when DPI occurs and it scales with DPI.
When Cue Insertion is enabled, a cue table is inserted whenever an ad is inserted. No cue table is
inserted when postblack is inserted. Cue insertion does not have its own license. It depends on
DPI, and DPI requires a per-program license. If the DPI license expires, then no new ads are
inserted and no new cue tables are inserted.

CAP-1000 Software Guide v4.0 485

Chapter 24 Enabling Digital Program Insertion SCTE 35 Cue Insertion

Cue insertion is supported by all features that support DPI, including PRED, MRED, AIP, and
CPR. DPI is supported on both ASI and GIGE input and output ports, and Cue Insertion is
likewise supported on both kinds of ports.
Cue insertion is enabled on a per-groom basis. It can be enabled for a program groom, a custom
groom, a file groom, or a file+live audio groom. It cannot be enabled for a passed PID groom.
Even if Cue Insertion is enabled for a groom, Cue Insertion occurs on the groom only if DPI
occurs. Since DPI is not allowed on a groom that does not include a non-still video stream, Cue
Insertion will not occur on such a groom either.
Cue insertion occurs only when DPI occurs, and DPI occurs only when a non-still video stream is
groomed. However, the CAP-1000 will not prevent you from enabling Cue Insertion when a still
video is groomed. The validation for the presence of a groomed non-still video stream (along with
other validations) is performed at runtime when DPI is attempted by the ad server.
You can disable Cue Insertion in the CAP-1000 by clearing the Enable Cue Insertion check box in
the groom definition. The CAP-1000 responds by automatically removing the CUEI Extra Output
Stream and re-enabling any ordinary CUEI stream in the groom by changing its DPI Rule from
Remove to Keep and by re-enabling its output PID.

NOTE Cue Insertion cannot be enabled, disabled, or monitored by SNMP. Cue Insertion does not generate any
alarms or SNMP traps.

CUEI Extra Output Streams and DPI Rules

When Cue Insertion is enabled, the CAP-1000 automatically creates a CUEI Extra Output Stream
with stream type 134 (CUEI) and DPI rule “Insert.” The Insert DPI rule signifies that cue tables
will be inserted in the output program on the PID defined for the CUEI Extra Output Stream. You
cannot modify this DPI Rule. However, you can modify the Output PID of the CUEI Extra Output
Stream.
In addition to creating the CUEI Extra Output Stream, the CAP-1000 prevents any normal CUEI
stream from being passed from input to output. If a groom definition includes a CUEI stream, then
the CAP-1000 disables the CUEI stream by changing the DPI Rule of the stream from Keep to
Remove and disabling the Output PID for the groomed CUEI stream. These actions signify that
the stream will not be included in the groom as long as Cue Insertion is enabled. No cue tables in
the stream will be passed from input to output, and there will be no PID in the output PMT for the
stream. The groomed CUEI stream is disabled because the cue tables that would otherwise be
passed if the stream were enabled are replaced in their function by the cue tables that are inserted
on the PID of the CUEI Extra Output Stream.
A CUEI Extra Output Stream can be defined when cue insertion is disabled. You can create an
Extra Output Stream of type 134, but this Extra Output Stream will not be used for Cue Insertion
and will be treated no differently than any other Extra Output Stream. In particular, its DPI Rule
will be Splice/Drop, not Insert. The Controller will not add a CUEI registration descriptor to the
output PMT to describe this stream. It is assumed that this output placeholder will be used for
some purpose other than to output SCTE 35 cue tables.

486 ARRIS Enterprises, Inc.

 DPI Functions

DPI Functions
This section describes the functions of the various components in DPI.

Connectivity
The communication between the server and the splicer is conducted over one TCP/IP socket
connection per output program. Once this connection is established, it remains established until
one of the devices terminates the connection, at which time the connection must be re-initialized
before DPI can begin again.

Splicer
The CAP-1000 is the splicer as defined in the SCTE 30 standard. The splicer requires information
about the ad before it can splice ads into the network program. The program name is used for
output program identification. This name is a unique name assigned to each output channel in the
splicer setup. It is needed by the server to determine which program will be replaced by the ad
when ad insertion occurs.
The splicer also needs to know which ad program to splice into the output programs. This includes
the insertion multiplex address which is provided in the Init_Request message. The insertion
stream information (PIDs, types, and descriptors) is included in the Splice _Request message. All
of this information is required before a splice can occur.

Number of Connections and Ad Servers

The CAP-1000 allows only one connection per output program– ad server IP address pair. For
example, if ad server “S1” has an open connection to the output program “P1,” a second request
from S1 to open an connection to P1 causes the current connection to close and new connection to
be accepted. The ad server S1 can open connections to any other output program, and other servers
can open connections to the output program P1.
• The CAP-1000 supports simultaneous connections with all output programs.
• The CAP-1000 monitors the TCP/IP connection with the ad server. If there is no activity for 90
seconds, then the connection to the server is terminated.
• The CAP-1000 supports up to three ad server connections per output program. Only one of
these is allowed to splice ads. The others can only monitor the Cue_Request messages sent by
the CAP-1000.

Response Time and Synchronization

The CAP-1000 sends a Response message to a server as soon as possible - within three seconds
after receiving a Request message.

CAP-1000 Software Guide v4.0 487

Chapter 24 Enabling Digital Program Insertion DPI Requirements

Ad Server Configuration Information

This section describes the configuration information sent to the splicer by the ad server. The
following information is required:
• Chassis—the value of this field is ignored.
• Card—an integer indicating the CAP-1000 slot on which the server's insertion multiplex(es)
will be received: 1 for the GigE ports and 3 and 4 for the DVB-ASI ports.
• Port—the hardware port number where the ad server’s insertion multiplex is connected. This
is the CAP-1000 physical input port number in the slot specified in the card field. If this port
does not exist, an error is returned. For example, Card 1 and Port 2 represent line 1/2.
• Logical Multiplex Type—a value from Table 24-3. Other types are not supported.

Table 24-3 Supported Logical Multiplex Types

Logical Multiplex Type Physical Interface Length Name Description

0x0000 DVB-ASI 0 Not Used This field is not present for type 0.

0x0003 GigE 6 IPV4 Address The most significant four bytes of the
Logical_Multiplex field contain the IP address of the
multiplex, and the remaining two bytes contain the IP
port number where the multiplex can be found.

0x0006 GigE Variable IPV4 Address See [ANSI/SCTE 30] Table 8-3a Type 0x0006 structure
length for details.

If this field contains a unicast IP address, this address should match either the IP address or the
virtual IP address (if defined) of the GigE Port. If Ad Insertion Protection (AIP) is enabled on that
port, the virtual IP address can be the virtual address of the associated AIP peer port. Otherwise, an
error is returned.

DPI Requirements
To perform DPI using the CAP-1000 as a splicer, ensure that the requirements defined in this
section are met.

NOTE The CAP-1000 does not support DPI for encrypted or passed programs.

Server Requirements
• The IP address or virtual IP (if it exists) of the CAP-1000 port used for STCE 30 traffic.
• The CAP-1000 splicer name that identifies the CAP-1000 device to be used as the splicer.
• The name of the output program in which ads will be spliced.

488 ARRIS Enterprises, Inc.

 DPI Requirements

• The input line (card and port) where ads will be received by the CAP-1000.
• The MPEG input port GigE IP address or virtual IP (if it exists) of the line where ads will be
received by the CAP-1000.

IMPORTANT Do not change any of the parameters specified above while an ad server has a working connection to the
device.

If you change any remaining parameters, the CAP-1000 will respond as follows:
• If the IP address (real or virtual) used for the SCTE 30 traffic changes, the connection with the
ad server will be closed.
• If either the splicer name of the CAP-1000 or the output program name changes, it will not
affect the existing connections. No errors are reported; however, any new connection to an
obsolete name will fail.
• If the IP address (real or virtual) used for the MPEG traffic changes, all the multiplexes will be
removed from the input port and the associated SCTE 30 connections will be closed.

NOTE The CAP-1000 does not report the number of input multiplexes that are used for DPI in the Input Mux:
Active and Input Mux: Inactive counters in the Status bar.

Ad Insertion License
An ad insertion license is required to perform DPI. Refer to Chapter 8, “Managing Licenses,”for
more information.

MPEG-4 AVC Requirements

To successfully splice an MPEG-4 AVC stream with a CAP-1000 during ad insertion, the
following requirements must be met:
• Two consecutive and valid Presentation Time-Stamps (PTS) have been encountered on the
source. The stream can be locked to a valid Program Clock Reference containing a
program_clock_reference field.
• A Sequence Parameter Set (SPS) has been encountered in the stream, and the
timing_info_present_flag has been detected in the Supplemental Enhancement Information
(SEI).
• The Instantaneous Decoding Refresh (IDR) has been encoded in the source stream, and it is
received at a suitable interval rate, such as 0.5 second intervals. When the stream contains IDR
on the source, the CAP-1000 restricts the splicing to IDR frames only if they are received at a
rate of at least two per second. If not, the splicing is done according to SPS detection, but the
grooming is not seamless.
• If no IDR is encountered, the CAP-1000 uses an SPS to splice into streams.

CAP-1000 Software Guide v4.0 489

Chapter 24 Enabling Digital Program Insertion DPI Requirements

Channel Naming Requirements

The CAP-1000 treats the Channel Name (defined in the ANSI/SCTE 30 2006) as the name of the
output channel corresponding to the Primary Channel into which the Insertion Channel is spliced.

NOTE The output program name must be unique across the CAP-1000 for DPI to work correctly.

Port Naming Requirements

The CAP-1000 and the SCTE 30 standard use the same numbering scheme. The CAP-1000 uses a
slot/port designation in which the slot and port are numbers. The GigE ports are labeled 1/1 to 1/4.
The ASI ports are labeled 3/1 to 3/4 and 4/1 to 4/4.

Splicer Naming Requirements

When connecting to the CAP-1000, the ad server sends an SCTE 30 Init_Request message over
the TCP/IP connection. The designated CAP-1000 receives the message and responds, attempting
to initialize the connection. Since there may be several CAP-1000s on a network, the identification
of the CAP-1000 is important. The CAP-1000 name must match the name requested by the ad
server.

Splicer Name

To change the CAP-1000 splicer name, refer to section,“Renaming the CAP-1000 as a Splicer,”on
page 77 for instructions.

490 ARRIS Enterprises, Inc.

 Synchronizing Equipment

Synchronizing Equipment
A critical element of DPI is the synchronization of the ad server and the CAP-1000. Without the
careful management of event timing, splicing does not occur. Some ad servers carry a time server
or Network Time Protocol (NTP) server on their platforms, while others use third-party NTP
servers for timing reference.

NTP Servers

Regardless of the configuration, the ad server and CAP-1000 must use the same NTP reference to
conduct successful splices. In many implementations, the CAP-1000 uses the ad server itself as an
NTP server. To synchronize the CAP-1000 with an NTP server, the NTP server’s IP address is
added through the Network window in the CherryPicker Element Manager interface.

NOTE If a third-party NTP server is used, it is critical that the CAP-1000 has ping access to this server.

Up to five NTP servers can be added. When multiple servers are configured, NTP automatically
selects the best time source on which to synchronize. This action helps to minimize accumulated
error. Refer to section,“Managing NTP Servers,”on page 78 for information on adding and
synchronizing NTP servers.

Out-of-Synchronization Alarms
Alarms can occur if the clock offset drifts occur between the CAP-1000 and NTP servers or ad
servers. For example, any offset greater than 15 milliseconds between the CAP-1000 and the
currently synchronized NTP server causes an alarm in CherryPicker Element Manager interface.
Similarly, an alarm is raised when an ad server is out of synchronization with the CAP-1000 by a
pre-defined threshold of 15 milliseconds.

CAP-1000 Software Guide v4.0 491

Chapter 24 Enabling Digital Program Insertion Verifying a Successful Ad Server Connection

See Chapter 35, “Managing Alarms and Logs” for more information about alarms.

Verifying a Successful Ad Server Connection

To verify the connection:
1 In the CherryPicker Element Manager, click Content Picking > Grooming.
2 In the DPI column, review the status of the DPI by referring to the following icons:

Indicates that the ad server is not connected.

Indicates that the output program is connected to an ad server.

Indicates that the ad server is connected and an ad is playing.

Ad Playout

492 ARRIS Enterprises, Inc.

 Verifying a Successful Ad Server Connection

3 In the CherryPicker Element Manager, click Content Picking > Mux.

4 Expand the Component tree.
5 Locate the ad multiplex.
When there is a successful connection of the ad server and CAP-1000, the label, “Ad Mux” is
displayed next to the ad multiplex. Use the Ad Mux option to display or hide ad muxes in the
Component Tree.

Ad Mux

CAP-1000 Software Guide v4.0 493

Chapter 24 Enabling Digital Program Insertion Verifying a Successful Ad Server Connection

494 ARRIS Enterprises, Inc.

 CHAPTER 25
Enabling Emergency Alert Messaging

In This Chapter
• Emergency Alert Messaging
• Enabling EAS on Input Multiplexes
• Enabling EAS on Output Multiplexes and Programs
• Passing EAS to Downstream Devices

Emergency Alert Messaging

The SCTE 18 standard, Emergency Alert Messaging for Cable, defines an Emergency Alert
signaling (EAS) method for use by cable TV systems to signal emergencies to digital set-top
boxes. EAS allows cable operators to disseminate emergency alert information related to state and
local-level emergencies and warnings in an efficient way, while minimizing disruption to
programming.
The CAP-1000 lets you configure dedicated input multiplexes to receive EAS messages from any
number of EAS generators. Each dedicated input multiplex contains a details channel that supplies
the audio/video service pertaining to the alert. On reception of a SCTE 18 EAS, the program
switches to the details channel for the EAS generator. The EAS switchover to the details channel is
controllable at a program level for a rate-shaped output multiplex.

CAP-1000 Software Guide v4.0 495

Chapter 25 Enabling Emergency Alert Messaging Emergency Alert Messaging

EAS Input Muxes

Emergency Alert Message

The Emergency Alert Message (EAM) is in the form of a standard MPEG-2 table and, when
necessary, is delivered in-band on cable Transport Streams that carry one or more programs in-the-
clear. For programs that are scrambled on a cable system, the EAM is delivered to the Point Of
Deployment (POD) module using the cable system’s forward data channel. The POD module
processes the message as necessary and delivers it to the receiving device out-of-band.
The EAM signaling scheme includes the following elements:
• The start time and expected duration of the alert event
• A textual description of the alert
• An indication of the availability and location of the details channel
• An indication whether the event is of sufficient importance that tuning to the details channel
shall be done unconditionally
• A pointer to an optional audio channel that can be used to replace the audio of the current
service for the duration of the EAM

Details Channel
The details channel is an audio/video service pertaining to the alert. When an SCTE 18 EAS alert
is received, the CAP-1000 switches channels in an output multiplex to the details channel or EAS
generator. On receipt of the EAS, the program switches to the details channel for the EAS
generator, whether ads are playing out or not. EAS switchover to the details channel is controllable
at a program level.

496 ARRIS Enterprises, Inc.

 Emergency Alert Messaging

You configure the EAS generator that provides the alerts and details channel in the CherryPicker
Element Manager. You can define multiple such sources.
.

EAS Input Mux and Details Channel

FIPS Codes
In some situations, a receiving device may be given emergency alert information that applies to an
event that is geographically too far away to be of interest. The cable emergency alert message
includes the Federal Information Processing Standard (FIPS) location codes that originally
accompanied the EAS event. With knowledge of the location of the cable terminal, the receiving
device can be designed to filter out any events that happen to be outside the area of interest.
All output muxes have a FIPS code identifying the zone in which a particular mux will play out the
EAS alert. You can control whether EAS alerts with FIPS codes are switched to the details channel
on a specific rate-shaped output multiplex or stat mux pool.
Using the GUI, you can specify the FIPS code for the location and then pass the EAM table to the
rate-shaped output mux.

CAP-1000 Software Guide v4.0 497

Chapter 25 Enabling Emergency Alert Messaging Emergency Alert Messaging

EAS Output Mux FIPS Code

The CAP-1000 processes EAS messages with FIPS codes as follows:

• For in-band EAS, detail channel switching occurs only if the FIPS code received on the EAS
alert matches with the configured FIPS code on the output multiplex.
• For out-of-band EAS, detail channel switching occurs on all output multiplexes in which the
FIPS code matches the received EAS alert message FIPS.
• EAS switching is disabled for output multiplexes not configured with FIPS code.

Alert Priorities
The Alert Priority parameter specifies the minimum alert priority to switchover a program to the
details channel. Based on the priority level of the alert, the EAS message instructs the receiving
device to force-tune to a designated emergency broadcast channel. The priorities are:
• 0—Test message
• 1-2—Reserved for future use
• 3—Low priority: the alert may be disregarded if processing the alert would interrupt viewing
of an access-controlled service
• 4-6—Reserved for future use
• 7—Medium priority: the alert may be disregarded if processing the alert would interrupt
viewing of a pay-per-view or video on demand event
• 8-10—Reserved for future use
• 11—High priority: the alert is processed unconditionally, but can involve text-only display if
no audio is available. This is the default
• 12-14—Reserved for future use
• 15—Maximum priority: the alert is processed unconditionally

498 ARRIS Enterprises, Inc.

 Emergency Alert Messaging

Alert priority “0” is a special case for test purposes. When an alert priority 0 is received, the
program switch is executed.
If the minimum alert priority for a program is 7 and an alert of 5 is received, the program will not
be switched. The CAP-1000 will execute the switch when the alert priority is 7 or higher. The
default priority level is “Alert Disabled.”
You enable or disable EAS messages and alert priorities for a specific program at either the output
multiplex-level or program-level of the GUI.

NOTE The EAS Alert feature is enabled through the EAS Alert License mechanism.

EAS Alert Priority

Digital Program Insertion

If an EAS alert is received and Digital Program Insertion (DPI) is configured to splice an ad, DPI
is interrupted, the splice is prevented, and the alert is allowed to play out. If an EAS alert is
received while DPI is active, DPI is interrupted, the splice fails, and the alert is allowed to play
out.

Configuration File
Information about the FIPS code, minimum alert priority for the switch, and whether the channel
will switch to the EAS is stored in the input and output multiplex configuration files.

CAP-1000 Software Guide v4.0 499

Chapter 25 Enabling Emergency Alert Messaging Enabling EAS on Input Multiplexes

Enabling EAS on Input Multiplexes

The CAP-1000 can receive EAS alerts and details from one or more EAS generators on any input
multiplex. You can designate the input mux that can specifically receive EAS alerts. Each
dedicated input multiplex is configured with a details channel; an audio/video service pertaining to
the alert. When an EAS alert is received on the dedicated input multiplex, the CAP-1000 switches
the selected output program to the configured details channel if enabled to do so.
If alerts are sent to a channel, rather than to an EAS encoder, you configure the input multiplex to
receive in-band alerts. For in-band signaling, the CAP-1000 can receive EAS messages on any
input multiplex from any number of input generators.

Enabling EAS on GigE Multiplexes

To enable:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the GigE input multiplex you want.
4 In the GigE Input Muxes panel, select the EAS parameter you want to edit.
5 Select the Enable EAS option.

Gigabit Ethernet Input Multiplex

500 ARRIS Enterprises, Inc.

 Enabling EAS on Input Multiplexes

Table 25-1 Gigabit Ethernet Input Multiplex EAS Parameters

Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this option.

EAS Type Indicates if Emergency Alert Service (EAS) alerts are delivered using in-band
signaling or out-of-band signaling. For in-band signaling, the CAP-1000 receives
EAS alerts on any input multiplex from any number of input generators.

Details Channel Same Mux When this option is selected (checked), the EAS received on this mux is switched to
the selected details channel and program for playout.

Details Line Shows the IP address and port for the EAS input mux.

Details Mux Shows the details channel for use when the receiving device is navigating using
out-of-band service information (SI). In the case that out-of-band SI is not available,
the channel reference is through major/minor channel number.

Details Channel Shows the audio/video service and program pertaining to the alert.
Note: When an output program is switched to an EAS details channel, the path in
the output, Path SDT, follows the EAS details channel. If there is no Path SDT
present in the input mux containing the EAS details channel, the CAP-1000
generates a new Path SDT table. See section,“Managing Path SDT,”on
page 294 for information.

6 Enter the required information for EAS.

7 Click Apply.
A configuration window opens.
8 Click Yes.

Enabling EAS on ASI Multiplexes

To enable:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the Component Tree.
3 In the Component Tree, select the ASI input multiplex you want.
4 Select the Enable EAS option.

CAP-1000 Software Guide v4.0 501

Chapter 25 Enabling Emergency Alert Messaging Enabling EAS on Input Multiplexes

ASI Input Multiplex

5 In the ASI Input Muxes panel, select the EAS parameter you want to edit.

Table 25-2 ASI Input Multiplex EAS Parameters

Enable EAS Enables or disables the Emergency Alert Service (EAS) on this mux.
• To enable the program to switch to the details channel, select this option.
• To restrict the programs from switching to the details channel, clear this option.

EAS Type Indicates if Emergency Alert Service (EAS) alerts are delivered using in-band
signaling or out-of-band signaling. For in-band signaling, the CAP-1000 receives
EAS alerts on any input multiplex from any number of input generators.

Details Channel Same Mux When this option is selected (checked), the EAS received on this mux is switched to
the selected details channel and program for playout.

Details Line Shows the IP address and port for the EAS input mux.

Details Mux Shows the details channel for use when the receiving device is navigating using
out-of-band service information (SI). In the case that out-of-band SI is not available,
the channel reference is through major/minor channel number.

Details Channel Shows the audio/video service and program pertaining to the alert.
Note: When an output program is switched to an EAS details channel, the path in
the output, Path SDT, follows the EAS details channel. If there is no Path SDT
present in the input mux containing the EAS details channel, the CAP-1000
generates a new Path SDT table. See section,“Managing Path SDT,”on
page 294 for information.

6 Enter the required information for EAS.

7 Click Apply.
A configuration window opens.
8 Click Yes.

502 ARRIS Enterprises, Inc.

 Enabling EAS on Output Multiplexes and Programs

Enabling EAS on Output Multiplexes and Programs

All output muxes have a FIPS (Federal Information Processing Standard) code identifying the
zone in which a particular mux will play out the EAS alert. You can control whether EAS alerts
with FIPS codes are switched to the details channel on a specific rate-shaped output multiplex or
stat mux pool.
You can also configure whether EAS alerts are enabled on a specific program, as well as set the
minimum alert priority to switchover a program to the details channel.

To enable:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Expand the device node in the Component Tree.
3 In the Component Tree, select the GigE or ASI output multiplex you want to modify.
4 To control EAS with FIPS codes for all programs on the multiplex, do one of the following:
• To enable EAS with FIPS codes to switch to the details channel if the alerts are matched, select
the Enable EAS option.
• To prevent EAS with FIPS codes from switching to the details channel, clear the Enable EAS
option.
5 If required, select the State Code, County Sub Division, and County Code you want from the
menus. This information is applied to all programs on the output multiplex.
6 Under Program Number, select the EAS alert to play out.
7 To control EAS with FIPS codes for a specific program on the multiplex, do one of the following:
8 To enable the program to switch to the details channel, select EAS Alert Priority to Low,
Medium, High, or Maximum. See section,“Alert Priorities,”on page 498 for a description of
levels.

NOTE Illustrations show a GigE output mux.

CAP-1000 Software Guide v4.0 503

Chapter 25 Enabling Emergency Alert Messaging Passing EAS to Downstream Devices

GigE Output Mux and Program

• To restrict the programs from switching to the details channel, select EAS Alert Priority to
Alert Disabled.
9 Click Apply.
10 Click Yes.

Passing EAS to Downstream Devices

In the event that you configured a particular input multiplex to receive an SCTE 18 EAM, the
EAM table entry will appear on the Configuration Tree for that particular mux. You can then pass
the SCTE 18 messages to an output mux using drag-and-drop.

To pass EAS:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux configured for EAS.

NOTE Example illustrations show the Diagram view.

4 In the Component Tree, select the input mux configured for EAS.
5 From the Table node, select EAM.
6 For streams, do one of the following:
• If you selected the All Muxes, All SPTS Muxes, or All MPTS Muxes option from the
Output Mux menu, drag the selected stream and drop it on a Passed PID placeholder for the
output mux you want.

504 ARRIS Enterprises, Inc.

 Passing EAS to Downstream Devices

• If you selected a specific multiplex for the Output Mux menu, drag the selected stream and
drop it on the Passed PID.

EAM PID Pass

7 Release the mouse button.

8 Click Apply.
9 Click Yes.
A confirmation window opens.
10 Click Yes.

CAP-1000 Software Guide v4.0 505

Chapter 25 Enabling Emergency Alert Messaging Passing EAS to Downstream Devices

506 ARRIS Enterprises, Inc.

 CHAPTER 26
Managing EBIF

In This Chapter
• Enhanced TV Binary Interchange Format
• EBIF Components
• DPI and Network Rules
• Ad Management Service and the Ad Decision Service
• Reports
• Enabling or Disabling EBIF
• Configuring Device-level EBIF
• Configuring Grooming-level EBIF
• Merging
• Bypassing EBIF Filters
• Managing Placeholders for ETV Streams

Enhanced TV Binary Interchange Format

Enhanced TV Binary Interchange Format (EBIF) is a multimedia content standard, developed
under the OpenCable project of CableLabs (Cable Television Laboratories, Inc.), that provides a
way to deploy targeted and interactive ETV applications to set-top boxes (STB). EBIF content
defines one or more multimedia pages, similar to web pages that are specialized for use within an
enhanced television system.
An EBIF resource (file) is a sequence of bytes that conforms to the EBIF content format. It forms
the primary information contained in an ETV application. An ETV user agent acquires and
decodes resources, presents screens to the end user, and executes actions in response to the end-
user input.
Broadcasters can add EBIF data to their traditional broadcast, or create a virtual channel that
references the primary broadcast audio/video while transmitting the additional EBIF data. Once
the EBIF data PID’s are groomed on an output mux, the broadcast program will begin carrying
EBIF to the STB. At this point, any EBIF applications that a broadcaster transmits on this service
will stream to the STB.

CAP-1000 Software Guide v4.0 507

Chapter 26 Managing EBIF Enhanced TV Binary Interchange Format

License
Use of the EBIF function requires an EBIF license. This includes configuring EBIF filters,
filtering, and merging. The license is added through the license mechanism. To determine if EBIF
is merged, the CAP-1000 inspects the network and DPI rules. If the rules indicate that the packets
will be merged, then a license is required.
The EBIF features are activated only upon entering a unique license key. You designate each
output program as subject to EBIF treatment (filtering and merging) by assigning an EBIF license
to the program. If no license is assigned, filtering and merging are not available for that program.
If a valid license is installed, EBIF processing does not automatically start. You need to re-enable
EBIF at the program level for EBIF processing to start.

NOTE If the CAP-1000 is configured to use network and Digital Program Insertion (DPI) rules, the system
validates if you are merging packets. If one source rule is KEEP and the other source rule is DROP, then no
license is required. If both source rules have KEEP, an EBIF license is required.

See Chapter 8, “Managing Licenses” for more information.

ETV
ETV applications are typically bound to programming on cable networks, allowing for interactive
overlays that correspond to the video content. The capabilities of these applications include:
• Graphic Overlays—Present on-screen widgets allowing subscribers to interact using their set-
top remote control.
• Synchronized Delivery—Insert applications into programming (either pre-produced or live) to
synchronize interactive overlays with the broadcast content.
• Two-way communication—Send form posts from the set-top box through the cable head-end
to a response server via HTTP. This allows for applications such as voting/polling and
advertising requests for information (RFI).
• Telescoping to VOD—Interface with the video on demand layer to jump from linear
programming to VOD assets.
• Dynamic Data—Use existing data feeds to update interactive applications with news,
programming information, product info, polls, etc.
• DVR Support—Set recordings for episodes or series on DVR boxes.
• Personalization and Targeting—Store user data to create customized experiences.

508 ARRIS Enterprises, Inc.

 Enhanced TV Binary Interchange Format

Filtering
Filtering is a process in which certain EBIF applications are dropped, while other applications are
passed to the output. A filter can be a whitelist or a blacklist. If the parameters in the EBIF
application match the criteria specified in the whitelist, then the application is passed. Similarly, if
the parameters in the application match the criteria in the blacklist, then the application is dropped.
If the parameters do not match a filter, then the next filter, if available, is matched. If the
parameters do not match any defined filter, then the device-level default action, which can be
whitelist or blacklist, is taken.

EBIF Enabled

The CAP-1000 lets you apply EBIF filtering commands per device or per groom. Filters at the
groom level have a higher priority than those at the device level.
You can exclude input multiplexes as sources from the filtering mechanism (i.e. there is no
filtering applied to any EBIF triggers coming from these input multiplexes). EBIF data coming
from input multiplexes is passed to the output without filtering, augmentation, or reporting. This
applies only to a custom groomed program where EBIF PIDs have multiple input source
multiplexes.
When not passing EBIF data, due to filtering settings, the CAP-1000 does not modify the PMT. It
retains the EBIF information in the PMT as if no filtering was applied.

CAP-1000 Software Guide v4.0 509

Chapter 26 Managing EBIF Enhanced TV Binary Interchange Format

IMPORTANT On upgrade, the filters from the previous releases of CAP-1000 software are ignored and EBIF is blocked
for old groomings. Similarly, filters from the old versions of the device configuration file are ignored.

EBIF Tables
The CAP-1000 filters EBIF tables using the organization ID, application ID, the major version,
application priority, test flag, application instance, and private data fields as defined in the
Enhanced TV Binary Interchange Format 1.0, Section 11.2. All fields except the organization ID
are optional. The organization ID is required.

Default Filters
The CAP-1000 provides two filters, whitelist and blacklist, for controlling how EBIF applications
are filtered. When grooming is assigned a whitelist filter, only those applications that match the
whitelist are passed to the output. When a grooming is assigned a blacklist, no application is
passed to the output or all applications are dropped. You can set the default filter you want to use.

Merging
The CAP-1000 lets you merge EISS and EBIF streams from a local feed with EISS and EBIF
streams from a network feed.You can custom groom EISS and EBIF streams from local and
network feeds, along with other streams, to the output. If EBIF is enabled for the output program,
the CAP-1000 assigns the same output PID to the EISS streams and the same output PID to the
EBIF streams. As a result, EBIF coming from two different sources is streamed on a single set of
output PIDs.
Merging of two EISS sources is allowed if their stream types match. Similarly, merging of two
EBIF sources is allowed if their stream types match. Merging is not allowed when the stream types
of the respective EISS streams or the stream types of the respective EBIF streams are different. In
this case, an error message is displayed
When the stream types match, you select between replacing the output PID with the new source
and inserting the new input data into the output PID. You can specify a maximum of two streams
coming from two different program sources.
Note the following constraints for merging:
• The CAP-1000 cannot merge EBIF streams with EBIF streams for pre-bind ads. Combinations
of DPI rules and network rules that require the CAP to merge the network EBIF with the ad
EBIF are rejected.
• Only one EISS EBIF stream and one EBIF stream are accepted per input program. The
software does not allow the merging of two EISS streams or two EBIF streams carried on two
different input PIDs in the same input program into a single output PID. The two inputs to be
combined into a single output must come from two different input programs. In addition,
merging does not work in conjunction with MRED.

510 ARRIS Enterprises, Inc.

 EBIF Components

• When the CAP-1000 is configured for CPR and a failover occurs, EBIF applications continue
to run as configured on the Backup CAP-1000. Similarly, if a program is configured with
PRED and a failover occurs, the EBIF action(s) continue on the backup program.
• If a custom groom includes a forced stream that shows up later on at the input as an EBIF or an
EISS stream, the CAP-1000 assigns Drop for the network rule and Drop for the DPI rule; the
forced stream will not be used in the groom. Streams are grouped together to indicate the same
sources (separated by red lines).
• The merge feature affects primary streams and backup streams under both the Diagram and
Tabular views. The Network rule and the DPI rule options are added to the backup stream as
well, so you can override the default values.

EBIF Pre- and Late-bind Ads

The CAP-1000 supports the merging of pre-bind and late-bind ads. Pre-bind ads are those in which
EBIF data is embedded in ads that are then inserted into programming using local ad insertion.
Pre-bind ads are delivered with enhancements already bound within the ad . Pre-bound content can
be streamed (ex. from a network) or file-based (ex. an enhanced advertisement on an ad server).
Late-bind ads are those in which EBIF data is dynamically inserted into network programs,
network ads, or local ads downstream from the original distribution, typically at the MSO headend
or local advertising insertion point. Thus, applications are muxed with the program or ad at the
splicer.
You use Network Rules to control how late-bind EBIF streams are handled during network
content. EBIF streams that are late bound are groomed from a different source than the network,
typically an EBIF spooler in the headend. You can still use DPI rules to control how the late bound
streams are managed while an ad splice is active.

Extra Output Streams

If a local advertisement contains EBIF data, but the network groom does not, you pre-configure
extra output streams in the groom definition to include the EBIF data PIDs and descriptors. Once
these PIDs are established on the output program, any EBIF data contained in the spliced content
will be transmitted through to the STB.
Filters are not allowed to be defined for a groom that contain extra output EISS/EBIF streams.

EBIF Components
This section describes the major components used in EBIF filtering and merging with the
CAP-1000.

CAP-1000 Software Guide v4.0 511

Chapter 26 Managing EBIF EBIF Components

Timestamps
The CAP-1000 displays the last received timestamp for a groomed input EISS stream. The
timestamp is displayed even if the EISS triggers are blocked according to the EBIF filter setting or
EBIF priority settings. The CAP-1000 continues to display the timestamp even if the groomings
that use the EISS stream are dropped. The display is removed if the Controller is restarted. The
timestamp is not displayed for EBIF application resource streams.

Tables
The CAP-1000 does not modify the content of any EBIF tables; either the data is passed as is or it
is not passed. When the EBIF data is not passed due to the filtering settings, the PMT is not
modified and still contains the EBIF information as if no filtering were applied.

NOTE You can modify the EBIF content via the Ad Decision System (ADS) file which, if configured, can send a
dynamic update to the EBIF enabled program.

The CAP-1000 reports a major severity alarm when is an EISS PID in the ad (data is ignored), but
not in the groomed program (either placeholders or actually in the input PMT). The alarm is
cleared when the CAP-1000 receives a new splice request and the error condition is resolved.

Transport Streams
To transmit applications from a headend or program uplink, EBIF requires a number of additions
to the standard MPEG transport stream. These include registration descriptors placed in Program
Management Tables (PMTs) that indicate the PIDs of specific application streams. EBIF also uses
a specially designated MPEG-2 data stream, known as the ETV Integrated Signaling Stream
(EISS), to send signals that trigger various events associated with each application. EISS carries
media timeline messages, stream events, and EISS tables for an ETV application.

512 ARRIS Enterprises, Inc.

 EBIF Components

EBIF Applications and EISS Streams

Gigabit Ethernet Multiplexes

To receive programming content with EBIF applications and EISS streams, create a GigE input
multiplex and enter the IP address and UDP port of the input transport streams. See
section,“Managing Gigabit Ethernet Input Multiplexes,”on page 244 for more information.

NOTE Once an output program is groomed for EBIF, the data PIDs remain in the program although the EBIF data
may or may not be actively streaming from the source.

Input Programs
Only one EISS EBIF stream and one EBIF application resource is accepted per input program. The
CAP-1000 does not allow you to merge two EISS streams or two EBIF application resource
streams when carried over two different input PIDs on the same input program. These resources
are not merged into a single output PID. The two inputs to be combined into a single output must
come from two different input programs. Merging does not work in conjunction with MRED.
These two features are mutually exclusive in the CAP-1000.

CAP-1000 Software Guide v4.0 513

Chapter 26 Managing EBIF DPI and Network Rules

Output Programs
You can perform pre-bind EBIF if the network doesn’t have EBIF by adding extra output streams
and changing the descriptors to include EISS and EBIF descriptors.

CPR and PRED

If the CAP-1000 is configured for CherryPicker Redundancy (CPR) and a failover occurs, the
EBIF applications continue to run as configured on the Primary CAP-1000. Similarly, if a program
is configured with Program Redundancy (PRED) and a failover occurs, the EBIF action(s)
continue on the backup input.

DPI and Network Rules

You use Network Rules to control how network and late-bind EBIF streams are handled during
network content. EBIF streams that are late bound are groomed from a different source than the
network, typically an EBIF spooler in the headend. You use digital program insertion (DPI) rules
to control how the network and late bound streams are managed while an ad splice is active.

Restrictions
• Only certain combinations of Network rules and DPI rules are allowed.
• The Core will not merge more than two EBIF streams, either during the network or during the
ad.
• The ad is not merged with the network.

Network Rules
For each network data stream, the following applies:
• Keep—Causes a network data stream to be groomed to the output when the network is
playing.
• Drop—Causes a network data stream to be dropped from the output when the network is
playing. The PID remains in the output PMT, but it is a placeholder, as the output stream has
no content.
During digital program insertion (DPI), network rules are not used, but the DPI rules are used.

DPI Rules
The CAP-1000 lets you control which network data streams are spliced, kept, or dropped during
DPI. You can set the DPI rules for data streams on both primary and backup programs. For each
network data stream, you select one of the following DPI rules:
• Keep—Causes a network data stream to be groomed to the output when an ad is playing.

514 ARRIS Enterprises, Inc.

 DPI and Network Rules

• Drop—Causes a network data stream to be dropped from the output when an ad is playing.
The PID remains in the output PMT, but it is a placeholder, as the output stream has no
content.
• Splice/Keep—Causes a network data stream that is matched by an insertion stream to be
spliced by the insertion stream. If there is no matching insertion stream, then the network
stream is kept during the ad.
• Splice/Drop—Causes a network data stream that is matched by an insertion stream to be
spliced by the insertion stream. If there is no matching insertion stream, then the network
stream is dropped during the ad. If the network stream is dropped, then its PID remains in the
output PMT, but it is a placeholder PID, as the stream has no content when the DPI program
plays.
The filters configured for ads in this grooming are applied to EBIF content in the ad when this
content is played.
Table 26-1 lists the valid network and DPI rule combinations for streams. The Controller will
ensure that you can select only from the allowable combinations.

Table 26-1 Valid Network-DPI Rule Combinations

Network Rule DPI Rule

Keep Keep

Keep Drop

Keep Splice/Keep

Keep Splice/Drop

Drop Keep

Drop Splice/Keep

Drop Drop

Table 26-2 shows the valid network rule combinations.

Table 26-2 Valid Network Rule Combinations

NW Rule NW Rule Valid Require License

for First EBIF for Second EBIF

Keep Keep Yes Yes

Keep Drop Yes No

Drop Drop Yes No

Table 26-3 shows the valid DPI rule combinations. Valid combinations are highlighted.

CAP-1000 Software Guide v4.0 515

Chapter 26 Managing EBIF Ad Management Service and the Ad Decision Service

Table 26-3 Valid DPI Rule Combinations

DPI Rule for DPI Rule for Valid (1)/

First EBIF Second EBIF Invalid(0) License Required

Keep Keep Yes Yes

Keep Drop Yes No

Keep Splice/Keep No

Keep Splice/Drop No

Drop Drop Yes No

Drop Splice/Keep Yes No

Drop Splice/Drop Yes No

Splice/Keep Splice/Keep Yes Yes

Splice/Keep Splice/Drop Yes No

Splice/Drop Splice/Drop Yes Yes (because network

rules must be KEEP)

Ad Management Service and the Ad Decision Service

The Ad Management Service (ADM) and the Ad Decision Service (ADS) are core elements in a
standardized SCTE 130 advanced advertising system. The ADM originates messages articulating
ad insertion opportunities (i.e., placement opportunities) with the primary communication
consumer being the ADS. The ADS determines how advertising content is combined with non-
advertising (entertainment) content assets (i.e., placement decisions). The ADM completes the
decision lifecycle via reporting activity events (i.e., placement status). The ADM interface
facilitates both preconfigured ad decisions as well as real-time placement selection.
The following figure illustrates a very basic example advertising system utilizing only an ADM
and an ADS.

Basic SCTE 130 Advertising System

516 ARRIS Enterprises, Inc.

 Reports

The placement system, represented by the Placement Execution cloud, is responsible for
opportunity determination and placement execution (e.g., content insertion/splicing). The ADM
communicates placement opportunities and placement status to the ADS and the ADS returns
placement decisions as a response to placement opportunities. The Campaign Management cloud
symbolizes the system providing the information necessary for the ADS to render ad decisions.
In the CAP-1000, the Controller acts as an ADM and communicates with the ADS. You enable the
following three messages in the GUI: PlacementRequest, PlacementResponse, and
PlacementStatusNotification. The ServiceCheckRequest, ServiceCheckResponse,
ADSRegistrationRequest and ADSRegistrationResponse messages are not supported.

Reports
The CAP-1000 supports reporting in the form of the Internet Protocol Detail Records (IPDR).
Reports are saved to the IP address where the CAP-1000 stores log files on an external syslog
server. If no syslog server has been configured, the syslog messages are redirected to the
/var/log/messages file on the Data Flash.
These XML reports are compliant with the OC_Report_MUX_3_0_Final_Draft.xsd schema
defined by Cablelabs. The reports can read by an ETV Activity Reporting System (EARS) system.

Enabling or Disabling EBIF

This section explains how to enable or disable EBIF at the device-level on the CAP-1000.

Enabling EBIF

To enable:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
5 In the Output panel, select the EBIF check box for each program on which you want to enable
EBIF.

CAP-1000 Software Guide v4.0 517

Chapter 26 Managing EBIF Enabling or Disabling EBIF

EBIF

6 Click Apply.
7 Click OK.

Disabling EBIF

To disable:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
5 In the Output panel, clear the EBIF check box.
6 Click Apply.
7 Click OK.

518 ARRIS Enterprises, Inc.

 Configuring Device-level EBIF

Configuring Device-level EBIF

This section explains how to configure to configure general settings, such as default reporting
settings and ADS registration information. At the device-level, use the whitelist filter pass all
EBIF applications. Use the blacklist filter to block all applications. If you use the blacklist filter,
ensure that the whitelist filter is not set at either the device- or grooming-levels.

To configure:
1 From the CherryPicker Element Manager, click Setup > System > Device.
2 Select the EBIF link.

EBIF Link

The EBIF Configuration window opens.

CAP-1000 Software Guide v4.0 519

Chapter 26 Managing EBIF Configuring Device-level EBIF

EBIF Configuration

3 In the Device Settings panel, choose the Default Filter Type.

The default filters take effect if there are no filter matching at the program level that result in the
explicit action of passing or dropping the application. If the default filter type is defined to be a
whitelist, the application will be passed. Conversely, a blacklist default will drop the application.
4 In the Device Settings panel, configure the settings for reporting.

Table 26-4 Reporting Parameters

Reporting

Syslog Address Gives the IP address of an external syslog server. If no syslog server has been
configured, the syslog messages are redirected to the /var/log/messages file
on the Data Flash.

Syslog Port Specifies the port for the syslog IP address.

Enable Reporting Enables reporting of filtering for the selected events:

• EISS Operations
• EISS Data
• EBIF Operations
• EBIF Data

5 In the Device Settings panel, configure the settings for the ADS server.

520 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Table 26-5 ADS Parameters

ADS

ADS Address for Placement (Optional) Specifies the Ad Decision Service (ADS) IP address for
Requests PlacementRequest messages.

Send Placement Requests Enables/disables sending PlacementRequest messages to an ADS.

ADS Address for PSNs (Optional) Specifies the ADS IP address for sending Placement Status
Notifications (PSN).

Send PSNs Enables/disables sending Placement Status Notifications.

6 Click OK.
7 Go to section,“Configuring EBIF for Ad Inputs,”on page 522.

Configuring Grooming-level EBIF

This section explains how to configure EBIF at the grooming-level. The example procedure is as
follows:
1 Groom a primary and a backup program
2 Configure the ad input settings
3 Configure the EBIF settings on the primary program
4 Configure EBIF settings on the backup program
Other types of EBIF deployment are possible. Refer to the OpenCable™ Specifications, MUX 3.0
Specification, OC-SP-MUX3.0-I01-130215 and OpenCable™ Specifications ETV, Enhanced TV
Binary Interchange Format, OC-SP-ETV-BIF1.0.1-120614 for more information.

IMPORTANT Grooming-level EBIF filters take precedence over device-level EBIF filters.

Grooming Programs

To groom programs:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
5 Expand the Component Tree.
6 In the Input panel, select one or more input programs that contain EBIF/EISS data from the Tree.

CAP-1000 Software Guide v4.0 521

Chapter 26 Managing EBIF Configuring Grooming-level EBIF

7 Drag and drop the programs to an output mux.

8 Click Apply.
9 Click Yes.
10 Repeat steps 3 through 9 and groom a backup program.
See Chapter 18, “Grooming Programs,” for complete information.

Configuring EBIF for Ad Inputs

To configure:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Line menu, select the output port you want.
4 In the Output Mux menu, select the output mux(es) you want.
5 In the Grooming Definitions panel, right-click the input programs that contain EBIF/EISS data.
6 From the Context menu, select EBIF.
The EBIF Configuration window opens.
7 Click Add Config.

Ad Input Configuration

8 In the EBIF Configuration panel, configure the session settings for the ad input.

Table 26-6 Ad Input Parameters

Session Name (Optional) Specifies a name for this session. This name is used to identify
individual streaming sessions associated with service definitions and
collectors.

Session Select AD Input (if an ad server is used).

522 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Table 26-6 Ad Input Parameters (continued)

Enable Reporting Enables reporting or EBIF merging and filtering for the selected events:
• EISS Operations
• EISS Data
• EBIF Operations
• EBIF Data

Use Device Settings Select this option to enable your pre-configured device-level settings.

9 Leave the window open.

10 Go to section,“Configuring EBIF for Primary Programs,”on page 523

Configuring EBIF for Primary Programs

To configure:
1 Click Add Config.
2 In the EBIF Configuration panel, configure the session settings for the primary program.

Primary Program Configuration

Table 26-7 Primary Program Parameters

Session Name (Optional) Specifies a name for this session. This name is used to identify
individual streaming sessions associated with service definitions and
collectors.

Session Select the name of the mux with the primary program.

CAP-1000 Software Guide v4.0 523

Chapter 26 Managing EBIF Configuring Grooming-level EBIF

Table 26-7 Primary Program Parameters (continued)

Enable Reporting Enables reporting or EBIF merging and filtering for the selected events:
• EISS Operations
• EISS Data
• EBIF Operations
• EBIF Data

Use Device Settings Select this option to enable your pre-configured device-level settings.

3 In the EBIF Configuration window, click Add Filter.

Primary Program Configuration

4 Click Add Entry.

524 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Primary Program Configuration

5 Configure the following attributes that define the application filter. Applications are identified by
matching against these attributes.

Table 26-8 Application List Entry Attributes

Organization ID (Required) Specifies a 32-bit field that identifies the organization that is
responsible for the application.

Application ID Specifies a16-bit field that identifies the application function. This is allocated
by the organization registered with the organization_id who decides the policy
for allocation within the organization.

Major Version Specifies an integer (0-255) that denotes the major version number of the
application.

Minor Version Specifies an integer (0-255) that denotes the minor version number of the
application.

App Priority Specifies the application priority (0-255) for matching. Used in combination
with the other application specific attributes.
• When there is more than one application with the same Application
identification, this priority is used to determine which application is
started.
• When there are insufficient resources to continue running a set of
applications, this priority is used to determine which applications to
terminate.
• The greater the numerical value, the higher the application priority.

Test Flag (Optional) Specifies an 8-bit field that conveys a set of test flags used to
target this application to a specific population of set-top boxes. The usage of
this field is governed by the cable operator.

CAP-1000 Software Guide v4.0 525

Chapter 26 Managing EBIF Configuring Grooming-level EBIF

Table 26-8 Application List Entry Attributes (continued)

App Instance (Optional) Specifies an application instance identifier for matching. The
notation is: a-zA-Z0-9_\-]*

Tracking Shows a system-supplied string that uniquely identifies this entry after the
filter is configured. This GUID can be passed in SCTE 130 PSNs, in reporting
entries, or the Alarms window.

Private Data (Optional) Specifies an ETV application descriptor private data field. It is a HEX
string.This field is defined as private use and is dependent upon the
Application Type being signaled.

Type Identifies the action to be taken on applications that match the filter criteria.
Type can be whitelist, blacklist or private.
• If specified as whitelist, an application that matches the filter defined by
the App Instance entry is passed in the stream.
• If specified as blacklist, an application that matches the filter defined by
the App Instance entry is dropped.

Priority of Entry Specifies the order in which entries are processed. It is used when more than
one Application List Entry exists. The default value is priority 1. The lower the
value, the higher the priority. If more than one entry has the same priority, the
order of interpretation is not specified.

NOTE If the organizationID is not specified, all other application identifiers are not relevant. If the organizationID
is not specified, all applications present at the flow point will match this filter. This function can be used to
define a flow point to “pass all” or “block all” applications that do not explicitly match a higher priority
filter. It is recommended to configure filters such as this (that match all applications) with a higher priority
of entry value (which makes it a lower priority), so that other filters are applied first.

6 If the primary program has multiple EBIF, click Add Entry and add one entry for each EBIF.

526 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Primary Program Configuration

7 Leave the window open.

8 Go to section,“Configuring EBIF for Backup Programs,”on page 527.

Configuring EBIF for Backup Programs

To configure:
1 Click Add Config.
2 In the EBIF Configuration panel, configure the session settings for the backup program.

CAP-1000 Software Guide v4.0 527

Chapter 26 Managing EBIF Configuring Grooming-level EBIF

Backup Program Configuration

Table 26-9 Backup Program Parameters

Session Name (Optional) Specifies a name for this session. This name is used to identify
individual streaming sessions associated with service definitions and
collectors.

Session Select the name of the output mux with the backup program.

Enable Reporting Enables reporting or EBIF merging and filtering for the selected events:
• EISS Operations
• EISS Data
• EBIF Operations
• EBIF Data

Use Device Settings If you use an Ad Decision Service, select this option to enable your pre-
configured device-level settings.

3 In the EBIF Configuration window, click Add Filter.

528 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Backup Program Configuration

4 Click Add Entry.

CAP-1000 Software Guide v4.0 529

Chapter 26 Managing EBIF Configuring Grooming-level EBIF

Backup Program Configuration

5 Configure the following attributes that define the application filter. Applications are identified by
matching against these attributes.

Table 26-10 Application List Entry Attributes

Organization ID (Required) Specifies a 32-bit field that identifies the organization that is
responsible for the application.

Application ID Specifies a16-bit field that identifies the application function. This is allocated
by the organization registered with the organization_id who decides the policy
for allocation within the organization.

Major Version Specifies an integer (0-255) that denotes the major version number of the
application.

Minor Version Specifies an integer (0-255) that denotes the minor version number of the
application.

530 ARRIS Enterprises, Inc.

 Configuring Grooming-level EBIF

Table 26-10 Application List Entry Attributes (continued)

App Priority Specifies the application priority (0-255) for matching. Used in combination
with the other application specific attributes.
• When there is more than one application with the same Application
identification, this priority is used to determine which application is
started.
• When there are insufficient resources to continue running a set of
applications, this priority is used to determine which applications to
terminate.
• The greater the numerical value, the higher the application priority.

Test Flag (Optional) Specifies an 8-bit field that conveys a set of test flags used to
target this application to a specific population of set-top boxes. The usage of
this field is governed by the cable operator.

App Instance (Optional) Specifies an application instance identifier for matching. The
notation is: a-zA-Z0-9_\-]*

Tracking Shows a system-supplied string that uniquely identifies this entry after the
filter is configured. This GUID can be passed in SCTE 130 PSNs, in reporting
entries, or the Alarms window.

Private Data (Optional) Specifies an ETV application descriptor private data field. It is a HEX
string.This field is defined as private use and is dependent upon the
Application Type being signaled.

Type Identifies the action to be taken on applications that match the filter criteria.
Type can be whitelist, blacklist or private.
• If specified as whitelist, an application that matches the filter defined by
the App Instance entry is passed in the stream (unless dropped as part of
another process in the mux).
• If specified as blacklist, an application that matches the filter defined by
the App Instance entry is dropped.

Priority of Entry Specifies the order in which entries are processed. It is used when more than
one Application List Entry exists. The default value is priority 1. The lower the
value, the higher the priority. If more than one entry has the same priority, the
order of interpretation is not specified.

6 If the backup program has multiple EBIF, click Add Entry and add one entry for each EBIF.

CAP-1000 Software Guide v4.0 531

Chapter 26 Managing EBIF Merging

Backup Program Configuration

7 Click OK.
EBIF is now configured for use.

Merging
A cable operator may have multiple sources on a given channel. At times, two or more sources
might be competing for both bandwidth and enhancement delivery. In addition to competing
sources, two sources may need to be merged to produce a compliant output. Once an output is
groomed for EBIF, the signaling and data PIDs remain in the output program’s PMT.
A device may need to select from data sources coming from broadcast programming, a local ad
splice that contains a pre-bind enhancement, or a local streamer inserting data that will be
combined with broadcast or spliced audio/video content (late-bind enhancement).
In the case of EBIF, once an output is groomed to carry ETV data, the data PIDs remain in the
PMT although the PES packets for the EBIF data PIDS may or may not be actively streaming from
the source.
When two or more EISS PIDs are merged, they create a single EISS PID on the output
representing both EISS sources. Merging EISS streams preserves the content of each source
through multiplexing.

532 ARRIS Enterprises, Inc.

 Merging

Merging EBIF
You custom groom EBIF and EISS streams from local and network feeds, along with other
streams, to the output. For the first part of EBIF merging, you select the elementary streams, EBIF,
and EISS from one program and custom groom them to the target output program. For the second
EBIF merging, you select only the EBIF and the EISS from one program and custom groom them
to the target output program.
You can perform EBIF merging on both primary and backup programs, if configured.

To merge:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
4 In the Output panel, select the output program(s) you want.
5 Select the EBIF check box.

NOTE Example illustrations show the Diagram view with EISS/EBIF merging from two different input lines, two
different input muxes, and two different input programs.

6 Expand the Component Tree.

7 To custom groom the national streams, do the following:
a In the Input panel, select a program that contains elementary streams, EBIF, and EISS from the
Tree.
b Drag and drop the elementary streams, EBIF, and EISS to the target output program.

CAP-1000 Software Guide v4.0 533

Chapter 26 Managing EBIF Merging

Drag-and-Drop Elementary Streams, EBIF Application, and EISS Stream from First Input

8 To custom groom the local streams, do the following:

a In the Input panel, select an EBIF application and an EISS stream from a program in the Tree.
b Drag and drop the EBIF and EISS to the target output program.

534 ARRIS Enterprises, Inc.

 Merging

Drag-and-Drop EBIF Application and EISS Stream from Second Input

NOTE Streams are grouped together to indicate that they come from the same sources (separated by red lines).

9 In the Primary Streams (or Backup Streams) panel, configure the Network Rule and DPI Rule
options.
The following DPI rules are available: Keep, Drop, Splice/Keep, or Splice/Drop. The following
Network rules are available: Keep or Drop. These rules are validated by the Controller after
“Apply” button is clicked.
10 Click Apply.
11 Click Yes.

Merging Late-bind Ads

Late-bind EBIF refers to applications that are muxed with the program at the splicer. You can
merge EISS/EBIF data to primary or backup streams. You can merge up to two EBIF streams at a
time.

To merge:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.

CAP-1000 Software Guide v4.0 535

Chapter 26 Managing EBIF Merging

4 In the Output panel, select the output program(s) you want.

5 Select the EBIF check box.

NOTE Example illustrations show the Diagram view with EISS/EBIF merging to primary streams.

6 Expand the Component Tree.

7 To custom groom the network streams, do the following:
a In the Input panel, select an EBIF application and an EISS stream from one program in the
Tree.
b Drag and drop the streams to the selected output multiplex.

Drag-and-Drop EBIF Application and EISS Stream from First Input

8 To custom groom the local streams, do the following:

a In the Input panel, select an EBIF application and an EISS stream from a different program in
the Tree.
b Drag and drop the streams to the Primary Streams (or Backup Streams panel if applicable)
panel.

536 ARRIS Enterprises, Inc.

 Merging

Drag-and-Drop EBIF Application and EISS Stream from Second Input

NOTE Streams are grouped together to indicate that they come from the same sources (separated by red lines).

9 In the Primary Streams (or Backup Streams) panel, configure the Network Rule and DPI Rule
options.
The following DPI rules are available: Keep, Drop, Splice/Keep, or Splice/Drop. The following
Network rules are available: Keep or Drop. These rules are validated by the Controller after
“Apply” button is clicked.
10 Click Apply.
11 Click Yes.

Merging Pre-bind Ads

Pre-bind refers to EBIF applications that arrive already muxed with the program (or ad) content.
You can perform pre-bind EBIF from ads if the network doesn’t have EBIF by adding extra output
streams and changing the descriptors to include EBIF and EISS.

NOTE The CAP-1000 will not merge EBIF streams with EBIF streams for pre-bind ads. Any combinations of DPI
rules and network rules that require the CAP-1000 to merge the network EBIF with the ad EBIF is rejected.

CAP-1000 Software Guide v4.0 537

Chapter 26 Managing EBIF Merging

To merge:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
4 In the Output panel, select the output program(s) you want.
5 Select the EBIF check box.

NOTE Example illustrations show the Diagram view with EISS/EBIF merging to primary streams.

6 Expand the Component Tree.

7 To custom groom the national streams, do the following:
a In the Input panel, select an EBIF application and an EISS stream from one program in the
Tree.
b Drag and drop the streams to the selected output multiplex.

Drag-and-Drop EBIF Application and EISS Stream from First Input

c In the Primary panel under Type, right-click an EBIF application and select Add Output
Stream from the Content menu.
d Select the Extra Output Stream.
e In the Descriptors panel, right-click anywhere in the panel and select Add Descriptors.

538 ARRIS Enterprises, Inc.

 Merging

Add Extra Output Stream

f In the Descriptors window, select an EBIF and an EISS descriptor.

Add Descriptors

g Click OK.
8 In the Primary Streams (or Backup Streams) panel, configure the Network Rule and DPI Rule
options.

CAP-1000 Software Guide v4.0 539

Chapter 26 Managing EBIF Bypassing EBIF Filters

The following DPI rules are available: Keep, Drop, Splice/Keep, or Splice/Drop. The following
Network rules are available: Keep or Drop. These rules are validated by the Controller after
“Apply” button is clicked.
9 Click Apply.
10 Click Yes.

Deleting EBIF Applications

To delete:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click .
3 In the Output Mux menu, select the output mux(es) you want.
4 In the Output panel, select the output program(s) you want.
5 In the Primary Streams or Backup Streams panel, right-click the program you want.
6 From the Context menu, select Delete.
7 Click Apply.
8 Click Yes.

Bypassing EBIF Filters

The following procedure explains how to exclude a specific input multiplex from EBIF filtering.
When you enable the EBIF Bypass Filter option for an input mux used in a grooming, filtering is
not applied to EISS applications from this input mux, even if the grooming definition has the EBIF
filters assigned. All applications from this mux are passed to the output independent of the filters.

To bypass:
1 From the CherryPicker Element Manager, click Content Picking > Mux.
2 Select the input multiplex(es) that carry the feeds.
3 Select the EBIF Filter Bypass check box.

540 ARRIS Enterprises, Inc.

 Managing Placeholders for ETV Streams

EBIF Filter Bypass

4 Click Apply.
5 Click Yes.

Managing Placeholders for ETV Streams

ETV provides a way to deploy interactive TV applications to legacy set-top boxes. Instead of
playing out network content to end users, the ETV data streams are spliced into the groomed
output programs and played on a user’s set-top box to allow targeted advertising.
Using the CAP-1000, you create placeholders for ETV data streams, such as EISS signaling and
EBIF applications, so that enhanced content will be played out should it become available in the
ads. To do so, you define extra output data stream placeholders in a groomed output program,
including stream types and descriptors.

Adding Placeholders

To add:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.

CAP-1000 Software Guide v4.0 541

Chapter 26 Managing EBIF Managing Placeholders for ETV Streams

4 To add the EISS signaling trigger, do the following:

a In the Primary Streams or Backup Streams panel, select Add Output Stream from the
Context menu.
The default Extra Output Stream 192 is added to the groom.

NOTE Example illustrations show the Diagram view.

Add Output Stream

b Select the Extra Output Stream.

c In the Descriptors panel, select Add Descriptor from the Context menu.

542 ARRIS Enterprises, Inc.

 Managing Placeholders for ETV Streams

Add Descriptor

d Select Registration ETV1 and ETV-Signaling Time-Shifted Service.

Add Descriptor

e Click OK.

CAP-1000 Software Guide v4.0 543

Chapter 26 Managing EBIF Managing Placeholders for ETV Streams

5 To add the EBIF application, do the following:

a In the Primary Streams or Backup Streams panel, select Add Output Stream from the
Context menu.
The default Extra Output Stream 192 is added to the groom.
b Select the Extra Output Stream.
c In the Descriptors panel, select Add Descriptor from the Context menu.
d Select Registration ETV1 and ETV-BIF.

Add Descriptor

e Click OK.
6 Click Apply.
7 Click Yes.

Deleting Placeholders

To delete:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
4 In the Primary Streams or Backup Streams panel, select the ETV stream you want to delete.
5 From the Context menu, select Delete.
6 Click Apply.
A confirmation window opens.
7 Click Yes.

544 ARRIS Enterprises, Inc.

 CHAPTER 27
Configuring CherryPicker
Redundancy
In This Chapter
• Redundancy Options
• Redundancy States
• CherryPicker Redundancy
• Configuring the Primary CAP-1000 for CPR
• Configuring Backup 1:1 Mode for CherryPicker Redundancy
• Configuring Backup N:1 Mode for CherryPicker Redundancy
• Forcing the Switch to a Backup CAP-1000 (Failover)
• Forcing the Switch to a Primary CAP-1000 (Failback)
• Upgrading the CherryPicker Software in Covering Mode
• Configuring Link Monitoring
• Synchronizing the Database

Redundancy Options
Table 27-1 describes the different types of redundancy that can be configured for CAP-1000
devices operating in your environment.

Table 27-1 Redundancy Options

CherryPicker Redundancy (CPR) Enables a Backup CAP-1000 to replace a Primary CAP-1000 when the Primary
CAP-1000 fails. Two modes are supported: Backup 1:1 mode and Backup N:1
mode. In Backup 1:1 mode, a Backup CAP-1000 protects a single Primary CAP-
1000. In Backup N:1 mode, a Backup device protects one or more Primary CAP-
1000 devices.

Multiplex Redundancy (MRED) Enables program redundancy at the output multiplex level. When the source
for a single groomed program fails on a GigE or DVB-ASI output multiplex with
MRED enabled, all programs from the source multiplex are switched from the
Primary to the backup input multiplex. See Chapter 28, “Configuring
Multiplex Redundancy” for information.

CAP-1000 Software Guide v4.0 545

Chapter 27 Configuring CherryPicker Redundancy Redundancy States

Table 27-1 Redundancy Options (continued)

Program Redundancy (PRED) Enables a backup program to replace an input program when a groomed input
program fails. PRED can be used in conjunction with CPR. For example, PRED
recovers from input stream failures, while CPR recovers from CAP-1000 and
local link failures.
Note: Redundancy settings at the program level are not configurable when
MRED is enabled for program grooming. See Chapter 29, “Configuring
Program Redundancy” for information.
Slates A slate can be defined at the device-level, multiplex level, or program level.
When defined at the device level, the second-level slate is active for every
output program of the device. When defined at the device or multiplex level,
two different file names are requested for two different video slate file
formats. A backup program can also have another program designated as the
slate program for a second-level backup. See Chapter 30, “Configuring
Slate Redundancy” for information
Ad Insertion Protection (AIP) Enables protection for unicast ad insertion input feeds. AIP can be used in
conjunction with PRED and output mux mirroring to provide link redundancy for
ad insertion. See Chapter 31, “Configuring Ad Insertion
Protection” for information.
Output Port Redundancy Mirroring is independent of CPR, but it can coexist with CPR to provide high
(Mirroring) availability for the CAP-1000. See Chapter 32, “Configuring Port
Mirroring” for information.

This chapter explains how to configure CPR. Subsequent chapters in this guide explain how to
configure the other types of redundancy.

Redundancy States
The state of a groom operation in a CPR, PRED, or MRED is represented by program icons.
Table 27-2 shows examples of the different icons that can appear in the GUI when configuring
redundancy.

Table 27-2 Redundancy States

State Description

Primary groomed and playing (no backup).

Backup groomed and playing via auto PRED.

546 ARRIS Enterprises, Inc.

 Redundancy States

Table 27-2 Redundancy States (continued)

State Description

Backup groomed and playing via manual override PRED.

Primary groomed and playing with encrypted content (no backup).

Primary groomed, but not playing (scheduled to play in the future).

Both primary and backup not groomed.

Both primary and backup not groomed. Manual override to backup via MRED.

Primary groomed with some errors (check the tool tips).

Slate groomed and playing. Manual override to backup via PRED.

Primary program, backup program, and slate not groomed. Manual override to slate via MRED.

Slate defined at program level.

Primary program, backup program, and slate defined and applied.

CAP-1000 Software Guide v4.0 547

Chapter 27 Configuring CherryPicker Redundancy CherryPicker Redundancy

Table 27-2 Redundancy States (continued)

State Description

Primary program and slate defined and applied.

CherryPicker Redundancy
System-level redundancy, also referred to as CherryPicker Redundancy (CPR), enables a Backup
CAP-1000 to automatically replace a Primary CAP-1000 when the Primary system fails. CPR
provides both system-level redundancy and local link monitoring. If the Primary CAP 1000 fails
or one of its local links fails, then the Backup replaces the Primary provided the Backup and its
links are healthy.
You configure CPR for the Primary and Backup CAP-1000 in the Redundancy window of the
CherryPicker Element Manager for the respective devices.

CPR Redundancy

Requirements
• The Primary CAP-1000 devices must have a valid license key for CPR. No license is needed
for the Backup CAP-1000.
• The hardware capability and configuration of the Backup CAP-1000 must be “super set” of
the hardware on the Primary.
• The Data Flash on the Backup CAP-1000 must have enough space to archive files from the
Primary CAP-1000. If Backup N:1 mode is used, the Backup CAP-100 must have enough
space to archive files from all Primary CAP-1000s defined in the backup group.
• The software version on the Primary CAP-1000 must match the software version on the
Backup. A mismatch of software version is allowed if the Backup CAP-1000 is currently
covering for the Primary, but only a failback without file sync is allowed.

548 ARRIS Enterprises, Inc.

 CherryPicker Redundancy

• The Backup CAP-1000 must have enabled network ports for each of the enabled Primary
ports. At least one network interface must enabled and be marked for monitoring.
• For each network port on the Primary that has the OSPF routing protocol, the corresponding
network port on the backup must also be configured with the OSPF routing protocol.

Modes
CPR operates in one of two modes: Backup 1:1 mode or Backup N:1 mode. In Backup1:1 mode, a
Backup CAP-1000 protects a single Primary CAP-1000. In Backup N:1 mode, a Backup
CAP-1000 protects one or more Primary CAP-1000. Up to four Primary CAP-1000 devices can be
protected in Backup N:1 mode (for example, Backup 4:1).
In Backup 1:1 mode, the Backup can detect a failure and replace the Primary within one second. In
Backup N:1 mode, the time required to make this transition ranges from 20 to 30 seconds, or
faster, depending on the load defined for the device. In either Backup 1:1 or Backup N:1 mode, the
time for an ad server to transition from the failed Primary to the Backup is expected to take from
one to two minutes. If CPR is not configured, the CAP-1000 operates in Independent mode.
The CAP-1000 v3.1 includes a new DSP module (CAP1-DSP-BLADE-2). The DSP provides all
functionality of the prior DSP module, plus dual Ethernet ports for management redundancy and
the capacity to perform Conditional Access (CA) encryption in future releases.

CR-DSP Module LEDs

The CR-DSP module on the front of the CAP-1000 has four LEDs:
• BOOT—housekeeping boot LED
• STS—housekeeping Alarm LED
• ACT—activity LED
• PWR—power LED

STS
IOA

ACT
4

CR-DSP Module LEDs

CAP-1000 Software Guide v4.0 549

Chapter 27 Configuring CherryPicker Redundancy CherryPicker Redundancy

The ACT LED provides status about CPR systems. See Table 27-3 on page 550 for information.

Table 27-3 DSP Module LEDs

BOOT - Housekeeping Boot LED

Steady Green CPU running with active CPU images.

Blinking Green CPU running with factory/backup CPU images.

Steady Amber Booting with active CPU images.

Blinking Amber Booting with factory/backup CPU images.

STS - Housekeeping Alarm LED

Blinking Amber Safety related alarm:

Fire condition

Steady Amber Non-safety related alarm:

• DC failure
• Midplane insertion is incorrect
• Over-temperature [Normal range 0 to +50° C]
• Input/Output adapter not present or not working properly

Steady Green All conditions normal.

ACT - Activity LED

Blinking Green The DSP module initialized. The heartbeat shows module activity. The CAP-
1000 is configured in one of the following modes:
• Independent mode
• CherryPicker Redundancy (CPR), primary, in Unprotected or Protected mode
• CherryPicker Redundancy (CPR), backup, in Covering mode
Note: an CAP-1000 in Independent mode is indicated by a blinking green LED.

Blinking Amber The DSP module initialized. The heartbeat shows module activity. The CAP-
1000 is configured in one of the following modes:
• CherryPicker Redundancy (CPR), Primary, in Covered mode
• CherryPicker Redundancy (CPR), Backup, in Idling or Protecting mode

Blinking Amber Off System / software error.

Green Off

PWR - Power LED

Off Power off.

Green Power on.

Blinking Amber Internal low level error.

550 ARRIS Enterprises, Inc.

 CherryPicker Redundancy

Failure Detection
Failure detection on the Primary CAP-1000 is provided by the Health Monitor. The Health
Monitor plays a role in detecting power failures and local link failures, Core failures, and
Controller failures. The Controller communicates with the local Health Monitor using TCP/IP
over port 6001. The Health Monitor on the Primary CAP-1000 communicates with the Health
Monitor on the Backup CAP-1000 using UDP protocol over port 6000. The communication is
repeated over all enabled GigE port for redundancy.

Switchover Conditions
The software triggers a switch over from the Primary CAP-1000 to the Backup CAP-1000 using
the following conditions:
• A power failure resulting from a bad power supply, a shutdown from overheating, a loss of
external power, or any other cause.
• A local link failure resulting in the inability to transmit or receive IP traffic over the link to the
other (Primary or Backup) CAP-1000.
• A Core software failure resulting in a crash or hang of the Core process (Backup 1:1 mode
only).
• A Controller failure, such as a crash or a hang, resulting in the inability to connect to an ad
server, a GUI client, or an SNMP client.

States for Primary CAP-1000 Devices

The following table shows the states for Primary CAP-1000 devices.

Table 27-4 States for Primary CAP-1000 Devices

State Description

Unprotected A Primary CAP-1000 in the Unprotected state can join a CPR group. If a Primary has received an
invitation to join a CPR group, but fails to complete the joining process (e.g., due to being
incompatible with the Backup or to the temporary suspension of CPR), or is released from a CPR
group, then the Primary remains in the Unprotected state and can accept an invitation from
another Backup CAP-1000. If the CAP-1000 is not configured in primary operation mode, all
invitations are rejected.

Protected A Primary in the Protected state is in a CPR group and is being monitored by a Backup CAP-1000. A
Primary CAP-1000 that is Protected notifies the Backup of all file changes on the Primary. Changes
made to the Primary CAP-1000 are continuously synchronized to the archive on the Backup.

CAP-1000 Software Guide v4.0 551

Chapter 27 Configuring CherryPicker Redundancy CherryPicker Redundancy

Table 27-4 States for Primary CAP-1000 Devices (continued)

Covered When a Primary CAP-1000 is in the Covered state, its identity and function are assumed by the
Backup. When the Primary is being covered by the Backup, the Primary itself can be up or down. If
it's up, then it doesn't output any MPEG packets, and its virtual IP addresses are released. Limited
configuration of the Primary is allowed while it is in Covered state. While the Primary is in this
state, most configuration changes for the Primary should be performed via the Backup that is
covering for the Primary. However, the user is allowed to failback via the Primary CAP-1000
interface.

NA The CAP-1000 is operating in Independent mode. CPR is not configured.

Transition States for Backup CAP-1000 Devices

The following table shows the states for Backup CAP-1000 devices.

Table 27-5 Transition States for Backup CAP-1000 Devices

States Description

Idle This is the initial state at power-up/restart. No Primary CAP-1000 devices are protected or
covered. If there are no Primary CAP-1000 devices in the CPR group, the Backup CAP-1000 remains
in this state. The transition out of the Idling state occurs when at least one of the following
conditions is met.
• The last known state for a Primary CAP-1000 is covered and it cannot be contacted to
determine its present state. In this case, the Backup resumes the Covering state. This situation
can only occur during start up of the Backup CAP-1000.
• A Primary CAP-1000 is enabled and has accepted a request to join a CPR group. In this case, the
Backup transitions to Protecting state. For a Backup 1:1 CAP-1000, the state is Protecting-Hot.
For a Backup N:1 CAP-1000, the state is Protecting-Warm.

Protecting In the Protecting state, a Backup is monitoring one or more primaries for failure. Depending on the
CPR mode, the protecting state is further qualified as:
• Warm standby—This state of operation is used when the Backup CAP-1000 is protecting a
Primary in a Backup N:1 configuration. In this state, the Backup Controller is idle and the Health
Monitor is ready and waiting to respond to a detected failure. When a failure is detected, the
Backup transitions to the Covering state.

• Hot standby—This state of operation is used when the Backup CAP-1000 is protecting a
Primary in a Backup 1:1 configuration. In this state, the Backup Controller and the Core are
close to the fully functioning status of the Primary. Appropriate database links are generated
and the database is loaded, input and output muxes are established, groomings are applied,
and rate-shaping is active. During this state, the only unsupported functions are: (1) the virtual
IP addresses are still held by the Primary (no ad insertion is available on the Backup) and (2) the
MPEG output is disabled.

Covering In the Covering state, the Backup CAP-1000 is functioning in place of a Primary CAP-1000. When a
Backup CAP-1000 is operating in a Backup N:1 configuration, all other Primary CAP-1000 devices
in the group are released while the Backup is in the Covering state.

552 ARRIS Enterprises, Inc.

 CherryPicker Redundancy

Backup Group and Primary Definitions

The following table describes the Backup group and Primary definitions.

Table 27-6 Backup Group and Primary Definitions

Definition Description

Unprotected Indicates an initial state before a request for backup has been made. A Primary CAP-1000 in an
Unprotected state can join a CPR group.

Protected Indicates a CPR session has been activated between the Backup and the Primary CAP-1000. The
Primary is being monitored for failure conditions.

Covered Indicates the Backup CAP-1000 has been notified of a failure and has assumed the role of the
failed Primary. When a Primary CAP-1000 is in the Covered state, its identity and function are
assumed by the Backup.

Released Indicates the Backup CAP-1000 has assumed the role of one Primary in the group. All other
Primaries defined as part of the group have been released, while the failed Primary has been
covered.

Unavailable Indicates the Backup CAP-1000 could not open a connection to the Primary to make a request.

Busy Indicates the Primary CAP-1000 has rejected the backup request. This status can occur because
the CAP-1000 is transitioning to another state, the Primary CAP-1000 is already participating in
another backup session, or CPR might be temporarily suspended on the Primary CAP-1000.

Not Configured Indicates the Primary CAP-1000 rejected the backup request because a license has not been
installed, or the system has not been enabled for redundancy.

Incompatible Indicates a hardware, software, or configuration mismatch.

Configuring the Management Port for the Ad Server

To include an ad server in the CPR configuration, you configure the virtual IP addresses on the
Primary CAP-1000. The ad server will be “pointed” to these virtual IP addresses. You must define
a virtual address for all ports that will be used to communicate the SCTE 35/30 messages, as well
as all ports that will be used to receive ad feeds.
When the Primary CAP-1000 fails, connections between the Primary CAP-1000 and the ad server
are broken. The virtual IP addresses are moved to the Backup CAP-1000. After approximately 1-2
minutes, the ad servers are re-established and ad insertion continues on the Backup CAP-1000.

CAP-1000 Software Guide v4.0 553

Chapter 27 Configuring CherryPicker Redundancy Configuring the Primary CAP-1000 for CPR

Configuring the Primary CAP-1000 for CPR

This section explains how to configure a CAP-1000 as a Primary device in CPR.

IMPORTANT Before the Primary CAP-1000 can be protected, at list one port must be enabled for link monitoring. See
section,“Configuring Link Monitoring,”on page 562 for more information.

To configure the Primary CAP-1000:

1 Log in to the CAP-1000 you want to configure as the Primary.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
3 In the Mode menu, select Primary.

NOTE To configure a Primary CAP-1000, a valid license key for CPR must be installed on the device.

4 To enable the Primary CAP-1000 to automatically fail back when a problem has been resolved,
configure the following parameters.

Table 27-7 Auto Failback Options

Enable Auto Fail Back Enables auto fail back for the Primary CAP-1000. The default is disabled.
Note: If this option is not enabled, manual intervention is required to fail back.

Checking Frequency Sets the frequency by which the health check is performed. When the check is
expressed in minutes, the valid values are 10 -720. When the values are
expressed in days, the valid values are 1 - 58.

Start Checking On Sets the date/time in which the primary health check period starts. Click the
clock icon to change the time. This value is used in conjunction with the
Checking Duration (Minute) parameter. If the Controller is running at the
beginning of the window, the health check is performed then. If the Controller
is started/restarted at any time within the defined window, the health check is
performed.

Checking Duration (Minute) Sets the duration of the primary health check period. The valid value is
between 1-1439 minutes. This parameter is used in conjunction with the Start
Checking On parameter. If the Controller is running at the beginning of the
window, the health check is performed then. If the Controller is
started/restarted at any time within the defined window, the health check is
performed.

See section,“Forcing the Switch to a Primary CAP-1000 (Failback),”on page 559 for more
information.
A warning window opens.
5 Select Yes to continue.
The CherryPicker Element Manager closes and the Controller restarts.

554 ARRIS Enterprises, Inc.

 Configuring Backup 1:1 Mode for CherryPicker Redundancy

6 After a few minutes, log in to the Primary CAP-1000.

7 From the CherryPicker Element Manager, click Setup > Redundancy.
After a few minutes, the Redundancy window for the CAP-1000 looks similar to the following.
The CPR state has changed to “CPR Primary: Unprotected” because configuration is not yet
complete.

Primary CAP-1000

Configuring Backup 1:1 Mode for CherryPicker Redundancy

This section explains to configure a CAP-1000 for Backup 1:1.

IMPORTANT Before the Primary CAP-1000 can be protected, at list one port must be enabled for link monitoring. See
section,“Configuring Link Monitoring,”on page 562 for more information.

To configure Backup 1:1 mode:

1 Log in to the CAP-1000 you want to configure as the Backup.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
3 In the Mode menu, select Backup 1:1.
A warning window opens.
4 Select Yes to continue.
The CherryPicker Element Manager closes and the Controller restarts.
5 After a few minutes, log in to the Backup 1:1 CAP-1000.
6 From the CherryPicker Element Manager, click Setup > Redundancy.
7 Enter the Primary CAP-1000 IP Address and click Apply.

CAP-1000 Software Guide v4.0 555

Chapter 27 Configuring CherryPicker Redundancy Configuring Backup N:1 Mode for CherryPicker Redundancy

Backup 1:1 CAP-1000

IMPORTANT Before the Primary CAP-1000 can be protected, at list one port must be enabled for link monitoring. See
section,“Configuring Link Monitoring,”on page 562 for more information.

After a few minutes, the Redundancy window for the CAP-1000 looks similar to the following.
The CPR state has changed to “CPR Backup 1:1:Protecting Hot.”

Backup 1:1 CAP-1000 Protecting Hot

Configuring Backup N:1 Mode for CherryPicker Redundancy

This section explains to configure a CAP-1000 for Backup N:1.

To configure Backup N:1 mode:

1 Log in to the CAP-1000 you want to configure as the Backup.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
3 In the Mode menu, select Backup N:1.

556 ARRIS Enterprises, Inc.

 Configuring Backup N:1 Mode for CherryPicker Redundancy

A warning window opens.

4 Select Yes to continue.
The CherryPicker Element Manager closes and the Controller restarts.
5 After a few minutes, log in to the Backup N:1 CAP-1000.
6 From the CherryPicker Element Manager, click Setup > Redundancy.

Backup N:1 CAP-1000s

7 To add Backup CAP-1000s, do the following:

a Click Add.
b Enter the Primary CAP-1000 IP Address.
c Click Apply.
d Repeat for each Primary CAP-1000 you want to add to CPR.

IMPORTANT Before the Primary CAP-1000 can be protected, at list one port must be enabled for link monitoring. See
section,“Configuring Link Monitoring,”on page 562 for more information.

After a few minutes, the Redundancy window for the CAP-1000s look similar to the following.
The CPR state has changed to “CPR Backup N:1:Protecting Warm.”

CAP-1000 Software Guide v4.0 557

Chapter 27 Configuring CherryPicker Redundancy Forcing the Switch to a Backup CAP-1000 (Failover)

Backup N:1 CAP-1000s Protecting Warm

Forcing the Switch to a Backup CAP-1000 (Failover)

A failover transition occurs when a failure is detected by the Backup CAP-1000 or when a user
initiates a manual failover from the Primary CAP-1000. If a Backup CAP-1000 detects a failure
for a Primary CAP-1000, the Backup CAP-1000 transitions to Covering state.
When manually forcing a failover, a file sync operation is automatically performed before the
failover is completed.
If the communication problem is due to a failure in the interconnecting network, this could result
in both the Backup and the Primary CAP-1000 devices broadcasting the same information. The
use of RIP advertisements with different metrics on the Primary and Backup allows networks to
implement fencing schemes to prevent duplicate packets from arriving at final destinations. See
section,“Configuring Link Monitoring,”on page 562 for more information.

NOTE The RIP Metric Backup parameter applies when the virtual IP is used on the Backup CAP-1000. Multicast
fencing down stream of the Primary and Backup devices can be implemented by using different values on
the RIP metric (value used from the Primary) and the RIP metric Backup (value used from the backup).

The RIP metric value is sent out on the interface of the primary CAP-1000 when a primary IS NOT covered
by the backup. A value of 0 indicates no RIP is sent. A RIP value should only be used if the OSPF value is
false.

To force a switch:
1 Log on to the Primary CAP-1000.
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 Click Fail Over.

558 ARRIS Enterprises, Inc.

 Forcing the Switch to a Primary CAP-1000 (Failback)

Primary CAP-1000

A warning window opens.

3 Click Yes.

Forcing the Switch to a Primary CAP-1000 (Failback)

The transition from Covered to Unprotected is called failback. During failback, the CAP-1000
compares software versions; if compatible, it performs a reverse data synchronization before
completing the process. Files are obtained from the Backup archive and restored on the Primary.
The virtual IP addresses are relinquished by the Backup CAP-1000 and re-established on the
Primary CAP-1000. This causes any ad server connections to fail. The necessary ARP and RIP
messages are sent to the appropriate gateways.

NOTE Failback is not be allowed if the Primary local links for enable ports are not up or the Core is down.

The Primary CAP-1000 transitions to the Hot Standby state. The MPEG output is handed off from
the Backup CAP-1000to the Primary. The backup GigE outputs go into standby mode and the
primary GigE outputs go into active mode. The ad server, if present, reconnects to the Primary
CAP-1000 within 1-2 minutes.
Two options are available for failback: auto failback and manual failback.

Auto Failback
You can enable the Primary CAP-1000 to automatically fail to the Backup CAP-1000 using the
Auto Fail Back option on the Redundancy tab. With this option, you configure the frequency, start
time, and duration in which a primary health check is performed on the Primary CAP-1000. If an
error occurs that meets the defined parameters, the Primary CAP-1000 automatically fails over to
the Backup CAP-1000.

CAP-1000 Software Guide v4.0 559

Chapter 27 Configuring CherryPicker Redundancy Forcing the Switch to a Primary CAP-1000 (Failback)

Auto Fail Back

To enable auto failback, See section,“Configuring the Primary CAP-1000 for CPR,”on page 554
for more information.

Manual Failback
You can manually trigger a failback when you determine that the Primary CAP-1000 is ready to
resume service. It is recommended that you perform a failback when a minimal service
interruption can be permitted. To manually failback, use the procedure in this section.

To force the switch:

1 Log on to the Primary CAP-1000.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
3 Click Fail Back.

Primary CAP-1000

560 ARRIS Enterprises, Inc.

 Upgrading the CherryPicker Software in Covering Mode

A window opens.

Select Failback Options

4 Do one of the following:

• Select the Copy option to copy files only if changes have been to the Primary configuration
when it was being hosted by the Backup.
• Clear the Copy option and do not copy files if the configuration might be incompatible due to
a software upgrade.
5 Click OK.

Upgrading the CherryPicker Software in Covering Mode

When the Backup CAP-1000 is in Covering mode, you cannot perform software updates using the
GUI, command line prompt, or SNMP. To work around this issue, use the following procedure.

To upgrade:
1 Log on to a Backup CAP-1000.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
3 Click Fail Back.
A window opens.

Select Failback Options

4 Clear the Copy option and do not copy files if the configuration might be incompatible due to a
software upgrade.
5 Click OK.
6 Upgrade the software. Go to section,“Upgrading the CherryPicker Software,”on page 102 for
information.

CAP-1000 Software Guide v4.0 561

Chapter 27 Configuring CherryPicker Redundancy Configuring Link Monitoring

Configuring Link Monitoring

At least one port must have the Monitoring Link option enabled before the Backup CAP-1000 will
protect the Primary CAP-1000. Heartbeats are sent between each enabled link on the Primary
CAP-1000 and the Backup CAP-1000. One type of link failure occurs when all links fail. Another
type of link failure occurs when individual links fail. To monitor individual links for failure,
enable the “Monitor Link” option for the individual ports.

Enabling Link Monitoring

To enable link monitoring:
1 Log on to the Primary CAP-1000.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
Ethernet port parameters display in the bottom panel.

Monitor Link

3 To monitor the link, do the following:

a Scroll the bottom panel until the Monitor Link column appears.
b To test the GigE input port for failure when the Primary CAP-1000 is in a Protected state,
select the Monitor Link check box. If the port fails, a failover is triggered.
4 To test both GigE ports for failure when the Primary CAP-1000 is in a Protected state, select the
Combine Peer Port check box.

562 ARRIS Enterprises, Inc.

 Configuring Link Monitoring

The Combine Peer Port option is only applicable if ports have been paired. Enabling this option
treats the paired ports as a single port for failure detection purposes. Both ports must fail before a
failover occurs.
This parameter is used to combine peer ports on the IOA for determining failover in a CPR
configuration. When selected, Monitor Link and Combine Peer Port check boxes are
automatically selected for the Peer Port option. If both ports fail, a failover is triggered.

NOTE Combine Peer Port can be used in conjunction with AIP and port mirroring. See Chapter 31,
“Configuring Ad Insertion Protection” for more information.

5 To set a single routing metric (hop count), scroll to the RIP Metric parameter and select a value
from the menu.
This parameter is used to measure the distance between the source and a destination network in a
CPR configuration. RIP prevents routing loops from continuing indefinitely by implementing a
limit on the number of hops allowed in a path from the source to a destination. The maximum
number of hops in a path is 15. The default is Off.

NOTE The RIP Metric Backup parameter applies when the virtual IP is used on the Backup CAP-1000. Multicast
fencing down stream of the Primary and Backup devices can be implemented by using different values on
the RIP Metric (value used from the Primary) and the RIP Metric Backup (value used from the backup).

The RIP Metric value is sent out on the interface of the primary CAP-1000 when a primary IS NOT covered
by the backup. A value of 0 indicates no RIP is sent. A RIP value should only be used if the OSPF value is
false.

6 Click Apply.
7 Click Yes.

Disabling Link Monitoring

IMPORTANT If CPR (either 1:1 or N:1 mode) is used in conjunction with a common management network switch (e.g.,
Primary and Backup CAP-1000 management ports connected to the same switch), do not enable link
monitoring for the management port on the CAP-1000. Under some circumstances, enabling link monitoring
on the management port can cause loss of video in the event of management network outages (such as a
switch failure).

To disable link monitoring:

1 Log on to the Primary CAP-1000.
2 From the CherryPicker Element Manager, click Setup > Redundancy.
Ethernet port parameters display in the bottom panel.
3 Scroll the bottom panel until the Monitor Link column appears.
4 Clear the Monitor Link check box.

CAP-1000 Software Guide v4.0 563

Chapter 27 Configuring CherryPicker Redundancy Synchronizing the Database

5 Clear the Combine Peer Port check box.

6 Click Apply.
7 Click Yes.

Synchronizing the Database

The Status bar in the CherryPicker Element Manager shows the database status and enables you to
synchronize it among redundant systems, if needed. File sync status only appears for the Primary
device under CPR.

Sync Database

Clicking the database icon lets view read/write status messages and you immediately sync the
database. The following table describes the different states of the database.

Table 27-8 Database Status

Icon Color Description

Green The databases among CherryPicker redundant systems are in sync. There are no pending
writes and the database is “clean.”

Yellow The database is out-of-sync because it has pending writes or is “not clean.”

Red The most recent writes to the database caused an error. Refer to the tool tip for a description
of the problem.

564 ARRIS Enterprises, Inc.

 Synchronizing the Database

When the database is out of sync, double-clicking the icon sends a request to synchronize the
database. A successful synchronization causes the following message to appear:

Operation Completed

CAP-1000 Software Guide v4.0 565

Chapter 27 Configuring CherryPicker Redundancy Synchronizing the Database

566 ARRIS Enterprises, Inc.

 CHAPTER 28
Configuring Multiplex Redundancy

In This Chapter
• Multiplex Redundancy
• Configuring MRED on Output Multiplexes
• Forcing the Switch to Backup Programs
• Forcing the Switch to Primary Programs

Multiplex Redundancy
Multiplex redundancy (MRED) enables program redundancy at the output multiplex level on GigE
and DVB-ASI outputs. When a single groomed program fails on an output multiplex with MRED
enabled, all programs are switched from the primary input multiplex to the backup input multiplex.

Mux Redundancy

You can also manually force a failover to the backup input muxes, or failback to the primary input
muxes, should it become necessary.

CAP-1000 Software Guide v4.0 567

Chapter 28 Configuring Multiplex Redundancy Multiplex Redundancy

Requirements
You configure MRED at the output multiplex level in the Content Picking > Mux window. You
need at least two input multiplexes: a primary and a backup. You also need to either create at least
one output multiplex, or use an existing output multiplex, and then groom the programs from the
primary input multiplex to the output multiplex.

Primary input mux

Backup input mux

Output mux with

groomed programs

MRED Configuration

To enable MRED, the primary and backup multiplexes must be in sync. The input multiplexes are
considered in sync according to the following statements:
• The number of programs and program numbers are the same for both the primary and backup
input multiplex.
• Corresponding programs on primary and backup input multiplexes are matched by program
number.
• The same elementary stream on a program from the primary multiplex must also exist on the
corresponding program of the backup multiplex. For instance, a given stream for a program
from the primary multiplex is validated against the same stream retrieved from the matching
program of the backup multiplex by elementary PID. The streams are considered to be
synchronized when having the identical stream type.
• The input multiplexes themselves need not be identical. For instance, the transport stream ID
for the two multiplexes can be different.
• Each input program of the primary multiplex is associated with each input program of the
backup multiplex based on the program ID. For instance, program 1 of the primary input
multiplex is associated with program 1 of the backup input multiplex for redundancy.
• MRED only allows grooming from the primary input multiplex to the designated output
multiplex. Grooming from any other input sources disables MRED.

568 ARRIS Enterprises, Inc.

 Multiplex Redundancy

• Only grooming from programs for which a synchronized backup program has been found is
allowed. If a proper program from the backup multiplex does not exist, the groom operation
disables MRED.

Constraints
• If the selected primary and backup input multiplexes are invalid, they are considered “out of
sync.” If out of sync, the MRED configuration is rejected and an error dialog provides an
explanation about the cause of the failure. MRED can only be enabled when the primary and
backup input multiplexes are initially in sync.
• If the output multiplex contains any previously groomed programs that were not from the
primary input multiplex, the MRED configuration process is stopped.
• If a backup program is currently playing on an output multiplex participating in PRED, MRED
cannot be configured.
• If you disable MRED, all the settings are removed, including the assigned backup programs.
• If you apply a configuration file to an MRED enabled mux, MRED is disabled. If the
configuration contains MRED parameters, MRED applies only if there are no conditions
violating MRED requirements.

Grooming
The following constraints apply when grooming to MRED muxes:
• Any groomed programs that already have PRED defined have their settings overridden in
favor of MRED during configuration.
• Any program groomed from the primary input multiplex after MRED configuration is done
automatically inherits MRED settings and is assigned a corresponding program from the
backup multiplex.
• You cannot edit PRED settings for any program groomed when MRED is enabled.
• During the out-of-sync periods for the primary and the backup input multiplexes, you can
choose to recover programs by grooming from different input sources. Choosing to do so
disables MRED.
• If grooming from the primary during the out-of-sync period in which a synchronized program
from the backup multiplex is not found, you have the option to disable MRED and proceed
with the grooming operation.
• Since the programs from the primary and backup multiplexes are associated based on the
program ID, custom grooming elementary streams only within the same input program is
allowed. This type of grooming is referred to as “PID blocking”. Any other custom grooming
disables MRED.
• Switched and passed PID grooming is not supported when MRED is enabled.

CAP-1000 Software Guide v4.0 569

Chapter 28 Configuring Multiplex Redundancy Multiplex Redundancy

Synchronization and Alarms

The CAP-1000 checks the synchronization of primary and backup input multiplexes when
PAT/PMT versions change. If the content is out-of-sync, then a synchronization alarm is raised and
a trap notification is sent out.When both multiplexes are synchronized thereafter, the
synchronization alarm is cleared and a trap is sent out for a cleared synchronization alarm.

NOTE The synchronization alarm is only for notification purposes. The alarm does not affect how the primary
multiplex will failover to the backup multiplex, or vice versa.

You can choose to recover from out-of-sync periods by grooming from other input sources, or
restoring the programs by applying a configuration file. This action effectively disables MRED
and clears any synchronization alarms.

Failover
When a single groomed program is determined to be in corrupted state when MRED is configured,
every groomed program from the primary input multiplex is switched to the corresponding
program from the backup multiplex. This switching occur regardless of whether an alarm has been
raised indicating that the primary and backup input multiplexes are out of sync.
If DPI is in progress, the switch is delayed, allowing the ad breaks to complete before switching to
the corresponding program of the backup multiplex. Only programs currently doing DPI are
delayed.

Failback
You cannot failback to the primary programs until all groomed primary input programs are in a
good state, with the exception of programs that are currently doing DPI. All switching back is
delayed until all current DPI sessions are complete.

Slates
The CAP-1000 enables manual switching to slates at the multiplex level for maintenance
purposes. When defined at the multiplex level, two different file names are requested for two
different video slate file formats: MPEG-4/AVC SD and MPEG-2 SD. The software automatically
selects the files based on the live video stream format of the program. See for Chapter 30,
“Configuring Slate Redundancy,” more information.

570 ARRIS Enterprises, Inc.

 Configuring MRED on Output Multiplexes

Monitoring Backup Input Programs While Primary is Playing

All ASI and GigE input multiplexes, except for the ad-insertion multiplexes, are monitored for
PAT byte count every 15 seconds to determine if the input multiplexes are active or inactive. An
alarm is raised when a backup input program disappears from the PAT. The alarm is cleared when
the backup input program re-appears while the primary input program is playing.
The format of the alarm is “Output program loses its backup input program <output param>
<backup param>” where <output param> is Output line ID / output mux ID / output program ID
and <backup param> is Input line ID / input mux ID / input program ID.

Configuring MRED on Output Multiplexes

You can configure MRED on Gigabit Ethernet or DVB output multiplexes.

NOTE The example in this section shows Gigabit Ethernet output multiplexes.

To configure MRED:
1 Create at least one pair of primary and backup input multiplexes that are in sync (contain the same
type and number of programs). See Chapter 14, “Configuring Multiplexes” for more information.

Primary input mux

Backup input mux

Input Muxes

CAP-1000 Software Guide v4.0 571

Chapter 28 Configuring Multiplex Redundancy Configuring MRED on Output Multiplexes

2 Create at least one output multiplex. See Chapter 14, “Configuring Multiplexes” for more
information.

Output mux

Output Mux

3 Do one of the following:

• From the CherryPicker Element Manager, click Content Picking > Mux.
• From the CherryPicker Element Manager, click Setup > Redundancy, click the
MRED/PRED icon ( ) in the toolbar, and then click Configure MRED.
4 Expand the Component Tree.
5 In the Component Tree, select the Gigabit Ethernet output multiplex you want.
6 In the Output panel, scroll until you see the Mux Redundancy parameter, and then select the
parameter.

572 ARRIS Enterprises, Inc.

 Configuring MRED on Output Multiplexes

Mux Redundancy

7 In the Output panel, scroll until you see the Primary Input Mux parameter. Right-click the cell
and select the primary input multiplex you want.

MRED Primary Input Mux

8 In the Output panel, scroll until you see the Backup Input Mux parameter. Right-click the cell
and select the backup input multiplex you want.

IMPORTANT The backup input mux must have the same type and number of programs as the primary input mux.

CAP-1000 Software Guide v4.0 573

Chapter 28 Configuring Multiplex Redundancy Configuring MRED on Output Multiplexes

MRED Backup Input Mux

9 Configure any other MRED parameters you want.

Table 28-1 Multiplex Redundancy Parameters

Mux Redundancy Select this option to enable MRED.

Primary Input Mux Select the input multiplex containing the groomed primary programs.

Error Period (1-100s) Specifies the length of time during which the primary cannot recover from
error. If the primary cannot recover by the end of the interval, switching to
backup occurs. If the primary can recover, no switching occurs. The options
are: Min 1 second (in 1 second increments) / Max 100 seconds. The default is
2 seconds.

Underflow Streams Configures underflow alarms to indicate that data has been lost in a stream.
The options are:
• Any Video/Audio Stream Underflow—enables the backup slate to switch
over if any video or audio stream underflows.
• All Video/Audio Streams Underflow—enables the backup slate to switch
over only if all video and audio streams underflow.
• Video or First Audio—enables the backup program to switch if the video
or the first audio stream underflows. The first audio is the first audio
elementary stream in PMT of output program.
• Video Only—enables the backup slate to switch over if any video stream
underflows.
• First Audio Only—enables the backup slate to switch over if the first
audio stream underflows.
Note: Data and CUEI streams are not checked.

574 ARRIS Enterprises, Inc.

 Configuring MRED on Output Multiplexes

Table 28-1 Multiplex Redundancy Parameters (continued)

Switch on Underflow • Immediate—Specifies that switching to the backup input multiplex

should occur immediately.
• After Alarm Interval—Specifies that switching to the backup input
multiplex should occur after the error period.

Backup Input Mux Select the backup multiplex containing the groomed backup programs.

Auto Switch Back Select to automatically switch back to the primary program when it is
restored.

Error Free Period (7-100) Specifies the length of time in which the primary program must be error-free
before a switch is made back to the primary source. If errors are detected
and they cannot be resolved, the CAP-1000 does not switch back to the
primary program. The CAP-1000 remains with the backup program instead.
The options are: Min 7 seconds / Max 100 seconds. The default is 12
seconds (in 1-second increments). The longer the period of time, the more
certain you can be that the primary program is error free.

10 Repeat step 5 to step 9 for each multiplex you want to configure for MRED.
11 Click Apply.
12 Click Yes.
13 Groom programs from the primary input multiplex(es) to the output multiplex(es). See Chapter 18,
“Grooming Programs” for more information.
14 To view the MRED status, do one of the following:
a Click Setup > Redundancy.
The MRED panel shows the protected multiplex and the PRED panel shows the protected
programs on the multiplex.

Mux Redundancy

CAP-1000 Software Guide v4.0 575

Chapter 28 Configuring Multiplex Redundancy Forcing the Switch to Backup Programs

b Click Content Picking > Grooming.

The Output panel shows the protected multiplex and the Programs panel shows the protected
programs on the multiplex in blue highlight.

MRED Redundancy

Forcing the Switch to Backup Programs

The CAP-1000 allows you to manually force programs to backup or primary at the output rate-
shaped multiplex level. The entire switch procedure takes no more than five seconds. During the
period of enforced “force to backup,” the CAP-1000 will not switch back to the primary. The
“force to backup” condition persists across system reboots and farmer restarts.

To force the switch:

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 Click the MRED/PRED icon ( ) in the toolbar.
3 In the Mux Redundancy panel, select the output multiplex(es) you want.
4 Click To Backup.

576 ARRIS Enterprises, Inc.

 Forcing the Switch to Primary Programs

The switchover occurs and the backup programs on the selected multiplexes are now active.

Force to Backup

Forcing the Switch to Primary Programs

When “force to primary” is executed at the multiplex level, all programs that are currently
switched to backup are re-groomed to primary.

To force the switch:

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 Click the MRED/PRED icon ( ) in the toolbar.
3 In the Mux Redundancy panel, select the output multiplex(es) you want.
4 Click To Primary.
The switchover occurs and the primary programs on the selected multiplexes are now active.

CAP-1000 Software Guide v4.0 577

Chapter 28 Configuring Multiplex Redundancy Forcing the Switch to Primary Programs

Force to Primary

578 ARRIS Enterprises, Inc.

 CHAPTER 29
Configuring Program Redundancy

In This Chapter
• Program Redundancy
• Configuring PRED in Diagram View
• Configuring PRED in Tabular View
• Managing Backup Streams and Definitions
• Forcing the Switch to Backup Programs
• Forcing the Switch to Primary Programs

Program Redundancy
Program Redundancy (PRED) provides the ability to groom a backup service in case of primary
service loss. You may also specify that the service will return to the primary when the primary
reappears.
For example, a primary video source and a backup video source are configured by the service
provider for redundancy. If the primary video source is lost, the system automatically switches to
the backup video source. After the primary source is fixed, the system automatically reverts back
to the primary video source if Auto Switch Back is set to True.
A static or animated slate stored locally on the CAP-1000 can also back up programs. Alarm
thresholds can be set to automatically switch to the backup program based on error reporting on
the input stream.
You configure PRED in the Grooming window of the CherryPicker Element Manager. Backup
programs appear in the Backup Streams panel for the output program.
For information on grooming a slate with PRED, refer to Chapter 30, “Configuring Slate
Redundancy.”

Stream Types
The supported stream types for PRED are video (MPEG-4/AVC or MPEG-2), and audio
(including MPEG, Dolby Digital, Dolby Digital Plus, AAC, and HEAAC).

CAP-1000 Software Guide v4.0 579

Chapter 29 Configuring Program Redundancy Program Redundancy

PRED Backup Streams

NOTE PRED is not supported for file grooming as the primary source.

Primary Source Program Requirements

You can set a maximum of 384 primary programs. A primary program must meet the following
requirements:
• An input program can be designated as a primary or backup program.
• The program must be groomed. The designation can also be made in the process of grooming.
• The program can be groomed using grooming by program or custom grooming.
• The program is not an ad (but could be a network program in ad insertion).
• The program is not groomed to a PID Sharing Program Group. PID sharing not supported.
• For backup programs, a slate can be designated if the backup program is not already groomed
to file(s).
• The process of selecting a primary or backup program must following these rules:
• An input program can be designated as a primary or backup program (slate) at any time.
• Any number of groomed input programs can be designated as primary or backup programs
(slate). A primary or backup program (slate) cannot belong to a PID sharing group. PID
sharing not supported.

580 ARRIS Enterprises, Inc.

 Program Redundancy

• The primary or backup (slate) designation can be removed from a program at any time.
• Each primary program must have another program designated as the backup program for this
primary program. The backup program can be one of the following:
• An input program.
• A combination of input elementary steams, which will be groomed using custom
grooming as a single output program in case of a primary failure. Such combination of
streams will be referred to as a custom backup program.
• A standard or custom file.
• Any of the backup types listed above can be selected for a primary program, regardless if the
primary program is groomed by program or custom groomed.

Backup Source Program Requirements

You can designate a backup program for a primary program. The backup input program can be in
input program, a custom input program (a combination of input elementary streams which are
groomed using custom grooming as a single output program in case of a switchover), or a standard
file (as used when grooming from a file), or a slate.
A backup program must meet the following requirements:
• Only one backup program can be selected for a primary program.
• One program can be designated as a backup program for several primary programs.
• The backup program (or elementary streams) can exist in the same input multiplex as the
primary program or in a different multiplex.
• The backup program (or elementary streams) must be present at the CAP-1000 input at the
time when it is selected as a backup program.
• The backup program (or elementary streams) do not have to be groomed at the time when
selected as a backup program.
• The backup program can have a different number of elementary streams than the primary
program.
• A primary program, which is groomed by program, cannot be selected as a backup for itself.
• A combination of custom-groomed input streams (designated as a primary program) cannot be
selected as a custom backup program for this primary.
• The backup program inherits the grooming settings of the primary program, such as the time
interval, recoding settings, etc.
• The process of selecting a backup program must follow these rules:
• A backup program for a given primary program can be changed at any time.
• In the case of a custom backup program, individual streams can be added to, or deleted
from, this program at any time.

CAP-1000 Software Guide v4.0 581

Chapter 29 Configuring Program Redundancy Program Redundancy

• If a primary program loses its designation as primary, or if it is dropped/deleted, then the

corresponding backup program automatically loses its designation as a backup program,
(unless it is associated with other primary programs).
• Each backup program can have another program designated as the slate program for this
backup program. See Chapter 30, “Configuring Slate Redundancy,” for more information.

Switchover Conditions for PRED

This section defines the conditions and constraints for switchover events in PRED when grooming
from a primary program to a first-level backup program. The stream types used for a switchover
decision are video (MPEG-4/AVC or MPEG-2), and audio (including MPEG audio, Dolby Digital
audio, Dolby Digital Plus, AAC audio and HEAAC).
Switchover conditions are configured using the Diagram view or the Tabular view of the
Grooming window.

PRED Backup Properties

When a primary program that was playing disappears, the CAP-1000 automatically switches over
to the backup program. The primary program is dropped, and the backup program is groomed to
the same output program as the primary program.
The conditions for switching from a primary program to a backup program are as follows:
• The primary program is not listed in a new version of the input PAT.
• One or more underflow alarms are raised for any video/audio streams in the primary program
and at least one of those alarms is not cleared for a specified time interval.

582 ARRIS Enterprises, Inc.

 Program Redundancy

• If the Any Audio Video option for Underflow Streams is selected and any elementary stream
has any underflow alarm, then switching to backup occurs according to the selected option:
either Immediate or After Alarm Interval.
• If the All Audio Video option for Underflow Streams is selected and every elementary stream
has any underflow alarm, then switching to backup occurs according to the selected option:
either Immediate or After Alarm Interval.
• If the Video or First Audio option for Underflow Streams is selected and either the video or
first audio of a single groomed program fails, then a switch to the backup program occurs
according to the selected option: either Immediate or After Alarm Interval. The first audio is
the first audio stream in the program. This option prevents switching in the event a provider
does not continuously provide a secondary audio program.
• If the Video Only option for Underflow Streams is selected and the video of a single groomed
program fails, then a switch to the backup program occurs according to the selected option:
either Immediate or After Alarm Interval. This option prevents switching in the event a
provider does not continuously provide audio streams.
• If the First Audio Only option for Underflow Streams is selected and the first audio stream of
a single groomed program fails, then a switch to the backup program occurs according to the
selected option: either Immediate or After Alarm Interval. This option prevents switching in
the event a provider does not continuously provide a secondary audio program.
If these conditions are met, switching to backup program occurs either right away or after the
alarm interval, depending on the Switch Immediate or Switch after Alarm Interval settings.

Switchback Conditions for Programs

You have the choice to specify if the CAP-1000 should return to the primary program when it re-
appears. This selection is available for a maximum of 384 primary programs. The default setting is
No return to the Primary.
A primary program is considered to have reappeared if all of the following conditions are met:
• The primary program is listed in the PAT.
• Packets are received for all video and audio streams in this program and they do not exhibit
any packet continuity or packet encryption errors for a defined time interval.

Error-free Duration
You can select the duration of the error-free time interval for the primary program before the
device returns to this primary. The minimum duration of the error-free interval is seven seconds.
This duration can be changed in five second intervals. The maximum value is 100 seconds. The
default duration is 12 seconds.

NOTE If a program switched to backup because it had disappeared from the PAT, the error free period is not
observed when the program comes back in the PAT. This behavior applies to program grooming as well as
custom grooming.

CAP-1000 Software Guide v4.0 583

Chapter 29 Configuring Program Redundancy Configuring PRED in Diagram View

NOTE These rules do not apply if the switchover is triggered by a user when forcing to backup.

Alarm Duration
The duration of the alarm interval is same for the alarm duration and the length of the alarm
counting interval. It is the same for both video and audio stream types. The duration can be set
independently for each primary program.
The minimum duration of the time interval is one second. The duration can be changed in one-
second intervals. The maximum value is 100 seconds. The default value is two seconds. In case of
PMT change, the duration is not taken into consideration for program grooming and custom
grooming.

Configuring PRED in Diagram View

To configure PRED:
1 Groom a primary program, elementary stream, or file.
See Chapter 18, “Grooming Programs” Chapter 19, “Grooming Elementary Streams” or Chapter
20, “Grooming Files” for more information.
2 Do one of the following:
• From the CherryPicker Element Manager, click Content Picking > Grooming.
• From the CherryPicker Element Manager, click Setup > Redundancy, click the
MRED/PRED icon ( ) in the toolbar, and then click Configure PRED.
3 From View, click .
4 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
5 Expand the Backup Streams panel at the bottom of the window.
6 In the Component Tree, select the program, elementary stream, or standard file you want to groom
as the backup.
7 Drag the input to the backup icon ( ) in Backup cell.
8 Release the mouse button.
The backup program is added to the Backup Streams panel at the bottom of the window.

584 ARRIS Enterprises, Inc.

 Configuring PRED in Tabular View

See Table 18-1 on page 343 for a description of properties that can appear in the Diagram view
when you groom a program.
9 In the Properties panel, enter the required information in the Backup section.
10 Click Apply.
A confirmation window opens.
11 Click Yes.

Configuring PRED in Tabular View

To configure PRED:
1 Groom a primary program, elementary stream, or file.
See Chapter 18, “Grooming Programs” Chapter 19, “Grooming Elementary Streams” or Chapter
20, “Grooming Files” for more information.
2 Do one of the following:
• From the CherryPicker Element Manager, click Content Picking > Grooming.
• From the CherryPicker Element Manager, click Setup > Redundancy, click the
MRED/PRED icon ( ) in the toolbar, and then click Configure PRED.
3 From View, click .
4 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.

NOTE Example illustrations show the a single multiplex in Tabular view.

5 Expand the Backup Streams panel at the bottom of the window.

6 In the Component Tree, select the program, elementary stream, or standard file you want to groom
as the backup.
7 If you selected a single output multiplex in the Output Mux menu, do the following:
a Drag the file to the output program you want.
b Release the mouse button.

CAP-1000 Software Guide v4.0 585

Chapter 29 Configuring Program Redundancy Managing Backup Streams and Definitions

Select Component

c Select Drop to Backup.

d Click OK.
e Click Apply.
8 If you selected All Muxes, All SPTS Muxes, or All MPTS Muxes in the Output Mux menu, do
the following:
a Drag the input to the backup icon ( ) in the Backup cell.
b Release the mouse button.
c Click Apply.
d Click Yes.
The file is added to the Backup Streams panel at the bottom of the window.
9 Scroll the Output panel until you see the Backup properties to configure.
10 In the Properties panel, enter the required information in the Backup section.
See Table 18-2 on page 356 for a description of properties that can appear in the Tabular view
when you groom a program.
11 In the Properties panel, enter the required information in the Backup section.
12 Click Apply.
13 Click Yes.

Managing Backup Streams and Definitions

You can delete backup streams and definitions for backup programs.

Deleting Backup Streams

If you have configured program-level redundancy and want to delete the backup stream, you can
do so in the Grooming window. If all backup streams are removed, PRED is disabled.

To delete a backup stream:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

586 ARRIS Enterprises, Inc.

 Managing Backup Streams and Definitions

3 Expand the Component Tree.

4 Expand the Backup Streams panel at the bottom of the window.
5 In the Backup Streams panel, right-click the stream you want and select Delete from the Context
menu.

NOTE Example illustrations show the Diagram view.

PRED Backup Streams Delete

A confirmation window opens.

6 Click OK.
The stream is deleted from the Backup Streams panel.
7 Click Apply.
8 Click Yes.

CAP-1000 Software Guide v4.0 587

Chapter 29 Configuring Program Redundancy Managing Backup Streams and Definitions

Deleting Backup Definitions

Deleting the grooming definition is the same as “dropping a groom.” In this case, the grooming
definition is deleted, but the programs remain.

To delete a backup definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 In the Output panel, right-click the programs you want and select Delete Backup Definition from
the Context menu.

NOTE Example illustrations show the Diagram view.

PRED Backup Definition Delete

588 ARRIS Enterprises, Inc.

 Forcing the Switch to Backup Programs

5 Click Apply.
6 Click Yes.

Forcing the Switch to Backup Programs

Manually switching to a backup program can take up to three seconds. This value is the sum of the
minimum duration of the underflow state (one second), plus the switching time (two seconds).
When a backup program is groomed, the grooming continues as with any other program. All the
requirements pertaining to grooming apply to this situation.

IMPORTANT The “force to backup” condition at the program level is not permitted if the output multiplex is configured
for MRED.

Forcing the Switch in the Content Picking Window

To force the switch:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Expand the Component Tree.

4 In the Output panel, right-click the backup program(s) you want.
5 Select Manual Override > Backup.

NOTE Example illustrations show the Diagram view.

CAP-1000 Software Guide v4.0 589

Chapter 29 Configuring Program Redundancy Forcing the Switch to Backup Programs

PRED Manual Override to Backup

When “force to backup” is executed, the Controller software checks the programs to determine if
backups have been defined. If backup programs have been defined, the programs are re-groomed
to the backup programs.
If some backup programs have not been defined, a pop-up window displays each program without
a backup.
6 Click Yes to Continue or No to abort.
• If you click Yes, the switch to backup occurs only for programs that have a backup defined. In
this case, the primary program icon appears with a purple border. The entire switch procedure
takes no more then five seconds.
• If you select No, the operation is cancelled and no switch to backup occurs.

NOTE When the CAP-1000 is in a “force to backup” condition, grooming is still allowed. If the groom is primary,
play primary occurs. If the groom is backup, play backup occurs. The “force to backup” condition is
persistent across system reboots and the Controller restarts.

590 ARRIS Enterprises, Inc.

 Forcing the Switch to Backup Programs

Forcing the Switch in the Redundancy Window

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the MRED/PRED icon ( ).
3 In the PRED panel, click the backup program(s) you want.
4 Do one of the following:
• To failover the selected program(s), click To Backup.

Force to Backup

• To failover all programs, click Force All to Backup.

CAP-1000 Software Guide v4.0 591

Chapter 29 Configuring Program Redundancy Forcing the Switch to Primary Programs

Force All to Backup

The backup programs are indicated in green highlight in the PRED panel.

Forcing the Switch to Primary Programs

Manually switching to a primary program can take up to three seconds. This value is the sum of
the minimum duration of the underflow state (one second), plus the switching time (two seconds).
A primary program is considered to have reappeared if all of the following conditions are satisfied:
• The primary program is listed in the PAT.
• No alarms are generated for a defined time interval.

IMPORTANT The “force to primary” condition at the program level is not permitted if the output multiplex is configured
for MRED.

Forcing the Switch in the Content Picking Window

To force the switch:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Expand the Component Tree.

4 In the output panel, right-click the primary program(s) you want.
5 Click Manual Override > Primary.

592 ARRIS Enterprises, Inc.

 Forcing the Switch to Primary Programs

NOTE Example illustrations show the Diagram view.

PRED Manual Override to Primary

Forcing the Switch in the Redundancy Window

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the MRED/PRED icon ( ).
3 In the PRED panel, select the primary program(s) you want.
4 Do one of the following:
• To failback the selected program(s), click To Primary.

CAP-1000 Software Guide v4.0 593

Chapter 29 Configuring Program Redundancy Forcing the Switch to Primary Programs

Force to Primary

• To failback all programs, click Force All to Primary.

Force All to Primary

The primary programs are indicated in green highlight in the PRED panel.

594 ARRIS Enterprises, Inc.

 CHAPTER 30
Configuring Slate Redundancy

In This Chapter
• Slates
• Managing Slate Files
• Configuring Slates (Second-level Backup)
• Managing Action Definitions for Slates
• Forcing the Switch to Backup
• Forcing the Switch to Primary

Slates
The CAP-1000 supports the use of slates, which can be groomed to output, in the event that both
Primary and Backup CAP-1000 units configured for Program Redundancy (PRED) are
unavailable.
A slate is a video file, a video file and audio file(s), or a video file and audio live stream(s). For
output programs or muxes that have a slate input source defined, the grooms can be forced to
switch from the Primary to the slate source, even though the primary source may not have failed. A
backup program can also have another program designated as the slate program for a second-level
backup.

Functions
You can define a custom slate for use at the device level, multiplex level, or program level. When
defined at the device level, the second-level slate is active for every output program of the device.
When defined at the device or multiplex level, two different file names are requested for two
different video slate file formats: MPEG-4/AVC SD and MPEG-2 SD. The software automatically
selects the files based on the live video stream format of the program.
Forcing the groom can be done at the device level, the mux level, or individual output program
level. When the forced to slate option is requested, the state is remembered for future grooms. For
those output programs that have no slate input source specified, the request is ignored.

CAP-1000 Software Guide v4.0 595

Chapter 30 Configuring Slate Redundancy Slates

For example, PRED provides the ability to groom a backup service in case of primary service loss.
In addition to video (MPEG-4/AVC or MPEG-2), and audio (including MPEG audio, Dolby
Digital, Dolby Digital Plus, AAC, and HEAAC), you can also choose a slate as a second-level
backup input. To use slates with the CAP-1000, you need to upload them to the Data Flash.

PRED first-
level backup

PRED second-
level backup
(slate)

PRED with a Slate

To set up slates, you do so in the Setup > Redundancy > Slate window. Information on how to set
up slates is described in this chapter.

Backup Slate Requirements

A backup slate must meet the following requirements:
• Only one slate program can be selected for a backup program.
• One slate program can be designated as a slate program for several backup programs.
• The audio stream must be present on the CAP-1000 at the time it is selected as a slate
program.
• The audio stream does not need to be groomed at the time when it is selected as a slate
program.
• The slate program can have a different number of elementary streams from the backup
program.
• A backup program, which is groomed by program, cannot be selected as a slate for itself.
• A backup program containing a video file cannot have a slate program. The last level of
redundancy is achieved as soon as a video file is groomed to the program.
• The backup program does not have any streams that are passed to the output.

596 ARRIS Enterprises, Inc.

 Slates

• A slate must always be groomed, never passed, even if the backup program is passed. When a
failover occurs, the slate is groomed.
• The slate program inherits all the grooming settings of the primary program.

Slate

Rules for Selecting Slates

The process of selecting a slate program is according to the following rules:
• When defined at the device level, the second-level slate is active for every output program on
the device. When defined at the device- or multiplex-level, different file names are requested
for two different video slate file formats, MPEG-4/AVC SD and MPEG-2 SD. The CAP-1000
automatically selects the files based on the live, video stream format of the program.
• When defined at the multiplex level, the second-level slate is active for every output program
on the multiplex.
• When setting the slate definitions, a first-level of PRED using a live stream must be defined
for that program. Using a second-level slate is not supported.
• In the case of a custom slate program, individual streams can be added to, or deleted from, this
program at any time.
• f a backup program loses its designation as backup, or if it is dropped or deleted, the
corresponding slate program automatically loses its designation as a slate program (unless it is
associated with other backup programs).

CAP-1000 Software Guide v4.0 597

Chapter 30 Configuring Slate Redundancy Slates

• When there is no multiplex-level slate or device-level slate defined:

• A slate cannot be groomed if a primary program has been groomed, but a backup program
has not been groomed.
• A backup program with an associated slate cannot be deleted. You must delete the slate
before the backup can be deleted.
• A slate can be groomed if a primary or a backup program has not been groomed.

Switchover Conditions for Slates

This section defines the conditions and constraints for the switchover events in PRED when
switching from a backup program to a second-level slate program. The stream types used for a
switchover decision are video (MPEG-4/AVC or MPEG-2), and audio (including MPEG audio,
Dolby Digital audio, Dolby Digital Plus, AAC audio and HEAAC).
The conditions for switching from a primary program to a backup slate are as follows:
• The backup program disappears from the new version of the input PAT.
• If no backup program is defined, the condition applies to switching from the primary input to
the slate.
• If backup program is defined and the backup disappears, the condition applies to switching
from the backup input to the slate.
• One or more underflow alarms are raised for any video/audio streams in the primary program
and at least one of those alarms is not cleared for a specified time interval.
• If the Any Audio Video option for Underflow Streams is selected and any elementary stream
has any underflow alarm, then switching to backup occurs according to the selected option:
either Immediate or After Alarm Interval.
• If the All Audio Video option for Underflow Streams is selected and every elementary stream
has any underflow alarm, then switching to backup occurs according to the selected option:
either Immediate or After Alarm Interval.
• If the Video or First Audio option for Underflow Streams is selected and either the video or
first audio of a single groomed program fails, then a switch to the backup program occurs
according to the selected option: either Immediate or After Alarm Interval. The first audio is
the first audio stream in the program. This option prevents switching in the event a provider
does not continuously provide a secondary audio program.
• If the Video Only option for Underflow Streams is selected and the video of a single groomed
program fails, then a switch to the backup program occurs according to the selected option:
either Immediate or After Alarm Interval. This option prevents switching in the event a
provider does not continuously provide audio streams.

598 ARRIS Enterprises, Inc.

 Slates

• If the First Audio Only option for Underflow Streams is selected and the first audio stream of
a single groomed program fails, then a switch to the backup program occurs according to the
selected option: either Immediate or After Alarm Interval. This option prevents switching in
the event a provider does not continuously provide a secondary audio program.
If these conditions are met, the switchover to the slate program occurs after the user-specified
alarm interval.

Switchback Conditions for Slates

You have the choice to specify if the CAP-1000 should return to the primary program when it re-
appears. The default setting is No return to the Primary.
A primary program is considered to have reappeared if all of the following conditions are met:
• The primary program is listed in the PAT.
• Packets are received for all video and audio streams in this program and they do not exhibit
any packet continuity or packet encryption errors for a defined time interval.

Error-free Duration
You can select the duration of the error-free time interval for the primary program before the
device returns to this primary. The minimum duration of the error-free interval is seven seconds.
This duration can be changed in five second intervals. The maximum value is 100 seconds. The
default duration is 12 seconds.
If a program switched to backup because it had disappeared from the PAT, the error free period is
not observed when the program comes back in the PAT. This behavior applies to program
grooming as well as custom grooming.

NOTE These rules do not apply if the switchover is triggered by a user when forcing to backup.

Error Period
The duration of the alarm interval is same for the alarm duration and the length of the alarm
counting interval. It is the same for both video and audio stream types. The duration can be set
independently for each primary program.
The minimum duration of the time interval is one second. The duration can be changed in one-
second intervals. The maximum value is 100 seconds. The default value is 10 seconds. In case of
PMT change, the duration is not taken into consideration for program grooming and custom
grooming.

CAP-1000 Software Guide v4.0 599

Chapter 30 Configuring Slate Redundancy Managing Slate Files

Managing Slate Files

To access slate files for use as backup, you upload them from a directory on your local machine to
the CAP-1000 Data Flash. Alternatively, you can extract the files from an elementary stream and
then upload them to the CAP-1000.
Once the files are selected, the CAP-1000 automatically extracts and uploads them to the
appropriate directory on the Data Flash. Video files are saved in the /usr/cp/video/custom
directory. Audio files are saved in the /usr/cp/audio/custom directory.

Uploading Slate Files

To upload:
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click Slate Files.

Slate Files

3 In the Select File panel, use the icons in the window to navigate to a directory where the slate files
are saved.
4 Under Name, select the file you want.
The file name appears in the File Name field.

600 ARRIS Enterprises, Inc.

 Managing Slate Files

NOTE You can filter by file types using the Files of Type menu.

5 Click Import Streams.

The video or audio file is extracted and appears in the Elementary Streams panel.

Slate Files

6 In the Elementary Streams panel, select the stream.

7 Click Upload.
The video or audio file is uploaded to the appropriate directory on the CAP-1000.

CAP-1000 Software Guide v4.0 601

Chapter 30 Configuring Slate Redundancy Managing Slate Files

Slate Files

Deleting Slate Files

You can delete video or audio files stored on the Data Flash to regain space. The total amount of
available space is shown in the Space Available Below Data Flash Alarm Threshold field in the
Slate Files window.
1 From the CherryPicker Element Manager, click Setup > Files.
2 Click Slate Files.
3 In the Device panel, select the video file or audio file you want to delete.

602 ARRIS Enterprises, Inc.

 Configuring Slates (Second-level Backup)

Slate Files

4 Click Delete.
The file(s) is immediately deleted from the Data Flash.

Configuring Slates (Second-level Backup)

This section explains how to configure slates at the device-, multiplex-, or program-level. These
slates can be used in the situation where both the primary program and backup program fails.

Configuring Device-Level Slates

To configure:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Slate icon ( ).

CAP-1000 Software Guide v4.0 603

Chapter 30 Configuring Slate Redundancy Configuring Slates (Second-level Backup)

Slate Configuration

3 In the Device Slate Configuration panel, select the Enable Slate option.
This step fills the all other column with default values. It also shows the default MPEG-2
(colorbars.ntsc) and MPEG-4 (colorbars.4AVC) video slate file in Slate Configuration panel.
a Modify the Slate configuration parameter, as needed, in the Slate Configuration panel.
b To replace the default MPEG-2 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.
c To replace the default MPEG-4 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.
d (Optional) Select a live audio or audio file from the input tree and drop it in the Slate
Configuration panel.
4 Click Apply.

Configuring Mux-Level Slates

To configure:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Slate icon ( ).

604 ARRIS Enterprises, Inc.

 Configuring Slates (Second-level Backup)

3 In the Mux Slate Configuration panel, select the output port you want from the Output Line
menu.
4 Select the slates you want to enable and then select the Enable Slate option.

Slate Configuration

This step fills the all other column with default values. It also shows the default MPEG-2
(colorbars.ntsc) and MPEG-4 (colorbars.4AVC) video slate file in Slate Configuration panel.
a Modify the Slate configuration parameter, as needed, in the Slate Configuration panel.
b To replace the default MPEG-2 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.
c To replace the default MPEG-4 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.
d (Optional) Select a live audio or audio file from the input tree and drop it in the Slate
Configuration panel.
5 Click Apply.

CAP-1000 Software Guide v4.0 605

Chapter 30 Configuring Slate Redundancy Configuring Slates (Second-level Backup)

Configuring Program-Level Slates

To configure:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Slate icon ( ).
3 In the Program Slate Configuration panel, select the output port you want from the Output Mux
menu.
4 Select the slates you want to enable and then select the Enable Slate option.

Slate Configuration

This step fills the all other column with default values. It also shows the default MPEG-2
(colorbars.ntsc) and MPEG-4 (colorbars.4AVC) video slate file in Slate Configuration panel.
a Modify the Slate configuration parameter, as needed, in the Slate Configuration panel.
b To replace the default MPEG-2 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.

606 ARRIS Enterprises, Inc.

 Configuring Slates (Second-level Backup)

c To replace the default MPEG-4 slate file, select a slate file from input tree and drop it in the
Slate Configuration panel.
d (Optional) Select a live audio or audio file from the input tree and drop it in the Slate
Configuration panel.
5 Click Apply.

Deleting Slates

To delete:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Slate icon ( ).
3 In the Slate Configuration panel, clear the Enable option.
4 Click Apply.

Deleting Slate Streams

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Slate icon ( ).
3 In the Slate Configuration panel, right-click the mouse button.
4 From the Context menu, select Delete.
If the deleted stream is a video slate file, then this step shows the default video slate file. If the
deleted stream is an audio file, then the row is removed.
5 Click Apply.

CAP-1000 Software Guide v4.0 607

Chapter 30 Configuring Slate Redundancy Managing Action Definitions for Slates

Managing Action Definitions for Slates

After configuring slates, you can click the Content Picking > Grooming tab to see details about
the slate stream and other parameter for the slate definitions.

Slate is Assigned

Managing Action Definitions

To manage:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

• If program-level slate is defined, and a gray slate icon shows in the Slate column, there is no
grooming.
• If program-level slate is defined, and a slate icon shows in the Slate column, there is grooming.
• If device-level or multiplex-level slate is defined, and a slate icon shows in the Slate column,
there is grooming.
3 Using a slate, you can perform any of the following tasks:
• View slate properties in the Properties panel.
• Edit the slate error period, underflow stream, and error free period for a program-level slate.
• Drag and drop an input on a slate icon to define or edit a program-level slate.

608 ARRIS Enterprises, Inc.

 Managing Action Definitions for Slates

4 Click Apply.
5 Click Yes.

Deleting Slate Streams

If you have configured program-level redundancy and want to delete the backup stream from a
slate definition, you can do so in the Grooming window.

To delete a slate stream:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Expand the Component Tree.

4 Expand the Slate Component panel at the bottom of the window.
5 In the Slate Component panel, right-click the stream you want and select Delete from the Context
menu.

NOTE Example illustrations show the Diagram view.

Backup Slate Delete

A confirmation window opens.

6 Click OK.
The slate is deleted from the Backup Streams panel.

CAP-1000 Software Guide v4.0 609

Chapter 30 Configuring Slate Redundancy Managing Action Definitions for Slates

7 Click Apply.
8 Click Yes.

Deleting Slate Definitions

To delete a slate definition:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 In the Output Mux menu, select the output mux(es) you want.
The contents of the Output panel differs depending on the Output Mux option you selected. If you
select the All Muxes option, all multiplexes display in the Output panel, along with program
placeholders, if any, that are associated with the configuration file.
If you select the All SPTS Muxes or All MPTS Muxes option, only those output multiplexes
display in the Output panel, along with program placeholders, if any, that are associated with the
configuration file. If you select a specific multiplex, program placeholders, if any, display in the
panel.
4 In the Output panel, right-click the programs you want and select Delete Slate Definition from the
Context menu.

NOTE Example illustrations show the Diagram view.

Delete Slate Definition

610 ARRIS Enterprises, Inc.

 Forcing the Switch to Backup

5 Click Apply.
6 Click Yes.

Forcing the Switch to Backup

Manually switching to a backup slate can take up to three seconds. This value is the sum of the
minimum duration of the underflow state (one second), plus the switching time (two seconds).
When a backup slate is groomed, the grooming continues as with any other program. All the
requirements pertaining to grooming apply to this situation.

IMPORTANT The “force to backup” condition at the program level is not permitted if the output multiplex is configured
for MRED.

Forcing the Switch in the Content Picking Window

To force the switch:
1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Expand the Component Tree.

4 In the Output panel, right-click the backup slate(s) you want.
5 Select Manual Override > Slate.

NOTE Example illustrations show the Tabular view.

CAP-1000 Software Guide v4.0 611

Chapter 30 Configuring Slate Redundancy Forcing the Switch to Backup

Manual Override to Slate

6 Click Yes to Continue or No to abort.

• If you click Yes, the switch to backup occurs only for programs that have a backup slate
defined. In this case, the primary program icon appears with a red border. The entire switch
procedure takes no more then five seconds.

Manual Override to Slate with Red Border Around Program

612 ARRIS Enterprises, Inc.

 Forcing the Switch to Backup

• If you select No, the operation is cancelled and no switch to backup occurs.

NOTE When the CAP-1000 is in a “force to backup” condition, grooming is still allowed. If the groom is primary,
play primary occurs. If the groom is backup, play backup occurs. The “force to backup” condition is
persistent across system reboots and the Controller restarts.

Forcing the Switch in the Redundancy Window

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the MRED/PRED icon ( ).
3 In the PRED panel, click the backup slate(s) you want.
4 Do one of the following:
• To failover the selected program(s), click To Slate.

Force to Slate

• To failover all programs, click Force All to Slate.

CAP-1000 Software Guide v4.0 613

Chapter 30 Configuring Slate Redundancy Forcing the Switch to Primary

Force All to Slate

Forcing the Switch to Primary

Manually switching to a primary program can take up to three seconds. This value is the sum of
the minimum duration of the underflow state (one second), plus the switching time (two seconds).
A primary program is considered to have reappeared if all of the following conditions are satisfied:
• The primary program is listed in the PAT.
• No alarms are generated for a defined time interval.

IMPORTANT The “force to primary” condition at the program level is not permitted if the output multiplex is configured
for MRED.

Forcing the Switch in the Content Picking Window

To force the switch:

1 From the CherryPicker Element Manager, click Content Picking > Grooming.
2 From View, click or .

3 Expand the Component Tree.

614 ARRIS Enterprises, Inc.

 Forcing the Switch to Primary

4 In the Output panel, right-click the slate(s) you want.

5 Click Manual Override > Primary.

NOTE Example illustrations show the Table view.

Manual Override to Slate

Forcing the Switch in the Redundancy Window

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the MRED/PRED icon ( ).
3 In the PRED panel, select the slate(s) you want.
4 Do one of the following:
• To failback the selected slate(s), click To Primary.

CAP-1000 Software Guide v4.0 615

Chapter 30 Configuring Slate Redundancy Forcing the Switch to Primary

Force To Primary

• To failback all slates, click Force All to Primary.

Force All to Primary

616 ARRIS Enterprises, Inc.

 CHAPTER 31
Configuring Ad Insertion Protection

In This Chapter
• Ad Insertion Protection
• Enabling Ad Insertion Protection
• Toggling the Active AIP Port
• Disabling Ad Insertion Protection

Ad Insertion Protection
Ad Insertion Protection (AIP) provides redundancy for ad input feeds. It enables unicast input
muxes to fail over from one failed GigE port to another pre-defined active GigE peer port when the
first port or its local link fails. AIP can be used in conjunction with Program Redundancy (PRED),
Multiplex Redundancy (MRED), or port mirroring to provide link redundancy for ad insertion.

Virtual IP
A virtual IP address is assigned to one of the peer ports. The ad server is configured to use the
virtual IP address for streaming ads. When the one port fails, the ad server connections associated
with the ad input muxes on the failed port are closed and the virtual IP is moved to the peer port.
The ad server will then reconnect using the virtual IP to stream the ads.
Each pair of peer ports on the IOA that carry the ad muxes must be assigned a single virtual IP
address. Assignment of a virtual IP address to the management port is optional. The virtual IP is
only needed on the AUX port if a device is configured for CPR and SCTE 30 connections will use
the AUX port.

AIP, CPR, and the RIP Metric

The AIP feature switches the virtual IP address between ports for a single port failure. When
CAP-1000 units are configured for CPR, the virtual IP address is switched to the Backup device
during failover if the Primary device fails.

CAP-1000 Software Guide v4.0 617

Chapter 31 Configuring Ad Insertion Protection Enabling Ad Insertion Protection

NOTE The RIP Metric Backup parameter applies when the virtual IP is used on the Backup CAP-1000. Multicast
fencing down stream of the Primary and Backup devices can be implemented by using different values on
the RIP Metric (value used from the Primary) and the RIP Metric Backup (value used from the backup).

The RIP Metric value is sent out on the interface of the primary CAP-1000 when a primary IS NOT covered
by the backup. A value of 0 indicates no RIP is sent. A RIP value should only be used if the OSPF value is
false.

Enabling Ad Insertion Protection

To enable AIP, both ports must be configured with physical IP addresses and one of the two
defined ports must be assigned a virtual IP address. When the physical or virtual IP address
parameters are updated on the active port, all SCTE 30 connections associated with ad input
muxes on the active port are closed.

To enable AIP:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the AIP icon ( ).

Ad Insertion Protection (AIP)

618 ARRIS Enterprises, Inc.

 Enabling Ad Insertion Protection

The following table describes the port parameters for AIP.

Table 31-1 Gigabit Ethernet Port Parameters

ID Shows the default ID assigned to the port in the format: <slot>/<port>.

Link Shows the link status and link speed for ports on either the 1G IOA and 10G IOA.
Mouse over the colored indicators to get a tool tip with the link speed.

—Active (green)
—Active (blue)
—Active (yellow)
—Active (orange)
—Inactive (red)
—Bonded (gray ports).

IP Specifies a static IP address for this port (1.1.1.1 to 223.255.255.355). The allowed
range of IP addresses is from 0.0.0.0 to 223.255.255.255, with the following
exceptions:
• Address 0.0.0.0 can not be used. This address is not a valid Internet address and
it is also used by the hardware as the host address after hardware is initialized.
• Address 127.X.X.X is not a valid IP address. It is used as the loop back address
for troubleshooting and network testing.
• The default value is an empty string. It may be also represented as an all-0
address in some interfaces where an empty string cannot be used.

Virtual IP Specifies a virtual IP address for the port: for example, the port to be used with
CherryPicker Device Redundancy (CPR).
Note: Selection of the virtual IP port option is only available if virtual IPs have been
assigned. Virtual IP assignment is not a requirement for using port mirroring. If it is
used in conjunction with the AIP feature, however, one virtual IP is available. See
Chapter 27, “Configuring CherryPicker Redundancy” or Chapter 31,
“Configuring Ad Insertion Protection”for information.
Virtual Netmask Specifies the virtual netmask to be used with the Virtual IP parameter.

GARP Specifies a gratuitous ARP for a Virtual IP address. GARP can only be enabled
whenever virtual IP and virtual netmask are defined.

Routing Protocol Lists the routing protocols you can enable: RIP, OSPF or None. This option is grayed
out when the port is network disabled. When no VIP is defined, the available
options are OSPF and None. The RIP option is only available when VIP is defined.
Note: When OSPF routing is enabled, you must configure the Router ID, Area ID,
and the Routing Protocol.

Routing Metric Sets the IPv4 internet working protocol for use with the RIP metric options. The
options are 1-15. You can edit this parameter when the Routing Protocol is not set
to None. A value of 0 indicates no RIP is sent.

CAP-1000 Software Guide v4.0 619

Chapter 31 Configuring Ad Insertion Protection Enabling Ad Insertion Protection

Table 31-1 Gigabit Ethernet Port Parameters (continued)

Router ID Sets the Router ID with a 32-bit number. When the Router ID is unset, use the
highest IP interface address belonging to the route. (Unset meaning not yet defined
via the GUI or cleared after setting a previous definition). Otherwise, you can set
the Router ID with dotted octets. Blanks are not allowed. This option is supported
when the OSPF, Virtual IP, and Netmask options are set.

Area ID Sets the IPv4 address that serves as the backbone. The Backbone has a reserved
Area ID of 0.0.0.0.

Peer Port Selects a redundant port for AIP or CPR. The combo box displays None or the port
name.

AIP Enable Enables or disables AIP on the selected port. The port must be paired with another
port and a VIP must be defined. The available ports can be 1, 2, 3, or 4.

Routing Metric Backup Sets the RIP metric based on the Routing Protocol option. The options are 1-15. You
can edit this parameter when the Routing Protocol is not set to None. A value of 0
indicates no RIP is sent. A RIP value should only be used if the OSPF value is false.

3 To pair up two ports, do the following:

a Identify the port you want to enable.
b Enter the Virtual IP address, Virtual Net Mask, and RIP Metric for the first port.
c In the Peer Port column, select the GigE port on the IOA to use as the peer.
The peer port of the selected port is automatically updated with the current port ID.
d Change the Virtual IP and Net Mask of the peer port to be blank and click Apply.
The two ports are now paired.
By default, the Peer Port parameter is editable and empty, AIP Enable is disabled
(unchecked), and Active AIP Port is read-only and empty. After a valid port pair is established,
the AIP Enable check box becomes editable.
4 To enable AIP, do the following:
a Locate the port with the virtual IP. Select the AIP Enable check box.
The check box for peer port is automatically selected.
b Click Apply.
A warning window opens.
c Click Yes.
After a valid port pair is established, the AIP Enable check box becomes editable. A Yes
value in the Active AIP Port column indicates that the port is currently active.

NOTE For peer ports, both AIP Enable check boxes should be synchronized (either both checked). If either the
Virtual IP or Virtual Netmask parameters are empty, the AIP Enable cell is not editable.

620 ARRIS Enterprises, Inc.

 Toggling the Active AIP Port

Ad Insertion Protection (AIP)

A failed port occurs when a GigE line goes down and the line status changes to “Cable
Disconnected.” When a port fails, the virtual IP address is moved from the failed port to the other
port defined in the paired relationship.
Any existing SCTE 30 connections associated with the ad input muxes on the port going down are
closed and the ad input muxes are deleted. The virtual IP is uninstalled on the port going down and
installed on the peer port. An alarm is posted to notify you that the active AIP port has been
switched.

Toggling the Active AIP Port

You can manually switch the active AIP port if both ports are up. The actions taken during the
switchover are the same as in the case of an automatic failover, however, the status of the currently
active port remains as a valid link speed (indicating that it is still available), but the Active AIP
Port parameter is set to “No.”

To toggle:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the AIP Status panel, select the port you want.
3 Click the arrow.

CAP-1000 Software Guide v4.0 621

Chapter 31 Configuring Ad Insertion Protection Disabling Ad Insertion Protection

AIP Status

4 After a few moments, the port is switched.

Disabling Ad Insertion Protection

To disable AIP:
1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the AIP icon ( ).
3 Locate the port with the virtual IP. Clear the AIP Enable check box.
4 Click Apply.
A warning window opens.
5 Click Yes.

622 ARRIS Enterprises, Inc.

 CHAPTER 32
Configuring Port Mirroring

In This Chapter
• Port Mirroring
• Configuring Port Mirroring
• Disabling Port Mirroring

Port Mirroring
The CAP-1000 supports port mirroring on multiple Gigabit Ethernet output ports on the IOA.
Output port mirroring provides port-level protection for CAP-1000 multiplexes. Should one port
fail, programs on the failed port are switched over to the same programs on the backup port. The
backup port is referred to as the “mirror.”
In output port mirroring, two copies of the same MPEG output traffic (UDP) are sent to two
different IP ports. In case of link failure on the primary port, the network re-routes the output from
the mirror port to the destination port.

NOTE Port mirroring is not supported on DVB-ASI interfaces.

When port mirroring is enabled, the CAP-1000 automatically puts the mirror port in standby mode
and creates a mirror output multiplex on the mirror port for each existing output multiplex on the
primary. As soon as a mirror is attached to a port, that port becomes a primary port. A primary port
can have one or more mirror ports. The number of mirror ports sharing a primary as source
depends on the number of available GigE ports. The 10G IOA has ten GigE ports, so the system
can have up to nine mirror ports.

NOTE Output multiplexes cannot be created or deleted on a mirror port. Modifications to output multiplexes must
be made on the primary port. Input multiplexes can be created or deleted on the mirror port. See Chapter
14, “Configuring Multiplexes” for more information.

CAP-1000 Software Guide v4.0 623

Chapter 32 Configuring Port Mirroring Configuring Port Mirroring

Constraints
The following lists constraints for GigE port mirroring:
• A primary port can have multiple mirror ports.
• A mirror port cannot be mirrored to any other port.
• Mirroring is allowed between electrical and optical ports.
• When enabling mirroring, all existing output multiplexes on the mirror port are deleted.
• When disabling port mirroring on a mirror port, all multiplexes created by the mirroring
mechanism are deleted.
• You cannot enable mirroring on a per-output multiplex basis.
• You cannot create or delete output multiplexes on mirror ports.
• You can create or delete input multiplexes on mirror ports.
• You can modify certain mirror output ports parameters on-the-fly without impacting the
primary output port.
• When a primary output multiplex is deleted, the mirror output multiplex is automatically
deleted.
• A mirror GigE mux must use the same RTP setting as the primary mux.

NOTE Output muxes on mirror ports are not counted in the Output Mux count displayed at the bottom of GUI.

See Chapter 14, “Configuring Multiplexes” for information on managing GigE multiplexes.

Configuring Port Mirroring

You can configure port mirroring in the Network window or the Redundancy window of the
CherryPicker Element Manager. The mirrored port is the primary, or the source, and the mirror
port(s) are the slaves.

Configuring Gigabit Ethernet Port Mirroring in the Network Window

To configure GigE port mirroring:

1 From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
2 Identify the port you want to make into a mirror.
3 Under Mirror Of, select the primary port the given port will mirror.

624 ARRIS Enterprises, Inc.

 Configuring Port Mirroring

Mirror Of

4 If you use Source Specific Multicast (SSM) in your network environment, specify the MPEG
Source IP address for the traffic to be permitted on this port.
If you do not specify a source IP address, the streams carry the IP address of the output GigE port.
Non-MPEG TCP/IP traffic continues to use the output GigE port's IP address.

CAP-1000 Software Guide v4.0 625

Chapter 32 Configuring Port Mirroring Configuring Port Mirroring

MPEG Source IP Origin

5 Click Apply.
A warning window opens.

Warning

6 Click Yes.
When first enabled, the mirror port automatically puts itself in Standby mode.
7 To start outputting MPEG traffic, scroll the bottom panel horizontally until the MPEG Out
column appears.
8 Select the Active option in the MPEG Out parameter to start outputting MPEG traffic.
9 Click Apply.
A warning window opens.
10 Click Yes.

626 ARRIS Enterprises, Inc.

 Configuring Port Mirroring

After port mirroring is enabled, all existing output multiplexes on the mirror port are automatically
deleted and a new set of output multiplexes are automatically created to duplicate the primary port.
If you navigate to Content Picking > Mux and select the mirrored port, newly-created
multiplexes appear.

Port Mirroring

Configuring Port Mirroring in the Redundancy Window

To configure GigE port mirroring:

1 From the CherryPicker Element Manager, click Setup > Redundancy.
2 In the toolbar, click the Port Mirroring icon ( ).
3 Identify the port you want to make into a mirror.
4 Under Mirror Of, select the primary port the given port will mirror.

CAP-1000 Software Guide v4.0 627

Chapter 32 Configuring Port Mirroring Configuring Port Mirroring

Mirror Of

5 If you use Source Specific Multicast (SSM) in your network environment, specify the MPEG
Source IP address for the traffic to be permitted on this port.
If you do not specify a source IP address, the streams carry the IP address of the output GigE port.
Non-MPEG TCP/IP traffic continues to use the output GigE port's IP address.

MPEG Source IP Origin

6 Click Apply.
A warning window opens.

Warning

7 Click Yes.
When first enabled, the mirror port automatically puts itself in Standby mode.

628 ARRIS Enterprises, Inc.

 Disabling Port Mirroring

8 To start outputting MPEG traffic, do the following:

a From the CherryPicker Element Manager, click Setup > System > Network.
Ethernet port parameters display in the bottom panel.
b Scroll the bottom panel horizontally until the MPEG Out column appears.
c Select the Active option in the MPEG Out parameter to start outputting MPEG traffic.
d Click Apply.
A warning window opens.
e Click Yes.
After port mirroring is enabled, all existing output multiplexes on the mirror port are automatically
deleted and a new set of output multiplexes are automatically created to duplicate the primary port.
If you navigate to Content Picking > Mux and select the mirror port, newly-created multiplexes
appear.

Disabling Port Mirroring

When disabling the mirroring on a mirror port, all multiplexes created by the mirroring mechanism
on the mirror port are also deleted.

To disable GigE port mirroring:

1 From the CherryPicker Element Manager, click Setup > System > Network.
2 Scroll the bottom panel until the Mirror column appears.
3 Locate the mirror port you want to disable for mirroring.
4 Double-click Mirror Of and select None from the menu.
5 Click Apply.
A warning window opens.
6 Review the warning messages and then click OK.

CAP-1000 Software Guide v4.0 629

Chapter 32 Configuring Port Mirroring Disabling Port Mirroring

630 ARRIS Enterprises, Inc.

 CHAPTER 33
Configuring OSPF

In This Chapter
• Overview
• Features
• OSPF Initialization and Configuration
• OSPF Operation
• OSPF Adjacencies
• RFC Supported Functions
• Optimizing OSPF Configuration in the Network
• OSPF Implementation Examples

Overview
Open Shortest Path First (OSPFv2) is a dynamic routing protocol for use in Internet Protocol (IP)
networks. It gathers link state information from available routers and constructs a topology map of
the network. The topology determines the routing table presented to the Internet Layer which
makes routing decisions based solely on the destination IP address found in IP datagrams.
OSPF detects changes in the topology, such as link failures and quickly converges on a new loop-
free routing structure within seconds. It computes the shortest path tree for each route. The link-
state information is maintained on each router as a link-state database (LSDB) which is a tree-
image of the entire network topology.
On the CAP-1000, OSPF is used to advertise the virtual IP addresses of the device when
CherryPicker Redundancy (CPR) or Ad Insertion Protection (AIP) are enabled. OSPF can be
selectively implemented on any Ethernet interface of the CAP-1000 running software v3.3 or
higher. OSPF can also be used to facilitate CPR failovers and virtual IP address (VIP) porting over
Layer 3 IP networks.

CAP-1000 Software Guide v4.0 631

Chapter 33 Configuring OSPF Features

Features
This section describes the features of OSFPv2 that are supported by the CAP-1000.

Link State Advertisements

• Send out Router LSAs (Link State Advertisements)
• Receive all types of LSAs, including Router LSAs, Network LSAs, Type 3 (inter-area
summary LSA describes routes to networks), Type 4 (inter-area summary LSA describes
routes to an AS Boundary Routers), Summary LSAs, and AS external LSAs.
When these LSAs are received, the CAP-1000 performs protocol-level checking. If all is well, the
CAP-1000 drops the contents of the advertisements. If all is not well with the check, the
CAP-1000 performs error handling for notification purposes. The CAP-1000 does not build an
LSDB, nor a shortest path tree with the advertisements.
• Various timers
• IP multicast support
• Variable length subnet support
• IP supernetting support
• Lower level protocol support
• List manipulating primitives

NOTE For backward compatibility with previous versions of OSPF, the CAP-1000 shall support encoding of TOS
in OSPF LSAs as defined in the RFC as required by the functionality described herein.

CherryPicker Redundancy Support

CPR enables a Backup CAP-1000 to automatically replace a Primary CAP-1000 when the primary
meets certain pre-defined failure criteria. During CPR failovers, the Primary CAP-1000 becomes
inactive and the Backup CAP-1000 becomes active with the complete configuration of the failed
Primary. Any VIP addresses that were defined on the Primary CAP-1000 are transferred to the
corresponding ports on the Backup CAP-1000. Thus, any ad servers communicating with a certain
VIP address on the Primary CAP-1000 will continue to use the same VIP address on the Backup.
Any VIP addresses that the Primary CAP-1000 was assigned on the network can quickly detect the
new routes to the VIP addresses on the Backup CAP-1000. The Primary CAP-1000 redirects any
traffic from ad servers to those VIPs. When the VIP moves from one device to another, it is the job
of the IP network to route traffic correctly to and from the VIP addresses.
For example, two CAP-1000s are deployed in a CPR Backup 1:1 mode. Under normal operating
conditions, the Primary CAP-1000 is operational and the Backup is in standby mode. Server A
(SvrA) is sending data to VIP addresses on the Primary CAP-1000.

632 ARRIS Enterprises, Inc.

 Features

During a CPR failover, the Primary CAP-1000 fails over to the Backup CAP-1000. The Primary
CAP-1000 shuts down and the Backup CAP-1000 comes online with the same configuration as the
Primary. The VIP addresses that the Primary was advertising are now taken up by the Backup
CAP-1000.
In this example, OSPF has been implemented in the routers (RT1, RT2, and RT3) and on the
CAP-1000s. The SvrA that was sending ad input feeds to a VIP on the Primary CAP-1000 will
continue to send the ad input feeds to the same VIP address, but the router network running OSPF
directs its traffic to the VIP address that is now displayed on the Backup CAP-1000.

CAP-1000 CPR Implementation with OSPF

IMPORTANT This implementation of OSPF is not intended to perform network traffic routing through the CAP-1000 via
two or more of its interfaces.

See Chapter 27, “Configuring CherryPicker Redundancy” for more information.

Ad Insertion Protection
AIP provides link redundancy for ad-insertion. Ad insertion redundancy enables unicast input
muxes to fail over from one failed GigE port to another pre-defined active GigE port when the first
port or local link fails.
In an AIP configuration, two peer ports are defined as primary and backup ports for ad server
communication. Both peer ports have unique physical IP addresses and share a common Virtual IP
address (VIP). The VIP is active on one port at a time. When the primary port is active, VIP is
active on the primary. When the primary fails and the backup port becomes active, VIP is dropped
from the failed primary and becomes active on the backup port. Thus, in AIP failovers, VIP moves
from the primary port to the backup port on the same CAP-1000. It is the job of the IP network to
route traffic correctly to and from the VIP addresses

CAP-1000 Software Guide v4.0 633

Chapter 33 Configuring OSPF OSPF Initialization and Configuration

The CAP-1000 typically ingests and terminates unicast traffic from an ad server and internally
consumes it for ad insertion applications. As such, the CAP-1000 can keep OSPF processing to a
minimum. This ensures that the CAP-1000 does not consume unnecessary internal resources in
performing OSPF functions, such as maintaining and communicating large databases and link state
advertisements.

OSPF Initialization and Configuration

You can enable or disable OSPF on any Gigabit Ethernet interface of the CAP-1000. You can also
configure OSPF on a per-GigE output port basis, including the management port on the DSP or
CR-DSP modules. Each network port on the primary that has enabled OSPF as the routing
protocol must have the OSPF routing protocol on the corresponding backup network port.
The OSPF option is available on the System > Setup > Network tab. You must also set up the
Routing Metric, Router ID, and Area ID parameters.

OSPF Routing Protocol

For correct operation of OSPF, you need to initialize and configure the following parameters:
• Router ID—a 32-bit number. Use the highest IP interface address belonging to the router if the
RouterID is unset (unset meaning not yet defined by the user using the GUI or cleared after
previous definition. Since each router instance on the CAP-1000has only one interface, the
physical IP of the port is used as the RouterID). Otherwise using the RouterID defined by the
user, dotted octets.
• Area ID—a 32-bit number. The backbone has a reserved Area ID of 0.0.0.0. As a member of
the stub network, the CAP-1000 shall support Area ID 1 or 0.0.0.1 or higher.

634 ARRIS Enterprises, Inc.

 OSPF Operation

• Area Address Ranges—each address range is specified by an [address, mask] pair

• Cost
• Timer Intervals

OSPF Operation
Routing Protocol Packets get preference over ordinary data packets both in sending and receiving,
assuming the CAP-1000 will be able to differentiate received packets.
The CAP-1000 shall use the Hello Protocol to acquire and maintain neighbors.
• Hello Packets shall be sent from all OSPF interfaces.
• On broadcast and point-to-point networks, the router dynamically detects its neighboring
routers by multicasting its Hello Packets to the multicast address All SPFRouters.
• On non-broadcast multiple access networks (NBMA), the Hello Packets are first sent by the
DR to the CAP-1000 on initialization. The CAP-1000 responds with Hello Packets of its own.
• On point-to-multipoint networks, Hello Packets are sent to all neighbors that the router can
communicate with directly. Neighbors are discovered dynamically via a protocol, such as
Inverse ARP.

OSPF Adjacencies
Adjacency forming is the process of synchronizing the link state databases of the two routers for
that common area. Adjacency forming shall be attempted by the CAP-1000 when the network type
is point to point broadcast.
The CAP-1000 attempts adjacency forming with a neighbor at each eligible OSPF interface by
sending Database Description packets to the neighbor.
The CAP-1000 shall follow the Database Exchange Process as follows:
• Database Description Packets are sent first, exchanging Link State Acknowledgements
(LSAs) between the routers.
• New or updated LSAs shall be requested in Link State Request Packets.
• New or updated LSAs shall be provided in Link State Update Packets.
• Receipt of each LSA shall be acknowledged via Link State Acknowledgements.
• When the link state databases are synchronized between the two router interfaces the Database
Exchange Process is said to be complete and the interfaces are marked as fully adjacent.
Changes in interface state are conveyed via Router-LSAs contained in Link State Updates or via
Lower level protocols to the attached neighbors. Link state updates are sent out via the Flooding
procedure to all eligible neighbors.
LSAs are retransmitted until they are acknowledged by putting them in Link State Retransmission
Lists. The LSAs in the retransmission list are resent every RxmtInterval until acknowledged. Link
State Databases are said to be synchronized when every single LSA has been acknowledged.

CAP-1000 Software Guide v4.0 635

Chapter 33 Configuring OSPF RFC Supported Functions

RFC Supported Functions

This section lists the supported functions for running OSPF on the CAP-1000:
• Flooding Procedure as defined in RFC2328 OSPF v2.
• OSPF Protocol Data Structures defined in the RFC as required by the functionality described
herein.
• Area Data Structure as defined in the RFC as required by the functionality described herein. A
separate Area Data Structure has to be maintained for each area that router is connected to.
The CAP-1000 shall belong to only a single stub area per interface.
• Interface Data Structure associated with each OSPF interface as defined in the RFC as
required by the functionality described in the RFC.
• Interface States and the Interface State Machine as defined in the RFC as required by the
functionality described in the RFC.
• Each OSPF interface of the CAP-1000 shall support and maintain a Neighbor Data Structure
as defined in the RFC as required by the functionality described herein.
• Neighbor States and the Neighbor State Machine as defined in the RFC as required by the
functionality described herein.
• OSPF Routing Table Structure as defined in the RFC. There shall be a single routing table for
each OSPF enabled CAP-1000. The CAP-1000 shall be capable of calculating its Routing
Table using the attached area’s Link State Database. The CAP-1000 shall be capable of
calculating the Shortest Path Tree for its area with the CAP-1000 itself as the root. The OSPF
enabled CAP-1000 shall be capable of routing packets based on the Routing Table.
• Authentication of OSPF packets via AuType 0 defined in the RFC. AuType 0 is Null or no
authentication.

Optimizing OSPF Configuration in the Network

This section explains how to optimize OSPF.

OSPF Fast Convergence

This section provides optimization tips for fast convergence of the OSPF network due to failures in
the CAP-1000 and/or its Ethernet interfaces (that have been configured for running the OSPF
protocol). Network convergence is the process by which the network converges back to a
synchronized state (synchronization of network forwarding tables) after deliberate or accidental
topology changes occur in the network. Fast convergence refers to the speedy convergence of a
network in response to a topology change.
Fast convergence time for a link-state protocol, such as OSPF is dependent on the following
parameters:
• Time to detect a network failure event e.g., interface down.
• Time to propagate the event e.g., flood the LSA across the affected areas.

636 ARRIS Enterprises, Inc.

 Optimizing OSPF Configuration in the Network

• Time to perform SPF calculations on all routers upon reception of the latest state information.
• Time to update the forwarding tables for all routers in the affected areas.

SPF Throttling
The Shortest Path First (SPF) Throttling feature makes it possible to configure SPF scheduling in
millisecond intervals and to potentially delay SPF calculations during periods of network
instability. SPF is scheduled to calculate the Shortest Path Tree (SPT) when there is a change in
topology. One SPF run may include multiple topology change events.
The interval at which the SPF calculations occur is chosen dynamically and is based on the
frequency of topology changes in the network. The chosen interval is within the boundary of the
user-specified value ranges. If network topology is unstable, SPF throttling calculates SPF
scheduling intervals to be longer until topology becomes stable.
SPF calculations occur at the interval set by the timers throttle spf command. The hold interval
indicates the amount of time to wait until the next SPF calculation occurs. Each hold interval after
that calculation is twice as long as the previous one until the hold interval reaches the maximum
wait (max-wait) time specified.
timers throttle spf initial hold max-wait
The SPF timing can be better explained using an example. In this example the initial interval is set
at 200 milliseconds (ms), the hold interval at 400 milliseconds, and the maximum wait time is set
at 9000 milliseconds.
timers throttle spf 200 400 9000
The above values have been used in the CAP-1000 for optimized failovers.

LSA Generation/Propagation Throttling

Routers running OSPF can perform OSPF LSA throttling. This feature enables fast convergence.
Prior to the introduction of the OSPF LSA, the throttling feature topology changes could not be
advertised by LSA in milliseconds, which prevented OSPF network convergence in the
millisecond time frame. The OSPF LSA throttling also throttles LSA generation, thus preventing
excessive flooding of LSAs within an area.
The LSA throttling feature is enabled by default on routers and its throttling values should be
optimized to obtain desired results. The throttling command is:
timers throttle lsa initial hold max_wait
Three parameters control the throttling process; the initial interval, the hold interval, and the
max_wait interval. All of these values are in milliseconds.

CAP-1000 Software Guide v4.0 637

Chapter 33 Configuring OSPF OSPF Implementation Examples

OSPF Implementation Examples

Using OSPF allow each port and virtual IP to be in a different subnet. Because the CAP-1000 does
function as a router, it only supports the OSPF stub area. The illustration depicts a single VIP that
is used between the Primary CAP-1000 on Port 7 and the Backup CAP-1000 on Port 7.
When a failover event occurs, the VIP is moved to the backup CAP-1000. The VIP is advertised
via OSPF to Router 2. If Port 7 is also an output port, the virtual IP is set as the source IP for the
video packets. This function allows the receiver to see a single multicast source. When using the
virtual IP as the MPEG source IP address, the multicast address used must be in the SSM range
defined for the network environment.

CAP-1000 CPR Implementation with OSPF

638 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

CherryPicker Redundancy (CPR) Implementation

In this CPR example, the following components are used:
• Primary CAP-1000
• Port 1: 192.160.4.2/30 GW: 192.160.4.1
• Backup CAP-1000
• Port 1: 192.160.6.2/30 GW: 192.160.6.1
• Virtual IP: 192.160.5.1/32

Primary CAP-1000 Network Configuration

The following illustration shows an example Primary CAP-1000 network configuration.

Primary CAP-1000 Network Configuration

Backup CAP-1000 Network Configuration

The following illustration shows an example Backup CAP-1000 network configuration.

Backup CAP-1000 Network Configuration

Router 1 Configuration

interface GigabitEthernet1/1
no switchport
ip address 192.160.4.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!

router ospf 1
log-adjacency-changes
area 32 stub
network 192.160.3.168 0.0.0.3 area 0
network 192.160.4.0 0.0.0.3 area 32
!

CAP-1000 Software Guide v4.0 639

Chapter 33 Configuring OSPF OSPF Implementation Examples

Router 2 Configuration

interface GigabitEthernet1/1
no switchport
ip address 192.160.6.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
router ospf 1
log-adjacency-changes
area 62 stub
network 192.160.3.164 0.0.0.3 area 0
network 192.160.6.0 0.0.0.3 area 62
!

Dual-home, Single-source Output Implementation with CPR

This section explains how to configure a dual-home, single-source output implementation with
CPR. Two modes are supported: Backup 1:1 mode and Backup N:1 mode. The following
illustration shows each CAP-1000 connected to two different routers. This configuration provides
an additional link layer and router protection without causing a CAP-1000 failover. It requires that
the multicast addresses at the output of the CAP-1000 are in the SSM range configured on the
router. The receiver specifies the source IP address for the multicast. A single-source IP address is
configured, as well as a virtual IP address (VIP). The VIP advertises as a /32 host via OSPF.

Dual-home, Single-source Output Implementation with CPR

640 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

Two NICs are designated for simultaneous input and output. In the illustration, Ports 7 and 8 are
used on the Primary and Backup CAP-1000 units. Port 7 is configured as the primary input/output
interface for video with a /30 subnet. Port 8 is configured as a mirror of Port 7 with a /30 subnet.
Program Redundancy (PRED) or Multiplex Redundancy (MRED) can be used on Ports 7 and 8.
Both Ports7 and 8 share the same VIP 192.160.5.1/32. Only one port advertises this VIP at any
given time. When Port 7 goes down, Port 8 starts advertising the VIP so the multicast flow can
continue. The CAP-1000 is configured to send a video multiplex with destination IP address
232.20.1.10. The same function applies to the redundant CAP-1000 when it becomes active after
the Primary CA-1000 fails over.
Ports 7 and 8 will both send the multicast 232.20.1.10 with source a IP 192.160.5.1. Because Port
7 is the primary port, it advertises the VIP via OSPF. Router 1 forwards the multicast from Port 7.
Port 8 is also actively transmitting the same multicast 232.20.1.10 with source IP 192.160.5.1.
Because router 2 does not “see” 192.160.5.1 as a valid source, it drops the packet due to a Reverse
Path Forwarding (RPF) check failure.
If a failure occurs with Router 1 or the link on Port 7, the CAP-1000 immediately moves the VIP
to Port 8. Router 2 is now able to forward the multicast to the network cloud. If Ports 7 and Port 8
go down, the Backup CAP-1000 takes over and starts advertising the VIP 192.160.5.1. If input
bandwidth is available, ad insertion could enabled on Ports 7 and 8 using the virtual IP as the
destination for the unicast ad stream.

Output Port Control

The active output port can be controlled in the Redundancy window on the CherryPicker Element
Manager.

Redundancy

CAP-1000 Software Guide v4.0 641

Chapter 33 Configuring OSPF OSPF Implementation Examples

Dual-home, Single-source Output Implementation with AIP

This section explains how to configure a dual-home, single-source output implementation with Ad
Insertion Protection (AIP). The example reuses the configuration described in
section,“CherryPicker Redundancy (CPR) Implementation,”on page 639. Ports 9 and 10 have
been added for ad insertions only. Ports 9 and 10 share a VIP. The ad server uses the VIP to stream
ads to the CAP-1000. Two modes are supported: Backup 1:1 mode and Backup N:1 mode. The
multicast output is in the SSM range.
See section,“OSPF Reference Diagram,”on page 653 for more information.

Ports 7 and 8 Functions

This example uses the Peer Port, Combined Peer Port, Mirror Port, and AIP.
• CAP-1000 joins traffic from both Primary Router and Backup Router (PRED or MRED).
• Ports 7 and 8 share the same VIP 192.160.5.1/32.
• If Port 7 goes down, the VIP moves to the Primary CAP-1000 on Port 8, and advertises via
OSPF.
• If Ports 7 and 8 go down, a CPR failover is triggered. The VIP moves to the Backup
CAP-1000 on Port 7, and advertises via OSPF.
• Only one router forwards the traffic at any given time; it follows the VIP.

Ports 9 and 10 Functions

This example uses the Peer Port, Combined Peer Port, and AIP.
• Ports 9 and 10 share the same VIP 192.160.5.1/32.
• If Port 9 goes down, the VIP moves to the Primary CAP-1000 on port 10, and advertises via
OSPF.
• If Ports 9 and 10 go down, a CPR failover is triggered. The VIP moves to the Backup
CAP-1000 Port 9, and advertises via OSPF.

642 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

Primary CAP-1000 Network Configuration

The following illustration shows an example Primary CAP-1000 network configuration.

Primary CAP-1000 Network Configuration

Backup CAP-1000 Network Configuration (Backup 1:1 Mode and Backup N:1 Mode)
The following illustration shows an example Backup CAP-1000 network configuration.

Backup CAP-1000 Network Configuration (Backup 1:1 Mode and Backup N:1 Mode)

CAP-1000 Software Guide v4.0 643

Chapter 33 Configuring OSPF OSPF Implementation Examples

Router 1 Configuration

# Interface Configuration:

interface GigabitEthernet1/1
no switchport
ip address 192.160.4.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/2
no switchport
ip address 192.160.4.5 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/3
no switchport
ip address 192.160.4.9 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/4
no switchport
ip address 192.160.4.13 255.255.255.252
ip pim sparse-mode
!
#OSPF Configuration:
router ospf 1
log-adjacency-changes
area 32 stub
area 33 stub
area 34 stub
area 35 stub
network 192.160.3.168 0.0.0.3 area 0
network 192.160.4.0 0.0.0.3 area 32
network 192.160.4.4 0.0.0.3 area 33
network 192.160.4.8 0.0.0.3 area 34
network 192.160.4.12 0.0.0.3 area 35
!

644 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

Router 2 Configuration

# Interface Configuration:

interface GigabitEthernet1/1
no switchport
ip address 192.160.6.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/2
no switchport
ip address 192.160.6.5 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/3
no switchport
ip address 192.160.6.9 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/4
no switchport
ip address 192.160.6.13 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
#OSPF Configuration:
router ospf 1
log-adjacency-changes
area 62 stub
area 63 stub
area 64 stub
area 65 stub
network 192.160.3.164 0.0.0.3 area 0
network 192.160.6.0 0.0.0.3 area 62
network 192.160.6.4 0.0.0.3 area 63
network 192.160.6.8 0.0.0.3 area 64
network 192.160.6.12 0.0.0.3 area 65
!

Dual-home, Dual-source Output Implementation with AIP

This section explains how to configure the CAP-1000 mirror output to use a different VIP source
address. Ports 7 and 8 are the input and output, respectively. Ports 9 and 10 are used for ad
insertion with AIP. Two modes are supported: Backup 1:1 mode and Backup N:1 mode.
The router configuration uses the configuration described in section,“CherryPicker Redundancy
(CPR) Implementation,”on page 639. Ports 7 and 8 are used for input in PRED and MRED. The
multicast output must be in the SSM range.

CAP-1000 Software Guide v4.0 645

Chapter 33 Configuring OSPF OSPF Implementation Examples

See section,“OSPF Reference Diagram,”on page 653 for more information.

Dual-home, Dual-source Output Implementation with AIP

In this example, the following VIP address are assigned on the Primary CAP-1000:
• Port 7: 192.160.5.1
• Port 8: 192.160.5.2
• Port 9-10: 192.160.5.3

Ports 7 and 8 Functions

This example uses the Peer Port, Combined Peer Port, and Mirror Port.
• Primary CAP-1000 Ports 7 and 8 are bundled together.
• CAP-1000 joins traffic from both the Primary Router and Backup Router (PRED or MRED).
• Port 7 VIP 192.160.5.1/32 Port 8 VIP 192.160.5.2/32.
• VIP is used for MPEG source.

646 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

• If Ports 7 and 8 are down, a CPR failover ia triggered. The VIP moves to the backup
CAP-1000 Port 7 via OSPF.
• The edge device selects the best available source (192.160.5.1 or.192.160.5.2).

Ports 9 and 10 Functions

This example uses the Peer Port, Combined Peer Port, and AIP.
• Primary CAP-1000 Ports 9 and 10 are bundled together for ad insertion.
• Ports 9 and 10 share the same VIP 192.160.5.3/32.
• If the Primary CAP-1000 Port 9 goes down, the VIP moves to the Primary CAP-1000 port 10.
• If the Primary CAP-1000 Ports 9 and 10 are down, a CPR failover is triggered, and the VIP
moves to the Backup CAP-1000.

Primary CAP-1000 Network Configuration

The following illustration shows an example Primary CAP-1000 network configuration.

Primary CAP-1000 Network Configuration

CAP-1000 Software Guide v4.0 647

Chapter 33 Configuring OSPF OSPF Implementation Examples

Backup CAP-1000 Network Configuration

The following illustration shows an example Backup CAP-1000 network configuration.

Backup CAP-1000 Network Configuration

Dual-home, Multi-source Output Implementation with CPR

This section describes a Dual-home, Multi-source Output Implementation with CPR. Each
CAP-1000 connects to two different routers. Both routers receive multicast traffic for the same
source. The receiver receives one copy of the multicast based on the unicast route OSPF cost. Two
modes are supported: Backup 1:1 mode and Backup N:1 mode.
This example requires that the multicast addresses at the output of the CAP-1000 are in the SSM
range configured on the router. The receiver specifies the source IP address for the multicast. A
single-source IP address is configured as VIP. The VIP advertises as a /30 subnet via OSPF.
See section,“OSPF Reference Diagram,”on page 653 for more information.

648 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

Dual-home, Multi-source Output Implementation with CPR

Two NIC are designated for simultaneous input and output. In this example, Ports 7 and 8 are used
on the Primary and Backup CAP-1000.

Port 7 and 8 Functions

This example uses the Peer Port, Combined Peer Port, and Mirror Port.
• Port 7 is configured as the primary input/output interface for video with a /30 subnet.
• Port 8 is configured as a mirror of Port 7 with a /30 subnet.
• CAP-1000 joins traffic from both the Primary Router and Backup Router (PRED or MRED).
• Ports 7 and 8 share the same virtual IP subnet.
• Ports 7 and 8 send multicast traffic using the same source IP (192.160.5.1).
• Ports 7 and 8 advertise the virtual IP subnet to router 1 and 2.
• OSPF cost will be the deciding factor selecting which router forwards the multicast to the
edge.

CAP-1000 Software Guide v4.0 649

Chapter 33 Configuring OSPF OSPF Implementation Examples

• AIP cannot be used on Ports 7 and 8.

• If Ports 7 and 8 are down, a CPR failover is triggered. The VIPs move to the Backup
CAP-1000 port 7/port 8, and advertises via OSPF.
In this example, the CAP-1000 is configured to send a video multiplex with destination IP
232.20.1.10. The same functions apply to the Backup CAP-1000 when it becomes active. If there
is a problem with Router 1 or the link on Port 7, the networks converge on Router 2 to forward the
multicast.

Primary CAP-1000 Network Configuration

The following illustration shows an example Primary CAP-1000 network configuration.

Primary CAP-1000 Network Configuration

Backup CAP-1000 Network Configuration

The following illustration shows an example Backup CAP-1000 network configuration.

Backup CAP-1000 Network Configuration

650 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

Router 1 Configuration

# Interface Configuration:

interface GigabitEthernet1/1
description PrimaryCAP port 7
no switchport
ip address 192.160.4.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/2
description PrimaryCAP port 9
no switchport
ip address 192.160.4.5 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/3
description BackupCAP port 7
no switchport
ip address 192.160.4.9 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/4
description BackupCAP port 9
no switchport
ip address 192.160.4.13 255.255.255.252
ip pim sparse-mode
!

#OSPF Configuration:
router ospf 1
log-adjacency-changes
area 32 stub
area 33 stub
area 34 stub
area 35 stub
network 192.160.3.168 0.0.0.3 area 0
network 192.160.4.0 0.0.0.3 area 32
network 192.160.4.4 0.0.0.3 area 33
network 192.160.4.8 0.0.0.3 area 34
network 192.160.4.12 0.0.0.3 area 35
!

CAP-1000 Software Guide v4.0 651

Chapter 33 Configuring OSPF OSPF Implementation Examples

Router 2 Configuration

# Interface Configuration:

interface GigabitEthernet1/1
description PrimaryCAP port 8 BFeed
no switchport
ip address 192.160.6.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/2
description PrimaryCAP port 10
no switchport
ip address 192.160.6.5 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/3
description BackupCAP port 8 BFeed
no switchport
ip address 192.160.6.9 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
interface GigabitEthernet1/4
description BackupCAP port 10
no switchport
ip address 192.160.6.13 255.255.255.252
ip pim sparse-mode
ip igmp version 3
!
#OSPF Configuration:
router ospf 1
log-adjacency-changes
area 62 stub
area 63 stub
area 64 stub
area 65 stub
network 192.160.3.164 0.0.0.3 area 0
network 192.160.6.0 0.0.0.3 area 62
network 192.160.6.4 0.0.0.3 area 63
network 192.160.6.8 0.0.0.3 area 64
network 192.160.6.12 0.0.0.3 area 65
!

652 ARRIS Enterprises, Inc.

 OSPF Implementation Examples

OSPF Reference Diagram

OSPF Reference Diagram

CAP-1000 Software Guide v4.0 653

Chapter 33 Configuring OSPF OSPF Implementation Examples

654 ARRIS Enterprises, Inc.

 CHAPTER 34
Analyzing Streams and Programs

In This Chapter
• Analysis
• Stream Analysis
• Program Analysis
• Starting Analysis
• Stopping Analysis

Analysis
The Analysis window lets you monitor the system, troubleshoot problems, and see historical
performance information about streams and programs from both input and output multiplexes for
comparative data analysis. This data helps you to troubleshoot problems and provides a visual
indication when resources are oversubscribed.
Information about various characteristics of MPEG streams is measured and presented in two
categories:
• Stream Analysis—provides information about all programs at a selected input or output port
or multiplex. Any input or output port can be selected. Only one selected port is analyzed at a
time.
• Program Analysis—provides information about all elementary streams in a selected program.
Any program at any CherryPicker input can be selected. Only one selected program is
analyzed at a time.
Analysis data is only updated when the Analysis window open and active. Leaving the window, or
inactivity for more than 15 seconds, causes the window to be refreshed when you return to it.

CAP-1000 Software Guide v4.0 655

Chapter 34 Analyzing Streams and Programs Stream Analysis

Stream Analysis
The Stream Analysis window measures the following parameters for the specified input or output:
• Average bit rate of every program at this Transport Stream
• Average rate for the entire Transport Stream
• Total rate for every Stat Mux Pool in this Transport Stream
• Recoding percentage for every recoded output program and recoded output multiplex
• Alarm severities at the multiplex level
The default view for the Stream Analysis window shows all enabled input and output lines (feeds)
for the selected CAP-1000, along with the total bit rate, average bit rate, and date/time. The
individual lines are labeled 1/1, 1/2, 1/3, and 1/4. They correspond to the Gigabit Ethernet ports on
the IOA of the CAP-1000. Another line, 1/* represents the sum total of lines 1/1 to 1/4.

Stream Analysis

The Stream Analysis window is divided into three main sections:

• Component Tree
• Input/Output Analysis graph
• Toolbar

656 ARRIS Enterprises, Inc.

 Stream Analysis

Component Tree
The Component Tree in the left panel is used to select a line, multiplex, or program from the
CAP-1000.

Input/Output Analysis Graph

The center panel displays each input and output lines of the CAP-1000 in a unique color. Input
lines are shown in the top panel and output lines are shown in the bottom panel. All lines with
throughput are stacked in the chart and the chart moves right to left as time progresses (oldest
entries to the left). Moving the mouse over a specific data point of a line displays the name, total
line rate, average line rate, and date/time for the selected line.
The vertical axis of the graph represents bit rate in megabits per second and the horizontal axis
represents minutes. The graphs automatically resizes in the individual panels if the Stream
Analysis window is resized.

Legend
The individual lines, 1/*, 1/1, 1/2, 1/3, and 1/4, are shown in a legend on the right side of the Input
and Output line panels. Clicking a data point on 1/* shows the name, total line rate, average line
rate, and date/time for all lines.

Legend

Selecting a square next to the line number lets you assign a color to the line using the Choose
Color dialog.

CAP-1000 Software Guide v4.0 657

Chapter 34 Analyzing Streams and Programs Stream Analysis

Choose Color

Toolbar
Table 34-1 describes the buttons in the toolbar.

Table 34-1 Toolbar

Button Description

Zooms in on the Input/Output panel to show more detail.

Note: You can also zoom in by placing the cursor on a particular portion of the graph and clicking the left
mouse button. As soon as you release the left mouse button, the GUI zooms in and centers the graph
around the portion you just selected.

Zooms out on the Input/Output panel to show less detail.

Scales the graphs to the window.

Toggles the background color between gray and black.

658 ARRIS Enterprises, Inc.

 Program Analysis

CALM Dialnorm Values

The input dialnorm values of the source audio elementary streams are reported in the Analysis
window (dialnorm2 is ignored). “N/A” is displayed when the elementary streams are encrypted. If
the audio stream header has not been obtained yet (for example, it might be encrypted), then the
message, “Dolby Digital Audio Dialnorm NA” displays. If the dialnorm value in the AC3 stream
header is 0, then “Dialnorm 0” appears as part of the stream description, as in “Dolby Digital
Audio Dialnorm 0.” Otherwise, it will contain a valid number of decibels.

Program Analysis
Selecting an input multiplex in the Component Tree changes the Stream Analysis window to the
Program Analysis window. The following parameters of a program are determined from the
streams measured in the Program Analysis window:
• Average bit rate of a program
• Elementary stream types
• Average bit rate of every stream in a program, including video, audio, private data, and private
sections (tables) streams
• Frame rate of the video streams
• Frame size of the video streams
• Recoder lossy and lossless reduction on an output program

Program Analysis

CAP-1000 Software Guide v4.0 659

Chapter 34 Analyzing Streams and Programs Program Analysis

The Program Analysis window is divided into three main sections:

• Component Tree
• Analysis graph
• Information panel

Component Tree
To view multiplex information, select a GigE or ASI Multiplex node from the Component Tree in
the left panel.

Analysis Graph
The center panel displays each program of a multiplex in a unique color. All programs with
throughput are stacked in the chart and the chart moves right to left as time progresses (oldest
entries to the left). Moving the mouse over each colored section displays the program name and
rate for the program at a point in time.

Information Panel
The Information panel on the right displays mux rate information and a program legend to help
identify programs in the graph. Table 34-2 describes the parameters in this panel.

Table 34-2 Program Analysis Parameters

Total Mux Rate Shows the total rate of the multiplex in megabits per second.

Aggregate Rate Shows the sum of all elementary stream average rates in the multiplex in
megabits per second. The PSI/SI rates are not included in this quantity; they are
included in the overhead rate.

Reduction Both lossy and lossless recoder efficiency for a multiplex are reported in the
Analysis window. This information provides an average of reductions across the
component programs:
• Lossy reduction—This reduction signifies the actual reduction in picture. For
example, the size of the original picture size minus recoded picture size (after
removal of bit stuffing).
• Lossless reduction—This reduction reports the percentage of stuffing bits
removed by the recoder.
Recoding efficiencies are reported for both MPEG-2 and MPEG-4. When a mux is
not fully utilized (null stuffing packets are present at output), the lossy reduction is
zero percent. Lossless reduction may still be greater than zero percent for an
under-utilized mux due to dropping stuffing bits through the recoder.

Video Stream

Frame Rate Shows the number of video frames per second.

Frame Size Shows the picture resolution of video stream.

660 ARRIS Enterprises, Inc.

 Program Analysis

Table 34-2 Program Analysis Parameters (continued)

Program Analysis

Type Shows the stream type; audio, video, or data as represented by an icon.

PID Shows the streams passed to the passed PIDS.

Description Shows the stream type.

Avg Rate Average bit rate, n megabits per second, of every stream in a program, including
video, audio, data, and private sections (tables) streams.

Output Mux Information

Selecting an output mux displays the Total Mux Rate and Aggregate Rate at the top of the
Information panel.

If the output mux contains stat mux pools, the Total Mux Rate, Aggregate Rate, and Reduction
parameters display at the top of the Information panel. Hide Pools and Show Pools options are also
provided. Selecting an individual pool displays the Total Rate and Reserved Rate information for
that pool.

CAP-1000 Software Guide v4.0 661

Chapter 34 Analyzing Streams and Programs Program Analysis

Program Legend
The legend section lists programs currently shown in the graph. Each program has a unique name
and color. Encrypted programs have an asterisk (*) character in the name. You can select a
program within a graph by clicking the graph. The corresponding program is highlighted in the
legend and the program analysis is started.

Input Mux Information

The Video Stream and Program Analysis areas display analysis information for input muxes only.

The Average Program Bit Rate section is based on the transport stream packet count, assuming
that each packet has 188 bytes. The time interval for rate measurement is five seconds. The
average bit rate of a program includes the sum of average rates of all PIDs defined in the PMT for
the program. It does not include the rate of the PMT itself. If a particular PID is defined for more
than one program, it is used in calculating the average rate for each program for which it is
defined.

662 ARRIS Enterprises, Inc.

 Starting Analysis

Starting Analysis
To start analysis:
1 From the CherryPicker Element Manager, click Analysis.
By default, analysis starts for all enabled lines in the IOA.
2 To view stream data, click the Device node at the top of the Component Tree.
The Stream Analysis window displays.

Analysis

3 Do the following:
• To view the name, total line rate, average line rate, and date/time for all lines, click a data point
on the 1/* line. Information displays in a pop-up near the mouse pointer.

CAP-1000 Software Guide v4.0 663

Chapter 34 Analyzing Streams and Programs Starting Analysis

Analysis

• To view input and output data for a line, select a Line node in the Component Tree.

Analysis

• To view data for a specific line, select the line label from the Line legend on the right-side of
the panel.

664 ARRIS Enterprises, Inc.

 Starting Analysis

Analysis

• To add more lines to the analysis, select a line number and use CTRL+click.

Analysis

CAP-1000 Software Guide v4.0 665

Chapter 34 Analyzing Streams and Programs Starting Analysis

• To zoom in, zoom out, or scale the graph, click the + or - icons at the top of the Input or Output
panel.

Analysis

• To scale the view, click the Scale to Fit icon.

Analysis

666 ARRIS Enterprises, Inc.

 Stopping Analysis

• To return to the device view, select the Device node at the top of the Component Tree.

Analysis

Stopping Analysis
Analysis data is only updated when the Analysis window is open and active. While you are
working with other windows, no updates are being made to the graph. Information displayed
before you left the window remains on the graph. Once you return to the Analysis window,
information begins updating again.
The analysis stops under the following conditions:
• You navigate away from Analysis window and returns within 10 seconds, the same analysis
continues in the background. If you do not return to the window within 10 seconds, the
analysis stops.
• The CPR mode or state changes.

CAP-1000 Software Guide v4.0 667

Chapter 34 Analyzing Streams and Programs Stopping Analysis

668 ARRIS Enterprises, Inc.

 CHAPTER 35
Managing Alarms and Logs

In This Chapter
• Alarms and Events
• Alarms Window
• Settings Window
• Other Alarms in the GUI
• Managing Alarms
• Configuring Alarm Settings
• Collecting Logs
• Working with Managed Groups of CAP-1000 or AGB240 Devices

Alarms and Events

The CAP-1000 reports on alarms and normal events. A raised alarm notifies the user when a
normal or abnormal condition is occurring. Some alarms are cleared automatically by the device
when the device determines that the condition no longer exists. Other alarms are cleared by the
user when the user determines that the condition no longer exists. Some alarms have user-
configurable debouncing durations for alarms. An event notifies a user of an incident that simply
occurs. It does not have a raised or cleared status.
The CAP-1000 has one list of alarms that can be accessed. The content of the list is persistent
across restarts. The alarm log file is stored in the /usr/cp/Log directory on the CAP-1000.

CAP-1000 Software Guide v4.0 669

Chapter 35 Managing Alarms and Logs Alarms and Events

Alarms and Events

NOTE There are some alarms that might be raised a second time without the preceding alarm being cleared. If a
new alarm is raised without the previous one being cleared, then the new alarm is ignored, as the condition
that triggered the first alarm still exists.

Alarm States
Alarms have two states: set and cleared. Every alarm that has a code with a severity other than
“Event,” is created in the raised state and can be cleared. The only update allowed to an alarm is to
clear it. An Event alarm cannot be cleared.
When an alarm is cleared, the time it is cleared is stored in the alarm. If the alarm is cleared
manually by a user, then the user name of the user is also stored in the alarm. There are two ways
to identify the alarms to clear: by alarm ID and by alarm source. An alarm ID uniquely identifies
an individual alarm. An alarm source identifies zero or more alarms that all have the same source.
When a source is specified, all alarms for the source node and its child nodes are cleared. For
example, if a source node is empty, such as the device node, then all raised alarms in the entire
CAP-1000 are cleared.
Raised alarms are automatically cleared before they are deleted.

Alarm Sources
Every alarm has an object called the “source object” which is the object most closely associated
with the alarm. In the GUI, the source is called the “affected node.” An alarm belongs to its source.
The source is identified by means of named attributes (name-value pairs) as described below.

670 ARRIS Enterprises, Inc.

 Alarms and Events

Affected Node

Device Source
If the source of an alarm contains no attributes, then its source is the device as a whole. To display
alarms in SGCM mode for multiple devices, the GUI identifies the device ID for each alarm, but
the Controller and the alarm do not include the device ID for each alarm because all alarms on a
particular device are only for that device.

Line Source
If the source of an alarm contains only a line attribute, such as line=1/3o, then the source of the
alarm is the identified line. The line can be an output line or an input line. For example, when the
MPEG output mode is changed from active to standby the alarm has a line as its source.

Mux Source
If the source contains only a line attribute and a mux attribute, such as line=1/3o and mux=000E,
then the source of the alarm is the mux identified by the source attributes. The mux can be an
output mux or an input mux as indicated by the line ID. Maximum bandwidth of output mux
exceeded is an example of an alarm that has a mux as its source. Alarms related to tables have a
mux as their source. For example, Corrupted SCTE 35 splicing table is an example of a table alarm
that has an input mux as its source. In the case of table alarms, the source includes an attribute that
identifies the PID of the table, such as Input PID=1001, in which case the alarm has the given PID
as its source (a child node of the mux node in the configuration tree).

CAP-1000 Software Guide v4.0 671

Chapter 35 Managing Alarms and Logs Alarms and Events

Program Source
If the source contains a line attribute, a mux attribute, and a program attribute, such as line=1/3o,
mux=000E, and program=7, then the source of the alarm is the program. The program may be an
output program or an input program as determined by the line ID. Recoder assignment failed is an
example of an alarm that has an output program as its source.

Elementary Stream Source

If the source contains a line attribute, a mux attribute, a program attribute, and an elementary pid
attribute, then the source of the alarm is the elementary stream identified by the source attributes.
Splice failed, no input stream is an example of an alarm that has an elementary stream as its
source.

DPI Connection Source

All DPI errors are treated the same as alarms and events for other CAP-1000 features. The source
of some DPI alarms or events is the combination of the DPI channel name and the ad server IP
address. This source represents the DPI connection between the given ad server and the given
channel name. In cases where the output program has been identified, the source is the output
program plus the channel name and the ad server IP address.

Primary Device Source

If the source contains only a Primary CAP-1000, such as Primary CAP=10.77.188.101, then the
source of the alarm is the primary CAP-1000. For example, the alarm, “Primary CAP denied CPR
protection, not defined in backup group,” is an example of an alarm that has a primary device as its
source. This type of alarm occurs on a CPR backup device

Other Sources
There are many other source attributes that are not identified in this document. Refer to the
CAP-1000 Error Code Reference Guide for more information.

Alarm History
The CAP-1000 keeps all raised alarms, but it does not keep more than one raised alarm for a given
affected node. However, the CAP-1000 cannot maintain an unlimited history of cleared alarms
without running out of memory or persistent storage. Therefore, cleared alarms and events are
deleted (archived) when there are too many of them.
When an event or cleared alarm is removed from active storage, it is retained in the alarm archive.
The archive consists of zero or more archive files. The contents of the archive files are not
displayed in the GUI, but can be displayed using the AlarmDisplay command. They can be
retrieved by the Log Collector (see section,“Collecting Logs,”on page 693 for information).
A maximum of 10 archive files, each one with a maximum size of 1 megabyte, are retained.The
total number of alarms that can be archived is approximately 60,000. When the total alarm archive
storage reaches 10 megabytes, the oldest archive file is purged from the data flash to make room
for the newest archive file.

672 ARRIS Enterprises, Inc.

 Alarms Window

Alarms are kept in persistent storage on the Data Flash so that they can survive a restartfarmer
command, a reboot, or a power fail without the alarms and events getting lost. The debounce,
severity, and alarm history settings are persisted in an XML file that is separate from the
CAP-1000 database.

Shared Input PIDs

The CAP-1000 supports shared input PIDs. A shared input PID is a PID that is shared by multiple
programs (PMTs) in the input mux. When the Core reports an alarm with an input PID as the
source object, it reports only the mux ID and the PID number. In the case of a shared PID, the
Controller duplicates the alarm for every input elementary stream that shares the PID so that the
Severity Propagation and Include Child Nodes features work correctly.

Alarms and Redundancy

This section explains how the CAP-1000 handles alarms for a CPR configuration.
• The alarms on a primary CAP are not synchronized to the backup CAP-1000. The Primary All
alarms at the mux level or lower are cleared and deleted during a CPR failover/failback.
Preserving the alarms on the line level maintains a record of why the failover occurred.
• A failback clears the failover alarm. This applies to CPR, PRED and MRED failover/failback.
An AIP switch will continue to generate a new event for every switch, since there is no
primary or backup line for AIP.

Alarms Window
The Alarms window lets you view and manage alarms and events for system operations. It
provides Alarms and Settings subtabs that let you view, configure, or manage CAP-1000 alarms.
With the Alarms window, you can:
• View active alarms
• Sort, filter, and find events
• Clear alarms
• View alarms history
• Modify alarm settings

Alarm Filters
The Alarms window provides check boxes for filtering alarms and events.

CAP-1000 Software Guide v4.0 673

Chapter 35 Managing Alarms and Logs Alarms Window

Filters

Table 35-1 Alarm Filters

Critical Shows service-affecting conditions that have occurred and require immediate corrective
action. Such a severity can be reported, for example, when a managed object becomes
totally out of service and its capability must be restored.

Major Shows service-affecting conditions that have developed and require urgent corrective
action. Such a severity can be reported, for example, when there is a severe
degradation in the capability of the managed object and its full capability must be
restored.

Minor Shows non-service affecting fault conditions that require corrective action to prevent a
more serious (for example, service affecting) fault. Such a severity can be reported, for
example, when the detected alarm condition is not currently degrading the capacity of
the managed object.

Warning Shows a potential or impending service-affecting fault. Action should be taken to

diagnose (if necessary) and correct the problem in order to prevent it from becoming a
more serious service affecting fault.

Info Shows additional information for this event.

Event Shows normal occurrences that do not represent a condition or require user attention.
An event is not raised or cleared; it simply occurs. It does not have a raised/cleared
statu, nor does it have a Cleared Time or a Cleared User indicator. An event is not de-
bounced.

Raised Only Shows only raised alarms.

674 ARRIS Enterprises, Inc.

 Alarms Window

Table 35-1 Alarm Filters (continued)

DPI Results Only Shows alarms and events related to Digital Program Insertion (DPI) splicing.

DPI Init/DPI Results Shows alarms and events related to DPI requests

Collapse Controls what information displays in the Alarm panel:

• Expanded mode—Shows each alarm instance in its own row.
• Collapsed mode—All alarms for a given scope (the affected node) are displayed in a
single row in summary form with an alarm count and an alarm percent. The percent
is the percent of all displayed alarms and events which occur in the collapsed row.
In expanded mode, you can correlate alarms in time. Collapsed mode prevents the
screen from too-frequent updates from high-frequency repeating alarms. It also gives
the total count for each alarm scope.

Include Child Nodes Shows the alarms for the selected nodes in the tree, or the alarms for the selected
nodes and the child nodes.

Time Filter Filters on the supplied start and end date/time.

Search Description Filters on a string.

If you use SNMP, you can filter by trap codes. Refer to section,“Filtering Trap Codes,”on page 101
for information.

Affected Node Tree

The Affected Node Tree, located on the left side of the window, provides a hierarchical display of
the hardware components and inputs that can be groomed through a CAP-1000. Each component
is depicted as a node of the tree. When you select one or more nodes in the tree, the alarms for
these nodes appear in the panel at the right. The source of the alarm can be one of the following:
device, line, mux, program, or stream (PID).
For example, the source of a DPI alarm includes the ad channel name and the IP address of the ad
server as attributes. Only the line, mux, program, and stream attributes in the source of the DPI
alarm are used to identify the hierarchy level of the alarm. If none of these standard source
attributes is present, then the alarm is at the device level.

CAP-1000 Software Guide v4.0 675

Chapter 35 Managing Alarms and Logs Alarms Window

Affected Node Tree

You can view the tree in collapsed or expanded mode. It is also possible to select individual nodes
and expand them for greater detail. Selecting a node in the tree displays the applicable normal
events, errors, and alarms in the Alarm panel to the left.

NOTE The tree filter applies only to the currently selected CAP-1000. It does not apply to Single GUI Centralized
Management (SGCM) groups. A Device parameter is supplied in the Alarm panel for SGCM groups. See
section,“Working with Managed Groups of CAP-1000 or AGB240 Devices,”on page 695 for more
information.

Alarm Table
The Alarm table displays normal events, errors, and alarms based on the options selected in the
Show panel. All alarm columns can be sorted in ascending and descending order. The following
table describes the parameters that can display in the Alarm table, depending on the Collapse
option selected in the Show panel.

Table 35-2 Alarm Table

% (Collapse mode) Shows the percent of all displayed alarms and events which occur in
the collapsed row.

Count (Collapse mode) Shows the number of alarms in the collapsed view.

676 ARRIS Enterprises, Inc.

 Alarms Window

Table 35-2 Alarm Table (continued)

State Shows the state of the alarm:

• Raised—When an alarm occurs it is in the raised state.
• Cleared—When an alarm is cleared, it is in the cleared state. When an alarm is
cleared by a user, this field contains the user ID. When an alarm is cleared by the
device, this field is empty.
• NA—An event.

Severity Shows the severity level description and color. See Table 35-3 on page 678 for
more information.

Description Provides a description of the alarm.

Affected Node Shows the node associated with the alarm.

Parameters Shows the alarm parameters as a list of name-value pairs.

Occurred Date/Time Shows the UTC date and time when the alarm was raised or the event first occurred.

Cleared Date/Time Shows the UTC date and time when the alarm was cleared.

Feature Shows the product feature associated with the alarm.

Error Code Shows the error code associated with the alarm. The error code is used by the ARRIS
Technical Assistance Center to debug system problems.

ID Shows the primary key for the alarm.

ETR-290 Classifies the alarm code according to ETSI TR 101 290 v1.2.1 (2001-05)
(tr_101290v010201p.pdf).

SCTE 142 Classifies the alarm code according to SCTE 142 2009 (ANSI_SCTE 142 2009.pdf).

Device (SGCM) Applies to Single GUI Centralized Management (SGCM) groups. In SGCM mode, a
Device column is included in the Alarm panel. In non-SGCM mode, neither the Device
filter nor the Device column are displayed. The Device filter shows alarms for only one
of the connected devices. See section,“Working with Managed Groups of
CAP-1000 or AGB240 Devices,”on page 695 for more information.
Note: When SGCM is in effect, the GUI monitors the alarms of multiple CAP-1000
units. The alarms for all the CAP-1000 systems in the group are mixed together in the
Alarm panel. The alarm severity counts include the alarms of all the devices in the
group.

CAP-1000 Software Guide v4.0 677

Chapter 35 Managing Alarms and Logs Alarms Window

Severity
The Alarm panel reports six severity levels. Every error code is assigned a severity level. These
levels are referred to as default severity levels.

Table 35-3 Alarm Severity Levels

Critical Indicates that a service-affecting condition has occurred and an immediate corrective action is
required. Such a severity can be reported, for example, when a managed object becomes
totally out of service and its capability must be restored.

Major Indicates that a service-affecting condition has developed and an urgent corrective action is
required. Such a severity can be reported, for example, when there is a severe degradation in
the capability of the managed object and its full capability must be restored.

Minor Indicates the existence of fault condition (not service-affecting) and that corrective action
should be taken in order to prevent a more serious (for example, service affecting) fault. Such a
severity can be reported, for example, when the detected alarm condition is not currently
degrading the capacity of the managed object.

Warning Indicates the detection of a potential or impending service affecting fault, before any
significant effects have been felt. Action should be taken to further diagnose (if necessary) and
correct the problem in order to prevent it from becoming a more serious service affecting fault.

Info Indicates a non-error alarm.

Event Indicates an event.

Cleared The color green is associated with cleared alarms, regardless of their severity.

Users with appropriate permissions can change the severity levels for all alarms through the
Settings tab of the Alarms window. Users cannot change the severity of an event to an alarm
severity, or vice-versa.

Detail Panel
Details about a selected events or alarms are displayed in the Detail panel at the bottom of the
window. This panel contains many of the parameters shown in the Alarm panel as well as advice
on how to handle the alarm.

Table 35-4 Detail Panel

Code Shows the error code associated with the alarm. The error code is used by the ARRIS
Technical Assistance Center to debug system problems.

Description Provides a description of the alarm.

Node Shows the affected node.

Parameters Shows the alarm parameters as a list of name-value pairs.

678 ARRIS Enterprises, Inc.

 Alarms Window

Table 35-4 Detail Panel (continued)

Advice Gives advice on how to resolve the issue.

Severity Shows the severity level description and color. See Table 35-3 on page 678 for
more information.

Cleared By Specifies the name of the user who manually cleared the alarm if the alarm was
cleared manually.

Occurred Shows the UTC date and time when the alarm was raised or the event first occurred.

Cleared Shows the UTC system date and time when the alarm was cleared.

Info Provides additional information about this alarm, if any.

Delete Deletes the selected alarm.

Copy Captures the alarms that are displayed in the GUI for the current set of filters. Select
the alarms with the cursor or press CTRL-A, copy the selected alarms to the clipboard,
and the paste the contents of the clipboard into a text document or Excel spreadsheet.

Clear Clears the selected alarm.

Show Detail Toggles the Details panel on.

Hide Detail Toggles the Details panel off.

Context Menu
Separate Context menus are provided for the Affected Node Tree and the Alarm table. Selecting an
element and clicking the right mouse button causes a Context menu to appear. Actions that are
supported for the selected element are boldface. Actions that are not applicable to the selected
element are grayed out.

CAP-1000 Software Guide v4.0 679

Chapter 35 Managing Alarms and Logs Alarms Window

Context Menu

Table 35-5 describes the commands that can appear in the Context menu.

Table 35-5 Context Menu

Affected Node Tree

Delete Alarms and Child Deletes the alarms for the source node and its child nodes.
Node Alarms

Clear Alarms and Child Node Clears the alarms for the source node and its child nodes.
Alarms

Alarm Table

Show in Tree Shows the affected node in the tree for a selected alarm.

Show Input in Tree Shows the input source for a selected alarm in the tree. For example, an elementary
stream associated with a program groom.

Clear Clears the selected alarm and removes it from the panel.

Delete Deletes the selected alarm and removes it from the panel.

680 ARRIS Enterprises, Inc.

 Settings Window

Settings Window
The Settings window is where you can change the default values for clearing and limiting the
number of alarms and events.
The Settings window depicts per-device alarm settings and a table of settings for each alarm code.
The settings for each alarm code consist of the following: code, feature, severity, debouncing-ms,
hierarchy, description, and advice. Only the severity and the debouncing-ms settings can be
modified by the user. Only certain alarm codes are debounceable. The columns in this window can
be sorted for your convenience.

Settings

The following table describes the parameters that are displayed in the Settings panel.

Table 35-6 Settings Parameters

Archive cleared alarms and Causes cleared alarms older than the given duration to be archived. For example, if
events after the expiration time is 3 days, then any cleared alarm or event older than 3 days is
archived. The allowed values are 1-30 days. The default value is 3 days.

Max cleared alarms and Defines the maximum number of events and cleared alarms that are preserved. When
events the maximum is reached, the oldest existing event or cleared alarm is archived to
make room for the new one. The allowed values are 10-10000. The default is 2000.

Severity Specifies the severity of the alarm. Alarms with a severity of Event cannot be raised
or cleared, hey just occur. Alarms with the other severity values are raised and
cleared. See Table 35-3 on page 678 for more information.

Hierarchy Specifies the type of node in the Tree with which the alarm code is most closely
associated: Device, Line, Mux, Program, or Stream.

Debounce Shows the current debounce duration and enables a user to change the duration.

Description Provides a description of the alarm.

Advice Specifies what to do when an alarm with this code occurs.

CAP-1000 Software Guide v4.0 681

Chapter 35 Managing Alarms and Logs Other Alarms in the GUI

Table 35-6 Settings Parameters (continued)

Feature Shows the feature most closely related to the alarm code, such as DPI, CPR, Groom,
etc. Alarms related to the base functionality of the device have feature a value of
“Base.”

Error Code Shows the error code associated with the alarm. The error code is used by the ARRIS
Technical Assistance Center to debug system problems.

ID Shows the primary key for the alarm in the database.

ETR-290 Classifies the alarm code according to ETSI TR 101 290 v1.2.1 (2001-05)
(tr_101290v010201p.pdf).

SCTE 142 Classifies the alarm code according to SCTE 142 2009 (ANSI_SCTE 142 2009.pdf).

Other Alarms in the GUI

You can get a quick status of the CAP-1000’s health from any window in the CherryPicker
Element Manager. The lower left corner of the window shows icons that represent the total number
of alarms with Critical, Major, and Minor severities.

CherryPicker Element Manager

Clicking on an Severity icon causes the Alarms window in the Alarms tab to display so you can
obtain additional information about the errors.
In the Content Picking > Grooming window there is a new panel called Alarms that displays the
alarms for the selected output program. This panel is similar to the main Alarm panel except that
the alarms have already been filtered for the selected output program. See section,“Grooming
Window,”on page 180 for more information.

682 ARRIS Enterprises, Inc.

 Managing Alarms

The Analysis window in the GUI displays alarm severities in the stream analysis panel. The alarm
severity is propagated to the multiplex level in the stream analysis panel. See section,“Stream
Analysis,”on page 656 for more information.

Managing Alarms
This section explains now to manage alarms in the Alarms window of the CherryPicker Element
Manager.

When Alarm Sources are Deleted or Reconfigured

An alarm belongs to its source object. When the source object is deleted, the alarm is cleared and a
trap is generated if is configured to do so. In some cases, the alarm is deleted after being cleared. In
other cases, the alarm is not deleted when its source is deleted, because the history of alarms for
deleted objects is often of interest. For example, an elementary stream may disappear and
reappear, or an ad server connection may be closed and then reopened, in which case the alarms
that occurred before the object was deleted are useful for diagnosing why the source object is
intermittently present.
The following list describes how the CAP-1000 handles cases when alarm sources are deleted or
reconfigured:
• When an output program is deleted, all alarms associated with the program and its component
streams are cleared and deleted.
• When an input program disappears from an input mux, all alarms associated with the program
and its component streams are cleared and deleted.
• When an input mux or output mux is deleted, all alarms associated with it are cleared and
deleted.
• When an output mux is torn down and rebuilt by means of loading a config file, all alarms
associated with the mux and its child nodes are cleared and deleted.
• When the Controller unloads the database as part of a CPR state transition, all alarms below
the line level are cleared and deleted. As a result, when a CPR failover occurs, all alarms at the
mux level and its child nodes are cleared and deleted on the primary CAP-1000. Similarly,
when a CPR failback occurs, all alarms at the mux level and its child nodes are cleared and
deleted on the backup CAP-1000. See section,“Alarms and Redundancy,”on page 673 for
more information.
• When an elementary stream is deleted, all alarms associated with it are cleared but not deleted.
• When the IP address, port, or source IP of a GigE input mux is changed, then all alarms for the
input mux and its child nodes are cleared and deleted.
• When a line is disabled for MPEG, all alarms associated the child nodes of the line are cleared
and deleted.

CAP-1000 Software Guide v4.0 683

Chapter 35 Managing Alarms and Logs Managing Alarms

Viewing Raised Alarms

To view raised alarms:

1 From the CherryPicker Element Manager, click Alarms > Alarms.

Alarms

2 In the Show panel, select the Raised Only option.

3 Select any other filters you want.
See Table 35-2 on page 676 for a description of alarm parameters.
4 To view alarm details, do the following:
a Select the alarm you want.
b Click Show Detail.
Details appear in a bottom panel.

684 ARRIS Enterprises, Inc.

 Managing Alarms

Alarm Details

Details appear in a bottom panel. See Table 35-4 on page 678 for a description of alarm details.

Clearing Alarms
When an alarm occurs it is in the raised state. When an alarm is cleared, it is in the cleared state. If
an alarm is configured to send an SNMP Trap, then a trap is sent when it is raised, and another trap
is sent when it is cleared. Events can also trigger traps.
Most alarms are automatically cleared by the device when the device determines that the condition
that triggered the alarm no longer exists or when the source object of an alarm is deleted or
reconfigured. Other alarms remain raised until they are cleared manually by the user. All alarms
can be cleared manually by the user, even those that are normally cleared by the device.

Clearing Alarms Manually by ID

You can select one or more raised alarms and clear them manually. In this case, the alarms are
cleared by their IDs (i.e., by the identity if each selected alarm instance).

Clearing Alarms Manually by Source

You can also select one or more alarm source nodes and clear all raised alarms for the selected
source nodes and their children. For example, you can select a given output mux and clear all
raised alarms for the output mux as well as all output programs and output streams under that
output mux. If you select a device node, then all raised alarms are cleared for the entire device.
The following procedure explains how to control the maximum number and age of cleared alarms
and events.

CAP-1000 Software Guide v4.0 685

Chapter 35 Managing Alarms and Logs Managing Alarms

To clear alarms:
1 From the CherryPicker Element Manager, click Alarms > Alarms.
2 Do one of the following:
• In the Alarm panel, select the alarm to delete and click Clear.
• In the Tree, right-click the parent or child node you want and select Clear Alarms and Child
Node Alarms.

Deleting Alarms
Only events and cleared alarms can be deleted. Deleting alarms removes them from active storage
and adds them to archive storage. Alarms in the archive are not visible. If any of the given alarms
are raised when the request is received, they are cleared before being deleted.

Deleting Alarms Manually by ID

You can select one or more cleared alarms and delete them manually. In this case, the alarms are
identified by their IDs.

Deleting Alarms Manually by Source

You can also select one or more source nodes and delete all cleared alarms for the selected source
nodes and their children. For example, you can select a given output mux and delete all cleared
alarms for the output mux as well as for all output programs and output streams under that output
mux. If you select a device node, then all cleared alarms are deleted for the entire device.

To delete alarms:
1 From the CherryPicker Element Manager, click Alarms > Alarms.
2 Do one of the following:
• In the Alarm panel, select the alarm to delete and click Delete.
• In the Tree, right-click the parent or child node you want and select Delete Alarms and Child
Node Alarms.

Configuring Audible Alarms

The CAP-1000 can play audible alarms by using Windows .wav files on a Windows system that
hosts the CherryPicker Element Manager (GUI). To use this function, associate a .wav file to each
of the three alarm severities (critical, major, or minor). Only 16-bit .wav files can be assigned to an
audible alarm.
When an audio file is assigned to the highest alarm severity and an alarm is raised, the CAP-1000
plays the .wav file associated with it. When all alarms for that alarm severity level are cleared, the
next highest severity alarm with an audio file assigned to it will play and so on.

686 ARRIS Enterprises, Inc.

 Managing Alarms

The alarm count icon indicates if the audible alarm feature is on or off. By default, .wav files are
not associated with alarms. The settings of the .wav files are persistent in the GUI when logging
off and on.
In Single GUI Centralized Management (SGCM) groups, the same audible alarm setting applies to
all the CAP-1000 devices in a the group. See section,“Working with Managed Groups of CAP-
1000 or AGB240 Devices,”on page 695 for more information.

To configure audible alarms:

1 From the CherryPicker Element Manager, right-click the lower left corner of the window.
The Status bar shows icons that represent the total number of alarms with Critical, Major, and
Minor severities.
2 Do one of the following:
• To assign an audio file, right-click an alarm counter and select Set Audio File. Navigate to the
file and click Test. If this is the file you want, click Open to assign it.
• To cancel an assigned audio file, right-click an alarm counter and select Cancel Audio File.
• To cancel all assigned audio files, right-click any alarm counter and select Cancel All Audio
Files.

Audible Alarms

CAP-1000 Software Guide v4.0 687

Chapter 35 Managing Alarms and Logs Managing Alarms

Using the Time Filter

Use the Time Filter function to filter alarms by a time period when a failure occurred.

To use the time filter:

1 From the CherryPicker Element Manager, click Alarms > Alarms.
2 Click Time Filter.

Define Time Filter

3 Do one or more of the following:

• Select the No Start Time and No End Time options return all alarms.
• Clear the No Start Time option to display a calendar for selecting the Start Date, Time Zone,
Start Time (hh:mm:ss:AM/PM), and month.
• Clear the No End Time option to display a calendar for selecting the End Date, Time Zone,
End Time (hh:mm:ss:AM/PM), and month.

688 ARRIS Enterprises, Inc.

 Configuring Alarm Settings

Define Time Filter

4 Click Apply.

Searching for Alarms by Description

Use the Search Description field to filter alarms and events by a given search term in the
Description field. Only those descriptions that match the filter are displayed.

To search:
1 From the CherryPicker Element Manager, click Alarms > Alarms.
2 In the Search Description field, enter the search terms you want.
3 The GUI immediately highlights search terms that match your description, if any.

Configuring Alarm Settings

This section explains how to configure alarm settings for clearing alarms, resetting alarms, setting
severity levels, and changing debounce durations.

Scheduling How Alarms are Cleared

When an alarm occurs, it is in the raised state. When an alarm is cleared, it is in the cleared state. If
an alarm is configured to send an SNMP trap, then a trap is sent when it is raised, and another trap
is sent when it is cleared.
Some alarms are automatically cleared by the device when the device determines that the
condition that triggered the alarm no longer exists. Other alarms remain raised until they are
manually cleared by a user. All alarms can be manually cleared by a user, even those that are
normally cleared by the device.

CAP-1000 Software Guide v4.0 689

Chapter 35 Managing Alarms and Logs Configuring Alarm Settings

All raised alarms are preserved. In other words, a raised alarm is never automatically deleted by
the device. However, a raised alarm can be deleted by a user. When a user deletes a raised alarm,
the alarm is first cleared and then deleted.
To preserve all raised alarms, the number of raised alarms must be bounded. This upper bound is
approximately 2000.

NOTE This number of raised alarms is not expected to ever be observed in a deployed system.

To schedule:
1 From the CherryPicker Element Manager, click Alarms > Settings.
2 In the Archive cleared alarms and events after field, enter the number of days to keep alarms
before they are cleared.
Cleared alarms and events are deleted from active storage and archived when their age exceeds
this many days.The default is 3 days.
3 In the Max cleared alarms and events, enter the number you want.
Cleared alarms and events are deleted from active storage and archived, oldest ones first, when the
number of cleared alarms and events exceeds this maximum. The default is 2000 alarms and
events.
4 Click Apply.

Changing Alarm Severity Levels

The CAP-1000 allows you to change the severity levels associated with specific errors. For
example, if you have a noisy input feed, you could change the severity to Warning.

To change severity levels:

1 From the CherryPicker Element Manager, click Alarms > Settings.
2 Under Severity, double click the alarm you want to change.

690 ARRIS Enterprises, Inc.

 Configuring Alarm Settings

Settings

3 Select the Severity level from the menu.

4 Click Apply.

Changing Alarm Debouncing Durations

Alarm debouncing refers to the process of limiting the number of recurring alarms in a sequence of
the same alarms. This feature prevents the CAP-1000 and all other reporting agents (SNMP Agent
and GUI logs) from being flooded with too many notifications of repeat alarms.
The default value for debouncing duration for most debounceable alarms is 500 milliseconds (ms)
with a range of 500 to 10,000 in increments of 500 ms. The duration refers to the length of time the
software uses to verify that the alarm condition has not reoccurred. The debounce duration also
specifies the maximum repetition rate at which the alarm messages are sent when error conditions
persist.

To change the alarm debounce duration:

1 From the CherryPicker Element Manager, click Alarms > Settings.
2 Under Debounce, double-click the duration you want to change.
3 Select the duration you want from the menu.

CAP-1000 Software Guide v4.0 691

Chapter 35 Managing Alarms and Logs Configuring Alarm Settings

Settings

When you change the default value of de-bouncing duration, a warning message appears.
4 Click OK.

NOTE When the new debouncing duration is applied, the alarm clearing report is delayed by the debouncing
duration. If the CAP-1000 has been configured for PRED, this delay impacts program redundancy. The
alarm interval specified in the Redundancy tab of the Program Interval window in the CAP-1000 should
always be greater than the debouncing duration.

5 Click Apply.

Resetting Alarms to Default Values

Resetting alarms restores the severity and debouncing durations to their default values.

To reset:
1 From the CherryPicker Element Manager, click Alarms > Settings.
2 Click Default.
3 Click OK.

Synchronizing Alarm Settings Across Multiple CAP-1000 Systems

If you need to synchronize the persisted Controller alarm settings across multiple CAP-1000 units
in a headend, copy the alarm-settings.xml file from a master location, such as a master CAP-1000
or a server of some kind, to the Data Flash directory of all the CAP-1000s on which the settings are
needed. FTP is one tool that can be used to copy the file. Restarting the Controller on each of the
CAP-1000s causes the Controller to read the settings file and put the settings into service.

692 ARRIS Enterprises, Inc.

 Collecting Logs

Collecting Logs
The CAP-1000 maintains logs of events and alarms in the /usr/cp/Log directory on the Data Flash.
Alarms and events are stored in the Alarms.log. Deleted (archived) alarms and events are stored in
the AlarmArchiven.log.
For example, AlarmArchive1.log. When contacting ARRIS for support, you may need to provide
these files to the Technical Assistance Center (TAC). Information about how to gather these files
is provided in this chapter.
The log file collection time is limited to maximum of 6 days (518400 seconds).

WARNING Performing log collection can impact services.

To collect logs:
1 Log on to the CherryPicker Element Manager.
2 Click the Logs hyperlink.

CherryPicker Application Platform Login

The Log Collector window opens.

Log Collector

CAP-1000 Software Guide v4.0 693

Chapter 35 Managing Alarms and Logs Collecting Logs

Along the top of the log collector window, the IP address of the CAP-1000, filename of the
resulting zip file, and duration to capture the debug ports (6008, 6010) are specified.
3 Set the parameters you want.
4 Click Start Collection in the bottom right corner.
5 After collecting the logs you want, click Stop. Otherwise, everything finishes as requested, with
the 6008 and 6010 logging taking the longest time. The default is 600 seconds.

Log Collector

The logs are saved to a zip file specified in the pathname.

6 Click Close.
7 Retrieve the zip file from the specified location.
8 Follow the instructions by the Technical Assistance Center for submitting the zip file to them.

694 ARRIS Enterprises, Inc.

 Working with Managed Groups of CAP-1000 or AGB240 Devices

Working with Managed Groups of CAP-1000 or AGB240 Devices

If your are managing multiple CAP-1000 or AGB240 devices with the Single GUI Centralized
Management (SGCM) functions, alarms for all devices are displayed in the Alarms window.

Filter Events Based on Managed Groups

You can filter events based on the devices in a managed group. You must be logged in to a
managed group to perform this procedure.

To filter events:
1 From the CherryPicker Element Manager, click Alarms > Alarms.
2 From the Device menu, select the managed group you want.

Device

The IP addresses for all devices in the managed group are listed in the Device column. Errors for
the selected device appear in regular text. Errors for other devices in the group appear in italicized
text.

CAP-1000 Software Guide v4.0 695

Chapter 35 Managing Alarms and Logs Working with Managed Groups of CAP-1000 or AGB240 Devices

Device
3 Click Device Filter.

Device Filter

a Under Include, select the devices you want.

b Click OK.

Applying Settings to Managed Groups

You can apply alarm settings to one member of a managed group or all members of a managed
group. You must be logged in to a managed group to perform this procedure.

To apply settings:
1 From the CherryPicker Element Manager, click Alarms > Settings.
2 Configure the settings you want.
See section,“Settings Window,”on page 681 for more information.

696 ARRIS Enterprises, Inc.

 Working with Managed Groups of CAP-1000 or AGB240 Devices

3 Do one of the following:

• If you are logged into a group, click Apply to Group.

Apply To Group

This button only appears if you are logged into a group. The Apply button is grayed out.
• If you are logged into a single device, click Apply.
Settings are applied as configured.

CAP-1000 Software Guide v4.0 697

Chapter 35 Managing Alarms and Logs Working with Managed Groups of CAP-1000 or AGB240 Devices

698 ARRIS Enterprises, Inc.

©ARRIS Enterprises, Inc. 2014. All rights reserved. No part of this publication may be reproduced in any
form or by any means or used to make any derivative work (such as translation, transformation, or
adaptation) without written permission from ARRIS Enterprises, Inc. ("ARRIS"). ARRIS reserves the right
to revise this publication and to make changes in content from time to time without obligation on the
part of ARRIS to provide notification of such revision or change.

365-095-19245 x.2 2/2014