HP VAN SDN Controller Release Notes

are discovered correctly in the HP VAN SDN Controller between only one of the VLAN
instances. The link between the other VLAN instances is not discovered. This issue does not
occur in Virtualized mode.
• Link Discovery displays link across two OpenFlow instances (CR139375)—The Link Discovery
application in the HP VAN SDN Controller shows links between two OpenFlow instances
when the same port is tagged to two different VLANs associated with the two OpenFlow
instances in Comware (5900) devices.
• Group/meter create/update/delete require optional and redundant command attribute
(CR141930)—When using the REST API for creating/updating/deleting a group/meter,
including the JSON request in the command field is required.
• During installation through the Ubuntu software center, the HP VAN SDN Controller Debian
package displays a “Package is of bad quality” error message (CR141745)—HP VAN SDN
Controller installation through the Ubuntu software center is not supported.
• Output of REST API to fetch application with name parameter is inconsistent (CR141736)—The
HP VAN SDN Controller Application Manager REST API for fetching applications currently
fetches all applications. There is no support for a filter based on query parameters.
• Jconsole utility is not available in openjdk-7–jre-headless, which is a dependency before
installing the HP VAN SDN Controller—If you create metrics in the HP VAN SDN Controller,
and then try to open the Jconsole to see the metrics, a message displays saying that Jconsole
cannot be found.
• HP VAN SDN Controller failed to delete clean start memento /tmp/HPN Van Controller.clean,
error message in the log.log file (CR142605) —This is a temporary file that is only created
during a restore or upgrade during normal operation when the OSGi Virgo container is
restarted with the —clean option.
• Zookeeper warning logged during initialization (CR138057)—The HP VAN SDN Controller
2.0 includes ZooKeeper connection logs. Failed connection attempts are normal during
Controller initialization and configuration changes and can be ignored.
• Delete failed error exception is noticed from teaming module in the log.log file
(CR142603)—The HP VAN SDN Controller 2.0 tries to cleanup internal data structures during
Controller initialization and configuration changes and logs error message if data is not found.
This is normal during Controller initialization and configuration changes and can be ignored.
• Backup/Restore fails when manual upload/download of backup files when file owner changes
to anyone other than sdn user (CR138689)—Any manual operation on the VAN SDN
Controller, other than using the REST APIs through curl can change the file attributes from sdn
username to Operator username. The backup/restore fails if you perform a manual
upload/download of files. To avoid this, always perform any manual operation via curl using
the REST APIs.
• Keystone-related SDN user password changes are not restored properly (CR141586)—If the
default sdn password is changed from skyline using keystone and the backup operation is
done, you cannot login with the new password after restore operation. You must still use the
default password (skyline) for login.
Switch software issues affecting HP VAN SDN Controller operations
The following are known issues with switch software affecting HP VAN Controller Release 2.0
operations:
• Flow is not added or retrieved correctly (CR138494)—The VLAN_VID: PRESENT bit is not
set for VLAN ID, which indicates an incorrectly formed VLAN_VID match field from a Match
structure in a MultipartReply / FlowStats.element.
• Unable to modify vlan_vid in table 101 (CR140524)—A switch error occurs if you push Flow
Mod with the vlan_vid value as part of set-fields.
Issues and suggested actions 5