m05 networking final

7/29/2019 M05 Networking FINAL

1/49

Networking

Module 5

Data ONTAP 7.3 Fundamentals


2/49

2008 NetApp. All rights reserved. 2

Module Objectives

By the end of this module, you should be able to:

Identify the configuration of network settings and

components in Data ONTAP

Explain the main features and uses of naming services

Explain the function of/etc/hosts

, NIS, and DNS

Configure Data ONTAP for name resolution in/etc/nsswitch.conf

Use host files to troubleshoot name resolution

Explain routing tables in Data ONTAP

Identify how a FAS system routes packets

Define and create virtual interfaces (VIFs)

Discuss the operation and method for routing in VLANs


3/49


Interface Configuration


4/49


Interface Configuration

Initial interface configuration

Configured by the setup command

After initial setup, you can create and modify

the interface configuration using:

CLI with the ifconfig command

FilerView

Interface configuration is stored in the

/etc/rc file, which is read when thestorage system boots


5/49


Interface Configuration (Cont.)

The storage system

supports the following

network types:

Ethernet 10/100 Base-T

1G Ethernet

10G Ethernet (Data

ONTAP 7.2 or later)

Storage systems with

multiple-port Ethernetadapters use letters to

identify each port.

Network Types Letter

Ethernet e

Port Number Letter

1 a

2 b

3 c

4 d


6/49


Interface Naming Example

Interface Type Slot Port Interface Name

Ethernet 0 (onboard) 1 e0a

Ethernet 0 (onboard) 2 e0b

Ethernet 3 1 e3a

Ethernet 3 2 e3b

Ethernet 3 3 e3cEthernet 3 4 e3d


7/49 2008 NetApp. All rights reserved. 7

Managing Interfaces: ifconfig

Network interface configuration parameters:

IP address

Netmask address

Broadcast address

Media type and speed Maximum Transmission Unit (MTU)

Flow control (Gigabit Ethernet II controller only)

Up or down state

To display current status: ifconfig -a

Interface configuration changes are notpermanent until entered into the /etc/rc file



NOTE: Modifications made in FilerView are persistent in

the /etc/rc file.

Managing Interfaces: FilerView



Managing Interfaces: FilerView (Cont.)



Managing Interfaces: CLI

To configure the current status:

ifconfig

To display permanent settings:

rdfile /etc/rc

To change permanent settings:

wrfile /etc/rc

Command overwrites the existing file

Existing information can be cut and pasted Press Control-C to save changes and exit

To activate changes to the /etc/rc file, reboot

or issue source /etc/rc



Name Resolution



Host-Name Resolution

A storage system must be able to resolve host

names to valid IP addresses.

Host-name resolution is commonly used in:

Processing CIFS requests

Processing NFS requests

Authenticating RSH sessions

Many other services



Host-Name Resolution (Cont.)

Data ONTAP stores and maintains host information in

the following locations: /etc/hosts file

DNS server

Network Information Service (NIS) server

In host-name resolution:

The /etc/nsswitch.conf file controls the order inwhich these three locations are checked.

Data ONTAP stops checking locations when a valid IPaddress is returned.

NOTE: For convenience, you can use the Host Name ResolutionPolicy Wizard in FilerView.



/etc/hosts Configuration

Local IP and name resolution is provided by/etc/hosts.

To modify /etc/hosts, use:

The rdfile and wrfile commands in CLI

adminhost

FilerView



/etc/hosts Configuration: FilerView



DNS Configuration

The DNS provides a centralized mechanism for

host-name resolution in Windows and UNIX

environments.

To configure the DNS: In FilerView, use the Host Name Resolution

Policy Wizard

In the CLI, use:

setup command

options dns.*

dns command



NIS

In UNIX environments, NIS provides:

A centralized mechanism for host-name resolution User authentication

The storage system can participate as an NIS client or

server.

To configure NIS:

In FilerView, use the Host Name Resolution PolicyWizard

In the CLI, use: setup command options nis.*

nis command



Host Name Resolution Policy Wizard:

FilerView

To ease configuration, use the FilerView Host

Name Resolution Policy Wizard:



Host Resolution Policy Wizard:

FilerView (Cont.)

Choose a resolution method:




FilerView (Cont.)

Provide DNS parameters:




FilerView (Cont.)

List DNS server address(es):


22/49



FilerView (Cont.)

Specify NIS information:


23/49



FilerView (Cont.)

Specify NIS Group Parameters:


24/49



FilerView (Cont.)

Specify the order for the Name Service

Configuration:


25/49



FilerView (Cont.)

Commit the changes:


26/49


Route Resolution


27/49


Route Information

A route defines the direction to a network or

host.To display the current routing table:

In CLI, use netstat -r

FilerView

system> netstat -r

Routing tables

Internet:

Destination Gateway Flags Refs

default 66.166.149.161 UGS 14

66.166.149.160/2 link#1 UC 0

66.166.149.161 0:20:6f:10:25:7a UHL


28/49


The netstat Command

Use the netstat r command to view or

change the network routing tables

Use the netstat nr command to view or

change the network routing tables with IP

addresses (instead of name resolution) Use the netstat rs command to view or

display the per protocol statistics


29/49


The route Command

Use the route -s command to show routing

tables

Use the route -f command to flush all

gateway entries in the routing table

Use the routens command to view

network routing tables with IP addresses

(instead of name resolution)


30/49


Virtual Interfaces


31/49


Virtual Interfaces

Virtual interfaces (VIFs) allow:

Trunking of one or more Ethernet interfaces

Increased throughput to and from the storagesystem

VIFs can be configured as:

Single-mode trunks

Multimode trunks

Load Balancing

Ether Channel SwitchVirtual IP


32/49


Single-Mode VIF

In single mode, only one

interface is active. Theother interface is on

standby. Provides failover capability

e0 e1

x


33/49


Multimode VIF

In multimode, all interfaces

are active and share aMAC address.

Provides multiplex capability

e0 e2e1

x


34/49


Second-Level VIF

Switch and NIC failures are transparent to clients when communicating

to system A through the Vif_A super virtual interface.

Quad Quad Quad Quad

Switch X Switch Y

Vif_YA

Vif_YB

Vif_XB Super Vif_B

Defining a virtual interface at this level provides resilience for a Quad NIC failure.

Final step: Active-Active

Vif_XA Super Vif_A


35/49


Load Balancing

Load balancing is supported for multimode VIFs only:

IP-based (default) MAC-based

Round-robin (not recommended)

Load balancing assumes an even distribution ofIP addresses, such as the following:

e0 e1 e2 e3

10.10.10.1 10.10.10.2 10.10.10.3 10.10.10.4

10.10.10.5 10.10.10.6 10.10.10.7 10.10.10.8

10.10.10.9 10.10.10.10 10.10.10.11 10.10.10.12

10.10.10.13 10.10.10.14 10.10.10.15 10.10.10.16

Creating a VIF from the CLI:


36/49



Single-level Example

The named virtual interface is treated as asingle interface: ifconfig vif_name

Entries created on the command line are not

permanent

system> vif create single SingVif1 e3a e3bsystem> ifconfig SingVif1 172.17.200.201 netmask

255.255.255.0 mediatype 100tx-fd up

system> vif favor e3a

system> ifconfig SingVif1

SingVif1:flags=1148043 mtu 1500

inet 172.17.200.201 netmask 0xffffff00 broadcast

172.17.200.255

ether 02:a0:98:03:28:8e (Disabled virtual interface)



37/49



Multilevel Example

system> vif create multi multiVif2 e3a e3b e3c e3d

system> ifconfig multiVif2 172.17.200.202 netmask

255.255.255.0 mediatype 100tx-fd up

system> ifconfig multiVif2

multiVif2:flags=1148043 mtu 1500

inet 172.17.200.202 netmask 0xffffff00 broadcast172.17.200.255

ether 02:a0:98:03:28:8e (Disabled virtual interface)



38/49



Second-Level VIF Example

system> vif create multi multiVif1 e3a e3b

system> vif create multi multiVif2 e3c e3dsystem> vif create single L2vif multiVif1 multiVif2

system> ifconfig L2vif 172.17.200.206 netmask255.255.255.0 mediatype 100tx-fd up

system> ifconfig L2vif

L2vif:flags=1148043 mtu 1500

inet 172.17.200.206 netmask 0xffffff00 broadcast172.17.200.255

ether 02:a0:98:03:28:8c (Disabled virtualinterface)


39/49


vif Commands

vif create [single|multi]

[-b [rr|ip|mac]][]

vif delete

[interface_list] vif destroy

vif add

vif [favor|nofavor]

vif status []

vif stat vif_name [interval]


40/49


After the VIF is created, assign it an address

using ifconfig.

Creating a VIF with FilerView


41/49


Virtual LANs


42/49


Virtual LANs (VLANs) provide:

Increased IP network security

Optimized packet routing

Virtual LANs

VLAN0

1

1

2

2

Floor 1

Floor 2

VLAN1 VLAN20

0


43/49


Creating a VLAN from the CLI

system> ifconfig e3b down

system> vlan create e3b 10vlan: e3b-10 has been created

system> ifconfig e3b-10 172.17.200.201 netmask255.255.255.0 mediatype 100tx-fd up

system> ifconfig a

e3b:flags=80908043 mtu 1500

ether 00:a0:98:03:28:8f (auto-1000t-fd-up)flowcontrol full


44/49


vlan Commands

Use the following commands for VLANs:

vlan createg on

vlan delete [-q]

vlan add

vlan stat

vlan modifyg [on|off]

Supported VLAN IDs are 14094

NOTE:VLAN ID 1 is used by a number of switch vendors.

VLANs over VIFs are supported

Use the /etc/rc file to persist configurations during

reboot


45/49


Module Summary

In this module, you should have learned to:

Use the ifconfig command to configure interfaces Identify host-name resolution methods:

/etc/hosts file

DNS

NIS Explain how a VIF is a single virtual interface created

from multiple physical interfaces

Identify trunking modes supported on the storagesystem:

Single modefailover

Multimodeincreased bandwidth

Explain how VLANs increase IP network security bytagging specific packets with the appropriate VLAN ID


46/49

Exercise

Module 5: Networking

Estimated Time: 45 minutes


47/49

Answers

Module 5: Networking


48/49


Check Your Understanding

Where can you set or change a host name

locally on the storage system?

FilerView > Network > Manage Hosts File

/etc/hosts

How do you configure host-name resolution fora storage system?

FilerView > Network > Host Name Resolution

Modifying

/etc/hosts

DNS, NIS commands

/etc/nsswitch.conf


49/49

Check Your Understanding (Cont.)

What is the difference between single-mode

and multimode trunks?

Single-modefailover

Multimodeimproved bandwidth

What are the benefits of a VLAN? Increased security

Improved packet routing

m05 networking final

Documents