janet_marshal
19 years agoLevel 2
VCS IPmultiNICB Errors
Hi,
we are runninig the VCS 4.1 symetric cluster on two nodes.
I installed the MP1 patch for veritas foundation suite 4.1 after that license for veritas is expired and my cluster was unable to come online.
according to veritas its a known bug and they are working on it meanwhile they gave me a temp license which i applied to cluster through #vxlicinst -k.
Now the cluster is up but it unable to load the service groups and it seems it because of IPMULTINICB resource
I would appreciate if any one can help me in this regard i am sending the error message
2006/01/03 18:05:08 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:02:55 2006
2006/01/03 18:05:08 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:05:08 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:05:08 2006
2006/01/03 18:07:20 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:05:08 2006
2006/01/03 18:07:20 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:07:20 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:07:20 2006
2006/01/03 18:09:32 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:07:20 2006
2006/01/03 18:09:32 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:09:32 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:09:32 2006
2006/01/03 18:11:44 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:09:32 2006
2006/01/03 18:11:44 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:11:44 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:11:44 2006
2006/01/03 18:13:56 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:11:44 2006
2006/01/03 18:13:56 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:13:56 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:13:56 2006
2006/01/03 18:15:25 VCS INFO V-16-6-15004 (EBS) hatrigger:Failed to send trigger for unable_to_restart_agent; script doesn't exist
2006/01/03 18:16:08 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:13:56 2006
2006/01/03 18:16:08 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:16:08 VCS ERROR V-16-1-10008 Agent IPMultiNICB has faulted 6 times since Tue Jan 3 18:05:08 2006
2006/01/03 18:16:08 VCS ERROR V-16-1-10009 Agent IPMultiNICB has faulted 6 times in less than 950 seconds -- Will not attempt to restart. Correct the problem and use haagent -start to start the agent
2006/01/03 18:16:08 VCS INFO V-16-6-15004 (DB) hatrigger:Failed to send trigger for unable_to_restart_agent; script doesn't exist
we are runninig the VCS 4.1 symetric cluster on two nodes.
I installed the MP1 patch for veritas foundation suite 4.1 after that license for veritas is expired and my cluster was unable to come online.
according to veritas its a known bug and they are working on it meanwhile they gave me a temp license which i applied to cluster through #vxlicinst -k.
Now the cluster is up but it unable to load the service groups and it seems it because of IPMULTINICB resource
I would appreciate if any one can help me in this regard i am sending the error message
2006/01/03 18:05:08 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:02:55 2006
2006/01/03 18:05:08 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:05:08 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:05:08 2006
2006/01/03 18:07:20 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:05:08 2006
2006/01/03 18:07:20 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:07:20 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:07:20 2006
2006/01/03 18:09:32 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:07:20 2006
2006/01/03 18:09:32 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:09:32 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:09:32 2006
2006/01/03 18:11:44 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:09:32 2006
2006/01/03 18:11:44 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:11:44 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:11:44 2006
2006/01/03 18:13:56 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:11:44 2006
2006/01/03 18:13:56 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:13:56 VCS NOTICE V-16-1-10016 Agent /opt/VRTSvcs/bin/IPMultiNICB/IPMultiNICBAgent for resource type IPMultiNICB successfully started at Tue Jan 3 18:13:56 2006
2006/01/03 18:15:25 VCS INFO V-16-6-15004 (EBS) hatrigger:Failed to send trigger for unable_to_restart_agent; script doesn't exist
2006/01/03 18:16:08 VCS WARNING V-16-1-10023 Agent IPMultiNICB not sending alive messages since Tue Jan 3 18:13:56 2006
2006/01/03 18:16:08 VCS WARNING V-16-1-53025 Agent IPMultiNICB has faulted; ipm connection was lost; restarting the agent
2006/01/03 18:16:08 VCS ERROR V-16-1-10008 Agent IPMultiNICB has faulted 6 times since Tue Jan 3 18:05:08 2006
2006/01/03 18:16:08 VCS ERROR V-16-1-10009 Agent IPMultiNICB has faulted 6 times in less than 950 seconds -- Will not attempt to restart. Correct the problem and use haagent -start to start the agent
2006/01/03 18:16:08 VCS INFO V-16-6-15004 (DB) hatrigger:Failed to send trigger for unable_to_restart_agent; script doesn't exist
- Exact same problem for me on a fresh install of VCS 4.1 w/ MP! on Solaris 10. Here's the fix:
hastatus -sum
haconf -dump
haconf -makerw
haattr -add IPMultiNICB ContainerName
hatype -modify IPMultiNICB ArgList -add ContainerName
haconf -dump -makero
haagent -start IPMultiNICB -sys "node1"
haagent -start IPMultiNICB -sys "node2"
...
Seems like soomething broke on MP1regarding zones.
Hope this helps