| 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 | 
    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.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 786.1 | KONING::KONING | Paul Koning, A-13683 | Mon Nov 16 1992 16:56 | 4 | |
| 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.2 | DECelms POLLER | BAGELS::LEVY | Wed Nov 18 1992 17:10 | 2 | |
|     Specifically, the POLLER function in DECelms can detect many ring
    events, including the wrapping of a DEFCN port.
 | |||||
| 786.3 | Example command file. | BSS::C_OUIMETTE | Don't just do something, sit there! | Fri Nov 20 1992 10:55 | 40 | 
|     	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.4 | DCL i'll have a go. | VIVIAN::C_MCCARTHY | Fri Jan 22 1993 06:26 | 6 | |
|     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 
 | |||||