pingdev

Purpose

Use the pingdev command to determine whether a device is accessible to Oracle Secure Backup by means of all configured attachments.

For each attachment defined for the device, Oracle Secure Backup performs the following steps:

1. Establishes a connection to the device

2. Queries the device's identity by using the SCSI inquiry command

3. Closes the connection

For each attachment that is remote from the host running obtool, Oracle Secure Backup establishes an NDMP session with the remote media server to test the attachment.

Prerequisites

You must have the right to manage devices and change device state to use the pingdev command.

Syntax

pingdev::=

pingd•ev [ --nohierarchy/-H ] [ --quiet/-q | --verbose/-v ]
[ --host/-h hostname ]... { --all/-a | devicename ... }

Semantics

--nohierarchy/-H

Suppresses access to each drive contained in a tape library. By default, obtool pings each drive contained in the library.

--quiet/-q

Suppresses output. By default, obtool displays the output shown in Example 2-101.

--verbose/-v

Displays verbose output as shown in the following sample output:

ob> pingdev --verbose lib1
Info: pinging library lib1.
Info: library    lib1             accessible.
Info: pinging drive tape1.
Info:   drive  1 tape1            accessible.

By default, obtool displays the output shown in Example 2-101.

--host/-h hostname ...

Specifies the name of the host machine whose attached devices you are pinging.

--all/-a

Pings all defined devices.

devicename ...

Specifies the name of the device that you want to ping. Refer to "devicename" for the rules governing device names.

Example

Example 2-101 pings the tape drive called tape3. The tape device has attachments to multiple hosts.

ob> pingdev tape3
Info: drive      tape3            via host stadv07 accessible.
Info: drive      tape3            via host brhost3 accessible.
ob> pingdev --host brhost3 tape3
Info: drive      tape3            via host brhost3 accessible.