Scribd
Upload
47 views

A Remote That Can Notify You If Its LAN Connection Goes Down

The document discusses remote telemetry units that can detect if their local area network (LAN) connection has gone down. It describes how the NetGuardian remote can monitor its own LAN connection status, unlike basic remotes that only detect their local connection and not issues further in the LAN. The NetGuardian can send a pager notification if the LAN connection fails using its internal modem as a backup. It also supports the SNMP protocol for improved network visibility.

Uploaded by

Anum Bakhtiar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
47 views

A Remote That Can Notify You If Its LAN Connection Goes Down

The document discusses remote telemetry units that can detect if their local area network (LAN) connection has gone down. It describes how the NetGuardian remote can monitor its own LAN connection status, unlike basic remotes that only detect their local connection and not issues further in the LAN. The NetGuardian can send a pager notification if the LAN connection fails using its internal modem as a backup. It also supports the SNMP protocol for improved network visibility.

Uploaded by

Anum Bakhtiar
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

A Remote That Can Notify You If Its LAN

Connection Goes Down


Most remote telemetry units offer only limited functions for detecting LAN
connectivity. A standard remote can only detect whether its local connection is
up. If the local connection is intact, but the LAN beyond the connection is down,
the basic remote will still report a working LAN. Compare this to the
NetGuardian, whose ability to ping any selected IP address gives it visibility of
the complete alarm reporting path.
One of the great things about the

NetGuardian is that it's a LAN-based

remote that's still operational when the LAN is down. Because of its internal
modem and paging capability, the NetGuardian always has an alternate path for
sending alarm data or page notifications even if your entire LAN fails.
This means that the NetGuardian can effectively monitor its own LAN
connection. Many users have configured their NetGuardians to send a pager
notification if the LAN connection fails. (Pager notifications can also be used to
provide continued visibility of other critical alarms during a LAN failure.)

NetGuardian RTUs That Support SNMP


SNMP is a widely used protocol. Therefore, many NetGuardians support 1 or
more versions of SNMP to improve your network visibility.
Mesh topology a typical scenario
A typical mesh scenario in an urban environment may look like this, connecting mostly rooftops - but
potentially including many other locations for nodes, like antenna towers, other towers, trees, mobile
nodes (like cars, people with computers, ...):

Image 3: A typical mesh scenario

Mesh routing protocol types


A mesh routing protocol is a piece of software that has to handle the (dynamic) routing and connection of
nodes in a mesh.
Mesh routing protocols: Types
Depending on the way in which the protocol controls the links and their states, we distinguish two main
types of mesh routing protocols:
Pro-active (Table-driven)
These are characterized by proactive checking of link state and updating of routing tables, which leads to
high complexity and CPU load, but also to high performance.
Reactive (On-demand)
Passive reacting on detection problems (non-working routes) tends to be less performant, but is also less
demanding on CPU.
The lines between those two types are not strict - many mixed and different approaches exist.
In what follows, we list the most important examples of mesh routing protocols:
Mesh routing protocols: Pro-active (Table-driven)
OLSR (Optimized Link State Routing Protocol), OLSR-EXT, QOLSR
TBRPF (Topology Broadcast based on Reverse-Path Forwarding routing protocol)
HSLS (Hazy Sighted Link State routing protocol)
MMRP (Mobile Mesh Routing Protocol), short: MobileMesh

OSPF (Open Shortest Path First)


Mesh routing protocols: Reactive (On-demand)
AODV
Elements of mesh routing
Among the main elements of mesh routing protocols are:
Node discovery to find out about nodes as they appear and disappear
Border discovery to find out about the limits/edges of a network
Link metrics to measure the quality of the links between the nodes
Route calculation to find the best routes, based on the quality of the links
IP address management to assign and control the IP addresses on the network
Uplink/backhaul management to take care of connections to external networks, for example uplinks to
the general internet

Mesh routing protocols: Examples


The following is an overview of some of the mesh routing protocols relevant in wireless networking.
MMRP (MobileMesh)

Mobile Mesh protocol contains three separate protocols, each addressing a specific function
Link Discovery - a Simple 'Hello- Protocol
Routing - Link State Packet Protocol
Border Discovery - Enables external tunnels

Developed by Mitre.
The Mobile Mesh software is covered by the GNU General Public License (Version 2)
Comment: MobileMesh is a good starting point for educationla experiments with Linux laptops.
Some instructions can be found here:
http://www.oreillynet.com/pub/a/wireless/2004/01/22/wirelessmesh.html
OSPF
Open Shortest Path First (OSPF) developed by the Interior Gateway Protocol (IGP) working group of the
IETF, is based on the SPF algorithm.
The OSPF specification is in the public domain, published as RFC1247.
OSPF sends calls for the sending of link-state advertisements (LSAs) to all other routers within the same
hierarchical area. Information on attached interfaces, metrics used, and other variables are included in
these LSAs.
OSPF routers accumulate link-state information, using the SPF algorithm to calculate shortest paths.
As a link-state routing protocol, OSPF contrasts (and competes) with RIP and IGRP, which are distancevector routing protocols. Routers running the distance-vector algorithm send all or a portion of their
routing tables in routing-update messages to their neighbours.

OLSR
OLSR is short for Optimized Link State Routing protocol, and described in RFC3626.
OLSR is a routing protocol for mobile ad-hoc networks. The protocol is pro-active, table driven and utilizes
a technique called multipoint relaying (MPR) for message flooding. Currently the implementation compiles
on GNU/Linux, Windows, OS X, FreeBSD and NetBSD systems.
OLSRD is meant to be a well structured and well coded implementation that should be easy to maintain,
expand and port to other platforms. The implementation is RFC3626 compliant with respect to both core
and auxiliary functioning.
OLSR is currently seen as one of the most promising and stable protocols.
Germany: Freifunk OLSR Mesh, Berlin, Germany
This experimental urban community network currently consists of around 200 nodes, based on OLSR
FreifunkFirmware. This software has found a lot of use in community and development projects.
Source: http://www.freifunk.net

Image
8: Freifunk OLSR Mesh Berlin

You might also like