I am in the process of testing a solution for a client and I have run into an interesting issue where a Windows XP laptop connected to the 3560 running
c3560-ipservicesk9-mz.122-55.SE5 displays 192.168.1.2 as its IP within IP device tracking. I have tested with 802.1X & MAB with the same 192.168.1.2 however the device is recieving the correct IP address via DHCP. I am in the process of trying to verify if it is the laptop or Windows XP, but I thought I would post to see if anyone has experienced this before?
A more indepth rundown of what I have running is ISE1.1 with multiple rule matching to provide inacl entries depending on the AD security groups the user has, the switchport is configured with MAB & 802.1X in that order but with 802.1X with the higher priority. Authentication is working correctly as the ISE is providing the inacl entries to the switch but as device tracking has the wrong IP, the acl applied to the port does not allow access for the end device.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...