Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/HTTPS_connections_to_an_ONTAP_LIF_are_not_possible_though_HTTP_works
      Applies to ONTAP 9 HTTPS services not reachable Issue HTTP (TCP port 80) access to an ONTAP LIF works, but HTTPS (TCP port 443) is not listening / rejects a connection attempt with a TCP reset
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Varonis_is_not_able_to_enumerate_shares
      Applies to ONTAP 9.5 and later Varonis Filewalk Issue During attempt to Filewalk Varonis fails to enumerate shares when the LIF it is accessing does not allow CIFS and management access
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_shares_inaccessible_no_route_to_host_and_secd_dns_srv_lookup_failed
      [netapp01-01: secd: secd.dns.srv.lookup.failed:error]: DNS server failed to look up service(_ldap._tcp.dc._msdcs.netapp.com) for vserver (netapp-cifs01) with error (Connection refused). [     6] Faile...[netapp01-01: secd: secd.dns.srv.lookup.failed:error]: DNS server failed to look up service(_ldap._tcp.dc._msdcs.netapp.com) for vserver (netapp-cifs01) with error (Connection refused). [     6] Failed to connect to 10.10.10.10 for DNS via Source Address 10.10.10.165: No route to host [     6] Failed to connect to 10.10.10.20 for DNS via Source Address 10.10.10.165: No route to host [     6] Failed to connect to 10.10.10.30 for DNS via Source Address 10.10.10.165: No route to host
    • https://kb.netapp.com/Cloud/Astra/Trident/Trident_connection_refused_when_trying_to_create_backend
      Applies to Trident Connection refused when creating a backend from tridentctl. # tridentctl create backend -f sample.json -n ecs-trident Error: could not create backend: problem initializing storage d...Applies to Trident Connection refused when creating a backend from tridentctl. # tridentctl create backend -f sample.json -n ecs-trident Error: could not create backend: problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver: could not create Data ONTAP API client: error reading SVM details: Post "https://<IP_ADDR>/servlets/netapp.servlets.admin.XMLrequest_filer": dial tcp <IP_ADDR>:443: connect: connection refused (400 Bad Request)
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_is_the_relation_between_firewall_policy_and_service-policy
      In ONTAP, firewall settings contain rules which limit what service ports can be contacted, and from which client IP addresses they may be contacted Firewall policies are used to control which LIFs can...In ONTAP, firewall settings contain rules which limit what service ports can be contacted, and from which client IP addresses they may be contacted Firewall policies are used to control which LIFs can be used for HTTP, Telnet, NDMP, NDMPS, RSH, DNS, and SNMP access Starting with ONTAP 9.6, you can assign service policies, instead of LIF roles, to LIFs that determine the kind of traffic that is supported for the LIFs
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_Detect_Resource_Type_from_Varonis_DatAdvantage_with_ONTAP_9_6_or_higher
      Applies to Varonis Fpolicy vendor ONTAP 9.6 and higher Issue When adding a file server (SVM) to the list of monitored resources in Varonis DatAdvantage software, the "Detect resource type" step fails ...Applies to Varonis Fpolicy vendor ONTAP 9.6 and higher Issue When adding a file server (SVM) to the list of monitored resources in Varonis DatAdvantage software, the "Detect resource type" step fails and/or displays Windows 2000 server. When clicking "Detect resource type", the software sends a ZAPI call over HTTPS to the LIF specified in the "Resource/Server Name" to retrieve the ONTAP platform, version, and Vserver UUID.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/CIFS_share_inaccessible_due_to_missing_network_interface_service-policy_entries
      CIFS share is inaccessible ::> network ping -vserver svm1 -lif lif1 -destination 10.10.10.1 DNS server check shows DNS server is down, unable to contact DNS server ::> vserver services dns check -vser...CIFS share is inaccessible ::> network ping -vserver svm1 -lif lif1 -destination 10.10.10.1 DNS server check shows DNS server is down, unable to contact DNS server ::> vserver services dns check -vserver svm1 -name-server * Vserver Name Server Status Status Details svm1 10.10.10.1 down Unable to contact DNS The network interface service policy shows below ::> network interface show -vserver svm1 -lif lif1 -fields service-policy,services,vserver,lif vserver lif service-policy services