cancel
Showing results for 
Search instead for 
Did you mean: 

OS level and NBU admin console failed to add the device

Home_224
Level 6

Hi ,

I use the NBU 6.5 , solairs 9, configure to connect to C4 library in UAT , I can see the hardware by probe-scsi-all and cfgadm -al 

root@devuarbak01 # cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c4::rmt/0 tape connected configured unknown

root@devuarbak01 # tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path
root@devuarbak01 # ./sgscna
./sgscna: not found
root@devuarbak01 # sgscan
root@devuarbak01 # scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
root@devuarbak01 # scan -tape
************************************************************
*********************** SDT_TAPE ************************
************************************************************
root@devuarbak01 # netstat -an | grep vnetd
30002a46ab8 stream-ord 30002eecf38 00000000 /usr/openv/var/vnetd/bmrd.uds
30002a46e48 stream-ord 3000dbcac78 00000000 /usr/openv/var/vnetd/bpcompatd.uds

root@devuarbak01 # bpps -a
NB Processes
------------
root 19074 19073 0 15:33:02 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm
root 19080 19079 0 15:33:03 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
root 19069 1 0 15:33:01 ? 0:00 /usr/openv/netbackup/bin/nbpem
root 19129 19061 0 15:33:53 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 19101 1 0 15:33:25 ? 0:00 /usr/openv/netbackup/bin/bmrd
root 19109 1 0 15:33:25 ? 0:00 /usr/openv/netbackup/bin/nbsvcmon
root 19073 19066 0 15:33:02 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm
root 19090 1 0 15:33:24 ? 0:00 /usr/openv/netbackup/bin/nbsl
root 19075 19066 0 15:33:02 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm_genjob
root 19078 19077 0 15:33:03 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 19066 1 0 15:33:00 ? 0:00 /usr/openv/netbackup/bin/nbjm
root 19076 19075 0 15:33:02 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm_genjob
root 19031 1 0 15:32:54 ? 0:01 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
root 19077 19069 0 15:33:03 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem_email
root 19037 1 0 15:32:56 ? 0:00 /usr/openv/netbackup/bin/nbemm
root 19034 1 0 15:32:55 ? 0:00 /usr/openv/netbackup/bin/nbnos
root 19040 1 0 15:32:57 ? 0:00 /usr/openv/netbackup/bin/nbrb
root 19061 1 0 15:32:58 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 19079 19069 0 15:33:03 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem

MM Processes
------------

Try to use admin console >  Add device wizard  >  The message return could not connect vnet media manager, MM status = 70 

Try to restart the netbackup and reboot, it still not improvement at all.

Can you advice if there is missing step to add the device?

Thanks,

Alfred 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to fix vmd and other NBU entries that are missing from /etc/services!

You will need to reboot after re-adding the entries.

 

View solution in original post

16 REPLIES 16

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Yes. 

You need to run sg.build and sg.install as per one of your previous posts:
https://vox.veritas.com/t5/NetBackup/nbu-new-connect-to-FC-tape-library-how-to/td-p/851588

Once this is done, check that sgscan can see the devices before you config devices in NBU.
Ensure that pbx_exchange and vmd daemons are running before you start the device config wizard. 

 

Thank you Marianne reminding 

I rebuild the sg driver and sgscan to see the tape drive but i cannot see if there is robot and drive by tpconfig -l , even I restart the netbackup service. 

I try to add device by admin console but still return the previous message cannot connect vnetd MP status 70. 

Please advice 

root@devuarbak01 # scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/rmt/0cbn"
Passthru Name: "/dev/sg/c1t1l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "HP Ultrium 3-SCSI G36Z"
Vendor ID : "HP "
Product ID : "Ultrium 3-SCSI "
Product Rev: "G36Z"
Serial Number: "HU106044ER"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "/dev/sg/c1t4l0"
Passthru Name: "/dev/sg/c1t4l0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "QUANTUM PX500 0033"
Vendor ID : "QUANTUM "
Product ID : "PX500 "
Product Rev: "0033"
Serial Number: "QP0739BDC00157"
WWN : ""
WWN Id Type : 0
Device Identifier: "QUANTUM PX500 QP0739BDC00157"
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 1
Number of Slots : 38
Number of Media Access Ports: 0
Drive 1 Serial Number : "HU106044ER"
Flags : 0x0
Reason: 0x0
root@devuarbak01 # tpconfig -d
Id DriveName Type Residence
Drive Path Status
****************************************************************************

Currently defined robotics are:

EMM Server = devuarbak01

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Rebuilding sg driver will not add devices, so forget about tpconfig.

You need to add devices AFTER ensuring that pbx_exchange and vmd daemons are running (as per my previous post).

Check with bpps -x if pbx is running.
If so, you can manually start vmd.

Yes, I check the pbx already startup

root@devuarbak01 # /opt/openv/volmgr/bin/vmd
root@devuarbak01 # bpps -x
NB Processes
------------
root 286 1 0 14:41:46 ? 0:00 /usr/openv/netbackup/bin/nbrb
root 283 1 0 14:41:45 ? 0:01 /usr/openv/netbackup/bin/nbemm
root 280 1 0 14:41:42 ? 0:00 /usr/openv/netbackup/bin/nbnos
root 277 1 0 14:41:38 ? 0:03 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
root 322 313 0 14:41:56 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm
root 330 1 0 14:41:58 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem
root 313 1 0 14:41:54 ? 0:00 /usr/openv/netbackup/bin/nbjm
root 307 1 0 14:41:50 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 323 322 0 14:41:56 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm
root 324 313 0 14:41:57 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm_genjob
root 325 324 0 14:41:57 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm_genjob
root 337 1 0 14:42:17 ? 0:00 /usr/openv/netbackup/bin/nbsl
root 328 1 0 14:41:58 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem_email
root 329 328 0 14:41:58 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 331 330 0 14:41:58 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
root 356 1 0 14:42:19 ? 0:00 /usr/openv/netbackup/bin/nbsvcmon
root 348 1 0 14:42:19 ? 0:00 /usr/openv/netbackup/bin/bmrd
root 426 1 0 14:42:21 ? 0:00 /usr/openv/netbackup/bin/bmrbd
root 1507 1 0 14:42:59 ? 0:00 /usr/openv/netbackup/bin/bpcd -standalone
root 3935 307 0 15:55:07 ? 0:00 /usr/openv/netbackup/bin/bpcompatd


MM Processes
------------
root 292 1 0 14:41:48 ? 0:00 /usr/openv/volmgr/bin/ltid
root 315 292 0 14:41:54 ? 0:00 avrd -v
root 311 292 0 14:41:52 ? 0:00 tldd -v
root 3933 311 0 15:55:06 ? 0:00 tldd -v

Shared VERITAS Processes
------------------------
root 1348 1 0 14:42:54 ? 0:00 /opt/VRTSpbx/bin/pbx_exchange

image.png

I use the device wizard to add tape device, it returns this message even I start vmd daemon, 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Something is wrong here:

root 292 1 0 14:41:48 ? 0:00 /usr/openv/volmgr/bin/ltid
root 315 292 0 14:41:54 ? 0:00 avrd -v
root 311 292 0 14:41:52 ? 0:00 tldd -v
root 3933 311 0 15:55:06 ? 0:00 tldd -v

You can see that vmd is not running. 

tldd says to me that you have library-based tape drive(s) configured, but the robotic daemon (tldcd) is not running.

I can see that you tried to start vmd manually, but it dit not stay up.
Please check for errors in /var/adm/messages around the time that you issued the command. 

I suggest you do the following:

Stop ltid: 
 stopltid

Check that ALL Media manager processes terminate.
Only when ALL MM processes are gone, start ltid (which will start vmd as well): 
 ltid -v

Check which MM processes are running.

If vmd does not stay up, check /var/adm/messages for errors. 

Hi Marianne, 

I find the /var/adm /message  , daemon terminated when run vmd daemon.

root@devuarbak01 # bpps -x
NB Processes
------------
root 275 1 0 14:34:34 ? 0:01 /usr/openv/netbackup/bin/nbemm
root 278 1 0 14:34:35 ? 0:00 /usr/openv/netbackup/bin/nbrb
root 272 1 0 14:34:31 ? 0:00 /usr/openv/netbackup/bin/nbnos
root 269 1 0 14:34:27 ? 0:01 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
root 305 1 0 14:34:43 ? 0:00 /usr/openv/netbackup/bin/nbjm
root 312 1 0 14:34:45 ? 0:00 /usr/openv/netbackup/bin/nbpem
root 314 305 0 14:34:45 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm
root 418 1 0 14:35:08 ? 0:00 /usr/openv/netbackup/bin/bmrbd
root 322 312 0 14:34:47 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem
root 299 1 0 14:34:40 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 315 314 0 14:34:45 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm
root 329 1 0 14:35:05 ? 0:00 /usr/openv/netbackup/bin/nbsl
root 318 305 0 14:34:46 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbjm_genjob
root 319 318 0 14:34:46 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbjm_genjob
root 320 312 0 14:34:47 ? 0:00 sh -c "/usr/openv/netbackup/bin/nbproxy" dblib nbpem_email
root 321 320 0 14:34:47 ? 0:00 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 323 322 0 14:34:47 ? 0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
root 348 1 0 14:35:07 ? 0:00 /usr/openv/netbackup/bin/nbsvcmon
root 340 1 0 14:35:06 ? 0:00 /usr/openv/netbackup/bin/bmrd
root 1452 1 0 14:35:46 ? 0:00 /usr/openv/netbackup/bin/bpcd -standalone
root 1921 1919 0 14:39:51 ? 0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
root 2220 299 0 14:49:17 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 1923 1919 0 14:39:53 ? 0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1
root 1919 1 0 14:39:51 ? 0:00 /usr/openv/netbackup/bin/bpjava-susvc root -1 -1 C /usr/openv/java/auth.conf 1


MM Processes
------------
root 284 1 0 14:34:37 ? 0:00 /usr/openv/volmgr/bin/ltid
root 301 284 0 14:34:41 ? 0:00 tldd -v
root 306 284 0 14:34:43 ? 0:00 avrd -v


Shared VERITAS Processes
------------------------
root 1293 1 0 14:35:41 ? 0:00 /opt/VRTSpbx/bin/pbx_exchange

Jul 19 14:51:02 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 14:51:02 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 14:52:22 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 14:53:20 devuarbak01 tldd[2426]: [ID 998793 daemon.error] TLD(0) [2426] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 14:53:20 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 14:53:20 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 14:54:28 devuarbak01 vmd[2484]: [ID 625030 daemon.error] unable to obtain bound socket, no port number available for vmd (0)
Jul 19 14:54:28 devuarbak01 vmd[2484]: [ID 423164 daemon.error] terminating - daemon cannot obtain socket (58)
Jul 19 14:54:28 devuarbak01 vmd[2484]: [ID 715111 daemon.error] volume daemon terminating because it received a signal (15)
Jul 19 14:54:28 devuarbak01 vmd[2484]: [ID 164182 daemon.error] terminating - daemon terminated (7)
^Croot@devuarbak01 #

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Could you please copy messages file to messages.txt and upload here?
Nothing is going to work without vmd.
You really need to find the reason!

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Did you see this?

unable to obtain bound socket, no port number available for vmd

You will need to find out what else is using port 13701.

Also check /etc/services if all NBU entries are there. vmd entry looks like this:

vmd          13701/tcp 

Has anyone changed anything at OS-level?
For NBU 6.x, it is NOT normal for bpcd to run in standalone mode.
If the default entries in inet.d.conf were removed, then vnetd should also run in standalone mode.

I check the bpcd not to comment but run in standalone services.

root@devuarbak01 # cat /etc/services

#ident "@(#)services 1.32 01/11/21 SMI"
#
#
# Copyright (c) 1999-2001 by Sun Microsystems, Inc.
# All rights reserved.
#
# Network services, Internet style
#
tcpmux 1/tcp
echo 7/tcp
echo 7/udp
discard 9/tcp sink null
discard 9/udp sink null
systat 11/tcp users
daytime 13/tcp
daytime 13/udp
netstat 15/tcp
chargen 19/tcp ttytst source
chargen 19/udp ttytst source
ftp-data 20/tcp
ftp 21/tcp
ssh 22/tcp # Secure Shell
telnet 23/tcp
smtp 25/tcp mail
time 37/tcp timserver
time 37/udp timserver
name 42/udp nameserver
whois 43/tcp nicname # usually to sri-nic
domain 53/udp
domain 53/tcp
bootps 67/udp # BOOTP/DHCP server
bootpc 68/udp # BOOTP/DHCP client
kerberos 88/udp kdc # Kerberos V5 KDC
kerberos 88/tcp kdc # Kerberos V5 KDC
hostnames 101/tcp hostname # usually to sri-nic
pop2 109/tcp pop-2 # Post Office Protocol - V2
pop3 110/tcp # Post Office Protocol - Version 3
sunrpc 111/udp rpcbind
sunrpc 111/tcp rpcbind
imap 143/tcp imap2 # Internet Mail Access Protocol v2
ldap 389/tcp # Lightweight Directory Access Protocol
ldap 389/udp # Lightweight Directory Access Protocol
submission 587/tcp # Mail Message Submission
submission 587/udp # see RFC 2476
ldaps 636/tcp # LDAP protocol over TLS/SSL (was sldap)
ldaps 636/udp # LDAP protocol over TLS/SSL (was sldap)
#
# Host specific functions
#
tftp 69/udp
rje 77/tcp
finger 79/tcp
link 87/tcp ttylink
supdup 95/tcp
iso-tsap 102/tcp
x400 103/tcp # ISO Mail
x400-snd 104/tcp
csnet-ns 105/tcp
pop-2 109/tcp # Post Office
uucp-path 117/tcp
nntp 119/tcp usenet # Network News Transfer
ntp 123/tcp # Network Time Protocol
ntp 123/udp # Network Time Protocol
netbios-ns 137/tcp # NETBIOS Name Service
netbios-ns 137/udp # NETBIOS Name Service
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp # NETBIOS Datagram Service
netbios-ssn 139/tcp # NETBIOS Session Service
netbios-ssn 139/udp # NETBIOS Session Service
NeWS 144/tcp news # Window System
slp 427/tcp slp # Service Location Protocol, V2
slp 427/udp slp # Service Location Protocol, V2
mobile-ip 434/udp mobile-ip # Mobile-IP
cvc_hostd 442/tcp # Network Console
ike 500/udp ike # Internet Key Exchange
uuidgen 697/tcp # UUID Generator
uuidgen 697/udp # UUID Generator
#
# UNIX specific services
#
# these are NOT officially assigned
#
exec 512/tcp
login 513/tcp
shell 514/tcp cmd # no passwords used
printer 515/tcp spooler # line printer spooler
courier 530/tcp rpc # experimental
uucp 540/tcp uucpd # uucp daemon
biff 512/udp comsat
who 513/udp whod
syslog 514/udp
talk 517/udp
route 520/udp router routed
ripng 521/udp
klogin 543/tcp # Kerberos authenticated rlogin
kshell 544/tcp cmd # Kerberos authenticated remote shell
new-rwho 550/udp new-who # experimental
rmonitor 560/udp rmonitord # experimental
monitor 561/udp # experimental
pcserver 600/tcp # ECD Integrated PC board srvr
sun-dr 665/tcp # Remote Dynamic Reconfiguration
kerberos-adm 749/tcp # Kerberos V5 Administration
kerberos-adm 749/udp # Kerberos V5 Administration
kerberos-iv 750/udp # Kerberos V4 key server
krb5_prop 754/tcp # Kerberos V5 KDC propogation
ufsd 1008/tcp ufsd # UFS-aware server
ufsd 1008/udp ufsd
cvc 1495/tcp # Network Console
ingreslock 1524/tcp
www-ldap-gw 1760/tcp # HTTP to LDAP gateway
www-ldap-gw 1760/udp # HTTP to LDAP gateway
listen 2766/tcp # System V listener port
nfsd 2049/udp nfs # NFS server daemon (clts)
nfsd 2049/tcp nfs # NFS server daemon (cots)
eklogin 2105/tcp # Kerberos encrypted rlogin
lockd 4045/udp # NFS lock daemon/manager
lockd 4045/tcp
dtspc 6112/tcp # CDE subprocess control
fs 7100/tcp # Font server
root@devuarbak01 #

/usr/openv/netbackup/bin/bpcd -standalone

more /etc/inetd.conf | grep bpcd
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd

more /etc/inetd.conf | grep vnetd

cd /var/adm/messages 

Jul 19 15:57:18 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 15:57:18 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 15:58:14 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 15:59:35 devuarbak01 tldd[4933]: [ID 547871 daemon.error] TLD(0) [4933] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 15:59:35 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 15:59:35 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:01:52 devuarbak01 tldd[4987]: [ID 511424 daemon.error] TLD(0) [4987] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:01:52 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:01:52 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:03:18 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 16:04:09 devuarbak01 tldd[5039]: [ID 884812 daemon.error] TLD(0) [5039] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:04:09 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:04:09 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:06:26 devuarbak01 tldd[5093]: [ID 245572 daemon.error] TLD(0) [5093] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:06:26 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:06:26 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:08:22 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 16:08:43 devuarbak01 tldd[5159]: [ID 314789 daemon.error] TLD(0) [5159] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:08:43 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:08:43 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:11:00 devuarbak01 tldd[5207]: [ID 894274 daemon.error] TLD(0) [5207] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:11:00 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:11:00 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:13:18 devuarbak01 tldd[5261]: [ID 255034 daemon.error] TLD(0) [5261] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:13:18 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:13:18 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:13:26 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 16:15:35 devuarbak01 tldd[5329]: [ID 834521 daemon.error] TLD(0) [5329] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:15:35 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:15:35 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:17:52 devuarbak01 tldd[5383]: [ID 195281 daemon.error] TLD(0) [5383] unable to connect to tldcd on devuarbak01: cannot connect to robotic software daemon (42)
Jul 19 16:17:52 devuarbak01 tldd[301]: [ID 560769 daemon.notice] DecodeQuery() Actual status: Control daemon connect or protocol error
Jul 19 16:17:52 devuarbak01 tldd[301]: [ID 181918 daemon.error] TLD(0) unavailable: initialization failed: Control daemon connect or protocol error
Jul 19 16:18:30 devuarbak01 ntpdate[205]: [ID 398266 daemon.notice] waiting 300 seconds before trying again
Jul 19 16:20:09 devuarbak01 tldd[5431]: [ID 774766 daemon.error] TLD(0) [5431] unable to connect to tldcd on devuarbak01: cannot connect to robotic software

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to find out why all the NBU entries were deleted from /etc/services.

I do not have any 6.x manuals anymore, but managed to find this Windows TN. The services entries for Solaris/Unix look the same: https://www.veritas.com/support/en_US/article.000016292

The NBU entries in /etc/inetd.conf can be found here: https://www.veritas.com/support/en_US/article.000036629

Only from NBU7.x are these entries no longer in services and inetd.conf.

If OS hardening is done, vnetd must also be started in standalone mode. 

I check the port is LISTEN

root@devuarbak01 # netstat -an | grep 13782
*.13782 *.* 0 0 49152 0 LISTEN
root@devuarbak01 # netstat -an | grep 13724
*.13724 *.* 0 0 49152 0 LISTEN
127.0.0.1.33153 127.0.0.1.13724 49152 0 49152 0 TIME_WAIT
10.26.174.22.33155 10.26.174.22.13724 49152 0 49152 0 TIME_WAIT
127.0.0.1.33165 127.0.0.1.13724 49152 0 49152 0 TIME_WAIT
127.0.0.1.33171 127.0.0.1.13724 49152 0 49152 0 TIME_WAIT

bpcd and vmd daemon on the /etc/inetd.conf, but no services startup /etc/services 

Thank you Marianne, I take a look from your document 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to fix vmd and other NBU entries that are missing from /etc/services!

You will need to reboot after re-adding the entries.

 

Thank you Marianne ! 

I add all the daemon in /etc/services, then restart the netbackup service. I can add the device right now.

Btw, I would like to know if the NBU can use the FC library and SCSI at the same time.  As the end users upgrade the tape encryption library, now the production running the backup, but he wants to the nbu can still use the old scsi library as well.  I afraid of the scsi drive or fc drive will be removed when I rebuild all.   Can you advice this ?

 

Thank you