[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

1813.0. "decconcentrator 500 trap description" by GIDDAY::POPPINS () Mon Sep 25 1995 03:45

    Hi all,
    	I have a customer with a FDDI ring consisting of DECconcentrator500
    and a CISCO 7000. The problem is that at intermittant intervals the
    HP OpenView station reports that the DECconcentrator500's go through a
    warm restart e.g. 
    "T 3342    0.02407  [134.18.80.50]  [134.18.225.2]   SNMP Trap Warm
    start".
    This is accompanied by end-station's freezing and then
    continuing so I believe that this is a real event on the ring. I have
    tried to find a definition of the warm restart trap from a
    DECconcentrator500 but have been unable to do so.
    
    1) Could some kind soul put a good, precise description of the conditions
    under which a DECconcentrator500 would generate a "warm Restart" trap.
    2) Does a document exist, in the same way that a MIB definition exists,
    of the traps which the older FDDI products generate.
    
    thanks in advance
    
    Chris Poppins
    CSC- System Support Engineer

T.R Title User Personal
Name Date Lines

1813.1 NPSS::TAYLOR Mon Sep 25 1995 13:02 46

T.R	Title	User	Personal Name	Date	Lines
1813.1		NPSS::TAYLOR		`Mon Sep 25 1995 13:02`	46
	>> 1) Could some kind soul put a good, precise description of the >> conditions under which a DECconcentrator500 would generate >> a "warm Restart" trap. Either a PC_Trace condition, a software fault, or some kind of hardware error, elm, mac, rmc. More than likely it's a result of a PC_trace, see note 1203 in this conference for a description of the event. In any event, the reset condition should be saved in the diagnostic block in nvram. The diagnostic block can be examined by either using DECmcc or by getting into the manufacturing diagnostic mode. If you can send me some form of the output, maybe I can help find the reset reason. Examining the diagnostic block using MCC: MCC> test conc 08-00-2b-1b-d1-f3 diag block = true Examining the diagnostic block using manufacturing diagnostic mode: Power off the concentrator. Connect a terminal to the OBM port of the concentrator, 19,200 baud. Connect a jumper on the left most two manufacturing pins, the three pins are located on the chassis in a cutout just right of the Power Supply DC OK LED. Power on the concentrator, a banner, some informational, and the DIAG> prompt will be displayed. To examine (dump) the block, type "du". >> 2) Does a document exist, in the same way that a MIB definition >> exists, of the traps which the older FDDI products generate. I'm unaware of a document. The DECconcentrator should support coldstart, warmstart, linkup, phy events (connect (port active), disconnect (standby, disabled, connecting)) and authenticity traps.

    
    >> 1) Could some kind soul put a good, precise description of the 
    >>    conditions under which a DECconcentrator500 would generate 
    >>    a "warm Restart" trap.

    Either a PC_Trace condition, a software fault, or some kind of 
    hardware error, elm, mac, rmc. More than likely it's a result of 
    a PC_trace, see note 1203 in this conference for a description 
    of the event. 

    In any event, the reset condition should be saved in the diagnostic 
    block in nvram. The diagnostic block can be examined by either using 
    DECmcc or by getting into the manufacturing diagnostic mode. If you
    can send me some form of the output, maybe I can help find the reset 
    reason.


    Examining the diagnostic block using MCC:

    MCC> test conc 08-00-2b-1b-d1-f3 diag block = true


    Examining the diagnostic block using manufacturing diagnostic mode:

    Power off the concentrator.

    Connect a terminal to the OBM port of the concentrator, 19,200 baud.

    Connect a jumper on the left most two manufacturing pins, the three
    pins are located on the chassis in a cutout just right of the Power
    Supply DC OK LED.

    Power on the concentrator, a banner, some informational, and the 
    DIAG> prompt will be displayed.

    To examine (dump) the block, type "du".


    >> 2) Does a document exist, in the same way that a MIB definition 
    >>    exists, of the traps which the older FDDI products generate.

    I'm unaware of a document. The DECconcentrator should support coldstart, 
    warmstart, linkup, phy events (connect (port active), disconnect 
    (standby, disabled, connecting)) and authenticity traps.