SNMP proxies and virtual server monitoring
Hi,
We're considering OpManager for managing corporate servers we have at various customer sites across Europe. These servers are all behind firewalls with dedicated (TCP) port openings to us for management purposes.
This is fairly complex, and I'm interested in how we can accommodate/customize OpManager to fit the bill. For alarms I imagine we have to use SNMP proxies and have OpManager receive traps from these proxies locally on the same network as the OpManager server resides (possible localhost).
1. Can these SNMP proxies somehow appear as different servers, e.g. in the server map? Do they all have to send traps from different ports? Could we use 127.0.0.2---n as source IP, and maybe 'trick' OpManager to
For WMI data we're looking into using NsClient and NsClientJ - NsClient is an NT Service server that translates WMI queries and replies in to a proprietary TCP protocol, i.e. allowing WMI to be exposed independant of NTLM and native windows authentication mechanisms. NsClientJ is a Java API that can talk to the NsClient server. We're going to use SSH and reverse tunnelling to access the corporate servers and thereby access NsClient directly or via JMX/MBean. The big question is - can I fool OpManager to thing that it's talking to a 'real' server on the LAN with this architecture?
Any input and thoughts around these issues would be much appreciated.
--
Thomas
We're considering OpManager for managing corporate servers we have at various customer sites across Europe. These servers are all behind firewalls with dedicated (TCP) port openings to us for management purposes.
This is fairly complex, and I'm interested in how we can accommodate/customize OpManager to fit the bill. For alarms I imagine we have to use SNMP proxies and have OpManager receive traps from these proxies locally on the same network as the OpManager server resides (possible localhost).
1. Can these SNMP proxies somehow appear as different servers, e.g. in the server map? Do they all have to send traps from different ports? Could we use 127.0.0.2---n as source IP, and maybe 'trick' OpManager to
For WMI data we're looking into using NsClient and NsClientJ - NsClient is an NT Service server that translates WMI queries and replies in to a proprietary TCP protocol, i.e. allowing WMI to be exposed independant of NTLM and native windows authentication mechanisms. NsClientJ is a Java API that can talk to the NsClient server. We're going to use SSH and reverse tunnelling to access the corporate servers and thereby access NsClient directly or via JMX/MBean. The big question is - can I fool OpManager to thing that it's talking to a 'real' server on the LAN with this architecture?
Any input and thoughts around these issues would be much appreciated.
--
Thomas