Outgoing IP

qwerty · Post by **qwerty** » Mon Sep 16, 2013 3:34 am

Hello,

I want to assign dedicated out IP (per interface) to the agent for server independence.
In this case I can move agent to backup server if anything happens with primary server.

Can I do this ?

Thank you!

KS-Soft · Post by **KS-Soft** » Mon Sep 16, 2013 4:33 am

Not sure I understand the question...
What kind of agent do you use? Passive RMA? Active RMA? RMA for Unix?
Backup server will have the same IP or different?

Regards
Alex

qwerty · Post by **qwerty** » Mon Sep 16, 2013 4:45 am

Hello KS-Soft, thank you for your reply!

As example:
1. We have 2 Servers: Server1(192.168.1.10) and Server2(192.168.1.20)
2. We want that RMA(passive) should have an independent IP - 192.168.1.30
3. If Server1 goes down we can move RMA IP(192.168.1.30) to the Server2 and all should work without any firewall changes on the monitored servers.
4. Also we have two interfaces on all our servers:
Front End: 192.168.1.X
Back End: 192.168.2.X
Will be fine to have an options to setup outgoing IP for both interfaces.

Thank you!

KS-Soft · Post by **KS-Soft** » Mon Sep 16, 2013 5:12 am

1. We have 2 Servers: Server1(192.168.1.10) and Server2(192.168.1.20)
2. We want that RMA(passive) should have an independent IP - 192.168.1.30

Imposible

Regards
Alex

qwerty · Post by **qwerty** » Mon Sep 16, 2013 5:15 am

Imposible

I think this can be a good feature request for transparent agent moving to another server.

Thank you!

KS-Soft · Post by **KS-Soft** » Mon Sep 16, 2013 5:35 am

This has nothing to do with agent. This is how IP networks work - you assign IP address to network interfaces (network card).
If you send packet to IP to 192.168.1.10, it should be sent to 192.168.1.10.
Yes, you can setup some router or firewall to translate all packets (or specific port) from 192.168.1.30 to 192.168.1.10 but if you move agent, you should change firewall/router settings anyway.

Regards
Alex

qwerty · Post by **qwerty** » Mon Sep 16, 2013 6:11 am

This has nothing to do with agent

MDaemon Mail Server have same features. When we can bind app with specified IP.

Yes, you can setup some router or firewall to translate all packets (or specific port) from 192.168.1.30 to 192.168.1.10 but if you move agent, you should change firewall/router settings anyway.

192.168.1.30 and 192.168.1.10 is in same subnet and I told about firewall on the server as example or about ACL on SNMP agent.

As example:
We have 50 Windows servers and one agent on Server01. On all our 50 servers SNMP ACL we have specified IP restriction(Server01).
If Server01 goes down we should move it's first IP to another server or add another IP(Server02) to the ACL, but this can be problematic.

KS-Soft · Post by **KS-Soft** » Mon Sep 16, 2013 8:08 am

MDaemon Mail Server have same features. When we can bind app with specified IP.

It creates some virtual network inteface?

Regards
Alex

qwerty · Post by **qwerty** » Tue Sep 17, 2013 10:03 am

No - simple checkbox.

Kris · Post by **Kris** » Thu Sep 19, 2013 7:42 am

Hi guys,

As far as I know it's like this:
The IP address field in this dialog has to be either 127.0.0.1 OR an IP address assigned to a network interface on the computer running MDaemon.
Any other address just won't do anything.

But That's just my 2 cents...

qwerty · Post by **qwerty** » Fri Sep 20, 2013 9:10 am

OR an IP address assigned to a network interface on the computer running MDaemon.

Kris, you are right.

It this case if we want to move MDaemon to another server we will move it with this IP - non default server IP.