Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

Sequence of action after controller receives port status from switch

This question from notification point of view and I am interested to know how after port status packet is received from switch series of flows are pushed to switch from controller. What is the trigger point to flow pushes. I am observing some time flows are not pushed after controller receives port status message.

Sequence of action after controller receives port status from switch

This question from notification point of view and I am interested to know how after port status packet is received from switch series of flows are pushed to switch from controller. What is the trigger point to flow pushes. I am observing some time flows are not pushed after controller receives port status message.

PORT_STATUS packet captured on wireshark

Frame 82: 146 bytes on wire (1168 bits), 146 bytes captured (1168 bits)
Encapsulation type: Ethernet (1)
Arrival Time: Aug 24, 2017 15:43:25.859658000 India Standard Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1503569605.859658000 seconds
[Time delta from previous captured frame: 0.001387000 seconds]
[Time delta from previous displayed frame: 0.875157000 seconds]
[Time since reference or first frame: 35.875663000 seconds]
Frame Number: 82
Frame Length: 146 bytes (1168 bits)
Capture Length: 146 bytes (1168 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp:openflow:openflow_v4]
[Coloring Rule Name: TCP]
[Coloring Rule String: tcp]




Ethernet II, Src: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47), Dst: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Destination: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Source: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47)
Type: IPv4 (0x0800)


Internet Protocol Version 4, Src: x, Dst: y
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
Total Length: 132
Identification: 0x2119 (8473)
Flags: 0x02 (Don't Fragment)
Fragment offset: 0
Time to live: 64
Protocol: TCP (6)
Header checksum: 0x4716 [validation disabled]
[Header checksum status: Unverified]
Source: x
Destination: y
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]




Transmission Control Protocol, Src Port: 55666 (55666), Dst Port: openflow (6653), Seq: 65, Ack: 65, Len: 80
Source Port: 55666 (55666)
Destination Port: openflow (6653)
[Stream index: 0]
[TCP Segment Len: 80]
Sequence number: 65    (relative sequence number)
[Next sequence number: 145    (relative sequence number)]
Acknowledgment number: 65    (relative ack number)
Header Length: 32 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 1566
[Calculated window size: 1566]
[Window size scaling factor: -1 (unknown)]
Checksum: 0x3f8a [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0
Options: (12 bytes), No-Operation (NOP), No-Operation (NOP), Timestamps
[SEQ/ACK analysis]
[PDU Size: 80]


OpenFlow 1.3
Version: 1.3 (0x04)
Type: OFPT_PORT_STATUS (12)
Length: 80
Transaction ID: 0
Reason: OFPPR_ADD (0)
Pad: 00000000000000
Port
    Port no: 68
    Pad: 00000000
    Hw addr: 00:00:00_00:00:00 (00:00:00:00:00:00)
    Pad: 0000
    Name: vhucc4a40e5-96
    Config: 0x00000000
    State: 0x00000001
    Current: 0x00000000
    Advertised: 0x00000000
    Supported: 0x00000000
    Peer: 0x00000000
    Curr speed: 0
    Max speed: 0

Sequence of action after controller receives port status from switch

This question from notification point of view and I am interested to know how after port status packet is received from switch series of flows are pushed to switch from controller. What is the trigger point to flow pushes. I am observing some time flows are not pushed after controller receives port status message.

PORT_STATUS packet captured on wireshark

Frame 82: 146 bytes on wire (1168 bits), 146 bytes captured (1168 bits)
Encapsulation type: Ethernet (1)
Arrival Time: Aug 24, 2017 15:43:25.859658000 India Standard Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1503569605.859658000 seconds
[Time delta from previous captured frame: 0.001387000 seconds]
[Time delta from previous displayed frame: 0.875157000 seconds]
[Time since reference or first frame: 35.875663000 seconds]
Frame Number: 82
Frame Length: 146 bytes (1168 bits)
Capture Length: 146 bytes (1168 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp:openflow:openflow_v4]
[Coloring Rule Name: TCP]
[Coloring Rule String: tcp]




Ethernet II, Src: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47), Dst: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Destination: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Source: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47)
Type: IPv4 (0x0800)


Internet Protocol Version 4, Src: x, Dst: y
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
Total Length: 132
Identification: 0x2119 (8473)
Flags: 0x02 (Don't Fragment)
Fragment offset: 0
Time to live: 64
Protocol: TCP (6)
Header checksum: 0x4716 [validation disabled]
[Header checksum status: Unverified]
Source: x
Destination: y
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]




Transmission Control Protocol, Src Port: 55666 (55666), Dst Port: openflow (6653), Seq: 65, Ack: 65, Len: 80
Source Port: 55666 (55666)
Destination Port: openflow (6653)
[Stream index: 0]
[TCP Segment Len: 80]
Sequence number: 65    (relative sequence number)
[Next sequence number: 145    (relative sequence number)]
Acknowledgment number: 65    (relative ack number)
Header Length: 32 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 1566
[Calculated window size: 1566]
[Window size scaling factor: -1 (unknown)]
Checksum: 0x3f8a [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0
Options: (12 bytes), No-Operation (NOP), No-Operation (NOP), Timestamps
[SEQ/ACK analysis]
[PDU Size: 80]


OpenFlow 1.3
Version: 1.3 (0x04)
Type: OFPT_PORT_STATUS (12)
Length: 80
Transaction ID: 0
Reason: OFPPR_ADD (0)
Pad: 00000000000000
Port
    Port no: 68
    Pad: 00000000
    Hw addr: 00:00:00_00:00:00 (00:00:00:00:00:00)
    Pad: 0000
    Name: vhucc4a40e5-96
    Config: 0x00000000
    State: 0x00000001
    Current: 0x00000000
    Advertised: 0x00000000
    Supported: 0x00000000
    Peer: 0x00000000
    Curr speed: 0
    Max speed: 0

Sequence of action after controller receives port status from switch

This question from notification point of view and I am interested to know how after port status packet is received from switch series of flows are pushed to switch from controller. What is the trigger point to flow pushes. I am observing some time flows are not pushed after controller receives port status message.

Issue is observed on a 3 node cluster

PORT_STATUS packet captured on wireshark

Frame 82: 146 bytes on wire (1168 bits), 146 bytes captured (1168 bits)
Encapsulation type: Ethernet (1)
Arrival Time: Aug 24, 2017 15:43:25.859658000 India Standard Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1503569605.859658000 seconds
[Time delta from previous captured frame: 0.001387000 seconds]
[Time delta from previous displayed frame: 0.875157000 seconds]
[Time since reference or first frame: 35.875663000 seconds]
Frame Number: 82
Frame Length: 146 bytes (1168 bits)
Capture Length: 146 bytes (1168 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ethertype:ip:tcp:openflow:openflow_v4]
[Coloring Rule Name: TCP]
[Coloring Rule String: tcp]




Ethernet II, Src: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47), Dst: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Destination: 02:e1:e9:2e:9a:8b (02:e1:e9:2e:9a:8b)
Source: 9a:5c:c3:65:ae:47 (9a:5c:c3:65:ae:47)
Type: IPv4 (0x0800)


Internet Protocol Version 4, Src: x, Dst: y
0100 .... = Version: 4
.... 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0xc0 (DSCP: CS6, ECN: Not-ECT)
Total Length: 132
Identification: 0x2119 (8473)
Flags: 0x02 (Don't Fragment)
Fragment offset: 0
Time to live: 64
Protocol: TCP (6)
Header checksum: 0x4716 [validation disabled]
[Header checksum status: Unverified]
Source: x
Destination: y
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]




Transmission Control Protocol, Src Port: 55666 (55666), Dst Port: openflow (6653), Seq: 65, Ack: 65, Len: 80
Source Port: 55666 (55666)
Destination Port: openflow (6653)
[Stream index: 0]
[TCP Segment Len: 80]
Sequence number: 65    (relative sequence number)
[Next sequence number: 145    (relative sequence number)]
Acknowledgment number: 65    (relative ack number)
Header Length: 32 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 1566
[Calculated window size: 1566]
[Window size scaling factor: -1 (unknown)]
Checksum: 0x3f8a [unverified]
[Checksum Status: Unverified]
Urgent pointer: 0
Options: (12 bytes), No-Operation (NOP), No-Operation (NOP), Timestamps
[SEQ/ACK analysis]
[PDU Size: 80]


OpenFlow 1.3
Version: 1.3 (0x04)
Type: OFPT_PORT_STATUS (12)
Length: 80
Transaction ID: 0
Reason: OFPPR_ADD (0)
Pad: 00000000000000
Port
    Port no: 68
    Pad: 00000000
    Hw addr: 00:00:00_00:00:00 (00:00:00:00:00:00)
    Pad: 0000
    Name: vhucc4a40e5-96
    Config: 0x00000000
    State: 0x00000001
    Current: 0x00000000
    Advertised: 0x00000000
    Supported: 0x00000000
    Peer: 0x00000000
    Curr speed: 0
    Max speed: 0