Storage Admin HubConfiguration · Protection · Recovery
All guides/Configuration
Configuration · ONTAP 9

Create an SVM and data network

A protocol-ready storage VM with correct data LIF placement.

Scenario

Example: SVM svm_prod serves NFS on VLAN 220 through two data LIFs. An SVM is the administrative and protocol boundary for volumes and client access.

Before you change production

Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.

1. Design the service

  1. List protocols, SVM name, IPspace/broadcast domain, VLAN, LIF IPs, subnet/gateway, DNS and directory services. Map data LIFs to nodes and ports with redundancy.
  2. Confirm physical switch VLANs, MTU, routing, and firewall rules. For SAN, use the protocol-specific LIF and host design rather than assuming NAS failover behavior.
Verify

Approved worksheet with one row per LIF, home node/port, address, role, and target switch.

2. Configure in System Manager

  1. Open Storage > Storage VMs and add a storage VM. Select the required protocol(s), root volume placement, security style, and administrative settings.
  2. Create data interfaces on the planned ports or VLANs and enter approved IP settings. Configure SVM DNS/name services, then enable protocol services only after prerequisite servers respond.
  3. Create a small test volume or LUN after the protocol is ready. Do not expose it broadly; validate with a test client or host.
Read-only validation 
vserver show
network interface show
network port show
network route show

3. Troubleshoot reachability

  1. If clients cannot reach the SVM, compare DNS answer to the data LIF address, check LIF operational status and current port, VLAN tagging and switch port, route, and firewall.
  2. If name-service operations fail, check SVM DNS, NTP, LDAP/AD reachability, and the relevant protocol logs before changing the service.
Verify

Each intended data LIF responds from its client network and appears on the expected port.

If validation fails

  1. If a LIF is administratively up but operationally down, check home port, switch link, VLAN, broadcast domain and physical cabling. Record current and home ports.
  2. If the LIF is reachable locally but not from a routed client, compare the SVM route and upstream firewall with the approved path. Confirm return routing.
  3. If only one protocol fails, investigate its service and identity settings after network reachability is proven; avoid changing every LIF at once.
Verify

Re-run the original validation and record the observed result, exact error, time, and corrective action.

NetApp references