RAC Attack - Oracle Cluster Database at Home/SSH and CVU


  1. Login to node collabn2. As the oracle user, make sure that you can ping both nodes on the interconnect and public network.

    [oracle@collabn2 ~]$ ping -c 1 collabn1
    PING collabn1 (192.168.78.51) 56(84) bytes of data.
    64 bytes from collabn1 (192.168.78.51): icmp_seq=1 ttl=64 time=0.793 ms
    
    [oracle@collabn2 ~]$ ping -c 1 collabn2
    PING collabn2 (192.168.78.52) 56(84) bytes of data.
    64 bytes from collabn2 (192.168.78.52): icmp_seq=1 ttl=64 time=0.024 ms
    
    [oracle@collabn2 ~]$ ping -c 1 collabn1-priv
    PING collabn1-priv (172.16.100.51) 56(84) bytes of data.
    64 bytes from collabn1-priv (172.16.100.51): icmp_seq=1 ttl=128 time=0.901 ms
    
    [oracle@collabn2 ~]$ ping -c 1 collabn2-priv
    PING collabn2-priv (172.16.100.52) 56(84) bytes of data.
    64 bytes from collabn2-priv (172.16.100.52): icmp_seq=1 ttl=64 time=0.058 ms
    
  2. Store the public keys for the hosts. You can do this with a tool called ssh-keyscan.

    [oracle@collabn2 .ssh]$ ssh-keyscan -t rsa collabn1 collabn1-priv collabn2 collabn2-priv >> ~/.ssh/known_hosts
    # collabn1 SSH-2.0-OpenSSH_4.3
    # collabn1-priv SSH-2.0-OpenSSH_4.3
    # collabn2 SSH-2.0-OpenSSH_4.3
    # collabn2-priv SSH-2.0-OpenSSH_4.3
    
  3. Test ssh equivilance. It is important that there is no prompt and you are automatically logged in.

    [oracle@collabn2 .ssh]$ ssh collabn1
    Warning: Permanently added the RSA host key for IP address '192.168.78.51' to the list of known hosts.
    Last login: Tue Apr 15 16:59:36 2008 from collabn2
    
    [oracle@collabn1 ~]$ exit
    logout
    Connection to collabn1 closed.
    
  4. Switch to node collabn1. As the oracle user, confirm that you can ping both servers. Then copy the known_hosts file from collabn2.

    [oracle@collabn1 ~]$ ping -c 1 collabn1
    PING collabn1 (192.168.78.51) 56(84) bytes of data.
    64 bytes from collabn1 (192.168.78.51): icmp_seq=1 ttl=64 time=0.793 ms
    
    [oracle@collabn1 ~]$ ping -c 1 collabn2
    PING collabn2 (192.168.78.52) 56(84) bytes of data.
    64 bytes from collabn2 (192.168.78.52): icmp_seq=1 ttl=64 time=0.024 ms
    
    [oracle@collabn1 ~]$ ping -c 1 collabn1-priv
    PING collabn1-priv (172.16.100.51) 56(84) bytes of data.
    64 bytes from collabn1-priv (172.16.100.51): icmp_seq=1 ttl=128 time=0.901 ms
    
    [oracle@collabn1 ~]$ ping -c 1 collabn2-priv
    PING collabn2-priv (172.16.100.52) 56(84) bytes of data.
    64 bytes from collabn2-priv (172.16.100.52): icmp_seq=1 ttl=64 time=0.058 ms
    
    [oracle@collabn1 ~]$ scp collabn2:.ssh/known_hosts ~/.ssh/known_hosts
    The authenticity of host 'collabn2 (192.168.78.52)' can't be established.
    RSA key fingerprint is 3f:65:e6:77:af:11:84:56:a4:b9:0f:8b:41:b4:2f:8a.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'collabn2,192.168.78.52' (RSA) to the list of known hosts.
    known_hosts                                   100% 3146     3.1KB/s   00:00
    
  5. Test ssh equivilance.

    [oracle@collabn1 ~]$ ssh collabn2
    Last login: Tue Apr 15 17:02:29 2008 from collabn2
    
    [oracle@collabn2 ~]$ exit
    logout
    Connection to collabn2 closed.
    
  6. You need to be able to login to yourself too; test this.

    [oracle@collabn1 ~]$ ssh collabn1
    Last login: Tue Apr 15 17:03:39 2008 from collabn2
    [oracle@collabn1 ~]$ exit
    logout
    Connection to collabn1 closed.
    
  7. Run CLUVFY to validate your hardware and OS installation! The shared disk test will fail; this is OK. Ignore that error.

    collabn1:/home/oracle[RAC1]$ /mnt/cdrom*/grid/runcluvfy.sh stage -post hwos -n collabn1,collabn2
    
    Performing post-checks for hardware and operating system setup
    
    Checking node reachability...
    Node reachability check passed from node "collabn1"
    
    Checking user equivalence...
    User equivalence check passed for user "oracle"
    
    Checking node connectivity...
    
    Checking hosts config file...
    
    Verification of the hosts config file successful
    
    Node connectivity passed for subnet "192.168.78.0" with node(s) collabn2,collabn1
    TCP connectivity check passed for subnet "192.168.78.0"
    
    Node connectivity passed for subnet "172.16.100.0" with node(s) collabn2,collabn1
    TCP connectivity check passed for subnet "172.16.100.0"
    
    Interfaces found on subnet "192.168.78.0" that are likely candidates for VIP are:
    collabn2 eth0:192.168.78.52
    collabn1 eth0:192.168.78.51
    
    Interfaces found on subnet "172.16.100.0" that are likely candidates for a private interconnect are:
    collabn2 eth1:172.16.100.52
    collabn1 eth1:172.16.100.51
    
    Node connectivity check passed
    
    Check for multiple users with UID value 0 passed
    
    Post-check for hardware and operating system setup was successful.
    


Next on ASM track: Setup ASMLIB

Next on Shared Filesystem track: Setup OCFS2



Last modified on 5 April 2013, at 05:45