Configuring VRMS connection…failed. The localsite is already paired to the given remote site. – VRMS Connection configuration


Error: Configuring VRMS connection…failed. The localsite is already paired to the given remote site while configuring VRMS connection configuration.

Cause: This problem araised due to VRMS database corrupt or more than one database available for VRMS host.

Solution: Delete the VRMS ovf host and the database created for the Specified VRMS host. Create new VRMS host and configure with new database which will solve the problem.

 

Ref: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2009631&sliceId=1&docTypeID=DT_KB_1_1&dialogID=283254170&stateId=1%200%20283250729

 

 

Advertisements

vrm server generic error. The detailed exception is: hostname While configuring VRMS connection


Error: vrm server generic error. The detailed exception is: hostname

Cause: VRMS Primary server unable to see the vcenter server of the secondary site.

Solution: Add the secondary vcenter server IP address and hostname in the VRMS server hosts file(/etc/hosts)

Eg: #vim /etc/hosts

please add an host entry in the file like

IP address(XXX.XXX.XXX.XXX)   Hostname (Your Vcenter hostname)

ISA Proxy configuration for Ubuntu


Symtom: To configure ISA proxy in Ubuntu where ubuntu accepts windows authentication

Solution: There are two tools are available for authenticating ISA server.

1. NTLMAPS

2. CNTLM

Installation procedure:

Download url for NTLMAPS ubuntu oneiric: http://packages.ubuntu.com/oneiric/ntlmaps

Step 1:  dpkg –install <package name>

Step 2: Configure the program:

[HTML]
Listen port: 5865
Parent Proxy: your.proxy.com
(e.g. enter the name or address of your proxy,
do not enter the port as “your.proxy.com:number”
as this will be taken care of in the next step)
Parent Proxy Port: port_number (usually 8080)
NT Windows Domain: domain_name (your domain)
NT Windows Username: user_name (the user name you will authenticate with)
NT Windows Password: password
(the password you will use to authenticate with the
ISA Proxy)
[/HTML]

Step 3: Check the service ntlmap available /etc/init.d/ntlmaps

Step 4:  If it installed properly you should be able to see it with these commands :- ps aux | grep ntl

Step 5: To reconfigure the program $sudo dpkg-reconfigure ntlmaps

Step 6:  Create a file /etc/apt/apt.conf.d/proxy and input the following line:

Acquire::http::Proxy http://127.0.0.1:5865/;

Step 7:  Reconfigure System->Preferences->”Network Proxy” to point to localhost:5865 with _no_ authentication. Also reconfigure your GUI Package managers similarly.

Step 8: restart the system and check

Also check in the export environment.

Check if the proxy setting have been updated properly.

$ export | grep proxy

You should see something exactly like this:
Code:

$declare -x ftp_proxy=”ftp://127.0.0.1:5865/
$declare -x http_proxy=”http://127.0.0.1:5865/
$declare -x https_proxy=”https://127.0.0.1:5865/

also check your etc/apt/apt.conf file to see if the proxyies have been changed to 127.0.0.1:5865

Now test to see if wget works from a command line

$wget www.google.com

It should display that it is checking 127.0.0.1:5865, and download the correct file.
If it fails then something is wrong with NTLMaps setup.

Your Synaptic Package manager should be working correclty now as well.

Ref url : http://www.linuxquestions.org/linux/answers/Networking/HOWTO_Install_and_Configure_NTLMaps_for_use_with_an_ISA_Proxy

http://ubuntuforums.org/showthread.php?t=1285745

Installation procedure for CNTLM

Step 1: download the application from the url  http://ftp.awk.cz/cntlm/

Step 2: dpkg -i <package name>

Step 3:  Edit /etc/cntlm.conf file to have following information.
———————————————————————————-

Username username
Domain domainname
Password password
Proxy **proxy server IP**:8080
Listen 3128

Step4: Set my username ,domain, password

$cntlm -I -M http://test.com

It asked password.I entered my password.The following lines appeared:

Config profile 1/4… OK (HTTP code: 302)

—————————-[ Profile 0 ]——

Auth NTLMv2 PassNTLMv2 90BA1F766F17FF732ACB9B48BC65E93E

Step 5: Check the service cntlm by /etc/init.d/cntlm status

Step 6:  Create a file /etc/apt/apt.conf.d/proxy and input the following line

Acquire::http::Proxy http://127.0.0.1:3128

Step 7: Restart the system and check.

Ref url : http://askubuntu.com/questions/23666/apt-get-does-not-work-with-proxy

http://askubuntu.com/questions/86149/error-in-authenticating-cntlm-for-ubuntu-11-10

Update :

Error scenario: I configured cntlm in Ubuntu for the connectivity to ISA proxy server.

My network administrator restarted the ISA proxy server, after that I can able to browse and unable to do sudo apt-get.

I am getting an error message “

  1. 502 Parent proxy unreachable
  2. Connection to proxy failed, bailing out when I do cntlm –M http://google.com

 

Root cause: My Ubuntu machine unable to contact Proxy server, since it is in different segment.

502 Bad Gateway – The server was acting as a gateway or proxy and received an invalid response from the upstream server

Solution: please do route add to enable access to the proxy server network segment.

Eg. $ sudo route add –net  xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx etho  (or)

$ sudo route add –net  xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx gw xxx.xxx.xxx.xxx

Unable to login in Vcenter


Symptom Error: Vsphere client could not connect to vcenter. An unknown connction error occured.(The request failed because of a connection failure. (Unable to connect to the remote server))

Root Cause: There is a same hostname or the IP address of the Vcenter server exist in the network.

Solution: Identify the hostname or ipaddress which creates the problem and rename the hostname or ip address which should not be identical to Vcenter server.

Unable to Add the ESX Host to the Cluster


Issue:

It is not possible to add the ESX host to the cluster.
 
Error: Request timed out
 
Solution:
 
The following actions were taken:
1. The customer was requested to restart the vmware-mgmt service.
The service could not be restarted because it is a production environment.
2. It was suggested that they disable and enable the HA.
3. The AAM and HA agents were deleted from the hosts. The vpxa agent was also deleted, and an attempt was made to read the host to the cluster but still the same issue persists.
4. A check was done by pinging to the ESX host from the VC installed physical Windows m/c and it works fine.
5. A search for tasks and events, for any clues was carried out, but nothing related to this error was found.
The management service had to be restarted to resolve the issue.
 
 

Find out who is monopolizing or eating the CPUs


Symtom: To find which process or application which chokes CPU usage.

Solution: Following command will displays the top 10 CPU users on the Linux system.

# ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10

or  

# ps -eo pcpu,pid,user,args | sort -r -k1 | less

Output:

%CPU   PID    USER       COMMAND
  96       2148   vivek      /usr/lib/vmware/bin/vmware-vmx -C /var/lib/vmware/Virtual Machines/Ubuntu 64-bit/Ubuntu 64-bit.vmx -@ “”
0.7       3358  mysql       /usr/libexec/mysqld –defaults-file=/etc/my.cnf –basedir=/usr –datadir=/var/lib/mysql –user=mysql –pid-file=/var/run/mysqld/mysqld.pid –skip-locking –socket=/var/lib/mysql/mysql.sock
0.4      29129  lighttpd    /usr/bin/php
0.4      29128  lighttpd    /usr/bin/php
0.4      29127  lighttpd    /usr/bin/php
0.4      29126   lighttpd    /usr/bin/php
0.2      2177     vivek         [vmware-rtc]
0.0      9              root     [kacpid]
0.0      8              root     [khelper]

Ref: http://www.cyberciti.biz/tips/how-do-i-find-out-linux-cpu-utilization.html

 

 

Guest VM not connecting to network


Symtom: The Guest Windows VM not connecting to the network. When I try to ping the gateway it shows destination unreachable.

 

Cause: IPSec service not started and the polstore.dll file is unregistered. IP Sec service is vital to Guest VM in the network. If the service is stopped or any issues, the network connection will not establish in the Guest VM

 

Solution:  To resolve this issue, delete the following registry subkey and then rebuild the policy:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\IPSec\Local
  1. Delete the local policy registry subkey. To do this, follow these steps:
    1. Click Start, click Run, type regedit, and then click OK.
    2. In Registry Editor, locate and then click the following subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\IPSec\Policy\Local
    3. On the Edit menu, click Delete.
    4. Click Yes to confirm that you want to delete the subkey.
    5. Quit Registry Editor

     

  2. Rebuild a new local policy store. To do this, follow this step:
    1. Click Start, click Run, type regsvr32 polstore.dll, and then click OK.

 

Ref:  http://support.microsoft.com/kb/870910