why MTU change from 1500 to 9000












1















in /var/log/message file we found something interesting



Mar  9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000


we can see the interface card - en3j87
change from 1500 MTU to 9000



is it normal ?



Mar  9 07:07:33 linux54 dbus-daemon: dbus[1153]: [system] Successfully activated service 'org.freedesktop.problems'
Mar 9 07:08:30 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
Mar 9 07:08:30 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Mar 9 07:08:31 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready
Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: removed PHC on en3j87
Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000
Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
Mar 9 07:08:32 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
Mar 9 07:08:32 linux54 kernel: team0: Port device en3j87 added
Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
Mar 9 07:08:33 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
Mar 9 07:08:33 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready









share|improve this question



























    1















    in /var/log/message file we found something interesting



    Mar  9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000


    we can see the interface card - en3j87
    change from 1500 MTU to 9000



    is it normal ?



    Mar  9 07:07:33 linux54 dbus-daemon: dbus[1153]: [system] Successfully activated service 'org.freedesktop.problems'
    Mar 9 07:08:30 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
    Mar 9 07:08:30 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
    Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
    Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    Mar 9 07:08:31 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready
    Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: removed PHC on en3j87
    Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000
    Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
    Mar 9 07:08:32 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
    Mar 9 07:08:32 linux54 kernel: team0: Port device en3j87 added
    Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
    Mar 9 07:08:33 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
    Mar 9 07:08:33 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready









    share|improve this question

























      1












      1








      1


      1






      in /var/log/message file we found something interesting



      Mar  9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000


      we can see the interface card - en3j87
      change from 1500 MTU to 9000



      is it normal ?



      Mar  9 07:07:33 linux54 dbus-daemon: dbus[1153]: [system] Successfully activated service 'org.freedesktop.problems'
      Mar 9 07:08:30 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
      Mar 9 07:08:30 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
      Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
      Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
      Mar 9 07:08:31 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: removed PHC on en3j87
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
      Mar 9 07:08:32 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
      Mar 9 07:08:32 linux54 kernel: team0: Port device en3j87 added
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
      Mar 9 07:08:33 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
      Mar 9 07:08:33 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready









      share|improve this question














      in /var/log/message file we found something interesting



      Mar  9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000


      we can see the interface card - en3j87
      change from 1500 MTU to 9000



      is it normal ?



      Mar  9 07:07:33 linux54 dbus-daemon: dbus[1153]: [system] Successfully activated service 'org.freedesktop.problems'
      Mar 9 07:08:30 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
      Mar 9 07:08:30 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
      Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
      Mar 9 07:08:31 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
      Mar 9 07:08:31 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: removed PHC on en3j87
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: changing MTU from 1500 to 9000
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1: registered PHC device on en3j87
      Mar 9 07:08:32 linux54 kernel: IPv6: ADDRCONF(NETDEV_UP): en3j87: link is not ready
      Mar 9 07:08:32 linux54 kernel: team0: Port device en3j87 added
      Mar 9 07:08:32 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: detected SFP+: 5
      Mar 9 07:08:33 linux54 kernel: ixgbe 0000:0b:00.1 en3j87: NIC Link is Up 10 Gbps, Flow Control: RX/TX
      Mar 9 07:08:33 linux54 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): en3j87: link becomes ready






      linux networking rhel network-interface dmesg






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      yaelyael

      2,72122574




      2,72122574






















          1 Answer
          1






          active

          oldest

          votes


















          2














          This means that your interface has been configured to use jumbo frames. If the connection is working, then it’s nothing to worry about, and you’ll get higher throughput as a result. (If it works, it means the network equipment the interface is connected to has also been configured for jumbo frames.)






          share|improve this answer
























          • The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

            – Rui F Ribeiro
            16 mins ago













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507069%2fwhy-mtu-change-from-1500-to-9000%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          This means that your interface has been configured to use jumbo frames. If the connection is working, then it’s nothing to worry about, and you’ll get higher throughput as a result. (If it works, it means the network equipment the interface is connected to has also been configured for jumbo frames.)






          share|improve this answer
























          • The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

            – Rui F Ribeiro
            16 mins ago


















          2














          This means that your interface has been configured to use jumbo frames. If the connection is working, then it’s nothing to worry about, and you’ll get higher throughput as a result. (If it works, it means the network equipment the interface is connected to has also been configured for jumbo frames.)






          share|improve this answer
























          • The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

            – Rui F Ribeiro
            16 mins ago
















          2












          2








          2







          This means that your interface has been configured to use jumbo frames. If the connection is working, then it’s nothing to worry about, and you’ll get higher throughput as a result. (If it works, it means the network equipment the interface is connected to has also been configured for jumbo frames.)






          share|improve this answer













          This means that your interface has been configured to use jumbo frames. If the connection is working, then it’s nothing to worry about, and you’ll get higher throughput as a result. (If it works, it means the network equipment the interface is connected to has also been configured for jumbo frames.)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 3 hours ago









          Stephen KittStephen Kitt

          176k24401479




          176k24401479













          • The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

            – Rui F Ribeiro
            16 mins ago





















          • The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

            – Rui F Ribeiro
            16 mins ago



















          The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

          – Rui F Ribeiro
          16 mins ago







          The key point here is that it was configured, it does not change alone. Now if people changes randomly MTUs, that is another problem.

          – Rui F Ribeiro
          16 mins ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507069%2fwhy-mtu-change-from-1500-to-9000%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Entries order in /etc/network/interfaces

          新発田市

          Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)