how to know if my servers should use jumbo frames ( MTU )












3














we have some redhat servers , cluster servers ( as mabri cluster )



few questions:




  1. which linux command print the current MTU value ? , ( we not configured yet MTU in ifcfg file )


  2. what is the default MTU value ( let say we install redhat machine from ISO , then what is the default MTU ? )


  3. in which cases need to use high MTU values and what is the max value ?


  4. , what is the formula to calculate the MTU and according to what ?











share|improve this question
























  • The sysctl command will allow you to print and change current mtu settings.
    – Raman Sailopal
    Feb 23 at 14:08










  • sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
    – yael
    Feb 23 at 14:15












  • If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
    – Raman Sailopal
    Feb 23 at 14:22










  • ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
    – yael
    Feb 23 at 14:25










  • I want to ask also when we increase the MTU , what about the huge pages size ?
    – yael
    Feb 23 at 14:28
















3














we have some redhat servers , cluster servers ( as mabri cluster )



few questions:




  1. which linux command print the current MTU value ? , ( we not configured yet MTU in ifcfg file )


  2. what is the default MTU value ( let say we install redhat machine from ISO , then what is the default MTU ? )


  3. in which cases need to use high MTU values and what is the max value ?


  4. , what is the formula to calculate the MTU and according to what ?











share|improve this question
























  • The sysctl command will allow you to print and change current mtu settings.
    – Raman Sailopal
    Feb 23 at 14:08










  • sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
    – yael
    Feb 23 at 14:15












  • If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
    – Raman Sailopal
    Feb 23 at 14:22










  • ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
    – yael
    Feb 23 at 14:25










  • I want to ask also when we increase the MTU , what about the huge pages size ?
    – yael
    Feb 23 at 14:28














3












3








3


1





we have some redhat servers , cluster servers ( as mabri cluster )



few questions:




  1. which linux command print the current MTU value ? , ( we not configured yet MTU in ifcfg file )


  2. what is the default MTU value ( let say we install redhat machine from ISO , then what is the default MTU ? )


  3. in which cases need to use high MTU values and what is the max value ?


  4. , what is the formula to calculate the MTU and according to what ?











share|improve this question















we have some redhat servers , cluster servers ( as mabri cluster )



few questions:




  1. which linux command print the current MTU value ? , ( we not configured yet MTU in ifcfg file )


  2. what is the default MTU value ( let say we install redhat machine from ISO , then what is the default MTU ? )


  3. in which cases need to use high MTU values and what is the max value ?


  4. , what is the formula to calculate the MTU and according to what ?








linux networking rhel ifconfig






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 28 at 19:13









Rui F Ribeiro

38.8k1479128




38.8k1479128










asked Feb 23 at 14:03









yael

2,41612059




2,41612059












  • The sysctl command will allow you to print and change current mtu settings.
    – Raman Sailopal
    Feb 23 at 14:08










  • sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
    – yael
    Feb 23 at 14:15












  • If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
    – Raman Sailopal
    Feb 23 at 14:22










  • ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
    – yael
    Feb 23 at 14:25










  • I want to ask also when we increase the MTU , what about the huge pages size ?
    – yael
    Feb 23 at 14:28


















  • The sysctl command will allow you to print and change current mtu settings.
    – Raman Sailopal
    Feb 23 at 14:08










  • sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
    – yael
    Feb 23 at 14:15












  • If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
    – Raman Sailopal
    Feb 23 at 14:22










  • ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
    – yael
    Feb 23 at 14:25










  • I want to ask also when we increase the MTU , what about the huge pages size ?
    – yael
    Feb 23 at 14:28
















The sysctl command will allow you to print and change current mtu settings.
– Raman Sailopal
Feb 23 at 14:08




The sysctl command will allow you to print and change current mtu settings.
– Raman Sailopal
Feb 23 at 14:08












sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
– yael
Feb 23 at 14:15






sysctl -a | grep -i mtu ת we got a lot of parameters which parameter refers to MTU ?
– yael
Feb 23 at 14:15














If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
– Raman Sailopal
Feb 23 at 14:22




If you are looking for the MTU of your NIC it will be net.ipv6.conf.{nic-name}.mtu
– Raman Sailopal
Feb 23 at 14:22












ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
– yael
Feb 23 at 14:25




ok but we see all this - net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.eno16780032.mtu = 1500 net.ipv6.conf.lo.mtu = 65536
– yael
Feb 23 at 14:25












I want to ask also when we increase the MTU , what about the huge pages size ?
– yael
Feb 23 at 14:28




I want to ask also when we increase the MTU , what about the huge pages size ?
– yael
Feb 23 at 14:28










1 Answer
1






active

oldest

votes


















4














In my opinion the question should not be "How to know ...if"; it is more suitable asking "When should I setup Jumbo frames".



As per your answers about MTU/Jumbo frames:



1) To see your MTU, either ifconfig or ip do:



$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.249 netmask 255.255.255.0 broadcast 192.168.1.255
ether 00:0c:29:40:68:ee txqueuelen 1000 (Ethernet)
RX packets 50182 bytes 22054712 (21.0 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 6674 bytes 838613 (818.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Or with ip:



$ ip addr show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:40:68:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.1.249/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever


Or more simply:



$ ip link show eth0 | grep mtu
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000


2) Normally in IPv4, the default is MTU being 1500 (bytes).



3 and 4)



Usually the default MTU is fine. Rarely you have to change it for lower, temporarily, when dealing with communications problems, when firewalls are blocking ICMP packets which do not allow MTU to be negotiated.



The other situation you may wish to change MTU is for defining JUMBO frames.



However, you do not benefit alway of using JUMBO frames, only in specific cases like a dedicated VLAN of file servers or maybe DB servers, and on top of that, in a VLAN with JUMBO frames ALL the machines have to be configured for JUMBO frames; the switches also have to support JUMBO frames.



You surely do not want to use JUMBO frames for Internet facing systems, like web servers or DNS servers.



For setting in run time an interface for JUMBO frames:



ip link set eth0 mtu 9000


Or in /etc/network/interfaces (in Debian) for making it permanent:



auto eth0
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
mtu 9000


For RH based systems:



Do vi /etc/sysconfig/network-scripts/ifcfg-eth0



and add:



MTU="9000"





share|improve this answer























    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%2f426113%2fhow-to-know-if-my-servers-should-use-jumbo-frames-mtu%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









    4














    In my opinion the question should not be "How to know ...if"; it is more suitable asking "When should I setup Jumbo frames".



    As per your answers about MTU/Jumbo frames:



    1) To see your MTU, either ifconfig or ip do:



    $ ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.249 netmask 255.255.255.0 broadcast 192.168.1.255
    ether 00:0c:29:40:68:ee txqueuelen 1000 (Ethernet)
    RX packets 50182 bytes 22054712 (21.0 MiB)
    RX errors 0 dropped 3 overruns 0 frame 0
    TX packets 6674 bytes 838613 (818.9 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


    Or with ip:



    $ ip addr show eth0
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:40:68:ee brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.249/24 brd 192.168.1.255 scope global eth0
    valid_lft forever preferred_lft forever


    Or more simply:



    $ ip link show eth0 | grep mtu
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000


    2) Normally in IPv4, the default is MTU being 1500 (bytes).



    3 and 4)



    Usually the default MTU is fine. Rarely you have to change it for lower, temporarily, when dealing with communications problems, when firewalls are blocking ICMP packets which do not allow MTU to be negotiated.



    The other situation you may wish to change MTU is for defining JUMBO frames.



    However, you do not benefit alway of using JUMBO frames, only in specific cases like a dedicated VLAN of file servers or maybe DB servers, and on top of that, in a VLAN with JUMBO frames ALL the machines have to be configured for JUMBO frames; the switches also have to support JUMBO frames.



    You surely do not want to use JUMBO frames for Internet facing systems, like web servers or DNS servers.



    For setting in run time an interface for JUMBO frames:



    ip link set eth0 mtu 9000


    Or in /etc/network/interfaces (in Debian) for making it permanent:



    auto eth0
    iface eth0 inet static
    address 192.168.1.100
    netmask 255.255.255.0
    network 192.168.1.0
    broadcast 192.168.1.255
    gateway 192.168.1.1
    mtu 9000


    For RH based systems:



    Do vi /etc/sysconfig/network-scripts/ifcfg-eth0



    and add:



    MTU="9000"





    share|improve this answer




























      4














      In my opinion the question should not be "How to know ...if"; it is more suitable asking "When should I setup Jumbo frames".



      As per your answers about MTU/Jumbo frames:



      1) To see your MTU, either ifconfig or ip do:



      $ ifconfig
      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      inet 192.168.1.249 netmask 255.255.255.0 broadcast 192.168.1.255
      ether 00:0c:29:40:68:ee txqueuelen 1000 (Ethernet)
      RX packets 50182 bytes 22054712 (21.0 MiB)
      RX errors 0 dropped 3 overruns 0 frame 0
      TX packets 6674 bytes 838613 (818.9 KiB)
      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


      Or with ip:



      $ ip addr show eth0
      2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      link/ether 00:0c:29:40:68:ee brd ff:ff:ff:ff:ff:ff
      inet 192.168.1.249/24 brd 192.168.1.255 scope global eth0
      valid_lft forever preferred_lft forever


      Or more simply:



      $ ip link show eth0 | grep mtu
      2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000


      2) Normally in IPv4, the default is MTU being 1500 (bytes).



      3 and 4)



      Usually the default MTU is fine. Rarely you have to change it for lower, temporarily, when dealing with communications problems, when firewalls are blocking ICMP packets which do not allow MTU to be negotiated.



      The other situation you may wish to change MTU is for defining JUMBO frames.



      However, you do not benefit alway of using JUMBO frames, only in specific cases like a dedicated VLAN of file servers or maybe DB servers, and on top of that, in a VLAN with JUMBO frames ALL the machines have to be configured for JUMBO frames; the switches also have to support JUMBO frames.



      You surely do not want to use JUMBO frames for Internet facing systems, like web servers or DNS servers.



      For setting in run time an interface for JUMBO frames:



      ip link set eth0 mtu 9000


      Or in /etc/network/interfaces (in Debian) for making it permanent:



      auto eth0
      iface eth0 inet static
      address 192.168.1.100
      netmask 255.255.255.0
      network 192.168.1.0
      broadcast 192.168.1.255
      gateway 192.168.1.1
      mtu 9000


      For RH based systems:



      Do vi /etc/sysconfig/network-scripts/ifcfg-eth0



      and add:



      MTU="9000"





      share|improve this answer


























        4












        4








        4






        In my opinion the question should not be "How to know ...if"; it is more suitable asking "When should I setup Jumbo frames".



        As per your answers about MTU/Jumbo frames:



        1) To see your MTU, either ifconfig or ip do:



        $ ifconfig
        eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.249 netmask 255.255.255.0 broadcast 192.168.1.255
        ether 00:0c:29:40:68:ee txqueuelen 1000 (Ethernet)
        RX packets 50182 bytes 22054712 (21.0 MiB)
        RX errors 0 dropped 3 overruns 0 frame 0
        TX packets 6674 bytes 838613 (818.9 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


        Or with ip:



        $ ip addr show eth0
        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 00:0c:29:40:68:ee brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.249/24 brd 192.168.1.255 scope global eth0
        valid_lft forever preferred_lft forever


        Or more simply:



        $ ip link show eth0 | grep mtu
        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000


        2) Normally in IPv4, the default is MTU being 1500 (bytes).



        3 and 4)



        Usually the default MTU is fine. Rarely you have to change it for lower, temporarily, when dealing with communications problems, when firewalls are blocking ICMP packets which do not allow MTU to be negotiated.



        The other situation you may wish to change MTU is for defining JUMBO frames.



        However, you do not benefit alway of using JUMBO frames, only in specific cases like a dedicated VLAN of file servers or maybe DB servers, and on top of that, in a VLAN with JUMBO frames ALL the machines have to be configured for JUMBO frames; the switches also have to support JUMBO frames.



        You surely do not want to use JUMBO frames for Internet facing systems, like web servers or DNS servers.



        For setting in run time an interface for JUMBO frames:



        ip link set eth0 mtu 9000


        Or in /etc/network/interfaces (in Debian) for making it permanent:



        auto eth0
        iface eth0 inet static
        address 192.168.1.100
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        mtu 9000


        For RH based systems:



        Do vi /etc/sysconfig/network-scripts/ifcfg-eth0



        and add:



        MTU="9000"





        share|improve this answer














        In my opinion the question should not be "How to know ...if"; it is more suitable asking "When should I setup Jumbo frames".



        As per your answers about MTU/Jumbo frames:



        1) To see your MTU, either ifconfig or ip do:



        $ ifconfig
        eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.1.249 netmask 255.255.255.0 broadcast 192.168.1.255
        ether 00:0c:29:40:68:ee txqueuelen 1000 (Ethernet)
        RX packets 50182 bytes 22054712 (21.0 MiB)
        RX errors 0 dropped 3 overruns 0 frame 0
        TX packets 6674 bytes 838613 (818.9 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


        Or with ip:



        $ ip addr show eth0
        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 00:0c:29:40:68:ee brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.249/24 brd 192.168.1.255 scope global eth0
        valid_lft forever preferred_lft forever


        Or more simply:



        $ ip link show eth0 | grep mtu
        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000


        2) Normally in IPv4, the default is MTU being 1500 (bytes).



        3 and 4)



        Usually the default MTU is fine. Rarely you have to change it for lower, temporarily, when dealing with communications problems, when firewalls are blocking ICMP packets which do not allow MTU to be negotiated.



        The other situation you may wish to change MTU is for defining JUMBO frames.



        However, you do not benefit alway of using JUMBO frames, only in specific cases like a dedicated VLAN of file servers or maybe DB servers, and on top of that, in a VLAN with JUMBO frames ALL the machines have to be configured for JUMBO frames; the switches also have to support JUMBO frames.



        You surely do not want to use JUMBO frames for Internet facing systems, like web servers or DNS servers.



        For setting in run time an interface for JUMBO frames:



        ip link set eth0 mtu 9000


        Or in /etc/network/interfaces (in Debian) for making it permanent:



        auto eth0
        iface eth0 inet static
        address 192.168.1.100
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        mtu 9000


        For RH based systems:



        Do vi /etc/sysconfig/network-scripts/ifcfg-eth0



        and add:



        MTU="9000"






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Feb 25 at 0:31

























        answered Feb 23 at 15:43









        Rui F Ribeiro

        38.8k1479128




        38.8k1479128






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f426113%2fhow-to-know-if-my-servers-should-use-jumbo-frames-mtu%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

            Morgemoulin

            Scott Moir

            Souastre