- An update on the old man for everyone. After a scary few days when he didn't seem to recognize us, he seems to be at least partly back and semi mobile. His right leg is still paralyzed and he has no feeling in it, but he seems to be able to use it. Left leg seems improved.The seizures continue and we have changed his medication to try to get them under control. He is waking up and calling for help in the early hours of the morning and is unable to control his bladder during a seizure.But he's responding to his name again… At least as much as the stubborn old man used to anyway. And he is being much better with Nanuq after the last few days of acting terrified of his little brother. Not out of the woods yet but we have a go forward and still hoping for the best. #stlloki #siberianhusky #huskiesofinstagram Photo taken yesterday while eating lunch at Have a Cow. - March 10, 2024
- Send good vibes for the old man Loki. #stlloki is in a bad way this week. Suffered several grand mal seizures this week with no identifiable cause and has been left paralyzed in his right leg and partially on his left. His behavior has turned extremely erratic and verging on violent. He's having trouble recognizing people and even Nanuq.Not the best pic I have of him, but one of the most recent of the old man. #siberianhusky #huskiesofinstagram - March 8, 2024
- Night walk through the Redwoods Tree walk in Rotorua… The lights are so beautiful and made for a lovely end to the evening… #newzealand #redwoodstreewalkrotorua - February 1, 2024
Well, I hit an interesting issue with VMotion in VMware vCenter. Funnily enough it seems eerily similar to a problem reported on Twitter last week by @joefarri. Maybe this will provide some insight into some of the odd problems that can occur.
Basically, I had a swath of VM’s that wouldn’t VMotion across my cluster. They seemed to be set up OK, and even seemed to have no removable devices attached, serial ports or any of the other things that usually cause problems with VMotion. I was a little stumped until I happened to start looking through the configuration in detail.
What I found was that under the NIC configuration, when I dropped down the list of attached networks I found that there were multiple networks with identical names. There were two networks listed under there called “Production Network”. On a whim, I selected the “other” defined network and suddenly my machines would vMotion again. Bizarre part is; once I’d done this, the “ghost” network had vanished.
What do I think caused this? Well, these were all older machines… some 2003 and early 2008 servers that we had stood up. I think some of them were P2V’s. Anyway, I think that somewhere during one of our upgrades these “ghost networks” appeared as a corruption in the config or in the vCenter database itself. Once I told it to use a “different” network, that corruption was cleared and suddenly stuff worked again.
I suspect another way to resolve this problem would be to unregister and re-register the VM… but I didn’t test that since these are all production systems I didn’t want to interrupt (and yes, changing the network caused no loss of pings).
Hope that helps anyone. Posting it here mostly so I can link it from Twitter for the benefit of my fellow VMware geeks 🙂