< draft-ietf-ptopomib-pdp-02.txt   draft-ietf-ptopomib-pdp-03.txt >
Draft PTOPO Discovery Protocol and MIB March 1998 PTOPOMIB Working Group Andy Bierman
Internet Draft Cisco Systems, Inc.
Keith McCloghrie
Cisco Systems, Inc.
16 November 1998
<draft-ietf-ptopomib-pdp-02.txt>
Physical Topology Discovery Protocol and MIB Physical Topology Discovery Protocol and MIB
2 March 1998 <draft-ietf-ptopomib-pdp-03.txt>
Andy Bierman
Cisco Systems Inc.
abierman@cisco.com
Keith McCloghrie
Cisco Systems Inc.
kzm@cisco.com
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 1id-abstracts.txt listing contained in the Internet- Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ftp.ietf.org, nic.nordu.net, venera.isi.edu, or
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). munnari.oz.au.
1. Introduction Distribution of this document is unlimited. Please send comments to the
PTOPOMIB Working Group, <ptopo@3com.com>.
1. Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
2. Abstract
This memo defines an experimental protocol, and an experimental portion This memo defines an experimental protocol, and an experimental portion
of the Management Information Base (MIB) for use with network management of the Management Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it describes a protocols in the Internet community. In particular, it describes a
physical topology discovery protocol and managed objects used for physical topology discovery protocol and managed objects used for
Draft PTOPO Discovery Protocol and MIB March 1998
managing the protocol. managing the protocol.
2. The SNMP Network Management Framework 3. Table of Contents
The SNMP Network Management Framework presently consists of three major
components. They are:
o the SMI, described in RFC 1902 [RFC1902], - the mechanisms used for 1 Copyright Notice ................................................ 1
describing and naming objects for the purpose of management. 2 Abstract ........................................................ 1
3 Table of Contents ............................................... 2
4 The SNMP Network Management Framework ........................... 3
5 Overview ........................................................ 4
5.1 Terms ......................................................... 4
5.2 Persistent Identifiers ........................................ 4
5.3 Relationship to the Physical Topology MIB ..................... 4
5.4 Relationship to Entity MIB .................................... 5
5.5 Relationship to Interfaces MIB ................................ 5
6 PTOPO Discovery Protocol ........................................ 5
6.1 Frame Encapsulation ........................................... 6
6.2 PDP Forwarding ................................................ 6
6.3 PDP Message Format ............................................ 7
6.3.1 PDP Header Format ........................................... 7
6.3.2 PDP PDU Encoding ............................................ 8
6.4 PDP Data MIB .................................................. 9
6.4.1 Definitions ................................................. 9
6.5 Protocol Operation ............................................ 13
6.5.1 Protocol Initialization ..................................... 14
6.5.2 Message Encoding ............................................ 14
6.5.2.1 Header Fields ............................................. 14
6.5.2.2 VarBindList ............................................... 14
6.5.3 Message Transmission ........................................ 15
6.5.4 Received Message Processing ................................. 15
6.5.4.1 Header Fields ............................................. 16
6.5.4.2 VarBindList ............................................... 16
6.5.4.3 PTOPO MIB Update .......................................... 16
6.5.5 Interface Shutdown Procedure ................................ 17
6.5.5.1 PDP Shutdown Transmission ................................. 17
6.5.5.2 PDP Shutdown Reception .................................... 17
7 PTOPO Discovery Protocol MIB .................................... 18
7.1 Definitions ................................................... 18
8 Intellectual Property ........................................... 27
9 Acknowledgements ................................................ 28
10 References ..................................................... 28
11 Security Considerations ........................................ 30
12 Authors' Addresses ............................................. 30
13 Full Copyright Statement ....................................... 32
4. The SNMP Network Management Framework
o the MIB-II, STD 17, RFC 1213 [RFC1213], - the core set of managed The SNMP Management Framework presently consists of five major
objects for the Internet suite of protocols. components:
o the protocol, RFC 1157 [RFC1157] and/or RFC 1905 [RFC1905], - the o An overall architecture, described in RFC 2271 [RFC2271].
protocol for accessing managed information.
Textual conventions are defined in RFC 1903 [RFC1903], and conformance o Mechanisms for describing and naming objects and events for the
statements are defined in RFC 1904 [RFC1904]. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The
second version, called SMIv2, is described in RFC 1902 [RFC1902],
RFC 1903 [RFC1903] and RFC 1904 [RFC1904].
The Framework permits new objects to be defined for the purpose of o Message protocols for transferring management information. The
experimentation and evaluation. first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [RFC1157]. A second version of the SNMP
message protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and
RFC 1906 [RFC1906]. The third version of the message protocol is
called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2272
[RFC2272] and RFC 2274 [RFC2274].
This memo specifies a MIB module that is compliant to the SNMPv2 SMI. A o Protocol operations for accessing management information. The first
semantically identical MIB conforming to the SNMPv1 SMI can be produced set of protocol operations and associated PDU formats is described
through the appropriate translation. in RFC 1157 [RFC1157]. A second set of protocol operations and
associated PDU formats is described in RFC 1905 [RFC1905].
2.1. Object Definitions o A set of fundamental applications described in RFC 2273 [RFC2273]
and the view-based access control mechanism described in RFC 2275
[RFC2275].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the mechanisms defined in the SMI.
SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type.
3. Overview This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
5. Overview
There is a need for a standardized way of representing the physical There is a need for a standardized way of representing the physical
network connections pertaining to a given management domain. A network connections pertaining to a given management domain. A
standardized discovery mechanism is also required to increase the standardized discovery mechanism is also required to increase the
Draft PTOPO Discovery Protocol and MIB March 1998
likelihood of multi-vendor interoperability of such physical topology likelihood of multi-vendor interoperability of such physical topology
management information. management information.
This document specifies a discovery protocol, suitable for use with the This document specifies a discovery protocol, suitable for use with the
Physical Topology MIB [PTOPO]. Physical Topology MIB [PTOPO].
3.1. Terms 5.1. Terms
Some terms are used throughout this document: Some terms are used throughout this document:
SNMP Agent SNMP Agent
This term refers to an SNMP agent co-located with a particular PDP This term refers to an SNMP agent co-located with a particular PDP
Agent. Specifically, it refers to the SNMP Agent providing PDP MIB, Agent. Specifically, it refers to the SNMP Agent providing PDP MIB,
Entity MIB, Interfaces MIB, and possibly PTOPO MIB support for a Entity MIB, Interfaces MIB, and possibly PTOPO MIB support for a
particular chassis. particular chassis.
PDP Agent PDP Agent
This term refers to a software entity which implements the PTOPO This term refers to a software entity which implements the PTOPO
Discovery Protocol for a particular chassis. Discovery Protocol for a particular chassis.
3.2. Persistent Identifiers 5.2. Persistent Identifiers
The PTOPO MIB utilizes non-volatile identifiers to distinguish The PTOPO MIB utilizes non-volatile identifiers to distinguish
individual chassis and port components. These identifiers are individual chassis and port components. These identifiers are
associated with external objects in order to relate topology information associated with external objects in order to relate topology information
to the existing managed objects. to the existing managed objects.
In particular, an object from the Entity MIB or Interfaces MIB can be In particular, an object from the Entity MIB or Interfaces MIB can be
used as the 'reference-point' for a connection component identifier. used as the 'reference-point' for a connection component identifier.
3.3. Relationship to the Physical Topology MIB 5.3. Relationship to the Physical Topology MIB
The Physical Topology MIB [PTOPO] allows a PDP Agent to expose learned The Physical Topology MIB [PTOPO] allows a PDP Agent to expose learned
physical topology information, using a standard MIB. PDP is intended to physical topology information, using a standard MIB. PDP is intended to
fully support the PTOPO MIB. fully support the PTOPO MIB.
3.4. Relationship to Entity MIB 5.4. Relationship to Entity MIB
The Entity MIB [RFC2037] allows the physical component inventory and The Entity MIB [RFC2037] allows the physical component inventory and
hierarchy to be identified. The chassis identifier strings passed in hierarchy to be identified. The chassis identifier strings passed in
PDP messages identify entPhysicalTable entries, and implementation of PDP messages identify entPhysicalTable entries, and implementation of
Draft PTOPO Discovery Protocol and MIB March 1998 the entPhysicalTable as specified in the Version 1 of the Entity MIB
[RFC2037], and implementation of the entPhysicalAlias object from
the entPhysicalTable and entPhysicalXTable (found in 'Entity MIB Version 2 of the Entity MIB [ENTITY-MIB], are required for SNMP agents
Extensions for Persistent Component Identification' [ENTITY-EXT]) are which also implement the PDP MIB.
required for SNMP agents which also implement the PDP MIB.
3.5. Relationship to Interfaces MIB 5.5. Relationship to Interfaces MIB
The Interfaces MIB provides a standard mechanism for managing network The Interfaces MIB provides a standard mechanism for managing network
interfaces. The port identifier strings passed in PDP messages identify interfaces. The port identifier strings passed in PDP messages identify
ifTable (or entPhysicalTable) entries, and implementation of the ifTable ifTable (or entPhysicalTable) entries, and implementation of the ifTable
and ifXTable [RFC2233] are required for SNMP agents which also implement and ifXTable [RFC2233] are required for SNMP agents which also implement
the PDP MIB, for the ports which are represented in the Interfaces MIB. the PDP MIB, for the ports which are represented in the Interfaces MIB.
4. PTOPO Discovery Protocol 6. PTOPO Discovery Protocol
This section defines a discovery protocol, suitable for supporting the This section defines a discovery protocol, suitable for supporting the
data requirements of the PTOPO MIB. data requirements of the PTOPO MIB.
The PTOPO Discovery Protocol (PDP) is a media independent protocol The PTOPO Discovery Protocol (PDP) is a media independent protocol
intended to be run on routers, bridges, access servers, switches, intended to be run on routers, bridges, access servers, switches,
repeaters, etc., allowing a PDP agent to learn SNMP reachability and repeaters, etc., allowing a PDP agent to learn SNMP reachability and
connection endpoint information from adjacent devices. connection endpoint information from adjacent devices.
PDP runs on various media that support Subnetwork Access Protocol PDP runs on various media that support Subnetwork Access Protocol
skipping to change at page 4, line 42 skipping to change at page 6, line 6
Each device configured with an active PDP Agent sends periodic messages Each device configured with an active PDP Agent sends periodic messages
to a multicast MAC address on all physical interfaces enabled for PDP to a multicast MAC address on all physical interfaces enabled for PDP
transmission, and listens for PDP messages on the same set on transmission, and listens for PDP messages on the same set on
interfaces. Each PDP message contains information identifying the source interfaces. Each PDP message contains information identifying the source
port as a PTOPO connection endpoint identifier. It also contains at port as a PTOPO connection endpoint identifier. It also contains at
least one network address which can be used by an NMS to reach an SNMP least one network address which can be used by an NMS to reach an SNMP
agent on the device (via the indicated source port). Each PDP message agent on the device (via the indicated source port). Each PDP message
contains a configurable time-to-live value, which tells the recipient contains a configurable time-to-live value, which tells the recipient
PDP agent when to discard each element of learned topology information. PDP agent when to discard each element of learned topology information.
4.1. Frame Encapsulation 6.1. Frame Encapsulation
The following open issues are under consideration by the working group: The following open issues are under consideration by the working group:
An EtherType value must be selected to identify PDP messages An EtherType value must be selected to identify PDP messages
transmitted over DIX Ethernet, and IEEE 802.3,802.5 media types transmitted over DIX Ethernet, and IEEE 802.3,802.5 media types
Draft PTOPO Discovery Protocol and MIB March 1998
(using LLC/SNAP encapsulation). (using LLC/SNAP encapsulation).
A multicast MAC address must be selected for the destination A multicast MAC address must be selected for the destination
address (DA) field in PDP messages transmitted over DIX Ethernet, address (DA) field in PDP messages transmitted over DIX Ethernet,
IEEE 802.3, and IEEE 802.5 media types. IEEE 802.3, and IEEE 802.5 media types.
4.2. PDP Forwarding 6.2. PDP Forwarding
If at all possible, PDP agents are not supposed to forward PDP messages If at all possible, PDP agents are not supposed to forward PDP messages
received on any port. However, some devices, such as repeaters, cannot received on any port. However, some devices, such as repeaters, cannot
examine each frame received on an interface or port. Such a device will examine each frame received on an interface or port. Such a device will
allow PDP messages to be retransmitted on one or more local ports, and allow PDP messages to be retransmitted on one or more local ports, and
will transmit its own PDP messages on those ports as well. These agents will transmit its own PDP messages on those ports as well. These agents
are termed 'forwarding' PDP agents. are termed 'forwarding' PDP agents.
PDP agents located on devices which examine each frame before PDP agents located on devices which examine each frame before
retransmitting it (e.g., routers and bridges), are expected to process retransmitting it (e.g., routers and bridges), are expected to process
received PDP messages and not retransmit them on any local port. These received PDP messages and not retransmit them on any local port. These
agents are termed 'non-forwarding' PDP agents. agents are termed 'non-forwarding' PDP agents.
An NMS may find physical topology information about the same physical An NMS may find physical topology information about the same physical
port, represented by several PTOPO agents. This may occur for one of port, represented by several PTOPO agents. This may occur for one of
several reasons, including a mixture of forwarding and non-forwarding several reasons, including a mixture of forwarding and non-forwarding
PDP agents within a network. PDP agents within a network.
4.3. PDP Message Format 6.3. PDP Message Format
The basic PDP packet consists of a header, followed by a variable number The basic PDP packet consists of a header, followed by a variable number
of variable bindings in an ASN.1/BER encoded 'VarBindList', as indicated of variable bindings in an ASN.1/BER encoded 'VarBindList', as indicated
in Figure 1. in Figure 1.
+------------+--------------------------------------+ +------------+--------------------------------------+
| header | (ASN.1/BER) VarBindList | | header | (ASN.1/BER) VarBindList |
+------------+--------------------------------------+ +------------+--------------------------------------+
[ Figure 1 -- Basic PDP Message Format ] [ Figure 1 -- Basic PDP Message Format ]
4.3.1. PDP Header Format 6.3.1. PDP Header Format
The PDP header is a 4 byte header, in network byte order, The PDP header is a 4 byte header, in network byte order,
containing 3 fields, as shown in figure 2: containing 3 fields, as shown in figure 2:
Draft PTOPO Discovery Protocol and MIB March 1998
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Flags | Time To Live | | Version | Flags | Time To Live |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
[ figure 2 -- PDP Message Format ] [ figure 2 -- PDP Message Format ]
The PDP header contains the following fields: The PDP header contains the following fields:
skipping to change at page 6, line 33 skipping to change at page 8, line 5
the header word-aligned for easier processing. No flag definition the header word-aligned for easier processing. No flag definition
bits are defined at this time. This field must be set to zero in bits are defined at this time. This field must be set to zero in
all version 1 PDP messages. all version 1 PDP messages.
- Time to live - Time to live
The number of seconds the information in this PDP message should be The number of seconds the information in this PDP message should be
regarded as valid by the recipient. Agents of the PTOPO MIB must regarded as valid by the recipient. Agents of the PTOPO MIB must
not return MIB information based on expired PDP messages. The not return MIB information based on expired PDP messages. The
valid range is 0 to 65535 for this field. valid range is 0 to 65535 for this field.
4.3.2. PDP PDU Encoding 6.3.2. PDP PDU Encoding
Following the PDP header is an SNMP varbind list encoded in ASN.1/BER Following the PDP header is an SNMP varbind list encoded in ASN.1/BER,
[ref. TBD], also referred to as the PDP protocol data unit (PDP-PDU). (as defined in the SMIv2 document [RFC1902]), also referred to as the
The individual MIB instances contained in a PDP PDU are referred to as PDP protocol data unit (PDP-PDU). The individual MIB instances contained
PDP data elements. in a PDP PDU are referred to as PDP data elements.
The standard PDP data elements, defined in the PDP Data MIB, are encoded The standard PDP data elements, defined in the PDP Data MIB, are encoded
as a VarBindList in each PDP message. This data enables a PDP agent to as a VarBindList in each PDP message. This data enables a PDP agent to
implement the PTOPO MIB for connections terminating on the local implement the PTOPO MIB for connections terminating on the local
chassis. chassis.
This section defines the ASN.1 syntax specific to the PDP message. This section defines the ASN.1 syntax specific to the PDP message.
Refer to the Protocol Operations specification [RFC1905] for a complete Refer to the Protocol Operations specification [RFC1905] for a complete
definition of the 'VarBindList' construct. definition of the 'VarBindList' construct.
Note that PDP places no constraints on which MIB instances may be Note that PDP places no constraints on which MIB instances may be
included in a particular VarBindList. included in a particular VarBindList.
Draft PTOPO Discovery Protocol and MIB March 1998
PDP-PDU DEFINITIONS ::= BEGIN PDP-PDU DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY MODULE-IDENTITY
FROM SNMPv2-SMI FROM SNMPv2-SMI
VarBindList VarBindList
FROM SNMPv2-PDU; FROM SNMPv2-PDU;
PDPv1-PDU MODULE-IDENTITY PDPv1-PDU MODULE-IDENTITY
LAST-UPDATED "9709150000Z" LAST-UPDATED "9709150000Z"
skipping to change at page 8, line 4 skipping to change at page 9, line 21
Protocol PDU syntax." Protocol PDU syntax."
::= { experimental xx } ::= { experimental xx }
PDP-PDU ::= PDP-PDU ::=
SEQUENCE { SEQUENCE {
pdp-variable-bindings pdp-variable-bindings
VarBindList VarBindList
} }
END END
Draft PTOPO Discovery Protocol and MIB March 1998
4.4. PDP Data MIB 6.4. PDP Data MIB
This section defines the standard data elements which may be contained This section defines the standard data elements which may be contained
in PDP messages. These elements are defined as MIB objects, but are in PDP messages. These elements are defined as MIB objects, but are
only intended to be encoded into PDP PDUs, and not intended to be only intended to be encoded into PDP PDUs, and not intended to be
instrumented by an SNMP agent. instrumented by an SNMP agent.
The MIB defines six standard data elements: The MIB defines six standard data elements:
- Chassis ID - Chassis ID
- Chassis ID Type - Chassis ID Type
- Port ID - Port ID
- Port ID Type - Port ID Type
- Management Address Type - Management Address Type
- Management Address - Management Address
4.4.1. Definitions 6.4.1. Definitions
PDP-DATA-MIB DEFINITIONS ::= BEGIN PDP-DATA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32 MODULE-IDENTITY, OBJECT-TYPE, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
IANAAddrFamily, PtopoGenAddr, PtopoChassisIdType, IANAAddrFamily, PtopoGenAddr, PtopoChassisIdType,
PtopoChassisId, PtopoPortIdType, PtopoPortId PtopoChassisId, PtopoPortIdType, PtopoPortId
FROM PTOPO-MIB; FROM PTOPO-MIB;
pdpDataMIB MODULE-IDENTITY pdpDataMIB MODULE-IDENTITY
LAST-UPDATED "9709150000Z" LAST-UPDATED "9709150000Z"
ORGANIZATION "IETF PTOPOMIB Working Group" ORGANIZATION "IETF PTOPOMIB Working Group"
CONTACT-INFO CONTACT-INFO
"PTOPOMIB WG Discussion: "PTOPOMIB WG Discussion:
ptopo@3com.com ptopo@3com.com
Subscription: Subscription:
majordomo@3com.com majordomo@3com.com
msg body: [un]subscribe ptopomib msg body: [un]subscribe ptopomib
Andy Bierman Andy Bierman
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Draft PTOPO Discovery Protocol and MIB March 1998
408-527-3711 408-527-3711
abierman@cisco.com abierman@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
408-526-5260 408-526-5260
kzm@cisco.com" kzm@cisco.com"
DESCRIPTION DESCRIPTION
skipping to change at page 9, line 32 skipping to change at page 11, line 4
-- MIB groups -- MIB groups
pdpDataElements OBJECT IDENTIFIER ::= { pdpDataMIBObjects 1 } pdpDataElements OBJECT IDENTIFIER ::= { pdpDataMIBObjects 1 }
-- --
-- *********************************************************** -- ***********************************************************
-- --
-- P D P D A T A E L E M E N T S -- P D P D A T A E L E M E N T S
-- --
-- *********************************************************** -- ***********************************************************
-- --
pdpChassisIdType OBJECT-TYPE pdpChassisIdType OBJECT-TYPE
SYNTAX PtopoChassisIdType SYNTAX PtopoChassisIdType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the type of chassis component "This object identifies the type of chassis component
identifier contained in the pdpChassisId object, within a identifier contained in the pdpChassisId object, within a
given PDP message." given PDP message."
::= { pdpDataElements 1 } ::= { pdpDataElements 1 }
pdpChassisId OBJECT-TYPE pdpChassisId OBJECT-TYPE
SYNTAX PtopoChassisId SYNTAX PtopoChassisId
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the chassis component of the "This object identifies the chassis component of the
particular connection endpoint identifier containing the PDP particular connection endpoint identifier containing the PDP
agent transmitting PDP messages. agent transmitting PDP messages.
Draft PTOPO Discovery Protocol and MIB March 1998
If the chassis ID is unknown for the entry, then this object If the chassis ID is unknown for the entry, then this object
will contain an empty string." will contain an empty string."
::= { pdpDataElements 2 } ::= { pdpDataElements 2 }
pdpPortIdType OBJECT-TYPE pdpPortIdType OBJECT-TYPE
SYNTAX PtopoPortIdType SYNTAX PtopoPortIdType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the type of port component "This object identifies the type of port component
skipping to change at page 11, line 4 skipping to change at page 12, line 23
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the type of network address "This object identifies the type of network address
contained in the pdpMgmtAddr object, within a given PDP contained in the pdpMgmtAddr object, within a given PDP
message." message."
::= { pdpDataElements 5 } ::= { pdpDataElements 5 }
pdpMgmtAddr OBJECT-TYPE pdpMgmtAddr OBJECT-TYPE
SYNTAX PtopoGenAddr SYNTAX PtopoGenAddr
MAX-ACCESS read-only MAX-ACCESS read-only
Draft PTOPO Discovery Protocol and MIB March 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies a particular network address, "This object identifies a particular network address,
associated with an SNMP agent which contains additional associated with an SNMP agent which contains additional
information pertaining to the connection endpoint identified information pertaining to the connection endpoint identified
in a given PDP message. in a given PDP message.
If a management address is unknown for the endpoint If a management address is unknown for the endpoint
described in a given PDP message, then this object will described in a given PDP message, then this object will
contain an empty string." contain an empty string."
skipping to change at page 12, line 4 skipping to change at page 13, line 23
OBJECTS { OBJECTS {
pdpChassisIdType, pdpChassisIdType,
pdpChassisId, pdpChassisId,
pdpPortIdType, pdpPortIdType,
pdpPortId, pdpPortId,
pdpMgmtAddrType, pdpMgmtAddrType,
pdpMgmtAddr pdpMgmtAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft PTOPO Discovery Protocol and MIB March 1998
"The collection of objects which identify connection "The collection of objects which identify connection
endpoint data elements, as used in the PTOPO Discovery endpoint data elements, as used in the PTOPO Discovery
Protocol, and represented in the PTOPO MIB. Protocol, and represented in the PTOPO MIB.
This group is mandatory for agents which implement the PTOPO This group is mandatory for agents which implement the PTOPO
Discovery Protocol." Discovery Protocol."
::= { pdpDataGroups 1 } ::= { pdpDataGroups 1 }
END END
4.5. Protocol Operation 6.5. Protocol Operation
An active PDP Agent must perform the following tasks: An active PDP Agent must perform the following tasks:
- transmit PDP messages - transmit PDP messages
- process received PDP messages - process received PDP messages
- maintain an instance of the PDP MIB - maintain an instance of the PDP MIB
- maintain an instance of the PTOPO MIB - maintain an instance of the PTOPO MIB
- maintain appropriate ifEntry and/or entPhysicalEntry instances - maintain appropriate ifEntry and/or entPhysicalEntry instances
- implement ifAlias and/or entPhysicalAlias MIB objects - implement ifAlias and/or entPhysicalAlias MIB objects
4.5.1. Protocol Initialization 6.5.1. Protocol Initialization
Upon system reinitialization, the following tasks are performed by the Upon system reinitialization, the following tasks are performed by the
PDP agent: PDP agent:
Non-volatile configuration for the PDP MIB is retrieved if Non-volatile configuration for the PDP MIB is retrieved if
applicable, otherwise appropriate default values are assigned to applicable, otherwise appropriate default values are assigned to
all PDP configuration variables. all PDP configuration variables.
If pdpAdminStatus is equal to 'disabled(2)', then PDP If pdpAdminStatus is equal to 'disabled(2)', then PDP
initialization is terminated (until such time that the initialization is terminated (until such time that the
pdpAdminStatus object is set to 'enabled(1)'), otherwise continue. pdpAdminStatus object is set to 'enabled(1)'), otherwise continue.
Internal (implementation-specific) data structures are initialized. Internal (implementation-specific) data structures are initialized.
such that appropriate local physical topology information and PDP such that appropriate local physical topology information and PDP
transmission parameters are set. transmission parameters are set.
4.5.2. Message Encoding 6.5.2. Message Encoding
This section does not assume a particular buffering strategy, and such This section does not assume a particular buffering strategy, and such
details are omitted. details are omitted.
Draft PTOPO Discovery Protocol and MIB March 1998 6.5.2.1. Header Fields
4.5.2.1. Header Fields
The version field is set to one (0x01). The version field is set to one (0x01).
The flags field is set to zero (0x00). The flags field is set to zero (0x00).
The time-to-live field is set to the value obtained by the following The time-to-live field is set to the value obtained by the following
formula: formula:
TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier)) TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier))
4.5.2.2. VarBindList 6.5.2.2. VarBindList
Each message must contain one instance of each of the six mandatory Each message must contain one instance of each of the six mandatory
PDP-PDU data elements, defined in the PDP Data MIB. Additional data PDP-PDU data elements, defined in the PDP Data MIB. Additional data
elements may be added as maximum frame size permits. elements may be added as maximum frame size permits.
ASN.1/BER encoding is defined in [TBD], and is outside the scope of this ASN.1/BER encoding is defined in Version 2 of the Structure of
document. Management Information (SMIv2) [RFC1902], and is outside the scope of
this document.
4.5.3. Message Transmission 6.5.3. Message Transmission
An active PDP agent must transmit a PDP message out each appropriate An active PDP agent must transmit a PDP message out each appropriate
port, once each message interval, as determined by the port, once each message interval, as determined by the
pdpMessageTxInterval MIB object. Messages transmitted on repeater pdpMessageTxInterval MIB object. Messages transmitted on repeater
devices may be sent for each repeater backplane, once per message devices may be sent for each repeater backplane, once per message
interval. Actual transmission intervals should be jittered to prevent interval. Actual transmission intervals should be jittered to prevent
synchronization effects. synchronization effects.
Note that the agent must suppress the transmission of multiple PDP Note that the agent must suppress the transmission of multiple PDP
messages during a single message interval, in the event message messages during a single message interval, in the event message
skipping to change at page 14, line 5 skipping to change at page 15, line 28
In this case, a single port in the port group should be selected (in an In this case, a single port in the port group should be selected (in an
implementation-specific manner) to represent the port group. Note that implementation-specific manner) to represent the port group. Note that
an agent is encouraged to represent port groups as 'backplanes', in the an agent is encouraged to represent port groups as 'backplanes', in the
entPhysicalTable of the Entity MIB, rather than individual ports in entPhysicalTable of the Entity MIB, rather than individual ports in
either the Entity MIB or Interfaces MIB. either the Entity MIB or Interfaces MIB.
Regarding the transmission of a single PDP message, for the indicated Regarding the transmission of a single PDP message, for the indicated
physical interface contained in the local system: physical interface contained in the local system:
Draft PTOPO Discovery Protocol and MIB March 1998
The PDP agent checks for the existence of a pdpSuppressEntry for The PDP agent checks for the existence of a pdpSuppressEntry for
the port. If an entry exists then this port is skipped, otherwise the port. If an entry exists then this port is skipped, otherwise
continue. continue.
The PDP message is encapsulated as appropriate for the port. The PDP message is encapsulated as appropriate for the port.
The MAC header is filled in with appropriate SA and DA and The MAC header is filled in with appropriate SA and DA and
EtherType fields. (Ignoring LLC/SNAP details). EtherType fields. (Ignoring LLC/SNAP details).
The frame is transmitted or passed to a lower layer for The frame is transmitted or passed to a lower layer for
transmission. transmission.
The pdpStatsOutPkts counter is incremented for the indicated local The pdpStatsOutPkts counter is incremented for the indicated local
port. port.
4.5.4. Received Message Processing 6.5.4. Received Message Processing
An active PDP agent must process PDP messages received on each An active PDP agent must process PDP messages received on each
appropriate port, as such messages arrive. appropriate port, as such messages arrive.
The following sections refer to the reception of a single PDP message, The following sections refer to the reception of a single PDP message,
for the indicated physical interface contained in the local system: for the indicated physical interface contained in the local system:
4.5.4.1. Header Fields 6.5.4.1. Header Fields
The PDP message and the chassis/port indices associated with the The PDP message and the chassis/port indices associated with the
receiving port are retrieved. receiving port are retrieved.
The PDP version and flags field are checked. The version should equal The PDP version and flags field are checked. The version should equal
one (0x01) and the flags should equal zero (0x00). If not, the one (0x01) and the flags should equal zero (0x00). If not, the
pdpStatsInErrors counter for the receiving port is incremented and pdpStatsInErrors counter for the receiving port is incremented and
processing is terminated; otherwise continue. processing is terminated; otherwise continue.
4.5.4.2. VarBindList 6.5.4.2. VarBindList
The ASN.1/BER portion of the message is decoded. (Such parsing The ASN.1/BER portion of the message is decoded. (Such parsing
techniques are beyond the scope of this document.) If this portion of techniques are beyond the scope of this document.) If this portion of
the PDP message is not properly encoded, as defined in the PDP Data MIB, the PDP message is not properly encoded, as defined in the PDP Data MIB,
then the pdpStatsInErrors counter for the receiving port is incremented, then the pdpStatsInErrors counter for the receiving port is incremented,
and processing is terminated; otherwise continue. and processing is terminated; otherwise continue.
The list of data elements is examined. The agent must skip and ignore The list of data elements is examined. The agent must skip and ignore
Draft PTOPO Discovery Protocol and MIB March 1998
PDU data elements unknown to the agent. If any of the mandatory data PDU data elements unknown to the agent. If any of the mandatory data
elements are missing, then the pdpStatsInErrors counter for the elements are missing, then the pdpStatsInErrors counter for the
receiving port is incremented, and processing is terminated; otherwise receiving port is incremented, and processing is terminated; otherwise
continue. continue.
The pdpStatsInGoodPkts counter is incremented for the receiving port. The pdpStatsInGoodPkts counter is incremented for the receiving port.
4.5.4.3. PTOPO MIB Update 6.5.4.3. PTOPO MIB Update
If the time-to-live field in the PDP message header is zero then execute If the time-to-live field in the PDP message header is zero then execute
this interface shutdown procedure, described below. Processing of the this interface shutdown procedure, described below. Processing of the
PDP message is now complete. PDP message is now complete.
If the time-to-live field is non-zero, then the appropriate If the time-to-live field is non-zero, then the appropriate
ptopoConnEntry is found or created, based on the data elements included ptopoConnEntry is found or created, based on the data elements included
in the PDP message. If the indicated entry is dynamic (i.e., in the PDP message. If the indicated entry is dynamic (i.e.,
ptopoConnIsStatic is true), then the current sysUpTime value is stored ptopoConnIsStatic is true), then the current sysUpTime value is stored
in the ptopoConnLastVerifyTime field for the entry. in the ptopoConnLastVerifyTime field for the entry.
skipping to change at page 15, line 37 skipping to change at page 17, line 14
If a ptopoConnEntry of one type was replaced with an entry of a If a ptopoConnEntry of one type was replaced with an entry of a
different type, then the ptopoConnTabReplaces counter is incremented. different type, then the ptopoConnTabReplaces counter is incremented.
If any ptopoConnEntry was added or deleted, or if information other than If any ptopoConnEntry was added or deleted, or if information other than
the ptopoConnLastVerifyTime changed for any entry due to the processing the ptopoConnLastVerifyTime changed for any entry due to the processing
of this PDP message, then the ptopoLastChangeTime object is set with the of this PDP message, then the ptopoLastChangeTime object is set with the
current sysUpTime, and a ptopoConfigChange trap event is generated. (See current sysUpTime, and a ptopoConfigChange trap event is generated. (See
the PTOPO MIB for information on ptopoConfigChange trap generation.) the PTOPO MIB for information on ptopoConfigChange trap generation.)
4.5.5. Interface Shutdown Procedure 6.5.5. Interface Shutdown Procedure
A special procedure exists for the case in which a PDP agent knows a A special procedure exists for the case in which a PDP agent knows a
particular port is about to become non-operational. particular port is about to become non-operational.
Note that the pdpSuppressTable has precedence over these procedures, and Note that the pdpSuppressTable has precedence over these procedures, and
they are only executed if the indicated interface is not specified in they are only executed if the indicated interface is not specified in
the pdpSuppressTable. the pdpSuppressTable.
If any entries are deleted as a result of these procedures, the If any entries are deleted as a result of these procedures, the
ptopoConnTabDeletes counter is incremented for each deleted entry. ptopoConnTabDeletes counter is incremented for each deleted entry.
Draft PTOPO Discovery Protocol and MIB March 1998 6.5.5.1. PDP Shutdown Transmission
4.5.5.1. PDP Shutdown Transmission
In the event an interface, currently configured with PDP message In the event an interface, currently configured with PDP message
transmission enabled, either becomes disabled for PDP activity, or the transmission enabled, either becomes disabled for PDP activity, or the
interface is administratively disabled, a final PDP message is interface is administratively disabled, a final PDP message is
transmitted with a time to live value of zero (before the interface is transmitted with a time to live value of zero (before the interface is
disabled). disabled).
In the event the pdpOperStatus is transitioning to the disabled state, In the event the pdpOperStatus is transitioning to the disabled state,
then this shutdown procedure should be executed for all local then this shutdown procedure should be executed for all local
interfaces. interfaces.
4.5.5.2. PDP Shutdown Reception 6.5.5.2. PDP Shutdown Reception
After reception of a valid PDP message with a time-to-live value equal After reception of a valid PDP message with a time-to-live value equal
to zero, the PDP Agent must remove all information in the PTOPO MIB to zero, the PDP Agent must remove all information in the PTOPO MIB
learned from the particular PDP agent, which is associated with the learned from the particular PDP agent, which is associated with the
indicated remote connection endpoint. indicated remote connection endpoint.
5. PTOPO Discovery Protocol MIB 7. PTOPO Discovery Protocol MIB
This section defines the MIB used to configure PDP agent behavior. This section defines the MIB used to configure PDP agent behavior.
5.1. Definitions 7.1. Definitions
PDP-MIB DEFINITIONS ::= BEGIN PDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus RowStatus
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
PhysicalIndex PhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
pdpMIB MODULE-IDENTITY pdpMIB MODULE-IDENTITY
LAST-UPDATED "9707300000Z" LAST-UPDATED "9707300000Z"
ORGANIZATION "IETF PTOPOMIB Working Group" ORGANIZATION "IETF PTOPOMIB Working Group"
CONTACT-INFO CONTACT-INFO
"PTOPOMIB WG Discussion: "PTOPOMIB WG Discussion:
Draft PTOPO Discovery Protocol and MIB March 1998
ptopo@3com.com ptopo@3com.com
Subscription: Subscription:
majordomo@3com.com majordomo@3com.com
msg body: [un]subscribe ptopomib msg body: [un]subscribe ptopomib
Andy Bierman Andy Bierman
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
408-527-3711 408-527-3711
skipping to change at page 18, line 4 skipping to change at page 19, line 28
If an object of this type has a value of 'ifIndexType(1)', If an object of this type has a value of 'ifIndexType(1)',
then the associated 'port ID' value represents an ifEntry, then the associated 'port ID' value represents an ifEntry,
with the same ifIndex value. with the same ifIndex value.
If an object of this type has a value of If an object of this type has a value of
'entPhysicalIndexType(2)', then the associated 'port ID' 'entPhysicalIndexType(2)', then the associated 'port ID'
value represents an entPhysicalEntry, with the same value represents an entPhysicalEntry, with the same
entPhysicalIndex value." entPhysicalIndex value."
SYNTAX INTEGER { SYNTAX INTEGER {
ifIndexType(1), ifIndexType(1),
Draft PTOPO Discovery Protocol and MIB March 1998
entPhysicalIndexType(2) entPhysicalIndexType(2)
} }
-- --
-- *********************************************************** -- ***********************************************************
-- --
-- P D P C O N F I G -- P D P C O N F I G
-- --
-- *********************************************************** -- ***********************************************************
-- --
skipping to change at page 19, line 4 skipping to change at page 20, line 28
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational status of the local PDP agent." "The current operational status of the local PDP agent."
::= { pdpConfig 2 } ::= { pdpConfig 2 }
pdpMessageTxInterval OBJECT-TYPE pdpMessageTxInterval OBJECT-TYPE
SYNTAX Integer32 (5..32768) SYNTAX Integer32 (5..32768)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
Draft PTOPO Discovery Protocol and MIB March 1998
DESCRIPTION DESCRIPTION
"The interval at which PDP messages are transmitted on "The interval at which PDP messages are transmitted on
behalf of this PDP agent. behalf of this PDP agent.
If the agent is capable of storing non-volatile If the agent is capable of storing non-volatile
configuration, then the value of this object must be configuration, then the value of this object must be
restored after a re-initialization of the management restored after a re-initialization of the management
system." system."
DEFVAL { 60 } DEFVAL { 60 }
::= { pdpConfig 3 } ::= { pdpConfig 3 }
skipping to change at page 20, line 4 skipping to change at page 21, line 29
-- PdpSuppressTable: -- PdpSuppressTable:
-- Disable PDP activity on individual local ports -- Disable PDP activity on individual local ports
pdpSuppressTable OBJECT-TYPE pdpSuppressTable OBJECT-TYPE
SYNTAX SEQUENCE OF PdpSuppressEntry SYNTAX SEQUENCE OF PdpSuppressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table controlling PDP message transmission on individual "A table controlling PDP message transmission on individual
interfaces, ports, or backplanes." interfaces, ports, or backplanes."
Draft PTOPO Discovery Protocol and MIB March 1998
::= { pdpConfig 6 } ::= { pdpConfig 6 }
pdpSuppressEntry OBJECT-TYPE pdpSuppressEntry OBJECT-TYPE
SYNTAX PdpSuppressEntry SYNTAX PdpSuppressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PDP message configuration information for a particular "PDP message configuration information for a particular
port. The port must be contained in the same chassis as the port. The port must be contained in the same chassis as the
PDP agent. PDP messages will not be transmitted or received PDP agent. PDP messages will not be transmitted or received
skipping to change at page 21, line 5 skipping to change at page 22, line 28
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entPhysicalIndex value used to identify the chassis "The entPhysicalIndex value used to identify the chassis
component associated with this entry. The associated component associated with this entry. The associated
entPhysicalEntry must be active, and the associated entPhysicalEntry must be active, and the associated
entPhysicalClass object must be equal to 'chassis(3)'." entPhysicalClass object must be equal to 'chassis(3)'."
::= { pdpSuppressEntry 1 } ::= { pdpSuppressEntry 1 }
Draft PTOPO Discovery Protocol and MIB March 1998
pdpSuppressPortIdType OBJECT-TYPE pdpSuppressPortIdType OBJECT-TYPE
SYNTAX PdpPortIdType SYNTAX PdpPortIdType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of index value contained in the associated "The type of index value contained in the associated
pdpSuppressPortId object." pdpSuppressPortId object."
::= { pdpSuppressEntry 2 } ::= { pdpSuppressEntry 2 }
pdpSuppressPortId OBJECT-TYPE pdpSuppressPortId OBJECT-TYPE
skipping to change at page 22, line 5 skipping to change at page 23, line 29
::= { pdpSuppressEntry 3 } ::= { pdpSuppressEntry 3 }
pdpSuppressRowStatus OBJECT-TYPE pdpSuppressRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this entry." "The status of this entry."
::= { pdpSuppressEntry 4 } ::= { pdpSuppressEntry 4 }
Draft PTOPO Discovery Protocol and MIB March 1998
-- --
-- *********************************************************** -- ***********************************************************
-- --
-- P D P S T A T S -- P D P S T A T S
-- --
-- *********************************************************** -- ***********************************************************
-- --
-- PDP Stats Group -- PDP Stats Group
pdpStatsTable OBJECT-TYPE pdpStatsTable OBJECT-TYPE
skipping to change at page 23, line 4 skipping to change at page 24, line 30
pdpStatsPortId pdpStatsPortId
} }
::= { pdpStatsTable 1 } ::= { pdpStatsTable 1 }
PdpStatsEntry ::= SEQUENCE { PdpStatsEntry ::= SEQUENCE {
pdpStatsChassisId PhysicalIndex, pdpStatsChassisId PhysicalIndex,
pdpStatsPortIdType PdpPortIdType, pdpStatsPortIdType PdpPortIdType,
pdpStatsPortId Integer32, pdpStatsPortId Integer32,
pdpStatsInGoodPkts Counter32, pdpStatsInGoodPkts Counter32,
pdpStatsInErrors Counter32, pdpStatsInErrors Counter32,
Draft PTOPO Discovery Protocol and MIB March 1998
pdpStatsOutPkts Counter32 pdpStatsOutPkts Counter32
} }
pdpStatsChassisId OBJECT-TYPE pdpStatsChassisId OBJECT-TYPE
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entPhysicalIndex value used to identify the chassis "The entPhysicalIndex value used to identify the chassis
component associated with this entry. The associated component associated with this entry. The associated
skipping to change at page 24, line 5 skipping to change at page 25, line 30
local chassis. local chassis.
If the associated pdpStatsPortIdType is equal to If the associated pdpStatsPortIdType is equal to
'entPhysicalIndexType(2)', then this pdpStatsPortId 'entPhysicalIndexType(2)', then this pdpStatsPortId
represents an entPhysicalEntry with the same represents an entPhysicalEntry with the same
entPhysicalIndex value. The associated entPhysicalEntry entPhysicalIndex value. The associated entPhysicalEntry
must be active, and the associated entPhysicalClass object must be active, and the associated entPhysicalClass object
must be equal to 'port(10)' or 'backplane(4)'." must be equal to 'port(10)' or 'backplane(4)'."
::= { pdpStatsEntry 3 } ::= { pdpStatsEntry 3 }
Draft PTOPO Discovery Protocol and MIB March 1998
pdpStatsInGoodPkts OBJECT-TYPE pdpStatsInGoodPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of valid PDP messages received by this PDP agent "The number of valid PDP messages received by this PDP agent
on the indicated port, while this PDP agent is enabled." on the indicated port, while this PDP agent is enabled."
::= { pdpStatsEntry 4 } ::= { pdpStatsEntry 4 }
pdpStatsInErrors OBJECT-TYPE pdpStatsInErrors OBJECT-TYPE
skipping to change at page 25, line 4 skipping to change at page 26, line 29
pdpConformance OBJECT IDENTIFIER ::= { pdpMIB 2 } pdpConformance OBJECT IDENTIFIER ::= { pdpMIB 2 }
pdpCompliances OBJECT IDENTIFIER ::= { pdpConformance 1 } pdpCompliances OBJECT IDENTIFIER ::= { pdpConformance 1 }
pdpGroups OBJECT IDENTIFIER ::= { pdpConformance 2 } pdpGroups OBJECT IDENTIFIER ::= { pdpConformance 2 }
-- compliance statements -- compliance statements
pdpCompliance MODULE-COMPLIANCE pdpCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft PTOPO Discovery Protocol and MIB March 1998
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities which implement
the PDP MIB." the PDP MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pdpConfigGroup, pdpStatsGroup } MANDATORY-GROUPS { pdpConfigGroup, pdpStatsGroup }
::= { pdpCompliances 1 } ::= { pdpCompliances 1 }
-- MIB groupings -- MIB groupings
pdpConfigGroup OBJECT-GROUP pdpConfigGroup OBJECT-GROUP
skipping to change at page 26, line 4 skipping to change at page 27, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent PTOPO "The collection of objects which are used to represent PTOPO
Discovery Protocol statistics. Discovery Protocol statistics.
This group is mandatory for agents which implement the PTOPO This group is mandatory for agents which implement the PTOPO
Discovery Protocol." Discovery Protocol."
::= { pdpGroups 2 } ::= { pdpGroups 2 }
END END
Draft PTOPO Discovery Protocol and MIB March 1998
6. Acknowledgements 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general
license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat."
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive
Director.
The IETF has been notified of intellectual property rights claimed in
regard to some or all of the specification contained in this document.
For more information consult the online list of claimed rights.
9. Acknowledgements
The PTOPO Discovery Protocol is a product of the IETF PTOPOMIB Working The PTOPO Discovery Protocol is a product of the IETF PTOPOMIB Working
Group. Group.
Draft PTOPO Discovery Protocol and MIB March 1998 10. References
7. References
[ENTITY-EXT] [ENTITY-MIB]
Bierman, A., McCloghrie, K., "Entity MIB Extensions for Persistent McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2 (Version
Component Identification", draft-bierman-entmib-compid-00.txt, 2)", draft-ietf-entmib-v2-01.txt, Cisco Systems, November 1998.
Cisco Systems, July 1997.
[PTOPO] [PTOPO]
Bierman, A., Jones, K., "Physical Topology MIB", draft-ietf- Bierman, A., and K. Jones, "Physical Topology MIB", draft-ietf-
ptopomib-mib-00.txt, Cisco Systems, Bay Networks, July 1997. ptopomib-mib-01.txt, Cisco Systems, Bay Networks, November 1998.
[RFC1155]
Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[RFC1157] [RFC1157]
Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, MIT Laboratory for Computer Science, May 1990. International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[RFC1213] [RFC1212]
McCloghrie, K., and M. Rose, Editors, "Management Information Base Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Performance Systems International, Hughes LAN Systems, March 1991.
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991. [RFC1215]
M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991.
[RFC1901]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901,
SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting,
Inc., International Network Services, January 1996.
[RFC1902] [RFC1902]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Structure of Management Information for version 2 Waldbusser, "Structure of Management Information for version 2 of
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP
January 1996. Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[RFC1903] [RFC1903]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Textual Conventions for version 2 of the Simple Waldbusser, "Textual Conventions for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996. Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[RFC1904] [RFC1904]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Conformance Statements for version 2 of the Simple Waldbusser, "Conformance Statements for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1904, January 1996. Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[RFC1905] [RFC1905]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
S. Waldbusser, "Protocol Operations for version 2 of the Simple Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research,
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
[RFC2037] International Network Services, January 1996.
McCloghrie, K., Bierman, A., "Entity MIB using SMIv2", RFC 2037,
Draft PTOPO Discovery Protocol and MIB March 1998 [RFC1906]
SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)"", RFC 1906, SNMP Research, Inc.,
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[RFC2037]
McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2", RFC 2037,
Cisco Systems, October 1996. Cisco Systems, October 1996.
[RFC2233] [RFC2233]
McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB McCloghrie, K., and F. Kastenholtz, "The Interfaces Group MIB using
using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997. SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997.
Draft PTOPO Discovery Protocol and MIB March 1998 [RFC2271]
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
8. Security Considerations [RFC2272]
Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[RFC2273]
Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998.
[RFC2274]
Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998.
[RFC2275]
Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998.
11. Security Considerations
This protocol and associated MIB can expose the existence of physical This protocol and associated MIB can expose the existence of physical
components, MAC layer addresses, and network layer addresses, pertaining components, MAC layer addresses, and network layer addresses, pertaining
to devices within a given network. A network administrator may wish to to devices within a given network. A network administrator may wish to
restrict access to this management information, using SNMP access restrict access to this management information, using SNMP access
control mechanisms, and restrict PDP message processing to a particular control mechanisms, and restrict PDP message processing to a particular
set of ports, by configuring entries in the pdpSuppressTable. set of ports, by configuring entries in the pdpSuppressTable.
9. Authors' Addresses 12. Authors' Addresses
Andy Bierman Andy Bierman
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA USA 95134
Phone: 408-527-3711 Phone: +1 408-527-3711
Email: abierman@cisco.com Email: abierman@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA USA 95134
Phone: 408-526-5260 Phone: +1 408-526-5260
Email: kzm@cisco.com Email: kzm@cisco.com
Draft PTOPO Discovery Protocol and MIB March 1998 13. Full Copyright Statement
Table of Contents Copyright (C) The Internet Society (1998). All Rights Reserved.
1 Introduction .................................................... 1 This document and translations of it may be copied and furnished to
2 The SNMP Network Management Framework ........................... 2 others, and derivative works that comment on or otherwise explain it or
2.1 Object Definitions ............................................ 2 assist in its implementation may be prepared, copied, published and
3 Overview ........................................................ 2 distributed, in whole or in part, without restriction of any kind,
3.1 Terms ......................................................... 3 provided that the above copyright notice and this paragraph are included
3.2 Persistent Identifiers ........................................ 3 on all such copies and derivative works. However, this document itself
3.3 Relationship to the Physical Topology MIB ..................... 3 may not be modified in any way, such as by removing the copyright notice
3.4 Relationship to Entity MIB .................................... 3 or references to the Internet Society or other Internet organizations,
3.5 Relationship to Interfaces MIB ................................ 4 except as needed for the purpose of developing Internet standards in
4 PTOPO Discovery Protocol ........................................ 4 which case the procedures for copyrights defined in the Internet
4.1 Frame Encapsulation ........................................... 4 Standards process must be followed, or as required to translate it into
4.2 PDP Forwarding ................................................ 5 languages other than English.
4.3 PDP Message Format ............................................ 5
4.3.1 PDP Header Format ........................................... 5 The limited permissions granted above are perpetual and will not be
4.3.2 PDP PDU Encoding ............................................ 6 revoked by the Internet Society or its successors or assigns.
4.4 PDP Data MIB .................................................. 8
4.4.1 Definitions ................................................. 8 This document and the information contained herein is provided on an "AS
4.5 Protocol Operation ............................................ 12 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
4.5.1 Protocol Initialization ..................................... 12 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
4.5.2 Message Encoding ............................................ 12 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
4.5.2.1 Header Fields ............................................. 13 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
4.5.2.2 VarBindList ............................................... 13 FITNESS FOR A PARTICULAR PURPOSE."
4.5.3 Message Transmission ........................................ 13
4.5.4 Received Message Processing ................................. 14
4.5.4.1 Header Fields ............................................. 14
4.5.4.2 VarBindList ............................................... 14
4.5.4.3 PTOPO MIB Update .......................................... 15
4.5.5 Interface Shutdown Procedure ................................ 15
4.5.5.1 PDP Shutdown Transmission ................................. 16
4.5.5.2 PDP Shutdown Reception .................................... 16
5 PTOPO Discovery Protocol MIB .................................... 16
5.1 Definitions ................................................... 16
6 Acknowledgements ................................................ 26
7 References ...................................................... 27
8 Security Considerations ......................................... 29
9 Authors' Addresses .............................................. 29
 End of changes. 94 change blocks. 
183 lines changed or deleted 254 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/