Hitachi NAS Platform
Network Administration Guide
Release 12.5
MK-92HNAS008-08
December 2015
© 2011-2015 Hitachi, Ltd. All rights reserved.
No part of this publication ma
y be reproduced or transmitted in any form or by any
means, electronic or mechanical, including photocopying and recording, or stored in a
database or retrieval system for any purpose without the express written permission of
Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without
notice and assumes no responsibility for its use. This document contains the most
current information available at the time of publication. When new or revised information
becomes available, this entire document will be updated and distributed to all registered
users.
Some of the features described in this document might not be currently available. Refer
to the most recent product announcement for information about feature and product
availability, or contact Hitachi Data Systems Corporation at
Notice: Hitachi, Ltd.
, products and services can be ordered only under the terms and
https://portal.hds.com.
conditions of the applicable Hitachi Data Systems Corporation agreements. The use of
Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data
Systems Corporation.
2
Hitachi NAS Platform Network Administration Guide
Hitachi Data Systems products and services can be ordered only under the terms and
conditions of Hitachi Data S
ystems’ applicable agreements. The use of Hitachi Data
Systems products is governed by the terms of your agreements with Hitachi Data
Systems.
By using this software, you agree that you are responsible for:
a) Acquiring the relevant consents as may be required under local privacy laws or
otherwise from employees and other individuals to access relevant data; and
b) Verifying that data continues to be held, retrieved, deleted, or otherwise processed
in accordance with relevant laws.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other
countries. Hitachi Data Systems is a registered trademark and service mark of
Hitachi, Ltd., in the United States and other countries.
Archivas, Dynamic Provisioning, Essential NAS Platform, HiCommand, Hi-Track,
ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy,
Universal Star Network, and Universal Storage Platform are registered trademarks of
Hitachi Data Systems Corporation.
AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON,
FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/
ESA, z/OS, z9, zSeries, z/VM, z/VSE are registered trademarks and DS6000, MVS,
and z10 are trademarks of International Business Machines Corporation.
All other trademarks, service marks, and company names in this document or
website are properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft
Corporation.
This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/). Some parts of ADC use open source code
from Network Appliance, Inc. and Traakan, Inc.
Part of the software embedded in this product is gSOAP software. Portions created by
gSOAP are copyright 2001-2009 Robert A. Van Engelen, Genivia Inc. All rights
reserved. The software in this product was in part provided by Genivia Inc. and any
express or implied warranties, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose are disclaimed. In no event shall
the author be liable for any direct, indirect, incidental, special, exemplary, or
consequential damages (including, but not limited to, procurement of substitute
goods or services; loss of use, data, or profits; or business interruption) however
caused and on any theory of liability, whether in contract, strict liability, or tort
(including negligence or otherwise) arising in any way out of the use of this software,
even if advised of the possibility of such damage.
The product described in this guide may be protected by one or more U.S. patents,
foreign patents, or pending applications.
Hitachi NAS Platform Network Administration Guide
3
Notice of Export Controls
Export of technical data contained in this document ma
y require an export license from
the United States government and/or the government of Japan. Contact the Hitachi Data
Systems Legal Department for any export compliance questions.
4
Hitachi NAS Platform Network Administration Guide
Hitachi NAS Platform Network Administration Guide
5
Contents
eface .............................................................................................. 10
Pr
Related Documentation.......................................................................................... 10
Accessing product documentation........................................................................... 12
Getting help...........................................................................................................12
Comments.............................................................................................................12
1 Network interfaces...............................................................................14
File serving interfaces.............................................................................................15
Link aggregation...............................................................................................15
Using LACP................................................................................................. 16
Typical LACP configurations..........................................................................16
VLAN interfaces................................................................................................ 19
Non-file serving interfaces...................................................................................... 19
Using Network and Port Address Translation....................................................... 20
Aggregate Linux interfaces................................................................................ 21
Typical non-file serving interface configurations.................................................. 23
Jumbo frames support............................................................................................24
2 Routing overview ................................................................................26
Default gateways................................................................................................... 27
Static routes.......................................................................................................... 27
Dynamic routes......................................................................................................27
Managing routes.................................................................................................... 28
Understanding routing by EVS.................................................................................29
3 Name and directory services.................................................................30
Name services....................................................................................................... 31
DNS and DDNS.................................................................................................31
Registering a CIFS name................................................................................... 31
WINS...............................................................................................................32
6
Hitachi NAS Platform Network Administration Guide
Directory services...................................................................................................32
NIS (f
LDAP advantages..............................................................................................32
or NFS and FTP) ..................................................................................... 32
4 Using IPv6 ........................................................................................ 34
IPv6 overview........................................................................................................35
IPv6 and the NAS server.........................................................................................35
IPv6 and non-file serving interfaces................................................................... 36
5 Configuring link aggregation.................................................................38
Viewing link aggregations....................................................................................... 39
Adding link aggregations.........................................................................................40
Editing link aggregations.........................................................................................41
Deleting link aggregations.......................................................................................41
Configuring LACP................................................................................................... 42
Configuring Aggregate Linux interfaces....................................................................43
6 Configuring VLAN interfaces................................................................. 44
Adding VLAN interfaces.......................................................................................... 45
Deleting VLAN interfaces.........................................................................................46
Advanced VLAN interface configuration....................................................................46
7 Configuring IP addresses......................................................................48
Viewing IP addresses..............................................................................................49
Adding IP addresses...............................................................................................49
Deleting IP addresses.............................................................................................50
Advanced IP configuration...................................................................................... 50
8 Configuring routes............................................................................... 54
Viewing IP routes...................................................................................................55
Adding IP routes.................................................................................................... 55
Deleting IP routes.................................................................................................. 56
9 Configuring name and directory services............................................... 58
Specifying name services........................................................................................59
Prioritizing name services....................................................................................... 61
Configuring NIS servers..........................................................................................62
Modifying NIS servers....................................................................................... 63
Adding NIS servers........................................................................................... 64
Deleting NIS servers......................................................................................... 64
Configuring LDAP servers........................................................................................65
Modifying LDAP configuration............................................................................ 66
Adding LDAP servers.........................................................................................67
Deleting LDAP servers.......................................................................................67
Hitachi NAS Platform Network Administration Guide
7
10 Managing networks and devices ...........................................................68
Configuring non-fi
Configuring devices on the system monitor.............................................................. 69
le serving interfaces..................................................................... 69
11 Troubleshooting...................................................................................74
Network health information.....................................................................................75
Detecting issues.....................................................................................................77
Collecting network packets......................................................................................78
A VLAN conversion..................................................................................80
Example VLAN conversion.......................................................................................82
B Network ports......................................................................................84
8
Hitachi NAS Platform Network Administration Guide
Hitachi NAS Platform Network Administration Guide
9
In PDF format, this guide provides information about the server's network
usage, and explains how to configure network interfaces, IP addressing,
name and directory services.
Related Documentation
Release Notes provide the most up-to-date information about the system,
including new feature summaries, upgrade instructions, and fixed and known
defects.
Administration Guides
• System Access Guide (MK-92HNAS014)—In PDF format, this guide
explains how to log in to the system, provides information about accessing
the NAS server/cluster CLI and the SMU CLI, and provides information
about the documentation, help, and search capabilities available in the
system.
• Server and Cluster Administration Guide (MK-92HNAS010)—In PDF format,
this guide provides information about administering servers, clusters, and
server farms. Includes information about licensing, name spaces,
upgrading firmware, monitoring servers and clusters, the backing up and
restoring configurations.
• Storage System User Administration Guide (MK-92HNAS013)—In PDF
format, this guide explains user management, including the different types
of system administrator, their roles, and how to create and manage these
users.
• Network Administration Guide (MK-92HNAS008)—In PDF format, this
guide provides information about the server's network usage, and explains
how to configure network interfaces, IP addressing, name and directory
services.
• File Services Administration Guide (MK-92HNAS006)—In PDF format, this
guide explains about file system formats, and provides information about
creating and managing file systems, and enabling and configuring file
services (file service protocols).
• Data Migrator Administration Guide (MK-92HNAS005) —In PDF format,
this guide provides information about the Data Migrator feature, including
how to set up migration policies and schedules.
• Storage Subsystem Administration Guide (MK-92HNAS012)—In PDF
format, this guide provides information about managing the supported
storage subsystems (RAID arrays) attached to the server/cluster. Includes
information about tiered storage, storage pools, system drives (SDs), SD
Preface
10 Preface
Hitachi NAS Platform Network Administration Guide
groups, and other storage device related configuration and management
features and functions.
• Snapshot Administration Guide (MK
-92HNAS011)—In PDF format, this
guide provides information about configuring the server to take and
manage snapshots.
• Replication and Disaster Recovery Administration Guide (MK-92HNAS009)
—In PDF format, this guide provides information about replicating data
using file-based replication and object-based replication, provides
information on setting up replication policies and schedules, and using
replication features for disaster recovery purposes.
• Antivirus Administration Guide (MK-92HNAS004)—In PDF format, this
guide describes the supported antivirus engines, provides information
about how to enable them, and how to configure the system to use them.
• Backup Administration Guide (MK-92HNAS007)—In PDF format, this guide
provides information about configuring the server to work with NDMP, and
making and managing NDMP backups.
• Command Line Reference Opens in a browser, and describes the
commands used to administer the system.
Note: F
or a complete list of Hitachi NAS open source software copyrights and
licenses, see the System Access Guide.
Command Line References
The Command Line Reference provides information on the commands used to
manage your system, and includes relevant information on the operation of
your hardware and software. Depending on the model of your server or
cluster node, you should refer to the Command Line Reference that is
appropriate for your system:
• Command Line Reference for models 3080 and 3090
• Command Line Reference for models 4060, 4080, and 4100
• Hitachi High-performance NAS Platform Command Line Reference
Hardware References
• Hitachi NAS Platform 3080 and 3090 G1 Hardware Reference
(MK-92HNAS016)—Provides an overview of the first-generation server
hardware, describes how to resolve any problems, and replace potentially
faulty parts.
• Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference
(MK-92HNAS017)—Provides an overview of the second-generation server
hardware, describes how to resolve any problems, and replace potentially
faulty parts.
• Hitachi NAS Platform Series 4000 Hardware Reference (MK-92HNAS030)
(MK-92HNAS030)—Provides an overview of the Hitachi NAS Platform
Series 4000 server hardware, describes how to resolve any problems, and
how to replace potentially faulty components.
Preface 11
Hitachi NAS Platform Network Administration Guide
• Hitachi NAS Platform System Manager Unit (SMU) Hardware Reference
(MK
-92HNAS065) —This document describes the usage and replacement
instructions for the SMU 300/400.
• Hitachi High-performance NAS Platform (MK-99BA012—Provides an
overview of the NAS Platform 3100/NAS Platform 3200 server hardware,
and describes how to resolve any problems, and replace potentially faulty
parts.
Accessing product documentation
Product documentation is available on Hitachi Support Connect:
support.hds.com/en_us/documents.html. Check this site for the most current
documentation, including important updates that ma
the release of the product.
Getting help
Hitachi Support Connect
and solutions sold by Hitachi. To contact technical support, log on to Hitachi
Support Connect for contact information:
contact-us.html.
Hitachi Community
partners, independent software vendors, employees, and prospects. It is the
destination to get answers, discover insights, and make connections. Join
the conversation today! Go to
your profile.
Comments
Please send us your comments on this document to
Include the document title and number
example, -07), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi.
https://
y have been made after
is the destination for technical support of products
https://support.hds.com/en_us/
is a global online community for HDS customers,
community.hds.com, register
doc.comments@hds.com.
, including the revision level (for
, and complete
Thank you!
12 Preface
Hitachi NAS Platform Network Administration Guide
Preface 13
Hitachi NAS Platform Network Administration Guide
1
Network interfaces
This section contains information on
aggregation and jumbo frames support.
File serving interfaces
□
Non-file serving interfaces
□
Jumbo frames support
□
HNAS network interfaces, link
14 Network interfaces
Hitachi NAS Platform Network Administration Guide
File serving interfaces
NA
S servers provide the following file serving physical interfaces:
Models 4040 and earlier
• ge1 - ge6 - 1 GbE interfaces (RJ45)
• tg1 - tg2 - 10 GbE interfaces (XFP)
Models 4060 / 4080 / 4100
• tg1 - tg4 - 10 GbE interfaces (SFP+)
File serving physical interfaces enable network clients to access an EVS on
the storage server. These interfaces are commonly added together in a link
aggregation in order to increase redundancy and throughput of data.
Link aggregation
In a link aggregation, one or more file serving interfaces are grouped to form
a single logical interface. This functionality can increase bandwidth capability
and create resilient and redundant links. Aggregating multiple network links
does not increase performance of a single client TCP connection but it does
enable more individual connections to be served faster, by using more
available links and also by reducing contention within a link. An aggregation
also provides load balancing where the processing and communications
activity is distributed across several links in a trunk. Therefore, aggregations
provide higher link availability and increased Link Aggregation Group (LAG)
capacity.
Note: All interfaces in an aggregation must be of the same t
(either all 1 Gbps interfaces or all 10 Gbps interfaces).
An aggregation is assigned a unique MAC address which is different on each
cluster node. Each aggregation can ha
to configure an aggregation without any IP addresses, but this prevents
communication through that interface. For example, in a cluster, an
aggregation associated with an EVS appears on all nodes but is only active on
the node that the EVS is running on because the EVS holds the IP address. If
the EVS fails over onto another node, the IP address moves with the EVS,
activating the aggregation on the new node.
The server supports static aggregations. It also supports the Link
Aggregation Control Protocol (LACP) for dynamic aggregations.
Network interfaces 15
Hitachi NAS Platform Network Administration Guide
ve multiple IP addresses. It is possible
ype/speed
Using LACP
To view the status of an aggregation, navigate to the Link Aggregation
page as shown below:
The serv
uses to manage an individual link's transmission state (within a Link
Aggregation Group). The server controls the LACP relationship between
multiple switches. The server determines which network interfaces are in use
and can bring up alternative network interfaces during a failure. For example,
if the server does not receive any LACP messages from the primary switch
(the waiting time is determined by the configured LACP timeout), the server
can use the network interfaces connected to the secondary switch instead.
LACP aggregates are not automatically created or populated. The
administrator must first create an aggregate interface, then enable LACP on
that interface.
Note: The serv
LACP timeouts
The serv
timers. A short timeout is three seconds (three x one second). A long timeout
is 90s (three x 30 seconds). Therefore, the link times out after three missed
messages. Long timeouts are recommended in order to upgrade upstream
network devices without causing path failover on the server. The default
setting is a short timeout.
er supports the Link Aggregation Control Protocol (LACP) which it
er always sends LACPDUs set to ACTIVE.
er supports both short (one second) and long (30 second) LACP
Typical LACP configurations
Here are three typical configurations when using LACP with NAS servers:
• Split-LAG with Layer-2 redundancy
• Split-LAG with Layer-2 redundancy and increased bandwidth
16 Network interfaces
Hitachi NAS Platform Network Administration Guide
• Split-LAG with a single logical switch
Note: The serv
ers are always in LACP Active mode while the switches can be
configured in active or passive LACP mode.
Split-LAG with Layer-2 redundancy
When LACP is enabled, it is possible to have a scenario where a pair of
clustered NAS servers are connected to a pair of switches configured with one
link aggregation (over two file-serving interfaces) as shown in the example
below:
This scenario provides basic Layer-2 redundancy on the NAS servers.
Note: Static aggregation is not supported in a split
-LAG scenario.
Split-LAG with Layer-2 redundancy and increased bandwidth
This scenario includes a link aggregation o
ver four file-serving interfaces for
increased bandwidth and increased standby links as shown in the example
below:
Network interfaces 17
Hitachi NAS Platform Network Administration Guide
Single logical switch with Layer-2 redundancy and increased
bandwidth
This scenario includes a pair or switches connected in such a w
ay as to
appear as one logical switch. The NAS servers are configured with a link
aggregation over four file-serving interfaces as shown in the example below:
18 Network interfaces
Hitachi NAS Platform Network Administration Guide
VLAN interfaces
A ph
ysical network can be partitioned into multiple, isolated distinct
broadcast domains called virtual LANs or VLANs.
An HNAS server can provide access to a VLAN using a VLAN interface on an
aggregate interface. Administrators can create a VLAN interface for each
tagged VLAN for each aggregate interface over which the HNAS needs to
communicate. For example, VLAN 1 on ag1 is different from VLAN 1 on ag2.
Note: If an address is assigned to a VLAN interface, the serv
untagged packets for that address. Therefore, do NOT create a VLAN
interface for the native or otherwise untagged VLAN, as it can result in a loss
of connectivity.
Non-file serving interfaces
A NA
S server provides two 10/100/1000 Ethernet non-file serving interfaces
as follows:
• eth1
Network interfaces 19
Hitachi NAS Platform Network Administration Guide
er discards
• eth0
These interfaces use standard RJ45 connectors.
The serv
We recommend a 1Gbps speed for the switch uplink port for the non-file
serving interface with full duplex, bi-directional flow control enabled.
eth1
This interface is mandatory and enables users to communicate with the SMU,
any auxiliary devices and the non-file serving interfaces of other HNAS
servers. During initial setup of the HNAS server, this interface is configured
with an IP address. This interface can also be configured with a separate
cluster node IP address if the server is intended to be part of a cluster.
eth0
This interface is optional and enables the user to configure file services on
the server as well as create and configure Enterprise Virtual Servers (EVSs).
For example, when using SyncDR, the Admin EVS needs to be on eth0.
During initial setup of the HNAS server, this interface is configured with an IP
address. Connecting to the HNAS server using this IP address enables direct
access to the server management interface and provides the user with a
command line interface. See the CLI Reference manual for available
commands.
er uses auto-negotiation for speed/duplex/flow control by default.
It is necessary for eth0 to be connected (and therefore in use by the Admin
EVS) for the following features:
• V2I
• VASA Provider
• Data Migrator to Cloud (DM2C)
• Using an internal SMU
Note: R
password are both 'supervisor') which is exposed when using the eth0
interface.
emember to secure the HNAS password (the default username and
Using Network and Port Address Translation
In order to minimiz
can be located on a private management network and use Network Address
Translation (NAT) and Port Address Translation (PAT) to communicate
between the two networks. For example, an HTTP request for a device in a
private management network is made to a public network on the server's
eth0 interface, on a NAT port. The server then translates this request to the
IP address and actual HTTP port of the device on the private management
network.
e data traffic on a public file-serving network, the server
20 Network interfaces
Hitachi NAS Platform Network Administration Guide
Note: The IP address range of a private management network can only
include IP addresses which share the first three octets of the serv
network IP address. For example, for an server IP address of 192.0.2.1,
devices on the private management network must have addresses in the
range of 192.0.2.2 - 192.0.2.254.
As the server supports mixed systems, It is also possible for some or all
auxiliary devices to be located on a public file-serving network. This enables
some devices to be located on a private management network, and others on
a public file-serving network.
Aggregate Linux interfaces
The NAS server provides the ability to access the file serving interfaces (agX)
from Linux, using a virtual Linux network interface (eth-agX), which is bound
to a specific agX interface as shown below:
er's eth1
Network interfaces 21
Hitachi NAS Platform Network Administration Guide
Using an Aggregate Linux interface (instead of eth0 or eth1) provides a
potentially faster route for data and management traffic. It also enables the
non-file serving interfaces (eth0 and eth1) and the file serving aggregations
to be physically separate while providing Linux access to both sets of
interfaces.
Example
For the scenario below:
22 Network interfaces
Hitachi NAS Platform Network Administration Guide
The Administrator can create eth-ag1
aggregate-linux-interface-create --interface ag1
, any functionality that is available on eth0 and eth1, is also available on
Now
the file serving interfaces. This can include using SSH with the Admin EVS IP
address.
For information on how to manage the eth-agX interfaces, see the following
CLI commands:
• aggregate-linux-interfaces
• aggregate-linux-interface-show
• aggregate-linux-interface-create
• aggregate-linux-interface-delete
over ag1 as shown below:
Typical non-file serving interface configurations
There are three typical configurations for NAS non-file serving interfaces:
• Single NAS server (embedded SMU)
• Single NAS server (external SMU)
• Clustered NAS servers (external SMU)
Single NAS server (internal SMU)
In this configuration, the NAS uses an internal SMU where eth1 is connected
to the private management network and eth0 is connected to the public
management network.
Single NAS server (external SMU)
In this configur
maintaining external configuration backups and also when preparing the NAS
to join a cluster. In this case, eth1 on the NAS and eth1 on the SMU are
connected to the same private management network and eth0 on the NAS is
optionally connected to the public management network.
ation, the NAS uses an external SMU. This is necessary when
Network interfaces 23
Hitachi NAS Platform Network Administration Guide
Clustered NAS servers (external SMU)
In this configur
this case, eth1 on each NAS and eth1 on the SMU are connected to the same
private management network and eth0 on each NAS is optionally connected
to the public management network.
ation, the NAS is part of a cluster with an external SMU. In
Jumbo frames support
All file serving interfaces of a serv
enable transmission of Ethernet frames with a payload larger than 1500
bytes and these frames co-exist with standard frames on an Ethernet
network.
er support jumbo frames. Jumbo frames
All file serving interfaces receive jumbo frames unconditionally, without any
configuration changes. It is possible to configure a file serving interface to
transmit jumbo frames by specifying an MTU size of between 1,501 and
9,600 bytes.
To use jumbo frame transmission, configure the following settings:
• IP MTU for off-subnet transmits - bytes
• TCP MTU
• Other Protocol MTU
Caution: Networking equipment lacking the jumbo frames extension can
drop jumbo frames and record an oversize packet error. Before configuring
jumbo frame transmission, verify that all network equipment along the route
(and at each end point) supports jumbo frames. If you enable jumbo frames
and either network equipment or clients on the subnet do not support jumbo
frames, it is possible to experience a loss of communication with the server/
cluster.
Successful IP data transmission using jumbo frames depends on the
destination IP address or sub-network. The maximum MTU siz
e for a
24 Network interfaces
Hitachi NAS Platform Network Administration Guide
destination IP address or sub-network is configured as an attribute in the IP
routing table.
The IP MTU in use is the lowest of:
•
The interface IP MTU setting
• Any IP MTU specified by the selected route
• Any IP MTU specified by the MTU command
The recommended MTU size is 8972 bytes (in order to compensate for the IP
and ICMP headers).
Network interfaces 25
Hitachi NAS Platform Network Administration Guide
2
Routing overview
This section contains
the HNAS server can route IP traffic in three ways: through Default
Gateways, Static Routes, and Dynamic Routes.
Default gateways
□
Static routes
□
Dynamic routes
□
Managing routes
□
Understanding routing by EVS
□
HNAS IP routing concepts. Depending on configuration,
26 Routing overview
Hitachi NAS Platform Network Administration Guide
Default gateways
The serv
connected to multiple IP networks, add a default gateway for each network to
which the server is connected. This configuration allows the server to direct
traffic through the appropriate default gateway by matching source IP
addresses specified in outgoing packets with the gateway on the same
subnet.
With multiple default gateways, the server routes IP traffic logically, reducing
the need to specify static routes for every network that connects with a
particular server.
Static routes
Static routing provides a fixed path for data in a network. When a server on a
network is connected to additional networks through a router, communication
between that server and the remote networks can be enabled by specifying a
static route to each network.
Static routes are set up in a routing table. Each entry in the table consists of
a destination network address, a gateway address, and a subnet mask.
Entries for static routes in the server’s routing table are persistent, meaning
that, if a server is restarted, the route table preserves the static routing
entries.
er supports multiple default gateways for routing IP traffic. When
The NAS server supports gateway, network and host static routes. The
Default option sets up a gateway and does not require a destination. Select
the Network option to set up a route to address all of the computers on a
specific network. Select the Host option to address a specific computer on a
different network. The maximum possible number of static routes is 127
(default gateways also count against this total).
In most cases, for IPv6, it is not necessary to statically configure gateways as
they are automatically discovered through the received router
advertisements.
Dynamic routes
The NAS server supports ICMP redirects and RIP versions 1 and 2, which
enable it to dynamically add routes to its route table.
ICMP redirects
Routing overview 27
Hitachi NAS Platform Network Administration Guide
Loading...