Enable Live Connect for Context Hub

[DesmondKwang]

Update:

To enable Live Connect for Context Hub, ensure that ESA (host) has Internet connection. Although Live Connect uses the same configuration as Live account in Live Services, the two connections are different. Live Services connects to cms.netwitness.com via SA (head unit), and Live Connect connects to cms.netwitness.com via ESA. Hence, you might encounter Live account in Live Services is connected but not Live Connect.

Subsequently, also need to ensure that Threat Insights is connected.

Additional resources:

Context Hub: Configure Live Connect Data Source 

[SeanLim]

For Live Services, the connection is between the Analytics Server (Head Unit) and cms.netwitness.com:443. Since this is showing as green and connected, this is working as expected. 

For Live Connect, the connection is between the Context Hub (on the ESA) and cms.netwitness.com:443. Since the test connection failed, I would suspect a connectivity issue here between the ESA appliance and cms.netwitness.com.

[DesmondKwang]

Agreed with you, was narrowing down to connectivity between ESA and Internet.

I got it working in my test environment. ESA was not connected to Internet initially. When I connected ESA to the Internet, Threat Insights was connected and Live Connect in Context Hub also showed connected. 

Thanks Sean.