06-30-2015 10:24 AM
Hi all,
Our environment as the following:
OS: redhat 6.5
VCS: VCS 6.2.1
Our server have two physical network port, namely eth0 and eth1.
We do create tagged vlan, vlan515, vlan516, vlan518, vlan520 based on eth0 and eth1.
We are able to create resource IP on vlan518 and failover between two nodes.
However, when we create resource IP on vlan515, it is not able to bring it online.
According to the link, https://support.symantec.com/en_US/article.TECH214469.html,
It knows that duplicate mac address would cause the problem.
However, it can't figure out where "MACAddress" attribute in VCS Java Console as mentioned in the solution.
I did manually add "MACAddress" attribute on main.cf on either NIC or IP resource, it come with not support with haconf -verify command.
Any hints or solution for the problem when configure the IP agent resource on same mac address?
Thanks,
Xentar
Solved! Go to Solution.
07-01-2015 12:54 AM
Just checking you already have an IP on vlan515 as VCS IP agent only adds logical IPs, not the base IP.
Mike
06-30-2015 10:55 AM
Hi Xentar,
The tech note that you point to is for Windows servers only. The solution does not apply to other platforms.
Maybe one of the Linux Gurus will chime in here on how to configure this in Linux.
Thank you,
Wally
06-30-2015 11:04 AM
Hi Wally,
Thanks for the remind.
Any Linux solution offer for it.?
Thanks,
Xentar
06-30-2015 11:12 AM
Hi Xentar,
Sorry, I'm a windows guy. I'm hoping that one of the guys that support linux can respond.
Thank you,
Wally
06-30-2015 11:14 AM
Can you provide:
output from "ifconfig -a"
extract from main.cf (in /etc/VRTSvcs/conf/config) of your IP and resources
extract from engine_A.log (in /var/VRTSvcs/log) when you try to online the resource
Have you tried manually adding a virtual IP to the interface - does this work.
Mike
07-01-2015 12:54 AM
Just checking you already have an IP on vlan515 as VCS IP agent only adds logical IPs, not the base IP.
Mike
07-01-2015 01:46 AM
Hi Mike,
Yes, vlan515 already had IP on both two hosts. And we would like to add a VIP in order to failover between node.
ifconfig -a as the following:
[root@FSCSTGU2 bin]# ifconfig -a
Bond0 Link encap:Ethernet HWaddr E0:97:96:15:A6:83
inet addr:10.30.212.117 Bcast:10.30.212.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a683/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2060546 errors:0 dropped:0 overruns:0 frame:0
TX packets:152654 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560276958 (534.3 MiB) TX bytes:35047087 (33.4 MiB)
Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes.
Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly.
Ifconfig is obsolete! For replacement check ip.
Bond1 Link encap:InfiniBand HWaddr A0:00:02:20:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00
inet addr:172.21.50.117 Bcast:172.21.50.255 Mask:255.255.255.0
UP BROADCAST MASTER MULTICAST MTU:64512 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Bond2 Link encap:Ethernet HWaddr E0:97:96:15:A6:87
inet6 addr: fe80::e297:96ff:fe15:a687/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:607287 errors:0 dropped:0 overruns:0 frame:0
TX packets:19465 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:37633374 (35.8 MiB) TX bytes:1473020 (1.4 MiB)
bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr E0:97:96:15:A6:83
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:932425 errors:0 dropped:0 overruns:0 frame:0
TX packets:96628 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:358298947 (341.7 MiB) TX bytes:19673520 (18.7 MiB)
Memory:965c0000-965e0000
eth1 Link encap:Ethernet HWaddr E0:97:96:15:A6:87
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:402343 errors:0 dropped:0 overruns:0 frame:0
TX packets:19371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25152850 (23.9 MiB) TX bytes:1465006 (1.3 MiB)
Memory:96580000-965a0000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:187464 errors:0 dropped:0 overruns:0 frame:0
TX packets:187464 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16206077 (15.4 MiB) TX bytes:16206077 (15.4 MiB)
vlan515 Link encap:Ethernet HWaddr E0:97:96:15:A6:87
inet addr:10.30.215.103 Bcast:10.30.215.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a687/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:636 (636.0 b)
vlan516 Link encap:Ethernet HWaddr E0:97:96:15:A6:87
inet addr:10.30.216.102 Bcast:10.30.216.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a687/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:636 (636.0 b)
vlan518 Link encap:Ethernet HWaddr E0:97:96:15:A6:83
inet addr:10.30.218.111 Bcast:10.30.218.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a683/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:257 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10828 (10.5 KiB) TX bytes:636 (636.0 b)
vlan520 Link encap:Ethernet HWaddr E0:97:96:15:A6:83
inet addr:172.21.20.114 Bcast:172.21.20.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a683/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:636 (636.0 b)
vlan521 Link encap:Ethernet HWaddr E0:97:96:15:A6:87
inet addr:172.21.21.114 Bcast:172.21.21.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe15:a687/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:1709 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:90444 (88.3 KiB) TX bytes:1762 (1.7 KiB)
[root@FSCSTGU2 bin]#
While main.cf as the following:
include "OracleASMTypes.cf"
include "types.cf"
include "Db2udbTypes.cf"
include "OracleTypes.cf"
include "SybaseTypes.cf"
cluster FSCVCSU (
UserNames = { admin = fklDkfKhlGllJtlFki }
Administrators = { admin }
)
system FSCSTGU1 (
)
system FSCSTGU2 (
)
group FSCSTGU1_SG (
SystemList = { FSCSTGU1 = 0, FSCSTGU2 = 1 }
AutoStartList = { FSCSTGU1, FSCSTGU2 }
)
IP FSCSTGU1_OS_IP (
Critical = 0
Device = vlan518
Address = "10.30.218.120"
NetMask = "255.255.255.0"
)
NIC FSCSTGU1_OS_NIC (
Critical = 0
Device = vlan518
)
FSCSTGU1_OS_IP requires FSCSTGU1_OS_NIC
// resource dependency tree
//
// group FSCSTGU1_SG
// {
// IP FSCSTGU1_OS_IP
// {
// NIC FSCSTGU1_OS_NIC
// }
// }
group ODSDBU1_SG (
SystemList = { FSCSTGU1 = 0, FSCSTGU2 = 1 }
AutoStartList = { FSCSTGU1, FSCSTGU2 }
)
IP ODSDBU1_IP (
Critical = 0
Device = vlan515
Address = "10.30.215.101"
NetMask = "255.255.255.0"
)
NIC ODSDBU1_NIC (
Critical = 0
Device @FSCSTGU1 = vlan515
Device @FSCSTGU2 = vlan515
)
ODSDBU1_IP requires ODSDBU1_NIC
// resource dependency tree
//
// group ODSDBU1_SG
// {
// IP ODSDBU1_IP
// {
// NIC ODSDBU1_NIC
// }
// }
We do have vlan518 able to online, while it doesn't online for vlan515. However, if we change vlan515 to vlan516 while other keep the same, resource IP ODSDBU1_IP able to online.
Thanks,
Xentar
07-01-2015 05:04 AM
Hello Xentar,
Please provide us with the ifcfg-ethX.X files for the VLAN configuration along with resource configuration from main.cf and the error you are seeing in engine_A.log.
Thank You,
Ed Cook
07-01-2015 07:01 AM
Hi Mike, Ed and other,
Attached please find the main.cf and the output of ifconfig -a.
From main.cf, we can online resource IP FSCSTGU1_OS_IP, with vlan518, but we can't bring resource IP ODSDBU1_IP with vlan515.
However, if we change vlan515 to vlan516 in ip and nic, which we can bring IP ODSDBU1_IP online.
And the message shows from engine_A.log as the following:
2015/07/01 02:10:27 VCS INFO V-16-1-50135 User admin fired command: hares -online ODSDBU1_IP FSCSTGU1 from ::ffff:10.30.212.220
2015/07/01 02:10:27 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group ODSDBU1_SG on all nodes
2015/07/01 02:10:27 VCS NOTICE V-16-1-10301 Initiating Online of Resource ODSDBU1_IP (Owner: Unspecified, Group: ODSDBU1_SG) on System FSCSTGU1
2015/07/01 02:12:29 VCS ERROR V-16-2-13066 (FSCSTGU1) Agent is calling clean for resource(ODSDBU1_IP) because the resource is not up even after online completed.
2015/07/01 02:12:30 VCS INFO V-16-2-13068 (FSCSTGU1) Resource(ODSDBU1_IP) - clean completed successfully.
2015/07/01 02:12:30 VCS INFO V-16-2-13071 (FSCSTGU1) Resource(ODSDBU1_IP): reached OnlineRetryLimit(0).
2015/07/01 02:12:30 VCS ERROR V-16-1-54031 Resource ODSDBU1_IP (Owner: Unspecified, Group: ODSDBU1_SG) is FAULTED on sys FSCSTGU1
2015/07/01 02:12:30 VCS NOTICE V-16-1-10446 Group ODSDBU1_SG is offline on system FSCSTGU1
2015/07/01 02:12:30 VCS INFO V-16-6-15015 (FSCSTGU1) hatrigger:/opt/VRTSvcs/bin/triggers/resfault is not a trigger scripts directory or can not be executed
Thanks,
Xentar
07-01-2015 07:14 AM
Could you also provide IP_A.log (in /var/VRSTvcs/log) and have you tried to do add logical IP manually:
ifconfig vlan515:1 10.30.215.101 netmask 255.255.255.0 up
Mike
07-01-2015 07:19 AM
Please enable debug logs and fire the Online
# hatype -modify NIC LogDbg 1 2 3 4 5
# hatype -modify IP LogDbg 1 2 3 4 5
Provide out of the logs from engine_A.log
07-01-2015 08:30 AM
Xentar,
PLease provide the /etc/sysconfig/network-scripts/ifcfg-<interface> files as well. This will give us a better idea how the networking is configured.
Thanks,
Ed Cook
07-01-2015 08:14 PM
Hi Mike, Sudhir and others,
Attached please find IP_A.log.
[root@FSCSTGU1 bin]# ifconfig vlan515:1 10.30.215.101 netmask 255.255.255.0 up
[root@FSCSTGU1 bin]# ifconfig vlan515
vlan515 Link encap:Ethernet HWaddr E0:97:96:13:FF:E5
inet addr:10.30.215.102 Bcast:10.30.215.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe13:ffe5/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:155 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7722 (7.5 KiB) TX bytes:6180 (6.0 KiB)
[root@FSCSTGU1 bin]# ifconfig vlan515:1
vlan515:1 Link encap:Ethernet HWaddr E0:97:96:13:FF:E5
inet addr:10.30.215.101 Bcast:10.30.215.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
From IP_A.log
2015/07/01 02:28:40 VCS DBG_AGDEBUG Calling monitor for resource ODSDBU1_IP
VCSAgType.C:call_monitor[1492]
2015/07/01 02:28:40 VCS DBG_1 IP:ODSDBU1_IP:monitor:device vlan515 address 10.30.215.101 netmask 255.255.255.0 IP.C:ip_monitor[203]
2015/07/01 02:28:40 VCS DBG_1 IP:ODSDBU1_IP:monitor:Number of Interfaces: 9
IP.C:ip_monitor[234]
2015/07/01 02:28:40 VCS DBG_5 IP:ODSDBU1_IP:monitor:Gathering status of device v lan515
IP.C:ip_monitor[255]
2015/07/01 02:28:40 VCS DBG_5 IP:ODSDBU1_IP:monitor:Interface vlan515 address do es not match
IP.C:get_ipv4_status[371]
2015/07/01 02:28:40 VCS DBG_AGINFO Resource(ODSDBU1_IP) - monitor entry point exited with a confidence value 0.
VCSAgType.C:call_monitor[1584]
2015/07/01 02:28:40 VCS DBG_AGINFO ODSDBU1_IP reported state (Offline) & conf_le vel (0)
VCSAgRes.C:call_entry_point[1599]
2015/07/01 02:28:40 VCS DBG_AGDEBUG Canceling timer for (ODSDBU1_IP) op(1608)
VCSAgTimer.C:_cancel[947]
It shows that VCS DBG_5 IP:ODSDBU1_IP:monitor:Interface vlan515 address does not matchIP.C:get_ipv4_status[371], but it can be manually added by ifconfig command as the above.
Thanks,
Xentar
07-01-2015 08:17 PM
Hi Ed,
[root@FSCSTGU1 network-scripts]# more ifcfg-vlan515
DEVICE=vlan515
IPADDR=10.30.215.102
NETMASK=255.255.255.0
BOOTPROTO=none
PHYSDEV=Bond2
ONBOOT=yes
USERCTL=no
VLAN=yes
[root@FSCSTGU1 network-scripts]# more ifcfg-vlan518
DEVICE=vlan518
IPADDR=10.30.218.110
NETMASK=255.255.255.0
BOOTPROTO=none
PHYSDEV=Bond0
ONBOOT=yes
USERCTL=no
VLAN=yes
[root@FSCSTGU1 network-scripts]# more ifcfg-vlan516
DEVICE=vlan516
IPADDR=10.30.216.101
NETMASK=255.255.255.0
BOOTPROTO=none
PHYSDEV=Bond2
ONBOOT=yes
USERCTL=no
VLAN=yes
Thanks,
Xentar
07-01-2015 08:18 PM
Hi Mike, Sudhir and others,
Attached please find IP_A.log.
[root@FSCSTGU1 bin]# ifconfig vlan515:1 10.30.215.101 netmask 255.255.255.0 up
[root@FSCSTGU1 bin]# ifconfig vlan515
vlan515 Link encap:Ethernet HWaddr E0:97:96:13:FF:E5
inet addr:10.30.215.102 Bcast:10.30.215.255 Mask:255.255.255.0
inet6 addr: fe80::e297:96ff:fe13:ffe5/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:155 errors:0 dropped:0 overruns:0 frame:0
TX packets:142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7722 (7.5 KiB) TX bytes:6180 (6.0 KiB)
[root@FSCSTGU1 bin]# ifconfig vlan515:1
vlan515:1 Link encap:Ethernet HWaddr E0:97:96:13:FF:E5
inet addr:10.30.215.101 Bcast:10.30.215.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
From IP_A.log, it shows that VCS DBG_5 IP:ODSDBU1_IP:monitor:Interface vlan515 address does not matchIP.C:get_ipv4_status[371],
but it can be manually added by ifconfig command as the above.
Thanks,
Xentar
07-01-2015 08:45 PM
Hi sudhir,
IP_A.log with debug logs enable,
2015/07/02 19:43:40 VCS DBG_FFDC Generating FFDC for resource (ODSDBU1_IP) as monitor entry point reported OFFLINE after online operation
==============================================
2015/07/02 19:43:40 VCS DBG_AGDEBUG Calling monitor for resource ODSDBU1_IP
VCSAgType.C:call_monitor[1492]
2015/07/02 19:43:40 VCS DBG_1 IP:ODSDBU1_IP:monitor:device vlan515 address 10.30.215.101 netmask 255.255.255.0
IP.C:ip_monitor[203]
2015/07/02 19:43:40 VCS DBG_1 IP:ODSDBU1_IP:monitor:Number of Interfaces: 9
IP.C:ip_monitor[234]
2015/07/02 19:43:40 VCS DBG_5 IP:ODSDBU1_IP:monitor:Gathering status of device vlan515
IP.C:ip_monitor[255]
2015/07/02 19:43:40 VCS DBG_5 IP:ODSDBU1_IP:monitor:Interface vlan515 address does not match
IP.C:get_ipv4_status[371]
2015/07/02 19:43:40 VCS DBG_AGINFO Resource(ODSDBU1_IP) - monitor entry point exited with a confidence value 0.
VCSAgType.C:call_monitor[1584]
2015/07/02 19:43:40 VCS DBG_AGINFO ODSDBU1_IP reported state (Offline) & conf_level (0)
VCSAgRes.C:call_entry_point[1599]
2015/07/02 19:43:40 VCS DBG_AGDEBUG Canceling timer for (ODSDBU1_IP) op(1608)
VCSAgTimer.C:_cancel[947]
==============================================
2015/07/02 19:43:40 VCS ERROR V-16-2-13066 Thread(4134534000) Agent is calling clean for resource(ODSDBU1_IP) because the resource is not up even after online completed.
2015/07/02 19:43:41 VCS DBG_FFDC Generating FFDC for resource (ODSDBU1_IP) as clean entry point completed successfully
==============================================
2015/07/02 19:43:40 VCS DBG_AGDEBUG Calling clean for resource ODSDBU1_IP
VCSAgType.C:call_clean[1051]
2015/07/02 19:43:40 VCS DBG_AGDEBUG Calling exec_script without passing container information
VCSAgType.C:_exec_script[3371]
2015/07/02 19:43:40 VCS DBG_AGDEBUG Value of VCSAgResEPStruct is {ResName=ODSDBU1_IP, EpName=clean, EpEnum=2, ConfLevel=6372561, MonitorInfo=-166723568}
VCSAgProcess.C:exec_script[1887]
2015/07/02 19:43:40 VCS DBG_AGDEBUG child pid is - 70349
VCSAgProcess.C:exec_script[2116]
2015/07/02 19:43:41 VCS DBG_AGDEBUG script (/opt/VRTSvcs/bin/IP/clean) exited with status (0)
VCSAgProcess.C:exec_script[2200]
2015/07/02 19:43:41 VCS DBG_AGINFO Resource(ODSDBU1_IP) - clean entry point exited with a return value 0.
VCSAgType.C:call_clean[1079]
2015/07/02 19:43:41 VCS DBG_AGINFO Resource(ODSDBU1_IP) - Clean was successful.
VCSAgType.C:call_clean[1085]
2015/07/02 19:43:41 VCS DBG_AGDEBUG Canceling timer for (ODSDBU1_IP) op(1603)
VCSAgTimer.C:_cancel[947]
==============================================
2015/07/02 19:43:41 VCS ERROR V-16-2-13068 Thread(4134534000) Resource(ODSDBU1_IP) - clean completed successfully.
2015/07/02 19:43:41 VCS ERROR V-16-2-13071 Thread(4134534000) Resource(ODSDBU1_IP): reached OnlineRetryLimit(0).
2015/07/02 19:43:41 VCS DBG_1 V-16-50-0 IP:ODSDBU1_IP:monitor:device vlan515 address 10.30.215.101 netmask 255.255.255.0
IP.C:ip_monitor[203]
2015/07/02 19:43:41 VCS DBG_1 V-16-50-0 IP:ODSDBU1_IP:monitor:Number of Interfaces: 9
IP.C:ip_monitor[234]
2015/07/02 19:43:41 VCS DBG_5 V-16-50-0 IP:ODSDBU1_IP:monitor:Gathering status of device vlan515
IP.C:ip_monitor[255]
2015/07/02 19:43:41 VCS DBG_5 V-16-50-0 IP:ODSDBU1_IP:monitor:Interface vlan515 address does not match
IP.C:get_ipv4_status[371]
2015/07/02 19:43:41 VCS DBG_FFDC Generating FFDC for resource (ODSDBU1_IP) as monitor entry point reported OFFLINE after online operation
==============================================
2015/07/02 19:43:41 VCS DBG_AGDEBUG Calling monitor for resource ODSDBU1_IP
VCSAgType.C:call_monitor[1492]
2015/07/02 19:43:41 VCS DBG_1 IP:ODSDBU1_IP:monitor:device vlan515 address 10.30.215.101 netmask 255.255.255.0
IP.C:ip_monitor[203]
2015/07/02 19:43:41 VCS DBG_1 IP:ODSDBU1_IP:monitor:Number of Interfaces: 9
IP.C:ip_monitor[234]
2015/07/02 19:43:41 VCS DBG_5 IP:ODSDBU1_IP:monitor:Gathering status of device vlan515
IP.C:ip_monitor[255]
2015/07/02 19:43:41 VCS DBG_5 IP:ODSDBU1_IP:monitor:Interface vlan515 address does not match
IP.C:get_ipv4_status[371]
2015/07/02 19:43:41 VCS DBG_AGINFO Resource(ODSDBU1_IP) - monitor entry point exited with a confidence value 0.
VCSAgType.C:call_monitor[1584]
2015/07/02 19:43:41 VCS DBG_AGINFO ODSDBU1_IP reported state (Offline) & conf_level (0)
VCSAgRes.C:call_entry_point[1599]
2015/07/02 19:43:41 VCS DBG_AGDEBUG Canceling timer for (ODSDBU1_IP) op(1608)
VCSAgTimer.C:_cancel[947]
==============================================
Thanks,
Xentar
07-01-2015 08:55 PM
Hi Sudhir,
Attache please find IP_A.log with debug log enabled.
Thanks,
Xentar
07-02-2015 01:03 AM
I would log a call with Symantec as I believe get_ipv4_status is a Symantec program (as oppose to an O/S library) and it looks as though this is not working correctly.
Mike
07-02-2015 07:58 AM
Going over the IP_A.log now.
What interfaces make up bond0 and bond2?
EDIT:
Please collect a Veritas explorer from each node in the cluster. This will provide us with the logs and configuraiton information needed to move forward.
Thank You,
Ed Cook
07-02-2015 10:02 AM
Hi Ed,
I do only have one node VRTSexploer in hand right now.
bond0 and bond2 is formed by eth0 and eth1. Thanks for your help.
Thanks,
Xentar