<?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 Re: Show Lan display in system analyzer in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553399#M49243</link>
    <description>MC,&lt;BR /&gt;&lt;BR /&gt;I've also checked on a couple of systems. Looks like this protocol is only set up, if you are running DECnet-Plus and have MOP enabled on that LAN interface (MOP CIRCUIT xxx).&lt;BR /&gt;&lt;BR /&gt;Datalink level loopback testing may come in handy, if you have problems in your network equipment. With NCL LOOP you can send packets to an individual LAN interface, varying things like packet length, packet contents (0/1/mixed) etc. &lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Sat, 28 May 2005 01:55:08 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2005-05-28T01:55:08Z</dc:date>
    <item>
      <title>Show Lan display in system analyzer</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553396#M49240</link>
      <description>Hello all,&lt;BR /&gt;&lt;BR /&gt;I was looking in the system analyzer at the SHOW LAN display for protocols on my LAN Adapters and I noticed one that was unfamiliar.  &lt;BR /&gt;&lt;BR /&gt;Client       State&lt;BR /&gt;------       -----&lt;BR /&gt;LOOP         009D STRTN,UNIQ,SHARE,STRTD,SHRDEF&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I understand the other bindings like LAT and IP etc.. but not sure what LOOP is?  I see it referenced in some documentation but nothing specific.  Anyone know what its used for?&lt;BR /&gt;&lt;BR /&gt;MC</description>
      <pubDate>Fri, 27 May 2005 10:29:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553396#M49240</guid>
      <dc:creator>M C_1</dc:creator>
      <dc:date>2005-05-27T10:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Show Lan display in system analyzer</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553397#M49241</link>
      <description>MC&lt;BR /&gt;&lt;BR /&gt;this protocol type corresponds to the Ethernet LOOP protocol type 90-00. It's used for LOOPBACK messages at the datalink level.&lt;BR /&gt;&lt;BR /&gt;You can generate these LOOP packets with:&lt;BR /&gt;&lt;BR /&gt;MC NCL LOOP MOP CIRCUIT csmacd-n ADDRESS xx-xx-xx-xx-xx-xx&lt;BR /&gt;&lt;BR /&gt;or&lt;BR /&gt;&lt;BR /&gt;MC NCP LOOP CIRCUIT xxx-0 PHYSICAL ADDRESS xx-xx-xx-xx-xx-xx&lt;BR /&gt;&lt;BR /&gt;You can check, whether your system has received/sent any messages with this protocol type with SDA&amp;gt; SHOW LAN/FULL/DEVICE=xxx where xxx is the LAN device unit UCB name from column 1 of the SHOW LAN protocol summary display (for the LOOP client line).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 27 May 2005 11:42:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553397#M49241</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-27T11:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: Show Lan display in system analyzer</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553398#M49242</link>
      <description>Volker - thanks for the quick response.  I checked SHOW LAN/FULL/DEVICE=xxx on the UCB and most counters were 0.&lt;BR /&gt;&lt;BR /&gt;So what is this really used for?  Is there a specific part of the OS that needs it?  I don't see it on other systems that I manage.  &lt;BR /&gt;&lt;BR /&gt;In the not too distant past, we used MOP for some of our old VXT's, could this LOOP binding have been established as part of that?&lt;BR /&gt;&lt;BR /&gt;MC</description>
      <pubDate>Fri, 27 May 2005 13:04:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553398#M49242</guid>
      <dc:creator>M C_1</dc:creator>
      <dc:date>2005-05-27T13:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Show Lan display in system analyzer</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553399#M49243</link>
      <description>MC,&lt;BR /&gt;&lt;BR /&gt;I've also checked on a couple of systems. Looks like this protocol is only set up, if you are running DECnet-Plus and have MOP enabled on that LAN interface (MOP CIRCUIT xxx).&lt;BR /&gt;&lt;BR /&gt;Datalink level loopback testing may come in handy, if you have problems in your network equipment. With NCL LOOP you can send packets to an individual LAN interface, varying things like packet length, packet contents (0/1/mixed) etc. &lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Sat, 28 May 2005 01:55:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/show-lan-display-in-system-analyzer/m-p/3553399#M49243</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-28T01:55:08Z</dc:date>
    </item>
  </channel>
</rss>

