The Technology Chronicle

Ubuntu P2V conversion is not as straight forward as other Linux machines with a root user. This is because we use a non-root user by default for managing Ubuntu machines and the root credentials are not known to us. So how do you convert a physical Ubuntu VM to virtual without the root credentials? Here are the steps PS: please note the steps are for VMware vCenter standalone converter 5.5 1.Edit VMware configuration files converter-agent.xml and converter-worker.xml files present in C:\ProgramData\VMware\VMware vCenter Converter Standalone , update the useSudo flag from false to true 2. Reboot the VMware converter standalone agent service

Scenario: 2 nics in Ubuntu machine, requirement to assign IPs from different VLANs to each of these interfaces, access from outside world to all the assigned IPs. The situation was a bit complex since the machine was a VM  in ESXi and each of these nics were added to portgroups of two VLANs 200 and 201. The first nic eth0 was assigned a gateway , and was accessible from outside world. The second nic eth1 was assigned IP in 201  VLAN, but was not able to ping to that machine from other machines in a different VLAN Solution: Inorder to solve the issue, we had to add an additional routing table, to select default route for packages which should go out of eth1. The following lines added to the eth1 interface configuration in /etc/networking/interfaces file did the trick post-up ip route add default via 10.1111.0.1 dev eth1 table 101 post-up ip rule add from 10.111.0.0/25 lookup 101

Recently we faced a strange issue while connecting a Windows server 2012 R2 to domain, connection was failing with network error. I was able to ping to the domain, as well as the domain controller. While troubleshooting the issue, I stumbled upon a gem called c:\windows\debug\netsetup.log. It was throwing an error 'NetUseAdd to \\<domain controller>\IPC$ returned 1231 Seems like the machine was having issue connecting to the share. I tried  the "Net view \\sharename " command and got system error 53. Now the root cause was confirmed, the machine was having trouble accessing shared drives How do we solve it? Actually the solution was pretty simple , you need to install 'client for Microsoft networks" in the network adapter of the server. Somehow it got uninstalled from my VM's adapter and created all this trouble. Installed it back and was able to add the machine to domain!!  

Steps to set an http proxy for apt-get permanently 1. Create a new file apt.conf in /etc/apt  . Add the following line in it Acquire::http::proxy " http://<proxyip>:<port>/" ;  2. Edit the file named environment in /etc .Add the following line to it. http_proxy= http://<proxyip>:<port> If you want to add the proxy temporarily for a session, you can use the command export http_proxy=http://yourproxyaddress:proxyport PS: if you want to add proxy exception for local addresses in your network, add the following command to /etc/environment no_proxy = localhost,<hostname>