You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would need a bit more information to debug this, I notice your capture is started after the log message so any change to TCP state of the control channel will be missing.
But does the switch eventually recover and have the correct flows programmed? dp not up isn't necessarily a problem, faucet is just saying the switch reset its control channel state.
A process send SIGHUP to the faucet controller every 5 seconds
Faucet controller running listening to port 6653
One Open vSwitch switch connected to the faucet controller
ovs-vsctl set-controller br-f1 tcp:127.0.0.1:6653
Faucet config file contains 5 VLANs each with 3 ACL rules
New flows are sent down to OVS
Populate faucet config file with 3000 VLANs each with 3 ACL rules
Faucet log shows DP down and new flows aren't sent down to the OVS switch
PCAP files
The pcap files contains the captured packets starting at the moment the config file has 5 VLANs and the flows for those are sent down to the switch (everything was fine up until this point) and end after faucet log shows DP down faucet.zip
Here is the capture of the traffic between the switch and the controller when "DP not up"
Faucet version: 1.10.11
The text was updated successfully, but these errors were encountered: