High Availability Agents - Agent Pack - 1Q2016 release
Veritas High Availability Agent Pack 1Q 2016 is now available on SORT: https://sort.veritas.com/agents. Application Agents Added support for JBoss 8.x and 9.x. The JBoss Application Server 8.0 and later releases are now known as WildFly. Added support for Infomatica 9.5.1 on the AIX, Linux, and Solaris operating systems. Added support for SAP HANA SPS11. Replication Agents Enhanced EMC SRDF/SRDFSnap agent to support TimeFinder Snap and TimeFinder Clone in the CVM environment. Enhanced EMC SRDF/SRDFSnap agent to support CVM/CFS (SFRAC) on the Solaris 11 SPARC operating system. Enhanced the HTC agent support on the Solaris x86 operating system. Enhanced the HP 3PAR RemoteCopy agent to support on the Solaris 11 SPARC operating system. Enhanced the HP 3PAR RemoteCopy agent to support in the CFS environment on the AIX, Linux, and Solaris operating systems. Added a new attribute known as VCSResLock, which ensures the serialized management in case of a parallel application on the AIX, Linux, and Solaris operating systems. Important Fixes IBM WebSphere agent Filter process pattern is updated in agent to find the appropriate WebSphere process. IBM Informix Dynamic Server In the Solaris non-global zone, the agent now monitors the process whose PPID is the PID of the zone scheduler process. Updated agent start operation, the oninit –yw command is used to start the Informix server. Updated agent stop operation, the onshutdown.sh script is used to stop the Informix server. Hitachi TrueCopy; HP XP Continuous Access Updated agent to rescan all slave nodes before importing the shared DiskGroup during online. If LinkMonitor attribute is set to 2, the agent logs messages when the state of the Hitachi TrueCopy instance changes from PAIR to NON-PAIR in every monitor cycle. AllowAutoFailoverInterval functionality, which allows failover even if the SplitTakeover attribute is set to 0 in case FENCE level NEVER, is now supported in the GCO environment.
LLT heartbeat link status changed
Hi Community, I'm having a problem in my cluster, I'm having two nodes in cluster,I'm trying to add new node to the cluster, when I booted up the new node I got and errors on the current cluster, I guess the new node is trying to join the cluster. V-16-1-10112 System (xxxxxx) - Membership: 0x6, DDNA: 0x4 V-16-1-10077 Received new cluster membership LLT heartbeat link status changed. Previous status = e1000g0 UP e1000g2 UP; Current status = e1000g0 UP e1000g2 DOWN. Now interface e1000g2 is down, but I've checked the phisical links, they are all up and running, please advise how to resolve this issue. BR Luay
Understanding RestartLimit for non critical ressource
Hello, we have some trouble with our oracle listener process. sometimes the listener is killed by vcs. We dont know why. xxx VCS ERROR V-16-2-13027 (node1) Resource(lsnr-ORADB1) - monitor procedure did not complete within the expected time. xxx VCS ERROR V-16-2-13210 (node1) Agent is calling clean for resource(lsnr-ORADB1) because 4 successive invocations of the monitor procedure did not complete within the expected time. xxx VCS NOTICE V-16-20002-42 (node1) Netlsnr:lsnr-ORADB1:clean:Listener(LISTENER) kill TERM 2342 xxx VCS INFO V-16-2-13068 (node1) Resource(lsnr-ORADB1) - clean completed successfully. xxx VCS INFO V-16-2-13026 (node1) Resource(lsnr-ORADB1) - monitor procedure finished successfully after failing to complete within the expected time for (4) consecutive times. xxx VCS INFO V-16-1-10307 Resource lsnr-ORADB1 (Owner: unknown, Group: ORADB1) is offline on node1 (Not initiated by VCS) However, Resource(lsnr-ORADB1) is set to non-critical, to prevent an failover. I'll now set an RestartLimit for Resource(lsnr-ORADB1) to let the cluster try to restart the listener, but what happen if this failed? Will the Ressouce still staying offline or initiate the cluster an failover for the whole ResourceGroup? thanks in advance for any help!
Symantec Connect Community] VCS CRITICAL V-16-1-50086 CPU usage is 97%
Hi, We receive VCS CRITICAL CPU usage errors very often: Jan 8 01:08:45 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 01:08:45 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 01:08:52 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 01:08:52 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 01:08:57 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 01:08:57 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 01:30:43 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 01:30:43 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 01:51:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS ERROR V-16-1-1 3027 (LHDBEAP01) Resource(app) - monitor procedure did not complete within the expected time. Jan 8 06:10:01 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 06:10:01 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 08:17:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 08:24:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 08:34:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 08:45:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 93% Jan 8 08:47:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 09:00:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 94% Jan 8 09:01:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 09:05:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 09:26:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 09:28:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 95% Jan 8 09:40:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 09:54:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 93% Jan 8 09:55:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 94% Jan 8 09:58:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 10:09:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 10:12:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 10:17:30 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS ERROR V-16-1-1 3027 (LHDBEAP01) Resource(app) - monitor procedure did not complete within the expected time. Jan 8 10:23:31 LHDBEDB01 last message repeated 2 times Jan 8 10:24:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 95% Jan 8 10:28:12 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 10:28:12 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 10:28:15 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 10:28:15 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 10:28:18 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 10:28:18 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 10:28:49 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 10:28:49 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 10:30:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 92% Jan 8 10:53:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 98% Jan 8 10:54:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 10:59:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 11:22:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 95% Jan 8 11:44:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 11:49:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 11:56:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 93% Jan 8 12:25:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 94% Jan 8 12:26:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 12:41:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 95% Jan 8 12:47:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 94% Jan 8 12:49:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 13:02:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 94% Jan 8 13:04:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 92% Jan 8 13:12:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 13:16:02 LHDBEDB01 last message repeated 2 times Jan 8 13:36:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 97% Jan 8 13:42:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 13:45:32 LHDBEDB01 last message repeated 1 time Jan 8 13:47:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 13:51:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 14:02:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 14:03:47 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 14:03:47 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 14:07:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 14:11:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% Jan 8 14:20:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 97% Jan 8 14:24:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 14:25:31 LHDBEDB01 last message repeated 1 time Jan 8 14:32:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 92% Jan 8 14:35:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 97% Jan 8 14:42:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS ERROR V-16-1-1 3027 (LHDBEAP01) Resource(app) - monitor procedure did not complete within the expected time. Jan 8 14:45:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 98% Jan 8 14:47:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 92% Jan 8 14:48:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 14:51:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 97% Jan 8 14:53:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 15:02:01 LHDBEDB01 last message repeated 2 times Jan 8 15:10:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 15:12:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 91% Jan 8 15:13:33 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS ERROR V-16-1-1 3027 (LHDBEAP01) Resource(app) - monitor procedure did not complete within the expected time. Jan 8 15:20:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 93% Jan 8 15:22:32 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 97% Jan 8 15:25:02 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 15:29:01 LHDBEDB01 last message repeated 4 times Jan 8 15:33:31 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 15:38:31 LHDBEDB01 last message repeated 2 times Jan 8 15:41:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 96% Jan 8 15:44:02 LHDBEDB01 last message repeated 1 time Jan 8 15:50:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 92% Jan 8 15:51:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 100% Jan 8 15:51:24 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 15:51:24 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 15:51:30 LHDBEDB01 llt: [ID 140958 kern.notice] LLT INFO V-14-1-10205 link 2 (ce0) node 1 in trouble Jan 8 15:51:30 LHDBEDB01 llt: [ID 860062 kern.notice] LLT INFO V-14-1-10024 link 2 (ce0) node 1 active Jan 8 15:57:01 LHDBEDB01 Had[377]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage on LHDBEDB01 is 99% bash-2.05$ root@LHDBEAP01 # pkginfo -l NTAPnfsa PKGINST: NTAPnfsa NAME: NetApp NFS Client Agent for Veritas Cluster Server by Symantec CATEGORY: optional ARCH: sun4u VERSION: 5.0.0 BASEDIR: / VENDOR: Network Appliance, Inc. DESC: NetApp NFS Client Agent for Veritas Cluster Server by Symantec PSTAMP: NTAPnfsa:693884:20070816.1459 INSTDATE: Dec 18 2013 03:54 STATUS: completely installed FILES: 26 installed pathnames 7 shared pathnames 10 directories 2 executables 242 blocks used (approx) bash-2.05$ sar 1 10 SunOS LHDBEDB01 5.9 Generic_117171-17 sun4u 01/08/2015 16:11:27 %usr %sys %wio %idle 16:11:28 71 2 0 27 16:11:29 56 5 0 39 16:11:30 51 4 0 45 16:11:31 78 9 0 13 16:11:32 52 0 0 48 16:11:33 51 2 0 47 16:11:34 56 5 0 39 16:11:35 50 1 0 49 16:11:36 58 6 0 36 16:11:37 50 1 0 49 Average 57 3 0 39 bash-2.05$