Conference azur::mcc

3884.0. "MCC-E-NOPARAMLIST in alarm" by CTHQ::WOODCOCK () Thu Oct 08 1992 21:19

Hello,

I have written a couple of rules, one to poll all the node4's in a domain:

exp=(node4 * state<>on,at every 0:1:0)

and another to watch the event when the above rule fires:

Expression = (occurs(domain .MCC_REACH rule * osi rule exception))
procedure=x.com

When procedure x.com run I get the following error in the log:

$ ty SYS$SCRATCH:MCC_ALARMS_DATA_20051995.DAT
RULE: Domain NOCMAN_NS:.OSI_RULES Rule osi_rule_except
MANAGED_OBJECT: Domain NOCMAN_NS:.MCC_REACH Rule node4_reach
DESCRIPTION: mcc_reach exception detection
CATEGORY: mcc_reach rule
EXPRESSION: (occurs(domain .MCC_REACH rule * osi rule exception))
TIME: 8-OCT-1992 20:05:19.95
EVIDENCE: The last event detected: Domain NOCMAN_NS:.MCC_REACH Rule node4_reach
OSI Rule Exception   8-OCT-1992 20:05:19.76
EVENT_ARGUMENTS: Event: OSI Rule Exception   Event Type = QualityofServiceAlarm
 Event Time =  8-OCT-1992 20:05:18.75  Probable Cause = Unknown  Additional Info
 = { ( significance = True, information = "Software logic error detected<EOS>%MC
C-E-NOPARAMLIST, no parameter list  was supplied in this ILV buffer" ),  ( signi
ficance = True, information = "(node4 * state<>on,at every 0:1:0)" ) }  Managed
Object = MCC 0 ALARMS RULE node4_reach   Perceived Severity = Indeterminate  Add
itionaltext = "Node4 Reachability Rule  "
PARAMETER:
DOMAIN: Domain NOCMAN_NS:.OSI_RULES
SEVERITY: Indeterminate

Is there anything I can do to get around this error (MCC-E-NOPARAMLIST) so I
can use this functionality with a greater degree of reliability???

thanks,
brad...

Here's another one while polling SNMP nodes. BTW, the tests involved
disconnecting the MCC node Ethernet connector and just putting on a "T" and
a terminator to bring the circuit back up. Maybe I'll try a different test
for these devices. This same testing works for a few other devices I've tried.

best regards,
brad...


$ ty SYS$SCRATCH:MCC_ALARMS_DATA_20315223.DAT
RULE: Domain NOCMAN_NS:.OSI_RULES Rule osi_rule_except
MANAGED_OBJECT: Domain NOCMAN_NS:.MCC_REACH Rule snmp_reach
DESCRIPTION: mcc_reach exception detection
CATEGORY: mcc_reach rule
EXPRESSION: (occurs(domain .MCC_REACH rule * osi rule exception))
TIME: 8-OCT-1992 20:31:52.23
EVIDENCE: The last event detected: Domain NOCMAN_NS:.MCC_REACH Rule snmp_reach O
SI Rule Exception   8-OCT-1992 20:31:52.20
EVENT_ARGUMENTS: Event: OSI Rule Exception   Event Type = QualityofServiceAlarm
 Event Time =  8-OCT-1992 20:31:51.55  Probable Cause = Unknown  Additional Info
 = { ( significance = True, information = "%MCC-E-INV_HANDLE, software error: in
valid handle parameter<EOS>The rule  has been disabled" ),  ( significance = Tru
e, information = "(snmp * ipreachability=down,at every 0:1:0)" ) }  Managed Obje
ct = SNMP NOCMAN_NS:.LITTLETON_W   Perceived Severity = Indeterminate  Additiona
ltext = "SNMP Reachability Rule  "
PARAMETER:
DOMAIN: Domain NOCMAN_NS:.OSI_RULES
SEVERITY: Indeterminate

ok, it's late and I'm talking to myself. The errors were indeed a network
problem (go figure) because of how I did the test. Good thing I figured it
out before anyone else :).

forget I asked,
brad...