Network service configuration
Before changing the network service to NVMe-TCP, please remember to remove iSCSI network portals while initiators are still connected.
We only allow changing the network service on eth2 between iSCSI and NVMe-TCP.
$ purenetwork eth setattr --servicelist nvme-tcp ct0.eth2 ct1.eth2
Name Enabled Type Subnet Address Mask Gateway MTU MAC Speed Services Subinterfaces
ct0.eth2 True physical - 10.135.3.78 255.255.255.0 10.135.3.1 9000 e2:cf:35:53:c3:14 100.00 Gb/s nvme-tcp -
ct1.eth2 True physical - 10.135.3.44 255.255.255.0 10.135.3.1 9000 32:0c:c4:0f:db:62 100.00 Gb/s nvme-tcp -
Note:
On the PAWS arrays, eth2 is the only port allowed configuring iSCSI and NVMe-TCP services.
Array Host and volume configuration
Array host and volume configuration follows the same procedure as the FlashArray. Please follow Connecting an NVMe-oF Initiator to a Volume.
Array scale limit
|
Description |
Limit |
|
Max # of hosts |
300 |
|
Max # of volumes |
800 |
|
Max # of LUNs (volumes) per host |
50 |