<!DOCTYPE html
SYSTEM "about:legacy-compat">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2023"><meta name="DC.rights.owner" content="(C) Copyright 2023"><meta name="DC.type" content="concept"><meta name="description" content="An event is something that happens in the system and that needs to be reported. Event notifications are formatted text messages issued by the DGW software to signal something of interest to the unit administrator."><meta name="prodname" content="All Mediatrix Products"><meta name="version" content="DGW 49.12.28842941"><meta name="platform" content="All"><meta name="DC.date.modified" content="2023-0308-2809"><meta name="DC.date.issued" content="2023-0308-2809"><meta name="DC.date.available" content="2023-0308-2809"><meta name="ChapterNumbering" content="no"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="concept_hzf_t1g_xz"><link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/62825785/commonltr.css"><link rel="stylesheet" type="text/css" href="https://documentation.media5corp.com/download/attachments/62825785/custom.css"><title>Generating Logs</title></head><body><header role="banner"><div class="topicmeta title">Generating Logs</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">All Mediatrix Products</div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/62825785/Generating%20Logs.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#concept_hzf_t1g_xz">Event Notifications</a><ul><li><a href="#task_f4n_wq3_11b">Logging Event Notifications</a></li><li><a href="#unique_4887489261937006916">Logging Specific Event Notifications</a></li></ul></li><li><a href="#topic_title_Destinations_for_Event_Notifications_d1e18">Destinations for Event Notifications</a><ul><li><a href="#concept_brq_dpg_1r">Send via Syslog</a></li><li><a href="#concept_dqy_pkp_f1b">Send via SIP</a></li><li><a href="#concept_wsr_1bs_d1b">Log Locally</a></li><li><a href="#concept_fsb_wmp_f1b">Log to File</a></li><li><a href="#concept_fgn_wqy_vjb">Send via SNMP</a></li></ul></li><li><a href="#concept_adk_ztr_d1b">Diagnostic Traces </a><ul><li><a href="#task_a55_cck_wz">Logging Diagnostic Traces</a></li></ul></li><li><a href="#topic_title_Basic_tasks_d1e26">Basic tasks</a><ul><li><a href="#task_url_2zf_xz">Clearing the Local Logs</a></li><li><a href="#unique_2120003795836893088">Updating the Local Logs</a></li><li><a href="#task_cnz_bfh_11b">Disabling Event Notification Reporting for a Service</a></li><li><a href="#unique_1191024339833039885">Modifying the Severity Level Triggering the Reporting of a Notification</a></li></ul></li><li><a href="#concept_zqb_h14_1r">Command Line Interface (CLI)</a><ul><li><a href="#reference_cyv_gsg_xz">Advanced Log Parameters</a></li></ul></li><li><a href="#reference_j4g_nbv_gfb">Online Help</a></li><li><a href="#concept_v4k_q3h_1r">DGW Documentation</a></li><li><a href="#concept_fqm_rv4_k4">Copyright Notice</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1"><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="nested0" aria-labelledby="ariaid-title1" id="concept_hzf_t1g_xz">
<h1 class="title topictitle1" id="ariaid-title1">Event Notifications</h1>
<div class="body conbody"><p class="shortdesc">An event is something that happens in the system and that needs to be reported. Event
notifications are formatted text messages issued by the DGW software to signal something of
interest to the unit administrator. </p>
<div class="p">Event Notifications are used to generate alarms in the customer's system and to monitor the
system. It is possible to control: <ul class="ul" id="concept_hzf_t1g_xz__ul_kkh_pks_d1b">
<li class="li">for which service event notifications will be reported;</li>
<li class="li">which event notifications will be reported based on the severity level of the
event;</li>
<li class="li">if a specific event notification should be reported or not;</li>
<li class="li">where the event notifications will be logged.</li>
</ul>For example, it is possible to log all event notifications raised for the Call Router
(Crout) service, or to log only one specific event notification for the Certification (Cert)
service. <div class="note important note_important"><span class="note__title">IMPORTANT:</span> Unit performance is affected by the quantity of events that
are reported. </div></div>
<div class="p">Event Notifications can be sent to different destinations to be logged:<ul class="ul" id="concept_hzf_t1g_xz__ul_hjt_tmk_d1b">
<li class="li">Internal destination <ul class="ul" id="concept_hzf_t1g_xz__ul_ijd_njs_d1b">
<li class="li"><a class="xref" href="#concept_fsb_wmp_f1b" title="The event notifications can be logged in a file saved in the DGW File Management system.">Log to File</a> to a file in the DGW File
management system (not available on the 4102S and the Mediatrix C7 series).</li>
<li class="li"><a class="xref" href="#concept_wsr_1bs_d1b" title="The DGW Local Log displays the Event Notifications related to the events occurring on the Mediatrix unit that are generated by the Mediatrix Notifications and Logging Manager (Nlm) service.">Log Locally</a> to the <a class="xref" href="#concept_wsr_1bs_d1b" title="The DGW Local Log displays the Event Notifications related to the events occurring on the Mediatrix unit that are generated by the Mediatrix Notifications and Logging Manager (Nlm) service.">Local Logs</a> page of the DGW Web
interface.</li>
</ul></li>
<li class="li">External destination<ul class="ul" id="concept_hzf_t1g_xz__ul_zp2_yjs_d1b">
<li class="li">to a <a class="xref" href="#concept_dqy_pkp_f1b" title="It is possible to send the event notifications to a SIP server.">SIP server via
NOTIFY</a>.</li>
<li class="li">to a <a class="xref" href="#concept_brq_dpg_1r" title="Event notifications can be logged by a Syslog server.">Syslog</a> server via
syslog transport.</li>
</ul>
</li>
</ul></div>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title2" id="task_f4n_wq3_11b">
<h2 class="title topictitle2" id="ariaid-title2">Logging Event Notifications</h2>
<div class="body taskbody">
<section id="task_f4n_wq3_11b__steps_vj1_kr3_11b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_f4n_wq3_11b__steps_vj1_kr3_11b"><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Event Log</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Service Notification Configuration</span> table, click + located next to <span class="keyword wintitle">Services</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">For each service, choose the <span class="keyword wintitle">Severity</span> level that will
trigger the notifications.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> if you do not wish to log the event notifications of a service, select
<span class="keyword wintitle">Disable</span>.</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> At this point, you have only enabled the possibility to log event
notifications.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Criteria</span>
field, enter <span class="keyword wintitle">All</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Action</span>
drop-down list, select where and how the event notifications will be
logged.</span>
<ol type="a" class="ol substeps" id="task_f4n_wq3_11b__substeps_y1d_wj3_f1b">
<li class="li substep substepexpand">
<span class="ph cmd">Choose <a class="xref" href="#concept_wsr_1bs_d1b" title="The DGW Local Log displays the Event Notifications related to the events occurring on the Mediatrix unit that are generated by the Mediatrix Notifications and Logging Manager (Nlm) service.">Log Locally</a> to display
the event notifications in the Local Log.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Choose <a class="xref" href="#concept_fsb_wmp_f1b" title="The event notifications can be logged in a file saved in the DGW File Management system.">Log to File</a> to send the
event notifications to the DGW file management system (not available on
the Mediatrix 4102S and C7 Series).</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Choose <a class="xref" href="#concept_brq_dpg_1r" title="Event notifications can be logged by a Syslog server.">Send via Syslog</a> to send
the event notifications to a Syslog server.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Choose <a class="xref" href="#concept_fgn_wqy_vjb" title="The event notification can be sent via the SNMP transport.">Send via SNMP</a> to send
the event notification via the SNMP transport.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> You cannot choose <a class="xref" href="#concept_dqy_pkp_f1b" title="It is possible to send the event notifications to a SIP server."><span class="keyword wintitle">Send Via SIP</span></a> if you wish to log all event notifications, as this
may overload the SIP gateway. The system will indicate <span class="keyword wintitle">Not Supported</span>.
</div>
</div>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">If you selected <a class="xref" href="#concept_brq_dpg_1r" title="Event notifications can be logged by a Syslog server.">Send via
Syslog</a> in the previous step, make sure you have configured the
address of the syslog server under <span class="keyword wintitle">Syslog Configuration</span>/<span class="keyword wintitle">Remote Host</span>
field.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <img class="image" id="task_f4n_wq3_11b__image_jlx_5v3_11b" src="https://documentation.media5corp.com/download/attachments/62825785/Plusbleu.jpg" width="15">.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>All event notifications with the appropriate selected <span class="keyword wintitle">Severity</span> level of each selected
service will be logged to the chosen destination. <br><img class="image" id="task_f4n_wq3_11b__image_tbk_lm3_f1b" src="https://documentation.media5corp.com/download/attachments/62825785/NotificationEvents.png" width="800"><br></section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title3" id="unique_4887489261937006916">
<h2 class="title topictitle2" id="ariaid-title3">Logging Specific Event Notifications</h2>
<div class="body taskbody">
<section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>Instead of logging all the event notifications, as specified in <a class="xref" href="#task_f4n_wq3_11b">Logging Event
Notifications</a>, the <span class="keyword wintitle">Criteria</span> can be refined to a subset
of events.</section>
<section id="unique_4887489261937006916__steps_vj1_kr3_11b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_4887489261937006916__steps_vj1_kr3_11b"><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Event Log</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Service Notification Configuration</span> table, click + located next to <span class="keyword wintitle">Services</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Severity</span>
drop-down list, for each service, choose the severity level that will trigger
the notification.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> If you do not wish to log the event notifications of a service, select
<span class="keyword wintitle">Disable</span>.</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> At this point, you have only enabled the possibility to log event
notifications.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Notification Events</span> table,
select a <span class="keyword wintitle">Service</span> for
which Event Notifications must be issued.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Notification</span>
drop-down list, select one, or several, specific service notifications you wish
to log.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> The <span class="keyword wintitle">Criteria</span>
field will be auto populated with the selection made in the <span class="keyword wintitle">Notification</span>
field.</div>
</div>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> To log all the notifications of a specific service enter in the <span class="keyword wintitle">Criteria</span> field the
service code with all separated by a coma. For example: 200.all to log all
the notifications of the Bni service. (The code can be found in the
<span class="keyword wintitle">Service</span>
drop-down list.)</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Action</span>
drop-down list, select where and how the event notifications will be
logged.</span>
<ol type="a" class="ol substeps" id="unique_4887489261937006916__substeps_y1d_wj3_f1b">
<li class="li substep">
<span class="ph cmd">Choose <a class="xref" href="#concept_wsr_1bs_d1b" title="The DGW Local Log displays the Event Notifications related to the events occurring on the Mediatrix unit that are generated by the Mediatrix Notifications and Logging Manager (Nlm) service.">Log Locally</a> to display
the event notifications in the Local Log.</span>
</li>
<li class="li substep">
<span class="ph cmd">Choose <a class="xref" href="#concept_fsb_wmp_f1b" title="The event notifications can be logged in a file saved in the DGW File Management system.">Log to
File</a> to send the event notifications to the DGW file
management system. (not available on the Mediatrix 4102S and C7
Series).</span>
</li>
<li class="li substep">
<span class="ph cmd">Choose <a class="xref" href="#concept_brq_dpg_1r" title="Event notifications can be logged by a Syslog server.">Send via Syslog</a> to send
the event notifications to a Syslog server. </span>
</li>
<li class="li substep">
<span class="ph cmd">Choose <a class="xref" href="#concept_dqy_pkp_f1b" title="It is possible to send the event notifications to a SIP server.">Send via SIP</a> to send the
event notifications to a SIP server. </span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">This step is not necessary if you chose <span class="keyword wintitle">Log To File</span> in the previous
step. In <span class="keyword wintitle">Syslog Configuration</span> table,
in the <span class="keyword wintitle">Remote Host</span>
field, enter the IP address of the server. </span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <img class="image" id="unique_4887489261937006916__image_jlx_5v3_11b" src="https://documentation.media5corp.com/download/attachments/62825785/Plusbleu.jpg" width="15">.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Repeat steps 4 to 7 for each notification you wish to publish.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The selected service notifications with the corresponding <span class="keyword wintitle">Severity</span> level will be published to
the selected destination. <br><img class="image" id="unique_4887489261937006916__image_vnm_nv3_f1b" src="https://documentation.media5corp.com/download/attachments/62825785/NotificationEvents_specific.png" width="800"><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title4" id="topic_title_Destinations_for_Event_Notifications_d1e18">
<h1 class="title topictitle1" id="ariaid-title4">Destinations for Event Notifications</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title5" id="concept_brq_dpg_1r">
<h2 class="title topictitle2" id="ariaid-title5">Send via Syslog</h2>
<div class="body conbody"><p class="shortdesc">Event notifications can be logged by a Syslog server.</p>
<div class="p">The event notifications will be sent over UDP in the syslog format, to the syslog server
specified in the configuration. Alternatively, the syslog server address can be provided through
DHCP. It is important to understand that if no syslog server address is provided by a DHCP server
or specified by the administrator, no messages are sent.<div class="note important note_important"><span class="note__title">IMPORTANT:</span> In some cases,
Mediatrix devices can generate more information than the syslog server can handle. In these
cases, it is preferable to capture the information with Wireshark.</div>
</div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title6" id="concept_dqy_pkp_f1b">
<h2 class="title topictitle2" id="ariaid-title6">Send via SIP</h2>
<div class="body conbody"><p class="shortdesc">It is possible to send the event notifications to a SIP server.</p>
<p class="p">The event notifications sent to a SIP server are included in the SIP Notify messages. When
choosing to send event notifications to a SIP server, it is not allowed to send all
notifications, i.e. select the <span class="keyword wintitle">All</span>
criteria when configuring event notifications. This has been implemented to avoid sending high
volumes of traffic and risking the overload of the SIP server.</p>
<p class="p">The destination can be configured with the <span class="keyword parmname">sipEp.sipNotificationsGateway</span>
parameter and the <span class="keyword parmname">sipEp.maxNotificationsPerNotify</span> parameter is used to
define how many messages can be sent in a single "SIP NOTIFY" request the </p>
<p class="p"> For more details, refer to <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Reference+Guide" target="_blank">DGW Configuration Guide - Reference Guide</a> published on the Media5
documentation portal at <a class="xref" href="https://documentation.media5corp.com" target="_blank">https://documentation.media5corp.com</a></p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title7" id="concept_wsr_1bs_d1b">
<h2 class="title topictitle2" id="ariaid-title7">Log Locally</h2>
<div class="body conbody"><p class="shortdesc">The DGW Local Log displays the Event Notifications related to the events occurring on
the Mediatrix unit that are generated by the Mediatrix Notifications and Logging Manager (Nlm)
service.</p>
<p class="p">Notifications will be displayed in the <span class="keyword wintitle">Local Log Entries</span> table of the DGW Web
interface provided the issuing of events for a service is enabled, and if the event meets the
selected severity level chosen to be reported. </p>
<div class="p">The <span class="keyword wintitle">Local Log Entries</span> table has the
following characteristics: <ul class="ul" id="concept_wsr_1bs_d1b__ul_qbk_jlh_11b">
<li class="li">Number of displayed event notifications is limited</li>
<li class="li">Newer notifications replace older ones. </li>
<li class="li">The routing criteria should be designed to avoid overloading the log. </li>
<li class="li">The local log has no persistence. Its content is erased when the unit or the Nlm service
is restarted. </li>
<li class="li">The local log does not accept messages from the SNMP service with a ‘Debug’ severity
level. This is to prevent an issue when reading the local log with SNMP. The SNMP walk
through the table would not catch up with the increasing index because of the DEBUG events
generated by the SNMP service itself.</li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title8" id="concept_fsb_wmp_f1b">
<h2 class="title topictitle2" id="ariaid-title8">Log to File</h2>
<div class="body conbody"><p class="shortdesc">The event notifications can be logged in a file saved in the DGW File Management
system.</p>
<p class="p">Event notifications logged to a file will be available in the DGW Web interface, under
<span class="keyword wintitle">Management</span>/<span class="keyword wintitle">File</span> tabs. The log to file feature is not
available on the Mediatrix 4102S and C7 Series as they do not have more than 1MB or more user
storage. The number of files stored in the unit is limited. When the maximal number is reached,
the oldest stored file is deleted. The limit is configured in the
<span class="keyword parmname">LogFileMaxNb</span> Mib parameter. </p>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title9" id="concept_fgn_wqy_vjb">
<h2 class="title topictitle2" id="ariaid-title9">Send via SNMP</h2>
<div class="body conbody"><p class="shortdesc">The event notification can be sent via the SNMP transport.</p>
<div class="p">The Send via SNMP entries have the following characteristics:<ul class="ul" id="concept_fgn_wqy_vjb__ul_jry_yqy_vjb">
<li class="li">The traps will be sent according to the Trap Destination(s) and SNMP Protocols configured in
the Management/SNMP tab of the unit.</li>
<li class="li">By default, Notifications are only sent at severity level Warning or higher. This means you
will only get traps in case of an error. To also get the recovery events for a particular
service, set its severity to « Info » in System/Event Log/Service Notification
Configuration.</li>
<li class="li">For SNMP traps, the notification queue is limited to 100 notifications per second for
bandwidth limitation purposes.</li>
<li class="li">Newer traps replace older ones.</li>
<li class="li">The routing criteria should be designed to avoid overloading the queue</li>
</ul></div>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title10" id="concept_adk_ztr_d1b">
<h1 class="title topictitle1" id="ariaid-title10">Diagnostic Traces </h1>
<div class="body conbody"><p class="shortdesc">Diagnostic Traces are specifically used for troubleshooting purposes. As for Event
Notifications, they report errors, warnings, or system information. </p>
<p class="p">Diagnostic Traces do not need to be activated, except at the specific demand of Media5
Technical Assistance Center. </p>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title11" id="task_a55_cck_wz">
<h2 class="title topictitle2" id="ariaid-title11">Logging Diagnostic Traces</h2>
<div class="body taskbody">
<section id="task_a55_cck_wz__steps_wxn_fck_wz"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_a55_cck_wz__steps_wxn_fck_wz"><li class="li step stepexpand">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Event Log</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Remote Host</span>
field, enter the static IP address or domain name and port number of the device
that archives the log entries sent by syslog transport. </span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> Specifying no port, or port 0, sends notifications to port 514.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">From the <span class="keyword wintitle">Diagnostic Traces</span> field,
select <span class="keyword wintitle">Enable</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Edit</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="keyword wintitle">Diagnostic Traces</span> table, select the level of severity an event should have to be reported by
the syslog.</span>
<div class="itemgroup info">
<div class="note important note_important"><span class="note__title">IMPORTANT:</span> Enabling all the traces will reduce the performance of
the Mediatrix unit and may cause it to no longer respond.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>. </span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="keyword wintitle">Apply</span>
again.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The traces generated by the Mediatrix unit with the selected severity level, will be
sent to the specified address.<br><img class="image" id="task_a55_cck_wz__image_qhd_x2k_wz" src="https://documentation.media5corp.com/download/attachments/62825785/SyslogConfiguration1.png" width="800"><br></section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title12" id="topic_title_Basic_tasks_d1e26">
<h1 class="title topictitle1" id="ariaid-title12">Basic tasks</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title13" id="task_url_2zf_xz">
<h2 class="title topictitle2" id="ariaid-title13">Clearing the Local Logs</h2>
<div class="body taskbody">
<section id="task_url_2zf_xz__steps_knt_nzf_xz"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_url_2zf_xz__steps_knt_nzf_xz"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Local Log</span>.</span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Clear Local Log</span>.
</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The entries in the <span class="keyword wintitle">Local Log Entries</span> table will be
permanently deleted. </section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title14" id="unique_2120003795836893088">
<h2 class="title topictitle2" id="ariaid-title14">Updating the Local Logs</h2>
<div class="body taskbody">
<section id="unique_2120003795836893088__steps_knt_nzf_xz"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_2120003795836893088__steps_knt_nzf_xz"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Local Log</span>.</span>
</li><li class="li step">
<span class="ph cmd">Click <span class="keyword wintitle">Refresh Local Log</span>. </span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>All new entries generated by the Notifications and Logging Manager (NLM) of your
Mediatrix unit will be displayed in the <span class="keyword wintitle">Local Log Entries</span> table. </section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title15" id="task_cnz_bfh_11b">
<h2 class="title topictitle2" id="ariaid-title15">Disabling Event Notification Reporting for a Service</h2>
<div class="body taskbody">
<section id="task_cnz_bfh_11b__steps_yyw_mfh_11b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_cnz_bfh_11b__steps_yyw_mfh_11b"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Event Log</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Service Notification Configuration</span> table, from the drop-down list located next to a service name, select
<span class="keyword wintitle">Disable</span>.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>No event notifications will be issued for the service.</section>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title16" id="unique_1191024339833039885">
<h2 class="title topictitle2" id="ariaid-title16">Modifying the Severity Level Triggering the Reporting of a Notification</h2>
<div class="body taskbody">
<section id="unique_1191024339833039885__steps_yyw_mfh_11b"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="unique_1191024339833039885__steps_yyw_mfh_11b"><li class="li step">
<span class="ph cmd">Go to <span class="keyword wintitle">System</span>/<span class="keyword wintitle">Event Log</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="keyword wintitle">Service Notification Configuration</span> table, from the drop-down list located next to a service name, select the
severity level an event should have to issue a notification.</span>
</li></ol></section>
<section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>Notifications will be issued for the service only if the severity level matches the
selection.</section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title17" id="concept_zqb_h14_1r">
<h1 class="title topictitle1" id="ariaid-title17">Command Line Interface (CLI)</h1>
<div class="body conbody"><p class="shortdesc">The Command Line Interface (CLI) provides an access to interactively configure all the
Mediatrix unit parameters.</p>
<div class="p"><div class="note important note_important"><span class="note__title">IMPORTANT:</span> Although it is possible to configure existing ruleset parameters via the
CLI, it is not possible to create or edit a ruleset from the CLI: it must be either imported
or directly created or edited in the DGW Web interface.</div>The CLI is accessed through
either a secure SSH session (default) or an unsecure TELNET session. When using a secure SSH
session, all communications between Client and server are encrypted before being sent over the
network, thus packet sniffers are unable to extract user names, passwords, and other
potentially sensitive data. This is the default and recommended way to access the Command Line
Interface.</div>
<p class="p">The command interpreter interface of the CLI allows the user to browse the unit parameters,
write the command lines, and display the system's notification log.</p>
</div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title18" id="reference_cyv_gsg_xz">
<h2 class="title topictitle2" id="ariaid-title18">Advanced Log Parameters</h2>
<div class="body refbody">
<section class="section">When using the <a class="xref" href="#concept_dqy_pkp_f1b" title="It is possible to send the event notifications to a SIP server.">Send via Syslog
</a>destination the following CLI parameters can be used:<ul class="ul" id="reference_cyv_gsg_xz__ul_lwz_fz2_g1b">
<li class="li"><span class="keyword parmname" id="reference_cyv_gsg_xz__sipEpsipNotificationsGateway">sipEp.sipNotificationsGateway</span> to
define the gateway that will be used.</li>
<li class="li"><span class="keyword parmname">sipEp.maxNotificationsPerNotify</span> to define how many messages can be
sent in a single "SIP NOTIFY" request.</li>
</ul></section>
<section class="section">When using the<a class="xref" href="#concept_fsb_wmp_f1b" title="The event notifications can be logged in a file saved in the DGW File Management system."> Log to File</a>
destination, the following CLI parameter can be used: <ul class="ul" id="reference_cyv_gsg_xz__ul_eqz_jz2_g1b">
<li class="li"><span class="keyword parmname">LogFileMaxNb</span> to set the maximum number of files stored in the file
management system. </li>
</ul></section>
<section class="section"> For complete details on parameters, refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Reference+Guide" target="_blank">DGW Configuration Guide - Reference Guide</a> published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</section>
</div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title19" id="reference_j4g_nbv_gfb">
<h1 class="title topictitle1" id="ariaid-title19">Online Help</h1>
<p class="shortdesc"><span class="ph">If you are not familiar with the meaning of the fields and
buttons, click <span class="keyword wintitle">Show Help</span>, located at the upper right corner of
the Web page. When activated, the fields and buttons that offer online help will
change to green and if you hover over them, the description will bedisplayed.</span></p>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title20" id="concept_v4k_q3h_1r">
<h1 class="title topictitle1" id="ariaid-title20">DGW Documentation</h1>
<div class="body conbody"><p class="shortdesc">Mediatrix devices are supplied with an exhaustive set of documentation. </p>
<p class="p">Mediatrix user documentation is available on the <a class="xref" href="http://documentation.media5corp.com" target="_blank">Media5 Documentation
Portal</a>.</p>
<div class="p">Several types of documents were created to clearly present the information you are looking for.
Our documentation includes:<ul class="ul" id="concept_v4k_q3h_1r__ul_bqy_cjh_1r">
<li class="li"><strong class="ph b">Release notes</strong>: Generated at each GA release, this document includes the known and
solved issues of the software. It also outlines the changes and the new features the release
includes.</li>
<li class="li"><strong class="ph b">Configuration notes</strong>: These documents are created to facilitate the configuration of a
specific use case. They address a configuration aspect we consider that most users will need to
perform. However, in some cases, a configuration note is created after receiving a question
from a customer. They provide standard step-by-step procedures detailing the values of the
parameters to use. They provide a means of validation and present some conceptual information.
The configuration notes are specifically created to guide the user through an aspect of the
configuration. </li>
<li class="li"><strong class="ph b">Technical bulletins</strong>: These documents are created to facilitate the configuration of a
specific technical action, such as performing a firmware upgrade.</li>
<li class="li"><strong class="ph b">Hardware installation guide</strong>: They provide the detailed procedure on how to safely and
adequately install the unit. It provides information on card installation, cable connections,
and how to access for the first time the Management interface.</li>
<li class="li"><strong class="ph b">User guide</strong>: The user guide explains how to customise to your needs the configuration
of the unit. Although this document is task oriented, it provides conceptual information to
help the user understand the purpose and impact of each task. The User Guide will provide
information such as where and how TR-069 can be configured in the Management Interface, how to
set firewalls, or how to use the CLI to configure parameters that are not available in the
Management Interface.</li>
<li class="li"><strong class="ph b">Reference guide</strong>: This exhaustive document has been created for advanced users. It
includes a description of all the parameters used by all the services of the Mediatrix units.
You will find, for example, scripts to configure a specific parameter, notification messages
sent by a service, or an action description used to create Rulesets. This document includes
reference information such as a dictionary, and it does not include any step-by-step
procedures. </li>
</ul></div>
</div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested0" aria-labelledby="ariaid-title21" id="concept_fqm_rv4_k4">
<h1 class="title topictitle1" id="ariaid-title21">Copyright Notice</h1>
<div class="body conbody"><p class="shortdesc">Copyright © 2023 Media5 Corporation.</p>
<p class="p">This document contains information that is proprietary to Media5 Corporation.</p>
<p class="p">Media5 Corporation reserves all rights to this document as well as to the Intellectual Property
of the document and the technology and know-how that it includes and represents.</p>
<p class="p">This publication cannot be reproduced, neither in whole nor in part, in any form whatsoever,
without written prior approval by Media5 Corporation.</p>
<p class="p">Media5 Corporation reserves the right to revise this publication and make changes at any time
and without the obligation to notify any person and/or entity of such revisions and/or
changes.</p>
</div>
</article></article></main></body></html> |
