Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
PowerScale: Network Design Considerations
Executive summary Network architecture design Latency, bandwidth, and throughput Ethernet flow control SyncIQ considerations Quality of Service (QoS) Software-Defined Networking PowerScale OneFS ports SmartConnect considerations Ethernet, MTU, and IP overhead Access Zones best practices
Introduction
System Zone
Root-based path
Source-Based Routing considerations Isilon 6th generation 1 GbE interfaces Intelligent Platform Management Interface IPv6 OneFS host-based firewall Network troubleshooting Appendix A: Supported network optics and transceivers Appendix B: Technical support and resources

System Zone

System Zone

  • When a PowerScale cluster is first configured, the System zone is created by default. The System zone should only be used for management as a best practice. In certain special cases, some protocols require the system zone, but generally speaking, all protocol traffic should be moved to an access zone. If nothing else, NFS and SMB should have protocol-specific access zones.

    Moving client traffic to access zones ensures that the System zone is only used for management and accessed by administrators. Access zones provide greater security because administration and file access are limited to a subset of the cluster, rather than the entire cluster.