ETECK

Two steps: 1>  Check DNS : check  /etc/resolv.conf check /etc/nsswitch.conf (hosts and also ipnodes should have files...dns.. entry) check /etc/hosts (FQDN & short host name) 2> Purge  /var/adm/wtmp and /var/adm/wtmps cd /var/adm rm wtmps wtmp touch wtmps wtmp chmod 664 wtmps wtmp chown adm:adm wtmps wtmp If those steps did not help; then check following : network to make the speed & duplex. sshd_config to turn off the DNS checkd and turn KerberosAuthentication off if you do not use.

In my previous post -- changed Oracle cluster IP/VIP address. I mentioned how to change those IPs. But for some reasons that SCAN VIP did not change. Here are the steps to change it: 1> Make sure that the SCAN VIP hostname can be resolved.      nslookup < SCAN_name> 2> Become root and set ORACLE_HOME environment [oracle@host1 ~]$ su - Password: [oracle@host1 ~]# export ORACLE_HOME=/u01/app/oracle/grid [oracle@host1 ~]$ srvctl config scan SCAN name: linpe-cluster, Network: 1/9.55.49.0/255.255.255.0/eth0 SCAN VIP name: scan1, IP: /linpe-cluster/ 10.10.46.183 [oracle@host1 ~]# modify scan -n linpe-cluster [oracle@host1 ~]$ srvctl config scan SCAN name: linpe-cluster, Network: 1/9.55.49.0/255.255.255.0/eth0 SCAN VIP name: scan1, IP: /linpe-cluster/ 9.55.49.183

# Displaying the vSwitch configurations    esxcfg-vswitch -l # Add/Delete the vSwitch    esxcfg-vswitch -a esxcfg-vswitch -d # Display all the NIC's       esxcfg-nics -l # Link another NIC to the switch       esxcfg-vswitch -L vmnic1 vSwitch0 # Unlink a NIC from a Switch      esxcfg-vswitch -U vmnic0 vSwitch0 # Display current IP address settings      esxcfg-vmknic -l # Change the Service console network      esxcfg-vmknic "Management Network" -i 192.168.0.190 -n 255.255.255.0 # Delete/Add the Service Console from a vWsiwtchx      escxfg-vswitch vSwitch0 -D "Service_Console_name"      esxcfg-vswitch -A "Service_Console_name" vSwitch0 # Add VLAN to the Service Console      esxcfg-vswitch vSwitch0 -p "Service_Console_name" -v 0 # Delete/add the Service Console interface ...

Oringial from http://zhefeng.wordpress.com/2009/02/02/change-ip-address-for-oracle-rac-public-and-vip-interfaces/ 1. Current Environment  1). Machine IP:  Node1: vmrac01  Node2: vmrac02 ## eth1-Public  10.50.96.101 vmrac01 vmrac01.test.com  10.50.96.102 vmrac02 vmrac02.test.com  ## eth0-Private  192.168.199.1 vmracprv01 vmracprv01.test.com  192.168.199.2 vmracprv02 vmracprv02.test.com  ## VIP  10.50.96.103 vmracvip01 vmracvip01.test.com  10.50.96.104 vmracvip02 vmracvip02.test.com 2). cluster information:  cluster name – vm10cls  database name – v10c  Instance 1 – v10c1  Instance 2 – v10c2  Node1 – vmrac01  Node2 – vmrac02 2. New IP changing map(different subnet mask too):  10.50.96.101/255.255.255.0 vmrac01 –&gt; 10.50.99.41/255.255.252.0  10.50.96.102/255.255.255.0 vmrac02 –&gt; 10.50.99.42/255.255.252.0  10.50.96.103/255.255.255.0 vmracvip01 –&gt; 10.50.99.43/255.255.252...

Modify /etc/hosts (ip) Modify /etc/sysconfig/network (IP & gateway Modify /etc/sysconfig/network-scripts/ifcfg-vswif[number]. By default, it should be 0 Or you can change it on fly: ifconfig ifcfg-vswif0 inet netmask broadcast up Useful tips (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1000266): To delete and recreate a virtual switch and Service Console from the command line: Note: On your system the vswif, vmnic, vSwitch numbers and network settings are different. 1. Run the following command to list the name of the vswif adapter: # esxcfg-vswif -l 2. Run the following command to delete the vswif adapter: # esxcfg-vswif --del vswif0 3. Run the following command to list the name of the vSwitch: # esxcfg-vswitch -l 4. Run the following command to delete the vSwitch: # esxcfg-vswitch -d vSwitch0 5. Run the following command to create the vSwitch: # esxcfg-vswitch -a vSwitch0 6. Run the following commands to create de...

Here is the error message: Command: MLSD Error: Connection timed out Error: Failed to retrieve directory listing Check the firewall. It happens to me that I have to open inbound and outbound traffic. Disable the firewall first and try if it works.

If you could not access the local computer, please check the firewall. By the default, the firewall allows all on Lo interface for the incoming package How about outbound? You need to open the outbound traffic for Lo interface, too iptables -L -nv --line-numbers iptables -v -I OUTPUT 1 -i LO -j ACCEPT