1MPLS-LC-ATM-STD-MIB DEFINITIONS ::= BEGIN 2IMPORTS 3 MODULE-IDENTITY, OBJECT-TYPE 4 FROM SNMPv2-SMI 5 MODULE-COMPLIANCE, OBJECT-GROUP 6 FROM SNMPv2-CONF 7 RowStatus, StorageType, TruthValue 8 FROM SNMPv2-TC 9 AtmVpIdentifier 10 FROM ATM-TC-MIB 11 mplsStdMIB, MplsAtmVcIdentifier 12 FROM MPLS-TC-STD-MIB 13 mplsInterfaceIndex 14 FROM MPLS-LSR-STD-MIB 15 ; 16 17mplsLcAtmStdMIB MODULE-IDENTITY 18 LAST-UPDATED "200601120000Z" -- 12 January 2006 19 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 20 CONTACT-INFO 21 " Thomas D. Nadeau 22 Postal: Cisco Systems, Inc. 23 250 Apollo Drive 24 Chelmsford, MA 01824 25 Tel: +1-978-244-3051 26 Email: tnadeau@cisco.com 27 28 Subrahmanya Hegde 29 Postal: Cisco Systems, Inc. 30 225 East Tazman Drive 31 Tel: +1-408-525-6562 32 Email: subrah@cisco.com 33 General comments should be sent to mpls@uu.net 34 " 35 DESCRIPTION 36 "This MIB module contains managed object definitions for 37 MPLS Label-Controlled ATM interfaces as defined in 38 [RFC3035]. 39 40 Copyright (C) The Internet Society (2006). This 41 version of this MIB module is part of RFC 4368; see 42 the RFC itself for full legal notices." 43 44 -- Revision history. 45 REVISION 46 "200601120000Z" -- 12 January 2006 47 DESCRIPTION 48 "Initial revision, published as part of RFC 4368." 49 ::= { mplsStdMIB 9 } 50 51-- Top level components of this MIB module. 52 53-- Tables, Scalars, Notifications, Conformance 54 55mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 } 56 57mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 } 58 59mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 } 60 61-- MPLS LC-ATM Interface Configuration Table. 62mplsLcAtmStdInterfaceConfTable OBJECT-TYPE 63 SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry 64 MAX-ACCESS not-accessible 65 STATUS current 66 DESCRIPTION 67 "This table specifies per-interface MPLS LC-ATM 68 capability and associated information. In particular, 69 this table sparsely extends the MPLS-LSR-STD-MIB's 70 mplsInterfaceConfTable." 71 ::= { mplsLcAtmStdObjects 1 } 72 73mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE 74 SYNTAX MplsLcAtmStdInterfaceConfEntry 75 MAX-ACCESS not-accessible 76 STATUS current 77 DESCRIPTION 78 "An entry in this table is created by an LSR for 79 every interface capable of supporting MPLS LC-ATM. 80 Each entry in this table will exist only if a 81 corresponding entry in ifTable and mplsInterfaceConfTable 82 exists. If the associated entries in ifTable and 83 mplsInterfaceConfTable are deleted, the corresponding 84 entry in this table must also be deleted shortly 85 thereafter." 86 INDEX { mplsInterfaceIndex } 87 ::= { mplsLcAtmStdInterfaceConfTable 1 } 88 89MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { 90 mplsLcAtmStdCtrlVpi AtmVpIdentifier, 91 mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, 92 mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, 93 mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier, 94 mplsLcAtmStdVcMerge TruthValue, 95 mplsLcAtmVcDirectlyConnected TruthValue, 96 mplsLcAtmLcAtmVPI AtmVpIdentifier, 97 mplsLcAtmStdIfConfRowStatus RowStatus, 98 mplsLcAtmStdIfConfStorageType StorageType 99} 100 101mplsLcAtmStdCtrlVpi OBJECT-TYPE 102 SYNTAX AtmVpIdentifier 103 MAX-ACCESS read-create 104 STATUS current 105 DESCRIPTION 106 "This is the VPI value over which this 107 LSR is willing to accept control traffic on 108 this interface." 109 ::= { mplsLcAtmStdInterfaceConfEntry 1 } 110 111mplsLcAtmStdCtrlVci OBJECT-TYPE 112 SYNTAX MplsAtmVcIdentifier 113 MAX-ACCESS read-create 114 STATUS current 115 DESCRIPTION 116 "This is the VCI value over which this 117 LSR is willing to accept control traffic 118 on this interface." 119 ::= { mplsLcAtmStdInterfaceConfEntry 2 } 120 121mplsLcAtmStdUnlabTrafVpi OBJECT-TYPE 122 SYNTAX AtmVpIdentifier 123 MAX-ACCESS read-create 124 STATUS current 125 DESCRIPTION 126 "This is the VPI value over which this 127 LSR is willing to accept unlabeled traffic 128 on this interface." 129 ::= { mplsLcAtmStdInterfaceConfEntry 3 } 130 131mplsLcAtmStdUnlabTrafVci OBJECT-TYPE 132 SYNTAX MplsAtmVcIdentifier 133 MAX-ACCESS read-create 134 STATUS current 135 DESCRIPTION 136 "This is the VCI value over which this 137 LSR is willing to accept unlabeled traffic 138 on this interface." 139 ::= { mplsLcAtmStdInterfaceConfEntry 4 } 140 141mplsLcAtmStdVcMerge OBJECT-TYPE 142 SYNTAX TruthValue 143 MAX-ACCESS read-create 144 STATUS current 145 DESCRIPTION 146 "If set to true(1), indicates that this interface 147 is capable of ATM VC merge; otherwise, it MUST 148 be set to false(2)." 149 DEFVAL { false } 150 ::= { mplsLcAtmStdInterfaceConfEntry 5 } 151 152mplsLcAtmVcDirectlyConnected OBJECT-TYPE 153 SYNTAX TruthValue 154 MAX-ACCESS read-create 155 STATUS current 156 DESCRIPTION 157 "This value indicates whether an LC-ATM is directly 158 or indirectly (by means of a VP) connected. If set to 159 true(1), indicates that this interface is directly 160 connected LC-ATM; otherwise, it MUST be set to 161 false(2). Note that although it can be intimated 162 from RFC 3057 that multiple VPs may be used, 163 in practice only a single one is used, and therefore 164 the authors of this MIB module have chosen to model 165 it as such." 166 DEFVAL { true } 167 ::= { mplsLcAtmStdInterfaceConfEntry 6 } 168 169mplsLcAtmLcAtmVPI OBJECT-TYPE 170 SYNTAX AtmVpIdentifier 171 MAX-ACCESS read-create 172 STATUS current 173 DESCRIPTION 174 "This is the VPI value used for indirectly 175 connected LC-ATM interfaces. For these 176 interfaces, the VPI field is not 177 available to MPLS, and the label MUST be 178 encoded entirely within the VCI field 179 (see [RFC3035]). If the interface is directly 180 connected, this value MUST be set to zero." 181 DEFVAL { 0 } 182 ::= { mplsLcAtmStdInterfaceConfEntry 7 } 183 184mplsLcAtmStdIfConfRowStatus OBJECT-TYPE 185 SYNTAX RowStatus 186 MAX-ACCESS read-create 187 STATUS current 188 DESCRIPTION 189 "This object is used to create and 190 delete entries in this table. When configuring 191 entries in this table, the corresponding 192 ifEntry and mplsInterfaceConfEntry 193 MUST exist beforehand. If a manager attempts to 194 create an entry for a corresponding 195 mplsInterfaceConfEntry that does not support LC-ATM, 196 the agent MUST return an inconsistentValue error. 197 If this table is implemented read-only, then the 198 agent must set this object to active(1) when this 199 row is made active. If this table is implemented 200 writable, then an agent MUST not allow modification 201 to its objects once this value is set to active(1), 202 except to mplsLcAtmStdIfConfRowStatus and 203 mplsLcAtmStdIfConfStorageType." 204 ::= { mplsLcAtmStdInterfaceConfEntry 8 } 205 206 mplsLcAtmStdIfConfStorageType OBJECT-TYPE 207 SYNTAX StorageType 208 MAX-ACCESS read-create 209 STATUS current 210 DESCRIPTION 211 "The storage type for this conceptual row. 212 Conceptual rows having the value 'permanent(4)' 213 need not allow write-access to any columnar 214 objects in the row." 215 DEFVAL { nonVolatile } 216 ::= { mplsLcAtmStdInterfaceConfEntry 9 } 217 218-- End of mplsLcAtmStdInterfaceConfTable 219 220-- Module compliance. 221 222mplsLcAtmStdCompliances 223 OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 } 224 225mplsLcAtmStdGroups 226 OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 } 227 228-- Compliance requirement for full compliance 229 230mplsLcAtmStdModuleFullCompliance MODULE-COMPLIANCE 231 STATUS current 232 DESCRIPTION 233 "Compliance statement for agents that provide 234 full support for MPLS-LC-ATM-STD-MIB. Such 235 devices can be monitored and also be configured 236 using this MIB module." 237 238 MODULE -- this module 239 MANDATORY-GROUPS { 240 mplsLcAtmStdIfGroup 241 } 242 243 OBJECT mplsLcAtmStdIfConfRowStatus 244 SYNTAX RowStatus { active(1), notInService(2) } 245 WRITE-SYNTAX RowStatus { active(1), notInService(2), 246 createAndGo(4), destroy(6) 247 } 248 DESCRIPTION "Support for createAndWait and notReady is 249 not required." 250 ::= { mplsLcAtmStdCompliances 1 } 251 252-- Compliance requirement for read-only implementations. 253 254mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE 255 STATUS current 256 DESCRIPTION 257 "Compliance requirement for implementations that only 258 provide read-only support for MPLS-LC-ATM-STD-MIB. 259 Such devices can be monitored but cannot be configured 260 using this MIB module. 261 " 262 MODULE -- this module 263 MANDATORY-GROUPS { 264 mplsLcAtmStdIfGroup 265 } 266 267 -- mplsLcAtmStdInterfaceConfTable 268 269 OBJECT mplsLcAtmStdCtrlVpi 270 MIN-ACCESS read-only 271 DESCRIPTION 272 "Write access is not required." 273 274 OBJECT mplsLcAtmStdCtrlVci 275 MIN-ACCESS read-only 276 DESCRIPTION 277 "Write access is not required." 278 279 OBJECT mplsLcAtmStdUnlabTrafVpi 280 MIN-ACCESS read-only 281 DESCRIPTION 282 "Write access is not required." 283 284 OBJECT mplsLcAtmStdUnlabTrafVci 285 MIN-ACCESS read-only 286 DESCRIPTION 287 "Write access is not required." 288 289 OBJECT mplsLcAtmStdVcMerge 290 MIN-ACCESS read-only 291 DESCRIPTION 292 "Write access is not required." 293 294 OBJECT mplsLcAtmStdIfConfRowStatus 295 SYNTAX RowStatus { active(1) } 296 MIN-ACCESS read-only 297 DESCRIPTION "Write access is not required." 298 299 OBJECT mplsLcAtmVcDirectlyConnected 300 MIN-ACCESS read-only 301 DESCRIPTION 302 "Write access is not required." 303 304 OBJECT mplsLcAtmLcAtmVPI 305 MIN-ACCESS read-only 306 DESCRIPTION 307 "Write access is not required." 308 309 OBJECT mplsLcAtmStdIfConfStorageType 310 MIN-ACCESS read-only 311 DESCRIPTION 312 "Write access is not required." 313 ::= { mplsLcAtmStdCompliances 2 } 314 315-- Units of conformance. 316 317mplsLcAtmStdIfGroup OBJECT-GROUP 318 OBJECTS { 319 mplsLcAtmStdCtrlVpi, 320 mplsLcAtmStdCtrlVci, 321 mplsLcAtmStdUnlabTrafVpi, 322 mplsLcAtmStdUnlabTrafVci, 323 mplsLcAtmStdVcMerge, 324 mplsLcAtmVcDirectlyConnected, 325 mplsLcAtmLcAtmVPI, 326 mplsLcAtmStdIfConfRowStatus, 327 mplsLcAtmStdIfConfStorageType 328 } 329 STATUS current 330 DESCRIPTION 331 "Collection of objects needed for MPLS LC-ATM 332 333 interface configuration." 334 ::= { mplsLcAtmStdGroups 1 } 335 336END 337