Home > Unable To > Tld 0 Mode_sense Error

Tld 0 Mode_sense Error

Contents

try a backup 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Doing add_drv of the sg driver Leaving existing sg configuration. Step 5. Go to Solution.

Will_Restore Level 6 ‎05-25-2010 01:47 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content can you see the drives in After that, if we go to the SLC robot arm is marked with a red X.Many libraries have a way to do tape motion directly from the front panel. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Your OS can no longer see the RiaanBadenhorst Moderator Partner Trusted Advisor Accredited Certified ‎02-16-2015 04:12 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to visit

Robot Inventory Failed: Unable To Sense Robotic Device (202)

HBA vendors usually provide a utility, luxadm is another solaris command that can be used). Jan 8 19:15:12 nbolmasterback emlxs: [ID 349649 kern.info] [ 5.04B4]emlxs1: NOTICE: 720: Link up. (4Gb, loop, initiator) Jan 8 19:15:14 nbolmasterback emlxs: [ID 349649 kern.info] [ 5.0554]emlxs1: NOTICE: 730: Link reset. Martin 0 Kudos Reply Check One more thing "Physically" bharatgangawane Level 5 ‎03-18-2012 01:10 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Assuming SAN connectivity, have you verified that the HBA is still logged into the fabric?

After doing that and rebooting the master with a reconfiguration we lost the robot. > > Everything is connected to McData switch and on the switch side I see all the Observe the status of the robot by looking at this or by using a Web interface to connect the robot, if one is available from the vendor. If this request isn't returned you get a "mode_sense ioctl failed". You need to check the following: Device Manager Event Viewer System Log Event Viewer Application log.

Additionally,robtest is not really a NetBackup command. Robot Inventory Failed: Unable To Open Robotic Path (201) You can try reboot the server/robot to see if it picks up the devices on a SCSI layer after that. 0 Kudos Reply If Robtest does not work, revarooo Level 6 May be this erro will not come in Future.. Re: robtest commands mode sense failing Stumpr2 Level 6 Trusted Advisor ‎08-13-2007 04:42 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report

Re-running cfgadm -al -o show_FCP_dev after this step still shows changer and tape in 'failed' condition. Any troubleshooting should therefore start at O/S level. In some configurations, stopping this service can resolve robot communication issues in NetBackup. also, look at the dmesg info, Apr 6 10:58:15 ATPBACKUPSP01 avrd[25419]: [ID 415999 daemon.notice] Unable to determine sg name for /dev/rmt/13cbn, using open() for scanning Apr 6 10:58:15 ATPBACKUPSP01 avrd[25419]:

Robot Inventory Failed: Unable To Open Robotic Path (201)

NetBackup periodically probe configured robots. https://vox.veritas.com/t5/NetBackup/TLD-0-going-to-DOWN-state-status-Unable-to-sense-robotic-device/td-p/483044 The following are useful tools in determining the root cause.  Event Viewer logs Be sure to look at the Event Viewer System and Application logs on the NetBackup Server that is Robot Inventory Failed: Unable To Sense Robotic Device (202) Assuming the default location of the NetBackup Install: "C:\Program Files\VERITAS\Volmgr\bin\scan.exe" How many tape drives are listed Do they report the following details: Device Name, Host, Port, Target, LUN, Serial Number, Inquiry Auto Empty Media Access Port Request Rejected By Tldcd, Unable To Sense Robotic Device View solution in original post 0 Kudos Reply 7 Replies also the output of scan ronak_padhya Level 3 ‎02-16-2015 04:03 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed

No lun# is displayed in your output, and device conditionis displayed as "failed". Can someone please explain me the meaning of "Ready and Write Enable = “No”" under the "Device Monitor" tab for the Drive even though the backups are running fine? 0 Kudos It is better to disable autonegotiation, If possible. The service avrd.exe is not running.

Please log a support call Marianne Moderator Partner Trusted Advisor Accredited Certified ‎03-20-2012 12:01 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Are you getting the error when you start robtest or when you're typing in 's d' / 's s'? anywho, after fixing my mistake: bash-3.00# modunload -i `modinfo| awk '$6=="sg"{print $1}'` bash-3.00# mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old bash-3.00# mv sg.links sg.links.safe bash-3.00# mv sg.conf sg.conf.safe bash-3.00# ../sg.build all The file ./st.conf should Jan 8 19:17:24 nbolmasterback emlxs: [ID 349649 kern.info] [ 5.04B4]emlxs1: NOTICE: 720: Link up. (4Gb, loop, init _________________ tpautoconf and scan -changer no longer bring anything up, as the robot

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Robot Enable=no (down) VOX : Backup and Recovery : NetBackup : Robot Enable=no (down) In this case, it should be reconfigured. any pertinent messages in Event Viewer? 0 Kudos Reply Check if the library is MOHAMED_PATEL Level 5 Partner Accredited Certified ‎05-25-2010 01:56 PM Options Mark as New Bookmark Subscribe Subscribe to

Try to powercycle the robot.

All output seen in robtest when you run commands (eg. Go to Solution Robot showing disabled ronak_padhya Level 3 ‎02-16-2015 03:59 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content [email protected] netbackup $ echo $(date) Fri Jan 4 12:08:03 GMT 2013 Hence ... Note.

Doing add_drv of the sg driver devfsadm: driver failed to attach: sg Warning: Driver (sg) successfully added to system but failed to attach WARNING: /usr/sbin/add_drv failed. Assuming the default location of the NetBackup Install: "C:\Program Files\VERITAS\Volmgr\bin\scan.exe" How many tape drives are listed Do they report the following details: Device Name, Host, Port, Target, LUN, Serial Number, Inquiry Can the Media Server communicate over the data path to the tape drives? Before disabling RSM, ensure that the service is not required for other unrelated purposes, such as removable hard disks.      Terms of use for this information are found in Legal

If the robot is fiber attached and there is other SAN Equipment involved between the robot and host, follow the hardware vendor's recommended power cycle procedure for the configuration.