After the Zixi Receiver resource is created, it is added to the list of existing Receivers. The Zixi Receivers screen displays all of the existing Zixi Receivers, their connection status and their CPU consumption levels.
When a Receiver is selected, the list pane is minimized and detailed info about the selected Receiver is shown on the right side of the screen. The info can be shown in Tab view or Accordion view, see Info Pages.
When a Receiver is selected, the following tabs are shown at the bottom of the screen:
Details – configuration details of the Receiver.
History – a graphical display the Receiver's CPU consumption over time.
Events - all the related events/alarms that have been generated by the system, such as connections, errors, warnings and disconnections.
Configuration – configuration procedures for connecting the Receiver to ZEN Master, including specific settings for this particular Receiver.
Notes – free-form text can be added with pertinent information about this Receiver.
The top of the Info pane includes buttons for taking the following actions on the selected Receiver:
Acknowledge/Clear Acknowledgment (for sources in disconnected status) – mark/clear the status of this source as acknowledged.
Mute/Clear Mute – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting mute until.
Edit – enables you to edit the Zixi Receiver configuration.
Disable/Enable – Disabling a Zixi Receiver stops all active outputs for that Receiver without deleting the configuration of the Zixi Receiver.
Delete – deletes the Zixi Receiver configuration.
The main display shows following data:
Parameter
Description
Status
The connection status of the Zixi Receiver. Possible values:
Green – OK
Red – error state
Pink (shown together with a checkmark) – acknowledged error state
Gray – pending/disabled (waiting for initial connection)
The icon next to a Feeder indicates that the Receiver is muted, disabling notifications for error/recovery events.
Name
The name of the Zixi Receiver as configured in ZEN Master.
IP
The remote Zixi Receiver IP address as seen by ZEN Master.
CPU
The CPU utilization on the Zixi Receiver source machine.
Version
The Zixi Receiver software version.
Actions
Open
A link to the Zixi Receiver UI.
When one of the Receivers in the list is selected, the details of the Receiver, divided into tabs, appear at the bottom of the screen.
Parameter
Description
Details Tab
Name
The name of the Zixi Receiver as configured in ZEN Master.
Access Tags
The Access Tag/s that is associated with this Zixi Receiver. You can edit the access tag/s as follows: click the icon. Then, delete the current tag by clicking the "X" next to the tag and/or add a new access tag/s by selecting one or more tags from the drop-down list.
API User
The user name used to access the Zixi API in order to communicate between ZEN Master and the Zixi Feeder.
API Password
The Zixi Receiver API password. Click Show to display the password.
Tunnel Port
The port on the ZEN Master server assigned for communication with the Zixi Receiver.
SSH Key
The name of thee SSH key file. Click on the link to download the SSH key onto your local machine.
Available Outputs
Shows a list of all outputs available in the Receiver, including information about their Status, Type, and target location.
History
A graphical representation of the CPU utilization of the selected Receiver, displayed over time.
Events
A list of the events that were generated in ZEN Master in relation to the selected Zixi Receiver. To learn about viewing event logs in ZEN Master, see Events. Click Quick Report to generate a report of events related to this receiver and download the .xls file.
Configuration
Shows an explanation of how to connect the selected Receiver to ZEN Master. This tab includes your personal connection configuration settings which are used to make the connection. See section Connecting the Zixi Receiver (Zixi Receiver UI).
Notes
Free-form text with information relevant to this broadcaster cluster.