cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2429
Views
5
Helpful
5
Replies

ip address pool exhausted UCS Director DMA Setup PXE

arnold-romeijn
Level 1
Level 1

UCS Director 5.2.0.2

When running a workflow with the task: Setup PXE boot we get the message:

Failed to setup PXE Boot With BMA Selection.IP Address pool exhausted, All addresses in use

 

But I cannot find any pool that is exhausted.

All previous flows have been rolled back.

1 Accepted Solution

Accepted Solutions

zerox45h
Level 1
Level 1

I ran into the same issue last Friday.  Everything seemed to be okay, but I kept getting the error you referenced. 

What I found was that I had an existing request for the same MAC address in the "PXE Boot Requests" tab under Physical/{location}.  I clicked "Clean PXE Request" and re-ran the orchestration and it went through and completed. 

Funny error.  Should state "duplicate MAC in active PXE requests"   or something.  

May not be the same issue, but worth the look.

 

View solution in original post

5 Replies 5

zerox45h
Level 1
Level 1

I ran into the same issue last Friday.  Everything seemed to be okay, but I kept getting the error you referenced. 

What I found was that I had an existing request for the same MAC address in the "PXE Boot Requests" tab under Physical/{location}.  I clicked "Clean PXE Request" and re-ran the orchestration and it went through and completed. 

Funny error.  Should state "duplicate MAC in active PXE requests"   or something.  

May not be the same issue, but worth the look.

 

Further investigation notes:  After extensive testing, it looks like you cannot execute a PXE orchestration if the server IP or MAC address are a duplicate of any other PXE request (in at least an "Environment Setup" status).

I brought this issue up to Engineering and they advised that this is something that is actively being worked on in this bug (CSCut04205)

Thank you - this was a great find and I have put together an internal tech note for our TAC team on this.

I had the same issue in one of the customer's environment and cleaning the PXE requests which were not active and were not in "Archived" status resolved it just fine.  Thanks for your post

This is fixed in the 5.3.1.0 patch as per the bug report CSCut04205.

arnold-romeijn
Level 1
Level 1

Wow, you were absolutly correct. Cleaned all (only a few) PXE requests and its working again.

Something went wrong with the rollback probably. I clicked everywhere in search of the pool that was exhausted even in the UCSM account but not on the POD.

 

Thank you!

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card