Srvctl Config VIP
Before checking the status of VIP by srvctl, we need to know VIP name in this cluster.
[grid@primary01 ~]$ srvctl config vip -node primary01
VIP exists: network number 1, hosting node primary01
VIP Name: primary01-vip
VIP IPv4 Address: 192.168.1.111
VIP IPv6 Address:
VIP is enabled.
VIP is individually enabled on nodes:
VIP is individually disabled on nodes:
The VIP name on the first node is primary01-vip.
[grid@primary01 ~]$ srvctl config vip -node primary02
VIP exists: network number 1, hosting node primary02
VIP Name: primary02-vip
VIP IPv4 Address: 192.168.1.112
VIP IPv6 Address:
VIP is enabled.
VIP is individually enabled on nodes:
VIP is individually disabled on nodes:
The VIP name on the second node is primary02-vip.
Actually, node name (-node) or VIP name (-vip) can be interchangeably used as an argument in srvctl status vip command.
Next, we'll use VIP name (-vip) to display their respective status.
Srvctl Status VIP
Let's see what status of the first VIP.
[grid@primary01 ~]$ srvctl status vip -vip primary01-vip
VIP 192.168.1.111 is enabled
VIP 192.168.1.111 is running on node: primary01
Another VIP might look like this:
[grid@primary01 ~]$ srvctl status vip -vip primary02-vip
VIP 192.168.1.112 is enabled
VIP 192.168.1.112 is running on node: primary01
Please note that, the VIP has been failover to another node. Even though it's running, it's not working. We have explained the whole case pretty much in How Oracle RAC VIP Failover to Another Node.