Re: Enet Repeater MIB

Donna McMaster <mcmaster@synoptics.com> Thu, 24 June 1993 23:04 UTC

Message-Id: <9306242237.AA05150@aladdin>
Date: Thu, 24 Jun 93 15:37:47 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Donna McMaster <mcmaster@synoptics.com>
To: richard@cayman.com
Subject: Re: Enet Repeater MIB
Cc: snmp@psi.com, hubmib@synoptics.com

Richard,

> I'm implementing an agent based on RFC1368, and I'm wondering
> what kind of events should be used to set the various errors
> which can be indicated in rptrOperStatus, rptrGroupOperStatus, and
> rptrPortOperStatus.  Besides just not being able to communicate
> with the repeater controller at all, there aren't really any failure
> modes that I can think of.  I'm assuming the all the various
> network and MAU problems such as FCS-errors, or 10baseT-link-failures
> don't qualify for this level of error.  Can anyone give me examples
> of what might trigger rptrFailure, groupFailure, portFailure, and
> malfunctioning?  Thanks in advance for any help.

You're right that network or link errors would not be reported 
in the oper status variables.  These variables are designed to 
allow vendors to report operational problems detected by their 
implementations.  If you don't detect an error then report that 
all is well.  Frankly most repeaters these days are like yours 
in that there isn't much that can go wrong with them.  I would 
think that rptrGroupFailure is the most likely as for example 
if a single module failed in a modular repeater.  

Regards,
Donna

--------------------------------------------------------------------
Donna McMaster                                  Voice (408) 764-1206
mcmaster@synoptics.com                          Fax   (408) 764-1299


p.s.  In the future you may want to address these questions to 
the mailing list for the Repeater MIB's working group 
(hubmib@synoptics.com.)  To add yourself to the hubmib mailing 
list, send a request to hubmib-request@synoptics.com.

Re: Enet Repeater MIB Donna McMaster