- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: Installation failed. Reason: TCP connectivity ...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installation failed. Reason: TCP connectivity failure ( port = 18191 ) erro 10
Hi team
I tried to install policies on a new cluster XL on r81.20, but I encountered the following error: Installation failed. Reason: TCP connectivity failure (port = 18191), error 10. Has anyone encountered this error before?
Regars
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats SIC problem, thats why its failing. Make sure traffic is allowed/working between gateways/management back and forth and routing is correct.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How could I validate it or what commands could I use?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
[Expert@R82:0]# netstat -na | grep 18191
tcp 0 0 0.0.0.0:18191 0.0.0.0:* LISTEN
[Expert@R82:0]#
Btw, also make sure routing is there, ie like below, or replace google dns with mgmt server and MAKE SURE it does take correct path.
[Expert@R82:0]# ip r g 8.8.8.8
8.8.8.8 via 172.16.10.1 dev eth0 src 172.16.10.253
cache
[Expert@R82:0]#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, as I said, ensure both "entities" can ping one another. One way to test this is just have rule that says any any allow in the policy, because that would tell you 100% if its policy issue. OR, even better, run fw unloadlocal and see if that works, because if it does, there is your answer.
Andy
