==================================================================
Configuring Jumbo Frames on a Catalyst switch
==================================================================
======================================================================
Configuring Jumbo Frames on the Nexus switch
======================================================================
!— You can enable the Jumbo MTU
!— for the whole switch by setting the MTU
!— to its maximum size (9216 bytes) in
!— the policy map for the default
!— Ethernet system class (class-default).
switch(config)#policy-map type network-qos jumbo
switch(config-pmap-nq)#class type network-qos class-default
switch(config-pmap-c-nq)#mtu 9216
switch(config-pmap-c-nq)#exit
switch(config-pmap-nq)#exit
switch(config)#system qos
switch(config-sys-qos)#service-policy type network-qos jumbo
======================================================================
Enable Jumbo frames in ESX and ESXi
======================================================================
1. Enable jumbo frames on the virtual switch (set the MTU on the uplinks/physical NICs)
- For vSS (standard vSwitch) you need to use the vSphere cli. For example, this cli command will set the MTU to 9000 bytes for the vSS named “vswitch0”:
vicfg-vswitch –m 9000 vswitch0
Use “vicfg-vswitch –l” to list the vswitches and their properties - For vDS (vNetwork Distributed Switch), you can set the MTU via the vSphere Client UI. From the Networking inventory menu, select the vDS and then “Edit Settings”. Set the “Maximum MTU” to the desired MTU (e.g. 9000B is most likely for jumbo).
2. Enable jumbo frames on the vmkernel ports
- Use the esxcfg-vmknic command to delete and then add a vmkernel interface with an MTU of 9000. On ESXi, there seems to be a glitch in creating a vmkernel port on a vDS through the vcli, so the workaround is to create a vmkernel interface with MTU 9000 on a standard switch and then migrate it over to the vDS through the vSphere Client.You can get the status (name/address/mask/MAC addr/MTU) of the vmkernel interfaces via
esxcfg-vmknic -l
=====================================================================
Configuring MTU in the UCS GUI
=====================================================================
1) Configure System Classes
2) Configure the MTU – it is a QoS System Classes property
Procedure
Step 1 | In the Navigation pane, click the LAN tab. | ||||||||||||||||||||||||
Step 2 | In the LAN tab, expand LAN > LAN Cloud. | ||||||||||||||||||||||||
Step 3 | Select the QoS System Class node. | ||||||||||||||||||||||||
Step 4 | In the Work pane, click the General tab. | ||||||||||||||||||||||||
Step 5 | Update the following properties for the system class you want to configure to meet the traffic management needs of the system:
|
||||||||||||||||||||||||
Step 6 | Click Save Changes.Enabling a QoS System Class
The Best Effort or Fibre Channel system classes are enabled by default. Procedure
|
Example CLI configuration of class based policy enabling Jumbo MTU:
policy-map type network-qos system_nq_policy
class type network-qos class-platinum
mtu 9000
pause no-drop
class type network-qos class-gold
mtu 9000
class type network-qos class-fcoe
pause no-drop
mtu 2158
class type network-qos class-default
mtu 9000
system qos
service-policy type network-qos system_nq_policy
===========================================================================
Configuring Jumbo Frames on the Nexus 1000v Virtual Distributed Switch
===========================================================================
•MTU can only be configured for uplink, Ethernet type port profiles.
•CSCtk05901 If you configure MTU for an Ethernet port profile, your ESX host may generate the following error:
2010 Nov 15 04:35:27 my-n1k %VEM_MGR-SLOT3-1-VEM_SYSLOG_ALERT: vssnet : sf_platform_set_mtu: Failed setting MTU for VMW port with portID 33554475.
Creating a System Port Profile
You can use this procedure to configure a system port profile for critical ports.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•The VSM is connected to vCenter server.
•You have configured the following:
–Port admin status is active (no shutdown).
–Port mode is access or trunk.
–VLANs that are to be used as system VLANs already exist.
–VLANs are configured as access VLANs or trunk-allowed VLANs.
•A system port profile must be of the Ethernet type because it is used for physical ports. This procedure configures the Ethernet type.
•In an installation where multiple Ethernet port profiles are active on the same VEM, it is recommended that they do not carry the same VLAN(s). The allowed VLAN list should be mutually exclusive. Overlapping VLANs can be configured but may cause duplicate packets to be received by virtual machines in the network.
•Once a port profile is created, you cannot change its type (Ethernet or vEthernet).
•The MTU size you set must be less than or equal to the fixed system jumbomtu size of 9000.
For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4a).
•The MTU configured on an interface takes precedence over the MTU configured on a port profile.
For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4a).
SUMMARY STEPS
1. config t
2. port-profile type ethernet profilename
3. description profiledescription
4. switchport mode trunk
5. switchport trunk allowed vlan vlan-id-list
6. no shutdown
7. system vlan vlan-id-list
8. (Optional) mtu mtu-size
9. show port-profile [brief | expand-interface | usage] [name profilename]
10. copy running-config startup-config
Not too bad right?
– Gabe@networkdojo.net