Browse Source

Merge "Manila VMAX docs - improve pre-configurations on VMAX section" into stable/rocky

tags/7.2.0
Zuul 2 months ago
parent
commit
c90c42d985

+ 82
- 35
doc/source/configuration/shared-file-systems/drivers/dell-emc-vmax-driver.rst View File

@@ -66,37 +66,45 @@ using the Data Movers on the array.
66 66
 Pre-configurations on VMAX
67 67
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
68 68
 
69
-#. Enable Unicode on Data Mover.
69
+#. Configure a storage pool
70 70
 
71
-   The VMAX driver requires that the Unicode is enabled on Data Mover.
71
+   There is a one to one relationship between a storage pool in embedded NAS
72
+   to a storage group on the VMAX. The best way to provision
73
+   storage for file is from the Unisphere for VMAX UI rather than eNAS UI.
74
+   Go to :menuselection:`{array} > SYSTEM > FIle` and under
75
+   :menuselection:`Actions` click :menuselection:`PROVISION STORAGE FOR FILE`
72 76
 
73
-   .. warning::
77
+   .. note::
78
+
79
+      When creating a new storage group you have the ability to assign a
80
+      service level e.g. Diamond and disable compression/deduplication
81
+      which is enabled by default.
74 82
 
75
-      After enabling Unicode, you cannot disable it. If there are some
76
-      file systems created before Unicode is enabled on the VMAX,
77
-      consult the storage administrator before enabling Unicode.
83
+   To pick up the newly created storage pool in the eNAS UI,
84
+   go to :menuselection:`{Control Station} > Storage > Storage Configuration > Storage Pools`
85
+   and under :menuselection:`File Storage` click :menuselection:`Rescan Storage Systems`
78 86
 
79
-   To check the Unicode status on Data Mover, use the following VMAX eNAS File
80
-   commands on the VMAX control station:
87
+   or on the command line:
81 88
 
82 89
    .. code-block:: console
83 90
 
84
-      server_cifs <MOVER_NAME> | head
85
-      # MOVER_NAME = <name of the Data Mover>
91
+      $ nas_diskmark -mark -all -discovery y -monitor y
86 92
 
87
-   Check the value of I18N mode field. UNICODE mode is shown as
88
-   ``I18N mode = UNICODE``.
93
+   The new storage pool should now appear in the eNAS UI
89 94
 
90
-   To enable the Unicode for Data Mover, use the following command:
95
+#. Make sure you have the appropriate licenses
91 96
 
92 97
    .. code-block:: console
93 98
 
94
-      uc_config -on -mover <MOVER_NAME>
95
-      # MOVER_NAME = <name of the Data Mover>
99
+      $ nas_license -l
100
+      key                 status    value
101
+      site_key            online    xx xx xx xx
102
+      nfs                 online
103
+      cifs                online
104
+      snapsure            online
105
+      replicatorV2        online
106
+      filelevelretention  online
96 107
 
97
-   Refer to the document Using International Character Sets on VMAX for
98
-   File on `EMC support site <http://support.emc.com>`_ for more
99
-   information.
100 108
 
101 109
 #. Enable CIFS service on Data Mover.
102 110
 
@@ -107,9 +115,9 @@ Pre-configurations on VMAX
107 115
 
108 116
    .. code-block:: console
109 117
 
110
-      server_setup <MOVER_NAME> -Protocol cifs -option start [=<n>]
111
-      # MOVER_NAME = <name of the Data Mover>
112
-      # n = <number of threads for CIFS users>
118
+      $ server_setup <movername> -Protocol cifs -option start [=<n>]
119
+        # movername = name of the Data Mover
120
+        # n = number of threads for CIFS users
113 121
 
114 122
    .. note::
115 123
 
@@ -121,8 +129,8 @@ Pre-configurations on VMAX
121 129
 
122 130
    .. code-block:: console
123 131
 
124
-      server_cifs <MOVER_NAME> | head
125
-      # MOVER_NAME = <name of the Data Mover>
132
+      $ server_cifs <movername> | head
133
+        # movername = name of the Data Mover
126 134
 
127 135
    The command output will show the number of CIFS threads started.
128 136
 
@@ -137,7 +145,19 @@ Pre-configurations on VMAX
137 145
    a share with this security service. There is a limitation that the
138 146
    time of the domains used by security-services, even for different
139 147
    tenants and different share networks, should be in sync. Time
140
-   difference should be less than 10 minutes.
148
+   difference should be less than 5 minutes.
149
+
150
+   .. note::
151
+
152
+      If there is a clock skew then you may see the following error
153
+      "The local machine and the remote machine are not synchronized.
154
+      Kerberos protocol requires a synchronization of both participants
155
+      within the same 5 minutes". To fix this error you must make sure
156
+      the times of the eNas controller host and the Domain Controller
157
+      or within 5 minutes of each other. You must be root to change the
158
+      date of the eNas control station.  Check also that your time zones
159
+      coincide.
160
+
141 161
 
142 162
    We recommend setting the NTP server to the same public NTP
143 163
    server on both the Data Mover and domains used in security services
@@ -147,16 +167,16 @@ Pre-configurations on VMAX
147 167
 
148 168
    .. code-block:: console
149 169
 
150
-      server_date <MOVER_NAME>
151
-      # MOVER_NAME = <name of the Data Mover>
170
+      $ server_date <movername>
171
+        # movername = name of the Data Mover
152 172
 
153 173
    Set the NTP server for Data Mover with the following command:
154 174
 
155 175
    .. code-block:: console
156 176
 
157
-      server_date <MOVER_NAME> timesvc start ntp <host> [<host> ...]
158
-      # MOVER_NAME = <name of the Data Mover>
159
-      # host = <IP address of the time server host>
177
+      $ server_date <movername> timesvc start ntp <host> [<host> ...]
178
+        # movername = name of the Data Mover
179
+        # host = IP address of the time server host
160 180
 
161 181
    .. note::
162 182
 
@@ -174,16 +194,16 @@ Pre-configurations on VMAX
174 194
 
175 195
    .. code-block:: console
176 196
 
177
-      server_usermapper <movername>
178
-      # movername = <name of the Data Mover>
197
+      $ server_usermapper <movername>
198
+        # movername = name of the Data Mover
179 199
 
180 200
    If usermapper does not start, use the following command
181 201
    to start the usermapper:
182 202
 
183 203
    .. code-block:: console
184 204
 
185
-      server_usermapper <movername> -enable
186
-      # movername = <name of the Data Mover>
205
+      $ server_usermapper <movername> -enable
206
+        # movername = name of the Data Mover
187 207
 
188 208
    For a multiple protocol environment, refer to Configuring VMAX eNAS User
189 209
    Mapping on `EMC support site <http://support.emc.com>`_ for
@@ -194,8 +214,35 @@ Pre-configurations on VMAX
194 214
    Find the network devices (physical port on NIC) of the Data Mover that
195 215
    has access to the share network.
196 216
 
197
-   To check the device list, go
198
-   to :menuselection:`Unisphere > Settings > Network > Device`.
217
+   To check the device list on the eNAS UI go
218
+   to :menuselection:`{Control Station} > Settings > Network > Devices`.
219
+
220
+   or on the command line:
221
+
222
+   .. code-block:: console
223
+
224
+      $ server_sysconfig server_2 -pci
225
+      server_2 : PCI DEVICES:
226
+
227
+      On Board:
228
+        VendorID=0x1120 DeviceID=0x1B00  Controller
229
+          0:  scsi-0  IRQ: 32
230
+
231
+          0:  scsi-16  IRQ: 33
232
+
233
+          0:  scsi-32  IRQ: 34
234
+
235
+          0:  scsi-48  IRQ: 35
236
+
237
+        Broadcom 10 Gigabit Ethernet Controller
238
+          0:  fxg-3-0  IRQ: 36
239
+          speed=10000 duplex=full txflowctl=disable rxflowctl=disable
240
+          Link: Up
241
+
242
+           0:  fxg-3-1  IRQ: 38
243
+          speed=10000 duplex=full txflowctl=disable rxflowctl=disable
244
+          Link: Down
245
+
199 246
 
200 247
 Back-end configurations
201 248
 ~~~~~~~~~~~~~~~~~~~~~~~

Loading…
Cancel
Save