idnits 2.17.1 draft-ietf-gsmp-mib-06.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 (October 2001) is 8222 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: 'RFC2021' is defined on line 2101, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 2105, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 2118, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 2122, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 2161, but no explicit reference was found in the text == Unused Reference: 'InetAdr' is defined on line 2164, 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 2021 (Obsoleted by RFC 4502) ** 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'InetAdr' -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPv3' -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPenc' Summary: 18 errors (**), 0 flaws (~~), 9 warnings (==), 5 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 April 2002 Joachim Buerkle 4 Nortel Networks 5 Balaji Srinivasan 6 Cplane 7 October 2001 9 Definitions of Managed Objects for 10 the General Switch Management Protocol (GSMP) 12 < draft-ietf-gsmp-mib-06.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 (2001). 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............................................. 11 70 5. Revision History................................................. 43 71 5.1 Changes from < draft-ietf-gsmp-mib-00.txt >.................. 43 72 5.2 Changes from < draft-ietf-gsmp-mib-01.txt >.................. 43 73 5.3 Changes from < draft-ietf-gsmp-mib-02.txt >.................. 43 74 5.4 Changes from < draft-ietf-gsmp-mib-03.txt >.................. 44 75 5.5 Changes from < draft-ietf-gsmp-mib-04.txt >.................. 44 76 5.6 Changes from < draft-ietf-gsmp-mib-05.txt >.................. 44 78 6. Acknowledgments.................................................. 45 80 7. References....................................................... 45 82 8. Security Considerations.......................................... 47 84 9. Authors' Addresses............................................... 48 86 10. Full Copyright Statement........................................ 48 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols in the Internet community. 91 In particular, it describes managed objects for the General Switch 92 Management Protocol (GSMP). 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in RFC 2119 [RFC2119]. 98 2. The SNMP Management Framework 100 The SNMP Management Framework presently consists of five major 101 components: 103 * An overall architecture, described in RFC 2571 [RFC2571]. 105 * Mechanisms for describing and naming objects and events for the 106 purpose of management. The first version of this Structure of 107 Management Information (SMI) is called SMIv1 and described in STD 108 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 109 [RFC1215]. The second version, called SMIv2, is described in STD 110 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580[RFC2580]. 112 * Message protocols for transferring management information. The 113 first version of the SNMP message protocol is called SNMPv1 and 114 described in STD 15, RFC 1157 [RFC1157]. A second version of the 115 SNMP message protocol, which is not an Internet standards track 116 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 117 RFC 1906 [RFC1906]. The third version of the message protocol is 118 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 119 [RFC2572] and RFC 2574 [RFC2574]. 121 * Protocol operations for accessing management information. The first 122 set of protocol operations and associated PDU formats is described 123 in STD 15, RFC 1157 [RFC1157]. A second set of operations and 124 associated PDU formats is described in 1905 [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, GsmpVersion, 407 GsmpPartitionType and GsmpPartitionIdType are used as textual 408 conventions in this document. These textual conventions are used for 409 the convenience of humans reading the MIB. Objects defined using 410 these conventions are always encoded by means of the rules that 411 define their primitive type. However, the textual conventions have 412 special semantics associated with them. Hence, no changes to the SMI 413 or the SNMP are necessary to accommodate these textual conventions 414 which are adopted merely for the convenience of readers. 416 4. GSMP MIB Definitions 418 GSMP-MIB DEFINITIONS ::= BEGIN 420 IMPORTS 421 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 422 Unsigned32, Integer32, mib-2 423 FROM SNMPv2-SMI -- RFC2578 424 RowStatus, TruthValue, TimeStamp, 425 StorageType, TEXTUAL-CONVENTION 426 FROM SNMPv2-TC -- RFC2579 427 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 428 FROM SNMPv2-CONF -- RFC2580 429 ZeroBasedCounter32 430 FROM RMON2-MIB -- RFC2021 431 InterfaceIndex 432 FROM IF-MIB -- RFC2863 433 AtmVcIdentifier, AtmVpIdentifier 434 FROM ATM-TC-MIB -- RFC2514 435 InetAddressType, InetAddress, InetPortNumber 436 FROM INET-ADDRESS-MIB ; -- InetAdr 438 gsmpMIB MODULE-IDENTITY 439 LAST-UPDATED "200110241200Z" -- Oct 24th 2001, 14.00 MET DST 440 ORGANIZATION "General Switch Management Protocol (gsmp) 441 Working Group, IETF" 442 CONTACT-INFO 443 "WG Charter: 444 http://www.ietf.org/html.charters/gsmp-charter.html 446 WG-email: gsmp@revnetworks.com 447 Subscribe: gsmp-request@revnetworks.com 448 Email Archive: 449 ftp://www.revnetworks.com/pub/mailing-lists/gsmp-archive 451 WG Chair: Avri Doria 452 Email: avri@apocalypse.org 454 WG Chair: Kenneth Sundell 455 Email: ksundell@nortelnetworks.com 457 Editor: Hans Sjostrand 458 Email: hans@ipunplugged.com 460 Editor: Joachim Buerkle 461 Email: joachim.buerkle@nortelnetworks.com 462 Editor: Balaji Srinivasan 463 Email: balaji@cplane.com" 464 DESCRIPTION 465 "This MIB contains managed object definitions for the 466 General Switch Management Protocol, GSMP, version 3" 468 REVISION "200110241200Z" 469 DESCRIPTION "Initial Version, published as RFC xxxx" 470 -- RFC-Editor assigns xxxx 472 ::= { mib-2 XXX } -- IANA assignes XXX 474 gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 0 } 475 gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } 476 gsmpNotificationsObjects OBJECT IDENTIFIER ::= { gsmpMIB 2 } 477 gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 } 479 --************************************************************** 480 -- GSMP Textual Conventions 481 --************************************************************** 483 GsmpNameType ::= TEXTUAL-CONVENTION 484 STATUS current 485 DESCRIPTION 486 "The Name is a 48-bit quantity. 487 A 48-bit IEEE 802 MAC address, if 488 available, may be used." 489 SYNTAX OCTET STRING (SIZE(6)) 491 GsmpPartitionType ::= TEXTUAL-CONVENTION 492 STATUS current 493 DESCRIPTION 494 "Defining if partitions are used and how the partition id 495 is negotiated. " 496 SYNTAX INTEGER { 497 noPartition(1), 498 fixedPartitionRequest(2), 499 fixedPartitionAssigned(3) 500 } 502 GsmpPartitionIdType ::= TEXTUAL-CONVENTION 503 STATUS current 504 DESCRIPTION 505 "A 8-bit quantity. The format of the Partition ID is not 506 defined in GSMP. If desired, the Partition ID can be 507 divided into multiple sub-identifiers within a single 508 partition. For example: the Partition ID could be 509 subdivided into a 6-bit partition number and a 2-bit 510 sub-identifier which would allow a switch to support 64 511 partitions with 4 available IDs per partition." 512 SYNTAX OCTET STRING (SIZE(1)) 514 GsmpVersion ::= TEXTUAL-CONVENTION 515 STATUS current 516 DESCRIPTION 517 "The version numbers defined for the GSMP protocol. 518 The version numbers used are defined in the 519 specifications of the respective protocool, 520 1 - GSMPv1.1 [RFC1987] 521 2 - GSMPv2.0 [RFC2397] 522 3 - GSMPv3 [GSMPv3] 523 Other numbes may be defined for other versions 524 of the GSMP protocool." 525 SYNTAX Unsigned32 527 GsmpLabelType ::= TEXTUAL-CONVENTION 528 STATUS current 529 DESCRIPTION 530 "The label is structured as a TLV, a tuple, consisting of 531 a Type, a Length, and a Value. The structure is defined 532 in [GSMPv3]. The label TLV is encoded as a 2 octet type 533 field, followed by a 2 octet Length field, followed by a 534 variable length Value field. 535 Additionally, a label field can be composed of many stacked 536 labels that together constitute the label." 537 SYNTAX OCTET STRING 539 --************************************************************** 540 -- GSMP Entity Objects 541 --************************************************************** 543 -- 544 -- Switch Controller Entity table 545 -- 547 gsmpControllerTable OBJECT-TYPE 548 SYNTAX SEQUENCE OF GsmpControllerEntry 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "This table represents the Switch Controller 553 Entities. An entry in this table needs to be configured 554 (created) before a GSMP session might be started." 555 ::= { gsmpObjects 1 } 557 gsmpControllerEntry OBJECT-TYPE 558 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, 583 gsmpControllerSessionState INTEGER, 584 gsmpControllerStorageType StorageType, 585 gsmpControllerRowStatus RowStatus 586 } 588 gsmpControllerEntityId OBJECT-TYPE 589 SYNTAX GsmpNameType 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "The Switch Controller Entity Id is unique 594 within the operational context of the device." 595 ::= { gsmpControllerEntry 1 } 597 gsmpControllerMaxVersion OBJECT-TYPE 598 SYNTAX GsmpVersion 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "The max version number of the GSMP protocol being used 603 in this session. The version is negotiated by the 604 adjacency protocol." 605 DEFVAL { 3 } 606 ::= { gsmpControllerEntry 2 } 608 gsmpControllerTimer OBJECT-TYPE 609 SYNTAX Unsigned32(1..255) 610 UNITS "100ms" 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "The timer specifies the nominal time between 615 periodic adjacency protocol messages. It is a constant 616 for the duration of a GSMP session. The timer is 617 specified in units of 100ms." 618 DEFVAL { 10 } 619 ::= { gsmpControllerEntry 3 } 621 gsmpControllerPort OBJECT-TYPE 622 SYNTAX Unsigned32 623 MAX-ACCESS read-create 624 STATUS current 625 DESCRIPTION 626 "The local port number for the Switch Controller 627 Entity. The port number is is a 32-bit number that 628 is typically structured into opaque sub-fields that 629 have meaning to the physical structure of the switch 630 (e.g. slot, port)." 631 ::= { gsmpControllerEntry 4 } 633 gsmpControllerInstance OBJECT-TYPE 634 SYNTAX Unsigned32(1..16777215) 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "The instance number for the Switch Controller 639 Entity. The Instance number is a 24-bit number 640 that should be guaranteed to be unique within 641 the recent past and to change when the link 642 or node comes back up after going down. Zero is 643 not a valid instance number. " 644 ::= { gsmpControllerEntry 5 } 646 gsmpControllerPartitionType OBJECT-TYPE 647 SYNTAX GsmpPartitionType 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "A controller can request the specific partition identifier 652 to the session by setting the Partition Type to 653 fixedPartitionRequest(2). A controller can let the switch 654 decide whether it wants to assign a fixed partition ID or 655 not, by setting the Partition Type to noPartition(1)." 656 ::= { gsmpControllerEntry 6 } 658 gsmpControllerPartitionId OBJECT-TYPE 659 SYNTAX GsmpPartitionIdType 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "The Id for the specific switch partition that this 664 Switch Controller is concerned with. 665 If partitions are not used or if the controller lets the 666 switch assigns Partition ID, i.e Partition Type = 667 noPartition(1), then this object is undefined." 668 ::= { gsmpControllerEntry 7 } 670 gsmpControllerDoResync OBJECT-TYPE 671 SYNTAX TruthValue 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "This object specifies whether the controller should 676 resynchronise or reset in case of loss of synchronisation. 677 If this object is set to true then the Controller should 678 resync with PFLAG=2 (recovered adjacency)." 679 DEFVAL { true } 680 ::= { gsmpControllerEntry 8 } 682 gsmpControllerNotificationMap OBJECT-TYPE 683 SYNTAX BITS { 684 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 { 710 null(1), 711 synsent(2), 712 synrcvd(3), 713 estab(4) 714 } 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "The state for the existing or potential session that 719 this entity is concerned with. 720 The NULL state is returned if the proper encapsulation 721 data is not yet configured, if the row is not in active 722 status or if the session is in NULL state as defined in 723 the GSMP specification." 724 ::= { gsmpControllerEntry 10} 726 gsmpControllerStorageType OBJECT-TYPE 727 SYNTAX StorageType 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "The storage type for this controller entity. 732 Conceptual rows having the value 'permanent' need not allow 733 write-access to any columnar objects in the row." 734 DEFVAL { nonVolatile } 735 ::= { gsmpControllerEntry 11 } 737 gsmpControllerRowStatus OBJECT-TYPE 738 SYNTAX RowStatus 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "An object that allows entries in this table to 743 be created and deleted using the 744 RowStatus convention. 745 While the row is in active state it's not 746 possible to modify the value of any object 747 for that row exept the gsmpControllerNotificationMap 748 and the gsmpControllerRowStatus objects." 749 ::= { gsmpControllerEntry 12 } 751 -- 752 -- Switch Entity table 753 -- 754 gsmpSwitchTable OBJECT-TYPE 755 SYNTAX SEQUENCE OF GsmpSwitchEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "This table represents the Switch 760 Entities. An entry in this table needs to be configured 761 (created) before a GSMP session might be started." 762 ::= { gsmpObjects 2 } 764 gsmpSwitchEntry OBJECT-TYPE 765 SYNTAX GsmpSwitchEntry 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "An entry in the table showing 770 the data for a specific Switch 771 Entity. If partitions are used, one entity 772 corresponds to one specific switch partition. 773 Depending of the encapsulation used, 774 a corresponding row in the gsmpAtmEncapTable or the 775 gsmpTcpIpEncapTable may have been created." 776 INDEX { gsmpSwitchEntityId } 777 ::= { gsmpSwitchTable 1 } 779 GsmpSwitchEntry ::= SEQUENCE { 780 gsmpSwitchEntityId GsmpNameType, 781 gsmpSwitchMaxVersion GsmpVersion, 782 gsmpSwitchTimer Unsigned32, 783 gsmpSwitchName GsmpNameType, 784 gsmpSwitchPort Unsigned32, 785 gsmpSwitchInstance Unsigned32, 786 gsmpSwitchPartitionType GsmpPartitionType, 787 gsmpSwitchPartitionId GsmpPartitionIdType, 788 gsmpSwitchNotificationMap BITS, 789 gsmpSwitchSwitchType OCTET STRING, 790 gsmpSwitchWindowSize Unsigned32, 791 gsmpSwitchSessionState INTEGER, 792 gsmpSwitchStorageType StorageType, 793 gsmpSwitchRowStatus RowStatus 794 } 796 gsmpSwitchEntityId OBJECT-TYPE 797 SYNTAX GsmpNameType 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "The Switch Entity Id is unique 802 within the operational context of the device. " 804 ::= { gsmpSwitchEntry 1 } 806 gsmpSwitchMaxVersion OBJECT-TYPE 807 SYNTAX GsmpVersion 808 MAX-ACCESS read-create 809 STATUS current 810 DESCRIPTION 811 "The max version number of the GSMP protocol being 812 supported by this Switch. The version is negotiated by 813 the adjacency protocol." 814 DEFVAL { 3 } 815 ::= { gsmpSwitchEntry 2 } 817 gsmpSwitchTimer OBJECT-TYPE 818 SYNTAX Unsigned32(1..255) 819 UNITS "100ms" 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "The timer specifies the nominal time between 824 periodic adjacency protocol messages. It is a constant 825 for the duration of a GSMP session. The timer is 826 specified in units of 100ms." 827 DEFVAL { 10 } 828 ::= { gsmpSwitchEntry 3 } 830 gsmpSwitchName OBJECT-TYPE 831 SYNTAX GsmpNameType 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "The name of the Switch. The first three octets must be an 836 Organisationally Unique Identifier (OUI) that identifies 837 the manufacturer of the Switch. This is by default set to 838 the same value as the gsmpSwitchId object if not 839 separately specified. " 840 ::= {gsmpSwitchEntry 4 } 842 gsmpSwitchPort OBJECT-TYPE 843 SYNTAX Unsigned32 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The local port number for this Switch Entity. 848 The port number is is a 32-bit number that 849 is typically structured into opaque sub-fields that 850 have meaning to the physical structure of the switch 851 (e.g. slot, port)" 852 ::= { gsmpSwitchEntry 5 } 854 gsmpSwitchInstance OBJECT-TYPE 855 SYNTAX Unsigned32(1..16777215) 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The instance number for the Switch Entity. 860 The Instance number is a 24-bit number 861 that should be guaranteed to be unique within 862 the recent past and to change when the link 863 or node comes back up after going down. Zero is 864 not a valid instance number." 865 ::= { gsmpSwitchEntry 6 } 867 gsmpSwitchPartitionType OBJECT-TYPE 868 SYNTAX GsmpPartitionType 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "A switch can assign the specific partition identifier to 873 the session by setting the Partition Type to 874 fixedPartitionAssigned(3). A switch can specify 875 that no partitions are handled in the session by setting 876 the Partition Type to noPartition(1)." 877 ::= { gsmpSwitchEntry 7 } 879 gsmpSwitchPartitionId OBJECT-TYPE 880 SYNTAX GsmpPartitionIdType 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The Id for this specific switch partition that the switch 885 entity represents. If partitions are not used, i.e. 886 Partition Type = noPartition(1), then this object is 887 undefined." 888 ::= { gsmpSwitchEntry 8 } 890 gsmpSwitchNotificationMap OBJECT-TYPE 891 SYNTAX BITS { 892 sessionDown(0), 893 sessionUp(1), 894 sendFailureIndication(2), 895 receivedFailureIndication(3), 896 portUpEvent(4), 897 portDownEvent(5), 898 invalidLabelEvent(6), 899 newPortEvent(7), 900 deadPortEvent(8), 901 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 { 944 null(1), 945 synsent(2), 946 synrcvd(3), 947 estab(4) 948 } 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "The state for the existing or potential session that 953 this entity is concerned with. 954 The NULL state is returned if the proper encapsulation 955 data is not yet configured, if the row is not in active 956 status or if the session is in NULL state as defined in 957 the GSMP specification." 958 ::= { gsmpSwitchEntry 12} 960 gsmpSwitchStorageType OBJECT-TYPE 961 SYNTAX StorageType 962 MAX-ACCESS read-create 963 STATUS current 964 DESCRIPTION 965 "The storage type for this switch entity. 966 Conceptual rows having the value 'permanent' need not allow 967 write-access to any columnar objects in the row." 968 DEFVAL { nonVolatile } 969 ::= { gsmpSwitchEntry 13 } 971 gsmpSwitchRowStatus OBJECT-TYPE 972 SYNTAX RowStatus 973 MAX-ACCESS read-create 974 STATUS current 975 DESCRIPTION 976 "An object that allows entries in this table to 977 be created and deleted using the 978 RowStatus convention. 979 While the row is in active state it's not 980 possible to modify the value of any object 981 for that row exept the gsmpSwitchNotificationMap 982 and the gsmpSwitchRowStatus objects." 983 ::= { gsmpSwitchEntry 14 } 985 --************************************************************** 986 -- GSMP Encapsulation Objects 987 --************************************************************** 989 -- 990 -- GSMP ATM Encapsulation Table 991 -- 993 gsmpAtmEncapTable OBJECT-TYPE 994 SYNTAX SEQUENCE OF GsmpAtmEncapEntry 995 MAX-ACCESS not-accessible 996 STATUS current 997 DESCRIPTION 998 "This table contains the atm encapsulation data 999 for the Controller or Switch that uses atm aal5 as 1000 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, 1021 gsmpAtmEncapRowStatus RowStatus 1022 } 1024 gsmpAtmEncapEntityId OBJECT-TYPE 1025 SYNTAX GsmpNameType 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "The Controller Id or Switch Id that is unique 1030 within the operational context of the device. " 1031 ::= { gsmpAtmEncapEntry 1 } 1033 gsmpAtmEncapIfIndex OBJECT-TYPE 1034 SYNTAX InterfaceIndex 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "The interface index for the virtual channel over which 1039 the GSMP session is established, i.e., the GSMP control 1040 channel for LLC/SNAP encapsulated GSMP messages on an 1041 ATM data link layer." 1042 ::= { gsmpAtmEncapEntry 2 } 1044 gsmpAtmEncapVpi OBJECT-TYPE 1045 SYNTAX AtmVpIdentifier 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 " The VPI value for the virtual channel over which the 1050 GSMP session is established, i.e., the GSMP control 1051 channel for LLC/SNAP encapsulated GSMP messages on an 1052 ATM data link layer." 1053 DEFVAL { 0 } 1054 ::= { gsmpAtmEncapEntry 3 } 1056 gsmpAtmEncapVci OBJECT-TYPE 1057 SYNTAX AtmVcIdentifier 1058 MAX-ACCESS read-create 1059 STATUS current 1060 DESCRIPTION 1061 " The VCI value for the virtual channel over which the 1062 GSMP session is established, i.e., the GSMP control 1063 channel for LLC/SNAP encapsulated GSMP messages on an 1064 ATM data link layer." 1065 DEFVAL { 15 } 1066 ::= { gsmpAtmEncapEntry 4 } 1068 gsmpAtmEncapStorageType OBJECT-TYPE 1069 SYNTAX StorageType 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "The storage type for this entry. It should have the same 1074 valur as the StorageType in the refering Switch Controller 1075 entity or Switch entity." 1076 DEFVAL { nonVolatile } 1077 ::= { gsmpAtmEncapEntry 5 } 1079 gsmpAtmEncapRowStatus OBJECT-TYPE 1080 SYNTAX RowStatus 1081 MAX-ACCESS read-create 1082 STATUS current 1083 DESCRIPTION 1084 "An object that allows entries in this table to 1085 be created and deleted using the 1086 RowStatus convention. 1087 While the row is in active state it's not 1088 possible to modify the value of any object 1089 for that row exept the gsmpAtmEncapRowStatus object." 1090 ::= { gsmpAtmEncapEntry 6 } 1092 -- 1093 -- GSMP TCP/IP Encapsulation Table 1094 -- 1096 gsmpTcpIpEncapTable OBJECT-TYPE 1097 SYNTAX SEQUENCE OF GsmpTcpIpEncapEntry 1098 MAX-ACCESS not-accessible 1099 STATUS current 1101 DESCRIPTION 1102 "This table contains the encapsulation data 1103 for the Controller or Switch that uses TCP/IP as 1104 encapsulation." 1105 ::= { gsmpObjects 4 } 1107 gsmpTcpIpEncapEntry OBJECT-TYPE 1108 SYNTAX GsmpTcpIpEncapEntry 1109 MAX-ACCESS not-accessible 1110 STATUS current 1111 DESCRIPTION 1112 "An entry in the table showing 1113 the encapsulation data for a specific 1114 Switch Controller entity or Switch entity." 1115 INDEX { gsmpTcpIpEncapEntityId } 1116 ::= { gsmpTcpIpEncapTable 1 } 1118 GsmpTcpIpEncapEntry ::= SEQUENCE { 1119 gsmpTcpIpEncapEntityId GsmpNameType, 1120 gsmpTcpIpEncapAddressType InetAddressType, 1121 gsmpTcpIpEncapAddress InetAddress, 1122 gsmpTcpIpEncapPortNumber InetPortNumber, 1123 gsmpTcpIpEncapStorageType StorageType, 1124 gsmpTcpIpEncapRowStatus RowStatus 1125 } 1127 gsmpTcpIpEncapEntityId OBJECT-TYPE 1128 SYNTAX GsmpNameType 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "The Controller or Switch Id is unique 1133 within the operational context of the device. " 1134 ::= { gsmpTcpIpEncapEntry 1 } 1136 gsmpTcpIpEncapAddressType OBJECT-TYPE 1137 SYNTAX InetAddressType 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "The type of address in gsmpTcpIpEncapAddress." 1142 ::= { gsmpTcpIpEncapEntry 2 } 1144 gsmpTcpIpEncapAddress OBJECT-TYPE 1145 SYNTAX InetAddress 1146 MAX-ACCESS read-create 1147 STATUS current 1148 DESCRIPTION 1149 "The IPv4 or IPv6 address used for 1150 the GSMP session peer." 1151 ::= { gsmpTcpIpEncapEntry 3 } 1153 gsmpTcpIpEncapPortNumber OBJECT-TYPE 1154 SYNTAX InetPortNumber 1155 MAX-ACCESS read-create 1156 STATUS current 1157 DESCRIPTION 1158 "The TCP port number used for the TCP session 1159 establishment to the GSMP peer." 1160 DEFVAL { 6068 } 1161 ::= { gsmpTcpIpEncapEntry 4 } 1163 gsmpTcpIpEncapStorageType OBJECT-TYPE 1164 SYNTAX StorageType 1165 MAX-ACCESS read-create 1166 STATUS current 1167 DESCRIPTION 1168 "The storage type for this entry. It should have the same 1169 value as the StorageType in the refering Switch Controller 1170 entity or Switch entity." 1171 DEFVAL { nonVolatile } 1172 ::= { gsmpTcpIpEncapEntry 5 } 1174 gsmpTcpIpEncapRowStatus OBJECT-TYPE 1175 SYNTAX RowStatus 1176 MAX-ACCESS read-create 1177 STATUS current 1178 DESCRIPTION 1179 "An object that allows entries in this table to 1180 be created and deleted using the 1181 RowStatus convention. 1182 While the row is in active state it's not 1183 possible to modify the value of any object 1184 for that row exept the gsmpTcpIpEncapRowStatus object." 1185 ::= { gsmpTcpIpEncapEntry 6 } 1187 --************************************************************** 1188 -- GSMP Session Objects 1189 --************************************************************** 1191 -- 1192 -- GSMP Session table 1193 -- 1195 gsmpSessionTable OBJECT-TYPE 1196 SYNTAX SEQUENCE OF GsmpSessionEntry 1197 MAX-ACCESS not-accessible 1198 STATUS current 1200 DESCRIPTION 1201 "This table represents the sessions between 1202 Controller and Switch pairs. " 1203 ::= { gsmpObjects 5 } 1205 gsmpSessionEntry OBJECT-TYPE 1206 SYNTAX GsmpSessionEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "An entry in the table showing 1211 the session data for a specific Controller and 1212 Switch pair. Also, statistics for this specific 1213 session is shown." 1214 INDEX { gsmpSessionThisSideId, gsmpSessionFarSideId } 1215 ::= { gsmpSessionTable 1 } 1217 GsmpSessionEntry ::= SEQUENCE { 1218 gsmpSessionThisSideId GsmpNameType, 1219 gsmpSessionFarSideId GsmpNameType, 1220 gsmpSessionVersion GsmpVersion, 1221 gsmpSessionTimer Integer32, 1222 gsmpSessionPartitionId GsmpPartitionIdType, 1223 gsmpSessionAdjacencyCount Unsigned32, 1224 gsmpSessionFarSideName GsmpNameType, 1225 gsmpSessionFarSidePort Unsigned32, 1226 gsmpSessionFarSideInstance Unsigned32, 1227 gsmpSessionLastFailureCode Unsigned32, 1228 gsmpSessionDiscontinuityTime TimeStamp, 1229 gsmpSessionStartUptime TimeStamp, 1230 gsmpSessionStatSentMessages ZeroBasedCounter32, 1231 gsmpSessionStatFailureInds ZeroBasedCounter32, 1232 gsmpSessionStatReceivedMessages ZeroBasedCounter32, 1233 gsmpSessionStatReceivedFailures ZeroBasedCounter32, 1234 gsmpSessionStatPortUpEvents ZeroBasedCounter32, 1235 gsmpSessionStatPortDownEvents ZeroBasedCounter32, 1236 gsmpSessionStatInvLabelEvents ZeroBasedCounter32, 1237 gsmpSessionStatNewPortEvents ZeroBasedCounter32, 1238 gsmpSessionStatDeadPortEvents ZeroBasedCounter32, 1239 gsmpSessionStatAdjUpdateEvents ZeroBasedCounter32 1240 } 1242 gsmpSessionThisSideId OBJECT-TYPE 1243 SYNTAX GsmpNameType 1244 MAX-ACCESS not-accessible 1245 STATUS current 1246 DESCRIPTION 1247 "This side ID uniquely identifies the entity that this 1248 session relates to within the operational 1250 context of the device. " 1251 ::= { gsmpSessionEntry 1 } 1253 gsmpSessionFarSideId OBJECT-TYPE 1254 SYNTAX GsmpNameType 1255 MAX-ACCESS not-accessible 1256 STATUS current 1257 DESCRIPTION 1258 "The Far side ID uniquely identifies the entity that this 1259 session is established against. " 1260 ::= { gsmpSessionEntry 2 } 1262 gsmpSessionVersion OBJECT-TYPE 1263 SYNTAX GsmpVersion 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The version number of the GSMP protocol being used in 1268 this session. The version is the result of the 1269 negotiation by the adjacency protocol." 1270 ::= { gsmpSessionEntry 3 } 1272 gsmpSessionTimer OBJECT-TYPE 1273 SYNTAX Integer32 1274 UNITS "100ms" 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "The timer specifies the time remaining until the 1279 adjacency timer expires. The object could take negative 1280 values since if no valid GSMP messages are 1281 received in any period of time in excess of three times 1282 the value of the Timer negotiated by the adjacency 1283 protocol loss of synchronisation may be declared. The 1284 timer is specified in units of 100ms." 1285 ::= { gsmpSessionEntry 4 } 1287 gsmpSessionPartitionId OBJECT-TYPE 1288 SYNTAX GsmpPartitionIdType 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "The Partition Id for the specific switch partition that 1293 this session is concerned with." 1294 ::= { gsmpSessionEntry 5 } 1296 gsmpSessionAdjacencyCount OBJECT-TYPE 1297 SYNTAX Unsigned32(1..255) 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "This object specifies the current number of adjacencies 1302 that are established with controllers and the switch 1303 partition that is used for this session. The value 1304 includes this session." 1305 ::= { gsmpSessionEntry 6 } 1307 gsmpSessionFarSideName OBJECT-TYPE 1308 SYNTAX GsmpNameType 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "The name of the far side as advertised in the adjacency 1313 message." 1314 ::= {gsmpSessionEntry 7} 1316 gsmpSessionFarSidePort OBJECT-TYPE 1317 SYNTAX Unsigned32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "The local port number of the link across which the 1322 message is being sent." 1323 ::= { gsmpSessionEntry 8 } 1325 gsmpSessionFarSideInstance OBJECT-TYPE 1326 SYNTAX Unsigned32(1..16777215) 1327 MAX-ACCESS read-only 1328 STATUS current 1329 DESCRIPTION 1330 "The instance number used for the link during this 1331 session. The Instance number is a 24-bit number 1332 that should be guaranteed to be unique within 1333 the recent past and to change when the link 1334 or node comes back up after going down. Zero is not 1335 a valid instance number." 1336 ::= { gsmpSessionEntry 9 } 1338 gsmpSessionLastFailureCode OBJECT-TYPE 1339 SYNTAX Unsigned32(0..255) 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "This is the last failure code that was received over 1344 this session. If no failure code have been received, the 1345 value is zero." 1346 ::= { gsmpSessionEntry 10 } 1348 gsmpSessionDiscontinuityTime OBJECT-TYPE 1349 SYNTAX TimeStamp 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The value of sysUpTime on the most recent occasion at 1354 which one or more of this session's counters 1355 suffered a discontinuity. If no such discontinuities have 1356 occurred since then, this object contains the same 1357 timestamp as gsmpSessionStartUptime ." 1358 ::= { gsmpSessionEntry 11 } 1360 gsmpSessionStartUptime OBJECT-TYPE 1361 SYNTAX TimeStamp 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 " The value of sysUpTime when the session came to 1366 established state." 1367 ::= { gsmpSessionEntry 12 } 1369 gsmpSessionStatSentMessages OBJECT-TYPE 1370 SYNTAX ZeroBasedCounter32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The number of messages that have been sent in this 1375 session. When the counter suffers any discontinuity, then 1376 the gsmpSessionDiscontinuityTime object indicates when it 1377 happened." 1378 ::= { gsmpSessionEntry 13 } 1380 gsmpSessionStatFailureInds OBJECT-TYPE 1381 SYNTAX ZeroBasedCounter32 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "The number of messages that have been sent with a 1386 failure indication in this session. 1387 When the counter suffers any discontinuity, then 1388 the gsmpSessionDiscontinuityTime object indicates when it 1389 happened." 1390 ::= { gsmpSessionEntry 14 } 1392 gsmpSessionStatReceivedMessages OBJECT-TYPE 1393 SYNTAX ZeroBasedCounter32 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "The number of messages that have been received in 1398 this session. 1399 When the counter suffers any discontinuity, then 1400 the gsmpSessionDiscontinuityTime object indicates when it 1401 happened." 1402 ::= { gsmpSessionEntry 15 } 1404 gsmpSessionStatReceivedFailures OBJECT-TYPE 1405 SYNTAX ZeroBasedCounter32 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 When the counter suffers any discontinuity, then 1412 the gsmpSessionDiscontinuityTime object indicates when it 1413 happened." 1414 ::= { gsmpSessionEntry 16 } 1416 gsmpSessionStatPortUpEvents OBJECT-TYPE 1417 SYNTAX ZeroBasedCounter32 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The number of Port Up events that have been sent or 1422 received on this session. 1423 When the counter suffers any discontinuity, then 1424 the gsmpSessionDiscontinuityTime object indicates when it 1425 happened." 1426 ::= { gsmpSessionEntry 17 } 1428 gsmpSessionStatPortDownEvents OBJECT-TYPE 1429 SYNTAX ZeroBasedCounter32 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "The number of Port Down events that have been sent or 1434 received on this session. 1435 When the counter suffers any discontinuity, then 1436 the gsmpSessionDiscontinuityTime object indicates when it 1437 happened." 1438 ::= { gsmpSessionEntry 18 } 1440 gsmpSessionStatInvLabelEvents OBJECT-TYPE 1441 SYNTAX ZeroBasedCounter32 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The number of Invalid label events that have been sent 1446 or received on this session. 1447 When the counter suffers any discontinuity, then 1448 the gsmpSessionDiscontinuityTime object indicates when it 1449 happened." 1450 ::= { gsmpSessionEntry 19 } 1452 gsmpSessionStatNewPortEvents OBJECT-TYPE 1453 SYNTAX ZeroBasedCounter32 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "The number of New Port events that have been sent or 1458 received on this session. 1459 When the counter suffers any discontinuity, then 1460 the gsmpSessionDiscontinuityTime object indicates when it 1461 happened." 1462 ::= { gsmpSessionEntry 20 } 1464 gsmpSessionStatDeadPortEvents OBJECT-TYPE 1465 SYNTAX ZeroBasedCounter32 1466 MAX-ACCESS read-only 1467 STATUS current 1468 DESCRIPTION 1469 "The number of Dead Port events that have been sent or 1470 received on this session. 1471 When the counter suffers any discontinuity, then 1472 the gsmpSessionDiscontinuityTime object indicates when it 1473 happened." 1474 ::= { gsmpSessionEntry 21 } 1476 gsmpSessionStatAdjUpdateEvents OBJECT-TYPE 1477 SYNTAX ZeroBasedCounter32 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "The number of Adjacency Update events that have been sent 1482 or received on this session. 1483 When the counter suffers any discontinuity, then 1484 the gsmpSessionDiscontinuityTime object indicates when it 1485 happened." 1486 ::= { gsmpSessionEntry 22 } 1488 -- ************************************************************** 1489 -- GSMP Notifications 1490 -- ************************************************************** 1492 -- 1493 -- Notification objects 1494 -- 1496 gsmpEventPort OBJECT-TYPE 1497 SYNTAX Unsigned32 1498 MAX-ACCESS accessible-for-notify 1499 STATUS current 1500 DESCRIPTION 1501 "This object specifies the Port Number that is 1502 carried in this event." 1503 ::= { gsmpNotificationsObjects 1 } 1505 gsmpEventPortSessionNumber OBJECT-TYPE 1506 SYNTAX Unsigned32 1507 MAX-ACCESS accessible-for-notify 1508 STATUS current 1509 DESCRIPTION 1510 "This object specifies the Port Session Number that is 1511 carried in this event." 1512 ::= { gsmpNotificationsObjects 2 } 1514 gsmpEventSequenceNumber OBJECT-TYPE 1515 SYNTAX Unsigned32 1516 MAX-ACCESS accessible-for-notify 1517 STATUS current 1518 DESCRIPTION 1519 "This object specifies the Event Sequence Number that is 1520 carried in this event." 1521 ::= { gsmpNotificationsObjects 3 } 1523 gsmpEventLabel OBJECT-TYPE 1524 SYNTAX GsmpLabelType 1525 MAX-ACCESS accessible-for-notify 1526 STATUS current 1527 DESCRIPTION 1528 "This object specifies the Label that is 1529 carried in this event." 1530 ::= { gsmpNotificationsObjects 4 } 1532 -- 1533 -- Notifications 1534 -- 1536 gsmpSessionDown NOTIFICATION-TYPE 1537 OBJECTS { 1538 gsmpSessionStartUptime, 1539 gsmpSessionStatSentMessages, 1540 gsmpSessionStatFailureInds, 1541 gsmpSessionStatReceivedMessages, 1542 gsmpSessionStatReceivedFailures, 1543 gsmpSessionStatPortUpEvents, 1544 gsmpSessionStatPortDownEvents, 1545 gsmpSessionStatInvLabelEvents, 1546 gsmpSessionStatNewPortEvents, 1547 gsmpSessionStatDeadPortEvents, 1548 gsmpSessionStatAdjUpdateEvents 1549 } 1550 STATUS current 1551 DESCRIPTION 1552 "When it has been enabled, this notification is 1553 generated whenever a session is taken down, regardless 1554 of whether the session went down normally or not. 1555 Its purpose is to allow a management application 1556 (primarily an accounting application) that is 1557 monitoring the session statistics to receive the final 1558 values of these counters, so that the application can 1559 properly account for the amounts the counters were 1560 incremented since the last time the application polled 1561 them. The gsmpSessionStartUptime object provides the 1562 total amount of time that the session was active. 1564 This notification is not a substitute for polling the 1565 session statistic counts. In particular, the count 1566 values reported in this notification cannot be assumed 1567 to be the complete totals for the life of the session, 1568 since they may have wrapped while the 1569 session was up. 1571 The session to which this notification 1572 applies is identified by the gsmpSessionThisSideId and 1573 gsmpSessionFarSideId which could be inferred from the 1574 Object Identifiers of the objects contained in the 1575 notification. 1576 An instance of this notification will contain exactly 1577 one instance of each of its objects, and these objects 1578 will all belong to the same conceptual row of the 1579 gsmpSessionTable." 1580 ::= { gsmpNotifications 1 } 1582 gsmpSessionUp NOTIFICATION-TYPE 1583 OBJECTS { 1584 gsmpSessionFarSideInstance 1585 } 1586 STATUS current 1587 DESCRIPTION 1588 "When it has been enabled, this notification is 1589 generated when new session is established. 1591 The new session is identified by the gsmpSessionThisSideId 1592 and gsmpSessionFarSideId which could be inferred from the 1593 Object Identifier of the gsmpSessionFarSideInstance object 1594 contained in the notification." 1595 ::= { gsmpNotifications 2 } 1597 gsmpSentFailureInd NOTIFICATION-TYPE 1598 OBJECTS { 1599 gsmpSessionLastFailureCode, 1600 gsmpSessionStatFailureInds 1601 } 1602 STATUS current 1603 DESCRIPTION 1604 "When it has been enabled, this notification is 1605 generated when a message with a failure indication was 1606 sent. 1608 The notification indicates a change in the value of 1609 gsmpSessionStatFailureInds. The 1610 gsmpSessionLastFailureCode contains the failure 1611 reason. 1613 The session to which this notification 1614 applies is identified by the gsmpSessionThisSideId and 1615 gsmpSessionFarSideId which could be inferred from the 1616 Object Identifiers of the objects contained in the 1617 notification." 1618 ::= { gsmpNotifications 3 } 1620 gsmpReceivedFailureInd NOTIFICATION-TYPE 1621 OBJECTS { 1622 gsmpSessionLastFailureCode, 1623 gsmpSessionStatReceivedFailures 1624 } 1625 STATUS current 1626 DESCRIPTION 1627 "When it has been enabled, this notification is 1628 generate when a message with a failure indication 1629 is received. 1631 The notification indicates a change in the value of 1632 gsmpSessionStatReceivedFailures. The 1633 gsmpSessionLastFailureCode contains the failure 1634 reason. 1636 The session to which this notification 1637 applies is identified by the gsmpSessionThisSideId and 1638 gsmpSessionFarSideId which could be inferred from the 1639 Object Identifiers of the objects contained in the 1640 notification." 1641 ::= { gsmpNotifications 4 } 1643 gsmpPortUpEvent NOTIFICATION-TYPE 1644 OBJECTS { 1645 gsmpSessionStatPortUpEvents, 1646 gsmpEventPort, 1647 gsmpEventPortSessionNumber, 1648 gsmpEventSequenceNumber 1649 } 1650 STATUS current 1651 DESCRIPTION 1652 "When it has been enabled, this notification is 1653 generated when a Port Up Event occurs. 1655 The notification indicates a change in the value of 1656 gsmpSessionStatPortUpEvents. 1658 The session to which this notification 1659 applies is identified by the gsmpSessionThisSideId and 1660 gsmpSessionFarSideId which could be inferred from the 1661 Object Identifier of the gsmpSessionStatPortUpEvents 1662 object contained in the notification." 1663 ::= { gsmpNotifications 5 } 1665 gsmpPortDownEvent NOTIFICATION-TYPE 1666 OBJECTS { 1667 gsmpSessionStatPortDownEvents, 1668 gsmpEventPort, 1669 gsmpEventPortSessionNumber, 1670 gsmpEventSequenceNumber 1671 } 1672 STATUS current 1673 DESCRIPTION 1674 "When it has been enabled, this notification is 1675 generated when a Port Down Event occurs. 1677 The notification indicates a change in the value of 1678 gsmpSessionStatPortDownEvents. 1680 The session to which this notification 1681 applies is identified by the gsmpSessionThisSideId and 1682 gsmpSessionFarSideId which could be inferred from the 1683 Object Identifier of the gsmpSessionStatPortDownEvents 1684 object contained in the notification." 1685 ::= { gsmpNotifications 6 } 1687 gsmpInvalidLabelEvent NOTIFICATION-TYPE 1688 OBJECTS { 1689 gsmpSessionStatInvLabelEvents, 1690 gsmpEventPort, 1691 gsmpEventLabel, 1692 gsmpEventSequenceNumber 1693 } 1694 STATUS current 1695 DESCRIPTION 1696 "When it has been enabled, this notification is 1697 generated when an Invalid Label Event occurs. 1699 The notification indicates a change in the value of 1700 gsmpSessionStatInvLabelEvents. 1702 The session to which this notification 1703 applies is identified by the gsmpSessionThisSideId and 1704 gsmpSessionFarSideId which could be inferred from the 1705 Object Identifier of the gsmpSessionStatInvLabelEvents 1706 object contained in the notification." 1707 ::= { gsmpNotifications 7 } 1709 gsmpNewPortEvent NOTIFICATION-TYPE 1710 OBJECTS { 1711 gsmpSessionStatNewPortEvents, 1712 gsmpEventPort, 1713 gsmpEventPortSessionNumber, 1714 gsmpEventSequenceNumber 1715 } 1716 STATUS current 1717 DESCRIPTION 1718 "When it has been enabled, this notification is 1719 generated when a New Port Event occurs. 1721 The notification indicates a change in the value of 1722 gsmpSessionStatNewPortEvents. 1724 The session to which this notification 1725 applies is identified by the gsmpSessionThisSideId and 1726 gsmpSessionFarSideId which could be inferred from the 1727 Object Identifier of the gsmpSessionStatNewPortEvents 1728 object contained in the notification." 1729 ::= { gsmpNotifications 8 } 1731 gsmpDeadPortEvent NOTIFICATION-TYPE 1732 OBJECTS { 1733 gsmpSessionStatDeadPortEvents, 1734 gsmpEventPort, 1735 gsmpEventPortSessionNumber, 1736 gsmpEventSequenceNumber 1737 } 1738 STATUS current 1739 DESCRIPTION 1740 "When it has been enabled, this notification is 1741 generated when a Dead Port Event occurs. 1743 The notification indicates a change in the value of 1744 gsmpSessionStatDeadPortEvents. 1746 The session to which this notification 1747 applies is identified by the gsmpSessionThisSideId and 1748 gsmpSessionFarSideId which could be inferred from the 1749 Object Identifier of the gsmpSessionStatDeadPortEvents 1750 object contained in the notification." 1751 ::= { gsmpNotifications 9 } 1753 gsmpAdjacencyUpdateEvent NOTIFICATION-TYPE 1754 OBJECTS { 1755 gsmpSessionAdjacencyCount, 1756 gsmpSessionStatAdjUpdateEvents, 1757 gsmpEventSequenceNumber 1758 } 1759 STATUS current 1760 DESCRIPTION 1761 "When it has been enabled, this notification is 1762 generated when an Adjacency Update Event occurs. 1764 The gsmpSessionAdjacencyCount contains the new value of 1765 the number of adjacencies 1766 that are established with controllers and the switch 1767 partition that is used for this session. 1769 The notification indicates a change in the value of 1770 gsmpSessionStatAdjUpdateEvents. 1772 The session to which this notification 1773 applies is identified by the gsmpSessionThisSideId and 1774 gsmpSessionFarSideId which could be inferred from the 1775 Object Identifier of the gsmpSessionAdjacencyCount 1776 or the gsmpSessionStatAdjUpdateEvents object contained 1777 in the notification." 1778 ::= { gsmpNotifications 10 } 1780 --************************************************************** 1781 -- GSMP Compliance 1782 --************************************************************** 1784 gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 } 1785 gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 } 1786 gsmpModuleCompliance MODULE-COMPLIANCE 1787 STATUS current 1788 DESCRIPTION 1789 "The compliance statement for agents that support 1790 the GSMP MIB." 1791 MODULE -- this module 1792 MANDATORY-GROUPS { gsmpGeneralGroup 1793 } 1794 GROUP gsmpControllerGroup 1795 DESCRIPTION 1796 "This group is mandatory for all Switch 1797 Controllers" 1799 GROUP gsmpSwitchGroup 1800 DESCRIPTION 1801 "This group is mandatory for all Switches" 1803 GROUP gsmpAtmEncapGroup 1804 DESCRIPTION 1805 "This group must be supported if ATM is used for GSMP 1806 encapsulation. " 1808 GROUP gsmpTcpIpEncapGroup 1809 DESCRIPTION 1810 "This group must be supported if TCP/IP is used for GSMP 1811 encapsulation. " 1813 OBJECT gsmpTcpIpEncapAddressType 1814 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), 1815 ipv4z(3), ipv6z(4) } 1816 DESCRIPTION 1817 "An implementation is only required to support 1818 'unknown(0)', and IPv4 addresses. Supporting addresses with 1819 zone index or IPv6 addresses are optional. Defining 1820 Internet addresses by using DNS domain names are not 1821 allowed." 1823 OBJECT gsmpTcpIpEncapAddress 1824 SYNTAX InetAddress (SIZE(0|4|8|16|20)) 1825 DESCRIPTION 1826 "An implementation is only required to support 1827 IPv4 addresses. Supporting addresses with zone index or IPv6 1828 addresses are optional." 1830 GROUP gsmpNotificationObjectsGroup 1831 DESCRIPTION 1832 "This group must be supported if notifications 1833 are supported. " 1835 GROUP gsmpNotificationsGroup 1836 DESCRIPTION 1837 "This group must be supported if notifications 1838 are supported. " 1840 ::= { gsmpCompliances 1 } 1842 -- units of conformance 1844 gsmpGeneralGroup OBJECT-GROUP 1845 OBJECTS { 1846 gsmpSessionVersion, 1847 gsmpSessionTimer, 1848 gsmpSessionPartitionId, 1849 gsmpSessionAdjacencyCount, 1850 gsmpSessionFarSideName, 1851 gsmpSessionFarSidePort, 1852 gsmpSessionFarSideInstance, 1853 gsmpSessionLastFailureCode, 1854 gsmpSessionDiscontinuityTime, 1855 gsmpSessionStartUptime, 1856 gsmpSessionStatSentMessages, 1857 gsmpSessionStatFailureInds, 1858 gsmpSessionStatReceivedMessages, 1859 gsmpSessionStatReceivedFailures, 1860 gsmpSessionStatPortUpEvents, 1861 gsmpSessionStatPortDownEvents, 1862 gsmpSessionStatInvLabelEvents, 1863 gsmpSessionStatNewPortEvents, 1864 gsmpSessionStatDeadPortEvents, 1865 gsmpSessionStatAdjUpdateEvents 1866 } 1867 STATUS current 1868 DESCRIPTION 1869 "Objects that apply to all GSMP implementations." 1870 ::= { gsmpGroups 1 } 1872 gsmpControllerGroup OBJECT-GROUP 1873 OBJECTS { 1874 gsmpControllerMaxVersion, 1875 gsmpControllerTimer, 1876 gsmpControllerPort, 1877 gsmpControllerInstance, 1878 gsmpControllerPartitionType, 1879 gsmpControllerPartitionId, 1880 gsmpControllerDoResync, 1881 gsmpControllerNotificationMap, 1882 gsmpControllerSessionState, 1883 gsmpControllerStorageType, 1884 gsmpControllerRowStatus 1885 } 1886 STATUS current 1887 DESCRIPTION 1888 "Objects that apply GSMP implementations of 1889 Switch Controllers." 1890 ::= { gsmpGroups 2 } 1892 gsmpSwitchGroup OBJECT-GROUP 1893 OBJECTS { 1894 gsmpSwitchMaxVersion, 1895 gsmpSwitchTimer, 1896 gsmpSwitchName, 1897 gsmpSwitchPort, 1898 gsmpSwitchInstance, 1899 gsmpSwitchPartitionType, 1900 gsmpSwitchPartitionId, 1901 gsmpSwitchNotificationMap, 1902 gsmpSwitchSwitchType, 1903 gsmpSwitchWindowSize, 1904 gsmpSwitchSessionState, 1905 gsmpSwitchStorageType, 1906 gsmpSwitchRowStatus 1907 } 1908 STATUS current 1909 DESCRIPTION 1910 "Objects that apply GSMP implementations of 1911 Switches." 1912 ::= { gsmpGroups 3 } 1914 gsmpAtmEncapGroup OBJECT-GROUP 1915 OBJECTS { 1916 gsmpAtmEncapIfIndex, 1917 gsmpAtmEncapVpi, 1918 gsmpAtmEncapVci, 1919 gsmpAtmEncapStorageType, 1920 gsmpAtmEncapRowStatus 1921 } 1922 STATUS current 1923 DESCRIPTION 1924 "Objects that apply to GSMP implementations that 1925 supports ATM for GSMP encapsulation." 1926 ::= { gsmpGroups 4 } 1928 gsmpTcpIpEncapGroup OBJECT-GROUP 1929 OBJECTS { 1930 gsmpTcpIpEncapAddressType, 1931 gsmpTcpIpEncapAddress, 1932 gsmpTcpIpEncapPortNumber, 1933 gsmpTcpIpEncapStorageType, 1934 gsmpTcpIpEncapRowStatus 1935 } 1936 STATUS current 1937 DESCRIPTION 1938 "Objects that apply to GSMP implementations that 1939 supports TCP/IP for GSMP encapsulation." 1940 ::= { gsmpGroups 5 } 1942 gsmpNotificationObjectsGroup OBJECT-GROUP 1943 OBJECTS { 1944 gsmpEventPort, 1945 gsmpEventPortSessionNumber, 1946 gsmpEventSequenceNumber, 1947 gsmpEventLabel 1948 } 1949 STATUS current 1950 DESCRIPTION 1951 "Objects that are contained in the notifications." 1952 ::= { gsmpGroups 6 } 1954 gsmpNotificationsGroup NOTIFICATION-GROUP 1955 NOTIFICATIONS { 1956 gsmpSessionDown, 1957 gsmpSessionUp, 1958 gsmpSentFailureInd, 1959 gsmpReceivedFailureInd, 1960 gsmpPortUpEvent, 1961 gsmpPortDownEvent, 1962 gsmpInvalidLabelEvent, 1963 gsmpNewPortEvent, 1964 gsmpDeadPortEvent, 1965 gsmpAdjacencyUpdateEvent 1966 } 1967 STATUS current 1968 DESCRIPTION 1969 "The notifications which indicate specific changes 1970 in the value of objects gsmpSessionTable" 1971 ::= { gsmpGroups 7 } 1973 END 1974 5. Revision History 1976 This section should be removed when this document is published as an 1977 RFC. 1979 5.1 Changes from < draft-ietf-gsmp-mib-00.txt > 1981 Mib totally remade :-) 1983 5.2 Changes from < draft-ietf-gsmp-mib-01.txt > 1985 Besides from editorial changes the following updates was made; 1986 - Imported AtmVcIdentifier, AtmVpIdentifier FROM ATM-TC-MIB 1987 - Removed serviceModelType 1988 - Separated the Vse and Vsce config stuf in separate tables. 1989 - Also added ATM,TCP/IP, Vse and Vsce groups 1990 - Added control of multiple controllers 1991 - Added Vse window size and switch type configuration. 1992 - Added control of resync strategy 1993 - Added last failure code and discontinuity time 1994 - Added event config and count 1995 - Added notifications 1997 5.3 Changes from < draft-ietf-gsmp-mib-02.txt > 1999 Besides from editorial changes the following updates was made; 2000 - Added gsmpThisSideId and gsmpFarSideId helper objects. 2001 - Replaced Ipv4 address type with TC for Internet Network 2002 Addresses 2003 - Added textual conventions for reader convenience. 2004 - Removed gsmpVsceName object and added default behaviour of 2005 gsmpVseName 2006 - Added row status objects for the encap tables. 2007 - Added DEFVAL and ranges to objects. 2008 - Persistent storage clarified 2009 - "Virtual" removed from names and concepts. gsmpVsceTable now 2010 gsmpControllerTable and gsmpVseTable is gsmpSwitchTable. 2011 - Partition Type object added. 2012 - Session state moved from Session table to Controller and 2013 Switch tables. 2014 - Removed gsmpSwitchAllowMultContr object, it's redundant. 2015 - BITS import removed. 2016 - Partition ID object added to session table. 2017 - gsmpSessionStat table merged into the gsmpSessionTable. 2019 5.4 Changes from < draft-ietf-gsmp-mib-03.txt > 2021 The following updates was made; 2022 - Clarified behaviour on gsmpSessionDiscontinuityTime. 2023 � Changed contact info 2025 5.5 Changes from < draft-ietf-gsmp-mib-04.txt > 2027 Besides from editorial changes the following updates was made; 2028 - Added more text about the generic concepts of GSMP. 2029 - IF-MIB is now RFC 2863, not 2233 2030 - In CONTACT INFO, added WG mailing list,subscribe,archive info 2031 - Added a REVISION clause to the MODULE-IDENTITY 2032 - Notification OIDs updated with less overhead 2033 - Removed trap from Notification names 2034 - Added text about rows created outside SNMP. 2035 - Clarified port and instance number descriptions. 2036 - Clarified when objects can be changed in active row 2037 - gsmpSessionStatUptime changed to TimeStamp and renamed to 2038 gsmpSessionStartUptime 2039 - gsmpSessionStatFailureIndication renamed gsmpSessionStatFailureInds 2040 - ReceivedFailure got an s for plurality 2041 - gsmpEventLabel now of GsmpLabelType (new TC based on octet string). 2042 - Added SYNTAX clauses to inet-address objects compliance. 2043 - GsmpVersion TC changed from enumerated to Unsigned32 2044 - controller and switch instance numbers changed to read-only 2045 - gsmpThisSideId and gsmpFarSideId removed from Notifications, 2046 session ids is inferred from OIDs of the objects instead. 2047 - gsmpThisSideId and gsmpFarSideId objects removed 2048 - StorageType object added. 2049 - encapType objects removed, instead encap type is given by a 2050 encap entry with same id. 2051 - Creation order defined. 2052 - ptype updated to align with draft-ietf-gsmp-09 2054 5.6 Changes from < draft-ietf-gsmp-mib-05.txt > 2056 Besides from editorial changes the following updates was made; 2057 - Default values addded for storage type objects 2058 - Counter32 replaced by ZeroBasedCounter32 TC 2059 - draft-ops-rfc2851-update-04.txt used instead of rfc2851 2060 - InetPortNumber TC used for the gsmpTcpIpEncapPortNumber 2062 6. Acknowledgments 2064 The authors would like to thank Avri Doria and Kenneth Sundell for 2065 their contributions to this specification. Also thanks to David 2066 Partain and Bert Wijnen who has contributed significantly with their 2067 SNMP expertise. 2069 7. References 2071 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2072 of Management Information for TCP/IP-based Internets", STD 2073 16, RFC 1155, May 1990 2075 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2076 16, RFC 1212, March 1991 2078 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2079 SNMP", RFC 1215, March 1991 2081 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2082 Network Management Protocol", STD 15, RFC 1157, May 1990. 2084 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2085 "Introduction to Community-based SNMPv2", RFC 1901, January 2086 1996. 2088 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2089 "Protocol Operations for Version 2 of the Simple Network 2090 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2092 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2093 "Transport Mappings for Version 2 of the Simple Network 2094 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2096 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching 2097 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 2098 Switch Management Protocol Specification," Version 1.1, 2099 RFC 1987, August 1996. 2101 [RFC2021] Waldbusser, S., "Remote Network Monitoring Management 2102 Information Base Version 2 using SMIv2", RFC 2021, 2103 January 1997 2105 [RFC2026] Bradner, S., "The Internet Standards Process - Revision 2106 3", BCP 9, RFC 2026, Harvard University, October 1996 2108 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2109 Requirement Levels", BCP 14, RFC 2119, Harvard University, 2111 March 1997 2113 [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching 2114 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 2115 Switch Management Protocol Specification," Version 2.0, 2116 RFC 2397, March 1998. 2118 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an 2119 IANA Considerations Section in RFCs.", RFC 2434, IBM, 2120 Maxware, October 1998 2122 [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual 2123 Conventions and OBJECT-IDENTITIES for ATM Management", 2124 RFC 2514, February 1999. 2126 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2127 "Introduction to Version 3 of the Internet-standard Network 2128 Management Framework", RFC 2570, April 1999 2130 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2131 Architecture for Describing SNMP Management Frameworks", 2132 RFC 2571, April 1999 2134 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2135 "Message Processing and Dispatching for the Simple Network 2136 Management Protocol (SNMP)", RFC 2572, April 1999 2138 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", 2139 RFC 2573, April 1999 2141 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2142 (USM) for version 3 of the Simple Network Management 2143 Protocol (SNMPv3)", RFC 2574, April 1999 2145 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2146 Access Control Model (VACM) for the Simple Network 2147 Management Protocol (SNMP)", RFC 2575, April 1999 2149 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2150 Rose, M., and S. Waldbusser, "Structure of Management 2151 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2153 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2154 Rose, M., and S. Waldbusser, "Textual Conventions for 2155 SMIv2", STD 58, RFC 2579, April 1999 2157 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2158 Rose, M., and S. Waldbusser, "Conformance Statements for 2159 SMIv2", STD 58, RFC 2580, April 1999 2161 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group MIB" 2162 RFC 2863, June 2000. 2164 [InetAdr] Daniele, M., Haberman, B., Routhier, S. and J., 2165 Schoenwaelder "Textual Conventions for Internet Network 2166 Addresses", work in progress, September 2001 2168 [GSMPv3] Doria, Hellstrand, Sundell, Worster, "General Switch 2169 Management Protocol V3", work in progress, August 2001 2171 [GSMPenc] Worster, Doria, Buerkle, "GSMP Packet Encapsulations for ATM, 2172 Ethernet and TCP", work in progress, August 2001 2174 8. Security Considerations 2176 Assuming that secure network management (such as SNMP v3) is 2177 implemented, the objects represented in this MIB do not pose a threat 2178 to the security of the network. 2180 There are a number of management objects defined in this MIB that 2181 have a MAX-ACCESS clause of read-write and/or read-create. Such 2182 objects may be considered sensitive or vulnerable in some network 2183 environments. The support for SET operations in a non-secure 2184 environment without proper protection can have a negative effect on 2185 network operations. 2187 There are a number of managed objects in this MIB that may contain 2188 sensitive information. These are contained in the gsmpControllerTable 2189 and gsmpSwitchTable. It is thus important to control even GET access 2190 to these objects and possibly to even encrypt the values of these 2191 object when sending them over the network via SNMP. Not all versions 2192 of SNMP provide features for such a secure environment. 2194 SNMPv1 by itself is not a secure environment. Even if the network 2195 itself is secure (for example by using IPSec), even then, there is no 2196 control as to who on the secure network is allowed to access and 2197 GET/SET (read/change/create/delete) the objects in this MIB. 2199 It is recommended that the implementers consider the security 2200 features as provided by the SNMPv3 framework. Specifically, the use 2201 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2202 based Access Control Model RFC 2575 [RFC2575] is recommended. 2204 It is then a customer/user responsibility to ensure that the SNMP 2205 entity giving access to an instance of this MIB, is properly 2206 configured to give access to the objects only to those principals 2207 (users) that have legitimate rights to indeed GET or SET 2208 (change/create/delete) them. 2210 9. Authors' Addresses 2212 Hans Sjostrand 2213 ipUnplugged 2214 P.O. Box 101 60 2215 S-121 28 Stockholm, Sweden 2216 Phone: +46 8 725 5930 2217 Email: hans@ipunplugged.com 2219 Joachim Buerkle 2220 Nortel Networks Germany GmbH & Co. KG 2221 Hahnstrasse 37-39 2222 D-60528 Frankfurt am Main, Germany 2223 Phone: +49 69 6697 3281 2224 Email: joachim.buerkle@nortelnetworks.com 2226 Balaji Srinivasan 2227 CPlane Inc. 2228 5150 El Camino Real 2229 Suite B-31 2230 Los Altos, CA 94022 2231 Phone +1 650 938 8066 ext 103 2232 Email: balaji@cplane.com 2234 10. Full Copyright Statement 2236 Copyright (C) The Internet Society (2001). All Rights Reserved. 2238 This document and translations of it may be copied and furnished to 2239 others, and derivative works that comment on or otherwise explain it 2240 or assist in its implementation may be prepared, copied, published 2241 and distributed, in whole or in part, without restriction of any 2242 kind, provided that the above copyright notice and this paragraph are 2243 included on all such copies and derivative works. However, this 2244 document itself may not be modified in any way, such as by removing 2245 the copyright notice or references to the Internet Society or other 2246 Internet organizations, except as needed for the purpose of 2247 developing Internet standards in which case the procedures for 2248 copyrights defined in the Internet Standards process must be 2249 followed, or as required to translate it into languages other than 2250 English. 2252 The limited permissions granted above are perpetual and will not be 2253 revoked by the Internet Society or its successors or assigns. 2255 This document and the information contained herein is provided on an 2256 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2257 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2258 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2259 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2260 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.