idnits 2.17.1 draft-ietf-ips-ifcp-mib-01.txt: -(72): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 19 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 824 has weird spacing: '... N Port group...' -- 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 (May 2002) is 8007 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2851' is defined on line 941, but no explicit reference was found in the text == Unused Reference: 'FCMGT01' is defined on line 936, but no explicit reference was found in the text == Unused Reference: 'T11FCGS3' is defined on line 939, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) -- Possible downref: Non-RFC (?) normative reference: ref. 'FCMGT01' -- Possible downref: Non-RFC (?) normative reference: ref. 'T11FCGS3' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 16 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Kevin Gibbons 3 Internet Draft Josh Tseng 4 Charles Monia 5 Expires: November 2002 Nishan Systems 7 Franco Travostino 8 Nortel 10 May 2002 12 Definitions of Managed Objects 13 For iFCP 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance 18 with all provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as "work 29 in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright Notice 39 Copyright (C) The Internet Society (2002). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base 44 (MIB) for use with network management protocols in the Internet 45 community. In particular, it defines a basic set of managed 46 objects for SNMP-based monitoring and management of the Internet 47 Fibre Channel Protocol (iFCP). 49 This memo specifies a MIB module in a manner that is compliant to 50 the SMIv2. The set of objects is consistent with the SNMP 51 framework and existing SNMP standards. 53 This memo is a product of the IP Storage (IPS) working group 55 Gibbons Expires November 2002 1 56 within the Internet Engineering Task Force. Comments are 57 solicited and should be addressed to the working group's mailing 58 list at ips@ece.cmu.edu and/or the authors. 60 Table of Contents 62 Status of this Memo................................................1 63 Copyright Notice...................................................1 64 Abstract...........................................................1 65 1. Introduction...................................................2 66 2. The SNMP Management Framework..................................2 67 3. Overview.......................................................3 68 4. Technical Description..........................................3 69 5. MIB Definition.................................................3 70 6. Security Considerations.......................................17 71 7. References....................................................17 72 8. Authors� Addresses............................................19 73 9. Full Copyright Statement......................................19 75 1. Introduction 77 The iFCP protocol provides Fibre Channel fabric functionality on 78 a IP network in which TCP/IP switching and routing elements 79 replace Fibre Channel components. This draft provides a 80 mechanism to manage an iFCP connection using SNMP. 82 2. The SNMP Management Framework 84 The SNMP Management Framework presently consists of five major 85 components: 87 o An overall architecture, described in RFC 2571 [RFC2571]. 89 o Mechanisms for describing and naming objects and events for 90 the purpose of management. The first version of this 91 Structure of Management Information (SMI) is called SMIv1 92 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 93 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 94 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 95 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 97 o Message protocols for transferring management information. 98 The first version of the SNMP message protocol is called 99 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 100 second version of the SNMP message protocol, which is not an 101 Internet standards track protocol, is called SNMPv2c and 102 described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The 103 third version of the message protocol is called SNMPv3 and 104 described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 105 2574 [RFC2574]. 107 o Protocol operations for accessing management information. 109 Gibbons Expires November 2002 2 110 The first set of protocol operations and associated PDU 111 formats is described in STD 15, RFC 1157 [RFC1157]. A 112 second set of protocol operations and associated PDU formats 113 is described in RFC 1905 [RFC1905]. 115 o A set of fundamental applications described in RFC 2573 116 [RFC2573] and the view-based access control mechanism 117 described in RFC 2575 [RFC2575]. 119 A more detailed introduction to the current SNMP Management 120 Framework can be found in RFC 2570 [RFC2570]. 122 Managed objects are accessed via a virtual information store, 123 termed the Management Information Base or MIB. Objects in the 124 MIB are defined using the mechanisms defined in the SMI. 126 This memo specifies a MIB module that is compliant to the SMIv2. 127 A MIB conforming to the SMIv1 can be produced through the 128 appropriate translations. The resulting translated MIB must be 129 semantically equivalent, except where objects or events are 130 omitted because no translation is possible (use of Counter64). 131 Some machine readable information in SMIv2 will be converted into 132 textual descriptions in SMIv1 during the translation process. 133 However, this loss of machine readable information is not 134 considered to change the semantics of the MIB. 136 3. Overview 138 The iFCP protocol can be used by IP based storage devices for FCP 139 compatible storage. The iFCP MIB is designed to allow SNMP to be 140 used to monitor and manage an iFCP gateway. 142 4. Technical Description 144 The MIB is divided into several sections for iFCP local device 145 and N Port information, remote iFCP device information, iFCP 146 sessions, and iFCP session statistics. 148 5. MIB Definition 150 IFCP-MGMT-MIB DEFINITIONS ::= BEGIN 151 -- 152 -- IETF iFCP Management Information Base (MIB) 153 -- 154 IMPORTS 155 MODULE-IDENTITY, 156 OBJECT-TYPE, 157 Counter32, 158 Counter64, 159 Integer32, 160 experimental 161 FROM SNMPv2-SMI 163 OBJECT-GROUP, 165 Gibbons Expires November 2002 3 166 MODULE-COMPLIANCE 167 FROM SNMPv2-CONF 169 TEXTUAL-CONVENTION 170 FROM SNMPv2-TC 172 -- From RFC 2851 173 InetAddressType, 174 InetAddress 175 FROM INET-ADDRESS-MIB 177 -- From IETF Fibre Channel Management MIB, RFC TBD 178 FcNameIdOrZero, -- WWN 179 FcAddressId -- FCID 180 FROM FC-MGMT-MIB 181 ; 183 ifcpMgmtMIB MODULE-IDENTITY 184 LAST-UPDATED "200205150000Z" 185 ORGANIZATION "IETF IPS Working Group" 186 CONTACT-INFO " 187 Attn: Kevin Gibbons 188 Nishan Systems 189 3850 North First Street 190 San Jose, CA 95134 191 USA 192 Tel : +1 408 519-3700 193 email : snmp@nishansystems.com 195 Josh Tseng 196 Nishan Systems 197 3850 North First Street 198 San Jose, CA 95134 199 USA 200 Tel : +1 408 519-3700 201 email : snmp@nishansystems.com 203 Charles Monia 204 Nishan Systems 205 3850 North First Street 206 San Jose, CA 95134 207 USA 208 Tel : +1 408 519-3700 209 email : snmp@nishansystems.com 211 Franco Travostino 212 Nortel Networks 213 3 Federal Street 214 Billerica, MA 01821 215 USA 216 Tel : +1 978 288-7708 217 email : travos@nortelnetworks.com 218 " 220 Gibbons Expires November 2002 4 221 DESCRIPTION "The MIB for internet Fibre Channel Protocol 222 (iFCP) management." 224 -- Revision History 225 REVISION "0111010000Z" 226 DESCRIPTION " v1.0 (11/01/01): 227 The first IPS standard track version. 228 " 230 REVISION "200205150000Z" 231 DESCRIPTION " v1.1 (5/15/02): 232 Updated references for FC ID and FC WWN. 233 Added REFERENCES 234 " 235 -- an IETF number has not yet been assigned 236 ::= {experimental 4371} 238 IfIndexType ::= TEXTUAL-CONVENTION 239 STATUS current 240 DESCRIPTION "Represents the possible interface indexes that 241 can be used on the iFCP device." 242 SYNTAX INTEGER (0..1024) 244 NportIdx ::= TEXTUAL-CONVENTION 245 STATUS current 246 DESCRIPTION "Represents the count of iFCP N Ports 247 supported." 248 SYNTAX INTEGER (0..4294967295) 250 IfcpVersionType ::= TEXTUAL-CONVENTION 251 STATUS current 252 DESCRIPTION "Represents the protocol version 253 supported." 254 SYNTAX INTEGER (0..4294967295) 256 PortType ::= TEXTUAL-CONVENTION 257 STATUS current 258 DESCRIPTION "Represents the TCP Port being used for 259 and iFCP connection." 260 SYNTAX INTEGER (0..65535) 262 IfcpSessionStateType ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION "Represents the iFCP session state." 265 SYNTAX INTEGER {down(0), openPending(1), open(2)} 267 -- 268 -- Internet Fibre Channel Protocol (iFCP) 269 -- 271 ifcpDeviceObj OBJECT IDENTIFIER ::= {ifcpMgmtMIB 1} 272 ifcpDeviceConformance OBJECT IDENTIFIER ::= {ifcpMgmtMIB 2} 274 -- 276 Gibbons Expires November 2002 5 277 -- iFCP Objects -------------------- 278 -- 280 ifcpLocalDeviceObjInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 1} 282 -- top-level object information here 284 ifcpVersionMin OBJECT-TYPE 285 SYNTAX IfcpVersionType 286 MAX-ACCESS read-only 287 STATUS current 288 DESCRIPTION 289 "The minimum iFCP protocol version supported by the local iFCP 290 device." 291 REFERENCE "draft-ietf-ips-ifcp-10.txt" 292 ::= {ifcpLocalDeviceObjInfo 1} 294 ifcpVersionMax OBJECT-TYPE 295 SYNTAX IfcpVersionType 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The maximum iFCP protocol version supported by the local iFCP 300 device." 301 REFERENCE "draft-ietf-ips-ifcp-10.txt" 302 ::= {ifcpLocalDeviceObjInfo 2} 304 ifcpNumNports OBJECT-TYPE 305 SYNTAX NportIdx 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The current total number of iFCP N Ports supported by the local 310 iFCP device." 311 ::= {ifcpLocalDeviceObjInfo 3} 313 -- 314 -- iFCP Local Interface Information 315 -- 317 ifcpLocalTcpIfTable OBJECT-TYPE 318 SYNTAX SEQUENCE OF IfcpLocalTcpIfEntry 319 MAX-ACCESS not-accessible 320 STATUS current 321 DESCRIPTION 322 "Information on the local interfaces available for iFCP connections, 323 including the TCP port used. The maximum number of entries is 324 based on the number of local interfaces and TCP ports configured 325 for iFCP connections." 326 ::= {ifcpLocalDeviceObjInfo 4} 328 ifcpLocalTcpIfEntry OBJECT-TYPE 329 SYNTAX IfcpLocalTcpIfEntry 330 MAX-ACCESS not-accessible 332 Gibbons Expires November 2002 6 333 STATUS current 334 DESCRIPTION 335 "Information on local TCP interfaces for iFCP connections." 336 INDEX {ifcpInterfaceIfIndex, ifcpInterfaceTcpPort} 337 ::= {ifcpLocalTcpIfTable 1} 339 IfcpLocalTcpIfEntry ::= SEQUENCE { 340 ifcpInterfaceIfIndex IfIndexType, 341 ifcpInterfaceTcpPort PortType, 342 ifcpInterfaceAddrType InetAddressType, 343 ifcpInterfaceAddr InetAddress 344 } 346 ifcpInterfaceIfIndex OBJECT-TYPE 347 SYNTAX IfIndexType 348 MAX-ACCESS not-accessible 349 STATUS current 350 DESCRIPTION 351 "This is an interface index for local device, as described in RFC 352 1213. This can be used as an ifTable index to obtain additional 353 information about the interface." 354 REFERENCE "MIB-II, RFC 1213" 355 ::= {ifcpLocalTcpIfEntry 1} 357 ifcpInterfaceTcpPort OBJECT-TYPE 358 SYNTAX PortType 359 MAX-ACCESS not-accessible 360 STATUS current 361 DESCRIPTION 362 "This is the TCP port number being used for iFCP access in this 363 interface." 364 ::= {ifcpLocalTcpIfEntry 2} 366 ifcpInterfaceAddrType OBJECT-TYPE 367 SYNTAX InetAddressType 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The type of address in ifcpInterfaceAddr." 372 ::= {ifcpLocalTcpIfEntry 3} 374 ifcpInterfaceAddr OBJECT-TYPE 375 SYNTAX InetAddress 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "This is the external address of the interface being used 380 for iFCP access. This address is consistent with the address 381 defined in the ifTable of RFC 1213 for this interface." 382 REFERENCE "MIB-II, RFC 1213" 383 ::= {ifcpLocalTcpIfEntry 4} 385 -- 386 -- iFCP Local Device N Port Information 388 Gibbons Expires November 2002 7 389 -- 391 ifcpLocalDeviceNportInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 2} 393 -- 394 -- iFCP N Port Table 395 -- 397 ifcpDeviceNportTable OBJECT-TYPE 398 SYNTAX SEQUENCE OF IfcpDeviceNportEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "Information on iFCP N Ports available in the device. This 403 table can be used to statically configure connections between 404 iFCP devices when a name service, such as the iSNS, is not 405 being used. The maximum number of entries is based on the 406 number of iFCP Ports supported." 407 ::= {ifcpLocalDeviceNportInfo 1} 409 ifcpDeviceNportEntry OBJECT-TYPE 410 SYNTAX IfcpDeviceNportEntry 411 MAX-ACCESS not-accessible 412 STATUS current 413 DESCRIPTION 414 "Information on iFCP N Port Entries in the Device ." 415 INDEX {ifcpDeviceNportWwpn} 416 ::= {ifcpDeviceNportTable 1} 418 IfcpDeviceNportEntry ::= SEQUENCE { 419 ifcpDeviceNportWwpn FcNameIdOrZero, 420 ifcpDeviceNportID FcAddressId, 421 ifcpDeviceNportIfIndex IfIndexType, 422 ifcpDeviceNportTcpPort PortType 423 } 425 ifcpDeviceNportWwpn OBJECT-TYPE 426 SYNTAX FcNameIdOrZero 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "The iFCP N Port World Wide Port Name as defined in the 431 iFCP Specification." 432 REFERENCE "draft-ietf-ips-ifcp-10.txt" 433 ::= {ifcpDeviceNportEntry 1} 435 ifcpDeviceNportID OBJECT-TYPE 436 SYNTAX FcAddressId 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The iFCP N Port, Port ID as defined in the iFCP Specification." 441 REFERENCE "draft-ietf-ips-ifcp-10.txt" 442 ::= {ifcpDeviceNportEntry 2} 444 Gibbons Expires November 2002 8 445 ifcpDeviceNportIfIndex OBJECT-TYPE 446 SYNTAX IfIndexType 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The interface that is being used for this N Port. This can be 451 used along with ifcpDeviceNportTcpPort to access the 452 ifcpLocalTcpIfTable." 453 ::= {ifcpDeviceNportEntry 3} 455 ifcpDeviceNportTcpPort OBJECT-TYPE 456 SYNTAX PortType 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The iFCP N Port TCP port number as defined in the 461 iFCP Specification. This is the port number used 462 to login to the N Port." 463 ::= {ifcpDeviceNportEntry 4} 465 -- 466 -- iFCP remote device information ------------------------------ 467 -- 469 ifcpRemoteDeviceObjInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 3} 471 -- 472 -- iFCP remote device table 473 -- 475 ifcpRemoteDeviceTable OBJECT-TYPE 476 SYNTAX SEQUENCE OF IfcpRemoteDeviceEntry 477 MAX-ACCESS not-accessible 478 STATUS current 479 DESCRIPTION 480 "Information on remote iFCP devices available for connections. 481 This table can be used to statically configure connections between 482 iFCP devices when a name service, such as the iSNS, is not 483 being used. The maximum number of entries is based on the 484 number of iFCP devices in the network." 485 ::= {ifcpRemoteDeviceObjInfo 1} 487 ifcpRemoteDeviceEntry OBJECT-TYPE 488 SYNTAX IfcpRemoteDeviceEntry 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "Information on remote iFCP devices." 493 INDEX {ifcpRemoteDeviceIndex} 494 ::= {ifcpRemoteDeviceTable 1} 496 IfcpRemoteDeviceEntry ::= SEQUENCE { 498 Gibbons Expires November 2002 9 499 ifcpRemoteDeviceIndex Integer32, 500 ifcpRemoteDeviceIfIndex IfIndexType, 501 ifcpRemoteDevicePort PortType, 502 ifcpRemoteDeviceAddrType InetAddressType, 503 ifcpRemoteDeviceAddr InetAddress, 504 ifcpRemoteDeviceMgtAddrType InetAddressType, 505 ifcpRemoteDeviceMgtAddr InetAddress, 506 ifcpRemoteDeviceVersionMin IfcpVersionType, 507 ifcpRemoteDeviceVersionMax IfcpVersionType 508 } 510 ifcpRemoteDeviceIndex OBJECT-TYPE 511 SYNTAX Integer32 ( 1 .. 2147483647 ) 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "The remote device iFCP interface index. This is a monotonically 516 increasing value used as an index to the table. The device index 517 is used because the length of ifcpRemoteDeviceAddr, 518 ifcpRemoteDeviceIfIndex and ifcpRemoteDevicePort combined would 519 be too long to be an index. This index and mappings to remote 520 devices may be reset when the local iFCP device is rebooted." 521 ::= {ifcpRemoteDeviceEntry 1} 523 ifcpRemoteDeviceIfIndex OBJECT-TYPE 524 SYNTAX IfIndexType 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "The remote device interface If Index. This can also be used to 529 index into the ifTable of RFC 1213 for the remote device to 530 obtain additional information about the interface." 531 REFERENCE "MIB-II, RFC 1213" 532 ::= {ifcpRemoteDeviceEntry 2} 534 ifcpRemoteDevicePort OBJECT-TYPE 535 SYNTAX PortType 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The iFCP N Port, Port ID as defined in the iFCP Specification." 540 REFERENCE "draft-ietf-ips-ifcp-10.txt" 541 ::= {ifcpRemoteDeviceEntry 3} 543 ifcpRemoteDeviceAddrType OBJECT-TYPE 544 SYNTAX InetAddressType 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "The type of address in ifcpRemoteDeviceAddr." 549 ::= {ifcpRemoteDeviceEntry 4} 551 ifcpRemoteDeviceAddr OBJECT-TYPE 552 SYNTAX InetAddress 554 Gibbons Expires November 2002 10 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "The address of the remote device interface." 559 ::= {ifcpRemoteDeviceEntry 5} 561 ifcpRemoteDeviceMgtAddrType OBJECT-TYPE 562 SYNTAX InetAddressType 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The type of address in ifcpRemoteDeviceMgtAddr." 567 ::= {ifcpRemoteDeviceEntry 6} 569 ifcpRemoteDeviceMgtAddr OBJECT-TYPE 570 SYNTAX InetAddress 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "The SNMP management address of the remote device interface." 575 ::= {ifcpRemoteDeviceEntry 7} 577 ifcpRemoteDeviceVersionMin OBJECT-TYPE 578 SYNTAX IfcpVersionType 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "The minimum iFCP protocol version supported by the remote iFCP 583 device. It is important that the protocol version of the local 584 and remote iFCP device be compatible." 585 ::= {ifcpRemoteDeviceEntry 8} 587 ifcpRemoteDeviceVersionMax OBJECT-TYPE 588 SYNTAX IfcpVersionType 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "The maximum iFCP protocol version supported by the remote iFCP 593 device. It is important that the protocol version of the local 594 and remote iFCP device be compatible." 595 ::= {ifcpRemoteDeviceEntry 9} 597 -- 598 -- iFCP N Port session information ------------------------------ 599 -- 601 ifcpNportSessionInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 4} 603 -- Session Attributes Table 605 ifcpSessionAttributesTable OBJECT-TYPE 606 SYNTAX SEQUENCE OF 607 IfcpSessionAttributesEntry 608 MAX-ACCESS not-accessible 610 Gibbons Expires November 2002 11 611 STATUS current 612 DESCRIPTION 613 "An iFCP session consists of the pair of N_PORTs comprising 614 the session endpoints joined by a single TCP/IP connection. 615 This table provides information on each session currently 616 communicating with the local device." 617 ::= {ifcpNportSessionInfo 1} 619 ifcpSessionAttributesEntry OBJECT-TYPE 620 SYNTAX IfcpSessionAttributesEntry 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "An entry in the session table." 625 INDEX {ifcpSessionIndex} 626 ::= {ifcpSessionAttributesTable 1} 628 IfcpSessionAttributesEntry ::= SEQUENCE { 629 ifcpSessionIndex Integer32, 630 ifcpSessionLocalNport FcNameIdOrZero, 631 ifcpSessionRemoteNport FcNameIdOrZero, 632 ifcpSessionLocalInterface INTEGER, 633 ifcpSessionRemoteInterface INTEGER 634 } 636 ifcpSessionIndex OBJECT-TYPE 637 SYNTAX Integer32 (1..2147483647) 638 MAX-ACCESS not-accessible 639 STATUS current 640 DESCRIPTION 641 "The iFCP session index. This is a monotonically increasing 642 value used as an index to the table. The session index may 643 change between local device reboots. The index was used because 644 ifcpSessionLocalNport and ifcpSessionRemoteNport would create an 645 index that would be difficult to implement." 646 ::= {ifcpSessionAttributesEntry 1} 648 ifcpSessionLocalNport OBJECT-TYPE 649 SYNTAX FcNameIdOrZero 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "World Wide Name of the local N Port." 654 ::= {ifcpSessionAttributesEntry 2} 656 ifcpSessionRemoteNport OBJECT-TYPE 657 SYNTAX FcNameIdOrZero 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "World Wide Name of the remote N Port." 662 ::= {ifcpSessionAttributesEntry 3} 664 ifcpSessionLocalInterface OBJECT-TYPE 666 Gibbons Expires November 2002 12 667 SYNTAX INTEGER (1..2147483647) 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The interface of the local device used for this session." 672 ::= {ifcpSessionAttributesEntry 4} 674 ifcpSessionRemoteInterface OBJECT-TYPE 675 SYNTAX INTEGER (1..2147483647) 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The interface of the remote device used for this session." 680 ::= {ifcpSessionAttributesEntry 5} 682 -- 683 -- Statistics 684 -- 686 ifcpSessionStatsTable OBJECT-TYPE 687 SYNTAX SEQUENCE OF IfcpSessionStatsEntry 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "This table provides information on an iFCP session." 692 ::= {ifcpNportSessionInfo 2} 694 ifcpSessionStatsEntry OBJECT-TYPE 695 SYNTAX IfcpSessionStatsEntry 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "iFCP specific statistics per session." 700 AUGMENTS {ifcpSessionAttributesEntry} 701 ::= {ifcpSessionStatsTable 1} 703 IfcpSessionStatsEntry ::= SEQUENCE { 704 ifcpSessionState IfcpSessionStateType, 705 ifcpSessionTxOctets Counter64, 706 ifcpSessionRxOctets Counter64, 707 ifcpSessionTxFrames Counter64, 708 ifcpSessionRxFrames Counter64, 709 ifcpSessionStaleFrames Counter32, 710 ifcpSessionHeaderCRCErrors Counter32, 711 ifcpSessionPayloadCRCErrors Counter32, 712 ifcpSessionOtherErrors Counter32 713 } 715 ifcpSessionState OBJECT-TYPE 716 SYNTAX IfcpSessionStateType 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "The current session operating state." 722 Gibbons Expires November 2002 13 723 ::= {ifcpSessionStatsEntry 1} 725 ifcpSessionTxOctets OBJECT-TYPE 726 SYNTAX Counter64 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "The total number of octets transmitted since the 731 connection was first established." 732 ::= {ifcpSessionStatsEntry 2} 734 ifcpSessionRxOctets OBJECT-TYPE 735 SYNTAX Counter64 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "The total number of octets received since the 740 connection was first established." 741 ::= {ifcpSessionStatsEntry 3} 743 ifcpSessionTxFrames OBJECT-TYPE 744 SYNTAX Counter64 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "The total number of frames transmitted since the 749 connection was first established." 750 ::= {ifcpSessionStatsEntry 4} 752 ifcpSessionRxFrames OBJECT-TYPE 753 SYNTAX Counter64 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The total number of frames received since the 758 connection was first established." 759 ::= {ifcpSessionStatsEntry 5} 761 ifcpSessionStaleFrames OBJECT-TYPE 762 SYNTAX Counter32 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The total number of received frames that were stale and 767 discarded since the connection was first established." 768 ::= {ifcpSessionStatsEntry 6} 770 ifcpSessionHeaderCRCErrors OBJECT-TYPE 771 SYNTAX Counter32 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The total number of CRC errors that occurred in the frame 776 header detected since the connection was first established." 778 Gibbons Expires November 2002 14 779 ::= {ifcpSessionStatsEntry 7} 781 ifcpSessionPayloadCRCErrors OBJECT-TYPE 782 SYNTAX Counter32 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION 786 "The total number of CRC errors that occurred in the frame 787 payload detected since the connection was first established." 788 ::= {ifcpSessionStatsEntry 8} 790 ifcpSessionOtherErrors OBJECT-TYPE 791 SYNTAX Counter32 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "The total number of errors, other then errors explicitly 796 measured, detected since the connection was first established." 797 ::= {ifcpSessionStatsEntry 9} 799 ------------------------------------------------------------ 801 ifcpGroups OBJECT IDENTIFIER ::= {ifcpDeviceConformance 1} 803 ifcpDeviceObjGroup OBJECT-GROUP 804 OBJECTS { 805 ifcpVersionMin, 806 ifcpVersionMax, 807 ifcpNumNports, 808 ifcpInterfaceAddrType, 809 ifcpInterfaceAddr 810 } 811 STATUS current 812 DESCRIPTION 813 "iFCP local device info group" 814 ::= {ifcpGroups 1} 816 ifcpDeviceNportGroup OBJECT-GROUP 817 OBJECTS { 818 ifcpDeviceNportID, 819 ifcpDeviceNportIfIndex, 820 ifcpDeviceNportTcpPort 821 } 822 STATUS current 823 DESCRIPTION 824 "iFCP local device N Port group" 825 ::= {ifcpGroups 2} 827 ifcpRemoteDeviceGroup OBJECT-GROUP 828 OBJECTS { 829 ifcpRemoteDeviceIfIndex, 830 ifcpRemoteDevicePort, 831 ifcpRemoteDeviceAddrType, 832 ifcpRemoteDeviceAddr, 834 Gibbons Expires November 2002 15 835 ifcpRemoteDeviceMgtAddrType, 836 ifcpRemoteDeviceMgtAddr, 837 ifcpRemoteDeviceVersionMin, 838 ifcpRemoteDeviceVersionMax 839 } 840 STATUS current 841 DESCRIPTION 842 "iFCP local device N Port node group" 843 ::= {ifcpGroups 3} 845 ifcpDeviceSessionGroup OBJECT-GROUP 846 OBJECTS { 847 ifcpSessionLocalNport, 848 ifcpSessionRemoteNport, 849 ifcpSessionLocalInterface, 850 ifcpSessionRemoteInterface 851 } 852 STATUS current 853 DESCRIPTION 854 "iFCP Session group" 855 ::= {ifcpGroups 4} 857 ifcpDeviceSessionStatsGroup OBJECT-GROUP 858 OBJECTS { 859 ifcpSessionState, 860 ifcpSessionTxOctets, 861 ifcpSessionRxOctets, 862 ifcpSessionTxFrames, 863 ifcpSessionRxFrames, 864 ifcpSessionStaleFrames, 865 ifcpSessionHeaderCRCErrors, 866 ifcpSessionPayloadCRCErrors, 867 ifcpSessionOtherErrors 868 } 869 STATUS current 870 DESCRIPTION 871 "iFCP Session Statistics group" 872 ::= {ifcpGroups 5} 874 ifcpCompliances OBJECT IDENTIFIER ::= {ifcpDeviceConformance 2} 876 ifcpDeviceComplianceV1 MODULE-COMPLIANCE 877 STATUS current 878 DESCRIPTION 879 "Initial compliance statement for an iFCP device." 880 MODULE -- this module 881 MANDATORY-GROUPS { 882 ifcpDeviceObjGroup, 883 ifcpDeviceNportGroup, 884 ifcpDeviceSessionGroup, 885 ifcpDeviceSessionStatsGroup 886 } 887 ::= {ifcpCompliances 1} 889 Gibbons Expires November 2002 16 890 END 892 6. Security Considerations 894 There are a number of management objects defined in this MIB that 895 have a MAX-ACCESS clause of read-write and/or read-create. Such 896 objects may be considered sensitive or vulnerable in some network 897 environments. The support for SET operations in a non-secure 898 environment without proper protection can have a negative effect 899 on network operations. 901 SNMPv1 by itself is not a secure environment. Even if the 902 network itself is secure (for example by using IPSec), even then, 903 there is no control as to who on the secure network is allowed to 904 access and GET/SET (read/change/create/delete) the objects in 905 this MIB. 907 It is recommended that the implementers consider the security 908 features as provided by the SNMPv3 framework. Specifically, the 909 use of the User-based Security Model RFC 2574 [RFC2574] and the 910 View-based Access Control Model RFC 2575 [RFC2575] is 911 recommended. 913 It is then a customer/user responsibility to ensure that the SNMP 914 entity giving access to an instance of this MIB, is properly 915 configured to give access to the objects only to those principals 916 (users) that have legitimate rights to indeed GET or SET 917 (change/create/delete) them. 919 7. References 921 [ifcp001] Charles Monia, Rod Mullendore, Josh Tseng, Franco 922 Travostino, David Robinson, Wayland Jeong, Rory Bolt, 923 Mark Edwards, "iFCP - A Protocol for Internet Fibre 924 Channel Storage Networking", , Expires August 2002 927 [isns001] Josh Tseng, Kevin Gibbons, Franco Travostino, Charles 928 Monia, Curt Du Laney, "iSNS Internet Storage Name 929 Service", , Expires November 930 2002 932 [RFC2851] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder 933 "Textual Conventions for Internet Network Addresses", 934 RFC 2851, June 2000. 936 [FCMGT01] K. McCloghrie, "Fibre Channel Management MIB ", , Expires August 2002. 939 [T11FCGS3] Fibre Channel - Generic Services 3, NCITS 348-2000. 941 [RFC2851] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder 942 "Textual Conventions for Internet Network Addresses", 943 RFC 2851, June 2000. 945 Gibbons Expires November 2002 17 947 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 948 Architecture for Describing SNMP Management Frameworks", 949 RFC 2571, April 1999. 951 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 952 Identification of Management Information for TCP/IP- 953 based Internets", STD 16, RFC 1155, May 1990. 955 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 956 STD 16, RFC 1212, March 1991. 958 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 959 the SNMP", RFC 1215, March 1991. 961 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 962 J., Rose, M., and S. Waldbusser, "Structure of 963 Management Information Version 2 (SMIv2)", STD 58, RFC 964 2578, April 1999. 966 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 967 J., Rose, M., and S. Waldbusser, "Textual Conventions 968 for SMIv2", STD 58, RFC 2579, April 1999. 970 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 971 J., Rose, M., and S. Waldbusser, "Conformance Statements 972 for SMIv2", STD 58, RFC 2580, April 1999. 974 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 975 "Simple Network Management Protocol", STD 15, RFC 1157, 976 May 1990. 978 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 979 "Introduction to Community-based SNMPv2", RFC 1901, 980 January 1996. 982 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 983 "Transport Mappings for Version 2 of the Simple Network 984 Management Protocol (SNMPv2)", RFC 1906, January 1996. 986 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 987 "Message Processing and Dispatching for the Simple 988 Network Management Protocol (SNMP)", RFC 2572, April 989 1999. 991 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 992 Model (USM) for version 3 of the Simple Network 993 Management Protocol (SNMPv3)", RFC 2574, April 1999. 995 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 996 "Protocol Operations for Version 2 of the Simple Network 997 Management Protocol (SNMPv2)", RFC 1905, January 1996. 999 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1001 Gibbons Expires November 2002 18 1002 Applications", RFC 2573, April 1999. 1004 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1005 Access Control Model (VACM) for the Simple Network 1006 Management Protocol (SNMP)", RFC 2575, April 1999. 1008 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1009 "Introduction to Version 3 of the Internet-standard 1010 Network Management Framework", RFC 2570, April 1999. 1012 8. Authors� Addresses 1014 Josh Tseng 1015 Kevin Gibbons 1016 Charles Monia 1017 Postal: Nishan Systems 1018 3850 North First Street 1019 San Jose, CA 95134-1702 1020 USA 1022 Tel: (408) 519-3756 1023 Fax: (408) 519-3705 1025 E-mail: snmp@NishanSystems.com 1027 Franco Travostino 1028 Nortel Networks 1029 3 Federal Street 1030 Billerica, MA 01821 1031 USA 1033 Tel: (978) 288-7708 1035 E-mail: travos@nortelnetworks.com 1037 9. Full Copyright Statement 1039 "Copyright (C) The Internet Society 2001. All Rights Reserved. 1040 This document and translations of it may be copied and furnished 1041 to others, and derivative works that comment on or otherwise 1042 explain it or assist in its implementation may be prepared, 1043 copied, published and distributed, in whole or in part, without 1044 restriction of any kind, provided that the above copyright notice 1045 and this paragraph are included on all such copies and derivative 1046 works. However, this document itself may not be modified in any 1047 way, such as by removing the copyright notice or references to 1048 the Internet Society or other Internet organizations, except as 1049 needed for the purpose of developing Internet standards in which 1050 case the procedures for copyrights defined in the Internet 1051 Standards process must be followed, or as required to translate 1052 it into languages other than English. 1054 The limited permissions granted above are perpetual and will not 1055 be revoked by the Internet Society or its successors or assigns. 1057 Gibbons Expires November 2002 19 1058 This document and the information contained herein is provided on 1059 An "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1060 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1061 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1062 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1063 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1064 PURPOSE." 1066 Gibbons Expires November 2002 20