cancel
Showing results for 
Search instead for 
Did you mean: 

The SSO config failed on the media server itself

1) We could confirm that the SSO license was added successfully on the media server zzapp2 via bpminlicense.
2) But we repeatly failed to either tpautoconf or manually tpconfig with the SSO TD & Robot on the media server.
3) Finally we had to run Device Config Wizard successfully with the media server zzapp2 on the master server zzms.

So how to explain such SSO configuration phenomenon ?

license type = 1 Permanent
Site ID = 2010 Unknown site: 2010
Feature ID = 30 Shared Storage Option +
XXXX-YYYY-JJJJ-ZZZZ-CRPP-PPPP-KKKK-CPPR-PPPP-X KRXT-WLHK-JI8R-36C8-CRPP-P3JP-K4OZ-CPPR-PPPP-X
file version = 0x05000000
time added = 0x5f97ffa9 10/27/20 19:08:25
hostname = ZZAPP2
product ID = 7 NetBackup Enterprise Server
serial number = 50766
key version = 0x05000000
count = 0
server platform = 0 Any platform
client platform = 0 Any platform
server tier = 10 NetBackup Enterprise Server
client tier = 0 No tier
license type = 1 Permanent

c:\>
c:\>
c:\>tpautoconf -a
TPAC60 - - - -1~-1~-1~-1 2 - - - 0 - - - - - - - 0 0 - - zzapp2 4 - - 0 - - - -

c:\>
c:\>
c:\>tpautoconf -t
TPAC60 HP Ultrium 5-SCSI Y65W HUJ419093P 7 0 5 0 Tape0 - -

c:\>
c:\>tpconfig -l
Device Robot Drive Robot Drive Device
Type Num Index Type DrNum Status Comment Name Path
robot 0 - TLD - - - - zzms.hddj.com

c:\>
c:\>tpconfig -add -drive -type hcart2 -port 7 -bus 0 -target 5 -lun 0 -index 0 -robot 0 -robtype TLD -robdrnum 1
failed adding drive index 0 of type hcart2 to configuration
Cannot add drive: Shared Storage Option (SSO) is Not licensed

 

 

c:\>
c:\>
c:\>
c:\>tpconfig -l
Device Robot Drive Robot Drive Device
Type Num Index Type DrNum Status Comment Name Path
robot 0 - TLD - - - - zzms.hddj.com
drive - 0 hcart2 1 UP - HP.ULTRIUM5-SCSI.000 {7,0,5,0}

c:\>
c:\>

Tags (2)
9 Replies

Re: The SSO config failed on the media server itself

Did you restart NBU after adding the license? 

Re: The SSO config failed on the media server itself

Surely,  had restarted many times!

Re: The SSO config failed on the media server itself

It's been too long since I dealt with the particularities of individual license keys but I'm betting the issue is going to be the key either not being installed in the right location, or not being installed in ALL of the right locations. It looks like the robot is defined on your Master and the SSO key is installed on your Media Server. What other Media Server will be sharing the drive with zzapp2 ? Does that Media Server already have the key installed as well, and had its daemons/services cycled ?

Re: The SSO config failed on the media server itself

Did you install the same license on all servers that have access to the shared drive?

Re: The SSO config failed on the media server itself

Yes,  but all other media servers do not  have  such  problem !

And also  the  master server  zzms is the  RCH with this robot & TD.

Re: The SSO config failed on the media server itself

Always best to run Device Config on the master server - this is where EMM db needs to be updated.
The master will connect to the media server, check for devices and licenses, and then update the config on the master.

I have used this command on the master server with success:

vmoprcmd -h <media server name> -timeout 3600 -autoconfig -a

Just for the record - all of these licenses must be added on the media server:
Enterprise server (or Ent Client if SAN media server)
Library based tape drive
Shared Storage Otion

Re: The SSO config failed on the media server itself

Finally,  we unintentionally found the cue of the problem,  but might still not be the root cause.
That is, the SSO Lic for zzapp2 should be "wrong" or conflict with the same LBTD Lic for zzapp1 !
Thus, how the misplaced license phenomenon would happen 。。。?

 

zzapp2:
Feature ID = 30 Shared Storage Option +
RRRT-7777-8888-9999-AAAA-BBBB-CCCC-DDDD-W

 

zzapp1:
Feature ID = 49 Library Based Tape Drives +
RRRT-7777-8888-9999-AAAA-BBBB-CCCC-DDDD-W

Re: The SSO config failed on the media server itself

Really you did share your license key? Please remove it...

Re: The SSO config failed on the media server itself

@liuyl 

Any issues with license keys can only be resolved by Veritas Customer Care.