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 & ...
随机推荐
- Android仿微信界面
效果图 原理介绍 1.先绘制一个颜色(例如:粉红) 2.设置Mode=DST_IN 3.绘制我们这个可爱的小机器人 回答我,显示什么,是不是显示交集,交集是什么?交集是我们的小机器人的非透明区域,也就 ...
- Cocos2dx开发游戏移植到Android平台
第一步:安装配置安卓SDK,下载NDK并解压,下载cygwin并安装 第二步:导入platform文件夹下,android文件夹下java文件夹 在eclispe的windows--pereferen ...
- PHP5.3 goto操作符介绍
goto操作符是PHP5.+后新增功能,用来跳转到程序的另一位置:用法很简单:goto后面带上目标位置的标志,在目标位置上用目标名加冒号标记如下: <?php goto a; echo 'aaa ...
- hdu 4832 dp ***
dp1[i][j]表示只走x轴走j步到i位置有多少总走法,dp2同,dp方程就很好写 wa了无数发,发现MOD写在INF上了 #include<cstdio> #include<io ...
- 我与C++的不解情缘
我是一个老实人,我当时报考C++真的全心是为了自己自考的免考,绝不是为了什么二级证,可是,进行到一半的时候,突然获悉,C++自我们这次开始,不作为免考科目了,当时我的心里啊,那个纠结,那个痛啊,随后, ...
- 什么是超级立方体,HyperCube
我试试用我的方式说说如何构造n维空间吧. n维空间在n大于3后,说要画出来,有点难以想象.但从数学的角度看,高维空间这个概念还算比较普通.容易理解的. 与其解释,不如快快开始.我选择用图(Graph) ...
- Java 完美判断中文字符
Java判断一个字符串是否有中文一般情况是利用Unicode编码(CJK统一汉字的编码区间:0x4e00–0x9fbb)的正则来做判断,但是其实这个区间来判断中文不是非常精确,因为有些中文的标点符号比 ...
- 介绍开发Android手持终端PDA盘点APP软件
介绍开发Android手持终端PDA盘点APP软件 软件需要自动识别我导入的TXT格式或者excl格式的盘点表,然后自动生成一个复盘数据,做AB比对,界面上需要显示的有总数量,单品数量,条码,编码,商 ...
- 最短路(Floyd_Warshall) POJ 2240 Arbitrage
题目传送门 /* 最短路:Floyd模板题 只要把+改为*就ok了,热闹后判断d[i][i]是否大于1 文件输入的ONLINE_JUDGE少写了个_,WA了N遍:) */ #include <c ...
- BZOJ4377 : [POI2015]Kurs szybkiego czytania
因为$a$与$n$互质,所以对于$0$到$n-1$里每个$i$,$ai\bmod n$的值互不相同. 设匹配成功的起点为$i$,那么可以得到$3m$段$ai\bmod n$的值不能取的禁区,每段都是连 ...