HP VAN SDN Controller Administrator Guide v3

9.5 Application management error conditions
• If the Application Management framework is able to detect a failure to start an application
in the OSGi runtime environment, the application is automatically moved to the DISABLED
state.
◦ Correct the OSGi runtime conditions.
◦ Enable the application.
• •If an unexpected error condition occurs when manipulating an application (file I/O exception,
missing files, etc) the application will be left in a transitive state.
◦ An application can only be uninstalled when it is trapped in a transitive state.
◦ Examine the log files to determine the source of error and correct.
◦ Uninstall the application then upload and install the application again.
• If the Application Framework is able to detect a failure to start an upgraded version of an
application.
◦ The upgrade version of the application is removed from the SDN server.
◦ An attempt is made to restart the previous version of the application (if it was active).
9.6 Path Diagnostic application via REST command line API
This section describes a method tor troubleshooting switch connectivity issues in OpenFlow switch
environments. This includes two components:
• A packet generator to send test packets of supported protocols via the controller from one end
node to another across an OpenFlow domain.
• A path analyzer providing generated test packet information to help determine which path
the test packets take, and helps in identifying the point of failure; that is, the switch that is not
forwarding the traffic as expected on the path.
• The procedures in this section can be done using Use a REST-based tool such as RSdoc.
9.6.1 Symptoms
Unable to reach a specific end host for a particular type of service; that is, the end hosts cannot
communicate with each other using a particular traffic flow. For example, a user is unable use the
FTP services hosted by particular server.
9.6.2 Troubleshooting steps
9.6.2.1 Packet Generator Process
1. Collect the source and destination end host configuration details.
2. Register a packet that will be injected into the network for tracing the path.
3. Set an observation post on the switch where the destined end host is connected.
4. Inject the registered packet onto the network.
5. Query the observation post in step 3.
6. If the observation post has not received the registered packet, set an observation post on the
switch that is next-hop from the source switch.
7. Inject the registered packet into the network.
8. Query the observation post in step 3.
9. Repeat steps 3 – 8 to determine the switch data path ID where the packet is being dropped.
9.5 Application management error conditions 103