Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 252940

Re: ESXI VLAN/Trunking

$
0
0

hello Gkeerthy,

 

thank you for your answer.

please let me answer to your answers

 

the server is 100% for testing purposes. in a production enviroment i would not use a standalone nic.

 

from my understanding

the managment port is for connecting vSpare (and other VM Products to the ESXi) - am i wrong ?

there is no "allow management groups" in the SCSI port group activated - that is the strange thing

as i understand if the Management traffic goes over the NIC with the IP 172.x.x.x on the standalone NIC then vSpare should be connected to this NIC !!! if i am disconnecting the cable from the switch port 8 than vSpare should stay connected - correct ?

 

.............

i found the Issue

and the statements in top get confirmed after i cleared up the confuzion below

 

what was happened

i have 3 nics (nic 0 and 1 are onboard nics) nic2 is standalone nic.

they was listed as

NIC0 as vmnic0

NIC2 was vmnic1

NIC1 was vmnic2

i added VMNIC 0 and 2 because it was shown like that in netowkring

 

the names was wrong. done ask me why but after an reboot it was correct shown in the networking, after the team was between the 10 and the mangement.

 

doenst matter, the biggest is done

but still the team does not work - if i pull the cable on port 8 / no ping to the NAS possible

 

now i have on the switch vlan70 with port 5 and 8, and vlan71 with ports 6/7 - correct so far ? or do they need all 4 ports in the vlan 70 ?

 

the NAS does not have the function of VLAN


Viewing all articles
Browse latest Browse all 252940

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>