Note: This document is updated based on Jelastic 5.3 versionYou can monitor and manage a set of available IP addresses on Platform using the Cluster > IP Pool section of JCA. Herewith, the three pools of addresses are separated and are managed through the separate subsections:
- Internal IPv4
- Public IPv4
Within these sections you can monitor a set of available free and busy IP addresses, displayed with the appropriate environment domains (if any) and regions, where these IPs are available.
In the shown table you can find the following information:
- IP address - lists all of the IPs in a pool
- Status - indicates whether the IP is in use (the red busy label) or is available for users (the green free label)
- Environment - displays name of the environment, which includes a container with the corresponding address bound. Clicking on a particular domain will redirect you to the Cluster > Environments section, where the detailed information on the chosen environment will be shown
Region - shows a physical location of the hardware a particular IP belongs to
Using the upper tool panel, you can filter this list in order to show only those IP addresses, that Starts / Ends with the stated IP (specified within the blank input field next to the filtering drop-down list) or have Any match with it. In addition, you can select a particular Status (i.e. all, busy and free) and/or a Region for the addresses to be separated out.
Once all of the required parameters are stated, just click on Search to apply filtering. Subsequently, you can select Clear to remove the conditions and show the whole list of IPs.
Tip: Also, you can click on a particular domain name (with an assigned address) for viewing information on the corresponding Environment within the same-named section to the right.
Here, you can find the following environment data, divided into columns:
- Name - name of the chosen environment with the expandable list of all instances it includes and deployed contexts
- ID - unique ID value for each instance
- IP address - all bound IP’s, both internal and external (if are any) ones
- Hardware node - name and IP address of the hardware node, where a particular instance is located
Node Mission - type of the used software stack