[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

6090.0. "MCC-E-INV_SCHEDULE error?" by SALUD::ORTIZ () Mon Aug 22 1994 12:29

    Has any seen the MCC error message 
    
    	MCC-E-INV_SCHEDULE 
    
    I can't find this error anywhere. It is being generated from a
    CHANGE OF expression with AT EVERY 00:01:00 for time polling interval.
    
    Any help would be appreciated..
    
    Richard
T.RTitleUserPersonal
Name
DateLines
6090.1Means your AT clause is invalidTAEC::LAVILLATTue Aug 23 1994 03:4220
  Re .0:

>
>    Has any seen the MCC error message 
>    
>        MCC-E-INV_SCHEDULE 
>    
     Yes this error code correspond to <invalid schedule time> and is
     generated by the MCC kernel when you specify an invalid schedule time
     ( AT clause ), for example  AT start X until Y with X later than Y.

>    I can't find this error anywhere. It is being generated from a
>    CHANGE OF expression with AT EVERY 00:01:00 for time polling interval.
>    
     Can you give a bit more information : the complete alarm expression for
     example.

     Regards.

     Pierre.
6090.2actual rules that have the problemMSE1::LYONSMultivendor System Eng.Tue Aug 23 1994 18:3385
I have been working with Richard and am the engineer that was on site.

I typed the following in from a FAX the customer sent me so there may be some
typos... but these are the rules that fire immediately with

	MCC-E-INV_SCHEDULE invalid schedule time.

=============================================================================

Create Domain LOCAL_NS:.cluster Rule OMS_BRDG_FDDI_BRIDGE_1825_STATE  -
  Expression   = (BRIDGE FDDI_BRIDGE_1825 DEVICE STATE = BROKEN, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Bridge has changed state"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_BRDG_FDDI_BRIDGE_1855_STATE  -
  Expression   = (BRIDGE FDDI_BRIDGE_1855 DEVICE STATE = BROKEN, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Bridge has changed state"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_BRDG_FDDI_BRIDGE_2121_STATE  -
  Expression   = (BRIDGE FDDI_BRIDGE_2121 DEVICE STATE = BROKEN, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Bridge has changed state"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_CCF102_PORT_14_STATE  -
  Expression   = (SNMP CCF102 rs232 rs232InSigTable (14,dsr) rs232InSigState <> on, AT  EVERY=00:15:00.00), -
  Severity     = Critical, -
  Description  = "HSC000 physical console line changed state", -
  Alarm Fired Parameters       = "MDFOMS$CONTROL"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_CCF102_PORT_16_STATE  -
  Expression   = (SNMP CCF102 rs232 rs232InSigTable (16,dsr) rs232InSigState <> on, AT  EVERY=00:15:00.00), -
  Severity     = Critical, -
  Description  = "VEGA physical console line changed state", -
  Alarm Fired Parameters       = "MDFOMS$CONTROL"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_CCF102_STATE  -
  Expression   = (SNMP CCF102 ipReachability <> up, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Terminal Server failed", -
  Alarm Fired Parameters       = SYS$COMMON:[MCC]MDFOMS$TS_ERROR_EXCEPTION.COM, -
  Batch Queue		       = "MDFOMS$MCC_ALARM_BATCH"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_HOC100_PORT_14_STATE  -
  Expression   = (SNMP HOC100 rs232 rs232InSigTable (14,dsr) rs232InSigState <> on, AT  EVERY=00:15:00.00), -
  Severity     = Critical, -
  Description  = "HSC001 physical console line changed state", -
  Alarm Fired Parameters       = "MDFOMS$CONTROL"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_HOC100_PORT_16_STATE  -
  Expression   = (SNMP HOC100 rs232 rs232InSigTable (16,dsr) rs232InSigState <> on, AT  EVERY=00:15:00.00), -
  Severity     = Critical, -
  Description  = "MIRA physical console line changed state", -
  Alarm Fired Parameters       = "MDFOMS$CONTROL"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_HOC100_STATE  -
  Expression   = (SNMP HOC100 ipReachability <> up, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Terminal Server failed", -
  Alarm Fired Parameters       = SYS$COMMON:[MCC]MDFOMS$TS_ERROR_EXCEPTION.COM, -
  Batch Queue		       = "MDFOMS$MCC_ALARM_BATCH"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_RDT100_PORT_1_STATE  -
  Expression   = (SNMP RDT100 rs232 rs232InSigTable (1,dsr) rs232InSigState <> on, AT  EVERY=00:15:00.00), -
  Severity     = Critical, -
  Description  = "ALCOR physical console line changed state", -
  Alarm Fired Parameters       = "MDFOMS$CONTROL"
!
!
Create Domain LOCAL_NS:.cluster Rule OMS_TS_RDT100_STATE  -
  Expression   = (SNMP RDT100 ipReachability <> up, AT  EVERY=00:03:00.00), -
  Severity     = Critical, -
  Description  = "Terminal Server failed", -
  Alarm Fired Parameters       = SYS$COMMON:[MCC]MDFOMS$TS_ERROR_EXCEPTION.COM, -
  Batch Queue		       = "MDFOMS$MCC_ALARM_BATCH"
!
6090.3date formatMSE1::LYONSMultivendor System Eng.Wed Sep 07 1994 13:499
We found the problem.  Customer had modified the file:

	SYS$COMMON:[SYSMGR]LIB$DT_STARTUP.COM;1

to change the system date format.  Funny thing, some functions would work
like phase 4 node registration but he couldn't register a phase 5 node.
Also, the FDDI concentrators could not be registered but all the terminal
servers and FDDI bridges would.  Now the notifications work and everything
else as well.