Disk pools drop offline due to SAS enclosure ID collision when connecting secondary JBOD

I am connecting a secondary JBOD storage enclosure to our S2D node, but as soon as it is attached, the disk pools drop offline. The issue appears to be an enclosure ID collision on the SAS fabric, causing conflicting device paths across the nodes. How can we properly reassign the enclosure management IDs using SCSI command-line tools to resolve this conflict?