22-8
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 22 System
Connection Failure After ESX Reboot
Recovering Lost Connectivity Due to MTU Mismatch
Use this procedure to recover lost connectivity due to an MTU mismatch between the physical NIC and
the VMware kernel NIC after an ESX reboot.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
• You are logged in to the CLI in EXEC mode.
• To verify the ESX MTU settings for corresponding PNICs, use the ESXcfg-nics -l command.
Note Use vemcmds only as a recovery measure and then update the MTU value in the port profile
configuration for system uplinks or in the interface configuration for non-system uplinks.
SUMMARY STEPS
1. config t
2. module vem module_number execute vemcmd show port port-LTL-number
3. module vem module_number execute vemcmd set mtu size ltl port-LTL-number
DETAILED STEPS
Step 4
show port-profile [brief | expand-interface |
usage] [name profile-name]
Example:
switch(config-port-prof)# show port-profile
name AccessProf
(Optional) Displays the configuration for verification.
Step 5
copy running-config startup-config
Example:
switch(config-port-prof)# copy running-config
startup-config
(Optional) Saves the running configuration persistently
through reboots and restarts by copying it to the startup
configuration.
Command Description
Command Description
Step 1
config t
Example:
switch# config t
switch(config)#
Enters global configuration mode.
Step 2
module vem module_number execute vemcmd show
port port-LTL-number
Displays the port configuration including the LTL number
needed for Step 3.