I'm faced with standing up an open source NMS and am deep into Zenoss Core. I'm evaluating distributed collectors that will be deployed behind a customer NAT/Firewall. Cool, this works. What if the customer IP space overlaps with an existing customer IP space? From a management perspective Zenoss distinguishes devices by IP. So it will refuse to add duplicate addresses. To get multi-realm IP functionality, It would require purchasing a subscription to enterprise license.
So my pickle, do I spend weeks or months hacking the Zenoss sub structure to duplicate that? Do I somehow remap the IPs through site to site VPN at the router? Or do I look for a different open source solution?
Does anyone know of an open source NMS solution that addresses overlapping IP space and can do distributed collectors? I have posted a question on Zabbix forums asking if the distributed monitoring they have will do this. But I hope that someone else has tackled this and succeeded.
It's the old thread "Disk Space Monitoring Script", modified for UNIX
This is the new code:
df -k | awk ' { if ( int($4) > 90)
{subject = $1 " More than 90% disk usage. Used: " $4
email = "email@test.com"
print subject
cmd = "mailx -s \"" subject "\" " email
cmd | getline... (4 Replies)
hi guys
my boss asked me for a tool to monitor and alert my Linux boxes... and some Win boxes... but not only monitor for high CPU Usage, hign memory usage and so on....he also wants a tool for historical data I mean something like
I want to know the CPU Usage and memory usage for the last... (1 Reply)
Hi Friends
I'm new to this UNIX - I'm working on the porting project from Solaris To Linux i just want to map some commands from solaris to Linux so can any one please tell me how to get the source code of the commands like "ls", "cu", "du"
Regards
sabee (1 Reply)
NAT action in tc(8) Linux NAT action in tc(8)NAME
nat - stateless native address translation action
SYNOPSIS
tc ... action nat DIRECTION OLD NEW
DIRECTION := { ingress | egress }
OLD := IPV4_ADDR_SPEC
NEW := IPV4_ADDR_SPEC
IPV4_ADDR_SPEC := { default | any | all | in_addr[/{prefix|netmask}]
DESCRIPTION
The nat action allows to perform NAT without the overhead of conntrack, which is desirable if the number of flows or addresses to perform
NAT on is large. This action is best used in combination with the u32 filter to allow for efficient lookups of a large number of stateless
NAT rules in constant time.
OPTIONS
ingress
Translate destination addresses, i.e. perform DNAT.
egress Translate source addresses, i.e. perform SNAT.
OLD Specifies addresses which should be translated.
NEW Specifies addresses which OLD should be translated into.
NOTES
The accepted address format in OLD and NEW is quite flexible. It may either consist of one of the keywords default, any or all, represent-
ing the all-zero IP address or a combination of IP address and netmask or prefix length separated by a slash (/) sign. In any case, the
mask (or prefix length) value of OLD is used for NEW as well so that a one-to-one mapping of addresses is assured.
Address translation is done using a combination of binary operations. First, the original (source or destination) address is matched
against the value of OLD. If the original address fits, the new address is created by taking the leading bits from NEW (defined by the
netmask of OLD) and taking the remaining bits from the original address.
There is rudimental support for upper layer protocols, namely TCP, UDP and ICMP. While for the first two only checksum recalculation is
performed, the action also takes care of embedded IP headers in ICMP packets by translating the respective address therein, too.
SEE ALSO tc(8)iproute2 12 Jan 2015 NAT action in tc(8)
