Simple Chain not Forwarding to SF

Asked by John Studarus

Trying out my first service chain to a SF (tcpdump running in a VM) to monitor traffic between a web-client and web-server but can not see any traffic in the SF. Am I setting up the chain incorrectly? Running Octa (RDO install via Packstack).

I believe that tcpdump should see the traffic being sent through the VM when the chain is active.

web-client (neutron-port: web-client 192.168.1.108)
web-server (neutron-port: web-server 192.168.1.104)

Running curl command from the web-client to the web-server (which returns data OK).

netmon
  neutron ports: netmon1-in (eth1 .102) and netmon1-out (eth2 .107)

tcpdump command that isn't seeing the curl traffic. However, it does see other network traffic (i.e. broadcasts)
[root@netmon1 ~]# tcpdump -i eth1

neutron flow-classifier-create \
  --description "HTTP traffic from web-client .108 to web-server .104" \
  --ethertype IPv4 \
  --source-ip-prefix 192.168.1.108/32 \
  --destination-ip-prefix 192.168.1.104/32 \
  --protocol tcp \
  --logical-source-port web-client \
  --logical-destination-port web-server \
  --source-port 0:65535 \
  --destination-port 0:65535 FC1

neutron port-pair-create \
  --description "netmon1 port pair" \
  --ingress netmon1-in \
  --egress netmon1-out netmon1-pp

neutron port-pair-group-create \
  --port-pair netmon1-pp netmon1-ppg

neutron port-chain-create \
  --port-pair-group netmon1-ppg \
  --flow-classifier FC1 PC1

Question information

Language:
English Edit question
Status:
Expired
For:
networking-sfc Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.