Jumbo Frames
ExtremeWare XOS 11.3 Concepts Guide
117
configure jumbo-frame-size <framesize>
The jumbo frame size range is 1523 to 9216. This value describes the maximum size of the frame in
transit (on the wire), and includes 4 bytes of CRC plus another 4 bytes if 802.1Q tagging is being used.
Set the MTU size for the VLAN, using the following command:
configure ip-mtu <mtu> vlan <vlan_name>
Next, enable support on the physical ports that will carry jumbo frames using the following command:
enable jumbo-frame ports [all | <port_list>]
NOTE
The BlackDiamond 8800 family of switches and the Summit X450 switch enable or disable jumbo frames on the
entire switch; the system returns an error message if you attempt to enable jumbo frames on specified ports.
Path MTU Discovery
NOTE
The BlackDiamond 8800 family of switches and the Summit X450 switch do not support the router specification for
path MTU discovery.
Using path MTU discovery, a source host assumes that the path MTU is the MTU of the first hop
(which is known). The host sends all datagrams on that path with the “don’t fragment” (DF) bit set,
which restricts fragmentation. If any of the datagrams must be fragmented by an Extreme switch along
the path, the Extreme switch discards the datagrams and returns an ICMP Destination Unreachable
message to the sending host, with a code meaning “fragmentation needed and DF set”. When the
source host receives the message (sometimes called a “Datagram Too Big” message), the source host
reduces its assumed path MTU and retransmits the datagrams.
The path MTU discovery process ends when one of the following is true:
●
The source host sets the path MTU low enough that its datagrams can be delivered without
fragmentation.
●
The source host does not set the DF bit in the datagram headers.
If it is willing to have datagrams fragmented, a source host can choose not to set the DF bit in datagram
headers. Normally, the host continues to set DF in all datagrams, so that if the route changes and the
new path MTU is lower, the host can perform path MTU discovery again.
IP Fragmentation with Jumbo Frames
NOTE
The BlackDiamond 8800 family of switches and the Summit X450 switch do not support fragmentation of any IP
packets they forward.
Summary of Contents for ExtremeWare XOS 11.3
Page 20: ...Contents ExtremeWare XOS 11 3 Concepts Guide 20...
Page 25: ...1 Using ExtremeWare XOS...
Page 26: ......
Page 38: ...ExtremeWare XOS Overview ExtremeWare XOS 11 3 Concepts Guide 38...
Page 58: ...Accessing the Switch ExtremeWare XOS 11 3 Concepts Guide 58...
Page 146: ...Configuring Slots and Ports on a Switch ExtremeWare XOS 11 3 Concepts Guide 146...
Page 218: ...Status Monitoring and Statistics ExtremeWare XOS 11 3 Concepts Guide 218...
Page 240: ...Virtual LANs ExtremeWare XOS 11 3 Concepts Guide 240...
Page 248: ...Virtual Routers ExtremeWare XOS 11 3 Concepts Guide 248...
Page 278: ...Access Lists ACLs ExtremeWare XOS 11 3 Concepts Guide 278...
Page 288: ...Routing Policies ExtremeWare XOS 11 3 Concepts Guide 288 entry deny_rest if then deny...
Page 344: ...Security ExtremeWare XOS 11 3 Concepts Guide 344...
Page 393: ...2 Using Switching and Routing Protocols...
Page 394: ......
Page 454: ...Spanning Tree Protocol ExtremeWare XOS 11 3 Concepts Guide 454...
Page 484: ...Extreme Standby Router Protocol ExtremeWare XOS 11 3 Concepts Guide 484...
Page 514: ...IPv4 Unicast Routing ExtremeWare XOS 11 3 Concepts Guide 514...
Page 530: ...IPv6 Unicast Routing ExtremeWare XOS 11 3 Concepts Guide 530...
Page 538: ...RIP ExtremeWare XOS 11 3 Concepts Guide 538...
Page 556: ...OSPF ExtremeWare XOS 11 3 Concepts Guide 556...
Page 566: ...OSPFv3 ExtremeWare XOS 11 3 Concepts Guide 566...
Page 589: ...3 Appendixes...
Page 590: ......
Page 640: ...CNA Agent ExtremeWare XOS 11 3 Concepts Guide 640...
Page 670: ...Glossary ExtremeWare XOS 11 3 Concepts Guide 670...
Page 698: ...Index ExtremeWare XOS 11 3 Concepts Guide 698...