[P4-dev] Nanolog in Mininet

David Hancock dhancock at cs.utah.edu
Wed Oct 25 15:14:26 EDT 2017

I should add, after updating via git pull, I followed the instructions 
to build the code.  At one point I did disable logging and used 
--without-nanomsg.  Then, needing nanomsg again, I followed the build 
instructions again, including sudo ldconfig.

On 10/25/2017 01:07 PM, David Hancock wrote:
> When I run my mininet simulation that includes bmv2, the switch is 
> started with --nanolog, yet nanomsg_client returns:
>      The event logger is not enabled on the switch, run with 
> '--nanolog <ip addr>
> Relevent mininet output:
>      s1 Starting P4 switch s1.
>      <path>/bmv2/targets/simple_switch/simple_switch -i 1 at s1-eth1 -i 
> 2 at s1-eth2 -i 3 at s1-eth3 --thrift-port 22222 --nanolog 
> ipc:///tmp/bm-0-log.ipc --device-id 0 <json path>
>      P4 switch s1 has been started.
> From the bmv2/tools directory:
>      ./nanomsg_client.py --thrift-port 22222
>      The event logger is not enabled on the switch, run with 
> '--nanolog <ip addr>'
> I had not been having any problems with this until I updated bmv2. I'm 
> on commit ae84c2f6d5bc3dd6873a62e351f26c39038804da.
> Any ideas what I'm doing wrong?
> Thanks,
> David
> _______________________________________________
> P4-dev mailing list
> P4-dev at lists.p4.org
> http://lists.p4.org/mailman/listinfo/p4-dev_lists.p4.org

More information about the P4-dev mailing list