Inquire_config

Use this vmcli command to view configuration information about the Tivoli® Storage Manager nodes associated with Data Protection for VMware.

Syntax

The vmcli -f inquire_config command uses this syntax:

vmcli -f inquire_config [-t backuptype] [-v vcenternodename | vcloudnodename] [-s tsmserverhostname] [-n vctrclinodename] [-p tsmserverport]

You must issue the vmcli -f inquire_config command as tdpvmware user, and not as root.

Parameters

[-t backuptype]

Specify the type of backup. You can choose from one of the following types:

TSM: Select a backup that was created with Tivoli Storage Manager for Virtual Environments. This type must be specified when in vCloud mode.
FCM: Select a backup that was created with IBM® Tivoli Storage FlashCopy® Manager for VMware.

[-v vcenternodename | vcloudnodename]

Depending on the backup environment, specify the virtual node that represents either a vCenter or the vCloud Director. If this parameter is not specified in the Data Protection for VMware command-line interface, the value in the profile is used.

[-s tsmserverhostname]

Specify the host name or IP address of the Tivoli Storage Manager server. If this parameter is not specified, the value in the profile is used.

[-n vctrclinodename]

Specify the VMCLI node name. This name is the node that connects the Data Protection for VMware command-line interface to the Tivoli Storage Manager server and the data mover node. If this parameter is not specified, the value in the profile is used.

[-p tsmserverport]

Specify the port of the Tivoli Storage Manager server.

If this parameter is not specified in the Data Protection for VMware command-line interface and not specified in the profile, the default port (1500) is used.
If this parameter is not specified in the Data Protection for VMware command-line interface but is specified in the profile, the value in the profile is used.

vSphere environment example

The parameter values in this output for the vmcli -f inquire_config -s TSM command show that the Data Protection for VMware command-line interface recognizes the Tivoli Storage Manager node configuration. As a result, the configuration is correct:

#TASK 38 inquire_config 20140108213337381
#PARAM INSTALLED=TSM
#RUN 32 20140108213337381
#LANG en_US
#PARAM BACKEND=TSM
#PARAM OPERATION_TYPE 5
#PHASE_COUNT 4
#PHASE PREPARE
#PARAM BACKUP_TYPE=0
#PARAM TSM_SERVER_NAME=FVTSERIES11ESX6.STORAGE.MYCOMPANY.COM
#PARAM TSM_SERVER_PORT=1500
#PARAM TSMCLI_NODE_NAME=DPM02_VMCLI
#PARAM VCENTER_NODE_NAME=DPM02_VC1
#PARAM DATACENTER_NODE_NAME=
#PARAM OFFLOAD_HOST_NAME=
#PARAM PASSWORD_TYPE=CLINODE
#PARAM TSM_OPTFILE=C:\Users\ADMINI~1\AppData\Local\Temp\2\T4VBE42.tmp
#PARAM INPUT_FILE=
#PARAM TRACEFILE=
#PARAM TRACEFLAGS=
#PARAM RUNID=38
#PHASE INITIALIZE
#PHASE INQUIRE_DATACENTER_NODES
#CHILD datacenternode:DC1::DPM02_DC1
#PARENT vcenternode:DPM02_VC1
#PHASE INQUIRE_PROXY_NODES
#CHILD targetnode:DPM02_DC1
#PARENT peernode:DPM02_DC1_DM
#CHILD hladdress:tsmveesx2vm50.storage.mycompany.com
#PARENT peernode:DPM02_DC1_DM
#CHILD lladdress:49394
#PARENT peernode:DPM02_DC1_DM
#CHILD nodetype:DMNODE
#PARENT peernode:DPM02_DC1_DM
#CHILD partner:
#PARENT peernode:DPM02_DC1_DM
#CHILD targetnode:DPM02_DC1
#PARENT peernode:DPM02_DC1_2_MP_WIN
#CHILD hladdress:tsmveesx2vm50.storage.mycompany.com
#PARENT peernode:DPM02_DC1_2_MP_WIN
#CHILD lladdress:49453
#PARENT peernode:DPM02_DC1_2_MP_WIN
#CHILD nodetype:MPNODE
#PARENT peernode:DPM02_DC1_2_MP_WIN
#CHILD partner:DPM02_DC1_2_MP_LNX
#PARENT peernode:DPM02_DC1_2_MP_WIN
#CHILD targetnode:DPM02_DC1
#PARENT peernode:DPM02_DC1_2_MP_LNX
#CHILD hladdress:
#PARENT peernode:DPM02_DC1_2_MP_LNX
#CHILD lladdress:
#PARENT peernode:DPM02_DC1_2_MP_LNX
#CHILD nodetype:MPNODE
#PARENT peernode:DPM02_DC1_2_MP_LNX
#CHILD partner:DPM02_DC1_2_MP_WIN
#PARENT peernode:DPM02_DC1_2_MP_LNX
#PARAM STATUS=success
#PARAM STATUS=success
#END RUN 32 20140108213340100
#END TASK 38
#INFO FMM16014I The return code is 0.
#END

The PHASE INQUIRE_DATACENTER_NODES section shows the mapping of the datacenter name (DC1) from vSphere to the Tivoli Storage Manager node name for that datacenter (DPM02_DC1). The datacenter name is case sensitive and must be identical to the name shown in vSphere for the mapping to function.

The PHASE INQUIRE_PROXY_NODES section shows the data mover nodes with proxy access to each data center node. The format for this proxy relationship is shown in pairs:

#CHILD targetnode::<datacenter node name>
#PARENT peernode::<data mover node name>

Two types of proxy nodes are identified in the PHASE INQUIRE_PROXY_NODES section:

The CHILD nodetype:DMNODE subsection identifies the data mover nodes and their proxy relationships.
The CHILD nodetype:MPNODE subsection identifies the mount proxy nodes and their proxy relationships. These nodes represent the proxy system that accesses mounted VM disks through an iSCSI connection. Mount proxy nodes are required for file-level restore operations.

vCloud environment example

#TASK 3 inquire_config 20130109143746117
#PARAM INSTALLED=TSM
#RUN 2 20130109143746117
#LANG en_US
#PARAM BACKEND=TSM
#PARAM OPERATION_TYPE 4
#PHASE_COUNT 5

#PHASE PREPARE
#PARAM BACKUP_TYPE=0
#PARAM TSM_SERVER_NAME=VM-08R2-TSMDEV2
#PARAM TSM_SERVER_PORT=1500
#PARAM VCLOUD
#PARAM TSMCLI_NODE_NAME=VMCLI_OFIR
#PARAM VCLOUD_NODE_NAME=VCD_EUROPE
#PARAM DATACENTER_NODE_NAME=
#PARAM OFFLOAD_HOST_NAME=
#PARAM PASSWORD_TYPE=CLINODE
#PARAM TSM_OPTFILE=C:\Users\qa\AppData\Local\Temp\1\T4VEEF3.tmp
#PARAM INPUT_FILE=
#PARAM TRACEFILE=tsmcli.trace
#PARAM TRACEFLAGS=api api_detail

#PHASE INITIALIZE

#PHASE INQUIRE_PVDC_NODES

#CHILD  targetnode:VCD_EUROPE 
#PARENT peernode:PVDC_GOLD 
#CHILD  pvdcname:Gold provider vDC 
#PARENT peernode:PVDC_GOLD  
#CHILD  targetnode:VCD_EUROPE 
#PARENT peernode:PVDC_SILVER 
#CHILD  pvdcname:Silver provider vDC 
#PARENT peernode:PVDC_SILVER  

#PHASE INQUIRE_OVDC_NODES

#CHILD  targetnode:PVDC_GOLD 
#PARENT peernode:OVDC_HAIFA 
#CHILD  orgname:Israel 
#PARENT peernode:OVDC_HAIFA 
#CHILD  orgvdcname:Haifa organization virtual data center 
#PARENT peernode:OVDC_HAIFA  
#CHILD  targetnode:PVDC_SILVER 
#PARENT peernode:OVDC_JERUSALEM 
#CHILD  orgname:Israel 
#PARENT peernode:OVDC_JERUSALEM 
#CHILD  orgvdcname:Jerusalem organization virtual data center 
#PARENT peernode:OVDC_JERUSALEM  
#CHILD  targetnode:PVDC_GOLD 
#PARENT peernode:OVDC_MUNICH 
#CHILD  orgname:Germany 
#PARENT peernode:OVDC_MUNICH 
#CHILD  orgvdcname:Munich organization virtual data center 
#PARENT peernode:OVDC_MUNICH  
#CHILD  targetnode:PVDC_SILVER 
#PARENT peernode:OVDC_MAINZ 
#CHILD  orgname:Germany 
#PARENT peernode:OVDC_MAINZ 
#CHILD  orgvdcname:Mainz organization virtual data center 
#PARENT peernode:OVDC_MAINZ

#PHASE INQUIRE_DM_NODES

#CHILD  targetnode:PVDC_GOLD
#PARENT peernode:DM_DM1
#CHILD  targetnode:OVDC_HAIFA
#PARENT peernode:DM_DM1
#CHILD  targetnode:OVDC_MUNICH
#PARENT peernode:DM_DM1
#CHILD  hladdress:vm-DM1.com
#PARENT peernode:DM_DM1
#CHILD  lladdress:49391
#PARENT peernode:DM_DM1

#CHILD  targetnode:PVDC_GOLD
#PARENT peernode:DM_DM2
#CHILD  targetnode:OVDC_HAIFA
#PARENT peernode:DM_DM2
#CHILD  targetnode:OVDC_MUNICH
#PARENT peernode:DM_DM2
#CHILD  hladdress:vm-DM2.com
#PARENT peernode:DM_DM2
#CHILD  lladdress:49392
#PARENT peernode:DM_DM2

#CHILD  targetnode:PVDC_SILVER
#PARENT peernode:DM_DM3
#CHILD  targetnode:OVDC_JERUSALEM
#PARENT peernode:DM_DM3
#CHILD  targetnode:OVDC_MAINZ
#PARENT peernode:DM_DM3
#CHILD  hladdress:vm-DM3.com
#PARENT peernode:DM_DM3
#CHILD  lladdress:49391
#PARENT peernode:DM_DM3

#CHILD  targetnode:PVDC_SILVER
#PARENT peernode:DM_DM4
#CHILD  targetnode:OVDC_JERUSALEM
#PARENT peernode:DM_DM4
#CHILD  targetnode:OVDC_MAINZ
#PARENT peernode:DM_DM4
#CHILD  hladdress:vm-DM4.com
#PARENT peernode:DM_DM4
#CHILD  lladdress:49392
#PARENT peernode:DM_DM4

#PARAM STATUS=success
#END RUN 2 20130109143749906
#END TASK 3
#INFO FMM16014I The return code is 0.
#END

The PHASE INQUIRE_PVDC_NODES section shows the provider VDC nodes with proxy access to each vCloud Director node. The format for this proxy relationship is shown in pairs:

#CHILD targetnode::<vCloud Director node name>
#PARENT peernode::<provider VDC name>

The PHASE INQUIRE_OVDC_NODES section shows the organization VDC nodes with proxy access to each provider VDC node. The format for this proxy relationship is shown in pairs:

#CHILD targetnode::<provider VDC node name>
#PARENT peernode::<organization VDC node name>

The PHASE INQUIRE_DM_NODES section shows the data mover nodes with proxy access to each provider VDC node and organization VDC node. The format for this proxy relationship is shown in pairs:

#CHILD targetnode::<provider VDC node name> OR <organization VDC node name>
#PARENT peernode::<data mover node name>