How to interpret the NS2 tracefile (manually) for wireless simulation

Assume you created a tcl file for a wireless simulation and it generates a trace file (usually .tr as extension). If any tracing softwares are not available, how to interpret manually, here is the step

ACTION: [s|r|D]: s -- sent, r -- received, D – dropped


WHEN: the time when the action happened


 

WHERE: the node where the action happened


LAYER: AGT -- application,


RTR -- routing,
LL -- link layer (ARP is done here)
IFQ -- outgoing packet queue (between link and mac layer)
MAC -- mac,
PHY – physical

 

 

flags:

 

SEQNO: the sequence number of the packet


 

TYPE: the packet type
cbr -- CBR data stream packet
DSR -- DSR routing packet (control packet generated by routing)
RTS -- RTS packet generated by MAC 802.11
ARP -- link layer ARP packet


SIZE: the size of packet at current layer, when packet goes down, size increases, goes up size decreases
[a b c d]: a -- the packet duration in mac layer header
b -- the mac address of destination
c -- the mac address of source
d -- the mac type of the packet body


flags:

[......]: [
source node ip : port_number
destination node ip (-1 means broadcast) : port_number
ip header ttl
ip of next hop (0 means node 0 or broadcast)
]




So we can interpret the below trace

s 0.0297823400 _1_ RTR --- 2012 cbr 32 [0 0 0 0] ------- [1:0 0:0 32 0]


as Application 0 (port number) on node 1 sent a CBR packet whose ID is 2012 and size is 32 bytes, at time 0.029 second, to application 0 on node 0 with TTL is 32 hops. The next hop is not decided yet.



And we can also interpret the below trace



r 0.010176954 _9_ RTR  --- 1 gpsr 29 [0 ffffffff 8 800] ------- [8:255 -1:255 32 0]


in the same way, as The routing agent on node 9 received a GPSR broadcast (mac address 0xff, and ip address is -1, either of them means broadcast) routing packet whose ID is 1 and size is 19 bytes, at time 0.010176954 second, from node 8 (both mac and ip addresses are 8), port 255 (routing agent).



This link has been taken for reference from http://ns-2.blogspot.com/2007/06/how-to-interprete-ns2-tracefile-for.html

Comments

  1. hi,,,,,,
    actually i am doing project in Ad-hoc using Ant Colony Optimization. In this i am using ns-2.34 with pre-compiled AntHocNet. Now i need to study about the trace files created after running simple-wireless.tcl file. the routing protocols used and the corresponding trace file contents were mentioned below.
    will you give guidelines for studying these formats? means which column represents which thing etc. especially at first and last of each line.
    AODV
    M 10.00000 0 (5.00, 2.00, 0.00), (20.00, 18.00), 1.00
    s 10.000000000 _0_ AGT --- 0 tcp 40 [0 0 0 0] ------- [0:0 1:0 32 0] [0 0] 0 0
    r 10.000000000 _0_ RTR --- 0 tcp 40 [0 0 0 0] ------- [0:0 1:0 32 0] [0 0] 0 0
    s 10.000000000 _0_ RTR --- 0 AODV 48 [0 0 0 0] ------- [0:255 -1:255 30 0] [0x2 1 1 [1 0] [0 4]] (REQUEST)
    AntHocNet
    s 0.000000000 _0_ RTR --- 0 AntHocNet 44 [0 0 0 0] ------- [0:255 -1:255 0 0] [ant 0 0 0]
    DSR
    Sconfig 0.00000 tap: on snoop: rts? on errs? on
    Sconfig 0.00000 salvage: on !bd replies? on
    Sconfig 0.00000 grat error: on grat reply: on
    Sconfig 0.00000 $reply for props: on ring 0 search: on
    Sconfig 0.00000 using MOBICACHE
    M 10.00000 0 (5.00, 2.00, 0.00), (20.00, 18.00), 1.00
    s 10.000000000 _0_ AGT --- 0 tcp 40 [0 0 0 0] ------- [0:0 1:0 32 0] [0 0] 0 0
    r 10.000000000 _0_ RTR --- 0 tcp 40 [0 0 0 0] ------- [0:0 1:0 32 0] [0 0] 0 0
    s 10.006071162 _0_ RTR --- 1 DSR 32 [0 0 0 0] ------- [0:255 1:255 32 0] 1 [1 1] [0 1 0 0->0] [0 0 0 0->0]

    ReplyDelete

Post a Comment

Popular Posts