#BXP Classification port reqs

1 messages · Page 1 of 1 (latest)

soft spear
#

So the documentation states that from BXP Classification <> Cluster that port 443 is required.

No big deal, is this between the SVM's themselves or the Cluster vserver?

I ask because the cluster vserver and our management LIFS's are behind a firewall, the data SVM's aren't. I just need to know which I can point this bad boy at.

crystal burrow
#

Hmm... I was almost certain that 443 was only required between the connector and the cluster, not between the classification hots and the cluster. Between the connector and the cluster it's 443 on the cluster management LIF.

#

If there's a page stating Classification <> cluster over port 443 I'm happy to have the link. Maybe my memory is failing. 🙂

soft spear
#

Regardless of the port really, is it between the SVM's or the cluster itself?
I'll check the exact name in the AM 🙂

soft spear
# crystal burrow Hmm... I was almost certain that 443 was only required between the connector and...

You're right, this is what I get for typing in a hurry 🙂

What I am looking at though is this

BlueXP classification <> ONTAP cluster
    

    For NFS - 111 (TCP\UDP) and 2049 (TCP\UDP)

    For CIFS - 139 (TCP\UDP) and 445 (TCP\UDP)

    

BlueXP classification needs a network connection to each Cloud Volumes ONTAP subnet or on-prem ONTAP system. Firewalls or routing rules for Cloud Volumes ONTAP must allow inbound connections from the BlueXP classification instance.

Make sure these ports are open to the BlueXP classification instance:

    For NFS - 111 and 2049

    For CIFS - 139 and 445

NFS volume export policies must allow access from the BlueXP classification instance.
#

It lists "cluster" but gives end user protocol ports.

crystal burrow
#

That is weird. You wouldn't be able to talk NFS or CIFS over cluster mgmt. When you add shares to scan you point out the data LIF on the SVM.