Skip to content
Snippets Groups Projects
Commit 38b85968 authored by Srinivasan Ramasubramanian's avatar Srinivasan Ramasubramanian
Browse files

The previous fix is not correct. The fix generates a device moved event when...

The previous fix is not correct.  The fix generates a device moved event when the attachment points are not even updated.

Revert "Device moved notification has to be generated when the new attachment point was already in the oldAP list."

This reverts commit 2d6a75c4116790db7d1ddaa53e0d6d873d035815.
parent 0dfabb35
No related branches found
No related tags found
No related merge requests found
......@@ -464,14 +464,11 @@ public class Device implements IDevice {
} else if (oldAPFlag) {
// retain oldAP as is. Put the newAP in oldAPs for flagging
// possible duplicates.
oldAPList = new ArrayList<AttachmentPoint>();
if (oldAPs != null) oldAPList.addAll(oldAPs);
// Add to oldAPList only if it was picked up from the oldAPList
oldAPList.add(newAP);
this.oldAPs = oldAPList;
if (!topology.isInSameBroadcastDomain(oldAP.getSw(), oldAP.getPort(),
newAP.getSw(), newAP.getPort()))
return true; // attachment point changed.
oldAPList = new ArrayList<AttachmentPoint>();
if (oldAPs != null) oldAPList.addAll(oldAPs);
// Add ot oldAPList only if it was picked up from the oldAPList
oldAPList.add(newAP);
this.oldAPs = oldAPList;
}
return false;
}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment