cancel
Showing results for 
Search instead for 
Did you mean: 

Why don't SCI use tcp port 8443?

hyosang_choi
Valued Contributor
Hi.

Customer is using SCI and vSZ(above 3.5).

But thier SCI don't use 8443 port.

We can see some port using connection SCI and vSZ on document.
Image_ images_messages_5f91c3e8135b77e2478db496_68a01a497e4a30cdd9997577ad025510_RackMultipart2017090150452187k-d5d6b97f-e2e6-4d50-90d1-750c89ff3e56-2095853525.PNG1504230792

But SCI don't use 8443 in result I check it using tcpdump on SCI shell.

SCI reciecve only packets for 8883 port from vSZ.



Image_ images_messages_5f91c3e8135b77e2478db496_2405c6cfac7b1fe9ee477b3247b30c79_RackMultipart20170901171711fax-6fe27d1e-6011-42cc-b71a-4b583b506802-1789673450.png1504231247

Doesn't it use outbound-8443 port?

Is it intended?

Should we only open inbound tcp 8883 port from vSZ to SCI?

Thanks.
7 REPLIES 7

lakshmi_nagaraj
New Contributor III
Hi Jeronimo,  you are doing the right thing by adding only one vSZ. if you have more than one vSZ in a cluster, you need to add only one of them to SCI. 

Thanks
Lakshmi 

Thank you very much Lakshmi.

I got it from your reply.

Regrards.
Jeronimo

elmar_gruber
New Contributor II
Hi all, Since we first started to use SCI years back (v3) we are sometimes experiencing issues in Communication in between SCI and vSZ. Currently (again) after upgrading vSZ to 5.1, having SCI on on 5.3 SCI can't see our vSZ anymore. System-IDs are correct, IPs are correct and pingable vice-versa. There are no firewalls or anything else in between vSZs and SCI (plain L2).
Any help on this? btw. Spark Master always displays 502 Bad Gateway (which may be the reason) but nowhere there's documentation on SCI on how to fix things!
Thank You!