Ask Your Question
0

using network-sfc, packet flow is not as per service chain?

asked 2016-06-15 15:00:42 -0500

shabari gravatar image

We tried network-sfc in devstack envi. We have followed the following link: http:// docs.openstack.org/developer/networking-sfc/system_design%20and_workflow.html#create-flow-classifier

But, Service Chaining functionality is not operational. As packet flow is not passing through all the neutron ports as per service chain. But takes only destination port.

Port1-20.20.20.10 ingress vm1

Port2-20.20.20.12 egress vm1

Port3-20.20.20.6 ingress vm2

Port4-20.20.20.11 egress vm2

port5-20.20.20.14 ingree vm3

port6-20.20.20.5 egress vm3

Please find outputs of ovs-vsctl show, ovs-ofctl dump-flows br-int.

root@VSILMASV35:/home/v435621# ovs-vsctl show

90f4ad6a-a7c6-44ee-b8a4-0ab27b61c492

Bridge br-ex
    Port br-ex
        Interface br-ex
            type: internal
    Port "qg-b2cf204c-13"
        Interface "qg-b2cf204c-13"
            type: internal
Bridge br-int
    fail_mode: secure
    Port "tapade9cdf5-3f"
        tag: 4
        Interface "tapade9cdf5-3f"
    Port "tap0c6cc298-2f"
        tag: 4
        Interface "tap0c6cc298-2f"
    Port "tap1f413c85-47"
        tag: 2
        Interface "tap1f413c85-47"
    Port "qr-d1ed0610-5d"
        tag: 1
        Interface "qr-d1ed0610-5d"
            type: internal
    Port "tapf93fe4b7-ba"
        tag: 2
        Interface "tapf93fe4b7-ba"
    Port "tap754279d4-49"
        tag: 2
        Interface "tap754279d4-49"
    Port "tap8d819b28-91"
        tag: 2
        Interface "tap8d819b28-91"
    Port "tap862e757f-7b"
        tag: 2
        Interface "tap862e757f-7b"
    Port "qr-a7ede7fd-da"
        tag: 1
        Interface "qr-a7ede7fd-da"
            type: internal
    Port "tap11b315ec-16"
        tag: 4
        Interface "tap11b315ec-16"
            type: internal
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
    Port "tap3a0a6f12-ba"
        tag: 2
        Interface "tap3a0a6f12-ba"
    Port "tapd1858811-dc"
        tag: 2
        Interface "tapd1858811-dc"
    Port "tap7a99ce60-51"
        tag: 4
        Interface "tap7a99ce60-51"
    Port br-int
        Interface br-int
            type: internal
    Port "tap928f738f-e8"
        tag: 2
        Interface "tap928f738f-e8"
            type: internal
    Port "tape33b5022-3e"
        tag: 1
        Interface "tape33b5022-3e"
            type: internal
    Port "tap1fc2be67-28"
        tag: 4
        Interface "tap1fc2be67-28"
    Port "tapaa7572e2-67"
        tag: 4
        Interface "tapaa7572e2-67"
    Port "tapd4dd33e7-5f"
        tag: 4
        Interface "tapd4dd33e7-5f"
    Port "tap311017fd-46"
        tag: 4
        Interface "tap311017fd-46"
    Port "tap20f9dd0a-ff"
        tag: 4
        Interface "tap20f9dd0a-ff"
    Port "tap1999be5c-33"
        tag: 2
        Interface "tap1999be5c-33"
Bridge br-tun
    fail_mode: secure
    Port br-tun
        Interface br-tun
            type: internal
    Port patch-int
        Interface patch-int
            type: patch
            options: {peer=patch-tun}
ovs_version: "2.5.0"

root@VSILMASV35:/home/v435621#

root@VSILMASV35:/home/v435621# ovs-ofctl dump-flows br-int

NXST_FLOW reply (xid=0x4): cookie=0xa4381c47f0481d62, duration=67152.649s, table=0, n_packets=1424, n_bytes=139552, idle_age=62142, hard_age=65534, priority=30,icmp,in_port=20,nw_src=20.20.20.9,nw_dst=20.20.20.3 actions=drop cookie=0xa4381c47f0481d62, duration=67152.464s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=30,icmp,in_port=17,nw_src=20.20.20.9,nw_dst=20.20.20.3 actions=drop cookie=0xa4381c47f0481d62, duration=67152.276s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=30,icmp,in_port=19,nw_src=20.20.20.9,nw_dst=20.20.20.3 actions=drop cookie=0xa4381c47f0481d62, duration=67152.159s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=30,icmp,in_port=23,nw_src=20.20.20.9,nw_dst=20.20.20.3 actions=NORMAL cookie=0xa4381c47f0481d62, duration=341498.604s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=20,mpls actions=resubmit(,10) cookie=0xa4381c47f0481d62, duration=339713.740s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=10,icmp6,in_port=6,icmp_type=136 actions=resubmit(,24) cookie=0xa4381c47f0481d62, duration=336621.018s, table=0, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=10,icmp6 ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-07-18 20:09:31 -0500

I think your networking-sfc is something wrong.

If you installed using devstack or manual?

If you using manual... Check this link. (https://ask.openstack.org/en/question...)

Did you try delete br-int/br-tun and system reboot?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-06-15 14:30:20 -0500

Seen: 178 times

Last updated: Jul 18 '16