Hi All,
Small correction in previous mail.
Query 2: Is the hex-string used
(061F00180000000004000000000000000008050000000008) correct for
OFPTR_VACANCY_UP reason for table_status_messages ?
Regards
Shashwat Srivastava
Assistant System Engineer
Tata Consultancy Services
From: Shashwat Srivastava/MUM/TCS
To: d...@openvswitch.com
Cc: "Ben Pfaff" <b...@nicira.com>
Date: 12/11/2014 04:35 PM
Subject: Query while writing test case for Vacancy Events
Hi Team,
We are working on implementation of Vacancy Events as specified in
openflow specs 1.4.
While writing the test cases, in the test case no. 724 (ofproto -
asynchronous message control (OpenFlow 1.5)) we have added our vacancy
test case
check_async 3 for OFPTR_VACANCY_UP and we are using the following
command
# OFPT_TABLE_STATUS, OFPTR_VACANCY_UP
ovs-vsctl set bridge br0 protocols=OpenFlow14,OpenFlow15,OpenFlow13
ovs-ofctl add bridge br0 flow-tables 0=@nam1 -- --id=@nam1 create
flow_table flow_limit=5
ovs-ofctl -O openflow15 add-flow br0
priority=10,importance=10,action=drop
ovs-ofctl -O openflow15 add-flow br0
priority=11,importance=11,action=drop
ovs-ofctl -O openflow15 add-flow br0
priority=12,importance=12,action=drop
ovs-ofctl -O openflow15 mod-table br0 0 vacancy:20..80
if test X"$1" = X"OFPTR_VACANCY_UP"; then shift;
echo >>expout "OFPT_TABLE_STATUS (OF1.5): VACANCY_UP: config :
Vacancy table_id : 0 current vacancy : 60 vacancy up : 80 vacancy
down : 20"
fi
Openflow Protocol 1.5 (06) OFPT_TABLE_STATUS(1F) length(18) xid=0x0(0)
OFPTR_VACANCY_UP(04) pad(0) table_desc_length(08) table_id(5) config(8)
ovs-appctl -t ovs-ofctl ofctl/send 06 1F 00 18 00000000 04 00 0000 0000
00000008 05 00 00000008
check_async 3 OFPTR_VACANCY_UP
Query 1: Will the testcase for table status messages (where vacancy reason
value can be OFPTR_VACANCY_UP or OFPTR_VACANCY_DOWN) be written in
[ofproto - asynchronous message control (OpenFlow 1.5)] block or shall we
make a new block for OpenFlow1.4 async messages for table Status async
messages ?
Query 2: Is the hex-string used
(061F00180000000003000000000000000008000000000000) correct for
OFPTR_VACANCY_UP reason for table_status_messages ?
Query 3: While running the testcase it fails at check_async 2. Why does it
fails in check_async 2 if our changes are only in check_async 3 ?
Also here the monitor.log file contains TABLE_STATUS message along with
PORT_STATUS messages. Whereas it should contain only PORT_STATUS messages.
Can you please help me in understanding this behaviour.
Regards
Shashwat Srivastava
Assistant System Engineer
Tata Consultancy Services
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
