Sponsored Content
Operating Systems Solaris Solaris 10 and DELL TL-2000 Tape Library with ISCSI Post 302373417 by austin73 on Friday 20th of November 2009 07:38:26 AM
Old 11-20-2009
Question Solaris 10 and DELL TL-2000 Tape Library with ISCSI

Hello,

i am trying to get following configuration up running, but get no access to the library roboter.

Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc
DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL,
connected via ISCSI Bridge (build into the TL)

Backup software: bacula


i see both iSCSI connections:
(sudo iscsiadm list discovery-address -v)

Discovery Address: 192.168.100.14:3260
Target name: iqn.1988-11.com.dell.200ade:eui.5000e11132111002.1
Target address: 192.168.100.14:3260, 1
Target name: iqn.1988-11.com.dell.200ade:eui.5000e11132111002.0
Target address: 192.168.100.14:3260, 1


now i plumb the devices:
(sudo iscsiadm list target -S)

Target: iqn.1988-11.com.dell.200ade:eui.5000e11132111002.0
Alias: eui.5000e11132111002.0
TPGT: 1
ISID: 4000002a0000
Connections: 1
LUN 0
Vendor: IBM
Product: ULT3580-HH4
OS Device Name: /dev/rmt/0

Target: iqn.1988-11.com.dell.200ade:eui.5000e11132111002.1
Alias: eui.5000e11132111002.1
TPGT: 1
ISID: 4000002a0000
Connections: 1


ok, so the tape device was created but not the library robot, but why?
why is not at the second iscsi id the vendor name and device name presented?

i do not have a device /dev/sg* and no directory /dev/scsi.

So i looked for information about sg and libraries, found some infos about the files /kernel/drv/sgen.conf and /kernel/drv/st.conf and define there the name="sgen" ... and "st" ...

Can make a (sudo mt -f /dev/rmt/0 status) but get no information because no tape is loaded.

Rebooted the server, but still no library.

Do i need a special device driver? There is the IBM devdrv site, aber no file for SUN Solaris 10 on intel386 - only x64 ... bad ...


btw: where do i find a installable version of mtx for Solaris 10 i386 ?


Need your help.
Thank You.

Greetings
ast

Last edited by austin73; 11-20-2009 at 09:27 AM..
 

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. 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

3. 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

4. Solaris

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 (4 Replies)
Discussion started by: ppass
4 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. SCO

Dell PowerEdge 2600 tape backup

I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site. The only device names in /dev for a tape drive were /dev/xStp0 /dev/xcdt0 /dev/xct0 ... (6 Replies)
Discussion started by: ezlarry
6 Replies

7. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies

8. UNIX for Advanced & Expert Users

LTO2 tape drive as iSCSI target

I'm using Bacula as my backup system, with full backups going to an LTO2 tape drive, while differentials and incrementals go to a disk array on my main server, babylon4. The tape drive is currently attached to a separate machine, because babylon4 does not have a SCSI controller, nor a free PCI-X... (0 Replies)
Discussion started by: Phil Stracchino
0 Replies

9. Emergency UNIX and Linux Support

C4 scsci Tape library not detectable after lustarter patching on solaris 10 u4

Hi All, We have patched our solaris 10 u4 server with lustarter patch in order to get it prepared for solaris live upgrade.The patch installation went pretty fine and we did reboot the server after patching.But after patching we have noticed O.S is not able to detect tape library.Not sure what... (22 Replies)
Discussion started by: sahil_shine
22 Replies

10. Solaris

Add new EML 103e Tape Library in SUN Solaris Host to implement HP DP

Hi, Our environment is SUN Solaris. We have purchased HP EML 103e tape library. Can you please let me know do I need to install any Driver of newly added Tape Library to see from the Solaris Host? or how can i see the tape library from my Solaris hosts. Thanks, Hassan (0 Replies)
Discussion started by: M_Hassan
0 Replies
isnsadm(1M)						  System Administration Commands					       isnsadm(1M)

NAME
isnsadm - administer the internet Storage Name Server (iSNS) server SYNOPSIS
isnsadm options isnsadm subcommand [subcommand_options] [operand] DESCRIPTION
The isnsadm command is the command-line interface to the Internet Storage Name Service (iSNS) server. isnsadm comprises a set of subcom- mands, described in their own section, each of which accomplishes one of the iSNS server management functions. For any operations that will change the iSNS configurations the solaris.isnsmgr.write authorization is required. Refer to isns(1M). For read operations, the command does not require special authorizations. isnsadm has a set of general options and a set of subcommand-specific options. The first category is described under OPTIONS; the second category is described in the context of each subcommand description. OPTIONS
The following options are supported: -?, --help Displays context help. Stops interpretation of any subsequent arguments. -V, --version Displays version information. Stops interpretation of any subsequent arguments. OPERANDS
The following operands are used by one or more isnsadm subcommands. iscsi-node-name iSCSI target or iSCSI initiator symbolic name. A string with a maximum length of 223 characters. discovery-domain-name Discovery domain symbolic name. A string with a maximum length of 256 characters. discovery-domain-set-name Discovery domain set symbolic name. A string with a maximum length of 256 characters. SUBCOMMANDS
The isnsadm command supports the subcommands described below. add-dd The add-dd subcommand adds a discovery domain to a discovery domain set. The add-dd subcommand has the following syntax: # isnsadm add-dd option discovery-domain-name, ... add-dd has the following option: -s discovery-domain-set-name Specifies a discovery domain set. add-node The add-node subcommand adds a node to a specified discovery-domain. The add-node subcommand has the following syntax: # isnsadm add-node option iscsi-node-name,... add-node has the following options: -d,--dd discovery-domain-name Specifies a discovery domain. create-dd The create-dd subcommand creates a discovery domain with the name you specify. The create-dd subcommand has the following syntax: # isnsadm create-dd discovery-domain-name, ... create-dd has no options. create-dd-set The create-dd-set subcommand creates a discovery domain set with the name you specify. The create-dd-set subcommand has the following syntax: # isnsadm create-dd-set discovery-domain-set-name, ... create-dd-set has no options. delete-dd The delete-dd subcommand deletes a discovery domain of the name you specify. The delete-dd subcommand has the following syntax: # isnsadm delete-dd discovery-domain-name, ... delete-dd has no options. delete-dd-set The delete-dd-set subcommand deletes a discovery domain set of the name you specify. The delete-dd-set subcommand has the following syntax: # isnsadm delete-dd-set discovery-domain-set-name, ... delete-dd-set has no options. disable-dd-set The disable-dd-set subcommand disables a discovery domain set. The disable-dd-set subcommand has the following syntax: # isnsadm disable-dd-set discovery-domain-set-name, ... disable-dd-set has no options. enable-dd-set The enable-dd-set subcommand enables a discovery domain set. The enable-dd-set subcommand has the following syntax: # isnsadm enable-dd-set discovery-domain-set-name, ... enable-dd-set has no options. list-dd The list-dd subcommand displays information about discovery domains. If no operand is specified, it lists all discovery domains that cur- rently exist on the iSNS server. The list-dd subcommand has the following syntax: # isnsadm list-dd [option] [discovery-domain-name, ...] list-dd supports the following option: -v, --verbose Displays the member contents of the discovery domain(s). list-dd-set The list-dd-set subcommand lists the discovery domain sets, both enabled and disabled, that exist on the iSNS server. Note that there is no dd-set registration. If no operand is specified, it lists all of the discovery domain sets. The list-dd-set subcommand has the following syntax: # isnsadm list-dd-set [option] [discovery-domain-set-name, ...] list-dd-set supports the following option: -v, --verbose Shows all discovery domains within the discovery domain set. list-node The list-node subcommand displays information about nodes that are currently registered with the iSNS server or that are not registered and belong to non-default discovery-domain(s). For the latter case, the node has its type field shown as unknown. If no operand is specified, list-node lists all nodes known by the iSNS server. The list-node subcommand has the following syntax: # isnsadm list-node [options] [iscsi-node-name, ...] list-node supports the following options: -t, --target Filters the list to display only iSCSI target nodes. -i, --initiator Filters the list to display only iSCSI initiator nodes. -v, --verbose Displays details about a node. Without this option, only the name, alias, and type information are displayed. modify-dd The modify-dd subcommand modifies an attribute of a specified discovery domain. The modify-dd subcommand has the following syntax: # isnsadm modify-dd option discovery-domain-name modify-dd has the following option: -n discovery-domain-name Specifies the new name of a discovery domain to be applied to an existing discovery-domain. modify-dd-set The modify-dd-set subcommand modifies a discovery domain set. The modify-dd-set subcommand has the following syntax: # isnsadm modify-dd-set option discovery-domain-set-name modify-dd-set has the following option: -n discovery-domain-set-name Specifies the new name of a discovery domain set to be applied to an existing discovery-domain-set. remove-dd The remove-dd subcommand removes the association with a specified discovery domain set. The remove-dd subcommand has the following syntax: # isnsadm remove-dd option discovery-domain-name, ... remove-dd has the following option: -s discovery-domain-set-name Specifies the discovery domain set from which the discovery domain will be removed. remove-node The remove-node subcommand removes a node. The remove-node subcommand has the following syntax: # isnsadm remove-node option iscsi-node-name, ... remove-node has the following option: -d discovery-domain-name Specifies the discovery domain from which a node will be removed. show-config The show-config subcommand displays the iSNS server administrative settings. Note that the setting can be modified by means of the service management facility (see smf(5)). Refer to isns(1M). The show-config subcommand has the following syntax: # isnsadm show-config show-config has no options. EXAMPLES
Example 1 Displaying Clients The following use of the list-node subcommand displays clients. # isnsadm list-node -v iSCSI Name: iqn.1986-03.com.sun:01:000e0c9f10da.45173FEA.engr Alias: STK5320_NAS Type: Target Network Entity: SE5310 Portal: 172.20.57.95:3260 Portal Group: 1 Portal: 172.20.56.95:3260 Portal Group: 1 DD Name: Default iSCSI Name: iqn.1986-03.com.sun:01:000e0c9f10da.454F00A2.acct Alias: Type: Target Network Entity: SE5310 Portal: 172.20.57.95:3260 Portal Group: 1 Portal: 172.20.56.95:3260 Portal Group: 1 DD Name: Default iSCSI Name: iqn.1986-03.com.sun:01:e00000000000.46fd8e2b Alias: host-x2100 Type: Initiator Network Entity: iqn.1986-03.com.sun:01:e00000000000.46fd8e2b Portal: 172.20.236.123:58530 Portal Group: 1 DD Name: Default Example 2 Displaying a Discovery Domain The following use of the list-dd subcommand displays discovery domains. # isnsadm list-dd -v DD name: Default DD set(s): Default iSCSI Name: iqn.1986-03.com.sun:01:000e0c9f10da.45173FEA.engr iSCSI Name: iqn.1986-03.com.sun:01:000e0c9f10da.454F00A2.acct iSCSI name: iqn.1986-03.com.sun:01:e00000000000.46fd8e2b DD name: acct-dd DD name: engineering-dd Example 3 Adding a Node The following use of the add-node subcommand adds a node to a discovery domain, creating a discovery domain membership. # isnsadm add-node -d engineering-dd iqn.1986-03.com.sun:01:000e0c9f10da.454F00A2.engr Example 4 Removing a Node The following use of the remove-node subcommand removes a node from a discovery domain, thereby removing a discovery domain membership. # isnsadm remove-node -d acct-dd iqn.1986-03.com.sun:01:000e0c9f10da.454F00A2.acct Example 5 Creating a Discovery Domain Set The following use of the create-dd-set subcommand creates a discovery domain set. # isnsadm create-dd-set operation-dd-set Example 6 Displaying a Discovery Domain Set The following use of the list-dd-set subcommand displays discovery domain sets. # isnsadm list-dd-set -v DD Set name: Default State: Disabled DD Name: Default DD Set name: operation-dd-set State: Disabled Example 7 Adding a Discovery Domain The following use of the add-dd subcommand adds a discovery domain to a discovery domain set. # isnsadm add-dd -s operation-dd-set engineering-dd Example 8 Displaying a Discovery Domain Set The following use of the list-dd-set displays the attributes of a discovery domain set. # isnsadm list-dd-set DD Set name: Default State: Disabled DD Name: Default DD Set name: operation-dd-set State: Disabled DD Name: engineering-dd Example 9 Enabling a Discovery Domain Set The following use of the enable-dd-set subcommand enables a discovery domain set. # isnsadm enable-dd-set Default Example 10 Disabling a Discovery Domain Set The following use of the disable-dd-set subcommand disables a discovery domain set. # isnsadm disable-dd-set Default Example 11 Displaying Administrative Settings The following use of the show-config subcommand displays current administrative settings. # isnsadm show-config Data Store Location: /etc/isns/isnsdata.xml Entity Status Inquiry Non-Response Threshold: 3 Management SCN Enabled: yes Authorized Control Node Names: - ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWisnsadm | +-----------------------------+-----------------------------+ |Interface Stability |Volatile | +-----------------------------+-----------------------------+ SEE ALSO
iscsiadm(1M), iscsitadm(1M), isns(1M), attributes(5), smf(5) NOTES
When a subcommand is invoked with multiple operands and there are failures on one or more, but not all, operands, isnsadm displays a generic message indicating partial failure, with list of failed operands. An error on a specific operand can be found by issuing the same subcommand on the failing operand. SunOS 5.11 25 Sep 2008 isnsadm(1M)
All times are GMT -4. The time now is 07:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy