[VTN-2] Computation of logical ports names fail when adding more than once ODL controller to VTN Coordinator Created: 29/Jan/14  Updated: 03/May/18  Due: 31/Jan/14  Resolved: 19/Feb/14

Status: Resolved
Project: vtn
Component/s: ODC Driver
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Venkatrangan Govindarajan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All

External issue ID: 385

 Description   

When more than one ODL Controller is configured to VTN Coordinator, the computation of logical port fails for the second controller. This will result in the user always viewing only the logical ports of the first controller.
Logical ports are used in creating portmaps and vlanmaps.

Workaround: The user can list the switches and ports, and can construct the logical port string by himself/herself and create portmap or vlanmap for the port.

The user will be able to list all switches belonging to all controllers and for every switch can list all ports, then compute the logical port in the below format.The logical port is of the format PP-OF:<switch_id>-<PORT_ID>. This can be used in creation of portmap/vlanmap API.

 Comments   
Comment by Hideyuki Tai [ 19/Feb/14 ]

Kamatchi fixed the problem.
https://git.opendaylight.org/gerrit/#/c/5012/

I've confirmed that it is fixed in my local machine.
Information of my local machine is as follows:

  1. git log -3 --oneline
    a11652c Merge "Add Delay to FT after mininet session termination"
    5d40fd5 Add Delay to FT after mininet session termination
    25ef73d Fix VTN-2 to solve logical port computation in multiple controller scenarios
Generated at Wed Feb 07 20:47:43 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.