No jumbo frames between 4500-X and Force10

Hi,
We have just installed new Cisco 4500-X 10Gbe SFP+ switches.
We have Dell Blade Chasis with Force 10 MXL blade switches.
We are testing/preparing the environment before our new Dell compellent hybrid arrays arrive, but we face a problem with Jumbo frames between the Cisco 4500-X and the Dell Force10.
When I do a ping -L from the blade server to a host connected to the Cisco 4500-X anything bigger then 1472 bytes seems to get dropped.
When performing a ping between servers connected to the 4500-X I can use jumbo frame sizes like 9000 without issues
When performing a ping between servers in the blade chassis I can use jumbo frame sizes like 9000 without issues
Now we also have a pair of Cisco 3750X switches that are currently being used for Dell Equallogic 1Gbe SAN and they are connected to the same Force10 switches as the 4500-X are and I have created the exact same LACP port-channels between the Force10/3750X as for the Force10 4500-X. Jumbo packets to the 3750X is working fine but for the 4500-X it is not.
I have tried connecting the switches simply on access port level, creat a vlan trunk and create a portchannel with trunking but none of the solutions seem to work, in every situation packets above 1472 are dropped... at least they dont arrive at the destination.
On every port of the 4500-X the MTU is set to 9198, the vlan each port is in is set to 9198 and the port-channel is set to 9198
System MTU can only be set to 1550 so that is on default 1500 altough I tried setting it to 1550 but that didnt make any difference ofcourse.
The 4500-X is running version 03.04.04 SG / 15.0(1sr) SG10
The Force10 is running 9.6.0.0
Any help is appriciated

Sorry for the delay , i have bought the 3064-32T , it seemed more cost effective as the transceivers are so expensive and it has more ports too.

Similar Messages

Trunk between 4500-X and 4507R not working

Hi all,
i have got a new switch (4500-X) which i would like to connect to our existing 4507R switch. So i configured trunk ports on each of them, like i do this with all of my other access switches. I tried so many things, but i cant reach vlans from the new switch and iam totaly out of ideas
Iam quite sure that i make a verry dump config issue, but i cant fine the fault in my config...hopyfully someone could please help me? I hope this is the right information you need.
Many many Thanks!
The "OLD" Switch (4507R):
OLD#sh ver
Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500-IPBASEK9-M), Version 12.2(54)SG, RELEASE SOFTWARE (fc3)
OLD#sh run int gi3/6
Building configuration...
Current configuration : 149 bytes
interface GigabitEthernet3/6
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
end
OLD#sh int gi3/6 switch
Name: Gi3/6
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
OLD#sh int gi3/6 trunk
Port        Mode             Encapsulation Status        Native vlan
Gi3/6       on               802.1q         trunking      1
Port        Vlans allowed on trunk
Gi3/6       1-4094
Port        Vlans allowed and active in management domain
Gi3/6       1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999
Port        Vlans in spanning tree forwarding state and not pruned
Gi3/6       1
The "NEW" Switch (4500-X):
NEW#sh ver
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSALK9-M), Version 03.04.00.SG RELEASE SOFTWARE (fc3)
NEW#sh run int te1/32
Building configuration...
Current configuration : 94 bytes
interface TenGigabitEthernet1/32
switchport mode trunk
end
NEW#sh int te1/32 switchport
Name: Te1/32
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
NEW#sh int te1/32 trun
Port        Mode             Encapsulation Status        Native vlan
Te1/32      on               802.1q         trunking      1
Port        Vlans allowed on trunk
Te1/32      1-4094
Port        Vlans allowed and active in management domain
Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999
Port        Vlans in spanning tree forwarding state and not pruned
Te1/32      1-3,9-10,20,23-24,26,32-40,66-68,95-101,110-111,120,200,500-501,510,995-999

Hi!
Yes, sure:
######### OLD ##########
OLD#sh spanning-tree vlan 3
VLAN0003
Spanning tree enabled protocol ieee
Root ID    Priority    32771
             Address     000c.30b1.7540
             This bridge is the root
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    32771 (priority 32768 sys-id-ext 3)
             Address     000c.30b1.7540
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
             Aging Time 300 sec
Interface           Role Sts Cost      Prio.Nbr Type
Gi3/5               Desg FWD 4         128.133 P2p
Gi3/6               Desg FWD 4         128.134 P2p
Gi4/2               Desg FWD 4         128.194 P2p
Gi4/3               Desg FWD 4         128.195 P2p
Gi5/1               Desg FWD 4         128.257 P2p
Gi5/3               Desg FWD 4         128.259 P2p
Gi5/4               Desg FWD 4         128.260 P2p
Gi5/5               Desg FWD 4         128.261 P2p
Gi5/6               Desg FWD 4         128.262 P2p
Gi6/1               Desg FWD 4         128.321 P2p
Gi6/2               Desg FWD 4         128.322 P2p
Gi6/3               Desg FWD 4         128.323 P2p
Gi6/5               Desg FWD 4         128.325 P2p
Gi6/6               Desg FWD 4         128.326 P2p
Gi7/1               Desg FWD 4         128.385 P2p
Gi7/2               Desg FWD 4         128.386 P2p
Gi7/4               Desg FWD 4         128.388 P2p
Gi7/5               Desg FWD 4         128.389 P2p
Gi7/6               Desg FWD 4         128.390 P2p
Po3                 Desg FWD 3         128.643 P2p
Po6                 Desg FWD 3         128.646 P2p
Po7                 Desg FWD 3         128.647 P2p
OLD#sh int gi3/6
GigabitEthernet3/6 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet Port, address is 0016.9dd4.1fe7 (bia 0016.9dd4.1fe7)
Description: trunk core NEU
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX
Media-type configured as SFP connector
input flow-control is on, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 9000 bits/sec, 16 packets/sec
     809802 packets input, 156747108 bytes, 0 no buffer
     Received 809180 broadcasts (809157 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     77368681 packets output, 5652973144 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
######### NEW ##########
NEW#sh spanning-tree vlan 3
VLAN0003
Spanning tree enabled protocol ieee
Root ID    Priority    32771
             Address     000c.30b1.7540
             Cost        4
             Port        32 (TenGigabitEthernet1/32)
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority    32771 (priority 32768 sys-id-ext 3)
             Address     f872.ead8.4400
             Hello Time   2 sec Max Age 20 sec Forward Delay 15 sec
             Aging Time 300 sec
Interface           Role Sts Cost      Prio.Nbr Type
Te1/32              Root FWD 4         128.32   P2p
NEW#sh int ten 1/32
TenGigabitEthernet1/32 is up, line protocol is up (connected)
Hardware is Ten Gigabit Ethernet Port, address is f872.ead8.441f (bia f872.ead8.441f)
Description: trunk sw99rz1-1-1
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX
input flow-control is on, output flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 13000 bits/sec, 18 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
     365663 packets input, 26752705 bytes, 0 no buffer
     Received 365496 broadcasts (363520 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     3843 packets output, 745065 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
Thanks a lot!
tobias

Dual nic NAS and Jumbo Frame

I am posting this on the server area because I doubt I am going to get an answer anywhere else.
I have a linux based NAS running netatalk and avahi (afp server and bonjour) with two nics and I have a brand new Mac Pro with two NICS. What I want to do is run a crossover cable between the NAS and the Mac Pro in addition to both being plugged into the normal network. The normal network would have 1500 byte mtu so my internet performance and all of the various vintages of print servers work ok. The dedicated network would have jumbo frames. As we get more Mac Pros, we would add a switch and more machines to this secondary jumbo frame network.
That in theory should work fine (I have done it with other operating systems). My quandary is how to get the Mac to always connect to the NAS via the Jumbo nic and not through the other nic? The Mac learns of the server via Bonjour, so how do I tell it to prefer the "appearance" of the server on the jumbo NIC vs the appearance on the normal network. I know with WINS or DNS I can override the name resolution with a LMHOSTS or hosts file entry, can I do the same with Bonjour?
Thanks for any help or any pointers in the right direction!

I think you are misguided in your assumption that I am not intimately familiar with TCP and don't know what I am talking about.
TCP does not "negotiate" MSS, it advertises the MSS of each side to the remote in the 3 way handshake. It is perfectly acceptable to have asymetric MSS values. TCP does NOT NEGOTIATE a common MSS size. On a LAN, this will result in a functional communication. UDP however does not have such mechanisms and will fail.
TCP will also not function properly in the scnario of my local workstaion with jumbos enabled communicating with a distant endpoint that also has jumbos enabled across a transit network that does not support the maximum MSS used by one of the end stations. For giggles let's say the far end is FDDI and has 4k frame size. Our transit does not support frame sizes larger than the "natural" frame size of 576 bytes. We will use a 4k frame size from me to the remote and a 9k from the remote to me. If the remote sends to me it can use the full 4k MSS of token ring because its less than my MSS. In the reverse my workstation would send 4k frames back to the token ring station. Successful communication would then depend on path MTU and intermediary routers to send ICMP type 3 code 4 messages to signal back to our end stations to reduce our MSS (assuming the DF bit is set on our traffic or the transit router is incapable of fragmentation).
This is perhaps a bit of a flippant example in that nobody would be running FDDI or Token ring anymore, but random entities on the internet will run jumbo frame and perhaps some other l2 technology we aren't familiar with.
Did you ever deal with someone on a token ring segment trying to hit 3Com's web site when it was fddi or token ring? I have on several occasions. I also see this with VPNs all the time. Cisco's genius recomendation is to reduce your MSS on your server as some of their products don't support PMTU. I have had a Cisco <-> Juniper VPN where transfers worked one way because the Juniper would silently strip the DF bit from the packet and fragment it and the Cisco router (38xx) wouldn't do the same in the reverse direction. I also went through **** with the Nortel Contivity VPN devices while they sorted out what to do with the whole MTU negotiation issue.
I have spent many hours of my life pouring through sniffer captures because of mismatched MTUs. Let's not forget the old days of FDDI backbones with ethernet segments bridged across them and FDDI attached servers... mismatched buffers... no thanks.
I therefore don't want to waste my time troubleshooting some bizzare networking issue when there is a perfectly valid way of solving the issue for absolutely minimal expense. I am moving large files here (certainly large enough to get well out of TCP slow start), we easily saturate the full gig link minutes at a time and a saturated gigabit link at standard frame size is inefficient due to the interpacket gap which is locked at 96 bit times for ethernet and the 40 bytes of TCP/IP header plus whatever application payload is prepended per packet on each link. Cutting the number of TCP/IP headers and (probably more importantly since most decent nics do checksum offload these days) application layer headers also reduces load on both client and server.
On large sequential bulk data transfers jumbo frame effectively increases performance and reduces overhead. Period. I have implemented it from the early days of Alteon hardware in Sun servers through Juniper EX products last week. Every iSCSI implementation I run into is jumbo frame based for those exact reasons.
That being said, I don't need to restrict anything. All I want to do is to override bonjour/mDNS for this particular host such that the Pro always communicates over the jumbo segment. This is easily accomplished in windows with an LMHOST entry or in a unix environment with a HOSTS file entry. Is there some way to override bonjour from the client side? I'm ok even statically defining the services presented by bonjour on this host.
I am also willing to force all bonjour requests through a DNS server, however Apple doesn't have any decent documentation on how this is accomplished in an enterprise environment.

Airport Utility on iMac with Jumbo Frames can't read Airport configuration

My 24" iMac is connected to a Netgear switch (GS608 rev2) that supports Ethernet jumbo frames. My GigE Airport Extreme base station is also connected to the Netgear switch and is acting as a gateway for my cable modem connection. Here's the rough wired layout:
iMac--Netgear--Airport--Cable Modem
The iMac has jumbo frames enabled (MTU=9000) and can communicate fine to the Internet and other devices on my local LAN (including a Netgear NAS box also with Jumbo frames enabled).
Airport Utility on the iMac starts and discovers my 3 Airports (1 extreme + 2 express) but if I double click on one of them to configure it, the window says "Reading the AirPort Extreme configuration..." and hangs there never bringing up the setup screen. Printer jobs to the shared USB printer that worked before Jumbo Frames were enabled on the iMac are also failing. The same happens for the 2 Airport Express as well although I can still steam Airtunes music to them.
Any ideas what might be wrong ? Do the airports have problems negotiating with jumbo frame enabled Macs ?
My wireless MBA with std MTU can still communicate fine with the Airports.
Thanks,
E
Message was edited by: Gaijin Kuma

None of Apple's Airports support jumbo frames.
The networking chip that Apple uses in the Airport Extreme has the capability to support jumbo frames, but it isn't an option that Apple has chosen to expose to the user. So you can't reliably use the Airports on a jumbo frame enabled subnet.
The likely reason the Internet is still working is that, unless your uploading, it's unlikely the iMac sent a packet in excess of 1500 bytes to the Airport. The Airport is always sending 1500 byte packets which your iMac wold receive fine regardless of what the MTU was set (well, unless it was set below 1500).
Some people do report success but I would be wary of their results, they may not have down/upped the interface so the MTU may have been listed as changed, but not yet actually changed to the larger MTU. No-one has actually posted a tcpdump -e capture showing an Airport actually sending/receiving packets in excess of 1500 bytes.
Some more links to this discussion topic-
http://discussions.apple.com/thread.jspa?threadID=1085469
http://discussions.apple.com/thread.jspa?threadID=1222397
http://www.smallnetbuilder.com/content/view/30188/96/

KT6 FISR (5188) - Jumbo frames support

Hi,
I have the KT6 FISR motherboard up and running with a gigabit network (after a dodgy network cable dropped my speed to 100Mbps ) and was wondering if anyone knew whether it supports jumbo frames. Have searched the spec sheets and also broadcom's website without any joy. There are no settings in the 'configure' section of the hardware.
Anyone?
Mike

Taken from the netgear site - http://kbserver.netgear.com/kb_web_files/n101539.asp:
What is the Jumbo Frame Supported by Switches and Adapters?
Ethernet traffic moves in units called frames. The maximum size of frames is called the Maximum Transmission Unit (MTU). When a network device gets a frame larger than its MTU, the data is fragmented (broken into smaller frames) or dropped. Historically, Ethernet has a maximum frame size of 1500 bytes, so most devices use 1500 as their default MTU. An Ethernet packet larger than 1500 bytes is called a Jumbo Frame.
An Ethernet frame uses a fixed-size header. Since the header contains no user data, it's overhead. It is more efficient to transmit a larger frame — the overhead-to-data ratio is better.
The performance problem arises when the MTU of one device is different than another. Indeed, casual changes to MTU to "optimize performance" are likely to have the opposite effect. See MTU, Partial Loss of Internet Connection, and Performance for an explanation of MTU problems — before considering the effects of Jumbo Frames. Also note that Jumbo Frames only help LAN performance, traffic leaving your network to the Internet is limited to packets of 1500 bytes.
With Jumbo Frames, much larger frames than the Ethernet standard of 1500 bytes are supported. If most of your local network devices and applications can be configured for the same Jumbo Frame size, your network may benefit from large packets, little fragmentation, and little overhead. However, if there are many applications and devices on your network that already limit frames to less than 1500 bytes, Jumbo Frames might decrease your performance slightly.
So with a switch and NAS both supporting jumbo frames it would have been good to have used them (or is that being too greedy? )

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 within Solaris 10 zones and multiple interfaces...

We have Jumbo Frames working in the Global Zone, and have the MaxFrameSize=3,3,3 etc...
We also have our AGGR's built correctly and defined aggr1:1 and aggr1:2
the problem is on boot-up, if all the name files (hostname.aggr1 and hostname.aggr1:1) are defined in the /etc directory, then you can't start the zones....?
and if you place the files in the /export/zones/<machinename>/root/etc/ directory, than the interfaces do not start-up automatically..... ?
So If I want all the interfaces in the global zone to be seen by the other zones, and for the interfaces to come live when the zones are booted.... where do the hostname.interface files live....???

Darren:
I understand where you're coming from from a technical perspective. But there is a way you could work around it.
For argument's sake, zones a+b with e1000g0 - e1000g3
From an implementation perspective, what's to stop you from:
e1000g0 / e1000g1 shared between all
e1000g2 plumbed at global, only assigned to zone a.
e1000g3 plumbed at global, only assigned to zone b.
You can certainly have an empty interface file (i.e. cp /dev/null /etc/hostname.e1000g2 ; cp /dev/null /etc/hostname.e1000g3). The interface will plumb but have no IP information configured.
This doesn't give truly exclusive interfaces to either zone, but it operates effectively as though it were.
Warning: I haven't actually tested this, but I see no reason that it wouldn't work.

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

My SD video keeps jumping between the upper and lower frames. So the video starts frame blending and blurring in and out.

My SD video keeps jumping between the upper and lower frames. So the video starts frame blending and blurring in and out. The sequence settings are set to
Editing Mode: DV NTSC 29.97 frames/second.
Pixel Aspect Ration: D1/DV NTSC (0.9091)
Fileds: Lower Field First
Display Format: 30fps Non-Drop-Frame Timecode
720 x480

What is the source of your video, and exactly what is inside your video?
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download

FTTH connection proper MTU Size and Jumbo frames

I've recently moved to a ISP that provides a 4mbps connection through FTTH(Single OFC). There is a EPON ONU in my premise from which a RJ-45 lan cable is connected to my Intel DH67CL1 board based PC. manual says, the NIC is a gigabit ethernet card. I tried setting MTU of 8996 and I can ping and browse fine. But, I'm totally in dark whether this value is optimum and works flawlessly browsing sites. How to find and set the proper MTU for a fibre network like this? Is the value correct?
I tried like this decreasing mtu value:
ifconfig eth0 mtu 8997
SIOCSIFMTU: Invalid argument
then,
ifconfig eth0 mtu 8996
^^^ No error message and it seems accepting.
BTW, from arch wiki, I saw that the driver module(e1000e which is used here) used by NIC have some bug report filed wr.to Jumbo frame. Am I doing things correctly? Earlier MTU was at default 1500. Please guide. thank you
Some drivers will prevent lower C-states
Some kernel drivers, like e1000e will prevent the CPU from entering C-states under C3 with non-standard MTU sizes by design. See bugzilla #77361 for comments by the developers.
https://wiki.archlinux.org/index.php/Ju … mbo_frames

yeah, i actually talked to support and they told me the same thing. just another example of misleading information from Linksys as here is what the manual and the help page say:
MTU
MTU is the Maximum Transmission Unit. It specifics the largest packet size permitted for Internet transmission. Select Manual if you want to manually enter the largest packet size that will be transmitted. The recommended size, entered in the Size field, is 1500. You should leave this value in the 1200 to 1500 range. To have the Router select the best MTU for your Internet connection, keep the default setting, Auto.
no where in that description does it say that 1500 is the maxmium.
because this is also a gigabit switch, one would expect that jumbo frame support is not out of the realm of possibility. as a point of reference any other $50 (or less) gigabit switch supports this, but that's what i get for expecting too much from Linksys.
thanks for the info.

Catalyst 3750 and jumbo frames

We're looking to implement a gigabit segment with a 3750 switch, with the latest apple imac G5 clients connected and and an xserve G5 connected doing link aggregation using a 4 port smalltree NIC.
Although the Xserve supports jumbo frames i believe the imac NICs DON'T support jumbo frames although the operating system does( the imac NICs DO support 1000T ) Ideally we'd want the 3750 switch to be configured for Jumbo frames. The 3750 switch we've chosen has all ports of 10/100/1000T with the SMI, so all ports will have the MTU set at 9000 if we enable jumbo.
Although the Xserve will be fine, i'm worried about traffic that ingresses from the xserve and egresses out to a 10/100/1000 port to which an imac is connected which i believe does not support Jumbo frames. What are the issues in terms of connectivity and dropped packets for an imac G5 connected to a 3750 ?
seeing as the MTU is set globally and all our ports are gigabit, and machines will be connected to these ports that don't support jumbo but are advertised as having 'gigabit capability'
Sorry if these sounds like an incoherent rant, but i needed to provide as much info as possible. Help much appreciated

just to add, in comparison HP gigabit switches can do jumbo vlan on a per vlan and per port basis it's a shame the 3750 can't do that

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

SRW2048 and Jumbo frames

I have a Cisco SRW2048 (Firmware 1.2.2d, boot 1.0.0.05) on which I have enabled jumbo frames but yet when I attempt with a Windows 2003 server to ping the mgmt IP of this switch with a frame over 1472 (ping -f -l 1472 w.x.y.z) I get a response of "Packet needs to be fragmented". The server is connected to a Netgear gig switch (GS724AT) that has jumbo frames enabled and working as I can talk to other devices using jumbo frames. Attempts to access the SRW2048 switch fail on packets larger than 1472. I have also attempted a Windows 7 box using jumbo frames to no success. The Windows 7 box works when connected to the Netgear switch but when I move the connection back to the SRW2048, jumbo frames on the windows box stop working.
Any help or suggestions would be appreciated.
Thanks.
David

On the SF-300 and SG-300 for Jumbo to work the Enable Jumbo checkbox must be unchecked. Either I don't understand Cisco logic or it's a bug in the GUI.

T61 and Intel 82566mm Jumbo Frame Capable?

I'm trying to achieve the near 100MB/sec performance with my NAS but cannot seem to get past 15MB/sec with 25MB/sec bursts on my gigabit LAN. Do I need to enable jumbo frames for this to work? If so, is the Intel 82566 gigabit NIC even capable of jumbo frames or is this an OS dependent issue? In addition, does my switch also need to have jumbo frame support or is it built into gigabit? And lastly, how would this adversely affect my 802.11n clients connecting to my server - are jumbo frames something 802.11n clients capable of?
T61_Wide | Model No. 7662 - CTO
Core 2 Duo T7250 | 2GB OCZ DDR2-800
82566MM Gigabit | 4965AGN Centrino Pro

check BIOS / configuration and see if INTERNAL LAN is enbaled or disabled. i had this happen when my wireless and lan were not working. fixed it in bios.
T7600, T60p - 2GB - 2.33GHZ - 100GB

X200 The gap between the LCD and frame is unacceptable

Hi, My roommate and I received x200 last week and both of our x200 have the same problem. The gap(1 mm) between the LCD and frame is unacceptable (the left and right handside and especially the lower side of the frame) and when you touch it, it feels like a plastic toy. I compare it with x61, x61s, T61 which belongs to my friends and they do not have that problem.
I am not sure whether this is a serious problem or not and whether we can fix it by ourself.
Thank you for reading and replying.

I took some photos and I can not find how to attach them.
Well, about this problem, Lenovo asked me to go to some business partner to look for technician and the technician said that is not a techincal problem and it is engineering problem... They can not fix it.
And my friend told me that this is a normal problem maybe because lenovo change the material of the inside part of thinkpad.
So, I decided to return it.

No jumbo frames between 4500-X and Force10

Similar Messages

Maybe you are looking for