Recovering Lost Connectivity Due To Mtu Mismatch - Cisco Nexus 1000V Troubleshooting Manual

Connection Failure After ESX Reboot
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
Command
Step 4
show port-profile [brief | expand-interface |
usage] [name profile-name]
Example:
n1000v(config-port-prof)# show port-profile
name AccessProf
Step 5
copy running-config startup-config
Example:
n1000v(config-port-prof)# copy running-config
startup-config

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:
•
•
Note
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Command
Step 1
config t
Example:
n1000v# config t
n1000v(config)#
Step 2
module vem module_number execute vemcmd show
port port-LTL-number
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
21-8
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.
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.
config t
module vem module_number execute vemcmd show port port-LTL-number
module vem module_number execute vemcmd set mtu size ltl port-LTL-number
Description
(Optional) Displays the configuration for verification.
(Optional) Saves the running configuration persistently
through reboots and restarts by copying it to the startup
configuration.
Description
Enters global configuration mode.
Displays the port configuration including the LTL number
needed for Step 3.
Chapter 21 System
OL-28795-01