I don't understand the output of P4_NDN_experiment,help!

[zhangdongdongdong]

Hi,signorello .
Fortunately, I successfully installed the mini-ndn v0.1.1,and the next steps.
when I use: sudo minindn ~/bishe/mini-ndn/p4.ndn.basic.conf –experiment=P4_NDN_experiment --p4

the output as follows:
Parse of /home/zdd/bishe/mini-ndn/p4.ndn.basic.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b
*** Adding switches:
s1
*** Adding links:
(a, s1) (b, s1)
*** Configuring hosts
a b
Setup time: 0
Reading config file /usr/local/etc/mini-ndn//p4-switch.conf
/home/zdd/bishe/bmv2/targets/simple_switch/simple_switch /home/zdd/bishe/bmv2/targets/simple_switch/runtime_CLI /home/zdd/bishe/NDN.p4/p4src/ndn_router.json l3 9090 True True /home/zdd/bishe/NDN.p4/ndn_commands.partial.txt
P4 setting for host a
Starting NFD on host aa
P4 setting for host b
Starting NFD on host bb
*** Starting controller
c0
*** Starting 1 switches
s1 Starting P4 switch s1
/home/zdd/bishe/bmv2/targets/simple_switch/simple_switch -i 1@s1-eth1 -i 2@s1-eth2 --pcap --thrift-port 9090 --nanolog ipc:///tmp/bm-0-log.ipc --log-console --device-id 0 /home/zdd/bishe/NDN.p4/p4src/ndn_router.json
Disable IPv6 forwarding on the P4Switch
switch has been started
Filling switch tables using /home/zdd/bishe/NDN.p4/ndn_commands.partial.txt
Control utility for runtime P4 table manipulation
RuntimeCmd: Setting default action of count_table
action: storeNumOfComponents
runtime data: 00
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 01
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 02
Entry has been added with handle 1
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 03
Entry has been added with handle 2
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 04
Entry has been added with handle 3
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 05
Entry has been added with handle 4
RuntimeCmd: Setting default action of hashName_table
action: computeStoreTablesIndex
runtime data:
RuntimeCmd: Adding entry to exact match table pit_table
match key: EXACT-05
action: readPitEntry
runtime data:
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table pit_table
match key: EXACT-06
action: cleanPitEntry
runtime data:
Entry has been added with handle 1
RuntimeCmd: Setting default action of fib_table
action: _drop
runtime data:
RuntimeCmd: Adding entry to exact match table updatePit_table
match key: EXACT-01
action: updatePit_entry
runtime data:
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table updatePit_table
match key: EXACT-00
action: _drop
runtime data:
Entry has been added with handle 1
RuntimeCmd: Adding entry to exact match table routeData_table
match key: EXACT-01
action: setOutputIface
runtime data: 00:00
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table routeData_table
match key: EXACT-02
action: setOutputIface
runtime data: 00:01
Entry has been added with handle 1
RuntimeCmd: Setting default action of routeData_table
action: _drop
runtime data:
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 0
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 1
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 2
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-02 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 3
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 4
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 5
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 6
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-01 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 7
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-02 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 8
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 9
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 10
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 11
RuntimeCmd:
I don't start the NLSR daemon on the host
I don't start the NLSR daemon on the host
*** Starting CLI:
mininet> exit
*** Stopping 1 controllers
c0
*** Stopping 2 links
..
*** Stopping 1 switches
s1 ..
*** Stopping 2 hosts
a b
*** Done

Does this means the experiment was successful ? I found the issue 3(#3) it mentioned:
!#
Hello Salvatore,
I applied the last changes and commits,
I removed mini-ndn and installed it again and applied the changed patch files and so the problem is solved and "Hello World" is printed in packetpayload.txt.
Thank you very much for your help
!#

what is packetpayload.txt? where can I find it ? If can't, Is there any other output of for this experiment?
looking forward to your reply,thanks.

I will post my experimental steps later,for other's reference.

[zhangdongdongdong]

My steps is as follows:
(1) If you want to install mini-ndn v0.1.1 correctly，You must ensure that all dependencies of mini-ndn are corresponding version.
I list the correct version of dependencies :
mininet v2.2.1
NFD v0.3.4
NLSR v0.2.1
ndn-cxx 0.3.4
ndn-tools v0.2
mininet v2.2.1
install all dependencies manually,and use: sudo ./install.sh -i to install mini-ndn v0.1.1
(2) install bmv2
(3) install p4c-bmv2
(4) run your two patch files in my main minindn directory
cd $MININDN_DIR; patch -p1 < $NDNP4_DIR/mini-ndn/mini-ndn.patch
cd $MININDN_DIR; patch -p1 < $NDNP4_DIR/mini-ndn/ndn_dir.patch
(5) reinstall the mini-ndn by ./install.sh -i
(6) Copy corresponding files from NDN.p4 to your mini-ndn directory
(7) modified the paths in "p4-switch.conf" and copied it to "/usr/local/etc/mini-ndn/"
(8) run python createFIBrules.py --fib fib.txt --cmd ndn_commands.partial.txt -c 5
(9) generated json file to fix the thrift error using p4c-bmv2 --json JSON ndn_router.p4
(10) run your experiment by
sudo minindn $MININDN/p4.ndn.basic.conf --experiment=P4_NDN_experiment --p4

[zhangdongdongdong]

Hi,signorello.
I noticed you mentioned: If the experiment was run successfully, you should have the content "Hello world" written in the file /tmp/a/packetPayload.txt
but I can't find the packetPayload.txt in my /tmp/a directory,It does not exist!what's wrong with this?

I try over and over to run the P4_NDN_experiment,But I found the experiment do not create packetPayload.txt file,can you help me to fix this?

[zhangdongdongdong]

Hi,signorello.

I re-do all the steps on a new virtual machine，and this time I got the correct output and see ”hello world” in the packetPayload.txt.
I noticed the difference between this output and the previous output:
This time it's output:
Loading experiment: P4_NDN_experiment
Printing eth0 faceID: 257
but last time it was not.

So I have a question,Where is the code that loads the P4_NDN_experiment? How do I ensure that the experiment is loaded?Just in case I have not successfully loaded the NDN experiment again next time.

looking forward to your reply,thanks!

Terminal Output:
zdd@zdd-VirtualBox:~$ sudo minindn ~/bishe/mini-ndn/p4.ndn.basic.conf --experiment=P4_NDN_experiment --p4
No results folder specified; experiment results will remain in the working directory
Parse of /home/zdd/bishe/mini-ndn/p4.ndn.basic.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b
*** Adding switches:
s1
*** Adding links:
(a, s1) (b, s1)
*** Configuring hosts
a b
Setup time: 0
Reading config file /usr/local/etc/mini-ndn//p4-switch.conf
/home/zdd/bishe/bmv2/targets/simple_switch/simple_switch /home/zdd/bishe/bmv2/targets/simple_switch/runtime_CLI /home/zdd/bishe/NDN.p4/p4src/ndn_router.json l3 9090 True True /home/zdd/bishe/NDN.p4/ndn_commands.partial.txt
P4 setting for host a
Starting NFD on host aa
P4 setting for host b
Starting NFD on host bb
*** Starting controller
c0
*** Starting 1 switches
s1 Starting P4 switch s1
/home/zdd/bishe/bmv2/targets/simple_switch/simple_switch -i 1@s1-eth1 -i 2@s1-eth2 --pcap --thrift-port 9090 --nanolog ipc:///tmp/bm-0-log.ipc --log-console --device-id 0 /home/zdd/bishe/NDN.p4/p4src/ndn_router.json
Disable IPv6 forwarding on the P4Switch
switch has been started
Filling switch tables using /home/zdd/bishe/NDN.p4/ndn_commands.partial.txt
Control utility for runtime P4 table manipulation
RuntimeCmd: Setting default action of count_table
action: storeNumOfComponents
runtime data: 00
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 01
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 02
Entry has been added with handle 1
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 03
Entry has been added with handle 2
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 04
Entry has been added with handle 3
RuntimeCmd: Adding entry to exact match table count_table
match key: VALID- VALID- VALID- VALID- VALID-
action: storeNumOfComponents
runtime data: 05
Entry has been added with handle 4
RuntimeCmd: Setting default action of hashName_table
action: computeStoreTablesIndex
runtime data:
RuntimeCmd: Adding entry to exact match table pit_table
match key: EXACT-05
action: readPitEntry
runtime data:
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table pit_table
match key: EXACT-06
action: cleanPitEntry
runtime data:
Entry has been added with handle 1
RuntimeCmd: Setting default action of fib_table
action: _drop
runtime data:
RuntimeCmd: Adding entry to exact match table updatePit_table
match key: EXACT-01
action: updatePit_entry
runtime data:
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table updatePit_table
match key: EXACT-00
action: _drop
runtime data:
Entry has been added with handle 1
RuntimeCmd: Adding entry to exact match table routeData_table
match key: EXACT-01
action: setOutputIface
runtime data: 00:00
Entry has been added with handle 0
RuntimeCmd: Adding entry to exact match table routeData_table
match key: EXACT-02
action: setOutputIface
runtime data: 00:01
Entry has been added with handle 1
RuntimeCmd: Setting default action of routeData_table
action: _drop
runtime data:
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 0
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 1
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00TERNARY-7e:de &&& ff:ff TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:02
Entry has been added with handle 2
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-02 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 3
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 4
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 5
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-00:00 &&& 00:00 TERNARY-e7:30 &&& ff:ffTERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:03
Entry has been added with handle 6
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-01 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 7
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-02 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 8
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-03 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 9
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-04 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 10
RuntimeCmd: Adding entry to ternary match table fib_table
match key: EXACT-05 TERNARY-9c:dd &&& ff:ff TERNARY-00:00 &&& 00:00TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00 TERNARY-00:00 &&& 00:00
action: set_egr
runtime data: 00:04
Entry has been added with handle 11
RuntimeCmd:

I don't start the NLSR daemon on the host
I don't start the NLSR daemon on the host
Loading experiment: P4_NDN_experiment
Printing eth0 faceID: 257

Starting demo application onb
Starting demo application ona
*** Starting CLI: