Migrating a IPoIB subnet from default to custom IB partition
(Doc ID 1981575.1)
Last updated on SEPTEMBER 06, 2019
Applies to:
Big Data Appliance Hardware - Version Not Applicable to Not Applicable [Release N/A]Exadata X4-2 Full Rack - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Goal
To use a custom InfiniBand Partition instead of default and migrate the existing IPoIB subnet keeping all IP addresses same.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Steps to accomplish the task of migrating IPoIB from default to custom partition |
| Step 1: Identify an unused InfiniBand Partition key |
| Step 2: Determine if any node need to be added as limited member to the IB partition |
| Step 3: Collect all IB port GUIDs of the host compute nodes that need to be part of this new IB partition |
| Step 4: Identify the IB switch running master subnet manager |
| Step 5: Start IB partition editing on master SM switch |
| Step 6: Create IB partion on master SM switch |
| Step 7: Add all IB port GUIDs in the new IB partition |
| Step 8: Save and commit the switch configuration |
| Step 9: Verify that the IB partition information is propagated into all standby SM switches |
| Step 10: Backup current IPoIB configuration on all host compute nodes |
| Step 11: Migrate current IPoIB configuration into new IB partition based configuration |
| Step 12: Reboot first two host compute nodes one at a time |
| Step 13: Verify the connectivity between the rebooted nodes |
| Step 14: Reboot remaining host compute nodes one at a time |
| References |