VMware VSHIELD MANAGER 4.1.0 UPDATE 1 - API Manual do Utilizador Página 153

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
Vista de página 152
VMware, Inc. 153
Appendix C Troubleshooting
To troubleshoot if broadcast packets are being received but unicast packets are being dropped
1Run/opt/vmware/vslad/fence-util setSwitchMode 1onallESXhostsinquestion.Thiscommand
instructsthevshdmoduletobroadcastallfencedpackets.
Ifafterrunningthecommandonallhoststhingsstartworking,mostofthetimes,thismeansthattheissue
lieswithmirrorvirtualmachinesbecausemirrorvirtualmachinesarerequired
tobeconfiguredcorrectly
fortheunicastpacketdeliverytowork.
Formoreonfence-util,see“DetailsofthefenceutilUtility”onpage 153.
2OneachESXhost,checkthemirrorvirtualmachine’sNICstomakesurethatatleastoneNICisconnected
tothevSwitchtowhichthesevirtual
machinesareconnected.
3ConfirmthatthefilterentriesforthisNICinthemirrorvirtualmachinesVMXfilesarecorrect.Allofthe
entriesforthatvSwitchshouldhavethesameLanId?value.
Afterfixingtheproblem,resetthemodeto0byrunning/opt/vmware/vslad/fence-util
setSwitchMode 0.
4Confirmthatthepacketsare
reachingtheotherESXhost.Ifthemirrorvirtualmachinesare
misconfigured,packetsaredroppedatthedestinationESXhost,notbythesourcehost.
Ifstillthingsarenotworking,thiswouldmostlikelymeanthattheunicastswitchingisbroken
somewhereonthephysicalboxesinthenetwork.This
israrebecauseifbroadcastpacketsarereaching,
thatmeansphysicalconnectivityispresentbetweenthevirtualmachinescommunicatingwitheachother.
Ifbroadcastisworkingandunicastisnotworkingevenafterputtingallvshdmodulesinbroadcastmode
usingfenceutils,thenproblemsmaybepresentinthephysical
networkforsuchunicasts.
ThereisalsoachanceofmorethanonevShieldManager,PortGroupIsolation,vCenterinstallationson
thesamenetwork.Inthatcase,someofthehostkeyMACaddressesmaygetduplicatedwithinthesame
physicalnetwork.Becauseofthis,thebroadcasttrafficmayworkfine,
buttheunicasttrafficmayreach
thewronghostsbecausethephysicalswitchesonthenetworkmaylearnaboutsameMACfromtwo
differentplaces.
To troubleshoot if no packets are being received and broadcasts are being dropped
1ConfirmthatthetwoESXhostsarepresentonacommonphysicalnetworkandonthesameVLAN.
2Inthecaseoflegacyswitches,confirm
thatthesameportgroupisconnectedtothesamenamedvswitch
onalltheESXhostsinquestion.
3ConfirmthattheNICconnectedtothesevSwitchesconnecttothesamephysicalnetwork.
4Run/opt/vmware/vslad/fence-util infocommandmultipletimesonallESXhoststoseeifany
droppedpacketcountersareincremented.
This
modulealsoshowsdroppedpacketnumbersforunfencedpacketsenteringintofencedvNICs.This
wouldmeanthatalltheotherbroadcastsonthenetworkaredroppedwhentheyreachthefencedvNIC.
LookforFenced From VMandFenced To VM counters.
5Isolatethepointwherepacketsaregettingdroppedbyrunningcapturesonthe
ESXinterfaceatbothends.
IncaseswherepacketsarecomingoutofsourceESXbutarenotreachingthedestinationESX,thereare
rarechancesthatsomeintelligentdeviceinbetweenmaybedroppingthesepacketsbecauseofan
unknownethtypeinthepackets.
Details of the fence-util Utility
Log Levelindicatesdebugloglevel.
HostkeyistheconfiguredhostID.Thereisaprintingmistakeinthefenceutilprogram whereitsattachinga
0attheendofthehostid.hostidof0x30meanshostId3.
Configured LAN MTUsrefertotheexplicitelysetMTUvaluesviavsdh.
Vista de página 152
1 2 ... 148 149 150 151 152 153 154 155 156 157 158 ... 161 162

Comentários a estes Manuais

Sem comentários