idnits 2.17.1 draft-ietf-gsmp-mib-02.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: ---------------------------------------------------------------------------- == There are 7 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 24 longer pages, the longest (page 10) being 60 lines 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 26 instances of too long lines in the document, the longest one being 4 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 289 has weird spacing: '...ication ident...' == Line 730 has weird spacing: '... of the switc...' == Line 1886 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 (June 2000) is 8716 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2026' is defined on line 1749, but no explicit reference was found in the text == Unused Reference: 'RFC2233' is defined on line 1752, but no explicit reference was found in the text == Unused Reference: 'RFC2397' is defined on line 1758, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 1763, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 1767, 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPv3' -- Possible downref: Non-RFC (?) normative reference: ref. 'GSMPenc' Summary: 18 errors (**), 0 flaws (~~), 13 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 December 2000 Joachim Buerkle 4 Nortel Dasa 5 Balaji Srinivasan 6 Cplane 7 June 2000 9 Definitions of Managed Objects for 10 the General Switch Management Protocol (GSMP) 12 < draft-ietf-gsmp-mib-02.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 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet- 27 Drafts as reference material or to cite them other than as "work 28 in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Distribution of this document is unlimited. Please send comments 37 to the General Switch Management Protocol (gsmp) Working Group, 38 . 40 Copyright Notice 42 Copyright (C) The Internet Society (1999). All Rights Reserved. 44 Abstract 46 This memo defines a portion of the Management Information Base 47 (MIB)for use with network management protocols in the Internet 48 community. In particular, it describes managed objects for the 49 General Switch Management Protocol (GSMP). 51 Table of Contents 53 1. Introduction..................................................... 3 55 2. The SNMP Management Framework ................................... 3 57 3. Structure of the MIB............................................. 5 58 3.1 Overview..................................................... 5 59 3.2 MIB groups................................................... 5 60 3.2.1 GSMP Virtual Switch Controller group .................. 5 61 3.2.2 GSMP Virtual Switch group ............................. 6 62 3.2.3 GSMP Encapsulation groups ............................. 6 63 3.2.4 GSMP General group .................................... 7 64 3.2.5 The GSMP Notifications Group .......................... 7 66 4. GSMP MIB Definitions............................................. 9 68 5. Revision History................................................ 33 69 5.1 Design considerations ...................................... 33 70 5.1.1 Switch partitions .................................... 33 71 5.1.2 Protocol mib.......................................... 33 72 5.1.3 VSCE/VSE/VSC/VS relationships ........................ 33 73 5.1.4 Multiple controllers ................................. 33 74 5.1.5 Row index in notifications ........................... 33 75 5.2 Changes from < draft-ietf-gsmp-mib-00.txt > ................ 34 76 5.3 Changes from < draft-ietf-gsmp-mib-01.txt > ................ 34 78 6. Acknowledgments................................................. 34 80 7. References...................................................... 34 82 8. Security Considerations ........................................ 36 84 9. Authors' Addresses.............................................. 37 86 10. Full Copyright Statement ...................................... 37 87 1. Introduction 89 This memo defines a portion of the Management Information Base 90 (MIB)for use with network management protocols in the Internet 91 community. In particular, it describes managed objects for the 92 General Switch Management Protocol (GSMP). [RFC1987]. 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 95 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 96 in this document are to be interpreted as described in RFC 2119 97 [RFC2119]. 99 2. The SNMP Management Framework 101 The SNMP Management Framework presently consists of five major 102 components: 104 * An overall architecture, described in RFC 2571 [RFC2571]. 106 * Mechanisms for describing and naming objects and events for 107 the purpose of management. The first version of this Structure 108 of Management Information (SMI) is called SMIv1 and described 109 in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and 110 RFC 1215 [RFC1215]. The second version, called SMIv2, is 111 described in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] 112 and RFC 2580[RFC2580]. 114 * Message protocols for transferring management information. The 115 first version of the SNMP message protocol is called SNMPv1 116 and described in STD 15, RFC 1157 [RFC1157]. A second version 117 of the SNMP message protocol, which is not an Internet 118 standards track protocol, is called SNMPv2c and described in 119 RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version 120 of the message protocol is called SNMPv3 and described in RFC 121 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 123 * Protocol operations for accessing management information. The 124 first set of protocol operations and associated PDU formats is 125 described in STD 15, RFC 1157 [RFC1157]. A second set of 126 operations and associated PDU formats is described in 1905 127 [RFC1905]. 129 * A set of fundamental applications described in RFC 2573 130 [RFC2573] and the view-based access control mechanism 131 described RFC 2575 [RFC2575]. 133 A more detailed introduction to the current SNMP Management 134 Framework can be found in RFC 2570 [RFC2570]. 136 Managed objects are accessed via a virtual information store, 137 termed the Management Information Base or MIB. Objects in the MIB 138 are defined using the mechanisms defined in the SMI. 140 This memo specifies a MIB module that is compliant to the SMIv2. A 141 MIB conforming to the SMIv1 can be produced through the 142 appropriate translations. The resulting translated MIB must be 143 semantically equivalent, except where objects or events are 144 omitted because no translation is possible (use of Counter64). 145 Some machine readable information in SMIv2 will be converted into 146 textual descriptions in SMIv1 during the translation process. 147 However, this loss of machine readable information is not 148 considered to change the semantics of the MIB. 150 3. Structure of the MIB 152 This memo defines a portion of the Management Information Base 153 (MIB) for use with network management protocols in the Internet 154 community. In particular, it describes managed objects for the 155 General Switch Management Protocol (GSMP) as defined in [GSMPv3]. 157 3.1 Overview 159 The MIB provides objects to configure/set-up potential GSMP 160 sessions on specific switch or controllers. Two tables are used to 161 configure potential GSMP sessions, where each row in the table 162 initiates a GSMP session. To create a Virtual Switch, an entry in 163 the gsmpVseTable is created. To create a Virtual Switch 164 Controller, an entry in the gsmpVsceTable is created. 166 In order to define and configure what encapsulation the potential 167 GSMP session shall use, the encapType object in the respective 168 tables is set to either ethernet, atm or tcp/ip. If atm is used, a 169 row in the gsmpAtmEncapTable has to be created with the same 170 index. If tcp/ip is used, a row in the gsmpTcpIpEncapTable has to 171 be created with the same index. No extra encapsulation info is 172 needed if ethernet is used. 174 Another table, the gsmpSessionTable, shows the actual sessions 175 that have been, or are in the process of being established. Each 176 row represents a specific session between an Entity and a peer. 177 This table carries information about the peer, the session and 178 parameters that was negotiated by the adjacency procedures. The 179 gsmpSessionStatTable augments the gsmpSessionTable with 180 statistical information regarding the session. 182 3.2 MIB groups 184 3.2.1 GSMP Virtual Switch Controller group 186 The VSCE group is used to configure a potential GSMP session on a 187 Virtual Switch Controller. A row in the gsmpVsceTable is created 188 for each such session. If ATM or TCP/IP encapsulation is used a 189 corresponding row has to be created in these tables before the 190 session adjacency protocol is initiated. 192 The encapsulation used is specified in the encap type object. If 193 ATM or TCP/IP is used, further encap data is defined in the 194 corresponding encapsulation tables. If ethernet is used the MAC 195 address of the interface defined for the session is set by the 196 VSCE ID object. 198 The adjacency parameters are defined; such as 199 - Max supported GSMP version 200 � Time between the periodic adjacency messages 201 � VSCE Name, local port number and instance number. 202 � The partition ID for this specific partition if partitions are 203 used. 204 � The switch type defined by the manufacturer, which might be 205 predefined or configured. 207 The maximum number of controllers that are allowed for this VSE, 208 which e.g. could be used to restrict multiple controllers if set 209 to one. Also, the suggested maximum window size for unacknowledged 210 request messages could be set. 212 The notification mapping is set to specify for with events the 213 corresponding SNMP notifications are sent. 215 3.2.2 GSMP Virtual Switch group 217 The VSE group is used to configure a potential GSMP session on a 218 Virtual Switch. A row in the gsmpVseTable is created for each such 219 session. If ATM or TCP/IP encapsulation is used a corresponding 220 row has to be created in these tables before the session adjacency 221 protocol is initiated. 223 The encapsulation used is specified in the encap type object. If 224 ATM or TCP/IP is used, further encap data is defined in the 225 corresponding encapsulation tables. If ethernet is used the MAC 226 address of the interface defined for the session is set by the VSE 227 ID object. 229 The adjacency parameters are defined; such as 230 - Max supported GSMP version 231 � Time between the periodic adjacency messages 232 � VSCE Name, local port number and instance number. 233 � The partition ID for this specific partition if partitions are 234 used. 236 The resynchronisation strategy for the session is specified. Also, 237 a notification mapping is set to specify for with events the 238 corresponding SNMP notifications are sent. 240 3.2.3 GSMP Encapsulation groups 242 The ATM Encapsulation Table and the TCP/IP Encapsulation Table 243 provides a way to configure information that are encapsulation 244 specific. The encapsulation data is further specified in 245 [GSMPenc]. 247 If ATM encapsulation is used, the interface and the virtual 248 channel are specified. 250 If TCP/IP is used, the IP address and the port number are 251 specified. 253 No special config data needed if Ethernet encapsulation is used. 255 3.2.4 GSMP General group 257 The GSMP session table provides a way to define, configure and 258 monitor new GSMP session. Each row in the GSMP session table will 259 have a corresponding row in the session statistics table. 261 The session is defined by a Virtual Switch Controller Entity and 262 Virtual Switch Entity pair. 264 3.2.5 The GSMP Notifications Group 266 The GSMP Notification Group defines notifications for GSMP 267 entities. These notifications provide a mechanism for a GSMP 268 device to inform the management station of status changes. Also a 269 notification is defined for each type of GSMP events. To disable 270 or enable sending of the notifications is done by setting the 271 bitmap accordingly in the Notification mapping objects in the VSCE 272 or VSE tables. 274 The group of notifications consists of the following 275 notifications: 277 1) gsmpSessionDownTrap 279 This notification is generated when a session is terminating, to 280 report the final accounting statistics of the session. 282 2) gsmpSessionUpTrap 284 This notification is generated when a new session is established. 286 3) gsmpSendFailiureIndicationTrap 288 This notification is generated when a message with a failure 289 indication was sent. This means that this notification identifies 290 a change to the gsmpSessionStatFailiureIndication object in a row 291 of the gsmpSessionStatsTable. 293 4) gsmpReceivedFailiureIndicationTrap 294 This notification is generated when a message with a failure 295 indication received. This means that this notification identifies 296 a change to the gsmpSessionStatReceivedFailiure object in a row of 297 the gsmpSessionStatsTable. 299 5) gsmpPortUpEventTrap 301 This notification is generated when a Port Up Event occurs. This 302 means that this notification identifies a change to the 303 gsmpSessionStatPortUpEvents object in a row of the 304 gsmpSessionStatsTable. 306 6) gsmpPortDownEventTrap 308 This notification is generated when a Port Down Event occurs. 309 This means that this notification identifies a change to the 310 gsmpSessionStatPortDownEvents object in a row of the 311 gsmpSessionStatsTable. 313 7) gsmpInvalidLabelEventTrap 315 This notification is generated when an Invalid Label Event occurs. 316 This means that this notification identifies a change to the 317 gsmpSessionStatInvalidLabelEvents object in a row of the 318 gsmpSessionStatsTable. 320 8) gsmpNewPortEventTrap 322 This notification is generated when New Port Event occurs. This 323 means that this notification identifies a change to the 324 gsmpSessionStatNewPortEvents object in a row of the 325 gsmpSessionStatsTable. 327 9) gsmpDeadPortEventTrap 329 This notification is generated when a Dead Port Event occurs. 330 This means that this notification identifies a change to the 331 gsmpSessionStatDeadPortEvents object in a row of the 332 gsmpSessionStatsTable. 334 10) gsmpAdjacenyUpdateEventTrap 336 This notification is generated when an Adjacency Update Event 337 occurs. This means that this notification identifies a change to 338 the gsmpSessionStatAdjacenyUpdateEvents object in a row of the 339 gsmpSessionStatsTable. 341 4. GSMP MIB Definitions 343 GSMP-MIB DEFINITIONS ::= BEGIN 345 IMPORTS 346 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 347 Unsigned32, experimental, Integer32, Counter32,IpAddress,BITS 348 FROM SNMPv2-SMI 349 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 350 FROM SNMPv2-CONF 351 RowStatus,TruthValue,TimeStamp 352 FROM SNMPv2-TC 353 InterfaceIndex 354 FROM IF-MIB 355 AtmVcIdentifier, AtmVpIdentifier 356 FROM ATM-TC-MIB 357 ; 359 gsmpMIB MODULE-IDENTITY 360 LAST-UPDATED "0006091400Z" -- 9 June 2000, 16.00 MET DST 361 ORGANIZATION "General Switch Management Protocol (gsmp) 362 Working Group" 363 CONTACT-INFO 364 "Hans Sjostrand (hans.sjostrand@etx.ericsson.se) 365 Ericsson Telecom AB 366 Joachim Buerkle (joachim.buerkle@nortel-dasa.de) 367 Nortel Dasa Network Systems GmbH & Co KG 368 Balaji Srinivasan (balaji@cplane.com) 369 CPlane Inc." 370 DESCRIPTION 371 "This MIB contains managed object definitions for the 372 General Switch Management Protocol, GSMP, version 3" 373 ::= { experimental 9877 } -- to be assigned 375 --**************************************************************** 376 -- GSMP Textual Conventions 377 --**************************************************************** 379 gsmpObjects OBJECT IDENTIFIER ::= { gsmpMIB 1 } 380 gsmpNotifications OBJECT IDENTIFIER ::= { gsmpMIB 2 } 381 gsmpConformance OBJECT IDENTIFIER ::= { gsmpMIB 3 } 383 --**************************************************************** 384 -- GSMP Entity Objects 385 --**************************************************************** 387 -- 388 -- Virtual Switch Controller Entity table 389 -- 391 gsmpVsceTable OBJECT-TYPE 392 SYNTAX SEQUENCE OF GsmpVsceEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "This table represents the Virtual Switch Controller 397 Entity that needs to be configured before a gsmp session 398 might be started." 399 ::= { gsmpObjects 1 } 401 gsmpVsceEntry OBJECT-TYPE 402 SYNTAX GsmpVsceEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "An entry in the table showing 407 the data for a specific Virtual Switch Controller 408 Entity. " 409 INDEX { gsmpVsceId } 410 ::= { gsmpVsceTable 1 } 412 GsmpVsceEntry ::= SEQUENCE { 413 gsmpVsceId OCTET STRING, 414 gsmpVsceEncapType INTEGER, 415 gsmpVsceMaxVersion INTEGER, 416 gsmpVsceTimer Unsigned32, 417 gsmpVsceName OCTET STRING, 418 gsmpVscePort Unsigned32, 419 gsmpVsceInstance Unsigned32, 420 gsmpVscePartitionId OCTET STRING, 421 gsmpVsceDoResync TruthValue, 422 gsmpVsceNotificationMapping BITS, 423 gsmpVsceRowStatus RowStatus 424 } 426 gsmpVsceId OBJECT-TYPE 427 SYNTAX OCTET STRING (SIZE(6)) 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "The Virtual Switch Controller Entity Id is a 48- 432 bit quantity that is unique within the operational 433 context of the device. A 48-bit IEEE 802 MAC address, if 434 available, may be used for the VCSE Id." 435 ::= { gsmpVsceEntry 1 } 437 gsmpVsceEncapType OBJECT-TYPE 438 SYNTAX INTEGER { 439 ethernet(1), 440 atm(2), 441 tcpip(3) 442 } 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "The encapsulation used to for this Vsce. 448 If atm, a corresponing row in the gsmpAtmEncapTable 449 has to be defined. 450 If tcpip, a corresponing row in the gsmpTcpIpEncapTable 451 has to be defined." 452 ::= { gsmpVsceEntry 2 } 454 gsmpVsceMaxVersion OBJECT-TYPE 455 SYNTAX INTEGER { 456 version1dot1(1), 457 version2dot0(2), 458 version3(3) 459 } 460 MAX-ACCESS read-create 461 STATUS current 462 DESCRIPTION 463 "The max version number of the GSMP protocol being used in 464 this session. The version is negotiated by the 465 adjacency protocol." 466 ::= { gsmpVsceEntry 3 } 468 gsmpVsceTimer OBJECT-TYPE 469 SYNTAX Unsigned32 470 MAX-ACCESS read-create 471 STATUS current 472 DESCRIPTION 473 "The timer specifies the nominal time between 474 periodic adjacency protocol messages. It is a constant 475 for the duration of a GSMP session. The timer is 476 specified in units of 100ms." 477 ::= { gsmpVsceEntry 4 } 479 gsmpVsceName OBJECT-TYPE 480 SYNTAX OCTET STRING 481 MAX-ACCESS read-create 482 STATUS current 483 DESCRIPTION 484 "The name of the VSCE as advertised in the adjacency 485 message. The most first three octets must be an 486 Organisationally Unique Identifier (OUI) that identifies 487 the manufacturer of the VSCE." 488 ::= {gsmpVsceEntry 5} 490 gsmpVscePort OBJECT-TYPE 491 SYNTAX Unsigned32 492 MAX-ACCESS read-create 493 STATUS current 494 DESCRIPTION 495 "The local port number for the Virtual Switch Controller 496 Entity." 497 ::= { gsmpVsceEntry 6 } 499 gsmpVsceInstance OBJECT-TYPE 500 SYNTAX Unsigned32 501 MAX-ACCESS read-create 502 STATUS current 503 DESCRIPTION 504 "The instance number for the Virtual Switch Controller 505 Entity." 506 ::= { gsmpVsceEntry 7 } 508 gsmpVscePartitionId OBJECT-TYPE 509 SYNTAX OCTET STRING (SIZE(1)) 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "The Id for the specific switch partition that this Vsce 514 is concerned with. The format of the Partition ID is not 515 defined in GSMP. If desired, the Partition ID can be 516 divided into multiple sub-identifiers within a single 517 partition." 518 ::= { gsmpVsceEntry 8 } 520 gsmpVsceDoResync OBJECT-TYPE 521 SYNTAX TruthValue 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "In case of loss of syncronisation, should the controller 526 resyncronice or should it reset. If this object is set 527 to true than the Vsce should resync with PFLAG=2." 528 ::= { gsmpVsceEntry 9 } 530 gsmpVsceNotificationMapping OBJECT-TYPE 531 SYNTAX BITS { 532 sessionDown(0), 533 sessionUp(1), 534 sendFailiureIndication(2), 535 receivedFailiureIndication(3), 536 portUpEvent(4), 537 portDownEvent(5), 538 invalidLabelEvent(6), 539 newPortEvent(7), 540 deadPortEvent(8), 541 adjacencyUpdateEvent(9) 542 } 543 MAX-ACCESS read-create 544 STATUS current 545 DESCRIPTION 546 "This bitmap defines wheither a corresponding SNMP 547 notification should be send if an GSMP event is received 548 by the VSCE. If the bit is set to 1 a notfication should 549 be send." 550 ::= { gsmpVsceEntry 10 } 552 gsmpVsceRowStatus OBJECT-TYPE 553 SYNTAX RowStatus 554 MAX-ACCESS read-create 555 STATUS current 556 DESCRIPTION 557 "An object that allows entries in this table to 558 be created and deleted using the 559 RowStatus convention." 560 ::= { gsmpVsceEntry 11 } 562 -- 563 -- Virtual Switch Entity table 564 -- 566 gsmpVseTable OBJECT-TYPE 567 SYNTAX SEQUENCE OF GsmpVseEntry 568 MAX-ACCESS not-accessible 569 STATUS current 570 DESCRIPTION 571 "This table represents the Virtual Switch 572 Entity that needs to be configured before a gsmp session 573 might be started." 574 ::= { gsmpObjects 2 } 576 gsmpVseEntry OBJECT-TYPE 577 SYNTAX GsmpVseEntry 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "An entry in the table showing 582 the data for a specific Virtual Switch Controller 583 Entity. " 584 INDEX { gsmpVseId } 585 ::= { gsmpVseTable 1 } 587 GsmpVseEntry ::= SEQUENCE { 588 gsmpVseId OCTET STRING, 589 gsmpVseEncapType INTEGER, 590 gsmpVseMaxVersion INTEGER, 591 gsmpVseTimer Unsigned32, 592 gsmpVseName OCTET STRING, 593 gsmpVsePort Unsigned32, 594 gsmpVseInstance Unsigned32, 595 gsmpVsePartitionId OCTET STRING, 596 gsmpVseAllowMultContr Unsigned32, 597 gsmpVseNotificationMapping BITS, 598 gsmpVseSwitchType OCTET STRING, 599 gsmpVseWindowSize Unsigned32, 600 gsmpVseRowStatus RowStatus 601 } 603 gsmpVseId OBJECT-TYPE 604 SYNTAX OCTET STRING (SIZE(6)) 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "The Virtual Switch Controller Entity Id is a 48- 609 bit quantity that is unique within the operational 610 context of the device. A 48-bit IEEE 802 MAC address, if 611 available, may be used for the VSE Id." 612 ::= { gsmpVseEntry 1 } 614 gsmpVseEncapType OBJECT-TYPE 615 SYNTAX INTEGER { 616 ethernet(1), 617 atm(2), 618 tcpip(3) 619 } 620 MAX-ACCESS read-create 621 STATUS current 622 DESCRIPTION 623 "The encapsulation used to for this Vse. 624 If atm, a corresponing row in the gsmpAtmEncapTable 625 has to be defined. 626 If tcpip, a corresponing row in the gsmpTcpIpEncapTable 627 has to be defined." 628 ::= { gsmpVseEntry 2 } 630 gsmpVseMaxVersion OBJECT-TYPE 631 SYNTAX INTEGER { 632 version1dot1(1), 633 version2dot0(2), 634 version3(3) 635 } 636 MAX-ACCESS read-create 637 STATUS current 638 DESCRIPTION 639 "The max version number of the GSMP protocol being 640 supported by this VSE. The version is negotiated by the 641 adjacency protocol." 642 ::= { gsmpVseEntry 3 } 644 gsmpVseTimer OBJECT-TYPE 645 SYNTAX Unsigned32 646 MAX-ACCESS read-create 647 STATUS current 648 DESCRIPTION 649 "The timer specifies the nominal time between 650 periodic adjacency protocol messages. It is a constant 651 for the duration of a GSMP session. The timer is 652 specified in units of 100ms." 653 ::= { gsmpVseEntry 4 } 655 gsmpVseName OBJECT-TYPE 656 SYNTAX OCTET STRING 657 MAX-ACCESS read-create 658 STATUS current 659 DESCRIPTION 660 "The name of the Vse. The first three octets must be an 661 Organisationally Unique Identifier (OUI) that identifies 662 the manufacturer of the Vse." 663 ::= {gsmpVseEntry 5} 665 gsmpVsePort OBJECT-TYPE 666 SYNTAX Unsigned32 667 MAX-ACCESS read-create 668 STATUS current 669 DESCRIPTION 670 "The local port number for the Virtual Switch 671 Entity." 672 ::= { gsmpVseEntry 6 } 674 gsmpVseInstance OBJECT-TYPE 675 SYNTAX Unsigned32 676 MAX-ACCESS read-create 677 STATUS current 678 DESCRIPTION 679 "The instance number for the Virtual Switch 680 Entity." 681 ::= { gsmpVseEntry 7 } 683 gsmpVsePartitionId OBJECT-TYPE 684 SYNTAX OCTET STRING (SIZE(1)) 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "The Id for this specific switch partition that the Vse 689 is represents. The format of the Partition ID is not 690 defined in GSMP. " 691 ::= { gsmpVseEntry 8 } 693 gsmpVseAllowMultContr OBJECT-TYPE 694 SYNTAX Unsigned32(0..255) 695 MAX-ACCESS read-create 696 STATUS current 697 DESCRIPTION 698 "This object specifies the maximum number of controllers 699 are alloed to control this VSE." 700 ::= { gsmpVseEntry 9 } 702 gsmpVseNotificationMapping OBJECT-TYPE 703 SYNTAX BITS { 704 sessionDown(0), 705 sessionUp(1), 706 sendFailiureIndication(2), 707 receivedFailiureIndication(3), 708 portUpEvent(4), 709 portDownEvent(5), 710 invalidLabelEvent(6), 711 newPortEvent(7), 712 deadPortEvent(8), 713 adjacencyUpdateEvent(9) 714 } 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This bitmap defines wheither a corresponding SNMP 719 notification should be send if an GSMP event is send 720 by the VSE. If the bit is set to 1 a notfication should 721 be send." 722 ::= { gsmpVseEntry 10 } 724 gsmpVseSwitchType OBJECT-TYPE 725 SYNTAX OCTET STRING (SIZE(2)) 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "A 16-bit field allocated by the manufacturer 730 of the switch. The Switch Type 731 identifies the product. When the Switch Type is combined 732 with the OUI from the Switch Name the product is 733 uniquely identified. " 734 ::= { gsmpVseEntry 11 } 736 gsmpVseWindowSize OBJECT-TYPE 737 SYNTAX Unsigned32(1..65535) 738 MAX-ACCESS read-create 739 STATUS current 740 DESCRIPTION 741 "The maximum number of unacknowledged request messages 742 that may be transmitted by the controller without the 743 possibility of loss. This field is used to prevent 744 request messages being lost in the switch because of 745 overflow in the receive buffer. The field is a hint to 746 the controller." 747 ::= { gsmpVseEntry 12 } 749 gsmpVseRowStatus OBJECT-TYPE 750 SYNTAX RowStatus 751 MAX-ACCESS read-create 752 STATUS current 753 DESCRIPTION 754 "An object that allows entries in this table to 755 be created and deleted using the 756 RowStatus convention." 757 ::= { gsmpVseEntry 13 } 759 --**************************************************************** 760 -- GSMP Encapsulation Objects 761 --**************************************************************** 763 -- 764 -- GSMP ATM Encapsulation Table 765 -- 767 gsmpAtmEncapTable OBJECT-TYPE 768 SYNTAX SEQUENCE OF GsmpAtmEncapEntry 769 MAX-ACCESS not-accessible 770 STATUS current 771 DESCRIPTION 772 "This table contains the atm encapsulation data 773 for the VSCE or VSE that uses atm as encapsulation." 774 ::= { gsmpObjects 3 } 776 gsmpAtmEncapEntry OBJECT-TYPE 777 SYNTAX GsmpAtmEncapEntry 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "An entry in the table showing 782 the encapsulation data for a 783 specific VSCE or VSE." 784 INDEX { gsmpAtmEncapEntityId } 785 ::= { gsmpAtmEncapTable 1 } 787 GsmpAtmEncapEntry ::= SEQUENCE { 788 gsmpAtmEncapEntityId OCTET STRING, 789 gsmpAtmEncapIfIndex InterfaceIndex, 790 gsmpAtmEncapVpi AtmVpIdentifier, 791 gsmpAtmEncapVci AtmVcIdentifier 792 } 794 gsmpAtmEncapEntityId OBJECT-TYPE 795 SYNTAX OCTET STRING (SIZE(6)) 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "The VSCE or VSE Id is a 48- 800 bit quantity that is unique within the operational 801 context of the device. A 48-bit IEEE 802 MAC address, if 802 available, may be used for the entity Id." 803 ::= { gsmpAtmEncapEntry 1 } 805 gsmpAtmEncapIfIndex OBJECT-TYPE 806 SYNTAX InterfaceIndex 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "The interface index for the virtual channel over which 811 the GSMP session is established over, i.e the GSMP control 812 channel for LLC/SNAP encapsulated GSMP messages on an 813 ATM data link layer" 814 ::= { gsmpAtmEncapEntry 2 } 816 gsmpAtmEncapVpi OBJECT-TYPE 817 SYNTAX AtmVpIdentifier 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 " The VPI value for the virtual channel over which the 822 GSMP session is established over, i.e the GSMP control 823 channel for LLC/SNAP encapsulated GSMP messages on an 824 ATM data link layer" 825 DEFVAL { 0 } 826 ::= { gsmpAtmEncapEntry 3 } 828 gsmpAtmEncapVci OBJECT-TYPE 829 SYNTAX AtmVcIdentifier 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 " The VCI value for the virtual channel over which the 834 GSMP session is established over, i.e the GSMP control 835 channel for LLC/SNAP encapsulated GSMP messages on an 836 ATM data link layer" 837 DEFVAL { 15 } 838 ::= { gsmpAtmEncapEntry 4 } 840 -- 841 -- GSMP TCP/IP Encapsulation Table 842 -- 844 gsmpTcpIpEncapTable OBJECT-TYPE 845 SYNTAX SEQUENCE OF GsmpTcpIpEncapEntry 846 MAX-ACCESS not-accessible 847 STATUS current 848 DESCRIPTION 849 "This table contains the atm encapsulation data 850 for the VSCE or VSE that uses atmTCP/IP as 851 encapsulation." 852 ::= { gsmpObjects 4 } 854 gsmpTcpIpEncapEntry OBJECT-TYPE 855 SYNTAX GsmpTcpIpEncapEntry 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "An entry in the table showing 860 the encapsulation data for a 861 specific VSCE or VSE." 862 INDEX { gsmpTcpIpEncapEntityId } 863 ::= { gsmpTcpIpEncapTable 1 } 865 GsmpTcpIpEncapEntry ::= SEQUENCE { 866 gsmpTcpIpEncapEntityId OCTET STRING, 867 gsmpTcpIpEncapAddress IpAddress, 868 gsmpTcpIpPortNumber Unsigned32 869 } 871 gsmpTcpIpEncapEntityId OBJECT-TYPE 872 SYNTAX OCTET STRING (SIZE(6)) 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "The VSCE or VSE Id is a 48- 877 bit quantity that is unique within the operational 878 context of the device. A 48-bit IEEE 802 MAC address, if 879 available, may be used for the entity Id." 881 ::= { gsmpTcpIpEncapEntry 1 } 883 gsmpTcpIpEncapAddress OBJECT-TYPE 884 SYNTAX IpAddress 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "The IPv4 address of the GSMP session peer." 889 ::= { gsmpTcpIpEncapEntry 2 } 891 gsmpTcpIpPortNumber OBJECT-TYPE 892 SYNTAX Unsigned32 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "The TCP port number used for the TCP session 897 to the GSMP peer. The defaut value of this object 898 is the well know GSMP port number. " 899 ::= { gsmpTcpIpEncapEntry 3 } 901 --**************************************************************** 902 -- GSMP Session Objects 903 --**************************************************************** 905 -- 906 -- GSMP Session table 907 -- 909 gsmpSessionTable OBJECT-TYPE 910 SYNTAX SEQUENCE OF GsmpSessionEntry 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "This table represents the sessions between 915 VSCE and VSE pairs. " 916 ::= { gsmpObjects 5 } 918 gsmpSessionEntry OBJECT-TYPE 919 SYNTAX GsmpSessionEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "An entry in the table showing 924 the data for a specific VSCE and 925 VSE pair." 926 INDEX { gsmpSessionThisSideId, gsmpSessionFarSideId } 927 ::= { gsmpSessionTable 1 } 929 GsmpSessionEntry ::= SEQUENCE { 930 gsmpSessionThisSideId OCTET STRING, 931 gsmpSessionFarSideId OCTET STRING, 932 gsmpSessionVersion INTEGER, 933 gsmpSessionTimer Integer32, 934 gsmpSessionState INTEGER, 935 gsmpSessionAdjacencyCount Unsigned32, 936 gsmpSessionFarSideName OCTET STRING, 937 gsmpSessionFarSidePort Unsigned32, 938 gsmpSessionFarSideInstance Unsigned32, 939 gsmpSessionLastFailiureCode Unsigned32, 940 gsmpSessionDiscontinuityTime TimeStamp 941 } 943 gsmpSessionThisSideId OBJECT-TYPE 944 SYNTAX OCTET STRING (SIZE(6)) 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "This side ID uniqly identifies the entity that this 949 session relates to within the the operational 950 context of the device. " 951 ::= { gsmpSessionEntry 1 } 953 gsmpSessionFarSideId OBJECT-TYPE 954 SYNTAX OCTET STRING (SIZE(6)) 955 MAX-ACCESS not-accessible 956 STATUS current 957 DESCRIPTION 958 "The Far side ID uniqly identifies the entity that this 959 session is established against. " 960 ::= { gsmpSessionEntry 2 } 962 gsmpSessionVersion OBJECT-TYPE 963 SYNTAX INTEGER { 964 version1dot1(1), 965 version2dot0(2), 966 version3(3) 967 } 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The version number of the GSMP protocol being used in 972 this session. The version is the result of the 973 negotiation by the adjacency protocol." 974 ::= { gsmpSessionEntry 3 } 976 gsmpSessionTimer OBJECT-TYPE 977 SYNTAX Integer32 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "The timer specifies the time remaining until the 982 adjecency timer expires. The object could take negative 983 values since if no valid GSMP messages are 984 received in any period of time in excess of three times 985 the value of the Timer negotiated by the adjacency protocol 986 loss of synchronisation may be declared. The timer is 987 specified in units of 100ms." 988 ::= { gsmpSessionEntry 4 } 990 gsmpSessionState OBJECT-TYPE 991 SYNTAX INTEGER { 992 null(1), 993 synsent(2), 994 synrcvd(3), 995 estab(4) 996 } 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The state the session currently is in. " 1001 ::= { gsmpSessionEntry 5 } 1003 gsmpSessionAdjacencyCount OBJECT-TYPE 1004 SYNTAX Unsigned32(1..255) 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "This object specifies the current number of adjecensies 1009 that are established with the controller and partition 1010 that is used for this session." 1011 ::= { gsmpSessionEntry 6 } 1013 gsmpSessionFarSideName OBJECT-TYPE 1014 SYNTAX OCTET STRING 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "The name of the far side as advertised in the adjacency 1019 message." 1020 ::= {gsmpSessionEntry 7} 1022 gsmpSessionFarSidePort OBJECT-TYPE 1023 SYNTAX Unsigned32 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "The local port number of the link across which the message 1028 is being sent." 1029 ::= { gsmpSessionEntry 8 } 1031 gsmpSessionFarSideInstance OBJECT-TYPE 1032 SYNTAX Unsigned32 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "The instance number used for the link during this session. 1037 Zero is not a valid instance number." 1038 ::= { gsmpSessionEntry 9 } 1040 gsmpSessionLastFailiureCode OBJECT-TYPE 1041 SYNTAX Unsigned32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "This is the last failiure code that was received over 1046 this session. If no failiure code has been received, the 1047 value is zero." 1048 ::= { gsmpSessionEntry 10 } 1050 gsmpSessionDiscontinuityTime OBJECT-TYPE 1051 SYNTAX TimeStamp 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "The value of sysUpTime on the most recent occasion at 1056 which any one or more of this session's counters 1057 suffered a discontinuity. The relevant counters are 1058 the specific instances associated with this session 1059 of any Counter32 or Counter64 object contained in the 1060 gsmpSessionStatsTable. If no such discontinuities have 1061 occurred since then this object contains a zero 1062 value. 1063 Also, an NMS can distinguish when a session 1064 between a given Entity and the far side goes away and 1065 then is 're-established'. This value would change and 1066 thus indicate to the NMS that this is a 1067 different session." 1068 ::= { gsmpSessionEntry 11 } 1070 -- 1071 -- GSMP Session stats table 1072 -- 1074 gsmpSessionStatTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF GsmpSessionStatEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "This table contains the statistics collected for 1080 the different sessions. " 1081 ::= { gsmpObjects 6 } 1083 gsmpSessionStatEntry OBJECT-TYPE 1084 SYNTAX GsmpSessionStatEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "An entry in the table contains 1089 statistics data for a specific session." 1090 AUGMENTS { gsmpSessionEntry } 1091 ::= { gsmpSessionStatTable 1 } 1093 GsmpSessionStatEntry ::= SEQUENCE { 1094 gsmpSessionStatUptime Counter32, 1095 gsmpSessionStatSendmessages Counter32, 1096 gsmpSessionStatFailiureIndication Counter32, 1097 gsmpSessionStatReceivedmessages Counter32, 1098 gsmpSessionStatReceivedFailiure Counter32, 1099 gsmpSessionStatPortUpEvents Counter32, 1100 gsmpSessionStatPortDownEvents Counter32, 1101 gsmpSessionStatInvalidLabelEvents Counter32, 1102 gsmpSessionStatNewPortEvents Counter32, 1103 gsmpSessionStatDeadPortEvents Counter32, 1104 gsmpSessionStatAdjacenyUpdateEvents Counter32 1105 } 1107 gsmpSessionStatUptime OBJECT-TYPE 1108 SYNTAX Counter32 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "The time in seconds that the session has been in 1113 established state." 1114 ::= { gsmpSessionStatEntry 1 } 1116 gsmpSessionStatSendmessages OBJECT-TYPE 1117 SYNTAX Counter32 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "The number of messages that has been sent in this 1122 session." 1123 ::= { gsmpSessionStatEntry 2 } 1125 gsmpSessionStatFailiureIndication OBJECT-TYPE 1126 SYNTAX Counter32 1127 MAX-ACCESS read-only 1128 STATUS current 1129 DESCRIPTION 1130 "The number of messages that has been sent with a 1131 failiure indication in this session." 1132 ::= { gsmpSessionStatEntry 3 } 1134 gsmpSessionStatReceivedmessages OBJECT-TYPE 1135 SYNTAX Counter32 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The number of messages that has been received in 1140 this session." 1141 ::= { gsmpSessionStatEntry 4 } 1143 gsmpSessionStatReceivedFailiure OBJECT-TYPE 1144 SYNTAX Counter32 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "The number of messages that has been received in 1149 this session with a failiure indication." 1150 ::= { gsmpSessionStatEntry 5 } 1152 gsmpSessionStatPortUpEvents OBJECT-TYPE 1153 SYNTAX Counter32 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "The number of Port Up events that has been send or 1158 received on this session." 1159 ::= { gsmpSessionStatEntry 6 } 1161 gsmpSessionStatPortDownEvents OBJECT-TYPE 1162 SYNTAX Counter32 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "The number of Port Down events that has been send or 1167 received on this session." 1168 ::= { gsmpSessionStatEntry 7 } 1170 gsmpSessionStatInvalidLabelEvents OBJECT-TYPE 1171 SYNTAX Counter32 1172 MAX-ACCESS read-only 1173 STATUS current 1174 DESCRIPTION 1175 "The number of Invalid label events that has been send or 1176 received on this session." 1177 ::= { gsmpSessionStatEntry 8 } 1179 gsmpSessionStatNewPortEvents OBJECT-TYPE 1180 SYNTAX Counter32 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "The number of New Port events that has been send or 1185 received on this session." 1186 ::= { gsmpSessionStatEntry 9 } 1188 gsmpSessionStatDeadPortEvents OBJECT-TYPE 1189 SYNTAX Counter32 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "The number of Dead Port events that has been send or 1194 received on this session." 1195 ::= { gsmpSessionStatEntry 10 } 1197 gsmpSessionStatAdjacenyUpdateEvents OBJECT-TYPE 1198 SYNTAX Counter32 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "The number of Adjaceny Update events that has been send or 1203 received on this session." 1204 ::= { gsmpSessionStatEntry 11 } 1206 -- ******************************************************************* 1207 -- GSMP Notifications 1208 -- ******************************************************************* 1210 gsmpNotificationsPrefix OBJECT IDENTIFIER ::= { gsmpNotifications 0 } 1211 gsmpNotificationsObjects OBJECT IDENTIFIER ::= { gsmpNotifications 1 } 1213 -- 1214 -- Notification objects 1215 -- 1217 gsmpEventPort OBJECT-TYPE 1218 SYNTAX Unsigned32 1219 MAX-ACCESS accessible-for-notify 1220 STATUS current 1221 DESCRIPTION 1222 "This object specifies the Port Number that is 1223 carried in this event." 1224 ::= { gsmpNotificationsObjects 1 } 1226 gsmpEventPortSessionNumber OBJECT-TYPE 1227 SYNTAX Unsigned32 1228 MAX-ACCESS accessible-for-notify 1229 STATUS current 1230 DESCRIPTION 1231 "This object specifies the Port Session Number that is 1232 carried in this event." 1233 ::= { gsmpNotificationsObjects 2 } 1235 gsmpEventSequenceNumber OBJECT-TYPE 1236 SYNTAX Unsigned32 1237 MAX-ACCESS accessible-for-notify 1238 STATUS current 1239 DESCRIPTION 1240 "This object specifies the Event Sequence Number that is 1241 carried in this event." 1242 ::= { gsmpNotificationsObjects 3 } 1244 gsmpEventLabel OBJECT-TYPE 1245 SYNTAX Unsigned32 1246 MAX-ACCESS accessible-for-notify 1247 STATUS current 1248 DESCRIPTION 1249 "This object specifies the Label that is 1250 carried in this event." 1251 ::= { gsmpNotificationsObjects 4 } 1253 -- 1254 -- Notifications 1255 -- 1257 gsmpSessionDownTrap NOTIFICATION-TYPE 1258 OBJECTS { 1259 gsmpSessionThisSideId, 1260 gsmpSessionFarSideId, 1261 gsmpSessionStatUptime, 1262 gsmpSessionStatSendmessages, 1263 gsmpSessionStatFailiureIndication, 1264 gsmpSessionStatReceivedmessages, 1265 gsmpSessionStatReceivedFailiure, 1266 gsmpSessionStatPortUpEvents, 1267 gsmpSessionStatPortDownEvents, 1268 gsmpSessionStatInvalidLabelEvents, 1269 gsmpSessionStatNewPortEvents, 1270 gsmpSessionStatDeadPortEvents, 1271 gsmpSessionStatAdjacenyUpdateEvents 1272 } 1273 STATUS current 1274 DESCRIPTION 1275 "When it has been enabled, this notification is generated 1276 whenever an session is taken down, regardless of whether 1277 the session went down normally or abnormally. 1278 Its purpose is to allow a management application 1279 (primarily an accounting application) that is 1280 monitoring the session statistics to receive the final values 1281 of these counts, so that the application can properly account 1282 for the amounts the counts were incremented since the last 1283 time the application polled them. The gsmpSessionStatUptime 1284 object provides the total amount of time that the session was 1285 active. 1287 This notification is not a substitute for polling the session 1288 statistic counts. In particular, the count values reported in 1289 this 1290 notification cannot be assumed to be the complete totals for 1291 the life of the session, since they may have wrapped while the 1292 session was up. 1294 The session to which the objects in this notification apply is 1295 identified by the session gsmpSessionThisSideId, 1296 gsmpSessionFarSideId objects. 1297 An instance of this notification will contain exactly one 1298 instance 1299 of each of its objects, and these objects will all belong to 1300 the same conceptual row of the gsmpSessionTable." 1301 ::= { gsmpNotificationsPrefix 1 } 1303 gsmpSessionUpTrap NOTIFICATION-TYPE 1304 OBJECTS { 1305 gsmpSessionThisSideId, 1306 gsmpSessionFarSideId, 1307 gsmpSessionState 1308 } 1310 STATUS current 1311 DESCRIPTION 1312 "When it has been enabled, this notification is generated 1313 when new session is establised. 1315 The new session is identified by the session 1316 gsmpSessionThisSideId, gsmpSessionFarSideId objects." 1317 ::= { gsmpNotificationsPrefix 2 } 1319 gsmpSendFailiureIndicationTrap NOTIFICATION-TYPE 1320 OBJECTS { 1321 gsmpSessionThisSideId, 1322 gsmpSessionFarSideId, 1323 gsmpSessionLastFailiureCode, 1324 gsmpSessionStatFailiureIndication 1325 } 1326 STATUS current 1327 DESCRIPTION 1328 "When it has been enabled, this notification is generated 1329 when a message with a failure indication was sent. 1331 The notification indicates a change in the value of 1332 gsmpSessionStatFailiureIndication. The 1333 gsmpSessionLastFailiureCode contains the failiure reason." 1334 ::= { gsmpNotificationsPrefix 3 } 1336 gsmpReceivedFailiureIndicationTrap NOTIFICATION-TYPE 1337 OBJECTS { 1338 gsmpSessionThisSideId, 1339 gsmpSessionFarSideId, 1340 gsmpSessionLastFailiureCode, 1341 gsmpSessionStatReceivedFailiure 1342 } 1343 STATUS current 1344 DESCRIPTION 1345 "When it has been enabled, this notification is generated 1346 when a message with a failure indication received. 1348 The notification indicates a change in the value of 1349 gsmpSessionStatReceivedFailiure. The 1350 gsmpSessionLastFailiureCode contains the failiure reason." 1351 ::= { gsmpNotificationsPrefix 4 } 1353 gsmpPortUpEventTrap NOTIFICATION-TYPE 1354 OBJECTS { 1355 gsmpSessionThisSideId, 1356 gsmpSessionFarSideId, 1357 gsmpSessionStatPortUpEvents, 1358 gsmpEventPort, 1359 gsmpEventPortSessionNumber, 1360 gsmpEventSequenceNumber 1361 } 1362 STATUS current 1363 DESCRIPTION 1364 "When it has been enabled, this notification is generated 1365 when a Port Up Event occurs. 1367 The notification indicates a change in the value of 1368 gsmpSessionStatPortUpEvents." 1369 ::= { gsmpNotificationsPrefix 5 } 1371 gsmpPortDownEventTrap NOTIFICATION-TYPE 1372 OBJECTS { 1373 gsmpSessionThisSideId, 1374 gsmpSessionFarSideId, 1375 gsmpSessionStatPortDownEvents, 1376 gsmpEventPort, 1377 gsmpEventPortSessionNumber, 1378 gsmpEventSequenceNumber 1379 } 1380 STATUS current 1381 DESCRIPTION 1382 "When it has been enabled, this notification is generated 1383 when a Port Down Event occurs. 1385 The notification indicates a change in the value of 1386 gsmpSessionStatPortDownEvents." 1387 ::= { gsmpNotificationsPrefix 6 } 1389 gsmpInvalidLabelEventTrap NOTIFICATION-TYPE 1390 OBJECTS { 1391 gsmpSessionThisSideId, 1392 gsmpSessionFarSideId, 1393 gsmpSessionStatInvalidLabelEvents, 1394 gsmpEventPort, 1395 gsmpEventLabel, 1396 gsmpEventSequenceNumber 1397 } 1398 STATUS current 1399 DESCRIPTION 1400 "When it has been enabled, this notification is generated 1401 when an Invalid Label Event occurs. 1403 The notification indicates a change in the value of 1404 gsmpSessionStatInvalidLabelEvents." 1405 ::= { gsmpNotificationsPrefix 7 } 1407 gsmpNewPortEventTrap NOTIFICATION-TYPE 1408 OBJECTS { 1409 gsmpSessionThisSideId, 1410 gsmpSessionFarSideId, 1411 gsmpSessionStatNewPortEvents, 1412 gsmpEventPort, 1413 gsmpEventPortSessionNumber, 1414 gsmpEventSequenceNumber 1415 } 1416 STATUS current 1417 DESCRIPTION 1418 "When it has been enabled, this notification is generated 1419 when a New Port Event occurs. 1421 The notification indicates a change in the value of 1422 gsmpSessionStatNewPortEvents." 1423 ::= { gsmpNotificationsPrefix 8 } 1425 gsmpDeadPortEventTrap NOTIFICATION-TYPE 1426 OBJECTS { 1427 gsmpSessionThisSideId, 1428 gsmpSessionFarSideId, 1429 gsmpSessionStatDeadPortEvents, 1430 gsmpEventPort, 1431 gsmpEventPortSessionNumber, 1432 gsmpEventSequenceNumber 1433 } 1434 STATUS current 1435 DESCRIPTION 1436 "When it has been enabled, this notification is generated 1437 when a Dead Port Event occurs. 1439 The notification indicates a change in the value of 1440 gsmpSessionStatDeadPortEvents." 1441 ::= { gsmpNotificationsPrefix 9 } 1443 gsmpAdjacenyUpdateEventTrap NOTIFICATION-TYPE 1444 OBJECTS { 1445 gsmpSessionThisSideId, 1446 gsmpSessionFarSideId, 1447 gsmpSessionAdjacencyCount, 1448 gsmpSessionStatAdjacenyUpdateEvents, 1449 gsmpEventSequenceNumber 1450 } 1451 STATUS current 1452 DESCRIPTION 1453 "When it has been enabled, this notification is generated 1454 when an Adjancy Update Event occurs. 1456 The gsmpSessionAdjacencyCount contains the new value of the 1457 number of adjecensies 1458 that are established with the controller and partition 1459 that is used for this session. 1461 The notification indicates a change in the value of 1462 gsmpSessionStatAdjacenyUpdateEvents." 1463 ::= { gsmpNotificationsPrefix 10 } 1465 --****************************************************************** 1466 -- GSMP Compliance 1467 --****************************************************************** 1469 gsmpGroups OBJECT IDENTIFIER ::= { gsmpConformance 1 } 1470 gsmpCompliances OBJECT IDENTIFIER ::= { gsmpConformance 2 } 1471 gsmpModuleCompliance MODULE-COMPLIANCE 1472 STATUS current 1473 DESCRIPTION 1474 "The compliance statement for agents that support 1475 the GSMP MIB." 1476 MODULE -- this module 1477 MANDATORY-GROUPS { gsmpGeneralGroup 1478 } 1479 GROUP gsmpVsceGroup 1480 DESCRIPTION 1481 "This group is mandatory for all Virtual Switch 1482 Controllers" 1484 GROUP gsmpVseGroup 1485 DESCRIPTION 1486 "This group is mandatory for all Virtual Switches" 1488 GROUP gsmpAtmEncapGroup 1489 DESCRIPTION 1490 "This group must be supported if ATM is used for GSMP 1491 encapsulation. " 1493 GROUP gsmpTcpIpEncapGroup 1494 DESCRIPTION 1495 "This group must be supported if TCP/IP is used for GSMP 1496 encapsulation. " 1498 GROUP gsmpNotificationObjectsGroup 1499 DESCRIPTION 1500 "This group must be supported if notifications 1501 are supported. " 1503 GROUP gsmpNotificationsGroup 1504 DESCRIPTION 1505 "This group must be supported if notifications 1506 are supported. " 1508 ::= { gsmpCompliances 1 } 1510 -- units of conformance 1512 gsmpGeneralGroup OBJECT-GROUP 1513 OBJECTS { 1514 gsmpSessionVersion, 1515 gsmpSessionTimer, 1516 gsmpSessionState, 1517 gsmpSessionAdjacencyCount, 1518 gsmpSessionFarSideName, 1519 gsmpSessionFarSidePort, 1520 gsmpSessionFarSideInstance, 1521 gsmpSessionLastFailiureCode, 1522 gsmpSessionDiscontinuityTime, 1523 gsmpSessionStatUptime, 1524 gsmpSessionStatSendmessages, 1525 gsmpSessionStatFailiureIndication, 1526 gsmpSessionStatReceivedmessages, 1527 gsmpSessionStatReceivedFailiure, 1528 gsmpSessionStatPortUpEvents, 1529 gsmpSessionStatPortDownEvents, 1530 gsmpSessionStatInvalidLabelEvents, 1531 gsmpSessionStatNewPortEvents, 1532 gsmpSessionStatDeadPortEvents, 1533 gsmpSessionStatAdjacenyUpdateEvents 1534 } 1535 STATUS current 1536 DESCRIPTION 1537 "Objects that apply to all GSMP implementations." 1538 ::= { gsmpGroups 1 } 1540 gsmpVsceGroup OBJECT-GROUP 1541 OBJECTS { 1542 gsmpVsceEncapType, 1543 gsmpVsceMaxVersion, 1544 gsmpVsceTimer, 1545 gsmpVsceName, 1546 gsmpVscePort, 1547 gsmpVsceInstance, 1548 gsmpVscePartitionId, 1549 gsmpVsceDoResync, 1550 gsmpVsceNotificationMapping, 1551 gsmpVsceRowStatus 1552 } 1553 STATUS current 1554 DESCRIPTION 1555 "Objects that apply GSMP implementations of 1556 Virtual Switch Controllers." 1557 ::= { gsmpGroups 2 } 1559 gsmpVseGroup OBJECT-GROUP 1560 OBJECTS { 1561 gsmpVseEncapType, 1562 gsmpVseMaxVersion, 1563 gsmpVseTimer, 1564 gsmpVseName, 1565 gsmpVsePort, 1566 gsmpVseInstance, 1567 gsmpVsePartitionId, 1568 gsmpVseAllowMultContr, 1569 gsmpVseNotificationMapping, 1570 gsmpVseSwitchType, 1571 gsmpVseWindowSize, 1572 gsmpVseRowStatus 1573 } 1574 STATUS current 1575 DESCRIPTION 1576 "Objects that apply GSMP implementations of 1577 Virtual Switches." 1579 ::= { gsmpGroups 3 } 1581 gsmpAtmEncapGroup OBJECT-GROUP 1582 OBJECTS { 1583 gsmpAtmEncapIfIndex, 1584 gsmpAtmEncapVpi, 1585 gsmpAtmEncapVci 1586 } 1587 STATUS current 1588 DESCRIPTION 1589 "Objects that apply to GSMP implementations that 1590 supports ATM for GSMP encapsulation." 1591 ::= { gsmpGroups 4 } 1593 gsmpTcpIpEncapGroup OBJECT-GROUP 1594 OBJECTS { 1595 gsmpTcpIpEncapAddress, 1596 gsmpTcpIpPortNumber 1597 } 1598 STATUS current 1599 DESCRIPTION 1600 "Objects that apply to GSMP implementations that 1601 supports TCP/IP for GSMP encapsulation." 1602 ::= { gsmpGroups 5 } 1604 gsmpNotificationObjectsGroup OBJECT-GROUP 1605 OBJECTS { 1606 gsmpEventPort, 1607 gsmpEventPortSessionNumber, 1608 gsmpEventSequenceNumber, 1609 gsmpEventLabel 1610 } 1611 STATUS current 1612 DESCRIPTION 1613 "Objects that are contained in the notifications." 1614 ::= { gsmpGroups 6 } 1616 gsmpNotificationsGroup NOTIFICATION-GROUP 1617 NOTIFICATIONS { 1618 gsmpSessionDownTrap, 1619 gsmpSessionUpTrap, 1620 gsmpSendFailiureIndicationTrap, 1621 gsmpReceivedFailiureIndicationTrap, 1622 gsmpPortUpEventTrap, 1623 gsmpPortDownEventTrap, 1624 gsmpInvalidLabelEventTrap, 1625 gsmpNewPortEventTrap, 1626 gsmpDeadPortEventTrap, 1627 gsmpAdjacenyUpdateEventTrap 1628 } 1629 STATUS current 1630 DESCRIPTION 1631 "The notifications which indicate specific changes in the 1632 value of objects gsmpSessionTable and gsmpSessionStatTable." 1634 ::= { gsmpGroups 7 } 1636 END 1638 5. Revision History 1640 This section should be removed when this document is published as 1641 an RFC. 1643 5.1 Design considerations 1645 5.1.1 Switch partitions 1647 The management of switch partitions falls outside of the 1648 management of GSMP, so this is excluded from the GSMP mib. 1650 5.1.2 Protocol mib 1652 The GSMP mib is only a protocool mib. It contains object to manage 1653 the GSMP protocol. It does not provide any information learned via 1654 the protocool, such as "all ports config" information. 1656 5.1.3 VSCE/VSE/VSC/VS relationships 1658 The relationships between Virtual Switch Controller Entity, 1659 Virtual Switch Entity, Virtual Switch Controller and Virtual 1660 Switch are not included in the mib. 1662 5.1.4 Multiple controllers 1664 It is possible to define the maximum number of VSCE controlling 1665 one VSE. It is however not possible to define that one VSCE 1666 doesn't allow other VSCE on the same switch. It is assumed that 1667 there are mechanisms that syncronize controllers and the 1668 configuration of them. This is outside the scope of this mib. 1670 5.1.5 Row index in notifications 1672 {gsmpSessionThisSideId, gsmpSessionFarSideId} are used as index in 1673 the in the notifications. Since they are row indexes they are 1674 specified as not-accesoible in their definition and are hence not 1675 possisble to send in a notification. It is considered poor MIB 1676 design to use index items in the these clauses because their value 1677 is the same as the instance returned. Their value is infered from 1678 the instance OID of other objects in the notification. 1680 However, we violated this rule on purpuse since we think that it's 1681 clearer this way. We need input from the WG for how their 1682 respective managment systems prefer to get the information. 1684 The mib compiles (smicng) if option -CN is used. 1686 5.2 Changes from < draft-ietf-gsmp-mib-00.txt > 1688 Mib totaly remade :-) 1690 5.3 Changes from < draft-ietf-gsmp-mib-01.txt > 1692 - Imported AtmVcIdentifier, AtmVpIdentifier FROM ATM-TC-MIB 1694 - Removed serviceModelType 1696 - Separated the Vse and Vsce config stuf in separate tables. 1698 - Also added ATM,TCP/IP, Vse and Vsce groups 1700 - Added control of multiple controllers 1702 - Added Vse window size and switch type configuration. 1704 - Added control of resync strategy 1706 - Added last failure code and discontinuity time 1708 - Added event config and count 1710 - Added notifications 1712 6. Acknowledgments 1714 The authors would like to thank Avri Doria for valuable input and 1715 comments. 1717 7. References 1719 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1720 of Management Information for TCP/IP-based Internets", STD 1721 16, RFC 1155, May 1990 1723 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1724 16, RFC 1212, March 1991 1726 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1727 SNMP", RFC 1215, March 1991 1729 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1730 Network Management Protocol", STD 15, RFC 1157, May 1990. 1732 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1733 "Introduction to Community-based SNMPv2", RFC 1901, January 1734 1996. 1736 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1737 "Protocol Operations for Version 2 of the Simple Network 1738 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1740 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1741 "Transport Mappings for Version 2 of the Simple Network 1742 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1744 [RFC1987] Newman, P, Edwards, W., Hinden, R., Hoffman, E. Ching 1745 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 1746 Switch Management Protocol Specification," Version 1.1, 1747 RFC 1987, August 1996. 1749 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", 1750 BCP 9, RFC 2026, Harvard University, October 1996 1752 [RFC2233] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB 1753 using SMIv2", RFC 2233, November 1997. 1755 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1756 Levels", BCP 14, RFC 2119, Harvard University, March 1997 1758 [RFC2397] Newman, P, Edwards, W., Hinden, R., Hoffman, E., Ching 1759 Liaw, F., Lyon, T. and Minshall, G., "Ipsilon's General 1760 Switch Management Protocol Specification," Version 2.0, 1761 RFC 2397, March 1998. 1763 [RFC2434] Narten, T., and H. Alvestrand, "Guidelines for Writing an 1764 IANA Considerations Section in RFCs.", RFC 2434, IBM, 1765 Maxware, October 1998 1767 [RFC2514] Noto, M., E. Spiegel, K. Tesink, "Definition of Textual 1768 Conventions and OBJECT-IDENTITIES for ATM Management", 1769 RFC 2514, February 1999. 1771 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1772 "Introduction to Version 3 of the Internet-standard Network 1773 Management Framework", RFC 2570, April 1999 1775 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1776 for Describing SNMP Management Frameworks", RFC 2571, April 1777 1999 1779 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1780 Processing and Dispatching for the Simple Network Management 1781 Protocol (SNMP)", RFC 2572, April 1999 1783 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1784 RFC 2573, April 1999 1786 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1787 (USM) for version 3 of the Simple Network Management 1788 Protocol (SNMPv3)", RFC 2574, April 1999 1790 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1791 Access Control Model (VACM) for the Simple Network 1792 Management Protocol (SNMP)", RFC 2575, April 1999 1794 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1795 Rose, M., and S. Waldbusser, "Structure of Management 1796 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1798 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1799 Rose, M., and S. Waldbusser, "Textual Conventions for 1800 SMIv2", STD 58, RFC 2579, April 1999 1802 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1803 Rose, M., and S. Waldbusser, "Conformance Statements for 1804 SMIv2", STD 58, RFC 2580, April 1999 1806 [GSMPv3] Doria, Hellstrand, Sundell, Worster, "General Switch Management 1807 Protocol V3", work in progress, April 2000 1809 [GSMPenc] Doria, Worster, "GSMP Packet Encapsulations for ATM, Ethernet 1810 and TCP", work in progress, April 2000 1812 8. Security Considerations 1814 Assuming that secure network management (such as SNMP v3) is 1815 implemented, the objects represented in this MIB do not pose a 1816 threat to the security of the network. 1818 There are a number of management objects defined in this MIB that 1819 have a MAX-ACCESS clause of read-write and/or read-create. Such 1820 objects may be considered sensitive or vulnerable in some network 1821 environments. The support for SET operations in a non-secure 1822 environment without proper protection can have a negative effect 1823 on network operations. 1825 There are a number of managed objects in this MIB that may contain 1826 sensitive information. These are contained in the gsmpVsceTable 1827 and gsmpVseTable. It is thus important to control even GET access 1828 to these objects and possibly to even encrypt the values of these 1829 object when sending them over the network via SNMP. Not all 1830 versions of SNMP provide features for such a secure environment. 1832 SNMPv2 by itself is not a secure environment. Even if the network 1833 itself is secure (for example by using IPSec), even then, there is 1834 no control as to who on the secure network is allowed to access 1835 and GET/SET (read/change/create/delete) the objects in this MIB. 1837 It is recommended that the implementers consider the security 1838 features as provided by the SNMPv3 framework. Specifically, the 1839 use of the User-based Security Model RFC 2574 [RFC2574] and the 1840 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1842 It is then a customer/user responsibility to ensure that the SNMP 1843 entity giving access to an instance of this MIB, is properly 1844 configured to give access to the objects only to those principals 1845 (users) that have legitimate rights to indeed GET or SET 1846 (change/create/delete) them. 1848 9. Authors' Addresses 1850 Hans Sjostrand 1851 Ericsson Telecom AB 1852 Business Unit Data Backbone and Optical Networks 1853 S-126 25 Stockholm, Sweden 1854 Phone: +46 8 719 9960 1855 Email: hans.sjostrand@ericsson.com 1857 Joachim Buerkle 1858 Nortel Dasa Network Systems GmbH & Co KG 1859 (Nortel Networks) 1860 Hahnstrasse 37-39 1861 D-60528 Frankfurt, Germany 1862 Phone: +49 69 6697 3281 1863 Email: joachim.buerkle@nortel-dasa.de 1865 Balaji Srinivasan 1866 CPlane Inc. 1867 5150 El Camino Real 1868 Suite B-31 1869 Los Altos, CA 94022 1870 Phone +1 650 938 8066 ext 103 1871 Email: balaji@cplane.com 1873 10. Full Copyright Statement 1875 Copyright (C) The Internet Society (2000). All Rights Reserved. 1877 This document and translations of it may be copied and furnished 1878 to others, and derivative works that comment on or otherwise 1879 explain it or assist in its implementation may be prepared, 1880 copied, published and distributed, in whole or in part, without 1881 restriction of any kind, provided that the above copyright notice 1882 and this paragraph are included on all such copies and derivative 1883 works. However, this document itself may not be modified in any 1884 way, such as by removing the copyright notice or references to the 1885 Internet Society or other Internet organizations, except as needed 1886 for the purpose of developing Internet standards in which case 1887 the procedures for copyrights defined in the Internet Standards 1888 process must be followed, or as required to translate it into 1889 languages other than English. 1891 The limited permissions granted above are perpetual and will not 1892 be revoked by the Internet Society or its successors or assigns. 1894 This document and the information contained herein is provided on 1895 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1896 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1897 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1898 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1899 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.