Adding a Broadcaster Cluster – Manual

to add a manual broadcaster cluster in the main navigation, select broadcasters click + add the create new broadcaster cluster screen is displayed create new cluster in the info section, in the name field, type a logical name for the zixi broadcaster cluster resource in the tags field, select one or more of the predefined tags from the drop down list tags are used for access control by selecting a tag, you are relating this cluster to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this cluster by default, the default profile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger in the dns prefix field, enter a unique domain name for sending the streams to/from this cluster dtls is session based encryption over the connection, establish on the network link when the connection is made, using the broadcasters web certificate under dtls , select one of the following clear only select this option if you do not wish to use dtls, only clear ports (2077+2088) dual mode select this option to support both dtls encrypted and non dtls/clear ports (2077/2088 + 7077+7088) dtls only select this option to support dtls encrypted zixi connections only this means that zen master won't create non dtls zixi connections on the cluster, i e , no clear traffic on port 2077+2088 (7077+7088 only) if you selected the dtls mode or dtls dual mode options , then the ignore dtls certificate when not supported checkbox appears select this checkbox if you would like to enable resources using older versions of zixi software (\<v12 2) that don't support verification of the zen dtls certificate to connect to this cluster select the log scte 35 checkbox if you would like to log scte 35 markers for streams in this cluster to log scte 35 markers, scte 35 needs to be enabled both on the cluster and in the source configuration scte 35 logging is only available for v13 1 40262+ broadcaste select the rtmp server checkbox if you would like to receive rtmp push inputs if you selected rtmp server , in he rtmp server port field, enter the number of the rtmp server port if you want to configure an alternative path for disaster recovery, in the alternative cluster (disaster recovery) field, select the cluster that will be used as the alternative path for more details, see disaster recovery (alternative path) docid\ poo4zs1 zjra1sndylqe0 in the configuration section, in the management type field, for manual management, verify that manual is selected after creating a broadcaster cluster with manual management, you must add broadcaster instances for use in the cluster to do this, see adding a broadcaster to a manual cluster docid\ xyscyso498ly77zjqr 51 to create a broadcaster cluster with zen master managed broadcasters, see adding a broadcaster cluster managed docid 6slx4td zkr2xfho8qz6 in the authorization mode field, select one of the following options zen master – zen master automatically verifies the authorization for each zen entity (e g sources, channels and targets) that accesses the broadcaster cluster if you would like to allow access to inputs/outputs that are not configured in zen master, then in the allow access… section, select the push inputs and/or pull outputs global password – broadcasters are automatically configured to authorize all connections using a single global password the global password will be used in the source password field when you configure a source in the password field, enter the password or click random to generate a random password free for all – broadcasters will be automatically configured to allow all inputs/outputs to connect select inputs and/or outputs to automatically allow them to connect manual – zen will not authorize connections you will need to authorize each connection independently under allow access to inputs not configured in zen master , select the push inputs checkbox if you would like to automatically allow access to push inputs select the pull outputs checkbox if you would like to automatically allow access to pull outputs select the deletion protectio n checkbox if you want to prevent deletion of the broadcaster cluster if you would like to adjust the advanced settings, click advanced the advanced settings window is displayed advanced settings adjust the following advanced settings as desired load balance pull targets – select one of the following load balancing methods for pull outputs minimize the number of broadcasters (default)– transfers excess load to other broadcasters only when the allotted capacity on the host broadcaster is filled uniform distribution – distributes the load equally between all available broadcasters under all circumstances http streaming port – you can change the http streaming port from the default ( 7777 ) to a custom port the custom port should match the configuration on the zixi broadcaster bandwidth limits – set the bandwidth limits the transcode thresholds are used by zen master to determine whether an additional transcoded channel can be added to the broadcaster adjust the following thresholds as desired cpu threshold – percentage of cpu being used memory threshold – percentage of memory being used gpu threshold – percentage of gpu being used adding a broadcaster cluster – manual /#notes gpu memory threshold – percentage of gpu memory being used gpu decoder threshold – percentage of gpu decoder pipeline being used gpu encoder threshold – percentage of gpu encoder pipeline being used if you would like to track usage for this broadcaster, enter your billing code details, see billing codes docid\ lalxj n928tegcpdpbirj (supported for broadcasters v14 8+) external authorization if you want, in addition to the to the standard internal authorization process, you can add an external authorization service in this case, the requests for connections will be redirected to the external service for authorization for example, an external pay per view application can confirm that a requesting end device belongs to an account that has paid for a live event another example could be some external security management application that is managing firewalls accepting requests from dynamic ips in a consumer network to enable, set the following parameters server endpoint the url of the external authorization server endpoint authorization header type (optional) the type of authorization header schema (e g , basic) authorization header credentials (optional) the authorization header credentials code if you want to install agentz automatically, select the install agentz automatically checkbox agent z is a sidecar tool that sits on a zixi broadcaster, it acquires the system health data and other statistics locally and pushes it to zen master by enabling this option, zen master will automatically install agentz on any existing and future broadcasters connected to the cluster the feature is off by default due to agentz installation requiring a restart, zen master will not auto install agentz on a broadcaster that already contains any inputs to avoid disturbing active streams it is also possible to install agentz manually on a broadcaster unlike the zen master install, the manual install does not force a broadcaster restart the manual agentz installer can be downloaded from the zixi customer portal and instructions are provided in the agentz installation guide click save the broadcaster cluster will only be functional once you add one or more broadcaster instances to the cluster first you need to add the broadcaster (see adding a broadcaster to a manual cluster docid\ xyscyso498ly77zjqr 51 ), and then you need to connect the broadcasters to zen master (see connecting the zixi broadcaster (zixi broadcaster ui – for manual) docid\ oexqmqgq yzfbii oqjpo ) notes the gpu thresholds are only relevant for transcoding workflows using intel quick sync or nvidia gpus