stinkyptoz's Posts

Hi, Thank you for the response Yes, I did see that article and I just wasn't sure whether or not the vAPP option update/s had any bearing on "Option 1" or "Option 2"... from what I have read, up... See more...
Hi, Thank you for the response Yes, I did see that article and I just wasn't sure whether or not the vAPP option update/s had any bearing on "Option 1" or "Option 2"... from what I have read, updating the vAPP options only comes into play if the applicance is exported to an OVA/OFV, but I'm not 100% sure I'm correct in thinking this is the case? I totally agree though, documentation relating to this subject is hard to find or almost non existant. Cheers, Emb
Hi All, I'm just looking for some advice regarding changing the DNS Server allocated to our vRealize appliances. Basically, I was wondering if modifying the relevant vAPP options for the appliance ... See more...
Hi All, I'm just looking for some advice regarding changing the DNS Server allocated to our vRealize appliances. Basically, I was wondering if modifying the relevant vAPP options for the appliance will actually change the DNS server or whether I actually need to login to the appliance itself and modify it from there? As I understand it, the vAPP options can only be changed once the appliance is powered off?! Thanks in advance for any pointers... Cheers, Emb
Hi, Update for anyone experiencing a similar issue : The problem turned out to be the physical switch port configuration. The number of MAC adressess allowed per Switch Port was set to default (1) ... See more...
Hi, Update for anyone experiencing a similar issue : The problem turned out to be the physical switch port configuration. The number of MAC adressess allowed per Switch Port was set to default (1) and therefore when a MAC address(for a VM) was vMotioned from one ESX Host to another, this disabled the switch port and obviously disconnected the Host from vCenter. https://www.geeksforgeeks.org/configuring-port-security-on-cisco-ios-switch/ Hope this helps someone in the future.... Best Wishes, Pete
Hi Bobkin, Thanks for the reply Defnitely not multihoming the management and vMotion network, they are using separate physical connections into the physical server, they are using separate vSphe... See more...
Hi Bobkin, Thanks for the reply Defnitely not multihoming the management and vMotion network, they are using separate physical connections into the physical server, they are using separate vSphere switches with separate vmNICs and obviosuly separate vmKernals adapters with different IPs (Management = 10.111.60.10 and vMotion = 10.101.60.30) I've set the services, eg management/vMotion/VSAN/witness traffic to the correct vmkernal adapters. I've never tried to vMotion the vCenter VM...in fact that resides on a separate cluster in the datacentre...and this VSAN cluster in question, with this issue, is just a 2 node directly connected setup in a remote office etc....using a witness appliance located in the main datacentre.      
Hi depping, Thanks for reply first off! So this is/was a live migration... vMotion appears to be configured correctly - as in the vMotion service is specified to only use the dedicated vMotion V... See more...
Hi depping, Thanks for reply first off! So this is/was a live migration... vMotion appears to be configured correctly - as in the vMotion service is specified to only use the dedicated vMotion VMKernal port(with an IP on a different address space/subnet to the management VMKernal adapter) Yes, I have ensured that the correct Physical NICs in the server are associated with the correct vmNICs on the host... I have vmNICs 0 and 1 used for my Management VMKernal adapter(10.111.60.10) on my standard switch(which are obviosuly patched into the physical switch in the datacentre)...then vmNICS 4 and 5 are used for DVUplinks for my Distributed Switch, which has 2 VMKernal Adapters....one for VSAN and one for vMotion(both having separate IP addresses on different network spaces eg vSAN is 10.10.60.20 and vMotion is 10.101.60.30) I'm now wondering if it could be something to do with the way the vSAN has been setup or possibly some sort of issue/misconfiguration with the directly connected SFPs/cables/dualport 10GB Ethernet Card that the two host are connected by(vmNics 4 and 5 in vSphere etc). Bit of a head scratcher this one!!      
Hi all, I've recently adopted a 2 node VSAN cluster that has an issue whereby when a vmotion is initiated, from one host to another, the host seems to send a burst of traffic via the managment NIC, ... See more...
Hi all, I've recently adopted a 2 node VSAN cluster that has an issue whereby when a vmotion is initiated, from one host to another, the host seems to send a burst of traffic via the managment NIC, which is forcing the switch to close the port down....and I lose the host in vCenter obviously. I've created a standard switch for the management traffic and i've created a distributed switch for the vmotion/vsan traffic. I've also configured the traffic types/services for each vmkernal adapter correcty. My DVUplinks are configured correctly for my Distributed Switch(as per the physical ports on my hosts) and my VMNics for my Standard Switch are again configured correctly as per the physical setup/NICS on the host/s. I'm thinking that the Gateway address for my VSAN/vMotion kernal adapters is possibly the issue... and i've tried to set it to not have a gateway( as these are directly connected hosts and only need to have connectivity to themselves for vsan/vmotion traffic etc), but it wont allow me to do that. Does anyone have any ideas or can at least point me in a particular likely direction if its not what i'm thinking above? I'm only using the default TCP/IP Stack as it stands...I'm guessing best practise is to separate out the vMotion and VSAN traffic using separate TCP/IP Stacks - I guess this is one way to specify the gateway addresses for the vMotion and VSAN traffic, but would I just leave it blank? I was wondering if this article is perhaps my issue? Any thoughts ( https://www.yellow-bricks.com/2017/11/22/isolation-address-2-node-direct-connect-vsan-environment/ )   Cheers in advance, Pete