HP 2920 can't ping host to switch(openflow)

[wuc623123]

Hi all,

Problem is: switch can connect to controller(opendaylight) and it also appears on the Topology include host mac, ip

,but host ping switch not arrival.

Firmware: WB.16.01.0004

How can i setting the default gateway and host setting network config in win7?

i connect port 3 to controller and port 5 to host.

There is my config:

HP-2920-24G-PoEP(config)#show run

hostname "HP-2920-24G-PoEP"

module 1 type j9727a

ip default-gateway 192.168.6.254

ip route 0.0.0.0 0.0.0.0 192.168.6.254

ip routing

snmp-server community "public" unrestricted

openflow

controller-id 1 ip 192.168.6.189 controller-interface vlan 1

instance "control"

listen-port

member vlan 2

controller-id 1

enable

exit

enable

exit

oobm

ip address dhcp-bootp

exit

vlan 1

name "DEFAULT_VLAN"

no untagged 5-10

untagged 1-4,11-24

ip address 192.168.6.162 255.255.255.0

exit

vlan 2

name "openflow-ports"

untagged 5-10

ip address 192.168.3.1 255.255.255.0

exit

HP-2920-24G-PoEP(config)# show openflow instance control

Configured OF Version : 1.0

Negotiated OF Version : 1.0

Instance Name : control

Data-path Description : control

Administrator Status : Enabled

Member List : VLAN 2

Pipeline Model : Standard Match

Listen Port : 6633

Operational Status : Up

Operational Status Reason : NA

Datapath ID : 00029457a5182680

Mode : Active

Flow Location : Hardware and Software

No. of Hardware Flows : 1

No. of Software Flows : 7

Hardware Rate Limit : 0 kbps

Software Rate Limit : 100 pps

Conn. Interrupt Mode : Fail-Secure

Maximum Backoff Interval : 60 seconds

Probe Interval : 10 seconds

Hardware Table Miss Count : 193348

No. of Software Flow Tables : NA

Egress Only Ports : None

Table Model : Single Table

Source MAC Group Table : Disabled

Controller Id Connection Status Connection State Secure Role

------------- ----------------- ---------------- ------ ------

1 Connected Active No Equal

[ShaunWackerly]

My presumption is that the switch IP on the data-plane (192.168.3.1) is not known to be associated with the switch by the controller. The controller is only aware of the switch's control-plane IP (192.168.6.162). As such, the controller is likely paving flows across the switch as if 192.168.3.1 is a HOST connected to the switch, rather than an IP on the switch itself. This is a problem that's typical in an OpenFlow-only environment. 

Could you provide the output of "show openflow instance control flows"? That will confirm whether the OpenDaylight controller is treating the switch IP (192.168.3.1) as if it is a connected host. Look for any flows matching 192.168.3.1 as the destination IP.

To resolve this, you could also try using the HPE VAN SDN Controller with hybrid.mode=true, so that the controller will operate in OpenFlow-hybrid mode. In that mode, end-hosts should be able to ping switches or any other hosts on the network, but the controller will still provide visibility into the network state and allow OpenFlow to override the forwarding decision of the switches.

 PS: I also wouldn't expect the host you're sending pings from to be able to ping outside the local subnet.

[wuc623123]

And i change the switch to openflow 1.3 then hosts is disappear ,but switch icon and mininet is work fine.

There is output:

HP-2920-24G-PoEP(config)# show openflow instance control flows

OpenFlow Flow Table

Flow 1
Match
Incoming Port : Any Ethernet Type : Any
Source MAC : Any Destination MAC : Any
VLAN ID : Any VLAN priority : Any
Source Protocol Address : Any
Target Protocol Address : Any
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Attributes
Priority : 0 Duration : 242131 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : NA
Flow Table ID : 0 Controller ID : NA
Activity Count: NA Cookie : 0x0
Hardware Index : NA
Instructions
Goto Table ID : 100

Flow 2
Match
Incoming Port : Any Ethernet Type : Any
Source MAC : Any Destination MAC : Any
VLAN ID : Any VLAN priority : Any
Source Protocol Address : Any
Target Protocol Address : Any
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Attributes
Priority : 0 Duration : 242131 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : NA Packet Count : 1417
Flow Table ID : 100 Controller ID : NA
Activity Count: NA Cookie : 0x0
Hardware Index : NA
Instructions
Drop

Flow 3
Match
Incoming Port : Any Ethernet Type : Any
Source MAC : Any Destination MAC : Any
VLAN ID : Any VLAN priority : Any
Source Protocol Address : Any
Target Protocol Address : Any
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Attributes
Priority : 0 Duration : 242131 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : 0
Flow Table ID : 200 Controller ID : NA
Activity Count: NA Cookie : 0x0
Hardware Index : NA
Instructions
Drop

[ShaunWackerly]

Hmm, based on these initial flowmods that were presumably pushed by the OpenDaylight controller, I'm not sure how the controller would learn host locations or forward traffic. Essentially these flowmods say:

Table 0: all packets goto 100
Table 100: all packets DROP
Table 200: all packets DROP

No packets will be forwarded to the controller, so I'm not sure how it would ever learn about host traffic.

I'm not familiar with the flow initialization or path paving methodology in the OpenDaylight controller, so perhaps someone familiar with the OpenDaylight controller could chime in? If you're open to using the HPE VAN SDN controller, I could help you get that set up and working, because that's the platform I am familiar with.

[wuc623123]

Then i change openflow back to 1.0.

What causes the client not to connect the switch?
How to add the flow table?
What is the flow table content?

There is flows command output:

HP-2920-24G-PoEP(config)# show openflow instance control flows

OpenFlow Flow Table

Flow 1
Match
Incoming Port : Any Ethernet Type : ARP
Source MAC : Any Destination MAC : Any
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source Protocol Address : Any
Target Protocol Address : Any
ARP Opcode : Any IP ToS Bits : Any
Source Port : Any Destination Port : Any
Attributes
Priority : 1 Duration : 673 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 780 Packet Count : 13
Controller ID : 1 Cookie : 0x2b00000000000000
Flow Location : Software
Hardware Index: NA
Reason Code : 10
Reason Description : The action and output port in the rule is invalid or not
supported
Actions
Controller Port
Normal

Flow 2
Match
Incoming Port : Any Ethernet Type : 0x88cc
Source MAC : Any Destination MAC : Any
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : Any
Destination IP Address : Any
IP Protocol : Any IP ToS Bits : Any
Source Port : Any Destination Port : Any
Attributes
Priority : 100 Duration : 673 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : 0
Controller ID : 1 Cookie : 0x2b00000000000000
Flow Location : Hardware
Hardware Index: 0
Reason Code : 12
Reason Description : Rule is in hardware.
Actions
Controller Port

[ShaunWackerly]

In OpenFlow 1.0, there are no table IDs so that's why you don't see a table ID listed in these flows.

Also, it is important to note that the default behavior of a switch with OF 1.0 is to steal traffic to the controller (if not matched in the OF pipeline). The default behavior of a switch with OF 1.3 is to drop traffic (if not matched in the OF pipeline). Are your flows accounting for this change of behavior?

[ShaunWackerly]

I discussed this issue with a colleague. He said that you'll need to install the "l2switch" project from ODL in order to get l2 switching. You can see installed features using the "features:list" command in the karaf CLI. If it isn't installed, you'll need to use "feature:install odl-l2switch-all".

At this point, I won't be much more help, so hopefully someone else can provide advice if they have ODL experience.

[wuc623123]

The controller has already been installed odl-l2switch-all, then it cant see host in topology used openflow 1.3, but openflow 1.0 is work,but the two of them cant be ping.

so ,what moduals are missing?

[wuc623123 · Accepted solution]

I change the host ip config to

10.1.1.20

255.0.0.0

GW:10.1.1.2

and it will ping to switch but can't ping to controller.

i post a new question after change the host ip config.

Host can't ping to Controller (HP 2920).