I know the best idea here is likely to reserve an IP block per subnet that UCSD doesn't control, but is it possible to reserve an IP somehow such that a static pool won't allocate it, other than excluding it from the list?
E.g. if I create two VMs with UCSD, but need to reserve a VIP in the same pool, can I mark the IP as used even though UCSD doesn't create it?
Or, is it possible to modify an existing, in-use static pool without affecting existing reservations? So I can modify the IP range values to exclude an IP that is in use?
Solved! Go to Solution.
OK I see this task (Get IP Address from Pool) and it tests out good, but this would be for pulling an additional random address out of the pool correct?
So I could provide an additional IP if someone asks for it, but if someone assigns an IP and then lets me know what it is, is there a built in way to mark it as reserved?
I used this recently in a workflow (https://communities.cisco.com/docs/DOC-60468) to test for port 443. When it is up I have the workflow move on to the next part. First I test if ESXi is up and the I test if my vCenter installed.