I had a similar requirement. There is not a way to set up polling
intervals to skip this time period without going through difficult hoops
if the nodes are managed directly by NetView. However, it is easy to
set up Trap filters an MLM to block status traps.
Here is what I did:
1. Assign the nodes to an MLM using the collection facility (see the -G
and -C flags of netmon in the man pages).
2. Create a Filter in the MLM.
a. Set the default action to "blockTraps"
b. set the activation time 11PM
c. set the deacivation time to 3AM
d. set the Activation days to 0,1,2,3,4,5,6
e. set the Deactivation days to 1,2,3,4,5,6,0
f. set the agent address to the ip address of the MLM hostname
g. set the Variable Expression so that $SNMP_TRAP_VAR_VALUE3
matches all of the interfaces of the nodes you want to exclude
during that time. If they have multiple interfaces, include them
all.
One way to find out is to run "netmon -a 51", and then look in
/usr/OV/log/netmon.trace. Netmon will have dumped the ip address
of
all of the interfaces for all of the nodes assigned to the MLM.
Another way is to do ovtopodump <selection name> for all the
nodes.
The output will contain the IP addresses of all the interfaces on
each node.
The Variable Expression will look something like this one:
( $SM6K_TRAP_VAR_VALUE3 == "10.82.208.85" ) || (
$SM6K_TRAP_VAR_VALUE3 == "10.82.208.86" ) || ($SM6K_TRAP_VAR_VALUE3 ==
"10.82.208.87" ) || ($SM6K_TRAP_VAR_VALUE3 == "10.82.208.88" )
3. Set up a job to have NetView nmdemandpoll each node in the MLM
collection at 3 AM.
The last step is important. Since Status traps from the MLM will be
blocked, you will not know if a node goes down during your period and
never comes up. The MLM will send a trap only when the status changes,
and the trap will be blocked during the period 11 PM till 3 AM. If it
stays down, the status doesn't change, and the MLM doesn't send another
interface down trap.
I have created some shell scripts and C programs to automate the
creation of these filters given the collection name, and the
activation/deactivation days/time.
"Giuliotti, J. P." wrote:
>
> Hello Group,
>
> I have a couple of critical nodes that are shut down nightly as part of a
> backup procedure. How do I insure that Netview will not try to discover
> these nodes in that time frame so we are not paged between 11pm and 3AM
> every night? Is there a standard way of handling this situation?
> Thanks,
> J.P. Giuliotti - Massachusetts Financial Services
> (617) 954-5684
> JPG@MFS.COM
--
Ray Schafer | schafer@tkg.com
The Kernel Group | Network Computing Consulting
|