Good Day everyone,
we’re operating a remote location with a Windows-Server as a network-Gateway between Clients that have no connectivity to CS and Commserver. (Not the OVA)
All Clients (Windows Servers) are installed decoupled with just the Windows Core Agent.
Remote Customers clicked a powershell on 50 different Servers that were installed like this:
& C:\temp\CVtemp\Setup.exe /silent /install
and they registered also via the script:
$name = (hostname).tolower()
& 'C:\Program Files\Commvault\ContentStore\Base\SIMCallWrapper.exe' -optype 1000 -cshost CSFQDN -clientname $name -Connectioninfo PROXYFQDN:8403 -user 'clientregister' -password 'PASSWORD' -ClientGroup 'REMOTELOCATION_22'
Then the Fileagent was pushed automatically seconds after register (never seen this before as well) via commcell console...
Out of the blue the whole registration stopped working and I see this in the simmcallwrapper log on the clients behind the gateway:
13244 99c 11/27 12:08:15 ### XML Response :<?xml version="1.0" encoding="UTF-8" standalone="no" ?><CVInstallManager_ClientSetup><SimError ErrorCode="67109051" ErrorString="Backup infrastructure is currently unavailable. Please try later. If problem persists, contact your administrator." errorLevel="2"/></CVInstallManager_ClientSetup>
When executing the above SimcallWrapper.exe, I see in netstat that the registerclient has an established connection to Proxy and also does (after timeout?) a SYN_SENT to Commserver.
However, I’d like to ask first: am I right, that the -connectioninfo is the thing to use, if the client has no connectivity to the commserv itself and it will register itself via the proxy?
Since I have no clue why this stopped out of the blue - does anybody have any suggestions?
Best regards and thanks for help