1-- #ident "%Z%%M% %I% %E% SMI" 2 3 MIOX25-MIB DEFINITIONS ::= BEGIN 4 5 IMPORTS 6 Counter, 7 TimeTicks 8 FROM RFC1155-SMI 9 OBJECT-TYPE 10 FROM RFC-1212 11 DisplayString, transmission, 12 ifIndex 13 FROM RFC1213-MIB 14 InstancePointer 15 FROM RFC1316-MIB 16 X121Address 17 FROM RFC1382-MIB 18 PositiveInteger 19 FROM RFC1381-MIB; 20 21 -- IP over X.25 MIB 22 23 miox OBJECT IDENTIFIER ::= { transmission 38 } 24 25 mioxPle OBJECT IDENTIFIER ::= { miox 1 } 26 mioxPeer OBJECT IDENTIFIER ::= { miox 2 } 27 28 -- ########################################################### 29 -- Ple Table 30 -- ########################################################### 31 32 -- Systems that implement RFC 1356 must also implement 33 -- all objects in this group. 34 35 mioxPleTable OBJECT-TYPE 36 SYNTAX SEQUENCE OF MioxPleEntry 37 38 39 40 41 42 ACCESS not-accessible 43 STATUS mandatory 44 DESCRIPTION 45 "This table contains information relative to 46 an interface to an X.25 Packet Level Entity 47 (PLE)." 48 ::= { mioxPle 1 } 49 50 mioxPleEntry OBJECT-TYPE 51 SYNTAX MioxPleEntry 52 ACCESS not-accessible 53 STATUS mandatory 54 DESCRIPTION 55 "These objects manage the encapsulation of 56 other protocols within X.25." 57 INDEX { ifIndex } 58 ::= { mioxPleTable 1 } 59 60 MioxPleEntry ::= SEQUENCE { 61 mioxPleMaxCircuits 62 INTEGER, 63 mioxPleRefusedConnections 64 Counter, 65 mioxPleEnAddrToX121LkupFlrs 66 Counter, 67 mioxPleLastFailedEnAddr 68 OCTET STRING, 69 mioxPleEnAddrToX121LkupFlrTime 70 TimeTicks, 71 mioxPleX121ToEnAddrLkupFlrs 72 Counter, 73 mioxPleLastFailedX121Address 74 X121Address, 75 mioxPleX121ToEnAddrLkupFlrTime 76 TimeTicks, 77 mioxPleQbitFailures 78 Counter, 79 mioxPleQbitFailureRemoteAddress 80 X121Address, 81 mioxPleQbitFailureTime 82 TimeTicks, 83 mioxPleMinimumOpenTimer 84 PositiveInteger, 85 mioxPleInactivityTimer 86 PositiveInteger, 87 mioxPleHoldDownTimer 88 PositiveInteger, 89 mioxPleCollisionRetryTimer 90 91 92 93 94 95 PositiveInteger, 96 mioxPleDefaultPeerId 97 InstancePointer 98 } 99 100 mioxPleMaxCircuits OBJECT-TYPE 101 SYNTAX INTEGER (0..2147483647) 102 ACCESS read-write 103 STATUS mandatory 104 DESCRIPTION 105 "The maximum number of X.25 circuits that 106 can be open at one time for this interface. 107 A value of zero indicates the interface will 108 not allow any additional circuits (as it may 109 soon be shutdown). A value of 2147483647 110 allows an unlimited number of circuits." 111 ::= { mioxPleEntry 1 } 112 113 mioxPleRefusedConnections OBJECT-TYPE 114 SYNTAX Counter 115 ACCESS read-only 116 STATUS mandatory 117 DESCRIPTION 118 "The number of X.25 calls from a remote 119 systems to this system that were cleared by 120 this system. The interface instance should 121 identify the X.25 interface the call came in 122 on." 123 ::= { mioxPleEntry 2 } 124 125 mioxPleEnAddrToX121LkupFlrs OBJECT-TYPE 126 SYNTAX Counter 127 ACCESS read-only 128 STATUS mandatory 129 DESCRIPTION 130 "The number of times a translation from an 131 Encapsulated Address to an X.121 address 132 failed to find a corresponding X.121 133 address. Encapsulated addresses can be 134 looked up in the mioxPeerTable or translated 135 via an algorithm as for the DDN. Addresses 136 that are successfully recognized do not 137 increment this counter. Addresses that are 138 not recognized (reflecting an abnormal 139 packet delivery condition) increment this 140 counter. 141 142 If an address translation fails, it may be 143 144 145 146 147 148 difficult to determine which PLE entry 149 should count the failure. In such cases the 150 first likely entry in this table should be 151 selected. Agents should record the failure 152 even if they are unsure which PLE should be 153 associated with the failure." 154 ::= { mioxPleEntry 3 } 155 156 mioxPleLastFailedEnAddr OBJECT-TYPE 157 SYNTAX OCTET STRING (SIZE(2..128)) 158 ACCESS read-only 159 STATUS mandatory 160 DESCRIPTION 161 "The last Encapsulated address that failed 162 to find a corresponding X.121 address and 163 caused mioxPleEnAddrToX121LkupFlrs to be 164 incremented. The first octet of this object 165 contains the encapsulation type, the 166 remaining octets contain the address of that 167 type that failed. Thus for an IP address, 168 the length will be five octets, the first 169 octet will contain 204 (hex CC), and the 170 last four octets will contain the IP 171 address. For a snap encapsulation, the 172 first byte would be 128 (hex 80) and the 173 rest of the octet string would have the snap 174 header." 175 ::= { mioxPleEntry 4 } 176 177 mioxPleEnAddrToX121LkupFlrTime OBJECT-TYPE 178 SYNTAX TimeTicks 179 ACCESS read-only 180 STATUS mandatory 181 DESCRIPTION 182 "The most recent value of sysUpTime when the 183 translation from an Encapsulated Address to 184 X.121 address failed to find a corresponding 185 X.121 address." 186 ::= { mioxPleEntry 5 } 187 188 189 mioxPleX121ToEnAddrLkupFlrs OBJECT-TYPE 190 SYNTAX Counter 191 ACCESS read-only 192 STATUS mandatory 193 DESCRIPTION 194 "The number of times the translation from an 195 X.121 address to an Encapsulated Address 196 197 198 199 200 201 failed to find a corresponding Encapsulated 202 Address. Addresses successfully recognized 203 by an algorithm do not increment this 204 counter. This counter reflects the number 205 of times call acceptance encountered the 206 abnormal condition of not recognizing the 207 peer." 208 ::= { mioxPleEntry 6 } 209 210 mioxPleLastFailedX121Address OBJECT-TYPE 211 SYNTAX X121Address 212 ACCESS read-only 213 STATUS mandatory 214 DESCRIPTION 215 "The last X.121 address that caused 216 mioxPleX121ToEnAddrLkupFlrs to increase." 217 ::= { mioxPleEntry 7 } 218 219 mioxPleX121ToEnAddrLkupFlrTime OBJECT-TYPE 220 SYNTAX TimeTicks 221 ACCESS read-only 222 STATUS mandatory 223 DESCRIPTION 224 "The most recent value of sysUpTime when the 225 translation from an X.121 address to an 226 Encapsulated Address failed to find a 227 corresponding Encapsulated Address." 228 ::= { mioxPleEntry 8 } 229 230 mioxPleQbitFailures OBJECT-TYPE 231 SYNTAX Counter 232 ACCESS read-only 233 STATUS mandatory 234 DESCRIPTION 235 "The number of times a connection was closed 236 because of a Q-bit failure." 237 ::= { mioxPleEntry 9 } 238 239 mioxPleQbitFailureRemoteAddress OBJECT-TYPE 240 SYNTAX X121Address 241 ACCESS read-only 242 STATUS mandatory 243 DESCRIPTION 244 "The remote address of the most recent 245 (last) connection that was closed because of 246 a Q-bit failure." 247 ::= { mioxPleEntry 10 } 248 249 250 251 252 253 254 mioxPleQbitFailureTime OBJECT-TYPE 255 SYNTAX TimeTicks 256 ACCESS read-only 257 STATUS mandatory 258 DESCRIPTION 259 "The most recent value of sysUpTime when a 260 connection was closed because of a Q-bit 261 failure. This will also be the last time 262 that mioxPleQbitFailures was incremented." 263 ::= { mioxPleEntry 11 } 264 265 mioxPleMinimumOpenTimer OBJECT-TYPE 266 SYNTAX PositiveInteger 267 ACCESS read-write 268 STATUS mandatory 269 DESCRIPTION 270 "The minimum time in milliseconds this 271 interface will keep a connection open before 272 allowing it to be closed. A value of zero 273 indicates no timer." 274 DEFVAL { 0 } 275 ::= { mioxPleEntry 12 } 276 277 mioxPleInactivityTimer OBJECT-TYPE 278 SYNTAX PositiveInteger 279 ACCESS read-write 280 STATUS mandatory 281 DESCRIPTION 282 "The amount of time time in milliseconds 283 this interface will keep an idle connection 284 open before closing it. A value of 285 2147483647 indicates no timer." 286 DEFVAL { 10000 } 287 ::= { mioxPleEntry 13 } 288 289 mioxPleHoldDownTimer OBJECT-TYPE 290 SYNTAX PositiveInteger 291 ACCESS read-write 292 STATUS mandatory 293 DESCRIPTION 294 "The hold down timer in milliseconds. This 295 is the minimum amount of time to wait before 296 trying another call to a host that was 297 previously unsuccessful. A value of 298 2147483647 indicates the host will not be 299 retried." 300 DEFVAL { 0 } 301 ::= { mioxPleEntry 14 } 302 303 304 305 306 307 mioxPleCollisionRetryTimer OBJECT-TYPE 308 SYNTAX PositiveInteger 309 ACCESS read-write 310 STATUS mandatory 311 DESCRIPTION 312 "The Collision Retry Timer in milliseconds. 313 The time to delay between call attempts when 314 the maximum number of circuits is exceeded 315 in a call attempt." 316 DEFVAL { 0 } 317 ::= { mioxPleEntry 15 } 318 319 320 mioxPleDefaultPeerId OBJECT-TYPE 321 SYNTAX InstancePointer 322 ACCESS read-write 323 STATUS mandatory 324 DESCRIPTION 325 "This identifies the instance of the index 326 in the mioxPeerTable for the default 327 parameters to use with this interface. 328 329 The entry identified by this object may have 330 a zero length Encapsulation address and a 331 zero length X.121 address. 332 333 These default parameters are used with 334 connections to hosts that do not have 335 entries in the mioxPeerTable. Such 336 connections occur when using ddn-x25 IP-X.25 337 address mapping or when accepting 338 connections from other hosts not in the 339 mioxPeerTable. 340 341 The mioxPeerEncTable entry with the same 342 index as the mioxPeerTable entry specifies 343 the call encapsulation types this PLE will 344 accept for peers not in the mioxPeerTable. 345 If the mioxPeerEncTable doesn't contain any 346 entries, this PLE will not accept calls from 347 entries not in the mioxPeerTable." 348 ::= { mioxPleEntry 16 } 349 350 351 352 -- ########################################################### 353 -- Peer Table 354 -- ########################################################### 355 356 357 358 359 360 -- Systems that implement RFC 1356 must also implement 361 -- all objects in this group. 362 363 mioxPeerTable OBJECT-TYPE 364 SYNTAX SEQUENCE OF MioxPeerEntry 365 ACCESS not-accessible 366 STATUS mandatory 367 DESCRIPTION 368 "This table contains information about the 369 possible peers this machine may exchange 370 packets with." 371 ::= { mioxPeer 1 } 372 373 mioxPeerEntry OBJECT-TYPE 374 SYNTAX MioxPeerEntry 375 ACCESS not-accessible 376 STATUS mandatory 377 DESCRIPTION 378 "Per peer information." 379 INDEX { mioxPeerIndex } 380 ::= { mioxPeerTable 1 } 381 382 383 MioxPeerEntry ::= SEQUENCE { 384 mioxPeerIndex 385 PositiveInteger, 386 mioxPeerStatus 387 INTEGER, 388 mioxPeerMaxCircuits 389 PositiveInteger, 390 mioxPeerIfIndex 391 PositiveInteger, 392 mioxPeerConnectSeconds 393 Counter, 394 mioxPeerX25CallParamId 395 InstancePointer, 396 mioxPeerEnAddr 397 OCTET STRING, 398 mioxPeerX121Address 399 X121Address, 400 mioxPeerX25CircuitId 401 InstancePointer, 402 mioxPeerDescr 403 DisplayString 404 } 405 406 mioxPeerIndex OBJECT-TYPE 407 SYNTAX PositiveInteger 408 409 410 411 412 413 ACCESS read-only 414 STATUS mandatory 415 DESCRIPTION 416 "An index value that distinguished one entry 417 from another. This index is independent of 418 any other index." 419 ::= { mioxPeerEntry 1 } 420 421 -- Systems can claim conformance with this MIB without 422 -- implementing sets to mioxPeerStatus with a value of 423 -- clearCall or makeCall. 424 -- All other defined values must be accepted. 425 -- Implementors should realize that allowing these values 426 -- provides richer management, and implementations 427 -- are encouraged to accept these values. 428 mioxPeerStatus OBJECT-TYPE 429 SYNTAX INTEGER { 430 valid (1), 431 createRequest (2), 432 underCreation (3), 433 invalid (4), 434 clearCall (5), 435 makeCall (6) 436 } 437 ACCESS read-write 438 STATUS mandatory 439 DESCRIPTION 440 "This reports the status of a peer entry. 441 A value of valid indicates a normal entry 442 that is in use by the agent. A value of 443 underCreation indicates a newly created 444 entry which isn't yet in use because the 445 creating management station is still setting 446 values. 447 448 The value of invalid indicates the entry is 449 no longer in use and the agent is free to 450 delete the entry at any time. A management 451 station is also free to use an entry in the 452 invalid state. 453 454 Entries are created by setting a value of 455 createRequest. Only non-existent or invalid 456 entries can be set to createRequest. Upon 457 receiving a valid createRequest, the agent 458 will create an entry in the underCreation 459 state. This object can not be set to a 460 value of underCreation directly, entries can 461 462 463 464 465 466 only be created by setting a value of 467 createRequest. Entries that exist in other 468 than the invalid state can not be set to 469 createRequest. 470 471 Entries with a value of underCreation are 472 not used by the system and the management 473 station can change the values of other 474 objects in the table entry. Management 475 stations should also remember to configure 476 values in the mioxPeerEncTable with the same 477 peer index value as this peer entry. 478 479 An entry in the underCreation state can be 480 set to valid or invalid. Entries in the 481 underCreation state will stay in that state 482 until 1) the agent times them out, 2) they 483 are set to valid, 3) they are set to 484 invalid. If an agent notices an entry has 485 been in the underCreation state for an 486 abnormally long time, it may decide the 487 management station has failed and invalidate 488 the entry. A prudent agent will understand 489 that the management station may need to wait 490 for human input and will allow for that 491 possibility in its determination of this 492 abnormally long period. 493 494 Once a management station has completed all 495 fields of an entry, it will set a value of 496 valid. This causes the entry to be 497 activated. 498 499 Entries in the valid state may also be set 500 to makeCall or clearCall to make or clear 501 X.25 calls to the peer. After such a set 502 request the entry will still be in the valid 503 state. Setting a value of makeCall causes 504 the agent to initiate an X.25 call request 505 to the peer specified by the entry. Setting 506 a value of clearCall causes the agent to 507 initiate clearing one X.25 call present to 508 the peer. Each set request will initiate 509 another call or clear request (up to the 510 maximum allowed); this means that management 511 stations that fail to get a response to a 512 set request should query to see if a call 513 was in fact placed or cleared before 514 515 516 517 518 519 retrying the request. Entries not in the 520 valid state can not be set to makeCall or 521 clearCall. 522 523 The values of makeCall and clearCall provide 524 for circuit control on devices which perform 525 Ethernet Bridging using static circuit 526 assignment without address recognition; 527 other devices which dynamically place calls 528 based on destination addresses may reject 529 such requests. 530 531 An agent that (re)creates a new entry 532 because of a set with createRequest, should 533 also (re)create a mioxPeerEncTable entry 534 with a mioxPeerEncIndex of 1, and a 535 mioxPeerEncType of 204 (hex CC)." 536 ::= { mioxPeerEntry 2 } 537 538 mioxPeerMaxCircuits OBJECT-TYPE 539 SYNTAX PositiveInteger 540 ACCESS read-write 541 STATUS mandatory 542 DESCRIPTION 543 "The maximum number of X.25 circuits allowed 544 to this peer." 545 DEFVAL { 1 } 546 ::= { mioxPeerEntry 3 } 547 548 mioxPeerIfIndex OBJECT-TYPE 549 SYNTAX PositiveInteger 550 ACCESS read-write 551 STATUS mandatory 552 DESCRIPTION 553 "The value of the ifIndex object for the 554 interface to X.25 to use to call the peer." 555 DEFVAL { 1 } 556 ::= { mioxPeerEntry 4 } 557 558 mioxPeerConnectSeconds OBJECT-TYPE 559 SYNTAX Counter 560 ACCESS read-only 561 STATUS mandatory 562 DESCRIPTION 563 "The number of seconds a call to this peer 564 was active. This counter will be 565 incremented by one for every second a 566 connection to a peer was open. If two calls 567 568 569 570 571 572 are open at the same time, one second of 573 elapsed real time will results in two 574 seconds of connect time." 575 ::= { mioxPeerEntry 5 } 576 577 mioxPeerX25CallParamId OBJECT-TYPE 578 SYNTAX InstancePointer 579 ACCESS read-write 580 STATUS mandatory 581 DESCRIPTION 582 "The instance of the index object in the 583 x25CallParmTable from RFC 1382 for the X.25 584 call parameters used to communicate with the 585 remote host. The well known value {0 0} 586 indicates no call parameters specified." 587-- DEFVAL { {0 0} } 588 ::= { mioxPeerEntry 6 } 589 590 mioxPeerEnAddr OBJECT-TYPE 591 SYNTAX OCTET STRING (SIZE (0..128)) 592 ACCESS read-write 593 STATUS mandatory 594 DESCRIPTION 595 "The Encapsulation address of the remote 596 host mapped by this table entry. A length 597 of zero indicates the remote IP address is 598 unknown or unspecified for use as a PLE 599 default. 600 601 The first octet of this object contains the 602 encapsulation type, the remaining octets 603 contain an address of that type. Thus for 604 an IP address, the length will be five 605 octets, the first octet will contain 204 606 (hex CC), and the last four octets will 607 contain the IP address. For a snap 608 encapsulation, the first byte would be 128 609 (hex 80) and the rest of the octet string 610 would have the snap header." 611 DEFVAL { ''h } 612 ::= { mioxPeerEntry 7 } 613 614 mioxPeerX121Address OBJECT-TYPE 615 SYNTAX X121Address 616 ACCESS read-write 617 STATUS mandatory 618 DESCRIPTION 619 "The X.25 address of the remote host mapped 620 621 622 623 624 625 by this table entry. A zero length string 626 indicates the X.25 address is unspecified 627 for use as the PLE default." 628 DEFVAL { ''h } 629 ::= { mioxPeerEntry 8 } 630 631 -- Systems can claim conformance to this MIB without 632 -- implementing sets to mioxPeerX25CircuitId. 633 -- However systems that use PVCs with RFC1356 634 -- are encouraged to implement sets. 635 mioxPeerX25CircuitId OBJECT-TYPE 636 SYNTAX InstancePointer 637 ACCESS read-write 638 STATUS mandatory 639 DESCRIPTION 640 "This object identifies the instance of the 641 index for the X.25 circuit open to the peer 642 mapped by this table entry. The well known 643 value {0 0} indicates no connection 644 currently active. For multiple connections, 645 this identifies the index of a multiplexing 646 table entry for the connections. This can 647 only be written to configure use of PVCs 648 which means the identified circuit table 649 entry for a write must be a PVC." 650-- DEFVAL { {0 0} } 651 ::= { mioxPeerEntry 9 } 652 653 mioxPeerDescr OBJECT-TYPE 654 SYNTAX DisplayString (SIZE (0..255)) 655 ACCESS read-write 656 STATUS mandatory 657 DESCRIPTION 658 "This object returns any identification 659 information about the peer. An agent may 660 supply the comment information found in the 661 configuration file entry for this peer. A 662 zero length string indicates no information 663 available." 664-- DEFVAL { ''h } 665 ::= { mioxPeerEntry 10 } 666 667 668 669 -- ########################################################### 670 -- Peer Encapsulation Table 671 -- ########################################################### 672 673 674 675 676 677 678 mioxPeerEncTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF MioxPeerEncEntry 680 ACCESS not-accessible 681 STATUS mandatory 682 DESCRIPTION 683 "This table contains the list of 684 encapsulations used to communicate with a 685 peer. This table has two indexes, the first 686 identifies the peer, the second 687 distinguishes encapsulation types. 688 689 The first index identifies the corresponding 690 entry in the mioxPeerTable. The second 691 index gives the priority of the different 692 encapsulations. 693 694 The encapsulation types are ordered in 695 priority order. For calling a peer, the 696 first entry (mioxPeerEncIndex of 1) is tried 697 first. If the call doesn't succeed because 698 the remote host clears the call due to 699 incompatible call user data, the next entry 700 in the list is tried. Each entry is tried 701 until the list is exhausted. 702 703 For answering a call, the encapsulation type 704 requested by the peer must be found the list 705 or the call will be refused. If there are 706 no entries in this table for a peer, all 707 call requests from the peer will be refused. 708 709 Objects in this table can only be set when 710 the mioxPeerStatus object with the same 711 index has a value of underCreation. When 712 that status object is set to invalid and 713 deleted, the entry in this table with that 714 peer index must also be deleted." 715 ::= { mioxPeer 2 } 716 717 mioxPeerEncEntry OBJECT-TYPE 718 SYNTAX MioxPeerEncEntry 719 ACCESS not-accessible 720 STATUS mandatory 721 DESCRIPTION 722 "Per connection information." 723 INDEX { mioxPeerIndex, mioxPeerEncIndex} 724 ::= { mioxPeerEncTable 1 } 725 726 727 728 729 730 731 MioxPeerEncEntry ::= SEQUENCE { 732 mioxPeerEncIndex 733 PositiveInteger, 734 mioxPeerEncType 735 INTEGER 736 } 737 738 mioxPeerEncIndex OBJECT-TYPE 739 SYNTAX PositiveInteger 740 ACCESS read-only 741 STATUS mandatory 742 DESCRIPTION 743 "The second index in the table which 744 distinguishes different encapsulation 745 types." 746 ::= { mioxPeerEncEntry 1 } 747 748 mioxPeerEncType OBJECT-TYPE 749 SYNTAX INTEGER (0..256) 750 ACCESS read-write 751 STATUS mandatory 752 DESCRIPTION 753 "The value of the encapsulation type. For 754 IP encapsulation this will have a value of 755 204 (hex CC). For SNAP encapsulated 756 packets, this will have a value of 128 (hex 757 80). For CLNP, ISO 8473, this will have a 758 value of 129 (hex 81). For ES-ES, ISO 9542, 759 this will have a value of 130 (hex 82). A 760 value of 197 (hex C5) identifies the Blacker 761 X.25 encapsulation. A value of 0, 762 identifies the Null encapsulation. 763 764 This value can only be written when the 765 mioxPeerStatus object with the same 766 mioxPeerIndex has a value of underCreation. 767 Setting this object to a value of 256 768 deletes the entry. When deleting an entry, 769 all other entries in the mioxPeerEncTable 770 with the same mioxPeerIndex and with an 771 mioxPeerEncIndex higher then the deleted 772 entry, will all have their mioxPeerEncIndex 773 values decremented by one." 774 ::= { mioxPeerEncEntry 2 } 775 776 -- ########################################################### 777 778 END 779