Conference azur::mcc

5696.0. "rule on node4 ldb dos counter doesn't work !" by MLNCSC::LASAGNA (ls -l is s, right ?!) Thu Oct 28 1993 12:48

    Hi,
    
    I don't know if this problem is already known, i have encoutered it
    today to a customer site where i have to go back tomorrow .
    
    They want the reachability of PC with Pathworks, no problem, i
    registered partially them in Mcc (without NML) and then i received
    adjacency down event via DECnet.
    
    They launched the NML on some Pc's that they consider important
    and asked to have some rules on certain paramaters.
    
    We tried to set up a Change-Of rule on a counter called "LDB DOS 
    allocation failures" that we can regularly show with the counters
    returned from the pc.
    
MCC> show node4 nwssit all count

Node4 GUNDAM_NS:.dna_node.nwssit
AT 28-OCT-1993 17:29:33 Counters

Examination of Attributes shows:
                  Counter Creation Time = 28-OCT-1993 17:14:01.21
              Seconds Since Last Zeroed = 932 Seconds
                    User Bytes Received = 240 Bytes
                        User Bytes Sent = 2419 Bytes
                 User Messages Received = 21 Messages
                     User Messages Sent = 20 Messages
                   Total Bytes Received = 1634 Bytes
                       Total Bytes Sent = 3290 Bytes
                Total Messages Received = 111 Messages
                    Total Messages Sent = 110 Messages
                      Connects Received = 24 Connects
                          Connects Sent = 0 Connects
                      Response Timeouts = 2 Timeouts
       Received Connect Resource Errors = 0
           Maximum Logical Links Active = 3 Links
                    Packet Format Error = 0
                    Verification Reject = 0
            DOS CCB Allocation Failures = 0
            DOS SDB Allocation Failures = 0
            DOS LDB Allocation Failures = 0
           DOS Link Allocation Failures = 0
MCC>
    
    then we created the rule on mcc
    
MCC> show domain .domain.nsdp rule dosldb all char

Domain GUNDAM_NS:.domain.nsdp Rule dosldb
AT 28-OCT-1993 17:28:18 Characteristics

Examination of attributes shows:
                             Expression = (CHANGE_OF (Node4 nwssit  dos ldb
                                          allocation failures, *,*), at
                                          every=00:01:00)
                               Severity = Major
                         Probable Cause = Unknown

MCC>
    
    unfortunately the rule goes in indeterminate encountering an exception:
    
MCC> notify domain .domain.nsdp
%MCC-S-NOTIFSTART, Notify request 2 started
MCC>

!!!!!!!!!!!!!! Alarm, 28-OCT-1993 17:25:55 !!!!!!!!!!!!!! [2]
Domain: GUNDAM_NS:.DOMAIN.NSDP                        Severity: Indeterminate
Notification Entity: MCC GUNDAM_NS:.dna_node.nwssit ALARMS RULE dosldb
Event Source: Domain GUNDAM_NS:.DOMAIN.NSDP Rule dosldb
Event: OSI Rule Exception

                             Event Type = QualityofServiceAlarm
                             Event Time = 28-OCT-1993 17:25:54.85
                         Probable Cause = Unknown
                        Additional Info = { (
                               significance = True,
                                information = "Software logic error
                                              detected<EOS>%MCC-E-ILVSYNTAXERROR
                                              ,  data type of ASN.1 value
                                              conflicts with type supplied " ),
                                            (
                               significance = True,
                                information = "(CHANGE_OF (Node4 nwssit  dos
                                              ldb allocation failures, *,*), at
                                               every=00:01:00)" ) }
                         Managed Object = MCC 0 ALARMS RULE dosldb
                     Perceived Severity = Indeterminate

MCC>  Exit

    Could you help me ???, does the problem is already known ???
    I reproduced the problem here in office with the same results.
    
    Ciao and thanx in advance ...
    
    	Andrea Lasagna