Openflow Errors; Host Location Not Learned By Controller; Switches Constantly Being Disconnected And Reconnected; Unexpected Network Or Service Problems In Hybrid Mode - HP HPE VAN SDN Controller 2.7 Administrator's Manual

Cause
Occurs when the file format or contents is invalid, or when the signed jar verification failed (if
enabled).
Action
Indicates that an application zip file fails validation.

OpenFlow errors

Host location not learned by controller

Symptom
The host is not present in the node database maintained by the controller. The REST/Java API
that gets the node information is missing on that host.
Cause
The ARP/DHCP/IP (if ip.learn=true in pureof mode) packets might not have reached the
controller.
Action
1. Make the host trigger the ARP/DHCP/IP packets.
2. Turn on the OpenFlow trace in the controller.
3. Check that those packets are reaching the controller using the PACKET_IN messages.

Switches constantly being disconnected and reconnected

Symptom
The switches are constantly being disconnected and reconnected.
Cause
The pure OpenFlow loop topology requires packets to be flooded across the network. This can
result in a lot of network traffic and interfere with the switches' ability to send echo packets.
Action
When running a looped topology in pure OpenFlow mode, be aware of how much traffic is being
flooded. Some virtual switch implementations might get overwhelmed by the amount of traffic
being generated.

Unexpected network or service problems in hybrid mode

Symptom
Unexpected network or service problems.
Cause
You changed the hybrid.mode configuration of the controller without restarting and disabling
the controller, then re-enabling each controlled OpenFlow instance in the OpenFlow switches.
Action
Change the hybrid.mode configuration. See the HPE VAN SDN Controller Administrator Guide
for information about changing the hybrid.mode configuration.
162 Troubleshooting