Version 1 (modified by 9 years ago) ( diff ) | ,
---|
Network Deployment
Topology Control
Since multiple routers may run in a single LAN, connectivity needs to be enforced and packets destined to non-neighbor nodes be dropped. This is enabled in the MobilityFirst router pipeline by way of topology enforcement element that takes a GUID-based connectivity graph passed as a topology file at start up time. Consider below a simple topology with three MobilityFirst routers and two end hosts:
Sender ---- MFR1 ---- MFR2 ---- MFR3 ---- Receiver 100 1 2 3 101 MFR - MobilityFirst Router, and Sender/Receiver are traffic source and sink, respectively
The following contained in the topology file defines the 5-node topology shown above:
#syntax: <node-GUID> <neighbor-count> <neighbor-GUID1> [<neighbor-GUID2>] ... 100 1 1 1 2 2 100 2 2 1 3 3 2 2 101 101 1 3
Logging Configuration
The environment variable MF_CLICK_LOG_LEVEL can be set to an integer value between 0 and 7 corresponding to enable one of the following log levels for the Click-based MF router:
Value Log Level Description 0 TRACE 1 DEBUG 2 INFO 3 TIME Same as INFO with the addition of a micro-second precision timestamp to the beginning of the log message 4 WARN 5 ERROR 6 CRITICAL Out of memory, approaching resource limits, etc. 7 FATAL Unable to proceed, for example when integrity is compromised