Hi Yiping,

Which hypervisor do you use? Keep in mind if you use VMware then every VR will 
also get an IP address in this same range – hence you need to have enough IP 
addresses to cover all your networks, VPCs and SSVM+CPVM.

If you want to check in your DB the management IP range is defined in:

- host_pod_ref.description: think this is cosmetic
- cloud.op_dc_ip_address_alloc: row per IP address – and you have to reference 
“nic” and “reservation_id” back to the “nics” table and from there reference 
the “vm_instance” table. 
Something like this should work – but double check it please – this was just 
quickly thrown together:

SELECT 
    cloud.op_dc_ip_address_alloc.id,
    cloud.op_dc_ip_address_alloc.ip_address,
    cloud.op_dc_ip_address_alloc.pod_id,
    cloud.op_dc_ip_address_alloc.nic_id,
    cloud.nics.network_id,
    cloud.vm_instance.name
FROM
    cloud.op_dc_ip_address_alloc
LEFT JOIN
    cloud.nics ON (cloud.op_dc_ip_address_alloc.nic_id = cloud.nics.id
        AND cloud.op_dc_ip_address_alloc.reservation_id = 
cloud.nics.reservation_id)
LEFT JOIN
        cloud.vm_instance on (cloud.nics.instance_id = cloud.vm_instance.id)
WHERE
    cloud.op_dc_ip_address_alloc.reservation_id IS NOT NULL;

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 25/10/2017, 01:28, "Yiping Zhang" <yzh...@marketo.com> wrote:

    Hi, all:
    
    In ACS web GUI, on the Pod Details page, the fields “Start IP” and “End IP” 
are editable.  This IP range is reserved for systemVM’s (SSVM/CPVM).  When I 
built my ACS environments three years ago, I gave this a large range without 
fully understanding what it is for.  Now I am short of IPs on the management 
network, I would like to reduce this reserved range so that I can use some 
extra IP for other things, like more hypervisor hosts!
    
    When I try to trim some IP off either end, I get an error message: “The 
specified pod has allocated private IP addresses. So its IP address range can 
be extended only”, even though I know for facts that my system VM’s are not 
using any of the IP’s that I am trying to free up.
    
    So, I did the obvious thing:  disabled the zone, and deleted all the SSVM 
and CPVM’s. I even restarted the management service.  However, when I try again 
to edit “Start IP” and/or “End IP” fields on the Pod details page, I still get 
the same error message above, even though now I have zero system VM! This does 
not seem to be correct to me.
    
    I guess, at this point, my only solution is to do direct DB modifications.  
Can someone please tell me which table contains this information?  If any of 
you have successfully modified pod start/end IP without going direct DB hacks, 
please share your approaches.
    
    Thanks
    
    Yiping
    


dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Reply via email to