xspader's Posts

Hi All I'm trying to find a method to allow me to get a list of systems that are being replicated, their status, and systems that arent being replicated. Other than manually tagging systems that I'... See more...
Hi All I'm trying to find a method to allow me to get a list of systems that are being replicated, their status, and systems that arent being replicated. Other than manually tagging systems that I'm replicating and checking the replication appliance daily (no SRM) is this something I can simplify with vRO? As there seems to still not be a powerCLI API to be able to query the replication appliances, this is the next option I'm looking into. Just dont want to sink a bunch of time setting this up if its not going to buseful to report on replications and potentially automate replication setup to stop it being a manual task.  If I can prove it to be useful I might be able to convince them to pay for vRA
Thanks @ashilkrishnan and @depping for your responses. My preferred solution is to have 2 vcenters as I believe its cleaner and makes it more efficient during recovery time. The solution was initiall... See more...
Thanks @ashilkrishnan and @depping for your responses. My preferred solution is to have 2 vcenters as I believe its cleaner and makes it more efficient during recovery time. The solution was initially designed to be single logical datacenter with 2 clusters to share the vDS. I thought about VCHA but kept seeing a specific vmware employee posting everywhere to repeat after him that 'VCHA is NOT DR' I think at this point I just need to export the vDS from Prod and Import to DR so it keeps the same UUID and recovery errors when Prod is gone should go away.
We are replicating systems to a remote DR site and I currently have vcenters in linked mode to get some separation as it makes me feel more confident about the vcenter survivability. I've been looki... See more...
We are replicating systems to a remote DR site and I currently have vcenters in linked mode to get some separation as it makes me feel more confident about the vcenter survivability. I've been looking around and cannot find anything specifically about replicating vcenter in a single vcenter setup. Is this recommended and is there anything needed to recover the VCSA at the DR site if thats the reason for replicating? I have a call in with vmware to ask some other questions, but I was hoping someone here may have an answer on this one specifically. The reason is there is an idea to run a single vcenter to look after Prod and DR. Singe Datacenter in vcenter and two clusters so the vDS with the same UUID is present at both sites. If this is able to be successfully replicated and recovered at the remote site in a DR scenario then great, but I havent found anything other than an article from 2012 saying its a PITA
Thanks @ashilkrishnan . Just trying to come up with a reasonable solution incase the Prod site disappears. Ideally I'd like to use ELM to stick with a single vcenter and have that as a 'hot spare' bu... See more...
Thanks @ashilkrishnan . Just trying to come up with a reasonable solution incase the Prod site disappears. Ideally I'd like to use ELM to stick with a single vcenter and have that as a 'hot spare' but I dont believe it works that way. I'll split my sites into 2 different vcenters tomorrow and reconfigure everything for the DR site and then link them in ELM and finish my replication setup. Appreciate your help
Hi all I've been looking around and cant find anything that explicitly states that vsphere replication will work with vcenter ELM. I'd prefer not to assume that it does, so would appreciate it if so... See more...
Hi all I've been looking around and cant find anything that explicitly states that vsphere replication will work with vcenter ELM. I'd prefer not to assume that it does, so would appreciate it if someone has any insight into this.  After reading some of the discussions I figure I'll need to break my sites out from the single vcenter instance, create a separate vcenter in the DR site and reattach the hosts there to it. Ideally I'd like to connect these in ELM to make management easier while both sites are up, but will keep separate if ELM is a problem with vsphere replication Thanks
I've got the same issue on HPE DL360 G10 Running ESXi 6.7 latest update. Its bloody frustrating as I had the documented issue with the fans which I filtered out and was subsequently fixed in a pa... See more...
I've got the same issue on HPE DL360 G10 Running ESXi 6.7 latest update. Its bloody frustrating as I had the documented issue with the fans which I filtered out and was subsequently fixed in a patch, but these errors that pop up for no reason with nothing in the iLO/physical hardware event log or anywhere I can find are frustrating. Its almost like its a timeout for a response so it flags it as an error rather than adds it to a recheck
Hi All Just wanting to check my expectations. We have vsphere 6.7U3 Ent Plus we have also configured the HPE iLO details in the IPMI/iLO (BMC) settings. I havent used this setting before and a... See more...
Hi All Just wanting to check my expectations. We have vsphere 6.7U3 Ent Plus we have also configured the HPE iLO details in the IPMI/iLO (BMC) settings. I havent used this setting before and am wondering if we require the ability to WOL to allow Power On? I expected that as it has the iLO login details and IP address, that this wouldnt be required as it should log in and issue the Momentary Press command to start the system. Are my expectations incorrect? I've tried to find the answer from Google but theres no specific requirements paper to detail whats actually needed to enable the Power On functionality.
Thanks for the reply Andre Essentially I get the vmodl.fault.HostCommunication error and every tech article or community post I have tried has failed to resolve the issue. I just thought it wa... See more...
Thanks for the reply Andre Essentially I get the vmodl.fault.HostCommunication error and every tech article or community post I have tried has failed to resolve the issue. I just thought it was interesting that it didnt work despite trying everything I could find. I can add the hosts to vcentre but they will become unresponsive almost straight away and then will be disconnected, on trying to reconnect I get the HostCommunication error. Its only for a test lab so is not essential to be in vcentre, its just a nice to have. As I dont have the luxury of time or experience on my side to diagnose the issue I'll just move on with it as stand alone ESXi hosts. If the PoC works then we will be getting new hardware and will run VSphere 5 with vcentre which I will have much more time to ensure is right. This is old tech so dont worry about it too much.
Hi All Wasted 2 days going through these forums and various kb articles trying to get the ESXi systems (in evaluation mode) into a vcentre server I have checked DNS restarted management ... See more...
Hi All Wasted 2 days going through these forums and various kb articles trying to get the ESXi systems (in evaluation mode) into a vcentre server I have checked DNS restarted management agents reinstalled ESXi checked ESXi config files to ensure correct IP's are there set the IP address for the VCentre server Dont know what else to do. All the systems are connected to the same switch in the lab with a blank config on it, no firewalls or anything else to block portsand are on the same subnet. Surely it isnt supposed to be this difficult? Anyway I've given up for now but if there is anything anyone can add that could help as I'm going to try it again later, I would appreciate your input Hayden