idnits 2.17.1 draft-ietf-gsmp-mib-03.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 are 18 instances 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. ** There are 16 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 578 has weird spacing: '...session by se...' == Line 789 has weird spacing: '...session by se...' == Line 2020 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (November 2000) is 8556 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: 'RFC1987' is defined on line 1875, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 1880, but no explicit reference was found in the text == Unused Reference: 'RFC2233' is defined on line 1883, but no explicit reference was found in the text == Unused Reference: 'RFC2397' is defined on line 1890, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 1895, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 1899, but no explicit reference was found in the text == Unused Reference: 'RFC2851' is defined on line 1938, 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 2233 (Obsoleted by RFC 2863) ** 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: 20 errors (**), 0 flaws (~~), 14 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 Ericsson 3 Expires May 2001 Joachim Buerkle 4 Nortel Networks 5 Balaji Srinivasan 6 Cplane 7 November 2000 9 Definitions of Managed Objects for 10 the General Switch Management Protocol (GSMP) 12 < draft-ietf-gsmp-mib-03.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 Scope....................................................... 5 58 3.2 Overview.................................................... 5 59 3.3 MIB groups.................................................. 6 60 3.3.1 GSMP Switch Controller group ........................ 6 61 3.3.2 GSMP Switch group ................................... 6 62 3.3.3 GSMP Encapsulation groups ........................... 7 63 3.3.4 GSMP General group .................................. 7 64 3.3.5 The GSMP Notifications Group ........................ 7 65 3.4 Textual Conventions ........................................ 9 67 4. GSMP MIB Definitions........................................... 9 69 5. Revision History ............................................. 39 70 5.1 Changes from < draft-ietf-gsmp-mib-00.txt > ............... 39 71 5.2 Changes from < draft-ietf-gsmp-mib-01.txt > ............... 39 72 5.3 Changes from < draft-ietf-gsmp-mib-02.txt > ............... 39 74 6. Acknowledgments............................................... 40 76 7. References.................................................... 40 78 8. Security Considerations ...................................... 42 80 9. Authors' Addresses............................................ 43 82 10. Full Copyright Statement .................................... 43 83 1. Introduction 85 This memo defines a portion of the Management Information Base (MIB) 86 for use with network management protocols in the Internet community. 87 In particular, it describes managed objects for the General Switch 88 Management Protocol (GSMP). 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in RFC 2119 [RFC2119]. 94 2. The SNMP Management Framework 96 The SNMP Management Framework presently consists of five major 97 components: 99 * An overall architecture, described in RFC 2571 [RFC2571]. 101 * Mechanisms for describing and naming objects and events for the 102 purpose of management. The first version of this Structure of 103 Management Information (SMI) is called SMIv1 and described in STD 104 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 105 [RFC1215]. The second version, called SMIv2, is described in STD 106 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580[RFC2580]. 108 * Message protocols for transferring management information. The 109 first version of the SNMP message protocol is called SNMPv1 and 110 described in STD 15, RFC 1157 [RFC1157]. A second version of the 111 SNMP message protocol, which is not an Internet standards track 112 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 113 and RFC 1906 [RFC1906]. The third version of the message protocol 114 is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 115 [RFC2572] and RFC 2574 [RFC2574]. 117 * Protocol operations for accessing management information. The 118 first set of protocol operations and associated PDU formats is 119 described in STD 15, RFC 1157 [RFC1157]. A second set of 120 operations and associated PDU formats is described in 1905 121 [RFC1905]. 123 * A set of fundamental applications described in RFC 2573 [RFC2573] 124 and the view-based access control mechanism described RFC 2575 125 [RFC2575]. 127 A more detailed introduction to the current SNMP Management Framework 128 can be found in RFC 2570 [RFC2570]. 130 Managed objects are accessed via a virtual information store, termed 131 the Management Information Base or MIB. Objects in the MIB are 132 defined using the mechanisms defined in the SMI. 134 This memo specifies a MIB module that is compliant to the SMIv2. A 135 MIB conforming to the SMIv1 can be produced through the appropriate 136 translations. The resulting translated MIB must be semantically 137 equivalent, except where objects or events are omitted because no 138 translation is possible (use of Counter64). Some machine readable 139 information in SMIv2 will be converted into textual descriptions in 140 SMIv1 during the translation process. However, this loss of machine 141 readable information is not considered to change the semantics of the 142 MIB. 144 3. Structure of the MIB 146 This memo defines a portion of the Management Information Base (MIB) 147 for use with network management protocols in the Internet community. 148 In particular, it describes managed objects for the General Switch 149 Management Protocol (GSMP) as defined in [GSMPv3]. 151 3.1 Scope 153 The GSMP mib is a protocol mib. It contains object to configure, 154 monitor and maintain the GSMP protocol agent. It does not provide any 155 information learned via the protocol, such as "all ports config" 156 information. 158 The relationships between virtual entities, such as Virtual Switch 159 Entities, and entities, such as Switch Entities, falls outside of the 160 management of GSMP. This also applies for the management of switch 161 partitions. So this is excluded from the GSMP mib. 163 It is possible to configure which and how many Switch Controllers 164 that are controlling one Switch since every potential session with 165 the switch has to be represented with an Switch entity. It is however 166 not possible to define that one Switch Controller shouldn't allow 167 other Switch controllers to control the same switch or partition on 168 the switch. It is assumed that there are mechanisms that synchronise 169 controllers and the configuration of them. This is outside the scope 170 of this mib. 172 3.2 Overview 174 Each instance of a switch controller - switch partition adjacency is 175 a session between a switch controller entity and a switch entity. The 176 MIB provides objects to configure/setup these entities to form the 177 GSMP sessions. 179 Two tables are used to configure potential GSMP sessions depending if 180 you are acting as a GSMP switch controller or a GSMP switch. Each row 181 in these tables initiates a GSMP session. To create a Switch Entity, 182 an entry in the gsmpSwitchTable is created. To create a Switch 183 Controller Entity, an entry in the gsmpControllerTable is created. 185 In order to define and configure what encapsulation the potential 186 GSMP session shall use, the gsmpControllerEncapType or 187 gsmpSwitchEncapType object in the respective tables is set to 188 ethernet, atm or tcp/ip. If atm is used, a row in the 189 gsmpAtmEncapTable has to be created with the same index as in the 190 controller or switch table. If tcp/ip is used, a row in the 191 gsmpTcpIpEncapTable has to be created with the same index as in the 192 controller or switch table. No extra encapsulation info is needed if 193 ethernet is used. 195 Another table, the gsmpSessionTable, shows the actual sessions that 196 are established or are in the process of being established. Each row 197 represents a specific session between an Entity and a peer. This 198 table carries information about the peer, the session and parameters 199 that was negotiated by the adjacency procedures. The 200 gsmpSessionTable also contains statistical information regarding the 201 session. 203 3.3 MIB groups 205 3.3.1 GSMP Switch Controller group 207 The controller group is used to configure a potential GSMP session on 208 a Switch Controller. A row in the gsmpControllerTable is created for 209 each such session. If ATM or TCP/IP encapsulation is used a 210 corresponding row has to be created in these tables before the 211 session adjacency protocol is initiated. 213 The encapsulation used is specified in the gsmpControllerEncapType 214 object. If ATM or TCP/IP is used, further encapsulation data is 215 defined in the corresponding encapsulation tables. If ethernet is 216 used the MAC address of the interface defined for the session is set 217 by the Controller ID object. 219 The adjacency parameters are defined; such as 220 - Max supported GSMP version 221 � Time between the periodic adjacency messages 222 � Controller local port number and instance number. 223 � Whether partitions are being used and the partition ID for the 224 specific partitions this controller is concerned with if 225 partitions are used. 226 � The resynchronisation strategy for the session is specified. 228 The notification mapping is set to specify for with events the 229 corresponding SNMP notifications are sent. 231 3.3.2 GSMP Switch group 233 The switch group is used to configure a potential GSMP session on a 234 Switch. A row in the gsmpSwitchTable is created for each such 235 session. If ATM or TCP/IP encapsulation is used a corresponding row 236 has to be created in these tables before the session adjacency 237 protocol is initiated. 239 The encapsulation used is specified in the gsmpSwitchEncapType 240 object. If ATM or TCP/IP is used, further encapsulation data is 241 defined in the corresponding encapsulation tables. If ethernet is 242 used the MAC address of the interface defined for the session is set 243 by the Switch ID object. 245 The adjacency parameters are defined; such as 246 - Max supported GSMP version 247 � Time between the periodic adjacency messages 248 � Switch Name, local port number and instance number. 249 � Whether partitions are being used and the partition ID for this 250 specific partition if partitions are used. 251 - The switch type could be set. 252 - The suggested maximum window size for unacknowledged request 253 messages. 255 Also, a notification mapping is set to specify for with events the 256 corresponding SNMP notifications are sent. 258 3.3.3 GSMP Encapsulation groups 260 The ATM Encapsulation Table and the TCP/IP Encapsulation Table 261 provides a way to configure information that are encapsulation 262 specific. The encapsulation data is further specified in [GSMPenc]. 264 If ATM encapsulation is used, the interface and the virtual channel 265 are specified. 267 If TCP/IP is used, the IP address (or DNS address) and the port 268 number are specified. 270 No special config data needed if Ethernet encapsulation is used. 272 3.3.4 GSMP General group 274 The GSMP session table provides a way to monitor and maintain GSMP 275 sessions. 277 The session is defined by a Switch Controller Entity and Switch 278 Entity pair. 280 3.3.5 The GSMP Notifications Group 282 The GSMP Notification Group defines notifications for GSMP entities. 283 These notifications provide a mechanism for a GSMP device to inform 284 the management station of status changes. Also a notification is 285 defined for each type of GSMP events. To disable or enable sending of 286 each notification is done by setting the bitmap accordingly in the 288 Notification mapping objects in the Controller Entity or Switch 289 Entity tables. 291 The group of notifications consists of the following notifications: 293 - gsmpSessionDownTrap 295 This notification is generated when a session is terminating and also 296 reports the final accounting statistics of the session. 298 - gsmpSessionUpTrap 300 This notification is generated when a new session is established. 302 - gsmpSendFailureIndTrap 304 This notification is generated when a message with a failure 305 indication was sent. This means that this notification identifies a 306 change to the gsmpSessionStatFailureIndication object in a row of 307 the gsmpSessionTable. 309 - gsmpReceivedFailureIndTrap 311 This notification is generated when a message with a failure 312 indication received. This means that this notification identifies a 313 change to the gsmpSessionStatReceivedFailure object in a row of the 314 gsmpSessionTable. 316 - gsmpPortUpEventTrap 318 This notification is generated when a Port Up Event is either 319 received or sent. 321 - gsmpPortDownEventTrap 323 This notification is generated when a Port Down Event is either 324 received or sent. 326 - gsmpInvalidLabelEventTrap 328 This notification is generated when an Invalid Label Event is either 329 received or sent. 331 - gsmpNewPortEventTrap 333 This notification is generated when New Port Event either is received 334 or sent. 336 - gsmpDeadPortEventTrap 337 This notification is generated when a Dead Port Event is either 338 received or sent. 340 - gsmpAdjacencyUpdateEventTrap 342 This notification is generated when an Adjacency Update Event is 343 either received or sent. 345 3.4 Textual Conventions 347 The datatypes GsmpNameType, GsmpPartitionType, GsmpPartitionIdType 348 and GsmpEncapType are used as textual conventions in this document. 349 These textual conventions have NO effect on neither the syntax nor 350 the semantics of any managed object. Objects defined using these 351 conventions are always encoded by means of the rules that define 352 their primitive type. Hence, no changes to the SMI or the SNMP are 353 necessary to accommodate these textual conventions which are adopted 354 merely for the convenience of readers. 356 4. GSMP MIB Definitions 358 GSMP-MIB DEFINITIONS ::= BEGIN 360 IMPORTS 361 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 362 Unsigned32, Integer32, Counter32, mib-2 363 FROM SNMPv2-SMI -- RFC2578 364 RowStatus, TruthValue, TimeStamp, TEXTUAL-CONVENTION 365 FROM SNMPv2-TC -- RFC2579 366 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 367 FROM SNMPv2-CONF -- RFC2580 368 InterfaceIndex 369 FROM IF-MIB -- RFC2233 370 AtmVcIdentifier, AtmVpIdentifier 371 FROM ATM-TC-MIB -- RFC2514 372 InetAddressType, InetAddress 373 FROM INET-ADDRESS-MIB -- RFC2851 374 ; 376 gsmpMIB MODULE-IDENTITY 377 LAST-UPDATED "200011130900Z" -- 13 November 2000, 10.00 MET 378 ORGANIZATION "General Switch Management Protocol (gsmp) 379 Working Group, IETF" 380 CONTACT-INFO 381 "WG Chair: Avri Doria 382 Email: avri@nortelnetworks.com 383 WG Chair: Kenneth Sundell 384 Email: ksundell@nortelnetworks.com 386 Editor: Hans Sjostrand 387 Email: hans.sjostrand@ericsson.com 389 Editor: Joachim Buerkle 390 Email: joachim.buerkle@nortelnetworks.com 392 Editor: Balaji Srinivasan 393 Email: balaji@cplane.com" 394 DESCRIPTION 395 "This MIB contains managed object definitions for the 396 General Switch Management Protocol, GSMP, version 3" 397 ::= { mib-2 XXX } 399 gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } 400 gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 2 } 401 gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 } 403 --************************************************************** 404 -- GSMP Textual Conventions 405 --************************************************************** 407 GsmpNameType ::= TEXTUAL-CONVENTION 408 STATUS current 409 DESCRIPTION 410 "The Name is a 48-bit quantity. 411 A 48-bit IEEE 802 MAC address, if 412 available, may be used." 413 SYNTAX OCTET STRING (SIZE(6)) 415 GsmpPartitionType ::= TEXTUAL-CONVENTION 416 STATUS current 417 DESCRIPTION 418 "Defining if partitions are used and how the partition id 419 is negotiated. " 420 SYNTAX INTEGER { 421 noPartition(1), 422 fixedPartitionRequest(2), 423 fixedPartitionAssigned(3) 424 } 426 GsmpPartitionIdType ::= TEXTUAL-CONVENTION 427 STATUS current 428 DESCRIPTION 429 "A 8-bit quantity. The format of the Partition ID is not 430 defined in GSMP. If desired, the Partition ID can be 431 divided into multiple sub-identifiers within a single 432 partition. For example: the Partition ID could be 433 subdivided into a 6-bit partition number and a 2-bit 434 sub-identifier which would allow a switch to support 64 435 partitions with 4 available IDs per partition." 436 SYNTAX OCTET STRING (SIZE(1)) 438 GsmpEncapType ::= TEXTUAL-CONVENTION 439 STATUS current 440 DESCRIPTION 441 "The encapsulation types defined for GSMP." 442 SYNTAX INTEGER { 443 ethernet(1), 444 atm(2), 445 tcpip(3) 446 } 448 GsmpVersion ::= TEXTUAL-CONVENTION 449 STATUS current 450 DESCRIPTION 451 "The version numbers defined for the GSMP protocol." 452 SYNTAX INTEGER { 453 noneOfTheBelow(0), 454 version1dot1(1), 455 version2dot0(2), 456 version3(3) 457 } 459 --************************************************************** 460 -- GSMP Entity Objects 461 --************************************************************** 463 -- 464 -- Switch Controller Entity table 465 -- 467 gsmpControllerTable OBJECT-TYPE 468 SYNTAX SEQUENCE OF GsmpControllerEntry 469 MAX-ACCESS not-accessible 470 STATUS current 471 DESCRIPTION 472 "This table represents the Switch Controller 473 Entity that needs to be configured before a GSMP 474 session might be started." 475 ::= { gsmpObjects 1 } 477 gsmpControllerEntry OBJECT-TYPE 478 SYNTAX GsmpControllerEntry 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION 482 "An entry in the table showing 483 the data for a specific Switch Controller 484 Entity. If partitions are used, one entity 485 corresponds to one specific switch partition. 486 The entry should be persistently stored to 487 survive a restart of the entity. " 488 INDEX { gsmpControllerEntityId } 489 ::= { gsmpControllerTable 1 } 491 GsmpControllerEntry ::= SEQUENCE { 492 gsmpControllerEntityId GsmpNameType, 493 gsmpControllerEncapType GsmpEncapType, 494 gsmpControllerMaxVersion GsmpVersion, 495 gsmpControllerTimer Unsigned32, 496 gsmpControllerPort Unsigned32, 497 gsmpControllerInstance Unsigned32, 498 gsmpControllerPartitionType GsmpPartitionType, 499 gsmpControllerPartitionId GsmpPartitionIdType, 500 gsmpControllerDoResync TruthValue, 501 gsmpControllerNotificationMap BITS, 502 gsmpControllerSessionState INTEGER, 503 gsmpControllerRowStatus RowStatus 504 } 506 gsmpControllerEntityId OBJECT-TYPE 507 SYNTAX GsmpNameType 508 MAX-ACCESS not-accessible 509 STATUS current 510 DESCRIPTION 511 "The Switch Controller Entity Id is unique 512 within the operational context of the device. " 513 ::= { gsmpControllerEntry 1 } 515 gsmpControllerEncapType OBJECT-TYPE 516 SYNTAX GsmpEncapType 517 MAX-ACCESS read-create 518 STATUS current 519 DESCRIPTION 520 "The encapsulation used for this Switch Controller. 521 If atm, a corresponding row in the gsmpAtmEncapTable 522 has to be defined. 523 If tcpip, a corresponding row in the gsmpTcpIpEncapTable 524 has to be defined." 525 ::= { gsmpControllerEntry 2 } 527 gsmpControllerMaxVersion OBJECT-TYPE 528 SYNTAX GsmpVersion 529 MAX-ACCESS read-create 530 STATUS current 531 DESCRIPTION 532 "The max version number of the GSMP protocol being used 533 in this session. The version is negotiated by the 534 adjacency protocol." 535 DEFVAL { version3 } 536 ::= { gsmpControllerEntry 3 } 538 gsmpControllerTimer OBJECT-TYPE 539 SYNTAX Unsigned32(1..255) 540 UNITS "100ms" 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "The timer specifies the nominal time between 545 periodic adjacency protocol messages. It is a constant 546 for the duration of a GSMP session. The timer is 547 specified in units of 100ms." 548 ::= { gsmpControllerEntry 4 } 550 gsmpControllerPort OBJECT-TYPE 551 SYNTAX Unsigned32 552 MAX-ACCESS read-create 553 STATUS current 554 DESCRIPTION 555 "The local port number for the Switch Controller 556 Entity." 557 ::= { gsmpControllerEntry 5 } 559 gsmpControllerInstance OBJECT-TYPE 560 SYNTAX Unsigned32(1..16777215) 561 MAX-ACCESS read-create 562 STATUS current 563 DESCRIPTION 564 "The instance number for the Switch Controller 565 Entity." 566 ::= { gsmpControllerEntry 6 } 568 gsmpControllerPartitionType OBJECT-TYPE 569 SYNTAX GsmpPartitionType 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "A controller can assign the specific partition identifier 574 to the session by setting the Partition Type to 575 fixedPartitionAssigned(3). A controller can let the switch 576 assign the partition identifier by setting the Partition Type 577 to fixedPartitionRequest(2). A controller can specify that 578 no partitions are handled in the session by setting the 579 Partition Type to noPartition(1)." 580 ::= { gsmpControllerEntry 7 } 582 gsmpControllerPartitionId OBJECT-TYPE 583 SYNTAX GsmpPartitionIdType 584 MAX-ACCESS read-create 585 STATUS current 586 DESCRIPTION 587 "The Id for the specific switch partition that this 588 Switch Controller is concerned with. 589 If partitions are not used, i.e Partition Type = 590 noPartition(1), or if the controller lets the 591 switch assigns Partition ID, i.e Partition Type = 592 fixedPartitionRequest(2), then this object should 593 be set to zero." 594 ::= { gsmpControllerEntry 8 } 596 gsmpControllerDoResync OBJECT-TYPE 597 SYNTAX TruthValue 598 MAX-ACCESS read-create 599 STATUS current 600 DESCRIPTION 601 "This object specifies whether the controller should 602 resynchronise or reset in case of loss of synchronisation. 603 If this object is set to true then the Controller should 604 resync with PFLAG=2 (recovered adjacency)." 605 DEFVAL { true } 606 ::= { gsmpControllerEntry 9 } 608 gsmpControllerNotificationMap OBJECT-TYPE 609 SYNTAX BITS { 610 sessionDown(0), 611 sessionUp(1), 612 sendFailureIndication(2), 613 receivedFailureIndication(3), 614 portUpEvent(4), 615 portDownEvent(5), 616 invalidLabelEvent(6), 617 newPortEvent(7), 618 deadPortEvent(8), 619 adjacencyUpdateEvent(9) 620 } 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "This bitmap defines whether a corresponding SNMP 625 notification should be sent if a GSMP event is received 626 by the Switch Controller. If the bit is set to 1 a 627 notification should be sent." 629 DEFVAL {{ sessionDown, sessionUp, 630 sendFailureIndication, receivedFailureIndication }} 631 ::= { gsmpControllerEntry 10 } 633 gsmpControllerSessionState OBJECT-TYPE 634 SYNTAX INTEGER { 635 null(1), 636 synsent(2), 637 synrcvd(3), 638 estab(4) 639 } 640 MAX-ACCESS read-only 641 STATUS current 642 DESCRIPTION 643 "The state for the existing or potential session that 644 this entity is concerned with. 645 The NULL state is returned if the proper encapsulation 646 data is not yet configured, if the row is not in active 647 status or if the session is in NULL state as defined in 648 the GSMP specification." 649 ::= { gsmpControllerEntry 11} 651 gsmpControllerRowStatus OBJECT-TYPE 652 SYNTAX RowStatus 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "An object that allows entries in this table to 657 be created and deleted using the 658 RowStatus convention." 659 ::= { gsmpControllerEntry 12 } 661 -- 662 -- Switch Entity table 663 -- 665 gsmpSwitchTable OBJECT-TYPE 666 SYNTAX SEQUENCE OF GsmpSwitchEntry 667 MAX-ACCESS not-accessible 668 STATUS current 669 DESCRIPTION 670 "This table represents the Switch 671 Entity that needs to be configured before a gsmp 672 session might be started." 673 ::= { gsmpObjects 2 } 675 gsmpSwitchEntry OBJECT-TYPE 676 SYNTAX GsmpSwitchEntry 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "An entry in the table showing 681 the data for a specific Switch 682 Entity. If partitions are used, one entity 683 corresponds to one specific switch partition. 684 The entry should be persistently stored to 685 survive a restart of the entity. " 686 INDEX { gsmpSwitchEntityId } 687 ::= { gsmpSwitchTable 1 } 689 GsmpSwitchEntry ::= SEQUENCE { 690 gsmpSwitchEntityId GsmpNameType, 691 gsmpSwitchEncapType GsmpEncapType, 692 gsmpSwitchMaxVersion GsmpVersion, 693 gsmpSwitchTimer Unsigned32, 694 gsmpSwitchName GsmpNameType, 695 gsmpSwitchPort Unsigned32, 696 gsmpSwitchInstance Unsigned32, 697 gsmpSwitchPartitionType GsmpPartitionType, 698 gsmpSwitchPartitionId GsmpPartitionIdType, 699 gsmpSwitchNotificationMap BITS, 700 gsmpSwitchSwitchType OCTET STRING, 701 gsmpSwitchWindowSize Unsigned32, 702 gsmpSwitchSessionState INTEGER, 703 gsmpSwitchRowStatus RowStatus 704 } 706 gsmpSwitchEntityId OBJECT-TYPE 707 SYNTAX GsmpNameType 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "The Switch Entity Id is unique 712 within the operational context of the device. " 713 ::= { gsmpSwitchEntry 1 } 715 gsmpSwitchEncapType OBJECT-TYPE 716 SYNTAX GsmpEncapType 717 MAX-ACCESS read-create 718 STATUS current 719 DESCRIPTION 720 "The encapsulation used to for this Switch Entity. 721 If atm, a corresponding row in the gsmpAtmEncapTable 722 has to be defined. 723 If tcpip, a corresponing row in the gsmpTcpIpEncapTable 724 has to be defined." 725 ::= { gsmpSwitchEntry 2 } 727 gsmpSwitchMaxVersion OBJECT-TYPE 728 SYNTAX GsmpVersion 729 MAX-ACCESS read-create 730 STATUS current 731 DESCRIPTION 732 "The max version number of the GSMP protocol being 733 supported by this Switch. The version is negotiated by 734 the adjacency protocol." 735 DEFVAL { version3 } 736 ::= { gsmpSwitchEntry 3 } 738 gsmpSwitchTimer OBJECT-TYPE 739 SYNTAX Unsigned32(1..255) 740 UNITS "100ms" 741 MAX-ACCESS read-create 742 STATUS current 743 DESCRIPTION 744 "The timer specifies the nominal time between 745 periodic adjacency protocol messages. It is a constant 746 for the duration of a GSMP session. The timer is 747 specified in units of 100ms." 748 ::= { gsmpSwitchEntry 4 } 750 gsmpSwitchName OBJECT-TYPE 751 SYNTAX GsmpNameType 752 MAX-ACCESS read-create 753 STATUS current 754 DESCRIPTION 755 "The name of the Switch. The first three octets must be an 756 Organisationally Unique Identifier (OUI) that identifies 757 the manufacturer of the Switch. This is by default set to 758 the same value as the gsmpSwitchId object if not 759 separately specified. " 760 ::= {gsmpSwitchEntry 5} 762 gsmpSwitchPort OBJECT-TYPE 763 SYNTAX Unsigned32 764 MAX-ACCESS read-create 765 STATUS current 766 DESCRIPTION 767 "The local port number for this Switch Entity." 768 ::= { gsmpSwitchEntry 6 } 770 gsmpSwitchInstance OBJECT-TYPE 771 SYNTAX Unsigned32(1..16777215) 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "The instance number for the Switch Entity." 777 ::= { gsmpSwitchEntry 7 } 779 gsmpSwitchPartitionType OBJECT-TYPE 780 SYNTAX GsmpPartitionType 781 MAX-ACCESS read-create 782 STATUS current 783 DESCRIPTION 784 "A switch can assign the specific partition identifier to 785 the session by setting the Partition Type to 786 fixedPartitionAssigned(3). A switch can let the controller 787 assign the partition identifier by setting the Partition 788 Type to fixedPartitionRequest(2). A switch can specify 789 that no partitions are handled in the session by setting 790 the Partition Type to noPartition(1)." 791 ::= { gsmpSwitchEntry 8 } 793 gsmpSwitchPartitionId OBJECT-TYPE 794 SYNTAX GsmpPartitionIdType 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "The Id for this specific switch partition that the switch 799 entity represents. If partitions are not used, i.e. 800 Partition Type = noPartition(1), or if the switch lets the 801 controller assigns Partition ID, i.e. Partition Type = 802 fixedPartitionRequest(2), then this object should 803 be set to zero." 804 ::= { gsmpSwitchEntry 9 } 806 gsmpSwitchNotificationMap OBJECT-TYPE 807 SYNTAX BITS { 808 sessionDown(0), 809 sessionUp(1), 810 sendFailureIndication(2), 811 receivedFailureIndication(3), 812 portUpEvent(4), 813 portDownEvent(5), 814 invalidLabelEvent(6), 815 newPortEvent(7), 816 deadPortEvent(8), 817 adjacencyUpdateEvent(9) 818 } 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "This bitmap defines whether a corresponding SNMP 823 notification should be sent if an GSMP event is sent 824 by the Switch Entity. If the bit is set to 1 a 825 notification should be sent." 827 DEFVAL {{ sessionDown, sessionUp, 828 sendFailureIndication, receivedFailureIndication }} 829 ::= { gsmpSwitchEntry 10 } 831 gsmpSwitchSwitchType OBJECT-TYPE 832 SYNTAX OCTET STRING (SIZE(2)) 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "A 16-bit field allocated by the manufacturer 837 of the switch. The Switch Type 838 identifies the product. When the Switch Type is combined 839 with the OUI from the Switch Name the product is 840 uniquely identified. " 841 ::= { gsmpSwitchEntry 11 } 843 gsmpSwitchWindowSize OBJECT-TYPE 844 SYNTAX Unsigned32(1..65535) 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "The maximum number of unacknowledged request messages 849 that may be transmitted by the controller without the 850 possibility of loss. This field is used to prevent 851 request messages from being lost in the switch because of 852 overflow in the receive buffer. The field is a hint to 853 the controller." 854 ::= { gsmpSwitchEntry 12 } 856 gsmpSwitchSessionState OBJECT-TYPE 857 SYNTAX INTEGER { 858 null(1), 859 synsent(2), 860 synrcvd(3), 861 estab(4) 862 } 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The state for the existing or potential session that 867 this entity is concerned with. 868 The NULL state is returned if the proper encapsulation 869 data is not yet configured, if the row is not in active 870 status or if the session is in NULL state as defined in 871 the GSMP specification." 872 ::= { gsmpSwitchEntry 13} 874 gsmpSwitchRowStatus OBJECT-TYPE 875 SYNTAX RowStatus 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "An object that allows entries in this table to 880 be created and deleted using the 881 RowStatus convention." 882 ::= { gsmpSwitchEntry 14 } 884 --************************************************************** 885 -- GSMP Encapsulation Objects 886 --************************************************************** 888 -- 889 -- GSMP ATM Encapsulation Table 890 -- 892 gsmpAtmEncapTable OBJECT-TYPE 893 SYNTAX SEQUENCE OF GsmpAtmEncapEntry 894 MAX-ACCESS not-accessible 895 STATUS current 896 DESCRIPTION 897 "This table contains the atm encapsulation data 898 for the Controller or Switch that uses atm as 899 encapsulation. 900 The entry should be persistently stored to 901 survive a restart of the entity. " 902 ::= { gsmpObjects 3 } 904 gsmpAtmEncapEntry OBJECT-TYPE 905 SYNTAX GsmpAtmEncapEntry 906 MAX-ACCESS not-accessible 907 STATUS current 908 DESCRIPTION 909 "An entry in the table showing 910 the encapsulation data for a 911 specific Switch Controller or Switch." 912 INDEX { gsmpAtmEncapEntityId } 913 ::= { gsmpAtmEncapTable 1 } 915 GsmpAtmEncapEntry ::= SEQUENCE { 916 gsmpAtmEncapEntityId GsmpNameType, 917 gsmpAtmEncapIfIndex InterfaceIndex, 918 gsmpAtmEncapVpi AtmVpIdentifier, 919 gsmpAtmEncapVci AtmVcIdentifier, 920 gsmpAtmEncapRowStatus RowStatus 921 } 923 gsmpAtmEncapEntityId OBJECT-TYPE 924 SYNTAX GsmpNameType 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "The Controller Id or Switch Id that is unique 929 within the operational context of the device. " 930 ::= { gsmpAtmEncapEntry 1 } 932 gsmpAtmEncapIfIndex OBJECT-TYPE 933 SYNTAX InterfaceIndex 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "The interface index for the virtual channel over which 938 the GSMP session is established, i.e., the GSMP control 939 channel for LLC/SNAP encapsulated GSMP messages on an 940 ATM data link layer." 941 ::= { gsmpAtmEncapEntry 2 } 943 gsmpAtmEncapVpi OBJECT-TYPE 944 SYNTAX AtmVpIdentifier 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 " The VPI value for the virtual channel over which the 949 GSMP session is established, i.e., the GSMP control 950 channel for LLC/SNAP encapsulated GSMP messages on an 951 ATM data link layer." 952 DEFVAL { 0 } 953 ::= { gsmpAtmEncapEntry 3 } 955 gsmpAtmEncapVci OBJECT-TYPE 956 SYNTAX AtmVcIdentifier 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 " The VCI value for the virtual channel over which the 961 GSMP session is established, i.e., the GSMP control 962 channel for LLC/SNAP encapsulated GSMP messages on an 963 ATM data link layer." 964 DEFVAL { 15 } 965 ::= { gsmpAtmEncapEntry 4 } 967 gsmpAtmEncapRowStatus OBJECT-TYPE 968 SYNTAX RowStatus 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "An object that allows entries in this table to 973 be created and deleted using the 974 RowStatus convention." 975 ::= { gsmpAtmEncapEntry 5 } 977 -- 978 -- GSMP TCP/IP Encapsulation Table 979 -- 981 gsmpTcpIpEncapTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF GsmpTcpIpEncapEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "This table contains the encapsulation data 987 for the Controller or Switch that uses TCP/IP as 988 encapsulation. The entry should be persistently 989 stored to survive a restart of the entity. " 990 ::= { gsmpObjects 4 } 992 gsmpTcpIpEncapEntry OBJECT-TYPE 993 SYNTAX GsmpTcpIpEncapEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "An entry in the table showing 998 the encapsulation data for a 999 specific Controller or Switch." 1000 INDEX { gsmpTcpIpEncapEntityId } 1001 ::= { gsmpTcpIpEncapTable 1 } 1003 GsmpTcpIpEncapEntry ::= SEQUENCE { 1004 gsmpTcpIpEncapEntityId GsmpNameType, 1005 gsmpTcpIpEncapAddressType InetAddressType, 1006 gsmpTcpIpEncapAddress InetAddress, 1007 gsmpTcpIpEncapPortNumber Unsigned32, 1008 gsmpTcpIpEncapRowStatus RowStatus 1009 } 1011 gsmpTcpIpEncapEntityId OBJECT-TYPE 1012 SYNTAX GsmpNameType 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "The Controller or Switch Id is unique 1017 within the operational context of the device. " 1018 ::= { gsmpTcpIpEncapEntry 1 } 1020 gsmpTcpIpEncapAddressType OBJECT-TYPE 1021 SYNTAX InetAddressType 1022 MAX-ACCESS read-create 1023 STATUS current 1024 DESCRIPTION 1025 "The type of address in gsmpTcpIpEncapAddress." 1026 ::= { gsmpTcpIpEncapEntry 2 } 1028 gsmpTcpIpEncapAddress OBJECT-TYPE 1029 SYNTAX InetAddress 1030 MAX-ACCESS read-create 1031 STATUS current 1032 DESCRIPTION 1033 "The IPv4 or IPv6 address used for 1034 the GSMP session peer." 1035 ::= { gsmpTcpIpEncapEntry 3 } 1037 gsmpTcpIpEncapPortNumber OBJECT-TYPE 1038 SYNTAX Unsigned32(0..65535) 1039 MAX-ACCESS read-create 1040 STATUS current 1041 DESCRIPTION 1042 "The TCP port number used for the TCP session 1043 establishment to the GSMP peer." 1044 DEFVAL { 6068 } 1045 ::= { gsmpTcpIpEncapEntry 4 } 1047 gsmpTcpIpEncapRowStatus OBJECT-TYPE 1048 SYNTAX RowStatus 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "An object that allows entries in this table to 1053 be created and deleted using the 1054 RowStatus convention." 1055 ::= { gsmpTcpIpEncapEntry 5 } 1057 --************************************************************** 1058 -- GSMP Session Objects 1059 --************************************************************** 1061 -- 1062 -- GSMP Session table 1063 -- 1065 gsmpSessionTable OBJECT-TYPE 1066 SYNTAX SEQUENCE OF GsmpSessionEntry 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "This table represents the sessions between 1071 Controller and Switch pairs. " 1073 ::= { gsmpObjects 5 } 1075 gsmpSessionEntry OBJECT-TYPE 1076 SYNTAX GsmpSessionEntry 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "An entry in the table showing 1081 the session data for a specific Controller and 1082 Switch pair. Also, statistics for this specific 1083 session is shown." 1084 INDEX { gsmpSessionThisSideId, gsmpSessionFarSideId } 1085 ::= { gsmpSessionTable 1 } 1087 GsmpSessionEntry ::= SEQUENCE { 1088 gsmpSessionThisSideId GsmpNameType, 1089 gsmpSessionFarSideId GsmpNameType, 1090 gsmpSessionVersion GsmpVersion, 1091 gsmpSessionTimer Integer32, 1092 gsmpSessionPartitionId GsmpPartitionIdType, 1093 gsmpSessionAdjacencyCount Unsigned32, 1094 gsmpSessionFarSideName GsmpNameType, 1095 gsmpSessionFarSidePort Unsigned32, 1096 gsmpSessionFarSideInstance Unsigned32, 1097 gsmpSessionLastFailureCode Unsigned32, 1098 gsmpSessionDiscontinuityTime TimeStamp, 1099 gsmpSessionStatUptime Counter32, 1100 gsmpSessionStatSentMessages Counter32, 1101 gsmpSessionStatFailureIndication Counter32, 1102 gsmpSessionStatReceivedMessages Counter32, 1103 gsmpSessionStatReceivedFailure Counter32, 1104 gsmpSessionStatPortUpEvents Counter32, 1105 gsmpSessionStatPortDownEvents Counter32, 1106 gsmpSessionStatInvLabelEvents Counter32, 1107 gsmpSessionStatNewPortEvents Counter32, 1108 gsmpSessionStatDeadPortEvents Counter32, 1109 gsmpSessionStatAdjUpdateEvents Counter32 1110 } 1112 gsmpSessionThisSideId OBJECT-TYPE 1113 SYNTAX GsmpNameType 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "This side ID uniquely identifies the entity that this 1118 session relates to within the operational 1119 context of the device. " 1120 ::= { gsmpSessionEntry 1 } 1122 gsmpSessionFarSideId OBJECT-TYPE 1123 SYNTAX GsmpNameType 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "The Far side ID uniquely identifies the entity that this 1128 session is established against. " 1129 ::= { gsmpSessionEntry 2 } 1131 gsmpSessionVersion OBJECT-TYPE 1132 SYNTAX GsmpVersion 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The version number of the GSMP protocol being used in 1137 this session. The version is the result of the 1138 negotiation by the adjacency protocol." 1139 ::= { gsmpSessionEntry 3 } 1141 gsmpSessionTimer OBJECT-TYPE 1142 SYNTAX Integer32 1143 UNITS "100ms" 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The timer specifies the time remaining until the 1148 adjacency timer expires. The object could take negative 1149 values since if no valid GSMP messages are 1150 received in any period of time in excess of three times 1151 the value of the Timer negotiated by the adjacency 1152 protocol loss of synchronisation may be declared. The 1153 timer is specified in units of 100ms." 1154 ::= { gsmpSessionEntry 4 } 1156 gsmpSessionPartitionId OBJECT-TYPE 1157 SYNTAX GsmpPartitionIdType 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "The Partition Id for the specific switch partition that 1162 this session is concerned with." 1163 ::= { gsmpSessionEntry 5 } 1165 gsmpSessionAdjacencyCount OBJECT-TYPE 1166 SYNTAX Unsigned32(1..255) 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "This object specifies the current number of adjacencies 1171 that are established with controllers and the switch 1172 partition that is used for this session. The value 1173 includes this session." 1174 ::= { gsmpSessionEntry 6 } 1176 gsmpSessionFarSideName OBJECT-TYPE 1177 SYNTAX GsmpNameType 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "The name of the far side as advertised in the adjacency 1182 message." 1183 ::= {gsmpSessionEntry 7} 1185 gsmpSessionFarSidePort OBJECT-TYPE 1186 SYNTAX Unsigned32 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "The local port number of the link across which the 1191 message is being sent." 1192 ::= { gsmpSessionEntry 8 } 1194 gsmpSessionFarSideInstance OBJECT-TYPE 1195 SYNTAX Unsigned32(1..16777215) 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The instance number used for the link during this 1200 session. Zero is not a valid instance number." 1201 ::= { gsmpSessionEntry 9 } 1203 gsmpSessionLastFailureCode OBJECT-TYPE 1204 SYNTAX Unsigned32(0..255) 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "This is the last failure code that was received over 1209 this session. If no failure code have been received, the 1210 value is zero." 1211 ::= { gsmpSessionEntry 10 } 1213 gsmpSessionDiscontinuityTime OBJECT-TYPE 1214 SYNTAX TimeStamp 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The value of sysUpTime on the most recent occasion at 1219 which one or more of this session's counters 1220 suffered a discontinuity. If no such discontinuities have 1221 occurred since then, this object contains a zero value. 1222 Also, an NMS can distinguish when a session 1223 between a given Entity and the far side goes away and 1224 then is 're-established'. This value would change and 1225 thus indicate to the NMS that this is a 1226 different session." 1227 ::= { gsmpSessionEntry 11 } 1229 gsmpSessionStatUptime OBJECT-TYPE 1230 SYNTAX Counter32 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "The time in seconds that the session have been in 1235 established state." 1236 ::= { gsmpSessionEntry 12 } 1238 gsmpSessionStatSentMessages OBJECT-TYPE 1239 SYNTAX Counter32 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "The number of messages that have been sent in this 1244 session." 1245 ::= { gsmpSessionEntry 13 } 1247 gsmpSessionStatFailureIndication OBJECT-TYPE 1248 SYNTAX Counter32 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The number of messages that have been sent with a 1253 failure indication in this session." 1254 ::= { gsmpSessionEntry 14 } 1256 gsmpSessionStatReceivedMessages OBJECT-TYPE 1257 SYNTAX Counter32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The number of messages that have been received in 1262 this session." 1263 ::= { gsmpSessionEntry 15 } 1265 gsmpSessionStatReceivedFailure OBJECT-TYPE 1266 SYNTAX Counter32 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The number of messages that have been received in 1271 this session with a failure indication." 1272 ::= { gsmpSessionEntry 16 } 1274 gsmpSessionStatPortUpEvents OBJECT-TYPE 1275 SYNTAX Counter32 1276 MAX-ACCESS read-only 1277 STATUS current 1278 DESCRIPTION 1279 "The number of Port Up events that have been sent or 1280 received on this session." 1281 ::= { gsmpSessionEntry 17 } 1283 gsmpSessionStatPortDownEvents OBJECT-TYPE 1284 SYNTAX Counter32 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "The number of Port Down events that have been sent or 1289 received on this session." 1290 ::= { gsmpSessionEntry 18 } 1292 gsmpSessionStatInvLabelEvents OBJECT-TYPE 1293 SYNTAX Counter32 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "The number of Invalid label events that have been sent 1298 or received on this session." 1299 ::= { gsmpSessionEntry 19 } 1301 gsmpSessionStatNewPortEvents OBJECT-TYPE 1302 SYNTAX Counter32 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "The number of New Port events that have been sent or 1307 received on this session." 1308 ::= { gsmpSessionEntry 20 } 1310 gsmpSessionStatDeadPortEvents OBJECT-TYPE 1311 SYNTAX Counter32 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The number of Dead Port events that have been sent or 1316 received on this session." 1317 ::= { gsmpSessionEntry 21 } 1319 gsmpSessionStatAdjUpdateEvents OBJECT-TYPE 1320 SYNTAX Counter32 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "The number of Adjacency Update events that have been sent 1325 or received on this session." 1326 ::= { gsmpSessionEntry 22 } 1328 -- ************************************************************** 1329 -- GSMP Notifications 1330 -- ************************************************************** 1332 gsmpNotificationsPrefix 1333 OBJECT IDENTIFIER ::= { gsmpNotifications 0 } 1334 gsmpNotificationsObjects 1335 OBJECT IDENTIFIER ::= { gsmpNotifications 1 } 1337 -- 1338 -- Notification objects 1339 -- 1341 gsmpEventPort OBJECT-TYPE 1342 SYNTAX Unsigned32 1343 MAX-ACCESS accessible-for-notify 1344 STATUS current 1345 DESCRIPTION 1346 "This object specifies the Port Number that is 1347 carried in this event." 1348 ::= { gsmpNotificationsObjects 1 } 1350 gsmpEventPortSessionNumber OBJECT-TYPE 1351 SYNTAX Unsigned32 1352 MAX-ACCESS accessible-for-notify 1353 STATUS current 1354 DESCRIPTION 1355 "This object specifies the Port Session Number that is 1356 carried in this event." 1357 ::= { gsmpNotificationsObjects 2 } 1359 gsmpEventSequenceNumber OBJECT-TYPE 1360 SYNTAX Unsigned32 1361 MAX-ACCESS accessible-for-notify 1362 STATUS current 1363 DESCRIPTION 1364 "This object specifies the Event Sequence Number that is 1365 carried in this event." 1366 ::= { gsmpNotificationsObjects 3 } 1368 gsmpEventLabel OBJECT-TYPE 1369 SYNTAX Unsigned32 1370 MAX-ACCESS accessible-for-notify 1371 STATUS current 1372 DESCRIPTION 1373 "This object specifies the Label that is 1374 carried in this event." 1375 ::= { gsmpNotificationsObjects 4 } 1377 gsmpThisSideId OBJECT-TYPE 1378 SYNTAX GsmpNameType 1379 MAX-ACCESS accessible-for-notify 1380 STATUS current 1381 DESCRIPTION 1382 "This side ID uniquely identifies the entity that this 1383 session event relates to. " 1384 ::= { gsmpNotificationsObjects 5 } 1386 gsmpFarSideId OBJECT-TYPE 1387 SYNTAX GsmpNameType 1388 MAX-ACCESS accessible-for-notify 1389 STATUS current 1390 DESCRIPTION 1391 "Far side ID uniquely identifies the other entity that 1392 this session event relates to. " 1393 ::= { gsmpNotificationsObjects 6 } 1395 -- 1396 -- Notifications 1397 -- 1399 gsmpSessionDownTrap NOTIFICATION-TYPE 1400 OBJECTS { 1401 gsmpThisSideId, 1402 gsmpFarSideId, 1403 gsmpSessionStatUptime, 1404 gsmpSessionStatSentMessages, 1405 gsmpSessionStatFailureIndication, 1406 gsmpSessionStatReceivedMessages, 1407 gsmpSessionStatReceivedFailure, 1408 gsmpSessionStatPortUpEvents, 1409 gsmpSessionStatPortDownEvents, 1410 gsmpSessionStatInvLabelEvents, 1411 gsmpSessionStatNewPortEvents, 1412 gsmpSessionStatDeadPortEvents, 1413 gsmpSessionStatAdjUpdateEvents 1414 } 1415 STATUS current 1416 DESCRIPTION 1417 "When it has been enabled, this notification is 1418 generated whenever a session is taken down, regardless 1419 of whether the session went down normally or not. 1420 Its purpose is to allow a management application 1421 (primarily an accounting application) that is 1422 monitoring the session statistics to receive the final 1423 values of these counters, so that the application can 1424 properly account for the amounts the counters were 1425 incremented since the last time the application polled 1426 them. The gsmpSessionStatUptime object provides the 1427 total amount of time that the session was active. 1429 This notification is not a substitute for polling the 1430 session statistic counts. In particular, the count 1431 values reported in this notification cannot be assumed 1432 to be the complete totals for the life of the session, 1433 since they may have wrapped while the 1434 session was up. 1436 The session to which the objects in this notification 1437 apply is identified by the session gsmpThisSideId, 1438 gsmpFarSideId objects. 1439 An instance of this notification will contain exactly 1440 one instance of each of its objects, and these objects 1441 will all belong to the same conceptual row of the 1442 gsmpSessionTable." 1443 ::= { gsmpNotificationsPrefix 1 } 1445 gsmpSessionUpTrap NOTIFICATION-TYPE 1446 OBJECTS { 1447 gsmpThisSideId, 1448 gsmpFarSideId 1449 } 1450 STATUS current 1451 DESCRIPTION 1452 "When it has been enabled, this notification is 1453 generated when new session is established. 1455 The new session is identified by the 1456 gsmpThisSideId, gsmpFarSideId objects." 1457 ::= { gsmpNotificationsPrefix 2 } 1459 gsmpSentFailureIndTrap NOTIFICATION-TYPE 1460 OBJECTS { 1461 gsmpThisSideId, 1462 gsmpFarSideId, 1463 gsmpSessionLastFailureCode, 1464 gsmpSessionStatFailureIndication 1465 } 1466 STATUS current 1467 DESCRIPTION 1468 "When it has been enabled, this notification is 1469 generated when a message with a failure indication was 1470 sent. 1472 The notification indicates a change in the value of 1473 gsmpSessionStatFailureIndication. The 1474 gsmpSessionLastFailureCode contains the failure 1475 reason." 1476 ::= { gsmpNotificationsPrefix 3 } 1478 gsmpReceivedFailureIndTrap NOTIFICATION-TYPE 1479 OBJECTS { 1480 gsmpThisSideId, 1481 gsmpFarSideId, 1482 gsmpSessionLastFailureCode, 1483 gsmpSessionStatReceivedFailure 1484 } 1485 STATUS current 1486 DESCRIPTION 1487 "When it has been enabled, this notification is 1488 generate when a message with a failure indication 1489 is received. 1491 The notification indicates a change in the value of 1492 gsmpSessionStatReceivedFailure. The 1493 gsmpSessionLastFailureCode contains the failure 1494 reason." 1495 ::= { gsmpNotificationsPrefix 4 } 1497 gsmpPortUpEventTrap NOTIFICATION-TYPE 1498 OBJECTS { 1499 gsmpThisSideId, 1500 gsmpFarSideId, 1501 gsmpSessionStatPortUpEvents, 1502 gsmpEventPort, 1503 gsmpEventPortSessionNumber, 1504 gsmpEventSequenceNumber 1505 } 1506 STATUS current 1507 DESCRIPTION 1508 "When it has been enabled, this notification is 1509 generated when a Port Up Event occurs. 1511 The notification indicates a change in the value of 1512 gsmpSessionStatPortUpEvents." 1513 ::= { gsmpNotificationsPrefix 5 } 1515 gsmpPortDownEventTrap NOTIFICATION-TYPE 1516 OBJECTS { 1517 gsmpThisSideId, 1518 gsmpFarSideId, 1519 gsmpSessionStatPortDownEvents, 1520 gsmpEventPort, 1521 gsmpEventPortSessionNumber, 1522 gsmpEventSequenceNumber 1523 } 1524 STATUS current 1525 DESCRIPTION 1526 "When it has been enabled, this notification is 1527 generated when a Port Down Event occurs. 1529 The notification indicates a change in the value of 1530 gsmpSessionStatPortDownEvents." 1531 ::= { gsmpNotificationsPrefix 6 } 1533 gsmpInvalidLabelEventTrap NOTIFICATION-TYPE 1534 OBJECTS { 1535 gsmpThisSideId, 1536 gsmpFarSideId, 1537 gsmpSessionStatInvLabelEvents, 1538 gsmpEventPort, 1539 gsmpEventLabel, 1540 gsmpEventSequenceNumber 1541 } 1542 STATUS current 1543 DESCRIPTION 1544 "When it has been enabled, this notification is 1545 generated when an Invalid Label Event occurs. 1547 The notification indicates a change in the value of 1548 gsmpSessionStatInvLabelEvents." 1549 ::= { gsmpNotificationsPrefix 7 } 1551 gsmpNewPortEventTrap NOTIFICATION-TYPE 1552 OBJECTS { 1553 gsmpThisSideId, 1554 gsmpFarSideId, 1555 gsmpSessionStatNewPortEvents, 1556 gsmpEventPort, 1557 gsmpEventPortSessionNumber, 1558 gsmpEventSequenceNumber 1559 } 1560 STATUS current 1561 DESCRIPTION 1562 "When it has been enabled, this notification is 1563 generated when a New Port Event occurs. 1565 The notification indicates a change in the value of 1566 gsmpSessionStatNewPortEvents." 1567 ::= { gsmpNotificationsPrefix 8 } 1569 gsmpDeadPortEventTrap NOTIFICATION-TYPE 1570 OBJECTS { 1571 gsmpThisSideId, 1572 gsmpFarSideId, 1573 gsmpSessionStatDeadPortEvents, 1574 gsmpEventPort, 1575 gsmpEventPortSessionNumber, 1576 gsmpEventSequenceNumber 1577 } 1578 STATUS current 1579 DESCRIPTION 1580 "When it has been enabled, this notification is 1581 generated when a Dead Port Event occurs. 1583 The notification indicates a change in the value of 1584 gsmpSessionStatDeadPortEvents." 1585 ::= { gsmpNotificationsPrefix 9 } 1587 gsmpAdjacencyUpdateEventTrap NOTIFICATION-TYPE 1588 OBJECTS { 1589 gsmpThisSideId, 1590 gsmpFarSideId, 1591 gsmpSessionAdjacencyCount, 1592 gsmpSessionStatAdjUpdateEvents, 1593 gsmpEventSequenceNumber 1594 } 1595 STATUS current 1596 DESCRIPTION 1597 "When it has been enabled, this notification is 1598 generated when an Adjacency Update Event occurs. 1600 The gsmpSessionAdjacencyCount contains the new value of 1601 the number of adjacencies 1602 that are established with controllers and the switch 1603 partition that is used for this session. 1605 The notification indicates a change in the value of 1606 gsmpSessionStatAdjUpdateEvents." 1607 ::= { gsmpNotificationsPrefix 10 } 1608 --************************************************************** 1609 -- GSMP Compliance 1610 --************************************************************** 1612 gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 } 1613 gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 } 1615 gsmpModuleCompliance MODULE-COMPLIANCE 1616 STATUS current 1617 DESCRIPTION 1618 "The compliance statement for agents that support 1619 the GSMP MIB." 1620 MODULE -- this module 1621 MANDATORY-GROUPS { gsmpGeneralGroup 1622 } 1623 GROUP gsmpControllerGroup 1624 DESCRIPTION 1625 "This group is mandatory for all Switch 1626 Controllers" 1628 GROUP gsmpSwitchGroup 1629 DESCRIPTION 1630 "This group is mandatory for all Switches" 1632 GROUP gsmpAtmEncapGroup 1633 DESCRIPTION 1634 "This group must be supported if ATM is used for GSMP 1635 encapsulation. " 1637 GROUP gsmpTcpIpEncapGroup 1638 DESCRIPTION 1639 "This group must be supported if TCP/IP is used for GSMP 1640 encapsulation. " 1642 OBJECT gsmpTcpIpEncapAddressType 1643 DESCRIPTION 1644 "An implementation is only required to support 1645 'unknown(0)', and IPv4 addresses. Supporting IPv6 addresses 1646 is optional. Defining Internet addresses by using DNS 1647 domain names are not allowed." 1649 OBJECT gsmpTcpIpEncapAddress 1650 DESCRIPTION 1651 "An implementation is only required to support 1652 IPv4 addresses. Supporting IPv6 addresses 1653 is optional. Prefix sizes could range from 0..20." 1655 GROUP gsmpNotificationObjectsGroup 1656 DESCRIPTION 1657 "This group must be supported if notifications 1658 are supported. " 1660 GROUP gsmpNotificationsGroup 1661 DESCRIPTION 1662 "This group must be supported if notifications 1663 are supported. " 1665 ::= { gsmpCompliances 1 } 1667 -- units of conformance 1669 gsmpGeneralGroup OBJECT-GROUP 1670 OBJECTS { 1671 gsmpSessionVersion, 1672 gsmpSessionTimer, 1673 gsmpSessionPartitionId, 1674 gsmpSessionAdjacencyCount, 1675 gsmpSessionFarSideName, 1676 gsmpSessionFarSidePort, 1677 gsmpSessionFarSideInstance, 1678 gsmpSessionLastFailureCode, 1679 gsmpSessionDiscontinuityTime, 1680 gsmpSessionStatUptime, 1681 gsmpSessionStatSentMessages, 1682 gsmpSessionStatFailureIndication, 1683 gsmpSessionStatReceivedMessages, 1684 gsmpSessionStatReceivedFailure, 1685 gsmpSessionStatPortUpEvents, 1686 gsmpSessionStatPortDownEvents, 1687 gsmpSessionStatInvLabelEvents, 1688 gsmpSessionStatNewPortEvents, 1689 gsmpSessionStatDeadPortEvents, 1690 gsmpSessionStatAdjUpdateEvents 1691 } 1692 STATUS current 1693 DESCRIPTION 1694 "Objects that apply to all GSMP implementations." 1695 ::= { gsmpGroups 1 } 1697 gsmpControllerGroup OBJECT-GROUP 1698 OBJECTS { 1699 gsmpControllerEncapType, 1700 gsmpControllerMaxVersion, 1701 gsmpControllerTimer, 1702 gsmpControllerPort, 1703 gsmpControllerInstance, 1704 gsmpControllerPartitionType, 1705 gsmpControllerPartitionId, 1706 gsmpControllerDoResync, 1707 gsmpControllerNotificationMap, 1708 gsmpControllerSessionState, 1709 gsmpControllerRowStatus 1710 } 1711 STATUS current 1712 DESCRIPTION 1713 "Objects that apply GSMP implementations of 1714 Switch Controllers." 1715 ::= { gsmpGroups 2 } 1717 gsmpSwitchGroup OBJECT-GROUP 1718 OBJECTS { 1719 gsmpSwitchEncapType, 1720 gsmpSwitchMaxVersion, 1721 gsmpSwitchTimer, 1722 gsmpSwitchName, 1723 gsmpSwitchPort, 1724 gsmpSwitchInstance, 1725 gsmpSwitchPartitionType, 1726 gsmpSwitchPartitionId, 1727 gsmpSwitchNotificationMap, 1728 gsmpSwitchSwitchType, 1729 gsmpSwitchWindowSize, 1730 gsmpSwitchSessionState, 1731 gsmpSwitchRowStatus 1732 } 1733 STATUS current 1734 DESCRIPTION 1735 "Objects that apply GSMP implementations of 1736 Switches." 1737 ::= { gsmpGroups 3 } 1739 gsmpAtmEncapGroup OBJECT-GROUP 1740 OBJECTS { 1741 gsmpAtmEncapIfIndex, 1742 gsmpAtmEncapVpi, 1743 gsmpAtmEncapVci, 1744 gsmpAtmEncapRowStatus 1745 } 1746 STATUS current 1747 DESCRIPTION 1748 "Objects that apply to GSMP implementations that 1749 supports ATM for GSMP encapsulation." 1750 ::= { gsmpGroups 4 } 1752 gsmpTcpIpEncapGroup OBJECT-GROUP 1753 OBJECTS { 1754 gsmpTcpIpEncapAddressType, 1755 gsmpTcpIpEncapAddress, 1756 gsmpTcpIpEncapPortNumber, 1757 gsmpTcpIpEncapRowStatus 1758 } 1759 STATUS current 1760 DESCRIPTION 1761 "Objects that apply to GSMP implementations that 1762 supports TCP/IP for GSMP encapsulation." 1763 ::= { gsmpGroups 5 } 1765 gsmpNotificationObjectsGroup OBJECT-GROUP 1766 OBJECTS { 1767 gsmpEventPort, 1768 gsmpEventPortSessionNumber, 1769 gsmpEventSequenceNumber, 1770 gsmpEventLabel, 1771 gsmpThisSideId, 1772 gsmpFarSideId} 1773 STATUS current 1774 DESCRIPTION 1775 "Objects that are contained in the notifications." 1776 ::= { gsmpGroups 6 } 1778 gsmpNotificationsGroup NOTIFICATION-GROUP 1779 NOTIFICATIONS { 1780 gsmpSessionDownTrap, 1781 gsmpSessionUpTrap, 1782 gsmpSentFailureIndTrap, 1783 gsmpReceivedFailureIndTrap, 1784 gsmpPortUpEventTrap, 1785 gsmpPortDownEventTrap, 1786 gsmpInvalidLabelEventTrap, 1787 gsmpNewPortEventTrap, 1788 gsmpDeadPortEventTrap, 1789 gsmpAdjacencyUpdateEventTrap 1790 } 1791 STATUS current 1792 DESCRIPTION 1793 "The notifications which indicate specific changes 1794 in the value of objects gsmpSessionTable." 1795 ::= { gsmpGroups 7 } 1797 END 1798 5. Revision History 1800 This section should be removed when this document is published as an 1801 RFC. 1803 5.1 Changes from < draft-ietf-gsmp-mib-00.txt > 1805 Mib totally remade :-) 1807 5.2 Changes from < draft-ietf-gsmp-mib-01.txt > 1809 Besides from editorial changes the following updates was made; 1810 - Imported AtmVcIdentifier, AtmVpIdentifier FROM ATM-TC-MIB 1811 - Removed serviceModelType 1812 - Separated the Vse and Vsce config stuf in separate tables. 1813 - Also added ATM,TCP/IP, Vse and Vsce groups 1814 - Added control of multiple controllers 1815 - Added Vse window size and switch type configuration. 1816 - Added control of resync strategy 1817 - Added last failure code and discontinuity time 1818 - Added event config and count 1819 - Added notifications 1821 5.3 Changes from < draft-ietf-gsmp-mib-02.txt > 1823 Besides from editorial changes the following updates was made; 1824 - Added gsmpThisSideId and gsmpFarSideId helper objects. 1825 - Replaced Ipv4 address type with TC for Internet Network 1826 Addresses 1827 - Added textual conventions for reader convenience. 1828 - Removed gsmpVsceName object and added default behaviour of 1829 gsmpVseName 1830 � Added row status objects for the encap tables. 1831 � Added DEFVAL and ranges to objects. 1832 � Persistent storage clarified 1833 � "Virtual" removed from names and concepts. gsmpVsceTable now 1834 gsmpControllerTable and gsmpVseTable is gsmpSwitchTable. 1835 � Partition Type object added. 1836 � Session state moved from Session table to Controller and 1837 Switch tables. 1838 � Removed gsmpSwitchAllowMultContr object, it's redundant. 1839 � BITS import removed. 1840 � Partition ID object added to session table. 1841 � gsmpSessionStat table merged into the gmspSessionTable. 1843 6. Acknowledgments 1845 The authors would like to thank Avri Doria and David Partain for 1846 valuable input and comments. 1848 7. References 1850 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1851 of Management Information for TCP/IP-based Internets", STD 1852 16, RFC 1155, May 1990 1854 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1855 16, RFC 1212, March 1991 1857 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1858 SNMP", RFC 1215, March 1991 1860 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1861 Network Management Protocol", STD 15, RFC 1157, May 1990. 1863 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1864 "Introduction to Community-based SNMPv2", RFC 1901, January 1865 1996. 1867 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1868 "Protocol Operations for Version 2 of the Simple Network 1869 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1871 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1872 "Transport Mappings for Version 2 of the Simple Network 1873 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1875 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching 1876 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 1877 Switch Management Protocol Specification," Version 1.1, 1878 RFC 1987, August 1996. 1880 [RFC2026] Bradner, S., "The Internet Standards Process � Revision 1881 3", BCP 9, RFC 2026, Harvard University, October 1996 1883 [RFC2233] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 1884 using SMIv2", RFC 2233, November 1997. 1886 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1887 Requirement Levels", BCP 14, RFC 2119, Harvard University, 1888 March 1997 1890 [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching 1891 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 1892 Switch Management Protocol Specification," Version 2.0, 1893 RFC 2397, March 1998. 1895 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an 1896 IANA Considerations Section in RFCs.", RFC 2434, IBM, 1897 Maxware, October 1998 1899 [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual 1900 Conventions and OBJECT-IDENTITIES for ATM Management", 1901 RFC 2514, February 1999. 1903 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1904 "Introduction to Version 3 of the Internet-standard Network 1905 Management Framework", RFC 2570, April 1999 1907 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1908 Architecture for Describing SNMP Management Frameworks", 1909 RFC 2571, April 1999 1911 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1912 "Message Processing and Dispatching for the Simple Network 1913 Management Protocol (SNMP)", RFC 2572, April 1999 1915 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1916 RFC 2573, April 1999 1918 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1919 (USM) for version 3 of the Simple Network Management 1920 Protocol (SNMPv3)", RFC 2574, April 1999 1922 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1923 Access Control Model (VACM) for the Simple Network 1924 Management Protocol (SNMP)", RFC 2575, April 1999 1926 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1927 Rose, M., and S. Waldbusser, "Structure of Management 1928 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1930 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1931 Rose, M., and S. Waldbusser, "Textual Conventions for 1932 SMIv2", STD 58, RFC 2579, April 1999 1934 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1935 Rose, M., and S. Waldbusser, "Conformance Statements for 1936 SMIv2", STD 58, RFC 2580, April 1999 1938 [RFC2851] Daniele, M., Haberman, B., Routhier, S. and J., 1939 Schoenwaelder "Textual Conventions for Internet Network 1940 Addresses", RFC 2851, June 2000 1942 [GSMPv3] Doria, Hellstrand, Sundell, Worster, "General Switch 1943 Management Protocol V3", work in progress, November 2000 1945 [GSMPenc] Worster, Doria, Buerkle, "GSMP Packet Encapsulations for ATM, 1946 Ethernet and TCP", work in progress, November 2000 1948 8. Security Considerations 1950 Assuming that secure network management (such as SNMP v3) is 1951 implemented, the objects represented in this MIB do not pose a threat 1952 to the security of the network. 1954 There are a number of management objects defined in this MIB that 1955 have a MAX-ACCESS clause of read-write and/or read-create. Such 1956 objects may be considered sensitive or vulnerable in some network 1957 environments. The support for SET operations in a non-secure 1958 environment without proper protection can have a negative effect on 1959 network operations. 1961 There are a number of managed objects in this MIB that may contain 1962 sensitive information. These are contained in the gsmpSwitchTable and 1963 gsmpControllerTable. It is thus important to control even GET access to 1964 these objects and possibly to even encrypt the values of these object 1965 when sending them over the network via SNMP. Not all versions of 1966 SNMP provide features for such a secure environment. 1968 SNMPv2 by itself is not a secure environment. Even if the network 1969 itself is secure (for example by using IPSec), even then, there is no 1970 control as to who on the secure network is allowed to access and 1971 GET/SET (read/change/create/delete) the objects in this MIB. 1973 It is recommended that the implementers consider the security 1974 features as provided by the SNMPv3 framework. Specifically, the use 1975 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1976 based Access Control Model RFC 2575 [RFC2575] is recommended. 1978 It is then a customer/user responsibility to ensure that the SNMP 1979 entity giving access to an instance of this MIB, is properly 1980 configured to give access to the objects only to those principals 1981 (users) that have legitimate rights to indeed GET or SET 1982 (change/create/delete) them. 1984 9. Authors' Addresses 1986 Hans Sjostrand 1987 Ericsson Telecom AB 1988 Business Unit Data Backbone and Optical Networks 1989 S-126 25 Stockholm, Sweden 1990 Phone: +46 8 719 9960 1991 Email: hans.sjostrand@ericsson.com 1993 Joachim Buerkle 1994 Nortel Networks Germany GmbH & Co. KG 1995 Hahnstrasse 37-39 1996 D-60528 Frankfurt am Main, Germany 1997 Phone: +49 69 6697 3281 1998 Email: joachim.buerkle@nortelnetworks.com 2000 Balaji Srinivasan 2001 CPlane Inc. 2002 5150 El Camino Real 2003 Suite B-31 2004 Los Altos, CA 94022 2005 Phone +1 650 938 8066 ext 103 2006 Email: balaji@cplane.com 2008 10. Full Copyright Statement 2010 Copyright (C) The Internet Society (2000). All Rights Reserved. 2012 This document and translations of it may be copied and furnished to 2013 others, and derivative works that comment on or otherwise explain it 2014 or assist in its implementation may be prepared, copied, published 2015 and distributed, in whole or in part, without restriction of any 2016 kind, provided that the above copyright notice and this paragraph are 2017 included on all such copies and derivative works. However, this 2018 document itself may not be modified in any way, such as by removing 2019 the copyright notice or references to the Internet Society or other 2020 Internet organizations, except as needed for the purpose of 2021 developing Internet standards in which case the procedures for 2022 copyrights defined in the Internet Standards process must be 2023 followed, or as required to translate it into languages other than 2024 English. 2026 The limited permissions granted above are perpetual and will not be 2027 revoked by the Internet Society or its successors or assigns. 2029 This document and the information contained herein is provided on an 2030 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2031 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2033 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2034 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2035 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.