Data Migration from Insight Control server deployment to Insight Control server provisioning

12
The Fibre Channel HBA Configuration files are the exception in that they are not a Configuration File in IC server
provisioning. Refer to the above Fibre Channel HBA configuration files section.
To locate, copy and convert the hardware configuration or the operating system answer files to the rdpmigration
temporary location, from the RDP server and rdpmigration folder run rmu.exe /jobfiles.
Scripts
With IC server provisioning, the “Run Script” tasks and shell scripts should be stored as a Script.
For RDP, there are several Job “Run Script” tasks and shell scripts that call Scripting Toolkit utilities. For IC server
provisioning, the functionality are now Scripts. The Scripts’ parameters are the load, save, and configuation file names
similar to how “Run Script” tasks calls the shell scripts in RDP.
Table 5: RDP to IC server provisioning Scripting Toolkit mapping
Scripting Toolkit Functionality and
Utility
RDP eXpress Share Location and
Script
IC server provisioning Script
Name
System ROM Configuration, conrep
\hpfeatures\hw-
proliant\bin\conrep.sh
Manage System Configuration
System ROM reset, rbsueset
“Run Script” task only
Reset System Configuration
Smart Array configuration, hpacucli
\hpfeatures\hw-proliant\bin\acu.sh
Manage Smart Array Configuration
iLO configuration, hponcfg
\hpfeatures\hw-
proliant\bin\hponcfg.sh
Manage iLO Configuration
Fibre Channel HBA Qlogic
configuration, hpqlarep
\hpfeatures\hw-
proliant\bin\fchba.sh
Manage HBA Configuration
Fibre Channel HBA Emulex
configuration, hplpcfg
\hpfeatures\hw-
proliant\bin\fchba.sh
Manage HBA Configuration
Manual Procedure
“Run Script” Tasks
As with the RDP answer files, it is likely the “Run Script” Tasks included with RDP jobs will require modification to be used
with IC server provisioning. Since customized scripts can vary, there are no specific code lines to describe to change.
The following are best practices as to what might need to be changed:
1. Replace all @@aaaa@@ RDP macros.
2. Replace or comment out all references to RDP utilities, such as rdeploy or showdisk.
3. Replace all references to drive letters or drive references, such as system drives, RAM drives, mount points.
For Windows deployments in IC server provisioning,
o the system drive is usually referenced by the SystemDrive custom attribute with c: as the default.
o x: is the default RAM drive letter.
o z: is the default media server connection drive letter and the Set Media Source script is used to make
the media server connection.
For Linux and ESXi deployments in IC server provisioning,
o /mnt/ms or /mnt/media is the default media server mount point and the Set Media Source script
is used to make the media server connection.
4. Replace all references to RDP eXpress share location paths. Refer to Table 6: OS Distribution Folder Mapping
for references to the media server OS distribution locations.