Recently, hundreds of your peers in Spiceworks shared their thoughts on how theyīelieve artificial intelligence will affe. Interactive AI survey: Share and compare your opinions to earn 75 points! SpiceworksĪrtificial technology has been making headlines in recent months, sparking discussion around theįuture impact of the technology.Snap! - Driving a Moon Rover, Lunar Data Centers, Robot Realtors, Brain Zappers Spiceworks Originalsįlashback: March 6, 2012: Google introduces Google Play (Read more HERE.)īonus Flashback: March 6, 2009: NASA Launches Kepler, the first planet seeking space telescope (Read mo.I think that right now the best option for me would be to do as you and others have mentioned: ping the device and start unplugging switches to find it, lol. Yeah, I just found out that the Cisco SG200 Switches we are using does not support CLI, so that sucks. When you finally find the switch that doesn't do that, or the MAC belongs to a switch or other device itself. Most of the switches will show that MAC address on a single port, usually 1 or 24, that is trunked to another switch. OP, sounds like a great excuse to start doing some research and reading on your Cisco CLI? ) All you need to do is log into the switches and display the ARP tables. While tracing it back using the ARP table is a better method if you have managed switches, running a ping and manually unplugging stuff until the ping stops IS a foolproof, if slow, way of doing it! ) Well, it technically WAS the best answer. Please give us the courtesy of letting us know what you found as the problem and fix. You marked one question as Best Answer, but you have not said if you actually fixed the issue. At least that was my understanding of what was said. the OP didn't say if they could or couldn't find 00:1b:54:c7:31:40. If you read the message correctly, I believe the MAC 00:1B:54:C7:31:7F is the one they cant physically find, the one that's showing on the IP Scanner App. This would give you an idea of what kind of Cisco device you’re looking for at least. With such a similar MAC address, if you can physically find the device 00:1b:54:c7:31:40, it stands a good chance that the other device is an identical or very similar model. Even if it’s not a mix up, and I can’t imagine it is. So the device I've been talking about on the IP Scanner apps says it's 00:1B:54:C7:31:7F but I can't find it on any of the MAC Address Tables on the switches.īut on the Mac Address Tables, It shows a similar MAC Address 00:1b:54:c7:31:40, But I cannot find it anywhere on any IP Scanner application.Ĭan you physically find the device 00:1b:54:c7:31:40, disconnect it afterhours, see if the IP Scanner apps 00:1B:54:C7:31:7F disappears. Is it possible that my two IP scanner applications or the switches are getting the MAC Address of the device mixed up? Once you find the cable then you have to find where it goes physically from there.Īlternatively you can run CDP or LLDP on all switches until you find the adjacency for the device in question. Eventually you will trace it to the switch it is plugged into. If it is the port of another switch, login to that switch and run the exact same command as above. ![]() This will give you either the port the device is plugged into or a port of another switch. Next: (replace x's with mac address found above) This will give you the mac address you are looking for to track this device down. This will give you the entry in the arp table which has the IP address to mac address association. x.x.x.x is for the ip address of the device. On whatever device is hosting layer 3 for that specific subnet run the following command. ![]() The below commands are assuming cisco switches. And that Mac must be in your CAM tables on the switches. If the device is reachable on your network, it must have a mac address. I would suggest not tot trusting the scanner app for a second.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |