How to know error types of the validating connection result?
You probably have question how did I know which error types are for what? I used a very simple way that just give it a try. 🙂
# Simulating connection error
Connect-VIServer vCenter.zhengwu.org -User "xxx" -Password "yyy"
# Format output of $Error. $Error stores output of errors in PowerShell.
$error | fl * -force
# You will see similar lines below
writeErrorStream : True
Exception : VMware.VimAutomation.ViCore.Types.V1.ErrorHandling.InvalidLogin: 7/29/2019 9:27:30 AM Connect-VIServer Cannot complete login due to an
incorrect user name or password. ---> VMware.Vim.VimException: Cannot complete login due to an incorrect user name or password. --->
System.ServiceModel.FaultException`1[VimApi_67.InvalidLogin]: Cannot complete login due to an incorrect user name or password.
VMware.VimAutomation.ViCore.Types.V1.ErrorHandling.InvalidLogin is the error type we want to find.
This is very simple way to validating connection result of Connect-VIServer. Looks like the result errors coming from different assemblies. For example, connection error is VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.VimException.ViServerConnectionException. It’s hard to find out all possible errors. I’m looking for a official document but no lucky. Please let me know if you know where I can reference.
There is an official Bitbucket extension for Visual Studio Code if you use Bitbucket Cloud. Bitbucket has not yet released official extension for Bitbucket Server users. Following is how to configure Visual Studio Code to use Bitbucket Server.
Before the procedure you need to collect the following information:
Your user name on Bitbucket Server.
Your email on Bitbucket Server.
Decide the local path to store code. (It’s c:\temp\git\ in this guide)
Your account has permission to modify repositories on Bitbucket Server.
Assume project name is “ExampleProject” on Bitbucket Server.
Assume repository name in the project is “ExampleRepository“.
Get the URL of the target repository. (It’s https://email@example.com/scm/exampleproject/examplerepository.git in this guide)
Download windows installer in Github. Installation is simple. Only thing is to make sure to choose “Visual Studio Code” when it asks editor integration.
Configure user name and email in Git.
Name and email should match your account information on Bitbucket server. Run the commands in Windows command prompt. $ git config --global user.name "Name" $ git config --global user.email "firstname.lastname@example.org"
Clone repository to local.
Open a command prompt. Go to a folder you want to clone the remote “ExampleRepositiry” to. Run command: git clone https://email@example.com/scm/exampleproject/examplerepository.git You will see a sub-folder with the name “ExampleRepository” is created in local. A hidden folder “.git” is created in the sub-folder. It’s used to tracking changes.
Open workspace in Visual Studio Code
Bitbucket Server configuration is completed in local. Now open Visual Studio Code -> File -> Add folder to workspace -> Open “ExampleRepository” folder. Visual Studio Code is integrated with Git in-the-box. It detects the repository automatically. It shows “Unrack” if you create a new file in the folder.
This is an expressway to integrate Bitbucket Server with Visual Studio Code. I’m still new on Git. Following are some useful information.
It’s not easy for me to describe the issue in one line on the title. Let me give some background here. I have 2 set of VMs. Set 1 has VM A & VM B. Set 2 has VM C & VM D. Each VM has a vNIC configured with a private IP address. VM A and VM C also have another vNIC configured with an L3 (Routable) IP address. Each set’s private IP addresses are the same. To make sure no confusion I implemented a vRouter VM for each set. The vRouter is same as VM A or VM C, it has two vNICs. One is connected to L3 network, another is connected to the private network. This way can keep the private network traffic not going outside of the set. So the both set no disturb each other when I set same private IP addresses.
Following are IP addresses I set for each VM:
VM A: 192.168.0.11
VM B: 192.168.0.12
VM C: 192.168.0.11
VM D: 192.168.0.12
The problem is I still can get ping responding on VM A to 192.168.0.12 when I turn off VM B. I expected to see the L2 traffic goes to it own vRouter and finds VM B is offline. But tracert command shows me the traffic goes from VM A’s L3 network to vRouter of the 2nd set, and then get the answer from VM D. Looks like the L2 ping package is broadcasting on L3 network.
The issue was fixed by enabling a feature on L3 network. It called “Enforce Subnet Check for IP Learning“. Cisco changed the name to “Limit IP Learning To Subnet“. It’s a VLAN level setting. It will not allow broadcasting the private Ip traffic on an L3 network. It forces private IP traffic to go to L2 network only.
I have a box uses Emulex OneConnect OCe10102 network adapters. The adapter is quite old and Emulex brand card doesn’t support ESXi 6.0. I upgraded the server to ESXi 6.0 and the Emulex adapters lost.
In the initial troubleshooting, I noticed that the adapters are still visible in BIOS. So it should be some driver level issues. I checked VMware Compatibility Guide. The model OCe10102 doesn’t support by ESXi 6.0.
If you run the following command you will still be able to see the adapters in PCI list on ESXi.
esxcli hardware pci list
So it indicates the adapters are not visible in ESXi since the newer Emulex driver doesn’t contain the model of the adapter in ESXi 6.0 native driver.
Then I uninstalled the native Emulex driver for ESXi 6.0 by the following command and rebooted the ESXi host.
The adapters still not visible after rebooting since no any drivers for Emulex adapters. Then I downloaded the Emulex drivers for ESXi 5.5 on VMware website and uploaded the “offline” package in the zip file to /tmp directory of the host. Then installed the driver by the following command:
I wrote an article talk about how to find out which services lockout domain accounts on vCenter Server. It only applies to the scenarios that domain accounts very frequently lockout. Like every 1 second. If it’s minutes, it will be hard to find out as it’s manually processing.
The other way to identify source is to use vSphere Web Client. The trick was told by VMware BCS team.
Log in to vSphere Web Client. Go to the main page and the Events node. Search for “authen” you may see some error events. The real source is red text.
I wrote an article about how to manage Windows Server 2016 TP remotely. Today I had some spare time to re-build my lab environment by the latest release of Windows Server 2016 Core. It’s easy to remotely manage a Windows Server in a domain, but a trick for workgroup Windows Server. Following is an improved procedure.
One Windows Server 2016 Core
Run sconfig command on Windows Server 2016 Core.
Go to Configure Remote Management – Enable Remote Managementto enable remote management.
Then enable responding to ping in same page.
Enable NetBIOS protocol on the firewall by PowerShell.
mRemoteNG is a very nice fork of open source remote tools. It supports multi-protocol. The official website says:
mRemoteNG supports the following protocols: RDP (Remote Desktop/Terminal Server) VNC (Virtual Network Computing) ICA (Citrix Independent Computing Architecture) SSH (Secure Shell) Telnet (TELecommunication NETwork) HTTP/HTTPS (Hypertext Transfer Protocol) rlogin Raw Socket Connections
But one thing makes me frustrated is the mouse cursor disappeared randomly when I try select strings in browser or notepad in remote desktop. I use Windows 10, the issue doesn’t occur in Windows native remote desktop. I went through the bug list of mRemoteNG, and figured out it may be related to HiDPI of my screen.
Looks like no solution at this moment until 1.77 release. The workaround is the following:
HPE 3PAR upgrading team usually sends a per-requisites before upgrading. One thing in the guide incorrect is the Windows 2012 required patch KB3046101.
You may see error below when you install the path on Windows 2012 server.
The update is not applicable to your computer
The reason is the version of mpio.sys and msdsm.sys on your server is higher than 6.3.9600.17809. Usually, because the server installed KB3121261 already. You can ignore KB3046101.
You may need only 1 IP address for blade console in Cisco UCS Manager. You can follow Understanding “Management IP” of Cisco UCS Manager to configure it. You may see warning “Vlan ‘xxx’ resolved to unsupported VLAN ID” when you delete existing inbound and outbound IP pools if you are trying to clean up existing management IP pools.
That’s because inbound IP address for blade is not cleaned. You have to go to “Equipment” -> “Chassis” -> Target chassis -> “Servers” -> Target server -> Go to “Inventory” tab -> “CIMC” tab -> Click “Change Inbound Management IP” -> Remove existing VLAN and IP pool.
You will see inband IP tab is blank once it’s saved. Please note, the IP address reassign back after 1 minute if you clicked “Delete Inband Configuration” instead of “Change Inbound Managemnt IP“.