1 2-------------------------------------------------------------------- 3-- OAM MIB Definition File 4-- 5-- Dec 1995, rbhide 6-- 7-- Copyright (c) 1996, 2003, 2006 by cisco Systems, Inc. 8-- All rights reserved. 9-------------------------------------------------------------------- 10-- 11 12CISCO-OAM-MIB DEFINITIONS ::= BEGIN 13 14IMPORTS 15 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 16 Unsigned32, 17 Counter32, Integer32 FROM SNMPv2-SMI 18 TimeStamp, TEXTUAL-CONVENTION, 19 TruthValue, RowStatus FROM SNMPv2-TC 20 ifIndex FROM IF-MIB 21 OwnerString FROM RMON-MIB 22 ciscoExperiment FROM CISCO-SMI 23 NOTIFICATION-GROUP, 24 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 25 26ciscoOamPingMIB MODULE-IDENTITY 27 LAST-UPDATED "200602170000Z" 28 ORGANIZATION "Cisco Systems, Inc." 29 CONTACT-INFO 30 " Cisco Systems 31 Customer Service 32 33 Postal: 170 W Tasman Drive 34 San Jose, CA 95134 35 USA 36 37 Tel: +1 800 553-NETS 38 39 E-mail: cs-atm@cisco.com" 40 DESCRIPTION 41 "A MIB module for invoking OAM loopback Ping on ATM 42 connections." 43 44 REVISION "200602170000Z" 45 DESCRIPTION 46 "Removed the OwnerString TEXTUAL-CONVENTION and 47 imported the same from RMON-MIB." 48 REVISION "200306270000Z" 49 DESCRIPTION 50 "Add object to oamLoopbackPingTable: 51 - oamLoopbackPingMinRttuSec, 52 - oamLoopbackPingAvgRttuSec, 53 - oamLoopbackPingMaxRttuSec." 54 55 REVISION "200304040000Z" 56 DESCRIPTION 57 "Add objects to oamLoopbackPingTable: 58 - oamLoopbackPingExecTime, 59 - oamLoopbackPingDir, 60 - oamLoopbackPingOperStatus 61 62 Add new table oamLoopbackSegEndPointTable for OAM segment 63 endpoint provisioning. 64 65 Usage of oamLoopbackSegEndPointTable: 66 If the loopback ping test type (oamLoopbackPingType) is 67 'segment', the test requires the endpoint under test 68 and the remote ping endpoint are both OAM segment 69 loopback endpoints. 70 71 The table oamLoopbackSegEndPointTable is used to 72 provision an ATM connection endpoint to be an OAM 73 segment endpoint. 74 75 If the endpoints are already OAM segment endpoints, the 76 provisioning of the table is not required." 77 78 REVISION "9605010000Z" 79 DESCRIPTION "Initial version of the MIB." 80 81 ::= { ciscoExperiment 15 } 82 83 84ciscoOamPingMIBObjects OBJECT IDENTIFIER ::= { ciscoOamPingMIB 1 } 85 86 87-- 88-- The OAM Loopback Group 89-- 90 91CiscoOAMPingDir ::= TEXTUAL-CONVENTION 92 STATUS current 93 DESCRIPTION 94 "Direction in which the OAM segment cells are sent: 95 forward : send OAM loopback cells in the 96 direction form the originator towards the 97 destination of the connection. 98 backward : send OAM loopback cells in the direction 99 towards the originator of the connection." 100 SYNTAX INTEGER { 101 forward(1), 102 backward(2) 103 } 104 105CiscoOAMPingStatus ::= TEXTUAL-CONVENTION 106 STATUS current 107 DESCRIPTION 108 "Defines possible test status. 109 success(1) - The test has completed. 110 111 timeOut(2) - The test has been failed because 112 the test does not receive loopback 113 cell response from remote endpoint 114 and it times out. 115 116 resourceNotAvailable(3) - The resources required by the 117 test is not available, such as other 118 application is testing on the same 119 endpoint. 120 121 aborted(4) - The test is aborted due to the removal 122 of connection endpoint or failed to 123 proceed. 124 125 inProgress(5) - The endpoint is still in progress of 126 testing and waiting for the response. 127 128 noResponseData(6) - If the test receives response from 129 the remote end but without any data. 130 131 failToStart(7) - The test fails to kickoff (internal 132 messaging timeout)." 133 SYNTAX INTEGER { 134 success(1), 135 timeOut(2), 136 resourceNotAvailable(3), 137 aborted(4), 138 inProgress(5), 139 noResponseData(6), 140 failToStart(7) 141 } 142 143oamLoopbackPingTable OBJECT-TYPE 144 SYNTAX SEQUENCE OF OamLoopbackPingEntry 145 MAX-ACCESS not-accessible 146 STATUS current 147 DESCRIPTION 148 "A table of OAM loopback request entries. (This table 149 is similar to the CISCO-PING-MIB.)" 150 ::= { ciscoOamPingMIBObjects 1 } 151 152oamLoopbackPingEntry OBJECT-TYPE 153 SYNTAX OamLoopbackPingEntry 154 MAX-ACCESS not-accessible 155 STATUS current 156 DESCRIPTION 157 "A OAM loopback request entry. 158 159 A management station wishing to create an entry should 160 first generate a pseudo-random serial number to be used 161 as the index to this sparse table. The NMS should 162 then create the associated instance of the row status 163 and row owner objects. It must also, either in the same 164 or in successive PDUs, create the associated instances 165 specifying the VPI and VCI values. It should also modify 166 the default values for the other configuration objects 167 if the defaults are not appropriate. 168 169 Once the appropriate instance of all the configuration 170 objects have been created, either by an explicit SNMP 171 set request or by default, the row status should be set 172 to active to initiate the request. Note that this entire 173 procedure may be initiated via a single set request which 174 specifies a row status of createAndGo as well as specifies 175 valid values for the non-defaulted configuration objects. 176 177 Once the OAM sequence has been activated, it cannot be 178 stopped -- it will run until the configured number of 179 cells have been sent. 180 181 Once the sequence completes, the management station should 182 retrieve the values of the status objects of interest, and 183 should then delete the entry. In order to prevent old 184 entries from clogging the table, entries will be aged out, 185 but an entry will never be deleted within 5 minutes of 186 completing." 187 INDEX { oamLoopbackPingSerialNumber } 188 ::= { oamLoopbackPingTable 1 } 189 190OamLoopbackPingEntry ::= 191 SEQUENCE { 192 -- index 193 oamLoopbackPingSerialNumber INTEGER, 194 -- configuration items 195 oamLoopbackPingInterface Integer32, 196 oamLoopbackPingVpi INTEGER, 197 oamLoopbackPingVci INTEGER, 198 oamLoopbackPingType INTEGER, 199 oamLoopbackPingLocation OCTET STRING, 200 oamLoopbackPingLocationFlag INTEGER, 201 oamLoopbackPingCount INTEGER, 202 oamLoopbackPingTimeout INTEGER, 203 oamLoopbackPingDelay INTEGER, 204 oamLoopbackPingTrapOnCompletion TruthValue, 205 -- status items 206 oamLoopbackPingSentCells Counter32, 207 oamLoopbackPingReceivedCells Counter32, 208 oamLoopbackPingMinRtt Integer32, 209 oamLoopbackPingAvgRtt Integer32, 210 oamLoopbackPingMaxRtt Integer32, 211 oamLoopbackPingCompleted TruthValue, 212 oamLoopbackPingEntryOwner OwnerString, 213 oamLoopbackPingEntryStatus RowStatus, 214 --- 215 oamLoopbackPingDir CiscoOAMPingDir, 216 oamLoopbackPingOperStatus CiscoOAMPingStatus, 217 oamLoopbackPingExecTime TimeStamp, 218 oamLoopbackPingMinRttuSec Integer32, 219 oamLoopbackPingAvgRttuSec Integer32, 220 oamLoopbackPingMaxRttuSec Integer32 221 } 222 223oamLoopbackPingSerialNumber OBJECT-TYPE 224 SYNTAX INTEGER (1..2147483647) 225 MAX-ACCESS not-accessible 226 STATUS current 227 DESCRIPTION 228 "Object which identifies a unique entry in the 229 oamLoopbackPingTable. A management station wishing 230 to initiate a OAM-loopback operation should use a 231 pseudo-random value for this object when creating 232 or modifying an instance of an oamLoopbackPingEntry. 233 The RowStatus semantics of the oamLoopbackPingEntryStatus 234 object will prevent access conflicts." 235 ::= { oamLoopbackPingEntry 1 } 236 237oamLoopbackPingInterface OBJECT-TYPE 238 SYNTAX Integer32 (1..2147483647) 239 MAX-ACCESS read-create 240 STATUS current 241 DESCRIPTION 242 "The interface of the connection on which OAM loopbacks are 243 to be sent. Once an instance of this object is created, its 244 value can not be changed. The value specified for this object 245 must equate to a value of ifIndex in the ifTable." 246 ::= { oamLoopbackPingEntry 2 } 247 248oamLoopbackPingVpi OBJECT-TYPE 249 SYNTAX INTEGER (0..4095) 250 MAX-ACCESS read-create 251 STATUS current 252 DESCRIPTION 253 "The VPI of the connection on which OAM loopbacks are 254 to be sent. 255 Once an instance of this object is created, its 256 value can not be changed." 257 ::= { oamLoopbackPingEntry 3 } 258 259oamLoopbackPingVci OBJECT-TYPE 260 SYNTAX INTEGER (-1..65535) 261 MAX-ACCESS read-create 262 STATUS current 263 DESCRIPTION 264 "Either -1 or the VCI of the connection on which F5 OAM 265 loopback cells are to be sent. 266 If the value of this object is -1, then an F4 OAM loopback 267 cells will be sent on the VPC indicated by oamLoopbackPingVpi. 268 An instance of this object cannot be created until the 269 associated instance of oamLoopbackPingVpi is created. 270 Once an instance of this object is created, its 271 value can not be changed." 272 ::= { oamLoopbackPingEntry 4 } 273 274oamLoopbackPingType OBJECT-TYPE 275 SYNTAX INTEGER { segment(1), end2end(2) } 276 MAX-ACCESS read-create 277 STATUS current 278 DESCRIPTION 279 "The type of OAM loopback to be performed." 280 DEFVAL { end2end } 281 ::= { oamLoopbackPingEntry 5 } 282 283oamLoopbackPingLocation OBJECT-TYPE 284 SYNTAX OCTET STRING (SIZE (0..16)) 285 MAX-ACCESS read-create 286 STATUS current 287 DESCRIPTION 288 "The value to be placed in the 'Loopback Location ID' field 289 of the OAM loopback cell. If this value is less than 16 290 octets in length, then it will be appended with zero-valued 291 octets to form the required 96-bit value. One possibility 292 is to set this value to the IP-address of the node at which 293 the OAM loopback is to occur. 294 295 An instance of this object cannot be created until the 296 associated instance of oamLoopbackPingVpi is created. 297 Once an instance of this object is created, its 298 value can not be changed." 299 DEFVAL { 'FF'H } 300 ::= { oamLoopbackPingEntry 6 } 301 302oamLoopbackPingLocationFlag OBJECT-TYPE 303 SYNTAX INTEGER { ipAddress(1), nsapPrefix(2), 304 fixed16byteValue(3) } 305 MAX-ACCESS read-create 306 STATUS current 307 DESCRIPTION 308 "Specifies what kind of information is embedded into the 309 oamLoopbackPingLocation string. This flag is ignored when 310 oamLoopbackPingType is set to segment." 311 DEFVAL { ipAddress } 312 ::= { oamLoopbackPingEntry 7 } 313 314oamLoopbackPingCount OBJECT-TYPE 315 SYNTAX INTEGER (0..2147483647) 316 MAX-ACCESS read-create 317 STATUS current 318 DESCRIPTION 319 "Specifies the number of OAM loopback cells to send to the 320 target in this sequence." 321 DEFVAL { 5 } 322 ::= { oamLoopbackPingEntry 8 } 323 324oamLoopbackPingTimeout OBJECT-TYPE 325 SYNTAX INTEGER (0..3600000) 326 UNITS "milliseconds" 327 MAX-ACCESS read-create 328 STATUS current 329 DESCRIPTION 330 "Specifies the amount of time to wait for a response to a 331 transmitted OAM loopback cells before declaring the OAM 332 loopback cells as 'dropped.'" 333 DEFVAL { 1000 } 334 ::= { oamLoopbackPingEntry 9 } 335 336oamLoopbackPingDelay OBJECT-TYPE 337 SYNTAX INTEGER (0..3600000) 338 UNITS "milliseconds" 339 MAX-ACCESS read-create 340 STATUS current 341 DESCRIPTION 342 "Specifies the minimum amount of time to wait before sending 343 the next OAM loopback cell in a sequence after receiving a 344 response or declaring a timeout for a previous OAM cell. The 345 actual delay may be greater due to internal task scheduling." 346 DEFVAL { 0 } 347 ::= { oamLoopbackPingEntry 10 } 348 349oamLoopbackPingTrapOnCompletion OBJECT-TYPE 350 SYNTAX TruthValue 351 MAX-ACCESS read-create 352 STATUS current 353 DESCRIPTION 354 "Specifies whether or not a oamLoopbackPingCompletion trap 355 should be issued on completion of the sequence of OAM loopback 356 cells. If such a trap is desired, it is the responsibility of 357 the management entity to ensure that the SNMP administrative 358 model is configured in such a way as to allow the trap to be 359 delivered." 360 DEFVAL { false } 361 ::= { oamLoopbackPingEntry 11 } 362 363oamLoopbackPingSentCells OBJECT-TYPE 364 SYNTAX Counter32 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The number of OAM loopback cells that have been sent to the 369 target in this sequence." 370 ::= { oamLoopbackPingEntry 12 } 371 372oamLoopbackPingReceivedCells OBJECT-TYPE 373 SYNTAX Counter32 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The number of OAM loopback cells that have been received 378 from the target in this sequence." 379 ::= { oamLoopbackPingEntry 13 } 380 381oamLoopbackPingMinRtt OBJECT-TYPE 382 SYNTAX Integer32 (0..2147483647) 383 UNITS "milliseconds" 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The minimum round trip time of all the OAM loopback cells 388 that have been sent in this sequence. 389 390 This object will not be created until the first OAM loopback 391 response in a sequence is received." 392 ::= { oamLoopbackPingEntry 14 } 393 394oamLoopbackPingAvgRtt OBJECT-TYPE 395 SYNTAX Integer32 (0..2147483647) 396 UNITS "milliseconds" 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The average round trip time of all the OAM loopback cells 401 that have been sent in this sequence. 402 403 This object will not be created until the first OAM loopback 404 response in a sequence is received." 405 ::= { oamLoopbackPingEntry 15 } 406 407oamLoopbackPingMaxRtt OBJECT-TYPE 408 SYNTAX Integer32 (0..2147483647) 409 UNITS "milliseconds" 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The maximum round trip time of all the OAM loopback cells 414 that have been sent in this sequence. 415 416 This object will not be created until the first OAM loopback 417 response in a sequence is received." 418 ::= { oamLoopbackPingEntry 16 } 419 420oamLoopbackPingCompleted OBJECT-TYPE 421 SYNTAX TruthValue 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "Set to true when all the OAM loopback cells in this sequence 426 have been either responded to or timed out." 427 ::= { oamLoopbackPingEntry 17 } 428 429oamLoopbackPingEntryOwner OBJECT-TYPE 430 SYNTAX OwnerString 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "The entity that configured this entry." 435 ::= { oamLoopbackPingEntry 18 } 436 437oamLoopbackPingEntryStatus OBJECT-TYPE 438 SYNTAX RowStatus 439 MAX-ACCESS read-create 440 STATUS current 441 DESCRIPTION 442 "The status of this table entry. Once the entry status is 443 set to active, the associate entry cannot be modified until 444 the sequence completes (oamLoopbackPingCompleted is true)." 445 ::= { oamLoopbackPingEntry 19 } 446 447oamLoopbackPingDir OBJECT-TYPE 448 SYNTAX CiscoOAMPingDir 449 MAX-ACCESS read-create 450 STATUS current 451 DESCRIPTION 452 "This object set the traveling direction of the OAM 453 segment loopback cells which are injected to the 454 connection endpoint." 455 ::= { oamLoopbackPingEntry 20 } 456 457oamLoopbackPingOperStatus OBJECT-TYPE 458 SYNTAX CiscoOAMPingStatus 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "This object indicates the ping test status." 463 ::= { oamLoopbackPingEntry 21 } 464 465oamLoopbackPingExecTime OBJECT-TYPE 466 SYNTAX TimeStamp 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "The value of sysUpTime when the MIB object 471 is created which triggers the loppback ping test." 472 ::= { oamLoopbackPingEntry 22 } 473 474oamLoopbackPingMinRttuSec OBJECT-TYPE 475 SYNTAX Integer32 (0..2147483647) 476 UNITS "microseconds" 477 MAX-ACCESS read-only 478 STATUS current 479 DESCRIPTION 480 "The minimum round trip time of all the OAM loopback cells 481 that have been sent in this sequence. 482 483 This object will not be created until the first OAM loopback 484 response in a sequence is received. 485 486 Notes: this object is the same as oamLoopbackPingMinRtt but 487 the unit is in microseconds instead of milliseconds." 488 ::= { oamLoopbackPingEntry 23 } 489 490oamLoopbackPingAvgRttuSec OBJECT-TYPE 491 SYNTAX Integer32 (0..2147483647) 492 UNITS "microseconds" 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "The average round trip time of all the OAM loopback cells 497 that have been sent in this sequence. 498 499 This object will not be created until the first OAM loopback 500 response in a sequence is received. 501 502 Notes: this object is the same as oamLoopbackPingAvgRtt but 503 the unit is in microseconds instead of milliseconds." 504 ::= { oamLoopbackPingEntry 24 } 505 506oamLoopbackPingMaxRttuSec OBJECT-TYPE 507 SYNTAX Integer32 (0..2147483647) 508 UNITS "microseconds" 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The maximum round trip time of all the OAM loopback cells 513 that have been sent in this sequence. 514 515 This object will not be created until the first OAM loopback 516 response in a sequence is received. 517 518 Notes: this object is the same as oamLoopbackPingMaxRtt but 519 the unit is in microseconds instead of milliseconds." 520 ::= { oamLoopbackPingEntry 25 } 521 522oamLoopbackSegEndPointTable OBJECT-TYPE 523 SYNTAX SEQUENCE OF OamLoopbackSegEndPointEntry 524 MAX-ACCESS not-accessible 525 STATUS current 526 DESCRIPTION 527 "This table contains a list of OAM loopback segment 528 endpoints. 529 530 When the endpoint is an OAM segment endpoint, it is able to 531 send ATM segment loop back cells or loop back the cells to 532 the originator which initiates the OAM loop back ping test. 533 534 The provisioning of this table is required if the loopback 535 ping test type (oamLoopbackPingType) in oamLoopbackPingTable 536 is 'segment', and the endpoint under test or the remote ping 537 endpoint is not OAM segment loopback endpoints." 538 ::= { ciscoOamPingMIBObjects 2 } 539 540oamLoopbackSegEndPointEntry OBJECT-TYPE 541 SYNTAX OamLoopbackSegEndPointEntry 542 MAX-ACCESS not-accessible 543 STATUS current 544 DESCRIPTION 545 "An entry in the segment endpoint table." 546 INDEX { ifIndex, oamLoopSegVpi, oamLoopSegVci } 547 ::= { oamLoopbackSegEndPointTable 1 } 548 549OamLoopbackSegEndPointEntry ::= 550 SEQUENCE { 551 oamLoopSegVpi Unsigned32, 552 oamLoopSegVci Unsigned32, 553 oamLoopSegRowStatus RowStatus 554 } 555 556oamLoopSegVpi OBJECT-TYPE 557 SYNTAX Unsigned32 (0..4095) 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "The VPI value of a VP or VC connection." 562 ::= { oamLoopbackSegEndPointEntry 1 } 563 564oamLoopSegVci OBJECT-TYPE 565 SYNTAX Unsigned32 (0..65535) 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "The VCI value of VC connection. For a VPC connection, 570 the VCI value is 0." 571 ::= { oamLoopbackSegEndPointEntry 2 } 572 573oamLoopSegRowStatus OBJECT-TYPE 574 SYNTAX RowStatus 575 MAX-ACCESS read-create 576 STATUS current 577 DESCRIPTION 578 "To create, delete an OAM segment entry. Only 579 the value 'active', 'createAndGo', and 'destroy' are 580 supported. 581 582 If the connection endpoint does not exist, the entry could 583 not be created. 584 585 If the associated ATM connection is de-routed or deleted, the 586 connection endpoint is gone. The associated row entry will be 587 removed automatically." 588 ::= { oamLoopbackSegEndPointEntry 3 } 589 590oamLoopbackPingMIBTrapPrefix OBJECT IDENTIFIER ::= 591 { ciscoOamPingMIB 2 } 592oamLoopbackPingMIBTraps OBJECT IDENTIFIER ::= 593 { oamLoopbackPingMIBTrapPrefix 0 } 594 595oamLoopbackPingCompletionTrap NOTIFICATION-TYPE 596 OBJECTS { oamLoopbackPingCompleted 597 } 598 STATUS current 599 DESCRIPTION 600 "A oamLoopbackPingCompleted trap is sent at the completion 601 of a sequence of OAM loopback cells if such a trap was 602 requested when the sequence was initiated." 603 ::= { oamLoopbackPingMIBTraps 1 } 604 605-- conformance information 606 607ciscoOamPingMIBConformance 608 OBJECT IDENTIFIER ::= { ciscoOamPingMIB 3 } 609ciscoOamPingMIBCompliances 610 OBJECT IDENTIFIER ::= { ciscoOamPingMIBConformance 1 } 611ciscoOamPingMIBGroups 612 OBJECT IDENTIFIER ::= { ciscoOamPingMIBConformance 2 } 613 614 615-- compliance statements 616 617ciscoOamPingMIBCompliance MODULE-COMPLIANCE 618 STATUS deprecated -- replace by ciscoOamPingMIBCompliance2 619 DESCRIPTION 620 "The compliance statement for the Cisco OAM MIB." 621 MODULE -- this module 622 MANDATORY-GROUPS { ciscoOamPingMIBGroup } 623 ::= { ciscoOamPingMIBCompliances 1 } 624 625ciscoOamPingMIBCompliance2 MODULE-COMPLIANCE 626 STATUS deprecated -- replace by ciscoOamPingMIBCompliance3 627 DESCRIPTION 628 "The compliance statement for the Cisco OAM MIB." 629 MODULE -- this module 630 MANDATORY-GROUPS { ciscoOamPing2MIBGroup, 631 oamLoopbackNotificationsGroup } 632 633 GROUP ciscoOamPingSegEndPointGroup 634 DESCRIPTION 635 "Implementation of this group is optional for the 636 systems where OAM connection segment endpoint is 637 not configuration." 638 639 ::= { ciscoOamPingMIBCompliances 2 } 640 641ciscoOamPingMIBCompliance3 MODULE-COMPLIANCE 642 STATUS current 643 DESCRIPTION 644 "The compliance statement for the Cisco OAM MIB." 645 MODULE -- this module 646 MANDATORY-GROUPS { ciscoOamPingMIBGroupRev3, 647 oamLoopbackNotificationsGroup } 648 649 GROUP ciscoOamPingSegEndPointGroup 650 DESCRIPTION 651 "Implementation of this group is optional for the 652 systems where OAM connection segment endpoint is 653 not configuration." 654 655 ::= { ciscoOamPingMIBCompliances 3 } 656 657-- units of conformance 658 659ciscoOamPingMIBGroup OBJECT-GROUP 660 OBJECTS { oamLoopbackPingInterface,oamLoopbackPingVpi, 661 oamLoopbackPingVci, oamLoopbackPingCount, 662 oamLoopbackPingType, oamLoopbackPingLocation, 663 oamLoopbackPingLocationFlag, 664 oamLoopbackPingTimeout, oamLoopbackPingDelay, 665 oamLoopbackPingTrapOnCompletion, 666 oamLoopbackPingSentCells, 667 oamLoopbackPingReceivedCells, oamLoopbackPingMinRtt, 668 oamLoopbackPingAvgRtt, oamLoopbackPingMaxRtt, 669 oamLoopbackPingCompleted, oamLoopbackPingEntryOwner, 670 oamLoopbackPingEntryStatus 671 } 672 STATUS deprecated -- replaced by ciscoOamPing2MIBGroup 673 DESCRIPTION 674 "A collection of objects providing the ability to invoke 675 the sending of OAM loopback cells." 676 ::= { ciscoOamPingMIBGroups 1 } 677 678ciscoOamPing2MIBGroup OBJECT-GROUP 679 OBJECTS { oamLoopbackPingInterface,oamLoopbackPingVpi, 680 oamLoopbackPingVci, oamLoopbackPingCount, 681 oamLoopbackPingType, oamLoopbackPingLocation, 682 oamLoopbackPingLocationFlag, 683 oamLoopbackPingTimeout, oamLoopbackPingDelay, 684 oamLoopbackPingTrapOnCompletion, 685 oamLoopbackPingSentCells, 686 oamLoopbackPingReceivedCells, oamLoopbackPingMinRtt, 687 oamLoopbackPingAvgRtt, oamLoopbackPingMaxRtt, 688 oamLoopbackPingCompleted, oamLoopbackPingEntryOwner, 689 oamLoopbackPingEntryStatus, 690 oamLoopbackPingDir, oamLoopbackPingOperStatus, 691 oamLoopbackPingExecTime 692 } 693 STATUS deprecated -- replaced by ciscoOamPingMIBGroupRev3 694 DESCRIPTION 695 "A collection of objects providing the ability to invoke 696 the sending of OAM loopback cells." 697 ::= { ciscoOamPingMIBGroups 2 } 698 699ciscoOamPingSegEndPointGroup OBJECT-GROUP 700 OBJECTS { oamLoopSegRowStatus } 701 STATUS current 702 DESCRIPTION 703 "A collection of objects providing the ability to provision 704 ATM connection endpoints to be OAM segment loopback endpoint." 705 ::= { ciscoOamPingMIBGroups 3 } 706 707 708-- current notification group 709oamLoopbackNotificationsGroup NOTIFICATION-GROUP 710 NOTIFICATIONS { 711 oamLoopbackPingCompletionTrap 712 } 713 STATUS current 714 DESCRIPTION 715 "A collection of notifications for OAM loopback ping test." 716 ::= { ciscoOamPingMIBGroups 4 } 717 718ciscoOamPingMIBGroupRev3 OBJECT-GROUP 719 OBJECTS { oamLoopbackPingInterface,oamLoopbackPingVpi, 720 oamLoopbackPingVci, oamLoopbackPingCount, 721 oamLoopbackPingType, oamLoopbackPingLocation, 722 oamLoopbackPingLocationFlag, 723 oamLoopbackPingTimeout, oamLoopbackPingDelay, 724 oamLoopbackPingTrapOnCompletion, 725 oamLoopbackPingSentCells, 726 oamLoopbackPingReceivedCells, oamLoopbackPingMinRtt, 727 oamLoopbackPingAvgRtt, oamLoopbackPingMaxRtt, 728 oamLoopbackPingCompleted, oamLoopbackPingEntryOwner, 729 oamLoopbackPingEntryStatus, 730 oamLoopbackPingDir, oamLoopbackPingOperStatus, 731 oamLoopbackPingExecTime, oamLoopbackPingAvgRttuSec, 732 oamLoopbackPingMinRttuSec, oamLoopbackPingMaxRttuSec 733 } 734 STATUS current 735 DESCRIPTION 736 "A collection of objects providing the ability to invoke 737 the sending of OAM loopback cells." 738 ::= { ciscoOamPingMIBGroups 5 } 739 740 741END 742 743 744 745