NetAct Hardware Configuration Guide (NetAct22)
NetAct Hardware Configuration Guide (NetAct22)
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be used except for the purposes
defined in the agreement between You and Nokia Solutions and Networks (“Agreement”) under which this document is distributed. No part of
this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia
Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been
terminated, You may not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or
delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when
using it. Nokia Solutions and Networks welcome Your comments as part of the process of continuous development and improvement of the
documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia
Solutions and Networks reserves the right to change any such information and statements without notice. Nokia Solutions and Networks has
made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia
Solutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in
the document is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the use of the software
in the Product will be uninterrupted or error-free.
This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not be distributed or disclosed to any
third parties without the prior written consent of Nokia Solutions and Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like
to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging
and follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia
Solutions and Networks for any additional information.
NetAct Hardware Configuration Guide D565912996 4-0 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Purpose.............................................................................................................................................................6
5 Appendix.........................................................................................................................................................17
5.1 Hardware changes for previous releases............................................................................................... 17
5.1.1 Hardware changes for NetAct 19................................................................................................... 17
5.1.1.1 Firmware and hardware recommendations............................................................................17
5.1.1.2 Increase in VMGuestDisk size............................................................................................... 17
5.1.1.3 End of support for EMC VNX 5100 and 5300 Storages........................................................ 17
5.1.1.4 End of support for HPE P2000 (MSA 2000) Storage............................................................ 17
5.1.2 Hardware changes for NetAct 18A.................................................................................................17
1 Summary of changes
Date Version Summary of changes
2 Purpose
NetAct Hardware Configuration Guide is a single reference document to all NetAct hardware
configuration documents.
This document includes the best practices to be followed to configure NetAct supported Data
Communication Network (DCN), Storage and Server configurations.
Every NetAct release has its own specific supported hardware and it is recommended that you verify
them. For more information on system cabling, see NetAct System Cabling Guide.
Integrating DCN Backbone to NetAct document aims to help the installation engineer in integrating the
switches and routers that are part of the DCN backbone to NetAct. Select the NetAct version you want
to install, for example, NetAct 20. See NetAct Operating Documentation -> Integration -> Integrating
DCN backbone to NetAct document for more information.
Note: To use configuration templates for the DCN backbone devices, see NetAct DCN
templates.
Note:
Ensure that you have completed the procedures described in the above chapters before
proceeding for storage configurations. For more information, see Configuring Storage Area
Network.
This document covers examples on how to configure EMC VNX5300 and EMC VNX5200 storage
systems for NetAct system usage. The document includes disk layout, pool and/or raid group definition
and LUN configuration for all typical storage array sizes.
This document provides default storage array configurations for a NetAct system. NetAct internal disk
configuration is not in the scope of this document. For more information, see Installing and Configuring
EMC Storage Array with Unisphere.
This document provides default storage array configurations for a NetAct system with EMC Unity
storages. For more information, see Installing and Configuring EMC Unity Storage.
Note: NetAct internal disk configuration is not in the scope of this document.
For integrating EMC Unity storages to HP SIM, see Integrating Unity Storage with HP SIM.
This document is meant for large variety of NetAct products and all product-specific storage
configuration details – such as the number of LUNs, input and output (I/O) path load balancing, and
LUN sizes – are only examples.
For more information on installing and configuring HP storages see Installing and Configuring HP
3PAR Storeserv 7200 and 8200 Storage.
This document covers examples on how to configure 3PAR StoreServ 7200 storage systems for
NetAct system usage. Document includes the detailed definition of Virtual Volumes configuration for all
typical storage array sizes. For more information, see HP 3PAR Provisioning Sample for NetAct.
The disk array configurations in this document includes different types of storages. It is highly
recommended to check the specific storage models supported in every NetAct release.
This document covers examples on how to configure EMC VNX5300, EMC VNX5200, EMC Unity
All Flash Array, EMC Unity 380/380F, EMC Unity 480F, HPE MSA 2040 and 3PAR StoreServ 7200
storage systems for NetAct system usage. For more information, see Storage Array Disk Configuration
Guide for NetAct. The document includes disk layout, pool and/or raid group definition and LUN
configuration for all typical storage array sizes.
• Storage Array Disk Configuration Guide for EMC VNX5200 with 1TB NL-SAS Vault Disks
• Storage Array Disk Configuration, Using SSD disks for Redo
• Installation Instructions for Extending Virtual Disks
• Resizing Backup Disks
• Storage Improvement Requests for EMC Storages
• EMC LUN Migration
• HP Storage Swap Best Practices
3.12 Storage Array Disk Configuration Guide for NetAct 16.x with
Cloning
This document provides a storage array configuration for a NetAct system with cloning. NetAct internal
disk configuration is not in the scope of this document.
This document covers examples on how to configure EMC VNX5300, EMC VNX5200, EMC VNX5400,
3PAR StoreServ 7200 and 8200 storage systems for NetAct 8 to 16.x systems with cloning usage. The
document includes disk layout, pool and/or raid group definition and LUN configuration for all typical
storage array sizes. For more information, see Storage Array Disk Configuration Guide for NetAct 16.x
with Cloning.
3.13 Storage Array Disk Configuration Guide for NetAct 17.x NZDT
Upgrade
Storage Array Disk Configuration Guide for NetAct 17.x NZDT Upgrade document provides storage
array configuration disk layout and LUN information for the latest NetAct NZDT upgrades (Upgrade
with Cloning). NetAct internal disk configuration is not in the scope of this document.
This document covers examples on how to configure EMC VNX5200, EMC VNX5400, EMC Unity All
Flash Array, 3PAR StoreServ 7200 and 8200 storage systems for latest NetAct system with cloning
usage.
The document includes disk layout, pool and/or raid group definition and LUN configuration for various
NetAct configurations. For more information, see Storage Array Disk Configuration Guide for NetAct
17.x NZDT Upgrade.
Make sure you are completed the configurations of NetAct System Power cabling Guide,
NetAct System Cabling Guide, Integrating DCN Backbone to NetAct guide, and Storage
specific configurations mentioned in the above chapters before proceeding the Server
configurations.
This document is a set of non-binding system racking recommendations you can refer to if you need to
do a site change before or after new hardware is installed. You can also use your own site layout if it
better meets the needs of the customer. For more information, see NetAct System Racking Guide.
This document is meant for NetAct in OpenSAN concept and all product-specific HP Virtual Connect
Fibre Channel Module configuration details – such as type, number and layout of fibre channel module
– are only examples.
In every NetAct release there are specific supported hardware, it is highly recommended to verify what
those are. For more information, see Installing and Configuring HP Virtual Connect Fibre Channel
Module for c-Class BladeSystem.
For example, when you add new hosts to your existing NetAct cluster, you can migrate your virtual
machines to new server and remove your older server. Thus enabling EVC helps in reusing HP BL
460c Gen8, HP BL 460c Gen9 hardware from previous NetAct installations with mixed HP BL 460c
Gen8, HP BL 460c Gen9 and HP BL 460c Gen10.
Detailed steps mentioned in the below sections of each devices supported by NetAct for IPv6
configuration. For more information, see IPv6 support on Hardware Devices.
EMC Unity 480F provides capacity support for future NetAct releases.
EMC Unity 380F is a life cycle-driven replacement of EMC Unity 350F with similar performance
characteristics.
EMC Unity 380 is a life cycle-driven replacement of EMC Unity 300 array used for NetAct backup
storage.
• The LUN size of VMGuestDisk (1-3) used in NetAct XXL configuration is increased from 1250 GB
to 1350 GB.
• The LUN size of VMGuestDisk (1-3) used in NetAct 3XL configuration is increased from 1250 GB
to 2000 GB.
Note: Support to HPE Synergy 12000 Frame is introduced through NetAct 20 SP880
release.
HPE Synergy Frames for NetAct includes 12 Synergy 480 Gen10 servers for compute pourpose. Each
Synergy 480 Gen10 servers contains 2P16C processor with 384GB RAM.
Ethernet networking uses Virtual Connect SE 100Gb F32 Module for Synergy Ethernet Connections
for HPE Synergy which provides 25/50G bandwidth across the servers within the chassis and
maximum of 40G speed for the external traffic. Comparing with the HPE c7000 chassis HPE Virtual
Connect configuration, in synergy HPE Virtual Connect runs as Active-Active configuration and
this requires physical cabling between both the HPE VC ports using HPE VC Cluster ports Q7-Q8
(100Gb) .
SAN Connectivity uses Brocade 32G Fibre Channel SAN Switch for HPE Synergy which provides 32G
speed for the SAN access and external access with 16G speed.
Composer2 embedded management appliance on Synergy runs the Embedded HPE OneView
as clustered mode. High availability of Composer2 manages HPE OneView to run when the other
Composer goes down. HPE OneView supports Integrated management for compute, fabrics,
and storage (HPE storages only). Logical enclosures and logical interconnects control the new
interconnect links between a set of connected frames.
In NetAct 20, the backup storage is dimensioned to support three configurations. One with minimum
disk requirements in NetAct 20, the second with minimum disk requirements in NetAct 20 including
VDP to AVE migration, and the third with recommended disk requirements to accomodate future
capacity requriements of NetAct releases. The recommended configuration also includes the
additional capacity that is required for creating temperory LUN during VDP to AVE migration.
Customers can choose any one of the configurations based on their storage models and NetAct
upgrade plans.
5 Appendix
• Appendix1: Storage Array Disk Configuration Guide for EMC VNX5200 with 1TB NL-SAS Vault
Disks
• Appendix2: Storage Array Disk Configuration, Using SSD disks for Redo
• Appendix3: Installation Instructions for Extending Virtual Disks
• Appendix4: Resizing Backup Disks
• Appendix5: EMC LUN Migration
• Appendix6: HP Storage Swap Best Practices
• Appendix7: 3PAR Storage Sizing Rules
5.1.1.3 End of support for EMC VNX 5100 and 5300 Storages
Support for ENC VNX1 (VNX5100 and VNX5300) is removed from NetAct 19 release onwards as it
has reached end of support.
From NetAct 18A onwards, the Installation and upgrade instructions for EMC VNX 5200 and 5400
extra large configuration document is not provided to customers.
5.1.2.3 NetAct EMC VNX 5400 XXL and EMC UNITY 350 XXL Storage configuration support
NetAct 18A supports new NetAct EMC VNX 5400 XXL and EMC UNITY 350 XXL storage
configuration.
Note: For more information on XXL storage configuration, see NetAct hardware section
under NetAct Operating Documentation → System Overviews → NetAct deployment
and configurations document in Support Portal.
Note: For support to Gen10 servers, you must have NetAct 18A.
The below mentioned table contains the number of new HPE ProLiant Gen10 servers required for
different NetAct configurations:
NetAct Compact 2 x HPE DL360 Gen10 servers with 2p16c CPU and 384GB
RAM
NetAct Small 4 x HPE BL460c Gen10 servers with 1p16c CPU and
192GB RAM
NetAct Mainstream 4 x HPE BL460c Gen10 servers with 2p16c CPU and
384GB RAM
NetAct Large and XXL 5 x HPE BL460c Gen10 servers with 2p16c CPU and
384GB RAM
Table 2: HPE ProLiant Gen10 Server details for different NetAct configurations
Note: For more information on new Gen10 hardware configuration, see NetAct hardware
section under NetAct Operating Documentation → System Overviews → NetAct
deployment and configurations document in Support Portal.
Table 3: EMC Unity 300 Hybrid backup storage support for NetAct configurations
Note: For more information on HP MSA 2050 backup storage configuration, see NetAct
hardware section under NetAct Operating Documentation → System Overviews →
NetAct deployment and configurations document in Support Portal.
The samples covered in this document are for EMC VNX 5200 NetAct layout configuration. See
Storage Array Disk Configuration Guide for EMC VNX5200 with 1TB NL-SAS Vault Disks
5.3 Appendix2: Storage Array Disk Configuration, Using SSD disks for
Redo
This document gives configuration options and instructions how to modify the default EMC VNX
storage configurations so that redo is using SSD disks. At the current default NetAct storage
configurations redo is configured to a raid group made from the vault disks. For most of the NetAct
installations this default storage configuration is acceptable and will give enough performance. In
some cases if there is doubt about the performance or database activity is known to be very high
then using SSD disks for redo is one possible option to increase DB performance. But if performance
bottleneck is somewhere else than in the redo then this will not give any remarkable improvements.
The instructions at this document give guidance how to make additions and modifications to the
NetAct standard configurations and then how to use that information in the ordering and storage
configuration phases. For more information, see Storage Array Disk Configuration, Using SSD disks
for Redo.
1. Extending LUN on the storage system. However steps to add disks to the storage system are not
in scope of his document.
2. Extending datastore on the VI layer
3. Extending virtual disks (vmdk) or adding virtual disks to the VM
4. Extending or adding physical volume
5. Extending volume group
6. Extending logical volume
7. Extending file system
For more information, see Installation Instructions for Extending Virtual Disks.
The procedures in this document pertain to adding and removing virtual disks when switching from
bigger disks to smaller disks that are mounted in the systems. For more information, see NetAct
Backup Sizing Guidelines.
The LUN Migration means move of a LUN within the storage system from one location to another.
With this feature, it is possible to solve both capacity and performance bottlenecks at the system by
reorganizing raid groups and LUNs. With LUN migration it is possible to move LUN to:
• bigger LUN
• different types of disks
• different RAID type
• move LUN’s from SATA disks to FC disks after OSS5 to NetAct 8 upgrade at the EMC CX4 series
storages
• reorganize and resize LUN’s after storage extension
• move LUN’s to faster or slower disks if there are performance issues at the storage
• Extend LUN size
LUN migration is done at background and it is non-intrusive and transparent to the servers. There
is four possible speed settings (Low, Medium, High and ASAP) of the migration process. High is the
default value and ASAP is not recommended if the system is used during the migration. LUN migration
process can take quite long time even with the highest speed setting. For more information, see EMC
LUN Migration.
For more information, see HP 3PAR Storage Sizing and Consolidation Rules.