1-- ***************************************************************** 2-- CISCO-RTTMON-TC-MIB.my: IP SLA Textual Conventions MIB file 3-- 4-- August 2005, Katherine Yang 5-- 6-- Copyright (c) 2005-2014, 2017 by Cisco Systems Inc. 7-- All rights reserved. 8-- 9-- ***************************************************************** 10 11CISCO-RTTMON-TC-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY, 15 Unsigned32, 16 Integer32 17 FROM SNMPv2-SMI 18 TEXTUAL-CONVENTION 19 FROM SNMPv2-TC 20 ciscoMgmt 21 FROM CISCO-SMI; 22 23 24ciscoRttMonTCMIB MODULE-IDENTITY 25 LAST-UPDATED "201709060000Z" 26 ORGANIZATION "Cisco Systems, Inc." 27 CONTACT-INFO 28 "Cisco Systems, Inc. 29 Customer Service 30 31 Postal: 170 W Tasman Drive 32 San Jose, CA 95134 33 34 Tel: +1 800 553 NETS 35 Email: cs-ipsla@cisco.com" 36 DESCRIPTION 37 "This MIB contains textual conventions used by 38 CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and 39 CISCO-RTTMON-ICMP-MIB, but they are not limited 40 to only these MIBs. 41 These textual conventions were originally defined in 42 CISCO-RTTMON-MIB. 43 44 Acronyms: 45 FEC: Forward Equivalence Class 46 LPD: Label Path Discovery 47 LSP: Label Switched Path 48 MPLS: Multi Protocol Label Switching 49 RTT: Round Trip Time 50 SAA: Service Assurance Agent 51 VPN: Virtual Private Network 52 CFM: Connection Fault Management" 53 REVISION "201708030000Z" 54 DESCRIPTION 55 "Added a new TC cipslaPercentileVar" 56 REVISION "201403190000Z" 57 DESCRIPTION 58 "Added new fabricPathEcho type to RttMonRttType and 59 fabricPathEchoAppl type to RttMonProtocol" 60 REVISION "201311260000Z" 61 DESCRIPTION 62 "Added new RttMonReactVar type named 'protocolSpecificError'" 63 REVISION "201211020000Z" 64 DESCRIPTION 65 "Added RttMonScheduleStartType TC. 66 67 Added enumeration y1731dmmv1 to RttMonProtocol. 68 69 Added the following to RttMonReactVar: 70 lpdGroup, lpdTreeTrace, lpdAll, 71 unavailSD, unavailDS, pktLossPctSD, 72 pktLossPctDS, rttPct, maxOfLatencySDPct, 73 maxOfLatencyDSPct, latencySDAvgPct, latencyDSAvgPct, 74 jitterSDAvgPct, jitterDSAvgPct, jitterAvgPct, 75 overThreshold." 76 REVISION "201205250000Z" 77 DESCRIPTION 78 "Added enumeration y1731slm to RttMonProtocol 79 80 Added the following to RttResopnseSense. 81 statsRetrieveOk, statsRetrieveNoConnect, 82 statsRetrieveVersionFail, statsRetrieveInternalError, 83 statsRetrieveAbort, statsRetrieveFail, 84 statsRetrieveAuthFail, statsRetrieveFormatError, 85 statsRetrievePortInUse. 86 87 For enumeration from controlOk to controlPortInUse, changed the 88 prefix from control to enable." 89 REVISION "201109150000Z" 90 DESCRIPTION 91 "Updated following textual conventions to include Y1731 92 and Multicast extensions. 93 -RttMonRttType, RttMonProtocol." 94 REVISION "201004260000Z" 95 DESCRIPTION 96 "Added enumeration 'video' to RttMonRttType TC." 97 REVISION "200608110000Z" 98 DESCRIPTION 99 "Added RttMonIdLst and RttMonCtrlIndex textual conventions." 100 REVISION "200607170000Z" 101 DESCRIPTION 102 "Added enumeration 'lspPingPseudowire' to RttMonRttType TC." 103 REVISION "200603020000Z" 104 DESCRIPTION 105 "Added ethernetPing and ethernetJitter in RttMonRttType. 106 Added ethernetPingAppl and ethernetJitterAppl 107 in RttMonProtocol" 108 REVISION "200508090000Z" 109 DESCRIPTION 110 "Initial version of this MIB module." 111 ::= { ciscoMgmt 485 } 112 113 114 115-- Textual Conventions 116 117RttMonScheduleStartType ::= TEXTUAL-CONVENTION 118 STATUS current 119 DESCRIPTION 120 "These are defined values for scheduling the start time of a 121 probe 122 123 pending(1) - Pending state 124 now(2) - Schedule the start time of probe to current time 125 and probe is immediately started 126 random(3) - Schedule the start time of probe at a random 127 time over a range. 128 after(4) - Schedule the start time of probe after a certain 129 amount of time from now. 130 specific(5) - Schedule the start time of probe at a specific 131 given time interval" 132 SYNTAX INTEGER { 133 pending(1), 134 now(2), 135 random(3), 136 after(4), 137 specific(5) 138 } 139 140RttReset ::= TEXTUAL-CONVENTION 141 STATUS current 142 DESCRIPTION 143 "When the value set to 'reset', the entire RTT application 144 goes through a reset sequence, making a best 145 effort to revert to its startup condition. At other times, 146 the value is 'ready'." 147 SYNTAX INTEGER { 148 ready(1), 149 reset(2) 150 } 151 152RttMonOperation ::= TEXTUAL-CONVENTION 153 STATUS current 154 DESCRIPTION 155 "The following are specific RTT operations for a 156 particular probe type: 157 notApplicable(0) - This object is not applicable for the 158 probe type. 159 httpGet(1) - HTTP get request 160 httpRaw(2) - HTTP request with user defined payload 161 ftpGet(3) - FTP get request 162 ftpPassive(4) - FTP passive mode 163 ftpActive(5) - FTP active mode 164 voipDTAlertRinging(6) - Voip post dial delay detect point: 165 Alerting / Ringing 166 voipDTConnectOK(7) - Voip post dial delay detect point: 167 Connect /OK" 168 SYNTAX INTEGER { 169 notApplicable(0), 170 httpGet(1), 171 httpRaw(2), 172 ftpGet(3), 173 ftpPassive(4), 174 ftpActive(5), 175 voipDTAlertRinging(6), 176 voipDTConnectOK(7) 177 } 178 179-- Operation completion sense code textual convention 180 181RttResponseSense ::= TEXTUAL-CONVENTION 182 STATUS current 183 DESCRIPTION 184 "These are the defined values for a completion status 185 of a RTT operation. 186 187 other(0) - the operation is not started or completed 188 or this object is not applicable for 189 the probe type. 190 ok(1) - a valid completion occurred and 191 timed successfully 192 disconnected(2) - the operation did not occur because 193 the connection to the target 194 was lost 195 overThreshold(3) - a valid completion was received but 196 the completion time exceeded a 197 threshold value 198 timeout(4) - an operation timed out; no completion 199 time recorded 200 busy(5) - the operation did not occur because a 201 previous operation is still 202 outstanding 203 notConnected(6) - the operation did not occur because no 204 connection (session) exists with the 205 target 206 dropped(7) - the operation did not occur due to lack 207 of internal resource 208 sequenceError(8) - a completed operation did not contain 209 the correct sequence id; no completion 210 time recorded 211 verifyError(9) - a completed operation was received, but 212 the data it contained did not match 213 the expected data; no completion time 214 recorded 215 applicationSpecific(10) 216 - the application generating the operation 217 had a specific error 218 dnsServerTimeout(11) 219 - DNS Server Timeout 220 tcpConnectTimeout(12) 221 - TCP Connect Timeout 222 httpTransactionTimeout(13) 223 - HTTP Transaction Timeout 224 dnsQueryError(14) 225 - DNS Query error (because of unknown address 226 etc.,) 227 httpError(15) 228 - HTTP Response StatusCode is not OK (200), 229 or permenent redirect(301), temporary redirect 230 (302) then HTTP error is set. 231 error(16) 232 - if there are socket failures or some other 233 errors not relavant to the actual probe, they 234 are recorded under this error 235 mplsLspEchoTxError(17) 236 - MPLS echo request transmission failure. 237 mplsLspUnreachable(18) 238 - MPLS Target FEC not reachable or unsupported 239 mpls echo reply code. 240 mplsLspMalformedReq(19) 241 - MPLS echo request was malformalformed, pointed 242 out by the reply router. 243 mplsLspReachButNotFEC(20) 244 - MPLS echo request processed by the downstream 245 router but not the target. 246 enableOk(21) 247 - Control enable request OK 248 enableNoConnect(22) 249 - Control enable request fail due to no connection to 250 the target. 251 enableVersionFail(23) 252 - Control enable request version fail. 253 enableInternalError(24) 254 - Control enable request internal error. 255 enableAbort(25) 256 - Control enable request abort. 257 enableFail(26) 258 - Control enable request fail. 259 enableAuthFail(27) 260 - Control enable request fail due to authentication 261 fail. 262 enableFormatError(28) 263 - Control enable request fail due to format error. 264 enablePortInUse(29) 265 - Control enable request fail due to port in use. 266 statsRetrieveOk(30) 267 - Stats retrieve request OK 268 statsRetrieveNoConnect(31) 269 - Stats retrieve request fail due to no connection 270 to the target. 271 statsRetrieveVersionFail(32) 272 - Stats retrieve request version fail. 273 statsRetrieveInternalError(33) 274 - Stats retrieve request internal error. 275 statsRetrieveAbort(34) 276 - Stats retrieve request abort. 277 statsRetrieveFail(35) 278 - Stats retrieve request fail. 279 statsRetrieveAuthFail(36) 280 - Stats retrieve request fail due to authentication fail. 281 statsRetrieveFormatError(37) 282 - Stats retrieve request fail due to format error. 283 statsRetrievePortInUse(38) 284 - Stats retrieve request fail due to port in use." 285 SYNTAX INTEGER { 286 other(0), 287 ok(1), 288 disconnected(2), 289 overThreshold(3), 290 timeout(4), 291 busy(5), 292 notConnected(6), 293 dropped(7), 294 sequenceError(8), 295 verifyError(9), 296 applicationSpecific(10), 297 dnsServerTimeout(11), 298 tcpConnectTimeout(12), 299 httpTransactionTimeout(13), 300 dnsQueryError(14), 301 httpError(15), 302 error(16), 303 mplsLspEchoTxError(17), 304 mplsLspUnreachable(18), 305 mplsLspMalformedReq(19), 306 mplsLspReachButNotFEC(20), 307 enableOk(21), 308 enableNoConnect(22), 309 enableVersionFail(23), 310 enableInternalError(24), 311 enableAbort(25), 312 enableFail(26), 313 enableAuthFail(27), 314 enableFormatError(28), 315 enablePortInUse(29), 316 statsRetrieveOk(30), 317 statsRetrieveNoConnect(31), 318 statsRetrieveVersionFail(32), 319 statsRetrieveInternalError(33), 320 statsRetrieveAbort(34), 321 statsRetrieveFail(35), 322 statsRetrieveAuthFail(36), 323 statsRetrieveFormatError(37), 324 statsRetrievePortInUse(38) 325 } 326 327-- Operation type textual convention 328 329RttMonRttType ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "Specifies the type of RTT operation to be performed. 333 334 The value 'echo' will cause the RTT application to 335 perform a timed echo request/response operation directed 336 at the 'RttMonTargetAddress'. 337 338 The value 'pathEcho' will cause the RTT application 339 to perform path discovery to the 'RttMonTargetAddress', 340 then it will perform a timed echo request/response 341 operation directed at the each hop along the path. 342 This operation will provide two types of information, 343 first the path and second the time delay along the path. 344 345 NOTE: The 'pathEcho' time delay operation is a heuristic 346 measurement because an intermediate hop may forward 347 the different echo request/response at different 348 rates. Thus the time delay difference between two 349 hops along a path may contain very little 'true' 350 statistical meaning. 351 352 The value 'fileIO' will cause the RTT application to 353 write, read, or write/read a file to a preconfigured 354 file server. 355 356 The value 'script' will cause the RTT application to 357 execute a preconfigured script. 358 359 The value 'udpEcho' will cause the RTT application 360 to perform a timed udp packet send/receive operation 361 directed at the 'RttMonTargetAddress'. 362 363 The value 'tcpConnect' will cause the RTT application 364 to perform a timed tcp connect operation directed at the 365 'RttMonTargetAddress'. 366 367 The value 'http' will cause the RTT application 368 to perform a download of the object specified in the URL. 369 370 The value 'dns' will cause the RTT application 371 to perform a name lookup of an IP Address or a hostname. 372 373 The value 'jitter' will cause the RTT application 374 to perform delay variance analysis. 375 376 The value 'dlsw' will cause the RTT application 377 to perform a keepalive operation to measure the response 378 time of a DLSw peer. 379 380 The value 'dhcp' will cause the RTT application 381 to perform an IP Address lease request/teardown operation. 382 383 The value 'voip' will cause the RTT application 384 to perform call set up operation to measure the response. 385 386 The value 'rtp' will cause the RTT application to perform 387 delay variance analysis for RTP packet. 388 389 The value 'lspGroup' will cause the RTT application to 390 logically 391 group Label Switched Paths discovered as part of LSP Path 392 Discovery to the target and perform an RTT operation end to end 393 over each path in the Group. The type of operation configured 394 is determined by rttMplsVpnMonCtrlRttType. 395 396 The value 'icmpjitter' will cause the RTT application 397 to perform delay variance analysis using ICMP timestamp 398 packets. 399 400 The value of 'lspPingIpv4' will cause the RTT application to 401 perform ping over LSP path. 402 403 The value of 'lspTraceIpv4' will cause the RTT application to 404 perform trace over LSP path. 405 406 The value of 'ethernetPing' will cause the RTT application to 407 perform delay variance analysis using regular 802.1ag loopback 408 frame. 409 410 The value of 'ethernetJitter' will cause the RTT application to 411 perform delay variance analysis using CFM frame. 412 413 The value of 'lspPingPseudowire' will cause the RTT application 414 to perform LSP Ping over Pseudowire and measure response time. 415 416 The value 'video' will cause the the RTT application to perform 417 a video stream analysis directed at the 'RttMonTargetAddress'. 418 419 The value 'y1731Delay' will cause the RTT application to 420 perform 421 a ITU-T standard Y.1731 delay variance analysis. 422 423 The value 'y1731Loss' will cause the RTT application to perform 424 a ITU-T standard Y.1731 loss measure analysis. 425 426 The value 'mcastJitter' will cause the RTT application to 427 perform udp jitter stream analysis on a multicast network. 428 429 The value 'fabricPathEcho' will cause the RTT application to 430 perform delay performance measurment and verify connectivity in 431 a Fabric Path Network." 432 SYNTAX INTEGER { 433 echo(1), 434 pathEcho(2), 435 fileIO(3), 436 script(4), 437 udpEcho(5), 438 tcpConnect(6), 439 http(7), 440 dns(8), 441 jitter(9), 442 dlsw(10), 443 dhcp(11), 444 ftp(12), 445 voip(13), 446 rtp(14), 447 lspGroup(15), 448 icmpjitter(16), 449 lspPing(17), 450 lspTrace(18), 451 ethernetPing(19), 452 ethernetJitter(20), 453 lspPingPseudowire(21), 454 video(22), 455 y1731Delay(23), 456 y1731Loss(24), 457 mcastJitter(25), 458 fabricPathEcho(26) 459 } 460 461-- Operation type for Auto SAA L3 MPLS VPN textual convention 462 463RttMplsVpnMonRttType ::= TEXTUAL-CONVENTION 464 STATUS current 465 DESCRIPTION 466 "Specifies the type of RTT operation to be performed for 467 Auto SAA L3 MPLS VPN. 468 469 The value 'jitter' will cause the Auto SAA L3 MPLS VPN to 470 automatically configure jitter operations. 471 472 The value 'echo' will cause the Auto SAA L3 MPLS VPN to 473 automatically configure jitter operations. 474 475 The value 'pathEcho' will cause the Auto SAA L3 MPLS VPN to 476 automatically configure jitter operations." 477 SYNTAX INTEGER { 478 jitter(1), 479 echo(2), 480 pathEcho(3) 481 } 482 483-- -- 484-- Auto SAA L3 MPLS VPN LSP Path Discovery 485-- Failure Cause textual convention 486 487RttMplsVpnMonLpdFailureSense ::= TEXTUAL-CONVENTION 488 STATUS current 489 DESCRIPTION 490 "These are the defined values for the causes of failure in 491 LSP Path Discovery. 492 493 unknown(1) - The cause of failure for the 494 LSP Path Discovery cannot be 495 determined. The discovery for 496 the target PE may not have 497 started. 498 noPath(2) - No paths were found to the 499 target FEC while doing the 500 LSP Path Discovery. 501 allPathsBroken(3) - All paths to the target FEC 502 are broken. This means an 503 untagged interface on the LSP 504 to the target. 505 allPathsUnexplorable(4) - All paths to the target FEC are 506 unexplorable. This identifies 507 a case where there is some 508 problem in reaching the next 509 hop while doing Discovery. 510 allPathsBrokenOrUnexplorable(5) - All paths to the target FEC are 511 are either broken or 512 unexplorable. 513 timeout(6) - The LSP Path Discovery could 514 not be completed for the 515 target FEC within the 516 configured time. 517 error(7) - Error occurred while 518 performing LSP Path Discovery. 519 It might be also due to some 520 reasons unrelated to LSP Path 521 Discovery." 522 SYNTAX INTEGER { 523 unknown(1), 524 noPath(2), 525 allPathsBroken(3), 526 allPathsUnexplorable(4), 527 allPathsBrokenOrUnexplorable(5), 528 timeout(6), 529 error(7) 530 } 531 532-- textual convention 533 534RttMplsVpnMonLpdGrpStatus ::= TEXTUAL-CONVENTION 535 STATUS current 536 DESCRIPTION 537 "These are the defined values for the status of the LPD Group. 538 539 unknown(1) - This indicates that some/all of the probes which are 540 part of the LPD group have not completed even 541 a single operation, so the group status cannot be 542 identified. 543 up(2) - This state indicates that all the probes which are 544 part of the LPD group are up with latest return 545 code as 'ok'. 546 partial(3) - This state indicates that some probes are up and 547 running fine and some are not 'ok'. 548 down(4) - This state indicates that all the probes to the 549 target are not running fine. This state indicates 550 that there is connectivity problem to the target 551 PE." 552 SYNTAX INTEGER { 553 unknown(1), 554 up(2), 555 partial(3), 556 down(4) 557 } 558 559RttMonProtocol ::= TEXTUAL-CONVENTION 560 STATUS current 561 DESCRIPTION 562 "Specifies the protocol to be used to perform the timed 563 echo request/response. The following protocols are 564 defined: 565 566 NOTE: All protocols that end in 'Appl' will support 567 the asymetric request/response (ARR) protocol. 568 See the DESCRIPTION for ciscoRttMonMIB for a 569 complete description of the asymetric 570 request/response protocol. 571 572 notApplicable - no protocol is defined 573 ipIcmpEcho - uses Echo Request/Reply as defined 574 in RFC792 for Internet Protocol 575 networks 576 ipUdpEchoAppl - uses the UDP based echo server 577 snaRUEcho - uses the REQECHO and ECHOTEST RU's 578 to an SSCP over an SNA LU-SSCP 579 session 580 snaLU0EchoAppl - uses test RU's sent to the Echo 581 Server over an SNA LU0-LU0 session 582 snaLU2EchoAppl - uses test RU's sent to the Echo 583 Server over an SNA LU2-LU2 session 584 snaLU62Echo - uses the native appn ping ie. aping 585 snaLU62EchoAppl - uses test RU's sent to the ARR 586 Echo Server over an SNA LU6.2-LU6.2 587 session 588 appleTalkEcho - uses Echo Request/Reply as defined 589 for appleTalk networks 590 appleTalkEchoAppl - uses the appleTalk based echo 591 server 592 decNetEcho - uses Echo Request/Reply as defined 593 for DECNet networks 594 decNetEchoAppl - uses the DECnet based echo server 595 ipxEcho - uses Echo Request/Reply as defined 596 for Novell IPX networks 597 ipxEchoAppl - uses the Novel IPX based echo 598 server 599 isoClnsEcho - uses Echo Request/Reply as defined 600 for ISO CLNS networks 601 isoClnsEchoAppl - uses the ISO CLNS based echo 602 server 603 vinesEcho - uses Echo Request/Reply as defined 604 for VINES networks 605 vinesEchoAppl - uses the VINES based echo server 606 xnsEcho - uses Echo Request/Reply as defined 607 for XNS networks 608 xnsEchoAppl - uses the XNS based echo server 609 apolloEcho - uses Echo Request/Reply as defined 610 for APOLLO networks 611 apolloEchoAppl - uses the APOLLO based echo 612 server 613 netbiosEchoAppl - uses the netbios based echo 614 server 615 ipTcpConn - uses the tcp's connect mechanism 616 httpAppl - uses udp for name resolution, 617 tcp connect and tcp data transfer 618 mechanisms for HTTP data download 619 from a particular HTTP Server 620 dnsAppl - uses udp for name resolution 621 jitterAppl - uses udp for packet transfers 622 dlswAppl - uses tcp for sending keepalives 623 dhcpAppl - uses udp for sending dhcp requests 624 ftpAppl - uses tcp for connect & data transfer 625 mplsLspPingAppl - uses MPLS Echo Request/Response as per 626 draft-ietf-mpls-lsp-ping-04 ietf 627 standard 628 voipAppl - uses Symphony infrastructure to measure 629 H.323/SIP call set up time 630 rtpAppl - uses Symphony infrastructure to measure 631 rtp packets delay variance. 632 icmpJitterAppl - uses ICMP Timestamp for packet transfer 633 to measure jitter. 634 ethernetPingAppl - uses regular 802.1ag loopback frame 635 ethernetJitterAppl - uses CFM frames . 636 videoAppl - uses synthetic traffic depending on video 637 profile 638 y1731dmm - used to measure Y1731 delay 639 y17311dm - used to measure Y1731 1DM 640 y1731lmm - used to measure Y1731 Loss measurement 641 mcastJitterAppl - uses udp jitter to measure multicast 642 network performance 643 y1731slm - used to measure Y1731 Synthetic Loss 644 measurement 645 y1731dmmv1 - used to measure Y1731 DMMv1 measurement 646 647 fabricPathEchoAppl - uses Fabric Path connect mechanism" 648 SYNTAX INTEGER { 649 notApplicable(1), 650 ipIcmpEcho(2), 651 ipUdpEchoAppl(3), 652 snaRUEcho(4), 653 snaLU0EchoAppl(5), 654 snaLU2EchoAppl(6), 655 snaLU62Echo(7), 656 snaLU62EchoAppl(8), 657 appleTalkEcho(9), 658 appleTalkEchoAppl(10), 659 decNetEcho(11), 660 decNetEchoAppl(12), 661 ipxEcho(13), 662 ipxEchoAppl(14), 663 isoClnsEcho(15), 664 isoClnsEchoAppl(16), 665 vinesEcho(17), 666 vinesEchoAppl(18), 667 xnsEcho(19), 668 xnsEchoAppl(20), 669 apolloEcho(21), 670 apolloEchoAppl(22), 671 netbiosEchoAppl(23), 672 ipTcpConn(24), 673 httpAppl(25), 674 dnsAppl(26), 675 jitterAppl(27), 676 dlswAppl(28), 677 dhcpAppl(29), 678 ftpAppl(30), 679 mplsLspPingAppl(31), 680 voipAppl(32), 681 rtpAppl(33), 682 icmpJitterAppl(34), 683 ethernetPingAppl(35), 684 ethernetJitterAppl(36), 685 videoAppl(37), 686 y1731dmm(38), 687 y17311dm(39), 688 y1731lmm(40), 689 mcastJitterAppl(41), 690 y1731slm(42), 691 y1731dmmv1(43), 692 fabricPathEchoAppl(44) 693 } 694 695RttMonCodecType ::= TEXTUAL-CONVENTION 696 STATUS current 697 DESCRIPTION 698 "Specifies the codec type to be used with the jitter probe. 699 The following codec types are defined: 700 701 notApplicable - no CodecType is defined 702 g711ulaw - uses G.711 U Law 64000 bps 703 g711alaw - uses G.711 A Law 64000 bps 704 g729a - uses G.729 8000 bps" 705 SYNTAX INTEGER { 706 notApplicable(0), 707 g711ulaw(1), 708 g711alaw(2), 709 g729a(3) 710 } 711 712RttMonLSPPingReplyMode ::= TEXTUAL-CONVENTION 713 STATUS current 714 DESCRIPTION 715 "Specifies the Reply mode for the MPLS LSP Echo request 716 packets. The following reply modes are supported: 717 718 replyIpv4Udp(1) - an mpls echo request will normally 719 have reply via IPv4 UDP packets. 720 replyIpv4UdpRA(2) - reply via IPv4 UDP Router Alert. Used 721 when IPv4 return path is deemed 722 unreliable." 723 SYNTAX INTEGER { 724 replyIpv4Udp(1), 725 replyIpv4UdpRA(2) 726 } 727 728RttMonTargetAddress ::= TEXTUAL-CONVENTION 729 STATUS current 730 DESCRIPTION 731 "A string which specifies the address of the target for 732 the RTT operation; a value of RttMonTargetAddress 733 which corresponds to a 'broadcast' address is disallowed. 734 735 The interpretation of this string depends on the type of 736 RTT operation selected, as specified by RttMonProtocol; 737 consequently, this object cannot be created until 738 RttMonProtocol has been created (or must be in the same 739 PDU). 740 741 SNA addresses will be provided in ASCII, but will be 742 converted to EBCDIC 743 744 It is interpreted as follows, for the specified values of 745 RttMonProtocol: 746 747 ipIcmpEcho, ipUdpEchoAppl, ipTcpConn, jitterAppl, dlswAppl, 748 dnsAppl, httpAppl, and dhcpAppl 749 - 4 octets 750 751 snaRUEcho 752 - N octets, containing the value of the sna 753 HOSTNAME of which the SSCP LU will be used 754 for the operation. For many systems this value 755 can be empty, and the system will use the 756 implied SSCP LU. For example 'NSPECHO'. 757 758 snaLU0EchoAppl and snaLU2EchoAppl 759 - N octets, the first x octets are the HOSTNAME 760 (Alternatively, this could be a PU name defined 761 to transport to the desired HOST), the second 762 y octets are the APPLID, and the last z octets 763 are the MODENAME of the Echo Server (blank 764 for a MODENAME default). The address will be 765 encoded with a size byte preceding each of 766 the x y and z called s. For example sxsysz 767 as in '0x06CWBC060x07NSPECHO0x00' where 768 HOSTNAME = CWBC06, APPLID = NSPECHO, and 769 MODENAME is defaulted to 8 blanks. 770 NOTE: MODENAME is either size 0 or 8. 771 772 snaLU62Echo and snaLU62EchoAppl 773 - N octets, the first x octets are the LU-NAME, 774 the second y octets are the TP-NAME, and the 775 last z octets are the MODENAME of the Echo 776 Server. The address will be encoded with a size 777 byte preceding each of the x y and z called s. 778 For example sxsysz (zero size before z for a 779 MODENAME default). The LU-NAME is composed of 780 8 bytes '.' 8 bytes. The Transaction Program 781 name (TP-NAME) is 1-64 bytes. The MODENAME 782 is 8 bytes. 783 784 appleTalkEcho, appleTalkEchoAppl 785 786 decNetEcho, decNetEchoAppl 787 788 ipxEcho, ipxEchoAppl 789 790 isoClnsEcho, isoClnsEchoAppl 791 792 vinesEcho, vinesEchoAppl 793 794 xnsEcho, xnsEchoAppl 795 apolloEcho, apolloEchoAppl 796 797 netbiosEchoAppl, voipAppl 798 - unsupported protocols. 799 800 mplsLspPingAppl 801 - 8 octets, the first 4 octets are the FEC address 802 and the next 4 octets are the FEC address mask." 803 SYNTAX OCTET STRING 804 805RttMonReactVar ::= TEXTUAL-CONVENTION 806 STATUS current 807 DESCRIPTION 808 "The following are specific Reaction variables for a 809 particular probe type: 810 rtt(1) - Round Trip Time 811 jitterSDAvg(2) - Jitter average from source to Destination 812 jitterDSAvg(3) - Jitter average from destination to source 813 packetLossSD(4) - Packet loss from source to destination 814 packetLossDS(5) - Packet loss from destination to source 815 mos(6) - Mean Opinion Score 816 timeout(7) - Timeout of the Operation 817 connectionLoss(8) - Connection Failed to the destination 818 verifyError(9) - Data corruption occurs 819 jitterAvg(10) - Jitter Average in both the directions 820 icpif(11) - Calculated Planning Impairment Factor 821 packetMIA(12) - Missing In Action 822 packetLateArrival(13) - Packets arriving Late 823 packetOutOfSequence(14) - Packets arriving out of sequence 824 maxOfPositiveSD(15) - Maximum positive jitter from 825 Source to Destination 826 maxOfNegativeSD(16) - Maximum negative jitter from 827 Source to Destination 828 maxOfPositiveDS(17) - Maximum positive jitter from 829 Destination to Source 830 maxOfNegativeDS(18) - Maximum negative jitter from 831 Destination to Source. 832 iaJitterDS(19) - Inter arrival jitter from 833 Destination to Source 834 frameLossDS(20) - Number of frame loss recorded 835 at source DSP 836 mosLQDS(21) - Listener quality MOS at Source 837 mosCQDS(22) - Conversational quality MOS at source 838 rFactorDS(23) - R-Factor value at Destination. 839 successivePacketLoss(24)- Successive Dropped Packet 840 maxOfLatencyDS(25) - Maximum Latency from Destination 841 to Source 842 maxOfLatencySD(26) - Maximum Latency from Source 843 to Destination 844 latencyDSAvg(27) - Latency average from Destination 845 to Source 846 latencySDAvg(28) - Latency average from Source 847 to Destination 848 packetLoss(29) - Packets loss in both directions 849 iaJitterSD(30) - Inter arrival jitter from 850 Source to Destination 851 mosCQSD(31) - Conversational quality MOS at 852 Destination 853 rFactorSD(32) - R-Factor value at Destination. 854 lpdGroup(33) - Label Path Discovery (LPD) group 855 lpdTreeTrace(34) - LPD Tree Trace 856 lpdAll(35) - LPD All 857 unavailSD(36) - Unavailability threshold crossing 858 crossing - Source to Destination 859 unavailDS(37) - Unavailability threshold crossing 860 crossing - Destination to source 861 pktLossPctSD(38) - Loss ratio threshold crossing 862 based on percent - Source to 863 Destination 864 pktLossPctDS(39) - Loss ratio threshold crossing 865 based on percent - Destination to 866 Source 867 rttPct(40) - Percentile Round Trip Time 868 maxOfLatencySDPct(41) - Percentile Maximum Latency from 869 Source to Destination 870 maxOfLatencyDSPct(42) - Percentile Maximum Latency from 871 Destination to Source 872 latencySDAvgPct(43) - Percentile Latency Average from 873 Source to Destination 874 latencyDSAvgPct(44) - Percentile Latency Average from 875 Destination to Source 876 jitterSDAvgPct(45) - Percentile Jitter Average from 877 Source to Destination 878 jitterDSAvgPct(46) - Percentile Jitter Average from 879 Destination to Source 880 jitterAvgPct(47) - Percentile Jitter Average in 881 both directions 882 overThreshold(48) - Percent of Round Trip Times 883 over threshold. 884 protocolSpecificError(49)-Any protocol specific error." 885 SYNTAX INTEGER { 886 rtt(1), 887 jitterSDAvg(2), 888 jitterDSAvg(3), 889 packetLossSD(4), 890 packetLossDS(5), 891 mos(6), 892 timeout(7), 893 connectionLoss(8), 894 verifyError(9), 895 jitterAvg(10), 896 icpif(11), 897 packetMIA(12), 898 packetLateArrival(13), 899 packetOutOfSequence(14), 900 maxOfPositiveSD(15), 901 maxOfNegativeSD(16), 902 maxOfPositiveDS(17), 903 maxOfNegativeDS(18), 904 iaJitterDS(19), 905 frameLossDS(20), 906 mosLQDS(21), 907 mosCQDS(22), 908 rFactorDS(23), 909 successivePacketLoss(24), 910 maxOfLatencyDS(25), 911 maxOfLatencySD(26), 912 latencyDSAvg(27), 913 latencySDAvg(28), 914 packetLoss(29), 915 iaJitterSD(30), 916 mosCQSD(31), 917 rFactorSD(32), 918 lpdGroup(33), 919 lpdTreeTrace(34), 920 lpdAll(35), 921 unavailSD(36), 922 unavailDS(37), 923 pktLossPctSD(38), 924 pktLossPctDS(39), 925 rttPct(40), 926 maxOfLatencySDPct(41), 927 maxOfLatencyDSPct(42), 928 latencySDAvgPct(43), 929 latencyDSAvgPct(44), 930 jitterSDAvgPct(45), 931 jitterDSAvgPct(46), 932 jitterAvgPct(47), 933 overThreshold(48), 934 protocolSpecificError(49) 935 } 936 937RttMonIdLst ::= TEXTUAL-CONVENTION 938 STATUS current 939 DESCRIPTION 940 "A string that specifies a list of the IP SLA probe 941 identifiers or other numeric identifiers. 942 The identifiers will be specified in the following form. 943 (a) Individual identifiers with comma separated as 1,5,3. 944 (b) Range form including hyphens with multiple ranges 945 being 946 separated by comma as 1-10,12-34. 947 (c) Mix of the above two forms as 1,2,4-10,12,15,19-25." 948 SYNTAX OCTET STRING (SIZE (0..255)) 949 950RttMonCtrlIndex ::= TEXTUAL-CONVENTION 951 STATUS current 952 DESCRIPTION 953 "The value of this object identifies the row in the 954 ipslaEthernetGrpCtrlTable and ipslaEthernetGrpReactTable. 955 It can be used for other IP SLA control tables." 956 SYNTAX Unsigned32 (1..2147483647) 957 958CipslaPercentileVar ::= TEXTUAL-CONVENTION 959 STATUS current 960 DESCRIPTION 961 "The following are specific percentile types. These types are 962 supported by UDP Jitter, ICMP Jitter and Ethernet Jitter 963 probes: 964 rtt(1) - Round Trip Time 965 owsd(2) - One way delay - Source to Destination 966 owds(3) - One way delay - Destination to Source 967 jittersd(4) - One way jitter - Source to Destination 968 jitterds(5) - One way jitter - Destination to Source 969 jitteravg(6) - Jitter values in both directions." 970 SYNTAX INTEGER { 971 rtt(1), 972 owsd(2), 973 owds(3), 974 jittersd(4), 975 jitterds(5), 976 jitteravg(6) 977 } 978 979END 980