1. Using the dynamic view gv$cluster_interconnects:
select * from gv$cluster_interconnects ;
INST_ID NAME IP_ADDRESS IS_ SOURCE
---------- --------------- ---------------- --- -------------------------------
1 eth0 192.168.10.1 NO Oracle Cluster Repository
1 eth1 192.168.11.1 NO Oracle Cluster Repository
2 eth0 192.168.10.2 NO Oracle Cluster Repository
2 eth1 192.168.11.2 NO Oracle Cluster Repository
In the above output, the column SOURCE indicates where the private
interconnect info was derived from; this column could be one of OCR, OS
dependent software or cluster_interconnects parameter.
2. Using the clusterware command oifcfg:
$oifcfg getif
eth2 10.104.95.0 global public
eth0 192.168.10.0 global cluster_interconnect
eth1 192.168.11.0 global cluster_interconnect
3. Using oradebug
ipc:
sqlplus “/ as sysdba”SQL>oradebug setmypid
Statement processed.
SQL>oradebug ipc
Information written to trace file.
The above command would dump a trace to user_dump_dest. The last few lines
of the trace would indicate the IP of the cluster interconnect. Below is a
sample output of those lines.
From the trace file on node1:
SSKGXPT 0x5edf558 flags SSKGXPT_READPENDING socket no 9 IP 192.168.11.1 UDP
18852
From the trace file on node2:
SSKGXPT 0x5edf558 flags SSKGXPT_READPENDING socket no 9 IP 192.168.10.2 UDP
38967
No comments:
Post a Comment