| Asset ID: |
1-72-2167305.1 |
| Update Date: | 2017-10-11 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2167305.1
:
Mx-32 Failure to Hotplug EMS holding boot device
| Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx-32
|
In this Document
Applies to:
SPARC M5-32 - Version All Versions to All Versions [Release All Releases]
SPARC M6-32 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
hotplug of an EMS (aka Base I/O Board) holding boot devices may fail with these errors:
hotplug utilizing 'cfgadm' command:
root@XXX-IO-A:~# cfgadm -c unconfigure IOU1-EMS1
Apr 21 06:27:30 XXX-IO-A genunix: WARNING: (pcieb3): failed to detach driver for the device (pcieb4) in the Connection IOU1-EMS1
Apr 21 06:27:30 XXX-IO-A genunix: WARNING: (pcieb3): failed to unconfigure the device in the Connection IOU1-EMS1
hotplug utilizing 'hotplug' command:
root@XXX-IO-A:~# hotplug offline /pci@700/pci@1/pci@0/pci@c pci.0,0
Apr 21 06:44:38 XXX-IO-A genunix: WARNING: (pcieb3): failed to detach driver for the device (pcieb4) in the Connection pci.0,0 ERROR: devices or resources are busy.
root@XXX-IO-A:~# hotplug offline /pci@700/pci@1/pci@0/pci@c/pci@0/pci@4 pci.0,0
Apr 21 07:44:36 XXX-IO-A genunix: WARNING: (pcieb6): failed to detach driver for the device (mpt_sas0) in the Connection pci.0,0 ERROR: devices or resources are busy.
root@XXX-IO-A:~# hotplug list -l
...
/pci@700
/pci@700 <pci.1,0> ONLINE
/pci@700/pci@1
/pci@700/pci@1 <pci.0,0> ONLINE
/pci@700/pci@1/pci@0
/pci@700/pci@1/pci@0 <pci.6,0> ONLINE
/pci@700/pci@1/pci@0/pci@6
/pci@700/pci@1/pci@0/pci@6 [IOU1-PCIE3] EMPTY
/pci@700/pci@1/pci@0 <pci.c,0> ONLINE
/pci@700/pci@1/pci@0/pci@c
/pci@700/pci@1/pci@0/pci@c [IOU1-EMS1] ENABLED <==========
/pci@700/pci@1/pci@0/pci@c <pci.0,0> ONLINE
/pci@700/pci@1/pci@0/pci@c/pci@0
/pci@700/pci@1/pci@0/pci@c/pci@0 <pci.0,0> ONLINE
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@0
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@0 <pci.0,0> ONLINE <====== net0
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@0/network@0
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@0 <pci.0,1> ONLINE <====== net1
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@0/network@0,1
/pci@700/pci@1/pci@0/pci@c/pci@0 <pci.4,0> ONLINE
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4 <pci.0,0> MAINTENANCE <= we are replacing the EMS1 because it faulted
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0 <============ Internal SAS Disks
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@1
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@2
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@4
/pci@700/pci@1/pci@0/pci@c/pci@0/pci@4/scsi@0/iport@v0
Cause
Drives connected via EMS are most frequently used as boot devices. This is the reason why the MPT driver reports these resources as busy.
However, EMS SAS hard drives are dual ported and hotplug should be possible.
Solution
Enhancements to successfully hotplug an EMS (holding boot devices) are provided in Solaris 11.3 SRU 8.7 or higher
Criteria for successful hotplug of an EMS with dual ported SAS disks containing boot devices are as follows:
1. EMS network ports must be "unplumbed & unconfigured" prior to hotplug
2. Solaris needs to be 11.3 SRU 8.7 or higher
3. The EMS boot device must not be an SSD (only SAS disks are dual ported)
4. The OS Domain must be assigned the other EMS pair (ldoms) for successful dual port of disks
EMS1/EMS3 disks are dual ported to each other
EMS2/EMS4 disks are dual ported to each other
References
<BUG:23150295> - UNABLE TO HOTPLUG FAILED EMS
Attachments
This solution has no attachment
