Conference azur::mcc

>    Given the following:
>    
>    line syn-0    Recorded from 14-jul-1992 17:20 until 18-jul-1992 06:00
>    circ syn-0       "       "     "        17:35  "       "          "
>    
>    1. Can I export just a portion of the above time frame e.g 15-jul-1992
>    00:00 to 03:00, or do I have to export exactly the same interval as the
>    Historical recording?

	You can export any portion of previously recorded data.
	Export directive has "begin time", "end time", and "export
	period" arguments which allow you to specify desired time interval.

>    2. If the Historical recording was done every 15 mins, do I have to do
>   the exporting every 15mins?

	See above. An "export period" argument allow you to specify any
	interval you want. If the "export period" is less that "polling
	period" some of the data will be duplicated. In general, the
	Exporter sees historical data in the way they are returned by
	the Show directive:
		Show .... ,for ... every... until ... , in domain ...

>    3. I have recorded line and circuit attributes (identifiers, counters,
>    characteristics and status) for a router but no attributes for the
>    router node entity itself. I wish to produce graphical output using Mcc
>    Reports. Do I have sufficient information?  
 
	You should look at Performance Analyzer Use manual. In the section
	" Computing Statistics from Historical Data" you will find which 
        partitions for what entity should be recorded in order to calculate
        past time statistics.        

>    4. Am I correct in thinking that I can export all information (e.g line 
>    and circuit information for five routers) within one mcc_export.rdb 
>    database provided that these routers all lie within one domain? 


	You are free to export any number of entities to the same database.
	The Export operation is not domain based therefore these entities
	do not need to "lie within one domain".


	Sam Shmuylovich
    

    re .1
    
    Hello Sam,
    
    you mentioned 1. that we can export historical data from the past,
    which means that we will export data from the historical recorder.
    In our configuration every time we try to export historical data (past
    time data) we get into trouble. 
    
    We have DECmcc v1.2 SSB with VMS v5.5
    
    Everytime we try to EXPORT a single line's recorded data, from 1-jul
    to 21-jul. After about half hour DECmcc open's up all available links
    to the router, then starts producing alarm exceptions for all node4
    alarms in the database (about one per second) and never stops.
    
    The alarms keep comming even after the export command was killed.
    We had to actualy kill the alarms enable batch job to stop this.
    
    Data for the line in question, and other lines on the same router
    was recorded for the counter amd characteristics partitions.
    
    	Gil

	Hi Gil,

	As for as I know Past Time Export command does not create any
    new links to the target. Just to verify this I recorded the same
    partitions as you did (counters and characteristics for line) and
    set up Past Time Export. In the same time I monitored links to
    the target using NCP. It did not show any!

	As I understood from your note you have a number of active
    alarm rules. They definitely create links. What else is going on
    on your system?

	Sam 

	
 	
    

    Hi Sam
    
    Yes our DECmcc has about 300 polling alarms, but it was the EXPORT
    process that created all the links to the router. I verified this,
    from the beginning the export process starts creating links to the
    router (an in about half an hour) it takes over all links up to the
    max link limit preventing anything else from creating links.
    
    I experimented recording 2 days of data, and then exporting that.
    It worked (althought it took about an hour, why this long !!!) AND 
    it too created links to the router but not many (1 to 5 links at 
    anytime).
    
    DOES the exporter check up (with the router) the entity characteristics
    or something before it exports a record ??? Does this problem only show
    up when you have lots of recorded data to export? We do have 45 days of
    recorded counters and characteristics for about 30 lines and 30 circuits 
    in 11 routers. (Alarm Polls and Recording Line/Circ Counters are done 
    every 15 minutes,  recording line charateristics is done every hour)
    
    	Gil
    
    Another thing,  Regarding the recording, even such a simple thing as
    deleting the recording for a line. Takes a long LONG time, 10-15 minutes
    what is it doing ?  Something like this should be take what, 1-2 seconds.
    

    	Gil,

   Could you, please, post here or send me (TOOK::SHMUYLOVICH) the exact 
 command you are using to export past time data. Are you using wildcard?

Regarding the Delete Recording command. 10-15 minutes is too much for 
this operation. Could you, please, do two Delete Recording commands in a row
( for different recording requests). Does the second command take less time?


	Sam
    

    Hi sam, here is my export command, the one that blows all the links.
    
!---------------------------------------------------------------------------
export node4 .EU.BY.BYL.BYLR01 line syn-2 -
          begin = 01-jul-1992 -
        , end   = 21-jul-1992 -
        , export target = DISK$DATA:[MCC]EXP_TEMP.RDB -
        , in domain .DM.WAN
!---------------------------------------------------------------------------
    
    And here are the SLOW record commands, I tried both with and without
     wildcards as you can see. Same SLOW results anyway I try it.
    
!-------------------------------------------------------------------------------
delete record node4 .EU.BY.BYL.BYLR01        partition=*, in domain= .DM.WAN
!-------------------------------------------------------------------------------
delete record node4 .EU.BY.BYL.BYLR01 line * partition=*, in domain= .DM.WAN
!-------------------------------------------------------------------------------
delete record node4 .EU.BY.BYL.BYLR01 circ * partition=*, in domain= .DM.WAN
!-------------------------------------------------------------------------------
    
del record node4 .EU.BY.BYL.BYLR01 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line ethernet partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ ethernet partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-1 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-1 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-2 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-2 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-3 partition=counters,  in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-3 partition=counters,  in domain= .DM.WAN
!
del record node4 .EU.BY.BYL.BYLR01 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line ethernet partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ ethernet partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-1 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-1 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-2 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-2 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 line syn-3 partition=characteristics, in domain= .DM.WAN
del record node4 .EU.BY.BYL.BYLR01 circ syn-3 partition=characteristics, in domain= .DM.WAN