10 More Discussions You Might Find Interesting
1. AIX
The monitoring tools what we have not able to see historical information about the process name or pid number for the process that consumed high CPU or memory or paging space. Can you please suggest some of the best monitoring tools available in the market that monitors primarily AIX and other Unix... (0 Replies)
Discussion started by: baladelaware73
0 Replies
2. Infrastructure Monitoring
Hi guys,
I am currently managing an application running on around 150 servers.
I only have application usage rights on those servers and do not have any root privileges.
I have an external node that can connect to those servers and I have root privileges on that one box.
I want to setup... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies
3. Solaris
Hi forum
We have nearly 240 servers inclding zones . How can i monitor server and its performance by using any monitoring tools. My indentions is to plot graphs based on server utilization interms of cpu and memory
Is there any opensource tools for this.
I saw collectd and it has agent... (3 Replies)
Discussion started by: bentech4u
3 Replies
4. UNIX for Dummies Questions & Answers
Hello mates..
i need help with these things
*Users should be allowed to login only once, i.e Multiple logins from single user should be restricted and should issue an alert if any user tries .
*statistics of everyday log in time ,duration of login,and the commands executed by the user
*Alert... (6 Replies)
Discussion started by: safijunaid
6 Replies
5. Infrastructure Monitoring
I am interested whitch tools are the best by monitoring the UNIX processes and network interfaces ? and whitch tools for management UNIX ?
I know that the nagios very good monitoring tools, but interested me and others who have ? (4 Replies)
Discussion started by: danyy
4 Replies
6. Infrastructure Monitoring
Hi ,
I am new for Aix i am using IBM AIX server in our org. I am using tomcat and JDK 1.6 for our own ERP software the data base was stored in another server (windows )
i want to monitor my AIX server with graphical output from another system it is possible please help me, any other... (7 Replies)
Discussion started by: krishna_vnr`
7 Replies
7. Infrastructure Monitoring
Hi,
Are there any GUI (preferably web based) Solaris monitoring tools available for the SPARC platform.
Just to clarify, when i say GUI, I don't mean buttons to configure the Software, of course that would be a plus, but rather GUI in terms of output, like Graphs.
Thanks (6 Replies)
Discussion started by: Mack1982
6 Replies
8. Red Hat
Hi,
In HPUX there is a grate monitor tools named GLANCE, which give you
information on the disks load, memory usage, cpu ...
What is the equivalent tool in LINUX Redhat 4.
Thanks (3 Replies)
Discussion started by: yoavbe
3 Replies
9. UNIX for Advanced & Expert Users
Guys, I would like to know who are using monitoring tools? I use Nagios before but it seems is more on Linux and Windows platform.
- Nagios
- BigBrother
- BigSister
- Cacti
- MRTG
- JFFNMS
- anymore? Please give comment too
I would like to have some comment on UNIX monitoring tools.... (2 Replies)
Discussion started by: dwarf007
2 Replies
10. IP Networking
Any idea where can I get a freware to monitor the network traffic in my department? The best is this tool can store the log files. Thanks! (5 Replies)
Discussion started by: zheng_soon
5 Replies
scdpm(1M) System Administration Commands scdpm(1M)
NAME
scdpm - manage disk path monitoring daemon
SYNOPSIS
scdpm [-a] {node | all}
scdpm -f filename
scdpm -m {[node | all][:/dev/did/rdsk/]dN | [:/dev/rdsk/]cNtXdY | all}
scdpm -n {node | all}
scdpm -p [-F] {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all}
scdpm -u {[node | all][:/dev/did/rdsk/]dN | [/dev/rdsk/]cNtXdY | all}
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scdpm command manages the disk path monitoring daemon in a cluster. You use this command to monitor and unmonitor disk paths. You can
also use this command to display the status of disk paths or nodes. All of the accessible disk paths in the cluster or on a specific node
are printed on the standard output. You must run this command on a cluster node that is online and in cluster mode.
You can specify either a global disk name or a UNIX path name when you monitor a new disk path. Additionally, you can force the daemon to
reread the entire disk configuration.
You can use this command only in the global zone.
OPTIONS
The following options are supported:
-a
Enables the automatic rebooting of a node when all monitored disk paths fail, provided that the following conditions are met:
o All monitored disk paths on the node fail.
o At least one of the disks is accessible from a different node in the cluster.
You can use this option only in the global zone.
Rebooting the node restarts all resource and device groups that are mastered on that node on another node.
If all monitored disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot
again. However, if any monitored disk paths become available after the node reboots but then all monitored disk paths again fail, the
node automatically reboots again.
You need solaris.cluster.device.admin role-based access control (RBAC) authorization to use this option. See rbac(5).
-F
If you specify the -F option with the -p option, scdpm also prints the faulty disk paths in the cluster. The -p option prints the cur-
rent status of a node or a specified disk path from all the nodes that are attached to the storage.
-f filename
Reads a list of disk paths to monitor or unmonitor in filename.
You can use this option only in the global zone.
The following example shows the contents of filename.
u schost-1:/dev/did/rdsk/d5
m schost-2:all
Each line in the file must specify whether to monitor or unmonitor the disk path, the node name, and the disk path name. You specify
the m option for monitor and the u option for unmonitor. You must insert a space between the command and the node name. You must also
insert a colon (:) between the node name and the disk path name.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-m
Monitors the new disk path that is specified by node:diskpath.
You can use this option only in the global zone.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-n
Disables the automatic rebooting of a node when all monitored disk paths fail.
You can use this option only in the global zone.
If all monitored disk paths on the node fail, the node is not rebooted.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
-p
Prints the current status of a node or a specified disk path from all the nodes that are attached to the storage.
You can use this option only in the global zone.
If you also specify the -F option, scdpm prints the faulty disk paths in the cluster.
Valid status values for a disk path are Ok, Fail, Unmonitored, or Unknown.
The valid status value for a node is Reboot_on_disk_failure. See the description of the -a and the -n options for more information
about the Reboot_on_disk_failure status.
You need solaris.cluster.device.read RBAC authorization to use this option. See rbac(5).
-u
Unmonitors a disk path. The daemon on each node stops monitoring the specified path.
You can use this option only in the global zone.
You need solaris.cluster.device.admin RBAC authorization to use this option. See rbac(5).
EXAMPLES
Example 1 Monitoring All Disk Paths in the Cluster Infrastructure
The following command forces the daemon to monitor all disk paths in the cluster infrastructure.
# scdpm -m all
Example 2 Monitoring a New Disk Path
The following command monitors a new disk path.All nodes monitor /dev/did/dsk/d3 where this path is valid.
# scdpm -m /dev/did/dsk/d3
Example 3 Monitoring New Disk Paths on a Single Node
The following command monitors new paths on a single node. The daemon on the schost-2 node monitors paths to the /dev/did/dsk/d4 and
/dev/did/dsk/d5 disks.
# scdpm -m schost-2:d4 -m schost-2:d5
Example 4 Printing All Disk Paths and Their Status
The following command prints all disk paths in the cluster and their status.
# scdpm -p
schost-1:reboot_on_disk_failure enabled
schost-2:reboot_on_disk_failure disabled
schost-1:/dev/did/dsk/d4 Ok
schost-1:/dev/did/dsk/d3 Ok
schost-2:/dev/did/dsk/d4 Fail
schost-2:/dev/did/dsk/d3 Ok
schost-2:/dev/did/dsk/d5 Unmonitored
schost-2:/dev/did/dsk/d6 Ok
Example 5 Printing All Failed Disk Paths
The following command prints all of the failed disk paths on the schost-2 node.
# scdpm -p -F all
schost-2:/dev/did/dsk/d4 Fail
Example 6 Printing the Status of All Disk Paths From a Single Node
The following command prints the disk path and the status of all disks that are monitored on the schost-2 node.
# scdpm -p schost-2:all
schost-2:reboot_on_disk_failure disabled
schost-2:/dev/did/dsk/d4 Fail
schost-2:/dev/did/dsk/d3 Ok
EXIT STATUS
The following exit values are returned:
0 The command completed successfully.
1 The command failed completely.
2 The command failed partially.
Note -
The disk path is represented by a node name and a disk name. The node name must be the host name or all. The disk name must be the global
disk name, a UNIX path name, or all. The disk name can be either the full global path name or the disk name: /dev/did/dsk/d3 or d3. The
disk name can also be the full UNIX path name: /dev/rdsk/c0t0d0s0.
Disk path status changes are logged with the syslogd LOG_INFO facility level. All failures are logged with the LOG_ERR facility level.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
Intro(1CL), cldevice(1CL), clnode(1CL), attributes(5)
Sun Cluster System Administration Guide for Solaris OS
Sun Cluster 3.2 22 Jun 2006 scdpm(1M)
