aaa port-access mac-based Īllows client moves between the specified ports under MAC authenticated control. Even in my humble opinion it's also clearly a bug, the switch doesn't work as expected, it makes no difference if there are more switches behind a port, a moving MAC should trigger re-authentication or should simply passed on to the new port.įor the procurve series exists a special option for this:Īllowing addresses to move without re-authentication but let me know your thoughts.Īnd thank you for the quick reply. ![]() I have raised a support ticket for this, as I think it's a bug. The mac address continues to be listed as attached to the original port, even though it's been moved. When the re-auth period comes around the switch continues to authenticate the device on the old port it's no longer connected to. It is never authenticated in the new port. ![]() This is necessary because in many locations we're using mini-switches like the NJ5000 to provide additional connections.Įverything works just fine until a device that was plugged into a daisychained switch (be it an NJ5000 or a phone) is moved to another port on the same switch or IRF.Īt this point because the original port doesn't go down, the mac-authentication doesn't detect the device has moved. Using hybrid ports to assign vlans to mac addresses, so we can have multiple devices on different vlans through the same port. I'm experiencing a curious mac-auth issue, which I think is a bug but wondered if I'd missed a command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |