< draft-ietf-ptopomib-mib-04.txt   draft-ietf-ptopomib-mib-05.txt >
PTOPOMIB Working Group Andy Bierman PTOPOMIB Working Group Andy Bierman
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Ken Jones Ken Jones
Nortel Networks Nortel Networks
11 February 2000 14 June 2000
Physical Topology MIB Physical Topology MIB
<draft-ietf-ptopomib-mib-04.txt> <draft-ietf-ptopomib-mib-05.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026 [RFC2026]. provisions of Section 10 of RFC2026 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line ? skipping to change at page 2, line ?
Distribution of this document is unlimited. Please send comments to the Distribution of this document is unlimited. Please send comments to the
authors. authors.
1. Copyright Notice 1. Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
2. Abstract 2. Abstract
This memo defines an experimental portion of the Management Information This memo defines a portion of the Management Information Base (MIB) for
Base (MIB) for use with network management protocols in the Internet use with network management protocols in the Internet community. In
community. In particular, it describes managed objects used for particular, it describes managed objects used for managing physical
managing physical topology identification and discovery. topology identification and discovery.
3. Table of Contents 3. Table of Contents
1 Copyright Notice ................................................ 1 1 Copyright Notice ................................................ 1
2 Abstract ........................................................ 2 2 Abstract ........................................................ 2
3 Table of Contents ............................................... 2 3 Table of Contents ............................................... 2
4 The SNMP Network Management Framework ........................... 2 4 The SNMP Network Management Framework ........................... 2
5 Overview ........................................................ 4 5 Overview ........................................................ 4
5.1 Terms ......................................................... 4 5.1 Terms ......................................................... 4
5.2 Design Goals .................................................. 5 5.2 Design Goals .................................................. 5
skipping to change at page 11, line 24 skipping to change at page 11, line 24
This group contains tables to configure the behavior of the physical This group contains tables to configure the behavior of the physical
topology function. The transmission of ptopoLastChange notifications topology function. The transmission of ptopoLastChange notifications
can be configured using the ptopoConfigTrapInterval scalar MIB object. can be configured using the ptopoConfigTrapInterval scalar MIB object.
7.8. Physical Topology MIB Definitions 7.8. Physical Topology MIB Definitions
PTOPO-MIB DEFINITIONS ::= BEGIN PTOPO-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, mib-2 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Counter32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, AutonomousType, RowStatus, TimeStamp, TruthValue TEXTUAL-CONVENTION, AutonomousType, RowStatus, TimeStamp, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TimeFilter TimeFilter
FROM RMON2-MIB FROM RMON2-MIB
PhysicalIndex PhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB
AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB;
ptopoMIB MODULE-IDENTITY ptopoMIB MODULE-IDENTITY
LAST-UPDATED "200002110000Z" LAST-UPDATED "200002110000Z"
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
skipping to change at page 12, line 30 skipping to change at page 12, line 33
ptopoMIBObjects OBJECT IDENTIFIER ::= { ptopoMIB 1 } ptopoMIBObjects OBJECT IDENTIFIER ::= { ptopoMIB 1 }
-- MIB groups -- MIB groups
ptopoData OBJECT IDENTIFIER ::= { ptopoMIBObjects 1 } ptopoData OBJECT IDENTIFIER ::= { ptopoMIBObjects 1 }
ptopoGeneral OBJECT IDENTIFIER ::= { ptopoMIBObjects 2 } ptopoGeneral OBJECT IDENTIFIER ::= { ptopoMIBObjects 2 }
ptopoConfig OBJECT IDENTIFIER ::= { ptopoMIBObjects 3 } ptopoConfig OBJECT IDENTIFIER ::= { ptopoMIBObjects 3 }
-- textual conventions -- textual conventions
IANAAddrFamily ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An address family. Values are defined in Assigned Numbers,
RFC1700. Note that not all these values make sense in all
contexts where this type is used in this MIB, but they are
included for completeness."
REFERENCE
"Assigned Numbers, [RFC1700], ADDRESS FAMILY NUMBERS"
SYNTAX INTEGER {
other(0),
ipV4(1),
ipV6(2),
nsap(3),
hdlc(4),
bbn1822(5),
ieee802(6),
e163(7),
e164(8),
f69(9),
x121(10),
ipx(11),
appleTalk(12),
decnetIV(13),
banyanVines(14),
e164WithNsap(15)
}
PtopoGenAddr ::= TEXTUAL-CONVENTION PtopoGenAddr ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of an address." "The value of an address."
SYNTAX OCTET STRING (SIZE (0..20)) SYNTAX OCTET STRING (SIZE (0..20))
PtopoChassisIdType ::= TEXTUAL-CONVENTION PtopoChassisIdType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes the source of a chassis identifier. "This TC describes the source of a chassis identifier.
skipping to change at page 14, line 9 skipping to change at page 13, line 25
The enumeration 'chasIdMacAddress(4)' represents a chassis The enumeration 'chasIdMacAddress(4)' represents a chassis
identifier based on the value of a unicast source MAC identifier based on the value of a unicast source MAC
address (encoded in network byte order and IEEE 802.3 address (encoded in network byte order and IEEE 802.3
canonical bit order), of a port on the containing chassis. canonical bit order), of a port on the containing chassis.
The enumeration 'chasIdPtopoGenAddr(5)' represents a chassis The enumeration 'chasIdPtopoGenAddr(5)' represents a chassis
identifier based on a network address, associated with a identifier based on a network address, associated with a
particular chassis. The encoded address is actually particular chassis. The encoded address is actually
composed of two fields. The first field is a single octet, composed of two fields. The first field is a single octet,
representing the IANAAddrFamily for the specific address representing the IANA AddressFamilyNumbers value for the
type, and the second field is the PtopoGenAddr address specific address type, and the second field is the
value." PtopoGenAddr address value."
SYNTAX INTEGER { SYNTAX INTEGER {
chasIdEntPhysicalAlias(1), chasIdEntPhysicalAlias(1),
chasIdIfAlias(2), chasIdIfAlias(2),
chasIdPortEntPhysicalAlias(3), chasIdPortEntPhysicalAlias(3),
chasIdMacAddress(4), chasIdMacAddress(4),
chasIdPtopoGenAddr(5) chasIdPtopoGenAddr(5)
} }
PtopoChassisId ::= TEXTUAL-CONVENTION PtopoChassisId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 15, line 9 skipping to change at page 14, line 26
If the associated PtopoChassisIdType object has a value of If the associated PtopoChassisIdType object has a value of
'chasIdMacAddress(4)', then this string identifies a 'chasIdMacAddress(4)', then this string identifies a
particular unicast source MAC address (encoded in network particular unicast source MAC address (encoded in network
byte order and IEEE 802.3 canonical bit order), of a port on byte order and IEEE 802.3 canonical bit order), of a port on
the containing chassis. the containing chassis.
If the associated PtopoChassisIdType object has a value of If the associated PtopoChassisIdType object has a value of
'chasIdPtopoGenAddr(5)', then this string identifies a 'chasIdPtopoGenAddr(5)', then this string identifies a
particular network address, encoded in network byte order, particular network address, encoded in network byte order,
associated with one or more ports on the containing chassis. associated with one or more ports on the containing chassis.
The first octet contains the IANAAddrFamily enumeration The first octet contains the IANA Address Family Numbers
value for the specific address type, and octets 2 through N enumeration value for the specific address type, and octets
contain the PtopoGenAddr address value in network byte 2 through N contain the PtopoGenAddr address value in
order." network byte order."
SYNTAX OCTET STRING (SIZE (1..32)) SYNTAX OCTET STRING (SIZE (1..32))
PtopoPortIdType ::= TEXTUAL-CONVENTION PtopoPortIdType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes the source of a particular type of port "This TC describes the source of a particular type of port
identifier used in the PTOPO MIB. identifier used in the PTOPO MIB.
The enumeration 'portIdIfAlias(1)' represents a port The enumeration 'portIdIfAlias(1)' represents a port
identifier based on the ifAlias MIB object. identifier based on the ifAlias MIB object.
skipping to change at page 16, line 24 skipping to change at page 15, line 41
object for a port component (i.e., entPhysicalClass value of object for a port component (i.e., entPhysicalClass value of
'port(10)'). 'port(10)').
If the associated PtopoPortIdType object has a value of If the associated PtopoPortIdType object has a value of
'portIdMacAddr(3)', then this string identifies a particular 'portIdMacAddr(3)', then this string identifies a particular
unicast source MAC address associated with the port. unicast source MAC address associated with the port.
If the associated PtopoPortIdType object has a value of If the associated PtopoPortIdType object has a value of
'portIdPtopoGenAddr(4)', then this string identifies a 'portIdPtopoGenAddr(4)', then this string identifies a
network address associated with the port. The first octet network address associated with the port. The first octet
contains the IANAAddrFamily enumeration value for the contains the IANA AddressFamilyNumbers enumeration value for
specific address type, and octets 2 through N contain the the specific address type, and octets 2 through N contain
PtopoGenAddr address value in network byte order." the PtopoGenAddr address value in network byte order."
SYNTAX OCTET STRING (SIZE (1..32)) SYNTAX OCTET STRING (SIZE (1..32))
PtopoAddrSeenState ::= TEXTUAL-CONVENTION PtopoAddrSeenState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This TC describes the state of address detection for a "This TC describes the state of address detection for a
particular type of port identifier used in the PTOPO MIB. particular type of port identifier used in the PTOPO MIB.
The enumeration 'not-used(1)' represents an entry for which The enumeration 'notUsed(1)' represents an entry for which
the particular MIB object is not applicable to the remote the particular MIB object is not applicable to the remote
connection endpoint, connection endpoint,
The enumeration 'unknown(2)' represents an entry for which The enumeration 'unknown(2)' represents an entry for which
the particular address collection state is not known. the particular address collection state is not known.
The enumeration 'one-addr(3)' represents an entry for which The enumeration 'oneAddr(3)' represents an entry for which
exactly one source address (of the type indicated by the exactly one source address (of the type indicated by the
particular MIB object), has been detected. particular MIB object), has been detected.
The enumeration 'multi-addr(4)' represents an entry for The enumeration 'multiAddr(4)' represents an entry for
which more than one source address (of the type indicated by which more than one source address (of the type indicated by
the particular MIB object), has been detected. the particular MIB object), has been detected.
An agent is expected to set the initial state of the An agent is expected to set the initial state of the
PtopoAddrSeenState to 'not-used(1)' or 'unknown(2)'. PtopoAddrSeenState to 'notUsed(1)' or 'unknown(2)'.
Note that the PTOPO MIB does not restrict or specify the Note that the PTOPO MIB does not restrict or specify the
means in which the PtopoAddrSeenState is known to an agent. means in which the PtopoAddrSeenState is known to an agent.
In particular, an agent may detect this information through In particular, an agent may detect this information through
configuration data, or some means other than directly configuration data, or some means other than directly
monitoring all port traffic." monitoring all port traffic."
SYNTAX INTEGER { SYNTAX INTEGER {
not-used(1), notUsed(1),
unknown(2), unknown(2),
one-addr(3), oneAddr(3),
multi-addr(4) multiAddr(4)
} }
-- *********************************************************** -- ***********************************************************
-- --
-- P T O P O D A T A G R O U P -- P T O P O D A T A G R O U P
-- --
-- *********************************************************** -- ***********************************************************
-- Connection Table -- Connection Table
skipping to change at page 18, line 28 skipping to change at page 17, line 45
PtopoConnEntry ::= SEQUENCE { PtopoConnEntry ::= SEQUENCE {
ptopoConnTimeMark TimeFilter, ptopoConnTimeMark TimeFilter,
ptopoConnLocalChassis PhysicalIndex, ptopoConnLocalChassis PhysicalIndex,
ptopoConnLocalPort PhysicalIndex, ptopoConnLocalPort PhysicalIndex,
ptopoConnIndex Integer32, ptopoConnIndex Integer32,
ptopoConnRemoteChassisType PtopoChassisIdType, ptopoConnRemoteChassisType PtopoChassisIdType,
ptopoConnRemoteChassis PtopoChassisId, ptopoConnRemoteChassis PtopoChassisId,
ptopoConnRemotePortType PtopoPortIdType, ptopoConnRemotePortType PtopoPortIdType,
ptopoConnRemotePort PtopoPortId, ptopoConnRemotePort PtopoPortId,
ptopoConnDiscAlgorithm AutonomousType, ptopoConnDiscAlgorithm AutonomousType,
ptopoConnAgentNetAddrType IANAAddrFamily, ptopoConnAgentNetAddrType AddressFamilyNumbers,
ptopoConnAgentNetAddr PtopoGenAddr, ptopoConnAgentNetAddr PtopoGenAddr,
ptopoConnMultiMacSASeen PtopoAddrSeenState, ptopoConnMultiMacSASeen PtopoAddrSeenState,
ptopoConnMultiNetSASeen PtopoAddrSeenState, ptopoConnMultiNetSASeen PtopoAddrSeenState,
ptopoConnIsStatic TruthValue, ptopoConnIsStatic TruthValue,
ptopoConnLastVerifyTime TimeStamp, ptopoConnLastVerifyTime TimeStamp,
ptopoConnRowStatus RowStatus ptopoConnRowStatus RowStatus
} }
ptopoConnTimeMark OBJECT-TYPE ptopoConnTimeMark OBJECT-TYPE
SYNTAX TimeFilter SYNTAX TimeFilter
skipping to change at page 21, line 14 skipping to change at page 20, line 30
A value of ptopoDiscoveryLocal indicates this entry was A value of ptopoDiscoveryLocal indicates this entry was
configured by the local agent, without use of a discovery configured by the local agent, without use of a discovery
protocol. protocol.
A value of { 0 0 } indicates this entry was created manually A value of { 0 0 } indicates this entry was created manually
by an NMS via the associated RowStatus object. " by an NMS via the associated RowStatus object. "
::= { ptopoConnEntry 9 } ::= { ptopoConnEntry 9 }
ptopoConnAgentNetAddrType OBJECT-TYPE ptopoConnAgentNetAddrType OBJECT-TYPE
SYNTAX IANAAddrFamily SYNTAX AddressFamilyNumbers
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This network address type of the associated "This network address type of the associated
ptopoConnNetAddr object, unless that object contains a zero ptopoConnNetAddr object, unless that object contains a zero
length string. In such a case, an NMS application should length string. In such a case, an NMS application should
ignore any returned value for this object. ignore any returned value for this object.
This object may not be modified if the associated This object may not be modified if the associated
ptopoConnRowStatus object has a value of active(1)." ptopoConnRowStatus object has a value of active(1)."
skipping to change at page 22, line 8 skipping to change at page 21, line 26
SYNTAX PtopoAddrSeenState SYNTAX PtopoAddrSeenState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if multiple unicast source MAC "This object indicates if multiple unicast source MAC
addresses have been detected by the agent from the remote addresses have been detected by the agent from the remote
connection endpoint, since the creation of this entry. connection endpoint, since the creation of this entry.
If this entry has an associated ptopoConnRemoteChassisType If this entry has an associated ptopoConnRemoteChassisType
and/or ptopoConnRemotePortType value other than and/or ptopoConnRemotePortType value other than
'portIdMacAddr(3)', then the value 'not-used(1)' is 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned.
returned.
Otherwise, one of the following conditions must be true: Otherwise, one of the following conditions must be true:
If the agent has not yet detected any unicast source MAC If the agent has not yet detected any unicast source MAC
addresses from the remote port, then the value 'unknown(2)' addresses from the remote port, then the value 'unknown(2)'
is returned. is returned.
If the agent has detected exactly one unicast source MAC If the agent has detected exactly one unicast source MAC
address from the remote port, then the value 'one-addr(3)' address from the remote port, then the value 'oneAddr(3)' is
is returned. returned.
If the agent has detected more than one unicast source MAC If the agent has detected more than one unicast source MAC
address from the remote port, then the value 'multi-addr(4)' address from the remote port, then the value 'multiAddr(4)'
is returned." is returned."
::= { ptopoConnEntry 12 } ::= { ptopoConnEntry 12 }
ptopoConnMultiNetSASeen OBJECT-TYPE ptopoConnMultiNetSASeen OBJECT-TYPE
SYNTAX PtopoAddrSeenState SYNTAX PtopoAddrSeenState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if multiple network layer source "This object indicates if multiple network layer source
addresses have been detected by the agent from the remote addresses have been detected by the agent from the remote
connection endpoint, since the creation of this entry. connection endpoint, since the creation of this entry.
If this entry has an associated ptopoConnRemoteChassisType If this entry has an associated ptopoConnRemoteChassisType
or ptopoConnRemotePortType value other than or ptopoConnRemotePortType value other than
'portIdGenAddr(4)' then the value 'not-used(1)' is returned. 'portIdGenAddr(4)' then the value 'notUsed(1)' is returned.
Otherwise, one of the following conditions must be true: Otherwise, one of the following conditions must be true:
If the agent has not yet detected any network source If the agent has not yet detected any network source
addresses of the appropriate type from the remote port, then addresses of the appropriate type from the remote port, then
the value 'unknown(2)' is returned. the value 'unknown(2)' is returned.
If the agent has detected exactly one network source address If the agent has detected exactly one network source address
of the appropriate type from the remote port, then the value of the appropriate type from the remote port, then the value
'one-addr(3)' is returned. 'oneAddr(3)' is returned.
If the agent has detected more than one network source If the agent has detected more than one network source
address (of the same appropriate type) from the remote port, address (of the same appropriate type) from the remote port,
this the value 'multi-addr(4)' is returned." this the value 'multiAddr(4)' is returned."
::= { ptopoConnEntry 13 } ::= { ptopoConnEntry 13 }
ptopoConnIsStatic OBJECT-TYPE ptopoConnIsStatic OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies static ptopoConnEntries. If this "This object identifies static ptopoConnEntries. If this
object has the value 'true(1)', then this entry is not object has the value 'true(1)', then this entry is not
subject to any age-out mechanisms implemented by the agent. subject to any age-out mechanisms implemented by the agent.
skipping to change at page 26, line 46 skipping to change at page 26, line 19
Note that dynamic ptopoConnEntries may also be removed by Note that dynamic ptopoConnEntries may also be removed by
the agent due to the expired timeliness of learned topology the agent due to the expired timeliness of learned topology
information (e.g., timeliness interval for a remote port information (e.g., timeliness interval for a remote port
expires). The actual age-out interval for a given entry is expires). The actual age-out interval for a given entry is
defined by the following formula: defined by the following formula:
age-out-time = age-out-time =
min(ptopoConfigMaxHoldTime, <entry-specific hold-time>) min(ptopoConfigMaxHoldTime, <entry-specific hold-time>)
where <entry-specific hold-time> is determined by the where <entry-specific hold-time> is determined by the
discovery algorithm, and may be different for each entry. discovery algorithm, and may be different for each entry."
DEFVAL { 300 } DEFVAL { 300 }
::= { ptopoConfig 2 } ::= { ptopoConfig 2 }
-- PTOPO MIB Notification Definitions -- PTOPO MIB Notification Definitions
ptopoMIBNotifications OBJECT IDENTIFIER ::= { ptopoMIB 2 } ptopoMIBNotifications OBJECT IDENTIFIER ::= { ptopoMIB 2 }
ptopoMIBTrapPrefix OBJECT IDENTIFIER ::= ptopoMIBTrapPrefix OBJECT IDENTIFIER ::=
{ ptopoMIBNotifications 0 } { ptopoMIBNotifications 0 }
ptopoConfigChange NOTIFICATION-TYPE ptopoConfigChange NOTIFICATION-TYPE
OBJECTS { OBJECTS {
skipping to change at page 31, line 5 skipping to change at page 30, line 26
license or permission for the use of such proprietary rights by license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the implementors or users of this specification can be obtained from the
IETF Secretariat. IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. 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 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.
10. References 10. References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990. 16, RFC 1155, May 1990.
 End of changes. 26 change blocks. 
65 lines changed or deleted 43 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/