Configuring SNMP (Deprecated)

snmp for monitoring and control of the zixi broadcaster is no longer supported monitoring and control of zixi broadcasters should be implemented using the zen master api and kafka data pipelines available via zen master zixi broadcaster enables monitoring and control via snmp (on linux only) the monitoring system can receive snmp trap messages from zixi broadcaster as well as access monitored objects with read only and read write access privileges (objects and their access permissions are defined in the mib) zixi broadcaster supports snmpv1, snmpv2, and snmpv3 before using snmp you need to ensure that snmp is enabled in your zixi broadcaster license, run a script, as described below, and configure the snmp settings in the settings >snmp screen the snmp feature is not enabled by default if you do not see this screen, please contact zixi support activating snmp to activate snmp run the script file /install snmp sh , located in the broadcaster folder, where zixi broadcaster was installed the events on the log screen are deleted note running the script may cause zixi broadcaster to restart configuring snmp settings to configure snmp in zixi broadcaster ui, go to settings > snmp in the service field, click the button to activate the service do one of the following for snmpv1 or snmpv2, fill in the read only and/or read write community name in the read only community name, and read write community name fields for snmpv3, under the snmpv3 users section, click the + button the following screen appears in the user name field, enter the snmp user name in the write access field, select the checkbox to allow read write access rights if the checkbox is not selected, the user will have read only access rights in the password field, enter the snmp user's passwo under the trap receivers section, specify snmp trap receivers that will listen to the snmp traps that will be sent by zixi broadcaster, by clicking the + button to add a trap receiver the following screen appears in the community field, specify the community name for access in the host field, specify the ip address to which the trap messages will be transmitted in the port field, specify the port number to which the trap messages will be sent transmitted click apply viewing mib information you can view the "root mib" (which defines the zixi broadcaster tree root definitions) and the "broadcaster mib" (which describes the zixi broadcaster mib tree definition, including all its objects) to view mib information in zixi broadcaster ui, go to settings > snmp at the upper right hand corner click the root mib and/or broadcaster mib links snmp alerts/notifications the snmp traps are sent when an alert is raised and when alert is cleared on following occasions input stream alerts ( zbtinputstreamalertraised = 1 3 6 1 4 1 38369 1 1 1 0 58; zbtinputstreamalertcleared = 1 3 6 1 4 1 38369 1 1 1 0 60) important parameters $ zbsprogramid ( id of the broadcaster that sends the trap, 1 3 6 1 4 1 38369 1 1 1 1 2) $ zbtstreamid ( id of the stream, 1 3 6 1 4 1 38369 1 1 1 0 2) $ zbtstreamalerttype ( alert type, 1 3 6 1 4 1 38369 1 1 1 0 10) tr101 analyser alerts ( zbttr101alertraised = 1 3 6 1 4 1 38369 1 1 1 0 90; zbttr101alertcleared = 1 3 6 1 4 1 38369 1 1 1 0 91) important parameters $ zbsprogramid ( id of the broadcaster that sends the trap, 1 3 6 1 4 1 38369 1 1 1 1 2) $ zbtstreamid ( id of the stream, 1 3 6 1 4 1 38369 1 1 1 0 2) $ zbttr101alerterrorcode ( tr101 alert code, 1 3 6 1 4 1 38369 1 1 1 0 30) output stream alerts ( zbtoutputstreamalertraised = 1 3 6 1 4 1 38369 1 1 1 0 59; zbtoutputstreamalertcleared = 1 3 6 1 4 1 38369 1 1 1 0 61) $ zbsprogramid ( id of the broadcaster that sends the trap, 1 3 6 1 4 1 38369 1 1 1 1 2) $ zbtstreamid ( id of the input stream where output is assigned, 1 3 6 1 4 1 38369 1 1 1 0 2) $ zbtoutputid ( id of the output, 1 3 6 1 4 1 38369 1 1 1 0 3) $ zbtstreamalerttype ( alert type, 1 3 6 1 4 1 38369 1 1 1 0 10) performance alerts ( zbtperformancealertraised = 1 3 6 1 4 1 38369 1 1 1 0 80; zbtperformancealertcleared = 1 3 6 1 4 1 38369 1 1 1 0 81) important parameters $ zbsprogramid ( id of the broadcaster that sends the trap, 1 3 6 1 4 1 38369 1 1 1 1 2) $ zbtperformancealerttype (alert type, 1 3 6 1 4 1 38369 1 1 1 0 20) in addition, traps are sent on following events input stream created ( zbtinputstreamcreated = 1 3 6 1 4 1 38369 1 1 1 0 54) output stream created ( zbtoutputstreamcreated = 1 3 6 1 4 1 38369 1 1 1 0 55) input stream up ( zbtinputstreamup = 1 3 6 1 4 1 38369 1 1 1 0 50) input stream down ( zbtinputstreamdown = 1 3 6 1 4 1 38369 1 1 1 0 50) output stream up ( zbtoutputstreamup = 1 3 6 1 4 1 38369 1 1 1 0 51) output stream down ( zbtoutputstreamdown = 1 3 6 1 4 1 38369 1 1 1 0 53) input stream deleted ( zbtinputstreamdeleted = 1 3 6 1 4 1 38369 1 1 1 0 56) output stream deleted ( zbtoutputstreamdeleted = 1 3 6 1 4 1 38369 1 1 1 0 57) successful broadcaster process start ( zbtprogramstartsuccess = 1 3 6 1 4 1 38369 1 1 1 0 200) failure to start broadcaster process ( zbtprogramstartfailed = 1 3 6 1 4 1 38369 1 1 1 0 201) important parameters $ zbsprogramid ( id of the broadcaster that sends the trap, 1 3 6 1 4 1 38369 1 1 1 1 2) $ zbtstreamid ( id of the input stream, 1 3 6 1 4 1 38369 1 1 1 0 2) applicable for inputs' and outputs' events $ zbtoutputid ( id of the output, 1 3 6 1 4 1 38369 1 1 1 0 3), applicable only for outputs' events there are no snmp alerts on license status or port connections