Upgraded cluster, cannot merge node pools

Question

We upgraded our (4x iq_32000x-ssd) with 3 more X400 nodes, with exactly the same configuration (disk, memory). After I added the new nodes I realized that they went to a new node pool,  which is not what we wanted. Now we have a pool with 4 nodes and another with 3 nodes, and each one is protected with 2:1 , doubling the cluster overhead (correct me if my overhead logic is wrong). I opened a case and they are telling me that merging these node pools is impossible since the nodes have different config IDs: nyst0087-1# isi_for_array isi_hw_status|grep -i config | sort nyst0087-1:  Config: 851-0105-02 nyst0087-2:  Config: 851-0105-02 nyst0087-3:  Config: 851-0105-02 nyst0087-4:  Config: 851-0105-02 nyst0087-5:  Config: 851-0074-01 nyst0087-6:  Config: 400-0029-01 nyst0087-7:  Config: 400-0029-01 nyst0087-8:  Config: 400-0029-01 Is this true ? (We do not have SmartPools licenese, and with this configuration we do not need it)

bhalilov1 · Accepted Answer

This was caused by bug in 7.1.0 that is supposedly fixed in incoming 7.1.0.2 Engineering deleted the second pool an re-added the nodes to the first pool using internal use disi command

chughh · Answer

please provide more information about version  which you have upgraded too so I can suggest some workaround..

bhalilov1 · Answer

By upgrade I meant we added 3 Nodes to the existing cluster, not OneFS upgrade. We're running 7.1.

peglarr · Answer

Hi Burhan,

There is only one X400 CTO node that is in the same equivalence class as the 32000X-SSD - and that node, specifically, is the X400-SSD 32TB/24GB RAM. It's equivalence class 5.

Here's a handy document. Since node equivalence changed from pre-7.x to 7.x, it's worth a read.

https://support.emc.com/docu44518_Isilon-Supportability-and-Compatibility-Guide.pdf?language=en_US

bhalilov1 · Answer

Thanks Rob We have the following type of nodes Isilon X400-4U-Dual-24GB-2x1GE-2x10GE SFP+-32TB-400GB SSD Isilon IQ 32000x-ssd According to the documents they are equivalent in class 5.

BernieC · Answer

Node equivalence checks are not functional in OneFS 7.1.0.0. Please open a case with support so we can resolve this issue manually.

This will be fixed in a future OneFS update (likely the maintenance release after 7.1.0.1). When you open up the case, please reference internal bug ID 120151.

Thanks,

Bernie

Isilon

Was this post helpful?