Re: [Omnetpp] MPLS / LDP simulation framework of INET
Jens Buysse
1. Does the LDP_LSR ALWAYS assumes a NamTRACE ? Even if you do not
necessarily need it? Because when I startup the simulation (with
or without NamTrace) I get "Enter parameter
"Topology.Router1.namid" ... This is very annoying.
2. Assuming my .NED file (topology) is correct - I am not sure how I
can assign correct routing tables. In the example file LDP_Test
there are several files like LSR1.rt which I assume are the
routing tables/information of the corresponding routers.. So if I
create a LDP_LSR, do I always have to create such a file? If yes,
where can I find the template to do this - I do not see where this
is explained. Another question about the assignation of
IP-addresses and routing information : NetworkConfigurator claims
to autoassign IP-addresses and routers to nodes. The only thing I
should do is to add this module to my NED file, but this does not
seem to do anything. So how can I use it? Should I add the @node
paramter somewhere (this is what the doc. says).
If these questions could be answered, then I could finally start the
simulation and do some real work :)
Kind regards
Jens Buysse
>
> * MPLS / LDP simulation framework of INET <#group_thread_5> [1
> Update]
> * please help me to use mobility framework for omnet 4
> <#group_thread_6> [2 Updates]
> * Calculating confidence interval "Important" <#group_thread_7> [1
> Update]
> * Ieee80211gMac frames counting <#group_thread_8> [1 Update]
>
> Topic: MPLS / LDP simulation framework of INET
> <http://groups.google.com/group/omnetpp/t/3c9ff0b65ca6a0c2>
>
> "Andras Varga" <and...@omnetpp.org> Mar 02 01:15PM +0100 ^
> <#digest_top>
> Hi Jens,
> Currently the INET documentation consists of the generated
> neddoc, see
> http://inet.omnetpp.org/doc/INET/neddoc/index.html. It contains
> some
> overview-style pages, but not too many. I agree a dedicated
> manual would be
> nice to have.
> You can get a picture about the MPLS/LDP models by
> browsing the
> neddoc, and
> reading the docu of individual modules. E.g. the description of
> LDP_LSR
> looks like a good starting point, and from there you can explore
> the MPLS,
> LIBTable, TED etc modules. If you have specific questions, you
> can post them
> to the mailing list and I'll try to answer.
> You wrote you have compile/build problems with INET too.
> INET in
> general
> should build fine in the IDE just by importing the project and
> hitting
> Ctrl+B (Build). If there's any problem, please post the details.
> Some observations related to the NED file you attached. From
> what I've
> noticed, you added the "import" directives manually.
> Hand-editing them is
> quite painful and not necessary; in the IDE you can just run
> "Organize
> Imports" (context menu, or hit Ctrl+Shift+O) and that does it
> for you. Also
> what I've noticed is that you have LIBTable at network level;
> this module is
> meant to be used inside routers, so it can be removed from the
> network.
> Hope this helps.
> Regards,
> Andras
> -----Original Message-----
> From: omn...@googlegroups.com [mailto:omn...@googlegroups.com]
> On Behalf
> Of Jens Buysse
> Sent: Monday, March 01, 2010 3:30 PM
> To: omn...@googlegroups.com
> Subject: [Omnetpp-l] MPLS / LDP simulation framework of INET
> Dear users,
> I am fairly new to Omnet++ and Inet++ and I am trying
> several
> little tests
> before I go into the development of a large simulation
> environment for the
> Geysers Project (http://www.geysers.eu/). Now I have to say that
> finding
> information on using the INet library is not that easy. Could
> someone direct
> me to some information on how to use this library (not the only TCP
> tutorial) ? I have tried to model an example topology with some
> LDP routers
> but this does not seem to work/build/compile ...
> I have added the source file of my example ..
> Kind regards Jens Buysse
>
//
// This is the topology file for the first MPLS Test
// the topology structure is shown in figure 1 page 14 in
// the Project Proposal. One of the LICL topologies.
//
//
// @author Jens Buysse
// @version 1.0
//
//import inet.networklayer.extras.FailureManager;
////Standard IP host with TCP UDP layers and applications
//import inet.nodes.inet.StandardHost;
//// Ans LDP Label Switching Router
//import inet.nodes.mpls.LDP_LSR;
//
//
//import inet.world.ScenarioManager;
//
//import ned.DatarateChannel;
//import .FlatNetworkConfigurator;
//import inet.networklayer.mpls.*;
import inet.networklayer.autorouting.NetworkConfigurator;
import inet.nodes.inet.StandardHost;
import inet.nodes.mpls.LDP_LSR;
import inet.world.NAMTrace;
import ned.DatarateChannel;
network Topology
{
types:
channel ch extends DatarateChannel
{
datarate = 40000bps;
delay = 5ms;
}
submodules:
nam: NAMTrace;
configurator: NetworkConfigurator {
parameters:
@display("p=185,50");
}
Router1: LDP_LSR {
parameters:
peers = "router2 router3";
@display("i=abstract/router;p=617,267");
gates:
pppg[3];
}
Router2: LDP_LSR {
parameters:
peers = "router1 router5";
@display("i=abstract/router;p=551,173");
gates:
pppg[2];
}
Router3: LDP_LSR {
parameters:
peers = "router1 router4";
@display("i=abstract/router;;p=551,369");
gates:
pppg[2];
}
Router4: LDP_LSR {
peers = "router3 router6";
@display("i=abstract/router;p=438,173");
gates:
pppg[2];
}
Router5: LDP_LSR {
parameters:
peers = "router2 router6";
@display("i=abstract/router;p=438,369");
gates:
pppg[2];
}
Router6: LDP_LSR {
parameters:
peers = "router4 router5 router7 router8";
@display("i=abstract/router;p=375,277");
gates:
pppg[5];
}
Router7: LDP_LSR {
parameters:
peers = "router6 router9";
@display("i=abstract/router;;p=278,369");
gates:
pppg[2];
}
Router8: LDP_LSR {
parameters:
peers = "router6 router9";
@display("i=abstract/router;;p=278,173");
gates:
pppg[2];
}
Router9: LDP_LSR {
parameters:
peers = "router7 router8";
@display("i=abstract/router;p=180,275");
gates:
pppg[3];
}
host1: StandardHost { // client
parameters:
@display("i=device/pc;p=696,267");
}
host2: StandardHost { // client
parameters:
@display("i=device/pc;p=375,436");
}
host3: StandardHost { // client
parameters:
@display("i=device/pc;p=81,275");
}
connections:
//Backbone
Router1.pppg[0] <--> ch <--> Router2.pppg[0];
Router1.pppg[1] <--> ch <--> Router3.pppg[0];
Router2.pppg[1] <--> ch <--> Router5.pppg[0];
Router3.pppg[1] <--> ch <--> Router4.pppg[0];
Router4.pppg[1] <--> ch <--> Router6.pppg[0];
Router5.pppg[1] <--> ch <--> Router6.pppg[1];
Router6.pppg[2] <--> ch <--> Router7.pppg[0];
Router6.pppg[3] <--> ch <--> Router8.pppg[0];
Router7.pppg[1] <--> ch <--> Router9.pppg[0];
Router8.pppg[1] <--> ch <--> Router9.pppg[1];
//Access links
host1.pppg++ <--> ch <--> Router1.pppg[2];
host2.pppg++ <--> ch <--> Router6.pppg[4];
host3.pppg++ <--> ch <--> Router9.pppg[2];
}
Andras Varga
1. NamTrace. If you add this to omnetpp.ini, it will eliminate the
"Enter parameter "Topology.Router1.namid" question:
**.namid=-1
Alternatively, modify LDP_LSR and change the line
int namid;
to
int namid = default(-1);
for the same effect.
> Does the LDP_LSR ALWAYS assumes a NamTRACE
NAMTraceWriter's docu says it:
//
// When placed inside a host or router, it writes a NAM trace, based on
// notifications it receives via the NotificationBoard. It expects to find
// a NAMTrace module named "nam" at network level. If the "nam" module
// is missing, this module does not do anything and has no runtime
// overhead.
//
// This module has no gates and does not process messages.
//
// @see NAMTrace, NotificationBoard
//
simple NAMTraceWriter
{
parameters:
int namid = default(-1); // -1 means auto
@display("i=block/sink");
}
So no, it's not necessary. You can remove it from LDP_LSR if you like.
2. FlatNetworkConfigurator automatically assigns IP addresses (see any
example, e.g. inet/nclients), but maybe not the way you'd like. You can
tweak FlatNetworkConfigurator to better suit your needs, or you may use
routing files as in the examples. If there'd be a lot of routing files,
maybe you want to generate them, or write a configurator that makes routing
files unnecessary. @node is already included in the LDP_LSR's source.
Regards
Andras
Kind regards
Jens Buysse
nam: NAMTrace;
}
--
You received this message because you are subscribed to the Google Groups
"omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to
omnetpp+u...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/omnetpp?hl=en.