idnits 2.17.1 draft-ietf-gsmp-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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.) -- The document date (June 2001) is 8349 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2026' is defined on line 2072, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 2084, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 2088, but no explicit reference was found in the text == Unused Reference: 'RFC2851' is defined on line 2128, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 2132, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Downref: Normative reference to an Informational RFC: RFC 1987 ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPv3' -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPenc' Summary: 18 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Hans Sjostrand 2 INTERNET DRAFT ipUnplugged 3 Expires December 2001 Joachim Buerkle 4 Nortel Networks 5 Balaji Srinivasan 6 Cplane 7 June 2001 9 Definitions of Managed Objects for 10 the General Switch Management Protocol (GSMP) 12 < draft-ietf-gsmp-mib-05.txt > 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet- Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Distribution of this document is unlimited. Please send comments to 36 the General Switch Management Protocol (gsmp) Working Group, 37 . 39 Copyright Notice 41 Copyright (C) The Internet Society (1999). All Rights Reserved. 43 Abstract 45 This memo defines a portion of the Management Information Base (MIB) 46 for use with network management protocols in the Internet community. 47 In particular, it describes managed objects for the General Switch 48 Management Protocol (GSMP). 50 Table of Contents 52 1. Introduction...................................................... 3 54 2. The SNMP Management Framework..................................... 3 56 3. Structure of the MIB.............................................. 5 57 3.1 Overview...................................................... 5 58 3.2 Scope......................................................... 5 59 3.3 MIB guideline................................................. 6 60 3.4 MIB groups.................................................... 7 61 3.4.1 GSMP Switch Controller group............................ 7 62 3.4.2 GSMP Switch group....................................... 7 63 3.4.3 GSMP Encapsulation groups............................... 8 64 3.4.4 GSMP General group...................................... 8 65 3.4.5 The GSMP Notifications Group............................ 8 66 3.5 Textual Conventions.......................................... 10 68 4. GSMP MIB Definitions............................................. 10 70 5. Revision History................................................. 42 71 5.1 Changes from < draft-ietf-gsmp-mib-00.txt >.................. 42 72 5.2 Changes from < draft-ietf-gsmp-mib-01.txt >.................. 42 73 5.3 Changes from < draft-ietf-gsmp-mib-02.txt >.................. 42 74 5.4 Changes from < draft-ietf-gsmp-mib-03.txt >.................. 43 75 5.5 Changes from < draft-ietf-gsmp-mib-04.txt >.................. 43 77 6. Acknowledgments.................................................. 43 79 7. References....................................................... 43 81 8. Security Considerations.......................................... 46 83 9. Authors' Addresses............................................... 46 85 10. Full Copyright Statement........................................ 47 86 1. Introduction 88 This memo defines a portion of the Management Information Base (MIB) 89 for use with network management protocols in the Internet community. 90 In particular, it describes managed objects for the General Switch 91 Management Protocol (GSMP). 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119 [RFC2119]. 97 2. The SNMP Management Framework 99 The SNMP Management Framework presently consists of five major 100 components: 102 * An overall architecture, described in RFC 2571 [RFC2571]. 104 * Mechanisms for describing and naming objects and events for the 105 purpose of management. The first version of this Structure of 106 Management Information (SMI) is called SMIv1 and described in STD 107 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 108 [RFC1215]. The second version, called SMIv2, is described in STD 109 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580[RFC2580]. 111 * Message protocols for transferring management information. The 112 first version of the SNMP message protocol is called SNMPv1 and 113 described in STD 15, RFC 1157 [RFC1157]. A second version of the 114 SNMP message protocol, which is not an Internet standards track 115 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 116 and RFC 1906 [RFC1906]. The third version of the message protocol 117 is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 118 [RFC2572] and RFC 2574 [RFC2574]. 120 * Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in STD 15, RFC 1157 [RFC1157]. A second set of 123 operations and associated PDU formats is described in 1905 124 [RFC1905]. 126 * A set of fundamental applications described in RFC 2573 [RFC2573] 127 and the view-based access control mechanism described RFC 2575 128 [RFC2575]. 130 A more detailed introduction to the current SNMP Management Framework 131 can be found in RFC 2570 [RFC2570]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. A 138 MIB conforming to the SMIv1 can be produced through the appropriate 139 translations. The resulting translated MIB must be semantically 140 equivalent, except where objects or events are omitted because no 141 translation is possible (use of Counter64). Some machine readable 142 information in SMIv2 will be converted into textual descriptions in 143 SMIv1 during the translation process. However, this loss of machine 144 readable information is not considered to change the semantics of the 145 MIB. 147 3. Structure of the MIB 149 This memo defines a portion of the Management Information Base (MIB) 150 for use with network management protocols in the Internet community. 151 In particular, it describes managed objects for the General Switch 152 Management Protocol (GSMP) as defined in [GSMPv3]. 154 3.1 Overview 156 The General Switch Management Protocol (GSMP) is a general purpose 157 protocol to control a label switch. GSMP allows a controller to 158 establish and release connections across the switch, to manage switch 159 ports and to request configuration information or statistics. It also 160 allows the switch to inform the controller of asynchronous events 161 such as a link going down. 163 The GSMP protocol is asymmetric, the controller being the master and 164 the switch being the slave. Multiple switches may be controlled by a 165 single controller using multiple instantiations of the protocol over 166 separate control connections. Also a switch may be controlled by more 167 than one controller by using the technique of partitioning.. 169 Each instance of a switch controller - switch partition adjacency is 170 a session between one switch controller entity and one switch entity. 171 The MIB provides objects to configure/setup these entities to form 172 the GSMP sessions. It also provide objects to monitor these GSMP 173 sessions. 175 3.2 Scope 177 The GSMP mib is a protocol mib. It contains object to configure, 178 monitor and maintain the GSMP protocol entity. It does not provide 179 any information learned via the protocol, such as "all ports config" 180 information. 182 The relationships between virtual entities, such as Virtual Switch 183 Entities, and entities, such as Switch Entities, falls outside of the 184 management of GSMP. This also applies for the management of switch 185 partitions. So this is excluded from the GSMP mib. 187 It is possible to configure which and how many Switch Controllers 188 that are controlling one Switch since every potential session with 189 the switch has to be represented with an Switch entity. It is however 190 not possible to define that one Switch Controller shouldn't allow 191 other Switch controllers to control the same switch or partition on 192 the switch. It is assumed that there are mechanisms that synchronise 193 controllers and the configuration of them. This is outside the scope 194 of this mib. 196 3.3 MIB guideline 198 Two tables are used to configure potential GSMP sessions depending if 199 you are acting as a GSMP switch controller or a GSMP switch. Each row 200 in these tables initiates a GSMP session. 202 The entity ID is a 48-bit name that is unique within the operational 203 context of the device. A 48-bit IEEE 802 MAC address, if available, 204 MAY be used for the entity ID. If the Ethernet encapsulation is used, 205 the entity ID MUST be the IEEE 802 MAC address of the interface on 206 which the GSMP session is to be setup. 208 First the encapsulation the potential GSMP session shall be defined. 209 If atm is used, a row in the gsmpAtmEncapTable has to be created with 210 the index set to the entity ID. The specified resources should be 211 allocated to GSMP. If tcp/ip is used, a row in the 212 gsmpTcpIpEncapTable has to be created with the index set to the 213 entity ID. The specified port shall be allocated to GSMP. No special 214 action is needed if ethernet encapsulation is used. 216 Then the entity information shall be defined. To create a Switch 217 Entity, an entry in the gsmpSwitchTable is created with the index set 218 to the entity ID. To create a Switch Controller Entity, an entry in 219 the gsmpControllerTable is created with the index set to the entity 220 ID. 222 When the row status of the GsmpControllerEntry or GsmpSwitchEntry is 223 set to active, and in the case with atm or tcp/ip there are active 224 rows with corresponding entity ID, the adjacency protocol of GSMP is 225 started. 227 Another table, the gsmpSessionTable, shows the actual sessions that 228 are established or are in the process of being established. Each row 229 represents a specific session between an Entity and a peer. This 230 table carries information about the peer, the session and parameters 231 that was negotiated by the adjacency procedures. The 232 gsmpSessionTable also contains statistical information regarding the 233 session. 235 This creation order SHOULD be used by all GSMP managers. This is to 236 avoid clash situations in multiple SNMP manager scenarios where 237 different managers may create competing entries in the different 238 tables. 240 Entities may very well be configured by other means than SNMP, e.g. 241 cli command. Such configured entities SHOULD be represented as 242 entries in the tables of this mib and SHOULD be possible to query and 243 MAY be possible to alter with SNMP. 245 3.4 MIB groups 247 3.4.1 GSMP Switch Controller group 249 The controller group is used to configure a potential GSMP session on 250 a Switch Controller. A row in the gsmpControllerTable is created for 251 each such session. If ATM or TCP/IP encapsulation is used a 252 corresponding row has to be created in these tables before the 253 session adjacency protocol is initiated. 255 If ATM or TCP/IP is used, encapsulation data is defined in the 256 corresponding encapsulation tables. If ethernet is used the MAC 257 address of the interface defined for the session is set by the 258 Controller ID object. 260 The adjacency parameters are defined; such as 261 - Max supported GSMP version 262 - Time between the periodic adjacency messages 263 - Controller local port number and instance number. 264 - Whether partitions are being used and the partition ID for the 265 specific partitions this controller is concerned with if 266 partitions are used. 267 - The resynchronisation strategy for the session is specified. 269 The notification mapping is set to specify for with events the 270 corresponding SNMP notifications are sent. 272 3.4.2 GSMP Switch group 274 The switch group is used to configure a potential GSMP session on a 275 Switch. A row in the gsmpSwitchTable is created for each such 276 session. If ATM or TCP/IP encapsulation is used a corresponding row 277 has to be created in these tables before the session adjacency 278 protocol is initiated. 280 If ATM or TCP/IP is used, encapsulation data is defined in the 281 corresponding encapsulation tables. If ethernet is used the MAC 282 address of the interface defined for the session is set by the Switch 283 ID object. 285 The adjacency parameters are defined; such as 286 - Max supported GSMP version 287 - Time between the periodic adjacency messages 288 - Switch Name, local port number and instance number. 289 - Whether partitions are being used and the partition ID for this 290 specific partition if partitions are used. 292 - The switch type could be set. 293 - The suggested maximum window size for unacknowledged request 294 messages. 296 Also, a notification mapping is set to specify for with events the 297 corresponding SNMP notifications are sent. 299 3.4.3 GSMP Encapsulation groups 301 The ATM Encapsulation Table and the TCP/IP Encapsulation Table 302 provides a way to configure information that are encapsulation 303 specific. The encapsulation data is further specified in [GSMPenc]. 305 If ATM encapsulation is used, the interface and the virtual channel 306 are specified. 308 If TCP/IP is used, the IP address and the port number are specified. 310 No special config data needed if Ethernet encapsulation is used. 312 This mib MAY be extended with new, standard or proprietary, GSMP 313 encapsulation types. If a new encapsulation type needs to be added, 314 it SHOULD be done in the form of a new table with the entity ID as 315 index. A row in that encapsulation table SHOULD be created before any 316 row in an GSMP entity table are created that are using this new GSMP 317 encapsulation. 319 3.4.4 GSMP General group 321 The GSMP session table provides a way to monitor and maintain GSMP 322 sessions. 324 The session is defined by a Switch Controller Entity and Switch 325 Entity pair. 327 3.4.5 The GSMP Notifications Group 329 The GSMP Notification Group defines notifications for GSMP entities. 330 These notifications provide a mechanism for a GSMP device to inform 331 the management station of status changes. Also a notification is 332 defined for each type of GSMP events. 334 The group of notifications consists of the following notifications: 336 - gsmpSessionDown 338 This notification is generated when a session is terminating and also 339 reports the final accounting statistics of the session. 341 - gsmpSessionUp 343 This notification is generated when a new session is established. 345 - gsmpSendFailureInd 347 This notification is generated when a message with a failure 348 indication was sent. This means that this notification identifies a 349 change to the gsmpSessionStatFailureInds object in a row of the 350 gsmpSessionTable. 352 - gsmpReceivedFailureInd 354 This notification is generated when a message with a failure 355 indication received. This means that this notification identifies a 356 change to the gsmpSessionStatReceivedFailures object in a row of the 357 gsmpSessionTable. 359 - gsmpPortUpEvent 361 This notification is generated when a Port Up Event is either 362 received or sent. 364 - gsmpPortDownEvent 366 This notification is generated when a Port Down Event is either 367 received or sent. 369 - gsmpInvalidLabelEvent 371 This notification is generated when an Invalid Label Event is either 372 received or sent. 374 - gsmpNewPortEvent 376 This notification is generated when New Port Event either is received 377 or sent. 379 - gsmpDeadPortEvent 381 This notification is generated when a Dead Port Event is either 382 received or sent. 384 - gsmpAdjacencyUpdateEvent 386 This notification is generated when an Adjacency Update Event is 387 either received or sent. 389 To disable or enable sending of each notification is done by setting 390 the bitmap accordingly in the Notification mapping objects in the 391 Controller Entity or Switch Entity tables. 393 The GSMP notification map capability should not be seen as a 394 duplication of the filter mechanism in the snmp notification 395 originator application [RFC2573], but as a compliment, to configure 396 the relation between GSMP events and the SNMP notifications already 397 in the GSMP agent. SNMP notifications and GSMP events operate 398 sometimes on a different timescale, and it may in some applications 399 be devastating for a SNMP application to receive events for each GSMP 400 events. E.g. the invalid label event in a ATM switch scenario may 401 cause mass SNMP notification flooding if mapped to a SNMP 402 notification. 404 3.5 Textual Conventions 406 The datatypes GsmpNameType, GsmpLabelType, GsmpPartitionType and 407 GsmpPartitionIdType are used as textual conventions in this document. 408 These textual conventions are used for the convenience of humans 409 reading the MIB module and have NO effect on the syntax of any 410 managed object. Objects defined using these conventions are always 411 encoded by means of the rules that define their primitive type. 412 However, the textual conventions have special semantics associated 413 with them. Hence, no changes to the SMI or the SNMP are necessary to 414 accommodate these textual conventions which are adopted merely for 415 the convenience of readers. 417 4. GSMP MIB Definitions 419 GSMP-MIB DEFINITIONS ::= BEGIN 421 IMPORTS 422 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 423 Unsigned32, Integer32, Counter32, mib-2 424 FROM SNMPv2-SMI -- RFC2578 425 RowStatus, TruthValue, TimeStamp, 426 StorageType, TEXTUAL-CONVENTION 427 FROM SNMPv2-TC -- RFC2579 428 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 429 FROM SNMPv2-CONF -- RFC2580 430 InterfaceIndex 431 FROM IF-MIB -- RFC2863 432 AtmVcIdentifier, AtmVpIdentifier 433 FROM ATM-TC-MIB -- RFC2514 434 InetAddressType, InetAddress 435 FROM INET-ADDRESS-MIB -- RFC2851 437 ; 439 gsmpMIB MODULE-IDENTITY 440 LAST-UPDATED "200106211200Z" -- 21 June 2001, 12.00 MET DST 441 ORGANIZATION "General Switch Management Protocol (gsmp) 442 Working Group, IETF" 443 CONTACT-INFO 444 "WG Charter: 445 http://www.ietf.org/html.charters/gsmp-charter.html 447 WG-email: gsmp@revnetworks.com 448 Subscribe: gsmp-request@revnetworks.com 449 Email Archive: 450 ftp://www.revnetworks.com/pub/mailing-lists/gsmp-archive 452 WG Chair: Avri Doria 453 Email: avri@nortelnetworks.com 455 WG Chair: Kenneth Sundell 456 Email: ksundell@nortelnetworks.com 458 Editor: Hans Sjostrand 459 Email: hans@ipunplugged.com 461 Editor: Joachim Buerkle 462 Email: joachim.buerkle@nortelnetworks.com 464 Editor: Balaji Srinivasan 465 Email: balaji@cplane.com" 466 DESCRIPTION 467 "This MIB contains managed object definitions for the 468 General Switch Management Protocol, GSMP, version 3" 470 REVISION "200106211200Z" 471 DESCRIPTION "Initial Version, published as RFC xxxx" 472 -- RFC-Editor assigns xxxx 474 ::= { mib-2 XXX } -- IANA assignes XXX 476 gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 0 } 477 gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } 478 gsmpNotificationsObjects OBJECT IDENTIFIER ::= { gsmpMIB 2 } 479 gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 } 481 --************************************************************** 482 -- GSMP Textual Conventions 483 --************************************************************** 485 GsmpNameType ::= TEXTUAL-CONVENTION 486 STATUS current 487 DESCRIPTION 488 "The Name is a 48-bit quantity. 489 A 48-bit IEEE 802 MAC address, if 490 available, may be used." 491 SYNTAX OCTET STRING (SIZE(6)) 493 GsmpPartitionType ::= TEXTUAL-CONVENTION 494 STATUS current 495 DESCRIPTION 496 "Defining if partitions are used and how the partition id 497 is negotiated. " 498 SYNTAX INTEGER {noPartition(1), 499 fixedPartitionRequest(2), 500 fixedPartitionAssigned(3) 501 } 503 GsmpPartitionIdType ::= TEXTUAL-CONVENTION 504 STATUS current 505 DESCRIPTION 506 "A 8-bit quantity. The format of the Partition ID is not 507 defined in GSMP. If desired, the Partition ID can be 508 divided into multiple sub-identifiers within a single 509 partition. For example: the Partition ID could be 510 subdivided into a 6-bit partition number and a 2-bit 511 sub-identifier which would allow a switch to support 64 512 partitions with 4 available IDs per partition." 513 SYNTAX OCTET STRING (SIZE(1)) 515 GsmpVersion ::= TEXTUAL-CONVENTION 516 STATUS current 517 DESCRIPTION 518 "The version numbers defined for the GSMP protocol. 519 The version numbers used are defined in the 520 specifications of the respective protocool, 521 1 - GSMPv1.1 [RFC1987] 522 2 - GSMPv2.0 [RFC2397] 523 3 - GSMPv3 [GSMPv3] 524 Other numbes may be defined for other versions 525 of the GSMP protocool." 526 SYNTAX Unsigned32 528 GsmpLabelType ::= TEXTUAL-CONVENTION 529 STATUS current 530 DESCRIPTION 531 "The label is structured as a TLV, a tuple, consisting of 532 a Type, a Length, and a Value. The structure is defined 533 in [GSMPv3]. The label TLV is encoded as a 2 octet type 534 field, followed by a 2 octet Length field, followed by a 535 variable length Value field. 536 Additionally, a label field can be composed of many stacked 537 labels that together constitute the label." 538 SYNTAX OCTET STRING 540 --************************************************************** 541 -- GSMP Entity Objects 542 --************************************************************** 544 -- 545 -- Switch Controller Entity table 546 -- 548 gsmpControllerTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF GsmpControllerEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "This table represents the Switch Controller 554 Entities. An entry in this table needs to be configured 555 (created) before a GSMP session might be started." 556 ::= { gsmpObjects 1 } 558 gsmpControllerEntry OBJECT-TYPE 559 SYNTAX GsmpControllerEntry 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "An entry in the table showing 564 the data for a specific Switch Controller 565 Entity. If partitions are used, one entity 566 corresponds to one specific switch partition. 567 Depending of the encapsulation used, 568 a corresponding row in the gsmpAtmEncapTable or the 569 gsmpTcpIpEncapTable may have been created." 570 INDEX { gsmpControllerEntityId } 571 ::= { gsmpControllerTable 1 } 573 GsmpControllerEntry ::= SEQUENCE { 574 gsmpControllerEntityId GsmpNameType, 575 gsmpControllerMaxVersion GsmpVersion, 576 gsmpControllerTimer Unsigned32, 577 gsmpControllerPort Unsigned32, 578 gsmpControllerInstance Unsigned32, 579 gsmpControllerPartitionType GsmpPartitionType, 580 gsmpControllerPartitionId GsmpPartitionIdType, 581 gsmpControllerDoResync TruthValue, 582 gsmpControllerNotificationMap BITS, 584 gsmpControllerSessionState INTEGER, 585 gsmpControllerStorageType StorageType, 586 gsmpControllerRowStatus RowStatus 587 } 589 gsmpControllerEntityId OBJECT-TYPE 590 SYNTAX GsmpNameType 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "The Switch Controller Entity Id is unique 595 within the operational context of the device." 596 ::= { gsmpControllerEntry 1 } 598 gsmpControllerMaxVersion OBJECT-TYPE 599 SYNTAX GsmpVersion 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "The max version number of the GSMP protocol being used 604 in this session. The version is negotiated by the 605 adjacency protocol." 606 DEFVAL { 3 } 607 ::= { gsmpControllerEntry 2 } 609 gsmpControllerTimer OBJECT-TYPE 610 SYNTAX Unsigned32(1..255) 611 UNITS "100ms" 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "The timer specifies the nominal time between 616 periodic adjacency protocol messages. It is a constant 617 for the duration of a GSMP session. The timer is 618 specified in units of 100ms." 619 DEFVAL { 10 } 620 ::= { gsmpControllerEntry 3 } 622 gsmpControllerPort OBJECT-TYPE 623 SYNTAX Unsigned32 624 MAX-ACCESS read-create 625 STATUS current 626 DESCRIPTION 627 "The local port number for the Switch Controller 628 Entity. The port number is is a 32-bit number that 629 is typically structured into opaque sub-fields that 630 have meaning to the physical structure of the switch 631 (e.g. slot, port)." 632 ::= { gsmpControllerEntry 4 } 634 gsmpControllerInstance OBJECT-TYPE 635 SYNTAX Unsigned32(1..16777215) 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The instance number for the Switch Controller 640 Entity. The Instance number is a 24-bit number 641 that should be guaranteed to be unique within 642 the recent past and to change when the link 643 or node comes back up after going down. Zero is 644 not a valid instance number. " 645 ::= { gsmpControllerEntry 5 } 647 gsmpControllerPartitionType OBJECT-TYPE 648 SYNTAX GsmpPartitionType 649 MAX-ACCESS read-create 650 STATUS current 651 DESCRIPTION 652 "A controller can request the specific partition identifier 653 to the session by setting the Partition Type to 654 fixedPartitionRequest(2). A controller can let the switch 655 decide whether it wants to assign a fixed partition ID or 656 not, by setting the Partition Type to noPartition(1)." 657 ::= { gsmpControllerEntry 6 } 659 gsmpControllerPartitionId OBJECT-TYPE 660 SYNTAX GsmpPartitionIdType 661 MAX-ACCESS read-create 662 STATUS current 663 DESCRIPTION 664 "The Id for the specific switch partition that this 665 Switch Controller is concerned with. 666 If partitions are not used or if the controller lets the 667 switch assigns Partition ID, i.e Partition Type = 668 noPartition(1), then this object is undefined." 669 ::= { gsmpControllerEntry 7 } 671 gsmpControllerDoResync OBJECT-TYPE 672 SYNTAX TruthValue 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "This object specifies whether the controller should 677 resynchronise or reset in case of loss of synchronisation. 678 If this object is set to true then the Controller should 679 resync with PFLAG=2 (recovered adjacency)." 680 DEFVAL { true } 681 ::= { gsmpControllerEntry 8 } 683 gsmpControllerNotificationMap OBJECT-TYPE 684 SYNTAX BITS { sessionDown(0), 685 sessionUp(1), 686 sendFailureIndication(2), 687 receivedFailureIndication(3), 688 portUpEvent(4), 689 portDownEvent(5), 690 invalidLabelEvent(6), 691 newPortEvent(7), 692 deadPortEvent(8), 693 adjacencyUpdateEvent(9) 694 } 695 MAX-ACCESS read-create 696 STATUS current 697 DESCRIPTION 698 "This bitmap defines whether a corresponding SNMP 699 notification should be sent if a GSMP event is received 700 by the Switch Controller. If the bit is set to 1 a 701 notification should be sent. The handling and filtering of 702 the SNMP notifications are then further specified in the 703 SNMP notification originator application. " 704 DEFVAL {{ sessionDown, sessionUp, 705 sendFailureIndication, receivedFailureIndication }} 706 ::= { gsmpControllerEntry 9 } 708 gsmpControllerSessionState OBJECT-TYPE 709 SYNTAX INTEGER { null(1), 710 synsent(2), 711 synrcvd(3), 712 estab(4) 713 } 714 MAX-ACCESS read-only 715 STATUS current 716 DESCRIPTION 717 "The state for the existing or potential session that 718 this entity is concerned with. 719 The NULL state is returned if the proper encapsulation 720 data is not yet configured, if the row is not in active 721 status or if the session is in NULL state as defined in 722 the GSMP specification." 723 ::= { gsmpControllerEntry 10} 725 gsmpControllerStorageType OBJECT-TYPE 726 SYNTAX StorageType 727 MAX-ACCESS read-create 728 STATUS current 729 DESCRIPTION 730 "The storage type for this controller entity. A 731 row which is volatile(2) is lost upon reboot. A row which 732 is either nonVolatile(3), permanent(4) or readOnly(5), is 733 backed up by stable storage. A row which is permanent(4) 734 can be changed but not deleted. A row which is readOnly(5) 735 cannot be changed nor deleted." 736 ::= { gsmpControllerEntry 11 } 738 gsmpControllerRowStatus OBJECT-TYPE 739 SYNTAX RowStatus 740 MAX-ACCESS read-create 741 STATUS current 742 DESCRIPTION 743 "An object that allows entries in this table to 744 be created and deleted using the 745 RowStatus convention. 746 While the row is in active state it's not 747 possible to modify the value of any object 748 for that row exept the gsmpControllerNotificationMap 749 and the gsmpControllerRowStatus objects." 750 ::= { gsmpControllerEntry 12 } 752 -- 753 -- Switch Entity table 754 -- 756 gsmpSwitchTable OBJECT-TYPE 757 SYNTAX SEQUENCE OF GsmpSwitchEntry 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "This table represents the Switch 762 Entities. An entry in this table needs to be configured 763 (created) before a GSMP session might be started." 764 ::= { gsmpObjects 2 } 766 gsmpSwitchEntry OBJECT-TYPE 767 SYNTAX GsmpSwitchEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "An entry in the table showing 772 the data for a specific Switch 773 Entity. If partitions are used, one entity 774 corresponds to one specific switch partition. 775 Depending of the encapsulation used, 776 a corresponding row in the gsmpAtmEncapTable or the 777 gsmpTcpIpEncapTable may have been created." 778 INDEX { gsmpSwitchEntityId } 779 ::= { gsmpSwitchTable 1 } 781 GsmpSwitchEntry ::= SEQUENCE { 782 gsmpSwitchEntityId GsmpNameType, 783 gsmpSwitchMaxVersion GsmpVersion, 784 gsmpSwitchTimer Unsigned32, 785 gsmpSwitchName GsmpNameType, 786 gsmpSwitchPort Unsigned32, 787 gsmpSwitchInstance Unsigned32, 788 gsmpSwitchPartitionType GsmpPartitionType, 789 gsmpSwitchPartitionId GsmpPartitionIdType, 790 gsmpSwitchNotificationMap BITS, 791 gsmpSwitchSwitchType OCTET STRING, 792 gsmpSwitchWindowSize Unsigned32, 793 gsmpSwitchSessionState INTEGER, 794 gsmpSwitchStorageType StorageType, 795 gsmpSwitchRowStatus RowStatus 796 } 798 gsmpSwitchEntityId OBJECT-TYPE 799 SYNTAX GsmpNameType 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "The Switch Entity Id is unique 804 within the operational context of the device. " 805 ::= { gsmpSwitchEntry 1 } 807 gsmpSwitchMaxVersion OBJECT-TYPE 808 SYNTAX GsmpVersion 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "The max version number of the GSMP protocol being 813 supported by this Switch. The version is negotiated by 814 the adjacency protocol." 815 DEFVAL { 3 } 816 ::= { gsmpSwitchEntry 2 } 818 gsmpSwitchTimer OBJECT-TYPE 819 SYNTAX Unsigned32(1..255) 820 UNITS "100ms" 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "The timer specifies the nominal time between 825 periodic adjacency protocol messages. It is a constant 827 for the duration of a GSMP session. The timer is 828 specified in units of 100ms." 829 DEFVAL { 10 } 830 ::= { gsmpSwitchEntry 3 } 832 gsmpSwitchName OBJECT-TYPE 833 SYNTAX GsmpNameType 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "The name of the Switch. The first three octets must be an 838 Organisationally Unique Identifier (OUI) that identifies 839 the manufacturer of the Switch. This is by default set to 840 the same value as the gsmpSwitchId object if not 841 separately specified. " 842 ::= {gsmpSwitchEntry 4 } 844 gsmpSwitchPort OBJECT-TYPE 845 SYNTAX Unsigned32 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "The local port number for this Switch Entity. 850 The port number is is a 32-bit number that 851 is typically structured into opaque sub-fields that 852 have meaning to the physical structure of the switch 853 (e.g. slot, port)" 854 ::= { gsmpSwitchEntry 5 } 856 gsmpSwitchInstance OBJECT-TYPE 857 SYNTAX Unsigned32(1..16777215) 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The instance number for the Switch Entity. 862 The Instance number is a 24-bit number 863 that should be guaranteed to be unique within 864 the recent past and to change when the link 865 or node comes back up after going down. Zero is 866 not a valid instance number." 867 ::= { gsmpSwitchEntry 6 } 869 gsmpSwitchPartitionType OBJECT-TYPE 870 SYNTAX GsmpPartitionType 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "A switch can assign the specific partition identifier to 875 the session by setting the Partition Type to 876 fixedPartitionAssigned(3). A switch can specify 877 that no partitions are handled in the session by setting 878 the Partition Type to noPartition(1)." 879 ::= { gsmpSwitchEntry 7 } 881 gsmpSwitchPartitionId OBJECT-TYPE 882 SYNTAX GsmpPartitionIdType 883 MAX-ACCESS read-create 884 STATUS current 885 DESCRIPTION 886 "The Id for this specific switch partition that the switch 887 entity represents. If partitions are not used, i.e. 888 Partition Type = noPartition(1), then this object is 889 undefined." 890 ::= { gsmpSwitchEntry 8 } 892 gsmpSwitchNotificationMap OBJECT-TYPE 893 SYNTAX BITS { sessionDown(0), 894 sessionUp(1), 895 sendFailureIndication(2), 896 receivedFailureIndication(3), 897 portUpEvent(4), 898 portDownEvent(5), 899 invalidLabelEvent(6), 900 newPortEvent(7), 901 deadPortEvent(8), 902 adjacencyUpdateEvent(9) 903 } 904 MAX-ACCESS read-create 905 STATUS current 906 DESCRIPTION 907 "This bitmap defines whether a corresponding SNMP 908 notification should be sent if an GSMP event is sent 909 by the Switch Entity. If the bit is set to 1 a 910 notification should be sent. The handling and filtering of 911 the SNMP notifications are then further specified in the 912 SNMP notification originator application. " 913 DEFVAL {{ sessionDown, sessionUp, 914 sendFailureIndication, receivedFailureIndication }} 915 ::= { gsmpSwitchEntry 9 } 917 gsmpSwitchSwitchType OBJECT-TYPE 918 SYNTAX OCTET STRING (SIZE(2)) 919 MAX-ACCESS read-create 920 STATUS current 921 DESCRIPTION 922 "A 16-bit field allocated by the manufacturer 923 of the switch. The Switch Type 924 identifies the product. When the Switch Type is combined 925 with the OUI from the Switch Name the product is 926 uniquely identified. " 927 ::= { gsmpSwitchEntry 10 } 929 gsmpSwitchWindowSize OBJECT-TYPE 930 SYNTAX Unsigned32(1..65535) 931 MAX-ACCESS read-create 932 STATUS current 933 DESCRIPTION 934 "The maximum number of unacknowledged request messages 935 that may be transmitted by the controller without the 936 possibility of loss. This field is used to prevent 937 request messages from being lost in the switch because of 938 overflow in the receive buffer. The field is a hint to 939 the controller." 940 ::= { gsmpSwitchEntry 11 } 942 gsmpSwitchSessionState OBJECT-TYPE 943 SYNTAX INTEGER { null(1), 944 synsent(2), 945 synrcvd(3), 946 estab(4) 947 } 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "The state for the existing or potential session that 952 this entity is concerned with. 953 The NULL state is returned if the proper encapsulation 954 data is not yet configured, if the row is not in active 955 status or if the session is in NULL state as defined in 956 the GSMP specification." 957 ::= { gsmpSwitchEntry 12} 959 gsmpSwitchStorageType OBJECT-TYPE 960 SYNTAX StorageType 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "The storage type for this switch entity. 965 A row which is volatile(2) is lost upon reboot. A row which 966 is either nonVolatile(3), permanent(4) or readOnly(5), is 967 backed up by stable storage. A row which is permanent(4) 968 can be changed but not deleted. A row which is readOnly(5) 969 cannot be changed nor deleted." 970 ::= { gsmpSwitchEntry 13 } 972 gsmpSwitchRowStatus OBJECT-TYPE 973 SYNTAX RowStatus 974 MAX-ACCESS read-create 975 STATUS current 976 DESCRIPTION 977 "An object that allows entries in this table to 978 be created and deleted using the 979 RowStatus convention. 980 While the row is in active state it's not 981 possible to modify the value of any object 982 for that row exept the gsmpSwitchNotificationMap 983 and the gsmpSwitchRowStatus objects." 984 ::= { gsmpSwitchEntry 14 } 986 --************************************************************** 987 -- GSMP Encapsulation Objects 988 --************************************************************** 990 -- 991 -- GSMP ATM Encapsulation Table 992 -- 994 gsmpAtmEncapTable OBJECT-TYPE 995 SYNTAX SEQUENCE OF GsmpAtmEncapEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "This table contains the atm encapsulation data 1000 for the Controller or Switch that uses atm aal5 as 1001 encapsulation. " 1002 ::= { gsmpObjects 3 } 1004 gsmpAtmEncapEntry OBJECT-TYPE 1005 SYNTAX GsmpAtmEncapEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "An entry in the table showing 1010 the encapsulation data for a specific 1011 Switch Controller entity or Switch entity." 1012 INDEX { gsmpAtmEncapEntityId } 1013 ::= { gsmpAtmEncapTable 1 } 1015 GsmpAtmEncapEntry ::= SEQUENCE { 1016 gsmpAtmEncapEntityId GsmpNameType, 1017 gsmpAtmEncapIfIndex InterfaceIndex, 1018 gsmpAtmEncapVpi AtmVpIdentifier, 1019 gsmpAtmEncapVci AtmVcIdentifier, 1020 gsmpAtmEncapStorageType StorageType, 1022 gsmpAtmEncapRowStatus RowStatus 1023 } 1025 gsmpAtmEncapEntityId OBJECT-TYPE 1026 SYNTAX GsmpNameType 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "The Controller Id or Switch Id that is unique 1031 within the operational context of the device. " 1032 ::= { gsmpAtmEncapEntry 1 } 1034 gsmpAtmEncapIfIndex OBJECT-TYPE 1035 SYNTAX InterfaceIndex 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "The interface index for the virtual channel over which 1040 the GSMP session is established, i.e., the GSMP control 1041 channel for LLC/SNAP encapsulated GSMP messages on an 1042 ATM data link layer." 1043 ::= { gsmpAtmEncapEntry 2 } 1045 gsmpAtmEncapVpi OBJECT-TYPE 1046 SYNTAX AtmVpIdentifier 1047 MAX-ACCESS read-create 1048 STATUS current 1049 DESCRIPTION 1050 " The VPI value for the virtual channel over which the 1051 GSMP session is established, i.e., the GSMP control 1052 channel for LLC/SNAP encapsulated GSMP messages on an 1053 ATM data link layer." 1054 DEFVAL { 0 } 1055 ::= { gsmpAtmEncapEntry 3 } 1057 gsmpAtmEncapVci OBJECT-TYPE 1058 SYNTAX AtmVcIdentifier 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 " The VCI value for the virtual channel over which the 1063 GSMP session is established, i.e., the GSMP control 1064 channel for LLC/SNAP encapsulated GSMP messages on an 1065 ATM data link layer." 1066 DEFVAL { 15 } 1067 ::= { gsmpAtmEncapEntry 4 } 1069 gsmpAtmEncapStorageType OBJECT-TYPE 1070 SYNTAX StorageType 1071 MAX-ACCESS read-create 1072 STATUS current 1073 DESCRIPTION 1074 "The storage type for this entry. It should have the same 1075 valur as the StorageType in the refering Switch Controller 1076 entity or Switch entity. A 1077 row which is volatile(2) is lost upon reboot. A row which 1078 is either nonVolatile(3), permanent(4) or readOnly(5), is 1079 backed up by stable storage. A row which is permanent(4) 1080 can be changed but not deleted. A row which is readOnly(5) 1081 cannot be changed nor deleted." 1082 ::= { gsmpAtmEncapEntry 5 } 1084 gsmpAtmEncapRowStatus OBJECT-TYPE 1085 SYNTAX RowStatus 1086 MAX-ACCESS read-create 1087 STATUS current 1088 DESCRIPTION 1089 "An object that allows entries in this table to 1090 be created and deleted using the 1091 RowStatus convention. 1092 While the row is in active state it's not 1093 possible to modify the value of any object 1094 for that row exept the gsmpAtmEncapRowStatus object." 1095 ::= { gsmpAtmEncapEntry 6 } 1097 -- 1098 -- GSMP TCP/IP Encapsulation Table 1099 -- 1101 gsmpTcpIpEncapTable OBJECT-TYPE 1102 SYNTAX SEQUENCE OF GsmpTcpIpEncapEntry 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "This table contains the encapsulation data 1107 for the Controller or Switch that uses TCP/IP as 1108 encapsulation." 1109 ::= { gsmpObjects 4 } 1111 gsmpTcpIpEncapEntry OBJECT-TYPE 1112 SYNTAX GsmpTcpIpEncapEntry 1113 MAX-ACCESS not-accessible 1114 STATUS current 1115 DESCRIPTION 1116 "An entry in the table showing 1117 the encapsulation data for a specific 1118 Switch Controller entity or Switch entity." 1119 INDEX { gsmpTcpIpEncapEntityId } 1121 ::= { gsmpTcpIpEncapTable 1 } 1123 GsmpTcpIpEncapEntry ::= SEQUENCE { 1124 gsmpTcpIpEncapEntityId GsmpNameType, 1125 gsmpTcpIpEncapAddressType InetAddressType, 1126 gsmpTcpIpEncapAddress InetAddress, 1127 gsmpTcpIpEncapPortNumber Unsigned32, 1128 gsmpTcpIpEncapStorageType StorageType, 1129 gsmpTcpIpEncapRowStatus RowStatus 1130 } 1132 gsmpTcpIpEncapEntityId OBJECT-TYPE 1133 SYNTAX GsmpNameType 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "The Controller or Switch Id is unique 1138 within the operational context of the device. " 1139 ::= { gsmpTcpIpEncapEntry 1 } 1141 gsmpTcpIpEncapAddressType OBJECT-TYPE 1142 SYNTAX InetAddressType 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "The type of address in gsmpTcpIpEncapAddress." 1147 ::= { gsmpTcpIpEncapEntry 2 } 1149 gsmpTcpIpEncapAddress OBJECT-TYPE 1150 SYNTAX InetAddress 1151 MAX-ACCESS read-create 1152 STATUS current 1153 DESCRIPTION 1154 "The IPv4 or IPv6 address used for 1155 the GSMP session peer." 1156 ::= { gsmpTcpIpEncapEntry 3 } 1158 gsmpTcpIpEncapPortNumber OBJECT-TYPE 1159 SYNTAX Unsigned32(1..65535) 1160 MAX-ACCESS read-create 1161 STATUS current 1162 DESCRIPTION 1163 "The TCP port number used for the TCP session 1164 establishment to the GSMP peer." 1165 DEFVAL { 6068 } 1166 ::= { gsmpTcpIpEncapEntry 4 } 1168 gsmpTcpIpEncapStorageType OBJECT-TYPE 1169 SYNTAX StorageType 1170 MAX-ACCESS read-create 1171 STATUS current 1172 DESCRIPTION 1173 "The storage type for this entry. It should have the same 1174 value as the StorageType in the refering Switch Controller 1175 entity or Switch entity. A 1176 row which is volatile(2) is lost upon reboot. A row which 1177 is either nonVolatile(3), permanent(4) or readOnly(5), is 1178 backed up by stable storage. A row which is permanent(4) 1179 can be changed but not deleted. A row which is readOnly(5) 1180 cannot be changed nor deleted." 1181 ::= { gsmpTcpIpEncapEntry 5 } 1183 gsmpTcpIpEncapRowStatus OBJECT-TYPE 1184 SYNTAX RowStatus 1185 MAX-ACCESS read-create 1186 STATUS current 1187 DESCRIPTION 1188 "An object that allows entries in this table to 1189 be created and deleted using the 1190 RowStatus convention. 1191 While the row is in active state it's not 1192 possible to modify the value of any object 1193 for that row exept the gsmpTcpIpEncapRowStatus object." 1194 ::= { gsmpTcpIpEncapEntry 6 } 1196 --************************************************************** 1197 -- GSMP Session Objects 1198 --************************************************************** 1200 -- 1201 -- GSMP Session table 1202 -- 1204 gsmpSessionTable OBJECT-TYPE 1205 SYNTAX SEQUENCE OF GsmpSessionEntry 1206 MAX-ACCESS not-accessible 1207 STATUS current 1208 DESCRIPTION 1209 "This table represents the sessions between 1210 Controller and Switch pairs. " 1211 ::= { gsmpObjects 5 } 1213 gsmpSessionEntry OBJECT-TYPE 1214 SYNTAX GsmpSessionEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "An entry in the table showing 1220 the session data for a specific Controller and 1221 Switch pair. Also, statistics for this specific 1222 session is shown." 1223 INDEX { gsmpSessionThisSideId, gsmpSessionFarSideId } 1224 ::= { gsmpSessionTable 1 } 1226 GsmpSessionEntry ::= SEQUENCE { 1227 gsmpSessionThisSideId GsmpNameType, 1228 gsmpSessionFarSideId GsmpNameType, 1229 gsmpSessionVersion GsmpVersion, 1230 gsmpSessionTimer Integer32, 1231 gsmpSessionPartitionId GsmpPartitionIdType, 1232 gsmpSessionAdjacencyCount Unsigned32, 1233 gsmpSessionFarSideName GsmpNameType, 1234 gsmpSessionFarSidePort Unsigned32, 1235 gsmpSessionFarSideInstance Unsigned32, 1236 gsmpSessionLastFailureCode Unsigned32, 1237 gsmpSessionDiscontinuityTime TimeStamp, 1238 gsmpSessionStartUptime TimeStamp, 1239 gsmpSessionStatSentMessages Counter32, 1240 gsmpSessionStatFailureInds Counter32, 1241 gsmpSessionStatReceivedMessages Counter32, 1242 gsmpSessionStatReceivedFailures Counter32, 1243 gsmpSessionStatPortUpEvents Counter32, 1244 gsmpSessionStatPortDownEvents Counter32, 1245 gsmpSessionStatInvLabelEvents Counter32, 1246 gsmpSessionStatNewPortEvents Counter32, 1247 gsmpSessionStatDeadPortEvents Counter32, 1248 gsmpSessionStatAdjUpdateEvents Counter32 1249 } 1251 gsmpSessionThisSideId OBJECT-TYPE 1252 SYNTAX GsmpNameType 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION 1256 "This side ID uniquely identifies the entity that this 1257 session relates to within the operational 1258 context of the device. " 1259 ::= { gsmpSessionEntry 1 } 1261 gsmpSessionFarSideId OBJECT-TYPE 1262 SYNTAX GsmpNameType 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "The Far side ID uniquely identifies the entity that this 1267 session is established against. " 1268 ::= { gsmpSessionEntry 2 } 1270 gsmpSessionVersion OBJECT-TYPE 1271 SYNTAX GsmpVersion 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "The version number of the GSMP protocol being used in 1276 this session. The version is the result of the 1277 negotiation by the adjacency protocol." 1278 ::= { gsmpSessionEntry 3 } 1280 gsmpSessionTimer OBJECT-TYPE 1281 SYNTAX Integer32 1282 UNITS "100ms" 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "The timer specifies the time remaining until the 1287 adjacency timer expires. The object could take negative 1288 values since if no valid GSMP messages are 1289 received in any period of time in excess of three times 1290 the value of the Timer negotiated by the adjacency 1291 protocol loss of synchronisation may be declared. The 1292 timer is specified in units of 100ms." 1293 ::= { gsmpSessionEntry 4 } 1295 gsmpSessionPartitionId OBJECT-TYPE 1296 SYNTAX GsmpPartitionIdType 1297 MAX-ACCESS read-only 1298 STATUS current 1299 DESCRIPTION 1300 "The Partition Id for the specific switch partition that 1301 this session is concerned with." 1302 ::= { gsmpSessionEntry 5 } 1304 gsmpSessionAdjacencyCount OBJECT-TYPE 1305 SYNTAX Unsigned32(1..255) 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "This object specifies the current number of adjacencies 1310 that are established with controllers and the switch 1311 partition that is used for this session. The value 1312 includes this session." 1313 ::= { gsmpSessionEntry 6 } 1315 gsmpSessionFarSideName OBJECT-TYPE 1316 SYNTAX GsmpNameType 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "The name of the far side as advertised in the adjacency 1321 message." 1322 ::= {gsmpSessionEntry 7} 1324 gsmpSessionFarSidePort OBJECT-TYPE 1325 SYNTAX Unsigned32 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The local port number of the link across which the 1330 message is being sent." 1331 ::= { gsmpSessionEntry 8 } 1333 gsmpSessionFarSideInstance OBJECT-TYPE 1334 SYNTAX Unsigned32(1..16777215) 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The instance number used for the link during this 1339 session. The Instance number is a 24-bit number 1340 that should be guaranteed to be unique within 1341 the recent past and to change when the link 1342 or node comes back up after going down. Zero is not 1343 a valid instance number." 1344 ::= { gsmpSessionEntry 9 } 1346 gsmpSessionLastFailureCode OBJECT-TYPE 1347 SYNTAX Unsigned32(0..255) 1348 MAX-ACCESS read-only 1349 STATUS current 1350 DESCRIPTION 1351 "This is the last failure code that was received over 1352 this session. If no failure code have been received, the 1353 value is zero." 1354 ::= { gsmpSessionEntry 10 } 1356 gsmpSessionDiscontinuityTime OBJECT-TYPE 1357 SYNTAX TimeStamp 1358 MAX-ACCESS read-only 1359 STATUS current 1360 DESCRIPTION 1361 "The value of sysUpTime on the most recent occasion at 1362 which one or more of this session's counters 1363 suffered a discontinuity. If no such discontinuities have 1364 occurred since then, this object contains the same 1365 timestamp as gsmpSessionStartUptime ." 1366 ::= { gsmpSessionEntry 11 } 1368 gsmpSessionStartUptime OBJECT-TYPE 1369 SYNTAX TimeStamp 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 " The value of sysUpTime when the session came to 1374 established state." 1375 ::= { gsmpSessionEntry 12 } 1377 gsmpSessionStatSentMessages OBJECT-TYPE 1378 SYNTAX Counter32 1379 MAX-ACCESS read-only 1380 STATUS current 1381 DESCRIPTION 1382 "The number of messages that have been sent in this 1383 session." 1384 ::= { gsmpSessionEntry 13 } 1386 gsmpSessionStatFailureInds OBJECT-TYPE 1387 SYNTAX Counter32 1388 MAX-ACCESS read-only 1389 STATUS current 1390 DESCRIPTION 1391 "The number of messages that have been sent with a 1392 failure indication in this session." 1393 ::= { gsmpSessionEntry 14 } 1395 gsmpSessionStatReceivedMessages OBJECT-TYPE 1396 SYNTAX Counter32 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "The number of messages that have been received in 1401 this session." 1402 ::= { gsmpSessionEntry 15 } 1404 gsmpSessionStatReceivedFailures OBJECT-TYPE 1405 SYNTAX Counter32 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "The number of messages that have been received in 1410 this session with a failure indication." 1411 ::= { gsmpSessionEntry 16 } 1413 gsmpSessionStatPortUpEvents OBJECT-TYPE 1414 SYNTAX Counter32 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "The number of Port Up events that have been sent or 1419 received on this session." 1420 ::= { gsmpSessionEntry 17 } 1422 gsmpSessionStatPortDownEvents OBJECT-TYPE 1423 SYNTAX Counter32 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The number of Port Down events that have been sent or 1428 received on this session." 1429 ::= { gsmpSessionEntry 18 } 1431 gsmpSessionStatInvLabelEvents OBJECT-TYPE 1432 SYNTAX Counter32 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "The number of Invalid label events that have been sent 1437 or received on this session." 1438 ::= { gsmpSessionEntry 19 } 1440 gsmpSessionStatNewPortEvents OBJECT-TYPE 1441 SYNTAX Counter32 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The number of New Port events that have been sent or 1446 received on this session." 1447 ::= { gsmpSessionEntry 20 } 1449 gsmpSessionStatDeadPortEvents OBJECT-TYPE 1450 SYNTAX Counter32 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "The number of Dead Port events that have been sent or 1455 received on this session." 1456 ::= { gsmpSessionEntry 21 } 1458 gsmpSessionStatAdjUpdateEvents OBJECT-TYPE 1459 SYNTAX Counter32 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION 1463 "The number of Adjacency Update events that have been sent 1464 or received on this session." 1466 ::= { gsmpSessionEntry 22 } 1468 -- ************************************************************** 1469 -- GSMP Notifications 1470 -- ************************************************************** 1472 -- 1473 -- Notification objects 1474 -- 1476 gsmpEventPort OBJECT-TYPE 1477 SYNTAX Unsigned32 1478 MAX-ACCESS accessible-for-notify 1479 STATUS current 1480 DESCRIPTION 1481 "This object specifies the Port Number that is 1482 carried in this event." 1483 ::= { gsmpNotificationsObjects 1 } 1485 gsmpEventPortSessionNumber OBJECT-TYPE 1486 SYNTAX Unsigned32 1487 MAX-ACCESS accessible-for-notify 1488 STATUS current 1489 DESCRIPTION 1490 "This object specifies the Port Session Number that is 1491 carried in this event." 1492 ::= { gsmpNotificationsObjects 2 } 1494 gsmpEventSequenceNumber OBJECT-TYPE 1495 SYNTAX Unsigned32 1496 MAX-ACCESS accessible-for-notify 1497 STATUS current 1498 DESCRIPTION 1499 "This object specifies the Event Sequence Number that is 1500 carried in this event." 1501 ::= { gsmpNotificationsObjects 3 } 1503 gsmpEventLabel OBJECT-TYPE 1504 SYNTAX GsmpLabelType 1505 MAX-ACCESS accessible-for-notify 1506 STATUS current 1507 DESCRIPTION 1508 "This object specifies the Label that is 1509 carried in this event." 1510 ::= { gsmpNotificationsObjects 4 } 1512 -- 1513 -- Notifications 1514 -- 1516 gsmpSessionDown NOTIFICATION-TYPE 1517 OBJECTS { 1518 gsmpSessionStartUptime, 1519 gsmpSessionStatSentMessages, 1520 gsmpSessionStatFailureInds, 1521 gsmpSessionStatReceivedMessages, 1522 gsmpSessionStatReceivedFailures, 1523 gsmpSessionStatPortUpEvents, 1524 gsmpSessionStatPortDownEvents, 1525 gsmpSessionStatInvLabelEvents, 1526 gsmpSessionStatNewPortEvents, 1527 gsmpSessionStatDeadPortEvents, 1528 gsmpSessionStatAdjUpdateEvents 1529 } 1530 STATUS current 1531 DESCRIPTION 1532 "When it has been enabled, this notification is 1533 generated whenever a session is taken down, regardless 1534 of whether the session went down normally or not. 1535 Its purpose is to allow a management application 1536 (primarily an accounting application) that is 1537 monitoring the session statistics to receive the final 1538 values of these counters, so that the application can 1539 properly account for the amounts the counters were 1540 incremented since the last time the application polled 1541 them. The gsmpSessionStartUptime object provides the 1542 total amount of time that the session was active. 1544 This notification is not a substitute for polling the 1545 session statistic counts. In particular, the count 1546 values reported in this notification cannot be assumed 1547 to be the complete totals for the life of the session, 1548 since they may have wrapped while the 1549 session was up. 1551 The session to which this notification 1552 applies is identified by the gsmpSessionThisSideId and 1553 gsmpSessionFarSideId which could be inferred from the 1554 Object Identifiers of the objects contained in the 1555 notification. 1556 An instance of this notification will contain exactly 1557 one instance of each of its objects, and these objects 1558 will all belong to the same conceptual row of the 1559 gsmpSessionTable." 1560 ::= { gsmpNotifications 1 } 1561 gsmpSessionUp NOTIFICATION-TYPE 1562 OBJECTS { 1563 gsmpSessionFarSideInstance 1564 } 1565 STATUS current 1566 DESCRIPTION 1567 "When it has been enabled, this notification is 1568 generated when new session is established. 1570 The new session is identified by the gsmpSessionThisSideId 1571 and gsmpSessionFarSideId which could be inferred from the 1572 Object Identifier of the gsmpSessionFarSideInstance object 1573 contained in the notification." 1574 ::= { gsmpNotifications 2 } 1576 gsmpSentFailureInd NOTIFICATION-TYPE 1577 OBJECTS { 1578 gsmpSessionLastFailureCode, 1579 gsmpSessionStatFailureInds 1580 } 1581 STATUS current 1582 DESCRIPTION 1583 "When it has been enabled, this notification is 1584 generated when a message with a failure indication was 1585 sent. 1587 The notification indicates a change in the value of 1588 gsmpSessionStatFailureInds. The 1589 gsmpSessionLastFailureCode contains the failure 1590 reason. 1592 The session to which this notification 1593 applies is identified by the gsmpSessionThisSideId and 1594 gsmpSessionFarSideId which could be inferred from the 1595 Object Identifiers of the objects contained in the 1596 notification." 1597 ::= { gsmpNotifications 3 } 1599 gsmpReceivedFailureInd NOTIFICATION-TYPE 1600 OBJECTS { 1601 gsmpSessionLastFailureCode, 1602 gsmpSessionStatReceivedFailures 1603 } 1604 STATUS current 1605 DESCRIPTION 1606 "When it has been enabled, this notification is 1607 generate when a message with a failure indication 1608 is received. 1610 The notification indicates a change in the value of 1611 gsmpSessionStatReceivedFailures. The 1612 gsmpSessionLastFailureCode contains the failure 1613 reason. 1615 The session to which this notification 1616 applies is identified by the gsmpSessionThisSideId and 1617 gsmpSessionFarSideId which could be inferred from the 1618 Object Identifiers of the objects contained in the 1619 notification." 1620 ::= { gsmpNotifications 4 } 1622 gsmpPortUpEvent NOTIFICATION-TYPE 1623 OBJECTS { 1624 gsmpSessionStatPortUpEvents, 1625 gsmpEventPort, 1626 gsmpEventPortSessionNumber, 1627 gsmpEventSequenceNumber 1628 } 1629 STATUS current 1630 DESCRIPTION 1631 "When it has been enabled, this notification is 1632 generated when a Port Up Event occurs. 1634 The notification indicates a change in the value of 1635 gsmpSessionStatPortUpEvents. 1637 The session to which this notification 1638 applies is identified by the gsmpSessionThisSideId and 1639 gsmpSessionFarSideId which could be inferred from the 1640 Object Identifier of the gsmpSessionStatPortUpEvents 1641 object contained in the notification." 1642 ::= { gsmpNotifications 5 } 1644 gsmpPortDownEvent NOTIFICATION-TYPE 1645 OBJECTS { 1646 gsmpSessionStatPortDownEvents, 1647 gsmpEventPort, 1648 gsmpEventPortSessionNumber, 1649 gsmpEventSequenceNumber 1650 } 1651 STATUS current 1652 DESCRIPTION 1653 "When it has been enabled, this notification is 1654 generated when a Port Down Event occurs. 1656 The notification indicates a change in the value of 1657 gsmpSessionStatPortDownEvents. 1659 The session to which this notification 1660 applies is identified by the gsmpSessionThisSideId and 1661 gsmpSessionFarSideId which could be inferred from the 1662 Object Identifier of the gsmpSessionStatPortDownEvents 1663 object contained in the notification." 1664 ::= { gsmpNotifications 6 } 1666 gsmpInvalidLabelEvent NOTIFICATION-TYPE 1667 OBJECTS { 1668 gsmpSessionStatInvLabelEvents, 1669 gsmpEventPort, 1670 gsmpEventLabel, 1671 gsmpEventSequenceNumber 1672 } 1673 STATUS current 1674 DESCRIPTION 1675 "When it has been enabled, this notification is 1676 generated when an Invalid Label Event occurs. 1678 The notification indicates a change in the value of 1679 gsmpSessionStatInvLabelEvents. 1681 The session to which this notification 1682 applies is identified by the gsmpSessionThisSideId and 1683 gsmpSessionFarSideId which could be inferred from the 1684 Object Identifier of the gsmpSessionStatInvLabelEvents 1685 object contained in the notification." 1686 ::= { gsmpNotifications 7 } 1688 gsmpNewPortEvent NOTIFICATION-TYPE 1689 OBJECTS { 1690 gsmpSessionStatNewPortEvents, 1691 gsmpEventPort, 1692 gsmpEventPortSessionNumber, 1693 gsmpEventSequenceNumber 1694 } 1695 STATUS current 1696 DESCRIPTION 1697 "When it has been enabled, this notification is 1698 generated when a New Port Event occurs. 1700 The notification indicates a change in the value of 1701 gsmpSessionStatNewPortEvents. 1703 The session to which this notification 1704 applies is identified by the gsmpSessionThisSideId and 1705 gsmpSessionFarSideId which could be inferred from the 1706 Object Identifier of the gsmpSessionStatNewPortEvents 1707 object contained in the notification." 1709 ::= { gsmpNotifications 8 } 1711 gsmpDeadPortEvent NOTIFICATION-TYPE 1712 OBJECTS { 1713 gsmpSessionStatDeadPortEvents, 1714 gsmpEventPort, 1715 gsmpEventPortSessionNumber, 1716 gsmpEventSequenceNumber 1717 } 1718 STATUS current 1719 DESCRIPTION 1720 "When it has been enabled, this notification is 1721 generated when a Dead Port Event occurs. 1723 The notification indicates a change in the value of 1724 gsmpSessionStatDeadPortEvents. 1726 The session to which this notification 1727 applies is identified by the gsmpSessionThisSideId and 1728 gsmpSessionFarSideId which could be inferred from the 1729 Object Identifier of the gsmpSessionStatDeadPortEvents 1730 object contained in the notification." 1731 ::= { gsmpNotifications 9 } 1733 gsmpAdjacencyUpdateEvent NOTIFICATION-TYPE 1734 OBJECTS { 1735 gsmpSessionAdjacencyCount, 1736 gsmpSessionStatAdjUpdateEvents, 1737 gsmpEventSequenceNumber 1738 } 1739 STATUS current 1740 DESCRIPTION 1741 "When it has been enabled, this notification is 1742 generated when an Adjacency Update Event occurs. 1744 The gsmpSessionAdjacencyCount contains the new value of 1745 the number of adjacencies 1746 that are established with controllers and the switch 1747 partition that is used for this session. 1749 The notification indicates a change in the value of 1750 gsmpSessionStatAdjUpdateEvents. 1752 The session to which this notification 1753 applies is identified by the gsmpSessionThisSideId and 1754 gsmpSessionFarSideId which could be inferred from the 1755 Object Identifier of the gsmpSessionAdjacencyCount 1756 or the gsmpSessionStatAdjUpdateEvents object contained 1757 in the notification." 1759 ::= { gsmpNotifications 10 } 1761 --************************************************************** 1762 -- GSMP Compliance 1763 --************************************************************** 1765 gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 } 1766 gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 } 1768 gsmpModuleCompliance MODULE-COMPLIANCE 1769 STATUS current 1770 DESCRIPTION 1771 "The compliance statement for agents that support 1772 the GSMP MIB." 1773 MODULE -- this module 1774 MANDATORY-GROUPS { gsmpGeneralGroup 1775 } 1776 GROUP gsmpControllerGroup 1777 DESCRIPTION 1778 "This group is mandatory for all Switch 1779 Controllers" 1781 GROUP gsmpSwitchGroup 1782 DESCRIPTION 1783 "This group is mandatory for all Switches" 1785 GROUP gsmpAtmEncapGroup 1786 DESCRIPTION 1787 "This group must be supported if ATM is used for GSMP 1788 encapsulation. " 1790 GROUP gsmpTcpIpEncapGroup 1791 DESCRIPTION 1792 "This group must be supported if TCP/IP is used for GSMP 1793 encapsulation. " 1795 OBJECT gsmpTcpIpEncapAddressType 1796 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 1797 DESCRIPTION 1798 "An implementation is only required to support 1799 'unknown(0)', and IPv4 addresses. Supporting IPv6 addresses 1800 is optional. Defining Internet addresses by using DNS 1801 domain names are not allowed." 1803 OBJECT gsmpTcpIpEncapAddress 1804 SYNTAX InetAddress (SIZE(0|4|16|20)) 1805 DESCRIPTION 1806 "An implementation is only required to support 1807 IPv4 addresses. Supporting IPv6 addresses 1808 is optional." 1810 GROUP gsmpNotificationObjectsGroup 1811 DESCRIPTION 1812 "This group must be supported if notifications 1813 are supported. " 1815 GROUP gsmpNotificationsGroup 1816 DESCRIPTION 1817 "This group must be supported if notifications 1818 are supported. " 1820 ::= { gsmpCompliances 1 } 1822 -- units of conformance 1824 gsmpGeneralGroup OBJECT-GROUP 1825 OBJECTS { 1826 gsmpSessionVersion, 1827 gsmpSessionTimer, 1828 gsmpSessionPartitionId, 1829 gsmpSessionAdjacencyCount, 1830 gsmpSessionFarSideName, 1831 gsmpSessionFarSidePort, 1832 gsmpSessionFarSideInstance, 1833 gsmpSessionLastFailureCode, 1834 gsmpSessionDiscontinuityTime, 1835 gsmpSessionStartUptime, 1836 gsmpSessionStatSentMessages, 1837 gsmpSessionStatFailureInds, 1838 gsmpSessionStatReceivedMessages, 1839 gsmpSessionStatReceivedFailures, 1840 gsmpSessionStatPortUpEvents, 1841 gsmpSessionStatPortDownEvents, 1842 gsmpSessionStatInvLabelEvents, 1843 gsmpSessionStatNewPortEvents, 1844 gsmpSessionStatDeadPortEvents, 1845 gsmpSessionStatAdjUpdateEvents 1846 }STATUS current 1847 DESCRIPTION 1848 "Objects that apply to all GSMP implementations." 1849 ::= { gsmpGroups 1 } 1851 gsmpControllerGroup OBJECT-GROUP 1852 OBJECTS { 1853 gsmpControllerMaxVersion, 1854 gsmpControllerTimer, 1855 gsmpControllerPort, 1856 gsmpControllerInstance, 1857 gsmpControllerPartitionType, 1858 gsmpControllerPartitionId, 1859 gsmpControllerDoResync, 1860 gsmpControllerNotificationMap, 1861 gsmpControllerSessionState, 1862 gsmpControllerStorageType, 1863 gsmpControllerRowStatus 1864 } 1865 STATUS current 1866 DESCRIPTION 1867 "Objects that apply GSMP implementations of 1868 Switch Controllers." 1869 ::= { gsmpGroups 2 } 1871 gsmpSwitchGroup OBJECT-GROUP 1872 OBJECTS { 1873 gsmpSwitchMaxVersion, 1874 gsmpSwitchTimer, 1875 gsmpSwitchName, 1876 gsmpSwitchPort, 1877 gsmpSwitchInstance, 1878 gsmpSwitchPartitionType, 1879 gsmpSwitchPartitionId, 1880 gsmpSwitchNotificationMap, 1881 gsmpSwitchSwitchType, 1882 gsmpSwitchWindowSize, 1883 gsmpSwitchSessionState, 1884 gsmpSwitchStorageType, 1885 gsmpSwitchRowStatus 1886 } 1887 STATUS current 1888 DESCRIPTION 1889 "Objects that apply GSMP implementations of 1890 Switches." 1891 ::= { gsmpGroups 3 } 1893 gsmpAtmEncapGroup OBJECT-GROUP 1894 OBJECTS { 1895 gsmpAtmEncapIfIndex, 1896 gsmpAtmEncapVpi, 1897 gsmpAtmEncapVci, 1898 gsmpAtmEncapStorageType, 1899 gsmpAtmEncapRowStatus 1900 } 1901 STATUS current 1902 DESCRIPTION 1903 "Objects that apply to GSMP implementations that 1904 supports ATM for GSMP encapsulation." 1906 ::= { gsmpGroups 4 } 1908 gsmpTcpIpEncapGroup OBJECT-GROUP 1909 OBJECTS { 1910 gsmpTcpIpEncapAddressType, 1911 gsmpTcpIpEncapAddress, 1912 gsmpTcpIpEncapPortNumber, 1913 gsmpTcpIpEncapStorageType, 1914 gsmpTcpIpEncapRowStatus 1915 } 1916 STATUS current 1917 DESCRIPTION 1918 "Objects that apply to GSMP implementations that 1919 supports TCP/IP for GSMP encapsulation." 1920 ::= { gsmpGroups 5 } 1922 gsmpNotificationObjectsGroup OBJECT-GROUP 1923 OBJECTS { 1924 gsmpEventPort, 1925 gsmpEventPortSessionNumber, 1926 gsmpEventSequenceNumber, 1927 gsmpEventLabel} 1928 STATUS current 1929 DESCRIPTION 1930 "Objects that are contained in the notifications." 1931 ::= { gsmpGroups 6 } 1933 gsmpNotificationsGroup NOTIFICATION-GROUP 1934 NOTIFICATIONS { 1935 gsmpSessionDown, 1936 gsmpSessionUp, 1937 gsmpSentFailureInd, 1938 gsmpReceivedFailureInd, 1939 gsmpPortUpEvent, 1940 gsmpPortDownEvent, 1941 gsmpInvalidLabelEvent, 1942 gsmpNewPortEvent, 1943 gsmpDeadPortEvent, 1944 gsmpAdjacencyUpdateEvent 1945 } 1946 STATUS current 1947 DESCRIPTION 1948 "The notifications which indicate specific changes 1949 in the value of objects gsmpSessionTable" 1950 ::= { gsmpGroups 7 } 1952 END 1953 5. Revision History 1955 This section should be removed when this document is published as an 1956 RFC. 1958 5.1 Changes from < draft-ietf-gsmp-mib-00.txt > 1960 Mib totally remade :-) 1962 5.2 Changes from < draft-ietf-gsmp-mib-01.txt > 1964 Besides from editorial changes the following updates was made; 1965 - Imported AtmVcIdentifier, AtmVpIdentifier FROM ATM-TC-MIB 1966 - Removed serviceModelType 1967 - Separated the Vse and Vsce config stuf in separate tables. 1968 - Also added ATM,TCP/IP, Vse and Vsce groups 1969 - Added control of multiple controllers 1970 - Added Vse window size and switch type configuration. 1971 - Added control of resync strategy 1972 - Added last failure code and discontinuity time 1973 - Added event config and count 1974 - Added notifications 1976 5.3 Changes from < draft-ietf-gsmp-mib-02.txt > 1978 Besides from editorial changes the following updates was made; 1979 - Added gsmpThisSideId and gsmpFarSideId helper objects. 1980 - Replaced Ipv4 address type with TC for Internet Network 1981 Addresses 1982 - Added textual conventions for reader convenience. 1983 - Removed gsmpVsceName object and added default behaviour of 1984 gsmpVseName 1985 - Added row status objects for the encap tables. 1986 - Added DEFVAL and ranges to objects. 1987 - Persistent storage clarified 1988 - "Virtual" removed from names and concepts. gsmpVsceTable now 1989 gsmpControllerTable and gsmpVseTable is gsmpSwitchTable. 1990 - Partition Type object added. 1991 - Session state moved from Session table to Controller and 1992 Switch tables. 1993 - Removed gsmpSwitchAllowMultContr object, it's redundant. 1994 - BITS import removed. 1995 - Partition ID object added to session table. 1996 - gsmpSessionStat table merged into the gsmpSessionTable. 1998 5.4 Changes from < draft-ietf-gsmp-mib-03.txt > 2000 The following updates was made; 2001 - Clarified behaviour on gsmpSessionDiscontinuityTime. 2002 � Changed contact info 2004 5.5 Changes from < draft-ietf-gsmp-mib-04.txt > 2006 Besides from editorial changes the following updates was made; 2007 - Added more text about the generic concepts of GSMP. 2008 - IF-MIB is now RFC 2863, not 2233 2009 - In CONTACT INFO, added WG mailing list,subscribe,archive info 2010 - Added a REVISION clause to the MODULE-IDENTITY 2011 - Notification OIDs updated with less overhead 2012 - Removed trap from Notification names 2013 - Added text about rows created outside SNMP. 2014 - Clarified port and instance number descriptions. 2015 - Clarified when objects can be changed in active row 2016 - gsmpSessionStatUptime changed to TimeStamp and renamed to 2017 gsmpSessionStartUptime 2018 - gsmpSessionStatFailureIndication renamed gsmpSessionStatFailureInds 2019 - ReceivedFailure got an s for plurality 2020 - gsmpEventLabel now of GsmpLabelType (new TC based on octet string). 2021 - Added SYNTAX clauses to inet-address objects compliance. 2022 - GsmpVersion TC changed from enumerated to Unsigned32 2023 - controller and switch instance numbers changed to read-only 2024 - gsmpThisSideId and gsmpFarSideId removed from Notifications, 2025 session ids is inferred from OIDs of the objects instead. 2026 - gsmpThisSideId and gsmpFarSideId objects removed 2027 - StorageType object added. 2028 - encapType objects removed, instead encap type is given by a 2029 encap entry with same id. 2030 - Creation order defined. 2031 - ptype updated to align with draft-ietf-gsmp-09 2033 6. Acknowledgments 2035 The authors would like to thank Avri Doria and Kenneth Sundell for 2036 their contributions to this specification. Also thanks to David 2037 Partain and Bert Wijnen who has contributed significantly with their 2038 SNMP expertise. 2040 7. References 2042 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2043 of Management Information for TCP/IP-based Internets", STD 2044 16, RFC 1155, May 1990 2046 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2047 16, RFC 1212, March 1991 2049 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2050 SNMP", RFC 1215, March 1991 2052 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2053 Network Management Protocol", STD 15, RFC 1157, May 1990. 2055 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2056 "Introduction to Community-based SNMPv2", RFC 1901, January 2057 1996. 2059 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2060 "Protocol Operations for Version 2 of the Simple Network 2061 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2063 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2064 "Transport Mappings for Version 2 of the Simple Network 2065 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2067 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching 2068 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 2069 Switch Management Protocol Specification," Version 1.1, 2070 RFC 1987, August 1996. 2072 [RFC2026] Bradner, S., "The Internet Standards Process - Revision 2073 3", BCP 9, RFC 2026, Harvard University, October 1996 2075 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2076 Requirement Levels", BCP 14, RFC 2119, Harvard University, 2077 March 1997 2079 [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching 2080 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 2081 Switch Management Protocol Specification," Version 2.0, 2082 RFC 2397, March 1998. 2084 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an 2085 IANA Considerations Section in RFCs.", RFC 2434, IBM, 2086 Maxware, October 1998 2088 [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual 2089 Conventions and OBJECT-IDENTITIES for ATM Management", 2090 RFC 2514, February 1999. 2092 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2093 "Introduction to Version 3 of the Internet-standard Network 2095 Management Framework", RFC 2570, April 1999 2097 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2098 Architecture for Describing SNMP Management Frameworks", 2099 RFC 2571, April 1999 2101 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2102 "Message Processing and Dispatching for the Simple Network 2103 Management Protocol (SNMP)", RFC 2572, April 1999 2105 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", 2106 RFC 2573, April 1999 2108 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2109 (USM) for version 3 of the Simple Network Management 2110 Protocol (SNMPv3)", RFC 2574, April 1999 2112 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2113 Access Control Model (VACM) for the Simple Network 2114 Management Protocol (SNMP)", RFC 2575, April 1999 2116 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2117 Rose, M., and S. Waldbusser, "Structure of Management 2118 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2120 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2121 Rose, M., and S. Waldbusser, "Textual Conventions for 2122 SMIv2", STD 58, RFC 2579, April 1999 2124 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2125 Rose, M., and S. Waldbusser, "Conformance Statements for 2126 SMIv2", STD 58, RFC 2580, April 1999 2128 [RFC2851] Daniele, M., Haberman, B., Routhier, S. and J., 2129 Schoenwaelder "Textual Conventions for Internet Network 2130 Addresses", RFC 2851, June 2000 2132 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB" 2133 RFC 2863, June 2000. 2135 [GSMPv3] Doria, Hellstrand, Sundell, Worster, "General Switch 2136 Management Protocol V3", work in progress, June 2001 2138 [GSMPenc] Worster, Doria, Buerkle, "GSMP Packet Encapsulations for ATM, 2139 Ethernet and TCP", work in progress, November 2000 2141 8. Security Considerations 2143 Assuming that secure network management (such as SNMP v3) is 2144 implemented, the objects represented in this MIB do not pose a threat 2145 to the security of the network. 2147 There are a number of management objects defined in this MIB that 2148 have a MAX-ACCESS clause of read-write and/or read-create. Such 2149 objects may be considered sensitive or vulnerable in some network 2150 environments. The support for SET operations in a non-secure 2151 environment without proper protection can have a negative effect on 2152 network operations. 2154 There are a number of managed objects in this MIB that may contain 2155 sensitive information. These are contained in the gsmpControllerTable 2156 and gsmpSwitchTable. It is thus important to control even GET access 2157 to these objects and possibly to even encrypt the values of these 2158 object when sending them over the network via SNMP. Not all versions 2159 of SNMP provide features for such a secure environment. 2161 SNMPv1 by itself is not a secure environment. Even if the network 2162 itself is secure (for example by using IPSec), even then, there is no 2163 control as to who on the secure network is allowed to access and 2164 GET/SET (read/change/create/delete) the objects in this MIB. 2166 It is recommended that the implementers consider the security 2167 features as provided by the SNMPv3 framework. Specifically, the use 2168 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2169 based Access Control Model RFC 2575 [RFC2575] is recommended. 2171 It is then a customer/user responsibility to ensure that the SNMP 2172 entity giving access to an instance of this MIB, is properly 2173 configured to give access to the objects only to those principals 2174 (users) that have legitimate rights to indeed GET or SET 2175 (change/create/delete) them. 2177 9. Authors' Addresses 2179 Hans Sjostrand 2180 ipUnplugged 2181 P.O. Box 101 60 2182 S-121 28 Stockholm, Sweden 2183 Phone: +46 8 725 5930 2184 Email: hans@ipunplugged.com 2186 Joachim Buerkle 2187 Nortel Networks Germany GmbH & Co. KG 2188 Hahnstrasse 37-39 2189 D-60528 Frankfurt am Main, Germany 2190 Phone: +49 69 6697 3281 2191 Email: joachim.buerkle@nortelnetworks.com 2193 Balaji Srinivasan 2194 CPlane Inc. 2195 5150 El Camino Real 2196 Suite B-31 2197 Los Altos, CA 94022 2198 Phone +1 650 938 8066 ext 103 2199 Email: balaji@cplane.com 2201 10. Full Copyright Statement 2203 Copyright (C) The Internet Society (2001). All Rights Reserved. 2205 This document and translations of it may be copied and furnished to 2206 others, and derivative works that comment on or otherwise explain it 2207 or assist in its implementation may be prepared, copied, published 2208 and distributed, in whole or in part, without restriction of any 2209 kind, provided that the above copyright notice and this paragraph are 2210 included on all such copies and derivative works. However, this 2211 document itself may not be modified in any way, such as by removing 2212 the copyright notice or references to the Internet Society or other 2213 Internet organizations, except as needed for the purpose of 2214 developing Internet standards in which case the procedures for 2215 copyrights defined in the Internet Standards process must be 2216 followed, or as required to translate it into languages other than 2217 English. 2219 The limited permissions granted above are perpetual and will not be 2220 revoked by the Internet Society or its successors or assigns. 2222 This document and the information contained herein is provided on an 2223 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2224 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2225 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2226 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2227 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.