![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1928383.1 : SuperCluster - IB Connectivity Issues in Expansion Storage Configuration After IBSwitch Reboot
In this Document
Created from <SR 3-9606466731> Applies to:Oracle SuperCluster T5-8 Full Rack - Version All Versions to All Versions [Release All Releases]Oracle SuperCluster M6-32 Hardware - Version All Versions to All Versions [Release All Releases] SPARC SuperCluster T4-4 - Version All Versions to All Versions [Release All Releases] Oracle SuperCluster T5-8 Half Rack - Version All Versions to All Versions [Release All Releases] Oracle SuperCluster T5-8 Hardware - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. SymptomsAfter rebooting the IB switch, some IB Connections are reporting down. We found the spine switch was not the master. ChangesCustomer had rebooted a IB Switch and we lost some IB connectivity. CauseThe spine switch was not the master, but the switch in Exadata Storage Expansion Rack (IB4 in this case) was the master.
[root@pdcsc1sw-ib4 ~]# getmaster -l
Local SM enabled and running, state MASTER [root@pdcsc1sw-ib1 ~]# getmaster -l Local SM enabled and running, state STAND BY
Supercluster expansion storage config was incomplete in IBSwitch perspective. SolutionThe following steps were performed to fix this configuration. 1) We disabled SM in all smnodes. 4) Also added the missing smnodes in IB1,IB2,IB3 # smpartition list active
References<NOTE:1912199.1> - Configuring Infiniband Switches when Interconnecting an Oracle SuperCluster and a Exadata Expansion RackAttachments This solution has no attachment |
||||||||||||||||||||
|