cancel
Showing results for 
Search instead for 
Did you mean: 

All drives showing AVR

Venki009
Level 4

Hi Team,

 

Tape library on my server showing all drives as AVR mode.

Pls help

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Venki009 - please help us to help you and reply to the questions we have been asking.

Not sure why you have started a new discussion:
Library in AVR mode 
without giving us any information about your environment.

Have a look at this TN and previous discussions for troubleshooting tips and type of information needed:

http://www.symantec.com/docs/TECH38829 

https://www-secure.symantec.com/connect/forums/all-drives-are-avr-state 

https://www-secure.symantec.com/connect/forums/all-tape-drives-are-avr-state

View solution in original post

24 REPLIES 24

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

See if OS can see the robot on robot control host:

Post output of cfgadm -al 
and
/usr/openv/volmgr/bin/sgscan

revarooo
Level 6
Employee

AVR mode is rarely ever a NetBackup issue.

rookie11
Moderator
Moderator
   VIP   

Once u check output as suggested by marianne. please paste it. if it is detectable at OS level then simply reboot ur tape library.

u can also dwell into OS logs to check if something useful can be found.

 

Greek-God
Level 3
Employee Accredited

Also Please check the errors in the  /var/adm/messages file , The logs might have error regarding the tape device. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

No reply from Venki009 in 3 days....

I guess it cannot be too much of an issue! surprise

mph999
Level 6
Employee Accredited
The tape device is not at fault as such, most likely is communication to the library was lost, or the drives were configured as standalone, in which case AVR would be correct, though of course, not what you were expecting.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Venki009 - please help us to help you and reply to the questions we have been asking.

Not sure why you have started a new discussion:
Library in AVR mode 
without giving us any information about your environment.

Have a look at this TN and previous discussions for troubleshooting tips and type of information needed:

http://www.symantec.com/docs/TECH38829 

https://www-secure.symantec.com/connect/forums/all-drives-are-avr-state 

https://www-secure.symantec.com/connect/forums/all-tape-drives-are-avr-state

SaurabhHeda
Level 4
Employee Accredited

Hi Venki009

The drives goes in AVR mode is most often a result of communication problems.There are two NetBackup daemons for robotic control:  one runs on the machine with robotic control, the other runs on the machine that has drives in the robot. For example, if the robot is a TLD robot the two daemons are tldcd(runs on the server with robotic control) and tldd (runs on server with drives on the robot). 

Check the network connectivity between the robot control host and device host. From robot control host You can try: 

bptestbpcd -client <robot_control_host>

How to test client connections using the bptestbpcd command

http://www.symantec.com/business/support/index?page=content&id=TECH42657

Thanks,

Saurabh

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Curious to know how backups will be done this weekend...

Drives in AVR state since last Saturday? frown

Venki009
Level 4

Hi marianne,

Every thing is fine upto today ,again drives on avr mode on other server.

its linux

./scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************


its not showing anything

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks for telling us that it is Linux. 
You have selected Solaris as OS.

Was everything working fine previously? If so, what has changed?

It seems that the OS has lost connectivity to the robot and the drives.
Have you checked the robot console and/or GUI interface for errors?
If SAN connected - have you checked switch logs?
Physical connectivity - cables, etc?

Please check what the OS sees:

cat /proc/scsi/scsi

 

Venki009
Level 4

Hi,

cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM-ESXS Model: ST9600205SS      Rev: B552
  Type:   Direct-Access                    ANSI SCSI revision: 06
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM-ESXS Model: ST9600205SS      Rev: B552
  Type:   Direct-Access                    ANSI SCSI revision: 06
Host: scsi0 Channel: 01 Id: 03 Lun: 00
  Vendor: LSILOGIC Model: Logical Volume   Rev: 3000
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 01 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 01
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 02
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 03
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 04
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 05
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 02 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 01
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 02
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 03
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 04
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 05
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 03 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 04 Lun: 00
  Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
  Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi3 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 01
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 02
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 03
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 04
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 01 Lun: 05
  Vendor: IBM      Model: VirtualDisk      Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 01
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 02
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 03
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 04
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 05
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
  Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi1 Channel: 00 Id: 01 Lun: 01
  Vendor: IBM      Model: 3573-TL          Rev: C.20
  Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 00
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 01
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 02
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 03
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 04
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 05
  Vendor: IBM      Model: 1746      FAStT  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 02 Lun: 31
  Vendor: IBM      Model: Universal Xport  Rev: 1070
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 05 Lun: 00
  Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
  Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi1 Channel: 00 Id: 03 Lun: 00
  Vendor: IBM      Model: ULT3580-HH5      Rev: D8D5
  Type:   Sequential-Access                ANSI SCSI revision: 06
Host: scsi2 Channel: 00 Id: 05 Lun: 01
  Vendor: IBM      Model: 3573-TL          Rev: C.20
  Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 04 Lun: 01
  Vendor: IBM      Model: 3573-TL          Rev: C.20
  Type:   Medium Changer                   ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 03 Lun: 01
  Vendor: IBM      Model: 3573-TL          Rev: C.20
  Type:   Medium Changer                   ANSI SCSI revision: 05

 

Venki009
Level 4

Hi,

My TL again reconfigure the entire drives.Now its working fine.

What is basic cause of drives going AVR mode can u please elobrate.

 

Thanx

Will_Restore
Level 6

As noted above, communication loss is the likely problem.  It could be cable disconnect, bad switch or HBA.  You have to trace the path from library to host, verifying each part along the way.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

NBU needs the OS for device access.

All device-related troubleshooting should start at OS level.

Check /var/log/messages for errors when drives go in AVR state.

Please look at all the URLs that I posted on 4 Sept:
https://www-secure.symantec.com/connect/forums/all-drives-showing-avr#comment-10456631

Venki009
Level 4

Thanks all.

Venki009
Level 4

Hi marianne,

Again AVR mode,why this happen frequently,is any problem with drives or os.

pls help

output of /var/log/messages

 

Sep  6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Starting checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep  6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep  6 10:41:17 SRILANKA SQLAnywhere(nb_SRILANKA): Finished checkpoint of "NBAZDB" (NBAZDB.db) at Sat Sep 06 2014 10:41

Sep  6 10:42:35 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:42:35 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:43:35 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a6d 2002.

Sep  6 10:43:35 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a6d 2002.

Sep  6 10:43:35 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:43:35 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:43:35 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:43:35 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:43:37 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep  6 10:43:37 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep  6 10:43:37 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:43:37 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:44:37 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a8d 2002.

Sep  6 10:44:37 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704a8d 2002.

Sep  6 10:44:37 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:44:37 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:44:37 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:44:37 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:44:37 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep  6 10:44:37 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep  6 10:44:37 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep  6 10:44:37 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep  6 10:46:39 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:46:39 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:47:39 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704aea 2002.

Sep  6 10:47:39 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704aea 2002.

Sep  6 10:47:39 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:47:39 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:47:39 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:47:39 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:47:41 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep  6 10:47:41 SRILANKA tldcd[25107]: tldcd.c.3021, process_request(), received command=9, from peername=172.27.195.56, version 50

Sep  6 10:47:41 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:47:41 SRILANKA tldcd[25107]: TLD(0) opening robotic path /dev/sg16

Sep  6 10:48:41 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704b12 2002.

Sep  6 10:48:41 SRILANKA kernel: qla2xxx 0000:29:00.0: scsi(1:1:1): Abort command issued -- 1 10704b12 2002.

Sep  6 10:48:41 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:48:41 SRILANKA kernel: scsi 1:0:1:1: timing out command, waited 60s

Sep  6 10:48:41 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:48:41 SRILANKA tldcd[25107]: TLD(0) mode_sense ioctl() failed: Success

Sep  6 10:48:41 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep  6 10:48:41 SRILANKA tldd[25098]: DecodeQuery() Actual status: Unable to sense robotic device

Sep  6 10:48:41 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Sep  6 10:48:41 SRILANKA tldd[25098]: TLD(0) unavailable: initialization failed: Unable to sense robotic device

Venki009
Level 4

Hi,

./scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
************************************************************

./robtest
Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = /dev/sg16

Robot Selection
---------------
  1)  TLD 0
  2)  none/quit
Enter choice: 1

Robot selected: TLD(0)   robotic path = /dev/sg16

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg16

Opening /dev/sg16

 

 

 

mph999
Level 6
Employee Accredited
AVR is either : Drives not configured as robotic controlled Drives correctly configured, but comms failure to the robot If drives on avr on a media server that is not the robot control host, but drives on the robot control host are fine, then comms issue between tldd on the media server and tldcd on the robot control host. I don't think I have ever seen a AVR issue not caused by one of the above.