HP VAN SDN Controller Software Products manual

Technical white paper HPN SDN Controller Link Discovery

Using the example topology above, we will illustrate a few of the issues that may arise with link discovery. Assume that switches A, B, C OpenFlow instances are configured to connect to the same controller and that each inter-switch physical connection is tagged with the vlans shown. The notation “OF Inst” indicates an OpenFlow instance running on the given switch.

The following will be the discovered topology:

Direct link

Multihop link

Undiscovered link (ERROR)

All of the undiscovered links have switch C as their destination, so we may be tempted to assume that this is a misconfiguration on switch C. Actually, these links would be discovered with configuration changes on either switch C or the other controlled switches (A, B).

•The multi-hop link from Ax to Cy is not discovered because the controller injects an untagged link discovery packet from Ax port 1. The untagged packet is associated with vlan 3 by the uncontrolled switch, so the link discovery packet is never received by switch C.

•The direct links from Bx to Cx and Cy are not discovered because the controller injects an untagged link discovery packet from Bx on port 2. The untagged packet is received by switch C and associated with the untagged vlan on switch C port 2.

–If the untagged vlan on switch C port 2 is vlan 1, only the Bx to Cx link will be discovered.

–If the untagged vlan on switch C port 2 is vlan 2, only the Bx to Cy link will be discovered.

–If the untagged vlan on switch C port 2 is neither vlan 1 or 2, no Bx to Cx/y links will be discovered.

Device-specific recommendations

In general, HP recommends that OpenFlow instance-to-vlan mappings remain consistent throughout the controlled network topology. If an OpenFlow instance contains a set of vlans on one switch, then neighboring switches should also have an OpenFlow instance with the same set of vlans.

ProVision: Virtualization Mode

There are no known issues when using ProVision products in virtualization mode. Since virtualization mode limits each OpenFlow instance to a single vlan, the vlan can be derived from the OpenFlow instance. Any packets which the controller injects into an OpenFlow instance in virtualization mode are tagged correctly by the OpenFlow instance - an 802.1Q header is added, if the egress port is configured to be tagged. No known issues exist under these circumstances.

Comware: PVID in OpenFlow instance

There are no known issues with link discovery (limited testing) when using Comware devices when the port’s pvid is set to an OpenFlow vlan. If any link discovery packets arrive untagged on a port, they will be assigned to the pvid. If the pvid is set to an OpenFlow vlan, then all link discovery packets will be received by the controller from the OpenFlow instance which contains that vlan.

If multiple OpenFlow instances are configured on a single Comware device, then at least one port must be used per OpenFlow instance per neighboring switch. This is required because only one pvid can be assigned per port, and no single vlan can be associated with multiple OpenFlow instances.

VAN SDN Controller Software Products specifications

HP VAN SDN Controller Software Products represent a significant advancement in network management by leveraging software-defined networking (SDN) principles. These products aim to centralize control of network resources, provide enhanced automation, and simplify network management, which can dramatically improve the overall performance and agility of data centers.

One of the main features of HP VAN SDN Controller is its ability to enable an application-centric network environment. By separating the control plane from the data plane, network administrators can gain a holistic view of the entire network. This separation allows for dynamic reconfiguration of network devices and sets the stage for the development of innovative applications that can respond to real-time network conditions.

The controller supports OpenFlow as its primary protocol, ensuring interoperability with a wide range of network devices from different vendors. This compatibility facilitates a heterogeneous network environment, allowing organizations to transition to SDN at their own pace without needing to replace all existing hardware. It also promotes vendor diversity, reducing the risk of vendor lock-in.

HP VAN SDN Controller features robust security capabilities, including support for micro-segmentation, which helps in isolating critical components within the network. This layer of security can safeguard sensitive data and protect against threats, ensuring that only authorized traffic is allowed within designated network segments.

Another key characteristic is the controller's emphasis on automation and orchestration. Through APIs and built-in tools, network policies can be defined and applied consistently across the entire network. This intelligent automation reduces the potential for human error and accelerates the implementation of networking changes, enabling organizations to adapt quickly to evolving business needs.

The HP VAN SDN Controller also incorporates advanced analytics capabilities that provide real-time visibility into network performance. These analytics can help in troubleshooting, forecasting capacity needs, and optimizing resource utilization, contributing to improved operational efficiency and reduced downtime.

Furthermore, the scalable architecture of the HP VAN SDN Controller makes it suitable for various environments, from small enterprises to large-scale data centers. The product supports multi-tenancy, allowing multiple virtual networks to coexist on the same infrastructure, which can be ideal for service providers and organizations operating within cloud environments.

In summary, HP VAN SDN Controller Software Products deliver a powerful suite of features and technologies that enhance network control, security, automation, and scalability, positioning organizations to leverage the full potential of software-defined networking.