NetApp - ONTAP network state as built

category: solutionz · date: 2019-12-31 · updated: 2026-10-02 · author: LALA

NetApp Solution · Config document · referenced from Network design

noteThis is a listing of state, not a command set. The commands that created the interface group, the VLAN ports, the IPspaces, the broadcast domains and the interfaces were not kept in the working notes, and none are invented here.

The network configuration of one cluster as the as-built report recorded it: ports, the interface group, VLAN ports, IPspaces, broadcast domains, subnets, failover groups, logical interfaces and routes. It is arranged in the order in which the objects depend on each other, each block under the ONTAP command that shows it.

Item	Value
Shown here	Cluster `DC1-A-XNAS001`, datacenter A of site 1
Also applies to	`DC1-B-XNAS001`; see the differences below
Source	The as-built report produced with NetAppDocs; the columns are those of the report, not the exact columns of the commands
Cross-checked with	`network interface show` and `network port show` output in the notes of September 2017
ONTAP version at the time	9.1P11
State of the SVMs	Four data SVMs; the two added in 2019 are not in the report

The file

ini

# --- network port show -------------------------------------------------------
# Node DC1-A-ANAS001. Node DC1-A-ANAS002 is identical line for line.
# Port      Type      Link  MTU   Flow control  IPspace                  Broadcast domain
e0a         physical  up    9000  none/none     Cluster                  Cluster
e0b         physical  up    9000  none/none     Cluster                  Cluster
e0c         physical  down  1500  full/none     Default                  -
e0d         physical  down  1500  full/none     Default                  -
e0g         physical  up    9000  none/none     Default                  -
e0h         physical  up    9000  none/none     Default                  -
e0M         physical  up    1500  full/full     Default                  Default
a0a         if_group  up    9000  full/-        Default                  -
a0a-1020    vlan      up    9000  full/-        DC1-S-VCVSM001_ipspace   vlan-1020
a0a-1022    vlan      up    9000  full/-        Default                  vlan-1022
a0a-1024    vlan      up    9000  full/-        Default                  vlan-1024
a0a-1026    vlan      up    9000  full/-        DC1-S-VCVSM002_ipspace   vlan-1026
a0a-1027    vlan      up    9000  full/-        DC1-S-VCVSM004_ipspace   vlan-1027
a0a-1028    vlan      up    9000  full/-        DC1-S-VCVSM003_ipspace   vlan-1028

# --- network port ifgrp show -------------------------------------------------
# Node            Ifgrp  Mode            Distribution  Ports
DC1-A-ANAS001     a0a    multimode_lacp  ip            e0g, e0h
DC1-A-ANAS002     a0a    multimode_lacp  ip            e0g, e0h

# --- network port vlan show --------------------------------------------------
# On both nodes, parent interface a0a
# VLAN port  VLAN ID
a0a-1020     1020
a0a-1022     1022
a0a-1024     1024
a0a-1026     1026
a0a-1027     1027
a0a-1028     1028

# --- network ipspace show ----------------------------------------------------
# IPspace                 Broadcast domains               Ports on both nodes        Vservers
Cluster                   Cluster                         e0a, e0b                   Cluster
Default                   Default, vlan-1022, vlan-1024   a0a, a0a-1022, a0a-1024,   DC1-A-XNAS001
                                                          e0c, e0d, e0g, e0h, e0M
DC1-S-VCVSM001_ipspace    vlan-1020                       a0a-1020                   DC1-S-VCVSM001
DC1-S-VCVSM002_ipspace    vlan-1026                       a0a-1026                   DC1-S-VCVSM002
DC1-S-VCVSM003_ipspace    vlan-1028                       a0a-1028                   DC1-S-VCVSM003
DC1-S-VCVSM004_ipspace    vlan-1027                       a0a-1027                   DC1-S-VCVSM004-mc

# --- network port broadcast-domain show --------------------------------------
# Every domain holds the named port of both nodes and has a failover group
# of the same name.
# Broadcast domain  IPspace                  MTU   Ports           Subnet
Cluster             Cluster                  9000  e0a, e0b        -
Default             Default                  1500  e0M             -
vlan-1020           DC1-S-VCVSM001_ipspace   9000  a0a-1020        DC1-S-VCVSM001_subnet
vlan-1022           Default                  9000  a0a-1022        -
vlan-1024           Default                  9000  a0a-1024        -
vlan-1026           DC1-S-VCVSM002_ipspace   9000  a0a-1026        DC1-S-VCVSM002_subnet
vlan-1027           DC1-S-VCVSM004_ipspace   9000  a0a-1027        -
vlan-1028           DC1-S-VCVSM003_ipspace   9000  a0a-1028        DC1-S-VCVSM003_subnet

# --- network subnet show -----------------------------------------------------
# Subnet                 Broadcast domain  Network           Gateway        Range
DC1-S-VCVSM001_subnet    vlan-1020         10.11.18.224/28   10.11.18.238   10.11.18.236
DC1-S-VCVSM002_subnet    vlan-1026         10.11.10.64/27    -              10.11.10.94
DC1-S-VCVSM003_subnet    vlan-1028         10.11.10.48/29    10.11.10.54    10.11.10.49

# --- network interface failover-groups show ----------------------------------
# Vserver                 Group      Targets
Cluster                   Cluster    DC1-A-ANAS001:e0a, :e0b, DC1-A-ANAS002:e0a, :e0b
DC1-A-XNAS001             Default    DC1-A-ANAS001:e0M, DC1-A-ANAS002:e0M
DC1-A-XNAS001             vlan-1022  DC1-A-ANAS001:a0a-1022, DC1-A-ANAS002:a0a-1022
DC1-A-XNAS001             vlan-1024  DC1-A-ANAS001:a0a-1024, DC1-A-ANAS002:a0a-1024
DC1-S-VCVSM001_ipspace    vlan-1020  DC1-A-ANAS001:a0a-1020, DC1-A-ANAS002:a0a-1020
DC1-S-VCVSM002_ipspace    vlan-1026  DC1-A-ANAS001:a0a-1026, DC1-A-ANAS002:a0a-1026
DC1-S-VCVSM003_ipspace    vlan-1028  DC1-A-ANAS001:a0a-1028, DC1-A-ANAS002:a0a-1028
DC1-S-VCVSM004_ipspace    vlan-1027  DC1-A-ANAS001:a0a-1027, DC1-A-ANAS002:a0a-1027

# --- network interface show --------------------------------------------------
# Vserver            Interface                  Admin/Oper  Address             Node            Port      Home
Cluster              DC1-A-XNAS001-01_clus1     up/up       169.254.30.146/16   DC1-A-ANAS001   e0a       true
Cluster              DC1-A-XNAS001-01_clus2     up/up       169.254.229.162/16  DC1-A-ANAS001   e0b       true
Cluster              DC1-A-XNAS001-02_clus1     up/up       169.254.211.26/16   DC1-A-ANAS002   e0a       true
Cluster              DC1-A-XNAS001-02_clus2     up/up       169.254.88.192/16   DC1-A-ANAS002   e0b       true
DC1-A-XNAS001        cluster_mgmt               up/up       10.11.10.33/28      DC1-A-ANAS001   a0a-1024  true
DC1-A-XNAS001        DC1-A-XNAS001-01_mgmt1     up/up       10.11.10.37/28      DC1-A-ANAS001   a0a-1024  true
DC1-A-XNAS001        DC1-A-XNAS001-02_mgmt1     up/up       10.11.10.38/28      DC1-A-ANAS002   a0a-1024  true
DC1-A-XNAS001        intercluster_lif_1         up/up       10.11.10.1/27       DC1-A-ANAS001   a0a-1022  true
DC1-A-XNAS001        intercluster_lif_2         up/up       10.11.10.2/27       DC1-A-ANAS001   a0a-1022  true
DC1-A-XNAS001        intercluster_lif_3         up/up       10.11.10.3/27       DC1-A-ANAS002   a0a-1022  true
DC1-A-XNAS001        intercluster_lif_4         up/up       10.11.10.4/27       DC1-A-ANAS002   a0a-1022  true
DC1-S-VCVSM001       DC1-S-VCVSM001_nfs_lif1    up/up       10.11.18.236/28     DC1-A-ANAS002   a0a-1020  true
DC1-S-VCVSM002       DC1-S-VCVSM002_nfs_lif1    up/up       10.11.10.94/27      DC1-A-ANAS001   a0a-1026  true
DC1-S-VCVSM003       DC1-S-VCVSM003_cifs_lif1   up/up       10.11.10.49/29      DC1-A-ANAS001   a0a-1028  true
DC1-S-VCVSM004-mc    DC1-S-VCVSM004_cifs_lif1   up/down     10.11.10.57/29      DC1-A-ANAS001   a0a-1027  true

# --- network route show ------------------------------------------------------
# Vserver            Destination  Gateway        Metric
DC1-A-XNAS001        0.0.0.0/0    10.11.10.46    20
DC1-S-VCVSM001       0.0.0.0/0    10.11.18.238   20
DC1-S-VCVSM003       0.0.0.0/0    10.11.10.54    20
DC1-S-VCVSM004-mc    0.0.0.0/0    10.11.10.62    20

# --- system service-processor network show -----------------------------------
# Node            Type  Status  Address          Gateway
DC1-A-ANAS001     SP    online  10.11.15.42/24   10.11.15.254
DC1-A-ANAS002     SP    online  10.11.15.44/24   10.11.15.254

What changes on cluster B

Object	`DC1-A-XNAS001`	`DC1-B-XNAS001`
Ports, interface group, VLAN ports	As above	Identical, on `DC1-B-ANAS001` and `DC1-B-ANAS002`
IPspaces and broadcast domains	As above	Identical names and members
Subnet objects	`DC1-S-VCVSM001_subnet`, `_002_`, `_003_`	Only `DC1-S-VCVSM004_subnet`: `10.11.10.56/29`, gateway `10.11.10.62`, range `10.11.10.57`
Cluster interfaces	Four addresses as above	`169.254.34.158`, `169.254.190.190`, `169.254.198.52`, `169.254.98.88`
`cluster_mgmt`	`10.11.10.33/28`	`10.11.10.34/28`
Node management	`10.11.10.37`, `10.11.10.38`	`10.11.10.39`, `10.11.10.40`
Intercluster interfaces	`10.11.10.1` to `10.11.10.4`	`10.11.10.5` to `10.11.10.8`
Interfaces of `DC1-S-VCVSM001` to `003`	`up/up` under the SVM	`up/down` under `DC1-S-VCVSM001-mc` to `003-mc`; home nodes are `DC1-B-ANAS001` for 001 and `DC1-B-ANAS002` for 002 and 003
Interface of `DC1-S-VCVSM004`	`up/down` under `DC1-S-VCVSM004-mc`	`up/up` under the SVM, on `DC1-B-ANAS002`
Default route of the admin SVM	`10.11.10.46`	`10.11.10.46`
Service processors	`10.11.15.42`, `10.11.15.44`, gateway `10.11.15.254`	`10.11.23.42`, `10.11.23.44`, gateway `10.11.23.254`

A subnet object exists only on the cluster where the SVM was created. The interfaces of the -mc copies are put on the partner by MetroCluster, which is also why they need the same IPspace, broadcast domain and VLAN port to exist there.

In September 2017, before the data SVMs existed, each node had only a0a-1022 and a0a-1024 as VLAN ports, and the node names ended in M. The addresses of the cluster, management and intercluster interfaces in that listing are the same as above.

Checked against ONTAP 9.19.1

As built	Today
Interface group, VLAN ports, broadcast domains, failover groups	The commands `network port ifgrp create`, `network port vlan create`, `network port broadcast-domain create` and `network interface failover-groups create` are all still in the command reference
Interfaces defined by a role (cluster, node management, cluster management, intercluster, data), as in the design drawing	The parameters `-role` and `-firewall-policy` of the interface commands are deprecated; `-service-policy` replaces them
Service processor network	`system service-processor network modify` is still the command
ONTAP 9.1 on a FAS8200	The last ONTAP release for a FAS8200 is 9.16.1

The research behind this section did not compare the output of the show commands between 9.1 and today, only the existence of the commands and the deprecated parameters.