Re: [nv-l] Change TEC forwarding via command line?

[Leslie Clark <lclark@us.ibm.com>]

Any comments about which approaches preserve or flush the cache? In some cases (such as switching to a backup tec) we might want to preserve cached events bound for the tec that piled up since the primary tec went down. In other cases ( such as stopping forwarding because we figured out we lost our own connection to the network) we might not want cached events saved.  

I too am working with a failover scheme, but we don't yet have a tec to actually test with. I'm assuming that I can use nvtecia from an action spawned by actionsvr. This week I figured out that I cannot stop/start actionsvr from an action spawned by actionsvr (I wanted to swap ESE.automation), but I live in hope that I will be able to signal nvserverd using nvtecia from such an action. 


Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

James Shanks/Raleigh/IBM@IBMUS Sent by: owner-nv-l@lists.us.ibm.com 01/08/2004 01:03 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        Re: [nv-l] Change TEC forwarding via command line?

Well, nv6000_smit is a script and you can examine it to see what it's doing.   
But basically, the one with the -N flag is deleting the existing tecint.conf and the one with the -Y flag is creating is, and then nv6000_smit restarts nvserverd to have him pick up the changes.   So you are correct that your method maintains the status across reboots.  But that isn't what Craig asked for.  He wants to avoid a restart. 

nvtecia avoids having to recreate the file and restart the daemon, provided he's already active.  So is your "inactive" box hot or not?  If nvserverd is already active and not forwarding to TEC, you can get him to start (provided the tecint.conf file exists and is accurate) with nvtecia.  If your inactive box is cold, or there's a chance someone deleted the file, then I think your current way is better.  But nvtecia is quick (it just uses user signals, SIGUSR1 and SIGUSR2 to notify nvserverd) and has less overhead.  But nvtecia also is not permanent.  If your backup box is hot, and you have stopped TEC forwarding with nvtecia, and then you restart nvserverd while a good tecint.conf file is present, he will start sending upon initialization.  nvserverd has no memory of his prior state across startups. 


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

bill.kellam@worldspan.com Sent by: owner-nv-l@lists.us.ibm.com 01/08/2004 12:07 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com        cc:                Subject:        Re: [nv-l] Change TEC forwarding via command line?

James, I have a failover script that I execute to flip flop my pair of
Netview servers to make one active and the other inactive. The respective
commands I use are these:

/usr/OV/bin/nv6000_smit tecint_conf '-Y' -s'TecServer' -p'5529'
-r'tecfwd.rs'";
/usr/OV/bin/nv6000_smit tecint_conf '-N' -s'TecServer' -p'5529'
-r'tecfwd.rs'";

Any thoughts on whether the nvtecia command would be a better choice? This
maintains state across a reboot (I think!). I got this straight off the
window that displays command status when reconfiguring tec forwarding from
the serversetup interface.

Regards,
Bill Kellam
Enterprise Integration and Management




                                                                          
            James Shanks                                                  
            <jshanks@us.ibm.c                                             
            om>                                                        To 
            Sent by:                  nv-l@lists.us.ibm.com               
            owner-nv-l@lists.                                          cc 
            us.ibm.com                                                    
                                                                  Subject 
                                      Re: [nv-l] Change TEC forwarding    
            01/08/2004 10:04          via command line?                   
            AM                                                            
                                                                          
                                                                          
            Please respond to                                             
            nv-l@lists.us.ibm                                             
                  .com                                                    
                                                                          
                                                                          





nvserverd does not have to be bounced.
You can stop and start TEC forwarding dynamically, once it has been
initially set up, with the nvtecia  command.  It has two options.
       /usr/OV/bin/nvtecia  -stop
stop TEC forwarding.
       /usr/OV/bin/nvtecia -reload
cause nvserverd to reload the ruleset which is defined in the tecint.conf
file and begin forwarding again.
Note that this allows you to edit the file and change the rule name
whenever you  want to.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

                                                                         
  "Treptow, Craig"                                                       
  <Treptow.Craig@principal.com>            To:        "NetView List      
  Sent by:                         (E-mail)" <nv-l@lists.us.ibm.com>     
  owner-nv-l@lists.us.ibm.com              cc:                           
                                           Subject:        [nv-l] Change 
                                   TEC forwarding via command line?      
  01/08/2004 09:44 AM                                                    
  Please respond to nv-l                                                 
                                                                         





Hi.  We are running Netview 7.1.3 on AIX 5.1.  We have a need to
temporarily stop forwarding events to TEC and would like to change this via
the command line over dial-up.

Reading the tecint.conf man page, I see:

"  The /usr/OV/conf/tecint.conf file contains definitions for the
forwarding
of NetView events to TEC. The presence of this file will cause nvserverd
to
attempt TEC forwarding. If absent, no forwarding to TEC will occur."

So, it appears we could temporarily rename the file.  The man page doesn't
seem to say whether or not we will need to bounce nvserverd.  Does anybody
know if we'll need to?


Thanks,

Craig