P4factory 运行结果展示 basic_routing 以及 ./run_all_tests 的运行结果
p4factory子目录下的run_all_tests
安装好p4factory之后，打算跑一下样例来测试是否正确。
但是，跑了targets目录内的basic_routing，make又报错了，但之前成功过，我想可能是长时间放置导致一些虚拟接口的问题，于是cd回上级目录，跑下全部的样例，看看是什么结果。
半个小时过去了，终于跑完了，可能是因为有其它进程的原因，导致某些样例没有通过。
**************************************
TESTS PASSED: 10/13
sudo killall -q behavioral-model
sudo killall -q drivers-switchapi
sudo killall -q drivers
sudo killall -q l2_switch_bmv2
sudo killall -q switch_bmv2
sudo killall -q basic_routing_bmv2
sudo killall -q drivers-switchsai
3 TESTS FAILED!
If some tests fail because extra packets are received, you may want to try disabling IPv6 with:
sudo sysctl -w net.ipv6.conf.eth0.disable_ipv6=1
于是在没有其它终端执行命令的情况下又跑了一遍，还是这个结果，于是打算按它提示的试一试。
basic_routing
终端A，执行
./behavior-model
终端B，执行sudo python run_tests.py --test-dir tests/ptf-tests/
A的结果：
Resetting buffer
Resetting buffer
Cleaning all state (resetting all tables)
In ipv4_fib_set_default_action_on_miss
ipv4_fib: setting default action
In ipv4_fib_lpm_set_default_action_on_miss
ipv4_fib_lpm: setting default action
In rewrite_mac_set_default_action_on_miss
rewrite_mac: setting default action
In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 0
**********
entry at index 0:
key:
standard_metadata_ingress_port: 0x00000001 (0 0 0 1),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
**********
In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 1
**********
entry at index 1:
key:
standard_metadata_ingress_port: 0x00000002 (0 0 0 2),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
**********
In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 2
**********
entry at index 2:
key:
standard_metadata_ingress_port: 0x00000003 (0 0 0 3),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
**********
In port_mapping_table_add_with_set_bd
port_mapping: adding entry
empty index: 3
**********
entry at index 3:
key:
standard_metadata_ingress_port: 0x00000004 (0 0 0 4),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
**********
In bd_table_add_with_set_vrf
bd: adding entry
empty index: 0
**********
entry at index 0:
key:
ingress_metadata_bd: 0x0000000a (0 0 0 10),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
**********
In bd_table_add_with_set_vrf
bd: adding entry
empty index: 1
**********
entry at index 1:
key:
ingress_metadata_bd: 0x00000014 (0 0 0 20),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
**********
In ipv4_fib_lpm_table_add_with_fib_hit_nexthop
ipv4_fib_lpm: adding entry
empty index: 0
**********
entry at index 0:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0xc0a80000 (192 168 0 0),
prefix_length:
48
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
**********
In ipv4_fib_lpm_table_add_with_fib_hit_nexthop
ipv4_fib_lpm: adding entry
empty index: 1
**********
entry at index 1:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0x0a000000 (10 0 0 0),
prefix_length:
40
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
**********
In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 0
**********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
**********
In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 0
**********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
**********
In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 1
**********
entry at index 1:
key:
ingress_metadata_nexthop_index: 0x00000002 (0 0 0 2),
action:
set_egress_details
action data:
egress_spec: 0x00000002 (0 0 0 2),
**********
In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 1
**********
entry at index 1:
key:
ingress_metadata_nexthop_index: 0x00000002 (0 0 0 2),
action:
rewrite_src_dst_mac
action data:
smac: 0x010202020202, dmac: 0x000202020202,
**********
In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 2
**********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
**********
In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 2
**********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
**********
In nexthop_table_add_with_set_egress_details
nexthop: adding entry
empty index: 3
**********
entry at index 3:
key:
ingress_metadata_nexthop_index: 0x00000004 (0 0 0 4),
action:
set_egress_details
action data:
egress_spec: 0x00000004 (0 0 0 4),
**********
In rewrite_mac_table_add_with_rewrite_src_dst_mac
rewrite_mac: adding entry
empty index: 3
**********
entry at index 3:
key:
ingress_metadata_nexthop_index: 0x00000004 (0 0 0 4),
action:
rewrite_src_dst_mac
action data:
smac: 0x010404040404, dmac: 0x000404040404,
**********
Packet in on port 2 length 100; first bytes:
00010203 04050006 0708090a 08004500
new packet, len : 100, ingress : 2
rmt proc returns 0
ingress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
all checksums are correct
Applying table port_mapping
Lookup key for port_mapping:
standard_metadata_ingress_port: 0x00000002,
table hit
**********
entry at index 1:
key:
standard_metadata_ingress_port: 0x00000002 (0 0 0 2),
action:
set_bd
action data:
bd: 0x0000000a (0 0 0 10),
**********
action set_bd
action data:
bd: 0x0000000a (0 0 0 10),
executing next table for action
Applying table bd
Lookup key for bd:
ingress_metadata_bd: 0x0000000a,
table hit
**********
entry at index 0:
key:
ingress_metadata_bd: 0x0000000a (0 0 0 10),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
**********
action set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
executing next table for action
Applying table ipv4_fib
Lookup key for ipv4_fib:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0x0a000002,
table miss, applying default action
action on_miss
executing next table for action
Applying table ipv4_fib_lpm
Lookup key for ipv4_fib_lpm:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0x0a000002,
table hit
**********
entry at index 1:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0x0a000000 (10 0 0 0),
prefix_length:
40
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
**********
action fib_hit_nexthop
action data:
nexthop_index: 0x00000003 (0 0 0 3),
executing next table for action
Applying table nexthop
Lookup key for nexthop:
ingress_metadata_nexthop_index: 0x00000003,
table hit
**********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
**********
action set_egress_details
action data:
egress_spec: 0x00000003 (0 0 0 3),
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
total length for outgoing meta: 26
copying metadata
deparsing standard_metadata
deparsing ingress_metadata
queuing system: packet dequeued
egress port set to 3
instance type set to 0
egress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
extracting metadata
extracting all metadata for 0x7f1974000930
Applying table rewrite_mac
Lookup key for rewrite_mac:
ingress_metadata_nexthop_index: 0x00000003,
table hit
**********
entry at index 2:
key:
ingress_metadata_nexthop_index: 0x00000003 (0 0 0 3),
action:
rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
**********
action rewrite_src_dst_mac
action data:
smac: 0x010303030303, dmac: 0x000303030303,
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
outgoing thread: packet dequeued
outgoing thread: sending pkt: Size[100]: Port[3]
Packet in on port 4 length 100; first bytes:
00010203 04050006 0708090a 08004500
new packet, len : 100, ingress : 4
rmt proc returns 0
ingress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
all checksums are correct
Applying table port_mapping
Lookup key for port_mapping:
standard_metadata_ingress_port: 0x00000004,
table hit
**********
entry at index 3:
key:
standard_metadata_ingress_port: 0x00000004 (0 0 0 4),
action:
set_bd
action data:
bd: 0x00000014 (0 0 0 20),
**********
action set_bd
action data:
bd: 0x00000014 (0 0 0 20),
executing next table for action
Applying table bd
Lookup key for bd:
ingress_metadata_bd: 0x00000014,
table hit
**********
entry at index 1:
key:
ingress_metadata_bd: 0x00000014 (0 0 0 20),
action:
set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
**********
action set_vrf
action data:
vrf: 0x0000001e (0 0 0 30),
executing next table for action
Applying table ipv4_fib
Lookup key for ipv4_fib:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0xc0a80102,
table miss, applying default action
action on_miss
executing next table for action
Applying table ipv4_fib_lpm
Lookup key for ipv4_fib_lpm:
ingress_metadata_vrf: 0x0000001e, ipv4_dstAddr: 0xc0a80102,
table hit
**********
entry at index 0:
key:
ingress_metadata_vrf: 0x0000001e (0 0 0 30), ipv4_dstAddr: 0xc0a80000 (192 168 0 0),
prefix_length:
48
action:
fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
**********
action fib_hit_nexthop
action data:
nexthop_index: 0x00000001 (0 0 0 1),
executing next table for action
Applying table nexthop
Lookup key for nexthop:
ingress_metadata_nexthop_index: 0x00000001,
table hit
**********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
**********
action set_egress_details
action data:
egress_spec: 0x00000001 (0 0 0 1),
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
total length for outgoing meta: 26
copying metadata
deparsing standard_metadata
deparsing ingress_metadata
queuing system: packet dequeued
egress port set to 1
instance type set to 0
egress_pipeline: packet dequeued
parsing start
parsing parse_ethernet
parsing parse_ipv4
payload length: 66
extracting metadata
extracting all metadata for 0x7f1970000930
Applying table rewrite_mac
Lookup key for rewrite_mac:
ingress_metadata_nexthop_index: 0x00000001,
table hit
**********
entry at index 0:
key:
ingress_metadata_nexthop_index: 0x00000001 (0 0 0 1),
action:
rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
**********
action rewrite_src_dst_mac
action data:
smac: 0x010101010101, dmac: 0x000101010101,
executing next table for action
total length for outgoing pkt: 100
deparsing ethernet
deparsing ipv4
outgoing thread: packet dequeued
outgoing thread: sending pkt: Size[100]: Port[1]
B的结果：
WARNING: No route found for IPv6 destination :: (no default route?)
routing.TwoBdLpmTest ... ok
----------------------------------------------------------------------
Ran 1 test in 1.829s
OK
2016/10/14
P4factory 运行结果展示 basic_routing 以及 ./run_all_tests 的运行结果的更多相关文章
- C# 获取当前服务器运行程序的根目录，获取当前运行程序物理路径
C# 获取当前服务器运行程序的根目录,获取当前运行程序物理路径 string tmpRootDir = AppDomain.CurrentDomain.BaseDirectory;//获得当前服务器程 ...
- 未能加载文件或程序集“BLL”或它的某一个依赖项。生成此程序集的运行时比当前加载的运行时新，无法加载此程序集。
今天使用VS2012创建项目的时候,考虑到项目中代码的重用性以及清晰简洁性,搭建了一个三层架构,但是在项目运行的时候,总是报错: “未能加载文件或程序集“BLL”或它的某一个依赖项.生成此程序集的运行 ...
- Docker在Linux上运行NetCore系列（一）配置运行DotNetCore控制台
转发请注明此文章作者与路径,请尊重原著,违者必究. 系列文章:https://www.cnblogs.com/alunchen/p/10121379.html 本篇文章操作系统信息 Linux:ubu ...
- Ubuntu上运行Blender，在控制台上查看运行结果
1.首先在控制台打开Blender. 具体操作:找到Blender的安装路径,我的是:/home/lcx/下载/blender-2.78c-linux-glibc219-x86_64 $cd /hom ...
- Singer 学习七 运行&&开发taps、targets (二 targets 运行说明)
接上文: Singer 学习六 运行&&开发taps.targets (一 taps 运行说明) 说明target 需要tap 进行配合运行,所以需要了解tap 的使用 运行targe ...
- Java线程面试题：子线程先运行 2 次，然后主线程运行 4 次，如此反复运行 3 次
package thread; /** * 需求:线程编程:子线程先运行 2 次,然后主线程运行 4 次,如此反复运行 3 次. * @author zhongfg * @date 2015-06-1 ...
- bat 判断 bat 是否是以管理员权限运行，和自动以管理员权限运行
bat 判断 bat 是否是以管理员权限运行,和自动以管理员权限运行 判断 @echo off net.exe session 1>NUL 2>NUL && ( goto ...
- C#.Net集成Bartender条码打印，VS调试运行可以打印，发布到IIS运行打印报错
C#.Net集成Bartender条码打印,VS调试运行可以打印,发布到IIS运行打印报错 问题原因: 问题出现在iis账户权限. 解决方法: iis默认是用network service这个账户去执 ...
- bat代码中判断 bat是否是以管理员权限运行，以及自动以管理员权限运行CMD BAT
· bat 代码中判断bat是否是以管理员权限运行,以及自动以管理员权限运行CMD BAT 一.判断bat是否是以管理员权限运行 @echo off net.exe session >NUL & ...
随机推荐
- ECSHOP去版权与标志
前台部分: 1:去掉头部TITLE部分的ECSHOP演示站 Powered by ecshop 前者在后台商店设置 - 商店标题修改 后者打开includes/lib_main.php $page_t ...
- 用mtrace检查内存泄漏
http://blog.csdn.net/ixidof/article/details/6638066内存泄漏检查方法(for Linux) 如果你更想读原始文档, 请参考glibc info的&qu ...
- javascript reduce map函数方法
retduce: 对数组中的所有元素调用指定的回调函数.该回调函数的返回值为累积结果,并且此返回值在下一次调用该回调函数时作为参数提供. 语法 array1.reduce(callbackfn ...
- Java中Json用法
首先导入json.jar,非常简单看过代码就明白怎么用了 package cn.mylucene; import java.util.HashMap; import java.util.Map; im ...
- 菜鸟学Linux命令:chmod命令和数字文件权限
chmod是一条在Unix系统中用于控制用户对文件的权限的命令(change mode单词前缀的组合)和函数.只有文件所有者和超级用户可以修改文件或目录的权限.可以使用绝对模式,符号模式指定文件的权限 ...
- CI中写原生SQL(封装查询)
封装查询 封装,通过让系统为你组装各个查询语句,能够简化你的查询语法.参加下面的范例: $sql = "SELECT * FROM some_table WHERE id = ? AND s ...
- mac平台下面nodejs环境搭配
方法一(pkg方式:下载链接http://nodejs.org/dist/v0.12.4/node-v0.12.4.pkg): 官网:https://nodejs.org/download/ 例子: ...
- javascript中window.open()与window.location.href的区别
window.open("www.baidu.com"); 只是表示打开这个页面,并不是打开并刷新baidu.com window.location.href="www. ...
- ☆ fragment和fragmentactivity解析 (转)
一.为什么要使用Fragment 1.当我们需要动态的多界面切换的时候,就需要将UI元素和Activity融合成一 个模块.在2.3中我们一般通过各种Activity中进行跳转来实现多界面的跳转和单 ...
- cocos2dx游戏开发——微信打飞机学习笔记（六）——PlayerLayer的搭建
一.创建文件~ PlayerLayer.h PlayerLayer.cpp 一般类名都会和文件名有关系的~(在这里当然是一样) 二.How to do? 1.首先就是放一个飞机~ CC_SYNTHES ...