SNMP Trap document

dsiinc!rem@uunet.uu.net Wed, 26 May 1993 15:31 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07331; 26 May 93 11:31 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07327; 26 May 93 11:31 EDT
Received: from CS.UTK.EDU by CNRI.Reston.VA.US id aa13035; 26 May 93 11:31 EDT
Received: from localhost by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA26973; Wed, 26 May 93 10:55:24 -0400
X-Resent-To: fddi-mib@CS.UTK.EDU ; Wed, 26 May 1993 10:55:22 EDT
Errors-To: owner-fddi-mib@CS.UTK.EDU
Received: from relay2.UU.NET by CS.UTK.EDU with SMTP (5.61+IDA+UTK-930125/2.8s-UTK) id AA26884; Wed, 26 May 93 10:54:32 -0400
Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA11925; Wed, 26 May 93 10:54:10 -0400
Date: Wed, 26 May 93 10:54:08 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: dsiinc!rem@uunet.uu.net
Message-Id: <9305261454.AA11925@relay2.UU.NET>
Received: from dsiinc.UUCP by spool.uu.net with UUCP/RMAIL (queueing-rmail) id 105352.19323; Wed, 26 May 1993 10:53:52 EDT
To: uunet!cs.utk.edu!fddi-mib@uunet.uu.net
Subject: SNMP Trap document
Content-Type: text
Content-Length: 16071

Here is the first draft of the SNMP trap document.  It includes all 
the SRF information we discussed at the last meeting with the exception
of the special "MIB variable" to control trap suppression.  I didn't
know where to put it and am still looking for suggestions.  In addition, 
since I haven't seen the final FDDIMIB RFC, those references may not 
be entirely correct. [Anil, can you make sure my variable names
correspond to the latest FDDIMIB RFC?]

Basically, I took the template we started to use for the 6.2 trap
document (before we axed it) and added the current SRF event and
condition information.  Someone may want to independently verify that
I've includes all the correct mappings.  The only information that can't
really be represented in traps is the "multiple occurrence" flag in SRFs.

I'd appreciate any comments on this, both on the syntax and semantics.

By the way, the FDDI working group for Amsterdam is set for Thursday,
July 15.  We couldn't get Friday because no groups are being scheduled
for that day.

Ron Mackey			Distributed Systems International, Inc.
rem@dsiinc.com			531 W. Roosevelt Road, Suite 2
708-665-4639			Wheaton, IL 60187-5057

--------cut here--------

	  Internet Draft	    FDDI Traps		      April 1993


		    SNMP Trap Definitions For FDDI Management

				   April, 1993
				Version	0.1 as of
			   Thu Apr 15 13:32:56 CDT 1993


				  Ron E. Mackey

		     Distributed Systems International,	Inc.
			531 West Roosevelt Road	- Suite	2
			   Wheaton, Illinois 60187-5057
				  (708)	665-4639

				  rem@dsiinc.com






	  1.  Status of	this Memo

	  This draft document will be submitted	to the RFC editor as an
	  experimental extension to the	SNMP MIB.  Distribution	of this
	  memo is unlimited.  Please send comments to the working group
	  mailing list,	fddi-mib@cs.utk.edu.

	  2.  Abstract

	  This memo defines an experimental portion of the Management
	  Information Base (MIB) for use with network management
	  protocols in TCP/IP-based internets.	In particular, it
	  defines trap objects for managing devices which implement the
	  FDDI,	as specified in	the ANSI SMT 7.3 draft standard.

	  This memo does not specify a standard	for the	Internet
	  community.












	  R. E.	Mackey						[Page 1]





	  Internet Draft	    FDDI Traps		      April 1993


	  3.  Historical Perspective

	  As reported in RFC 1052, IAB Recommendations for the
	  Development of Internet Network Management Standards [1], a
	  two-prong strategy for network management of TCP/IP-based
	  internets was	undertaken.  In	the short-term,	the Simple
	  Network Management Protocol (SNMP), defined in RFC 1067, was
	  to be	used to	manage nodes in	the Internet community.	 In the
	  long-term, the use of	the OSI	network	management framework was
	  to be	examined.  Two documents were produced to define the
	  management information:  RFC 1065, which defined the Structure
	  of Management	Information (SMI), and RFC 1066, which defined
	  the Management Information Base (MIB).  Both of these
	  documents were designed so as	to be compatible with both the
	  SNMP and the OSI network management framework.

	  This strategy	was quite successful in	the short-term:
	  Internet-based network management technology was fielded, by
	  both the research and	commercial communities,	within a few
	  months.  As a	result of this,	portions of the	Internet
	  community became network manageable in a timely fashion.

	  As reported in RFC 1109, Report of the Second	Ad Hoc Network
	  Management Review Group [2], the requirements	of the SNMP and
	  the OSI network management frameworks	were more different than
	  anticipated.	As such, the requirement for compatibility
	  between the SMI/MIB and both frameworks was suspended.  This
	  action permitted the operational network management framework,
	  based	on the SNMP, to	respond	to new operational needs in the
	  Internet community by	producing MIB-II.

	  In May of 1990, the core documents were elevated to "Standard
	  Protocols" with "Recommended"	status.	 As such, the Internet-
	  standard network management framework	consists of:  Structure
	  and Identification of	Management Information for TCP/IP-based
	  internets, RFC 1155 [3], which describes how managed objects
	  contained in the MIB are defined; Management Information Base
	  for Network Management of TCP/IP-based internets, which
	  describes the	managed	objects	contained in the MIB, RFC 1156
	  [4]; and, the	Simple Network Management Protocol, RFC	1157
	  [5], which defines the protocol used to manage these objects.









	  R. E.	Mackey						[Page 2]





	  Internet Draft	    FDDI Traps		      April 1993


	  4.  Overview

	  This document, a companion documument	to [11], defines the
	  trap objects for FDDI	devices	which are to be	manageable via
	  the Simple Network Management	Protocol (SNMP).  At present,
	  this applies to these	values of the ifType variable in the
	  Internet-standard MIB:

	       fddi(15)

	  For these interfaces,	the value of the ifSpecific variable in
	  the MIB-II [4] has the OBJECT	IDENTIFIER value:

	       fddimib73       OBJECT IDENTIFIER ::= { experimental 8 73 }

	  The definitions of these objects draws heavily from related
	  work in the ANSI X3T9.5 committee and	the SMT	subcommittee of
	  that committee.  In fact, the	definitions of the managed
	  objects in this document are,	to the maximum extent possible,
	  identical to those identified	by the ANSI committee.	The
	  semantics of each managed object should be the same with
	  syntactic changes made as necessary to recast	the objects in
	  terms	of the Internet-standard SMI and MIB so	as to be
	  compatible with the SNMP.  Examples of these syntactic changes
	  include remapping booleans to	enumerated integers, remapping
	  bit strings to octet strings,	and the	like.  In addition, the
	  naming of the	objects	was changed to achieve compatibility.

	  These	minimal	syntactic changes with no semantic changes
	  should allow implementations of SNMP manageable FDDI systems
	  to share instrumentation with	other network management schemes
	  and thereby minimize implementation cost.  In	addition, the
	  translation of information conveyed by managed objects from
	  one network management scheme	to another is eased by these
	  shared definitions.

	  Only the essential trap messages, as indicated by their
	  mandatory status in the ANSI specification were retained in
	  this document.  The importance of trap messages which	have an
	  optional status in the ANSI specification were perceived as
	  being	less widely accepted.  Events and actions are remapped
	  into SNMP/SMI/MIB compliant counterparts








	  R. E.	Mackey						[Page 3]





	  Internet Draft	    FDDI Traps		      April 1993


	  4.1.	Format of Definitions

	  Section ? contains contains the specification	of all object
	  types	contained in this module.  The object types are	defined
	  using	the conventions	defined	in the SMI, as amended by the
	  extensions specified in [9,10].












































	  R. E.	Mackey						[Page 4]





	  Internet Draft	    FDDI Traps		      April 1993


	  5.  Object Definitions

	  RFCxxxx-MIB DEFINITIONS ::= BEGIN

	  IMPORTS
		  experimental
		      FROM RFC1155-SMI
		  OBJECT-TYPE
		      FROM RFC-1212
		  TRAP-TYPE
		      FROM RFC-1215
		  fddimib,
		  fddimibSMTPeerWrapFlag,
		  fddimibSMTCFState,
		  fddimibMACDaFlag,
		  fddimibMACUnaDaFlag,
		  fddimibMACSMTAddress,
		  fddimibMACUpstreamNbr,
		  fddimibMACFrameErrorFlag,
		  fddimibMACFrameCts,
		  fddimibMACErrorCts,
		  fddimibMACLostCts,
		  fddimibMACFrameErrorRatio,
		  fddimibMACOldUpstreamNeighbor,
		  fddimibMACUpstreamNeighbor,
		  fddimibMACOldDownstreamNeighbor,
		  fddimibMACDownstreamNeighbor,
		  fddimibMACCurrentPath,
		  fddimibMACAvailablePaths,
		  fddimibMACRequestedPaths,
		  fddimibPORTLerCutoff,
		  fddimibPORTLerAlarm,
		  fddimibPORTLerEstimate,
		  fddimibPORTLemRejectCts,
		  fddimibPORTLemCts,
		  fddimibPORTMyType,
		  fddimibPORTConnectState,
		  fddimibPORTNeighborType,
		  fddimibPORTPCWithhold,
		  fddimibPORTAvailablePaths,
		  fddimibPORTCurrentPath,
		  fddimibPORTRequestedPaths,
		  fddimibPORTNeighborType
		      FROM RFC-ffff;






	  R. E.	Mackey						[Page 5]





	  Internet Draft	    FDDI Traps		      April 1993


	  --  This MIB module uses the extended	OBJECT-TYPE macro as
	  --  defined in [9], and the TRAP-TYPE	macro as defined in [10]

	  -- this is the FDDI MIB trap module

	  fddimib OBJECT IDENTIFIER ::=	{ experimental 8 73 }

	  fddimibSMTPeerWrapCondition TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibSMTPeerWrapFlag,
			  fddimibSMTCFState }
	      DESCRIPTION
		      "This trap message is generated when
		      fddimibSMTPeerWrapFlag changes."
	      REFERENCE
		      "ANSI { fddiSMT 72 }"
	      ::= 1

	  fddimibMACDuplicateAddressCondition TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibMACDaFlag,
			  fddimibMACUnaDaFlag,
			  fddimibMACSMTAddress,
			  fddimibMACUpstreamNbr	}
	      DESCRIPTION
		      "This trap message is generated when either
		      fddimibMACDaFlag or fddimibMACUnaDaFlag change."
	      REFERENCE
		      "ANSI { fddiMAC 140 }"
	      ::= 2

	  fddimibMACFrameErrorCondition	TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibMACFrameErrorFlag,
			  fddimibMACFrameCts,
			  fddimibMACErrorCts,
			  fddimibMACLostCts,
			  fddimibMACFrameErrorRatio }
	      DESCRIPTION
		      "This trap message is generated when
		      fddimibMACFrameErrorRatio	is greater than	or equal
		      to fddimibMACFrameErrorThreshold."
	      REFERENCE
		      "ANSI { fddiMAC 141 }"
	      ::= 3





	  R. E.	Mackey						[Page 6]





	  Internet Draft	    FDDI Traps		      April 1993


	  fddimibMACNeighborChangeEvent	TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibMACOldUpstreamNeighbor,
			  fddimibMACUpstreamNeighbor,
			  fddimibMACOldDownstreamNeighbor,
			  fddimibMACDownstreamNeighbor,
			  fddimibMACCurrentPath,
			  fddimibMACSMTAddress }
	      DESCRIPTION
		      "This trap message is generated when a change in a
		      MAC's upstream neighbor address or downstream
		      neighbor address is detected."
	      REFERENCE
		      "ANSI { fddiMAC 143 }"
	      ::= 4

	  fddimibMACPathChangeEvent TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibMACAvailablePaths,
			  fddimibMACCurrentPath,
			  fddimibMACRequestedPaths }
	      DESCRIPTION
		      "This trap message is generated when the value of
		      fddimibMACCurrentPath changes, except if the value
		      changes from isolated(1) to local(2) or local(2)
		      to isolated(1)."
	      REFERENCE
		      "ANSI { fddiMAC 144 }"
	      ::= 5

	  fddimibPORTLerCondition TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibPORTLerCutoff,
			  fddimibPORTLerAlarm,
			  fddimibPORTLerEstimate,
			  fddimibPORTLemRejectCts,
			  fddimibPORTLemCts }
	      DESCRIPTION
		      "This trap message is generated when the value of
		      fddimibPORTLerEstimate is	less than or equal to
		      fddiPORTLerAlarm."
	      REFERENCE
		      "ANSI { fddiPORT 80 }"
	      ::= 6






	  R. E.	Mackey						[Page 7]





	  Internet Draft	    FDDI Traps		      April 1993


	  fddimibPORTUndesiredConnectionAttemptEvent TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibPORTMyType,
			  fddimibPORTConnectState,
			  fddimibPORTNeighborType,
			  fddimibPORTPCWithhold	}
	      DESCRIPTION
		      "This trap message is generated when an undesired
		      connection attempt has been made."
	      REFERENCE
		      "ANSI { fddiPORT 81 }"
	      ::= 7

	  fddimibPORTPathChangeEvent TRAP-TYPE
	      ENTERPRISE fddimib
	      VARIABLES	{ fddimibPORTAvailablePaths,
			  fddimibPORTCurrentPath,
			  fddimibPORTRequestedPaths,
			  fddimibPORTMyType,
			  fddimibPORTNeighborType }
	      DESCRIPTION
		      "This trap message is generated when the value of
		      fddimibPORTCurrentPath changes except when the
		      value changes from isolated(1) to	local(2) or
		      local(2) to isolated(1)."
	      REFERENCE
		      "ANSI { fddiPORT 83 }"
	      ::= 8

	  END




















	  R. E.	Mackey						[Page 8]





	  Internet Draft	    FDDI Traps		      April 1993


	  6.  Acknowledgements

	  This document	was produced by	the IETF FDDI MIB working group.















































	  R. E.	Mackey						[Page 9]





	  Internet Draft	    FDDI Traps		      April 1993


	  7.  References

	  [1]  V. Cerf,	IAB Recommendations for	the Development	of
	       Internet	Network	Management Standards.  Internet	Working
	       Group Request for Comments 1052.	 Network Information
	       Center, SRI International, Menlo	Park, California,
	       (April, 1988).

	  [2]  V. Cerf,	Report of the Second Ad	Hoc Network Management
	       Review Group, Internet Working Group Request for	Comments
	       1109.  Network Information Center, SRI International,
	       Menlo Park, California, (August,	1989).

	  [3]  M.T. Rose and K.	McCloghrie, Structure and Identification
	       of Management Information for TCP/IP-based internets,
	       Internet	Working	Group Request for Comments 1155.
	       Network Information Center, SRI International, Menlo
	       Park, California, (May, 1990).

	  [4]  K. McCloghrie and M.T. Rose, Management Information Base
	       for Network Management of TCP/IP-based internets,
	       Internet	Working	Group Request for Comments 1156.
	       Network Information Center, SRI International, Menlo
	       Park, California, (May, 1990).

	  [5]  J.D. Case, M.S. Fedor, M.L. Schoffstall,	and J.R. Davin,
	       Simple Network Management Protocol, Internet Working
	       Group Request for Comments 1157.	 Network Information
	       Center, SRI International, Menlo	Park, California, (May,
	       1990).

	  [6]  M.T. Rose (editor), Management Information Base for
	       Network Management of TCP/IP-based internets, Internet
	       Working Group Request for Comments 1158.	 Network
	       Information Center, SRI International, Menlo Park,
	       California, (May, 1990).

	  [7]  Information processing systems -	Open Systems
	       Interconnection - Specification of Abstract Syntax
	       Notation	One (ASN.1), International Organization	for
	       Standardization.	 International Standard	8824, (December,
	       1987).

	  [8]  Information processing systems -	Open Systems
	       Interconnection - Specification of Basic	Encoding Rules





	  R. E.	Mackey					       [Page 10]





	  Internet Draft	    FDDI Traps		      April 1993


	       for Abstract Notation One (ASN.1), International
	       Organization for	Standardization.  International	Standard
	       8825, (December,	1987).

	  [9]  M.T. Rose, K. McCloghrie	(editors), Towards Concise MIB
	       Definitions, Internet Draft, Internet Engineering Task
	       Force, (September, 1990).

	  [10] M.T. Rose (editor), A Convention	for Defining Traps for
	       use with	the SNMP, Internet Draft, Internet Engineering
	       Task Force, (September, 1990).

	  [11] J.D. Case (editor), FDDI	Management Information Base,
	       Internet	Draft, Internet	Engineering Task Force,	(March,
	       1991).



































	  R. E.	Mackey					       [Page 11]





	  Internet Draft	    FDDI Traps		      April 1993


	  Table	of Contents


	  1 Status of this Memo	...................................    1
	  2 Abstract ..............................................    1
	  3 Historical Perspective ................................    2
	  4 Overview ..............................................    3
	  4.1 Format of	Definitions ...............................    4
	  5 Object Definitions ....................................    5
	  6 Acknowledgements ......................................    9
	  7 References ............................................   10







































	  R. E.	Mackey					       [Page 12]