This guide focuses on the MLTG-360’s software configuration, it does not cover Documentation hardware installation of the MLTG-360. For information on how to install the MLTG-360 and all safety information and regulatory statements, see the following document: Quick Start Guide...
Page 4
Contact If you have further questions, please submit a ticket at: https://support.edge- core.com/hc/en-us or send us an email: ecwifi@edge-core.com. Revision History This section summarizes the changes in each revision of this guide. December 2021 Revision This is the third version of this guide. This guide is valid for software release v1.2.0.
Contents How to Use This Guide Contents Figures Tables Section I Getting Started 1 Introduction Terragraph Network Connecting to the Web Interface Section II Web Configuration 2 Dashboard System Network Topology 3 Management Network Configuration Management Admin Account Password Configuration PoE Out 4 Operation Mode Operation Mode...
Page 6
Contents IPv6 addressing and physical port assignment on the POP node 5 Topology Node Setting Configure Nodes (DN) Interface PoE Out General Radio Discover Nodes Link Setting 6 System General Settings Time Failure Recovery SNMP Maintenance System Actions Firmware Upgrade Radio Sectors Section III Appendices...
Section I Getting Started This section provides an overview of the device, and introduces some basic concepts about Terragraph networks. It also describes the basic settings required to access the management interface. This section includes these chapters: ◆ "Introduction" on page 10 –...
A Terragraph network is composed of individual nodes. There are two types of nodes in a Terragraph network – Distribution Nodes (DNs) such as the MLTG-360, and Client Nodes (CNs) such as the MLTG-CN. DNs are the backbone of the Terragraph network that distribute Internet connectivity from one or more fiber optic Points of Presence (PoPs) over multiple hops to CNs.
In case the DHCP server is unavailable, the MLTG-360 uses the fallback IP 192.168.1.20 and subnet mask 255.255.255.0. Set the PC IP address to be on the same subnet as the MLTG-360 MGMT PoE IN port. The PC IP address must start with 192.168.1.x and use subnet mask 255.255.255.0.
Chapter 1 | Introduction Connecting to the Web Interface Log in to the web interface using default settings: Username = admin Password = admin Figure 2: Login – 12 –...
Section II Web Configuration This section describes the basic MLTG-360 features, along with a detailed description of how to configure each feature via a web browser. This section includes these chapters: ◆ "Dashboard" on page 14 ◆ "Management" on page 19 ◆...
Dashboard After logging in to the web interface, the Dashboard screen is displayed. The Dashboard shows basic settings and status of the device regarding system information, network, and topology. Figure 3: System Dashboard System The following items are displayed in this section: ◆...
MAC address of each radio. The number of radios and their position varies ■ by model: Figure 4: Position of Radios Table 1: Product lineup Product Name Position of Radios MLTG-360 A, B, C, D MLTG-360-3 A, C, D MLTG-360-2R A, D MLTG-360-2P...
Chapter 2 | Dashboard Network The following interface addresses are displayed in this section: Figure 5: Network Dashboard ◆ Interface IP: Management Interface: Bound to the PoE In port. This traffic is separated ■ from the access network and should be assigned to a subnet different from the uplink interface.
Chapter 2 | Dashboard ◆ Neighbor Nodes: Node ID: Unique node ID defined for Open/R. ■ From (Local): Local interface connecting to a neighbor node. ■ To: Connected interface of the neighbor node. ■ Radio Link: Local address link of the neighbor node. ■...
Page 18
Chapter 2 | Dashboard Link Name: Automatically generated name based on the connected nodes. ■ Self Mac: Current device’s radio MAC address connecting the link. ■ Peer Mac: The radio MAC address of the peer device. ■ RSSI: Received signal strength indication, this is an indicator of the received ■...
Management Network Configuration The management interface is bound to the physical PoE In port. The management interface is isolated from the access network. There are two available configuration modes: DHCP or static. In both modes, the configuration of IPv4 and IPv6 addresses depends on the capability of the management network.
Chapter 3 | Management PoE Out PoE Out The four Ethernet LAN ports support PoE out function. There are two types of specifications; LAN1 supports 802.3af/802.3 at standard PoE whereas LAN2, LAN3, and LAN4 support 24V passive PoE out. For each port, the PoE out can be enabled/disabled independently. For passive PoE out ports, only enable PoE out when a compatible passive PoE device is connected to the port.
Mesh topology: Links can be established to form a mesh topology network ■ that provides path redundancy and high availability. Layer 3 based: Each MLTG-360 works as a Layer 3 router. The traffic is ■ transmitted based on routing information on the Terragraph network.
Terragraph LAN Prefix and Terragraph LAN Prefix Length to guarantee the address pool is large enough to accommodate all nodes. There are six wired network interfaces on the MLTG-360. The MGMT port (PoE In) is a dedicated, out-of-band management port, isolated from other ports.
◆ Enable GPS Sync Check: When enabled, the MLTG-360 checks whether the GPS information is synchronized when associating with a peer. Synchronized GPS information can help to optimize the TDMA algorithm in a mesh network.
Page 25
Chapter 4 | Operation Mode Operation Mode When this option is enabled, please make sure the MLTG-360 has a strong and stable GPS signal. Please disable GPS Sync when indoors. ◆ WebUI Access Through NMS Control interface: Enable to allow access to the POP WebUI through the NMS control address.
Chapter 4 | Operation Mode Operation Mode Control Interface: Select a physical interface for the PoP to communicate ■ with the external NMS or management terminals. You can check the physical port mapping in the graph. Control VLAN ID: Configure the VLAN ID for the control interface. If the ■...
Topology The network connectivity and topology can be defined on the PoP node when the local controller is enabled. After defining the topology, the PoP will find the nodes and set up links automatically. To configure a topology, all nodes and links must be defined.
Chapter 5 | Topology Configure Nodes (DN) ◆ POP Node: Only one of the MLTG-360 devices can be the PoP node in a topology. ◆ Status: Current status of the device. The keyword initiator means the DN is capable of initiating links.
Chapter 5 | Topology Configure Nodes (DN) PoE Out Enable or disable the PoE Out function for each LAN port. Figure 15: DN PoE Out Configuration ◆ General Failure Recovery: Configure the number of power sequences to trigger switching boot banks and reset to factory defaults. Figure 16: DN General Configuration Note: The number of retries for switching boot banks must be larger than for...
Chapter 5 | Topology Configure Nodes (DN) ◆ Radio Enable/Disable Radio Sectors: Click to disable the corresponding radio. All radios are enabled by default. ◆ Country: Select the installation region to automatically apply country-specific settings following local standards. Figure 17: DN Radio Configuration –...
Chapter 5 | Topology Discover Nodes Discover Nodes The Node Discovery feature allows you to add nodes quickly and correctly. It is designed to add nodes ahead of the on-site installation. To use this feature, connect the management port of the new nodes to a switch or a hub for the PoP to access their information via the management ports.
Chapter 5 | Topology Link Setting Figure 19: Link Setting Terragraph Mode ◆ Name: The name of the link. It is defined automatically based on the peers’ names. ◆ Peer: The two endpoints of a link. ◆ Channel: Select the working channel. Channels 1 to 4 are available. ◆...
System General Settings Figure 20: General Settings ◆ Time Time zone: Select the appropriate time zone using the pair continent/capital city. ◆ NTP server: Add the address of the network time protocol server used for time synchronization. Failure Recovery The device has dual boot partitions. ◆...
It is used to configure devices and monitor them for performance and errors. The MLTG-360 supports SNMP v2 and v3. It can be monitored through standard Management Information Bases (MIBs), such as MIB-II and UCD MIB—also private MIBs but only accessible via the control path (Control Address) or the Terragraph LAN address.
Chapter 6 | System Maintenance Maintenance Figure 21: Maintenance ◆ System Actions Download Diagnostics Log: Click to download the log file to the management workstation. On Windows, a GNU Zip (*.tar.gz) file is stored in the Downloads folder. The diagnostics log file contains information that can help resolve technical issues with the device.
Chapter 6 | System Maintenance ◆ File Input: Select an image file (.rom) to upgrade to a newer firmware from a local file on the management workstation. New firmware may be provided periodically by Edgecore. After a firmware upgrade, you must reboot the device to implement the changes.
Section III Appendices This section provides additional information and includes the following items: ◆ “Specifications” on page 38 ◆ “Troubleshooting” on page 39 – 37 –...
Specifications Specifications Table 3: Hardware Specifications Physical Power Passive PoE (Pins 1, 2, 4, 5 +; pins 3, 6, 7, 8 -; injector optional) 42.5 V ~ 59 V DC terminal block Size (WxDxH) 19.9 x 19.9 x 20.0 cm (7.83 x 7.83 x 7.87 in) Weight 3.9 kg (8.6 lb) with bracket Interfaces...
Be sure the management station has an IP address in the same subnet as the MLTG-360’s IP. ◆ If you are trying to connect to the MLTG-360 using a tagged VLAN group, your management station, and the ports connecting intermediate switches in the network, must be configured with the appropriate tag.
Need help?
Do you have a question about the MLTG-360 and is the answer not in the manual?
Questions and answers