search

faucetsdn / daq

DEPRECATED -- DAQ (Device Automated Qualification) framework in no longer in use, supported, or maintained. It is here for archival purposes only.
Apache License 2.0
40 stars 32 forks source link

Non openflow mode - port numbers and switch module #945

Open noursaidi opened 2 years ago

noursaidi commented 2 years ago

I have encountered an issue with the port numbers and the switch/DHCP modules in the non openflow mode.

The TARGET_PORT parameter seems to be set to true rather than a port number within the switch test module, so the module fails:

Exception in thread "main" java.lang.NumberFormatException: For input string: "true"    
at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)  
at java.base/java.lang.Integer.parseInt(Integer.java:652)   
at java.base/java.lang.Integer.parseInt(Integer.java:770)   
at switchtest.Main.main(Main.java:26)

Looking through daq logs, it seems there is no awareness of the physical port number in DAQ. I see the following in the logs:

Setting port set 1 to vlan 104
...
Setting port set 2 to vlan 103
...
Setting port set 3 to vlan 102

These are based on order of connection/identification, e.g.  the first device connected (to port 4 on the switch) is set to 'port set 1', the second to 'port set 2', so on. Though these numbers dont seem make it's way to test modules.

I'd sequentially setup my VLAN ID's, could this be made a requirement and used to derive the physical port number on the switch?