cancel
Showing results for 
Search instead for 
Did you mean: 

Syslog Error.

mansoor_sheik
Level 6
Certified

Hi all,

Got below error in master server syslog.

Symantec Authentication: Read error on /usr/openv/volmgr/misc/robotic_db/TLD0: Error(0)

can anyone suggest?

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

NBAC and second Tape Library configuration was done recently.

That would explain the message, right?

Auditing in version 7.1.x works best with OpsCenter to report on changes.

View solution in original post

5 REPLIES 5

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

looks like TLD0 robot is not having good communication with Netbackup

did you see any operationnal issues..? drvies AVR mode? Q jobs.. ? backup failures?

can you do you robtest for TLD0 from contorl host and see what its returning..?

Marianne
Level 6
Partner    VIP    Accredited Certified

You need to tell us more about the environment:

NBU version and patch level first of all.

Authentication/Authorization seems to be configured. Is this right?

The error says that someone/some system tried to access the robot config. Nothing more.

With NBU 7.0.1 and later the Auditing feature can be configured to report on changes and activitities - VERY limited reporting in NBU 7.0.1 and more in 7.1 and later. 
Auditing is covered in NBU Admin Guide I.

 

mansoor_sheik
Level 6
Certified

Hi,

Master Server: HPUX

Version:7.1.0.2

NABC:Reconfigured. Symantec team has taken webex and done the same.

The error says that someone/some system tried to access the robot config. Nothing more.---- NBAC and second Tape Library configuration was done recently.

Will read the Admin guide and update you.

Marianne
Level 6
Partner    VIP    Accredited Certified

NBAC and second Tape Library configuration was done recently.

That would explain the message, right?

Auditing in version 7.1.x works best with OpsCenter to report on changes.

mansoor_sheik
Level 6
Certified

Hi Marianne,

Thanks for your suggestion. I have closed the syslog ticket.