<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Identify Layer 2 devices in a Network in Switching</title>
    <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118425#M242554</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joseph,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the great piece of information !&lt;/P&gt;&lt;P&gt;Additionally I was thinking of doing a MAC address lookup of the MAC address ( from ARP cache of the machine) corresponding to "suspected" switch IP got from active probing. That would provide some additional information as well right ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Anup&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Dec 2012 09:21:21 GMT</pubDate>
    <dc:creator>Anup Sasikumar</dc:creator>
    <dc:date>2012-12-31T09:21:21Z</dc:date>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118421#M242550</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to identify Layer 2 devices in a network without any third party tools ?&lt;/P&gt;&lt;P&gt;Lets say if I am checking out a network for the first time and I login to one of the PCs , I can get information on the Layer 3 gateway device from the default gateway configuration&amp;nbsp; But , Will I be able to identify Layer 2 devices present in the network without the help of any third party tools ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anup&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2019 18:49:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118421#M242550</guid>
      <dc:creator>Anup Sasikumar</dc:creator>
      <dc:date>2019-03-07T18:49:35Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118422#M242551</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anup,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sadly, detecting Layer2 devices in a network from a position of an end host is almost an impossible task. Contrary to traceroute that exploits the ability to force indivdual routers into revealing their identity, there is no such standardized thing for Layer2 environments. Switches are absolutely transparent to transit traffic. They do not modify frames as they pass through them (save for trunking). Even if they drop frames (note that dropping is a relatively rare occasion), there is no signalling to tell the source station that the frame was discarded. So no matter what kind of user traffic you send, there is no way to persuade the switches to generate a frame on their own and send it back to you in response, or to record their identity somewhere into a frame.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could try sniffing the Layer2 assistive protocols like CDP, LLDP, LOOP, STP, VTP, PAgP/LACP, UDLD and similar to learn about your nearest Layer2 device and perhaps about some other devices in the topology, too. However, none of these protocols will allow you to discover the entire Layer2 topology simply by observing the traffic from a single spot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am afraid that the task of discovering the Layer2 devices in a network is practically impossible without focusing on the Layer2 assistive protocols. For sure, a cheap non-manageable switch for a couple of bucks can not be detected at all, as it is totally transparent and does not ever originate any frames itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Dec 2012 13:59:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118422#M242551</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2012-12-29T13:59:06Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118423#M242552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently I was involved in a remote infrastructure analysis task wherein I had to get maximum information about a remote infrastructure. We had access only to a Server at the location. I was just curious if we could get some information regarding Layer 2 network devices present in the network. Now,but sadly I think it is not possible. Thank you so much for your response , Peter. It was very helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anup&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Dec 2012 05:09:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118423#M242552</guid>
      <dc:creator>Anup Sasikumar</dc:creator>
      <dc:date>2012-12-30T05:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118424#M242553</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Disclaimer&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;STRONG&gt;&lt;EM&gt;Liability Disclaimer&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Posting&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As Peter noted, it's normally impossible to detect unmanaged switches as they don't have a "presence" on the network as themselves.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For managed switches, as Peter also described, they often generate "special" L2 control frames, that if "sniffed" would reveal their presence, and depending on the type of control frame, might reveal information about the switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However there's another method that often will reveal managed switches, although it is not 100% reliable.&amp;nbsp; This would be active probing address scans against different ports. A managed switch will often respond on its managed address to pings, SNMP, telnet and/or http.&amp;nbsp; How the switch responds, might provide additional clues to what device it is.&amp;nbsp; What address it responds on, also often provides clues that it's a switch (i.e. low or high series of addresses within a subnet, or all similar responses in the same [management] subnet).&amp;nbsp; Basically this is the same kind of technique used by those looking to break into a network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are some common reasons why active probling won't help include: the managed switch is configured to act like a non-managed switch (this is unusual), the managed switch has been properly secured (not as common as it should be), or the managed switch is mis-configured for remote access (not too common).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Dec 2012 13:06:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118424#M242553</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2012-12-30T13:06:28Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118425#M242554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joseph,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the great piece of information !&lt;/P&gt;&lt;P&gt;Additionally I was thinking of doing a MAC address lookup of the MAC address ( from ARP cache of the machine) corresponding to "suspected" switch IP got from active probing. That would provide some additional information as well right ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Anup&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 09:21:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118425#M242554</guid>
      <dc:creator>Anup Sasikumar</dc:creator>
      <dc:date>2012-12-31T09:21:21Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118426#M242555</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the only info you would get from MAC address is from the OUI portion which will tell you the manufacturer but that's all you'll get.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget to rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 09:39:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118426#M242555</guid>
      <dc:creator>cadet alain</dc:creator>
      <dc:date>2012-12-31T09:39:13Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118427#M242556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alain,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes , But lets say if I lookup and I get the manufacturer as Cisco , the chances are high that it will be a network device right ? I am not saying it's a reliable one but any additional information is always good !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anup&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 09:45:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118427#M242556</guid>
      <dc:creator>Anup Sasikumar</dc:creator>
      <dc:date>2012-12-31T09:45:42Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118428#M242557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anup,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Additionally I was thinking of doing a MAC address lookup of the MAC&amp;nbsp; address ( from ARP cache of the machine) corresponding to "suspected"&amp;nbsp; switch IP got from active probing. That would provide some additional&amp;nbsp; information as well right ?&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please keep in mind that the MAC address of a switch would be in your ARP table only if you happened to be on the switch's management VLAN. I do not think this is going to be the case too often.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 09:54:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118428#M242557</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2012-12-31T09:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118429#M242558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Disclaimer&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;STRONG&gt;&lt;EM&gt;Liability Disclaimer&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Posting&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Additionally I was thinking of doing a MAC address lookup of the MAC address ( from ARP cache of the machine) corresponding to "suspected" switch IP got from active probing. That would provide some additional information as well right ?&lt;/PRE&gt;&lt;P&gt;I had thought to mention that but as Peter described, your system would have to be in the same L2 domain to see the ARP entry.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Peter is also correct, good chance you won't be on the management VLAN to see the switch's management MAC but looking up MAC's OUI address to vendor might be helpful when "sniffing" BPDUs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS:&lt;/P&gt;&lt;P&gt;BTW, some devices also have "signatures", i.e. how they construct some of their packets, that can be used to identify the host OS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PPS:&lt;/P&gt;&lt;P&gt;Oh, also forgot to mention, sometimes if you do a ping scan that supports DNS reverse lookups, the management IP's DNS entry might indicate by its name that it's a switch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 10:25:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118429#M242558</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2012-12-31T10:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118430#M242559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anup - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just adding one more idea if that is helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a possible way by which we could know the L2 hops in between the default gateway and PC (if we have the access to the Default Gateway). You may take a look at the following discussion and check for command -&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/2184184"&gt;https://supportforums.cisco.com/thread/2184184&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;traceroute mac &lt;SOURCE-MAC&gt; &lt;DESTINATION-MAC&gt;&lt;/DESTINATION-MAC&gt;&lt;/SOURCE-MAC&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I don't think there is a direct way of getting the full topology from the PC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rahul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 16:59:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118430#M242559</guid>
      <dc:creator>Rahul Kukreja</dc:creator>
      <dc:date>2012-12-31T16:59:13Z</dc:date>
    </item>
    <item>
      <title>Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118431#M242560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Joseph..&lt;/P&gt;&lt;P&gt;I like the disclaimer.. u mind if I use it also?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2012 19:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118431#M242560</guid>
      <dc:creator>paul.strazza</dc:creator>
      <dc:date>2012-12-31T19:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: Identify Layer 2 devices in a Network</title>
      <link>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118432#M242561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;&lt;STRONG&gt;Disclaimer&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;STRONG&gt;&lt;EM&gt;Liability Disclaimer&lt;/EM&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;EM&gt;In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;Posting&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;paul.strazza wrote:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Joseph..&lt;/P&gt;&lt;P&gt;I like the disclaimer.. u mind if I use it also?&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Laugh - most, I believe, dislike it (truth be known I don't like it either but we do live in a litigious society, sigh) - and it's a pain to paste into every posting - but yes you, or anyone else, are welcome to copy it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Jan 2013 00:27:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/identify-layer-2-devices-in-a-network/m-p/2118432#M242561</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2013-01-01T00:27:54Z</dc:date>
    </item>
  </channel>
</rss>

