Jumbo Frames question on SRW series Switches

One of our vendors was saying that on an un vlaned switch, using jumbo frames, if a link to a server that did not use jumbo frames it would disable jumbo frames for the whole switch. Does anyone know if there is there is any truth to that statement?

I don't think so because once you enable jumbo frame on the switch it automatically enable it on all the ports.

Similar Messages

  • Firmware upgrade question for 300 series switches

    Hi-
    I have a customer that is investigating a strategy and solution for centralized firmware management of the 300 series switches.  They have found an issue in the lab where they were trying to roll back the firmware to a previous version  They can not roll back to the previous firmware version, which is desirable in the case of finding an issue in the new firmware that causes them to have need to rollback to a known working version.
    We have read in the cisco 300 switch admin guide that there are two images (active and inactive) and that a new downloaded firmware always replaces the inactive image and is active until explicitly set.  The admin guide does not mention inability to make an older firmware image as active image when the switch has previously run on a new release firmware image.  My customer's engineers testing have informed me that an older image can not be made active after a newer image has booted.  Can you please verify if this if a fallback is supposed to work as it is causing a lot of concern-
    Thanks-
    Jena

    Jena,
    The release notes -
    http://www.cisco.com/en/US/docs/switches/lan/csbms/sf30x_sg30x/release_notes/Sx200-Sx300_R1.1.2.x.pdf
    What firmware is the switches currently on?
    Major Changes and Defects Corrected
    • Hardware version 1.0 devices that were upgraded to software version 1.1
    can now be downgraded to software version 1.0. You must delete the
    startup configuration file before rebooting the device to software version
    1.0. Otherwise the device may have problems when booting up. You may
    backup your running configuration before the reboot, and re-import the
    configuration afterward. Major Changes and Defects Corrected
    • Hardware version 1.0 devices that were upgraded to software version 1.1
    can now be downgraded to software version 1.0. You must delete the
    startup configuration file before rebooting the device to software version
    1.0. Otherwise the device may have problems when booting up. You may
    backup your running configuration before the reboot, and re-import the
    configuration afterward.
    Please read full release notes for other work arounds
    Hope this helps,
    Jasbryan

  • Linksys SE2800 and jumbo frames

    Does the Linksys SE2800 gigabit 8 port switch support jumbo frames?  Anyone have this switch?  Any issues?  Looking to replace a netgear gigabit switch that likes to forget that it has gigabit machines connected to it.

    Hi Michael,
    Actually had a chat with a colleague at linksys regarding your question, but he referred me to a datasheet, which left me with the question I started with. The technician said yes it suppported Jumbo frames but he could post me nothing in black and white..
    Why not look at the Cisco Small Business  umnanaged product the SG100D-08.   It offers as the datasheet suggets;
    Peace of mind:
    All Cisco 100 Series switches are protected for the life of the product by the Cisco Limited Lifetime Hardware Warranty
    Also,  even though an unmanaged product, this series supports such features as;
    1. Green Energy—Efficient Technology
    The Cisco SG 100D-08 switch supports Green Energy-efficient
    Technology. It can enter sleep mode, turn off unused ports, and adjust
    power as needed. This increases energy efficiency to help businesses use
    less power and save money.
    2. Jumbo Frame Support
    The Cisco SG 100D-08 switch supports frames up to 9,000 bytes called
    jumbo frames. Jumbo Frame support improves network throughput and
    reduces CPU utilization during large file transfers, such as multimedia files,
    by allowing larger payloads in each packet.
    regards Dave

  • Enable jumbo frame on Nexus switch

    I read following phrase in configuration guide of Nexus 5020
    The Cisco Nexus 5000 Series switch is a Layer 2 device. This means it does not fragment frames. As a result,
    the switch cannot have two ports in the same Layer 2 domain with different maximum transmission units
    (MTUs). A per-physical Ethernet interface MTU is not supported. Instead, the MTU is set according to the
    QoS classes. You modify the MTU by setting Class and Policy maps.
    When you show the interface settings, a default MTU of 1500 is displayed for physical Ethernet interfaces
    and a receive data field size of 2112 is displayed for Fibre Channel interfaces
    Has anybody configured jumbo frame with above mentioned way ?

    Yes, it looks something like this:
    policy-map jumbo
    class class-default
    mtu 9216
    policy-map class-default
    class class-default
    mtu 9216
    system qos
    service-policy class-default

  • SG 300-28 Switch - Jumbo Frames Problem.

    I just got the SG 300-28 28 port switch tonight and got it up and running however, i've encountered a problem regarding jumbo frames. In the documentation and product brochures, it states the SG 300 switches supports jumbo frames up to 10k. When I first setup the switch and enabled jumbo frames, i was getting very slow speeds in my network transfers (800kb/s !!!). All the workstations are running Intel PCIE nic cards with jumbo frames enabled at 9014 bytes. After some troubleshooting, i lowered the frame size to 4088 bytes and everything returned to normal with fast speeds.
    I had a suspicion that it might be the switch that is causing the network slowdown with 9k frames; I went ahead and enabled the 9k jumbo frame settings on my NICs again and started to ping other workstations on the network using the "don't fragment" flag. It turns out, the largest packet that i can send out is 8972 bytes. This is a little far from 10k frames that is stated in the documentation and brochures. Please correct me if i'm wrong, but it seems that i've stumbled into a bug in switch.
    Time for a firmware update?

    Hi Dickson C,
    Interesting query.. TCP, UDP and ICMP packet overhead are fairly negligible according to the information below i would think about 94 bytes for ethernet plus tcp overhead.
    The switch would internally label the ethernet frame to identify what VLAN the frame is in (even Vlan 1), so an extra 4 bytes would be used within the switch for that.
    Ethernet frame format:
    6 byte dest MAC  addr
    6 byte src MAC  addr
    [4 byte optional 802.1q VLAN Tag]
    2 byte length/type
    46-9014 byte data (payload)
    4 byte CRC
    Ethernet overhead bytes:
    12 byte intergap + 8 preamble + 14 header + 4 trailer = 18 bytes/packet w/o 802.1q
    12 byte intergap + 8 preamble + 18 header + 4 trailer = 22 bytes/packet with 802.1q
    TCP encapsulated in Ethernet:
    Assuming no header compression (e.g. not PPP)
    Add 20 IPv4 header or 40 IPv6 header (no options)
    Add 20 TCP header
    Add 12 bytes optional TCP timestamps
    TCP overhead can be 52 bytes
    Ethernet + TCP overhead around 52+22 bytes = 74 bytes
    Your Intel ethernet NIC supports around 9500-byte, so the datasheets from intel suggest for a jumbo frame , but you have it enabled at 9014 bytes.
    So your  NIC enabled at 9014 bytes - 74 bytes for Ethernet and TCP packet overhead= approximately 8940 bytes of data.
    You say you are getting packet data throughput around 8972 bytes.
    Check my maths, I have made a few assumptions.  What you reckon, worth a call to the Small Business Support center to double check, please open a case  and report back with the results. I really may be way off in some of my assumptions.
    regards Dave
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html

  • SE2800 gigabit switch an jumbo frames

    Looking at this switch (would have posted this in the switch section but it is archived and there isn't a new one).  Does it support jumbo frames?

    No, the SE2800 doesn't support Jumbo Frames.

  • Enabling Jumbo Frames in CISCO Switch

    Hi,
    I have tried to enable jumbo frames by:
    Go to Port Management >> Port Settings
    Enable Jumbo Frames. Click Apply.
    Save configuration and reboot
    After that I try to verify that jumbo frames is really working by looking at the Status and Statistics >> RMON >> Statistics.
    It seems that the page only shows frame size of up to 1632  Bytes.  Does this mean that the Jumbo Frames are not working?  Is this the correct way to verify that Jumbo frames are enabled?
    Thanks.
    James

    Hi,
    This setting allows the frames to pass on the switch, nothing more. The rest of the devices needs to capable to send and receive such frames as well. You need to configure the NICs and possibly applications to do this.
    Make sure all communicating devices are capable of jumbo frames. If you mix them you will have trouble.
    For a sample how to do this on linux see
    https://wiki.archlinux.org/index.php/Jumbo_Frames
    Hope this helps.

  • How do I maximize LAN speeds using Gigabit Ethernet, jumbo frames?

    I move a lot of large files (RAW photos, music and video) around my internal network, and I'm trying to squeeze out the fastest transfer speeds possible. My question has to do both with decisions about hardware and what settings to use once it's all hooked up.
    This is what I have so far:
    -- imac 3.06GHz, macbook pro 2.53GHz
    -- Cisco gigabit smart switch capable of jumbo frames
    -- Buffalo Terastation Duo NAS (network attached storage), also capable of Gbit and jumbo frames
    -- All wired up with either cat6 or cat53e.
    -- The sizes of the files I'm moving would include large #s of files at either 15MB (photos), 7MB (music), 1-2GB (video) and 650MB (also video).
    -- jumbo frames have been enabled in the settings of the macs, the switch and the buffalo HD.
    -- I've played with various settings of simultaneous connections (more of a help with smaller files), no real difference
    -- Network utility shows the ethernet set to Gbit, with no errors or collisions.
    -- have tried both ftp and the finder's drap and drop
    -- also, whenever I'm doing a major move of data, I kick my family off the network, so there is no other traffic that should be interfering.
    Even with all that, I'm still lucky to get transfer speeds at 15-20mbps, but more commonly at around 10. The other odd thing I've encountered while trying to up my speeds, is that I might start out a transfer at maybe 60mbps, it will maintain that for about 30-60sec and then it appears to ramp itself down, sometimes to as low as 1-5mbps. I'm starting to think my network is mocking me
    I also have a dual band (2.4/5) wireless n router (not jumbo frame capable), but I'm assuming wired is going to trump wireless? (NOTE: in my tests, I have disabled wireless to force the connection through the ethernet).
    Can anyone help with suggestions, and/or suggest a strong networking reference book with emphasis on mac? I'm willing to invest in additional equipment within reason.
    Thanks in advance!
    juliana

    I'm going to pick and choose to answer just a few of the items you have listed. Hopefully others will address other items.
    • This setup was getting me speeds as high as 10-15MB/sec, and as low as 5-6MB/sec when I was transferring video files around 1-2 GB in size
    I would think a single large file would get the best sustained transfer rates, as you have less create new file overhead on the destination device. It is disturbing that the large files transfer at a slower rate.
    • Would a RAID0 config get me faster write speeds than RAID1? I have another NAS that can do other RAID configs, which is fastest as far as write times?
    RAID0 (Striped) is generally faster, as the I/O is spread across 2 disks.
    RAID1 is mirrored, so you can not free the buffer until the same data is on BOTH disks. The disks are NOT going to be in rotational sync, so at least one of the disks will have to wait longer for the write sectors to move under the write heads.
    But RAID1 gives you redundency. RAID0 has not redundency. And you can NOT switch back and forth between the 2 without reformatting your disks, so if you choose RAID0, you do not get redundency unless you provide your own via a backup device for your NAS.
    • what is the most efficient transfer protocol? ftp? smb? something else? And am I better off invoking the protocol from the terminal, or is the overhead of an app-based client negligible?
    Test the different transfers using a large file (100's of MB or a GB sized file would be good as a test file).
    I've had good file transfers with AFP file sharing, but not knowing anything about your NAS, I do not know if it supports AFP, and if it does, whether it is a good implementation.
    If your NAS supports ssh, then I would try scp instead of ftp. scp is like using cp only it works over the network.
    If your NAS support rsync, that would be even better, as it has the ability to just copy files that are either NOT on the destination or update files which have changed, but leave the matching files alone.
    This would help in situations where you cannot copy everything all at once.
    But no matter what you choose, you should measure your performance so you choose something that is good enough.
    • If a client is fine, does anyone have a suggestion as to best one for speed? Doesn't have to be free -- I don't mind supporting good software.
    Again just test what you have.
    • Whats a good number to allow for simultaneous connections, given the number of files and their size?
    If the bottleneck is the NAS, then adding more I/O that will force the disk heads to move away from the current file being written will just slow things down.
    But try 2 connections and measure your performance. If it gets better, then maybe the NAS is not the bottleneck.
    • What question am I not asking?
    You should try using another system as a test destination device in the network setup to see if it gets better, worse, or the same throughput as the NAS. You need to see about changing things in your setup to isolate where the problem might be.
    Also do not rule out bad ethernet cables, so switch them out as well. For example, there was a time I tried to use Gigabit ethernet, but could only get 100BaseT. I even purchased a new gigabit switch, thinking the 1st was just not up to the task. It turned out I had a cheap ethernet cable that only had 4 wires instead of 8 and was not capable of gigabit speeds. An ethernet cable that has a broken wire or connector could exhibit similar performance issues.
    So change anything and everything in your setup, one item at a time and use the same test so you have a pear to pear comparision.

  • How to enable "Jumbo Frame" at RV320 LAN ports?

    I'm sorry about my silly question, where is the option to turn on the "Jumbo Frame" or allow to adjust MTU at the RV320 LAN ports?
    I can't found that in the Web management interface, will it just take the 9Kb MTU packet and no need to set?
    Looks like the MTU settings is only available at those internet ports or USB interface.

    Hello,
    You won't find any LAN side MTU settings on any of the small business routers.  The LAN ports are simply layer 2 switch ports, which means they will either forward or drop the larger packets. They have to be gigabit ports as well, Jumbo Frames do not work with anything less. Unfortunately I cannot find anything specific to this model, and I am unable to test it since I don't have any Jumbo capable NICs. 
    So your best bet is really to just give it a try.  The switch ports on the router will either forward or drop the packets, and anyone going out to the internet will either lower their packet size using MTU discovery, or the router will fragment the packets down to a size appropriate for the WAN link.
    I wish I could be more specific, but without being able to test it that is the most info I can give you right now.
    Let me know how it goes,
    Christopher Ebert

  • *****Jumbo frame on colapse core****

    Hi Folks,
    I have been thinking and research about for that a while now, and yet i have not gotten a formal answer... Please read carefully...
    We are a medium size company.... In both our our remotes, we have four 3750G(two of them are 3750X) in a stack. All good there, the nightmare is we have everything single thing(pc,printer,phones,ipcam,servers(running esxi),SAN(storageFlex)) connected to the stack;therefore, the stack switches are acting as core,distribution and access layer at the same time.
    I need to enable jumbo frame to speed up back, isci frame between SAN and ESXi hosts. knowing i can only enable jumbo frame globally. Since i have all these devices connected to the stack which aren't supported jumbo! should i go head enable jumbo on the stack? Will the device which aren't support jumbo frame will continue to work? Or since i know interface with 100Mb and less will ignore jumbo, should i set all device for which i don't jumbo frame to 100Mb?
    Any help and suggestion will be greatly appreciate.
    Thanks,

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    A device that doesn't support jumbo on a port that does, will work fine as long as another device doesn't send it a jumbo frame.  If that happens, the device will be unable to process the received jumbo frame.  (I.e. a jumbo enabled switch can allow MTU mismatch between hosts.)
    (If you're thinking about IP fragmentation, that will only happen across a L3 hop, and it often creates additional performance issues.)
    BTW, on the 3750 series, data transfer performance problems are often caused by default 3750 buffer allocations.  Allowing jumbo doesn't address that.  I.e., you might obtain much be better data transfer performance via buffer tuning.

  • Jumbo Frame - Enabling on a VLAN of CAT 6500 running IOS

    Jumbo frames needs to be enabled on one of the vlan interface on Cisco 6500 IOS Switch.
    =================================================================
    •1) Once enabled the mtu 9216 on the required vlan interface do we need to reload the switch to take effect (I believe that in some low end swicthes it needs a reload)
    •2) If we enable only one Vlan interface, how about the other vlan interfaces(about 200 are on this switch)? Do we need to specify mtu1500 on other vlan interfaces?
    I have read information at the following two links, but I still wish to reconfirm by asking the questions in this forum. Someone who has already implemented this may have gained more experience while implementing it on CAT 6500 IOS Switch.
    https://supportforums.cisco.com/message/963341#963341
    http://www.cisco.com/en/US/products/hw/switches/ps700/products_configuration_example09186a008010edab.shtml
    http://www.cisco.com/en/US/products/hw/switches/ps700/products_configuration_example09186a008010edab.shtml#backinfo1
    Thanks.
    Alphonse

    You do not need to reboot your 6500 after you enable jumbo frames, but it is good idea to do it during an outage window. You only need to reboot smaller switches i.e. 3560, 3750, etc...after enabling jumbo frames. On these switches you can only enable it globally.  Only enable jumbo frames for the vlans you need.  You usually need jumbo frames for vlans connecting to the storage systems.
    Good Luck

  • Jumbo Frame iSCSI

    I am using iSCSI for backup to disk. The target is SUSE 10 and initiator
    is NW 6.5 sp7. The speed isn't so great, so I'm trying to make sure I've
    got Jumbo frames setup properly. I've added the switch Jumbo=9000 to my
    netinfo.cfg file, as per a post here by Massimo from 15-Aug-2007.
    So the load network card line looks like this:
    LOAD B57 NAME=B57_1_EII_EII FRAME=Ethernet_II SLOT=10019 Speed=AUTO
    RxBuffers=200 Jumbo=9000
    But when I look in Monitor > LAN/WAN Drivers the Jumbo Packet Size
    (bytes) still reads 0. So, I don't think I'm getting Jumbo frames happening.
    I've also set the following:
    TCP delayed acknowledgement =on
    tcp nagle algorithm=on
    tcp minshall algorithm=on
    set tcp maximum inital receive window = 64
    and in startup.ncf
    set maximum physical receive pacet size = 1800
    Can anyone help me figure this out?
    Thanks,
    Doug

    Massimo Rosen wrote:
    > Hi,
    >
    > Doug wrote:
    >> I am using iSCSI for backup to disk. The target is SUSE 10 and initiator
    >> is NW 6.5 sp7. The speed isn't so great, so I'm trying to make sure I've
    >> got Jumbo frames setup properly. I've added the switch Jumbo=9000 to my
    >> netinfo.cfg file, as per a post here by Massimo from 15-Aug-2007.
    >>
    >> So the load network card line looks like this:
    >>
    >> LOAD B57 NAME=B57_1_EII_EII FRAME=Ethernet_II SLOT=10019 Speed=AUTO
    >> RxBuffers=200 Jumbo=9000
    >
    > That looks good. Yre you sure this is the first load line for that nic?
    >
    >
    >> Can anyone help me figure this out?
    >
    > Well, you already got the question about your switch, but what about the
    > Target? Are you sure it can really do Jumbo Frames? If all else fails,
    > take a lan trace of a tcp connection setup, and you wil see which frame
    > size is advertised by each side.
    >
    > CU,
    Yes the target is doing jumbo frames. I set the MTU to 9000, and the
    Windows box saw a good improvement on speed.
    Here's the netinfo.cfg file.
    #!VERSION=2.3
    #! --- WARNING -- WARNING -- WARNING -- WARNING -- WARNING -- WARNING ----
    #! This file was created by the Internetworking Configuration Console.
    #! It is intended to be modified ONLY by the configurator (INETCFG.NLM).
    #! Tampering with this file may cause severe malfunctioning of the system.
    #! The configurator will check for tampering and abort if it is detected.
    #!SERVERTYPE=NORMAL
    #!UIMODE=NORMAL
    #!BEGINGENLOAD
    LOAD SNMP
    LOAD BCALLSRV
    #!END
    #!BEGINTSMLOAD
    #!END
    #!BEGINBOARD DRVR=B57 NAME=B57_2_EII STATUS=ENABLED NUMPORTS=1
    DRVRTYPE=LAN VARIABLEPORTS=NO PORTPARAM=CHANNEL SLOT=10020 Speed=AUTO
    RxBuffers=200
    #!BEGINPORT NAME=B57_2_EII NUMBER=1 STATUS=ENABLED FRAMES=YES NUMLINKS=0
    MEDIA=EtherTsm WANFRAME=UNCONFIGURED
    #!REFCOUNT=1
    LOAD B57 NAME=B57_2_EII_EII FRAME=Ethernet_II SLOT=10020 Speed=AUTO
    RxBuffers=200 Jumbo=9000
    #!END
    #!END
    #!BEGINBOARD DRVR=B57 NAME=B57_1_EII STATUS=ENABLED NUMPORTS=1
    DRVRTYPE=LAN VARIABLEPORTS=NO PORTPARAM=CHANNEL SLOT=10019 Speed=AUTO
    RxBuffers=200
    #!BEGINPORT NAME=B57_1_EII NUMBER=1 STATUS=ENABLED FRAMES=YES NUMLINKS=0
    MEDIA=EtherTsm WANFRAME=UNCONFIGURED
    #!REFCOUNT=1
    LOAD B57 NAME=B57_1_EII_EII FRAME=Ethernet_II SLOT=10019 Speed=AUTO
    RxBuffers=200 Jumbo=9000
    #!END
    #!END
    #!BEGINPROTO PROTO=TCPIP STATUS=ENABLED
    LOAD Tcpip RIP=No Static=Yes LoadSharing=No Forward=No VIPASupport=No
    #!BEGINBIND STATUS=ENABLED
    BIND IP B57_2_EII_EII ADDRESS=xxx.xxx.xxx.xxx MASK=255.255.255.0
    #xxx.xxx.xxx.xxx
    #!END
    #!BEGINBIND STATUS=ENABLED
    BIND IP B57_1_EII_EII ADDRESS=xxx.xxx.xxx.xxx MASK=255.255.255.0
    #xxx.xxx.xxx.xxx
    #!END
    #!END

  • Aggregates, VLAN's, Jumbo-Frames and cluster interconnect opinions

    Hi All,
    I'm reviewing my options for a new cluster configuration and would like the opinions of people with more expertise than myself out there.
    What I have in mind as follows:
    2 x X4170 servers with 8 x NIC's in each.
    On each 4170 I was going to configure 2 aggregates with 3 nics in each aggregate as follows
    igb0 device in aggr1
    igb1 device in aggr1
    igb2 device in aggr1
    igb3 stand-alone device for iSCSI network
    e1000g0 device in aggr2
    e1000g1 device in aggr2
    e1000g2 device in aggr3
    e1000g3 stand-alone device of iSCSI network
    Now, on top of these aggregates, I was planning on creating VLAN interfaces which will allow me to connect to our two "public" network segments and for the cluster heartbeat network.
    I was then going to configure the vlan's in an IPMP group for failover. I know there are some questions around that configuration in the sense that IPMP will not detect a nic failure if a NIC goes offline in the aggregate, but I could monitor that in a different manner.
    At this point, my questions are:
    [1] Are vlan's, on top of aggregates, supported withing Solaris Cluster? I've not seen anything in the documentation to mention that it is, or is not for that matter. I see that vlan's are supported, inluding support for cluster interconnects over vlan's.
    Now with the standalone interface I want to enable jumbo frames, but I've noticed that the igb.conf file has a global setting for all nic ports, whereas I can enable it for a single nic port in the e1000g.conf kernel driver. My questions are as follows:
    [2] What is the general feeling with mixing mtu sizes on the same lan/vlan? Ive seen some comments that this is not a good idea, and some say that it doesnt cause a problem.
    [3] If the underlying nic, igb0-2 (aggr1) for example, has 9k mtu enabled, I can force the mtu size (1500) for "normal" networks on the vlan interfaces pointing to my "public" network and cluster interconnect vlan. Does anyone have experience of this causing any issues?
    Thanks in advance for all comments/suggestions.

    For 1) the question is really "Do I need to enable Jumbo Frames if I don't want to use them (neither public nore private network)" - the answer is no.
    For 2) each cluster needs to have its own seperate set of VLANs.
    Greets
    Thorsten

  • Routers: What Are Jumbo Frames and why do I need them?

    Some routers' specs specifically mention that they handle jumbo frames (with a number like 9K). I have a network with 2 iphones, two ipads, 4 computers, two networked Blu-Ray players, and 3 computers, all of which are operating simultaneously a lot of the time.
    Some other companies seem to be using the fact that they support jumbo frames as part of their selling points. How do they help?
    I asked Cisco Chat support about the RVS4000 and whether it supported them on both the WAN and the LAN. They said not on the WAN. They also said "
    It appears under the L2 Switch tab you can input a Max Frame type.....
    I don't see anything that actually says jumbo frames but I believe you can put in a value.....
    after the device is setup you can navigate to the L2 Switch option and it has a Max Frame value"
    I'm not sure whether this router supports jumbo frames or not. I have a short list of wired gigabit routers that I'm considering for purchase and the RVS4000 is on the list.
    I need to learn more about this topic so any help or pointers to stuff to read would be greatly appreciated.

    Thanks so much for the info. I read virtually all of it. The Jumbo Frames thing sounds very tricky - and possibly detrimental. I'll have to see if Time Warner Roadrunner supports them and at what sizes. Other than for really big file transfers between machines on my network (which I don't do that often) it sounds like jumbo frames isn't going to do much for me.
    It also looks like the RVS4000 is not what I want. The smallnetbuilder review was a very useful one-although it's 4 yrs old, it's still likely mostly valid.
    I do some gaming at times and it sounded like the adjusting of frame sizes until all the devices in the path are the same can cause unacceptable latency. Now it seems that no matter which gigabit router I choose, I need to be sure I get one where I can disable the major frames process, and maybe enable it when I want to do hard drive backups across the network. Welcome to the gigabit ethernet world I guess.
    The RV220W sounds like a nice machine, but is a lot more machine than I think I need for my network. I read a very detailed review of it on Amazon at:  http://www.amazon.com/gp/cdp/member-reviews/A2BBGBR6ARRJQO/ref=cm_pdp_rev_more?ie=UTF8&sort_by=MostRecentReview#R2SCJUQOKY7EN
    It also sounds like it's more complex to set up than I would like to tackle. I'm a retired electrical engineer but definitely not a skilled IT person, so plug and play simplicity is important. I understand just enough to get in trouble.
    Thanks again for the links. Much appreciated.

  • Jumbo Frames support on G4 Powerbook 1.67Ghz??

    Hi - I have purchased a Thecus Nas and a gigabit switch, both support Jumbo frames. I want to use the NAS to stream video and hoped I could enable Jumbo Frames on all network devices. On my Powerbook internal NIC the Jumbo frames option is greyed out. Should I be able to configure Jumbo frames on my internal NIC? If so what am I doing wrong?
    Many Thanks in advance,
    Alan

    See the following article:
    Mac OS X 10.3 and later: "Jumbo" packet size is dimmed
    http://docs.info.apple.com/article.html?artnum=107962
    It seems that this important Gigabit Ethernet feature is not included with most Mac NICs.

Maybe you are looking for