<?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: MTU problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915286#M763933</link>
    <description>PathMTU may indeed be the best way to go here.  It does beg the question though - why do you want to cripple your NICs with a 500 byte MTU?&lt;BR /&gt;</description>
    <pubDate>Tue, 19 Dec 2006 20:50:46 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2006-12-19T20:50:46Z</dc:date>
    <item>
      <title>MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915280#M763927</link>
      <description>Hello all,&lt;BR /&gt;I was trying to change the MTU size by running the command lanadmin and it worked with me on the first server, but when i was trying to change the MTU on the 2nd server I was receiving an error message:unable to change MTU size errno=22.&lt;BR /&gt;Even when trying to change MTU from sam, the same problem persists.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ziad</description>
      <pubDate>Tue, 19 Dec 2006 08:41:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915280#M763927</guid>
      <dc:creator>Morcos</dc:creator>
      <dc:date>2006-12-19T08:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915281#M763928</link>
      <description>Ziad,&lt;BR /&gt;what are you trying to set it to ?&lt;BR /&gt;It may be a range limit problem.&lt;BR /&gt;  &lt;BR /&gt;Please list lanadmin command .&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Dec 2006 08:47:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915281#M763928</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-12-19T08:47:11Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915282#M763929</link>
      <description>Ziad,&lt;BR /&gt;&lt;BR /&gt;It is possible that the one value specified for one lan card may not work with other. The MTU value range depend on type of card you are using.&lt;BR /&gt;&lt;BR /&gt;You can set it with lanadmin -M &lt;MTU value=""&gt;&lt;BR /&gt;&lt;BR /&gt;Sunil&lt;BR /&gt;&lt;/MTU&gt;</description>
      <pubDate>Tue, 19 Dec 2006 10:42:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915282#M763929</guid>
      <dc:creator>Sunil Sharma_1</dc:creator>
      <dc:date>2006-12-19T10:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915283#M763930</link>
      <description>Thx Peter for your quick answer.&lt;BR /&gt;Well I'm trying to set the MTU to 500.&lt;BR /&gt;&lt;BR /&gt;The output of Lanadmin is:&lt;BR /&gt;PPA Number                      = 0&lt;BR /&gt;Description                     = lan0 HP PCI Core I/O 1000Base-T Release B.11.&lt;BR /&gt;1.21&lt;BR /&gt;Type (value)                    = ethernet-csmacd(6)&lt;BR /&gt;MTU Size                        = 1500&lt;BR /&gt;Speed                           = 100000000&lt;BR /&gt;Station Address                 = 0x14c210d2d9&lt;BR /&gt;Administration Status (value)   = up(1)&lt;BR /&gt;Operation Status (value)        = up(1)&lt;BR /&gt;Last Change                     = 403658437&lt;BR /&gt;Inbound Octets                  = 3745791373&lt;BR /&gt;Inbound Unicast Packets         = 401768101&lt;BR /&gt;Inbound Non-Unicast Packets     = 59107825&lt;BR /&gt;Inbound Discards                = 20037&lt;BR /&gt;Inbound Errors                  = 0&lt;BR /&gt;Inbound Unknown Protocols       = 20053536&lt;BR /&gt;Outbound Octets                 = 2079284204&lt;BR /&gt;Outbound Unicast Packets        = 434106130&lt;BR /&gt;Outbound Non-Unicast Packets    = 17722&lt;BR /&gt;Outbound Discards               = 0&lt;BR /&gt;Outbound Errors                 = 0&lt;BR /&gt;Outbound Queue Length           = 0&lt;BR /&gt;Specific                        = 655367&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thx in advanced.&lt;BR /&gt;&lt;BR /&gt;ziad</description>
      <pubDate>Tue, 19 Dec 2006 10:48:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915283#M763930</guid>
      <dc:creator>Morcos</dc:creator>
      <dc:date>2006-12-19T10:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915284#M763931</link>
      <description>Ziad,&lt;BR /&gt;I don't think you can set the MTu on this card to 500.&lt;BR /&gt;From:&lt;BR /&gt;docs.hp.com/en/J5683-90002/J5683-90002.pdf&lt;BR /&gt;&lt;BR /&gt;"1000Base-T features:&lt;BR /&gt;â   Triple speed 10/100/1000 Mbps&lt;BR /&gt;â   Full duplex operation at 10/100/1000 Mbps and half-duplex operation at 10/100&lt;BR /&gt;Mbps (no half-duplex support for 1000 Mbps)&lt;BR /&gt;â   Autonegotiation and autosensing to the highest available link speed"&lt;BR /&gt;&lt;BR /&gt;"â ¢ Maximum Transmission Unit (MTU)&lt;BR /&gt;The MTU can be either the regular Ethernet MTU (1500 bytes) or the Jumbo Frame&lt;BR /&gt;MTU (9000 bytes). For 1000Base-T, jumbo frames can be configured only when the&lt;BR /&gt;link speed is 1000 Mbps."</description>
      <pubDate>Tue, 19 Dec 2006 11:07:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915284#M763931</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-12-19T11:07:34Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915285#M763932</link>
      <description>What you might be able to do is to effectively set the MTU by re-specifying the default route with a PMTU.&lt;BR /&gt;&lt;BR /&gt;See man route &lt;BR /&gt;The -p parameter is the one to use.&lt;BR /&gt;&lt;BR /&gt;Don't do it on the same lan that you are connected through, or else do this on the console.  Otherwise you may be disconnected.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Dec 2006 11:13:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915285#M763932</guid>
      <dc:creator>Steve Lewis</dc:creator>
      <dc:date>2006-12-19T11:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: MTU problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915286#M763933</link>
      <description>PathMTU may indeed be the best way to go here.  It does beg the question though - why do you want to cripple your NICs with a 500 byte MTU?&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Dec 2006 20:50:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mtu-problem/m-p/3915286#M763933</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-12-19T20:50:46Z</dc:date>
    </item>
  </channel>
</rss>

