Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated @ 2023-08-09T12:28:55.847822
HTML
headtrue
encodingUTF-8
<!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="topic"><meta name="prodname" content="For all Mediatrix units"><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="yes"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="topic_title_Basic_Concepts_d1e15"><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>Network Interfaces</title></head><body class="nobody"><header role="banner"><div class="topicmeta title">Network Interfaces</div><div class="topicmeta date">2023-0308-28<09</div><div class="topicmeta product">For all Mediatrix units </div><div class="topicmeta version">DGW 49.12.2884<2941</div><div class="topicmeta pdf"><a href="https://documentation.media5corp.com/download/attachments/62825785/Network%20Interfaces.pdf" rel="nofollow">Download PDF Document</a></div><hr><span style="float: inline-end;"></span></header><nav role="toc"><ul><li><a href="#topic_title_Basic_Concepts_d1e15">Basic Concepts</a><ul><li><a href="#reference_lhs_xy4_qcb">Important Information About Network Interfaces </a></li><li><a href="#concept_dt4_p3s_jq">Default Network Interfaces</a><ul><li><a href="#reference_ybv_p1m_nw">Link Default Values for the Uplink Network Interface</a></li><li><a href="#reference_spk_msl_nw">Link Default Values for the Lan1 Network Interface</a></li></ul></li><li><a href="#concept_hfw_kjv_sbb">IP Address Reservation</a></li><li><a href="#concept_k3w_qjk_mcb">Link Layer Discovery Protocol (LLDP) </a></li><li><a href="#concept_q5m_knp_mcb">Link Connectivity Detection </a></li><li><a href="#concept_h4l_3xp_mcb">PPP Negotiation</a></li></ul></li><li><a href="#topic_title_Basic_Tasks_d1e24">Basic Tasks</a><ul><li><a href="#task_vn5_hrw_bq">Creating a Network Interface</a></li><li><a href="#task_xnh_xpf_5cb">Creating a VLAN</a></li><li><a href="#task_b5b_srr_2q">Configuring a Network Interface</a></li><li><a href="#task_dc2_vtm_lw">Associating an Ethernet Link to a Network Interface </a></li><li><a href="#task_gph_v4s_jq">Disabling the Rescue Interface</a></li><li><a href="#task_km3_zbf_xq">Configuring the PPPoE Connection Type</a></li><li><a href="#task_ktc_tpb_vbb">Configuring the Link Layer Discovery Protocol (LLDP)</a></li><li><a href="#task_mvd_dkh_vbb">Configuring the Ethernet Link linked to a Network Interface</a></li><li><a href="#task_fxh_4vh_vbb">Selecting the IEEE 802.1x Version </a></li><li><a href="#task_lc1_rh3_bq">Locating the MAC Address of Your Mediatrix Unit</a></li></ul></li><li><a href="#topic_title_Advanced_Parameters_d1e35">Advanced Parameters</a><ul><li><a href="#concept_mxb_21p_qcb">IPv6 Autoconfiguration Interfaces</a></li><li><a href="#concept_o2m_n1p_qcb">Stateless Autoconfiguration</a></li><li><a href="#concept_eln_fsp_mcb">Spanning Tree Protocol vs Stateless Autoconfiguration </a></li><li><a href="#concept_h2l_twp_mcb">Statefull Autoconfiguration</a></li><li><a href="#concept_bpb_ryp_mcb">Speed and Duplex Detection Issues</a></li><li><a href="#reference_h3d_yvp_mcb">Advanced Network Interface 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="topic_title_Basic_Concepts_d1e15">
   <h1 class="title topictitle1" id="ariaid-title1">Basic Concepts</h1>
<article class="topic reference nested1" aria-labelledby="ariaid-title2" id="reference_lhs_xy4_qcb">
  <h2 class="title topictitle2" id="ariaid-title2">Important Information About Network Interfaces </h2>
  <div class="body refbody">
    <section class="section"><h3 class="title sectiontitle">Naming</h3>
      
      <ul class="ul" id="reference_lhs_xy4_qcb__ul_bgh_zy4_qcb">
        <li class="li">The name of the network interface is case sensitive.</li>
        <li class="li">Using the special values All, Loop, LoopV6, and Rescue are not allowed to name a network
          interface</li>
        <li class="li">A valid network interface name: <ul class="ul" id="reference_lhs_xy4_qcb__ul_ejl_rz4_qcb">
            <li class="li"> must start with a letter</li>
            <li class="li">cannot contain characters other than letters, numbers, and underscores</li>
          </ul></li>
      </ul>
    </section>
    <section class="section"><h3 class="title sectiontitle">Configuration</h3>
      
      <ul class="ul" id="reference_lhs_xy4_qcb__ul_pl5_5z4_qcb">
        <li class="li">It is not possible to have different IP addresses from the same subnet on one
          interface.</li>
        <li class="li">It is possible to create up to 48 network interfaces.</li>
        <li class="li">LLDP cannot be activated on multiple network interfaces simultaneously.</li>
        <li class="li">If no network is configured in IPv6, the unit does not have any IPv6 address, not even
          the Link-Local address. When a network is configured in IPv6, the Link-Local (FE80 ::...)
          address is automatically created and displayed in the Network Status information.</li>
        <li class="li">In case of address conflicts between two or more network interfaces, the network
          interface with the highest priority will remain enabled and the other interfaces will be
          disabled. If the priority is the same, only the first enabled network interface will be
          able to use the IP address. When a conflict ends, all network interfaces concerned
          automatically return to an operational state.</li>
        <li class="li">Media5 recommends to reserve an IP address with an infinite lease for each Mediatrix unit
          on the network.</li>
        <li class="li">The Rescue Network Interface cannot be deleted.</li>
      </ul>
      <div class="note important note_important"><span class="note__title">IMPORTANT:</span> Use extreme care when configuring network interfaces, especially when
        configuring the network interface used to contact the unit for management. Be careful never
        to disable or delete the network interface used to contact the unit. Also be careful to
        always set the unit’s management interface to be an interface that you can contact.</div>
    </section>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title3" id="concept_dt4_p3s_jq">
  <h2 class="title topictitle2" id="ariaid-title3">Default Network Interfaces</h2>
  
  <div class="body conbody"><p class="shortdesc">There are four Network Interfaces created by default on the Mediatrix unit: Uplink, Lan
    1, UplinkV6,  and Rescue.</p>
    <div class="p">
      <ul class="ul" id="concept_dt4_p3s_jq__ul_jz3_35g_mr">
        <li class="li">The <span class="keyword wintitle">Uplink</span> network interface
          defines the uplink information required by the Mediatrix unit to properly connect to the
          WAN. (By default eth1 for all platforms, except for the 4102S which is WAN . By default,
          this interface uses the <span class="keyword wintitle">IpDhcp (IPv4 DHCP)</span>
          connection type. If you are using only one Network Interface, you must use <span class="keyword wintitle">Uplink</span>.</li>
        <li class="li">The <span class="keyword wintitle">Lan1</span> network interface
          defines the information required by the Mediatrix unit to properly connect to the LAN.(By
          default eth2-5 for all platforms, except for the 4102 which is LAN) By default, the
            <span class="keyword wintitle">Lan1</span> Network Interface uses
          the <span class="keyword wintitle">IpStatic (IPv4 Static)</span> connection type.
          The <span class="keyword wintitle">Lan1</span> network interface can
          only be added on units with 2 network ports. </li>
        <li class="li"> The <span class="keyword wintitle">Rescue</span> network interface,
          is used to display the <span class="keyword wintitle">Rescue</span>
          Management Interface when a partial reset of the unit is performed. By default, the
            <span class="keyword wintitle">Rescue</span> network interface <ul class="ul" id="concept_dt4_p3s_jq__ul_xxc_g2q_mcb">
            <li class="li">is disabled and automatically enabled when a partial reset is performed.</li>
            <li class="li">uses the <span class="keyword wintitle">IpStatic (IPv4 Static)</span> or the
                <span class="keyword wintitle">Ip6Static (IPv6 Static)</span> addresses.</li>
          </ul>The <span class="keyword wintitle">Rescue</span> Network
          Interface cannot be deleted. Refer to the <a class="xref" href="https://documentation.media5corp.com/display/DGWLATEST/Performing+a+Partial+Reset" target="_blank">Technical Bulletin - Performing a Partial Reset</a>
          document published on the <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</li>
        <li class="li">The <span class="keyword wintitle">UplinkV6 </span> network interface
          defines the IPv6 uplink information required by the Mediatrix unit to properly connect to
          the WAN. By default, this interface uses the <span class="keyword wintitle">IP6autoConf (IPv6 Auto-Conf)</span> configuration
          mode.</li>
      </ul>It is possible to create up to 48 Network Interfaces. </div>
  </div>
<hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested2" aria-labelledby="ariaid-title4" id="reference_ybv_p1m_nw">
  <h3 class="title topictitle3" id="ariaid-title4">Link Default Values for the Uplink Network Interface</h3>
  <div class="body refbody">
    <table class="table frame-all" id="reference_ybv_p1m_nw__table_zk3_cbm_nw"><caption></caption><colgroup><col style="width:50%"><col style="width:50%"></colgroup><thead class="thead">
          <tr class="row">
            <th class="entry colsep-1 rowsep-1" id="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Unit Type</th>
            <th class="entry colsep-1 rowsep-1" id="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">Link Default Value</th>
          </tr>
        </thead><tbody class="tbody">
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Sentinel 400</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">eth1</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Sentinel 100</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">eth1</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Mediatrix G7</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">eth1</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Mediatrix S7</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">eth1</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Mediatrix C7 series</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">eth1</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__1">Mediatrix 4102S</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_ybv_p1m_nw__table_zk3_cbm_nw__entry__2">Wan</td>
          </tr>
        </tbody></table>
  </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested2" aria-labelledby="ariaid-title5" id="reference_spk_msl_nw">
  <h3 class="title topictitle3" id="ariaid-title5">Link Default Values for the Lan1 Network Interface</h3>
  <div class="body refbody">
    <table class="table frame-all" id="reference_spk_msl_nw__table_nbm_rsl_nw"><caption></caption><colgroup><col style="width:50%"><col style="width:50%"></colgroup><thead class="thead">
          <tr class="row">
            <th class="entry colsep-1 rowsep-1" id="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Unit Type</th>
            <th class="entry colsep-1 rowsep-1" id="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">Link Default Value</th>
          </tr>
        </thead><tbody class="tbody">
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Sentinel 400</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">eth2-5</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Sentinel 100</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">eth2-5</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Mediatrix G7 series</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">eth2-5</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Mediatrix S7 series</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">eth2-5</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Mediatrix C7 series</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">eth2</td>
          </tr>
          <tr class="row">
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__1">Mediatrix 4102</td>
            <td class="entry colsep-1 rowsep-1" headers="reference_spk_msl_nw__table_nbm_rsl_nw__entry__2">lan</td>
          </tr>
        </tbody></table>
  </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title6" id="concept_hfw_kjv_sbb">
 <h2 class="title topictitle2" id="ariaid-title6">IP Address Reservation</h2>
 
 <div class="body conbody"><p class="shortdesc">Before connecting the Mediatrix unit to the network, Media5 strongly recommends to
  reserve an IP address in your network server – if using one – for the unit you are about to
  connect. </p>
  <p class="p">This way, the IP address associated with a particular unit will be known. Network servers
   generally allocate a range of IP addresses for use on a network and reserve IP addresses for
   specific devices using a unique identifier for each device. The Mediatrix unit unique identifier
   is the media access control (MAC) address. Refer to <a class="xref" href="#task_lc1_rh3_bq">Locating the MAC Address of Your Mediatrix Unit</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_k3w_qjk_mcb">
 <h2 class="title topictitle2" id="ariaid-title7">Link Layer Discovery Protocol (LLDP) </h2>
 
 <div class="body conbody"><p class="shortdesc">The Link Layer Discovery Protocol (LLDP) service is used by network devices for
  advertising their identity, capabilities, and neighbors on a IEEE 802 local area network, usually
  wired Ethernet.</p>
  <p class="p">LLDP cannot be activated on more than one network interface at a time.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title8" id="concept_q5m_knp_mcb">
 <h2 class="title topictitle2" id="ariaid-title8">Link Connectivity Detection </h2>
 
 <div class="body conbody"><p class="shortdesc">Each Ethernet port of the Mediatrix unit is associated with an Ethernet
  link.</p>
  <p class="p"> An Ethernet link has connectivity if at least one of its port status is not disconnected. The
   link connectivity is periodically polled (every 500 milliseconds). It takes two consecutive
   detections of the same link state before reporting a link connectivity transition. This avoids
   reporting many link connectivity transitions if the Ethernet cable is plugged and unplugged
   quickly.</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_h4l_3xp_mcb">
 <h2 class="title topictitle2" id="ariaid-title9">PPP Negotiation</h2>
 
 <div class="body conbody"><p class="shortdesc">When the Mediatrix unit restarts, it establishes the connection to the access
  concentrator in conformance with RFC 2516 section 5.1. </p>
  <div class="p">When establishing a PPP connection, the Mediatrix unit goes through three distinct phases:<ul class="ul" id="concept_h4l_3xp_mcb__ul_jsj_qxp_mcb">
    <li class="li"><span class="keyword wintitle">Discovery phase</span>: The Mediatrix unit broadcasts the value of the Service
          Name field. The access concentrator with a matching service name answers the Mediatrix
          unit. <ul class="ul" id="concept_h4l_3xp_mcb__ul_z3m_txp_mcb">
            <li class="li">If no access concentrator answers, this creates a <span class="keyword wintitle">PPPoE failure</span>
              error. </li>
            <li class="li">If more than one access concentrators respond to the discovery, the Mediatrix unit
              tries to establish the PPP connection with the first one that supports the requested
              service name.</li>
          </ul></li>
    <li class="li"><span class="keyword wintitle">Authentication phase</span>: If the access concentrator requests
          authentication, the Mediatrix unit sends the ID/secret pair configured in the User Name
          and Password fields. If the access concentrator rejects the authentication, this creates
          an “authentication failure” error.</li>
    <li class="li"><span class="keyword wintitle">Network-layer protocol phase</span>: The Mediatrix unit negotiates an IP
          address. The requested IP address is the one from the last successful PPPoE connection. If
          the Mediatrix unit never connected by using PPPoE (or after a factory reset), it does not
          request any specific IP address.</li>
   </ul></div>
 </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title10" id="topic_title_Basic_Tasks_d1e24">
   <h1 class="title topictitle1" id="ariaid-title10">Basic Tasks</h1>
<article class="topic task nested1" aria-labelledby="ariaid-title11" id="task_vn5_hrw_bq">
    <h2 class="title topictitle2" id="ariaid-title11">Creating a Network Interface</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Network Interface Configuration</span> table, click +.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd"><span class="ph">Enter a name in the <span class="keyword wintitle">Name</span> field.</span></span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> The Network Interface name must be unique and is case sensitive.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">Link</span>
                    selection list, select <span class="keyword wintitle">Ip6Static (IPv6 Static)</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Static IP Address</span> field, enter the FQDN or IP address of </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 new Network Interface will be available in the: <ul class="ul" id="task_vn5_hrw_bq__ul_gjm_bl4_qcb">
                <li class="li"><span class="keyword wintitle">Media Interface Configuration</span>
                    table under the <span class="keyword wintitle">SBC</span>/
                        <span class="keyword wintitle">Configuration</span> tabs
                    (provided you have the Sbc service)</li>
                <li class="li"><span class="keyword wintitle">Signaling Interface Configuration</span> table under <span class="keyword wintitle">SBC</span>/
                        <span class="keyword wintitle">Configuration</span> tabs
                    (provided you have the Sbc service)</li>
                <li class="li"><span class="keyword wintitle">DHCP Server
              Configuration</span> table under the <span class="keyword wintitle">Network</span>/ <span class="keyword wintitle">DHCP Server</span> tabs</li>
                <li class="li"><span class="keyword wintitle">Signaling Network</span> table
                    under the <span class="keyword wintitle">SIP</span>/<span class="keyword wintitle">Gateways</span>
                    tabs</li>
                <li class="li"><span class="keyword wintitle">Network Interface</span> table
                    under the <span class="keyword wintitle">SIP Proxy</span>/<span class="keyword wintitle">Configuration</span>
                    tabs.</li>
                <li class="li"><span class="keyword wintitle">Network Interface</span> table
                    under the <span class="keyword wintitle">Management</span>/<span class="keyword wintitle">Misc</span> tabs.</li>
                <li class="li"><span class="keyword wintitle">Forward To Network</span> table
                    under the <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">IP Routing</span>
                    tabs.</li>
            </ul></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title12" id="task_xnh_xpf_5cb">
    <h2 class="title topictitle2" id="ariaid-title12">Creating a VLAN</h2>
    <div class="body taskbody">
        
        <section id="task_xnh_xpf_5cb__steps_id3_fqf_5cb"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_xnh_xpf_5cb__steps_id3_fqf_5cb"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">VLAN</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">VLAN Configuration</span> table,
                    from the <span class="keyword wintitle">Link</span>
                    selection list, select the Ethernet link the vlan will use. </span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Complete the <span class="keyword wintitle">VlanId</span>
                    and the <span class="keyword wintitle">Default User Priority</span> fields
                    as required. </span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <img class="image" id="task_xnh_xpf_5cb__image_y4s_hrf_5cb" src="https://documentation.media5corp.com/download/attachments/62825785/Plusbleu.jpg" width="17"> located at the end of the newly created Vlan.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Do not forget to enable the VLan under <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span></div>
                </div>
            </li></ol></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title13" id="task_b5b_srr_2q">
    <h2 class="title topictitle2" id="ariaid-title13">Configuring a Network Interface</h2>
    <div class="body taskbody">
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div> When configuring
            network interfaces, Media5 recommends to have a syslog client properly configured and
            enabled in order to receive any message related to the network interfaces behaviour. The
            interface used to access the syslog client must also be properly enabled.</section>
        <section id="task_b5b_srr_2q__steps_hqr_vrr_2q"><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps" id="task_b5b_srr_2q__steps_hqr_vrr_2q"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
                <div class="itemgroup info">
                    <div class="note important note_important"><span class="note__title">IMPORTANT:</span> Use extreme care when configuring network interfaces,
                        especially when configuring the network interface used to contact the unit
                        for management. Be careful never to disable or delete the network interface
                        used to contact the unit. Also be careful to always set the unit’s
                        management interface to be an interface that you can contact.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Network Interface Configuration</span> table, complete the fields as required.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">Activation</span>
                    drop-down list, select <span class="keyword wintitle">Enable</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
            </li></ol></section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title14" id="task_dc2_vtm_lw">
    <h2 class="title topictitle2" id="ariaid-title14">Associating an Ethernet Link to a Network Interface </h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Network Interface Configuration</span> table, from the <span class="keyword wintitle">Link</span> field , select the link to be associated with a Network Interface (the link
                    will appear as ethx.VlanId).</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> Once the changes are applied, the connection with the unit might be lost.
                        You may need to reconnect to the Web page.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Complete the fields as required. </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 Network interface is associated with a physical interface i.e. an Ethernet
                Link.<br><img class="image" id="task_dc2_vtm_lw__image_ksm_dzz_nw" src="https://documentation.media5corp.com/download/attachments/62825785/NetworkInterfacesConfiguration_Vlan.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-title15" id="task_gph_v4s_jq">
    <h2 class="title topictitle2" id="ariaid-title15">Disabling the Rescue Interface</h2>
    <div class="body taskbody">
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>By default the Rescue interface is disabled. However, after a partial reset the
            rescue interface is enabled. <div class="note important note_important"><span class="note__title">IMPORTANT:</span> The Rescue interface is bound to the
                unit's WAN port (wan for the Mediatrix 4102S, and ETH1
                for all other Mediatrix units). The IP address of the Rescue interface is
                192.168.0.1 (IPv4) or an IPv6 Link Local address.</div></section>
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Management</span>/<span class="keyword wintitle">Misc</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">Network Interface</span> drop-down
                    menu, select the interface that will be used to manage the unit.</span>
                <div class="itemgroup info">
                    <div class="note important note_important"><span class="note__title">IMPORTANT:</span> If you keep the <span class="keyword wintitle">Rescue Interface</span>
                        selected, you will not be able to get into the management interface after
                        disabling it.</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">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Rescue Interface</span> table, from the <span class="keyword wintitle">Activation</span> selection list,
                    select <span class="keyword wintitle">Disable</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span>.</span>
                <div class="itemgroup info">
                    <div class="note important note_important"><span class="note__title">IMPORTANT:</span> Make sure to reconfigure at least the user's
                        authentication and firewall rules (if applicable), otherwise it may leave
                        the unit unsecure.</div>
                </div>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The unit will be reachable either on the new configured static IP address or on the
            DHCP .<br><img class="image" id="task_gph_v4s_jq__image_ils_j1c_3s" src="https://documentation.media5corp.com/download/attachments/62825785/RescueNetworkConfiguration.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-title16" id="task_km3_zbf_xq">
    <h2 class="title topictitle2" id="ariaid-title16">Configuring the PPPoE Connection Type</h2>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>The <span class="keyword wintitle">User Name</span> and <span class="keyword wintitle">Password</span> fields are not accessible
            if you have the User or Observer access right.</section>
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">Context</strong></div>Perform this procedure only if you have selected <span class="keyword wintitle">PppIpcp (IPv4 PPPoE)</span> as a connection type for
            your Network Interfaces.</section>
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">PPPoE Configuration</span> table,
                    complete the fields as required.</span>
            </li><li class="li step">
                <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 current PPPoE information is displayed in the <span class="keyword wintitle">Status</span> page.</section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title17" id="task_ktc_tpb_vbb">
    <h2 class="title topictitle2" id="ariaid-title17">Configuring the Link Layer Discovery Protocol (LLDP)</h2>
    <div class="body taskbody">
        <section class="section prereq"><div class="tasklabel"><strong class="sectiontitle tasklabel">Before you begin</strong></div>The Llpd service must be started. </section>
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">LLDP Configuration</span> table,
                    select the network interface name on which LLDP should be enabled.</span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span>  LLDP cannot be activated on multiple network interfaces
                        simultaneously.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Select the address type to populate the chassis ID device identifier.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Select whether to enable the LLDP-MED protocol override of the VLAN ID.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span> if you do
                    not need to set other parameters. </span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The current LLDP information is displayed in the <span class="keyword wintitle">Status</span> tab.</section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title18" id="task_mvd_dkh_vbb">
    <h2 class="title topictitle2" id="ariaid-title18">Configuring the Ethernet Link linked to a Network Interface</h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step stepexpand">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">In the <span class="keyword wintitle">Ethernet Link
              Configuration</span>table, set the <span class="keyword wintitle">MTU</span>
                    field of a specific Ethernet link with required value. </span>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span> The MTU value applied for a PPPoE connection is the smallest of the value
                        negotiated with the server and the value configured here.</div>
                </div>
                <div class="itemgroup info">
                    <div class="note note note_note"><span class="note__title">Note:</span>  Each Network interface used by TCP/IP may have a different MTU value
                        specified. All VLAN connections use the MTU size configured on their related
                        Ethernet link.</div>
                </div>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">802.1x Authentication</span> select
                        <span class="keyword wintitle">Enable</span> for each
                    Ethernet link requiring 802.1x Authentication.</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Enter  the <span class="keyword wintitle">EAP username</span> used to authenticate each Ethernet link interfaces during the IEEE 802.1x
                    EAPTLS authentication process..</span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">From the <span class="keyword wintitle">EAP Certificate
              Validation</span>
                    field, choose the IEEE 802.1x level of validation used by the device to
                    authenticate the IEEE 802.1x EAPTLS peer's certificate. </span>
            </li><li class="li step stepexpand">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span> if you do
                    not need to set other parameters. </span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>The current status of the network interfaces is displayed in the <span class="keyword wintitle">Status</span> page. </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title19" id="task_fxh_4vh_vbb">
    <h2 class="title topictitle2" id="ariaid-title19">Selecting the IEEE 802.1x Version </h2>
    <div class="body taskbody">
        
        <section><div class="tasklabel"><strong class="sectiontitle tasklabel">Steps</strong></div><ol class="ol steps"><li class="li step">
                <span class="ph cmd">Go to <span class="keyword wintitle">Network</span>/<span class="keyword wintitle">Interfaces</span>.</span>
            </li><li class="li step">
                <span class="ph cmd">In the <span class="keyword wintitle">EAP 802.1x Configuration</span> table,
                    select the IEEE 802.1x version.</span>
            </li><li class="li step">
                <span class="ph cmd">Click <span class="keyword wintitle">Apply</span> if you do
                    not need to set other parameters.</span>
            </li></ol></section>
        <section class="section result"><div class="tasklabel"><strong class="sectiontitle tasklabel">Result</strong></div>
            <br><img class="image" id="task_fxh_4vh_vbb__image_xpw_vcq_mcb" src="https://documentation.media5corp.com/download/attachments/62825785/EAP8021xConfiguration.png" width="500"><br>
        </section>
    </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic task nested1" aria-labelledby="ariaid-title20" lang="en-US" id="task_lc1_rh3_bq">
    <h2 class="title topictitle2" id="ariaid-title20">Locating the MAC Address of Your Mediatrix Unit</h2>
    <div class="body taskbody">
        <section class="section context"><div class="tasklabel"><strong class="sectiontitle tasklabel">About this task</strong></div>The MAC address of the unit is: <div class="p">
                <ul class="ul" id="task_lc1_rh3_bq__ul_qyz_1rb_3s">
                    <li class="li">printed on a label located under the Mediatrix unit</li>
                    <li class="li">displayed in the <span class="keyword wintitle">Current Status</span> table of
                        the Web Interface (<span class="keyword wintitle">System</span>/<span class="ph uicontrol">Information</span>)</li>
                </ul>
            </div></section>
    </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic nested0 nobody" aria-labelledby="ariaid-title21" id="topic_title_Advanced_Parameters_d1e35">
   <h1 class="title topictitle1" id="ariaid-title21">Advanced Parameters</h1>
<article class="topic concept nested1" aria-labelledby="ariaid-title22" id="concept_mxb_21p_qcb">
 <h2 class="title topictitle2" id="ariaid-title22">IPv6 Autoconfiguration Interfaces</h2>
 
 <div class="body conbody"><p class="shortdesc">When the Type drop-down menu is set to IPv6 Auto-Conf, the network interface is an IPv6
  over Ethernet connection with IP parameters obtained by stateless auto-configuration or stateful
  (DHCPv6) configuration.</p>
  <div class="p"> Autoconfiguration of IPv6 address is first initiated using state-less autoconfiguration.
   Stateful autoconfiguration is initiated only if one of the following conditions is met:<ul class="ul" id="concept_mxb_21p_qcb__ul_vdz_j1p_qcb">
    <li class="li">The router explicitly required stateful autoconfiguration by setting the “managed” or
     “other” flag of the router advertisement.</li>
    <li class="li">No router advertisement was received after 3 router solicitations. RFC 4861 defines the
     number of router solicitations to send and the 4 seconds interval between the sent router
     solicitations.</li>
   </ul></div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title23" id="concept_o2m_n1p_qcb">
 <h2 class="title topictitle2" id="ariaid-title23">Stateless Autoconfiguration</h2>
 
 <div class="body conbody"><p class="shortdesc">All IPv6 addresses present in the router advertisements are applied to the network
  interface</p>
  <div class="p">Each IPv6 address is assigned a network name based on the configured network name with a suffix
   in the following format: ConfiguredNetworkName-XX-Y. XX is the address scope <ul class="ul" id="concept_o2m_n1p_qcb__ul_ofv_x1p_qcb">
    <li class="li">GU (Global Unique)</li>
    <li class="li">UL (Unique Local) </li>
    <li class="li">LL (Link-Local) </li>
   </ul>Y is a unique ID for the address scope. </div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title24" id="concept_eln_fsp_mcb">
 <h2 class="title topictitle2" id="ariaid-title24">Spanning Tree Protocol vs Stateless Autoconfiguration </h2>
 
 <div class="body conbody"><p class="shortdesc">Many network switches use the Spanning Tree Protocol (STP) to manage Ethernet ports
  activity.</p>
  <p class="p"> STP uses a detection timeout before a router advertisement is sent to the Mediatrix unit. The
   default value for this timeout is usually 30 seconds. However, when the unit wants to get an IPv6
   address in Stateless autoconfiguration, this timeout is too long and the unit falls into Stateful
   Autoconfiguration mode before it receives the router advertisement. This results in the unit
   receiving a DHCPv6 address. To solve the issue, check if the default STP detection timeout value
   in your router can be modified. If so, set it to a value of 8 s or less. If you cannot modify the
   timeout value, Media5 recommends to disable the Spanning Tree Protocol on the network to which
   the unit is connected.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title25" id="concept_h2l_twp_mcb">
 <h2 class="title topictitle2" id="ariaid-title25">Statefull Autoconfiguration</h2>
 
 <div class="body conbody"><p class="shortdesc">Stateful autoconfiguration is managed by DHCPv6. The DHCPv6 lease is negotiated
    according to the limitations listed in section 1.5 of  RFC 3315.</p>
  <div class="p">DHCPv6 may be used to obtain the following information (depending on the router advertisement
    flags):<ul class="ul" id="concept_h2l_twp_mcb__ul_fzz_wwp_mcb">
    <li class="li"> IPv6 addresses (when the router advertisement “managed” flag is set)</li>
    <li class="li">Other configuration (when the router advertisement “other” flag is set) </li>
   </ul> If only the “other” flag is set in the router advertisement, the DHCPv6 client only sends
   an information request to the DHCPv6 server, otherwise it sends a DHCPv6 solicit message. If the
   flags change over time, only the transitions from “not set” to “set“ are handled.</div>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic concept nested1" aria-labelledby="ariaid-title26" id="concept_bpb_ryp_mcb">
 <h2 class="title topictitle2" id="ariaid-title26">Speed and Duplex Detection Issues</h2>
 
 <div class="body conbody"><p class="shortdesc">There are two protocols for detecting the Ethernet link speed:  parallel detection and
  auto-negotiation (IEEE 802.3u). </p>
  <p class="p">The auto-negotiation protocol allows the detection of the connection speed and duplex mode. It
   exchanges capabilities and establishes the most efficient connection. When both endpoints support
   the auto-negotiation, there are no problems. However, when only one endpoint supports
   auto-negotiation, the parallel detection protocol is used. This protocol can only detect the
   connection speed; the duplex mode cannot be detected. In this case, the connection may not be
   established. The Mediatrix unit has the possibility to force the desired Ethernet link speed and
   duplex mode by disabling the auto-negotiation and selecting the proper setting. When forcing a
   link speed at one end, be sure that the other end (a hub, switch, etc.) has the same
   configuration. To avoid any problem, the link speed and duplex mode of the other endpoint must be
   exactly the same.</p>
 </div>
</article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested1" aria-labelledby="ariaid-title27" id="reference_h3d_yvp_mcb">
  <h2 class="title topictitle2" id="ariaid-title27">Advanced Network Interface Parameters</h2>
  <div class="body refbody">
    <section class="section">Although the services can be configured in great part in the Web browser, some aspects
      of the configuration can only be completed with the configuration parameters by :<ul class="ul" id="reference_h3d_yvp_mcb__ul_gfn_14v_wr">
        <li class="li">using a MIB browser</li>
        <li class="li">using the CLI</li>
        <li class="li">creating a configuration script containing the configuration parameters</li>
      </ul>For more details on the following parameters, 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 <a class="xref" href="https://documentation.media5corp.com/" target="_blank">Media5 Documentation Portal</a>.</section>
    <section class="section"><h3 class="title sectiontitle">Network Interfaces Priority </h3>Refer to
        <span class="keyword parmname">eth.networkInterfacesPriority</span></section>
    <section class="section"><h3 class="title sectiontitle">DHCP Client Identifier Presentation</h3> Refer to
        <span class="keyword parmname">bni.dhcpClientIdentifierPresentation</span>
    </section>
    <section class="section"><h3 class="title sectiontitle">Ethernet Connection Speed</h3>Refer to <span class="keyword parmname">eth.portsSpeed</span>
    </section>
  </div>
</article></article><hr><span style="float: inline-end;"><a href="#">Top</a></span><article class="topic reference nested0" aria-labelledby="ariaid-title28" id="reference_j4g_nbv_gfb">
  <h1 class="title topictitle1" id="ariaid-title28">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-title29" id="concept_v4k_q3h_1r">
 <h1 class="title topictitle1" id="ariaid-title29">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-title30" id="concept_fqm_rv4_k4">
 <h1 class="title topictitle1" id="ariaid-title30">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>