[P4-dev] l2_switch x simple_switch (bmv2)

Regis Martins regisftm at gmail.com
Tue May 9 20:15:39 EDT 2017


Hi all!

I was trying to run the l2_switch.p4 in the simple_switch (switch) target
and it seems that it get stacked in tha mac_learn action...

type: PACKET_IN, switch_id: 0, cxt_id: 0, sig: 12187842339622128657, id:
21, copy_id: 0, port_in: 1
type: PARSER_START, switch_id: 0, cxt_id: 0, sig: 12187842339622128657, id:
21, copy_id: 0, parser_id: 0 (parser)
type: PARSER_EXTRACT, switch_id: 0, cxt_id: 0, sig: 12187842339622128657,
id: 21, copy_id: 0, header_id: 1 (ethernet)
type: PARSER_DONE, switch_id: 0, cxt_id: 0, sig: 12187842339622128657, id:
21, copy_id: 0, parser_id: 0 (parser)
type: PIPELINE_START, switch_id: 0, cxt_id: 0, sig: 12187842339622128657,
id: 21, copy_id: 0, pipeline_id: 0 (ingress)
type: TABLE_MISS, switch_id: 0, cxt_id: 0, sig: 12187842339622128657, id:
21, copy_id: 0, table_id: 0 (smac)
type: ACTION_EXECUTE, switch_id: 0, cxt_id: 0, sig: 12187842339622128657,
id: 21, copy_id: 0, action_id: 2 (mac_learn)
*>>> it stops here <<<*


In the other hand, I tried to run some counters in the l2_switch target...
and it could not start.

/home/ubuntu/bmv2/targets/l2_switch/l2_switch -i 1 at s1-eth1 -i 2 at s1-eth2
--pcap --thrift-port 22222 --nanolog ipc:///tmp/bm-0-log.ipc --device-id 0
task4.json
*P4 switch s1 did not start correctly.*


Does anyone know what are the differences among bmv2 targets
(simple_router, simple_switch, l2_switch, etc...)?

It seems that simple_switch is the more "complete" as switch.p4 runs on
it... (I guess)

Any information helps.

Thank you in advanced.

Regards,


*Regis Martins*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170509/4b80c430/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: task4.p4
Type: application/octet-stream
Size: 2129 bytes
Desc: not available
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170509/4b80c430/attachment.p4>


More information about the P4-dev mailing list