locked
Reserved IP address and Static Internal IP address. RRS feed

  • Question

  • Hello,

    I would like to ask if there is any possibility of making the both, public and Private IPs, static ? 

    I have assigned Reserved IP to a VM and the public IP issue is resolved. 

    I can assign the VM to VLAN Subnets so the Internal IP issue will be resolved.

    But when i tried to achieve both in a single VM, i failed. Are they (Reserved IPs and Subnets) compatible with each other ?

    I have tried with CMDlet powershell . I did not tried with the configuration files, i just passed my variables in arguments.

    So, to sum up, my question is, can put the both public and private IPs static ?

    Thanks and Regards,

    Rahul.


    Winspark Network - Journalism to the core

    Saturday, September 6, 2014 4:52 AM

Answers

  • Hi,

    I think you are right.

    We could not use both in the same cloud service.

    The Reserved IP address is sticky, meaning once it’s associated with the cloud service, it won’t change unless you decide to disassociate it.

    Please note the Reserved IP address that is not associated with a deployment (Both VM and Cloud Service) incurs billing costs and hence it is recommended.

    http://msdn.microsoft.com/en-us/library/azure/dn690120.aspx

    For the cloud service, we may use one of them.

    Regards.



    Vivian Wang

    • Marked as answer by Vivian_Wang Sunday, September 14, 2014 9:02 AM
    Monday, September 8, 2014 4:43 AM

All replies

  • Hi Rahul,

    Yes. You can have both,static.

    But, please confirm whether you are trying to reserve IP (VIP) for the cloud service OR for a particular Virtual machine in your cloud service.

    If you want to have a static IP for your cloud service where you have hosted the VMs, then you may use the Reserved IP concept. Please refer - http://msdn.microsoft.com/en-us/library/azure/dn690120.aspx

    And, if you are trying to access a particular Virtual machine in your cloud service, then you setup a endpoint to that particular VM, and you may access that VM using the Public port number(with the reserved IP of that cloud service) that you provided while configuring the Endpoint.

    Also, you have a static Internal IP address for a Virtual Machine, you may refer following link: http://msdn.microsoft.com/en-us/library/azure/dn630228.aspx

    Regards,

    Manu Rekhar

    • Proposed as answer by cnk_gr Saturday, September 6, 2014 7:15 AM
    Saturday, September 6, 2014 7:05 AM
  • Hello,

    I am assigning Both static IPs to my VM. I have just 1 instance on my cloud service.

    anyhow, i tried giving -ReservedIPName and AzureStaticVNetIP both in the New-AzureVM command, but its not accepting.

    I guess they are not allowing both at a same time. Please guide.


    Winspark Network - Journalism to the core

    Saturday, September 6, 2014 7:31 AM
  • Hi,

    I think you are right.

    We could not use both in the same cloud service.

    The Reserved IP address is sticky, meaning once it’s associated with the cloud service, it won’t change unless you decide to disassociate it.

    Please note the Reserved IP address that is not associated with a deployment (Both VM and Cloud Service) incurs billing costs and hence it is recommended.

    http://msdn.microsoft.com/en-us/library/azure/dn690120.aspx

    For the cloud service, we may use one of them.

    Regards.



    Vivian Wang

    • Marked as answer by Vivian_Wang Sunday, September 14, 2014 9:02 AM
    Monday, September 8, 2014 4:43 AM
  • Hi,

    Any update about the issue?

    Regards.


    Vivian Wang

    Wednesday, September 10, 2014 5:24 AM