How to Restore an EoIB Datalink That Failed During Migration

Language:

EoIB datalinks in previous Oracle Solaris releases existed as phys class datalinks similar to regular Ethernet datalinks. If you upgrade to Oracle Solaris 11.2 , existing EoIB datalinks on the system are automatically migrated to the new eoib class datalinks.

If you also plan to upgrade the gateway firmware, upgrade the OS first to ensure the proper migration of the Oracle Solaris EoIB instances to the new datalink class. Then, upgrade the gateway firmware.

Note that automatic migration only partially succeeds if the original gateway Ethernet port instances corresponding to the existing phys class datalinks are unavailable at the time of the upgrade. You must complete the migration manually.

Become an administrator.
Identify any EoIB datalink that has not been fully migrated.
```
# dladm show-eoib
```
Information would be missing for datalinks that have not successfully migrated, such as in the following example:
```
# dladm show-eoib
LINK   GWNAME GWPORT GWID FLAGS  SPEED MACADDRESS  OVER
eib2   ?      ?      1A8  ------ 10000 0:0:0:0:0:0 ibp1
```
Determine the gateway system name and Ethernet port corresponding to the GWID.
The gateway/IB fabric administrator can determine this information from knowledge of the configuration and by using appropriate tools on the gateway.
Delete any existing VNICs, VLANs, or IP interfaces that might have been configured over the datalink.
Use the appropriate dladm and ipadm subcommands to remove existing VNICs, VLANs, and IP interfaces.
Delete the partially migrated EoIB datalink.
```
# dladm delete-eoib link
```
Recreate the EoIB datalink with the correct information.
```
# dladm create-eoib -l link -g gway -c gway-port eoib-link
```
link

Name of the physical link.

gway

Gateway name.

gway-port

Gateway Ethernet port.

eoib-link

Name of the EoIB datalink.
Recreate the VNICs, VLANs, or IP interfaces that you might have previously removed in Step 4.
Use the appropriate dladm and ipadm subcommands to recreate deleted VNICs, VLANs, and IP interfaces.

Example 3-16 Restoring an EoIB Datalink That Failed Migration

In this example, eib2 did not completely migrate. You have determined that eib2 had the following configurations prior to the migration:

eib2 was configured over the physical link ibp1.
The GWID is 1A8.
The gateway name is nm2gw-2.
The gateway port is 0a-eth-1.

After determining that all existing configurations over eib2 have been deleted, you proceed as follows:

# dladm delete-eoib eib2
# dladm create-eoib -l ibp1 -g nm2gw-2 -c 0a-eth-1 eib2