idnits 2.17.1 draft-ietf-ion-scsp-atmarp-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-27) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 16 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 17 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 115: '...buted ATMARP servers. This MIB MUST be...' RFC 2119 keyword, line 182: '...ion (Classic IP). These objects SHOULD...' RFC 2119 keyword, line 256: '...er ATM operation. These objects SHOULD...' RFC 2119 keyword, line 545: '... then the HFSM MUST be considered t...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 94 has weird spacing: '... Server and i...' == Line 236 has weird spacing: '...ponding scspS...' == Line 545 has weird spacing: '...sidered to be...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '2' on line 112 looks like a reference -- Missing reference section? '3' on line 112 looks like a reference -- Missing reference section? '1' on line 107 looks like a reference -- Missing reference section? '5' on line 57 looks like a reference -- Missing reference section? '6' on line 57 looks like a reference -- Missing reference section? '7' on line 57 looks like a reference -- Missing reference section? '8' on line 67 looks like a reference -- Missing reference section? '9' on line 71 looks like a reference -- Missing reference section? '10' on line 72 looks like a reference -- Missing reference section? '11' on line 111 looks like a reference -- Missing reference section? '12' on line 111 looks like a reference -- Missing reference section? '13' on line 111 looks like a reference -- Missing reference section? '4' on line 112 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 6 warnings (==), 15 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internetworking Over NBMA Cliff X. Wang 3 Internet-Draft Colin Verrilli 4 IBM Corporation 5 James Luciani 6 Bay Networks 8 Definitions of Managed Objects for ATMARP dependent 9 Server Cache Synchronization Protocol Using SMIv2 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, 15 and its Working Groups. Note that other groups may also distribute 16 working documents as Internet Drafts. 18 Internet Drafts are draft documents valid for a maximum of six 19 months. Internet Drafts may be updated, replaced, or obsoleted by 20 other documents at any time. It is not appropriate to use Internet 21 Drafts as reference material or to cite them other than as a "working 22 draft" or "work in progress." 24 To view the entire list of current Internet-Drafts, please check the 25 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 26 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Europe), 27 munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or 28 ftp.isi.edu (US West Coast). 30 Abstract 32 This document defines the ATMARP[2], [3] protocol dependent part 33 Management Information Base (MIB) for supporting Server Cache 34 Synchronization Protocol (SCSP)[1]. SCSP is used to solve the 35 generalized cache synchronization/cache-replication problem for 36 distributed protocol entities. In a client/server paradigm, SCSP 37 synchronizes caches (or a portion of the caches) of a set of server 38 entities of a particular protocol which are bound to a Server Group. 40 The MIB module specified in this document follows the Structure of 41 Management Information (SMI) for the Simple Network Management 42 Protocol (SNMP) Version 2. 44 1. Introduction 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management protocols in 48 the Internet community. In particular, it describes managed objects 49 for hosts or routers that use Server Cache Synchronization Protocol 50 (SCSP) to synchronize caches among the distributed ATMARP servers in 51 a server group. MIB objects are defined to enable management of the 52 Local server (LS) and the cache synchronization/replication between 53 LS and its associated Directly Connected Servers (DCS). 55 2. The SNMPV2 Network Management Framework 57 IETF RFC 1157 [5], RFC 1213 [6], and RFC 1902 [7] form the three 58 major components of the SNMPv2 Network Management Framework. 60 o RFC 1902 specifies the SMI, which is the mechanisms used for 61 describing and naming objects for the purpose of management. 63 o RFC 1213 defines the second version of the Management Information 64 Base (MIB-II), which is the core set of managed objects for the 65 TCP/IP based Internets. 67 o RFC 1157 and/or RFC 1905 [8] specifies the protocol operations 68 for SNMPV2, with respect to the to the sending and receiving of 69 SNMP managed information. 71 In addition, RFC 1903 [9] defines Textual conventions for SNMPv2 and 72 RFC 1904 [10] specifies the conformance statements for SNMPv2. 74 The SNMPv2 Framework allows new objects to be defined for the purpose 75 of experimentation and evaluation. 77 2.1 Object Definition 79 Managed objects are accessed via a virtual information store, termed 80 the Management Information Base or MIB. Objects in the MIB are 81 defined using the subset of Abstract Syntax Notation One (ASN.1) 82 defined in the SMI. In particular, each object type is named by an 83 OBJECT IDENTIFIER, an administratively assigned name. The object 84 type together with an object instance serves to uniquely identify a 85 specific instantiation of the object. For human convenience, we 86 often use a textual string, termed the descriptor, to refer to the 87 object type. 89 3. Overview 91 SCSP contains three sub protocols: the "Hello" protocol, the "Cache 92 Alignment" Protocol, and the "Cache State Update" protocol. The Hello 93 protocol is used to monitor the status of the connections between the 94 Local Server and its Directly Connected Servers. The "Cache 95 Alignment" protocol is used to synchronize the cache of an 96 initializing LS with the cache of its DCSs. The "Cache State Update" 97 protocol is used to update the state of cache entries once the 98 servers are synchronized. 100 Synchronization is performed on a per Server Group / Protocol basis. 101 That is, a separate instance of the protocol is run for each SG in 102 the box. Therefore, the SGID/PID pair uniquely identifies an 103 instance of SCSP. Furthermore, A separate instance of the "Hello" 104 and "Cache Alignment" protocol are maintained for each DCS of the 105 Server Group. State machines exist to execute the protocol 106 independently for each DCS session. For more information, refer to 107 [1]. 109 SCSP is used to synchronize distributed servers running a 110 client/server protocol. Currently SCSP support for Classic IP 111 (RFC2225 )[11], MARS (RFC 2022)[12], and NHRP (RFC 2332)[13] has been 112 defined in the protocol dependent part of SCSP [2], [3], [4]. 114 This MIB provides specific information for management of SCSP when it 115 applies to synchronize distributed ATMARP servers. This MIB MUST be 116 used along with the protcol independent SCSP MIB. This ATMARP 117 protocol dependent SCSP MIB carries management objects related to 118 SCSP application to ATMARP, such as ATMARP server's IP address, 119 server's ATM address, etc. The MIB is divided into server group 120 table, local server table, peer server table, and HFSM table. 122 4. Definition of the SCSP ATMARP protocol dependent MIB 124 SCSPATMARP-MIB DEFINITIONS ::= BEGIN 126 IMPORTS 127 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 128 experimental, Integer32, IpAddress, Counter32 129 FROM SNMPv2-SMI 130 TEXTUAL-CONVENTION, RowStatus 131 FROM SNMPv2-TC 132 MODULE-COMPLIANCE, OBJECT-GROUP 133 FROM SNMPv2-CONF 134 AtmAddr, AtmConnKind 135 FROM ATM-TC-MIB 137 scspServerGroupID, scspServerGroupPID, scspLSID, scspDCSID, 138 ScspHFSMStateType, SCSPVPIInteger,SCSPVCIInteger 139 FROM SCSP-MIB 140 ; 142 scspAtmarpMIB MODULE-IDENTITY 143 LAST-UPDATED "9808020000Z" -- October 10, 1998 144 ORGANIZATION "IETF Internetworking Over NBMA Working Group (ion)" 145 CONTACT-INFO 146 "Jim Luciani (jliciani@BayNetworks.com 147 Bay Networks 149 Cliff X. Wang (cliff_wang@vnet.ibm.com) 150 Colin Verrilli (verrilli@vnet.ibm.com) 151 IBM Corp." 153 DESCRIPTION 154 "This module defines a portion of the management 155 information base (MIB) for managing Server Cache 156 Synchronizatio protocol applied to ATMARP servers." 157 ::= { experimental 2002 } 159 -- ***************************************************** 160 -- Top Level structure of the SCSP MIB 161 -- ***************************************************** 163 scspAtmarpObjects OBJECT IDENTIFIER ::= { scspAtmarpMIB 1} 164 scspAtmarpNotifications OBJECT IDENTIFIER ::= { scspAtmarpMIB 2} 165 scspAtmarpConformance OBJECT IDENTIFIER ::= { scspAtmarpMIB 3} 167 -- ***************************************************** 168 -- SCSP MIB Objects 169 -- ***************************************************** 171 -- ***************************************************** 172 -- SCSP atmarp Server Group Objects 173 -- ***************************************************** 175 scspAtmarpServerGroupTable OBJECT-TYPE 176 SYNTAX SEQUENCE OF ScspAtmarpServerGroupEntry 177 MAX-ACCESS not-accessible 178 STATUS current 179 DESCRIPTION 180 "The objects defined in this table are used to for the 181 management of SCSP server groups with application to 182 IP over ATM operation (Classic IP). These objects SHOULD 183 be used along with the protocol independent part objects 184 to support the management of the SCSP protocol applied 185 to synchronizing the atmarp servers in a LIS. 187 There is one entry in this table for each server group. 188 In the case of IP over ATM, each server group corresponds to 189 a Logical IP Subnet." 190 ::= { scspAtmarpObjects 1} 192 scspAtmarpServerGroupEntry OBJECT-TYPE 193 SYNTAX ScspAtmarpServerGroupEntry 194 MAX-ACCESS not-accessible 195 STATUS current 196 DESCRIPTION 197 "Information about SCSP server group running IP over ATM 198 operation. This table is indexed by scspServerGroupID and 199 scspServerGroupPID. The two indeces point to a corresponding 200 entry in the scspServerGroupTable." 201 INDEX {scspServerGroupID, scspServerGroupPID} 202 ::= { scspAtmarpServerGroupTable 1} 204 ScspAtmarpServerGroupEntry ::= 205 SEQUENCE { 206 scspAtmarpServerGroupNetMask IpAddress, 207 scspAtmarpServerGroupSubnetAddr IpAddress, 208 scspAtmarpServerGroupRowStatus RowStatus } 210 scspAtmarpServerGroupNetMask OBJECT-TYPE 211 SYNTAX IpAddress 212 MAX-ACCESS read-only 213 STATUS current 214 DESCRIPTION 215 "The subnet mask associated with this Server Group." 216 ::= { scspAtmarpServerGroupEntry 1 } 218 scspAtmarpServerGroupSubnetAddr OBJECT-TYPE 219 SYNTAX IpAddress 220 MAX-ACCESS read-only 221 STATUS current 222 DESCRIPTION 223 "The IP subnet address associated with this Server Group." 224 ::= { scspAtmarpServerGroupEntry 2 } 226 scspAtmarpServerGroupRowStatus OBJECT-TYPE 227 SYNTAX RowStatus 228 MAX-ACCESS read-create 229 STATUS current 230 DESCRIPTION 231 "This object allows Atmarp Server Group Table entries to be 232 created and deleted from the scspAtmarpServerGroupTable. Note 233 that scspAtmarpServerGroupTable entry creation and deletion 234 is coupled with scspServerGroupTable entry creation and 235 deletion. A scspAtmarpServerGroupTable entry cannot be 236 created until its corresponding scspServerGroupTable entry 237 is created. When a scspServerGroupTable entry is deleted, 238 it also removes the corresponding scspAtmarpServerGroupTable 239 entry." 240 REFERENCE 241 "RFC 1903, 'Textual Conventions for version 2 of the Simple 242 Network Management Protocol (SNMPv2).'" 243 ::= { scspAtmarpServerGroupEntry 3 } 245 -- **************************************************** 246 -- SCSP atmarp Local Server Objects 247 -- **************************************************** 249 scspAtmarpLSTable OBJECT-TYPE 250 SYNTAX SEQUENCE OF ScspAtmarpLSEntry 251 MAX-ACCESS not-accessible 252 STATUS current 253 DESCRIPTION 254 "The objects defined in this table are used to for the 255 management of the Atmarp Local server in a SCSP server group 256 for IP over ATM operation. These objects SHOULD 257 be used along with the protocol independent part objects 258 to support the management of the SCSP protocol applied 259 to synchronizing the IP over ATM servers." 260 ::= { scspAtmarpObjects 2} 262 scspAtmarpLSEntry OBJECT-TYPE 263 SYNTAX ScspAtmarpLSEntry 264 MAX-ACCESS not-accessible 265 STATUS current 266 DESCRIPTION 267 "Information about Atmarp Local Server in a SCSP server 268 group. This table is indexed by scspServerGroupID, 269 scspServerGroupPID, and scspLSID. The three indeces point 270 to a corresponding entry in the scspLSTable." 271 INDEX {scspServerGroupID, 272 scspServerGroupPID, 273 scspLSID 274 } 275 ::= { scspAtmarpLSTable 1} 277 ScspAtmarpLSEntry ::= 278 SEQUENCE { 279 scspAtmarpLSLSIPAddr IpAddress, 280 scspAtmarpLSLSAtmAddr AtmAddr, 281 scspAtmarpLSRowStatus RowStatus 282 } 284 scspAtmarpLSLSIPAddr OBJECT-TYPE 285 SYNTAX IpAddress 286 MAX-ACCESS read-only 287 STATUS current 288 DESCRIPTION 289 "The IP address of the Atmarp Local Server. Since an Atmarp 290 server does not have to be assigned an IP address, this 291 object is optional." 292 ::= { scspAtmarpLSEntry 1 } 294 scspAtmarpLSLSAtmAddr OBJECT-TYPE 295 SYNTAX AtmAddr 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The ATM address of the Atmarp Local Server." 300 ::= { scspAtmarpLSEntry 2 } 302 scspAtmarpLSRowStatus OBJECT-TYPE 303 SYNTAX RowStatus 304 MAX-ACCESS read-create 305 STATUS current 306 DESCRIPTION 307 "This object allows Atmarp Local Server Table entries to be 308 created and deleted from the scspAtmarpLSTable. Note 309 that scspAtmarpLSTable entry creation and deletion 310 is coupled with scspLSTable entry creation and deletion. 311 A scspAtmarpLSTable entry cannot be created until 312 its corresponding scspLSTable entry is created. 313 When a scspLSTable entry is deleted, it also removes 314 the corresponding scspAtmarpLSTable entry." 315 ::= { scspAtmarpLSEntry 3 } 317 -- *************************************************** 318 -- SCSP Atmarp Peer Objects 319 -- *************************************************** 321 scspAtmarpPeerTable OBJECT-TYPE 322 SYNTAX SEQUENCE OF ScspAtmarpPeerEntry 323 MAX-ACCESS not-accessible 324 STATUS current 325 DESCRIPTION 326 "The objects defined in this table are used to for the 327 management of the ATMARP sever peers." 328 ::= { scspAtmarpObjects 3} 330 scspAtmarpPeerEntry OBJECT-TYPE 331 SYNTAX ScspAtmarpPeerEntry 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "Information about each peer ATMARP server participated 336 in the scsp Server group. The table is indexed by 337 scspServerGroupID, scspServerGroupPID, and 338 scspAtmarpPeerIndex." 339 INDEX { scspServerGroupID, 340 scspServerGroupPID, 341 scspAtmarpPeerIndex 342 } 343 ::= { scspAtmarpPeerTable 1} 345 ScspAtmarpPeerEntry ::= 346 SEQUENCE { 347 scspAtmarpPeerIndex Integer32, 348 scspAtmarpPeerIPAddr IpAddress, 349 scspAtmarpPeerAtmAddr AtmAddr, 350 scspAtmarpPeerVCType AtmConnKind, 351 scspAtmarpPeerVPI SCSPVPIInteger, 352 scspAtmarpPeerVCI SCSPVCIInteger, 353 scspAtmarpPeerDCSID OCTET STRING(SIZE(0..63)), 354 scspAtmarpPeerRowStatus RowStatus 356 } 358 scspAtmarpPeerIndex OBJECT-TYPE 359 SYNTAX Integer32 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The table index of the peer Atmarp server table." 364 ::= { scspAtmarpPeerEntry 1 } 366 scspAtmarpPeerIPAddr OBJECT-TYPE 367 SYNTAX IpAddress 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The IP address of the peer Atmarp server. Since an Atmarp 372 server does not have to be assigned an IP address, 373 this object is optional." 374 ::= { scspAtmarpPeerEntry 2 } 376 scspAtmarpPeerAtmAddr OBJECT-TYPE 377 SYNTAX AtmAddr 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The ATM address of the Peer. If SVC is used between LS and 382 Peer, Peer's ATM address should be valid. However, if PVC is 383 used instead SVC, the Peer's ATM address may be a Null OCTET 384 STRING." 385 ::= { scspAtmarpPeerEntry 3 } 387 scspAtmarpPeerVCType OBJECT-TYPE 388 SYNTAX AtmConnKind 389 MAX-ACCESS read-only 390 STATUS current 391 DESCRIPTION 392 "The type of the virtual circuit between LS and Peer." 393 ::= { scspAtmarpPeerEntry 4 } 395 scspAtmarpPeerVPI OBJECT-TYPE 396 SYNTAX SCSPVPIInteger 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The VPI value for the virtual circuit between LS and Peer." 401 ::= { scspAtmarpPeerEntry 5 } 403 scspAtmarpPeerVCI OBJECT-TYPE 404 SYNTAX SCSPVCIInteger 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The VCI value for the virtual circuit between LS and Peer." 409 ::= { scspAtmarpPeerEntry 6 } 411 scspAtmarpPeerDCSID OBJECT-TYPE 412 SYNTAX OCTET STRING(SIZE(0..63)) 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The DCS ID for this peer. When the peer tabel is created, 417 DCS ID may not have been discovered. Tt is set to a 418 Null string. It will be update when the DCS ID 419 associated with this peer (ATM address) is discovered." 420 ::= { scspAtmarpPeerEntry 7 } 422 scspAtmarpPeerRowStatus OBJECT-TYPE 423 SYNTAX RowStatus 424 MAX-ACCESS read-create 425 STATUS current 426 DESCRIPTION 427 "This object allows Atmarp Peer table entries to be created 428 and deleted from the scspAtmarpPeerTable. Note that 429 scspAtmarpPeerTable entry is created when a peer is 430 configured loaclly or when a peer not previously 431 configured connects to LS." 432 REFERENCE 433 "RFC 1903, 'Textual Conventions for version 2 of the Simple 434 Network Management Protocol (SNMPv2).'" 435 ::= { scspAtmarpPeerEntry 8 } 437 -- **************************************************** 438 -- SCSP atmarp HFSM Objects 439 -- **************************************************** 441 scspAtmarpHFSMTable OBJECT-TYPE 442 SYNTAX SEQUENCE OF ScspAtmarpHFSMEntry 443 MAX-ACCESS not-accessible 444 STATUS current 445 DESCRIPTION 446 "The objects defined in this table are used to for the 447 management of the HFSM between the LS and the DCS." 448 ::= { scspAtmarpObjects 4} 450 scspAtmarpHFSMEntry OBJECT-TYPE 451 SYNTAX ScspAtmarpHFSMEntry 452 MAX-ACCESS not-accessible 453 STATUS current 454 DESCRIPTION 455 "Information about SCSP HFSM session between the LS and 456 its HFSMs. The table is indexed by 457 scspServerGroupID, scspServerGroupPID, and 458 scspAtmarpPeerIndex." 459 INDEX { scspServerGroupID, 460 scspServerGroupPID, 461 scspAtmarpPeerIndex 462 } 463 ::= { scspAtmarpHFSMTable 1} 465 ScspAtmarpHFSMEntry ::= 466 SEQUENCE { 467 scspHFSMHFSMState ScspHFSMStateType, 468 scspHFSMHelloIn Counter32, 469 scspHFSMHelloOut Counter32, 470 scspHFSMHelloInvalidIn Counter32, 471 scspHFSMHelloInterval Integer32, 472 scspHFSMDeadFactor Integer32, 473 scspHFSMFamilyID Integer32, 474 scspAtmarpHFSMRowStatus RowStatus 475 } 477 scspHFSMHFSMState OBJECT-TYPE 478 SYNTAX ScspHFSMStateType 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The current state of the Hello Finite State Machine. 483 The allowable states are: 484 down(1), 485 waiting(2), 486 uniConn(3), 487 biConn(4)." 488 REFERENCE 489 "SCSP draft, Section 2.1" 490 ::= { scspAtmarpHFSMEntry 1 } 492 scspHFSMHelloIn OBJECT-TYPE 493 SYNTAX Counter32 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "The number of 'Hello' messages received from this HFSM." 498 ::= { scspAtmarpHFSMEntry 2 } 500 scspHFSMHelloOut OBJECT-TYPE 501 SYNTAX Counter32 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "The number of 'Hello' messages sent from LS to this 506 HFSM." 507 ::= { scspAtmarpHFSMEntry 3 } 509 scspHFSMHelloInvalidIn OBJECT-TYPE 510 SYNTAX Counter32 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The number of invalid 'Hello' messages received from 515 this HFSM. Possible message errors include: 516 Hello message when the HFSM is in 'Down' state; 517 Hello message is too short to contain the number of 518 Receiver ID records specified in the header, etc. 519 Other common errors include failed authentication if 520 applicable, errors in the message fields, etc." 521 ::= { scspAtmarpHFSMEntry 4 } 523 scspHFSMHelloInterval OBJECT-TYPE 524 SYNTAX Integer32 (0..65535) 525 MAX-ACCESS read-create 526 STATUS current 527 DESCRIPTION 528 "This object contains the value for HelloInterval with 529 the associated HFSM. It is the time (in seconds) 530 between sending of consecutive Hello messages from the 531 HFSM." 532 ::= { scspAtmarpHFSMEntry 5 } 534 scspHFSMDeadFactor OBJECT-TYPE 535 SYNTAX Integer32 (0..65535) 536 MAX-ACCESS read-create 537 STATUS current 538 DESCRIPTION 539 "This object contains the value for DeadFactor with 540 this associated server. The DeadFactor along with 541 HelloInterval are contained in 'Hello' messages sent 542 from this HFSM. If 'Hello' messages are not received 543 from this HFSM within the time out interval 544 'HelloInterval*DeadFactor' (in seconds), 545 then the HFSM MUST be considered to be stalled." 546 ::= { scspAtmarpHFSMEntry 6 } 548 scspHFSMFamilyID OBJECT-TYPE 549 SYNTAX Integer32 (0..65535) 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The family ID is used to refer an aggregate of 554 Protocol ID/SGID pairs. Only a single HFSM is 555 run for all Protocol ID/SGID pairs assigned to 556 a Family ID. When the HFSM is not shared by an 557 aggregate of Protocol ID/SGID pairs, this 558 object should be set to 0." 559 REFERENCE 560 "SCSP draft, Sec.2 and Sec. B.2.5" 561 ::= { scspAtmarpHFSMEntry 7 } 563 scspAtmarpHFSMRowStatus OBJECT-TYPE 564 SYNTAX RowStatus 565 MAX-ACCESS read-create 566 STATUS current 567 DESCRIPTION 568 "This object allows Atmarp HFSM table entries to be created 569 and deleted from the scspAtmarpHFSMTable. Note that 570 scspAtmarpHFSMTable entry creation and deletion is 571 closely coupled with scspHFSMTable entry creation. 572 A scspAtmarpHFSMTable entry cannot be created until 573 its corresponding scspHFSMTable entry is created. 574 When a scspHFSMTable entry is deleted, it also removes 575 the corresponding scspAtmarpHFSMTable entry." 576 REFERENCE 577 "RFC 1903, 'Textual Conventions for version 2 of the Simple 578 Network Management Protocol (SNMPv2).'" 579 ::= { scspAtmarpHFSMEntry 8 } 581 -- *********************************************************** 582 -- Notifications 583 -- *********************************************************** 585 scspHFSMDown NOTIFICATION-TYPE 586 OBJECTS { 587 scspServerGroupID, 588 scspServerGroupPID, 589 scspAtmarpPeerIndex 590 } 591 STATUS current 592 DESCRIPTION 593 "The Hello Finite State Machine associated with this 594 LS/DCS pair enters 'Down' state." 595 ::= { scspAtmarpNotifications 1 } 597 scspHFSMWaiting NOTIFICATION-TYPE 598 OBJECTS { 599 scspServerGroupID, 600 scspServerGroupPID, 601 scspAtmarpPeerIndex 602 } 603 STATUS current 604 DESCRIPTION 605 "The Hello Finite State Machine associated with 606 this LS/DCS pair enters 'Waiting' state." 607 ::= { scspAtmarpNotifications 2 } 609 scspHFSMBiConn NOTIFICATION-TYPE 610 OBJECTS { 611 scspServerGroupID, 612 scspServerGroupPID, 613 scspAtmarpPeerIndex 614 } 615 STATUS current 616 DESCRIPTION 617 "The Hello Finite State Machine associated with this 618 LS/DCS pair enters 'Bidirectional connection' state." 619 ::= { scspAtmarpNotifications 3 } 621 -- ********************************************************* 622 -- Conformance Definitions 623 -- ********************************************************* 625 scspAtmarpCompliances OBJECT IDENTIFIER ::={scspAtmarpConformance 1} 626 scspAtmarpGroups OBJECT IDENTIFIER ::={scspAtmarpConformance 2} 628 --********************************************************** 629 -- SCSP MIB Compliance Statements 630 --********************************************************** 632 scspAtmarpCompliance MODULE-COMPLIANCE 633 STATUS current 634 DESCRIPTION 635 "The compliance statement for entities that are required 636 for the management of SCSP when applied to ATMARP servers." 637 MODULE 638 MANDATORY-GROUPS { 639 scspAtmarpGroup 640 } 641 ::= { scspAtmarpCompliances 1 } 643 scspAtmarpGroup OBJECT-GROUP 644 OBJECTS { 645 scspAtmarpServerGroupNetMask, 646 scspAtmarpServerGroupSubnetAddr, 647 scspAtmarpLSLSIPAddr, 648 scspAtmarpLSLSAtmAddr, 649 scspAtmarpPeerIndex, 650 scspAtmarpPeerAtmAddr, 651 scspAtmarpPeerVCType, 652 scspAtmarpPeerVPI, 653 scspAtmarpPeerVCI, 654 scspAtmarpPeerDCSID, 655 scspHFSMHFSMState, 656 scspHFSMHelloIn, 657 scspHFSMHelloOut, 658 scspHFSMHelloInvalidIn, 659 scspHFSMHelloInterval, 660 scspHFSMDeadFactor, 661 scspHFSMFamilyID 662 } 663 STATUS current 664 DESCRIPTION 665 "This group is mandatory when Atmarp is the client/server 666 protocol running SCSP." 667 ::= { scspAtmarpGroups 1 } 669 END 671 Acknowledgments 673 Reference 675 Authors' Addresses 677 Cliff X. Wang 678 IBM, Networking Hardware Division 679 Dept. MZDA/B664 680 P.O. Box 12195 681 Research Triangle Park, NC 27709 682 phone: +1-919-486-1255 683 email: cxwang@cxwang.ibm.com 685 Colin B. Verrilli 686 IBM, Networking Hardware Division 687 Dept. M6LA/B664 688 P.O. Box 12195 689 Research Triangle Park, NC 27709 690 phone: +1-919-254-9936 691 email: verrilli@raleigh.ibm.com 693 James V. Luciani 694 Bay Networks, Inc. 695 3 Federal Street, BL3-04 696 Billerica, MA 01821 697 phone: +1-508-916-4734 698 email: luciani@baynetworks.com