[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ns] mns_v2.0 for ns-2.1b8(a)



Hello,

a new version of the adapted mns_v2.0 for ns-2.1b8(a) is available. If you
are interested, send me an e-mail and I will send the software to you.
Major improvement:
Most re-routing scenarios are running now.

README
THIS IS AN ALPHA VERSION. PLEASE REPORT BUGS, PROBLEMS, ETC.
(to [email protected])

mns_v2.0 is an MPLS extension for ns-2 originally written by Gaeil Ahn
for ns-2.1b6. The changes of mns_v2.0 are based on the changes done in
the integration of mns_v1.0 for ns-2.1b8 by Haobo Yu.

Before installing mns_v2.0 make sure that you have installed ns-2.1b8(a)
properly.

To install the adapted mns_v2.0 just extract the archive
'gunzip -c -d mns_v2.0-for-ns-2.1b8a.tar.gz | tar xvfm -'
in the ns-allinone-2.1b8a/ directory.
In directory ns-2.1b8(a) run './configure' and then 'make'.

Note: The .tcl test-scripts in the tcl/ex/mns_v2.0 directory can all be
run:
test-lsp.tcl -> the .nam .tr files are equal compared to mns_v2.0
                integrated in ns-2.1b6
                (control-driven, data-driven, on-demand, ordered-control)
test-crlsp.tcl -> the .nam .tr files are equal compared to mns_v2.0 
                  integrated in ns-2.1b6, however the bandwidth
                  calculations are not the same
test-crlsp.tcl -> the .nam .tr files are slightly different compared to
                  mns_v2.0 integrated in ns-2.1b6, I think this is due
                  to the changed rtProto/DV, the bandwidth
                  calculations are not the same
test-constraint-routing.tcl -> the .nam .tr files are slightly different
                               compared to mns_v2.0 integrated in
                               ns-2.1b6 (maybe due
                               to the changed rtProto/DV), the bandwidth
                               calculations are not the same
test-reroute.tcl -> scripts are running, meaningful results are produced
                    'drop': trace file is the same as trace file produced
                            by mns_v2.0 integrated in ns-2.1b6 (despite
                            of rtProto/DV packets)

                    'L3control-driven'
                    'makam'
                    'simple-dynamic'
                    'shortest-dynamic': results are similar to results of
                                        mns_v2.0 integrated in ns-2.1b6

                    'L3data-driven'
                    'haskin':       re-routing does not work, behaviour
                                    is the same as with option 'drop'

----------------------------------------------------------------------------
Christian Glomb
Siemens AG
Corporate Technology
Networks and Multimedia Communications
Email: [email protected]
----------------------------------------------------------------------------