{"id":2205,"date":"2013-04-03T12:43:06","date_gmt":"2013-04-03T09:43:06","guid":{"rendered":"http:\/\/www.koraykey.com\/?p=2205"},"modified":"2013-06-26T23:54:57","modified_gmt":"2013-06-26T20:54:57","slug":"linux-isletim-sistemlerinde-oracle-rac-scan-ip-kullanimi-icin-dns-yapilandirmasi","status":"publish","type":"post","link":"https:\/\/www.koraykey.com\/?p=2205","title":{"rendered":"Linux \u0130\u015fletim Sistemlerinde Oracle RAC Scan IP Kullan\u0131m\u0131 i\u00e7in DNS Yap\u0131land\u0131rmas\u0131"},"content":{"rendered":"

\"OracleScanIP\"<\/a><\/p>\n

Bu makalemizde Oracle 11g R2 ile kar\u015f\u0131m\u0131za \u00e7\u0131kan Oracle SCAN IP \u00f6zelli\u011fini ve bunun kullan\u0131m\u0131 i\u00e7in DNS yap\u0131land\u0131rmam\u0131z\u0131 inceleyece\u011fiz. Bu yap\u0131land\u0131rma ortam\u0131m\u0131zda bir DNS sunucusu yoksa yap\u0131lacak i\u015flemdir.\u00a0E\u011fer ortam\u0131m\u0131zda bir DNS sunucusu varsa Oracle RAC i\u00e7in Scan IP adreslerini bu DNS sunucumuza kaydetmemiz yeterlidir.\u00a0B\u00f6yle bir durumda\u00a0sunucumuzda DNS servisinin “Round-robin” \u00f6zelli\u011finin a\u00e7\u0131k oldu\u011fundan emin olmal\u0131y\u0131z.<\/span><\/p>\n

Oracle SCAN IP nedir ?<\/span><\/strong><\/p>\n

Tam a\u00e7\u0131l\u0131m\u0131 Single Client Access Name’dir. Oracle 11gR2 ile gelen \u00f6zelliklerden biri olan SCAN, k\u0131saca network i\u00e7erisinde 3 adet sanal IP adresinin tek bir DNS kayd\u0131na ba\u011flanmas\u0131 i\u015flemidir. GNS ve DHCP sistemleriyle birlikte kullan\u0131ld\u0131\u011f\u0131nda Oracle Clusterware SCAN ismiyle network \u2018de sanal IP adresleri olu\u015fturarak bunlar\u0131 \u00e7al\u0131\u015fan\u00a0\u00fcyeler \u00fczerine atar. SCAN isimli sanal IP adresleri\u00a0\u00fcyeler \u00fczerinde bulut yap\u0131s\u0131nda \u00e7al\u0131\u015farak “Load Balancing” ve “Failover” ayarlar\u0131na g\u00f6re gerekti\u011finde\u00a0\u00fcyeler \u00fczerinde yer de\u011fi\u015ftirebilir. \u0130stemciler bu IP adreslerinin kullanarak veritaban\u0131na ba\u011flant\u0131 sa\u011flar.<\/span><\/p>\n

1. \u00d6ncelikle sunucumuzda DNS Paketlerimizi y\u00fckl\u00fcyoruz.<\/span><\/p>\n

# yum -y install bind<\/span><\/pre>\n
2. Sunucumuzda<\/span> Dns yap\u0131land\u0131rma dosyam\u0131z “\/etc\/named.conf”\u00a0i\u00e7erisinde DNS Sunucu adresimizi ve isim \u00e7\u00f6z\u00fcmleyemedi\u011fi durumlarda y\u00f6nlendirece\u011fi DNS adreslerimizi d\u00fczenliyoruz.<\/span><\/p>\n
# vim \/etc\/named.conf<\/span>\r\n-- Dosyas\u0131nda a\u015fa\u011f\u0131daki sat\u0131rlar\u0131 d\u00fczenliyoruz. <\/span>\r\n-- Burada bold i\u015faretledi\u011fim yerlere kendi sisteminizin bilgilerini yaz\u0131yoruz.<\/span>\r\n\r\n\/\/ named.conf<\/span>\r\n\/\/<\/span>\r\n\/\/ Provided by Red Hat bind package to configure the ISC BIND named(8) DNS<\/span>\r\n\/\/ server as a caching only nameserver (as a localhost DNS resolver only).<\/span>\r\n\/\/<\/span>\r\n\/\/ See \/usr\/share\/doc\/bind*\/sample\/ for example named configuration files.<\/span>\r\n\/\/<\/span>\r\n\r\noptions {<\/span>\r\n        listen-on port 53 { 127.0.0.1; 192.168.2.120<\/strong>; };<\/span>\r\n        listen-on-v6 port 53 { ::1; };<\/span>\r\n        directory       \"\/var\/named\";<\/span>\r\n        dump-file       \"\/var\/named\/data\/cache_dump.db\";<\/span>\r\n        statistics-file \"\/var\/named\/data\/named_stats.txt\";<\/span>\r\n        memstatistics-file \"\/var\/named\/data\/named_mem_stats.txt\";<\/span>\r\n        allow-query     { any; };<\/span>\r\n        recursion yes;<\/span>\r\n\r\n        dnssec-enable yes;<\/span>\r\n        dnssec-validation yes;<\/span>\r\n        dnssec-lookaside auto;<\/span>\r\n\r\n        \/* Path to ISC DLV key *\/<\/span>\r\n        bindkeys-file \"\/etc\/named.iscdlv.key\";<\/span>\r\n\r\n        forwarders { 192.168.2.150<\/strong>; };<\/span>\r\n};<\/span>\r\n\r\nlogging {<\/span>\r\n        channel default_debug {<\/span>\r\n                file \"data\/named.run\";<\/span>\r\n                severity dynamic;<\/span>\r\n        };<\/span>\r\n};<\/span>\r\n\r\nzone \".\" IN {<\/span>\r\n        type hint;<\/span>\r\n        file \"named.ca\";<\/span>\r\n};<\/span>\r\n\r\nzone \"localdomain<\/strong>.\" IN {<\/span>\r\n        type master;<\/span>\r\n        file \"localdomain.zone<\/strong>\";<\/span>\r\n        allow-update { none; };<\/span>\r\n};<\/span>\r\n\r\nzone \"0.168.192<\/strong>.in-addr.arpa.\" IN {<\/span>\r\n        type master;<\/span>\r\n        file \"0.168.192<\/strong>.in-addr.arpa\";<\/span>\r\n        allow-update { none; };<\/span>\r\n};<\/span><\/pre>\n
3. Sunucumuzda “Forward”<\/span>\u00a0DNS kay\u0131tlar\u0131m\u0131z\u0131 yapabilmek i\u00e7in “\/var\/named\/localdomain.zone” dosyas\u0131nda gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
# vim \/var\/named\/localdomain.zone\r\n-- Dosyam\u0131z\u0131 a\u00e7\u0131yoruz ve a\u015fa\u011f\u0131daki gibi d\u00fczenliyoruz.\r\n\r\n<\/span>\r\n$TTL    86400<\/span>\r\n@               IN SOA  localhost root.localhost (               <\/span>\r\n                                        42              ; serial (d. adams)<\/span>\r\n                                        3H              ; refresh<\/span>\r\n                                        15M             ; retry<\/span>\r\n                                        1W              ; expiry<\/span>\r\n                                        1D )            ; minimum<\/span>\r\n                IN NS           localhost<\/span>\r\nlocalhost       IN A            127.0.0.1<\/span>\r\nkryrac1         IN A    192.168.2.121<\/span>\r\nkryrac2         IN A    192.168.2.122<\/span>\r\nkryrac1-priv    IN A    192.168.117.141<\/span>\r\nkryrac2-priv    IN A    192.168.117.142<\/span>\r\nkryrac1-priv2   IN A    192.168.117.143<\/span>\r\nkryrac2-priv2   IN A    192.168.117.144<\/span>\r\nkryrac1-vip     IN A    192.168.2.131<\/span>\r\nkryrac2-vip     IN A    192.168.2.132<\/span>\r\nkryrac-scan     IN A    192.168.2.125<\/span>\r\nkryrac-scan     IN A    192.168.2.126<\/span>\r\nkryrac-scan     IN A    192.168.2.127<\/span><\/pre>\n
4. Sunucumuzda Reverse DNS kay\u0131tlar\u0131m\u0131z\u0131 yapabilmek i\u00e7in “\/var\/named\/0.168.192.in-addr.arpa” dosyas\u0131nda gerekli d\u00fczenlemeleri yap\u0131yoruz.<\/span><\/p>\n
# vim \/var\/named\/0.168.192.in-addr.arpa<\/span>\r\n\r\n-- Dosyam\u0131z\u0131 a\u00e7\u0131yoruz ve a\u015fa\u011f\u0131daki gibi d\u00fczenliyoruz.<\/span>\r\nBurada \"reverse\" kay\u0131tlar\u0131n\u0131 olu\u015ftururken atam\u0131\u015f oldu\u011fumuz<\/span>\r\nIP adreslerinin son rakamlar\u0131n\u0131 yaz\u0131yoruz. Di\u011fer k\u0131sm\u0131n\u0131 \"DNS<\/span>\r\nReverse\" \u00f6zelli\u011fi tamamlayacakt\u0131r.<\/span>\r\n\r\n$ORIGIN 0.168.192.in-addr.arpa.<\/span>\r\n$TTL 1H<\/span>\r\n@       IN      SOA     koraykey.localdomain.     root.koraykey.localdomain. (      2<\/span>\r\n                                                3H<\/span>\r\n                                                1H<\/span>\r\n                                                1W<\/span>\r\n                                                1H )<\/span>\r\n0.168.192.in-addr.arpa.         IN NS      koraykey.localdomain.<\/span>\r\n\r\n121     IN PTR  kryrac1.localdomain.<\/span>\r\n122     IN PTR  kryrac2.localdomain.<\/span>\r\n131     IN PTR  kryrac1-vip.localdomain<\/span>\r\n132     IN PTR  kryrac2-vip.localdomain<\/span>\r\n125     IN PTR  kryrac-scan.localdomain.<\/span>\r\n126     IN PTR  kryrac-scan.localdomain.<\/span>\r\n127     IN PTR  kryrac-scan.localdomain.<\/span><\/pre>\n
5. Sunucumuzda i\u015flemleri tamamlad\u0131ktan sonra servisimizi ba\u015flat\u0131yoruz ve sunucumuz ba\u015flad\u0131\u011f\u0131nda otomatik a\u00e7\u0131lmas\u0131 i\u00e7in gerekli yap\u0131land\u0131rmalar\u0131 yap\u0131yoruz.<\/span><\/p>\n
# service named start<\/span>\r\nStarting named:                   [  OK  ]\r\n\r\n# chkconfig named on<\/span><\/pre>\n
6. Sunucumuzda DNS yap\u0131land\u0131rmam\u0131z tamamlad\u0131. \u015eimdi isim \u00e7\u00f6z\u00fcmleyecek sunucular\u0131m\u0131z \u00fczerinde “\/etc\/resolv.conf” dosyas\u0131na yap\u0131land\u0131rd\u0131\u011f\u0131m\u0131z bu sunucumuzun adresini giriyoruz.<\/span><\/p>\n
# vim \/etc\/resolv.conf<\/span>\r\n\r\n-- Dosyas\u0131n\u0131 a\u00e7\u0131p a\u015fa\u011f\u0131daki d\u00fczenlemeleri <\/span>yap\u0131yoruz.<\/span>\r\n\r\nsearch localdomain<\/span>\r\nnameserver 192.168.2.120<\/span><\/pre>\n
7. Bu d\u00fczenlemeleri yapt\u0131ktan sonra sistemimizi test edebiliriz. \u00d6zellikler Oracle RAC kurulumu yap\u0131lacak sunucular \u00fczerinde isimlendirmeleri \u00e7\u00f6zebildi\u011fine emin olmal\u0131y\u0131z. Aksi takdirde kurulum i\u015fleminde s\u0131k\u0131nt\u0131lar \u00e7\u0131kacakt\u0131r.<\/span><\/p>\n
# nslookup kryrac-scan<\/span>\r\nServer:         192.168.2.120<\/span>\r\nAddress:        192.168.2.120#53<\/span>\r\n\r\nName:   kryrac-scan.localdomain<\/span>\r\nAddress: 192.168.2.126<\/span>\r\nName:   kryrac-scan.localdomain<\/span>\r\nAddress: 192.168.2.127<\/span>\r\nName:   kryrac-scan.localdomain<\/span>\r\nAddress: 192.168.2.125<\/span>\r\n\r\n# nslookup kryrac1<\/span>\r\nServer:         192.168.2.120<\/span>\r\nAddress:        192.168.2.120#53<\/span>\r\n\r\nName:   kryrac1.localdomain<\/span>\r\nAddress: 192.168.2.121<\/span>\r\n\r\n# nslookup kryrac2<\/span>\r\nServer:         192.168.2.121<\/span>\r\nAddress:        192.168.2.121#53<\/span>\r\n\r\nName:   kryrac2.localdomain<\/span>\r\nAddress: 192.168.2.122<\/span><\/pre>\n
Bu makalemizdeki Linux \u0130\u015fletim Sistemlerinde Oracle RAC Scan IP Kullan\u0131m\u0131 i\u00e7in DNS Yap\u0131land\u0131rmas\u0131n\u0131 inceledik. Yap\u0131land\u0131rmam\u0131z\u0131 test ortamlar\u0131m\u0131z veya daha k\u00fc\u00e7\u00fck a\u011f ortamlar\u0131nda DNS sunucusu kurmadan yapmak i\u00e7in “Linux \u0130\u015fletim Sistemlerinde Basit DNS Yap\u0131land\u0131rmas\u0131”<\/a> makalemizi inceleyebilirsiniz.\u00a0Bu makalemizdeki\u00a0uygulanan ad\u0131mlar \u201cOracle Enterprise Linux 6.4\u2033 i\u015fletim sistemi \u00fczerinde test edilmi\u015ftir. Di\u011fer Linux da\u011f\u0131t\u0131mlar\u0131yla uyumludur. Bu a\u015famadan sonra Oracle RAC Kurulumu yapacaksak “Oracle Enterprise Linux \u0130\u015fletim Sisteminde Oracle Real Application Cluster (Rac) Veritaban\u0131 Kurulumu”<\/a> makalemizden yararlanabilirsiniz.<\/span><\/p>\n
Ba\u015fka bir makalede g\u00f6r\u00fc\u015fmek \u00fczere\u2026<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
Bu makalemizde Oracle 11g R2 ile kar\u015f\u0131m\u0131za \u00e7\u0131kan Oracle SCAN IP \u00f6zelli\u011fini ve bunun kullan\u0131m\u0131 i\u00e7in DNS yap\u0131land\u0131rmam\u0131z\u0131 inceleyece\u011fiz. Bu yap\u0131land\u0131rma ortam\u0131m\u0131zda bir DNS sunucusu yoksa yap\u0131lacak i\u015flemdir.\u00a0E\u011fer ortam\u0131m\u0131zda bir DNS sunucusu varsa Oracle RAC i\u00e7in Scan IP adreslerini bu … Okumaya devam et →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,8],"tags":[21,290,20,19,164,163,129,529,162,530,165],"class_list":["post-2205","post","type-post","status-publish","format-standard","hentry","category-oracle","category-unix-linux","tag-h-koray-gunduz","tag-halil-koray-gunduz","tag-koray-gunduz","tag-koraykey","tag-linux-dns","tag-oracle-rac-scan-ip-dns","tag-oracle-scan-ip","tag-oracle-scan-ip-nedir","tag-scan-ip","tag-scan-ip-nedir","tag-single-client-access-name"],"_links":{"self":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts\/2205","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2205"}],"version-history":[{"count":0,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=\/wp\/v2\/posts\/2205\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2205"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2205"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.koraykey.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2205"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}