- Apr 11, 2012
-
-
Kanzhe Jiang authored
This reverts commit 51ca40a3. Conflicts: src/main/java/net/floodlightcontroller/devicemanager/internal/DeviceManagerImpl.java
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
- Apr 10, 2012
-
-
Kanzhe Jiang authored
-
- Apr 09, 2012
-
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
- Apr 05, 2012
-
-
Srinivasan Ramasubramanian authored
Add 5 seconds for attachment point change from one broadcast domain to another. When the attachment points flap quickly, the controller should avoid learing the attachment point but should continue processing the packet.
-
Srinivasan Ramasubramanian authored
-
Srinivasan Ramasubramanian authored
Device manager will have a 5-second time gap to change an attachment point for a host from one broadcast domain to another.
-
- Apr 03, 2012
-
-
Shudong Zhou authored
-
Kanzhe Jiang authored
-
- Apr 01, 2012
-
-
Srinivasan Ramasubramanian authored
Fix a bug for checking BDDP packet if the packet is not unicast for it to continue down the processing chain.
-
Srinivasan Ramasubramanian authored
If the incoming node port is blocked, allow only unicast and BDDP packets to continue down the processing chain.
-
- Mar 31, 2012
-
-
Srinivasan Ramasubramanian authored
When the device manager gets cleaned up (or when during topologyChanged), it should consider the time difference between switching from broadcast to non-broadcast attachment points (as they might be previously on two different switches).
-
Alex Reimers authored
-
Alex Reimers authored
Added a DeviceManager REST API. You can use this to see what devices the controller has learned along with their IPs and attachment points. Conflicts: src/main/java/net/floodlightcontroller/devicemanager/internal/DeviceManagerImpl.java
-
- Mar 29, 2012
-
-
Srinivasan Ramasubramanian authored
Device manager should implement ITopologyListener to clear out attachment points when topology changes.
-
Srinivasan Ramasubramanian authored
(1) Device manager will drop packets (as the first step) if the topology indicates the packet-in port is not allowed for incoming transmissions. (2) Remove a log message from LinkDiscoveryManager. (3) Topology provides a service called isAllowed() that indicates if the port is enabled for incoming and outgoing traffic. (4) Tests are modified accordingly.
-
- Mar 28, 2012
-
-
Kanzhe Jiang authored
-
- Mar 27, 2012
-
-
Rob Adams authored
Change device manager to not allow attachment point flapping (there was a bug in the implementation before). Also, remove some crappy info log from ForwardingBase.
-
- Mar 26, 2012
-
-
Alex Reimers authored
Added a DeviceManager REST API. You can use this to see what devices the controller has learned along with their IPs and attachment points.
-
Kanzhe Jiang authored
-
- Mar 24, 2012
-
-
Kanzhe Jiang authored
-
- Mar 23, 2012
-
-
Gregor Maier authored
-
Gregor Maier authored
Attachment point move suppresion when moving from non-broadcast domain port to broadcast domain port wasn't working. Fixed.
-
Srinivasan Ramasubramanian authored
Increase the timeout for switching attachment point from non broadcast domain ports to broadcast domain ports to 5 minutes (from 5 seconds).
-
- Mar 22, 2012
-
-
Srinivasan Ramasubramanian authored
If the attachment point of device moves too fast from a non-broadcast domain switch port to a broadcast domain switch port, ignore learning and stop processing the packets.
-
- Mar 21, 2012
-
-
Alex Reimers authored
-
- Mar 16, 2012
-
-
Alex Reimers authored
-
Srinivasan Ramasubramanian authored
Device manager will learn new attachment points only if the switch ports do not belong to the same broadcast domain.
-
- Mar 15, 2012
-
-
Kanzhe Jiang authored
-
- Mar 14, 2012
-
-
Kanzhe Jiang authored
-
Kanzhe Jiang authored
-
- Mar 13, 2012
-
-
Kanzhe Jiang authored
-
Srinivasan Ramasubramanian authored
-
- Mar 05, 2012
-
-
Srinivasan Ramasubramanian authored
-
- Mar 03, 2012
-
-
Srinivasan Ramasubramanian authored
-