Re: portDown/portUp
Anil Rijsinghani <anil@levers.enet.dec.com> Mon, 26 October 1992 20:09 UTC
Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa19950; 26 Oct 92 15:09 EST
Received: from NRI.RESTON.VA.US by IETF.NRI.Reston.VA.US id aa19946; 26 Oct 92 15:09 EST
Received: from CS.UTK.EDU by NRI.Reston.VA.US id aa03433; 26 Oct 92 15:09 EST
Received: by CS.UTK.EDU (5.61++/2.8s-UTK) id AA13783; Mon, 26 Oct 92 14:09:59 -0500
Received: from inet-gw-1.pa.dec.com by CS.UTK.EDU with SMTP (5.61++/2.8s-UTK) id AA13644; Mon, 26 Oct 92 14:05:55 -0500
Received: by inet-gw-1.pa.dec.com; id AA15166; Mon, 26 Oct 92 11:04:15 -0800
Received: by us1rmc.bb.dec.com; id AA05273; Mon, 26 Oct 92 13:59:58 -0500
Message-Id: <9210261859.AA05273@us1rmc.bb.dec.com>
Received: from levers.enet; by us1rmc.enet; Mon, 26 Oct 92 14:00:09 EST
Date: Mon, 26 Oct 1992 14:00:09 -0500
Sender: ietf-archive-request@IETF.NRI.Reston.VA.US
From: Anil Rijsinghani <anil@levers.enet.dec.com>
To: pablo@fibhaifa.com
Cc: fddi-mib@cs.utk.edu
Apparently-To: fddi-mib@cs.utk.edu, pablo@fibhaifa.com
Subject: Re: portDown/portUp
> Agree with Paul and Anil, but if we go further, because of the > same reason we may need some other traps (Duplicate address found > for example?) Pablo, Consistent with the recommendation in RFC-1215 to define new traps sparingly, and following a WG meeting prior to the advancement of the FDDI MIB to PS, we had decided to eliminate traps defined at the time. (I don't believe that portDown/portUp were amongst those defined in the document.) However from operational experience so far, we (and at least one other vendor) have found that portDown traps are needed, at the least. Two customers have specifically asked for them. I guess Duplicate address found could be another reason for network problems, but it doesn't seem to have been encountered in practise often enough to be considered a real problem. This is why I proposed portDown at least. The fewer the traps we define the better, I believe. Anil
- portDown/portUp Anil Rijsinghani
- Re: portDown/portUp Paul DeBeasi
- Re: portDown/portUp James Reeves
- Re: portDown/portUp Anil Rijsinghani
- Re: portDown/portUp Pablo Brenner
- Re: portDown/portUp Anil Rijsinghani
- Re: portDown/portUp Pablo Brenner