PCE Working Group Quinin Zhao
Internet-Draft Dhruv Dhody
Intended status: Informational Udayasree Palle
Expires: January 6, 2011 Huawei Technologies
Daniel King
OldDog Consulting
July 5, 2010
PCE communication protocol(PCEP) Management Information Base for P2MP
draft-zhao-pce-pcep-p2mp-mib-00
Abstract
This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects for
modeling of Path Computation Element communication Protocol (PCEP)
[RFC 5440] for communications between a Path Computation Client (PCC)
and a Path Computation Element (PCE), or between two PCEs in P2MP
scenarios.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 6, 2011.
Zhao & Dhruv Expires January 6, 2011 [Page 1]
Internet-Draft PCE P2MP MIB January, 2011
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This Internet-Draft will expire on January 6, 2011.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 4
4. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4
5. Object definitions . . . . . . . . . . . . . . . . . . . . . . 4
5.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. Objects related to P2MP . . . . . . . . . . . . . . . . . 4
5.3. Objects common for both P2P and P2MP . . . . . . . . . . . 6
5.4. Suggestion for some more objects in [PCE-PCEP-MIB] . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Zhao & Dhruv Expires January 6, 2011 [Page 2]
Internet-Draft PCE P2MP MIB January, 2011
1. Introduction
This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects for
modeling of Path Computation Element communication Protocol (PCEP)
[RFC 5440] for communications between a Path Computation Client (PCC)
and a Path Computation Element (PCE), or between two PCEs in P2MP
scenarios.
This draft is divided into three sections
o Objects related to P2MP
o Objects common for both P2P and P2MP
o Suggestion for some more objects in [PCE-PCEP-MIB]
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119.
2. Terminology
The following terminology is used in this document.
Domain: Any collection of network elements within a common sphere of
address management or path computational responsibility. Examples
of domains include Interior Gateway Protocol (IGP) areas and
Autonomous Systems (ASs).
IGP: Interior Gateway Protocol. Either of the two routing
protocols, Open Shortest Path First (OSPF) or Intermediate System
to Intermediate System (IS-IS).
PCC: Path Computation Client: any client application requesting a
path computation to be performed by a Path Computation Element.
PCE: Path Computation Element. An entity (component, application,
or network node) that is capable of computing a network path or
route based on a network graph and applying computational
constraints.
Zhao & Dhruv Expires January 6, 2011 [Page 3]
Internet-Draft PCE P2MP MIB January, 2011
P2MP: Point-to-Multipoint
P2P: Point-to-Point
3. The Internet-Standard Management Framework
Please refer section 3 of [PCE-PCEP-MIB].
4. PCEP P2MP MIB Module Architecture
The PCEP P2MP MIB is just an extention of the exising
architecture defiend in PCE-PCEP-MIB by adding additional
obejcets which are either common to P2P and P2MP or which are specific
to P2MP. All these new objects are added into the two new
tables (pcePcepExtSessionTable and pcePcepExtClientTable) defined in
this new MIB module. The relationship among the two new tables to the two
existing tables in PCE-PCEP-MIB are shown in the following figure:
pcePcepSessionTable-------->pcePcepExtSessionTable
pcePcepClientTable-------->pcePcepExtClientTable
An arrow in the figure above shows that the MIB table pointed from contains
a reference to the MIB table pointed to.
5. Object definitions
5.1. Objects related to P2MP
Following is the client object, this MUST be added to the
pcePcepExtClientTable created in this MIB module.
pcePcepClientP2mpCapabilityStatus;
Following are the Session objects defined for P2MP , these are added to
the pcePcepExtSessionTable created in this MIB module.
pcePcepSessionP2mpPCReqMessagesSent;
pcePcepSessionP2mpPCRepMessagesSent;
pcePcepSessionP2mpPCReqMessagesReceived;
pcePcepSessionP2mpPCRepMessagesReceived;
pcePcepSessionP2mpAddLeaves;
Zhao & Dhruv Expires January 6, 2011 [Page 4]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionP2mpRemoveLeaves;
pcePcepSessionP2mpModifyLeaves;
pcePcepSessionP2mpUnchangedLeaves
5.2. Objects common for both P2P and P2MP
Following are the client objects defined which are common to both P2P
and P2MP path computation, these are added to the
pcePcepExtClientTable created in this MIB module.
pcePcepClientPathKeysGenerated;
pcePcepClientOverloadStatus;
pcePcepClientOverloadDuration;
Following is the client object defined which is common to both PCC
and PCE client, this MUST be added as pcePcepExtClientObjects 1 to the
pcePcepExtMIBObjects created in this MIB module.
pcePcepClientVersionnumber
Following are the Session objects defined which are common to both
P2P and P2MP path computation, these are added to the
pcePcepExtSessionTable created in this MIB module.
pcePcepSessionTotalMessagesSent;
pcePcepSessionOpenMessagesSent;
pcePcepSessionKeepaliveMessagesSent;
pcePcepSessionPCNtfMessagesSent;
pcePcepSessionPCErrMessagesSent;
pcePcepSessionTotalMessagesReceived;
pcePcepSessionOpenMessagesReceived;
pcePcepSessionKeepaliveMessagesReceived;
pcePcepSessionPCNtfMessagesReceived;
pcePcepSessionPCErrMessagesReceived;
pcePcepSessionIntraDomainRequest;
pcePcepSessionInterDomainRequest;
pcePcepSessionSuccessComps;
Zhao & Dhruv Expires January 6, 2011 [Page 5]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionNoReply;
pcePcepSessionExpandUnknownPathkey;
pcePcepSessionExpandExpiredPathkey;
pcePcepSessionExpandPathkey;
pcePcepSessionPathKeyExpansionSuccess;
pcePcepSessionPathKeyExpansionFailures;
pcePcepSessionSyncronization;
pcePcepSessionReoptimization;
pcePcepSessionFragmentation;
pcePcepSessionP2pPCReqMessagesSent;
pcePcepSessionP2pPCRepMessagesSent;
pcePcepSessionP2pPCReqMessagesReceived;
pcePcepSessionP2pPCRepMessagesReceived;
5.3. PCE PCEP P2MP MIB Definitions
This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2863], [RFC4001],
[RFC4265],[RFC3813], [PCE-PCEP-MIB].
PCE-PCEP-P2MP-DRAFT-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32,
experimental
FROM SNMPv2-SMI
RowStatus, TimeInterval, TruthValue,
TimeStamp, StorageType,TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579]
InetAddressType,
InetAddress,
InetPortNumber
FROM INET-ADDRESS-MIB
Zhao & Dhruv Expires January 6, 2011 [Page 6]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepClientPcepId, pcePcepClientIndex,
pcePcepPeerPcepId, pcePcepPeerEntry
FROM PCE-PCEP-DRAFT-MIB
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF;
pcePcepDraftMIB MODULE-IDENTITY
LAST-UPDATED "201006181200Z" --Jun 18, 2010
ORGANIZATION "Path Computation Element (PCE) Working Group"
CONTACT-INFO "
Dhruv Dhody
Udayasree Palle
Quintin Zhao
Huawei Technology
Daniel King
OldDog Consulting
EMail: dhruvd@huawei.com
EMail: Udayasreepalle@huawei.com
Email: zhao@huawei.com
Email: daniel@oldog.co.uk
Email comments directly to the PCE WG Mailing List at pce@ietf.org
WG-URL: http://www.ietf.org/html.charters/pce-charter.html
"
DESCRIPTION
"This MIB module defines a collection of objects for managing
PCE communication protocol(PCEP)which are common to P2P and P2MP and also
a collection of objects for P2MP."
-- Revision history
REVISION
"201006181200Z" -- 18 Jun 2010 12:00:00 EST
DESCRIPTION
"draft-00 version"
::= { experimental 9999 } --
Zhao & Dhruv Expires January 6, 2011 [Page 7]
Internet-Draft PCE P2MP MIB January, 2011
-- Textual Conventions used in this MIB module --
PcePcepIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d:1d:1d"
STATUS current
DESCRIPTION
"The LDP identifier is a six octet
quantity which is used to identify a
PCE client."
SYNTAX OCTET STRING (SIZE (6))
-- Notifications --
pcePcepExtNotifications OBJECT IDENTIFIER ::= { pcePcepExtDraftMIB 0 }
pcePcepExtMIBObjects OBJECT IDENTIFIER ::= { pcePcepExtDraftMIB 1 }
pcePcepExtConformance OBJECT IDENTIFIER ::= { pcePcepExtDraftMIB 2 }
pcePcepExtClientObjects OBJECT IDENTIFIER ::= { pcePcepExtMIBObjects 1 }
--
-- PCE Extended Client Objects
--
pcePcepClientVersionnumber OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current version number of the PCEP protocol is 1."
::= { pcePcepExtClientObjects 1 }
pcePcepExtClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepClientEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the
PCEP Client."
::= { pcePcepExtClientObjects 2 }
pcePcepExtClientEntry OBJECT-TYPE
SYNTAX PcePcepClientEntry
MAX-ACCESS not-accessible
STATUS current
Zhao & Dhruv Expires January 6, 2011 [Page 8]
Internet-Draft PCE P2MP MIB January, 2011
DESCRIPTION
"An entry in this table represents a PCEP client.
An entry can be created by a network administrator
or by an SNMP agent as instructed by PCEP."
INDEX { pcePcepClientPcepId,
pcePcepClientIndex,
pcePcepPeerPcepId }
::= { pcePcepExtClientTable 1 }
PcePcepExtClientEntry ::= SEQUENCE {
pcePcepClientP2mpCapabilityStatus INTEGER,
pcePcepClientPathKeysGenerated Unsigned32,
pcePcepClientOverloadStatus INTEGER,
pcePcepClientOverloadDuration Unsigned32
}
pcePcepClientP2mpCapabilityStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
enabled(2),
disabled(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The P2MP capability status of this PCEP client.
The value of unknown(1) indicates that the
capability status cannot be determined at
this time. The value of unknown should be
a transient condition before changing
to enabled(2) or disabled(3)."
::= { pcePcepExtClientEntry 1 }
pcePcepClientPathKeysGenerated OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of path-keys generated by this PCE client."
::= { pcePcepExtClientEntry 2 }
Zhao & Dhruv Expires January 6, 2011 [Page 9]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepClientOverloadStatus OBJECT-TYPE
SYNTAX INTEGER {
overloaded(1),
resumed(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Overload status of this PCE client."
::= { pcePcepExtClientEntry 3 }
pcePcepClientOverloadDuration OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The period of time during which no further request should
be sent to the PCE client. Once this period of time has
elapsed, the PCE client should no longer be considered in
a congested state."
::= { pcePcepExtClientEntry 4 }
--
-- The PCEP Sessions Table
--
pcePcepExtSessionTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of Sessions between PCEP clients.
This table AUGMENTS the pcePcepPeerTable.
Each row in this table represents a single session."
::= { pcePcepExtSessionObjects 1 }
pcePcepExtSessionEntry OBJECT-TYPE
SYNTAX PcePcepP2mpSessionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents information on a
single session between two PCEP clients.
The information contained in a row is read-only."
AUGMENTS { pcePcepPeerEntry }
::= { pcePcepExtSessionTable 1 }
Zhao & Dhruv Expires January 6, 2011 [Page 10]
Internet-Draft PCE P2MP MIB January, 2011
PcePcepExtSessionEntry ::= SEQUENCE {
pcePcepSessionP2mpPCReqMessagesSent Unsigned32,
pcePcepSessionP2mpPCRepMessagesSent Unsigned32,
pcePcepSessionP2mpPCReqMessagesReceived Unsigned32,
pcePcepSessionP2mpPCRepMessagesReceived Unsigned32,
pcePcepSessionP2mpAddLeaves Unsigned32,
pcePcepSessionP2mpRemoveLeaves Unsigned32,
pcePcepSessionP2mpModifyLeaves Unsigned32,
pcePcepSessionP2mpUnchangedLeaves Unsigned32,
pcePcepSessionTotalMessagesSent Unsigned32,
pcePcepSessionOpenMessagesSent Unsigned32,
pcePcepSessionKeepaliveMessagesSent Unsigned32,
pcePcepSessionPCNtfMessagesSent Unsigned32,
pcePcepSessionPCErrMessagesSent Unsigned32,
pcePcepSessionTotalMessagesReceived Unsigned32,
pcePcepSessionOpenMessagesReceived Unsigned32,
pcePcepSessionKeepaliveMessagesReceived Unsigned32,
pcePcepSessionPCNtfMessagesReceived Unsigned32,
pcePcepSessionPCErrMessagesReceived Unsigned32,
pcePcepSessionIntraDomainRequest Unsigned32,
pcePcepSessionInterDomainRequest Unsigned32,
pcePcepSessionSuccessComps Unsigned32,
pcePcepSessionNoReply Unsigned32,
pcePcepSessionExpandUnknownPathkey Unsigned32,
pcePcepSessionExpandExpiredPathkey Unsigned32,
pcePcepSessionExpandPathkey Unsigned32,
pcePcepSessionPathKeyExpansionSuccess Unsigned32,
pcePcepSessionPathKeyExpansionFailures Unsigned32,
pcePcepSessionSyncronization Unsigned32,
pcePcepSessionReoptimization Unsigned32,
pcePcepSessionFragmentation Unsigned32,
pcePcepSessionP2pPCReqMessagesSent Unsigned32,
pcePcepSessionP2pPCRepMessagesSent Unsigned32,
pcePcepSessionP2pPCReqMessagesReceived Unsigned32,
pcePcepSessionP2pPCRepMessagesReceived Unsigned32
}
pcePcepSessionFailedComps OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests which had failed
computations."
::= { pcePcepExtSessionEntry 1 }
Zhao & Dhruv Expires January 6, 2011 [Page 11]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionP2mpPCReqMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2MP Request messages sent on this
session."
::= { pcePcepExtSessionEntry 2 }
pcePcepSessionP2mpPCRepMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2MP Reply messages sent on this session."
::= { pcePcepExtSessionEntry 3 }
pcePcepSessionP2mpPCReqMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2MP Request messages received on this
session."
::= { pcePcepExtSessionEntry 4 }
pcePcepSessionP2mpPCRepMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2MP Reply messages received on this
session."
::= { pcePcepExtSessionEntry 5 }
pcePcepSessionP2mpAddLeaves OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of leaves to be Added(Type1) for the
total P2MP requests."
::= { pcePcepExtSessionEntry 6 }
Zhao & Dhruv Expires January 6, 2011 [Page 12]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionP2mpRemoveLeaves OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of leaves to be Removed(Type2) for the
total P2MP requests."
::= { pcePcepExtSessionEntry 7 }
pcePcepSessionP2mpModifyLeaves OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of leaves to be Modified(Type3) for
the total P2MP requests."
::= { pcePcepExtSessionEntry 8 }
pcePcepSessionP2mpUnchangedLeaves OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of leaves not to be changed(Type4) for
the total P2MP requests."
::= { pcePcepExtSessionEntry 9 }
pcePcepSessionTotalMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of PCEP messages sent on this session."
::= { pcePcepExtSessionEntry 10 }
pcePcepSessionOpenMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Open messages sent on this session."
::= { pcePcepExtSessionEntry 11 }
pcePcepSessionKeepaliveMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Keepalive messages sent on this session."
::= { pcePcepExtSessionEntry 12 }
Zhao & Dhruv Expires January 6, 2011 [Page 13]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionPCNtfMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCNtf messages sent on this session."
::= { pcePcepExtSessionEntry 13 }
pcePcepSessionPCErrMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCErr messages sent on this session."
::= { pcePcepExtSessionEntry 14 }
pcePcepSessionTotalMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of PCEP messages received on this
session."
::= { pcePcepExtSessionEntry 15 }
pcePcepSessionOpenMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Open messages received on this
session."
::= { pcePcepExtSessionEntry 16 }
pcePcepSessionKeepaliveMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Keepalive messages received on this
session."
::= { pcePcepExtSessionEntry 17 }
pcePcepSessionPCNtfMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCNtf messages received on this
session."
::= { pcePcepExtSessionEntry 18 }
Zhao & Dhruv Expires January 6, 2011 [Page 14]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionPCErrMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCErr messages received on this
session."
::= { pcePcepExtSessionEntry 19 }
pcePcepSessionIntraDomainRequest OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests sent for the Intra-Domain
path computation."
::= { pcePcepExtSessionEntry 20 }
pcePcepSessionInterDomainRequest OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests sent for the Inter-Domain path
computation."
::= { pcePcepExtSessionEntry 21 }
pcePcepSessionSuccessComps OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests which had successful
computations.In case of PCC-PCE session, it is core
computation value and in case of PCE-PCE session, it
is transit computation value."
::= { pcePcepExtSessionEntry 22 }
pcePcepSessionNoReply OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" The number of requests which had not been replied
either success or failure."
::= { pcePcepExtSessionEntry 23 }
Zhao & Dhruv Expires January 6, 2011 [Page 15]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionExpandUnknownPathkey OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of attempts to expand an unknown path-key."
::= { pcePcepExtSessionEntry 24 }
pcePcepSessionExpandExpiredPathkey OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of attempts to expand an expired path-key."
::= { pcePcepExtSessionEntry 25 }
pcePcepSessionExpandPathkey OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of attempts to expand the same path-key."
::= { pcePcepExtSessionEntry 26 }
pcePcepSessionPathKeyExpansionSuccess OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of path-key expansion requests which
had successful computations."
::= { pcePcepExtSessionEntry 27 }
pcePcepSessionPathKeyExpansionFailures OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of path-key expansion requests which
had failed computations."
::= { pcePcepExtSessionEntry 28 }
pcePcepSessionSyncronization OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of synchronized path computation requests
that can be either dependent or independent."
::= { pcePcepExtSessionEntry 29 }
Zhao & Dhruv Expires January 6, 2011 [Page 16]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionReoptimization OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests for Reoptimization."
::= { pcePcepExtSessionEntry 30 }
pcePcepSessionFragmentation OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets of a PCReq / PCRep
message which had been fragmented."
::= { pcePcepExtSessionEntry 31 }
pcePcepSessionP2pPCReqMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2P Request messages sent on this
session."
::= { pcePcepExtSessionEntry 32 }
pcePcepSessionP2pPCRepMessagesSent OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2P Reply messages sent on this session."
::= { pcePcepExtSessionEntry 33 }
pcePcepSessionP2pPCReqMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2P PCReq messages received on this
session."
::= { pcePcepExtSessionEntry 34}
pcePcepSessionP2pPCRepMessagesReceived OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of P2P PCRep messages received on this
session."
::= { pcePcepExtSessionEntry 35 }
Zhao & Dhruv Expires January 6, 2011 [Page 17]
Internet-Draft PCE P2MP MIB January, 2011
--****************************************************************
-- Module Conformance Statement
--****************************************************************
pcePcepExtGroups
OBJECT IDENTIFIER ::= { pcePcepExtConformance 1 }
pcePcepExtCompliances
OBJECT IDENTIFIER ::= { pcePcepExtConformance 2 }
--
-- Full Compliance
--
pcePcepExtModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support
for read-create and read-write. In other
words, both monitoring and configuration
are available when using this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS { pcePcepExtGeneralGroup,
pcePcepExtNotificationsGroup
}
::= { pcePcepExtCompliances 1 }
--
-- Read-Only Compliance
--
pcePcepExtModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support
for read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS { pcePcepExtGeneralGroup,
pcePcepExtNotificationsGroup
}
Zhao & Dhruv Expires January 6, 2011 [Page 18]
Internet-Draft PCE P2MP MIB January, 2011
::= { pcePcepExtCompliances 2 }
-- units of conformance
pcePcepExtGeneralGroup OBJECT-GROUP
OBJECTS {
pcePcepClientVersionnumber,
pcePcepClientP2mpCapabilityStatus,
pcePcepClientPathKeysGenerated,
pcePcepClientOverloadStatus,
pcePcepClientOverloadDuration,
pcePcepSessionP2mpPCReqMessagesSent,
pcePcepSessionP2mpPCRepMessagesSent,
pcePcepSessionP2mpPCReqMessagesReceived,
pcePcepSessionP2mpPCRepMessagesReceived,
pcePcepSessionP2mpAddLeaves,
pcePcepSessionP2mpRemoveLeaves,
pcePcepSessionP2mpModifyLeaves,
pcePcepSessionP2mpUnchangedLeaves,
pcePcepSessionTotalMessagesSent,
pcePcepSessionOpenMessagesSent,
pcePcepSessionKeepaliveMessagesSent,
pcePcepSessionPCNtfMessagesSent,
pcePcepSessionPCErrMessagesSent,
pcePcepSessionOpenMessagesReceived,
pcePcepSessionKeepaliveMessagesReceived,
pcePcepSessionPCNtfMessagesReceived,
pcePcepSessionPCErrMessagesReceived,
pcePcepSessionIntraDomainRequest,
pcePcepSessionInterDomainRequest,
pcePcepSessionSuccessComps,
pcePcepSessionNoReply,
pcePcepSessionExpandUnknownPathkey,
pcePcepSessionExpandExpiredPathkey,
pcePcepSessionExpandPathkey,
pcePcepSessionPathKeyExpansionSuccess,
pcePcepSessionPathKeyExpansionFailures,
pcePcepSessionSyncronization,
pcePcepSessionReoptimization,
pcePcepSessionFragmentation,
pcePcepSessionP2pPCReqMessagesSent,
pcePcepSessionP2pPCRepMessagesSent,
Zhao & Dhruv Expires January 6, 2011 [Page 19]
Internet-Draft PCE P2MP MIB January, 2011
pcePcepSessionP2pPCReqMessagesReceived,
pcePcepSessionP2pPCRepMessagesReceived,
pcePcepSessionTotalMessagesReceived
}
STATUS current
DESCRIPTION
"Objects that apply to all PCEP MIB implementations."
::= { pcePcepExtGroups 1 }
END
6. IANA Considerations
Please refer section 8 of [PCE-PCEP-MIB]
7. Security Considerations
Please refer section 7 of [PCE-PCEP-MIB]
8. References
8.1. Normative References
8.2. Informative References
[RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "MPLS
Multiprotocol Label Switching (MPLS) Label Switch Router
Management Information Base ", RFC 3813, June 2004
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual
Conventions for Virtual Private Network (VPN)
Management", RFC 4265, November 2005.
[PCE-PCEP-MIB] Kiran Koushik, A S., Stephan, E., Zhao, Q., and D.
King, "PCE communication protocol(PCEP) Management
Information Base", March 2010.
[RFC 5440] Ayyangar, A ., Farrel, A ., Oki, E., Atlas, A.,
Dolganow, A., Ikejiri, Y., Kumaki, K., Vasseur, J.,
and J. Roux, "Path Computation Element (PCE)
communication Protocol (PCEP)", March 2009.
Authors' Addresses
Quintin Zhao
Huawei Technology
125 Nagog Technology Park
Acton, MA 01719
US
Email: qzhao@huawei.com
Dhruv Dhody
Huawei Technologies India Pvt Ltd
Leela Palace
Bangalore, Karnataka 560008
INDIA
EMail: dhruvd@huawei.com
Udayasree Palle
Huawei Technologies India Pvt Ltd
Leela Palace
Bangalore, Karnataka 560008
INDIA
EMail: Udayasreepalle@huawei.com
Daniel King
Old Dog Consulting
UK
Email: daniel@olddog.co.uk