10-09-2012 05:10 PM - edited 03-01-2019 10:40 AM
We are running a UCS cluster as above using a pair of 6120XP's - UCSM is running 2.0(3b).
Recently we ran some failover testing to confirm our solution was redundant. When doing this, upon each cluster failover a minor alert was generated for "iqn pool default is empty". We can clear this fauly by going to the fault and using the "Affected object" in the properties section and then using the delete action.
The main problems we have are;
1) We can't find any reference to an IQN pool using the standard navigation of UCSM
2) Each time a failover event is conducted the alert is generated and the pool requires being deleted manually again
Is there a way to ensure this default pool is permanantly removed? Is this addressed in a future UCSM release?
10-09-2012 11:58 PM
Hello Jess,
Whenever any default pool ( mac,wwnn , IQN etc ) are empty, system returns a warning message.
If you are not using iSCSI or not using the default pool, you can delete the pool or add dummy values to get rid of this warning message.
UCSM GUI - > SAN - > Pools - > IQN Pools
previous post
https://supportforums.cisco.com/thread/2109684?tstart=0
HTH
Padma
10-10-2012 04:56 PM
Thanks Padma. You've sorted me for question one and we can now find the pool. As you mention, we have been deleting the pool to clear the error. We do also have have bogus IPs in our iscsi-initiator-pool.
My second question still stands, is there any way to stop this default empty pool being created during a failover event? Or do we just have to fill the pool with a bogus value and store that?
10-12-2012 08:16 AM
Hello Jess,
I did a test with UCSM 2.0.3c and yes, IQN default pool returns after FI fail over event.
Not sure if this design behavior or a bug where deleted default pool should not be created after a fail over event.
At this stage, adding dummy values to the default pool would stop the warning fault message.
Padma
10-15-2012 07:00 PM
I'm glad you could replicate this Padma. Means we aren't doing something odd.
Do you think I should raise this behaviour as a bug?
10-15-2012 11:09 PM
Hello Jess,
When I deleted default MAC pool, it was not re-created after FI fail over event. So I believe re-creating default IQN pool after FI fail over is a new defect.
I have submitted following bug for development team's analysis on the design behavior.
*NOTE* It will take atleast a day to get published and visible on cisco.com web site.
Padma
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide