I'm not sure why write/read via that file?
And I don't think you need a switch-block.
Try something like this
$menu=for($i=0;$i-lt$v.Count;$i+=2)
{
$obj=[ordered]@{
Odd="$($i+1). $($v[$i].Name)"
}
if($v[$i+1])
{
$obj.Add('Even',"$($i+2). $($v[$i+1].Name)")
}
New-Object PSObject -Property $obj
}
$menu|Format-Table-HideTableHeaders
$choice=Read-Host-Prompt "Select tag (1..$($v.Count))"
Get-VM-Tag $v[$choice-1].Name
Thank you for looking into this.
Following is the info when I login to a baremetal server that is in the same subnet as the underlay VLAN 11.
root@bs101-01l:~# ip addr show dev eno1 4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 10000 link/ether 0c:c4:7a:33:5c:d0 brd ff:ff:ff:ff:ff:ff inet 10.4.11.101/24 brd 10.4.11.255 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::ec4:7aff:fe33:5cd0/64 scope link valid_lft forever preferred_lft forever root@bs101-01l:~# traceroute 10.4.11.154 traceroute to 10.4.11.154 (10.4.11.154), 30 hops max, 60 byte packets 1 10.4.11.101 (10.4.11.101) 3077.627 ms !H 3077.538 ms !H 3077.515 ms !H root@bs101-01l:~# root@bs101-01l:~# ping 10.4.11.154 PING 10.4.11.154 (10.4.11.154) 56(84) bytes of data. From 10.4.11.101 icmp_seq=1 Destination Host Unreachable From 10.4.11.101 icmp_seq=2 Destination Host Unreachable From 10.4.11.101 icmp_seq=3 Destination Host Unreachable From 10.4.11.101 icmp_seq=4 Destination Host Unreachable From 10.4.11.101 icmp_seq=5 Destination Host Unreachable From 10.4.11.101 icmp_seq=6 Destination Host Unreachable ^C --- 10.4.11.154 ping statistics --- 7 packets transmitted, 0 received, +6 errors, 100% packet loss, time 6148ms pipe 4
From a web vm on the overlay network, I'm unable to ping 10.4.11.101 (a sample host on the underlay network). Few other things about my environment
Thank you for your help again. I'll also try to use tcpdump etc on the ToR to see what's going on..
Thanks Rags
AWESOME! Yes thank you this works great. I tried to do it my way because I wasn't sure of the right way! Thanks very much for the help.
It's actually a matter of consolidating the snapshots, as already mentioned by Wil.
What you may try - after backing up the files - is to follow Option 2, or 3 from https://kb.vmware.com/kb/1020000. Option 3 has the advantage, that a new .vmdk file will be created, i.e. the current .vmdk files won't get modified.
One thing to point out, is that the virtual disk's provisioned size is ~1.8TB. Do you really need this, or is it simply the result of the conversion from the "real" Boot Camp machine?
If you don't want/need that size, it might be worth using the vSphere Converter, and reduce the provisioned size.
If you are unsure about the commands in Option 3, please don't hesitate to ask.
André
Thanx, that did it and I was able to reset the root PW. When I got back into the console, two of the three vCenters are now showing green. I'm going to update the appliance and see what happens.
Build 7400497 is the GA release of 7.4.0. We were delivered build 821556 to resolve that issue. You could contact support and request the hot patch to stay on 7.4 until you are ready for 7.8.
There was no consistency to when we would see the issue. I had initially reported the issue to support and worked with them to get the hot patch.
Certificates with Horizon are well documented and straightforward. It can get complex when you introduce Unified Access Gateways (UAG)/Security Servers and load balancer depending on where the SSL termination is taking place. Can you start a new discussion with the details of your environment and we can assist.
Can you tell us more about your environment? Newer versions have improved the DPI/Display scaling. I've also had better luck fixing the resolution on a tablet/phone (e.g. 1920x1080) to avoid the scaling.
Horizon Client Versions
Horizon Agent/VMware Tools versions
UAG/Security Server versions
Connection Server versions
I would recommend opening an SR while you still have access to support for 6.x to get their insight.
What is the hold up on upgrading to 7.x? That can typically be accomplished within just a few hours.
I know there are some known issue with Global Entitlements after upgrading to 7.8.0. Are you possibly using a read-only admin account?
Release Notes for VMware Horizon 7 version 7.8
Users that have the Administrators (Read Only) role cannot see View Configuration > Cloud Pod Architecture in Horizon Administrator or Settings > Cloud Pod Architecture in Horizon Console.
Workaround: None.
From the Horizon Console you can manage Global Entitlements.
Setting Up and Managing Cloud Pod Architecture in Horizon Console
You can also try using lmvutil.
Saludos.
El problema puede estar en la compatibilidad de la controller de disco
HPE Smart Array S100i SR Gen10
link: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00026319en_us
link: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00059854en_us&docLocale=en_US
También hay tema de soporte con el tipo de Procesador en este equipo.
Suerte
Can confirm that having a 2.14.2 Agent and adding the *msiexec.exe||* into the HookInjectionWhitelist key and installing the latest Cumulative updates does seem to work fine together. Going to keep testing to make sure though.
I know this post is is a year old now, but was there ever a definitive resolution to this? I have both vRA manager servers in the NSX L\B pool enabled, I configured automatic failover in the vRA appliance, and I see in the VAMI that the 1st manager server is showing active, and the 2nd manager server is passive. If I take the active server down, the 2nd server never goes active and I start to see the error in the logs. Additional from the error described here, if I check the Windows security event logs I see audit failures that state that Windows Filtering Platform denied the connection, and in the vRA VAMI certificate page "SSL routines: ssl23_write:ssl handshake failure: s23_lib.c:177:"
Thanks but I run Instant Clones so i'm not sure that will not work.
so no support for v14, which I bought last year (AFTER windows 10 was released).
This is rubbish.
I'm terminating our VMware and AirWatch relationship. I hope someone with a spine contacts me.
I'm furious.
Cool backup vCenter to SMB share now in 6.7 U2!
I can't get it to work! Not sure what I am missing.
The helpful 'example' in the path shows:
protocol://server-address<:port-number>/folder/subfolder
Share I want to backup to is a Windows 2012 R2 share.
Port? I thought it would be 445.
My example:
SMB://10.1.1.1:445/hiddenshare$/subfolder
I enter my domain account that has full control on share and NTFS.
I get a "SMB location is invalid" error.
Where am I going wrong? VMware doc doesn't give examples.
Thanks!
Good case:
only one name-cbt.vmdk is damaged.
Disable cbt-block-tracking for that VM.
Stop backup-jobs for that VM.
Delete job.
Delete all cbt.vmdk of that VM.
Start VM again.
Create new job and create a full backup on first run.
Worst case:
this is just a symptom of a serious corruption of your datastore.
But you would have noticed that ....
Has anyone had issues with the VCSA backups using SMB not following the retention setting? I usually set it for 2 but they just keep being added and the older ones not being deleted.
Hi. I'm still working on this since I haven't touched it in a while. I still have the critical alerts since I wanted to get to the bottom of this before acknowledging them. Traffic seems to be working fine, despite the alerts persisting.
There are 2 physical switches going to the vDS: HP ProCurve --> Flex-10 pair switch --> vDS
The ProCurve pair is trunking 3 Vlans to the Flex-10s:
2 ports in a trunk (x2, 4 total, 2 per switch)
Vlan 100 Untagged
Vlan 200 Tagged
Lan 300 Tagged
The Flex-10s configuration shows the same:
6 nics per host x 5 hosts (30 uplinks to vDS)
Vlan 100 (Native)
Vlan 200
Vlan 300
vDS:
dvUplink Group 1 (6 links x 5 hosts = 30 total)
Port Group A (Vlan ID = 0)
Port Group B (Vlan ID = 0)
Port Group C (Vlan ID = 0)
These links from the Flex-10s are all trunked to a single dvUplink group on the vDS, and then there are a few vDistributed Port Groups and each of those have no Vlan ID assigned, as mentioned (so, Vlan ID = 0)
For some reason, all 5 of the hosts appear to be configured the same but only one of them now shows no critical alerts. I don't recall acknowledging the alerts.
I'm thinking of testing out just assigning the matching Vlan IDs to the Port Groups as recommended, but I'd like more info before I break something.
I read at the link below that if tagging is done on the physical switch, the Port Groups' Vlan ID on the Virtual Switch should be zero, but I'm not sure if this applies here or if they mean in a situation where the vDS is connecting to an ACCESS port in a Vlan on the physical switch, or something else. Any clarification or additional help would be great, based on the detail I've added. Thanks.
Anyone had issues with the statsmonitor serverice not starting after a VCSA reboot? I run the following after a reboot but if there is a permenate fix I would like to apply it.
http://www.wickhorst.com/2018/03/31/vcenter-server-appliance-6-5-backup-troubleshooting/
VMware support did give me a fix but it is overwritten when VCSA is updated...which is when I mostly am restarting VCSA.