PowerStore 3.0 PowerStore T Implementation

POWERSTORE 3.
0
POWERSTORE T
IMPLEMENTATION
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerStore 3.0 PowerStore T Implementation
© Copyright 2023 Dell Inc Page 2

Table of Contents
PowerStore T Implementation 6
Introduction 6
PowerStore T Networking Concepts 7

PowerStore Networks 7
Management Network 8
Initial Discovery Network (IDN) 9
File Mobility and File Import Networks 10
Cluster Network 11
Storage Network 13
Replication and Block Import Network 14
NAS Server Network 15
Service Network 16
PowerStore Connectivity Options 16
PowerStore Appliance Ports 17
PowerStore T Implementation Process 18

About Dual Switch Topology 18
Connectivity Types Pros and Cons 20
Process Overview 23
Planning 24
Ethernet Switching and Cabling 25
System Discovery 26
Initialization 26
Storage Services 27
PowerStore T Planning 29
Management Switch Requirements for PowerStore T 29
User-Defined Link Aggregation 33
Link Aggregation Configuration Overview 34
Complete the Planning Worksheets 35

Scavenger Hunt 40
PowerStore T Management Switch 43

Connect to a ToR Switch 43
Configure Management Switch Introduction 44
Management and Discovery Networks, 1 of 2 45
Management and Discovery Networks, 2 of 2 50
Activity: Configure Management Switch 56
PowerStore T Discovery and Initial Configuration 57

PowerStore Discovery Options 57
Initial Configuration Wizard 59
Initial Configuration Wizard Overview, 1 of 2 62
Initial Configuration Wizard Overview, 2 of 2 68
Practice: Initial Configuration Wizard 74
Configure PowerStore T Data Switch 75

Configure Data Switches 75
ToR Data Switching Configuration Requirements for PowerStore T Models 76
Storage Network Configuration Requirements for PowerStore T Models 85
Configure General Settings on Top-of-Rack (ToR) Data Switch 1 90
Spanning Tree Data Switch 1 95
Activity: Configure Spanning Tree on Data Switches 96
Configure VLANs on ToR Data Switch 1 96
Activity: Configure VLANs on Data Switches 102
Configure VLT on ToR Data Switch 1 103
Activity: Configure VLT on Data Switches 106
Configure LACP Port Channels for PowerStore Cluster Network on ToR Data Switch 1 107
Configure LACP Port Channels for PowerStore NAS Network on ToR Data Switch 1 112
Configure Ports for PowerStore Storage Networks on Data Switch 1 118
Activity: Configure LACP Port Channels for Nodes on Data Switches 120
Configure Core Switching Uplinks on ToR Data Switch 1 121
Activity: Configure Core Switching Uplinks on Data switches 124
Storage Network and NAS Server Network Configuration 125

Expand Storage Networking 126
Expand Storage Networking on ToR Data Switch 1 127
Activity: Expand Storage Networking on Data Switches 131
PowerStore T Licensing 132

PowerStore Licensing Overview 132
PowerStore License Flow Without Internet Access 134
PowerStore License Manual Installation Flow 135
Trial License Extension 136
Practice: Licensing Status 137
PowerStore T Implementation Key Points 138

PowerStore T Implementation Key Points 138
Appendix 141

PowerStore T Implementation
PowerStore T Implementation
Introduction
In this course, learn the steps to complete implementation of a newly

installed PowerStore T, including:
 PowerStore T Networking Concepts
 PowerStore Discovery and Deployment Options
 PowerStore implementation workflow overview
 Network switch interconnectivity recommendations
 Top-of-Rack management switch configuration for PowerStore T
models
 Initial Configuration of a PowerStore T model
Important: This training uses examples of network cabling

and a network environment for installing PowerStore
systems. The switch port cabling and networking details will
be different for your installation. Use the ports, VLANs,
addressing, and other settings from your own completed
planning worksheets for your installation.
Switch settings involve the configuration of VLANs, LACP
port channels, trunk ports, access ports, VLT interconnects,
and Rapid Spanning Tree Protocol. If unfamiliar with
performing these configurations, contact your Dell
representative for assistance.

PowerStore T Networking Concepts
PowerStore Networks
Every PowerStore appliance connects to multiple networks, as shown in

the graphic.
PowerStore appliance that is connected to multiple networks
 All PowerStore networks must be configured on the switch.

 Management and Storage networks are configured in PowerStore
when a cluster is created through the PowerStore Initial
Configuration Wizard (ICW).
 Other networks are configured manually during the ICW.
 A PowerStore network is a subset of addresses on an IP
network/subnet over a single L2 broadcast domain.
 PowerStore T model requires all networks to be unique.
 It is highly recommended to deploy PowerStore T with multiple and
unique VLANs to separate the traffic.
 If only one VLAN is available, PowerStore T can be deployed with a
single VLAN and multiple unique subnets.

 PowerStore T uses only a reserved subset of addresses within each IP

network/subnet.
 Sometimes, multiple PowerStore networks share a single L2 broadcast
domain.
 For example, the Storage Network, NAS networks, and Cluster

networks are all on one set of cables.
Management Network
The Management Network is only used on the PowerStore T.
PowerStore T cluster and appliances over the Management network
Management network provides access to:

 Infrastructure services, such as DNS, NTP, and SMTP
 PowerStore REST API, PowerStore Manager, and PowerStore CLI

 Support Connectivity
 VASA provider
Management Network is configured explicitly.

 It can be IPv4 or IPv6.
 It can be on the native VLAN or on a tagged VLAN.
Initial Discovery Network (IDN)
Initial Discovery Network (IDN)
The Initial Discovery Network (IDN) is used for initial appliance

discovery with remote connection, using the PowerStore Discovery Utility.
 When a PowerStore node boots, it assigns itself an IP address on IDN.

 The address is within the 169.254.0.0/16 IPv4 network, obtained by
using zero-configuration technology (zeroconf).

 IDN runs over the native VLAN only.

 IDN network resides on the same cabling as the Management
Network.
 On PowerStore T systems, IDN uses a dedicated management

port.
Before Initial Configuration, attach a workstation to the IDN. Then, run the
PowerStore Discovery Utility to find any uninitialized PowerStore
appliances that are connected to the network.
The Discover Utility uses Multicast DNS (mDNS) to allow name resolution
on a local network when there is no local name server.
File Mobility and File Import Networks
File Mobility Network
File Mobility is a prerequisite for replication and import of File storage.
 File Mobility runs over the Management network through the

management switch.
 PowerStore T model clusters use the File Mobility interface to establish
SSH connections with external file resources.
 To create File Mobility in PowerStore Manager:
 PowerStore T model must have been deployed in Unified mode.

 File Mobility network is not configured on the switch, but must be
configured in PowerStore Manager.
 Three IP addresses must be reserved for File Mobility:
o Two IP addresses per appliance (one each for Node A and
Node B)
o One IP address per cluster

File Import Network
File Import network is used with the File Mobility network to import File
storage from remote systems.
 The File Import network requires that:

 The PowerStore T model is deployed in Unified mode to support
NAS services.
 The File Mobility network is configured on the Management switch.
 The File Import network must be configured in an LACP bond.
 The PowerStore T model appliance node ports that are cabled for
LACP must be the same speed.
 LACP can be configured using the same number of ports, either 2
or 4, on each node.
 File Import can use the same bond that is used for the NAS network,
but it cannot use the bond dedicated to the Cluster network.
Cluster Network
Cluster network

 The Cluster network is used for intracluster management and data

communications.
 The Cluster network is encrypted with IPSEC.
 Data communications facilitate storage migration traffic between
appliances.
 The Intra-Cluster Data (ICD) network1 and the Intra-Cluster
Management (ICM) networks2 both use the PowerStore backplane.
 The system automatically configures the Cluster network using IPv6
addressing.
 The network traffic is untagged and uses the Ethernet switching native
VLAN.
 The Cluster Network must be cabled through the first two ports of the
4-port card in an LACP Bond (0).
 Ports 0 and 1 on the PowerStore T model appliance node are

reserved for the Cluster network.
 Bond 0 is reserved only for the Cluster network.
1
Internal storage network that provides continuous storage connectivity
between nodes and appliances in the PowerStore cluster. For example,
NAS servers use the ICD network to access underlying storage resources.
2
Internal management network that provides continuous management
connectivity between nodes and appliances in the PowerStore cluster. For
example, during a NAS installation, the PowerStore nodes communicate
with each other using the ICM network.

Storage Network
The Storage Network is used to access block storage data from

PowerStore. The Storage Network supports data replication and migration
features. The network is configured after initial deployment, when adding
storage services.
Storage Network
iSCSI Storage Network
The iSCSI network:

 Can be cabled through any port on the 4-port card or I/O module.
 Can be IPv4 or IPv6.
 Can be on the native VLAN or a tagged VLAN.
 Shares port with Replication and Block Import network, which is
separated by VLANs.
 Shared port: Port 2 on I/O Module 0
NVMe/TCP Storage Network
The NVMe/TCP network:

 Provides front-end connectivity for block storage access.

 Is configured after initialization in PowerStore Manager by the

administrator to support block storage access operations.
 Can be cabled through any port on the 4-port card or I/O module.
 Dedicated port: Port 0 on I/O Module 0
Replication and Block Import Network
The Replication and Block Import network is configured after initialization

in PowerStore Manager. It is a storage network to support replication and
block import operations.
The Replication and Block Import network:
 Uses front-end traffic for both file and block storage and external data
mobility traffic for block storage.
 Shares port with iSCSI network, which is separated by VLANs.
 Shared port: Port 2 on I/O Module 0
Important: Replication and Block Import is a shared

network. The Block Import network is not used for any File
functionality. Only the Replication portion of the network,
with File Mobility, is used for replication of File storage.

NAS Server Network
NAS Server Network
 Network Attached Storage (NAS) Server network provides:

 Front-end access such as NFS, SMB, and FTP
 Active Directory (AD) for the NAS services
 External data mobility traffic for file storage
 The NAS Server network:
 Is configured on the PowerStore system after initialization.

 Is configured on PowerStore T models (Unified deployments only)
and used for NAS Server file storage communications.
 Can use IPv4 or IPv6 addresses.
o The network traffic can be untagged or tagged. Tagged traffic is
recommended.
 Uses LACP bonded ports.
 Can be built on user-defined LACP bonds, but not the system
defined bond 0.
o The example here, shows NAS user defined LACP bond using
mezz card port 3 and SLIC 1 port 3 for Node B. Similarly, the
user defined LACP bond is created for Node A.

Service Network
Service Network
 The Service network is used for PowerStore service-related tasks.

 Each PowerStore node has a service port with a hard-coded static IP
address.
 The ports are not connected to Ethernet switching. They are used to
directly connect to a service system.
 The service port IP address is browser accessible and provides an
optional method for initializing the system.
PowerStore Connectivity Options
One out-of-band (OOB) management switch and two Top-of-Rack (ToR)

switches are required for PowerStore T to support iSCSI or NVMe/TCP
host connectivity.
To implement NVMe/TCP on a PowerStore.
 Enable NVMe/TCP on the PowerStore cluster:

 NVMe/TCP is supported wherever iSCSI is available.

o Ethernet ports at 4-Port Card (MEZZ0), IOModule0 (SLIC0), and

IOModule1 (SLIC1)
o System Bond
 Configure NVMe/TCP on the cluster.
 Configure NVMe/TCP on supported host types:
 VMware vSphere 7.0U3 (vSphere 7.0U3 is also supported with
SmartFabric Storage Software).
 Red Hat Enterprise Linux 8.2-8.4
 SLES 15 SP2-SP3
 Create or modify volume access to use NVMe/TCP.
PowerStore Appliance Ports
Node A is at the bottom. Node B is at the top. The port layouts are
identical on both nodes.
PowerStore T ports
PowerStore T uses the management port to connect to OOB

management.
The first two ports on the 4-port card form an LACP bond.

PowerStore T Implementation Process
About Dual Switch Topology
Provide redundancy at the network interface controller (NIC) and switch

levels using dual switch topology. Each base enclosure appliance node
must have at least one connection to each physical Ethernet switch.
MC-LAG
Two switches act like a single switch using VLTi.
Multi-chassis Link Aggregation Group (MC-LAG)
VLTi is required for Link Aggregation Control Protocol (LACP) connectivity

between the nodes, and:
 Allows a single device to use a LAG across two upstream switches.
 Assures high availability.
 Provides a loop-free topology and eliminates STP-blocked ports.
 Optimizes the use of all available uplink bandwidth.
 Guarantees fast convergence if either a link or a device fails.

 Provides Layer 2 multipathing.

 Provides link-level resiliency.
Warning: Only an experienced network administrator

should configure VLTi. Do not configure VLTi if you have
limited networking experience and are not a network
specialist.
Reliable L2 Uplink
L2 Uplink
PowerStore requirements for this type of connectivity include:

 No single point of failure (SPOF). Provide redundant connectivity to
both data switches.
 Dell recommends using switches that are listed in the Simple Support
Matrix on the PowerStore Info Hub.

Direct Trunk Link
Direct Trunk Link
If neither MC-LAG nor reliable L2 uplinks are viable options, use a direct
trunk link between the switches.
PowerStore requirements for this type of connectivity include:

 No SPOF. Two or more cable connections joined by Dynamic LAG.
 Dynamic LAG link allows traffic for the native VLAN and PowerStore
network VLANs.
 The combined bandwidth of the link between the Physical Ethernet
switches must be at least the recommended minimum bandwidth
(RMB).
 Spanning tree protocol must be enabled on the Physical Ethernet
switches with the link ports marked as STP non-edge ports.
Connectivity Types Pros and Cons
When comparing the different interconnectivity options, there are pros and
cons to each method. Overall the VLT solution performs the best, but the
other two methods are easier to set up.

MC-LAG like VLT Reliable L2 Uplinks Dynamic LAG
Recommended Allowed Allowed

Pros: Pros: Pros:

 High Availability:  Complexity:  Complexity:
Data switch failure Reduced switch Reduced switch
is accommodated complexity on initial complexity on initial
by sending traffic deployment deployment
over surviving  Cost: Reduced  Cost: Reduced
LACP links. deployment cost, deployment cost,
 Maintenance: VLT self-installable self-installable
allows the firmware
of either VLT peer
switch to be
updated
independently.
 High
Performance:
Traffic is load
balanced across all
LACP members
according to the
LAG hash
algorithm.

Con: Cons: Cons:

 Complexity: VLT  Performance: Only  Performance: Only
technology requires one of the two 10 one of the two
networking GbE cables coming 10GbE cables
expertise to from each coming from each
configure. PowerStore node is PowerStore node is
active and the other active and the
becomes logically other becomes
disabled. 50% logically disabled.
reduction in 50% reduction in
bandwidth for the bandwidth for the
minimal-cabled minimal-cabled
configuration. configuration.
 Spanning Tree  Spanning Tree
Protocol: Risk of Protocol: Risk of
STP blocking STP blocking the
redundant L2 LAG interconnect.
uplinks. If an active In certain
uplink were to fail, environments, it
recovery time may cause
depends on STP PowerStore traffic
reconvergence to move further into
times. the network to
reach the peer
node. Including
intracluster traffic,
management
traffic, and traffic
for the first iSCSI
target.
Process Overview
The implementation of a PowerStore is a multistep process for

establishing network connectivity to the installation site network

environment. When the process is complete, the PowerStore has network

connectivity for management and data storage access.
The process workflow for PowerStore T models is:

1. Planning
2. Ethernet Switching and Cabling
3. System Discovery
4. Initialization
5. Storage Services
Planning
The web version of this content contains an interactive activity.
There are several worksheets for planning network cabling connections

and network configuration for implementing PowerStore into a site network
environment. The network preparation worksheets and initial configuration
worksheets are specific to the PowerStore T models.
The worksheets are contained within the Networking Guide for

PowerStore T Models in PowerStore Info Hub.
 PowerStore T Worksheet:
 Management Network Preparation Worksheet

 Switch Resources for Storage services Worksheet
 Storage Network Preparation Worksheet
 Initial Configuration Worksheet

Initial Configuration Worksheet excerpt
Ethernet Switching and Cabling
Dell Technologies recommends using PowerSwitch Series switching

running OS10 Enterprise Edition (OS10EE).
For a PowerStore T storage configuration using Fibre Channel (FC)

connectivity, the configuration requires less switching.
 PowerStore T switching:
 One management switch

o Only required switch for FC connectivity configuration
o Cable and configure management switch per completed
Management Network Preparation Worksheet.

 Two data switches

o Switch cabling and configuration are performed at Storage
Services step.
System Discovery
System discovery establishes a browser connection to the unconfigured

PowerStore system.
Discovery Tool example
Initialization
The Initial Configuration Wizard (ICW) runs on the first browser connection
to the PowerStore.

The Initial Configuration Wizard (ICW) prompts you to enter the necessary
network information for initial configuration of your PowerStore T model
appliance.
The Powerstore T ICW configures the system management network.
The storage network is configured in the Storage Services section.
Initial Configuration Wizard
Storage Services
PowerStore T model appliances provide the option to add storage

services after initial deployment.
It is performed per the completed Switch Resources for Storage

services Worksheet and the Storage Network Preparation Worksheet.
Steps to configure the storage network include:

 Cable the PowerStore T and the two ToR data switches.

 Configure the data switches.

 Configure the Storage network in PowerStore Manager.
PowerStore T data switch cabling example

PowerStore T Planning
Management Switch Requirements for PowerStore T
Identify the information that is required to configure the PowerStore T

management switch.
Important: Download the Networking Guide for

PowerStore T Models on PowerStore Info Hub for detailed
instructions and requirements. Working with your network
administrator, record the data about the management
switch on the Management Network Preparation
Worksheet, which is in the guide.
Switch Requirements
Example of management switch.
Three switches are recommended per rack for PowerStore T models: One
management switch and two data switches. Planning the management
switch configuration is covered in this section. PowerStore T data switch
configuration occurs at the Storage Services section of the workflow.

 Enterprise Ethernet switching is required. PowerSwitch Series

switches running OS10 Enterprise Edition (OS10EE) are
recommended.
 Switch license must be perpetual and active.
Training Example Key
Management switch - PowerSwitch S4148T-ON
Networks
Example of management switch networks, connections, and VLANs
The management switch is configured to support the PowerStore T

management network. Ethernet cabling connects the PowerStore node
management ports to the management switch.
If the static discovery address or zeroconf address options are used for
system discovery, the management switch is configured to support the
Initial Discovery Network (IDN). A management switchport must be cabled
and configured for the discovery system. If the service port address is
used for discovery, the IDN configuration and cabling are not required.
PowerStore Node A management Management switch port 1

PowerStore Node B management Management switch port 2
Discovery system Management switch port 54
Management network (untagged) VLAN 1501
IDN (untagged) VLAN 1501
Important: This training configures the IDN and uses the

Discovery Utility to discover the PowerStore zeroconf
address.
Uplinks
Example of management switch uplinks.
The management switch is connected to the site core switching through

redundant uplinks that are configured as a port channel.
Management uplink A Management switch port 25

Management uplink B Management switch port 26
Port channel ID 40
General Switch Settings
Example of management switch networks, connections, and VLANs.
The management switch is configured with an IP address to manage the

switch. The switch is also configured with a default gateway and NTP
server.
Switch hostname MgmtSwitch
IP address for switch management 172.17.57.10/24
Default gateway 0.0.0.0/0 172.17.57.254
NTP server 172.17.57.50
The completed Management Network Preparation Worksheet contains

the information that is required to configure the management switch.

Before configuring the switch, continue to work with the network

administrator to complete the Initial Configuration Worksheet.
User-Defined Link Aggregation
Go to: Link Aggregation for a concise on Link Aggregation

Group (LAG) and Link Aggregation Control Protocol (LACP)
concepts.
Link Aggregation (LAG) provides redundancy for production network ports

and the ability to scale out NAS from the system bond to other ports on
PowerStore.
Possible User-defined LAG
Link aggregation features:

 Create, expand, and delete Link Aggregation.
 Aggregates from two to four ports.
 Can be across 4-port cards and I/O modules.
 Ports must have the same speeds, duplex settings, and MTU.
 Aggregated links provide aggregated bandwidth, so two 10 Gbps links
in a LAG would provide (potentially) 20 Gbps total bandwidth.
 If LACP is not set up properly, link aggregation ports fail back to two
independent links . The total bandwidth is the same as one link.
 Alerts indicate that link aggregation is not set up properly.

User-defined link aggregation considerations:

 Link aggregation is supported for NAS servers and File Import
interfaces.
 No block support
 Link aggregation is supported on PowerStore T only.
Link Aggregation Configuration Overview
Top of Rack and PowerStore cabling bonding ports 2 and 3
There are three major procedures:
1. Configure switches
 Identify available ports on Top of Rack (ToR) switches to be used
for aggregation.
 Configure Port Channel and Ethernet interfaces for every selected
port into a bond on the two ToR data switches.
 Properly run cables and connect to the configured ports on ToR
switches and the PowerStore appliances.
2. Create link aggregation in PowerStore Manager.

 Configure link aggregation—bond—for the identified and selected

ports on the PowerStore.
3. Create or modify a NAS server to use the bond interface.
Complete the Planning Worksheets
Download the Networking Guide for PowerStore T Models

from PowerStore Info Hub for detailed instructions and
requirements. Working with your network administrator,
record the data to complete the Initial Configuration
Worksheet in the guide.
Print the worksheet pages and enter the values for the
cluster. Use these values when running the Initial
Configuration Wizard (ICW).
Locate the Worksheets
There are three planning worksheets to use when configuring a new

PowerStore T for block storage:
 Management Network Worksheet is completed with the help of a
network administrator. It includes ports and VLANs to use when setting
up the management network.
 Switch Resources for Storage Services Worksheet is completed
with the help of a network administrator. It includes spanning tree
settings, ports, priorities, and VLANs to use when setting up the
storage network.
 Initial Configuration Worksheet includes all of the information
required to complete the Initial Configuration Wizard, including the
cluster name, appliance service tags, and IP addresses to use when
completing the PowerStore T configuration.

Two additional planning worksheets are used for file storage:

 Network Configuration Worksheet for NAS storage Service
includes the network details that are required for setting up file storage.
 Network Configuration Worksheet for File Import includes the
network details that are required for importing existing file systems to
PowerStore.
The worksheets are embedded into the Networking Guide for PowerStore
T Models on the PowerStore Info Hub. Download the guide to print and
add your specific configuration information.
Management Network Prep
Use the Management Network Preparation Worksheet when doing the

initial configuration of the management switch for PowerStore T.
Top of the Management Network Preparation Worksheet

Switch Resources for Storage Services
Use the Switch Resources for Storage Services Worksheet when

doing the initial configuration of the data switches for PowerStore T.
Top of the Network Setup Preparation Worksheet

Cluster Details
Page 1 of Initial Configuration Worksheet filled in with values for the lab

Network

vCenter
Scavenger Hunt
Practice Using the Worksheets 1 of 5
When deploying a new PowerStore T cluster, what are some of the

settings to use?
Find the answers to the questions on the sample worksheets. Each

worksheet opens on a new browser tab. Use the same three worksheets
for all questions.
 Management Network Worksheet
 Switch Resources for Storage Services Worksheet
 Initial Configuration Worksheet
1. What is the port channel ID for the management switch?

a. port channel 30
b. port channel 1
c. port channel 10
d. port channel 20

settings to use?


for all questions.
2. How many appliances are being configured in the cluster?

a. 0
b. 1
c. 2
d. 4

settings to use?

for all questions.
3. What is the VLT priority for ToR switch 2?

a. 8192
b. 9216
c. 1
d. VLT is not in use

settings to use?


for all questions.
4. What is the selected storage configuration?

a. Unified
b. Block Optimized

settings to use?

for all questions.
5. Which IP addresses are reserved for the File Mobility Network?

a. 192.168.1.14-16
b. 192.168.1.11-13
c. None
d. 192.168.50.200-201

PowerStore T Management Switch
Connect to a ToR Switch
To configure the switch settings, connect a serial cable to a laptop with a

terminal emulator program.
PuTTY configuration settings
Use these connection settings:

 Baud rate: 115200 (9600 for micro-USB port)
 Data bits: 8
 Parity: None
 Stop bits: 1
 Flow Control: None

Important: The default login credentials are admin/admin.

Dell recommends changing the default password on the
Ethernet switch using the configure terminal command.
# configure terminal
#(config) username admin password <NEW_PASSWORD> role
sysadmin
Configure Management Switch Introduction
Important: The following cabling and network environment

scenario is used for this example. Switch port cabling and
network environment may be different for your installation.
Use the ports, VLANs, addressing, and other settings
that are specific to your installation.
On the PowerStore T Top-of-Rack (ToR) management switch, configure:

1. The PowerStore management and initial discovery networks on
switchports connecting to the management port on each PowerStore
node
2. A switchport for the discovery system
3. Switchports connecting to core switching uplinks
When management switch configuration is complete, the PowerStore is

ready for discovery and initial configuration with the Initial Configuration
Wizard (ICW).

PowerStore T management switch cabling and portgroup 40
Management and Discovery Networks, 1 of 2
Follow these steps to configure the basic management switch settings.
Hostname and VLAN
Review the management network requirements.
Define the management switch hostname and management VLAN
1. Run configure terminal to enter global configuration mode and

start making configurations.
2. Run hostname <name> to set a hostname for the switch.

3. Run interface vlan <ID> to create a management VLAN

(optional).
4. Run description <description> to create a description for the
VLAN.
5. Run no shutdown to commit this configuration.
6. Run exit to exit VLAN configuration mode.
#configure terminal
#(config) hostname MgmtSwitch
#(config) interface vlan 1501
#(conf-vl-1501) description Management_network
#(conf-vl-1501) no shutdown
#(conf-vl-1501) exit
Deep Dive: 30-minute video about VLANs.
Discovery System
If performing remote discovery, configure an Ethernet interface on the

switch to configure the port for the PowerStore Discovery network. Review
information about the initial discovery network (IDN).

Define port used for the Discovery system
1. Run interface ethernet chassis/slot/port to identify the

port to be configured as the Discovery system port.
port.
– If spaces are used in the description, include quotation marks
around the string, as in description "Discovery port"
– If spaces are not used, quotation marks are not required, as in
description Discovery_port
3. Run switchport access vlan <ID> to allow access to the
Discovery network traffic.
4. Run no shutdown to commit this configuration.
5. Run exit to exit interface configuration mode.
#(config) interface ethernet 1/1/54

#(conf-if-eth1/1/54) description Discovery_port
#(conf-if-eth1/1/54) switchport access vlan 1501
#(conf-if-eth1/1/54) no shutdown
#(conf-if-eth1/1/54) exit

S4148T-ON switch front view
Switch Management IP
Configure the management port on the back of the switch.
Define the switch management port
1. Run interface mgmt chassis/slot/port to select the

management interface of the switch.
2. Run no shutdown to enable the port.
3. Run no ip address dhcp to disable the DHCP client on the port.
4. Run ip address <IP> to create a management IP address for the
management switch.
– Use this IP address to SSH into the switch for configuration
purposes.
5. Run exit to exit the interface configuration.

#(conf-if-eth1/1/54) interface mgmt 1/1/1

#(conf-if-ma-1/1/1) no shutdown
#(conf-if-ma-1/1/1) no ip address dhcp
#(conf-if-ma-1/1/1) ip address 172.17.57.10/24
#(conf-if-ma-1/1/1) exit
S4148T-ON switch back view.
Default Route and Time Service
Define the default route and time service
Configure the management route and NTP server.
1. Run management route <IP/netmask gateway> to define the

path to manage the system through the management port.
2. Run ntp server <IP> to set the NTP server IP address.
#(config) management route 0.0.0.0/0 172.17.57.254

#(config) ntp server 172.17.57.50

Management and Discovery Networks, 2 of 2
Follow these steps to configure PowerStore and core switching on the

management switch.
Node A management ports
Configure the switch Ethernet port that connects to the node A

management port.
Define management port for node A
1. Run interface ethernet chassis/slot/port to configure the

port connection to the PowerStore T node A management port.
port.
3. Run switchport mode access to configure the port for access
mode.
management VLAN.

#(conf-if-vl-1501) interface ethernet 1/1/1

#(conf-if-eth1/1/1) description “Node A management
port”
#(conf-if-eth1/1/1) switchport mode access
Node B management ports
Configure the switch Ethernet port that connects to the node B

management port.
Define management port for node B

port connection to the PowerStore T node A management port.
port.

3. Run switchport mode access to configure the port for access

mode.
management VLAN.

#(conf-if-eth1/1/2) description “Node B management
port”
#(conf-if-eth1/1/2) switchport mode access
Port channel for Core uplinks
Configure the switch port channel for the core switching uplinks.

Port channel for management switch uplinks
1. Run interface port-channel <channel number> to configure

the port channel for core switching uplinks.
port channel.
3. Run no shutdown to enable the port channel.
4. Run switchport mode trunk to enable trunk mode on the port
channel.
5. Run switchport access vlan <ID> to allow untagged traffic over
the port channel.
6. Run switchport trunk allowed vlan <ID> to enable the
management VLAN over the trunk.
7. Run exit to exit the port channel configuration.
#(config) interface port-channel 40

#(conf-if-po-40) description "Port-channel for
management switch uplink"
#(conf-if-po-40) no shutdown
#(conf-if-po-40) switchport mode trunk
#(conf-if-po-40) switchport access vlan 1
#(conf-if-po-40) switchport trunk allowed vlan 1501
#(conf-if-po-40) exit

Port group interfaces
Configure the switch port group Ethernet interfaces for the core switching
uplinks.
Port group Ethernet interfaces for management switch uplinks

port connection to the core switching.
interface.
3. Run no shutdown to enable the interface.
4. Run channel-group <channel-group number> mode active
to enable the port group on the interface.
5. Run no switchport to enable interface L3 mode.
6. Run flowcontrol receive off to turn off interface receive flow
control.
7. Run flowcontrol transmit off to turn off interface transmit flow
control.
port connection to the core switching.
interface.

11. Run no shutdown to enable the interface.

12. Run channel-group <channel-group number> mode active
to enable the port group on the interface.
13. Run no switchport to enable interface L3 mode.
control.
control.
16. Run end to exit the global configuration mode.

#(conf-if-eth1/1/25) description "Uplink to core
switching"
#(conf-if-eth1/1/25) channel-group 40 mode active
#(conf-if-eth1/1/25) no switchport
#(conf-if-eth1/1/25) flowcontrol receive off
#(conf-if-eth1/1/25) flowcontrol transmit off
#(conf-if-eth1/1/26) description "Uplink to core
switching"
#(conf-if-eth1/1/26) end

Activity: Configure Management Switch
Virtual lab: Configure the management

switch.
Go to the activities section in your SABA
transcript to launch the VLP lab.
This lab can be completed during a classroom
session or on demand.

PowerStore T Discovery and Initial Configuration
PowerStore Discovery Options
There are several options for PowerStore system discovery and

initialization.
Discovery with a direct connection
Discovery with a direct connection is the recommended procedure. IDN

is not required, simplifying system discovery and initialization. The
procedure requires the installer to be physically present with the
PowerStore system. The process uses a service port static address.
 Connect the network adapter of the workstation directly to the

PowerStore service port on Node B.
 Configure the discovery system with a static IP address on the
128.221.1.0/24 network with no gateway defined.
 Example: 128.221.1.249; 255.255.255.0; no gateway.
 Connect the workstation or laptop to the LAN port on Node B of the
base enclosure.
 In a web browser, go to https://128.221.1.251.
 Log in to PowerStore Manager using the default credentials.
 Initial Configuration Wizard (ICW) opens to initialize system.
Remote Discovery using PowerStore Discovery Utility
The remote discovery and initialization process using the PowerStore

Discovery Utility.

PowerStore Initial Discovery
 Performed over the network, remote from the PowerStore physical

location.
 Discovery tool advertises a 169.254.x.x/16 IP address.
 Discovery system is connected to the IDN and runs PowerStore
Discovery Utility.
 PowerStore Discovery Utility queries IDN for zeroconf address of
connected PowerStore systems.
 Select the PowerStore system to configure.
 Utility opens browser https connection to selected system zeroconf
address.
 Initial Configuration Wizard (ICW) opens to initialize system.
Go to the PowerStore Discovery Utility Process for more information.
Remote Discovery with Static Discovery Address
The remote discovery and initialization process using the static discovery
address:
 The PowerStore Discovery Utility is not required.

 Establish an http browser session to static discovery address.
 Important: http session is required, do not use https.
 Static addresses: 169.254.0.10, 169.254.0.20, 169.254.0.30,
169.254.0.40, 169.254.0.50

 PowerStore system redirects browser to zeroconf address of system

with static discovery address.
 If multiple systems are on IDN, select the PowerStore system to
initialize.
 Browser is redirected to selected system zeroconf address, and ICW
opens to initialize system.
When multiple PowerStore systems are connected to the IDN, the system
with the lowest MAC address is configured with the static discovery
addresses.
Initial Configuration Wizard
Cluster Creation Split into Core and Noncore Services
ICW
 The Initial Configuration Wizard (ICW) divides cluster configuration into

two phases:
 Core Services Initialization – Makes cluster operational from a

systems viewpoint—network settings, HA services, cluster
database, microservices, and so on.
Core service components that are required to be initialized are
Telemetry Notice, Cluster Details, Default Users, Fault Tolerance,
Management Network, Infrastructure Services, and Create Cluster.
As a result of successful core initialization steps, a cluster is
created, but not fully configured.
Block Optimized systems do not have a Component Initialization
step in the ICW. There are no non-core services to install.
In Unified systems, the ICW is finished once all non-core service
initializations are complete.

Core Services Initializations and Cluster Creation
 Non-core Services Initialization – Must be installed for the cluster

to be configured from a product viewpoint such as File Services.
The Component Initialization panel shows the initialization status.
After the Core Services Initializations are complete, the Noncore
Services Initializations start. The Component Initialization step
tracks startup services as they initialize.

Component Initialization
Component Initialization Panel
Each core service component must successfully complete its initialization

before the PowerStore cluster is ready. After the ICW is complete, the
PowerStore T model is configured to support Fibre Channel Connectivity.
For iSCSI or NVMe/TCP connectivity, additional configuration steps are
performed.

Component Initialization Status
Initial Configuration Wizard Overview, 1 of 2
Use the information on the Initial Configuration Worksheet to complete

the Initial Configuration Wizard (ICW). Planning is important. If
completed correctly, running the ICW is a matter of moving information
from the worksheet to the wizard.
EULA and Telemetry Notice
After initial login using the default username and password, the End User
License Agreement (EULA) must be accepted or configuration cannot
continue. The first step in the ICW is the Telemetry Notice.
The privacy or telemetry notification is:

 A legal requirement to inform customers of any potential impact to their
personal information, including how personal and system information is
gathered and used.
 Displayed after the EULA.

ICW Telemetry Notice step
Cluster Details
Configure the basics:

1. Name the cluster.
This name becomes the primary name of the cluster. It shows at the
top of the PowerStore Manager interface.
2. Select Storage Configuration: Unified or Block Optimized.
Use Unified if creating and managing NAS File Systems. If not, use
Block Optimized.
If adding NAS Servers in the future, and Unified is not selected during
this step, contact the service provider.
3. Select 1-4 appliances to belong to the cluster.
The first appliance is required. Other discovered but unconfigured

appliances may be added to the cluster, if no more than four total
appliances are added to a single cluster. A cluster can only consist of
appliances of the same model type, either all PowerStore T or all
PowerStore X model appliances.

ICW Cluster Details step
Default Users
For security reasons, the preconfigured default admin and service users
must change their passwords.
1. Admin Password
Enter the default password. Enter and verify a new password.
2. Service Password
By default, the option to use the same password as admin user is

selected. Clear the option to specify a unique service user password.

ICW Default Users step
Fault Tolerance
Set the Fault Tolerance level.
1. This setting can only be set once on the appliance. It cannot be

changed after it is configured.
Select Single Drive Failure or Double Drive Failure.

The double drive failure is only available if the appliance has seven or
more data drives, excluding the NVMe NVRAM drives.

ICW Fault Tolerance step
Management Network
The PowerStore management network requires a subset of addresses on

IP networks/subnets over a single L2 broadcast domain. The management
network can be native or VLAN tagged. The ICW provides hints with
content and formatting help for each text entry field. All fields are required
except for the Gateway.
1. Configure the Ethernet Management Network.
Connect to the cluster by the Management network. Settings include:

a. The VLAN, select the Use VLAN tagging option to specify a VLAN.
b. The cluster IP address used to access the entire cluster
c. A range of at least three IP addresses to use when connecting to
management services.
i. One of the addresses is for the appliance, one is for node A,
and one is for node B.
In the example, the Use VLAN tagging option is checked. If using the
native VLAN, do not check the Use VLAN tagging option.

To tag the Native VLAN, configure the physical switch to accept the
tagged VLAN ID. If a VLAN ID is not specified during the initial
configuration, the network traffic is sent as untagged. When the traffic is
untagged, the physical switch applies the Native VLAN to the traffic.
ICW Management Network step
Infrastructure Services
1. Add one or more DNS servers.

The primary DNS IP address is required. Optionally, include up to two
additional DNS servers.
2. Add one or more NTP servers.
The primary NTP IP address is required. Optionally, include up to two
additional NTP servers.
3. Add information about physical switches.
Optionally, include the protocol, switch name, switch port, IP

addresses, username, password, and whether it uses out-of-band
management.

Note: Installation can proceed even if servers are not reachable at the
time of initial configuration.
ICW Infrastructure Services step
Initial Configuration Wizard Overview, 2 of 2
Continuation of the Initial Configuration Wizard (ICW) using the

information from the completed Initial Configuration Worksheet.
vCenter Information
The vCenter Server Information is an optional configuration step. It

establishes a connection between the cluster and the vCenter server.
1. Enter vCenter Server IP Address/Host Name.

2. Enter vCenter Administrator Credentials
3. Enter PowerStore Administrator Credentials.
The preconfigured admin user is selected. The credentials are used to

register the PowerStore as a VASA provider in vCenter.

vCenter Configuration step
Cluster Creation
When all previous configuration information has been entered, the cluster
creation can be performed.
1. Optionally, choose VALIDATE to manually validate the configuration
settings.
Wait a few minutes while information is verified.
2. Optionally, select VIEW FULL DETAILS to see all the configuration
information you entered.
3. Optionally, select EXPORT CONFIGURATION DETAILS to see the
JSON that is sent to the back end in the configuration request.
4. Select CONFIGURE.
The system automatically runs a validation of the configuration

settings. If issues are found that prevent the cluster creation, they must
be addressed. The cluster creation process takes a few minutes, as all
settings are put into place.

ICW Cluster Creation step
 After the cluster is created, go to the PowerStore Manager using the

link on the Cluster Creation step.
 Log in to the PowerStore Manager using the admin user account and
the new password that was created during the ICW.

ICW Cluster Creation step with cluster created
Support & CloudIQ
By default, the options for Support Connectivity and CloudIQ are checked.
It is recommended that Support Connectivity is enabled to help with
problem diagnosis, troubleshooting, and resolution time. Support
Connectivity features are available with a warranty or ProSupport
Enterprise Suite coverage.
Deep Dive: Follow the link for information about CloudIQ.

Initialization and Completion
Each component completes its initialization. This step may take several
minutes.

ICW Component Initialization step
For PowerStore T block-optimized FC-only deployed systems,

implementation is complete. For other deployments, add storage services
including cluster, NVMe/TCP, iSCSI, Replication and Block Import, NAS
and File Import networks.

ICW Configuration Complete step
Practice: Initial Configuration Wizard

Configure PowerStore T Data Switch
Configure Data Switches
 PowerStore networks are configured on switchports connecting to the

PowerStore T node ports:
 Cluster
 Storage (iSCSI and NVMe/TCP
 Replication and Block Import
 NAS and File Import
 The data switches are configured for spanning tree.
 VLANs for the storage, internal, and NAS networks are configured on
the data switches.
 VLT interconnects are configured on the data switches.

 LACP port channels for cluster and file networks are configured.
 Switchports connecting the data switches to core switching uplinks are
also configured.
When the configuration of the data switches is complete, the PowerStore

T is ready to create storage and NAS networks in PowerStore Manager.
Important: Steps to connect to the data switch.
ToR Data Switching Configuration Requirements for

PowerStore T Models
In this section, you identify the information that is required to configure the
PowerStore T ToR data switches.
Important: Download the Networking Guide for PowerStore

T Models for detailed instructions and requirements.
Working with your network administrator, record the data
about the ToR data switches, on the Switch resources for
Storage services Worksheet. It is in the guide.
This training configures the minimum required storage
networking connections, using VLT connections.

Switch Requirements
Example of PowerStore T management and ToR data switches.
Add two ToR data switches to support iSCSI connectivity, replication,

import, cluster, and Network Attached Storage (NAS). These switches are
in addition to the Management switch you configured during your initial
deployment of PowerStore T.
 Enterprise Ethernet switching is required. Dell PowerSwitch Series

switches running OS10 Enterprise Edition (OS10EE) are
recommended.
 Switch license must be perpetual and active.
Training Example
Management switch - PowerSwitch S4148T-ON
Data Switch 1 - PowerSwitch S5248F-ON
Data Switch 2 - PowerSwitch S5248F-ON

System Bond
At a minimum, ports 0 and 1 of the PowerStore T nodes must be

connected to the ToR data switches. Ports 0 and 1 form the system bond.
The system bond is created automatically during initial configuration, and
cannot be removed.
 Port 0 and Port 1 on the same node must connect to opposite

switches.
 Port 0 on Node A, and Port 0 on Node B must connect to opposite
switches.
 Port 1 on Node A, and Port 1 on Node B must connect to opposite
switches.
Training Example
PowerStore Node A Port 0 ToR Data switch 2 port 1
PowerStore Node A Port 1 ToR Data switch 1 port 1

PowerStore Node B Port 0 ToR Data switch 1 port 2
PowerStore Node B Port 1 ToR Data switch 2 port 2
LACP Port Channel ID for Node A 10
LACP Port Channel ID for Node B 20
NAS and File Import Bond
The Network Attached Storage (NAS) network must be configured on a

Link Aggregation Control Protocol (LACP) bond.
It is recommended to configure a bond with one port from different I/O

modules.
The File Import network can use the same bond that is used for the NAS
network, but it cannot use the bond that is dedicated to the Cluster
network.

 On both nodes, I/O Module 0 Port 3 and I/O Module 1 Port 3 connect
to opposite switches.
 I/O Module 0 Port 3 on Node A, and I/O Module 0 Port 3 on Node B
must connect to opposite switches.
 I/O Module 1 Port 3 on Node A, and I/O Module 1 Port 3 on Node B
must connect to opposite switches.
Training Example
PowerStore Node A I/O Module 0 ToR Data switch 1 port 11

Port 3
PowerStore Node A I/O Module 1 ToR Data switch 2 port 11

Port 3
PowerStore Node B I/O Module 0 ToR Data switch 2 port 12

Port 3
PowerStore Node B I/O Module 1 ToR Data switch 1 port 12

Port 3
LACP Port Channel ID for Node A 50
LACP Port Channel ID for Node B 60

Network VLANs
Top of rack switch connections
A maximum of 32 storage networks can be configured. Up to eight storage

networks can be configured per PowerStore interface.
NAS Server network is configured for unified deployments only.
The internal network uses the native VLAN.
Training Example
iSCSI storage network VLAN 1502
NAS Server network VLAN 1503
NVMe/TCP storage network VLAN 1505
Replication and Block Import VLAN 1506

network
File Import VLAN 1507
Cluster network VLAN 1 (native VLAN)

General Settings and Spanning Tree
Example of ToR data switching general settings.
The ToR data switches are configured with IP addressing to manage the
switches. The switches are also configured with a spanning tree priority,
default gateway, and NTP server.
Training Example
ToR Switch 1 hostname Data_Switch_1
ToR Switch 1 IP address 172.17.57.20/24
ToR Switch 2 hostname Data_Switch_2
ToR Switch 2 IP address 172.17.57.30/24
ToR Switch 1 Spanning Tree 40960

Priority
ToR Switch 2 Spanning Tree 45056

Priority
Default gateway 0.0.0.0/0 172.17.57.254

NTP Server 172.17.57.50
Interconnects and VLT Configuration
Example of ToR switch VLT interconnects.
The ToR data switches are interconnected to join the independent

switches into a single virtual chassis. MC-LAG is the general name for the
technology. Virtual Link Trunking (VLT) is the MC-LAG proprietary
technology on Dell EMC PowerSwitch Series.
Training Example
Interconnect type VLT
ToR Switch 1 to ToR Switch 2 port Switch 1 port 55 to Switch 2 port 55

pair 1
ToR Switch 1 to ToR Switch 2 port Switch 1 port 56 to Switch 2 port 56

pair 2
VLT Domain ID 1
VLT MAC address (same on both 00:00:00:00:00:01

switches)
VLT priority for ToR Switch 1 1

VLT priority for ToR Switch 2 8192
Uplinks to Core switching
Example of core switching uplinks to the ToR data switches.
The ToR data switches are connected to the site core switching through
redundant uplinks that are configured as a port channel.
Training Example
Uplink A to ToR Switch 1 Port 53
Uplink B to ToR Switch 1 Port 54
Uplink A to ToR Switch 2 Port 53
Uplink B to ToR Switch 2 Port 54
Uplink Port Channel 30
The completed Switch Resources for Storage services Worksheet

contains the information that is required to configure the ToR data
switches.

Before configuring the switches, continue to work with the network

administrator to complete the Storage Network Configuration
Worksheet.
Storage Network Configuration Requirements for

PowerStore T Models
Identify the information that is required to configure the PowerStore T

storage network.
Each storage network is configured with a name, VLAN, network IP

information, global discovery address, and node ports that the storage
network maps to.
The tabs on this page provide details about each network.
PowerStore T Networks

iSCSI
Training Example
Storage Network Name iSCSI Network 1
VLAN ID 1502
Netmask/Prefix Length 24
Gateway (optional) N/A
Storage Network IP addresses 192.168.2.31-33

(minimum of 2 per appliance, which
are used for iSCSI targets and
initiators)
Global Discovery Address 192.168.2.30
Port to map storage addresses to Node A, I/O Module 0, Port 1

Node B, I/O Module 0, Port 1
NAS
The NAS network must be configured in a Link Aggregation Control

Protocol (LACP) bond.
It is recommended that you configure the bond with one port from different
I/O modules.
Training Example
Storage Network Name NAS Network
VLAN ID 1503
Gateway 192.168.3.254

Network IP addresses (minimum of 192.168.3.1-16

1 per appliance, used for NAS
Server production)
LACP Port Channel ID Node A 50
LACP Port Channel ID Node B 60
Ports to map storage addresses to Node A, I/O Module 0, Port 3 to

Switch 1 Port 11
Node A, I/O Module 1, Port 3 to
Switch 2 Port 11
Node B, I/O Module 0, Port 3 to
Switch 2 Port 12
Switch 1 Port 12
NVMe/TCP
Training Example
Storage Network Name NVMe Network 1
VLAN ID 1505

initiators)


Replication and Block Import
The replication and block import networks cannot be separated and must
run over the same ports.
In this example, the replication and block import networks share the same
physical ports with the iSCSI network.
Training Example
Storage Network Name Replication Network
VLAN ID 1506

initiators)

File Import
Training Example

Storage Network Name File Import Network
VLAN ID N/A
Gateway 192.168.6.1
Network IP Addresses (minimum of 192.168.6.11

1 IP address for each active file
import session.
Global Discovery Address N/A

(Optional)
Ports to map storage addresses to Node A, I/O Module 0, Port 3 to

(same as NAS network) Switch 1 Port 11
Node A, I/O Module 1, Port 3 to
Switch 2 Port 11
Switch 2 Port 12
Switch 1 Port 12
Cluster
Training Example
Storage Network Name Cluster
VLAN ID 1

Ports to map storage addresses to Node A, 4-port card, Port 0 to

(same as NAS network) Switch 2 Port 1
Node A, 4-port card, Port 1 to
Switch 1 Port 1
Node B, 4-port card, Port 0 to
Switch 1 Port 2
Node B, 4-port card, Port 1 to
Switch 2 Port 2
Important: Working with your network administrator, record

the data about the storage network on the Storage Network
Configuration Worksheet. It is located in the Networking
Guide for PowerStore T Models.
Important: This training configures networks according to
recommendations in the Networking Guide for PowerStore T
Models.
Configure General Settings on Top-of-Rack (ToR) Data

Switch 1
Follow these steps to configure the general setting on the ToR data switch
1. When finished, repeat these steps on data switch 2.
Validate version and licensing
Connect serially to data switch1.

The commands on this page affect the data switch connections shown here.
1. Log in with the default admin/admin credentials.

2. Run show version to display and verify the operating system on the
switch.
– PowerStore requires OS10 Enterprise Edition (OS10EE).
# show version
Dell EMC Networking OS10 Enterprise
Copyright (c) 1999-2019 by Dell Inc. All Rights
Reserved.
OS Version: 10.4.3.6
Build Version: 10.4.3.6.244
Build Time: 2019-08-20T00:26:44+0000
System Type: S5248F-ON
Architecture: x86_64
Up Time: 9 weeks 3 days 02:06:44
3. Run show license status to verify the license type on the switch.
Verify:
– License type is PERPETUAL.

– License status is Active.

# show license status

System Information
-----------------------------------------
Vendor Name : Dell EMC
Product Name : S5248F-ON
Hardware Version: A00
Platform Name : x86_64-dellemc_s5248f_c3538-ro
PPID : CN0YF0T6CES008BL0023A00
Service Tag : 8ZK00Q2
License Details
-----------------------------------------
Software : OS10-Enterprise
Version : 10.4.3.6
License Type : PERPETUAL
License Duration: Unlimited
License Status : Active
License location: /mnt/license/8ZK00Q2.lic
-----------------------------------------
Hostname
Set the hostname for data switch 1


#configure terminal
#(config) hostname Data_Switch_1
Switch management IP
Identify the management port on data switch 1.

management switch.
purposes.
5. Run exit to exit the switch configuration.

#(config) interface mgmt 1/1/1

#(config-if-ma-1/1/1) no shutdown
#(config-if-ma-1/1/1) no ip address dhcp
#(config-if-ma-1/1/1) ip address 172.17.57.20/24
#(config-if-ma-1/1/1) exit
S5248F-ON switch back view.
Set the management route and NTP server for data switch 1.



Spanning Tree Data Switch 1
Set the spanning tree priority for data switch 1.
1. When finished, repeat these steps on data switch 2.
As a best practice, it is recommended to add the spanning tree protocol to

ToR switches. Spanning tree detects and prevents network loops and
broadcast storms.
1. Run spanning-tree mode rstp to set the switch mode to Rapid

Spanning Tree Protocol (RSTP).
2. Run spanning-tree rstp priority <0-61440> to set the
priority.
– Set the priority in increments of 4096.
– Work with a network administrator to determine the best priority
to use.
3. Run end to exit global configuration mode.
#(config) spanning-tree mode rstp

#(config) spanning-tree rstp priority 40960
#(config) end

Deep Dive: For more information about Spanning Tree,

watch a Spanning Tree presentation (84 minutes).
Activity: Configure Spanning Tree on Data Switches
Virtual lab: Configure Spanning Tree on Data

Switches.
Configure VLANs on ToR Data Switch 1
Follow these steps to configure VLANs on the ToR data switch 1. When
finished, repeat these steps on data switch 2.
Cluster VLAN 1
Click here to see the cluster network requirements.

Data switch 1 VLAN for internal network.
1. Run interface vlan <ID> to create the cluster VLAN.

2. Run description <VLAN description> to add a description to
the VLAN.
3. Run no shutdown to enable the VLAN.

#(conf-if-vl-1) description Cluster_Network
#(conf-if-vl-1) no shutdown
#(conf-if-vl-1) exit
iSCSI Storage VLAN
Click here to see the storage network requirements.

Data switch 1 with Storage VLAN.
1. Run interface vlan <ID> to create an iSCSI Storage VLAN.

the iSCSI Storage VLAN.

#(conf-if-vl-1502) description iSCSI_Storage_Network
NAS VLAN
Click here to see the NAS network requirements.

Data switch 1 with NAS VLAN.
1. Run interface vlan <ID> to create a NAS VLAN.

the NAS VLAN.
#(config interface vlan 1503

#(conf-if-vl-1503) description NAS_Network
NVMe/TCP Storage VLAN

Data switch 1 with NVMe/TCP Storage VLAN.
1. Run interface vlan <ID> to create an NVMe/TCP Storage VLAN.


#(conf-if-vl-1505) description NVMe_Storage_Network
Replication and Block Import VLAN

Data switch 1 with Replication and Block Import VLAN.
1. Run interface vlan <ID> to create the Replication and Block

Import VLAN.
the Replication and Block Import VLAN.

#(conf-if-vl-1506) description
Replication_Block_Import_Network
File Import VLAN

Data switch 1 with File Import VLAN.
1. Run interface vlan <ID> to create the File Import VLAN.


#(conf-if-vl-1507) description File_Import_Network
Activity: Configure VLANs on Data Switches

Virtual lab: Configure VLANs on Data

Switches.
Configure VLT on ToR Data Switch 1
Follow these steps to configure VLT on the ToR data switch 1. When
finished, repeat these steps on data switch 2.
Disable L2 Mode on VLT Ports
Configure data switch 1 ports for VLT interconnectivity.
1. Run interface range ethernet chassis/slot/port-

chassis/slot/port to identify the range of 100 GbE ports to have
L2 mode disabled. These ports are used for VLT interconnects.
ports.
3. Run no switchport to disable L2 mode on the identified ports.

4. Run no shutdown to enable the ports.

#(config) interface range ethernet 1/1/55-1/1/56

#(conf-range-eth1/1/55-1/1/56) description VLTi
#(conf-range-eth1/1/55-1/1/56) no switchport
#(conf-range-eth1/1/55-1/1/56) no shutdown
#(conf-range-eth1/1/55-1/1/56) exit
S5248F-ON switch front view.
Create VLT Domain, Interfaces, and Heartbeat
Configure VLT interconnectivity
1. Run vlt-domain <ID> to create a VLT domain.

2. Run discovery-interface ethernet chassis/slot/port-
chassis/slot/port to add the two VLT ports to the new domain.
3. Run backup destination <IP address of the other
switch> to set the other switch as VLT backup, which is required for
VLT heartbeat.

#(config) vlt-domain 1
#(conf-vlt-1) discovery-interface ethernet 1/1/55-
1/1/56
#(conf-vlt-1) backup destination 172.17.57.30
Example of PowerStore rack with one management switch and two data switches.
Set Peer Routing, Switch Priority, and MAC
Configure VLT interconnectivity
1. Run peer-routing to enable routing to the peer.

2. Run primary-priority <number from 1-65535> to set the
priority of the switch.
– Switches with lower numbers take priority over switches with higher
numbers.

3. Run vlt-mac <MAC address> to enter a unique made up MAC

address to ensure that a real MAC address is not reused. Configure
the same VLT MAC on both switches.
#(conf-vlt-1) peer-routing
#(conf-vlt-1) primary-priority 1
#(conf-vlt-1) vlt-mac 00:00:00:00:00:01
#(conf-vlt-1) end
Deep Dive: For more information about VLT, watch a VLT

presentation (29 minutes).
Activity: Configure VLT on Data Switches
Virtual lab: Configure VLT on Data Switches.


Configure LACP Port Channels for PowerStore Cluster

Network on ToR Data Switch 1
Follow these steps to configure LACP port channels for nodes on the ToR
data switch 1. When finished, repeat these steps on data switch 2.
Create Node A port channel
1. Run interface port-channel <number> to create an LACP port

channel.
2. Run description <port-channel description> to add a
description to the LACP port channel.
3. Run vlt-port-channel <port-channel created above> to
assign the new port channel to span the VLT domain.
4. Run no shutdown to commit the port channel configuration.


#(conf-if-po-10) description "Cluster LACP port-
channel for Node A"
#(conf-if-po-10) vlt-port-channel 10
Node A Trunk and Spanning Tree
Node A uses port channel 10.
1. Run switchport mode trunk to enable trunk mode.

2. Run switchport access vlan 1 to allow the internal network
traffic on the port channel.
3. Run spanning-tree port type edge to configure the ports that
are connected to nodes as spanning tree edge ports.
4. Run exit to exit the port channel configuration mode.

#(conf-if-po-10) spanning-tree port type edge
Create Node B port channel

1. Run interface port-channel <number> to create a LACP port

channel.

channel for Node B"

Node B Trunk and Spanning Tree
Node B uses port channel 20.

2. Run switchport access vlan 1 to allow untagged traffic on the
port channel.
4. Run exit to exit global configuration mode.

Activate Interfaces for port channels
1. Run interface ethernet chassis/slot/port to select the

port to be assigned to the node A port channel.


3. Run no switchport to disable L2 mode on the identified port.
4. Run channel-group <ID> mode active to set the node A port
channel active on this port.
control.
control.
7. Run exit to exit the configuration of this port.
next port to be assigned to the node B port channel.
11. Run channel-group <ID> mode active to set the node B port
control.
control.
14. Run end to end the global configuration mode.


Configure LACP Port Channels for PowerStore NAS

data switch 1. When finished, repeat these steps on data switch 2.


channel.

#(conf-if-po-10) description "NAS LACP port-channel
for Node A"


3. Run switchport trunk allowed vlan <comma-separated
VLAN IDs> to allow node A traffic on the Storage and NAS VLANs.



channel.

#(conf-if-po-20) description "LACP port-channel for
Node B"


port channel.



control.
control.
control.

control.

Configure Ports for PowerStore Storage Networks on

Data Switch 1
Follow these steps to configure PowerStore network ports. When finished,

repeat these steps on data switch 2.
Configure iSCSI Storage Port
On ToR Switch 1:

port to be assigned to node A.
2. Run description <description to provide a description of the
interface.
3. Run no shutdown to commit the interface configuration.

5. Run switchport trunk allowed vlan <VLAN ID> to allow

node B traffic on the new storage VLAN.
control.
control.
8. Run spanning-tree port type edge to configure the interface
as a spanning tree edge port.

#(conf-if-eth1/1/7) description "Node A IO Mod0 P1"
#(conf-if-eth1/1/7) switchport mode trunk
#(conf-if-eth1/1/7) switchport trunk allowed vlan 1502
#(conf-if-eth1/1/7) spanning-tree port type edge
Configure NVMe/TCP Storage Port
On ToR Switch 1:

port to be assigned to the node A.
interface.
control.


control.

#(conf-if-eth1/1/5) description "Node A IO Mod0 P0"
Activity: Configure LACP Port Channels for Nodes on

Data Switches
Virtual lab: Configure LACP Port Channels

for Nodes on Data Switches.

Configure Core Switching Uplinks on ToR Data Switch

1
Follow these steps to configure core switching uplinks on the ToR data
switch 1. When finished, repeat these steps on data switch 2.
Configure uplink port channel
Configure uplink port channel on data switch 1.

channel.
2. Run description <description> to add a description to the
LACP port channel.
port channel.
VLAN IDs> to allow traffic for Storage and NAS VLANs over the port
channel.


8. Run exit to exit the new port channel configuration mode.

core switch uplink"
#(conf-if-po-30) switchport trunk allowed vlan
1502,1503,1505,1506,1507
Activate Interface for port channel
Data switch 1 ports 53 and 54 assigned to port channel 30.

port to be assigned to the port channel.
2. Run description <description> to add a description to the port.
3. Run no shutdown to activate the port.

4. Run channel-group <ID> mode active to set the port channel

active on this port.
5. Run no switchport to disable L2 mode on the port.
control.
7. Run flowcontrol transmit off to turn off interface receive flow
control.
control.
control.
16. Run end to end the current configuration.


#(conf-if-eth1/1/53) description Uplink_port
#(config) intereface ethernet 1/1/54
Activity: Configure Core Switching Uplinks on Data

switches
Virtual lab: Configure Core Switching Uplinks

on Data switches.

Storage Network and NAS Server Network

Configuration
With the ToR data switching configuration completed, storage and NAS
Server networking is now configured with the PowerStore Manager UI.
Storage Network Configuration
The storage network is configured using the information from the

completed Storage Network Configuration Worksheet.
From PowerStore Manager, go to Settings > Network IPs > Storage.

Click CREATE to open the Create Storage Network wizard and configure
the storage network.
Example of storage network configuration.
NAS Server Network Configuration
For PowerStore T unified deployments, the NAS Server network is

configured when a NAS Server is created. Use the VLAN and IP
addressing for your NAS Server network.

From PowerStore Manager, go to Storage > NAS Servers. Click

CREATE to open the Create NAS Server wizard.
Example of NAS Server network addressing and VLAN.
Expand Storage Networking
There are two ways to expand a Storage network to run across multiple
ports on a PowerStore T appliance.
1. Expand the existing iSCSI network to additional PowerStore ports.
2. Create an additional iSCSI storage network on different available
PowerStore ports.
The training covers this second aspect to expand a Storage network.

To expand storage networking, cable the specific unused node ports to
the data switches. In this example, a new storage network is being created
using port 2 of the mezz card of both PowerStore nodes. Node A and
Node B must be cabled to opposite switches. In this example, node B

mezz card port 2 is cabled to data switch 1 port 3. Node A mezz card port
2 is cabled to data switch 2 port 3.
Expand storage networking
Expand Storage Networking on ToR Data Switch 1
Follow these steps to create a new storage network to expand PowerStore

storage networking. When finished, repeat these steps on data switch 2.
New Storage VLAN
Create a new storage network VLAN.

Data switch 1 with new Storage VLAN.
1. Run interface vlan <ID> to create a Storage VLAN.

the Storage VLAN.

#(conf-if-vl-1504) description Storage_Network2

Configure switchport for Node B
Node B switchport configuration.

port to be assigned to the node B.
interface.
control.
control.


#(conf-if-eth1/1/3) description "Node B port 2"
1. Run interface port-channel <number> to the port channel.

traffic for the new Storage VLAN over the port channel.

#(conf-if-po-30) end

Activity: Expand Storage Networking on Data Switches
Virtual lab: Expand Storage Networking on

Data Switches.

PowerStore T Licensing
PowerStore Licensing Overview
Overview
 If PowerStore has no installed license, there is a 30-day trial period to

request and install a license—either using Auto-Licensing or manually.
 If there is an unblocked connection, automatic licensing occurs using
the Internet to the license server.
 Automatic licensing connects to the license server using the Secure
Connect Gateway tunnel if no Internet connection is available.
 The failover to the Secure Connect Gateway tunnel is automatic. There
are no commands to enable or disable it.
 When an appliance is removed from the cluster, the licenses are
erased from the appliance.
 Upgrading a cluster does not impact the licenses.
Automatic Licensing
License features:
 Initial Configuration Wizard (ICW) installs a license to each appliance
automatically.
 License is all-inclusive and permanent.
 Features, such as replication, snapshots, migration, and so forth,
do not require separate licenses.
Important: PowerStore license does not include the VMware

vSphere license. For PowerStore X cluster licensing, obtain a
separate VMware vSphere license.
 Liense Management is centralized and run from the primary appliance.

 The primary appliance is the point of contact for all appliances.

 The system sends a request to Dell Technologies over HTTPS.
 Port 443 must be open.

If Internet access is temporarily unavailable:
 A default temporary 30-day trial license is used.
 Auto install tries three times, and then daily for the 30-day period.
 Each appliance installs its own license.
Elicensing failover flow
Auto-Licensing sequence:
1. PowerStore node requests license from Dell Electronic Licensing
Management System (ELMS) over standard Internet connection.
2. ELMS processes license file and sends it back to PowerStore node.
3. If direct request fails and PowerStore has valid Support configuration,
node automatically sends request through Secure Connect Gateway
tunnel ESE /elms API.
4. ELMS processes license file and sends it back to PowerStore node
using Secure Connect Gateway tunnel.

Manual Licensing
Complete Initial Configuration and start I/O without licensing.
If the automatic licensing is not installed correctly, the system provides

options.
 Run the ICW and start I/O using the default temporary 30-day
license.
 The trial period allows all features and functions to be available
without interruption.
 Automatic licensing is retried once per day until the license is
successfully installed.
 During the temporary license period, the system generates Alerts
periodically to install the license.
 If the expiration date is within a week, the alerts severity increases
to Minor.
 Click Refresh on the PowerStore Licensing page to retry auto
license installation without waiting 24 hours.
 If auto install does not work, the system generates an alert with
diagnostic information.
 Dark sites may use Manual Licensing since there is no outside
access.
 Perform a manual license installation with PowerStore Manager or

REST API.
PowerStore License Flow Without Internet Access
The example shows the default behavior on a newly initialized PowerStore

storage system without Internet access.
1. After the ICW completes, log in to the system and select Settings >
Licensing > INSTALL LICENSE
2. Select CONTINUE WITH TRIAL LICENSING or CONFIGURE
LICENSE.

The trial period is determined from the time the PowerStore was initialized.
License installation without Internet access
PowerStore License Manual Installation Flow
Manually installing a license requires two steps. In the example, the trial
license displays an expiration date 30 days after the PowerStore has been
initialized. To install a new license, select Licensing > INSTALL
LICENSE.
1. Export the PowerStore Activation file to the local machine. Upload the
Activation file to Software Licensing Central and retrieve the license
file. Account access is part of the purchase of the PowerStore system.
2. Upload the license file to activate the PowerStore license.
Important: if there are multiple appliances, all appliances

must have a valid license installed before the Active status is
displayed.
A successful license installation displays an Active status, replacing the

Trial status shown here.

Manual license installation steps
Trial License Extension
Trial license expiration:

 After a trial license expires, storage objects continue to function.
However, no new resources can be created until the license is
rectified.
 If multiple appliances in single cluster are added in different times, the
trial license expires based on the first appliance that was added.
To check the status of the license from the PSTCLI:

 Create a PSTCLI session: pstcli -d <PowerStore_address> -
session -u admin -p <password>
 Show the license status:
 license show
 For example:

 This system is using a temporary license.

 When a trial license expires, PowerStore switches into Read-Only
mode, but allows one time extension of trial period for additional 7
days.
 When you try to extend a second time, a dialog indicates that no
additional trial extension is possible. Install a permanent license.
Practice: Licensing Status
Hint

PowerStore T Implementation Key Points
PowerStore T switch configuration:

1. PowerStore T uses switches--one management switch and two data
switches.
2. VLTi or another Multi-Chassis Link Aggregation Group (MC-LAG)
solution is recommended for interconnectivity between the switches.
 Reliable L2 Links or Dynamic LAG should be used only if an MC-
LAG solution like VLTi is not an option.
3. VLANs and ranges of IP addresses must be identified before
configuring the switches.
4. When setting up the switches, consult the Network Setup Preparation
Worksheet that is part of the Networking Guide for PowerStore T
Models.
These processes enable a new PowerStore to be discovered and

configured:
1. PowerStore Discovery with a Direct Connection—user is connected
directly to the PowerStore service port on node A. This is the
recommended procedure and requires that you are physically present
in the data center or lab where the base enclosure is installed.
2. PowerStore Discovery with a Remote Connection— Using the
PowerStore Discovery Utility, discovers new unconfigured appliances
and makes them available to the Initial Configuration Wizard.
3. Initial Configuration Wizard—Allows you to set up IP addresses and
user credentials for the system. For a smooth installation, be prepared
with a completed Initial Configuration Worksheet.

Deep Dive: For more information and planning worksheet

templates, see the Networking Guide for PowerStore T
Models on the PowerStore Info Hub.

Appendix
Link Aggregation
Link Aggregation Overview
A Link Aggregation Group (LAG) is a combined collection of physical

network ports on a switch or host.
Ethernet LAG implementations may follow vendor-dependent or an open

standard such as Link Aggregation Control Protocol (LACP).
LACP is a control protocol to set up and control LAGs.
 LACP is defined in the IEEE 802.3ad standard.

 LAG and LACP combine multiple network connections to form a
logical connection.
 Link Aggregation is also referred to as bonding, channeling, or
teaming.

Appendix
 LAG is used to increase throughput and redundancy.

 Configuration must be performed within each host operating system
and network switch.
 Host side – Set up a link aggregation across two or more network

interfaces.
 Switch side – Set up a port channel aggregating two or more switch
interface ports.
VLAN Overview
If the video fails to play on the screen click here.
Movie:
The web version of this content contains a movie.
PowerStore Discovery
After the management switch and the network have been configured, the
PowerStore is ready for discovery and initialization.
Connection
PowerStore uses connected network to discovery appliances

Appendix
The PowerStore Discovery Utility uses the IDN network to discover

appliances. It runs from a discovery system on the same 169.254.x.x link
local network, using a browser that has Zeroconf networking capabilities.
1. Download the PowerStore Discovery Utility to the discover system.
2. Connect the discovery system by Ethernet cable to the switch port
configured for discovery. Administrator permissions are not required.
3. Configure IP on the discovery system.
Tip: For discovery, the switches must pass untagged

discovery traffic.

Appendix
Process
Step 1. Once Step 2. All discovered Step 3. Select the

physically connected, appliances are listed. appliances and create
scan for available the cluster.
appliances.
PowerStore Discovery
PowerStore Discovery Utility appliance selected
PowerStore Discovery Utility appliances found
Utility Start
Safeguards
There are a few safeguards in place.

Appendix
Unsupported configurations: No appliances found. The

The PowerStore Discovery Utility PowerStore Discovery Utility
prevents picking unsupported shows a message and suggestions
configurations. For example, on how to fix the problem.
combining PowerStore X and T
models in a single cluster or
selecting more than four
PowerStore T appliances is not
allowed.
No appliances found warning
Note: If the firewall cannot be

disabled, use TCP/UDP port 5353.
Warning that the combination of

appliances selected is not valid

Appendix
Troubleshooting
If you cannot get to the cluster using the usual methods, the tool discovers
unconfigured and configured appliances, and can be used in
troubleshooting.
Step 1. Select the Configured tab Step 2. Appliances that are

to see the configured appliances. already configured are listed and
can be accessed from this screen.
No appliances found message List of configured appliances

Appendix
Connect to a Data Switch

To configure the switch settings, with the switch running, connect a serial
cable to a laptop with a terminal emulator program.
Use these connection settings:

 Baud rate: 115200 (9600 for micro-USB port)
 Data bits: 8
 Parity: None
 Stop bits: 1
 Flow Control: None
Configure General Settings on Top-of-Rack (ToR) Data

Switch 2
2.

Appendix
Validate version and licensing
Connect serially to data switch 2.
The commands on this page affect the data switch connections, which are shown here.
1. Log in with the default admin/admin credentials.

2. Run show version to display and verify the operating system on the
switch.
– PowerStore requires OS10 Enterprise Edition (OS10EE).
# show version
Dell EMC Networking OS10 Enterprise
Copyright (c) 1999-2019 by Dell Inc. All Rights
Reserved.
OS Version: 10.4.3.6
Build Version: 10.4.3.6.244
Build Time: 2019-08-20T00:26:44+0000
System Type: S5248F-ON
Architecture: x86_64
Up Time: 9 weeks 32 days 02:06:44
3. Run show license status to verify the license type on the switch.
Verify:
– License type is PERPETUAL.

Appendix
– License status is Active.
# show license status

System Information
------------------------------------------------------
---
Vendor Name : Dell EMC
Product Name : S5248F-ON
Hardware Version: A00
Platform Name : x86_64-dellemc_s5248f_c3538-ro
PPID : MX05RY1NCEM0095K06FX
Service Tag : GJJ00Q2
License Details
----------------
Software : OS10-Enterprise
Version : 10.4.3.6
License Type : PERPETUAL
License Duration: Unlimited
License Status : Active
License location: /mnt/license/GJJ00Q2.lic
------------------------------------------------------
---
Hostname

Appendix
Set the hostname for data switch 2.

#configure terminal
#(config) hostname Data_Switch_2

Appendix
Switch management IP
Identify the management port on data switch 2.

management switch.
purposes.
5. Run exit to exit the switch configuration.
#(config) interface mgmt 1/1/1

#(config-if-ma-1/1/1) no shutdown
#(config-if-ma-1/1/1) no ip address dhcp
#(config-if-ma-1/1/1) ip address 172.17.57.30/24
#(config-if-ma-1/1/1) exit

Appendix
S5248F-ON switch back view.
Set the management route and NTP server for data switch 2.



Appendix
Spanning Tree

priority.
to use.

#(config) end
Commit and Disconnect

Appendix
1. Run copy running-configuration startup-configuration

to commit the configuration as the configuration run on switch startup
and copies the config to the startup.
2. Run exit to exit the session.
# copy running-configuration startup-configuration

# exit
Spanning Tree Data Switch 2

2.

priority.
to use.

Appendix

#(config) end
Spanning Tree Overview

If the video fails to play on the screen click here.
Movie:
Configure VLANs on ToR Data Switch 2

Follow these steps to configure VLANs on the ToR data switch 2.
Cluster VLAN 1
Data switch 2 VLAN for internal network.
1. Run interface vlan <ID> to create the cluster VLAN.

the VLAN.

Appendix


#(conf-if-vl-1) description Internal_Network
iSCSI Storage VLAN
Data switch 2 with Storage VLAN.
1. Run interface vlan <ID> to create an iSCSI Storage VLAN.


#(conf-if-vl-1502) description Storage_Network

Appendix
NAS VLAN
Data switch 2 with NAS VLAN.
1. Run interface vlan <ID> to create a NAS VLAN.

the NAS VLAN.
#(conf-if-vl-1502) interface vlan 1503

#(conf-if-vl-1503) description NAS_Network
#(conf-if-vl-1503) end
NVMe/TCP Storage VLAN

Appendix
Data switch 2 with NVMe/TCP Storage VLAN.
1. Run interface vlan <ID> to create an NVMe/TCP Storage VLAN.


#(conf-if-vl-1505) description NVMe_Storage_Network
Replication and Block Import VLAN

Appendix
Data switch 2 with Replication and Block Import VLAN.
1. Run interface vlan <ID> to create the Replication and Block

Import VLAN.

#(conf-if-vl-1506) description
Replication_Block_Import_Network
File Import VLAN

Appendix
Data switch 2 with File Import VLAN.
1. Run interface vlan <ID> to create the File Import VLAN.


#(conf-if-vl-1507) description File_Import_Network
Configure VLT on ToR Data Switch 2

Follow these steps to configure VLT on the ToR data switch 2.
Disable L2 Mode on VLT Ports

Appendix
1. Run interface range ethernet chassis/slot/port-

chassis/slot/port to identify the range of 100 GbE ports to have
L2 mode disabled. These ports are used for VLT interconnects.
ports.
3. Run no switchport to disable L2 mode on the identified ports.
4. Run no shutdown to enable the ports.
#(config) interface range ethernet 1/1/55-1/1/56

#(conf-range-eth1/1/55-1/1/56) description VLTi
#(conf-range-eth1/1/55-1/1/56) no switchport
#(conf-range-eth1/1/55-1/1/56) no shutdown
#(conf-range-eth1/1/55-1/1/56) exit
S5248F-ON switch front view.
Create VLT Domain, Interfaces, and Heartbeat

Appendix
1. Run vlt-domain <ID> to create a VLT domain.

2. Run discovery-interface ethernet chassis/slot/port-
chassis/slot/port to add the two VLT ports to the new domain.
3. Run backup destination <IP address of the other
switch> to set the other switch as VLT backup, which is required for
VLT heartbeat.
#(config) vlt-domain 1
#(conf-vlt-1) discovery-interface ethernet 1/1/55-
1/1/56
#(conf-vlt-1) backup destination 172.17.57.20
Example of PowerStore rack with one management switch and two data switches.

Appendix
Set Peer Routing, Switch Priority, and MAC
1. Run peer-routing to enable routing to the peer.

2. Run primary-priority <number from 1-65535> to set the
priority of the switch.
– Switches with lower numbers take priority over switches with higher
numbers.
3. Run vlt-mac <MAC address> to enter a unique made up MAC
address to ensure that a real MAC address is not reused. Configure
the same VLT MAC on both switches.
#(conf-vlt-1) peer-routing
#(conf-vlt-1) primary-priority 8192
#(conf-vlt-1) vlt-mac 00:00:00:00:00:01
#(conf-vlt-1) end
VLT Overview
Movie:
Click to open the video on a new browser tab.

Appendix
Configure LACP Port Channels for PowerStore Cluster

data switch 2.

channel.

channel for Node A"

port channel.

Appendix


channel.

channel for Node B"


Appendix


control.
control.
control.
control.

Appendix

Configure LACP Port Channels for PowerStore NAS

data switch 2.

channel.

Appendix

for Node A"



channel.

Appendix

for Node B"



control.

Appendix

control.
control.
control.


Appendix
Configure Ports for PowerStore Storage Networks on

Data Switch 2
Follow these steps to configure PowerStore network ports.
Configure iSCSI Storage Port
On ToR Switch 2:

interface.
control.
control.

#(conf-if-eth1/1/7) description "Node B IO Mod0 P1"

Appendix
Configure NVMe/TCP Storage Port
On ToR Switch 2:

interface.
control.
control.

#(conf-if-eth1/1/5) description "Node B IO Mod0 P0"

Appendix
Configure Core Switching Uplinks on ToR Data Switch

2
Follow these steps to configure core switching uplinks on the ToR data
switch 2.

channel.
2. Run description <description> to add a description to the
LACP port channel.
port channel.
VLAN IDs> to allow traffic for Storage and NAS VLANs over the port
channel.

Appendix

8. Run exit to exit the new port channel configuration mode.

core switch uplink"
#(conf-if-po-30) switchport trunk allowed vlan
1502,1503,1505,1506,1507
Activate Interface for port channel
Data switch 2 ports 53 and 54 assigned to port channel 30.


Appendix

control.
control.
control.
control.
16. Run end to end the current configuration.

Appendix

#(config) intereface ethernet 1/1/54
Expand Storage Networking on ToR Data Switch 2

Follow these steps to create a new storage network to expand PowerStore
storage networking.
New Storage VLAN
Create a new storeage network VLAN

Appendix
Data switch 2 with new Storage VLAN.
1. Run interface vlan <ID> to create a Storage VLAN.

the Storage VLAN.

#(conf-if-vl-1504) description Storage_Network2
Configure switchport for Node A

Appendix
Node A switchport configuration.

interface.
control.
control.

Appendix

#(conf-if-eth1/1/3) description "Node A port 2"
1. Run interface port-channel <number> to the port channel.

traffic for the new Storage VLAN over the port channel.

#(conf-if-po-30) end

Appendix
Trial License Extension
To check the status of the license from the PSTCLI:

 Create a PSTCLI session: pstcli -d <PowerStore_address> -
session -u admin -p <password>
 Show the license status:
 license show
 For example:
 This is a temporary license.

 When a trial license expires, PowerStoreOS 2.x and earlier versions
prompt you to install a new license, either online or from a downloaded
file.
Trail license is still valid.

Appendix
 When a trial license expires, PowerStoreOS 3.0 switches into Read-

Only mode, but allows one time extension of trial period for additional
7 days.
Trial license has expired. Install full license or extend trial.
 When you try to extend a second time, a dialog indicates that no

additional trial extension is possible. Install a permanent license.
License is already extended. Install full license.


PowerStore 3.0 PowerStore T Implementation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PowerStore 3.0 PowerStore T Implementation

Uploaded by

Copyright:

Available Formats

POWERSTORE 3.

© Copyright 2023 Dell Inc Page 2

PowerStore T Networking Concepts 7

PowerStore T Implementation Process 18