Why would a "service policy" name change after upgrade to ONTAP 9.6 or later?

• When upgrading a cluster from ONTAP 9.5 to a release that supports LIF services for management and data LIFs, ONTAP will sometimes need to create a custom service policy to capture the role, data protocol, and firewall policy settings of existing LIFs.
• During the upgrade, a new service-policy will be created using a prefix of custom-data- or custom-management- followed by a random integer.
• More descriptive names can be applied using the "network interface service-policy rename" command.

• Example:
• As part of the upgrade process, the https firewall service is transformed into the management-https service policy service, in order to maintain the same connectivity before and after upgrade. 
• The system will process the effective service list of each LIF and confirm that a service policy matching this effective service list is available.
• If no such policy is found, a new custom policy containing these services is created and assigned to the LIF.
• NOTE：

Starting in ONTAP 9.7, the portmap firewall service is eliminated. Instead, the portmap port is opened automatically for all LIFs that support the NFS service
Therefore, for NFS service, a service-policy of default-data-files is created.