Skip to main content
NetApp Knowledge Base

Logical interface creation with service policy default-data-nvme-tcp fails

  1. Last updated
  2. Save as PDF
Views:
590
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
core
Last Updated:

Applies to

  • AFF800
  • ONTAP 9.10.1RC1
  • ONTAP 9.10.1X3

Issue

  • Logical interface creation with service policy default-data-nvme-tcp fails.
Cluster1::> network interface create -vserver svm0 -lif lif_svm0_1 -data-protocol nvme-tcp -address xx.xxx.xxx.xxx -netmask xxx.xxx.xxx.xxx -home-node cluster1-01 -home-port port_name -status-admin up -service-policy default-data-nvme-tcp
(network interface create)
 
Info: create_imp: Failed to create logical interface.
Error: command failed: Cannot create LIF "lif_svm0_1" on Vserver "svm0" with data protocols "-" because this list of data protocols is inconsistent with service policy "default-data-nvme-tcp". Try the command again without specifying a data protocol list and the system will populate this setting automatically based on the specified service policy.
 
  • Follow the error prompt to remove -data-protocol option from command line allows lif creation.
  • However, subsequent -data-protocol addition is not possible. The option -data-protocol is only available during initial creation.

Cluster1::> network interface create -vserver svm0 -lif lif_svm0_1 -address xx.xxx.xxx.xxx -netmask xxx.xxx.xxx.xxx -home-node cluster1-01 -home-port port_name -status-admin up -service-policy default-data-nvme-tcp
(network interface create)

Cluster1::> network interface show -vserver svm0 -lif lif_svm0_1 -instance
 (network interface show)
                               Vserver Name: svm0
                     Logical Interface Name: lif_svm0_1
                             Service Policy: default-data-nvme-tcp
                               Service List: -
                          (DEPRECATED)-Role: data
                              Data Protocol: none
                              …

cluster1::> network interface modify -
    -vserver                  -lif
    -service-policy           -address
    -netmask                  -netmask-length
    -subnet-name              -home-node
    -home-port                -status-admin
    -failover-policy          -firewall-policy
    -auto-revert              -dns-zone
    -listen-for-dns-query     -allow-lb-migrate
    -lb-weight                -failover-group
    -comment                  -force-subnet-association
    -is-dns-update-enabled    -rdma-protocols

cluster1::> network interface create -
    -vserver                  -lif
    -service-policy           -data-protocol  
    -address                  -netmask
    -netmask-length           -is-vip
    -auto                     -subnet-name
    -home-node                -home-port
    -status-admin             -failover-policy
    -firewall-policy          -auto-revert
    -dns-zone                 -listen-for-dns-query
    -allow-lb-migrate         -lb-weight
    -failover-group           -comment
    -force-subnet-association -is-dns-update-enabled
    -broadcast-domain         -rdma-protocols

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.