Conference azur::mcc

5903.0. "IP Poller Problem again" by VNABRW::HAINZL_R () Wed Mar 09 1994 06:33

    In addition to my performance problems stated in 5891 I am fighting 
    with the IP-Poller functionality :
    
    the setup is :
    VMS5.5-2H4 on a VAX4000 Model 90 / 80 Mb
    DNS, DECnet/OSI, TCP/IP Services for VMS
    
    just two domains 
    a lot of DECnis's, FDDI-concentrators
    4 IP-nodes should be polled in 2 domains
    the operator window should be unprivileged (nosysprv !!)
    and ip polling should be started (as all the other things are) 
    automatically when the operator logs in, since he should only see
    the status of the network, not be able to change anything, and no
    necessity to know anything about mcc for him.
    
    So I tried to startup the MCC-Poller in Batch with the standard 
    Prodedure in MCC_COMMON:MCC_ENABLE_IP-bla-bla-bla (you know what I
    mean) with SYSPRV enabled in the BATCH Procedure.
    
    - this actually starts the MCC-IP-POLL detached process
    
    --> but normally I see only one (or sometimes no) poll result
    (ip-notification).
    
    - I tried to restart the MCC_ENABLE_IP-bla-bla-bla Command procedure
      every minute
    
    --> but this is not very elegant and doesnt help my performance
    problems a lot (besides ... it works sometimes but not always ...).
    
    
    anyone any suggestions to this, any help much appriciated
    rgds Richard
    
      

	When you run the MCC_COMMON:MCC_ENABLE_IP-bla-bla-bla procedure
	in batch be sure to provide your top level domain name as a parameter.
	If you do not have a top level domain, then you will have to run
	the procedure multiple times, each time providing the domain name
	in which you want polling to occur. You can make sure that the
	poller actually got started by looking for the process MCC_IP_POLLER
	when you do a SHOW SYSTEM command.

	Rahul.

    .1
       Top Domain is specified when activating IP-Poller with 
       MCC_COMMON:MCC_ENABLE_IP-bla-bla-bla - Procedure and existence of
       MCC_IP_POLLER detached Proze� is verified. 
    
    could the Problem arise because of trying to send the
    IP-Poll-notifications to an unprivileged account ?
    
    rgds Richard
    

	Do you see more notifications when you run the same test under
	a privileged account? The IP Poller will generate events only
	when the status of a node changes. (It will also generate reachability
	down events for down nodes at startup).

	Rahul.