[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

632.0. "X.25 events via NODE4 AM?" by BAHTAT::BOND () Thu Jan 17 1991 09:51

    Although the NODE4 access module does not offer X25 management, is
    there any way that I can receive X.25 events (eg 5.17/18 DTE up/down)
    and do something meaningful within MCC with them eg firing an Alarm?
    
    I see from the "Phase IV AM use" manual Appendix A that the X.25 events
    are listed but because there is no X25 PROTOCOL entity, there is not a
    GETEVENT directive that covers these X25 events.  Is there therefore
    any other way I can pick up these events within MCC and react to them?
    
    [I realise that I will have to use NCP to define and manage the lines
    and DTEs but that is not an issue.  I just need MCC to receive any X.25
    status change events.]
    
    Chris Bond
T.RTitleUserPersonal
Name		DateLines
632.1Not in V1.1TOOK::CAREYFri Jan 18 1991 21:0020
    
    Nope.  Sorry.
    
    No way in V1.1 can we do that for you.
    
    I like the idea though.  With the [almost] infinite list of tasks that we
    are doing, supporting X.25 with DECnet Phase 4 keeps getting pushed
    into the "maybe next time" category, and that has gone on so long there
    is a lot of doubt that it will ever get done.
    
    Just pulling in X.25 events sounds smaller, almost something that could
    sneak in on the odd weekend.  Would just event support for X.25 provide
    significant value added?
    
    Thanks for the idea.  Sorry I don't have a more positive message to
    give you.
    
    -Jim Carey
632.2x.25 events would be usefulBAHTAT::BONDMon Jan 21 1991 04:4027
    Jim,
    
    Thanks for your prompt response.
    
    My requirement was for a demonstration of our work between mcc and an
    OSI/NMF management system.  We need to indicate failure of an x.25
    circuit.  Now we can do that by setting up DLM over it to another
    system and waiting for the decnet circuit to fail after we pull the
    x.25 plug.  So by mapping events we can satisfy our requirements.  If
    node4 could have received DTE down/up events we could have dispensed
    with DLM and the mapping, but for our demo it is no great shakes!
    
    In terms of real life application; customers may well use mcc for
    monitoring purposes as much as for control.  Hence having a workstation
    running mcc which is capable of indicating x.25 faults would be of use
    even though other utilities would be needed to try to fix the x.25
    fault.  Many other management systems major on the monitoring aspects
    including generation of trouble tickets and fault reports and regard
    the control aspects as secondary.  The management station serves as an
    integration point for ALL fault events.
    
    So in summary: Yes I think receiving other events (eg X.25) is useful;
    both in real life and for my demo - if you managed to do it one
    weekend.  As ncp (ie evl/OPCOM) currently logs X.25 events, I feel
    customers will miss this in mcc.  Hope that positions it!
    
    chris