1CISCO-IETF-MPLS-ID-STD-03-MIB DEFINITIONS ::= BEGIN 2 3IMPORTS 4 MODULE-IDENTITY, 5 OBJECT-TYPE, 6 NOTIFICATION-TYPE 7 FROM SNMPv2-SMI 8 MODULE-COMPLIANCE, 9 OBJECT-GROUP, 10 NOTIFICATION-GROUP 11 FROM SNMPv2-CONF 12 mplsStdMIB 13 FROM MPLS-TC-STD-MIB 14 CMplsGlobalId, 15 CMplsIccId, 16 CMplsNodeId 17 FROM CISCO-MPLS-TC-EXT-STD-MIB 18 ciscoExperiment 19 FROM CISCO-SMI; 20 21 22cmplsIdStdMIB MODULE-IDENTITY 23 LAST-UPDATED "201206070000Z" 24 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 25 CONTACT-INFO 26 "Venkatesan Mahalingam 27 Dell Inc, 28 350 Holger way, San Jose, CA, USA 29 Email: venkat.mahalingams@gmail.com 30 31 Kannan KV Sampath 32 Aricent, 33 India 34 Email: Kannan.Sampath@aricent.com 35 36 Sam Aldrin 37 Huawei Technologies 38 2330 Central Express Way, 39 Santa Clara, CA 95051, USA 40 Email: aldrin.ietf@gmail.com 41 42 Thomas D. Nadeau 43 Juniper Networks 44 10 Technology Park Drive, Westford, MA 01886 45 Email: tnadeau@juniper.net" 46 DESCRIPTION 47 "Copyright (c) 2012 IETF Trust and the persons identified 48 as the document authors. All rights reserved. 49 50 This MIB module contains generic object definitions for 51 MPLS Traffic Engineering in transport networks. This module is a 52 cisco-ized version of the IETF draft: 53 draft-ietf-mpls-tp-te-mib-03." 54 REVISION "201204080000Z" 55 DESCRIPTION 56 "MPLS identifiers mib object extension" 57 ::= { ciscoExperiment 147 } 58 59 60-- traps 61 62cmplsIdNotifications OBJECT IDENTIFIER 63 ::= { cmplsIdStdMIB 0 } 64 65-- tables, scalars 66 67cmplsIdObjects OBJECT IDENTIFIER 68 ::= { cmplsIdStdMIB 1 } 69 70-- conformance 71 72cmplsIdConformance OBJECT IDENTIFIER 73 ::= { cmplsIdStdMIB 2 } 74 75 76-- MPLS common objects 77 78cmplsGlobalId OBJECT-TYPE 79 SYNTAX CMplsGlobalId 80 MAX-ACCESS read-write 81 STATUS current 82 DESCRIPTION 83 "This object allows the administrator to assign a unique 84 operator identifier also called MPLS-TP Global_ID." 85 REFERENCE "MPLS-TP Identifiers [RFC6370]." 86 ::= { cmplsIdObjects 1 } 87 88cmplsIcc OBJECT-TYPE 89 SYNTAX CMplsIccId 90 MAX-ACCESS read-write 91 STATUS current 92 DESCRIPTION 93 "This object allows the operator or service provider to 94 assign a unique MPLS-TP ITU-T Carrier Code (ICC) to a 95 network." 96 REFERENCE "MPLS-TP Identifiers [RFC6370]." 97 ::= { cmplsIdObjects 2 } 98 99cmplsNodeId OBJECT-TYPE 100 SYNTAX CMplsNodeId 101 MAX-ACCESS read-write 102 STATUS current 103 DESCRIPTION 104 "This object allows the operator or service provider to 105 assign a unique MPLS-TP Node_ID. 106 107 The Node_ID is assigned within the scope of 108 the Global_ID." 109 REFERENCE "MPLS-TP Identifiers [RFC6370]." 110 ::= { cmplsIdObjects 3 } 111-- Module compliance. 112 113cmplsIdGroups OBJECT IDENTIFIER 114 ::= { cmplsIdConformance 1 } 115 116cmplsIdCompliances OBJECT IDENTIFIER 117 ::= { cmplsIdConformance 2 } 118 119 120-- Compliance requirement for fully compliant implementations. 121 122cmplsIdModuleFullCompliance MODULE-COMPLIANCE 123 STATUS current 124 DESCRIPTION 125 "Compliance statement for agents that provide full 126 support the MPLS-ID-STD-MIB module." 127 MODULE -- this module 128 MANDATORY-GROUPS { cmplsIdScalarGroup } 129 ::= { cmplsIdCompliances 1 } 130 131-- Compliance requirement for read-only implementations. 132 133cmplsIdModuleReadOnlyCompliance MODULE-COMPLIANCE 134 STATUS current 135 DESCRIPTION 136 "Compliance statement for agents that provide full 137 support the MPLS-ID-STD-MIB module." 138 MODULE -- this module 139 MANDATORY-GROUPS { cmplsIdScalarGroup } 140 ::= { cmplsIdCompliances 2 } 141 142-- Units of conformance. 143 144cmplsIdScalarGroup OBJECT-GROUP 145 OBJECTS { 146 cmplsGlobalId, 147 cmplsNodeId, 148 cmplsIcc 149 } 150 STATUS current 151 DESCRIPTION 152 "Scalar object needed to implement MPLS TP path." 153 ::= { cmplsIdGroups 1 } 154 155END 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186