Broadcaster Cluster Configuration Parameters Table (for Manual and Managed Clusters)

configuration (for manual and managed clusters) parameter description info name specify the name of the broadcaster cluster in zen master tags select one or more of the predefined tags from the drop down list tags are used for access control by selecting an tag, you are relating this broadcaster 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 events configuration profile select from the dropdown list the profile that you would like to apply to this cluster by default, the default profile is applied note events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger dns prefix specify a unique domain name for sending sources to this cluster ip whitelist select this checkbox if you would like to control access to this cluster by limiting access to push inputs and pull outputs to specific ip address (for an aws cluster this will enable you to control the aws security groups) note if you select ip whitelist , then you must use zen authorization mode for this cluster note if you selected ip whitelist then after configuring the broadcaster cluster you must input the ips that will have access to this cluster, see adding ips to the whitelist docid\ ricodzjuvwvliz6i2qtgx dtls select this checkbox if you would like to encrypt the stream dynamically using dtls (this feature is supported for v12 2+ broadcasters) ignore dtls certificate when not supported (for dtls) 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 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 log scte 35 select this checkbox if you would like to log scte 35 markers for streams in this cluster note to log scte 35 markers, scte 35 needs to be enabled both on the ingest cluster and in the source configuration note scte 35 logging is only available for v13 1 40262+ broadcasters rtmp servers select this checkbox if you need to receive rtmp push inputs rtmp server port specify the port in the broadcaster that will be used to receive the rtmp push inputs configuration (for manual) management type select manual after creating a manual broadcaster cluster, you must configure each broadcaster instance for use in the cluster to do this, see adding a broadcaster to a manual cluster docid\ xyscyso498ly77zjqr 51 authorization mode 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 note all authorization modes other than manual will override the authorization configured on your broadcasters therefore, if you have streams on your broadcasters that are not configured on zen master, then any mode other than manual or free for all may interrupt those streams allow access to inputs not configured in zen master (for zen master authorization) 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 termination protection select the deletion protection checkbox if you want to prevent deletion of the broadcaster cluster managed clusters configuration for managed clusters parameter description management type select one of the aws, azure or gcp accounts configured in zen master from the list shown under aws, azure or gcp in the drop down menu to create a new cloud service account see linking an aws account docid\ erygxkcufmmz8bakidjz4 , linking an azure account docid\ jsst1kxhrrrfcdyc1lenl or linking a google gcp account docid\ jbuzi2tjvsps3o vzvxxh aws clusters parameter description region select from the drop down list the aws region key pair select from the drop down list one of the available key pairs to access the cluster if no key pair is displayed, then go to your amazon account to setup your key pair vpc select from the drop down list one of the available vpc (virtual private cloud) networks to which the cluster will be connected subnets select from the drop down list one or more of the subnets that are available in this vpc security groups select from the drop down list one or more of the security groups associated with this vpc if no security group is displayed then go to your amazon account to configure your security groups (for guidance in setting up your security groups see amazon security groups) or use the zen ip whitelist to manage your aws security (see the following step) manage security groups via zen master ip whitelist (for ip whitelist) select this checkbox to use the ip whitelist to manage your aws security instance type select from the drop down list one of the available aws instance types that will be used in this cluster root device size \[gib] specify the capacity of the hard drive (in gib) azure clusters parameter description region select from the drop down list the location of the account to be used for this cluster virtual network select from the drop down list a vn in your azure account note you need to have a virtual network in your azure account in order to be able to create a broadcaster cluster in zen master if you don’t have a vn in your account, you can create one via the azure portal subnet select from the drop down list a subnet that is available in the specified vn network security group select from the drop down list a network security group for this cluster gcp managed clusters parameter description region select from the drop down list the region of the gcp account zones select from the drop down list one or more zones in the specified region network select from the drop down list one or more of the subnets that are available in the specified region machine type select from the drop down list the type of machine to be used for the cluster note both n1 and n2 machine types are supported gpu type select from the drop down list the type of gpu to be used for the cluster root device size specify the size of the root device in gib all managed clusters parameter description activation key enter the activation key for your zixi broadcaster license api user enter the username for accessing the zixi broadcaster via api api password enter the password for accessing the zixi broadcaster via api broadcaster version select from the drop down list the zixi broadcaster version that you want to install authorization mode 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 external server – the request for content is relayed to an authorization server in the authorization server field, enter the url of the external server 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 note all authorization modes other than manual will override the authorization configured on your broadcasters therefore, if you have streams on your broadcasters that are not configured on zen master, then any mode other than manual or free for all may interrupt those streams allow access to inputs not configured in zen master (for zen master authorization) 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 termination protection select the deletion protection checkbox if you want to prevent deletion of the broadcaster cluster advanced parameters parameter description 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 elastic ip allocation ids (for managed) enter comma separated elastic ip allocation ids bandwidth limits input/output specify the bandwidth limits in mbps default hls/ dash segment configuration (for managed) specify the count and duration parameters for hls and dash segments on this broadcaster cluster transcode thresholds these 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 \[%] specify the percentage of cpu being used memory threshold \[%] specify the percentage of memory being used gpu threshold \[%] specify the percentage of gpu being used gpu memory threshold \[%] specify the percentage of gpu memory being used gpu decoder threshold \[%] specify the percentage of gpu decoder pipeline being used gpu encoder threshold \[%] specify the percentage of gpu encoder pipeline being used process priority (for managed clusters) this setting determines the process priority of your broadcasters enable real time broadcasters process priority this setting is deselected by default you can increase the broadcaster's process priority by selecting it this may be beneficial for sending streams to highly sensitive irds however, this should not be done without consulting with your customer success agent billing codes if you would like to track usage for this broadcaster, enter your billing code details, see (supported for broadcasters v14 8+) install agentz automatically select this checkbox to install agentz automatically 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