idnits 2.17.1 draft-ietf-storm-ifcpmib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 indicate that this document obsoletes RFC4369, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 17, 2010) is 4908 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 4133 (Obsoleted by RFC 6933) ** Obsolete normative reference: RFC 4369 (Obsoleted by RFC 6173) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Prakash Venkatesen, Editor 2 STORM Working Group HCL Technologies 3 Intended status: Proposed Standard November 17, 2010 4 Expires: May 2011 5 Obsoletes: 4369 7 Definitions of Managed Objects for Internet Fibre Channel Protocol 8 (iFCP) 9 draft-ietf-storm-ifcpmib-07.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This Internet-Draft will expire on May 17, 2011. 34 Copyright Notice 36 Copyright (c) 2010 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 This document may contain material from IETF Documents or IETF 50 Contributions published or made publicly available before November 51 10, 2008. The person(s) controlling the copyright in some of this 52 material may not have granted the IETF Trust the right to allow 53 modifications of such material outside the IETF Standards Process. 54 Without obtaining an adequate license from the person(s) controlling 55 the copyright in such materials, this document may not be modified 56 outside the IETF Standards Process, and derivative works of it may 57 not be created outside the IETF Standards Process, except to format 58 it for publication as an RFC or to translate it into languages other 59 than English. 61 Abstract 63 This document defines Management Information Base (MIB) objects to 64 monitor and control iFCP Gateway instances and their associated 65 sessions, for use with network management protocols. 67 This document obsoletes RFC4369. 69 Table of Contents 71 1. The Internet-Standard Management Framework.....................2 72 2. Introduction...................................................3 73 3. Technical Description..........................................4 74 4. Differences from RFC 4369......................................5 75 5. MIB Definition.................................................5 76 6. Security Considerations.......................................27 77 7. IANA Considerations...........................................28 78 8. References....................................................29 79 8.1. Normative References.....................................29 80 8.2. Informative References...................................30 81 9. Acknowledgments...............................................30 83 1. The Internet-Standard Management Framework 85 For a detailed overview of the documents that describe the current 86 Internet-Standard Management Framework, please refer to section 7 of 87 RFC 3410 [RFC3410]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. MIB objects are generally 91 accessed through the Simple Network Management Protocol (SNMP). 93 Objects in the MIB are defined using the mechanisms defined in the 94 Structure of Management Information (SMI). This memo specifies a MIB 95 module that is compliant to the SMIv2, which is described in STD 58, 96 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 97 [RFC2580]. 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in [RFC2119]. 103 2. Introduction 105 The iFCP protocol (RFC 4172 [RFC4172]) provides Fibre Channel fabric 106 functionality on an IP network in which TCP/IP switching and routing 107 elements replace Fibre Channel components. The iFCP protocol is used 108 between iFCP Gateways. This protocol can be used by FC-to-IP-based 109 storage gateways for Fibre Channel Protocol (FCP) storage 110 interconnects. 112 Figure 1 provides an example of an interconnect between iFCP 113 gateways. 115 Gateway Region Gateway Region 116 +--------+ +--------+ +--------+ +--------+ 117 | FC | | FC | | FC | | FC | 118 | Device | | Device | | Device | | Device | Fibre 119 |........| |........| FC |........| |........| Channel 120 | N_PORT | | N_PORT |<.........>| N_PORT | | N_PORT | Device 121 +---+----+ +---+----+ Traffic +----+---+ +----+---+ Domain 122 | | | | ^ 123 +---+----+ +---+----+ +----+---+ +----+---+ | 124 | F_PORT | | F_PORT | | F_PORT | | F_PORT | | 125 =+========+==+========+===========+========+==+========+========== 126 | iFCP Layer |<--------->| iFCP Layer | | 127 |....................| ^ |....................| | 128 | iFCP Portal | | | iFCP Portal | v 129 +--------+-----------+ | +----------+---------+ IP 130 iFCP|Gateway Control iFCP|Gateway Network 131 | Data | 132 | | 133 | | 134 |<------Encapsulated Frames------->| 135 | +------------------+ | 136 | | | | 137 +------+ IP Network +--------+ 138 | | 139 +------------------+ 140 Figure 1: Interconnect between iFCP Gateways 142 The iFCP MIB Module is designed to allow a network management 143 protocol such as SNMP to be used to monitor and manage local iFCP 144 gateway instances, including the configuration of iFCP sessions 145 between gateways. 147 3. Technical Description 149 The iFCP MIB Module is divided into sections for iFCP local gateway 150 instance management, iFCP session management, and iFCP session 151 statistics. 153 The section for iFCP gateway management provides default settings and 154 information about each local instance. A single management entity 155 can monitor multiple local gateway instances. Each local gateway is 156 conceptually an independent gateway that has both Fibre Channel and 157 IP interfaces. The default IP Time Out Value (IP_TOV) is 158 configurable for each gateway. Other standard MIBs, such as the 159 Fibre Management MIB [RFC4044] or Interfaces Group MIB [RFC2863], can 160 be used to manage non-iFCP-specific gateway parameters. The local 161 gateway instance section provides iFCP-specific information as well 162 as optional links to other standard management MIBs. 164 The iFCP session management section provides information on iFCP 165 sessions that use one of the local iFCP gateway instances. This 166 section allows the management of specific iFCP parameters, including 167 changing the IP_TOV from the default setting of the gateway. 169 The iFCP session statistics section provides statistical information 170 on the iFCP sessions that use one of the local iFCP gateways. These 171 tables augment the session management table. Additional statistical 172 information for an iFCP gateway or session, that is not 173 iFCP-specific, can be obtained using other standard MIBs. The iFCP 174 statistics are provided in both high-capacity (Counter64) and low- 175 capacity (Counter32) methods. 177 The following MIB module imports from SNMPv2-SMI [RFC2578], SNMPv2- 178 TC [RFC2579], SNMPv2-CONF [RFC2580], HCNUM-TC [RFC2856], IF-MIB 179 [RFC2863], SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001], 180 FC-MGMT-MIB [RFC4044], ENTITY-MIB (v3)[RFC4133] and RMON2-MIB 181 [RFC4502]. 183 4. Differences from RFC 4369 185 As explained in [RFCyyyy], the iFCP address translation mode is 187 (Note to the RFC Editor: replace yyyy with the RFC number assigned to 188 draft-ietf-storm-ifcp-ipn133-updates & remove this note.) 190 deprecated. This document obsoletes the iFCP MIB module [RFC4369] 191 for this change. 193 5. MIB Definition 195 IFCP-MGMT-MIB DEFINITIONS ::= BEGIN 197 IMPORTS 198 MODULE-IDENTITY, 199 OBJECT-TYPE, 200 Gauge32, 201 Integer32, 202 Unsigned32, 203 transmission 204 FROM SNMPv2-SMI 206 OBJECT-GROUP, 207 MODULE-COMPLIANCE 208 FROM SNMPv2-CONF 210 TEXTUAL-CONVENTION, 211 TimeStamp, 212 TruthValue, 213 StorageType 214 FROM SNMPv2-TC 216 -- From RFC 4502 217 ZeroBasedCounter32 218 FROM RMON2-MIB 220 -- From RFC 2856 221 ZeroBasedCounter64 222 FROM HCNUM-TC 224 -- From RFC 2863 225 InterfaceIndexOrZero 226 FROM IF-MIB 228 -- From RFC 3411 229 SnmpAdminString 230 FROM SNMP-FRAMEWORK-MIB 232 -- From RFC 4001 233 InetAddressType, 234 InetAddress, 235 InetPortNumber 236 FROM INET-ADDRESS-MIB 238 -- From RFC 4044 239 FcNameIdOrZero, 240 FcAddressIdOrZero 241 FROM FC-MGMT-MIB 243 -- From RFC 4133 244 PhysicalIndexOrZero 245 FROM ENTITY-MIB 246 ; 248 ifcpMgmtMIB MODULE-IDENTITY 249 LAST-UPDATED "201010250000Z" 250 ORGANIZATION "IETF STORage Maintenance (STORM) Working Group" 251 CONTACT-INFO " 252 Working Group Email : storm@ietf.org 253 Attn: Prakash Venkatesen 254 HCL Technologies 255 Email: prakashvn@hcl.com" 257 DESCRIPTION 258 "This module defines management information specific 259 to internet Fibre Channel Protocol (iFCP) gateway 260 management. 262 Copyright (C) The IETF Trust (2010). This 263 version of this MIB module is part of RFC xxxx; 264 see the RFC itself for full legal notices." 265 -- RFC Editor: replace xxxx with actual RFC number & remove this note. 267 REVISION "201010250000Z" 268 DESCRIPTION 269 "Second version of iFCP Management Module. The iFCP 270 address translation mode is deprecated. 271 This MIB module published as RFC xxxx." 272 -- RFC Editor: replace xxxx with actual RFC number & remove this note. 273 REVISION "200601170000Z" 274 DESCRIPTION 275 "Initial version of iFCP Management Module. 276 This MIB module published as RFC 4369." 277 ::= { transmission 230 } 279 -- 280 -- Textual Conventions 281 -- 283 IfcpIpTOVorZero ::= TEXTUAL-CONVENTION 284 DISPLAY-HINT "d" 285 STATUS current 286 DESCRIPTION "The maximum propagation delay, in seconds, 287 for an encapsulated FC frame to traverse the 288 IP network. A value of 0 implies fibre 289 channel frame lifetime limits will not be 290 enforced." 291 REFERENCE "RFC 4172, iFCP Protocol Specification" 292 SYNTAX Unsigned32 (0..3600) 294 IfcpLTIorZero ::= TEXTUAL-CONVENTION 295 DISPLAY-HINT "d" 296 STATUS current 297 DESCRIPTION "The value for the Liveness Test Interval 298 (LTI) being used in an iFCP connection, in 299 seconds. A value of 0 implies no Liveness 300 Test Interval will be used." 301 REFERENCE "RFC 4172, iFCP Protocol Specification" 302 SYNTAX Unsigned32 (0..65535) 304 IfcpSessionStates ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION "The value for an iFCP session state." 307 SYNTAX INTEGER {down(1), openPending(2), open(3)} 309 IfcpAddressMode ::= TEXTUAL-CONVENTION 310 STATUS current 311 DESCRIPTION "The values for iFCP Address Translation 312 Mode." 313 REFERENCE "RFC yyyy, Updates to the iFCP Protocol and 314 Internet Protocol Number 133 " 315 -- RFC Editor: replace yyyy with the RFC number assigned to 316 -- draft-ietf-storm-ifcp-ipn133-updates & remove this note. 317 SYNTAX INTEGER {addressTransparent(1), 318 addressTranslation(2)} 320 -- 321 -- Internet Fibre Channel Protocol (iFCP) 322 -- 323 ifcpGatewayObjects OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1} 324 ifcpGatewayConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2} 325 -- 326 -- Local iFCP Gateway Instance Information ================== 327 -- 329 ifcpLclGatewayInfo OBJECT IDENTIFIER ::= {ifcpGatewayObjects 1} 331 ifcpLclGtwyInstTable OBJECT-TYPE 332 SYNTAX SEQUENCE OF IfcpLclGtwyInstEntry 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "Information about all local iFCP Gateway instances that can 337 be monitored and controlled. This table contains an entry 338 for each local iFCP Gateway instance that is being managed." 339 ::= {ifcpLclGatewayInfo 1} 341 ifcpLclGtwyInstEntry OBJECT-TYPE 342 SYNTAX IfcpLclGtwyInstEntry 343 MAX-ACCESS not-accessible 344 STATUS current 345 DESCRIPTION 346 "An entry in the local iFCP Gateway Instance table. 347 Parameters and settings for the gateway are found here." 348 INDEX { ifcpLclGtwyInstIndex } 349 ::= {ifcpLclGtwyInstTable 1} 351 IfcpLclGtwyInstEntry ::= SEQUENCE { 352 ifcpLclGtwyInstIndex Unsigned32, 353 ifcpLclGtwyInstPhyIndex PhysicalIndexOrZero, 354 ifcpLclGtwyInstVersionMin Unsigned32, 355 ifcpLclGtwyInstVersionMax Unsigned32, 356 ifcpLclGtwyInstAddrTransMode IfcpAddressMode, 357 ifcpLclGtwyInstFcBrdcstSupport TruthValue, 358 ifcpLclGtwyInstDefaultIpTOV IfcpIpTOVorZero, 359 ifcpLclGtwyInstDefaultLTInterval IfcpLTIorZero, 360 ifcpLclGtwyInstDescr SnmpAdminString, 361 ifcpLclGtwyInstNumActiveSessions Gauge32, 362 ifcpLclGtwyInstStorageType StorageType 363 } 365 ifcpLclGtwyInstIndex OBJECT-TYPE 366 SYNTAX Unsigned32 (1..2147483647) 367 MAX-ACCESS not-accessible 368 STATUS current 369 DESCRIPTION 370 "An arbitrary integer value to uniquely identify this iFCP 371 Gateway from other local Gateway instances." 372 ::= {ifcpLclGtwyInstEntry 1} 374 ifcpLclGtwyInstPhyIndex OBJECT-TYPE 375 SYNTAX PhysicalIndexOrZero 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "An index indicating the location of this local gateway within 380 a larger entity, if one exists. If supported, this is the 381 entPhysicalIndex from the Entity MIB (Version 3), for this 382 iFCP Gateway. If not supported, or if not related to a 383 physical entity, then the value of this object is 0." 384 REFERENCE "Entity MIB (Version 3)" 385 ::= {ifcpLclGtwyInstEntry 2} 387 ifcpLclGtwyInstVersionMin OBJECT-TYPE 388 SYNTAX Unsigned32 (0..255) 389 MAX-ACCESS read-only 390 STATUS current 391 DESCRIPTION 392 "The minimum iFCP protocol version supported by the local iFCP 393 gateway instance." 394 REFERENCE "RFC 4172, iFCP Protocol Specification" 395 ::= {ifcpLclGtwyInstEntry 3} 397 ifcpLclGtwyInstVersionMax OBJECT-TYPE 398 SYNTAX Unsigned32 (0..255) 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The maximum iFCP protocol version supported by the local iFCP 403 gateway instance." 404 REFERENCE "RFC 4172, iFCP Protocol Specification" 405 ::= {ifcpLclGtwyInstEntry 4} 407 ifcpLclGtwyInstAddrTransMode OBJECT-TYPE 408 SYNTAX IfcpAddressMode 409 MAX-ACCESS read-write 410 STATUS current 411 DESCRIPTION 412 "The local iFCP gateway operating mode. Changing this value 413 may cause existing sessions to be disrupted." 414 REFERENCE "RFC 4172, iFCP Protocol Specification; 415 RFC yyyy, Updates to the iFCP Protocol and 416 Internet Protocol Number 133 " 417 -- RFC Editor: replace yyyy with the RFC number assigned to 418 -- draft-ietf-storm-ifcp-ipn133-updates & remove this note. 420 DEFVAL { addressTransparent } 421 ::= {ifcpLclGtwyInstEntry 5} 423 ifcpLclGtwyInstFcBrdcstSupport OBJECT-TYPE 424 SYNTAX TruthValue 425 MAX-ACCESS read-write 426 STATUS current 427 DESCRIPTION 428 "Whether the local iFCP gateway supports FC Broadcast. 429 Changing this value may cause existing sessions to be 430 disrupted." 431 REFERENCE "RFC 4172, iFCP Protocol Specification" 432 DEFVAL { false } 433 ::= {ifcpLclGtwyInstEntry 6} 435 ifcpLclGtwyInstDefaultIpTOV OBJECT-TYPE 436 SYNTAX IfcpIpTOVorZero 437 UNITS "seconds" 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "The default IP_TOV used for iFCP sessions at this gateway. 442 This is the default maximum propagation delay that will be 443 used for an iFCP session. The value can be changed on a 444 per-session basis. The valid range is 0 - 3600 seconds. 445 A value of 0 implies that fibre channel frame lifetime limits 446 will not be enforced." 447 REFERENCE "RFC 4172, iFCP Protocol Specification" 448 DEFVAL { 6 } 449 ::= {ifcpLclGtwyInstEntry 7} 451 ifcpLclGtwyInstDefaultLTInterval OBJECT-TYPE 452 SYNTAX IfcpLTIorZero 453 UNITS "seconds" 454 MAX-ACCESS read-write 455 STATUS current 456 DESCRIPTION 457 "The default Liveness Test Interval (LTI), in seconds, used 458 for iFCP sessions at this gateway. This is the default 459 value for an iFCP session and can be changed on a 460 per-session basis. The valid range is 0 - 65535 seconds. 461 A value of 0 implies no Liveness Test Interval will be 462 performed on a session." 463 REFERENCE "RFC 4172, iFCP Protocol Specification" 464 DEFVAL { 10 } 465 ::= {ifcpLclGtwyInstEntry 8} 467 ifcpLclGtwyInstDescr OBJECT-TYPE 468 SYNTAX SnmpAdminString (SIZE (0..64)) 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "A user-entered description for this iFCP Gateway." 473 DEFVAL { "" } 474 ::= {ifcpLclGtwyInstEntry 9} 476 ifcpLclGtwyInstNumActiveSessions OBJECT-TYPE 477 SYNTAX Gauge32 (0..4294967295) 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The current total number of iFCP sessions in the open or 482 open-pending state." 483 ::= {ifcpLclGtwyInstEntry 10} 485 ifcpLclGtwyInstStorageType OBJECT-TYPE 486 SYNTAX StorageType 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The storage type for this row. Parameter values defined 491 for a gateway are usually non-volatile, but may be volatile 492 or permanent in some configurations. If permanent, then 493 the following parameters must have read-write access: 494 ifcpLclGtwyInstAddrTransMode, ifcpLclGtwyInstDefaultIpTOV, 495 and ifcpLclGtwyInstDefaultLTInterval." 496 DEFVAL { nonVolatile } 497 ::= {ifcpLclGtwyInstEntry 11} 499 -- 500 -- iFCP N Port Session Information ============================ 501 -- 503 ifcpNportSessionInfo 504 OBJECT IDENTIFIER ::= {ifcpGatewayObjects 2} 506 ifcpSessionAttributesTable OBJECT-TYPE 507 SYNTAX SEQUENCE OF 508 IfcpSessionAttributesEntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 "An iFCP session consists of the pair of N_PORTs comprising 513 the session endpoints joined by a single TCP/IP connection. 514 This table provides information on each iFCP session 515 currently using a local iFCP Gateway instance. iFCP sessions 516 are created and removed by the iFCP Gateway instances, which 517 are reflected in this table." 518 ::= {ifcpNportSessionInfo 1} 520 ifcpSessionAttributesEntry OBJECT-TYPE 521 SYNTAX IfcpSessionAttributesEntry 522 MAX-ACCESS not-accessible 523 STATUS current 524 DESCRIPTION 525 "Each entry contains information about one iFCP session consisting 526 of a pair of N_PORTs joined by a single TCP/IP connection. This 527 table's INDEX includes ifcpLclGtwyInstIndex, which identifies the 528 local iFCP Gateway instance that created the session for the 529 entry. 531 Soon after an entry is created in this table for an iFCP session, it 532 will correspond to an entry in the tcpConnectionTable of the TCP-MIB 533 (RFC 4022). The corresponding entry might represent a preexisting 534 TCP connection, or it might be a newly-created entry. (Note that if 535 IPv4 is being used, an entry in RFC 2012's tcpConnTable may also 536 correspond.) The values of ifcpSessionLclPrtlAddrType and 537 ifcpSessionRmtPrtlIfAddrType in this table and the values of 538 tcpConnectionLocalAddressType and tcpConnectionRemAddressType used 539 as INDEX values for the corresponding entry in the 540 tcpConnectionTable should be the same; this makes it simpler to 541 locate a session's TCP connection in the TCP-MIB. (Of course, all 542 four values need to be 'ipv4' if there's a corresponding entry in 543 the tcpConnTable.) 545 If an entry is created in this table for a session, prior to 546 knowing which local and/or remote port numbers will be used for 547 the TCP connection, then ifcpSessionLclPrtlTcpPort and/or 548 ifcpSessionRmtPrtlTcpPort have the value zero until such time as 549 they can be updated to the port numbers (to be) used for the 550 connection. (Thus, a port value of zero should not be used to 551 locate a session's TCP connection in the TCP-MIB.) 553 When the TCP connection terminates, the entry in the 554 tcpConnectionTable and the entry in this table both get deleted 555 (and, if applicable, so does the entry in the tcpConnTable)." 556 INDEX { ifcpLclGtwyInstIndex, ifcpSessionIndex } 557 ::= {ifcpSessionAttributesTable 1} 559 IfcpSessionAttributesEntry ::= SEQUENCE { 560 ifcpSessionIndex Integer32, 561 ifcpSessionLclPrtlIfIndex InterfaceIndexOrZero, 562 ifcpSessionLclPrtlAddrType InetAddressType, 563 ifcpSessionLclPrtlAddr InetAddress, 564 ifcpSessionLclPrtlTcpPort InetPortNumber, 565 ifcpSessionLclNpWwun FcNameIdOrZero, 566 ifcpSessionLclNpFcid FcAddressIdOrZero, 567 ifcpSessionRmtNpWwun FcNameIdOrZero, 568 ifcpSessionRmtPrtlIfAddrType InetAddressType, 569 ifcpSessionRmtPrtlIfAddr InetAddress, 570 ifcpSessionRmtPrtlTcpPort InetPortNumber, 571 ifcpSessionRmtNpFcid FcAddressIdOrZero, 572 ifcpSessionRmtNpFcidAlias FcAddressIdOrZero, 573 ifcpSessionIpTOV IfcpIpTOVorZero, 574 ifcpSessionLclLTIntvl IfcpLTIorZero, 575 ifcpSessionRmtLTIntvl IfcpLTIorZero, 576 ifcpSessionBound TruthValue, 577 ifcpSessionStorageType StorageType 578 } 580 ifcpSessionIndex OBJECT-TYPE 581 SYNTAX Integer32 (1..2147483647) 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "The iFCP session index is a unique value used as an index 586 to the table, along with a specific local iFCP Gateway 587 instance. This index is used because the local N Port and 588 remote N Port information would create an complex index that 589 would be difficult to implement." 590 ::= {ifcpSessionAttributesEntry 1} 592 ifcpSessionLclPrtlIfIndex OBJECT-TYPE 593 SYNTAX InterfaceIndexOrZero 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "This is the interface index in the IF-MIB ifTable being used 598 as the local portal in this session, as described in the 599 IF-MIB. If the local portal is not associated with an entry 600 in the ifTable, then the value is 0. The ifType of the 601 interface will generally be a type that supports IP, but an 602 implementation may support iFCP using other protocols. This 603 object can be used to obtain additional information about the 604 interface." 605 REFERENCE "RFC 2863, The Interfaces Group MIB (IF-MIB)" 606 ::= {ifcpSessionAttributesEntry 2} 608 ifcpSessionLclPrtlAddrType OBJECT-TYPE 609 SYNTAX InetAddressType 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The type of address in ifcpSessionLclIfAddr." 614 ::= {ifcpSessionAttributesEntry 3} 616 ifcpSessionLclPrtlAddr OBJECT-TYPE 617 SYNTAX InetAddress 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "This is the external IP address of the interface being used 622 for the iFCP local portal in this session. The address type 623 is defined in ifcpSessionLclPrtlAddrType. If the value is a 624 DNS name, then the name is resolved once, during the initial 625 session instantiation." 626 ::= {ifcpSessionAttributesEntry 4} 628 ifcpSessionLclPrtlTcpPort OBJECT-TYPE 629 SYNTAX InetPortNumber 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "This is the TCP port number that is being used for the iFCP 634 local portal in this session. This is normally an ephemeral 635 port number selected by the gateway. The value may be 0 636 during an initial setup period." 637 ::= {ifcpSessionAttributesEntry 5} 639 ifcpSessionLclNpWwun OBJECT-TYPE 640 SYNTAX FcNameIdOrZero 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "World Wide Unique Name of the local N Port. For an unbound 645 session, this variable will be a zero-length string." 646 REFERENCE "RFC 4172, iFCP Protocol Specification" 647 DEFVAL { "" } 648 ::= {ifcpSessionAttributesEntry 6} 650 ifcpSessionLclNpFcid OBJECT-TYPE 651 SYNTAX FcAddressIdOrZero 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "Fibre Channel Identifier of the local N Port. For an unbound 656 session, this variable will be a zero-length string." 657 REFERENCE "RFC 4172, iFCP Protocol Specification" 658 ::= {ifcpSessionAttributesEntry 7} 660 ifcpSessionRmtNpWwun OBJECT-TYPE 661 SYNTAX FcNameIdOrZero 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 666 "World Wide Unique Name of the remote N Port. For an unbound 667 session, this variable will be a zero-length string." 668 REFERENCE "RFC 4172, iFCP Protocol Specification" 669 DEFVAL { "" } 670 ::= {ifcpSessionAttributesEntry 8} 672 ifcpSessionRmtPrtlIfAddrType OBJECT-TYPE 673 SYNTAX InetAddressType 674 MAX-ACCESS read-only 675 STATUS current 676 DESCRIPTION 677 "The type of address in ifcpSessionRmtPrtlIfAddr." 678 ::= {ifcpSessionAttributesEntry 9} 680 ifcpSessionRmtPrtlIfAddr OBJECT-TYPE 681 SYNTAX InetAddress 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "This is the remote gateway IP address being used for the 686 portal on the remote iFCP gateway. The address type is 687 defined in ifcpSessionRmtPrtlIfAddrType. If the value is a 688 DNS name, then the name is resolved once, during the initial 689 session instantiation." 690 ::= {ifcpSessionAttributesEntry 10} 692 ifcpSessionRmtPrtlTcpPort OBJECT-TYPE 693 SYNTAX InetPortNumber 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "This is the TCP port number being used for the portal on the 698 remote iFCP gateway. Generally, this will be the iFCP 699 canonical port. The value may be 0 during an initial setup 700 period." 701 DEFVAL { 3420 } 702 ::= {ifcpSessionAttributesEntry 11} 704 ifcpSessionRmtNpFcid OBJECT-TYPE 705 SYNTAX FcAddressIdOrZero 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "Fibre Channel Identifier of the remote N Port. For an 710 unbound session, this variable will be a zero-length string." 711 REFERENCE "RFC 4172, iFCP Protocol Specification" 712 ::= {ifcpSessionAttributesEntry 12} 714 ifcpSessionRmtNpFcidAlias OBJECT-TYPE 715 SYNTAX FcAddressIdOrZero 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "Fibre Channel Identifier Alias assigned by the local gateway 720 for the remote N Port. For an unbound session, this variable 721 will be a zero-length string." 722 REFERENCE "RFC 4172, iFCP Protocol Specification" 723 ::= {ifcpSessionAttributesEntry 13} 725 ifcpSessionIpTOV OBJECT-TYPE 726 SYNTAX IfcpIpTOVorZero 727 UNITS "seconds" 728 MAX-ACCESS read-write 729 STATUS current 730 DESCRIPTION 731 "The IP_TOV being used for this iFCP session. This is the 732 maximum propagation delay that will be used for the iFCP 733 session. The value can be changed on a per-session basis 734 and initially defaults to ifcpLclGtwyInstDefaultIpTOV for 735 the local gateway instance. The valid range is 0 - 3600 736 seconds. A value of 0 implies fibre channel frame lifetime 737 limits will not be enforced." 738 REFERENCE "RFC 4172, iFCP Protocol Specification" 739 ::= {ifcpSessionAttributesEntry 14} 741 ifcpSessionLclLTIntvl OBJECT-TYPE 742 SYNTAX IfcpLTIorZero 743 UNITS "seconds" 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The Liveness Test Interval (LTI) used for this iFCP session. 748 The value can be changed on a per-session basis and initially 749 defaults to ifcpLclGtwyInstDefaultLTInterval for the local 750 gateway instance. The valid range is 0 - 65535 seconds. 751 A value of 0 implies that the gateway will not originate 752 Liveness Test messages for the session." 753 REFERENCE "RFC 4172, iFCP Protocol Specification" 754 ::= {ifcpSessionAttributesEntry 15} 756 ifcpSessionRmtLTIntvl OBJECT-TYPE 757 SYNTAX IfcpLTIorZero 758 UNITS "seconds" 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The Liveness Test Interval (LTI) as requested by the remote 763 gateway instance to use for this iFCP session. This value may 764 change over the life of the session. The valid range is 0 - 765 65535 seconds. A value of 0 implies that the remote gateway 766 has not been requested to originate Liveness Test messages for 767 the session." 768 REFERENCE "RFC 4172, iFCP Protocol Specification" 769 ::= {ifcpSessionAttributesEntry 16} 771 ifcpSessionBound OBJECT-TYPE 772 SYNTAX TruthValue 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "This value indicates whether this session is bound to a 777 specific local and remote N Port. Sessions by default are 778 unbound and ready for future assignment to a local and remote 779 N Port." 780 REFERENCE "RFC 4172, iFCP Protocol Specification" 781 ::= {ifcpSessionAttributesEntry 17} 783 ifcpSessionStorageType OBJECT-TYPE 784 SYNTAX StorageType 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The storage type for this row. Parameter values defined 789 for a session are usually non-volatile, but may be volatile 790 or permanent in some configurations. If permanent, then 791 ifcpSessionIpTOV must have read-write access." 792 DEFVAL { nonVolatile } 793 ::= {ifcpSessionAttributesEntry 18} 795 -- 796 -- Local iFCP Gateway Instance Session Statistics ============= 797 -- 799 ifcpSessionStatsTable OBJECT-TYPE 800 SYNTAX SEQUENCE OF 801 IfcpSessionStatsEntry 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "This table provides statistics on an iFCP session." 806 ::= {ifcpNportSessionInfo 2} 808 ifcpSessionStatsEntry OBJECT-TYPE 809 SYNTAX IfcpSessionStatsEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 814 "Provides iFCP-specific statistics per session." 815 AUGMENTS {ifcpSessionAttributesEntry} 816 ::= {ifcpSessionStatsTable 1} 818 IfcpSessionStatsEntry ::= SEQUENCE { 819 ifcpSessionState IfcpSessionStates, 820 ifcpSessionDuration Unsigned32, 821 ifcpSessionTxOctets ZeroBasedCounter64, 822 ifcpSessionRxOctets ZeroBasedCounter64, 823 ifcpSessionTxFrames ZeroBasedCounter64, 824 ifcpSessionRxFrames ZeroBasedCounter64, 825 ifcpSessionStaleFrames ZeroBasedCounter64, 826 ifcpSessionHeaderCRCErrors ZeroBasedCounter64, 827 ifcpSessionFcPayloadCRCErrors ZeroBasedCounter64, 828 ifcpSessionOtherErrors ZeroBasedCounter64, 829 ifcpSessionDiscontinuityTime TimeStamp 830 } 832 ifcpSessionState OBJECT-TYPE 833 SYNTAX IfcpSessionStates 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "The current session operating state." 838 ::= {ifcpSessionStatsEntry 1} 840 ifcpSessionDuration OBJECT-TYPE 841 SYNTAX Unsigned32 (0..4294967295) 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "This indicates, in seconds, how long the iFCP session has 846 been in an open or open-pending state. When a session is 847 down, the value is reset to 0." 848 ::= {ifcpSessionStatsEntry 2} 850 ifcpSessionTxOctets OBJECT-TYPE 851 SYNTAX ZeroBasedCounter64 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "The total number of octets transmitted by the iFCP gateway 856 for this session. Discontinuities in the value of this 857 counter can occur at reinitialization of the management 858 system, and at other times as indicated by the value of 859 ifcpSessionDiscontinuityTime." 860 ::= {ifcpSessionStatsEntry 3} 862 ifcpSessionRxOctets OBJECT-TYPE 863 SYNTAX ZeroBasedCounter64 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "The total number of octets received by the iFCP gateway for 868 this session. Discontinuities in the value of this 869 counter can occur at reinitialization of the management 870 system, and at other times as indicated by the value of 871 ifcpSessionDiscontinuityTime." 872 ::= {ifcpSessionStatsEntry 4} 874 ifcpSessionTxFrames OBJECT-TYPE 875 SYNTAX ZeroBasedCounter64 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The total number of iFCP frames transmitted by the gateway 880 for this session. Discontinuities in the value of this 881 counter can occur at reinitialization of the management 882 system, and at other times as indicated by the value of 883 ifcpSessionDiscontinuityTime." 884 ::= {ifcpSessionStatsEntry 5} 886 ifcpSessionRxFrames OBJECT-TYPE 887 SYNTAX ZeroBasedCounter64 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "The total number of iFCP frames received by the gateway 892 for this session. Discontinuities in the value of this 893 counter can occur at reinitialization of the management 894 system, and at other times as indicated by the value of 895 ifcpSessionDiscontinuityTime." 896 ::= {ifcpSessionStatsEntry 6} 898 ifcpSessionStaleFrames OBJECT-TYPE 899 SYNTAX ZeroBasedCounter64 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The total number of received iFCP frames that were stale and 904 discarded by the gateway for this session. Discontinuities 905 in the value of this counter can occur at reinitialization 906 of the management system, and at other times as indicated by 907 the value of ifcpSessionDiscontinuityTime." 908 ::= {ifcpSessionStatsEntry 7} 910 ifcpSessionHeaderCRCErrors OBJECT-TYPE 911 SYNTAX ZeroBasedCounter64 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "The total number of CRC errors that occurred in the frame 916 header, detected by the gateway for this session. Usually, 917 a single Header CRC error is sufficient to terminate an 918 iFCP session. Discontinuities in the value of this 919 counter can occur at reinitialization of the management 920 system, and at other times as indicated by the value of 921 ifcpSessionDiscontinuityTime." 922 ::= {ifcpSessionStatsEntry 8} 924 ifcpSessionFcPayloadCRCErrors OBJECT-TYPE 925 SYNTAX ZeroBasedCounter64 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The total number of CRC errors that occurred in the Fibre 930 Channel frame payload, detected by the gateway for this 931 session. Discontinuities in the value of this counter can 932 occur at reinitialization of the management system, and 933 at other times as indicated by the value of 934 ifcpSessionDiscontinuityTime." 935 ::= {ifcpSessionStatsEntry 9} 937 ifcpSessionOtherErrors OBJECT-TYPE 938 SYNTAX ZeroBasedCounter64 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The total number of errors, other than errors explicitly 943 measured, detected by the gateway for this session. 944 Discontinuities in the value of this counter can occur at 945 reinitialization of the management system, and at other 946 times as indicated by the value of 947 ifcpSessionDiscontinuityTime." 948 ::= {ifcpSessionStatsEntry 10} 950 ifcpSessionDiscontinuityTime OBJECT-TYPE 951 SYNTAX TimeStamp 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "The value of sysUpTime on the most recent occasion at which 956 any one (or more) of the ifcpSessionStatsTable counters 957 suffered a discontinuity. The relevant counters are the 958 specific Counter64-based instances associated with the 959 ifcpSessionStatsTable: ifcpSessionTxOctets, 960 ifcpSessionRxOctets, ifcpSessionTxFrames, 961 ifcpSessionRxFrames, ifcpSessionStaleFrames, 962 ifcpSessionHeaderCRCErrors, ifcpSessionFcPayloadCRCErrors, 963 and ifcpSessionOtherErrors. If no such discontinuities have 964 occurred since the last reinitialization of the local 965 management subsystem, then this object contains a zero value." 966 ::= {ifcpSessionStatsEntry 11} 968 -- 969 -- Low Capacity Statistics 970 -- 972 ifcpSessionLcStatsTable OBJECT-TYPE 973 SYNTAX SEQUENCE OF 974 IfcpSessionLcStatsEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "This table provides low capacity statistics for an iFCP 979 session. These are provided for backward compatibility with 980 systems that do not support Counter64-based objects. At 981 1-Gbps rates, a Counter32-based object can wrap as often as 982 every 34 seconds. Counter32-based objects can be sufficient 983 for many situations. However, when possible, it is 984 recommended to use the high capacity statistics in 985 ifcpSessionStatsTable based on Counter64 objects." 986 ::= {ifcpNportSessionInfo 3} 988 ifcpSessionLcStatsEntry OBJECT-TYPE 989 SYNTAX IfcpSessionLcStatsEntry 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 "Provides iFCP-specific statistics per session." 994 AUGMENTS {ifcpSessionAttributesEntry} 995 ::= {ifcpSessionLcStatsTable 1} 997 IfcpSessionLcStatsEntry ::= SEQUENCE { 998 ifcpSessionLcTxOctets ZeroBasedCounter32, 999 ifcpSessionLcRxOctets ZeroBasedCounter32, 1000 ifcpSessionLcTxFrames ZeroBasedCounter32, 1001 ifcpSessionLcRxFrames ZeroBasedCounter32, 1002 ifcpSessionLcStaleFrames ZeroBasedCounter32, 1003 ifcpSessionLcHeaderCRCErrors ZeroBasedCounter32, 1004 ifcpSessionLcFcPayloadCRCErrors ZeroBasedCounter32, 1005 ifcpSessionLcOtherErrors ZeroBasedCounter32 1006 } 1007 ifcpSessionLcTxOctets OBJECT-TYPE 1008 SYNTAX ZeroBasedCounter32 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "The total number of octets transmitted by the iFCP gateway 1013 for this session." 1014 ::= {ifcpSessionLcStatsEntry 1} 1016 ifcpSessionLcRxOctets OBJECT-TYPE 1017 SYNTAX ZeroBasedCounter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "The total number of octets received by the iFCP gateway for 1022 this session." 1023 ::= {ifcpSessionLcStatsEntry 2} 1025 ifcpSessionLcTxFrames OBJECT-TYPE 1026 SYNTAX ZeroBasedCounter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The total number of iFCP frames transmitted by the gateway 1031 for this session." 1032 ::= {ifcpSessionLcStatsEntry 3} 1034 ifcpSessionLcRxFrames OBJECT-TYPE 1035 SYNTAX ZeroBasedCounter32 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The total number of iFCP frames received by the gateway 1040 for this session." 1041 ::= {ifcpSessionLcStatsEntry 4} 1043 ifcpSessionLcStaleFrames OBJECT-TYPE 1044 SYNTAX ZeroBasedCounter32 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The total number of received iFCP frames that were stale and 1049 discarded by the gateway for this session." 1050 ::= {ifcpSessionLcStatsEntry 5} 1052 ifcpSessionLcHeaderCRCErrors OBJECT-TYPE 1053 SYNTAX ZeroBasedCounter32 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The total number of CRC errors that occurred in the frame 1058 header, detected by the gateway for this session. Usually, 1059 a single Header CRC error is sufficient to terminate an 1060 iFCP session." 1061 ::= {ifcpSessionLcStatsEntry 6} 1063 ifcpSessionLcFcPayloadCRCErrors OBJECT-TYPE 1064 SYNTAX ZeroBasedCounter32 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The total number of CRC errors that occurred in the Fibre 1069 Channel frame payload, detected by the gateway for this 1070 session." 1071 ::= {ifcpSessionLcStatsEntry 7} 1073 ifcpSessionLcOtherErrors OBJECT-TYPE 1074 SYNTAX ZeroBasedCounter32 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The total number of errors, other than errors explicitly 1079 measured, detected by the gateway for this session." 1080 ::= {ifcpSessionLcStatsEntry 8} 1082 --========================================================== 1084 ifcpCompliances 1085 OBJECT IDENTIFIER ::= {ifcpGatewayConformance 1} 1087 ifcpGatewayCompliance MODULE-COMPLIANCE 1088 STATUS deprecated 1089 DESCRIPTION 1090 "This MODULE-COMPLIANCE has been deprecated because address 1091 translation mode has been deprecated in the iFCP standard. It has 1092 the implementation requirements for iFCP MIB module compliance." 1093 MODULE -- this module 1094 MANDATORY-GROUPS { 1095 ifcpLclGatewayGroup, 1096 ifcpLclGatewaySessionGroup, 1097 ifcpLclGatewaySessionStatsGroup, 1098 ifcpLclGatewaySessionLcStatsGroup 1099 } 1101 OBJECT ifcpSessionLclPrtlAddrType 1102 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1103 DESCRIPTION 1104 "Support is only required for global IPv4 1105 and IPv6 address types." 1107 OBJECT ifcpSessionRmtPrtlIfAddrType 1108 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1109 DESCRIPTION 1110 "Support is only required for global IPv4 1111 and IPv6 address types." 1113 OBJECT ifcpLclGtwyInstAddrTransMode 1114 SYNTAX IfcpAddressMode {addressTransparent(1), 1115 addressTranslation(2)} 1116 DESCRIPTION 1117 "This object must support addressTransparent(1) and 1118 addressTranslation(2)." 1120 ::= {ifcpCompliances 1} 1122 ifcpGatewayComplianceNoTranslation MODULE-COMPLIANCE 1123 STATUS current 1124 DESCRIPTION 1125 "Implementation requirements for iFCP MIB module compliance. 1126 Address translation mode has been deprecated in the iFCP standard." 1127 REFERENCE "RFC 4172, iFCP Protocol Specification; 1128 RFC yyyy, Updates to the iFCP Protocol and 1129 Internet Protocol Number 133 " 1130 -- RFC Editor: replace yyyy with the RFC number assigned to 1131 -- draft-ietf-storm-ifcp-ipn133-updates & remove this note. 1133 MODULE -- this module 1134 MANDATORY-GROUPS { 1135 ifcpLclGatewayGroup, 1136 ifcpLclGatewaySessionGroupNoTranslation, 1137 ifcpLclGatewaySessionStatsGroup, 1138 ifcpLclGatewaySessionLcStatsGroup 1139 } 1141 OBJECT ifcpSessionLclPrtlAddrType 1142 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1143 DESCRIPTION 1144 "Support is only required for global IPv4 1145 and IPv6 address types." 1147 OBJECT ifcpSessionRmtPrtlIfAddrType 1148 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 1149 DESCRIPTION 1150 "Support is only required for global IPv4 1151 and IPv6 address types." 1153 OBJECT ifcpLclGtwyInstAddrTransMode 1154 SYNTAX IfcpAddressMode {addressTransparent(1)} 1155 DESCRIPTION 1156 "Support is only required for addressTransparent(1)." 1158 ::= {ifcpCompliances 2} 1160 ifcpGroups OBJECT IDENTIFIER ::= {ifcpGatewayConformance 2} 1162 ifcpLclGatewayGroup OBJECT-GROUP 1163 OBJECTS { 1164 ifcpLclGtwyInstPhyIndex, 1165 ifcpLclGtwyInstVersionMin, 1166 ifcpLclGtwyInstVersionMax, 1167 ifcpLclGtwyInstAddrTransMode, 1168 ifcpLclGtwyInstFcBrdcstSupport, 1169 ifcpLclGtwyInstDefaultIpTOV, 1170 ifcpLclGtwyInstDefaultLTInterval, 1171 ifcpLclGtwyInstDescr, 1172 ifcpLclGtwyInstNumActiveSessions, 1173 ifcpLclGtwyInstStorageType 1174 } 1175 STATUS current 1176 DESCRIPTION 1177 "iFCP local device info group. This group provides 1178 information about each gateway." 1179 ::= {ifcpGroups 1} 1181 ifcpLclGatewaySessionGroup OBJECT-GROUP 1182 OBJECTS { 1183 ifcpSessionLclPrtlIfIndex, 1184 ifcpSessionLclPrtlAddrType, 1185 ifcpSessionLclPrtlAddr, 1186 ifcpSessionLclPrtlTcpPort, 1187 ifcpSessionLclNpWwun, 1188 ifcpSessionLclNpFcid, 1189 ifcpSessionRmtNpWwun, 1190 ifcpSessionRmtPrtlIfAddrType, 1191 ifcpSessionRmtPrtlIfAddr, 1192 ifcpSessionRmtPrtlTcpPort, 1193 ifcpSessionRmtNpFcid, 1194 ifcpSessionRmtNpFcidAlias, 1195 ifcpSessionIpTOV, 1196 ifcpSessionLclLTIntvl, 1197 ifcpSessionRmtLTIntvl, 1198 ifcpSessionBound, 1199 ifcpSessionStorageType 1200 } 1201 STATUS deprecated 1202 DESCRIPTION 1203 "This OBJECT-GROUP has been deprecated because address translation 1204 mode has been deprecated in the iFCP standard. iFCP Session group. 1205 This group provides information about each iFCP session currently 1206 active between iFCP gateways." 1207 ::= {ifcpGroups 4} 1209 ifcpLclGatewaySessionStatsGroup OBJECT-GROUP 1210 OBJECTS { 1211 ifcpSessionState, 1212 ifcpSessionDuration, 1213 ifcpSessionTxOctets, 1214 ifcpSessionRxOctets, 1215 ifcpSessionTxFrames, 1216 ifcpSessionRxFrames, 1217 ifcpSessionStaleFrames, 1218 ifcpSessionHeaderCRCErrors, 1219 ifcpSessionFcPayloadCRCErrors, 1220 ifcpSessionOtherErrors, 1221 ifcpSessionDiscontinuityTime 1222 } 1223 STATUS current 1224 DESCRIPTION 1225 "iFCP Session Statistics group. This group provides 1226 statistics with 64-bit counters for each iFCP session 1227 currently active between iFCP gateways. This group 1228 is only required for agents that can support Counter64- 1229 based data types." 1230 ::= {ifcpGroups 5} 1232 ifcpLclGatewaySessionLcStatsGroup OBJECT-GROUP 1233 OBJECTS { 1234 ifcpSessionLcTxOctets, 1235 ifcpSessionLcRxOctets, 1236 ifcpSessionLcTxFrames, 1237 ifcpSessionLcRxFrames, 1238 ifcpSessionLcStaleFrames, 1239 ifcpSessionLcHeaderCRCErrors, 1240 ifcpSessionLcFcPayloadCRCErrors, 1241 ifcpSessionLcOtherErrors 1242 } 1243 STATUS current 1244 DESCRIPTION 1245 "iFCP Session Low Capacity Statistics group. This group 1246 provides statistics with low-capacity 32-bit counters 1247 for each iFCP session currently active between iFCP 1248 gateways. This group is only required for agents that 1249 do not support Counter64-based data types, or that need 1250 to support SNMPv1 applications." 1251 ::= {ifcpGroups 6} 1253 ifcpLclGatewaySessionGroupNoTranslation OBJECT-GROUP 1254 OBJECTS { 1255 ifcpSessionLclPrtlIfIndex, 1256 ifcpSessionLclPrtlAddrType, 1257 ifcpSessionLclPrtlAddr, 1258 ifcpSessionLclPrtlTcpPort, 1259 ifcpSessionLclNpWwun, 1260 ifcpSessionLclNpFcid, 1261 ifcpSessionRmtNpWwun, 1262 ifcpSessionRmtPrtlIfAddrType, 1263 ifcpSessionRmtPrtlIfAddr, 1264 ifcpSessionRmtPrtlTcpPort, 1265 ifcpSessionRmtNpFcid, 1266 ifcpSessionIpTOV, 1267 ifcpSessionLclLTIntvl, 1268 ifcpSessionRmtLTIntvl, 1269 ifcpSessionBound, 1270 ifcpSessionStorageType 1271 } 1272 STATUS current 1273 DESCRIPTION 1274 "iFCP Session group. This group provides information 1275 about each iFCP session currently active between iFCP 1276 gateways." 1277 ::= {ifcpGroups 7} 1279 END 1281 6. Security Considerations 1283 There are a number of management objects defined in this MIB module 1284 with a MAX-ACCESS clause of read-write and/or read-create. Such 1285 objects may be considered sensitive or vulnerable in some network 1286 environments. The support for SET operations in a non-secure 1287 environment without proper protection can have a negative effect on 1288 network operations. 1290 Changing the following object values, with a MAX-ACCESS of read- 1291 write, may cause disruption in storage traffic: 1293 ifcpLclGtwyInstAddrTransMode 1294 ifcpLclGtwyInstFcBrdcstSupport 1295 ifcpLclGtwyInstDefaultIpTOV 1296 ifcpLclGtwyInstDefaultLTInterval 1297 ifcpSessionIpTOV 1299 Changing the following object value, with a MAX-ACCESS of read-write, 1300 may cause a user to lose track of the iFCP gateway: 1302 ifcpLclGtwyInstDescr 1304 Some of the readable objects in this MIB module (i.e., objects with a 1305 MAX-ACCESS other than not-accessible) may be considered sensitive or 1306 vulnerable in some network environments. It is thus important to 1307 control even GET and/or NOTIFY access to these objects and possibly 1308 to even encrypt the values of these objects when sending them over 1309 the network via SNMP. 1311 The following object tables provide information about storage traffic 1312 sessions, and can indicate to a user who is communicating and 1313 exchanging storage data: 1315 ifcpLclGtwyInstTable 1316 ifcpSessionAttributesTable 1318 SNMP versions prior to SNMPv3 did not include adequate security. 1319 Even if the network itself is secure (for example by using IPsec), 1320 even then, there is no control as to who on the secure network is 1321 allowed to access and GET/SET (read/change/create/delete) the objects 1322 in this MIB module. 1324 It is RECOMMENDED that implementers consider the security features as 1325 provided by the SNMPv3 framework (see [RFC3410], section 8), 1326 including full support for SNMPv3 cryptographic mechanisms (for 1327 authentication and privacy). 1329 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1330 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1331 enable cryptographic security. It is then a customer/operator 1332 responsibility to ensure that the SNMP entity giving access to an 1333 instance of this MIB module is properly configured to give access to 1334 the objects only to those principals (users) that have legitimate 1335 rights to indeed GET or SET (change/create/delete) them. 1337 7. IANA Considerations 1339 The MIB module in this document uses the following IANA-assigned 1340 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1342 Descriptor OBJECT IDENTIFIER value 1343 ---------- ----------------------- 1344 ifcpMgmtMIB { transmission 230 } 1346 8. References 1348 8.1. Normative References 1350 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1351 Requirement Levels", BCP 14, RFC 2119, March 1997. 1353 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1354 "Structure of Management Information Version 2 (SMIv2)", 1355 STD 58, RFC 2578, April 1999. 1357 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1358 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1359 1999. 1361 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1362 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1363 April 1999. 1365 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 1366 Conventions for Additional High Capacity Data Types", RFC 1367 2856, June 2000. 1369 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1370 MIB", RFC 2863, June 2000. 1372 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1373 Architecture for Describing Simple Network Management 1374 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 1375 December 2002. 1377 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1378 Schoenwaelder, "Textual Conventions for Internet Network 1379 Addresses", RFC 4001, February 2005. 1381 [RFC4044] McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, 1382 May 2005. 1384 [RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", 1385 RFC 4133, August 2005. 1387 [RFC4172] Monia, C., Mullendore, R., Travostino, F., Jeong, W., and 1388 M. Edwards, "iFCP - A Protocol for Internet Fibre Channel 1389 Storage Networking", RFC 4172, September 2005. 1391 [RFC4369] Gibbons, K., Monia, C., Tseng, J. and Travostino, F, 1392 "Definitions of Managed Objects for Internet Fibre Channel 1393 Protocol (iFCP)", RFC 4369, January 2006. 1395 [RFC4502] Waldbusser, S., "Remote Network Monitoring Management 1396 Information Base Version 2", RFC 4502, May 2006. 1398 [RFCyyyy] Black, D. and D. Peterson, "Updates to the iFCP Protocol 1399 and Internet Protocol Number 133", RFC yyyy, mmyy 1400 (Note to the RFC Editor: please replace yyyy with the RFC number 1401 assigned to draft-ietf-storm-ifcp-ipn133-updates, replace mmyy 1402 with the RFC month and year assigned to 1403 draft-ietf-storm-ifcp-ipn133-updates & remove this note.) 1405 8.2. Informative References 1407 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1408 "Introduction and Applicability Statements for Internet- 1409 Standard Management Framework", RFC 3410, December 2002. 1411 9. Acknowledgments 1413 Credit goes to the authors of [RFC4369] for preparing the first version 1414 of the iFCP MIB module. I wish to thank David Black, Tom Talpey and 1415 David Harrington for their significant inputs on this update. 1417 Authors' Address 1419 Prakash Venkatesen 1420 HCL Technologies Ltd. 1421 50-53, Greams Road, 1422 Chennai - 600006 1423 India 1424 EMail: prakashvn@hcl.com 1426 Authors of RFC 4369: 1428 Kevin Gibbons 1429 2Wire Corporation 1430 1704 Automation Parkway 1431 San Jose, CA 95131 USA 1432 Phone: (408)895-1387 1433 EMail: kgibbons@yahoo.com 1434 Charles Monia 1435 Consultant 1436 7553 Morevern Circle 1437 San Jose, CA 95135 USA 1438 EMail: charles_monia@yahoo.com 1440 Josh Tseng 1441 Riverbed Technology 1442 501 2nd Street, Suite 410 1443 San Francisco, CA 94107 USA 1444 Phone: (650)274-2109 1445 EMail: joshtseng@yahoo.com 1447 Franco Travostino 1448 eBay Inc. 1449 2145 Hamilton Avenue 1450 San Jose, CA 95125 1451 EMail: travos@ieee.org