idnits 2.17.1 draft-ietf-ips-ifcp-mib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1360. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1329. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1336. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1342. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC4172]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1222: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 1228: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Unrecognized Status in '', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2005) is 6740 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) ** Obsolete normative reference: RFC 2021 (Obsoleted by RFC 4502) -- Duplicate reference: RFC2021, mentioned in 'RFC2856', was also mentioned in 'RFC2021'. ** Obsolete normative reference: RFC 2021 (ref. 'RFC2856') (Obsoleted by RFC 4502) ** Obsolete normative reference: RFC 4133 (Obsoleted by RFC 6933) Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPS Kevin Gibbons 3 Internet Draft McDATA Corporation 4 Charles Monia 5 Category: standards-track Consultant 6 Expires: April 2006 Josh Tseng 7 Riverbed Technology 8 Franco Travostino 9 Nortel 11 October 2005 13 Definitions of Managed Objects for iFCP 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other documents 29 at any time. It is inappropriate to use Internet-Drafts as 30 reference material or to cite them other than as "work in progress". 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire in April 2006. 40 Abstract 42 The iFCP protocol [RFC4172] provides Fibre Channel fabric 43 functionality on an IP network in which TCP/IP switching and routing 44 elements replace Fibre Channel components. The iFCP protocol is 45 used between iFCP Gateways. This draft provides a mechanism to 46 monitor and control iFCP Gateway instances, and their associated 47 sessions, using SNMP. 49 This memo is a product of the IP Storage (IPS) working group within 50 the Internet Engineering Task Force. Comments are solicited and 51 should be addressed to the working group's mailing list at 52 ips@ietf.org and/or the authors. 54 Gibbons Expires April 2006 1 55 Table of Contents 57 Status of this Memo................................................1 58 Abstract...........................................................1 59 Table of Contents..................................................2 60 1. The Internet-Standard Management Framework.....................3 61 2. Introduction...................................................3 62 3. Technical Description..........................................4 63 4. MIB Definition.................................................4 64 5. IANA Considerations...........................................23 65 6. Security Considerations.......................................23 66 7. Normative References..........................................24 67 8. Informative References........................................25 68 9. Authors' Addresses............................................25 69 10. Intellectual Property Statement...............................26 70 11. Full Copyright Statement......................................26 71 12. Disclaimer of Validity........................................26 72 13. Acknowledgment................................................27 74 Gibbons Expires April 2006 2 75 1. The Internet-Standard Management Framework 77 For a detailed overview of the documents that describe the current 78 Internet-Standard Management Framework, please refer to section 7 of 79 RFC 3410 [RFC3410]. 81 Managed objects are accessed via a virtual information store, termed 82 the Management Information Base or MIB. MIB objects are generally 83 accessed through the Simple Network Management Protocol (SNMP). 84 Objects in the MIB are defined using the mechanisms defined in the 85 Structure of Management Information (SMI). This memo specifies a 86 MIB module that is compliant to the SMIv2, which is described in STD 87 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 88 2580 [RFC2580]. 90 2. Introduction 92 The iFCP protocol can be used by FC to IP based storage gateways for 93 Fibre Channel Protocol (FCP) storage interconnects. Figure 1 94 provides an example interconnect between iFCP gateways. 96 Gateway Region Gateway Region 97 +--------+ +--------+ +--------+ +--------+ 98 | FC | | FC | | FC | | FC | 99 | Device | | Device | | Device | | Device | Fibre 100 |........| |........| FC |........| |........| Channel 101 | N_PORT | | N_PORT |<.........>| N_PORT | | N_PORT | Device 102 +---+----+ +---+----+ Traffic +----+---+ +----+---+ Domain 103 | | | | ^ 104 +---+----+ +---+----+ +----+---+ +----+---+ | 105 | F_PORT | | F_PORT | | F_PORT | | F_PORT | | 106 =+========+==+========+===========+========+==+========+========== 107 | iFCP Layer |<--------->| iFCP Layer | | 108 |....................| ^ |....................| | 109 | iFCP Portal | | | iFCP Portal | v 110 +--------+-----------+ | +----------+---------+ IP 111 iFCP|Gateway Control iFCP|Gateway Network 112 | Data | 113 | | 114 | | 115 |<------Encapsulated Frames------->| 116 | +------------------+ | 117 | | | | 118 +------+ IP Network +--------+ 119 | | 120 +------------------+ 122 The iFCP MIB Module is designed to allow SNMP to be used to monitor 123 and manage local iFCP gateway instances, including the configuration 124 of iFCP sessions between gateways. 126 Gibbons Expires April 2006 3 127 3. Technical Description 129 The iFCP MIB Module is divided into sections for iFCP local gateway 130 instance management, iFCP session management, and iFCP session 131 statistics. 133 The section for iFCP gateway management provides default settings 134 and information about each local instance. A single management 135 entity can monitor multiple local gateway instances. Each local 136 gateway is conceptually an independent gateway that has both Fibre 137 Channel and IP interfaces. The default IP Time Out Value (IP_TOV) 138 is configurable for each gateway. Other standard MIBs, such as the 139 Fibre Management MIB [RFC4044] or Interfaces Group MIB [RFC2863], 140 can be used to manage non-iFCP specific gateway parameters. The 141 local gateway instance section provides iFCP specific information as 142 well as optional links to other standard management MIBs. 144 The iFCP session management section provides information on iFCP 145 sessions that are using one of the local iFCP gateway instances. 146 This section allows the management of specific iFCP parameters, 147 including changing the IP_TOV from the default setting of the 148 gateway. 150 The iFCP session statistics section provides statistical information 151 on the iFCP sessions that are using one of the local iFCP gateways. 152 These tables augment the session management table. Additional 153 statistical information for an iFCP gateway or session, that is not 154 iFCP specific, can be obtained using other standard MIBs. The iFCP 155 statistics are provided in both standard and low-capacity 156 (counter32) methods. 158 The following MIB module imports from RMON2-MIB [RFC2021], SNMPv2- 159 SMI [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], HCNUM-TC 160 [RFC2856], IF-MIB [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET- 161 ADDRESS-MIB [RFC4001], FC-MGMT-MIB [RFC4044], and ENTITY-MIB (v3) 162 [RFC4133]. 164 4. MIB Definition 166 IFCP-MGMT-MIB DEFINITIONS ::= BEGIN 168 IMPORTS 169 MODULE-IDENTITY, 170 OBJECT-TYPE, 171 Gauge32, 172 Integer32, 173 Unsigned32, 174 transmission 175 FROM SNMPv2-SMI 177 OBJECT-GROUP, 178 MODULE-COMPLIANCE 180 Gibbons Expires April 2006 4 181 FROM SNMPv2-CONF 183 TEXTUAL-CONVENTION, 184 TimeStamp, 185 TruthValue, 186 StorageType 187 FROM SNMPv2-TC 189 -- From RFC 2021 190 ZeroBasedCounter32 191 FROM RMON2-MIB 193 -- From RFC 2856 194 ZeroBasedCounter64 195 FROM HCNUM-TC 197 -- From RFC 2863 198 InterfaceIndexOrZero 199 FROM IF-MIB 201 -- From RFC 3411 202 SnmpAdminString 203 FROM SNMP-FRAMEWORK-MIB 205 -- From RFC 4001 206 InetAddressType, 207 InetAddress, 208 InetPortNumber 209 FROM INET-ADDRESS-MIB 211 -- From RFC 4044 212 FcNameIdOrZero, 213 FcAddressIdOrZero 214 FROM FC-MGMT-MIB 216 -- From RFC 4133 217 PhysicalIndexOrZero 218 FROM ENTITY-MIB 219 ; 221 ifcpMgmtMIB MODULE-IDENTITY 222 LAST-UPDATED "200510040000Z" 223 ORGANIZATION "IETF IPS Working Group" 224 CONTACT-INFO " 225 Attn: Kevin Gibbons 226 McDATA Corporation 227 4555 Great America Pkwy 228 Santa Clara, CA 95054-1208 USA 229 Phone: (408)567-5765 230 EMail: kevin.gibbons@mcdata.com 232 Charles Monia 234 Gibbons Expires April 2006 5 235 Consultant 236 7553 Morevern Circle 237 San Jose, CA 95135 USA 238 EMail: charles_monia@yahoo.com 240 Josh Tseng 241 Riverbed Technology 242 501 2nd Street, Suite 410 243 San Francisco, CA 94107 USA 244 Phone: (650)274-2109 245 EMail: joshtseng@yahoo.com 247 Franco Travostino 248 Nortel 249 600 Technology Park Drive 250 Billerica, MA 01821 USA 251 Phone: (978)288-7708 252 EMail: travos@nortel.com" 254 DESCRIPTION 255 "This module defines management information specific 256 to internet Fibre Channel Protocol (iFCP) gateway 257 management. 259 Copyright (C) The Internet Society 2005. This 260 version of this MIB module is part of RFC XXXX; see 261 the RFC itself for full legal notices." 263 REVISION "200510040000Z" 264 DESCRIPTION 265 "Initial version of iFCP Management Module. 266 This MIB published as RFC XXXX." 268 -- RFC Ed.: replace XXXX with RFC number assigned to this document 269 ::= { transmission YYYY } 270 -- RFC Ed.: enter the IANA assigned number to this MIB for YYYY 272 -- 273 -- Textual Conventions 274 -- 276 IfcpIpTOVorZero ::= TEXTUAL-CONVENTION 277 DISPLAY-HINT "d" 278 STATUS current 279 DESCRIPTION "The maximum propagation delay, in seconds, 280 for an encapsulated FC frame to traverse the 281 IP network. A value of 0 implies fibre 282 channel frame lifetime limits will not be 283 enforced." 284 REFERENCE "RFC 4172, iFCP Protocol Specification" 285 SYNTAX Unsigned32 (0..3600) 287 Gibbons Expires April 2006 6 288 IfcpLTIorZero ::= TEXTUAL-CONVENTION 289 DISPLAY-HINT "d" 290 STATUS current 291 DESCRIPTION "The value for the Liveness Test Interval 292 (LTI) being used in an iFCP connection, in 293 seconds. A value of 0 implies no Liveness 294 Test Interval will be used." 295 REFERENCE "RFC 4172, iFCP Protocol Specification" 296 SYNTAX Unsigned32 (0..65535) 298 IfcpSessionStates ::= TEXTUAL-CONVENTION 299 STATUS current 300 DESCRIPTION "The value for an iFCP session state." 301 SYNTAX INTEGER {down(1), openPending(2), open(3)} 303 IfcpAddressMode ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION "The values for iFCP Address Translation 306 Mode." 307 REFERENCE "RFC 4172, iFCP Protocol Specification" 308 SYNTAX INTEGER {addressTransparent(1), 309 addressTranslation(2)} 311 -- 312 -- Internet Fibre Channel Protocol (iFCP) 313 -- 315 ifcpGatewayObjects OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1} 316 ifcpGatewayConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2} 318 -- 319 -- Local iFCP Gateway Instance Information ================== 320 -- 322 ifcpLclGatewayInfo OBJECT IDENTIFIER ::= {ifcpGatewayObjects 1} 324 ifcpLclGtwyInstTable OBJECT-TYPE 325 SYNTAX SEQUENCE OF IfcpLclGtwyInstEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "Information about all local iFCP Gateway instances that can 330 be monitored and controlled. This table contains an entry 331 for each local iFCP Gateway instance that is being managed." 332 ::= {ifcpLclGatewayInfo 1} 334 ifcpLclGtwyInstEntry OBJECT-TYPE 335 SYNTAX IfcpLclGtwyInstEntry 336 MAX-ACCESS not-accessible 337 STATUS current 338 DESCRIPTION 339 "An entry in the local iFCP Gateway Instance table. 341 Gibbons Expires April 2006 7 342 Parameters and settings for the gateway are found here." 343 INDEX { ifcpLclGtwyInstIndex } 344 ::= {ifcpLclGtwyInstTable 1} 346 IfcpLclGtwyInstEntry ::= SEQUENCE { 347 ifcpLclGtwyInstIndex Unsigned32, 348 ifcpLclGtwyInstPhyIndex PhysicalIndexOrZero, 349 ifcpLclGtwyInstVersionMin Unsigned32, 350 ifcpLclGtwyInstVersionMax Unsigned32, 351 ifcpLclGtwyInstAddrTransMode IfcpAddressMode, 352 ifcpLclGtwyInstFcBrdcstSupport TruthValue, 353 ifcpLclGtwyInstDefaultIpTOV IfcpIpTOVorZero, 354 ifcpLclGtwyInstDefaultLTInterval IfcpLTIorZero, 355 ifcpLclGtwyInstDescr SnmpAdminString, 356 ifcpLclGtwyInstNumActiveSessions Gauge32, 357 ifcpLclGtwyInstStorageType StorageType 358 } 360 ifcpLclGtwyInstIndex OBJECT-TYPE 361 SYNTAX Unsigned32 (1..2147483647) 362 MAX-ACCESS not-accessible 363 STATUS current 364 DESCRIPTION 365 "An arbitrary integer value to uniquely identify this iFCP 366 Gateway from other local Gateway instances." 367 ::= {ifcpLclGtwyInstEntry 1} 369 ifcpLclGtwyInstPhyIndex OBJECT-TYPE 370 SYNTAX PhysicalIndexOrZero 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "An index indicating the location of this local gateway within 375 a larger entity, if one exists. If supported, this is the 376 entPhysicalIndex from the Entity MIB (Version 3), for this 377 iFCP Gateway. If not supported, or if not related to a 378 physical entity, then the value of this object is 0." 379 REFERENCE "Entity MIB (Version 3)" 380 ::= {ifcpLclGtwyInstEntry 2} 382 ifcpLclGtwyInstVersionMin OBJECT-TYPE 383 SYNTAX Unsigned32 (0..255) 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The minimum iFCP protocol version supported by the local iFCP 388 gateway instance." 389 REFERENCE "RFC 4172, iFCP Protocol Specification" 390 ::= {ifcpLclGtwyInstEntry 3} 392 ifcpLclGtwyInstVersionMax OBJECT-TYPE 393 SYNTAX Unsigned32 (0..255) 395 Gibbons Expires April 2006 8 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The maximum iFCP protocol version supported by the local iFCP 400 gateway instance." 401 REFERENCE "RFC 4172, iFCP Protocol Specification" 402 ::= {ifcpLclGtwyInstEntry 4} 404 ifcpLclGtwyInstAddrTransMode OBJECT-TYPE 405 SYNTAX IfcpAddressMode 406 MAX-ACCESS read-write 407 STATUS current 408 DESCRIPTION 409 "The local iFCP gateway operating mode. Changing this value 410 may cause existing sessions to be disrupted." 411 REFERENCE "RFC 4172, iFCP Protocol Specification" 412 DEFVAL { addressTranslation } 413 ::= {ifcpLclGtwyInstEntry 5} 415 ifcpLclGtwyInstFcBrdcstSupport OBJECT-TYPE 416 SYNTAX TruthValue 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "Whether the local iFCP gateway supports FC Broadcast. 421 Changing this value may cause existing sessions to be 422 disrupted." 423 REFERENCE "RFC 4172, iFCP Protocol Specification" 424 DEFVAL { false } 425 ::= {ifcpLclGtwyInstEntry 6} 427 ifcpLclGtwyInstDefaultIpTOV OBJECT-TYPE 428 SYNTAX IfcpIpTOVorZero 429 MAX-ACCESS read-write 430 STATUS current 431 DESCRIPTION 432 "The default IP_TOV used for iFCP sessions at this gateway. 433 This is the default maximum propagation delay that will be 434 used for an iFCP session. The value can be changed on a 435 per-session basis. The valid range is 0 - 3600 seconds. 436 A value of 0 implies that fibre channel frame lifetime limits 437 will not be enforced." 438 REFERENCE "RFC 4172, iFCP Protocol Specification" 439 DEFVAL { 6 } 440 ::= {ifcpLclGtwyInstEntry 7} 442 ifcpLclGtwyInstDefaultLTInterval OBJECT-TYPE 443 SYNTAX IfcpLTIorZero 444 MAX-ACCESS read-write 445 STATUS current 446 DESCRIPTION 447 "The default Liveness Test Interval (LTI), in seconds, used 449 Gibbons Expires April 2006 9 450 for iFCP sessions at this gateway. This is the default 451 value for an iFCP session and can be changed on a 452 per-session basis. The valid range is 0 - 65535 seconds. 453 A value of 0 implies no Liveness Test Interval will be 454 performed on a session." 455 REFERENCE "RFC 4172, iFCP Protocol Specification" 456 DEFVAL { 10 } 457 ::= {ifcpLclGtwyInstEntry 8} 459 ifcpLclGtwyInstDescr OBJECT-TYPE 460 SYNTAX SnmpAdminString (SIZE (0..64)) 461 MAX-ACCESS read-write 462 STATUS current 463 DESCRIPTION 464 "A user entered description for this iFCP Gateway." 465 DEFVAL { "" } 466 ::= {ifcpLclGtwyInstEntry 9} 468 ifcpLclGtwyInstNumActiveSessions OBJECT-TYPE 469 SYNTAX Gauge32 (0..4294967295) 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "The current total number of iFCP sessions in the open or 474 open-pending state." 475 ::= {ifcpLclGtwyInstEntry 10} 477 ifcpLclGtwyInstStorageType OBJECT-TYPE 478 SYNTAX StorageType 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The storage type for this row. Parameter values defined 483 for a gateway are usually non-volatile, but may be volatile 484 or permanent in some configurations. If permanent, than 485 the following parameters must have read-write access: 486 ifcpLclGtwyInstAddrTransMode, ifcpLclGtwyInstDefaultIpTOV, 487 and ifcpLclGtwyInstDefaultLTInterval." 488 DEFVAL { nonVolatile } 489 ::= {ifcpLclGtwyInstEntry 11} 491 -- 492 -- iFCP N Port Session Information ============================ 493 -- 495 ifcpNportSessionInfo 496 OBJECT IDENTIFIER ::= {ifcpGatewayObjects 2} 498 ifcpSessionAttributesTable OBJECT-TYPE 499 SYNTAX SEQUENCE OF 500 IfcpSessionAttributesEntry 501 MAX-ACCESS not-accessible 503 Gibbons Expires April 2006 10 504 STATUS current 505 DESCRIPTION 506 "An iFCP session consists of the pair of N_PORTs comprising 507 the session endpoints joined by a single TCP/IP connection. 508 This table provides information on each iFCP session 509 currently using a local iFCP Gateway instance. iFCP sessions 510 are created and removed by the iFCP Gateway instances, which 511 are reflected in this table." 512 ::= {ifcpNportSessionInfo 1} 514 ifcpSessionAttributesEntry OBJECT-TYPE 515 SYNTAX IfcpSessionAttributesEntry 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "An entry in the session table." 520 INDEX { ifcpLclGtwyInstIndex, ifcpSessionIndex } 521 ::= {ifcpSessionAttributesTable 1} 523 IfcpSessionAttributesEntry ::= SEQUENCE { 524 ifcpSessionIndex Integer32, 525 ifcpSessionLclPrtlIfIndex InterfaceIndexOrZero, 526 ifcpSessionLclPrtlAddrType InetAddressType, 527 ifcpSessionLclPrtlAddr InetAddress, 528 ifcpSessionLclPrtlTcpPort InetPortNumber, 529 ifcpSessionLclNpWwun FcNameIdOrZero, 530 ifcpSessionLclNpFcid FcAddressIdOrZero, 531 ifcpSessionRmtNpWwun FcNameIdOrZero, 532 ifcpSessionRmtPrtlIfAddrType InetAddressType, 533 ifcpSessionRmtPrtlIfAddr InetAddress, 534 ifcpSessionRmtPrtlTcpPort InetPortNumber, 535 ifcpSessionRmtNpFcid FcAddressIdOrZero, 536 ifcpSessionRmtNpFcidAlias FcAddressIdOrZero, 537 ifcpSessionIpTOV IfcpIpTOVorZero, 538 ifcpSessionLclLTIntvl IfcpLTIorZero, 539 ifcpSessionRmtLTIntvl IfcpLTIorZero, 540 ifcpSessionBound TruthValue, 541 ifcpSessionStorageType StorageType 542 } 544 ifcpSessionIndex OBJECT-TYPE 545 SYNTAX Integer32 (1..2147483647) 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "The iFCP session index is a unique value used as an index 550 to the table, along with a specific local iFCP Gateway 551 instance. This index is used because the local N Port and 552 remote N Port information would create an complex index that 553 would be difficult to implement." 554 ::= {ifcpSessionAttributesEntry 1} 556 Gibbons Expires April 2006 11 557 ifcpSessionLclPrtlIfIndex OBJECT-TYPE 558 SYNTAX InterfaceIndexOrZero 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "This is the interface index in the IF-MIB ifTable being used 563 as the local portal in this session, as described in the 564 IF-MIB. If the local portal is not associated with an entry 565 in the ifTable, then the value is 0. The ifType of the 566 interface will generally be a type that supports IP, but an 567 implementation may support iFCP using other protocols. This 568 object can be used to obtain additional information about the 569 interface." 570 REFERENCE "RFC 2863, The Interfaces Group MIB (IF-MIB)" 571 ::= {ifcpSessionAttributesEntry 2} 573 ifcpSessionLclPrtlAddrType OBJECT-TYPE 574 SYNTAX InetAddressType 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The type of address in ifcpSessionLclIfAddr." 579 ::= {ifcpSessionAttributesEntry 3} 581 ifcpSessionLclPrtlAddr OBJECT-TYPE 582 SYNTAX InetAddress 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "This is the external IP address of the interface being used 587 for the iFCP local portal in this session. The address type 588 is defined in ifcpSessionLclPrtlAddrType. If the value is a 589 DNS name, then the name is resolved once, during the initial 590 session instantiation." 591 ::= {ifcpSessionAttributesEntry 4} 593 ifcpSessionLclPrtlTcpPort OBJECT-TYPE 594 SYNTAX InetPortNumber 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "This is the TCP port number that is being used for the iFCP 599 local portal in this session. This is normally an ephemeral 600 port number selected by the gateway. The value may be 0 601 during an initial setup period." 602 ::= {ifcpSessionAttributesEntry 5} 604 ifcpSessionLclNpWwun OBJECT-TYPE 605 SYNTAX FcNameIdOrZero 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 610 Gibbons Expires April 2006 12 611 "World Wide Unique Name of the local N Port. For an unbound 612 session this variable will be a zero-length string." 613 REFERENCE "RFC 4172, iFCP Protocol Specification" 614 DEFVAL { "" } 615 ::= {ifcpSessionAttributesEntry 6} 617 ifcpSessionLclNpFcid OBJECT-TYPE 618 SYNTAX FcAddressIdOrZero 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "Fibre Channel Identifier of the local N Port. For an unbound 623 session this variable will be a zero-length string." 624 REFERENCE "RFC 4172, iFCP Protocol Specification" 625 ::= {ifcpSessionAttributesEntry 7} 627 ifcpSessionRmtNpWwun OBJECT-TYPE 628 SYNTAX FcNameIdOrZero 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "World Wide Unique Name of the remote N Port. For an unbound 633 session this variable will be a zero-length string." 634 REFERENCE "RFC 4172, iFCP Protocol Specification" 635 DEFVAL { "" } 636 ::= {ifcpSessionAttributesEntry 8} 638 ifcpSessionRmtPrtlIfAddrType OBJECT-TYPE 639 SYNTAX InetAddressType 640 MAX-ACCESS read-only 641 STATUS current 642 DESCRIPTION 643 "The type of address in ifcpSessionRmtPrtlIfAddr." 644 ::= {ifcpSessionAttributesEntry 9} 646 ifcpSessionRmtPrtlIfAddr OBJECT-TYPE 647 SYNTAX InetAddress 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "This is the remote gateway IP address being used for the 652 portal on the remote iFCP gateway. The address type is 653 defined in ifcpSessionRmtPrtlIfAddrType. If the value is a 654 DNS name, then the name is resolved once, during the initial 655 session instantiation." 656 ::= {ifcpSessionAttributesEntry 10} 658 ifcpSessionRmtPrtlTcpPort OBJECT-TYPE 659 SYNTAX InetPortNumber 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 664 Gibbons Expires April 2006 13 665 "This is the TCP port number being used for the portal on the 666 remote iFCP gateway. Generally, this will be the iFCP 667 canonical port. The value may be 0 during an initial setup 668 period." 669 DEFVAL { 3420 } 670 ::= {ifcpSessionAttributesEntry 11} 672 ifcpSessionRmtNpFcid OBJECT-TYPE 673 SYNTAX FcAddressIdOrZero 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "Fibre Channel Identifier of the remote N Port. For an 678 unbound session this variable will be a zero-length string." 679 REFERENCE "RFC 4172, iFCP Protocol Specification" 680 ::= {ifcpSessionAttributesEntry 12} 682 ifcpSessionRmtNpFcidAlias OBJECT-TYPE 683 SYNTAX FcAddressIdOrZero 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "Fibre Channel Identifier Alias assigned by the local gateway 688 for the remote N Port. For an unbound session this variable 689 will be a zero-length string." 690 REFERENCE "RFC 4172, iFCP Protocol Specification" 691 ::= {ifcpSessionAttributesEntry 13} 693 ifcpSessionIpTOV OBJECT-TYPE 694 SYNTAX IfcpIpTOVorZero 695 MAX-ACCESS read-write 696 STATUS current 697 DESCRIPTION 698 "The IP_TOV being used for this iFCP session. This is the 699 maximum propagation delay that will be used for the iFCP 700 session. The value can be changed on a per-session basis 701 and initially defaults to ifcpLclGtwyInstDefaultIpTOV for 702 the local gateway instance. The valid range is 0 - 3600 703 seconds. A value of 0 implies fibre channel frame lifetime 704 limits will not be enforced." 705 REFERENCE "RFC 4172, iFCP Protocol Specification" 706 ::= {ifcpSessionAttributesEntry 14} 708 ifcpSessionLclLTIntvl OBJECT-TYPE 709 SYNTAX IfcpLTIorZero 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "The Liveness Test Interval (LTI) used for this iFCP session. 714 The value can be changed on a per-session basis and initially 715 defaults to ifcpLclGtwyInstDefaultLTInterval for the local 716 gateway instance. The valid range is 0 - 65535 seconds. 718 Gibbons Expires April 2006 14 719 A value of 0 implies that the gateway will not originate 720 Liveness Test messages for the session." 721 REFERENCE "RFC 4172, iFCP Protocol Specification" 722 ::= {ifcpSessionAttributesEntry 15} 724 ifcpSessionRmtLTIntvl OBJECT-TYPE 725 SYNTAX IfcpLTIorZero 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The Liveness Test Interval (LTI) as requested by the remote 730 gateway instance to use for this iFCP session. This value may 731 change over the life of the session. The valid range is 0 - 732 65535 seconds. A value of 0 implies that the remote gateway 733 has not been requested to originate Liveness Test messages for 734 the session." 735 REFERENCE "RFC 4172, iFCP Protocol Specification" 736 ::= {ifcpSessionAttributesEntry 16} 738 ifcpSessionBound OBJECT-TYPE 739 SYNTAX TruthValue 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "This value indicates whether this session is bound to a 744 specific local and remote N Port. Sessions by default are 745 unbound and ready for future assignment to a local and remote 746 N Port." 747 REFERENCE "RFC 4172, iFCP Protocol Specification" 748 ::= {ifcpSessionAttributesEntry 17} 750 ifcpSessionStorageType OBJECT-TYPE 751 SYNTAX StorageType 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The storage type for this row. Parameter values defined 756 for a session are usually non-volatile, but may be volatile 757 or permanent in some configurations. If permanent, than 758 ifcpSessionIpTOV must have read-write access." 759 DEFVAL { nonVolatile } 760 ::= {ifcpSessionAttributesEntry 18} 762 -- 763 -- Local iFCP Gateway Instance Session Statistics ============= 764 -- 766 ifcpSessionStatsTable OBJECT-TYPE 767 SYNTAX SEQUENCE OF 768 IfcpSessionStatsEntry 769 MAX-ACCESS not-accessible 770 STATUS current 772 Gibbons Expires April 2006 15 773 DESCRIPTION 774 "This table provides statistics on an iFCP session." 775 ::= {ifcpNportSessionInfo 2} 777 ifcpSessionStatsEntry OBJECT-TYPE 778 SYNTAX IfcpSessionStatsEntry 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "Provides iFCP specific statistics per session." 783 AUGMENTS {ifcpSessionAttributesEntry} 784 ::= {ifcpSessionStatsTable 1} 786 IfcpSessionStatsEntry ::= SEQUENCE { 787 ifcpSessionState IfcpSessionStates, 788 ifcpSessionDuration Unsigned32, 789 ifcpSessionTxOctets ZeroBasedCounter64, 790 ifcpSessionRxOctets ZeroBasedCounter64, 791 ifcpSessionTxFrames ZeroBasedCounter64, 792 ifcpSessionRxFrames ZeroBasedCounter64, 793 ifcpSessionStaleFrames ZeroBasedCounter64, 794 ifcpSessionHeaderCRCErrors ZeroBasedCounter64, 795 ifcpSessionFcPayloadCRCErrors ZeroBasedCounter64, 796 ifcpSessionOtherErrors ZeroBasedCounter64, 797 ifcpSessionDiscontinuityTime TimeStamp 798 } 800 ifcpSessionState OBJECT-TYPE 801 SYNTAX IfcpSessionStates 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The current session operating state." 806 ::= {ifcpSessionStatsEntry 1} 808 ifcpSessionDuration OBJECT-TYPE 809 SYNTAX Unsigned32 (0..4294967295) 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "This indicates, in seconds, how long the iFCP session has 814 been in an open or open-pending state. When a session is 815 down the value is reset to 0." 816 ::= {ifcpSessionStatsEntry 2} 818 ifcpSessionTxOctets OBJECT-TYPE 819 SYNTAX ZeroBasedCounter64 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The total number of octets transmitted by the iFCP gateway 824 for this session. Discontinuities in the value of this 826 Gibbons Expires April 2006 16 827 counter can occur at reinitialization of the management 828 system, and at other times as indicated by the value of 829 ifcpSessionDiscontinuityTime." 830 ::= {ifcpSessionStatsEntry 3} 832 ifcpSessionRxOctets OBJECT-TYPE 833 SYNTAX ZeroBasedCounter64 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "The total number of octets received by the iFCP gateway for 838 this session. Discontinuities in the value of this 839 counter can occur at reinitialization of the management 840 system, and at other times as indicated by the value of 841 ifcpSessionDiscontinuityTime." 842 ::= {ifcpSessionStatsEntry 4} 844 ifcpSessionTxFrames OBJECT-TYPE 845 SYNTAX ZeroBasedCounter64 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "The total number of iFCP frames transmitted by the gateway 850 for this session. Discontinuities in the value of this 851 counter can occur at reinitialization of the management 852 system, and at other times as indicated by the value of 853 ifcpSessionDiscontinuityTime." 854 ::= {ifcpSessionStatsEntry 5} 856 ifcpSessionRxFrames OBJECT-TYPE 857 SYNTAX ZeroBasedCounter64 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The total number of iFCP frames received by the gateway 862 for this session. Discontinuities in the value of this 863 counter can occur at reinitialization of the management 864 system, and at other times as indicated by the value of 865 ifcpSessionDiscontinuityTime." 866 ::= {ifcpSessionStatsEntry 6} 868 ifcpSessionStaleFrames OBJECT-TYPE 869 SYNTAX ZeroBasedCounter64 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "The total number of received iFCP frames that were stale and 874 discarded by the gateway for this session. Discontinuities 875 in the value of this counter can occur at reinitialization 876 of the management system, and at other times as indicated by 877 the value of ifcpSessionDiscontinuityTime." 878 ::= {ifcpSessionStatsEntry 7} 880 Gibbons Expires April 2006 17 881 ifcpSessionHeaderCRCErrors OBJECT-TYPE 882 SYNTAX ZeroBasedCounter64 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The total number of CRC errors that occurred in the frame 887 header, detected by the gateway for this session. Usually, 888 a single Header CRC error is sufficient to terminate an 889 iFCP session. Discontinuities in the value of this 890 counter can occur at reinitialization of the management 891 system, and at other times as indicated by the value of 892 ifcpSessionDiscontinuityTime." 893 ::= {ifcpSessionStatsEntry 8} 895 ifcpSessionFcPayloadCRCErrors OBJECT-TYPE 896 SYNTAX ZeroBasedCounter64 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The total number of CRC errors that occurred in the Fibre 901 Channel frame payload, detected by the gateway for this 902 session. Discontinuities in the value of this counter can 903 occur at reinitialization of the management system, and 904 at other times as indicated by the value of 905 ifcpSessionDiscontinuityTime." 906 ::= {ifcpSessionStatsEntry 9} 908 ifcpSessionOtherErrors OBJECT-TYPE 909 SYNTAX ZeroBasedCounter64 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "The total number of errors, other than errors explicitly 914 measured, detected by the gateway for this session. 915 Discontinuities in the value of this counter can occur at 916 reinitialization of the management system, and at other 917 times as indicated by the value of 918 ifcpSessionDiscontinuityTime." 919 ::= {ifcpSessionStatsEntry 10} 921 ifcpSessionDiscontinuityTime OBJECT-TYPE 922 SYNTAX TimeStamp 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "The value of sysUpTime on the most recent occasion at which 927 any one or more of the ifcpSessionStatsTable counters 928 suffered a discontinuity. The relevant counters are the 929 specific Counter64 based instances associated with the 930 ifcpSessionStatsTable: ifcpSessionTxOctets, 931 ifcpSessionRxOctets, ifcpSessionTxFrames, 933 Gibbons Expires April 2006 18 934 ifcpSessionRxFrames, ifcpSessionStaleFrames, 935 ifcpSessionHeaderCRCErrors, ifcpSessionFcPayloadCRCErrors, 936 and ifcpSessionOtherErrors. If no such discontinuities have 937 occurred since the last reinitialization of the local 938 management subsystem, then this object contains a zero value." 939 ::= {ifcpSessionStatsEntry 11} 941 -- 942 -- Low Capacity Statistics 943 -- 945 ifcpSessionLcStatsTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF 947 IfcpSessionLcStatsEntry 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "This table provides low capacity statistics for an iFCP 952 session. These are provided for backward compatibility with 953 systems that do not support Counter64 based objects. At 954 1Gbps rates, a Counter32 based object can wrap as often as 955 every 34 seconds. Counter32 based objects can be sufficient 956 for many situations. However, when possible, it is 957 recommended to use the high capacity statistics in 958 ifcpSessionStatsTable based on Counter64 objects." 959 ::= {ifcpNportSessionInfo 3} 961 ifcpSessionLcStatsEntry OBJECT-TYPE 962 SYNTAX IfcpSessionLcStatsEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "Provides iFCP specific statistics per session." 967 AUGMENTS {ifcpSessionAttributesEntry} 968 ::= {ifcpSessionLcStatsTable 1} 970 IfcpSessionLcStatsEntry ::= SEQUENCE { 971 ifcpSessionLcTxOctets ZeroBasedCounter32, 972 ifcpSessionLcRxOctets ZeroBasedCounter32, 973 ifcpSessionLcTxFrames ZeroBasedCounter32, 974 ifcpSessionLcRxFrames ZeroBasedCounter32, 975 ifcpSessionLcStaleFrames ZeroBasedCounter32, 976 ifcpSessionLcHeaderCRCErrors ZeroBasedCounter32, 977 ifcpSessionLcFcPayloadCRCErrors ZeroBasedCounter32, 978 ifcpSessionLcOtherErrors ZeroBasedCounter32 979 } 981 ifcpSessionLcTxOctets OBJECT-TYPE 982 SYNTAX ZeroBasedCounter32 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 987 Gibbons Expires April 2006 19 988 "The total number of octets transmitted by the iFCP gateway 989 for this session." 990 ::= {ifcpSessionLcStatsEntry 1} 992 ifcpSessionLcRxOctets OBJECT-TYPE 993 SYNTAX ZeroBasedCounter32 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "The total number of octets received by the iFCP gateway for 998 this session." 999 ::= {ifcpSessionLcStatsEntry 2} 1001 ifcpSessionLcTxFrames OBJECT-TYPE 1002 SYNTAX ZeroBasedCounter32 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "The total number of iFCP frames transmitted by the gateway 1007 for this session." 1008 ::= {ifcpSessionLcStatsEntry 3} 1010 ifcpSessionLcRxFrames OBJECT-TYPE 1011 SYNTAX ZeroBasedCounter32 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The total number of iFCP frames received by the gateway 1016 for this session." 1017 ::= {ifcpSessionLcStatsEntry 4} 1019 ifcpSessionLcStaleFrames OBJECT-TYPE 1020 SYNTAX ZeroBasedCounter32 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The total number of received iFCP frames that were stale and 1025 discarded by the gateway for this session." 1026 ::= {ifcpSessionLcStatsEntry 5} 1028 ifcpSessionLcHeaderCRCErrors OBJECT-TYPE 1029 SYNTAX ZeroBasedCounter32 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "The total number of CRC errors that occurred in the frame 1034 header, detected by the gateway for this session. Usually, 1035 a single Header CRC error is sufficient to terminate an 1036 iFCP session." 1037 ::= {ifcpSessionLcStatsEntry 6} 1039 ifcpSessionLcFcPayloadCRCErrors OBJECT-TYPE 1041 Gibbons Expires April 2006 20 1042 SYNTAX ZeroBasedCounter32 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "The total number of CRC errors that occurred in the Fibre 1047 Channel frame payload, detected by the gateway for this 1048 session." 1049 ::= {ifcpSessionLcStatsEntry 7} 1051 ifcpSessionLcOtherErrors OBJECT-TYPE 1052 SYNTAX ZeroBasedCounter32 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "The total number of errors, other than errors explicitly 1057 measured, detected by the gateway for this session." 1058 ::= {ifcpSessionLcStatsEntry 8} 1060 --========================================================== 1062 ifcpCompliances 1063 OBJECT IDENTIFIER ::= {ifcpGatewayConformance 1} 1065 ifcpGatewayCompliance MODULE-COMPLIANCE 1066 STATUS current 1067 DESCRIPTION 1068 "Implementation requirements for iFCP MIB compliance." 1069 MODULE -- this module 1070 MANDATORY-GROUPS { 1071 ifcpLclGatewayGroup, 1072 ifcpLclGatewaySessionGroup, 1073 ifcpLclGatewaySessionStatsGroup, 1074 ifcpLclGatewaySessionLcStatsGroup 1075 } 1076 ::= {ifcpCompliances 1} 1078 ifcpGroups OBJECT IDENTIFIER ::= {ifcpGatewayConformance 2} 1080 ifcpLclGatewayGroup OBJECT-GROUP 1081 OBJECTS { 1082 ifcpLclGtwyInstPhyIndex, 1083 ifcpLclGtwyInstVersionMin, 1084 ifcpLclGtwyInstVersionMax, 1085 ifcpLclGtwyInstAddrTransMode, 1086 ifcpLclGtwyInstFcBrdcstSupport, 1087 ifcpLclGtwyInstDefaultIpTOV, 1088 ifcpLclGtwyInstDefaultLTInterval, 1089 ifcpLclGtwyInstDescr, 1090 ifcpLclGtwyInstNumActiveSessions, 1091 ifcpLclGtwyInstStorageType 1092 } 1093 STATUS current 1095 Gibbons Expires April 2006 21 1096 DESCRIPTION 1097 "iFCP local device info group. This group provides 1098 information about each gateway." 1099 ::= {ifcpGroups 1} 1101 ifcpLclGatewaySessionGroup OBJECT-GROUP 1102 OBJECTS { 1103 ifcpSessionLclPrtlIfIndex, 1104 ifcpSessionLclPrtlAddrType, 1105 ifcpSessionLclPrtlAddr, 1106 ifcpSessionLclPrtlTcpPort, 1107 ifcpSessionLclNpWwun, 1108 ifcpSessionLclNpFcid, 1109 ifcpSessionRmtNpWwun, 1110 ifcpSessionRmtPrtlIfAddrType, 1111 ifcpSessionRmtPrtlIfAddr, 1112 ifcpSessionRmtPrtlTcpPort, 1113 ifcpSessionRmtNpFcid, 1114 ifcpSessionRmtNpFcidAlias, 1115 ifcpSessionIpTOV, 1116 ifcpSessionLclLTIntvl, 1117 ifcpSessionRmtLTIntvl, 1118 ifcpSessionBound, 1119 ifcpSessionStorageType 1120 } 1121 STATUS current 1122 DESCRIPTION 1123 "iFCP Session group. This group provides information 1124 about each iFCP session currently active between iFCP 1125 gateways." 1126 ::= {ifcpGroups 4} 1128 ifcpLclGatewaySessionStatsGroup OBJECT-GROUP 1129 OBJECTS { 1130 ifcpSessionState, 1131 ifcpSessionDuration, 1132 ifcpSessionTxOctets, 1133 ifcpSessionRxOctets, 1134 ifcpSessionTxFrames, 1135 ifcpSessionRxFrames, 1136 ifcpSessionStaleFrames, 1137 ifcpSessionHeaderCRCErrors, 1138 ifcpSessionFcPayloadCRCErrors, 1139 ifcpSessionOtherErrors, 1140 ifcpSessionDiscontinuityTime 1141 } 1142 STATUS current 1143 DESCRIPTION 1144 "iFCP Session Statistics group. This group provides 1145 statistics with 64 bit counters for each iFCP session 1146 currently active between iFCP gateways. This group 1147 is only required for agents that can support Counter64 1149 Gibbons Expires April 2006 22 1150 based data types." 1151 ::= {ifcpGroups 5} 1153 ifcpLclGatewaySessionLcStatsGroup OBJECT-GROUP 1154 OBJECTS { 1155 ifcpSessionLcTxOctets, 1156 ifcpSessionLcRxOctets, 1157 ifcpSessionLcTxFrames, 1158 ifcpSessionLcRxFrames, 1159 ifcpSessionLcStaleFrames, 1160 ifcpSessionLcHeaderCRCErrors, 1161 ifcpSessionLcFcPayloadCRCErrors, 1162 ifcpSessionLcOtherErrors 1163 } 1164 STATUS current 1165 DESCRIPTION 1166 "iFCP Session Low Capacity Statistics group. This group 1167 provides statistics with low capacity 32 bit counters 1168 for each iFCP session currently active between iFCP 1169 gateways. This group is only required for agents which 1170 do not support Counter64 based data types, or need to 1171 support SNMPv1 applications." 1172 ::= {ifcpGroups 6} 1174 END 1176 5. IANA Considerations 1178 IANA is requested to make a unique MIB OID assignment under the 1179 transmission branch. 1181 6. Security Considerations 1183 There are a number of management objects defined in this MIB module 1184 with a MAX-ACCESS clause of read-write and/or read-create. Such 1185 objects may be considered sensitive or vulnerable in some network 1186 environments. The support for SET operations in a non-secure 1187 environment without proper protection can have a negative effect on 1188 network operations. 1190 Changing the following object values, with a MAX-ACCESS of read- 1191 write, may cause disruption in storage traffic: 1192 ifcpLclGtwyInstAddrTransMode 1193 ifcpLclGtwyInstFcBrdcstSupport 1194 ifcpLclGtwyInstDefaultIpTOV 1195 ifcpLclGtwyInstDefaultLTInterval 1196 ifcpSessionIpTOV 1198 Changing the following object value, with a MAX-ACCESS of read- 1199 write, may cause a user to lose track of the iFCP gateway: 1200 ifcpLclGtwyInstDescr 1202 Gibbons Expires April 2006 23 1203 Some of the readable objects in this MIB module (i.e., objects with 1204 a MAX-ACCESS other than not-accessible) may be considered sensitive 1205 or vulnerable in some network environments. It is thus important to 1206 control even GET and/or NOTIFY access to these objects and possibly 1207 to even encrypt the values of these objects when sending them over 1208 the network via SNMP. 1210 The following object tables provide information about storage 1211 traffic sessions, and can indicate to a user who is communicating 1212 and exchanging storage data: 1213 ifcpLclGtwyInstTable 1214 ifcpSessionAttributesTable 1216 SNMP versions prior to SNMPv3 did not include adequate security. 1217 Even if the network itself is secure (for example by using IPSec), 1218 even then, there is no control as to who on the secure network is 1219 allowed to access and GET/SET (read/change/create/delete) the 1220 objects in this MIB module. 1222 It is RECOMMENDED that implementers consider the security features 1223 as provided by the SNMPv3 framework (see [RFC3410], section 8), 1224 including full support for SNMPv3 cryptographic mechanisms (for 1225 authentication and privacy). 1227 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1228 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1229 enable cryptographic security. It is then a customer/operator 1230 responsibility to ensure that the SNMP entity giving access to an 1231 instance of this MIB module is properly configured to give access to 1232 the objects only to those principals (users) that have legitimate 1233 rights to indeed GET or SET (change/create/delete) them. 1235 7. Normative References 1237 [RFC2021] S. Waldbusser, "Remote Network Monitoring Management 1238 Information Base", RFC 2021, January 1997. 1240 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1241 J., Rose, M., and S. Waldbusser, "Structure of 1242 Management Information Version 2 (SMIv2)", STD 58, RFC 1243 2578, April 1999. 1245 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1246 J., Rose, M., and S. Waldbusser, "Textual Conventions 1247 for SMIv2", STD 58, RFC 2579, April 1999. 1249 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1250 J., Rose, M., and S. Waldbusser, "Conformance 1251 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1253 [RFC2856] A. Bierman, K. McCloghrie, "Textual Conventions for 1254 Additional High Capacity Data Types", RFC 2021, June 1256 Gibbons Expires April 2006 24 1257 2000. 1259 [RFC2863] K. McCloghrie, and F. Kastenholz, "The Interfaces Group 1260 MIB", RFC 2863, June 2000. 1262 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1263 Architecture for Describing Simple Network Management 1264 Protocol (SNMP) Management Frameworks", STD 62, RFC 1265 3411, December 2002. 1267 [RFC4001] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder 1268 "Textual Conventions for Internet Network Addresses", 1269 RFC 4001, February 2005. 1271 [RFC4044] McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, 1272 May 2005. 1274 [RFC4133] Bierman, A., and McCloghrie, K., "Entity MIB (Version 1275 3)", RFC 4133, August 2005. 1277 [RFC4172] Charles Monia, Rod Mullendore, Franco Travostino, 1278 Wayland Jeong, Mark Edwards, "iFCP - A Protocol for 1279 Internet Fibre Channel Storage Networking", RFC 4172, 1280 September 2005. 1282 8. Informative References 1284 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1285 "Introduction and Applicability Statements for 1286 Internet-Standard Management Framework", RFC 3410, 1287 December 2002. 1289 9. Authors' Addresses 1291 Kevin Gibbons 1292 McDATA Corporation 1293 4555 Great America Pkwy 1294 Santa Clara, CA 95054-1208 USA 1295 Phone: (408)567-5765 1296 EMail: kevin.gibbons@mcdata.com 1298 Charles Monia 1299 Consultant 1300 7553 Morevern Circle 1301 San Jose, CA 95135 USA 1302 EMail: charles_monia@yahoo.com 1304 Josh Tseng 1305 Riverbed Technology 1306 501 2nd Street, Suite 410 1307 San Francisco, CA 94107 USA 1308 Phone: (650)274-2109 1310 Gibbons Expires April 2006 25 1311 EMail: joshtseng@yahoo.com 1313 Franco Travostino 1314 Nortel 1315 600 Technology Park Drive 1316 Billerica, MA 01821 USA 1317 Phone: (978)288-7708 1318 EMail: travos@nortel.com 1320 10. Intellectual Property Statement 1322 The IETF takes no position regarding the validity or scope of any 1323 Intellectual Property Rights or other rights that might be claimed 1324 to pertain to the implementation or use of the technology described 1325 in this document or the extent to which any license under such 1326 rights might or might not be available; nor does it represent that 1327 it has made any independent effort to identify any such rights. 1328 Information on the procedures with respect to rights in RFC 1329 documents can be found in BCP 78 and BCP 79. 1331 Copies of IPR disclosures made to the IETF Secretariat and any 1332 assurances of licenses to be made available, or the result of an 1333 attempt made to obtain a general license or permission for the use 1334 of such proprietary rights by implementers or users of this 1335 specification can be obtained from the IETF on-line IPR repository 1336 at http://www.ietf.org/ipr. 1338 The IETF invites any interested party to bring to its attention any 1339 copyrights, patents or patent applications, or other proprietary 1340 rights that may cover technology that may be required to implement 1341 this standard. Please address the information to the IETF at 1342 ietf-ipr@ietf.org. 1344 11. Full Copyright Statement 1346 Copyright (C) The Internet Society (2005). 1348 This document is subject to the rights, licenses and restrictions 1349 contained in BCP 78, and except as set forth therein, the authors 1350 retain all their rights. 1352 12. Disclaimer of Validity 1354 This document and the information contained herein are provided on 1355 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1356 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 1357 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 1358 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1359 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1360 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1362 Gibbons Expires April 2006 26 1363 13. Acknowledgment 1365 Funding for the RFC Editor function is currently provided by the 1366 Internet Society. 1368 Gibbons Expires April 2006 27