!-->
Hello,
I’m playing around backup Azure VMs to on-prem Commvault. I setup all Azure stuff: create application, assign custom roles etc. So next step is configure access node.
I deployed Commvault Cloud BYOL Access Node VM as described here: https://documentation.commvault.com/11.40/software/deploying_commvault_cloud_access_node_from_azure_marketplace.html (selected 11.36 as there is no 11.40 version on Azure).
In Azure I setup network rules to open incoming connections on 22 and 8400-8403 ports from my on-premise public IP. Checked network connectivity from Commserve (telnet) on this ports - it's ok.
So according to documentation next step is register node by commvaultRegistration.sh script.
Entered values:
- client name: whatever
- client hostname: public IP of the Azure VM
- CS Name: commserve
- CS hostname: local IP of commserve
- Is CS behind firewall: yes - option 2 (CS can connect to client)
- Port number: 8403
- HTTP proxy? no
And here are first problems. Script is not finishing, it's just stay on "executing given operation":
Do you wish to proceed with registration using the above information? (yes/no)yes
cat: /sys/class/net/: Is a directory
cat: eth0/address: No such file or directory
cat: /etc/sysconfig/network-scripts/ifcfg-: No such file or directory
cat: eth0: No such file or directory
mv: target 'eth0' is not a directory
Configured of network interfaces...
Redirecting to /bin/systemctl restart network.service
Failed to restart network.service: Unit network.service not found.
Restarted networking services ...
error reading information on service yum-cron: No such file or directory
Redirecting to /bin/systemctl start yum-cron.service
Failed to start yum-cron.service: Unit yum-cron.service not found.
Redirecting stopping service for Instance001 to systemd ...
Running "systemctl stop commvault.Instance001.service" ...
Stopping Commvault services for Instance001 ...
Cleaning up /var/log/commvault/Log_Files/locks ...
All services stopped.
check if cvfwd(sa) is running..
root 11802 11027 0 14:41 pts/0 00:00:00 grep cvfwd
Executing given operation...
No output was generated
SimCallWrapper failed. Please check SimCallWrapper.log under Simpana Log Files. Error [2]And that's all - script is in some loop, nothing more happened. So checked the SimCallWraper log but don't know what is the problem - there are only some generic errors like:
- SIM Call ProcessClientSetupRequest failed with error = -1
- No output was generated
- SimCallWrapper failed. Error [2]
I tried to finish installation from Commserve side (like in documentation) but with no luck.
Just for mention, commserve just have local IP, of course it's not public so Azure VM cannot reach it. But as far as I know, it's not a problem because Commserve can reach Azure VM and I can setup one-way network topology (but how since I don't have the client registered yet).
How can I register Azure Access Node in on-prem Commvault then?
I tried to create pseudoclient, then apply one-way network configuration and install software but it doesn't work. I tried with 11.42 node from Marketplace, but it seems like registration script is bugged there, it stops just after last anserw and in logs there is info about empty credentials (which was of course not true).
I discovered that the only way I managed to register/install client was just deploy 11.36 Access node (even without commvaultRegistration.sh script), creating pseudoclient in CommCell console, provide public IP, check "Fetch configuration information from the client that is already in cecoupled mode" and provide 8400 port. Then configure network topology, update client etc. It was successful but it seems rather like a workaround than official way described in the documentation.
Any thoughts?
