on 01-13-2015 12:57 AM
Dear All,
Are there any ways to use multiple IPs/Ports in IQ16?
I can use multiple IPs/Ports in Previous Version(IQ12.x/IQ15.x).
-x tcpip(host=xxx;port=xxx;host=xxx;port=xxx)
But It's not able to startup with above configuration in IQ16.
I already have tested as follows.
-x tcpip(MyIP=IP Address1:Port1,IP Address2:Port2)
But I failed to startup IQ.
Could please let me know how to use multiple IPs/Ports in IQ16?
Thanks
Gi-Sung Jang
Hi,
I have tried to test with below Scenario.
[Test Scenario]
1. -x tcpip{host=IP_Address_1;port=Port_Number_1;host=IP_Address_2;port=Port_Number_2}
-x tcpip(host=IP_Address_1;port=Port_Number_1;host=IP_Address_2;port=Port_Number_2)
2. -x tcpip{MyIP=IP_Address_1, IP_Address_2 ;Port=Port_Number_1,Port_Number_2}
-x tcpip(MyIP=IP_Address_1, IP_Address_2 ;Port=Port_Number_1,Port_Number_2)
3. -x tcpip{MyIP=IP_Address_1:Port_Number_1,IP_Address_1:Port_Number_2}
-x tcpip(MyIP=IP_Address_1:Port_Number_1,IP_Address_1:Port_Number_2)
Here are our results of test with below Scenario.
1) 1,3 Fail
2) 2 Success(IQ is able to startup and be connected)
HTH
Thanks
Gi-Sung Jang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For instance...
Imagine that you have outside users that must drill in through a firewall. But you also have internal users. You may decide that the port open to the firewall is not the same port that is used internally for all other IQ instances.
Another example... Imagine that you have two groups of users: finance and analytics. Today, the system is small enough that you need just one IQ server for them. You want to future proof the solution by giving each user community their own IP address and port to connect to. When you implement a second machine you would then move the IP and port to the other machine. No need to go back in and change the connection info for either user community.
It is not that common to have different ports for IQ. But it is not completely foreign.
Mark
Hi,
the parameter host was tolerated in 12/15. In fact it has no effect on the server. IQ was listening on all available interfaces (a netstat will show the 0.0.0.0:port line). Looks like 16 (partially) fixed the host parameter (host parameter it may be used on client side only to specify where the server is located):
I. 01/20 14:03:39. Trying to start TCPIP link ...
I. 01/20 14:03:39. Error parsing passed options - TCP/IP
I. 01/20 14:03:39. Unknown option "host"
[partially - the parameters is still ignored when it has a single value/IP, IQ will listen on all available interfaces/IPs]
The parameter MyIP is used to restrict the listener to the IP(s) listed here. MyIP doesn't allow you to specify the port (the reason why the 3rd test fails). You may use it like in test 2, or list the IP addresses one after another, comma separated:
MyIP=1.1.1.1,2.2.2.2
The same rules goes for the parameter PORT (ServerPort)
The outcome of your configuration is an IQ listening on both IP* addresses, on both ports on each IP:
TCP 1.1.1.1:2638 0.0.0.0:0 LISTENING
TCP 1.1.1.1:9638 0.0.0.0:0 LISTENING
TCP 2.2.2.2:2638 0.0.0.0:0 LISTENING
TCP 2.2.2.2:9638 0.0.0.0:0 LISTENING
(* IP addresses were edited, the ports used in my test were 2638 and 9638)
However, I cannot see how you can combine them, so the server will listen on IP1 on Port1 only and IP2, Port2 only !?!?!?
Dan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
this is normal and expected. What I'm looking for is to have something similar to ASE, where you can define on which port the server is listening for a given IP. ASE interfaces (section master) can define the listeners as IP + Port combination. IQ (or at least I don't know how) doesn't allow for such combinations: IQ will listen on all listen ports on all listed IP addresses.
If you try to connect to 1.1.1.1:9638 or 2.2.2.2:2638 will also work.
Dan
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.