mirror of
https://github.com/NetAppDocs/e-series-santricity.git
synced 2026-10-23 03:37:37 +09:00
Change host I/O module protocol edits
This commit is contained in:
driley committed
1 parent
94ba278729
commit
711930a589
6 files changed
+166
-7
No files matched your search
@@ -4,17 +4,17 @@
|
||||
a|
|
||||
Google Chrome
|
||||
a|
|
||||
89
|
||||
120
|
||||
a|
|
||||
Mozilla Firefox
|
||||
a|
|
||||
80
|
||||
120
|
||||
a|
|
||||
Safari
|
||||
a|
|
||||
14
|
||||
16
|
||||
a|
|
||||
Microsoft Edge
|
||||
a|
|
||||
90
|
||||
120
|
||||
|===
|
||||
@@ -290,6 +290,8 @@ sidebar:
|
||||
url: "/sm-storage/change-the-settings-for-a-host-cluster.html"
|
||||
- title: Change host port identifiers for host
|
||||
url: "/sm-storage/change-host-port-identifiers-for-a-host.html"
|
||||
- title: Change the host I/O module protocol
|
||||
url: "sm-storage/io-module-change-protocol.html"
|
||||
- title: Host systems and host clusters FAQ
|
||||
url: "/sm-storage/faq-systems-clusters.html"
|
||||
- title: Snapshots
|
||||
|
||||
@@ -18,7 +18,7 @@ By default, resource provisioning is enabled on systems where the drives support
|
||||
|
||||
.Before you begin
|
||||
|
||||
* You must have an EF80, EF50, EF300/EF300C, or EF600/EF600C storage array.
|
||||
* You must have an EF80, EF50, EF300, or EF600 storage array.
|
||||
* You must have SSD volume groups or pools, where all the drives support the NVMe Deallocated or Unwritten Logical Block Error Enable (DULBE) error recovery capability. Otherwise, the resource provisioning option is not available.
|
||||
|
||||
.About this task
|
||||
|
||||
@@ -472,7 +472,7 @@ The Additional Optimization Capacity slider is only available for EF600 and EF30
|
||||
|
||||
== What is resource provisioning capable?
|
||||
|
||||
Resource Provisioning is a feature available in the EF80, EF50, EF300/EF300C, and EF600/EF600C storage arrays, which allows volumes to be put in use immediately with no background initialization process.
|
||||
Resource Provisioning is a feature available in the EF80, EF50, EF300, and EF600 storage arrays, which allows volumes to be put in use immediately with no background initialization process.
|
||||
|
||||
A resource-provisioned volume is a thick volume in an SSD volume group or pool, where drive capacity is allocated (assigned to the volume) when the volume is created, but the drive blocks are deallocated (unmapped). By comparison, in a traditional thick volume, all drive blocks are mapped or allocated during a background volume initialization operation in order to initialize the Data Assurance protection information fields and to make data and RAID parity consistent in each RAID stripe. With a resource provisioned volume, there is no time-bound background initialization. Instead, each RAID stripe is initialized upon the first write to a volume block in the stripe.
|
||||
|
||||
@@ -482,7 +482,7 @@ Resource-provisioned volumes are supported only on SSD volume groups and pools,
|
||||
|
||||
== What do I need to know about the resource-provisioned volumes feature?
|
||||
|
||||
Resource Provisioning is a feature available in the EF80, EF50, EF300/EF300C, and EF600/EF600C storage arrays, which allows volumes to be put in use immediately with no background initialization process.
|
||||
Resource Provisioning is a feature available in the EF80, EF50, EF300, and EF600 storage arrays, which allows volumes to be put in use immediately with no background initialization process.
|
||||
|
||||
A resource-provisioned volume is a thick volume in an SSD volume group or pool, where drive capacity is allocated (assigned to the volume) when the volume is created, but the drive blocks are deallocated (unmapped). By comparison, in a traditional thick volume, all drive blocks are mapped or allocated during a background volume initialization operation in order to initialize the Data Assurance protection information fields and to make data and RAID parity consistent in each RAID stripe. With a resource provisioned volume, there is no time-bound background initialization. Instead, each RAID stripe is initialized upon the first write to a volume block in the stripe.
|
||||
|
||||
|
||||
@@ -0,0 +1,155 @@
|
||||
---
|
||||
permalink: sm-storage/io-module-change-protocol.html
|
||||
sidebar: sidebar
|
||||
keywords: host protocol change, EF50, EF80
|
||||
summary: You can change the protocol on the host I/O modules in your EF50 or EF80 storage system when you need to use a different protocol on your existing I/O modules, as part of an I/O module upgrade, or when the default protocol on new controllers part of a new storage system installation or controller upgrade is not the protocol you want.
|
||||
---
|
||||
= Change the host I/O module protocol - EF50 and EF80
|
||||
:experimental:
|
||||
:icons: font
|
||||
:imagesdir: ../media/
|
||||
|
||||
[.lead]
|
||||
// You can change the host port protocol on I/O modules using either Infiniband (IB) or Fibre Channel (FC) in an EF50 or EF80 storage system.
|
||||
|
||||
You can change the protocol on the host I/O modules for your controllers storage when you need to use a different protocol on your existing I/O modules, as part of an I/O module upgrade, or when the default protocol on new controllers part of a new storage system installation or controller upgrade is not the protocol you want.
|
||||
|
||||
// I'm not addressing all these use cases here? Only the change on existing modules? For the other 3 use cases, I need to embed steps in the right place for each procedure and each version of steps would mostly be unique per the use case? I need to understand if I got the uses cases right. TK seemed to think upgrading a module had nothing to do with changing the protocol, but customer would upgrade
|
||||
|
||||
.About this task
|
||||
|
||||
* Changing the protocol on the host I/O modules involves preparing for the protocol change, stopping the host I/O operations, changing the protocol, and then configuring the host to use the new protocol.
|
||||
|
||||
* The protocol is changed on all host I/O modules in your storage system.
|
||||
|
||||
* Changing the protocol on the host I/O modules temporarily disrupts host access to all volumes and causes the storage system to be unavailable during the reboot process (both controllers are rebooted), which can take a few minutes.
|
||||
|
||||
//* New storage system installations and new controllers being used in a controller upgrade ship with a default host protocol. You need to check if the default host protocol is what you want and if not, you need to change it.
|
||||
|
||||
|
||||
== Step 1: Prepare for the protocol change
|
||||
|
||||
Prepare to change the protocol on the host I/O modules in your storage system by verifying the current protocol on the host I/O modules, determining if you need to change the protocol, and if yes, scheduling a downtime maintenance window, and obtaining any necessary hardware.
|
||||
|
||||
//Need to create includes
|
||||
//syntax example:
|
||||
// include::../_include/ge_io_module_upgrade_power_off_controllers.adoc[]
|
||||
|
||||
.Steps
|
||||
|
||||
. If you do not know the current protocol on the host I/O modules in your storage system, verify it using SANtricity System Manager.
|
||||
|
||||
.. Select *Settings* > *System*.
|
||||
.. In the *Additional Settings* section, click *Change host I/O protocol* to open that page.
|
||||
.. See the default protocol used on the host I/O modules in your storage system displayed in the *Host I/O Protocol* field.
|
||||
|
||||
. The next step depends on whether the default protocol is the protocol you want or not:
|
||||
+
|
||||
[options="header" cols="1,2"]
|
||||
|===
|
||||
|If...| Then...
|
||||
a|
|
||||
The default protocol is the protocol you want
|
||||
a|
|
||||
No action is needed. You can exit this procedure.
|
||||
a|
|
||||
The default protocol is not the protocol you want
|
||||
a|Continue with this procedure to change the protocol.
|
||||
|===
|
||||
//+
|
||||
//+
|
||||
//. The next step depends on whether you need to change the protocol or not:
|
||||
//+
|
||||
//[options="header" cols="1,2"]
|
||||
//|===
|
||||
//|If...| Then...
|
||||
//a|
|
||||
//If you need to change the protocol
|
||||
//a|
|
||||
//Continue to the next step and then complete this procedure.
|
||||
//a| If you do not need to change the protocol...| Then you can skip to the next section.
|
||||
//|===
|
||||
//+
|
||||
. Schedule a downtime maintenance window for this procedure.
|
||||
|
||||
. If needed, obtain the necessary hardware for the conversion, which might include a new set of I/O modules and/or SFPs. Your NetApp Sales Representative can help you determine what hardware you need and help you order the correct parts.
|
||||
|
||||
|
||||
== Step 2: Stop host I/O operations
|
||||
|
||||
You must stop all I/O operations from the host before changing the protocol on the host I/O modules.
|
||||
|
||||
NOTE: You cannot access data on the storage system until you successfully complete the protocol change.
|
||||
|
||||
//Need to create includes
|
||||
//syntax example:
|
||||
// include::../_include/ge_io_module_upgrade_power_off_controllers.adoc[]
|
||||
|
||||
.Steps
|
||||
|
||||
. Ensure that no I/O operations are occurring between the storage system and all connected hosts. For example, you can perform these steps:
|
||||
** Stop all processes that involve the LUNs mapped from the storage to the hosts.
|
||||
** Ensure that no applications are writing data to any LUNs mapped from the storage to the hosts.
|
||||
** Unmount all file systems associated with volumes on the storage system.
|
||||
+
|
||||
NOTE: The exact steps to stop host I/O operations depend on the host operating system and the configuration, which are beyond the scope of these instructions. If you are not sure how to stop host I/O operations in your environment, consider shutting down the host or contact https://mysupport.netapp.com/site/global/dashboard[NetApp Support^].
|
||||
+
|
||||
CAUTION: *Possible data loss* -- If you continue this procedure while I/O operations are occurring, you might lose data.
|
||||
|
||||
. On each controller, make sure the NV Caching Active (green) LED is off.
|
||||
+
|
||||
When the NV Caching Active (green) LED is off, any data in cache memory has been written to the drives and it is safe to continue with the procedure.
|
||||
+
|
||||
NOTE: If the NV Caching Active (green) LED is on, cached data is being written to the drives. You must wait for the process to complete and the NV Caching Active (green) LED to turn off. However, if the LED remains on for longer than five minutes, contact https://mysupport.netapp.com/site/global/dashboard[NetApp Support] before continuing with this procedure.
|
||||
+
|
||||
The NV Caching Active (green) LED is located next to the NV icon on the controller.
|
||||
+
|
||||
image::../media/drw_g_nvmem_led_ieops-1839.svg[NV status LED location]
|
||||
+
|
||||
[cols="1,4"]
|
||||
|
||||
|===
|
||||
a|
|
||||
image::../media/icon_round_1.png[Callout number 1]
|
||||
a|
|
||||
NV icon and NV Caching Active LED on the controller
|
||||
|===
|
||||
+
|
||||
|
||||
. Confirm operations on the controllers have completed in SANtricity System Manager:
|
||||
.. Select *Storage* > *Operations in progress* to see the Overview screen.
|
||||
.. Wait for all operations to complete and the Overview screen displays *No operations currently in progress*, before continuing to the next step.
|
||||
|
||||
== Step 3: Change the protocol
|
||||
|
||||
Change the protocol on the host I/O modules to a supported protocol, using SANtricity System Manager.
|
||||
|
||||
//Need to create includes
|
||||
//syntax example:
|
||||
// include::../_include/ge_io_module_upgrade_power_off_controllers.adoc[]
|
||||
|
||||
.Steps
|
||||
|
||||
. Select *Settings* > *System*.
|
||||
. In the *Additional Settings* section, click *Change host I/O protocol* to open that page.
|
||||
. In the *Host I/O Protocol* field, click the drop-down menu and choose the protocol you want to use.
|
||||
. Type *CHANGE* in the open field to confirm your change.
|
||||
. Click the *Change* button.
|
||||
|
||||
== Step 4: Configure the host to use the new protocol
|
||||
|
||||
After changing the protocol of the host ports, you must configure the host to use the new protocol.
|
||||
|
||||
//Need to create includes
|
||||
//syntax example:
|
||||
// include::../_include/ge_io_module_upgrade_power_off_controllers.adoc[]
|
||||
|
||||
For step-by-step instructions, see the guide appropriate for your storage system:
|
||||
|
||||
* link:../config-linux/index.html[Linux express configuration]
|
||||
+
|
||||
* link:../config-vmware/index.html[VMware express configuration]
|
||||
+
|
||||
* link:../config-windows/index.html[Windows express configuration]
|
||||
+
|
||||
Specific settings might vary. Check the http://mysupport.netapp.com/matrix[NetApp Interoperability Matrix^] for specific instructions and additional recommended settings for your solution.
|
||||
@@ -23,6 +23,8 @@ a|This release introduces the EF80 and EF50 all-NVMe-flash storage systems. The
|
||||
High-capacity NVMe SSD drives of 30TB or 60TB sizes are also supported with the EF80 and EF30. The EF80 and EF30 is compatible for Dynamic Disk Pool use only with no legacy RAID support.
|
||||
a|New user interface for SANtricity System Manager
|
||||
a|For the new EF80 and EF50 controllers, the SANtricity System Manager user interface has been redesigned to provide a more modern look and feel. The new interface includes a left-panel navigation and enhanced usability to streamline management tasks.
|
||||
+
|
||||
NOTE: The new user interface is currently available only for the EF80 and EF50 storage systems with the SANtricity 12.0 release. If you are using SANtricity 11.9 or older, please refer to link:https://docs.netapp.com/us-en/e-series-santricity-119/system-manager/index.html[SANtricity System Manager 11.9] for instructions on using the legacy user interface.
|
||||
|===
|
||||
|
||||
[cols="35h,~",options="header"]
|
||||
|
||||
Reference in new issue
Block a user