Conference azur::mcc

5610.0. "How EXPORTER works?" by WARABI::CHIUANDREW () Wed Sep 22 1993 01:41

    Hi,
    
    Could someone explain how EXPORTER works (e.g. if we define the delay to
    60 seconds and there are 300 export entries active at the same time, how
    does EXPORTER perform multiple export request at the same time, does it
    behave similar to IP poller, which sends 50 ICMP msg in an
    interval...)? 
    
    Customer would like to use DECmcc to produce WAN network utilization
    reports and we have already started the collection on 
    100 entities running on a DECMCC BMS V1.3 station at 30 minutes export
    period. And each of these entities will have 4-8 links/lines/interfaces 
    and EXPORTER will write the data to a single RDB database, then they 
    use 4GL tools to produce the graphical reports.
    
    These entities are TransLAN, IP nodes and Terminal server (MUXserver),
    and during our collecting process, the EXPORTER batch queue died
    without any warning, and after we have re-submit the EXPORTER batch
    job, some of the 'active export' entries DO NOT EXPORT any more (by checking
    the last succesful polled/time), could someone explain why this
    happens?
    
    Is there any tools that can be used to detect the activity of those 
    'active export' entries (since it's status remains ACTIVE, so I cannot 
    use alarm to detect the change of its status)?
    
    If 60 seconds delay is used in starting the EXPORTER job, then does it mean
    EXPORTER can only export 30 entries within 30 minutes export period?
    
    If the exported entities have multiple link/interface/line
    sub-entities, how many 'total' export entries can be handled within
    each export period (e.g. 30 minutes)?
    
    Does multiple EXPORTER batch jobs handle more export entries?
    
    Thanks in advance for help!
    Andrew - NIS Sydney              

	1. Let's say that you have 60 active exporting requests and you
	   restart  the Exporter background process with 60 seconds delay
	   at 1 p.m. The last (30-th) request will be actually "activated"
	   at 2 p.m. The export period for each exporting request is defined 
	   by the original export command.

	2. Exporter works on per entity basis, it does not expand structure
	   for an entity being exported. For example, if you want to export
	   data for  a node4 and its line you have to set up two exporting	
	   requests: one -  for node4 and second - for node4 line. 


		Sam