Sponsored Content
Operating Systems Solaris realtime monitoring to Sunstorage 3310 Post 302297614 by ahmad_wa on Saturday 14th of March 2009 04:54:35 AM
Old 03-14-2009
realtime monitoring to Sunstorage 3310

Hi all,

I have Sun storage 3310 and i have installed CAM to make real time monitor, but unfortunately CAM not supported to 3000 model.

is there is any application like CAM and support to 3310 model i can use.. please ur advice??

Thx

Regards,
Ahmad
 

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

compare realtime

I have two log files which keeps appending every sec...I want to extract a certain field from each file(using awk for extracting the data) and compare them in real time... ex: log1 122 234 567 log2 234 567 log3 122 i need a log3 which keeps appending the data found in log1 and... (7 Replies)
Discussion started by: wannalearn
7 Replies

2. Solaris

Add new disk to Sun StorEdge 3310 RAID

HI guys. Bit of a noob so bear with me. I have 2 new disks I want to add to my StorEdge 3310 but am getting lost in the steps. We have another 3310 (JBOD) that I was able to plug the disks into and they instantly showed up. Did a few minor commands after (drvconfig, devfsadm etc..) and I was... (4 Replies)
Discussion started by: jamie_collins
4 Replies

3. Shell Programming and Scripting

Copying files realtime

I have a primary server where certain files are created real time. These files have varying file sizes. I want to FTP or copy them over to a different server server as soon a file gets created. I have to ensure that only full file is copied. The receiving end process expects a FULL file. I am ok... (3 Replies)
Discussion started by: vskr72
3 Replies

4. UNIX for Dummies Questions & Answers

Realtime monitoring of files in a directory

Hello Experts, Here are my requirements. I want to monitor a directory and retrieve file properties like file names along with file sizes of files being generated today and that exceeds a threshold limit (say 10MB) using a shell script. Basically this shell script should monitor (kinda... (1 Reply)
Discussion started by: RamanM
1 Replies
PASS(4)                                                    BSD Kernel Interfaces Manual                                                    PASS(4)

NAME
pass -- CAM application passthrough driver SYNOPSIS
device pass DESCRIPTION
The pass driver provides a way for userland applications to issue CAM CCBs to the kernel. Since the pass driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this driver. If used improperly, this driver can allow userland applications to crash a machine or cause data loss. The pass driver attaches to every SCSI device found in the system. Since it attaches to every device, it provides a generic means of access- ing SCSI devices, and allows the user to access devices which have no "standard" peripheral driver associated with them. KERNEL CONFIGURATION
It is only necessary to configure one pass device in the kernel; pass devices are automatically allocated as SCSI devices are found. IOCTLS
CAMIOCOMMAND This ioctl takes most kinds of CAM CCBs and passes them through to the CAM transport layer for action. Note that some CCB types are not allowed through the passthrough device, and must be sent through the xpt(4) device instead. Some examples of xpt-only CCBs are XPT_SCAN_BUS, XPT_DEV_MATCH, XPT_RESET_BUS, XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC. These CCB types have various attributes that make it illogical or impossible to service them through the passthrough interface. CAMGETPASSTHRU This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question. Although this ioctl is available through the pass driver, it is of limited use, since the caller must already know that the device in question is a passthrough device if they are issuing this ioctl. It is probably more useful to issue this ioctl through the xpt(4) device. FILES
/dev/passn Character device nodes for the pass driver. There should be one of these for each device accessed through the CAM subsystem. DIAGNOSTICS
None. SEE ALSO
cam(3), cam(4), cam_cdbparse(3), xpt(4), camcontrol(8) HISTORY
The CAM passthrough driver first appeared in FreeBSD 3.0. AUTHORS
Kenneth Merry <ken@FreeBSD.org> BUGS
It might be nice to have a way to asynchronously send CCBs through the passthrough driver. This would probably require some sort of read/write interface or an asynchronous ioctl interface. BSD October 10, 1998 BSD
All times are GMT -4. The time now is 01:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy