Last for 4 days, i’m still have facing problem for install media agent at linux client (rhel 7.9), where the process installation at half process and stuck at “ Firewall Configuration “
“The server computer is not reachable. Please check the network and the firewall”
Info:
Commserv :V11sp20 FR55. (Windows 2019)
Client (rhel 7.9)
Telnet from Commserve to Client (Success)
Telnet from Client to Commserve (Success)
Ping both of them, status reply.
Any one can help me?
Regards
Nilles
Best answer by Mike Struening RETIRED
Found the case and resolution:
--> Customer has reported that there are multiple failed attempts in the archive index phase of the job ID 186. --> Reviewed the logs for Job 186 and could see there are timed-out errors while connecting to Commserve. --> Due to this, we could see multiple failed attempts in the archive index phase "CCVAPipelayer::StartPipeline() - Failed to initiate pipeline".
Solution:
--> Created a one-way firewall between the MA and Commserve. --> This one-way firewall will create a persistent tunnel between the CS and the MA. --> One-way tunnels are persistent tunnels that send a keepalive packet every 5 minutes so that the connection is never terminated. --> New backup job was kicked off and it got completed successfully, customer confirmed to close the case.
I can see the log states that the nchatterflag is set to 1. If the nChatterFlag additional setting is set to 1, normal Communication and Connection testing will work properly but communication between MediaAgent or Client and the CommServe will continue to fail.
There is most likely a reason why this was set but this set to 1 will cause you issues.
You can change the flag in additional settings.
It is recommended to stop Commvault services on the MediaAgent(s) and/or Client(s) before modifying additional settings.
Check the nChatterFlag additional setting.
From the CommCell Browser, navigate to Client Computers.
Right-click the <Client> or MediaAgent, and then click Properties.
Click Advanced and then click Additional Settings tab.
Click Add.
In the Name box, type nChatterFlag.
The Category and Type fields are populated automatically.
I can see the log states that the nchatterflag is set to 1. If the nChatterFlag additional setting is set to 1, normal Communication and Connection testing will work properly but communication between MediaAgent or Client and the CommServe will continue to fail.
There is most likely a reason why this was set but this set to 1 will cause you issues.
You can change the flag in additional settings.
It is recommended to stop Commvault services on the MediaAgent(s) and/or Client(s) before modifying additional settings.
Check the nChatterFlag additional setting.
From the CommCell Browser, navigate to Client Computers.
Right-click the <Client> or MediaAgent, and then click Properties.
Click Advanced and then click Additional Settings tab.
Click Add.
In the Name box, type nChatterFlag.
The Category and Type fields are populated automatically.
In the Value box, type 0.
This enables communication to the CommServe.
Click OK.
Restart Commvault services.
Hi Sir,
Sorry for late give feedback, i’m done for add nChatterFlag additional setting at Commserver(after change, restart services) and the result still same at linux client.
seems there is a communication issue there and something is stopping the traffic somewhere.
We would need more logs to investigate, client logs, CS logs and wireshark trace from Commserve and network trace from this linux machine.
If you could raise a ticket with all of the above we can help further. Please also pop the ticket number here so it can be tracked and we can then update this thread witht he answer.
--> Customer has reported that there are multiple failed attempts in the archive index phase of the job ID 186. --> Reviewed the logs for Job 186 and could see there are timed-out errors while connecting to Commserve. --> Due to this, we could see multiple failed attempts in the archive index phase "CCVAPipelayer::StartPipeline() - Failed to initiate pipeline".
Solution:
--> Created a one-way firewall between the MA and Commserve. --> This one-way firewall will create a persistent tunnel between the CS and the MA. --> One-way tunnels are persistent tunnels that send a keepalive packet every 5 minutes so that the connection is never terminated. --> New backup job was kicked off and it got completed successfully, customer confirmed to close the case.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.