- Notes, cautions, and warnings
- Revision history
- Introduction
- Revision history
- Administering the network
- Customer switch port configuration examples
- Configuration data
- Configuring the Cisco Nexus access aggregation network
- Configuring the Dell EMC PowerSwitch access switches
- Using an embedded operating system-based jump server
- Install the embedded operating system-based iDRAC tools
- Converting the Windows jump VM to the embedded operating system jump VM
- Verifying connectivity between Storage Data Server (SDS) and Storage Data Client (SDC)
- Verifying connectivity between Storage Data Server (SDS) and PowerFlex Gateway
- Checking the maximum transmission unit on all switches and servers
- Adding a network to the deployed service using PowerFlex Manager
- Add a network to a service
- Add a VLAN to an access switch connected to a PowerFlex appliance cluster
- Verifying a VLAN configuration
- Gather logs from the network switch for troubleshooting
- Customer switch port configuration examples
- Upgrade the Dell EMC network
- Check the current version of switch operating system
- Save the license file and the configuration
- Download Dell EMC Networking OS10
- Connect to a switch
- Configure a USB drive for OS10 installation
- Manual install using USB
- Upgrade OS10 image from existing OS10 install
- Upgrade from non-OS10 operating system to OS10 using ONIE
- Install OS from ONIE
- Update ONIE using an existing ONIE and TFTP
- DIAG OS installation or update
- Install or upgrade EDA-DIAG tools
- Firmware requirements
- Verify Dell switch firmware
- IP address assignment in ONIE
- Administering the storage
- PowerFlex management controller datastore and virtual machine details
- Determining and switching the MDM
- Update resource inventory
- Add volumes to the service
- Add volumes to a service in lifecycle mode
- Adding a PowerFlex appliance node to an existing cluster
- Removing a PowerFlex node for maintenance
- Rebooting a PowerFlex node
- Resize a volume
- Resize a volume in lifecycle mode
- Unmapping a volume
- Unmap a volume on PowerFlex management controller 2.0
- Unmapping a volume using a PowerFlex version prior to 3.5
- Removing a volume
- Remove a volume on the PowerFlex management controller 2.0
- Removing a volume using a PowerFlex version prior to 3.5
- Disabling persistent checksum on medium granularity storage pools
- Enabling persistent checksum for medium granularity storage pools
- Enable fine granularity metadata read cache using the command line
- Add licenses to PowerFlex and PowerFlex Manager
- Managing volumes, nodes, and network components
- Monitoring system health
- Upgrading PowerFlex appliance firmware
- Upgrade Windows and Linux compute-only nodes
- Mapping a volume using a PowerFlex version prior to 3.5 to a Windows PowerFlex compute-only node
- Mapping a volume using Windows PowerFlex compute-only node
- Enabling and disabling SDC authentication
- Administering the storage with asynchronous replication
- Remote replication on PowerFlex hyperconverged nodes
- Remote consistency group (RCG)
- Replication direction and mapping
- Adding a replication consistency group
- Checking the current copy status
- Modifying the recovery point objective
- Adding a replication pair to a remote consistency group
- Unpairing from a remote consistency group
- Freezing a remote consistency group
- Unfreezing a remote consistency group
- Setting the target to inconsistent mode
- Setting the target to consistent mode
- Running a test failover
- Stopping test failover
- Running a failover
- Restoring replication
- Reversing replication
- Creating a snapshot of the remote consistency group (RCG) volume
- Pausing the remote consistency group
- Pausing the initial copy
- Resuming the initial copy
- Resuming the replication consistency group
- Setting priority
- Mapping remote consistency groups to the Storage Data Clients (SDC)
- Mounting a VMFS datastore copy on the target VMware ESXi cluster
- Unmapping an Storage Data Client (SDC) from the remote consistency group target volumes
- Configuring replication on PowerFlex storage-only nodes
- Add storage data replication to PowerFlex
- Extract and add the MDM certificate
- Create the replication consistency group
- Disabling replication on PowerFlex storage-only nodes
- Freeze the remote consistency group
- Remove the remote consistency group
- Remove a peer system
- Remove replication trust for peer system
- Enter SDS in maintenance mode
- Remove storage data replication from PowerFlex
- Remove a storage data replication RPM
- Clean up network configurations
- Exit SDS in maintenance mode
- Remove journal capacity
- Remove target volumes from the destination system
- Configuring and viewing alerts
- Administering PowerFlex Manager
- PowerFlex Manager limits
- Back up and restore
- Add or modify user accounts
- Assigning users to services
- Recovering a lost password
- Access switch password management
- VMware vCenter password management
- VMware ESXi operating system password management
- Minimum VMware vCenter permissions
- Windows server operating system password management
- Updating passwords in PowerFlex Manager
- Embedded operating system password management
- Presentation server root password management
- Red Hat Enterprise Linux user and password management
- SUSE user and password management
- Credentials management
- Restarting the PowerFlex Manager virtual appliance
- Deploying PowerFlex nodes using PowerFlex Manager
- Deployment modes
- Full network automation
- Full network automation: Deploying a PowerFlex compute-only node with Red Hat Enterprise Linux or CentOS
- Full network automation: Deploying a PowerFlex storage-only node
- Full network automation: Deploying a VMware ESXi PowerFlex hyperconverged node or PowerFlex compute-only node
- Adding volumes to a PowerFlex hyperconverged node or PowerFlex compute-only node
- Partial network automation
- Partial network automation: Deploying a PowerFlex compute-only node with Red Hat Enterprise Linux or CentOS
- Partial network automation: Deploying a PowerFlex storage-only node
- Partial network automation: Deploying a VMware ESXi PowerFlex hyperconverged node or PowerFlex compute-only node
- Adding volumes to a PowerFlex hyperconverged node or PowerFlex compute-only node
- Restoring the PowerFlex Gateway
- Configure SNMP for PowerFlex Gateway
- Installing the PowerFlex Gateway
- Installing the PowerFlex Gateway prior to PowerFlex 3.5
- Changing the root password on the VM
- Configuring the PowerFlex Gateway network interfaces
- Configuring the PowerFlex Gateway NTP client
- Configuring the PowerFlex Gateway hostname
- Installing the Java and PowerFlex Gateway RPMs
- Restoring the PowerFlex Gateway configuration
- Deploying the PowerFlex GUI presentation server
- Linking and unlinking the MDM to the presentation server web UI
- Upgrading VMware vCenter
- Upgrading VMware vCenter infrastructure management components
- Stage and upgrade the iDRAC and firmware
- Shutting down all the VMs running on the controller host
- Upgrading VMware vSphere ESXi
- Powering on all the VMs running on the controller host
- Upgrading the iDRAC service module
- Change the SVM CPU clock reservation
- Migrating vCLS VMs on controller nodes
- Upgrading the embedded operating system jump VM
- Installing the offline repository
- Upgrading a PowerFlex appliance environment
- Intelligent catalog (IC) trains and the upgrade process
- Verify and change the maximum transmission unit (MTU) value
- Add a new compatibility management file
- Upgrade the PowerFlex Manager virtual appliance
- Back up using PowerFlex Manager
- Back up the appliance SSL and trusted certificates
- Power off the PowerFlex Manager appliance
- Take a snapshot of the PowerFlex Manager appliance
- Upgrading the PowerFlex Manager virtual appliance without using Secure Remote Services (from a local repository path)
- Confirming service settings
- Adding a new Intelligent Catalog file and OS images to PowerFlex Manager
- Upgrade the PowerFlex presentation server
- Upgrade CloudLink Center
- Upgrading PowerFlex
- Update PowerFlex appliance nodes
- Migrating VMware vSphere Cluster Services (vCLS) VMs
- Upgrading Cisco NX-OS 7.x to Cisco NX-OS 9.x
- Upgrading the electronic programmable logic device (EPLD)
- Upgrade firmware for IPI G5 network controller
- Upgrading VMware NSX-T Edge nodes
- Stage and upgrade the iDRAC and firmware
- Validate the vSAN health
- Shut down all the VMs on the NSX-T Edge Gateway host
- Put VMware NSX-T Edge Gateway host into maintenance mode
- Upgrade VMware vSphere ESXi
- Exit maintenance mode
- Power on all VMs running on the VMware NSX-T Edge Gateway host
- Upgrade the iDRAC service module
- Upgrade the VMware vSphere Distributed Switch
- Upgrade the VMware vSAN disk format (vSAN storage option only)
- Verifying VMware vSAN health (vSAN storage option only)
- Enable replication on existing PowerFlex hyperconverged nodes
- Prerequisites
- Workflow
- Remove an existing PowerFlex hyperconverged service from PowerFlex Manager
- Create and configure replication port groups
- Preparing the SVMs for replication
- Enter the SDS nodes into maintenance mode and power off
- Add virtual NICs to SVMs
- Record the MAC address of the newly added network interface controllers
- Modifying the vCPU, memory, vNUMA and CPU reservation settings on SVMs
- Modify the memory size
- Increase the vCPU count
- Setting the vNUMA advanced option
- Set the vNUMA advanced option
- Modifying the memory size according to the SDR requirements for FG pool-based PowerFlex systems with replication
- Increasing the vCPU count according to the SDR requirement
- Setting the vNUMA advanced option
- Editing the SVM configuration
- Powering on the SVM and configuring network interfaces
- Install SDR RPMs on the SDS nodes (SVMs)
- Exit SDS maintenance mode
- Verify communication between the source and destination
- Add journal capacity percentage
- Adding the Storage Data Replicator to a PowerFlex appliance
- Create the peer system between the source and destination site
- Add the peer system
- Create the replication consistency group
- Define the network for replication in PowerFlex Manager
- Add an existing service to PowerFlex Manager
- Retrieving PowerFlex performance metrics
- Performing maintenance activities in a PowerFlex cluster
- Administering the CloudLink Center
- Adding and managing CloudLink Center licenses
- Manage a self-encrypting drive (SED) from CloudLink Center
- Manage a self-encrypting drive from the command line
- Release a self-encrypting drive
- Release management of a self-encrypting drive from the command line
- Changing the CloudLink secadmin user password
- Unlocking the CloudLink secadmin user
- Setting CloudLink Vault passcodes
- Back up and restore CloudLink Center
- Powering off and on the PowerFlex appliance cluster
- Power off the PowerFlex management controller 2.0
- Power on the PowerFlex management controller 2.0
- Powering off a PowerFlex appliance hyperconverged cluster
- Powering on a PowerFlex appliance hyperconverged cluster
- Powering off PowerFlex appliance two-layer cluster
- Powering on PowerFlex appliance two-layer cluster
- Powering off PowerFlex compute-only nodes with Windows Server 2016 or 2019
- Powering off PowerFlex compute-only nodes with Red Hat
- Ports and authentication protocols
- Additional documentation
Dell EMC PowerFlex Appliance Administration Guide
Intelligent catalog (IC) trains and the upgrade process
NOTE During the storage-only service upgrade, the
/home partition is removed and the
root partition is resized.
PowerFlex Manager deletes any data that is present under
/home of the
PowerFlex storage-only node.
An Intelligent Catalog (IC) is a catalog of a storage, firmware, and drivers that have been engineered and validated together. Staying on an engineered IC reduces the chance of a system outage due to conflicting components or other problems such as, known issues.
A new IC train is created when major version changes occur.
NOTE IC jumps greater than two are considered high risk. Contact
Dell Technologies Support before proceeding.
To upgrade to a new IC train, you first upgrade to the end of the IC train on which your system resides, and then upgrade to the new IC train. Performing these two upgrades keeps the system on an engineered and validated path. This is the safest choice for system stability and data integrity.
For example, the following diagram shows the multihop upgrade from IC
37_355_0x to IC
38_363_0x and a two-step upgrade, if the customer is upgrade from IC
37_361_0x to IC
38_363_0x.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\