Static IP address(internal IP address)

[hisao.aso]

I want to use static ip addredd for internal ip adderss.
please teach me how to set up.

[PeterNic]

hisao.aso,

AppLogic dynamically assigns IP addresses for all terminals. They don't change on restart, but can change if you add or remove components (appliances) in an application; they also change if you make a copy of the app -- the copy will use a different set of IPs.

If you want to use user-defined IP addresses that will never be changed automatically, we recommend using external interfaces. You can use RFC1918 addresses (non-routable). Let me know if you need to know how to assign an RFC1918 range.

(We are planning to add support for statically assigned IP addresses for terminals in the future, but that is not currently supported.)

If you don't need them to be truly static but need to be able to obtain the assigned value, AppLogic stores that in a config file on each appliance -- let me know if you need more info on that.


Best regards,
-- Peter

[hisao.aso]

Thank you for reply.

I don't want to change Local ipaddress,
so I want to know how not to change Local ipadderss.
(I want to know how to assign an RFC1918 range.)

[PeterNic]

hisao.aso,

How to add an RFC1918 range to your external network ranges depends on how you obtain AppLogic:

- if you are getting it as a service from one of our service provider partners (http://www.3tera.com/Partners), simply ask them to add a RFC1918 range to your virtual private datacenter (VPDC)

- if you have a license to install on your own servers, then check out the installation options -- there is an 'aldo set' command which allows you to add IP ranges (version 2.4 and later)

Please keep in mind this applies only to external interfaces of appliances. You can PM me for details if you don't want to post them publicly.


Best regards,
-- Peter

[PeterNic]

Dear hisao.aso,

Just a clarification:

1. You cannot change the IP addresses of terminals. AppLogic assigns those automatically, making sure that there are no duplicates and that routing and filtering is set correctly. You can ALWAYS get the IP addresses and use the terminal names as host names to direct traffic (the right way to access external services).

2. You can set the IP addresses of external interfaces. The allowed values are what your service provider has assigned to you and listed on the dashboard (and, in recent AppLogic versions also shown as output of the 'grid info -v' command). By default, there is only one range, with public IP addresses. Most providers will also assign an internal, RFC1918 range if you request it.

For more information on the appliance model, see http://doc.3tera.com/AppLogic27/AdvApplicationModel.html and http://doc.3tera.com/AppLogic27/RefEditorClassEditorSimple.html#Interfaces

If you can describe the use case in more detail, I will be able to give you examples. You can also contact your service provider for assistance.

Happy Holidays!

Best regards,
-- Peter

[calvin1982]

Hi Peter,
I want to know who to set static ip of external interface on windows appliance not vds, we want to install active directory on windows appliance, the ad needs static ip binding ,but we do not want to use windows vds, how to bind static ip of ext. in standard windows appliance? thanks,

[PeterNic]

Calvin,

Generally, there are four steps:

add network configuration properties on the appliance boundary (IP address, netmask; gateway/dns1/dns2 if needed)
inside the appliance, retrieve the property values - see the APK docs, there are several ways to get those
inside the appliance, retrieve the network interfaces list and identify the name of the Windows network connection for the external interface
use the standard Windows means to configure the IP settings on the network connection


You can borrow the external interface configuration script from the Windows VDS, as the setup should be identical; that script will do steps 2-4 (and step 1 is something you need to do on your appliance after branching it).

That's the short of it; let me know if you need help with any of the steps above.

Best regards,
- Peter

[calvin1982]

Hi peter
I know what you said. The configuration retrieved from web form was defined in appliance.sh file. The start script source(command) that script to define configuration. But I have a question want to ask you(STEP 3), which number of ethnet card is the external ? how to determine that ? I found our engineer use the lowest number of ethnet, the lowest is the IN terminal mostly, and the highest number is the ssh control network, is that right?

Regards,
Calvin

[Jsmart]

Hello,

when you enable the external interface it will always be the lowest number interface. the "default interface" or control network will be the highest.

Regards,
Jessie

[calvin1982]

Hi jessie,
Thank for your help.

Calvin