User guide

DataDirect Networks SFA™ OS 2.2.1.3 Release Notes Revision A1 | 16
2. modprobe ib_uverbs
3. modprobe mlx4_ib
4. opensm -g <
port GUID > (where port GUID is the port GUID from ibstat
output
5. run_srp_daemon -R 20 -T 10 -nce
-i < ca_name> -p <port> (where ca_name is
the channel adapter name and port is the port number)
6.0 Recommended Practices
The recommended best practices for SFA OS version 2.2.1.3 include:
• SS6000 DEM and I/O module replacement.
For SS6000 DEM and I/O module replacement, see the SFA OS User Guide for the
procedures.
• On hosts that are directly connected, if the configuration is cleared, the
Fibre Channel initiators may not log back into the subsystem.
This results in no initiators being available to assign to new presentations. To correct
this, do a rescan from the host before setting up your presentations.
This does not apply to the SFA12K-40 and SFA12K-20.
• Disk firmware upgrades.
Before performing a disk firmware upgrade, scp the .DDN file to both controllers.
This avoids a situation where a controller attempts to perform the upgrade but can’t
find the .DDN file.
• Firmware upgrades should be done during low usage periods whenever
possible.
As upgrading your system will interrupt I/O operations as paths fail over, be aware of
the possibility of increased I/O latencies during the upgrade operation. Prior to
upgrading your firmware, DDN recommends reviewing the system logs to ensure the
system is running cleanly. DDN also recommends allowing any rebuilds and forced
verify jobs to complete and pausing any running verify jobs.
When a controller is shut down, all cached data must be flushed before the controller
will shut down. This operation can take a considerable amount of time depending
upon the amount of cache and if the cached data is sequential vs. random, large block
vs. small block, number of VDs, and so on. Should the shutdown fail, an event will be
generated. If you do not see the event, the controller is still shutting down. Please
allow it to complete to avoid possible data loss issues.
• Update the secondary controller first.
When performing an SFA OS upgrade, upgrade the secondary controller first. Doing
this requires primary to move once instead of twice.