ioscan -fnC tape hangs and ioscan -kfnCtape shows "SCAN" in Hardware state

[sujit kumar singh]

server rx6600 ... msl 6060 Tape Library , FC Connected .. 11.23 HP-UX IA .. We had been today morning able to take backup and all without any probs ..
no changes on the CiscO SAN Switch zoning or ports. One backup had stuck and failed and after that ..we did ioscan and following is the O/P for all the ioscan -kfnCtape and ioscan -kfnCfc

Class I H/W Path Driver S/W State H/W Type Description
========================================================================
tape 23 0/2/1/0/4/0.191.19.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/23m /dev/rmt/c44t0d0BEST
/dev/rmt/23mb /dev/rmt/c44t0d0BESTb
/dev/rmt/23mn /dev/rmt/c44t0d0BESTn
/dev/rmt/23mnb /dev/rmt/c44t0d0BESTnb
tape 24 0/2/1/0/4/0.191.21.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/24m /dev/rmt/c45t0d0BEST
/dev/rmt/24mb /dev/rmt/c45t0d0BESTb
/dev/rmt/24mn /dev/rmt/c45t0d0BESTn
/dev/rmt/24mnb /dev/rmt/c45t0d0BESTnb
tape 19 0/2/1/0/4/0.191.33.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/19m /dev/rmt/c40t0d0BEST
/dev/rmt/19mb /dev/rmt/c40t0d0BESTb
/dev/rmt/19mn /dev/rmt/c40t0d0BESTn
/dev/rmt/19mnb /dev/rmt/c40t0d0BESTnb
tape 20 0/2/1/0/4/0.191.36.255.0.1.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/20m /dev/rmt/c41t1d0BEST
/dev/rmt/20mb /dev/rmt/c41t1d0BESTb
/dev/rmt/20mn /dev/rmt/c41t1d0BESTn
/dev/rmt/20mnb /dev/rmt/c41t1d0BESTnb
tape 25 0/3/1/0/4/0.148.21.255.0.0.1 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/25m /dev/rmt/c47t0d1BEST
/dev/rmt/25mb /dev/rmt/c47t0d1BESTb
/dev/rmt/25mn /dev/rmt/c47t0d1BESTn
/dev/rmt/25mnb /dev/rmt/c47t0d1BESTnb
tape 26 0/3/1/0/4/0.148.21.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/26m /dev/rmt/c47t0d2BEST
/dev/rmt/26mb /dev/rmt/c47t0d2BESTb
/dev/rmt/26mn /dev/rmt/c47t0d2BESTn
/dev/rmt/26mnb /dev/rmt/c47t0d2BESTnb
tape 30 0/3/1/0/4/0.148.21.255.0.0.4 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/30m /dev/rmt/c47t0d4BEST
/dev/rmt/30mb /dev/rmt/c47t0d4BESTb
/dev/rmt/30mn /dev/rmt/c47t0d4BESTn
/dev/rmt/30mnb /dev/rmt/c47t0d4BESTnb
tape 29 0/3/1/0/4/0.148.21.255.0.0.5 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/c47t0d5BEST /dev/rmt/c47t0d5BESTn
/dev/rmt/c47t0d5BESTb /dev/rmt/c47t0d5BESTnb
tape 33 0/3/1/0/4/0.148.22.255.0.0.0 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/33m /dev/rmt/c50t0d0BEST
/dev/rmt/33mb /dev/rmt/c50t0d0BESTb
/dev/rmt/33mn /dev/rmt/c50t0d0BESTn
/dev/rmt/33mnb /dev/rmt/c50t0d0BESTnb
tape 34 0/3/1/0/4/0.148.22.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/c50t0d2BEST /dev/rmt/c50t0d2BESTn
/dev/rmt/c50t0d2BESTb /dev/rmt/c50t0d2BESTnb
tape 27 0/6/1/0/4/0.148.21.255.0.0.1 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/27m /dev/rmt/c49t0d1BEST
/dev/rmt/27mb /dev/rmt/c49t0d1BESTb
/dev/rmt/27mn /dev/rmt/c49t0d1BESTn
/dev/rmt/27mnb /dev/rmt/c49t0d1BESTnb
tape 28 0/6/1/0/4/0.148.21.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/28m /dev/rmt/c49t0d2BEST
/dev/rmt/28mb /dev/rmt/c49t0d2BESTb
/dev/rmt/28mn /dev/rmt/c49t0d2BESTn
/dev/rmt/28mnb /dev/rmt/c49t0d2BESTnb
tape 31 0/6/1/0/4/0.148.21.255.0.0.3 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/31m /dev/rmt/c49t0d3BEST
/dev/rmt/31mb /dev/rmt/c49t0d3BESTb
/dev/rmt/31mn /dev/rmt/c49t0d3BESTn
/dev/rmt/31mnb /dev/rmt/c49t0d3BESTnb
tape 32 0/6/1/0/4/0.148.21.255.0.0.4 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/32m /dev/rmt/c49t0d4BEST
/dev/rmt/32mb /dev/rmt/c49t0d4BESTb
/dev/rmt/32mn /dev/rmt/c49t0d4BESTn
/dev/rmt/32mnb /dev/rmt/c49t0d4BESTnb




ioscan -kfnCfc O/P is


Class I H/W Path Driver S/W State H/W Type Description
========================================================================
fc 0 0/2/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd0
fc 1 0/2/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd1
fc 2 0/3/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd2
fc 3 0/3/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd3
fc 4 0/5/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd4
fc 5 0/5/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd5
fc 6 0/5/2/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd6
fc 7 0/5/2/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd7
fc 8 0/6/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd8
fc 9 0/6/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd9


Please suggest some from your side.


Regards
sujit

[Patrick Wallek]

SCAN means that there is another 'ioscan' process running. It was likely an 'ioscan -fnC tape' (note the absence of the '-k' option) and it is still running.

What does:

# ps -ef |grep ioscan

show? Are there any ioscan processes running?

[Steven E. Protter]

Shalom,

Ideas:
1) Unterminated scsi in the tape scsi chain
2) daisy chained devices, a big no no for tape drives.
3) Bad tape drive.
4) Problem with scsi controller

SEP

[sujit kumar singh]

HI Patrik and SEP , thanks for the responses.


Hi Patrick,


Yes there are ioscan s running whivh gad been executed without a -k option, few of them when tried to kill as they had all been hanging became defunct.

Hi SEP,

The standard and suggested way of the cabling in the NSR card to the SCSI Channels according to the MSL 6060 cabling has been done and there is none Chaining or Cascading of the Tape Drives in the Library and HTTP to the NSR shows the Terminations ON , Besides the Termination LED on the terminators are green.

Tried also by rebooting the MSL6060 but no results.

any ioscan without a -k hangs and after killing becomes defunct.

NSRs has been set to the N_Port Fabric mode, Mapping AUTO_assigned, Discovery Mode as auto on start -up and the changer and the Drives are visible in the respective NSR on the respective SCSI Ports as OK. All the Hosts as done in the zoning on the Cisco MDS 9000 FC Switch visible in the auto-assigned map on the NSR.

There are SUN servers and one HP_UX 11.23 , rx6600 on none of them the Library or the Media changer or the drives are visible.

Tried also by enabling / disabling zoning.

the ioscan -kfnCtape looks like

Class I H/W Path Driver S/W State H/W Type Description
========================================================================
tape 23 0/2/1/0/4/0.191.19.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/23m /dev/rmt/c44t0d0BEST
/dev/rmt/23mb /dev/rmt/c44t0d0BESTb
/dev/rmt/23mn /dev/rmt/c44t0d0BESTn
/dev/rmt/23mnb /dev/rmt/c44t0d0BESTnb
tape 24 0/2/1/0/4/0.191.21.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/24m /dev/rmt/c45t0d0BEST
/dev/rmt/24mb /dev/rmt/c45t0d0BESTb
/dev/rmt/24mn /dev/rmt/c45t0d0BESTn
/dev/rmt/24mnb /dev/rmt/c45t0d0BESTnb
tape 19 0/2/1/0/4/0.191.33.255.0.0.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/19m /dev/rmt/c40t0d0BEST
/dev/rmt/19mb /dev/rmt/c40t0d0BESTb
/dev/rmt/19mn /dev/rmt/c40t0d0BESTn
/dev/rmt/19mnb /dev/rmt/c40t0d0BESTnb
tape 20 0/2/1/0/4/0.191.36.255.0.1.0 stape SCAN DEVICE HP Ultrium 3-SCSI
/dev/rmt/20m /dev/rmt/c41t1d0BEST
/dev/rmt/20mb /dev/rmt/c41t1d0BESTb
/dev/rmt/20mn /dev/rmt/c41t1d0BESTn
/dev/rmt/20mnb /dev/rmt/c41t1d0BESTnb
tape 25 0/3/1/0/4/0.148.21.255.0.0.1 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/25m /dev/rmt/c47t0d1BEST
/dev/rmt/25mb /dev/rmt/c47t0d1BESTb
/dev/rmt/25mn /dev/rmt/c47t0d1BESTn
/dev/rmt/25mnb /dev/rmt/c47t0d1BESTnb
tape 26 0/3/1/0/4/0.148.21.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/26m /dev/rmt/c47t0d2BEST
/dev/rmt/26mb /dev/rmt/c47t0d2BESTb
/dev/rmt/26mn /dev/rmt/c47t0d2BESTn
/dev/rmt/26mnb /dev/rmt/c47t0d2BESTnb
tape 30 0/3/1/0/4/0.148.21.255.0.0.4 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/30m /dev/rmt/c47t0d4BEST
/dev/rmt/30mb /dev/rmt/c47t0d4BESTb
/dev/rmt/30mn /dev/rmt/c47t0d4BESTn
/dev/rmt/30mnb /dev/rmt/c47t0d4BESTnb
tape 29 0/3/1/0/4/0.148.21.255.0.0.5 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/c47t0d5BEST /dev/rmt/c47t0d5BESTn
/dev/rmt/c47t0d5BESTb /dev/rmt/c47t0d5BESTnb
tape 33 0/3/1/0/4/0.148.22.255.0.0.0 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/33m /dev/rmt/c50t0d0BEST
/dev/rmt/33mb /dev/rmt/c50t0d0BESTb
/dev/rmt/33mn /dev/rmt/c50t0d0BESTn
/dev/rmt/33mnb /dev/rmt/c50t0d0BESTnb
tape 34 0/3/1/0/4/0.148.22.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/c50t0d2BEST /dev/rmt/c50t0d2BESTn
/dev/rmt/c50t0d2BESTb /dev/rmt/c50t0d2BESTnb
tape 27 0/6/1/0/4/0.148.21.255.0.0.1 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/27m /dev/rmt/c49t0d1BEST
/dev/rmt/27mb /dev/rmt/c49t0d1BESTb
/dev/rmt/27mn /dev/rmt/c49t0d1BESTn
/dev/rmt/27mnb /dev/rmt/c49t0d1BESTnb
tape 28 0/6/1/0/4/0.148.21.255.0.0.2 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/28m /dev/rmt/c49t0d2BEST
/dev/rmt/28mb /dev/rmt/c49t0d2BESTb
/dev/rmt/28mn /dev/rmt/c49t0d2BESTn
/dev/rmt/28mnb /dev/rmt/c49t0d2BESTnb
tape 31 0/6/1/0/4/0.148.21.255.0.0.3 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/31m /dev/rmt/c49t0d3BEST
/dev/rmt/31mb /dev/rmt/c49t0d3BESTb
/dev/rmt/31mn /dev/rmt/c49t0d3BESTn
/dev/rmt/31mnb /dev/rmt/c49t0d3BESTnb
tape 32 0/6/1/0/4/0.148.21.255.0.0.4 stape SCAN DEVICE HP Ultrium 2-SCSI
/dev/rmt/32m /dev/rmt/c49t0d4BEST
/dev/rmt/32mb /dev/rmt/c49t0d4BESTb
/dev/rmt/32mn /dev/rmt/c49t0d4BESTn
/dev/rmt/32mnb /dev/rmt/c49t0d4BESTnb


IN that the Ultruim-3 Drives correspond to the MSL 8096 that has been removed.




had also tried by detaching the FC connected at the MSL Side so some errors in the event logs also can have a look at the same , but the same persists.



EVENT log is as follows:



Notification Time: Wed Apr 1 18:19:02 2009

aivmh sent Event Monitor notification information:

/adapters/events/ql_adapter/0_3_1_0_4_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Wed Apr 1 18:19:02 2009
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 59
System..............: aivmh

Summary:
Adapter at hardware path 0/3/1/0/4/0 : Target device is back. Port
World-wide name remains the same as original.



Description of Error:


lbolt value: 141459731

Target with device id 0x941500 is back in the Name Server GPN_FT (FCP type)
response. And the 'Port World-wide name' remains the same as original.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

This is a paired message with "Target device is lost in the
Name Server GPN_FT response".
On receiving another RSCN, driver sent Name Server GPN_FT request
to obtain all the FC-4 type device information in the fabric.
Driver has detected that a previously lost device (Nport_id)
is back in the GPN_FT response, or it's corresponding World-Wide
Name remains the same.

Driver will be able to communicate with the device.
No action is needed.


Additional Event Data:
System IP Address...: 10.2.16.98
Event Id............: 0x49d362be00000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x49d362be00000000
Additional System Data:
System Model Number.............: ia64 hp server rx6600
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#59

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 0/3/1/0/4/0

I/O Log Event Data:

Driver Status Code..................: 0x0000003B
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 66 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 086E8113 00000001 00000001 00941500 2F75782F 636F7265 2F697375
2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D
2E63





>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed Apr 1 21:54:59 2009

aivmh sent Event Monitor notification information:

/adapters/events/ql_adapter/0_6_1_0_4_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Wed Apr 1 21:54:59 2009
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 59
System..............: aivmh

Summary:
Adapter at hardware path 0/6/1/0/4/0 : Target device is back. Port
World-wide name remains the same as original.



Description of Error:


lbolt value: 142755431

Target with device id 0x941500 is back in the Name Server GPN_FT (FCP type)
response. And the 'Port World-wide name' remains the same as original.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

This is a paired message with "Target device is lost in the
Name Server GPN_FT response".
On receiving another RSCN, driver sent Name Server GPN_FT request
to obtain all the FC-4 type device information in the fabric.
Driver has detected that a previously lost device (Nport_id)
is back in the GPN_FT response, or it's corresponding World-Wide
Name remains the same.

Driver will be able to communicate with the device.
No action is needed.


Additional Event Data:
System IP Address...: 10.2.16.98
Event Id............: 0x49d3955b00000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x49d3955b00000000
Additional System Data:
System Model Number.............: ia64 hp server rx6600
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#59

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 0/6/1/0/4/0

I/O Log Event Data:

Driver Status Code..................: 0x0000003B
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 66 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 08824667 00000001 00000001 00941500 2F75782F 636F7265 2F697375
2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D
2E63





>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed Apr 1 22:03:53 2009

aivmh sent Event Monitor notification information:

/adapters/events/ql_adapter/0_6_1_0_4_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Wed Apr 1 22:03:53 2009
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 58
System..............: aivmh

Summary:
Adapter at hardware path 0/6/1/0/4/0 : Device id has disappeared from
GPN_FT response or
Port World-wide name for device has changed.



Description of Error:


lbolt value: 142808876

The device id has disappeared from Name Server GPN_FT (FCP type) response
OR Port World-wide name for device id 0x941500 has changed.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

On receiving RSCN, driver sent Name Server GPN_FT request to
obtain all the FC-4 type device information in the fabric.
Driver has detected that a previously discovered device
(Nport_id) is no longer in the GPN_FT response, or it's
corresponding World-Wide Name has changed.

Driver won't be able to communicate with the device any
more, please check that device.
If the problem persists, please contact your HP customer
representative.


Additional Event Data:
System IP Address...: 10.2.16.98
Event Id............: 0x49d3977100000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x49d3977100000002
Additional System Data:
System Model Number.............: ia64 hp server rx6600
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#58

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 0/6/1/0/4/0

I/O Log Event Data:

Driver Status Code..................: 0x0000003A
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 66 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 0883172C 00000001 00000001 00941500 2F75782F 636F7265 2F697375
2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D
2E63





>---------- End Event Monitoring Service Event Notification ----------<


Please suggest
regards
sujit

[sujit kumar singh]

Hi


Also to add that the ioscan have hung without any O/P for more that 3 hours now.

Regards
sujit

[T G Manikandan]

Please check the syslog.log file. I suppose you need to check if you notice lbolt errors.

I would suggest you to check the scsi termination.

[Torsten.]

Do you really have 14 drives in this MSL library?

You should use an "indexed" map for the NSR, not auto-assigned!

[sujit kumar singh]

Hi Mani and Torsten, Thanks for the replies.

Ok well there are in all 4 drives in the MSL6060 all ultrium-2 and the Ultrium-3 that is being seen is for a temporarily disconnected MSL8096 which is not right now connected.

Correctly we should see only 1 CHanger and only 4 Drives as CALIMED if all Fine.

We have only the MSL6060 right now connected to the server rx6600 and no other Tape Library.

We also had checked by doing the indexed MAP on the NSR but that also did not help.

Regarding the SCSI Termination and Such can please tell in details how to perform a check?

However for one more information when the MSL 6060 was freshly zoned with the same NSR settings to an existing rx8640 NPAR Server running 11.23 all the 4 drives got detected in a single shot and the MSL 6060 is visible on the rx8640 server.

The Currnet NSR Setting for which this is getting deteced flawlessly on rx 8640 are as :

Fabric_Mode N_Port, Discovery Mode: Auto on Start Up, Mapping : Auto_Assigned , The SCSI Termination as seen from HTTP to the NSRs is ON and the Changer and the SCSI Drives being detected in the respective NSRs,The HOST FC WWN being discovered in the NSR Mappings, there are 2 NSRs and both connected to CISCO MDS 9000 SAN Switch, Zoned with the rx8640 Server, all working fine on the rx8640, But the same settings and zoning not working for the rx6600.

We have asked for a reboot of the rx6600 but that is an IVM host and has 5 IVM guests on that running on Various applications of SAP QA and DEV. The rx6600 has 60GB Phys MEM and 6 Cores. The customer wants to avoid the Reboot of the IVM Guests and the IVM Host rx6600. No ideas perhaps the Reboot shall help!

Please suggest
regards
sujit

[Torsten.]

You should really ensure to use an indexed map, not auto-assigned.

If you have multiple FC HBAs (you have!), adjust your zoning so that only one can see the library and do the same in your NSR map.

[sujit kumar singh]

Hi Torsten,

OK Shall be ensuring the Indexd Map on the NSR and yes the zoning as on the Cisco MDS 9000 Includes onlhy one FC HBA from the server that is on the path /dev/fcd2 that is 0/3/1/0/4/0.

Also shall be ensuring that only one FC HBA that is /dev/fcd2 is zoned with the NSRs of the Library MSL 6060 and if others appear in the zoning with NSR of the TL , shall be removing that and shall let know.

Meanwhile if you have any other ideas then also can share.

Also we are planning for a reboot of the system.


Regards
sujit