<?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: VMS731_LAN-V1200 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404817#M48040</link>
    <description>Ian,&lt;BR /&gt;&lt;BR /&gt;Yes, it seems strange. But if you think abbout collisions, packets droped by network devices (bridges,switches,routers...) and packets which are not received in sequence, this must be handled by a higher protocol. Which is the difference between a not sent packet and a droped packet?&lt;BR /&gt;Maybe the sent packet reported as not sent is slightly more difficult to handle. I dont know how higher protocols handle this. TCP puts a sequence number in the packet header and probably drops duplicate packets.&lt;BR /&gt;&lt;BR /&gt;The duplex mismatch detection code is realy a good new. This is realy a problem which is seen to much times. The worth thing abbout this problem is that the network works, but like an old modem connection.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
    <pubDate>Sat, 23 Oct 2004 15:06:28 GMT</pubDate>
    <dc:creator>Bojan Nemec</dc:creator>
    <dc:date>2004-10-23T15:06:28Z</dc:date>
    <item>
      <title>VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404810#M48033</link>
      <description>I was just reading the release notes (just for fun :-) and I noticed some interesting points.&lt;BR /&gt;&lt;BR /&gt;It is possible for ethernet frames to be reported as successfully sent when the driver has not sent them yet. The failure to send will only be reported in the statistics !&lt;BR /&gt;&lt;BR /&gt;It is possible for a frame to be reported as not send due to timeout and infact it gets successfully sent !&lt;BR /&gt;&lt;BR /&gt;As it points out, the transmission of data in ethernet frames is a datagram sort of service and higher level protocols have to cope.&lt;BR /&gt;&lt;BR /&gt;One bit good news is that this patch kit has the duplex mismatch detection code in (mentioned at the TUD) - a console message is output by the driver if it thinks there may be duplex mismatch (e.g NIC on full duplex, switch on half uplex). This should help detect this problem which has bothered some people here.</description>
      <pubDate>Thu, 21 Oct 2004 03:32:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404810#M48033</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-10-21T03:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404811#M48034</link>
      <description>Oh, cool. The first one sounds a bit like a writeback cache on the network ;-)</description>
      <pubDate>Thu, 21 Oct 2004 04:13:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404811#M48034</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-10-21T04:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404812#M48035</link>
      <description>and writeback cache without battery backup is an abomination unto Nuggen !&lt;BR /&gt;(see Terry Pratchett Monstrous Regiment)</description>
      <pubDate>Thu, 21 Oct 2004 04:32:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404812#M48035</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-10-21T04:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404813#M48036</link>
      <description>... but it saves money which is more important ;-)</description>
      <pubDate>Thu, 21 Oct 2004 05:55:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404813#M48036</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-10-21T05:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404814#M48037</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;see Terry Pratchett&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;Shouldn't information going to The Unseen University  be shielded for commoners?&lt;BR /&gt;&lt;BR /&gt;Looks like they achieved it  :-)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Thu, 21 Oct 2004 08:01:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404814#M48037</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-10-21T08:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404815#M48038</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;well the first paragraph makes one wonder how the DEATH of network pakets looks like and what he uses as a scythe ;-)&lt;BR /&gt;&lt;BR /&gt;Sorry, could not resist, it is too long I read my last Pratchett book.&lt;BR /&gt;&lt;BR /&gt;Cheers, &lt;BR /&gt;&lt;BR /&gt;Martin</description>
      <pubDate>Thu, 21 Oct 2004 17:01:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404815#M48038</guid>
      <dc:creator>Martin P.J. Zinser</dc:creator>
      <dc:date>2004-10-21T17:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404816#M48039</link>
      <description>All this humour does lighten up this dark and wet night (as does the beer I'm drinking - Belgian abbey ale called Maredsous - a triple at 10% - light in colour and very good).&lt;BR /&gt;&lt;BR /&gt;However the point of my posting was to see if people thought that the behaviour of the LAN driver with this patch was surprising. It can report success when the transmit has failed and failure when the transmit succeeds! This seems very strange to me although I do accept the point about it being a datagram level service.</description>
      <pubDate>Sat, 23 Oct 2004 13:55:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404816#M48039</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-10-23T13:55:17Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404817#M48040</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;Yes, it seems strange. But if you think abbout collisions, packets droped by network devices (bridges,switches,routers...) and packets which are not received in sequence, this must be handled by a higher protocol. Which is the difference between a not sent packet and a droped packet?&lt;BR /&gt;Maybe the sent packet reported as not sent is slightly more difficult to handle. I dont know how higher protocols handle this. TCP puts a sequence number in the packet header and probably drops duplicate packets.&lt;BR /&gt;&lt;BR /&gt;The duplex mismatch detection code is realy a good new. This is realy a problem which is seen to much times. The worth thing abbout this problem is that the network works, but like an old modem connection.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Sat, 23 Oct 2004 15:06:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404817#M48040</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2004-10-23T15:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: VMS731_LAN-V1200</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404818#M48041</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;Good choice, Maredsous. Also try Chimay blue and Rochefort 10.&lt;BR /&gt;&lt;BR /&gt;1) It is possible for ethernet frames to be reported as successfully sent when the driver has not sent them yet. &lt;BR /&gt;-&amp;gt; Yes. You get an OK as fast as it is put into a buffer. It is the tcp or decnet software that will receive the NOK and increase the counters/do retransmit.&lt;BR /&gt;&lt;BR /&gt;2) It is possible for a frame to be reported as not send due to timeout and infact it gets successfully sent !&lt;BR /&gt;-&amp;gt; Yes. If the network fails when your frame was sent and a network failure occurs before the ack/answer is received.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Sun, 24 Oct 2004 10:58:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms731-lan-v1200/m-p/3404818#M48041</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-10-24T10:58:25Z</dc:date>
    </item>
  </channel>
</rss>

