[CONTROLLER-554] Nmap scan of port 6633 causes erroneous switch connection message Created: 09/Jun/14 Updated: 25/Jul/23 Resolved: 21/Apr/16 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | adsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Daniel Farrell | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 1174 |
| Description |
|
This is a third of Steps to recreate:
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 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. |
| Comments |
| Comment by Carol Sanders [ 04/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL |
| Comment by Robert Varga [ 21/Apr/16 ] |
|
AD-SAL was removed, hence won't fix. |