idnits 2.17.1 draft-ietf-ion-scsp-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-25) 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 22 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 23 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], [4], [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 464: '...s), then the DCS MUST consider the LS ...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 102 has weird spacing: '... Server and i...' -- 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? '1' on line 938 looks like a reference -- Missing reference section? '2' on line 941 looks like a reference -- Missing reference section? '3' on line 944 looks like a reference -- Missing reference section? '4' on line 947 looks like a reference -- Missing reference section? '5' on line 950 looks like a reference -- Missing reference section? '6' on line 953 looks like a reference -- Missing reference section? '7' on line 956 looks like a reference -- Missing reference section? '8' on line 960 looks like a reference -- Missing reference section? '9' on line 964 looks like a reference -- Missing reference section? '10' on line 80 looks like a reference -- Missing reference section? '11' on line 129 looks like a reference -- Missing reference section? '12' on line 119 looks like a reference -- Missing reference section? '13' on line 119 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 4 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 Oct 10th, 1998 10 Definitions of Managed Objects for 11 Server Cache Synchronization Protocol Using SMIv2 13 Status of this Memo 15 This document is an Internet Draft. Internet Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its Areas, 17 and its Working Groups. Note that other groups may also distribute 18 working documents as Internet Drafts. 20 Internet Drafts are draft documents valid for a maximum of six 21 months. Internet Drafts may be updated, replaced, or obsoleted by 22 other documents at any time. It is not appropriate to use Internet 23 Drafts as reference material or to cite them other than as a "working 24 draft" or "work in progress." 26 Please check the I-D abstract listing contained in each Internet 27 Draft directory to learn the current status of this or any Internet 28 Draft. Distribution of this document is unlimited. 30 Abstract 32 This document defines the Management Information Base (MIB) for 33 supporting Server Cache Synchronization Protocol (SCSP)[1], [2], [3], 34 [4]. SCSP is used to solve the generalized cache 35 synchronization/cache-replication problem for distributed protocol 36 entities. In a client/server paradigm, SCSP synchronizes caches (or a 37 portion of the caches) of a set of server entities of a particular 38 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 Revision History 46 April 1998, removed Hello finite state machine related entries from 47 DCS table, notification group, and conformance definition. Hello 48 finite state machine related entries will be placed in the protocol 49 dependent MIB, where link layer information can be grouped. Move 50 retransmit related entries from DCS to LS table. 52 1. Introduction 54 This memo defines an experimental portion of the Management 55 Information Base (MIB) for use with network management protocols in 56 the Internet community. In particular, it describes managed objects 57 for hosts or routers that use Server Cache Synchronization Protocol 58 (SCSP) to synchronize caches among the distributed servers in a 59 server group. MIB objects are defined to enable management of the 60 Local server (LS) and the cache synchronization/replication between 61 LS and its associated Directly Connected Servers (DCS). 63 2. The SNMPV2 Network Management Framework 65 IETF RFC 1157 [5], RFC 1213 [6], and RFC 1902 [7] form the three 66 major components of the SNMPv2 Network Management Framework. 68 o RFC 1902 specifies the SMI, which is the mechanisms used for 69 describing and naming objects for the purpose of management. 71 o RFC 1213 defines the second version of the Management Information 72 Base (MIB-II), which is the core set of managed objects for the 73 TCP/IP based Internets. 75 o RFC 1157 and/or RFC 1905 [8] specifies the protocol operations 76 for SNMPV2, with respect to the to the sending and receiving of 77 SNMP managed information. 79 In addition, RFC 1903 [9] defines Textual conventions for SNMPv2 and 80 RFC 1904 [10] specifies the conformance statements for SNMPv2. 82 The SNMPv2 Framework allows new objects to be defined for the purpose 83 of experimentation and evaluation. 85 2.1 Object Definition 87 Managed objects are accessed via a virtual information store, termed 88 the Management Information Base or MIB. Objects in the MIB are 89 defined using the subset of Abstract Syntax Notation One (ASN.1) 90 defined in the SMI. In particular, each object type is named by an 91 OBJECT IDENTIFIER, an administratively assigned name. The object 92 type together with an object instance serves to uniquely identify a 93 specific instantiation of the object. For human convenience, we 94 often use a textual string, termed the descriptor, to refer to the 95 object type. 97 3. Overview 99 SCSP contains three sub protocols: the "Hello" protocol, the "Cache 100 Alignment" Protocol, and the "Cache State Update" protocol. The Hello 101 protocol is used to monitor the status of the connections between the 102 Local Server and its Directly Connected Servers. The "Cache 103 Alignment" protocol is used to synchronize the cache of an 104 initializing LS with the cache of its DCSs. The "Cache State Update" 105 protocol is used to update the state of cache entries once the 106 servers are synchronized. 108 Synchronization is performed on a per Server Group / Protocol basis. 109 That is, a separate instance of the protocol is run for each SG in 110 the box. Therefore, the SGID/PID pair uniquely identifies an 111 instance of SCSP. Furthermore, A separate instance of the "Hello" 112 and "Cache Alignment" protocol are maintained for each DCS of the 113 Server Group. State machines exist to execute the protocol 114 independently for each DCS session. For more information, refer to 115 [1]. 117 SCSP is used to synchronize distributed servers running a 118 client/server protocol. Currently SCSP support for Classic IP (RFC 119 2225)[11], MARS (RFC 2022)[12], and NHRP (RFC 2332)[13] has been 120 defined in the protocol dependent part of SCSP [2], [3], [4]. 122 The following terms are defined in the SCSP definition and used 123 frequently. They are included here for reference: 125 Server Group (SG) 126 The SCSP synchronizes caches (or a portion of the caches) of a 127 set of server entities which are bound to a SG through some 128 means (e.g., all servers belonging to a Logical IP Subnet 129 (LIS)[11]). Thus a SG is just a grouping of servers around 130 some commonality. 132 SGID - Server Group ID 133 This ID is a 16 bit identification field that uniquely 134 identifies the instance client/server protocol for which the 135 servers of the SG are being synchronized. This implies that 136 multiple instances of the same protocol may be in operation at 137 the same time and have their servers synchronized independently 138 of each other. 140 PID - Protocol ID 141 This field contains an identifier which identifies the 142 client/server protocol which is making use of SCSP for the given 143 message. The assignment of Protocol IDs for this field is given 144 over to IANA. 146 Local Server (LS) 147 Local Server is the server sitting on this IP end station or 148 router and is the server under scrutiny. 150 LSID - Local Server ID 151 The LSID is a unique token that identifies an LS. This value 152 might be taken from the protocol address of the LS. 154 Directly Connected Server (DCS) 155 Directly Connected Server is the server which is directly 156 connected to the LS, e.g., there exists a VC between the LS and 157 DCS. Thus, every server is a DCS from the point of view of every 158 other server which connects to it directly, and every server is 159 an LS which has zero or more DCSs directly connected to it. 161 HFSM - Hello Finite State Machine 162 An LS has a HFSM associated with each of its DCSs. The HFSM 163 monitors the state of the connectivity between the LS and a 164 particular DCS. 166 CA Message - Cache Alignment Message 167 These messages allow an LS to synchronize its entire cache with 168 that of the cache of one of its DCSs. 170 CAFSM - Cache Alignment Finite State Machine 171 The CAFSM monitors the state of the cache alignment between an 172 LS and a particular DCS. There exists one CAFSM per DCS as 173 seen from an LS. 175 CSA Record - Cache State Advertisement Record 176 A CSA is a record within a CSU message which identifies an 177 update to the status of a "particular" cache entry. 179 CSAS Record - Cache State Advertisement Summary Record 180 A CSAS contains a summary of the information in a CSA. A server 181 will send CSAS records describing its cache entries to another 182 server during the cache alignment process. CSAS records are 183 also included in a CSUS messages when an LS wants to request 184 the entire CSA from the DCS. The LS is requesting the CSA from 185 the DCS because the LS believes that the DCS has a more recent 186 view of the state of the cache entry in question. 188 CSU Message - Cache State Update message 189 This is a message sent from an LS to its DCSs when the LS 190 becomes aware of a change in state of a cache entry. 192 CSUS Message - Cache State Update Solicit Message 193 This message is sent by an LS to its DCS after the LS and DCS 194 have exchanged CA messages. The CSUS message contains one or 195 more CSAS records which represent solicitations for entire CSA 196 records (as opposed to just the summary information held in 197 the CSAS). 199 This document defines SCSP protocol independent MIB definition, which 200 contains three tables: scspServerGroupTable, scspLSTable, and 201 scspDCSTable. 203 The scspServerGroupTable contains information for the server group, 204 such as the Server group ID, and Protocol ID. The scspLSTable 205 contains the attributes associated with the Local Server, such as the 206 Local server ID, HelloInterval, DeadFactor, and retransmit 207 properties. Note that there is one to one mapping between one 208 scspServerGroupEntry and one scspLSEntry, since only one Local Server 209 is defined for each Server Group. 211 The scspDCSTable contains information associated with the DCS session 212 between the Local Server and its associated Directly Connected 213 Servers. The scspDCSTable keeps track the current state of the Cache 214 Alignment State Machine. In addition, the scspDCSTable keeps track of 215 statistics of messages exchanges such as the Cache Alignment 216 messages. Note that one scspServerGroupEntry or one scspLSEntry may 217 map to multiple scspDCSEntries, since in a server group multiple DCS 218 may connect to the Local Server. 220 The Notifications Group contains the notification objects for 221 supporting SCSP. SNMP trap scspCSAReXmExceed trap event is used to 222 notify management that CSA exchange between LS and DCS has timed out. 224 4. Definition of the Server Cache Synchronization Protocol MIB 226 SCSP-MIB DEFINITIONS ::= BEGIN 228 IMPORTS 229 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 230 experimental, Integer32, IpAddress, Counter32 231 FROM SNMPv2-SMI 232 TEXTUAL-CONVENTION, RowStatus 233 FROM SNMPv2-TC 234 MODULE-COMPLIANCE, OBJECT-GROUP 235 FROM SNMPv2-CONF 236 ; 238 scspMIB MODULE-IDENTITY 239 LAST-UPDATED "9808200000Z" -- October 10, 1998 240 ORGANIZATION "IETF Internetworking Over NBMA Working Group (ion)" 241 CONTACT-INFO 242 "Jim Luciani (luciani@BayNetworks.com) 243 Bay Networks 245 Cliff X. Wang (cliff_wang@vnet.ibm.com) 246 Colin Verrilli (verrilli@vnet.ibm.com) 247 IBM Corp." 249 DESCRIPTION 250 "This module defines a portion of the management 251 information base (MIB) for managing Server Cache 252 Synchronization protocols entities." 253 ::= { experimental 2001 } 254 -- Need to get an "official" experimental number from IANA 256 -- ***************************************************************** 258 -- Textual Conversion 260 -- ***************************************************************** 262 ScspPIDType ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION 265 "The protocol type associated with a SCSP instance." 266 SYNTAX INTEGER { 267 atmarp(1), 268 nhrp(2), 269 mars(3), 270 dhcp(4), 271 lnni(5) 272 } 274 ScspHFSMStateType ::= TEXTUAL-CONVENTION 275 STATUS current 276 DESCRIPTION 277 "The various states of the Hello Finite State Machine." 278 SYNTAX INTEGER { 279 down(1), 280 waiting(2), 281 uniConn(3), 282 biConn(4) 283 } 285 ScspCAFSMStateType ::= TEXTUAL-CONVENTION 286 STATUS current 287 DESCRIPTION 288 "The various states of the Cache Alignment Finite 289 State Machine." 290 SYNTAX INTEGER { 291 down(1), 292 msNego(2), 293 cacheSumm(3), 294 cacheUpdate(4), 295 aligned(5) 296 } 298 SCSPVPIInteger ::= TEXTUAL-CONVENTION 299 STATUS current 300 DESCRIPTION 301 "An integer large enough to contain the value of a VPI." 302 SYNTAX Integer32 (0..255) 304 SCSPVCIInteger ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION 307 "An integer large enough to contain the value of a VCI." 308 SYNTAX Integer32 (0..65535) 310 -- ***************************************************************** 311 -- Top Level structure of the SCSP MIB 313 -- ***************************************************************** 315 scspObjects OBJECT IDENTIFIER ::= { scspMIB 1} 316 scspNotifications OBJECT IDENTIFIER ::= { scspMIB 2} scspConformance 317 OBJECT IDENTIFIER ::= { scspMIB 3} 319 -- ***************************************************************** 321 -- SCSP MIB Objects 323 -- ***************************************************************** 325 -- ***************************************************************** 327 -- SCSP Server Group Objects 329 -- ***************************************************************** 331 scspServerGroupTable OBJECT-TYPE 332 SYNTAX SEQUENCE OF ScspServerGroupEntry 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "The objects defined in this table are used to for the 337 management of server groups. There is one entry in this 338 table for each server group." 339 ::= { scspObjects 1} 341 scspServerGroupEntry OBJECT-TYPE 342 SYNTAX ScspServerGroupEntry 343 MAX-ACCESS not-accessible 344 STATUS current 345 DESCRIPTION 346 "Each entry contains attributes associated with a scsp 347 server group." 348 INDEX {scspServerGroupID, scspServerGroupPID } 349 ::= { scspServerGroupTable 1} 351 ScspServerGroupEntry ::= SEQUENCE { 352 scspServerGroupID Integer32, 353 scspServerGroupPID ScspPIDType, 354 scspServerGroupRowStatus RowStatus} 356 scspServerGroupID OBJECT-TYPE 357 SYNTAX Integer32 (0..65535) 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "This is the Group ID of this SCSP server group instance." 362 ::= { scspServerGroupEntry 1 } 364 scspServerGroupPID OBJECT-TYPE 365 SYNTAX ScspPIDType 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "This is the protocol ID of this SCSP server group 370 instance." 371 ::= { scspServerGroupEntry 2 } 373 scspServerGroupRowStatus OBJECT-TYPE 374 SYNTAX RowStatus 375 MAX-ACCESS read-create 376 STATUS current 377 DESCRIPTION 378 "This object allows entries to be created and deleted 379 from the scspServerGroupTable. This table is closely 380 coupled with the scspLSTable, scspDCSTable, and the 381 corresponding protocol dependent tables. A new row 382 creation in this table results in creation of 383 corresponding entries in the scspLSTable and scspDCSTable. 384 In addition, entries in appropriate protocol dependent 385 table may also be added. When the scspServerRowStatus is 386 deleted by setting this object to destroy(6), this results 387 in removing corresponding entries in scspLSTable, 388 scspDCSTable, and those in corresponding protocol 389 dependent table." 390 REFERENCE 391 "RFC 1903, 'Textual Conventions for version 2 of the 392 Simple Network Management Protocol (SNMPv2).'" 393 ::= { scspServerGroupEntry 3 } 395 -- ***************************************************************** 397 -- SCSP LS Objects 399 -- ***************************************************************** 401 scspLSTable OBJECT-TYPE 402 SYNTAX SEQUENCE OF ScspLSEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "The objects defined in this table are for the 407 management of SCSP local server (LS)." 408 ::= { scspObjects 2} 410 scspLSEntry OBJECT-TYPE 411 SYNTAX ScspLSEntry 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "Information about the Local Server in a SCSP group. Each 416 entry contains attributes associated a LS." 417 INDEX {scspServerGroupID, 418 scspServerGroupPID, 419 scspLSID 420 } 421 ::= { scspLSTable 1} 423 ScspLSEntry ::= SEQUENCE { 424 scspLSID OCTET STRING(SIZE(0..63)), 425 scspLSHelloInterval Integer32, 426 scspLSDeadFactor Integer32, 427 scspLSCAReXmInterval Integer32, 428 scspLSCSUSReXmtInterval Integer32, 429 scspLSCSUReXmtInterval Integer32, 430 scspLSCSAMaxReXmt Integer32, 431 scspLSRowStatus RowStatus 432 } 434 scspLSID OBJECT-TYPE 435 SYNTAX OCTET STRING(SIZE(0..63)) 436 MAX-ACCESS not-accessible 437 STATUS current 438 DESCRIPTION 439 "This is the Local Server ID of this Local Server." 440 ::= { scspLSEntry 1 } 442 scspLSHelloInterval OBJECT-TYPE 443 SYNTAX Integer32 (0..65535) 444 MAX-ACCESS read-create 445 STATUS current 446 DESCRIPTION 447 "This object contains the value for HelloInterval for 448 the Local Server. It is the time (in seconds) between 449 sending of consecutive Hello messages from this server." 450 REFERENCE 451 "SCSP draft, Section 2.1" 452 ::= { scspLSEntry 2 } 454 scspLSDeadFactor OBJECT-TYPE 455 SYNTAX Integer32 (0..65535) 456 MAX-ACCESS read-create 457 STATUS current 458 DESCRIPTION 459 "This object contains the value for DeadFactor. The 460 DeadFactor along with HelloInterval are sent with 461 outgoing 'Hello' messages. If the DCS does not 462 received 'Hello' message from this LS within the 463 time out interval 'HelloInterval*DeadFactor' 464 (in seconds), then the DCS MUST consider the LS to 465 be stalled." 466 REFERENCE 467 "SCSP draft, Section 2.1" 468 ::= { scspLSEntry 3 } 470 scspLSCAReXmInterval OBJECT-TYPE 471 SYNTAX Integer32 (0..65535) 472 MAX-ACCESS read-create 473 STATUS current 474 DESCRIPTION 475 "The time out interval (in seconds) for re-sending CA 476 message to the DCS if no response is received." 477 ::= { scspLSEntry 4 } 479 scspLSCSUSReXmtInterval OBJECT-TYPE 480 SYNTAX Integer32 (0..65535) 481 MAX-ACCESS read-create 482 STATUS current 483 DESCRIPTION 484 "The time out interval (in seconds) for re-sending 485 CSUS Request to the DCS if not all CSA Records 486 corresponding to the CSAS records in the CSUS 487 message have been received." 488 ::= { scspLSEntry 5 } 490 scspLSCSUReXmtInterval OBJECT-TYPE 491 SYNTAX Integer32 (0..65535) 492 MAX-ACCESS read-create 493 STATUS current 494 DESCRIPTION 495 "The time out interval (in seconds) for re-sending CSU 496 Request to the DCS if not all CSA Records corresponding 497 to the CSU request have not been acknowledged." 498 ::= { scspLSEntry 6 } 500 scspLSCSAMaxReXmt OBJECT-TYPE 501 SYNTAX Integer32 (0..65535) 502 MAX-ACCESS read-create 503 STATUS current 504 DESCRIPTION 505 "The maximum number of retransmission of a CSA record. 506 If acknowledge fails to occur when the maximum number 507 is reached, an 'abnormal event' has happened between 508 the LS/DCS link." 509 ::= { scspLSEntry 7 } 511 scspLSRowStatus OBJECT-TYPE 512 SYNTAX RowStatus 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "This object allows entries to be created and deleted 517 from the scspLSTable. This table is closely coupled 518 with DCS table and its corresponding protocol dependent 519 tables. A new row creation in this table results 520 in creation of new rows in the DCS table for each of 521 its configured DCSs (peer servers). In addition, 522 entries are created in the appropriate protocol 523 dependent tables. When the scspServerRowStatus is 524 deleted by setting this object to destroy(6), this 525 results in removing the corresponding entries in 526 the DCS table of the same Server Group. In addition, 527 entries in the corresponding protocol dependent table 528 will also be removed." 529 REFERENCE 530 "RFC 1903." 531 ::= { scspLSEntry 8 } 533 -- ***************************************************************** 535 -- SCSP DCS Objects 537 -- ***************************************************************** 539 scspDCSTable OBJECT-TYPE 540 SYNTAX SEQUENCE OF ScspDCSEntry 541 MAX-ACCESS not-accessible 542 STATUS current 543 DESCRIPTION 544 "The objects defined in this table are used for the 545 management of the DCS session between the LS and DCS." 546 ::= { scspObjects 3} 548 scspDCSEntry OBJECT-TYPE 549 SYNTAX ScspDCSEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "Information about each DCS session between the LS and 554 its DCSs. The table is indexed by scspServerGroupID, 555 scspServerGroupPID, and scspDCSID." 556 INDEX { scspServerGroupID, 557 scspServerGroupPID, 558 scspDCSID 559 } 560 ::= { scspDCSTable 1} 562 ScspDCSEntry ::= SEQUENCE { 563 scspDCSID OCTET STRING(SIZE(0..63)), 564 scspDCSCAFSMState ScspCAFSMStateType, 565 scspDCSCASequence Integer32, 566 scspDCSCAIn Counter32, 567 scspDCSCAOut Counter32, 568 scspDCSCAInvalidIn Counter32, 569 scspDCSCADuplicateIn Counter32, 570 scspDCSMSState INTEGER, 571 scspDCSCSUSIn Counter32, 572 scspDCSCSUSOut Counter32, 573 scspDCSCSUSInvalidIn Counter32, 574 scspDCSCSURequestIn Counter32, 575 scspDCSCSURequestOut Counter32, 576 scspDCSCSUReplyOut Counter32, 577 scspDCSCSUReplyIn Counter32, 578 scspDCSCSUInvalidRequestIn Counter32, 579 scspDCSCSUInvalidReplyIn Counter32, 580 scspDCSCSAIn Counter32, 581 scspDCSCSAOut Counter32, 582 scspDCSCSAReXmted Counter32, 583 scspDCSCSAReXmtQDepth Integer32, 584 scspDCSRowStatus RowStatus } 586 scspDCSID OBJECT-TYPE 587 SYNTAX OCTET STRING(SIZE(0..63)) 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "This ID is used to identify a directly connected 592 server(DCS)." 593 ::= { scspDCSEntry 1 } 595 scspDCSCAFSMState OBJECT-TYPE 596 SYNTAX ScspCAFSMStateType 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The current state of the Cache Alignment Finite State 601 Machine. The allowable states are: 602 down(1), 603 msNego(2), 604 cacheSumm(3), 605 cacheUpdate(4), 606 aligned(5)." 607 REFERENCE 608 "SCSP draft, Section 2.2" 609 ::= { scspDCSEntry 2 } 611 scspDCSCASequence OBJECT-TYPE 612 SYNTAX Integer32 (-2147483648..2147483647) 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "The current CA sequence number associated with 617 this DCS." 618 ::= { scspDCSEntry 3 } 620 scspDCSCAIn OBJECT-TYPE 621 SYNTAX Counter32 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The number of CA messages received from this DCS." 626 ::= { scspDCSEntry 4 } 628 scspDCSCAOut OBJECT-TYPE 629 SYNTAX Counter32 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "The number of CA messages sent to this DCS." 634 ::= { scspDCSEntry 5 } 636 scspDCSCAInvalidIn OBJECT-TYPE 637 SYNTAX Counter32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The number of invalid CA messages received from this 642 DCS. 643 During Master/Slave negotiation state, two types of 644 messages are correct: 645 1) CA from the DCS has the M, I, and O bits on, with 646 no CSAS records and sender's ID is larger than the 647 LSID. 648 2) CA from the DCS has the M and I bits off and the 649 sender's ID is smaller than the LSID. 650 All other types of CA messages are invalid and 651 ignored. During Cache Summarize State, two kinds of 652 message errors are possible: 653 1) M bit in received CA is set incorrectly; 654 2) CA sequence number is neither equal nor one 655 more than the current LS's CA sequence number when 656 LS is slave or CA sequence number is neither equal 657 nor one less than the current LS's CA sequence number 658 when LS is master. Other common errors include failed 659 check sum, failed authentication if applicable, 660 errors in the message fields." 662 REFERENCE 663 "SCSP draft, Section 2.2." 664 ::= { scspDCSEntry 6 } 666 scspDCSCADuplicateIn OBJECT-TYPE 667 SYNTAX Counter32 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The number of duplicate CA messages received from 672 this DCS. A CA message is considered duplicate when 673 1)LS is master and received a CA message with its 674 sequence number one less than the current sequence 675 number; or 676 2)LS is slave and received a CA message with its 677 sequence number equal to the LS's current sequence 678 number." 679 REFERENCE 680 "SCSP draft, Section 2.2" 681 ::= { scspDCSEntry 7 } 683 scspDCSMSState OBJECT-TYPE 684 SYNTAX INTEGER { 685 master (1), 686 slave (2) 687 } 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "The master/slave status of this DCS. This object 692 should be ignored when CAFSM is in 'down' state." 693 ::= { scspDCSEntry 8 } 695 scspDCSCSUSIn OBJECT-TYPE 696 SYNTAX Counter32 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "The number of CSUS sent from this DCS to the LS." 701 ::= { scspDCSEntry 9 } 703 scspDCSCSUSOut OBJECT-TYPE 704 SYNTAX Counter32 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "The number of CSUS sent from LS to this DCS." 709 ::= { scspDCSEntry 10 } 711 scspDCSCSUSInvalidIn OBJECT-TYPE 712 SYNTAX Counter32 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "The number of Invalid CSUS sent from this DCS to the LS." 717 ::= { scspDCSEntry 11 } 719 scspDCSCSURequestIn OBJECT-TYPE 720 SYNTAX Counter32 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "The number of CSU requests LS received from this DCS." 725 ::= { scspDCSEntry 12 } 727 scspDCSCSUReplyOut OBJECT-TYPE 728 SYNTAX Counter32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The number of CSU replies sent from LS to this DCS." 733 ::= { scspDCSEntry 13 } 735 scspDCSCSURequestOut OBJECT-TYPE 736 SYNTAX Counter32 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "The number of CSU requests sent from LS to this DCS." 741 ::= { scspDCSEntry 14 } 743 scspDCSCSUReplyIn OBJECT-TYPE 744 SYNTAX Counter32 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "The number of CSU replies LS received from this DCS." 749 ::= { scspDCSEntry 15 } 751 scspDCSCSUInvalidRequestIn OBJECT-TYPE 752 SYNTAX Counter32 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "The number of invalid CSU requests LS received from 757 this DCS. The possible errors in the CSU request 758 messages: the received CSU request's Receiver ID is 759 not equal to the LSID, etc. 760 Other common errors include failed authentication if 761 applicable, errors in the message fields, etc." 762 ::= { scspDCSEntry 16 } 764 scspDCSCSUInvalidReplyIn OBJECT-TYPE 765 SYNTAX Counter32 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The number of invalid CSU replies LS received from 770 this DCS. The possible errors in the CSU reply 771 messages: the received CSU reply's Receiver ID is not 772 equal to the LSID, etc. 773 Other common errors include failed authentication if 774 applicable, errors in the message fields, etc." 775 ::= { scspDCSEntry 17 } 777 scspDCSCSAIn OBJECT-TYPE 778 SYNTAX Counter32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "The total number of CSA records received from 783 this DCS to this LS." 784 ::= { scspDCSEntry 18 } 786 scspDCSCSAOut OBJECT-TYPE 787 SYNTAX Counter32 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The total number of CSA records sent from LS 792 to this DCS." 793 ::= { scspDCSEntry 19 } 795 scspDCSCSAReXmted OBJECT-TYPE 796 SYNTAX Counter32 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "The total number of CSA records re-transmited from LS 801 to this DCS." 802 ::= { scspDCSEntry 20 } 804 scspDCSCSAReXmtQDepth OBJECT-TYPE 805 SYNTAX Integer32 (0..65535) 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The depth of CSA Re-transmit queue associated with 810 this DCS. The CSAs in the Re-transmit queue are 811 pending to acknowledged." 812 ::= { scspDCSEntry 21 } 814 scspDCSRowStatus OBJECT-TYPE 815 SYNTAX RowStatus 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "This object allows DCS entries to be created and 820 deleted from the scspDCSTable. This table is closely 821 coupled with its corresponding protocol dependent table. 822 A new row creation in this table results in creation of 823 a new row in the corresponding protocol dependent table. 824 When the scspServerRowStatus is deleted by setting this 825 object to destroy(6), this results in removing the 826 corresponding entries in its corresponding protocol 827 dependent table." 828 REFERENCE 829 "RFC 1903, 'Textual Conventions for version 2 of the 830 Simple Network Management Protocol (SNMPv2).'" 831 ::= { scspDCSEntry 22 } 833 -- ***************************************************************** 835 -- Notifications 837 -- ***************************************************************** 838 scspCSAReXmExceed NOTIFICATION-TYPE 839 OBJECTS { 840 scspServerGroupID, 841 scspServerGroupPID, 842 scspDCSID 843 } 844 STATUS current 845 DESCRIPTION 846 "Retransmission of a CSA to this DCS has exceeded 847 maximum retry limit, indicating an 'abnormal event' 848 has happened between the LS/DCS association. The 849 HSFM associated with this DCS is transitioned into 850 the 'Waiting' state, and a 'scspHFSMWaiting' trap 851 is also generated." 852 ::= { scspNotifications 1 } 854 -- ***************************************************************** 856 -- Conformance Definitions 858 -- ***************************************************************** 860 scspCompliances OBJECT IDENTIFIER ::= { scspConformance 1 } 861 scspGroups OBJECT IDENTIFIER ::= { scspConformance 2 } 863 -- ***************************************************************** 865 -- SCSP MIB Compliance Statements 867 -- ***************************************************************** 869 scspCompliance MODULE-COMPLIANCE 870 STATUS current 871 DESCRIPTION 872 "The compliance statement for entities that are required 873 for the management of SCSP." 874 MODULE 875 MANDATORY-GROUPS { 876 scspLSGroup, 877 scspDCSGroup 878 } 880 ::= { scspCompliances 1 } 882 scspLSGroup OBJECT-GROUP 883 OBJECTS { 884 scspServerGroupID, 885 scspServerGroupPID, 886 scspLSID, 887 scspLSHelloInterval, 888 scspLSCAReXmInterval, 889 scspLSCSUSReXmtInterval, 890 scspLSCSUReXmtInterval, 891 scspLSCSAMaxReXmt, 892 scspLSDeadFactor 893 } 894 STATUS current 895 DESCRIPTION 896 "A collection of objects which support the management of 897 the Server group and the Local Server. This group is 898 mandatory." 899 ::= { scspGroups 1 } 901 scspDCSGroup OBJECT-GROUP 902 OBJECTS { 903 scspDCSID, 904 scspDCSCAFSMState, 905 scspDCSCAIn, 906 scspDCSCAOut, 907 scspDCSCAInvalidIn, 908 scspDCSCADuplicateIn, 909 scspDCSMSState, 910 scspDCSCSUSIn, 911 scspDCSCSUSOut, 912 scspDCSCSURequestIn, 913 scspDCSCSURequestOut, 914 scspDCSCSUReplyOut, 915 scspDCSCSUReplyIn, 916 scspDCSCSUInvalidRequestIn, 917 scspDCSCSUInvalidReplyIn, 918 scspDCSCSAIn, 919 scspDCSCSAOut, 920 scspDCSCSAReXmted, 921 scspDCSCSAReXmtQDepth 922 } 923 STATUS current 924 DESCRIPTION 925 "A collection of objects which support the management of 926 the information exchange session between the LS and its 927 associated DCS. This group is mandatory." 928 ::= { scspGroups 2 } 930 END 932 Acknowledgments 933 I would like to thank Hoylen Sue of CiTR Australia for many 934 insightful discussions. 936 Reference 938 [1] "Server Cache Synchronization Protocol (SCSP)", J. Luciani, 939 G. Armitage, J. Halpern,and N. Doraswamy, RFC 2334 941 [2] "A Distributed NHRP Service Using SCSP", J. Luciani, 942 RFC 2335 944 [3] "A Distributed ATMARP Service Using SCSP", J. Luciani 945 draft-ietf-ion-scsp-atmarp-00.txt. 947 [4] "A Distributed MARS Service Using SCSP", J. Luciani, A. Gallo, 948 draft-ietf-ion-scsp-mars-01.txt 950 [5] "Simple Network Management Protocol", J. Case, M. Fedor, 951 M. Schoffstall, J. Davin, RFC 1157, 953 [6] "Management Information Base for Network Management of 954 TCP/IP-based internets: MIB-II", K. McCloghrie,M. Rose, RFC 121 956 [7] "Structure of Management Information for version 2 of the 957 Simple Network Management Protocol (SNMPv2)", J. Case, 958 K. McCloghrie, M. Rose, S. Waldbusser, RFC 1902, 960 [8] "Protocol Operations for version 2 of the Simple Network 961 Management Protocol (SNMPv2)", J. Case, K. McCloghrie, 962 M. Rose, S. Waldbusser, RFC 1905 964 [9] "Textual Conventions for version 2 of the Simple Network 965 Management Protocol (SNMPv2)", J. Case, K. McCloghrie, M. Rose, 966 S. Waldbusser, RFC 1903 968 [10]"Conformance Statements for version 2 of the Simple Network 969 Management Protocol (SNMPv2)", J. Case, K. McCloghrie, M. Rose, 970 S. Waldbusser, RFC 1904 972 [11]"Classic IP and ARP over ATM", M. Laubach and J. Halpern, 973 RFC 2225 975 [12]"Support for Multicast over UNI 3.0/3.1 based ATM Networks", 976 G. Armitage, RFC 2022 978 [13]"NBMA Next Hop Resolution Protocol (NHRP)", J. Luciani, 979 D. Katz, D. Piscitello, B. Cole, N. Doraswamy, 980 RFC 2332 982 Authors' Addresses 984 Cliff X. Wang 985 IBM, Networking Hardware Division 986 Dept. MZDA/B664 987 P.O. Box 12195 988 Research Triangle Park, NC 27709 989 phone: +1-919-486-1255 990 email: cxwang@us.ibm.com 992 Colin B. Verrilli 993 IBM, Networking Hardware Division 994 Dept. M6LA/B664 995 P.O. Box 12195 996 Research Triangle Park, NC 27709 997 phone: +1-919-254-9936 998 email: verrilli@raleigh.ibm.com 1000 James V. Luciani 1001 Bay Networks, Inc. 1002 3 Federal Street, BL3-04 1003 Billerica, MA 01821 1004 phone: +1-508-916-4734 1005 email: luciani@baynetworks.com