Hitachi 3100 Network Administration Manual Download Page 22 | Manualshive

Page: 22 / 89

background image

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

«
...
20
21
22
23
24
...
»

Summary of Contents for 3100

Page 1: ...Hitachi NAS Platform Network Administration Guide Release 12 5 MK 92HNAS008 08 December 2015 ...

Page 2: ...me 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 https portal hds com Notic...

Page 3: ...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 so...

Page 4: ...tained in this document may 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 ...

Page 5: ...5 Hitachi NAS Platform Network Administration Guide ...

Page 6: ...erving 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 ...

Page 7: ...ing 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...

Page 8: ...aces 69 Configuring devices on the system monitor 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 ...

Page 9: ...9 Hitachi NAS Platform Network Administration Guide ...

Page 10: ...tem 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 directo...

Page 11: ...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 Comman...

Page 12: ...hi Support Connect is the destination for technical support of products and solutions sold by Hitachi To contact technical support log on to Hitachi Support Connect for contact information https support hds com en_us contact us html Hitachi Community is a global online community for HDS customers partners independent software vendors employees and prospects It is the destination to get answers dis...

Page 13: ...Preface 13 Hitachi NAS Platform Network Administration Guide ...

Page 14: ... contains information on HNAS network interfaces link aggregation and jumbo frames support File serving interfaces Non file serving interfaces Jumbo frames support 14 Network interfaces Hitachi NAS Platform Network Administration Guide ...

Page 15: ...ation 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 type speed either all 1 Gbps interfaces or all 10 Gbps interfaces An aggregation is assigned a unique MAC...

Page 16: ...ch 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 server always sends LACPDUs set to ACTIVE LACP timeouts The server supports both short one second and long 30 second LACP timers A short timeout is three seconds three x one second A long timeout is 90s three x 30 seconds There...

Page 17: ... 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 over four file serving interfaces for increased bandwidth and incre...

Page 18: ...rio includes a pair or switches connected in such a way 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 ...

Page 19: ...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 server discards 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 NAS server provides two 10 100 1000 Ethe...

Page 20: ...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 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 Remember...

Page 21: ...pports 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 ag...

Page 22: ... 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 ...

Page 23: ...r 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 configuration the NAS uses an exter...

Page 24: ... 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 th...

Page 25: ...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 ...

Page 26: ...onfiguration 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 26 Routing overview Hitachi NAS Platform Network Administration Guide ...

Page 27: ...uting 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 The NAS server supports gateway network and host static routes The Default option sets up a gateway and does not require a d...

Page 28: ...ICMP router discovery is controlled using the CLI command irdp For more information see the Command Line Reference A router learned using IRDP is propagated to the routing table as a default gateway The NAS server discovers IPv6 default gateways through ICMPv6 router advertisements RIP v1 and v2 This is an industry standard enabling servers to automatically discover routes and then update routes i...

Page 29: ...se the current EVS to influence routing decisions With routing by EVS enabled many subsystems such as DNS which normally would not use the EVS to influence routing decisions now would use routing by EVS If routing by EVS is to be enabled in non multi tenant mode it is necessary to use the routing by evs enable command See the CLI reference for routing by evs commands routing by evs enable routing ...

Page 30: ...ame and directory services that the HNAS server can support These services help the server to support the location administration and management of network resources Name services Directory services 30 Name and directory services Hitachi NAS Platform Network Administration Guide ...

Page 31: ...y with the configured DNS servers in both the forward and reverse lookup zones for each configured ADS CIFS name and IP address associated with the EVS Thus the EVS records one entry in DDNS for every configured IP address If a server has more than one configured ADS CIFS name an entry for each IP address for each configured CIFS name is registered Each hostname registered with the DNS server has ...

Page 32: ...NIS for NFS and FTP NIS databases provide simple management and administration of Unix based networks These databases can provide details about users and groups also individual client machines including IP address and host name to facilitate authentication for users logging in to clients on the network The server supports integration with NIS directory services which can provide the following NFS ...

Page 33: ...ections to the LDAP database instead of anonymous access to NIS databases The server supports LDAP version 2 and 3 the default is version 3 including two of the most common LDAP service implementations Oracle Directory Server OpenLDAP Name and directory services 33 Hitachi NAS Platform Network Administration Guide ...

Page 34: ...Using IPv6 This section contains an overview of IPv6 and information on using IPv6 with the NAS server IPv6 overview IPv6 and the NAS server 34 Using IPv6 Hitachi NAS Platform Network Administration Guide ...

Page 35: ...a 64 bit netmask which consists of the 64 leftmost bits of the address which is represented in CIDR format as shown below 2001 db8 64 This represents an address range of 2001 db8 0 0 0 0 0 0 to 2001 db8 0 0 ffff ffff ffff ffff Address resolution IPv6 uses NDP Neighbor Discovery Protocol instead of ARP for address resolution and IRDP for router discovery IPv6 and the NAS server On the NAS server wh...

Page 36: ...rom 2001 db8 220a 480 baac 6fff fe80 5962 icmp_seq 0 time 6 ms 32 bytes from 2001 db8 220a 480 baac 6fff fe80 5962 icmp_seq 1 time 1 ms 32 bytes from 2001 db8 220a 480 baac 6fff fe80 5962 icmp_seq 2 time 1 ms IPv6 and non file serving interfaces On the NAS server an IPv6 address can be configured on the Admin Services Node eth0 or eth1 However on the SMU IPv6 addresses are only configurable on eth...

Page 37: ...tor can use this address to launch the external SMU GUI and it also enables the external SMU to manage a server with an IPv6 Admin Services Node address Using IPv6 37 Hitachi NAS Platform Network Administration Guide ...

Page 38: ... and removing link aggregations and configuring Aggregate Linux interfaces Viewing link aggregations Adding link aggregations Editing link aggregations Deleting link aggregations Configuring LACP Configuring Aggregate Linux interfaces 38 Configuring link aggregation Hitachi NAS Platform Network Administration Guide ...

Page 39: ...s between the NAS server and the network switch For this setting use a network switch that supports the LACP protocol The switch can be configured for either active or passive LACP mode If the LACP timeout period is not long enough adjust it using the CLI By default the NAS server uses short LACP timeouts Ports This field lists the available ge gigabit Ethernet and tg 10 GbE interfaces in use for ...

Page 40: ...gation The options are Normal the server distributes all traffic for a given conversation through one of the physical interfaces in the appropriate aggregation The server s hash and routing functions determine which packets use which physical interfaces For example all traffic for a particular TCP connection is always distributed through the same physical interface unless the link drops However th...

Page 41: ...the interface 4 The Available Ports field lists the available ge gigabit Ethernet and tg 10 GbE interfaces that can be added to the aggregation To add an interface to the aggregation select the check box next to the name of the interface 5 The Use LACP field specifies whether the aggregation uses LACP Select Yes in order to use LACP An aggregation that does not use LACP is called a static aggregat...

Page 42: ... example below aggedit add ag1 tg1 tg2 where ag1 is the aggregation and tg1 and tg2 are the file serving interfaces To view the status of LACP for an aggregation use the lacp command Configuring LACP timeouts To set a short LACP timeout use the lacp set timeout short command as shown in the example below lacp set timeout short ag1 where ag1 is the required aggregation interface To set a long LACP ...

Page 43: ...the following command aggregate linux interface create interface interface For example aggregate linux interface create interface ag1 In this example the HNAS server creates an interface named eth ag1 which uses ag1 to send and receive management traffic Deleting an existing interface To remove an existing interface enter the following command aggregate linux interface delete eth ag interface For ...

Page 44: ...on contains information on configuring adding and deleting VLAN interfaces Adding VLAN interfaces Deleting VLAN interfaces Advanced VLAN interface configuration 44 Configuring VLAN interfaces Hitachi NAS Platform Network Administration Guide ...

Page 45: ...ce create interface ag1 499 Created ag1 vlan0499 For further details on vlan interface create see the CLI Reference 2 Use the vlan interface show command to display the existing VLAN interface names vlan interface show ag1 vlan0433 ag1 vlan0499 For further details on vlan interface show see the CLI Reference 3 Associate IP addresses with the VLAN interfaces using the evs create command Use the evs...

Page 46: ...r ag2 vlan0017 To apply an MTU setting to a specific VLAN interface it is necessary to create a specific configuration for the full interface name of the VLAN For example to change the MTU for VLAN 17 on ag2 create a specific configuration for ag2 vlan0017 and set the required values Before creating a specific VLAN interface configuration use the ifconfig command to view all the names of all avail...

Page 47: ...e name For example ipadv othermtu 9000 p ag2 vlan0017 Alternatively ipadv n 9000 p ag2 vlan0017 For off subnet values ipadv offsubnetmtu offsubnetmtu p VLAN interface name For example ipadv offsubnetmtu 9000 p ag2 vlan0017 Alternatively ipadv o 9000 p ag2 vlan0017 Configuring VLAN interfaces 47 Hitachi NAS Platform Network Administration Guide ...

Page 48: ...ins information on viewing adding and deleting IP addresses for the HNAS server Viewing IP addresses Adding IP addresses Deleting IP addresses Advanced IP configuration 48 Configuring IP addresses Hitachi NAS Platform Network Administration Guide ...

Page 49: ...er File Services IP addresses must be on the public data network Node the IP address associated with the physical cluster node As File and Administrative services can migrate between nodes the Cluster Node IP address communicates with the node instead of a service Port This field contains the interface in use by the IP address agX identifies one of the file serving aggregation interfaces eth agX i...

Page 50: ...and Subnet Mask for the selected interface 5 Verify the settings then click OK to apply the settings or cancel to decline Deleting IP addresses Caution IP address deletion alert Before following the instructions in this procedure ensure that the IP address is not in use Active connections are terminated on removal and clients can become unresponsive Procedure 1 Navigate to Server Settings EVS Mana...

Page 51: ...less than 1280 TCP Keep Alive Yes filled When selected this option instructs the system to send a keep alive packet when it has received no data or acknowledgment packets for a connection within the specified timeout period TCP Keep Alive timeout seconds 7200 This field specifies the number of seconds to keep alive a connection TCP MTU bytes 1500 This field specifies the size of the maximum transm...

Page 52: ...ields in the Global Settings area All aggregations interfaces use the global settings by default Click apply to save the changes To restore the global settings to the factory default values click reset Interface settings To customize settings for an individual interface select the interface in the Ports field and click customize The Advanced IP Per Port Configuration page appears The following tab...

Page 53: ...ipadv command in order to view or change these settings It is also possible to configure an MTU value on a per route basis using the mtu command Configuring IP addresses 53 Hitachi NAS Platform Network Administration Guide ...

Page 54: ... section contains information on configuring default gateways static IP routes and dynamic IP routes Viewing IP routes Adding IP routes Deleting IP routes 54 Configuring routes Hitachi NAS Platform Network Administration Guide ...

Page 55: ...r a Network route this field displays the IP address and Address Prefix Length of the destination For a Host route this field displays an IP address only Gateway This field displays the gateway IP address of the route Type This field displays the type of route which can be Host Network or Gateway Creation Type A route is either static or dynamic Static indicates a manually created route and dynami...

Page 56: ...he route MTU This field requires the Maximum Transmission Unit which is the largest size Ethernet frame that the HNAS server can send for this route This is an optional field Note Fields which are not required for a route type are grayed out and cannot be configured Deleting IP routes To delete an IP route Procedure 1 Navigate to Network Configuration IP Routes 2 Select the check box next to the r...

Page 57: ...Configuring routes 57 Hitachi NAS Platform Network Administration Guide ...

Page 58: ... on specifying and prioritizing name services and configuring NIS and LDAP servers Specifying name services Prioritizing name services Configuring NIS servers Configuring LDAP servers 58 Configuring name and directory services Hitachi NAS Platform Network Administration Guide ...

Page 59: ...Specifying name services To specify name services Configuring name and directory services 59 Hitachi NAS Platform Network Administration Guide ...

Page 60: ...the EVS individual security context to make changes even if those settings are the same as the settings used by the global security context Click change to select a different EVS security context or to select the global configuration DNS Servers Specifies the IP addresses of up to three DNS servers If more than one DNS server is entered the search will be performed using the DNS servers in the ord...

Page 61: ... on the Name Services Order page Prioritizing name services To change the priority of the name services Procedure 1 Navigate to Network Configuration Name Services order 2 Use the change button to change the security context if required Changes to the name services on this page apply only to the currently selected EVS security context If an EVS uses the Global Configuration any changes made to the...

Page 62: ...y to save the changes Configuring NIS servers Before using NIS it is necessary to enable NIS for the HNAS server To enable NIS navigate to Network Configuration NIS LDAP Configuration and click Enable NIS The current NIS configuration settings appear as shown in the following example This page contains the following options Modify this option enables the Administrator to change the NIS configurati...

Page 63: ... table below Field Item Description EVS Security Context This field displays the currently selected EVS security context Changes to the name services on this page apply only to the currently selected EVS security context If an EVS uses the Global Configuration any change made to the global configuration settings affects the EVS If an EVS uses an individual security context changes made to the glob...

Page 64: ...server which can satisfy NIS queries Priority Enter the priority level for the selected NIS server lowest value is highest priority If the NIS domain contains multiple servers the system attempts to bind to the server with the highest priority level whenever it performs a rebind check Note Servers discovered by broadcast do not have a priority If the Administrator assigns a priority after clicking...

Page 65: ... options Modify this option enables the Administrator to change the LDAP configuration settings Add this option enables the Administrator to add a new LDAP server Delete this option enables the Administrator to remove an existing LDAP server Switch to using NIS this option enables NIS only mode and displays the NIS configuration settings Disable NIS and LDAP this option disables NIS and LDAP CLI c...

Page 66: ...rk Configuration NIS LDAP Configuration 2 Click modify 3 Modify the settings as described in the table below Field Item Description Domain Enter the name of the LDAP domain for which the system is a client Username This field contains the username of the Administrator for the LDAP servers The name can be up to 256 characters in length However if it includes spaces the name must be enclosed in doub...

Page 67: ...erver The default value is 389 TLS Port This field specifies the secure port to use for communication with the LDAP server The default value is 636 4 Click OK Note An Administrator can query the LDAP server for information about hosts configured into netgroups using the nis is host in netgroup and nisnetgroups for host commands Deleting LDAP servers To delete an LDAP server Procedure 1 Navigate to...

Page 68: ...formation on configuring non file system interfaces and managing system devices using the SMU Configuring non file serving interfaces Configuring devices on the system monitor 68 Managing networks and devices Hitachi NAS Platform Network Administration Guide ...

Page 69: ...rface The default address for the eth1 interface is 192 0 2 1 The eth1 address must end with 1 in order to simplify the management relationship of the SMU with secondary devices The NAT Port range is provided for information only 3 Once defined record the IP address settings separately for future reference and click apply Configuring devices on the system monitor The system monitor allows you to e...

Page 70: ...following table list the basic components that make up a HNAS system This table indicates what happens when you click on a component s name in the component list Component Description Clicking the component Clicking the details button Storage Server This component provides Ethernet interfaces for connecting to the Public Data Network and the Private Management Network as well as Fibre Channel inte...

Page 71: ...automatically discovered and added to the Status Monitor Loads the NDMP Devices page Loads the NDMP Details page for the device if the device can be contacted or loads the NDMP Device List page if the device cannot be contacted FC Switches FC switches and cables connect FC devices generally storage arrays to the server s Note Upon adding an FC switch through the FC Switches page it is automaticall...

Page 72: ...ivate management network are hidden from the data network through Network Address Translation NAT Once a device has been added to the System Monitor clicking its name in the System Monitor Opens its embedded management utility in the Web browser using either HTTP HTTPS or Telnet The SMU periodically checks for device activity and connectivity with the server if a device fails to respond to network...

Page 73: ...Managing networks and devices 73 Hitachi NAS Platform Network Administration Guide ...

Page 74: ...nformation on checking the network status of the HNAS server and also how to detect any potential issues Network health information Detecting issues Collecting network packets 74 Troubleshooting Hitachi NAS Platform Network Administration Guide ...

Page 75: ...ntains network information on a per aggregation basis for example ag1 ag2 Ethernet Statistics per port Physical ports this page contains network information on a per physical port basis for example tg1 tg2 Navigate to the Network Configuration Ethernet Statistics per port page in order to view the Aggregation ports page On this page there is a link to the Ethernet statistics per port Physical port...

Page 76: ...display information on the current network health status agg this command lists any existing aggregations ethernetstats this command displays statistics for each Ethernet interface tcpstats this command displays statistics for TCP protocol packets udpstats this command displays statistics for UDP protocol packets ip stats other this command displays statistics for all other IP protocol packets icm...

Page 77: ...rfaces 200 MMBNetwork interfaces link status network remote nfs 270 MMB RemoteNFS network nisclient 280 MMB Nisclient status network wins 290 MMB UnreachableWINS servers network ip eng adv 300 MMB ipeng ipadv status network mac cluster 340 MMB MAC_10status network mac network 340 MMB MAC_1status network external migration protocol errors 350 MMB External migration protocol errors network packet ca...

Page 78: ...um size of 32MB or 15000 frames whichever is reached first To retrieve this file use the nail command to email it to a user Alternatively use the ssget command to send it to the SMU for later collection The ssget command works from an ssc connection and therefore is usable locally or on a server connected to an external SMU To analyze the file contents the following filter applications are support...

Page 79: ...formance is severely degraded during packet capture It is recommended to use port mirroring on the upstream switch instead of using the packet capture command on the NAS server Troubleshooting 79 Hitachi NAS Platform Network Administration Guide ...

Page 80: ...d VLANs into the new static VLANs The following procedure describes how to run the script and convert the VLANs The procedure has three stages Accessing the NAS Linux console Retrieving and running the script Converting a subnet VLAN Accessing the NAS Linux console The script does not run under the NAS CLI but is available on the NAS platform from version 12 2 through the Linux console To access t...

Page 81: ...e script prompts for the password without displaying the entered text On the NAS Linux console only When executing the script on the NAS Linux console the name localhost can be used to identify the NAS server In this case it is normally not necessary to supply the username and password For example opt mercury utils bin vlan convert config rb localhost tmp vlan conv commands Converting a subnet VLA...

Page 82: ...esses in VLANs from still enabled EVS before updating the configuration This applies to EVS with non VLAN address assignments in order to minimise disruption to non VLAN services echo Removing VLAN IP addresses from EVS prior to re configuration Remove the address 172 31 61 61 24 on ag1 from EVS 2 evs2 evsipaddr e 2 remove confirm ip 172 31 61 61 Remove existing legacy VLAN configuration vlan remo...

Page 83: ...e confirm ip 172 31 61 61 Warning Removing IP address 172 31 61 61 while EVS is ONLINE hnas hnas Remove existing legacy VLAN configuration hnas vlan remove all hnas hnas Create new VLAN interfaces hnas Processing address 172 31 62 62 24 for ag1 vlan0200 hnas vlan interface create interface ag1 200 Created ag1 vlan0200 hnas Processing address 172 31 61 61 24 for ag1 vlan0100 hnas vlan interface cre...

Page 84: ... EVS 137 NetBIOS name lookup service including WINS UDP EVS 139 SMB CIFS over NetBIOS TCP EVS 161 SNMP agent UDP Admin Service node Cluster node and EVS 202 VSS TCP Admin Service node and optionally EVS 206 SSC TCP Admin Service node Cluster node and optionally EVS 443 HTTPS SMU GUI TCP Admin Service node and Cluster node 445 SMB over TCP TCP EVS 762 rquota TCP UDP EVS 1344 ICAP AV TCP EVS 2049 NF...

Page 85: ...P Only available on the non file serving interfaces Configur able Loopback NFS TCP UDP Only available on the non file serving interfaces NAS as a client The NAS server uses these destination ports on a peer server Port Protocol 25 SMTP TCP 53 DNS TCP UDP 88 Kerberos TCP UDP 123 NTP UDP 139 SMB CIFS over NetBIOS TCP 162 SNMP traps UDP 389 LDAP TCP UDP 445 SMB over TCP TCP 464 Kerberos Password Chan...

Page 86: ... SNMP trap receiver UDP 443 HTTPS GUI TCP 59515 59536 Quorum device UDP External SMU as a client The external SMU uses these destination ports on a peer server Port Protocol 25 SMTP relay TCP 123 NTP UDP 8443 SOAP requests to HNAS TCP 2001 HCS device manager updates TCP 86 Network ports Hitachi NAS Platform Network Administration Guide ...

Page 87: ...Network ports 87 Hitachi NAS Platform Network Administration Guide ...

Page 88: ...Hitachi NAS Platform Network Administration Guide ...

Page 89: ... Street Santa Clara California 95050 2639 U S A www hds com Regional Contact Information Americas 1 408 970 1000 info hds com Europe Middle East and Africa 44 0 1753 618000 info emea hds com Asia Pacific 852 3189 7900 hds marketing apac hds com MK 92HNAS008 08 ...

Reviews:

No comments

Related manuals for 3100

Brand: D-Link Pages: 29

DGS-3700 Series

Brand: D-Link Pages: 292

Brand: D-Link Pages: 140

DGS-1224T - Web Smart Switch

Brand: D-Link Pages: 61

DI-LB604 - Load Balancing Router

Brand: D-Link Pages: 14

Brand: D-Link Pages: 2

Brand: D-Link Pages: 45

Brand: D-Link Pages: 218

DES-3528 - xStack Switch - Stackable

Brand: D-Link Pages: 322

DIR-130 - Broadband VPN Router

Brand: D-Link Pages: 10

DIR-130 - Broadband VPN Router

Brand: D-Link Pages: 4

DIR-130 - Broadband VPN Router

Brand: D-Link Pages: 13

Brand: D-Link Pages: 13

DI-804HV - Express ENwork Router

Brand: D-Link Pages: 19

Brand: D-Link Pages: 12

Brand: D-Link Pages: 8

Brand: D-Link Pages: 16

Brand: D-Link Pages: 7

Brands by name

0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Popular brands

Load more brands