cancel
Showing results for 
Search instead for 
Did you mean: 

RDSM has encountered an STS error: getStorageServerConfig

perez_cmz
Level 6

Configuring media server deduplication pool media3-authentication failed (160)

This is my first attempt at creating an MSDP, and this message appears at the end during the config status window.

16 REPLIES 16

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Please share all the steps that you have followed.
We can only try to assist if we have insight into what you have done.

We've setup a new media server for this, and it appears under Host Properties - Media Servers.

I'm using the "Configure Disk Storage Servers" wizard to setup MSDP. I receive this message at the very end of wizard.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Is that all that you have done?
What about setting up storage on the media server and verifying the mount point and folders for data and db? And correct license keys on media server?

What exactly did you type in at each of the wizard prompts?

Storage, mount points and folders have been setup. I've been told I have the right licenses.

Tape_Archived
Moderator
Moderator
   VIP   

This looks like communication issue, can you please check if there is correct connectivity between master and MSDP media server?? Please run basic connectivity commands and ensure proper communication and also check if all the required ports are open.

Not very familiar with Linux, what would be some connectivity commands and ports I can check ?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

'Basic connectivity commands' are the same for all OS's. 

Try to ping the hostname in both directions.
If that works, then try bpclntcmd and bptestbpcd commands.

bpclntcmd:
On master and media server:
bpclntcmd -hn <other-server-name>
bpclntcmd -ip <other-server-IP>

If all of this rrespond with expected output, then run bptestbpcd on the master: 

bptestbpcd -client <media-server-name> -debug -verbose

PS:
Linux has an OS firewall (iptables) that needs to be stopped and disabled.

bpclntcmd output seemed normal

# bptestbpcd -client mediaserver03.domain.com -debug -verbose
15:05:42.905 [21284] <2> bptestbpcd: VERBOSE = 0
15:05:43.084 [21284] <2> vnet_pbxConnect: pbxConnectEx Succeeded
15:05:43.084 [21284] <2> logconnections: BPCD CONNECT FROM 999.28.72.175.51007 TO 777.72.188.50.1556 fd = 3
15:05:43.261 [21284] <2> vnet_pbxConnect: pbxConnectEx Succeeded
15:05:43.349 [21284] <8> do_pbx_service: [vnet_connect.c:2227] via PBX VNETD CONNECT FROM 444.28.72.175.49868 TO 777.72.188.50.1556 fd = 4
15:05:43.349 [21284] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:440] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
15:05:43.564 [21284] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:457] ipc_string /usr/openv/var/tmp/vnet-51538529586343523149000000193-FAw3QH
15:05:43.998 [21284] <2> bpcr_get_version_rqst: bpcd version: 07720000
1 1 1
444.28.72.175:51007 -> 777.72.188.50:1556
444.28.72.175:49868 -> 777.72.188.50:1556
15:05:44.095 [21284] <2> bpcr_get_peername_rqst: Server peername length = 28
15:05:44.271 [21284] <2> bpcr_get_hostname_rqst: Server hostname length = 31
15:05:44.446 [21284] <2> bpcr_get_clientname_rqst: Server clientname length = 31
15:05:44.621 [21284] <2> bpcr_get_version_rqst: bpcd version: 07720000
15:05:44.708 [21284] <2> bpcr_get_platform_rqst: Server platform length = 17
15:05:44.894 [21284] <2> bpcr_get_version_rqst: bpcd version: 07720000
15:05:45.074 [21284] <2> bpcr_patch_version_rqst: theRest == > <
15:05:45.162 [21284] <2> bpcr_get_version_rqst: bpcd version: 07720000
15:05:45.376 [21284] <2> bpcr_patch_version_rqst: theRest == > <
15:05:45.464 [21284] <2> bpcr_get_version_rqst: bpcd version: 07720000
PEER_NAME = master.domain.com
HOST_NAME = mediaserver03.domain.com
CLIENT_NAME = mediaserver03.domain.com
VERSION = 0x07720000
PLATFORM = linuxR_x86_2.6.18
PATCH_VERSION = 7.7.2.0
SERVER_PATCH_VERSION = 7.7.2.0
MASTER_SERVER = master.domain.com
EMM_SERVER = master.domain.com
NB_MACHINE_TYPE = MEDIA_SERVER
15:05:45.825 [21284] <2> vnet_pbxConnect: pbxConnectEx Succeeded
15:05:45.913 [21284] <8> do_pbx_service: [vnet_connect.c:2227] via PBX VNETD CONNECT FROM 444.28.72.175.39911 TO 777.72.188.50.1556 fd = 5
15:05:45.913 [21284] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:440] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
15:05:46.128 [21284] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:457] ipc_string /usr/openv/var/tmp/vnet-51669529586346088026000000193-ZYhm8O
444.28.72.175:39911 -> 777.72.188.50:1556
<2>bptestbpcd: EXIT status = 0
15:05:46.431 [21284] <2> bptestbpcd: EXIT status = 0

Tape_Archived
Moderator
Moderator
   VIP   

Also, please prove log set when you try to configure from /usr/openv/volmgr/debug/tpcommand and nbstserv ( after extracting unified vxlogs). Also you may look into bptm logs on the media server you are trying to configure.

What is the exact tpcommand and nbsterv commands I shoudl run ?

Tape_Archived
Moderator
Moderator
   VIP   

These are not commands, I meant to say "logs". You will have find these logs and check for the error message. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@perez_cmz

Your paths for storage and database seem to be incorrect - the entries in /dev/mapper are LVM logical volumes.  You need to specify the mount point(s). 

One more thing: Looking at bptestbpcd output: 

PEER_NAME = svxxx17.domain.com
HOST_NAME = mediaserver03.domain.com
CLIENT_NAME = mediaserver03.domain.com

MASTER_SERVER = master.domain.com
EMM_SERVER = master.domain.com
NB_MACHINE_TYPE = MEDIA_SERVER

It seems that you ran bptestbpcd from this machine: svxxx17

Could you please repeat the command from the master server ? 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@perez_cmz

Have you retried the MSDP config with mount points instead of the /dev/mapper LVM paths?

I had to run some cleanup commands on the master server to remove mentions of the media server being used for MSDP.

After running these commands, I reran the wizard successfully

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Was it successful when you used mount points instead of LVM volume paths?

I used /msdp/msdpdata and /msdp/msdpcatalog