Sponsored Content
Full Discussion: C4 tape library
Operating Systems Solaris C4 tape library Post 302176596 by ppass on Tuesday 18th of March 2008 05:09:43 PM
Old 03-18-2008
C4 tape library

Hi all ,

Anybody has an installation manual for Sun StorageTek C4 tape library . i am trying to do the installation on a Sun Fire V245 .

Thanks a million
cheers
ppass
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ATL L200 Tape Library and Solaris

I picked up this library but I cannot get the device to actuate. How do I make this work with Solaris 7? (2 Replies)
Discussion started by: n9ninchd
2 Replies

2. HP-UX

HP-UX / Tape Library Communication Problems

Hi All, Hoping that you'll be able to help out on - I've a problem occuring in our backups that's driving me up the wall. I've got an HP-UX Visualise 6500 as below: ================================ root # uname -a HP-UX <NAME> B.11.00 A 9000/785 2005956095 two-user license... (2 Replies)
Discussion started by: geralex
2 Replies

3. AIX

Tape Library 3583

Hello every body, I have one tape library 3583 but I can't install this some body have ben installed?? when I tray to install it, the output is the next: Method error (/etc/methods/cfgAtape): 0514-022 The specified connection is not valid. some Idea?? thanks greetings (5 Replies)
Discussion started by: xanatos
5 Replies

4. AIX

Tape Library on Aix

I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library. I had a backup scheduled on tape library but after taking backup successfully, Now, Question 1:- I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
Discussion started by: Shrek
0 Replies

5. Solaris

Configuration issue with Tape Library in Solaris 10

Env: Server : Sparc Ultra-80 OS: Solaris 10 Direct SCSI connection to Library. Terminator connected at the Tape End. Problem: Unable to see any device file related to Robotic /dev/rsst0. Unable to see any device file /dev/rmt. ------------ Messages while the machine boots sst0: No... (3 Replies)
Discussion started by: amqstam
3 Replies

6. AIX

AIX 5.3 & Veritas Backup with Tape Library

hello, I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup: Veritas Software is not able to communicate properly with our tape library When we tried to run these commands here's the output # cfgmgr -l fscsi0 # cfgmgr -l fscsi2 # cfgmgr -l fscsi1 cfgmgr:... (3 Replies)
Discussion started by: filosophizer
3 Replies

7. AIX

AIX doesn't detect TS3200 tape library

Hi all, I have a problem here root@host1 / # lsdev -Cc tape rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP) smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP) root@host1 / # cfgmgr -l fcs2 Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

8. Solaris

Connecting an array and a tape library

I am a solaris noob. I have a SPARC enterprise T5120 server which i am trying to connect 1 StorEdge 3300 and 1 StorageWorks MSL2024 tape library. Each device is connecting to 1 pci card on the server. I can see the array when i run the format command but i can't seem to detect the tape library. ... (2 Replies)
Discussion started by: M_Owen
2 Replies

9. Solaris

SL24 tape library connection.

hi all please tell me how can i connect SunFire V240 to a SL24 tape library. is there any slots which i can connect? can i connect through SCSI port? (1 Reply)
Discussion started by: nikhil kasar
1 Replies

10. AIX

AIX 7.1 cannot discover drives from TS3310 tape library

Good day! Need help in checking my AIX 7.1 box. After we have finished zoning our TS3200 and TS3310 tape libraries, we installed the Atape driver, # lslpp -L |grep tape Atape.driver 11.7.7.0 C F IBM AIX Enhanced Tape and devices.fcp.tape.rte 7.1.3.15 C ... (0 Replies)
Discussion started by: alainken3
0 Replies
BOOTSTRAP(5)						   Sun Grid Engine File Formats 					      BOOTSTRAP(5)

NAME
bootstrap - Sun Grid Engine bootstrap file DESCRIPTION
bootstrap contains parameters that are needed for the startup of Sun Grid Engine components. It is created during the sge_qmaster instal- lation. Modifying bootstrap in a running system is not supported. FORMAT
The paragraphs that follow provide brief descriptions of the individual parameters that compose the bootstrap configuration for a Sun Grid Engine cluster: admin_user Administrative user account used by Sun Grid Engine for all internal file handling (status spooling, message logging, etc.). Can be used in cases where the root account does not have the corresponding file access permissions (e.g. on a shared file system without global root read/write access). Being a parameter set at installation time changing admin_user in a running system is not supported. Changing it manually on a shut-down cluster is possible, but if access to the Sun Grid Engine spooling area is interrupted, this will result in unpredictable behavior. The admin_user parameter has no default value, but instead it is defined during the master installation procedure. default_domain Only needed if your Sun Grid Engine cluster covers hosts belonging to more than a single DNS domain. In this case it can be used if your hostname resolving yields both qualified and unqualified hostnames for the hosts in one of the DNS domains. The value of default_domain is appended to the unqualified hostname to define a fully qualified hostname. The default_domain parameter will have no effect if ignore_fqdn is set to "true". Being a parameter set at installation time changing default_domain in a running system is not supported. The default for default_domain is "none", in which case it will not be used. ignore_fqdn Ignore fully qualified domain name component of hostnames. Should be set if all hosts belonging to a Sun Grid Engine cluster are part of a single DNS domain. It is switched on if set to either "true" or "1". Switching it on may solve problems with load reports due to different hostname resolutions across the cluster. Being a parameter set at installation time changing ignore_fqdn in a running system is not supported. The default for ignore_fqdn is "true". spooling_method Defines how sge_qmaster(8) writes its configuration and the status information of a running cluster. The available spooling methods are berkeleydb and classic. spooling_lib The name of a shared library containing the spooling_method to be loaded at sge_qmaster(8) initialization time. The extension characteriz- ing a shared library (.so, .sl, .dylib etc.) is not contained in spooling_lib. If spooling_method was set to berkeleydb during installation, spooling_lib is set to libspoolb, if classic was chosen as spooling_method, spooling_lib is set to libspoolc. Not all operating systems allow the dynamic loading of libraries. On these platforms a certain spooling method (default: berkeleydb) is compiled into the binaries and the parameter spooling_lib will be ignored. spooling_params Defines parameters to the chosen spooling method. Parameters that are needed to initialize the spooling framework, e.g. to open database files or to connect to a certain database server. The spooling parameters value for spooling method berkeleydb is [rpc_server:]database directory, e.g. /sge_local/default/spool/qmas- ter/spooldb for spooling to a local filesystem, or myhost:sge for spooling over a Berkeley DB RPC server. For spooling method classic the spooling parameters take the form <common_dir>;<qmaster spool dir>, e.g. /sge/default/com- mon;/sge/default/spool/qmaster binary_path The directory path where the Sun Grid Engine binaries reside. It is used within Sun Grid Engine components to locate and startup other Sun Grid Engine programs. The path name given here is searched for binaries as well as any directory below with a directory name equal to the current operating sys- tem architecture. Therefore, /usr/SGE/bin will work for all architectures, if the corresponding binaries are located in subdirectories named aix43, cray, lx24-x86, hp11, irix65, tru64, sol-sparc, etc. The default location for the binary path is <sge_root>/bin qmaster_spool_dir The location where the master spool directory resides. Only the sge_qmaster(8) and sge_shadowd(8) need to have access to this directory. The master spool directory - in particular the job_scripts directory and the messages log file - may become quite large depending on the size of the cluster and the number of jobs. Be sure to allocate enough disk space and regularly clean off the log files, e.g. via a cron(8) job. Being a parameter set at installation time changing qmaster_spool_dir in a running system is not supported. The default location for the master spool directory is <sge_root>/<cell>/spool/qmaster. security_mode The security mode defines the set of security features the installed cluster is using. Possible security mode settings are none, afs, dce, kerberos, csp. (no additional security, AFS, DCE, KERBEROS, CSP security model). listener_threads The number of listener threads (defaults set by installation). worker_threads The number of worker threads (defaults set by installation). scheduler_threads The number of scheduler threads (allowed: 0-1, default set by installation: 1, off: 0). (see qconf(1) -kt/-at option) jvm_threads The number of jvm threads (allowed: 0-1, default set by installation, off: 0). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ BOOTSTRAP(5)
All times are GMT -4. The time now is 01:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy