nnmtracker
Technical User
Hi,
Anyone familar with a way to correlate multiple node down based on a substring on the hostname (say the first 4 characters of a hostname). Need to reduce the number of node down traps when an entire site does down.
Solaris NNM 6.2 ECS 3.1
Typically I would just use Secondary Failure and connector Down, but in this environment there are several extra challenges:
- NAT (The address space is always NAT going one way and sometimes also NAT in the other direction as well depending on address conflicts with public address space)
- Ip address space that falls outside of network boundaries
[IPSEC vpn established at some sites and use some of the same network space used in other locations)
These make it difficult for NNM to figure out whats a secondary failure (findroute can't seem to find its way).
Looking for ideas to reduce the number of Node Down traps received when a site goes down.
Thanks
Anyone familar with a way to correlate multiple node down based on a substring on the hostname (say the first 4 characters of a hostname). Need to reduce the number of node down traps when an entire site does down.
Solaris NNM 6.2 ECS 3.1
Typically I would just use Secondary Failure and connector Down, but in this environment there are several extra challenges:
- NAT (The address space is always NAT going one way and sometimes also NAT in the other direction as well depending on address conflicts with public address space)
- Ip address space that falls outside of network boundaries
[IPSEC vpn established at some sites and use some of the same network space used in other locations)
These make it difficult for NNM to figure out whats a secondary failure (findroute can't seem to find its way).
Looking for ideas to reduce the number of Node Down traps received when a site goes down.
Thanks