Nmap scan of port 6633 causes erroneous switch connection message

This is a third of CONTROLLER-530 which I was told by Devin Avery to split.

Steps to recreate:

1. Starting with a fresh Fedora 20 Cloud VM on an OpenStack deployment with an IP I can reach
   sudo yum update -y
   sudo yum install -y java-1.7.0-openjdk unzip wget which
   wget -P /home/fedora 'https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.2-SNAPSHOT-osgipackage.zip'
   unzip distributions-base-0.1.2-SNAPSHOT-osgipackage.zip
   cd /home/fedora/opendaylight
   ./run.sh

1. From another machine, in my case a second fresh Fedora 20 VM on an OpenStack deployment:
   sudo yum update -y
   sudo yum install -y nmap
   nmap -Pn -p 6633 172.18.14.10 # IP of first VM

That nmap scan of port 6633 results in the following erroneous log message on the first VM (running ODL):

osgi> 2014-06-09 15:29:50.317 UTC [ControllerI/O Thread] INFO o.o.c.p.o.core.internal.Controller - Switch:172.18.14.12:56265 is connected to the Controller

osgi>

Here's the nmap output of the scan:

[fedora@dfarrell-opendaylight-bug1124-2 ~]$ nmap -Pn -p 6633 172.18.14.10

Starting Nmap 6.45 ( http://nmap.org ) at 2014-06-09 15:29 UTC
Nmap scan report for 172.18.14.10
Host is up (0.00079s latency).
PORT STATE SERVICE
6633/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds

I filed this under controller/protocol_plugins because the log message comes from controller/opendaylight/protocol_plugins/openflow/src/main/java/org/opendaylight/controller/protocol_plugin/openflow/core/internal/Controller.java:249. If it should be moved, please let me know and forgive my ignorance.