HP VAN SDN Controller Administrator Guide v3

• Builds an ARP cache with MAC-IP translations of end hosts.
• Maintains ARPs on a per-VID basis.
• Provides the edge port details for end hosts.
Example ARP table data:
VidMACIP Address
10000:af:cd:12:10:0110.250.100.1
11000:af:cd:12:10:2010.250.100.2
12000:af:cd:12:10:0210.250.100.3
The Node Manager uses the services of the Topology Manager application.
Determines and verifies the path taken by a specific packet from a source
host to destination host.
Path Diagnostics
• Evaluates flows configured across the switches in the control domain
for diagnosis.
• Creates ‘Observation posts’ on every switch in the path that the packet
would take.
• Tallys packet_ins from the observation posts to figure out where a path
is broken.
• Lists neighbors for any given device.
Builds information about links between network elements in the controller
domain. Provides information about the linkages between network elements
Link Manager
and serves as a base for other applications such as topology, etc. This
application maintains a table of source and destination devices and ports,
and transmits discovery packets to ports on attached datapaths.
Operation includes:
• Learning and maintaining all inter-switch links in the control domain.
• Providing data used by the controller topology module to construct
end-to-end paths.
• Deciphering port state changes.
• Generates link events to notify interested listeners.
• Identifies "multi-hop" links between disconnected segments of the control
domain.
• Providing information used by applications to reconfigure flows when
a link goes down.
NOTE: The controller injects only BDDP packets for discovery. No LLDP
packets are sent.
To avoid sending discovery packets on certain ports such as an edge port,
LinkManager maintains a special list of ports identified as "Suppressed
LLDP Ports". Adding ports to the suppressed LLDP list can be done using
the REST API.
Link Service sends BDDP packets with LLDP payloads containing a TLV with
an associated link controller ID in one of the optional LLDP TLVs. This
enables Link Service to differentiate the BDDP messages it has generated.
As it is possible for non-OpenFlow devices to be present between
OpenFlow switches, Link Service also sends out BDDP messages to discover
"multi-hop links", which refer to a link between two OpenFlow switches
on a path through one or more non-OpenFlow devices.
Path Daemon is a "proof of concept" network service application built on
top of the SDN controller. Path Daemon is responsible for pushing
Path Daemon
end-to-end flows for all ARP and IPv4 flow misses that arrive at the
controller. By default, Path Daemon is responsible for Layer-2 forwarding
2.3 Application Manager 19