I can confirm the BUGs in HPE Nic FW as well because one of my customer tried to upgrade FW by it self and got all problems you have described. We downgrade the Nic FW to the old version and all was fine again. It was some hassle because vMotion does not work anymore and we need to cable the unused 1GbE nics on the hosts.
Regards
Joerg
Try like this
$csvpath='.\controllers.csv'
$vmName=Read-Host-Prompt "Name of the VM"
$vm=Get-VM-Name $vmName
foreach($vmdkin(Import-CSV-Path $csvpath-UseCulture))
{
# Does the SCSI Controller exist?
$controller=Get-ScsiController-Name $vmdk.SCSI_Control-VM $vm-ErrorAction SilentlyContinue
if(-not$controller)
{
$newBusNumber=($vm.ExtensionData.Config.Hardware.Device|
where{$_-is[VMware.Vim.VirtualSCSIController]}|
Select -ExpandProperty BusNumber |
Measure-Object-Maximum |
Select -ExpandProperty Maximum)+1
$spec=New-Object VMware.Vim.VirtualMachineConfigSpec
$device=New-Object VMware.Vim.VirtualDeviceConfigSpec
$device.Operation=[VMware.Vim.VirtualDeviceConfigSpecOperation]::add
$device.Device=New-Object VMware.Vim.VirtualLsiLogicSASController
$device.Device.BusNumber=$newBusNumber
$device.Device.SharedBus=[VMware.Vim.VirtualSCSISharing]::PhysicalSharing
$spec.DeviceChange+=$device
Write-Host"Adding SCSI $($vmdk.SCSI_Control) Bus $($newBusNumber)"
$vm.ExtensionData.ReconfigVM($spec)
$vm.ExtensionData.UpdateViewData()
}
}
LucD,
From the csv file, I have provided SCSI Controller 1, 2 and 5
From CLI, I see as below
From GUI, I see SCSI Controllers added as 1, 2 and 3, instead of 5
That is how vSphere works I'm afraid.
It assigns the numbers in the Label sequentially, you can't leave gaps.
EDGE v should be in a different VLAN than TEP from the Edge Transport Node, in this case, assuming you are using Logical Segment to connect the TEP of the EDGE vm.
Thanks for the update and help LucD.
I think, I am good now, let me go with sequential then...
it was time for this subgroup, Jenn.
Edge VM's TEP is on different Vlan than the Compute Transport Node's TEP. Funny thing is from the upstream switch, I can ping the Edge VM's TEP but not the Compute Transport Node's TEPs. The Compute Transport Node's TEPs can see each other and VM's in the N-VDS Overlay can communicate with each other.
Just to share with this group my blog post on NSX group.
A PKS tale: NSX-T Protected Objects or Protected by superuser
extract:
Hi just want to post something to track my PKS upgrade from 1.1.4 to 1.2, so let me give some context here:
PKS on this time was installed in the 1.1.4 version with NSX-T 2.1, nothing weirdo so the deal was to move to 1.2 the PKS, and here is the challenge faced, there is an issue in PKS regarding that version in where some elements are not able to be "deleted", so let me explain more in detail.
PKS is a solution composed of mainly 3 elements: PKS tile, Operations Manager Tile and Bosh Director, extras you have NSX-T and Harbor if registry selection is that, so in short PKS does on-prem a GCP for K8s and consequently for CNA's, so by means of BOSH connects to vSphere and do the magic to create VMs (vSphere based in this case )when you request the creation of PODs at K8s level, so K8`s orchestrates Docker and PKS takes care of K8s and BOSH of the VM´s n a declarative way of construct infrastructure,so long story short when you install everything and integrated with NSX-T PKS creates a superuser in NSX manager to wire all the pods in K8's in automatic was every time you need a new namespace, so if you see any installation include the HOL´s PKS you will see something similar to the pic below.
Well,
There is a lot of logs:
For example:
2019-06-06T05:59:56.801Z 36787 INET TERM domain-c47/1016 IN TCP TIMEOUT 10.0.0.7/60499->10.0.210.14/445 1/0 52/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/34420->10.0.210.13/443 10/0 1904/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/54444->10.0.210.12/443 10/0 1904/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/34426->10.0.210.13/443 9/0 1802/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/54450->10.0.210.12/443 10/0 1842/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/54452->10.0.210.12/443 10/0 1929/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/34434->10.0.210.13/443 10/0 1929/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/54458->10.0.210.12/443 11/0 1998/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP FIN 10.0.210.10/34440->10.0.210.13/443 10/0 1958/0
2019-06-06T05:59:56.801Z 48972 INET TERM domain-c47/1016 IN TCP RST 10.0.210.10/48480->10.0.210.12/9080 11/0 2572/0
What kind of log should I look for ?
Best Regards
Marcin Gwóźdź
Mine is nothing there
Sure
well, my bad on logs, please check this link :
also, check this link from the AD side:
https://girl-germs.com/?p=1538
if you have access to myVMware open a TSR what I read the GSS has lots of tricks to look under.
hope this helps.
I think the issue is where I cannot ping the Compute Transport Node's VTEPs from the upstream switches. So the 2 VTEP cannot route to each other. When I configure the VTEP pool for Compute Transport Node, I configure the default-gateway but don't remember anywhere I could configure any Vlan tagging. So when VTEP traffic goes upstream, how does the switch know which Vlan to put it in?
Check the following code:
var allDVS = Server.findAllForType("VC:DistributedVirtualSwitch");
for each (var dvs in allDVS) { System.log(dvs);
}I use vcenter 6.7 U1 appliance version. I login vcenter with HTML but cannot login FLEX. How can resolved this issue?
so, for example, TEP of Transport Node/ Edge Transport Node or ESXi with vibs for NSX will be in VLAN 200 EDGE VM eth1 or second interface for TEP proposes on LS backend on VLAN TZ with the tag of VLAN 400 the reason is that ESXi host will drop Geneve if this traffic is not passing thru the vmnic of the host. please check this link to document starting in page 32 VMware® NSX-T Reference Design
Hello,
Facing the same problem with Windows 2008 R2, Windows 2012 and Windows 10.
Sending ctrl/alt/del doesn't work.
Only via the remote console i could login to the systems
Used esxi 6.7.0 Update 2 (Build 13006603)
The HTML5 client is the one you should use. Check this Fully Featured vSphere Client in vSphere 6.7 Update 1 - VMware vSphere Blog