topic Re: Netapp Data Broker web interface connection issue in Ask The Experts

Netapp Data Broker web interface connection issue

luc_beaudoinlefort — Wed, 09 Oct 2019 19:39:51 GMT

I'm trying to connect to the web interface of my new install of Netapp DAta Broker with SnapCenter 4.2

everything is pingnig well

but I have the message "This site can’t be reached" when I put

https://data broker appliance IP:8080

any ideas ?

Re: Netapp Data Broker web interface connection issue

Ontapforrum — Wed, 09 Oct 2019 20:47:48 GMT

Could you ensure this:

1) Firewall is disabled (or Ports are allowed)
2) Both Data broker IP & Hostname resolution works from SnapCenter server.

Re: Netapp Data Broker web interface connection issue

luc_beaudoinlefort — Thu, 10 Oct 2019 18:58:53 GMT

Firewall is disabled ...

I can ping the snapcenter server ... and the NEtapp data broker appliance

I installed and configured the appliance, when I use the link that the appliance tells me to use, I got the message

if I go in Maintenance console, I have Appliance services status : not running

I can't start the service ...

any idea

Re: Netapp Data Broker web interface connection issue

Ontapforrum — Fri, 11 Oct 2019 08:56:07 GMT

I don't have access to databroker, so I can't really do much but I have few suggestions:

[On Page 26]
https://library.netapp.com/ecm/ecm_get_file/ECMLP2858035

Could you try these steps from the ,maintenance console:
1) Display NetApp Data Broker summary
2) Start or stop NetApp Data Broker service
3) Ping a host [SnapCenter]
4) Reboot

If that dosen't work, go for diags:

Support and Diagnostics:
a) Generate support bundle
b) Access diagnostic shell
c) Enable remote diagnostic access
d) Generate core dump bundle

So that anyone in the forum can take a look and guide you further.

Re: Netapp Data Broker web interface connection issue

bhenson — Wed, 16 Oct 2019 21:03:29 GMT

Same issue here. From talks with my SE buddies, this is an issue, but there aren't too many customers migrated to SC 4.2 and Data Broker, so... maybe there will be a fix (4.2.1 or 1.1)?

For t-shoot, I've gone through all the steps - disabled firewall in SC's Windows Server, checked services, checked DNS resolution, restarted Data Broker, just about everything short of a clean install. There's definitely a bug affecting some users. Let us know if you ever get it sorted out.