[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

4024.0. "CAN MODEM CONNECTION BE MONITORED BY DECMCC?" by COOKIE::MERMEL () Tue Nov 03 1992 18:30

    
    We are developing a system that will be interfacing with modems (full
    modem control) connected to terminal servers (upto 256 ports will be 
    connected to modems). These sessions should be up all the time.  If we
    lose a modem connection, this in considered an alarm state, and we
    attempt to re-establish the connection.  
    
    We will be using DECMCC for providing the network status and was
    wondering if there is a way to configure the DECMCC terminal server
    Manager to alarm on the loss of the modem connection to alarm an
    operator.  All communications with the modems will be via the $QIO
    interface.
    
    
    
    Thanks in Advance,
    	Adam Mermel
        Cookie::mermel 
    
T.RTitleUserPersonal
Name
DateLines
4024.1may be some answersMQOSWS::F_MONETTEMontreal Sales SupportWed Nov 04 1992 13:2917
    I know that if you do a show to a specific port , you will be able to
    see parameters like input signal= dsr,cts,cd,ri and output signal = dsr
    and rts also. ( show terminal server XXX port 1 all status)
    
    I did try with the field test version of TSAM  and I wasn't able to
    define an alarm rule on the Carrier Detect(CD) parameters because it 
    was a complex datatypes. I don't know with the new version (SSB).
    
    However, you can set DSRlogout the the specific port and define an
    alarm rule to check if the port status is idle or connected. If you
    set DSRlogout, as soon as you will loose your modem( meaning loosing CD
    for example) the port will be logged out automatically and the alarm
    will become true.
    
    I suppose here that your application using QIO will set the port to be
    connected all the time.
      
4024.2TOOK::FONSECAI heard it through the Grapevine...Fri Nov 06 1992 17:1216
I can't add much to that last reply.  Francois, you'll
be pleased to know that I changed the port input signals and port output signals
complex data type to Latin1String so that alarms could be done on that.
(Changed as a result of field test input for the SSB version of TSAM.)

Our local modem signals expert said to make sure to check for DSR, she said also
to check for DCD, but I got lost at that point.
Now I don't know what that means for TSAM, but the best I can tell is
that you want to make sure that the port input signals and port output signals
attributes contain the string DSR in them.  I don't know if alarm rules
can be written to do that.  

You might also check in the TOOK::TERMINAL_SERVERS notesfile, those folks
know more about that end of things....

-Dave
4024.3IT's workMQOSWS::F_MONETTEMontreal Sales SupportTue Nov 10 1992 19:129
    I did install the tSAM SSB version and i am able to define an alarm
    rule on output signal. (nice job done). What you have to do is define
    an alarm rule (changed of) based on output signal. When you have the
    modem connected, you should be able to see output signal=
    "DSR,CD,CTS,RI" and I think only "DSR" if there is nothing connected on
    the port.
    
    GOOD luck
    Francois