Home » Server Options » RAC & Failsafe » SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS (windows server 2012 , rac 10g)
SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584234] Fri, 10 May 2013 06:36 Go to next message
x-oracle
Messages: 380
Registered: April 2011
Location: gujarat
Senior Member
hello i have to install oracle 10g rac on windows server 2012 during my installation i got this error

SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS

Report message to a moderator

Re: SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584238 is a reply to message #584234] Fri, 10 May 2013 06:53 Go to previous messageGo to next message
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
Senior Member
One possibility is that you have not assigned a fixed static address to each NIC.

Report message to a moderator

Re: SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584240 is a reply to message #584238] Fri, 10 May 2013 07:11 Go to previous messageGo to next message
x-oracle
Messages: 380
Registered: April 2011
Location: gujarat
Senior Member
john i hv assing ip address on both nodes
i have check already

Report message to a moderator

Re: SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584254 is a reply to message #584240] Fri, 10 May 2013 10:32 Go to previous messageGo to next message
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
Senior Member
Can you show the network configuration, for all the nodes in the cluster? Please use ipconfig, and format the results properly with code tags, so it looks like this:
c:\users\john\home>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::9919:1231:50c6:b815%42
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :


Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::d4b3:a724:86b3:a8d6%10
   IPv4 Address. . . . . . . . . . . : 10.0.0.104
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.0.1


c:\users\john\home>
also the hosts files on each machine, properly formatted with [code] tags.

Report message to a moderator

Re: SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584359 is a reply to message #584254] Mon, 13 May 2013 06:27 Go to previous messageGo to next message
x-oracle
Messages: 380
Registered: April 2011
Location: gujarat
Senior Member
ok this are the ip setting in my both nodes


RAC01


C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter PUBLIC:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::b18c:2ea4:63e0:d760%14
   IPv4 Address. . . . . . . . . . . : 192.168.2.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter PRIVATE:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::40a9:ef4e:7bba:37ff%12
   IPv4 Address. . . . . . . . . . . : 192.168.0.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{E33EB267-FCCC-4E49-99CF-10E56E5DBDA8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{C6C486C3-BDF9-42A5-8481-CE7C1B17ACFD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :


on rac 2 server


C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter PUBLIC:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::fd4d:70b0:3e13:34ad%14
   IPv4 Address. . . . . . . . . . . : 192.168.2.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter PRIVATE:

   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 192.168.0.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{E33EB267-FCCC-4E49-99CF-10E56E5DBDA8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{C6C486C3-BDF9-42A5-8481-CE7C1B17ACFD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

C:\Users\Administrator>



host file of rac01
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.

       127.0.0.1      localhost.localdomain    localhost
# public
      192.168.2.101    rac01.localdomain       rac01
      192.168.2.102    rac02.localdomain       rac02
#private
      192.168.0.101    rac01-priv.localdomain  rac01-priv
      192.168.0.102    rac02-priv.localdomain  rac02-priv
#virtual
      192.168.2.111    rac01-vip.localdomain   rac01-vip
      192.168.2.112    rac02-vip.localdomain   rac02-vip


host file of rac02

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.

       127.0.0.1      localhost.localdomain    localhost
# public
      192.168.2.101    rac01.localdomain       rac01
      192.168.2.102    rac02.localdomain       rac02
#private
      192.168.0.101    rac01-priv.localdomain  rac01-priv
      192.168.0.102    rac02-priv.localdomain  rac02-priv
#virtual
      192.168.2.111    rac01-vip.localdomain   rac01-vip
      192.168.2.112    rac02-vip.localdomain   rac02-vip

[Updated on: Tue, 14 May 2013 02:26]

Report message to a moderator

Re: SPECIFY NETWORK INTERFACE USAGE" SCREEN DOESN'T SHOW BOTH INTERFACE CARD DETAILS [message #584445 is a reply to message #584359] Tue, 14 May 2013 07:00 Go to previous message
x-oracle
Messages: 380
Registered: April 2011
Location: gujarat
Senior Member
x-oracle wrote on Mon, 13 May 2013 14:27
ok this are the ip setting in my both nodes


RAC01


C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter PUBLIC:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::b18c:2ea4:63e0:d760%14
   IPv4 Address. . . . . . . . . . . : 192.168.2.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter PRIVATE:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::40a9:ef4e:7bba:37ff%12
   IPv4 Address. . . . . . . . . . . : 192.168.0.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{E33EB267-FCCC-4E49-99CF-10E56E5DBDA8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{C6C486C3-BDF9-42A5-8481-CE7C1B17ACFD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :


on rac 2 server


C:\Users\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter PUBLIC:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::fd4d:70b0:3e13:34ad%14
   IPv4 Address. . . . . . . . . . . : 192.168.2.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter PRIVATE:

   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 192.168.0.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{E33EB267-FCCC-4E49-99CF-10E56E5DBDA8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{C6C486C3-BDF9-42A5-8481-CE7C1B17ACFD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

C:\Users\Administrator>



host file of rac01
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.

       127.0.0.1      localhost.localdomain    localhost
# public
      192.168.2.101    rac01.localdomain       rac01
      192.168.2.102    rac02.localdomain       rac02
#private
      192.168.0.101    rac01-priv.localdomain  rac01-priv
      192.168.0.102    rac02-priv.localdomain  rac02-priv
#virtual
      192.168.2.111    rac01-vip.localdomain   rac01-vip
      192.168.2.112    rac02-vip.localdomain   rac02-vip


host file of rac02

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.

       127.0.0.1      localhost.localdomain    localhost
# public
      192.168.2.101    rac01.localdomain       rac01
      192.168.2.102    rac02.localdomain       rac02
#private
      192.168.0.101    rac01-priv.localdomain  rac01-priv
      192.168.0.102    rac02-priv.localdomain  rac02-priv
#virtual
      192.168.2.111    rac01-vip.localdomain   rac01-vip
      192.168.2.112    rac02-vip.localdomain   rac02-vip



i also successfully ping on both the nodes

From rac01 server

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ping 192.168.2.102 -t

Pinging 192.168.2.102 with 32 bytes of data:
Reply from 192.168.2.102: bytes=32 time=1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128
Reply from 192.168.2.102: bytes=32 time<1ms TTL=128




C:\Users\Administrator>ping 192.168.0.102  -t

Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.102: bytes=32 time=1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128
Reply from 192.168.0.102: bytes=32 time<1ms TTL=128


From RAC02 server
C:\Users\Administrator>ping 192.168.2.101 -t

Pinging 192.168.2.101 with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time=1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128



C:\Users\Administrator>ping 192.168.0.101 -t

Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time=1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128

Report message to a moderator

Previous Topic: Manual failover to standby db without RAC and DG?
Next Topic: Need Help to Create Shared file system between two Desktop PC
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Mon Feb 03 02:51:35 CST 2025
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.