idnits 2.17.1 draft-ietf-ips-ifcp-mib-00.txt: -(82): 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 18 longer pages, the longest (page 2) being 71 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 516 has weird spacing: '...because the l...' == Line 822 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 (November 2001) is 8196 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 919, but no explicit reference was found in the text == Unused Reference: 'RFC2837' is defined on line 923, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) ** Obsolete normative reference: RFC 2837 (Obsoleted by RFC 4044) ** 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: 17 errors (**), 0 flaws (~~), 8 warnings (==), 2 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: May 2002 Nishan Systems 7 Franco Travostino 8 Nortel 10 November 2001 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 (2001). 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 May 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 64 Copyright Notice...................................................1 66 Abstract...........................................................1 68 1. Introduction...................................................2 70 2. The SNMP Management Framework..................................2 72 3. Overview.......................................................3 74 4. Technical Description..........................................3 76 5. MIB Definition.................................................3 78 6. Security Considerations.......................................16 80 7. References....................................................17 82 8. Authors� Addresses............................................18 84 9. Full Copyright Statement......................................19 86 1. Introduction 88 The iFCP protocol provides Fibre Channel fabric functionality on 89 a IP network in which TCP/IP switching and routing elements 90 replace Fibre Channel components. This draft provides a 91 mechanism to manage an iFCP connection using SNMP. 93 2. The SNMP Management Framework 95 The SNMP Management Framework presently consists of five major 96 components: 98 o An overall architecture, described in RFC 2571 [RFC2571]. 100 o Mechanisms for describing and naming objects and events for 101 the purpose of management. The first version of this 102 Structure of Management Information (SMI) is called SMIv1 103 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 104 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 105 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 106 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 108 o Message protocols for transferring management information. 109 The first version of the SNMP message protocol is called 110 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 111 second version of the SNMP message protocol, which is not an 112 Internet standards track protocol, is called SNMPv2c and 113 described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The 114 third version of the message protocol is called SNMPv3 and 115 described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 116 2574 [RFC2574]. 118 o Protocol operations for accessing management information. 120 Gibbons Expires May 2002 2 121 The first set of protocol operations and associated PDU 122 formats is described in STD 15, RFC 1157 [RFC1157]. A 123 second set of protocol operations and associated PDU formats 124 is described in RFC 1905 [RFC1905]. 126 o A set of fundamental applications described in RFC 2573 127 [RFC2573] and the view-based access control mechanism 128 described in RFC 2575 [RFC2575]. 130 A more detailed introduction to the current SNMP Management 131 Framework can be found in RFC 2570 [RFC2570]. 133 Managed objects are accessed via a virtual information store, 134 termed the Management Information Base or MIB. Objects in the 135 MIB are defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. 138 A MIB conforming to the SMIv1 can be produced through the 139 appropriate translations. The resulting translated MIB must be 140 semantically equivalent, except where objects or events are 141 omitted because no translation is possible (use of Counter64). 142 Some machine readable information in SMIv2 will be converted into 143 textual descriptions in SMIv1 during the translation process. 144 However, this loss of machine readable information is not 145 considered to change the semantics of the MIB. 147 3. Overview 149 The iFCP protocol can be used by IP based storage devices for FCP 150 compatible storage. The iFCP MIB is designed to allow SNMP to be 151 used to monitor and manage an iFCP gateway. 153 4. Technical Description 155 The MIB is divided into several sections for iFCP local device 156 and N Port information, remote iFCP device information, iFCP 157 sessions, and iFCP session statistics. 159 5. MIB Definition 161 IFCP-MIB DEFINITIONS ::= BEGIN 162 -- 163 -- iFCP.mib: IETF iFCP management information 164 -- base (MIB) 165 -- 166 IMPORTS 167 MODULE-IDENTITY, 168 OBJECT-TYPE, 169 Counter32, 170 Counter64, 171 experimental 172 FROM SNMPv2-SMI 174 OBJECT-GROUP, 176 Gibbons Expires May 2002 3 177 MODULE-COMPLIANCE 178 FROM SNMPv2-CONF 180 TEXTUAL-CONVENTION 181 FROM SNMPv2-TC 183 -- From rfc 2851 184 InetAddressType, 185 InetAddress 186 FROM INET-ADDRESS-MIB 188 -- From rfc 2837 189 FcNameId, 190 FcAddressId 191 FROM FIBRE-CHANNEL-FE-MIB 192 ; 194 ifcpModule MODULE-IDENTITY 195 LAST-UPDATED "0111010000Z" 196 ORGANIZATION "IETF IPS Working Group" 197 CONTACT-INFO " 198 Attn: Kevin Gibbons 199 Nishan Systems 200 3850 North First Street 201 San Jose, CA 95134 202 USA 203 Tel : +1 408 519-3700 204 email : snmp@nishansystems.com 206 Josh Tseng 207 Nishan Systems 208 3850 North First Street 209 San Jose, CA 95134 210 USA 211 Tel : +1 408 519-3700 212 email : snmp@nishansystems.com 214 Charles Monia 215 Nishan Systems 216 3850 North First Street 217 San Jose, CA 95134 218 USA 219 Tel : +1 408 519-3700 220 email : snmp@nishansystems.com 222 Franco Travostino 223 Nortel Networks 224 3 Federal Street 225 Billerica, MA 01821 226 USA 227 Tel : +1 978 288-7708 228 email : travos@nortelnetworks.com 229 " 231 Gibbons Expires May 2002 4 232 DESCRIPTION "The MIB for internet Fibre Channel Protocol 233 (iFCP) management." 235 -- Revision History 236 REVISION "0111010000Z" 237 DESCRIPTION " v1.0 (11/01/01): 238 the first IPS standard track version. 239 " 240 -- an IETF number has not yet been assigned 241 ::= {experimental XXXX} 243 IfIndexType ::= TEXTUAL-CONVENTION 244 STATUS current 245 DESCRIPTION "Represents the possible interface indexes that 246 can be used on the iFCP device." 247 SYNTAX INTEGER (0..1024) 249 NportIdx ::= TEXTUAL-CONVENTION 250 STATUS current 251 DESCRIPTION "Represents the count of iFCP N Ports 252 supported." 253 SYNTAX INTEGER (0..4294967295) 255 IfcpVersionType ::= TEXTUAL-CONVENTION 256 STATUS current 257 DESCRIPTION "Represents the protocol version 258 supported." 259 SYNTAX INTEGER (0..4294967295) 261 PortType ::= TEXTUAL-CONVENTION 262 STATUS current 263 DESCRIPTION "Represents the TCP Port being used for 264 and iFCP connection." 265 SYNTAX INTEGER (0..65535) 267 IfcpSessionStateType ::= TEXTUAL-CONVENTION 268 STATUS current 269 DESCRIPTION "Represents the iFCP session state." 270 SYNTAX INTEGER {down(0), openPending(1), open(2)} 272 -- 273 -- Internet Fibre Channel Protocol (iFCP) 274 -- 276 ifcpDeviceObj OBJECT IDENTIFIER ::= {ifcpModule 1} 277 ifcpDeviceConformance OBJECT IDENTIFIER ::= {ifcpModule 2} 279 -- 280 -- iFCP Objects -------------------- 281 -- 283 ifcpLocalDeviceObjInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 1} 285 -- top-level object information here 287 Gibbons Expires May 2002 5 288 ifcpVersionMin OBJECT-TYPE 289 SYNTAX IfcpVersionType 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The minimum iFCP protocol version supported by the local iFCP 294 device." 295 ::= {ifcpLocalDeviceObjInfo 1} 297 ifcpVersionMax OBJECT-TYPE 298 SYNTAX IfcpVersionType 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The maximum iFCP protocol version supported by the local iFCP 303 device." 304 ::= {ifcpLocalDeviceObjInfo 2} 306 ifcpNumNports OBJECT-TYPE 307 SYNTAX NportIdx 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The current total number of iFCP N Ports supported by the local 312 iFCP device." 313 ::= {ifcpLocalDeviceObjInfo 3} 315 -- 316 -- iFCP Local Interface Information 317 -- 319 ifcpLocalTcpIfTable OBJECT-TYPE 320 SYNTAX SEQUENCE OF IfcpLocalTcpIfEntry 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "Information on the local interfaces available for iFCP connections, 325 including the TCP port used. The maximum number of entries is 326 based on the number of local interfaces and TCP ports configured 327 for iFCP connections." 328 ::= {ifcpLocalDeviceObjInfo 10} 330 ifcpLocalTcpIfEntry OBJECT-TYPE 331 SYNTAX IfcpLocalTcpIfEntry 332 MAX-ACCESS not-accessible 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, 342 Gibbons Expires May 2002 6 343 ifcpInterfaceTcpPort PortType, 344 ifcpInterfaceAddrType InetAddressType, 345 ifcpInterfaceAddr InetAddress 346 } 348 ifcpInterfaceIfIndex OBJECT-TYPE 349 SYNTAX IfIndexType 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "This is an interface index for local device, as described in RFC 354 1213. This can be used as an ifTable index to obtain additional 355 information about the interface." 356 ::= {ifcpLocalTcpIfEntry 1} 358 ifcpInterfaceTcpPort OBJECT-TYPE 359 SYNTAX PortType 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "This is the TCP port number being used for iFCP access in this 364 interface." 365 ::= {ifcpLocalTcpIfEntry 2} 367 ifcpInterfaceAddrType OBJECT-TYPE 368 SYNTAX InetAddressType 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "This type of address in ifcpInterfaceAddr." 373 ::= {ifcpLocalTcpIfEntry 3} 375 ifcpInterfaceAddr OBJECT-TYPE 376 SYNTAX InetAddress 377 MAX-ACCESS read-only 378 STATUS current 379 DESCRIPTION 380 "This is the address of the interface being used iFCP access. 381 This address is consistent with the address defined in the 382 ifTable of RFC 1213 for this interface." 383 ::= {ifcpLocalTcpIfEntry 4} 385 -- 386 -- iFCP Local Device N Port Information 387 -- 389 ifcpLocalDeviceNportInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 3} 391 -- 392 -- iFCP N Port Table 393 -- 395 ifcpDeviceNportTable OBJECT-TYPE 396 SYNTAX SEQUENCE OF IfcpDeviceNportEntry 398 Gibbons Expires May 2002 7 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 FcNameId, 420 ifcpDeviceNportID FcAddressId, 421 ifcpDeviceNportIfIndex IfIndexType, 422 ifcpDeviceNportTcpPort PortType 423 } 425 ifcpDeviceNportWwpn OBJECT-TYPE 426 SYNTAX FcNameId 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "The iFCP N Port World Wide Port Name as defined in the 431 iFCP Specification." 432 ::= {ifcpDeviceNportEntry 1} 434 ifcpDeviceNportID OBJECT-TYPE 435 SYNTAX FcAddressId 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The iFCP N Port, Port ID as defined in the iFCP Specification." 440 ::= {ifcpDeviceNportEntry 3} 442 ifcpDeviceNportIfIndex OBJECT-TYPE 443 SYNTAX IfIndexType 444 MAX-ACCESS read-only 445 STATUS current 446 DESCRIPTION 447 "The interface that is being used for this N Port. This can be 448 used along with ifcpDeviceNportTcpPort to access the 449 ifcpLocalTcpIfTable." 450 ::= {ifcpDeviceNportEntry 9} 452 ifcpDeviceNportTcpPort OBJECT-TYPE 454 Gibbons Expires May 2002 8 455 SYNTAX PortType 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The iFCP N Port TCP port number as defined in the 460 iFCP Specification. This is the port number used 461 to login to the N Port." 462 ::= {ifcpDeviceNportEntry 11} 464 -- 465 -- iFCP remote device information ------------------------------ 466 -- 468 ifcpRemoteDeviceObjInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 5} 470 -- 471 -- iFCP remote device table 472 -- 474 ifcpRemoteDeviceTable OBJECT-TYPE 475 SYNTAX SEQUENCE OF IfcpRemoteDeviceEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "Information on remote iFCP devices available for connections. 480 This table can be used to statically configure connections between 481 iFCP devices when a name service, such as the iSNS, is not 482 being used. The maximum number of entries is based on the 483 number of iFCP devices in the network." 484 ::= {ifcpRemoteDeviceObjInfo 1} 486 ifcpRemoteDeviceEntry OBJECT-TYPE 487 SYNTAX IfcpRemoteDeviceEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "Information on remote iFCP devices." 492 INDEX {ifcpRemoteDeviceIndex} 493 ::= {ifcpRemoteDeviceTable 1} 495 IfcpRemoteDeviceEntry ::= SEQUENCE { 496 ifcpRemoteDeviceIndex INTEGER, 497 ifcpRemoteDeviceIfIndex IfIndexType, 498 ifcpRemoteDevicePort PortType, 499 ifcpRemoteDeviceAddrType InetAddressType, 500 ifcpRemoteDeviceAddr InetAddress, 501 ifcpRemoteDeviceMgtAddrType InetAddressType, 502 ifcpRemoteDeviceMgtAddr InetAddress, 503 ifcpRemoteDeviceVersionMin IfcpVersionType, 504 ifcpRemoteDeviceVersionMax IfcpVersionType 505 } 507 ifcpRemoteDeviceIndex OBJECT-TYPE 509 Gibbons Expires May 2002 9 510 SYNTAX INTEGER (1..2147483647) 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The remote device iFCP interface index. This is a monotonically 515 increasing value used as an index to the table. The device index 516 is used because the length of ifcpRemoteDeviceAddr, 517 ifcpRemoteDeviceIfIndex and ifcpRemoteDevicePort combined would 518 be too long to be an index. This index and mappings to remote 519 devices may be reset when the local iFCP device is rebooted." 520 ::= {ifcpRemoteDeviceEntry 1} 522 ifcpRemoteDeviceIfIndex OBJECT-TYPE 523 SYNTAX IfIndexType 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "The remote device interface If Index. This can also be used to 528 index into the ifTable of RFC 1213 for the remote device to 529 obtain additional information about the interface." 530 ::= {ifcpRemoteDeviceEntry 2} 532 ifcpRemoteDevicePort OBJECT-TYPE 533 SYNTAX PortType 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "The iFCP N Port, Port ID as defined in the iFCP Specification." 538 ::= {ifcpRemoteDeviceEntry 3} 540 ifcpRemoteDeviceAddrType OBJECT-TYPE 541 SYNTAX InetAddressType 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The type of address in ifcpRemoteDeviceAddr." 546 ::= {ifcpRemoteDeviceEntry 4} 548 ifcpRemoteDeviceAddr OBJECT-TYPE 549 SYNTAX InetAddress 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The address of the remote device interface." 554 ::= {ifcpRemoteDeviceEntry 5} 556 ifcpRemoteDeviceMgtAddrType OBJECT-TYPE 557 SYNTAX InetAddressType 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The type of address in ifcpRemoteDeviceMgtAddr." 562 ::= {ifcpRemoteDeviceEntry 6} 564 Gibbons Expires May 2002 10 565 ifcpRemoteDeviceMgtAddr OBJECT-TYPE 566 SYNTAX InetAddress 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The SNMP management address of the remote device interface." 571 ::= {ifcpRemoteDeviceEntry 7} 573 ifcpRemoteDeviceVersionMin OBJECT-TYPE 574 SYNTAX IfcpVersionType 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The minimum iFCP protocol version supported by the remote iFCP 579 device. It is important that the protocol version of the local 580 and remote iFCP device be compatible." 581 ::= {ifcpRemoteDeviceEntry 8} 583 ifcpRemoteDeviceVersionMax OBJECT-TYPE 584 SYNTAX IfcpVersionType 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The maximum iFCP protocol version supported by the remote iFCP 589 device. It is important that the protocol version of the local 590 and remote iFCP device be compatible." 591 ::= {ifcpRemoteDeviceEntry 9} 593 -- 594 -- iFCP N Port session information ------------------------------ 595 -- 597 ifcpNportSessionInfo OBJECT IDENTIFIER ::= {ifcpDeviceObj 7} 599 -- Session Attributes Table 601 ifcpSessionAttributesTable OBJECT-TYPE 602 SYNTAX SEQUENCE OF 603 IfcpSessionAttributesEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "An iFCP session consists of the pair of N_PORTs comprising 608 the session endpoints joined by a single TCP/IP connection. 609 This table provides information on each session currently 610 communicating with the local device." 611 ::= {ifcpNportSessionInfo 1} 613 ifcpSessionAttributesEntry OBJECT-TYPE 614 SYNTAX IfcpSessionAttributesEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "An entry in the session table." 620 Gibbons Expires May 2002 11 621 INDEX {ifcpSessionIndex} 622 ::= {ifcpSessionAttributesTable 1} 624 IfcpSessionAttributesEntry ::= SEQUENCE { 625 ifcpSessionIndex INTEGER, 626 ifcpSessionLocalNport FcNameId, 627 ifcpSessionRemoteNport FcNameId, 628 ifcpSessionLocalInterface INTEGER, 629 ifcpSessionRemoteInterface INTEGER 630 } 632 ifcpSessionIndex OBJECT-TYPE 633 SYNTAX INTEGER (1..2147483647) 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "The iFCP session index. This is a monotonically increasing 638 value used as an index to the table. The session index may 639 change between local device reboots. The index was used because 640 ifcpSessionLocalNport and ifcpSessionRemoteNport would create an 641 index that would be difficult to implement." 642 ::= {ifcpSessionAttributesEntry 1} 644 ifcpSessionLocalNport OBJECT-TYPE 645 SYNTAX FcNameId 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "World Wide Name of the local N Port." 650 ::= {ifcpSessionAttributesEntry 2} 652 ifcpSessionRemoteNport OBJECT-TYPE 653 SYNTAX FcNameId 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "World Wide Name of the remote N Port." 658 ::= {ifcpSessionAttributesEntry 3} 660 ifcpSessionLocalInterface OBJECT-TYPE 661 SYNTAX INTEGER (1..2147483647) 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The interface of the local device used for this session." 666 ::= {ifcpSessionAttributesEntry 4} 668 ifcpSessionRemoteInterface OBJECT-TYPE 669 SYNTAX INTEGER (1..2147483647) 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The interface of the remote device used for this session." 674 ::= {ifcpSessionAttributesEntry 5} 676 Gibbons Expires May 2002 12 677 -- 678 -- Statistics 679 -- 681 ifcpSessionStatsTable OBJECT-TYPE 682 SYNTAX SEQUENCE OF IfcpSessionStatsEntry 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "This table provides information on an iFCP session." 687 ::= {ifcpNportSessionInfo 2} 689 ifcpSessionStatsEntry OBJECT-TYPE 690 SYNTAX IfcpSessionStatsEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "iFCP specific statistics per session." 695 AUGMENTS {ifcpSessionAttributesEntry} 696 ::= {ifcpSessionStatsTable 1} 698 IfcpSessionStatsEntry ::= SEQUENCE { 699 ifcpSessionState IfcpSessionStateType, 700 ifcpSessionTxOctets Counter64, 701 ifcpSessionRxOctets Counter64, 702 ifcpSessionTxFrames Counter64, 703 ifcpSessionRxFrames Counter64, 704 ifcpSessionStaleFrames Counter32, 705 ifcpSessionHeaderCRCErrors Counter32, 706 ifcpSessionPayloadCRCErrors Counter32, 707 ifcpSessionOtherErrors Counter32 708 } 710 ifcpSessionState OBJECT-TYPE 711 SYNTAX IfcpSessionStateType 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The current session operating state." 716 ::= {ifcpSessionStatsEntry 1} 718 ifcpSessionTxOctets OBJECT-TYPE 719 SYNTAX Counter64 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The total number of octets transmitted since the 724 connection was first established." 725 ::= {ifcpSessionStatsEntry 2} 727 ifcpSessionRxOctets OBJECT-TYPE 728 SYNTAX Counter64 729 MAX-ACCESS read-only 731 Gibbons Expires May 2002 13 732 STATUS current 733 DESCRIPTION 734 "The total number of octets received since the 735 connection was first established." 736 ::= {ifcpSessionStatsEntry 3} 738 ifcpSessionTxFrames OBJECT-TYPE 739 SYNTAX Counter64 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "The total number of frames transmitted since the 744 connection was first established." 745 ::= {ifcpSessionStatsEntry 4} 747 ifcpSessionRxFrames OBJECT-TYPE 748 SYNTAX Counter64 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The total number of frames received since the 753 connection was first established." 754 ::= {ifcpSessionStatsEntry 5} 756 ifcpSessionStaleFrames OBJECT-TYPE 757 SYNTAX Counter32 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "The total number of received frames that were stale and 762 discarded since the connection was first established." 763 ::= {ifcpSessionStatsEntry 6} 765 ifcpSessionHeaderCRCErrors OBJECT-TYPE 766 SYNTAX Counter32 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "The total number of CRC errors that occurred in the frame 771 header detected since the connection was first established." 772 ::= {ifcpSessionStatsEntry 7} 774 ifcpSessionPayloadCRCErrors OBJECT-TYPE 775 SYNTAX Counter32 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The total number of CRC errors that occurred in the frame 780 payload detected since the connection was first established." 781 ::= {ifcpSessionStatsEntry 8} 783 ifcpSessionOtherErrors OBJECT-TYPE 784 SYNTAX Counter32 785 MAX-ACCESS read-only 787 Gibbons Expires May 2002 14 788 STATUS current 789 DESCRIPTION 790 "The total number of errors, other then errors explicitly 791 measured, detected since the connection was first established." 792 ::= {ifcpSessionStatsEntry 9} 794 ------------------------------------------------------------ 796 ifcpGroups OBJECT IDENTIFIER ::= {ifcpDeviceConformance 1} 798 ifcpDeviceObjGroup OBJECT-GROUP 799 OBJECTS { 800 ifcpVersionMin, 801 ifcpVersionMax, 802 ifcpNumNports, 803 ifcpInterfaceIfIndex, 804 ifcpInterfaceTcpPort, 805 ifcpInterfaceAddrType, 806 ifcpInterfaceAddr 807 } 808 STATUS current 809 DESCRIPTION 810 "iFCP local device info group" 811 ::= {ifcpGroups 1} 813 ifcpDeviceNportGroup OBJECT-GROUP 814 OBJECTS { 815 ifcpDeviceNportWwpn, 816 ifcpDeviceNportID, 817 ifcpDeviceNportIfIndex, 818 ifcpDeviceNportTcpPort 819 } 820 STATUS current 821 DESCRIPTION 822 "iFCP local device N Port group" 823 ::= {ifcpGroups 2} 825 ifcpRemoteDeviceGroup OBJECT-GROUP 826 OBJECTS { 827 ifcpRemoteDeviceIndex, 828 ifcpRemoteDeviceIfIndex, 829 ifcpRemoteDevicePort, 830 ifcpRemoteDeviceAddrType, 831 ifcpRemoteDeviceAddr, 832 ifcpRemoteDeviceMgtAddrType, 833 ifcpRemoteDeviceMgtAddr, 834 ifcpRemoteDeviceVersionMin, 835 ifcpRemoteDeviceVersionMax 836 } 837 STATUS current 838 DESCRIPTION 839 "iFCP local device N Port node group" 840 ::= {ifcpGroups 3} 842 Gibbons Expires May 2002 15 843 ifcpDeviceSessionGroup OBJECT-GROUP 844 OBJECTS { 845 ifcpSessionLocalNport, 846 ifcpSessionRemoteNport, 847 ifcpSessionLocalInterface, 848 ifcpSessionRemoteInterface 849 } 850 STATUS current 851 DESCRIPTION 852 "iFCP Session group" 853 ::= {ifcpGroups 4} 855 ifcpDeviceSessionStatsGroup OBJECT-GROUP 856 OBJECTS { 857 ifcpSessionState, 858 ifcpSessionTxOctets, 859 ifcpSessionRxOctets, 860 ifcpSessionTxFrames, 861 ifcpSessionRxFrames, 862 ifcpSessionStaleFrames, 863 ifcpSessionHeaderCRCErrors, 864 ifcpSessionPayloadCRCErrors, 865 ifcpSessionOtherErrors 866 } 867 STATUS current 868 DESCRIPTION 869 "iFCP Session Statistics group" 870 ::= {ifcpGroups 5} 872 ifcpCompliances OBJECT IDENTIFIER ::= {ifcpDeviceConformance 2} 874 ifcpDeviceComplianceV1 MODULE-COMPLIANCE 875 STATUS current 876 DESCRIPTION 877 "Initial compliance statement for an iFCP device." 878 MODULE -- this module 879 MANDATORY-GROUPS { 880 ifcpDeviceObjGroup, 881 ifcpDeviceNportGroup, 882 ifcpDeviceSessionGroup, 883 ifcpDeviceSessionStatsGroup 884 } 885 ::= {ifcpCompliances 1} 887 END 889 6. Security Considerations 891 There are a number of management objects defined in this MIB that 892 have a MAX-ACCESS clause of read-write and/or read-create. Such 893 objects may be considered sensitive or vulnerable in some network 894 environments. The support for SET operations in a non-secure 895 environment without proper protection can have a negative effect 896 on network operations. 898 Gibbons Expires May 2002 16 899 SNMPv1 by itself is not a secure environment. Even if the 900 network itself is secure (for example by using IPSec), even then, 901 there is no control as to who on the secure network is allowed to 902 access and GET/SET (read/change/create/delete) the objects in 903 this MIB. 905 It is recommended that the implementers consider the security 906 features as provided by the SNMPv3 framework. Specifically, the 907 use of the User-based Security Model RFC 2574 [RFC2574] and the 908 View-based Access Control Model RFC 2575 [RFC2575] is 909 recommended. 911 It is then a customer/user responsibility to ensure that the SNMP 912 entity giving access to an instance of this MIB, is properly 913 configured to give access to the objects only to those principals 914 (users) that have legitimate rights to indeed GET or SET 915 (change/create/delete) them. 917 7. References 919 [RFC2851] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder 920 "Textual Conventions for Internet Network Addresses", 921 RFC 2851, June 2000. 923 [RFC2837] Rose, M., and K. McCloghrie, "Definitions of Managed 924 Objects for the Fabric Element in Fibre Channel 925 Standard", RFC 2837, May 2000. 927 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 928 Architecture for Describing SNMP Management Frameworks", 929 RFC 2571, April 1999. 931 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 932 Identification of Management Information for TCP/IP- 933 based Internets", STD 16, RFC 1155, May 1990. 935 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 936 STD 16, RFC 1212, March 1991. 938 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 939 the SNMP", RFC 1215, March 1991. 941 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 942 J., Rose, M., and S. Waldbusser, "Structure of 943 Management Information Version 2 (SMIv2)", STD 58, RFC 944 2578, April 1999. 946 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 947 J., Rose, M., and S. Waldbusser, "Textual Conventions 948 for SMIv2", STD 58, RFC 2579, April 1999. 950 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 951 J., Rose, M., and S. Waldbusser, "Conformance Statements 953 Gibbons Expires May 2002 17 954 for SMIv2", STD 58, RFC 2580, April 1999. 956 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 957 "Simple Network Management Protocol", STD 15, RFC 1157, 958 May 1990. 960 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 961 "Introduction to Community-based SNMPv2", RFC 1901, 962 January 1996. 964 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 965 "Transport Mappings for Version 2 of the Simple Network 966 Management Protocol (SNMPv2)", RFC 1906, January 1996. 968 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 969 "Message Processing and Dispatching for the Simple 970 Network Management Protocol (SNMP)", RFC 2572, April 971 1999. 973 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 974 Model (USM) for version 3 of the Simple Network 975 Management Protocol (SNMPv3)", RFC 2574, April 1999. 977 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 978 "Protocol Operations for Version 2 of the Simple Network 979 Management Protocol (SNMPv2)", RFC 1905, January 1996. 981 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 982 Applications", RFC 2573, April 1999. 984 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 985 Access Control Model (VACM) for the Simple Network 986 Management Protocol (SNMP)", RFC 2575, April 1999. 988 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 989 "Introduction to Version 3 of the Internet-standard 990 Network Management Framework", RFC 2570, April 1999. 992 8. Authors� Addresses 994 Josh Tseng 995 Kevin Gibbons 996 Charles Monia 997 Postal: Nishan Systems 998 3850 North First Street 999 San Jose, CA 95134-1702 1000 USA 1002 Tel: (408) 519-3756 1003 Fax: (408) 519-3705 1005 E-mail: snmp@NishanSystems.com 1007 Franco Travostino 1009 Gibbons Expires May 2002 18 1010 Nortel Networks 1011 3 Federal Street 1012 Billerica, MA 01821 1013 USA 1015 Tel: (978) 288-7708 1017 E-mail: travos@nortelnetworks.com 1019 9. Full Copyright Statement 1021 "Copyright (C) The Internet Society 2001. All Rights Reserved. 1022 This document and translations of it may be copied and furnished 1023 to others, and derivative works that comment on or otherwise 1024 explain it or assist in its implementation may be prepared, 1025 copied, published and distributed, in whole or in part, without 1026 restriction of any kind, provided that the above copyright notice 1027 and this paragraph are included on all such copies and derivative 1028 works. However, this document itself may not be modified in any 1029 way, such as by removing the copyright notice or references to 1030 the Internet Society or other Internet organizations, except as 1031 needed for the purpose of developing Internet standards in which 1032 case the procedures for copyrights defined in the Internet 1033 Standards process must be followed, or as required to translate 1034 it into languages other than English. 1036 The limited permissions granted above are perpetual and will not 1037 be revoked by the Internet Society or its successors or assigns. 1039 This document and the information contained herein is provided on 1040 An "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1041 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1042 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 1043 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 1044 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1045 PURPOSE." 1047 Gibbons Expires May 2002 19