10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
2. Red Hat
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies
3. Solaris
Until I really began to explore the practical implications of using ZFS with VCS, I would not have necessarily realised the obstacles that would be put in my path. Data integrity is a must-have for storage in a shared host environment, so it surprised me to learn as I opened this particular... (0 Replies)
Discussion started by: cambridge
0 Replies
4. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
5. UNIX for Advanced & Expert Users
Hello,
Usually I use "vxresize" to grow vxfs directory in a stand-alone server without any problems, but I am just told to grow vxfs directorys in Veritas Cluster nodes.
Since I never done it before, would like to ask all the experts here to make sure the concept and steps will be fine... (1 Reply)
Discussion started by: sunnychen98
1 Replies
6. Gentoo
How to failover the cluster ? GNU/Linux
By which command,
My Linux version
2008 x86_64 x86_64 x86_64 GNU/Linux
What are the prerequisites we need to take while failover ?
if any
Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies
7. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
8. Solaris
Hi,
We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover?
Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies
9. Solaris
Is it possible to configure veritas cluster server using 2 Ldoms on same host? I just want to test and learn VCS. We can do a cluster (sun cluster3.2 ) in a box using 2 Ldoms but i 'm not sure if thats possible with veritas cluster or not ? (1 Reply)
Discussion started by: fugitive
1 Replies
10. High Performance Computing
Hello,
This might not be the right place to post my questions.
- I installed VCS 5.0 on the 2 nodes. What's next? I want to test the HA of NFS: i.e. the shared disk always accessible if one node goes down. How to do that?
- The management console was not installed. This is the GUI to manage... (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
LEARN ABOUT SUNOS
init.wbem
init.wbem(1M) System Administration Commands init.wbem(1M)
NAME
init.wbem - start and stop the CIM Boot Manager
SYNOPSIS
/etc/init.d/init.wbem start | stop | status
DESCRIPTION
The init.wbem utility is run automatically during installation and each time the system is rebooted. This utility manipulates the CIM
Object Manager (CIMOM) and the Solaris Management Console server, both of which run combined in a single process. init.wbem can be used to
start, stop, or retrieve status from the server.
CIM Object Manager
The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a computer representation, or model, of a managed
resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes.
When a WBEM client application accesses information about a CIM object, the CIM Object Manager contacts either the appropriate provider for
that object or the CIM Object Manager Repository. Providers are classes that communicate with managed objects to access data.
When a WBEM client application requests data from a managed resource that is not available from the CIM Object Manager Repository, the CIM
Object Manager forwards the request to the provider for that managed resource. The provider dynamically retrieves the information.
At startup, the CIM Object Manager performs the following functions:
o Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 5988.
o Sets up a connection to the CIM Object Manager Repository.
o Waits for incoming requests.
During normal operations, the CIM Object Manager performs the following functions:
o Performs security checks to authenticate user login and authorization to access namespaces.
o Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification.
o Routes requests to the appropriate provider or to the CIM Object Manager Repository.
o Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications.
A WBEM client application contacts the CIM Object Manager to establish a connection when it needs to perform WBEM operations, such as cre-
ating a CIM class or updating a CIM instance. When a WBEM client application connects to a CIM Object Manager, it gets a reference to the
CIM Object Manager, which it then uses to request services and operations.
Solaris Management Console Server
The Solaris Management Console server is the back end to the front end console, smc(1M). It provides tools for the console to download and
performs common services for the console and its tools to use, such as authentication, authorization, logging, messaging, and persistence.
System Booting
The init.wbem script is installed in the /etc/init.d directory.
OPTIONS
The following options are supported:
start Starts the CIMOM and Solaris Management Console server on the local host.
stop Stops the CIMOM and Solaris Management Console server on the local host.
status Gets the status of the CIMOM and Solaris Management Console server on the local host.
NOTES
When the init.wbem script is run, it does not run the CIMOM and Solaris Management Console server directly. The server process is in Java
and is too heavyweight to be run immediately at system boot time. Instead, three lightweight processes listen on three different ports that
the CIMOM and the Solaris Management Console server normally use. This acts similarly to inetd(1M).
Because Java programs cannot inherit file descriptors as other programs can, there is a small time period from when the first connection is
made until the server is fully operational where client connections may be dropped. WBEM clients are immune to this, as they will retry
until the server comes online. Solaris Management Console clients are not immune, and it may be necessary to manually reconnect, though
this should not happen in the common case.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWwbcor |
+-----------------------------+-----------------------------+
SEE ALSO
inetd(1M), mofcomp(1M), smc(1M), smcconf(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5)
SunOS 5.10 2 Jan 2002 init.wbem(1M)