DFC devices are not automatically discovered after upgrade, reboot or FS restart

Summary: After an upgrade, reboot or FS restart, some servers can't see DFC device. VTL devices are working fine.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



Some servers configured with DFC devices can't see devices after upgrade, reboot or FS restart.
  • No issue found at FC level and VTL devices configured on same servers (different initiators) are correctly discovered after the upgrade.
  • Found in the field with Windows hosts, but other O/S types may be affected as well
  

 

Cause

Client sent PLOGI and PRLI before the DFCuser daemon restarted after the upgrade and established a session. After the DFCuser daemon restarted a LINK FAILURE and LINK REINIT occurred and the established session was deleted as a result.

The session will not re-establish properly again unless a there is a restart of the DFCuser daemon which triggers LINK events.

Session establishment depends on the client sending the LUN discovery SCSI FC command in this instance the client was not sending any FC SCSI commands after the LINK was re-established.

 

Resolution

Restart the DFC service by running the commands.

#ddboost option set fc disable

#ddboost option set fc enable

Affected Products

Data Domain

Products

Data Domain, DD860 Appliance
Article Properties
Article Number: 000059437
Article Type: Solution
Last Modified: 25 Sep 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.