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

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

786.0. "monitoring ring/duff concentrators" by VIVIAN::C_MCCARTHY () Mon Nov 16 1992 12:09

    I have a customer that wants to monitor his ring so if one of the 
    concentrators goes duff he can either see it auomatically on a 
    vdu or maybe be mailed about it.  I know you can look at the 
    LED's on the concentrator but over a period, people will forget 
    to check. Because in theory the ring should loop around the 
    duff device and users, other than the onesf hanging off the duff
    concentrator won't realise theres a problem, config:-
    
           __________        __________        __________  TO CONC1
    -------I        I--------I        I--------I        I------->
           I CONC1  I        I CONC2  I        I CONC3  I
    -------I        I--------I        I--------I        I------->
           ----------        ----------        ----------  TO CONC1
    
    
    is there any software he could buy, he has DECELMS, is this
    any good for the job.
    
    Thanks in advance.
    
    Cornell McCarthy
T.RTitleUserPersonal
Name
DateLines
786.1KONING::KONINGPaul Koning, A-13683Mon Nov 16 1992 16:564
ELMS will display everything you can see from the LEDs, plus a lot more.
The information you're looking for is definitely available.

	paul
786.2DECelms POLLERBAGELS::LEVYWed Nov 18 1992 17:102
    Specifically, the POLLER function in DECelms can detect many ring
    events, including the wrapping of a DEFCN port.
786.3Example command file.BSS::C_OUIMETTEDon't just do something, sit there!Fri Nov 20 1992 10:5540
    	Cornell,                                 
    
    FWIW, here's a command file I wrote many moons ago for exactly the
    function you're looking for. Modify as needed for your customer.
    Specifically, it formats the ELMS event logger (produced by the poller)
    every 2 minutes, and searches for particular events, in this case ANY
    alarm from either the concentrator "nsu_con" or the bridge "nsu_lb",
    and sends E-mail when an event occurs. 
    
    See the Appendix in the ELMS manual for specific events you might want
    to search on, i.e., Concentrator unreachable or port operational state
    change.
    
    $ set noon
    $ elms start poller
    $ TIME = f$time()
    $ time_stamp = F$EXTRACT(0,17,TIME)
    $START:
    $ elms format since 'time_stamp' to event.log
    $ TIME = f$time()
    $ time_stamp = F$EXTRACT(0,17,TIME)
    $ FILE = F$SEARCH("SYS$LOGIN:EVENT.LOG")
    $ IF FILE .EQS. "" THEN GOTO WAIT
    $ sea event.log nsu_con /out=conalarm.txt /wind=10
    $ if $STATUS .eqs. "%X00000001" then GOSUB CONALARM
    $ sea event.log nsu_lb /out=lanalarm.txt /wind=10
    $ if $STATUS .eqs. "%X00000001" then GOTO LANALARM
    $ goto WAIT
    $ CONALARM:
    $ MAIL/SUBJ="ELMS CON ALARM" conalarm.txt bss::c_ouimette
    $       RETURN %X1
    $ LANALARM:
    $ MAIL/SUBJ="ELMS LAN ALARM" lanalarm.txt bss::c_ouimette
    $WAIT:
    $ pu/keep=1 event.log
    $ ren event.log event.sav
    $ wait 00:02:00
    $ goto START
    $exit
    
786.4DCL i'll have a go.VIVIAN::C_MCCARTHYFri Jan 22 1993 06:266
    Thanks for program example. I shall have a play with it over the 
    next weeks, now that hols. and xmas are behind us.
    
    Cheers
    
    Cornell McCarthy