Hi,
some of our ressources in the cluster configuration are not critical. If this ressource fails, we do not get a monitoring message from VOM.
VOM only monitores faulted servicegroups, but in this case, the servicegroup is partial online.
...
Hi,
I didn't found a monitoring method to monirot faulted VCS agents.
2011/08/27 18:20:22 VCS ERROR V-16-1-10008 Agent Phantom has faulted 6 times since August 27, 2011 6:14:52 PM CEST
2011/08/27 18:20:22 VCS ERROR V-16-1-10009 Agent ...
if we take a look at the " Faults and Risks", we got the following fault:
" Resource monitoring timed out in the group" "fault entity" "sg-name" and "time"
we have to take a look directly in ...
it would be nice to have a "tree view of the servicegroups" (of a single cluster or the whole environement) like the vcs java gui.
there should be a list of all servicegroups on the left. if you choose one sg, you should open the ...
I need a solution
Hi,
we want to create a report about all running servicegroups in a datacentre.
We tried to create a Business Entity "DC1" and added all hosts in the ...
This issue has been solved
Hi,
at the start page, you see the Top Fault and Risks of the whole environment.
It would be helpfull if you could configure which events of which business entity you want to see.
A filter by Business Entity would be helpful under Monitor ...
currently, the events which are configured in the rules are reported 24/7.
there should be the possibility to define timeperiods, where the messages are reported (e.g. production 24/7, non production 10/5)
Need clarification For certain ...
We created several different rules to monitor our systems (VCS, VxVM,...).
for every rule, we have to update a host list. When we add a new server to VOM, we have to add the server to every rule.
we just want to add the new host to a business ...
2 Datacenters – each has a Symmetrix and a Solaris-based cluster pair (storage is mirrored by SRDF)
- Datacenter 2 is the active site (SCSI-3 reservations on disk)
- Datacenter 2 failure due to power-outage or other problems
- Failover to ...
The Zone resource monitor script from 5.1RP1 (maybe others too) uses "zoneadm" to check for zone data.
This seems to happen on all nodes, even those where the zone is not currently running.
This again produces lots and lots of messages ...