So I created some scripts that help me to manage some things.
One of this is the information on the SCANs
The SCAN port, the SCAN name and the network interface where the SCAN listeners are configured are different. So, in order to check the information of the SCAN configuration, I wrote following script
The output is something like this
###################################################################
########################### SCAN info #############################
###################################################################
Scan Name : nodecl-scan
Scan Port : 1555
Dedined on : Network: 1
Subnet IPv4 : 10.10.226.0/255.255.254.0
Network Card : eth0
LISTENER_SCAN1: 10.10.227.38/eth0:2 (ONLINE on node01)
LISTENER_SCAN2: 10.10.227.39/eth0:3 (ONLINE on node02)
LISTENER_SCAN3: 10.10.227.40/eth0:3 (ONLINE on node01)
###################################################################
As you can see, the output shows also the interface where the listener is bound. In this case, on the node01, the listeners are on eth0:2 and eth0:3 with 10.10.267.38 and 10.10.267.40, respectively. On the node02 instead, the SCAN listener 2, with IP address 10.10.267.39, is on eth0:3
In case of the crs is down, the script returns the following error
>>>>> CRS is not working correctly <<<<<
>>>>> Check the crs status <<<<<
CRS-6750: unable to get the active version CRS-6752: Active version query failed