LIFs and service policies in ONTAP 9.6 and later

Contributors

You can assign service policies (instead of LIF roles) to LIFs that determine the kind of traffic that is supported for the LIFs. Service policies define a collection of network services supported by a LIF. ONTAP provides a set of built-in service policies that can be associated with a LIF.

You can display service policies and their details using the following command:
network interface service-policy show

Service policies for system SVMs

The admin SVM and any system SVM contain service policies that can be used for LIFs in that SVM, including management and intercluster LIFs. These policies are automatically created by the system when an IPspace is created.

The following table lists the built-in policies for LIFs in system SVMs as of ONTAP 9.10.1. For other releases, display the service policies and their details using the following command:

network interface service-policy show

Policy

Included services

Equivalent role

Description

default-intercluster

intercluster-core, management-https

intercluster

Used by LIFs carrying intercluster traffic.
Note: Service intercluster-core is available from ONTAP 9.5 with the name net-intercluster service policy.

default-route-announce

management-bgp

-

Used by LIFs carrying BGP peer connections
Note: Available from ONTAP 9.5 with the name net-route-announce service policy.

default-management

management-core, management-https, management-http, management-ssh management-autosupport, management-ems, management-ntp-client, management-snmp-server, management-ntp-server, backup-ndmp-control

node-mgmt, or cluster-mgmt

Used by LIFs handling system-scoped management requests. Management-ems controls which LIFs can publish EMS content.
The system-scoped management policy is used to create node-scoped and cluster-scoped management LIFs owned by a system SVM. These LIFs can be used for outbound connections to NTP or DNS servers as well as some additional connections to support applications run on behalf of the entire system.

The following table lists the services that LIFs can use on a system SVM as of ONTAP 9.10.1:

Service

Failover limitations

Description

intercluster-core

home-node-only

Core intercluster services

management-core

-

Core management services

management-ssh

-

Services for SSH management access

management-http

-

Services for HTTP management access

management-https

-

Services for HTTPS management access

management-autosupport

-

Services related to posting AutoSupport payloads

management-bgp

home-port-only

Services related to BGP peer interactions

backup-ndmp-control

-

Services for NDMP backup controls

management-ems

-

Services for management messaging access

management-ntp-client

-

Services for NTP client access.

management-ntp-server

system-only

Services for NTP server management access

management-portmap

-

Services for portmap management

management-rsh-server

system-only

Services for rsh server management

management-snmp-server

-

Services for SNMP server management

management-telnet-server

system-only

Services for telnet server management

Service policies for data SVMs

All data SVMs contain service policies that can be used by LIFs in that SVM.

The following table lists the built-in policies for LIFs in data SVMs as of ONTAP 9.10.1. For other releases, display the service policies and their details using the following command:

network interface service-policy show

Policy

Included services

Equivalent data protocol

Description

default-management

data-core, management-ssh, management-https, data-dns-server, management-http, backup-ndmp-control, management-snmp-server

none

Used by LIFs handling SVM-scoped management to create SVM management LIFs owned by a data SVM. These LIFs can be used to provide SSH or HTTPS access to SVM administrators.

default-data-blocks

data-core, data-iscsi

iscsi

Used by LIFs carrying block-oriented SAN data traffic

default-data-files

data-core, data-nfs, data-cifs, data-flexcache, data-fpolicy-client

nfs, cifs, fcache

Use default-data-files policy to create NAS LIFs supporting file-based data protocols.

The following table lists the services that can be used on a data SVM along with any restrictions each service imposes on a LIF’s failover policy as of ONTAP 9.10.1:

Service

Failover restrictions

Description

management-ssh

-

Services for SSH management access

management-http

-

Services for HTTP management access

management-https

-

Services for HTTPS management access

management-portmap

-

Services for portmap management access

management-snmp-server

-

Services for SNMP server management access

data-core

-

Core data services

data-nfs

-

NFS data service

data-cifs

-

CIFS data service

data-flexcache

-

FlexCache data service

data-iscsi

home-port-only

iSCSI data service

backup-ndmp-control

-

Backup NDMP controls data service

data-dns-server

-

DNS server data service

data-fpolicy-client

-

File-screening policy data service

data-nvme-tcp

home-port-only

NVMe TCP data service

data-s3-server

-

Simple Storage Service (S3) server data service

You should be aware of how the service policies are assigned to the LIFs in data SVMs:

  • If a data SVM is created with a list of data services, the built-in "default-data-files" and "default-data-blocks" service policies in that SVM are created using the specified services.

  • If a data SVM is created without specifying a list of data services, the built-in "default-data-files" and "default-data-blocks" service policies in that SVM are created using a default list of data services.

    The default data services list includes the iSCSI, NFS, SMB, and FlexCache services.

  • When a LIF is created with a list of data protocols, a service policy equivalent to the specified data protocols is assigned to the LIF.

    If an equivalent service policy does not exist, a custom service policy is created.

  • When a LIF is created without a service policy or list of data protocols, the default-data-files service policy is assigned to the LIF by default.

Data-core service

The data-core service allows components that previously used LIFs with the data role to work as expected on clusters that have been upgraded to manage LIFs using service policies instead of LIF roles (which are deprecated in ONTAP 9.6).

Specifying data-core as a service does not open any ports in the firewall, but the service should be included in any service policy in a data SVM. For example, the default-data-files service policy contains the following services by default:

  • data-core

  • data-nfs

  • data-cifs

  • data-flexcache

The data-core service should be included in the policy to ensure all applications using the LIF work as expected, but the other three services can be removed, if desired.

Client-side LIF service

Beginning with ONTAP 9.10.1, ONTAP provides client-side LIF services for multiple applications. These services provide control over which LIFs are used for outbound connections on behalf of each application.

The following new services give administrators control over which LIFs are used as source addresses for certain applications.

Service

SVM restrictions

Description

management-ntp-client

system-only

Beginning with ONTAP 9.10.1, ONTAP provides NTP client service for outbound connections to an external NTP server.

data-fpolicy-client

data-only

Beginning with ONTAP 9.8, ONTAP provides client service for outbound FPolicy connections.

Each of the new services are automatically included in some of the built-in service policies, but administrators can remove them from the built-in policies or add them to custom policies to control which LIFs are used for outbound connections on behalf of each application.