[openstack-dev] FW: FW: No Relevant flows in br-int after SFC Creation
Mohan Kumar
nmohankumar1011 at gmail.com
Thu Dec 22 06:06:11 UTC 2016
Hi Anirudh,
Please share q-svc.log
Thanks.,
Mohankumar.N
On Thu, Dec 22, 2016 at 10:21 AM, Anirudh Gupta <anirudh2.gupta at aricent.com>
wrote:
> Hi Mohan,
>
>
>
> Thanks a lot for your help and support on IRC yesterday.
>
>
>
> As per your suggestion, we have upgraded our OVS version to 2.5.0,
> downloaded older version of networking-sfc (stable/mitaka).
>
> We have also changed the default driver to *default=['ovs']* in the
> following files :-
>
>
>
> · networking_sfc/services/flowclassifier/common/config.py
>
> · networking_sfc/services/sfc/common/config.py
>
>
>
> We have removed the dummy section from the file
>
>
>
> · /opt/stack/networking-sfc/setup.cfg
>
>
>
> and run the command *sudo python setup.py install* in the networking-sfc.
>
>
>
> But still after creating Flow-Classifier, we could see the driver as *dummy
> *in q-svc logs.
>
>
>
> *2016-12-22 15:29:00.684 ^[[00;32mDEBUG
> networking_sfc.services.flowclassifier.drivers.dummy.dummy
> [^[[01;36mreq-a634ebc4-7f65-4f46-acf0-0a3135c57237 ^[[00;36madmin
> 2ef781adeee54ee38354452b8264ed08^[[00;32m]
> ^[[01;35m^[[00;32mnetworking_sfc.services.flowclassifier.drivers.dummy.dummy.DummyDriver
> method create_flow_classifier called with arguments
> (<networking_sfc.services.flowclassifier.common.context.FlowClassifierContext
> object at 0x7fcc69ec6590>,) {}^[[00m ^[[00;33mfrom (pid=21226) wrapper
> /usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py:47^[[00m*
>
>
>
> Can you please suggest what more steps we need to follow in order to use
> ovs driver in networking-sfc?
>
>
>
> Regards
>
> Anirudh Gupta
>
>
>
>
>
> *From:* Mohan Kumar [mailto:nmohankumar1011 at gmail.com]
> *Sent:* Friday, December 16, 2016 6:53 PM
> *To:* Anirudh Gupta <anirudh2.gupta at aricent.com>
> *Cc:* openstack-dev at lists.openstack.org; Lovelesh Pandya <
> lovelesh.pandya at aricent.com>; Mohit Gupta <mohit2.gupta at aricent.com>
> *Subject:* Re: FW: FW: No Relevant flows in br-int after SFC Creation
>
>
>
> Hi Anirudh,
>
>
>
> Please try out the suggestion as per our IRC chat and post your
> experience
>
>
>
> Thanks.,
>
> Mohankumar.N
>
>
>
>
>
>
>
>
>
> On Thu, Dec 15, 2016 at 3:56 PM, Anirudh Gupta <anirudh2.gupta at aricent.com>
> wrote:
>
> Hi Mohan,
>
>
>
> Yes, we are getting timeout messages in q-agt logs.
>
>
>
> We have suspecting some communication issue between Driver and the Agent.
>
>
>
> Setup Details :-
>
>
>
> *· Openstack Newton - Devstack*
>
> *· Kernel version - 3.19.0-25-generic*
>
> *· ovs version – 2.4.0*
>
>
>
> After creating the Port chain, it was found that no relevant flows were
> added in br-int (attached in the mail).
>
>
>
> On Analysing, it was found in *q-svc logs*, that the driver is asking
> agent to update the flows.
>
>
>
> *2016-12-13 21:59:45.190 2293 DEBUG
> networking_sfc.services.sfc.drivers.ovs.driver
> [req-12ff22b4-e672-4c0a-84f1-ac50286ecfb5 admin -] create assoc port with
> node: {'portpair_id': u'960b7bed-971d-48ed-804c-cfdb1ff7d73b',
> 'pathnode_id': '426067de-40aa-431e-a23e-02587f2ac43e', 'weight': 1}
> _create_portchain_path
> /opt/stack/networking-sfc/networking_sfc/services/sfc/drivers/ovs/driver.py:454*
>
> *2016-12-13 21:59:45.206 2293 DEBUG networking_sfc.db.flowclassifier_db
> [req-12ff22b4-e672-4c0a-84f1-ac50286ecfb5 admin -]
> networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin method
> get_flow_classifier called with arguments (<neutron.context.Context object
> at 0x7f4afaf4e290>, u'598c91d8-581d-4f14-9653-50767bb25d40') {} wrapper
> /usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py:47*
>
> *2016-12-13 21:59:45.424 2293 DEBUG
> networking_sfc.services.sfc.drivers.ovs.rpc
> [req-12ff22b4-e672-4c0a-84f1-ac50286ecfb5 admin -] Ask agent on the
> specific host to update flows ask_agent_to_update_flow_rules
> /opt/stack/networking-sfc/networking_sfc/services/sfc/drivers/ovs/rpc.py:60*
>
>
>
>
>
> But in *q-agt*, there are no flows were added and also there are some
> timeout logs.
>
>
>
> *2016-12-13 22:04:49.513 2486 ERROR neutron.common.rpc
> [req-f9c98709-0a3e-42ea-8437-b821adeff86d - -] Timeout in RPC method
> get_devices_details_list_and_failed_devices. Waiting for 33 seconds before
> next attempt. If the server is not down, consider increasing the
> rpc_response_timeout option as Neutron server(s) may be overloaded and
> unable to respond quickly enough.*
>
>
>
> It seems the request is not reaching the agent over rpc.
>
>
>
> PFA the following :-
>
> · q-agt logs
>
> · q-svc logs
>
> · nova.conf
>
> · Br-int flows
>
> · Dhcp agent
>
> · L3 agent
>
> · Local.conf
>
> · Ml2 conf
>
>
>
> Can you suggest if any configuration needs to be changed to resolve the
> issue?
>
>
>
> Regards
>
> Anirudh
>
>
>
> *From:* Mohan Kumar [mailto:nmohankumar1011 at gmail.com]
> *Sent:* Wednesday, December 14, 2016 10:17 PM
> *To:* Anirudh Gupta <anirudh2.gupta at aricent.com>
> *Cc:* openstack-dev at lists.openstack.org; Lovelesh Pandya <
> lovelesh.pandya at aricent.com>; Mohit Gupta <mohit2.gupta at aricent.com>
> *Subject:* Re: FW: FW: No Relevant flows in br-int after SFC Creation
>
>
>
> Hi Anirudh,
>
>
>
> Yes, SFC flow_rules are not downloaded. Could you check q-agt timeout
> errors? My suggestion is to recheck flow_classifer fields like protocol
> ports. If possible please find me over IRC #openstack-neutron in IST.
>
>
>
> Thanks.,
>
> Mohankumar.N
>
>
>
>
>
> On Wed, Dec 14, 2016 at 5:14 PM, Anirudh Gupta <anirudh2.gupta at aricent.com>
> wrote:
>
> Hi Mohan,
>
>
>
> Request you to further extend your support in order to resolve the issue.
>
>
>
> Regards
>
> Anirudh Gupta
>
>
>
> *From:* Anirudh Gupta
> *Sent:* Tuesday, December 13, 2016 5:25 PM
> *To:* 'nmohankumar1011 at gmail.com' <nmohankumar1011 at gmail.com>
> *Cc:* Mohit Gupta <mohit2.gupta at aricent.com>; Lovelesh Pandya <
> lovelesh.pandya at aricent.com>
> *Subject:* RE: FW: No Relevant flows in br-int after SFC Creation
>
>
>
> Hi Mohan,
>
>
>
> Thanks for your valuable inputs.
>
>
>
> We have deleted the previous port chain and flow classifier.
>
>
>
> As suggested, again created the port chain and flow classifier using vm1
> and vm3.
>
>
>
> · *neutron flow-classifier-create --ethertype IPv4 --description
> "HTTP traffic from 10.0.0.8 to 10.10.10.6" --ethertype IPv4
> --source-ip-prefix 10.10.10.8/32 <http://10.10.10.8/32>
> --destination-ip-prefix 10.10.10.6/32 <http://10.10.10.6/32> --protocol tcp
> --source-port 1000:1000 --destination-port 80:80 FC1
> --logical_source_port 3064d8be-2c14-4c3c-8e51-d1ed38be9cbf*
>
>
>
> · *neutron port-chain-create --port-pair-group PPG1
> --port-pair-group PPG2 --flow-classifier FC1 PC1*
>
>
>
> But still we are facing the issue that no dump-groups are getting created
> and no relevant flows are observed in the br-int.
>
>
>
> I have also captured specific q-agt and q-svc logs of scenarios where only
> the flow classifier and port chain is getting created.
>
>
>
> q-agt.log_specific and q-svc.log_specific corresponds to logs of only
> creation of flow classifier and port chain.
>
> q-agt.log_all and q-svc.log_all contains all the logs.
>
>
>
> I am sharing you new Br-int dump-flows and updated SFC Command List as
> well.
>
>
>
> Request you to extend your support in order to resolve the issue.
>
>
>
> Regards
>
> Anirudh Gupta
>
>
>
> *From:* Mohan Kumar [mailto:nmohankumar1011 at gmail.com
> <nmohankumar1011 at gmail.com>]
> *Sent:* Tuesday, December 13, 2016 4:19 PM
> *To:* Anirudh Gupta <anirudh2.gupta at aricent.com>
> *Cc:* Mohit Gupta <mohit2.gupta at aricent.com>; Lovelesh Pandya <
> lovelesh.pandya at aricent.com>
> *Subject:* Re: FW: No Relevant flows in br-int after SFC Creation
>
>
>
> Hi Anirudh,
>
>
>
> The Flow Classifier fields are not matching with port chain created.
>
>
>
> In SFC commands you've shared , The port_chain formed with vm1 , vm2, and
> vm3 . But flow _classifier fields pointing vm4 ingress as source_ip and
> logical_source_port and vm5 egress_port as the destination.
>
>
>
> Request you to change flow_classifer fields as "vm1" as source and "vm3"
> as the destination and try again.
>
>
>
> *P.S: *Request you always include <openstack-dev at lists.openstack.org> for
> widespread and fast response :)
>
>
>
>
>
> Thanks.,
>
> Mohankumar.N
>
>
>
> On Tue, Dec 13, 2016 at 2:59 PM, Anirudh Gupta <anirudh2.gupta at aricent.com>
> wrote:
>
> Hi Mohan,
>
>
>
> I saw one of your mail chain http://lists.openstack.org/
> pipermail/openstack-dev/2016-August/101755.html , in which Openstack SFC
> was created.
>
>
>
> We are trying to create Networking SFC using Newton Devstack setup using
> Openflow13, but facing some issues.
>
>
>
> After creating the port chain by the command list (attached in the mail),
> we are facing 2 issues :-
>
>
>
> · No relevant flows in br-int (also attached in the mail)
>
> · Empty dump-groups
>
>
>
> Setup Details :-
>
>
>
> · Openstack Newton
>
> · Kernel version - 3.19.0-25-generic
>
> · ovs version – 2.4.0
>
>
>
>
>
> We have configured all the configurational files using the link
> https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining and
> created SFC following the link http://docs.openstack.org/
> newton/networking-guide/config-sfc.html
>
>
>
> The command executed for dump-flows is :-
>
>
>
> *stack at Newton-VM:~$ sudo ovs-ofctl -O openflow13 dump-groups br-int*
>
> *OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):*
>
>
>
> We are currently stuck in the issue that there are no dump-groups and no
> relevant flows in br-int.
>
>
>
> Can you share some pointers to resolve this issue.
>
>
>
> The following files are attached in the mail :-
>
> · local.conf
>
> · /etc/neutron/plugins/ml2/ml2_conf.ini
>
> · /etc/neutron/l3_agent.ini
>
> · /etc/neutron/dhcp_agent.ini
>
> · q-svc
>
> · q-agt
>
> · Br-int Flows
>
> · SFC Command List
>
>
>
>
>
> With Regards
>
>
>
> Anirudh Gupta
>
> Software Engineer
>
> anirudh2.gupta at aricent.com | Extension – 4908
>
> <https://www.aricent.com/>
>
>
>
>
>
>
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161222/7edc922b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 157 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161222/7edc922b/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6374 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161222/7edc922b/attachment.jpg>
More information about the OpenStack-dev
mailing list
