idnits 2.17.1 draft-ietf-ips-fcip-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1447. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1341. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1348. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1354. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1311: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 1317: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (April 2006) is 6579 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) == Missing Reference: 'RFC2578' is mentioned on line 1382, but not defined == Missing Reference: 'RFC2579' is mentioned on line 1391, but not defined == Missing Reference: 'RFC2580' is mentioned on line 1395, but not defined == Missing Reference: 'RFC3821' is mentioned on line 1367, but not defined == Missing Reference: 'FCBB2' is mentioned on line 1370, but not defined == Missing Reference: 'RFC3822' is mentioned on line 1406, but not defined == Missing Reference: 'RFC4022' is mentioned on line 1403, but not defined == Missing Reference: 'RFC4044' is mentioned on line 1376, but not defined == Missing Reference: 'RFC2863' is mentioned on line 1379, but not defined == Missing Reference: 'RFC4001' is mentioned on line 255, but not defined == Missing Reference: 'RFC3411' is mentioned on line 1387, but not defined == Missing Reference: 'FC-SW-3' is mentioned on line 1373, but not defined == Missing Reference: 'RFC2883' is mentioned on line 1410, but not defined == Missing Reference: 'RFC1323' is mentioned on line 1414, but not defined ** Obsolete undefined reference: RFC 1323 (Obsoleted by RFC 7323) == Missing Reference: 'RFC2474' is mentioned on line 1399, but not defined Summary: 6 errors (**), 0 flaws (~~), 16 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPS Working Group 3 INTERNET-DRAFT Ravi Natarajan 4 F5 Networks 5 Expires April 2006 6 Anil Rijhsinghani 7 Accton Technology Corporation 9 October 2005 11 Definitions of Managed Objects for FCIP 13 Status of this Memo: 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 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 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress". 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt . 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html . 36 This Internet-Draft will expire on Aril 2006. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in TCP/IP based internets. 42 In particular it defines objects for managing FCIP entities, which 43 are used to interconnect FC fabrics with IP networks. 45 Table of Contents 47 Status of this Memo...............................................1 48 Copyright Notice..................................................1 49 Abstract..........................................................1 50 Table of Contents.................................................2 51 1. The Internet-Standard Management Framework....................3 52 2. Overview of FCIP management model.............................3 53 3. Relationship to other MIBs....................................5 54 4. MIB Definitions...............................................6 55 5. Security Considerations......................................29 56 6. IANA Considerations..........................................30 57 7. Intellectual Property........................................30 58 8. Acknowledgements.............................................30 59 9. Normative References.........................................30 60 10. Informative References.......................................32 61 11. Authors' Addresses...........................................32 62 12. Disclaimer of Validity.......................................32 63 13. Copyright Statement..........................................32 65 1. The Internet-Standard Management Framework 67 For a detailed overview of the documents that describe the current 68 Internet-Standard Management Framework, please refer to section 7 of 69 RFC 3410 [RFC3410]. 71 Managed objects are accessed via a virtual information store, termed 72 the Management Information Base or MIB. MIB objects are generally 73 accessed through the Simple Network Management Protocol (SNMP). 74 Objects in the MIB are defined using the mechanisms defined in the 75 Structure of Management Information (SMI). This memo specifies a MIB 76 module that is compliant to the SMIv2, which is described in STD 58, 77 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 78 [RFC2580]. 80 2. Overview of FCIP management model 82 Note that the FCIP Entity is fully described in [RFC3821] from a 83 functional point of view. A collection of multiple instances of 84 FCIP Entities and the corresponding FC Entities, described in 85 [FCBB2], within an SNMP Context is referred to as an FCIP device 86 here. This section describes FCIP from a management point of view. 88 +------------------------------------------+ 89 | FCIP Device | 90 | | 91 | +-----------+ +-----------+ | 92 | |FCIP Entity| |FCIP Entity| | 93 | | | | | | 94 | | | | | | 95 | +--+--+--+--+ +--+--+--+--+ | 96 | | | | | | | | 97 | | | | | | | | 98 | FCIP Links FCIP Links | 99 | | 100 +------------------------------------------+ 102 The FCIP device provides IP-based interconnection model to 103 interconnect FC fabric elements. In this model, the FCIP devices 104 along with the IP network on which they are running provide a new 105 FCIP transport network. 107 This IP-based FCIP Interconnection Model supports the following 108 topology: 109 o The FCIP-based transport network is formed by interconnecting the 110 FCIP-devices. 111 o Each FCIP device has one or more FCIP Entities or Instances. 113 o Peer FCIP Entities are connected by FCIP Links, attached to 114 VE_ports/B_Access. 115 o Each FCIP Link Endpoint contains one or more Data Engines. 116 o The FCIP device can work as a standalone box or as part 117 of a FC fabric element. 119 Each FCIP Entity managed by this MIB is referred to as a FCIP 120 Instance. The MIB is broken up as follows: 122 2.1 FCIP Entity Instances Table 123 The FCIP Entity table contains information about this entity's 124 existing instances of FCIP entities. 126 2.2 FCIP Link Table 127 The FCIP link table contains information about this FCIP device's 128 existing FCIP links. 130 2.3 FCIP TCP Connection Table 131 The FCIP TCP Connection table contains information about existing TCP 132 connections. Each FCIP link within a FCIP entity contains one or more 133 TCP connections. The FCIP entity employs a Data Engine for each TCP 134 connection for handling FC frame encapsulation, de-encapsulation and 135 transmission of FCIP frames on the connection. 137 2.4 FCIP Dynamic Route Table 138 The FCIP dynamic route table contains routing information that is 139 dynamically discovered by this FCIP device. The FCIP device may use 140 the SLPv2 protocol [RFC3822] in conjunction with other protocols, 141 such as FSPF, to dynamically discover other FCIP entities, and 142 populate this table to map destination domains to FCIP Links. 144 2.5 FCIP Static Route Table 145 The FCIP static route table contains routing information that is 146 statically configured into this FCIP device by Network Admin. 147 In the absence of dynamic discovery of remote FCIP entities, the 148 Network Manager can configure remote domains and FCIP Entities 149 that are reachable by this device into this table. 151 At any point of time, both the static and dynamic routing tables can 152 be active. If a DID is present in both tables, information in the 153 static route table will take precedence over the entry in the dynamic 154 route table for the same DID. 156 2.6 FCIP Discovery Domain Table 158 The FCIP Discovery Domain Table maps this device's FCIP Entities into 159 FCIP Discovery Domains. 161 2.7 FCIP Link Error Table 162 The FCIP Link Errors Table contains counters that indicate error 163 conditions on an FCIP Link. 165 3. Relationship to other MIBs 167 Objects accessible from other MIB modules applicable to FCIP devices 168 have not been included in this MIB module. The following lists all 169 applicable MIB modules that should be present with FCIP-MGMT-MIB. 171 3.1 Relationship to the 'TCP' group 173 This group is mandatory for all systems which implement TCP. 174 Objects relevant to TCP must be obtained from this group [RFC4022]. 176 3.2 Relationship to the 'interfaces' MIB 178 The 'interfaces' group is defined as being mandatory for 179 all systems and contains information on an entity's interfaces. 180 Each logical/virtual interface created as an FCIP Link should be 181 represented as a row in the ifTable with a unique ifIndex value and a 182 value of ifType 'fcipLink' (224) for each such interface. For a 183 complete list of interface types, refer to the IANA registry at 184 "ftp://ftp.isi.edu/mib/iana.mib/ianaiftype.mib". These are 185 the only ifIndex values of relevance to an FCIP Entity because FCIP 186 runs on top of TCP/IP. 188 FCIP runs over TCP. Thus, by definition, there is no ifTable 189 interface directly beneath it, and so ifStackLowerLayer is always 190 0. For any protocol using FCIP (i.e., above FCIP), FCIP appears to 191 be a regular FC interface. As stated in [RFC4044], a regular 192 "FC interface will typically have no other ifTable rows stacked on 193 top of it", and thus, ifStackHigherLayer is typically zero. 195 3.3 Relationship to the Fibre Channel Management MIB 197 The Fibre Channel Management MIB [RFC4044] is assumed for FC 198 functionality managed objects. 200 3.4 Specific Interface Group MIB Objects 202 The following table provides specific implementation guidelines for 203 applying the objects defined in the Interfaces Group MIB to FCIP Links. 204 For those objects not listed here, refer to their generic definitions 205 in [RFC2863]. 207 Object Guidelines 208 ifType 'fcipLink' (224) 210 ifSpeed The ifSpeed for the physical interface(s) 211 over which the FCIP Link runs. 213 ifPhysAddress There is no physical address corresponding 214 to an FCIP Link (only WWN). Reported as 0. 216 ifAdminStatus Write access is not required, and support 217 for 'testing' is not required. 219 ifOperStatus Support for 'testing' is not required. 220 The value 'dormant' has no meaning for 221 FCIP Links. 223 ifInOctets The number of octets of FCIP information 224 ifHCInOctets contained in received frames in TCP 225 streams, starting with FCIP header. 227 ifInUcastPkts The number of FCIP frames received 228 ifHCInUcastPkts on this FCIP Link. 230 ifOutOctets The number of octets of FCIP information 231 ifHCOutOctets contained in transmitted frames in TCP 232 streams, starting with FCIP header. 234 ifOutUcastPkts The number of FCIP frames transmitted 235 ifHCOutUcastPkts on this FCIP Link. 237 ifInMulticastPkts These counters are not incremented. 238 ifInBroadcastPkts 239 ifOutMulticastPkts 240 ifOutBroadcastPkts 241 ifHCInMulticastPkts 242 ifHCInBroadcastPkts 243 ifHCOutMulticastPkts 244 ifHCOutBroadcastPkts 246 ifLinkUpDownTrapEnable Default is 'disabled'. 248 ifPromiscuousMode This will be 'false' 250 ifConnectorPresent This will be 'false'. 252 4. MIB Definitions 253 -- 254 -- The following MIB module has IMPORTS from [RFC2578], [RFC2579], 255 -- [RFC4001], [RFC4044], [RFC2863], [RFC2580], and [RFC3411]. 256 -- In REFERENCE clauses, it refers to [FC-SW-3], [RFC3821], 257 -- [RFC2883], [RFC1323], [RFC2474] and [RFC3822]. 258 -- 260 FCIP-MGMT-MIB DEFINITIONS ::= BEGIN 262 IMPORTS 263 OBJECT-TYPE, 264 MODULE-IDENTITY, 265 Unsigned32, 266 Counter32, 267 mib-2 FROM SNMPv2-SMI 268 TEXTUAL-CONVENTION, 269 TruthValue, RowStatus, TimeStamp FROM SNMPv2-TC 270 InetAddressType, 271 InetAddress, 272 InetPortNumber FROM INET-ADDRESS-MIB 273 FcNameIdOrZero FROM FC-MGMT-MIB 274 InterfaceIndex FROM IF-MIB 275 MODULE-COMPLIANCE, 276 OBJECT-GROUP FROM SNMPv2-CONF 277 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 279 fcipMIB MODULE-IDENTITY 280 LAST-UPDATED "200510170000Z" 281 ORGANIZATION "IETF IPFC Working Group" 282 CONTACT-INFO "Anil Rijhsinghani 283 Accton Technology Corporation 284 5 Mount Royal Ave 285 Marlboro, MA 01752 USA. 287 Ravi Natarajan 288 F5 Networks 289 181 Metro Drive Suite 400 290 San Jose, CA 95110 USA." 291 DESCRIPTION "The module defines management information specific to 292 FCIP devices. 294 Copyright(C) The Internet Society(2005). This version 295 of this MIB module is part of RFC xxxx; see the RFC 296 itself for full legal notices." 297 -- RFC Editor: replace xxxx with actual RFC number & remove this note 298 REVISION "200510170000Z" 299 DESCRIPTION 300 "Initial version of this module, published as RFC xxxx." 302 -- RFC-Editor: replace xxxx with actual RFC number & remove this note 303 ::= { mib-2 nnn } -- nnn TO BE ASSIGNED by IANA 304 -- RFC Editor: replace nnn with IANA-assigned number & remove note 306 fcipObjects OBJECT IDENTIFIER ::= { fcipMIB 1 } 307 fcipConformance OBJECT IDENTIFIER ::= { fcipMIB 2 } 308 fcipConfig OBJECT IDENTIFIER ::= { fcipObjects 1 } 310 -- ****************************************************************** 311 -- Textual conventions 312 -- 314 FcipDomainIdInOctetForm ::= TEXTUAL-CONVENTION 315 STATUS current 316 DESCRIPTION "The Domain ID of a FC entity in octet form 317 to support the concatenation(000000h||Domain_ID) 318 format defined in the FSPF routing protocol." 319 REFERENCE "FC-SW-3 section 4.8" 320 SYNTAX OCTET STRING (SIZE(1)) 322 FcipEntityMode ::= TEXTUAL-CONVENTION 323 STATUS current 324 DESCRIPTION "The type of port mode provided by an FCIP Entity 325 for a FCIP Link. An FCIP Entity can be an E-Port 326 mode for one of its FCIP Link Endpoints, an B-Port 327 mode for another of its FCIP Link Endpoints." 328 REFERENCE "FC-BB, rev 4.7, 2 May 1997, section 3." 329 SYNTAX INTEGER { 330 ePortMode(1), 331 bPortMode(2) 332 } 334 FcipEntityId ::= TEXTUAL-CONVENTION 335 STATUS current 336 DESCRIPTION "The FCIP entity identifier as defined in RFC 3821." 337 REFERENCE "RFC 3821, Section 7.1, FCIP Special Frame Format" 338 SYNTAX OCTET STRING (SIZE(8)) 340 -- ****************************************************************** 341 -- The FCIP group 342 -- 343 -- This group defines the global scalar objects applicable to FCIP 344 -- devices only 345 -- 347 fcipDynIpConfType OBJECT-TYPE 348 SYNTAX INTEGER { 349 slpv2(1), 350 none(2) 351 } 352 MAX-ACCESS read-write 353 STATUS current 354 DESCRIPTION 355 "The type of discovery protocol used to discover remote 356 FCIP entities. The value of this object is persistent across 357 system restarts." 358 ::= { fcipConfig 1 } 360 fcipDeviceWWN OBJECT-TYPE 361 SYNTAX FcNameIdOrZero 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The World Wide Name of this FCIP device." 366 ::= { fcipConfig 2 } 368 fcipEntitySACKOption OBJECT-TYPE 369 SYNTAX INTEGER { 370 enabled(1), 371 disabled(2) 372 } 373 MAX-ACCESS read-only 374 STATUS current 375 DESCRIPTION 376 "Indication of whether the TCP Selective Acknowledgement Option 377 is enabled at this FCIP device to let the receiver acknowledge 378 multiple lost packets in a single ACK for faster recovery." 379 REFERENCE 380 "The Selective Ack option is defined in RFC 2883." 381 ::= { fcipConfig 3 } 383 -- ****************************************************************** 384 -- The FCIP Entity Table 385 -- 387 fcipEntityInstanceTable OBJECT-TYPE 388 SYNTAX SEQUENCE OF FcipEntityInstanceEntry 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "Information about this FCIP device's existing instances of 393 FCIP entities." 394 REFERENCE "RFC 3821, Section 5.4, FCIP Entity" 395 ::= { fcipConfig 4 } 397 fcipEntityInstanceEntry OBJECT-TYPE 398 SYNTAX FcipEntityInstanceEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "A conceptual row of the FCIP entity table with information 403 about a particular FCIP entity. Once a row has been created, 404 it is non-volatile across agent restarts until it is deleted." 405 INDEX { fcipEntityId } 406 ::= { fcipEntityInstanceTable 1 } 408 FcipEntityInstanceEntry ::= 409 SEQUENCE { 410 fcipEntityId FcipEntityId, 411 fcipEntityName SnmpAdminString, 412 fcipEntityAddressType InetAddressType, 413 fcipEntityAddress InetAddress, 414 fcipEntityTcpConnPort InetPortNumber, 415 fcipEntitySeqNumWrap TruthValue, 416 fcipEntityPHBSupport TruthValue, 417 fcipEntityStatus RowStatus 418 } 420 fcipEntityId OBJECT-TYPE 421 SYNTAX FcipEntityId 422 MAX-ACCESS not-accessible 423 STATUS current 424 DESCRIPTION 425 "The FCIP entity identifier." 426 REFERENCE "RFC 3821, Section 7.1, FCIP Special Frame Format" 427 ::= { fcipEntityInstanceEntry 1 } 429 fcipEntityName OBJECT-TYPE 430 SYNTAX SnmpAdminString (SIZE (0..32)) 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "An administratively-assigned name for this FCIP entity." 435 ::= { fcipEntityInstanceEntry 2 } 437 fcipEntityAddressType OBJECT-TYPE 438 SYNTAX InetAddressType 439 MAX-ACCESS read-create 440 STATUS current 441 DESCRIPTION 442 "The type of Internet address by which the entity is reachable. 443 Only address types IPv4 and IPv6 are supported." 445 ::= { fcipEntityInstanceEntry 3 } 447 fcipEntityAddress OBJECT-TYPE 448 SYNTAX InetAddress 449 MAX-ACCESS read-create 450 STATUS current 451 DESCRIPTION 452 "The Internet address for the entity, if configured. The format of 453 this address is determined by the value of the 454 fcipEntityAddressType object." 455 ::= { fcipEntityInstanceEntry 4 } 457 fcipEntityTcpConnPort OBJECT-TYPE 458 SYNTAX InetPortNumber 459 MAX-ACCESS read-create 460 STATUS current 461 DESCRIPTION 462 "A TCP port other than the FCIP Well-Known port on which the FCIP 463 entity listens for new TCP connection requests. It contains the 464 value zero(0) if the FCIP Entity only listens on the Well-Known 465 port." 466 DEFVAL { 0 } 467 ::= { fcipEntityInstanceEntry 5 } 469 fcipEntitySeqNumWrap OBJECT-TYPE 470 SYNTAX TruthValue 471 MAX-ACCESS read-only 472 STATUS current 473 DESCRIPTION 474 "An indication of whether the FCIP Entity supports protection 475 against sequence number wrap." 476 REFERENCE 477 "The PAWS option is defined in RFC 1323." 478 ::= { fcipEntityInstanceEntry 6 } 480 fcipEntityPHBSupport OBJECT-TYPE 481 SYNTAX TruthValue 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "An indication of whether the FCIP Entity supports PHB IP QoS." 486 REFERENCE 487 "Per hop behavior is defined in RFC 2474, definition of the 488 Differentiated Services Field." 489 ::= { fcipEntityInstanceEntry 7 } 491 fcipEntityStatus OBJECT-TYPE 492 SYNTAX RowStatus 493 MAX-ACCESS read-create 494 STATUS current 495 DESCRIPTION 496 "This object specifies the operational status of the row. 498 When a management station sets the status to active(1), then 499 the values for the objects fcipEntityName, 500 fcipEntityAddressType, 501 and fcipEntityAddress should be supplied as part of the set 502 request. The values of the objects fcipEntityName, 503 fcipEntityAddressType, and fcipEntityAddress can be changed 504 if the row status is in active state. The object 505 fcipEntityTcpConnPort takes the default value zero(0), if no 506 value is supplied at the time of row creation. 508 Setting the status to destroy(6), deletes the specified FCIP 509 entity instance row from the table. It also deletes all the 510 rows corresponding to the specified FCIP entity from the 511 fcipLinkTable and fcipTcpConnTable tables." 513 ::= { fcipEntityInstanceEntry 8 } 515 -- ****************************************************************** 516 -- The FCIP Link Table 517 -- 519 fcipLinkTable OBJECT-TYPE 520 SYNTAX SEQUENCE OF FcipLinkEntry 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "Information about FCIP links exist on this device." 525 ::= { fcipConfig 5 } 527 fcipLinkEntry OBJECT-TYPE 528 SYNTAX FcipLinkEntry 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "A conceptual row of the FCIP link table containing information 533 about a particular FCIP link. The values of the read-create 534 objects in this table are persistent across system restarts." 535 INDEX { fcipEntityId, fcipLinkIndex } 536 ::= { fcipLinkTable 1 } 538 FcipLinkEntry ::= 539 SEQUENCE { 540 fcipLinkIndex Unsigned32, 541 fcipLinkIfIndex InterfaceIndex, 542 fcipLinkCost Unsigned32, 543 fcipLinkLocalFcipEntityMode FcipEntityMode, 544 fcipLinkLocalFcipEntityAddressType InetAddressType, 545 fcipLinkLocalFcipEntityAddress InetAddress, 546 fcipLinkRemFcipEntityWWN FcNameIdOrZero, 547 fcipLinkRemFcipEntityId FcipEntityId, 548 fcipLinkRemFcipEntityAddressType InetAddressType, 549 fcipLinkRemFcipEntityAddress InetAddress, 550 fcipLinkStatus RowStatus, 551 fcipLinkCreateTime TimeStamp 552 } 554 fcipLinkIndex OBJECT-TYPE 555 SYNTAX Unsigned32 (1..4294967295) 556 MAX-ACCESS not-accessible 557 STATUS current 558 DESCRIPTION 559 "An arbitrary integer which uniquely identifies one FCIP link 560 within an FCIP entity." 561 ::= { fcipLinkEntry 1 } 563 fcipLinkIfIndex OBJECT-TYPE 564 SYNTAX InterfaceIndex 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "The ifIndex value of the virtual interface corresponding to the 569 FCIP Link running over TCP/IP." 570 ::= { fcipLinkEntry 2 } 572 fcipLinkCost OBJECT-TYPE 573 SYNTAX Unsigned32 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "The FSPF cost associated with this FCIP Link." 578 DEFVAL { 0 } 579 ::= { fcipLinkEntry 3 } 581 fcipLinkLocalFcipEntityMode OBJECT-TYPE 582 SYNTAX FcipEntityMode 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "The mode of the local end of the FCIP link." 587 ::= { fcipLinkEntry 4 } 589 fcipLinkLocalFcipEntityAddressType OBJECT-TYPE 590 SYNTAX InetAddressType 591 MAX-ACCESS read-create 592 STATUS current 593 DESCRIPTION 594 "The type of Internet address contained in the corresponding 595 instance of fcipLinkLocalFcipEntityAddress. Only address types 596 IPv4 and IPv6 are supported." 597 ::= { fcipLinkEntry 5 } 599 fcipLinkLocalFcipEntityAddress OBJECT-TYPE 600 SYNTAX InetAddress 601 MAX-ACCESS read-create 602 STATUS current 603 DESCRIPTION 604 "The Internet address for the local end of this FCIP Link. 605 The format of this object is determined by the value of the 606 fcipLinkLocalFcipEntityAddressType object." 607 ::= { fcipLinkEntry 6 } 609 fcipLinkRemFcipEntityWWN OBJECT-TYPE 610 SYNTAX FcNameIdOrZero 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "The World Wide Name of the remote FC Fabric Entity." 615 REFERENCE "RFC 3821, Section 7.1, FCIP Special Frame Format" 616 ::= { fcipLinkEntry 7 } 618 fcipLinkRemFcipEntityId OBJECT-TYPE 619 SYNTAX FcipEntityId 620 MAX-ACCESS read-create 621 STATUS current 622 DESCRIPTION 623 "The remote FCIP entity's identifier." 624 REFERENCE "RFC 3821, Section 7.1, FCIP Special Frame Format" 625 ::= { fcipLinkEntry 8 } 627 fcipLinkRemFcipEntityAddressType OBJECT-TYPE 628 SYNTAX InetAddressType 629 MAX-ACCESS read-create 630 STATUS current 631 DESCRIPTION 632 "The type of Internet address contained in the corresponding 633 instance of fcipLinkRemFcipEntityAddress. Only address types 634 IPv4 and IPv6 are supported." 635 ::= { fcipLinkEntry 9 } 637 fcipLinkRemFcipEntityAddress OBJECT-TYPE 638 SYNTAX InetAddress 639 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "The Internet address for the remote end of this FCIP Link. 643 The format of this object is determined by the value of the 644 fcipLinkRemFcipEntityAddressType object." 645 ::= { fcipLinkEntry 10 } 647 fcipLinkStatus OBJECT-TYPE 648 SYNTAX RowStatus 649 MAX-ACCESS read-create 650 STATUS current 651 DESCRIPTION 652 "This object specifies the operational status of the row. 654 The values of objects fcipLinkLocalFcipEntityAddressType, 655 fcipLinkLocalFcipEntityAddress, fcipLinkRemFcipEntityWWN, 656 fcipLinkRemFcipEntityId, fcipLinkRemFcipEntityAddressType and 657 fcipLinkRemFcipEntityAddress can be changed if the row is in 658 active(1) state. The object fcipLinkCost is set to the value 659 zero(0),if no value is supplied at the time of row creation. 661 Setting the status to destroy(6), deletes the specified FCIP 662 link from the table. It also deletes all rows corresponding 663 to the specified FCIP link from the fcipTcpConnTable table." 664 ::= { fcipLinkEntry 11 } 666 fcipLinkCreateTime OBJECT-TYPE 667 SYNTAX TimeStamp 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The value of sysUpTime when this entry was last created." 672 ::= { fcipLinkEntry 12 } 674 -- ****************************************************************** 675 -- The TCP Connection Table 676 -- 678 fcipTcpConnTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF FcipTcpConnEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "Information about existing TCP connections. Each FCIP link 684 within a FCIP entity manages one or more TCP connections. The 685 FCIP entity employs a Data Engine for each TCP connection for 686 handling FC frame encapsulation, de-encapsulation and 687 transmission of FCIP frames on the connection." 688 ::= { fcipConfig 6 } 690 fcipTcpConnEntry OBJECT-TYPE 691 SYNTAX FcipTcpConnEntry 692 MAX-ACCESS not-accessible 693 STATUS current 694 DESCRIPTION 695 "A conceptual row of the FCIP TCP Connection table containing 696 information about a particular TCP connection." 697 INDEX { fcipEntityId, 698 fcipLinkIndex, 699 fcipTcpConnLocalPort, 700 fcipTcpConnRemPort} 701 ::= { fcipTcpConnTable 1 } 703 FcipTcpConnEntry ::= 704 SEQUENCE { 705 fcipTcpConnLocalPort InetPortNumber, 706 fcipTcpConnRemPort InetPortNumber, 707 fcipTcpConnRWSize Unsigned32, 708 fcipTcpConnMSS Unsigned32 709 } 711 fcipTcpConnLocalPort OBJECT-TYPE 712 SYNTAX InetPortNumber 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "The local port number for this TCP connection." 717 ::= { fcipTcpConnEntry 1 } 719 fcipTcpConnRemPort OBJECT-TYPE 720 SYNTAX InetPortNumber 721 MAX-ACCESS not-accessible 722 STATUS current 723 DESCRIPTION 724 "The remote port number for this TCP connection." 725 ::= { fcipTcpConnEntry 2 } 727 fcipTcpConnRWSize OBJECT-TYPE 728 SYNTAX Unsigned32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The default maximum TCP Receiver Window size for this TCP 733 connection." 734 ::= { fcipTcpConnEntry 3 } 736 fcipTcpConnMSS OBJECT-TYPE 737 SYNTAX Unsigned32 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The TCP Maximum Segment Size(MSS) for this TCP connection." 742 ::= { fcipTcpConnEntry 4 } 744 -- ****************************************************************** 745 -- The Dynamic Route Table 746 -- 748 fcipDynamicRouteTable OBJECT-TYPE 749 SYNTAX SEQUENCE OF FcipDynamicRouteEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "Information about dynamically discovered routing information. 754 The FCIP device may use SLPv2 protocol in conjunction with other 755 protocols, say FSPF, for dynamically discovering other FCIP 756 entities,and populate this table for Destination Address 757 Identifier to connecting FCIP link information." 758 ::= { fcipConfig 7 } 760 fcipDynamicRouteEntry OBJECT-TYPE 761 SYNTAX FcipDynamicRouteEntry 762 MAX-ACCESS not-accessible 763 STATUS current 764 DESCRIPTION 765 "A conceptual row of the FCIP Dynamic Route Table containing 766 information about a particular FCIP route." 767 INDEX { fcipEntityId, fcipDynamicRouteDID } 768 ::= { fcipDynamicRouteTable 1 } 770 FcipDynamicRouteEntry ::= 771 SEQUENCE { 772 fcipDynamicRouteDID FcipDomainIdInOctetForm, 773 fcipDynamicRouteLinkIndex Unsigned32 774 } 776 fcipDynamicRouteDID OBJECT-TYPE 777 SYNTAX FcipDomainIdInOctetForm 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "8 bit ID of a Fibre Channel Domain that is reachable from 782 this FCIP device." 783 ::= { fcipDynamicRouteEntry 1 } 785 fcipDynamicRouteLinkIndex OBJECT-TYPE 786 SYNTAX Unsigned32 (1..4294967295) 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The FCIP Link used to reach the domain specified by the 791 corresponding instance of fcipDynamicRouteDID. The link 792 identified by a value of this object is the same FCIP link 793 as identified by the same value of fcipLinkIndex for the 794 same FCIP entity." 795 ::= { fcipDynamicRouteEntry 2 } 797 -- ****************************************************************** 798 -- The Static Route Table 799 -- 801 fcipStaticRouteTable OBJECT-TYPE 802 SYNTAX SEQUENCE OF FcipStaticRouteEntry 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "Information about static route entries configured by the Network 807 Admin. In the absence of dynamic discovery of remote FCIP 808 entities, the Network Manager will figure out all remote FCIP 809 devices that are reachable from this device, and populate this 810 table with FCIP link information for each Domain Id. At any time, 811 both static and dynamic routing can be active, and an entry in 812 the static route table for a given DID takes precedence over the 813 entry in the dynamic route table for the same DID." 814 ::= { fcipConfig 8 } 816 fcipStaticRouteEntry OBJECT-TYPE 817 SYNTAX FcipStaticRouteEntry 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "A conceptual row of the FCIP Static Route Table containing 822 information about a particular FCIP route. The values of the 823 read-create objects in this table are persistent across system 824 restarts." 825 INDEX { fcipEntityId, fcipStaticRouteDID } 826 ::= { fcipStaticRouteTable 1 } 828 FcipStaticRouteEntry ::= 829 SEQUENCE { 830 fcipStaticRouteDID FcipDomainIdInOctetForm, 831 fcipStaticRouteLinkIndex Unsigned32, 832 fcipStaticRouteStatus RowStatus 833 } 835 fcipStaticRouteDID OBJECT-TYPE 836 SYNTAX FcipDomainIdInOctetForm 837 MAX-ACCESS not-accessible 838 STATUS current 839 DESCRIPTION 840 "8 bit ID of a Fibre Channel Domain that is reachable from 841 this FCIP device." 842 ::= { fcipStaticRouteEntry 1 } 844 fcipStaticRouteLinkIndex OBJECT-TYPE 845 SYNTAX Unsigned32 (1..4294967295) 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "The FCIP Link used to reach the domain specified by the 850 corresponding instance of fcipStaticRouteDID. The link 851 identified by a value of this object is the same FCIP link 852 as identified by the same value of fcipLinkIndex for the 853 same FCIP entity." 854 ::= { fcipStaticRouteEntry 2 } 856 fcipStaticRouteStatus OBJECT-TYPE 857 SYNTAX RowStatus 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "This object specifies the operational status of the row. 863 When a management station sets the status to active(1), then 864 the values for the object fcipStaticRouteLinkIndex should be 865 supplied as part of the set request. 867 Setting the status to destroy(6), deletes the specified FCIP 868 static route entry from the table." 869 ::= { fcipStaticRouteEntry 3 } 871 -- ****************************************************************** 872 -- The FCIP Discovery Domain Table 873 -- 875 fcipDiscoveryDomainTable OBJECT-TYPE 876 SYNTAX SEQUENCE OF FcipDiscoveryDomainEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "Information about FCIP Discovery Domains. Each FCIP Discovery 881 Domain is associated with one or more FCIP entities." 882 ::= { fcipConfig 9 } 884 fcipDiscoveryDomainEntry OBJECT-TYPE 885 SYNTAX FcipDiscoveryDomainEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "A conceptual row of the FCIP Discovery Domain Table containing 890 information about a particular FCIP Discovery Domain which 891 is associated with one or more FCIP entities. The values of the 892 read-write object fcipDiscoveryDomainName are persistent across 893 system restarts." 894 INDEX { fcipEntityId, fcipDiscoveryDomainIndex } 895 ::= { fcipDiscoveryDomainTable 1 } 897 FcipDiscoveryDomainEntry ::= 898 SEQUENCE { 899 fcipDiscoveryDomainIndex Unsigned32, 900 fcipDiscoveryDomainName SnmpAdminString 901 } 903 fcipDiscoveryDomainIndex OBJECT-TYPE 904 SYNTAX Unsigned32 (1..4294967295) 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "An integer which uniquely identifies a FCIP Discovery Domain 909 associated with this FCIP entity." 910 ::= { fcipDiscoveryDomainEntry 1 } 912 fcipDiscoveryDomainName OBJECT-TYPE 913 SYNTAX SnmpAdminString (SIZE (0..128)) 914 MAX-ACCESS read-write 915 STATUS current 916 DESCRIPTION 917 "The name of this FCIP Discovery Domain." 918 REFERENCE "RFC 3822, Section 4.1.1, FCIP Discovery Domains" 919 ::= { fcipDiscoveryDomainEntry 2 } 921 -- ****************************************************************** 922 -- The FCIP Link Errors 923 -- 925 fcipLinkErrorsTable OBJECT-TYPE 926 SYNTAX SEQUENCE OF FcipLinkErrorsEntry 927 MAX-ACCESS not-accessible 928 STATUS current 929 DESCRIPTION 930 "A list of error counters for FCIP Links. Each counter records 931 the number of times a particular error happened that caused 932 closing down a TCP connection." 933 REFERENCE "RFC 3821, Section 5.2, FCIP Link" 934 ::= { fcipConfig 10 } 936 fcipLinkErrorsEntry OBJECT-TYPE 937 SYNTAX FcipLinkErrorsEntry 938 MAX-ACCESS not-accessible 939 STATUS current 940 DESCRIPTION 941 "A conceptual row of the FCIP Link Errors Table containing 942 error counters for a FCIP Link." 943 INDEX { fcipEntityId, fcipLinkIndex } 944 ::= { fcipLinkErrorsTable 1 } 946 FcipLinkErrorsEntry ::= 947 SEQUENCE { 948 fcipLinkFcipLossofFcSynchs Counter32, 949 fcipLinkFcipEncapErrors Counter32, 950 fcipLinkFcipNotReceivedSfResps Counter32, 951 fcipLinkFcipSfRespMismatches Counter32, 952 fcipLinkFcipSfInvalidNonces Counter32, 953 fcipLinkFcipReceivedSfDuplicates Counter32, 954 fcipLinkFcipSfInvalidWWNs Counter32, 955 fcipLinkFcipBB2LkaTimeOuts Counter32, 956 fcipLinkFcipSntpExpiredTimeStamps Counter32, 957 fcipLinkTcpTooManyErrors Counter32, 958 fcipLinkTcpExcessiveDroppedDatagrams Counter32, 959 fcipLinkTcpSaParamMismatches Counter32 960 } 962 fcipLinkFcipLossofFcSynchs OBJECT-TYPE 963 SYNTAX Counter32 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "The number of times FC synchronization lost on this FCIP 968 Link. The last discontinuity of this counter is indicated 969 by fcipLinkCreateTime." 970 ::= { fcipLinkErrorsEntry 1 } 972 fcipLinkFcipEncapErrors OBJECT-TYPE 973 SYNTAX Counter32 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "The number of FCIP frames received with encapsulation errors 978 such as improper header, format, or length. The last 979 discontinuity of this counter is indicated by 980 fcipLinkCreateTime." 981 ::= { fcipLinkErrorsEntry 2 } 983 fcipLinkFcipNotReceivedSfResps OBJECT-TYPE 984 SYNTAX Counter32 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "The number of times an FCIP Special Frame Response was expected 989 but not received on this FCIP Link. The last discontinuity of 990 this counter is indicated by fcipLinkCreateTime." 991 ::= { fcipLinkErrorsEntry 3 } 993 fcipLinkFcipSfRespMismatches OBJECT-TYPE 994 SYNTAX Counter32 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "The number of times FCIP Special Frame Bytes mismatch 999 happened on this FCIP Link. The last discontinuity of this 1000 counter is indicated by fcipLinkCreateTime." 1001 ::= { fcipLinkErrorsEntry 4 } 1003 fcipLinkFcipSfInvalidNonces OBJECT-TYPE 1004 SYNTAX Counter32 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "The number of times FCIP Special Frame Invalid Connection 1009 Nonce happened on this FCIP Link. The last discontinuity 1010 of this counter is indicated by fcipLinkCreateTime." 1011 ::= { fcipLinkErrorsEntry 5 } 1013 fcipLinkFcipReceivedSfDuplicates OBJECT-TYPE 1014 SYNTAX Counter32 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "The number of times duplicate FCIP Special Frames were received 1019 on this FCIP Link. The last discontinuity of this counter is 1020 indicated by fcipLinkCreateTime." 1021 ::= { fcipLinkErrorsEntry 6 } 1023 fcipLinkFcipSfInvalidWWNs OBJECT-TYPE 1024 SYNTAX Counter32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The number of times FCIP Special Frames with invalid 1029 destination FC Fabric Entity WWN received on this FCIP Link. 1030 The last discontinuity of this counter is indicated by 1031 fcipLinkCreateTime." 1032 ::= { fcipLinkErrorsEntry 7 } 1034 fcipLinkFcipBB2LkaTimeOuts OBJECT-TYPE 1035 SYNTAX Counter32 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The number of FC Keep Alive Time outs that occurred on 1040 this FCIP Link. The last discontinuity of this counter 1041 is indicated by fcipLinkCreateTime." 1042 ::= { fcipLinkErrorsEntry 8 } 1044 fcipLinkFcipSntpExpiredTimeStamps OBJECT-TYPE 1045 SYNTAX Counter32 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "The number of frames discarded due to an expired SNTP timestamp 1050 on this FCIP Link. The last discontinuity of this counter is 1051 indicated by fcipLinkCreateTime." 1052 ::= { fcipLinkErrorsEntry 9 } 1054 fcipLinkTcpTooManyErrors OBJECT-TYPE 1055 SYNTAX Counter32 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "The number of TCP connections that closed down on this 1060 FCIP Link due to too many errors on the connection. The 1061 last discontinuity of this counter is indicated by 1062 fcipLinkCreateTime." 1063 ::= { fcipLinkErrorsEntry 10 } 1065 fcipLinkTcpExcessiveDroppedDatagrams OBJECT-TYPE 1066 SYNTAX Counter32 1067 MAX-ACCESS read-only 1068 STATUS current 1069 DESCRIPTION 1070 "The number of TCP connections that closed down on this 1071 FCIP Link due to an excessive number of dropped FCIP packets. 1072 The last discontinuity of this counter is indicated by 1073 fcipLinkCreateTime." 1074 ::= { fcipLinkErrorsEntry 11 } 1076 fcipLinkTcpSaParamMismatches OBJECT-TYPE 1077 SYNTAX Counter32 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "The number of times TCP connections with Security Association 1082 parameter mismatches closed down on this FCIP Link. The last 1083 discontinuity of this counter is indicated by 1084 fcipLinkCreateTime." 1085 REFERENCE "RFC 3821, Section 9.4.2, TCP Connection Security 1086 Associations (SAs)" 1087 ::= { fcipLinkErrorsEntry 12 } 1089 -- ****************************************************************** 1090 -- Conformance Statements 1091 -- 1093 fcipCompliances OBJECT IDENTIFIER ::= { fcipConformance 1 } 1094 fcipGroups OBJECT IDENTIFIER ::= { fcipConformance 2 } 1096 fcipCompliance MODULE-COMPLIANCE 1097 STATUS current 1098 DESCRIPTION 1099 "Compliance statement for FCIP MIB." 1100 MODULE -- this module 1101 MANDATORY-GROUPS { 1102 fcipEntityScalarGroup, 1103 fcipEntityInstanceGroup, 1104 fcipLinkGroup, 1105 fcipTcpConnGroup, 1106 fcipDiscoveryDomainGroup, 1107 fcipLinkErrorsGroup 1108 } 1110 GROUP fcipDynamicRouteGroup 1111 DESCRIPTION 1112 "This group is mandatory only for systems which do not 1113 have these objects in any other FC MIB. It may be 1114 implemented even in that case for convenience." 1116 GROUP fcipStaticRouteGroup 1117 DESCRIPTION 1118 "This group is mandatory only for systems which do not 1119 have these objects in any other FC MIB. It may be 1120 implemented even in that case for convenience." 1122 OBJECT fcipEntityAddressType 1123 SYNTAX INTEGER { ipv4(1), ipv6(2) } 1124 DESCRIPTION 1125 "Only IPv4 and IPv6 address types need to be supported for 1126 addressing FCIP entities. " 1128 OBJECT fcipEntityAddress 1129 SYNTAX InetAddress (SIZE(4|16)) 1130 DESCRIPTION 1131 "Size of FCIP entity's IP address depends on address type. 1132 FCIP entity address size is four if the IP address is IPv4 1133 and sixteen if the IP address type is IPv6." 1135 OBJECT fcipLinkLocalFcipEntityAddressType 1136 SYNTAX INTEGER { ipv4(1), ipv6(2) } 1137 DESCRIPTION 1138 "Only IPv4 and IPv6 address types need to be supported for 1139 addressing the local FCIP entities. " 1141 OBJECT fcipLinkLocalFcipEntityAddress 1142 SYNTAX InetAddress (SIZE(4|16)) 1143 DESCRIPTION 1144 "Size of FCIP entity's IP address depends on address type. 1145 FCIP entity address size is four if the IP address is IPv4 1146 and sixteen if the IP address type is IPv6." 1148 OBJECT fcipLinkRemFcipEntityAddressType 1149 SYNTAX INTEGER { ipv4(1), ipv6(2) } 1150 DESCRIPTION 1151 "Only IPv4 and IPv6 address types need to be supported for 1152 addressing the remote FCIP entities. " 1154 OBJECT fcipLinkRemFcipEntityAddress 1155 SYNTAX InetAddress (SIZE(4|16)) 1156 DESCRIPTION 1157 "Size of FCIP entity's IP address depends on the address 1158 type. FCIP entity address size is four if the IP address 1159 is IPv4 and sixteen if the IP address type is IPv6." 1161 ::= { fcipCompliances 1 } 1163 fcipEntityScalarGroup OBJECT-GROUP 1164 OBJECTS { fcipDynIpConfType, 1165 fcipDeviceWWN, 1166 fcipEntitySACKOption 1167 } 1168 STATUS current 1169 DESCRIPTION 1170 "Collection of scalar objects applicable to all FCIP instances." 1171 ::= { fcipGroups 1 } 1173 fcipEntityInstanceGroup OBJECT-GROUP 1174 OBJECTS { 1175 fcipEntityName, 1176 fcipEntityAddressType, 1177 fcipEntityAddress, 1178 fcipEntityTcpConnPort, 1179 fcipEntitySeqNumWrap, 1180 fcipEntityPHBSupport, 1181 fcipEntityStatus 1182 } 1183 STATUS current 1184 DESCRIPTION 1185 "A collection of objects providing information about FCIP 1186 instances." 1187 ::= { fcipGroups 2 } 1189 fcipLinkGroup OBJECT-GROUP 1190 OBJECTS { 1191 fcipLinkIfIndex, 1192 fcipLinkCost, 1193 fcipLinkLocalFcipEntityMode, 1194 fcipLinkLocalFcipEntityAddressType, 1195 fcipLinkLocalFcipEntityAddress, 1196 fcipLinkRemFcipEntityWWN, 1197 fcipLinkRemFcipEntityId, 1198 fcipLinkRemFcipEntityAddressType, 1199 fcipLinkRemFcipEntityAddress, 1200 fcipLinkStatus, 1201 fcipLinkCreateTime 1202 } 1203 STATUS current 1204 DESCRIPTION 1205 "A collection of objects providing information about FCIP 1206 Links." 1207 ::= { fcipGroups 3 } 1209 fcipTcpConnGroup OBJECT-GROUP 1210 OBJECTS { 1211 fcipTcpConnRWSize, 1212 fcipTcpConnMSS 1213 } 1214 STATUS current 1215 DESCRIPTION 1216 "A collection of objects providing information about FCIP 1217 TCP connections." 1218 ::= { fcipGroups 4 } 1220 fcipDiscoveryDomainGroup OBJECT-GROUP 1221 OBJECTS { 1222 fcipDiscoveryDomainName 1223 } 1224 STATUS current 1225 DESCRIPTION 1226 "A collection of objects providing information about FCIP 1227 Discovery Domains." 1228 ::= { fcipGroups 5 } 1230 fcipLinkErrorsGroup OBJECT-GROUP 1231 OBJECTS { 1232 fcipLinkFcipLossofFcSynchs, 1233 fcipLinkFcipEncapErrors, 1234 fcipLinkFcipNotReceivedSfResps, 1235 fcipLinkFcipSfRespMismatches, 1236 fcipLinkFcipSfInvalidNonces, 1237 fcipLinkFcipReceivedSfDuplicates, 1238 fcipLinkFcipSfInvalidWWNs, 1239 fcipLinkFcipBB2LkaTimeOuts, 1240 fcipLinkFcipSntpExpiredTimeStamps, 1241 fcipLinkTcpTooManyErrors, 1242 fcipLinkTcpExcessiveDroppedDatagrams, 1243 fcipLinkTcpSaParamMismatches 1244 } 1245 STATUS current 1246 DESCRIPTION 1247 "A collection of objects providing information about FCIP 1248 link errors." 1250 ::= { fcipGroups 6 } 1252 fcipDynamicRouteGroup OBJECT-GROUP 1253 OBJECTS { 1254 fcipDynamicRouteLinkIndex 1255 } 1256 STATUS current 1257 DESCRIPTION 1258 "A collection of objects providing information about FCIP 1259 dynamic routes." 1260 ::= { fcipGroups 7 } 1262 fcipStaticRouteGroup OBJECT-GROUP 1263 OBJECTS { 1264 fcipStaticRouteLinkIndex, 1265 fcipStaticRouteStatus 1266 } 1267 STATUS current 1268 DESCRIPTION 1269 "A collection of objects providing information about FCIP 1270 static routes." 1271 ::= { fcipGroups 8 } 1273 END 1274 5. Security considerations 1276 There are a number of management objects defined in this MIB that 1277 have a MAX-ACCESS clause of read-write and/or read-create. Such 1278 objects may be considered sensitive or vulnerable in some network 1279 environments. The support for SET operations in a non-secure 1280 environment without proper protection can have a negative effect on 1281 network operations. In particular, write access to 1282 fcipDiscoveryDomainName and fcipEntityAddress can cause a loss of 1283 reachability to portions of the SAN, while write access to 1284 fcipStaticRouteStatus can create incorrect routes to remote devices. 1286 There are a number of managed objects in this MIB that contain what 1287 could be considered as sensitive information. In particular, the 1288 objects which provide information on identification and network 1289 topology: 1291 fcipDeviceWWN, fcipEntityName, fcipEntityAddress, 1292 fcipLinkLocalFcipEntityAddress, fcipLinkRemFcipEntityWWN, 1293 and fcipLinkRemFcipEntityAddress 1294 -- information on identification; 1296 fcipDiscoveryDomainName 1297 -- information on discovery domains; 1299 fcipDynamicRouteLinkIndex 1300 -- information on dynamic routes; 1302 fcipStaticRouteLinkIndex and fcipStaticRouteStatus 1303 -- information on static routes 1305 SNMP versions prior to SNMPv3 did not include adequate security. 1306 Even if the network itself is secure (for example by using IPSec), 1307 even then, there is no control as to who on the secure network is 1308 allowed to access and GET/SET (read/change/create/delete) the objects 1309 in this MIB module. 1311 It is RECOMMENDED that implementers consider the security features as 1312 provided by the SNMPv3 framework (see [RFC3410], section 8), 1313 including full support for the SNMPv3 cryptographic mechanisms (for 1314 authentication and privacy). 1316 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1317 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1318 enable cryptographic security. It is then a customer/operator 1319 responsibility to ensure that the SNMP entity giving access to an 1320 instance of this MIB module is properly configured to give access to 1321 the objects only to those principals (users) that have legitimate 1322 rights to indeed GET or SET (change/create/delete) them. 1324 6. IANA Considerations 1326 IANA is requested to make a MIB OID assignment under the transmission 1327 branch. Specifically, { transmission 224 } is requested 1328 as the OID for fcipMIB because this MIB contains 1329 the media-specific definitions that correspond to the ifType 1330 value of fcipLink(224). 1332 7. Intellectual Property 1334 The IETF takes no position regarding the validity or scope of any 1335 Intellectual Property Rights or other rights that might be claimed 1336 to pertain to the implementation or use of the technology 1337 described in this document or the extent to which any license 1338 under such rights might or might not be available; nor does it 1339 represent that it has made any independent effort to identify any 1340 such rights. Information on the procedures with respect to 1341 rights in RFC documents can be found in BCP 78 and BCP 79. 1343 Copies of IPR disclosures made to the IETF Secretariat and any 1344 assurances of licenses to be made available, or the result of an 1345 attempt made to obtain a general license or permission for the use 1346 of such proprietary rights by implementers or users of this 1347 specification can be obtained from the IETF on-line IPR repository 1348 at http://www.ietf.org/ipr. 1350 The IETF invites any interested party to bring to its attention 1351 any copyrights, patents or patent applications, or other 1352 proprietary rights that may cover technology that may be required 1353 to implement this standard. Please address the information to the 1354 IETF at ietf-ipr@ietf.org. 1356 8. Acknowledgements 1358 The authors acknowledge significant feedback and guidance from NM 1359 Area advisor Keith McCloghrie, Cisco. Comments and input from 1360 members of the FCIP Working Group have also been incorporated. 1362 Funding for the RFC Editor function is currently provided by the 1363 Internet Society. 1365 9. Normative References: 1367 [RFC3821] Rajagopal, M., et al "Fibre Channel Over TCP/IP (FCIP)", 1368 RFC 3821, July 2004. 1370 [FCBB2] Fibre Channel Backbone -2 v6 (FC-BB-2), T11/03-078v0, 1371 February 2003. 1373 [FC-SW-3] Fibre Channel Switch Fabric -3 (FC-SW-3), T11/03-018v4, 1374 December 2003. 1376 [RFC4044] McCloghrie, K., "Fibre Channel Management MIB", 1377 RFC 4044, May 2005. 1379 [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1380 MIB", RFC 2863, June 2000. 1382 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1383 Rose, M., and S. Waldbusser, "Structure of Management 1384 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1385 1999. 1387 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 1388 Architecture for Describing SNMP Management Frameworks", 1389 RFC 3411, December 2002. 1391 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1392 Rose, M., and S. Waldbusser, "Textual Conventions for 1393 SMIv2", STD 58, RFC 2579, April 1999. 1395 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1396 Rose, M., and S. Waldbusser, "Conformance Statements for 1397 SMIv2", STD 58, RFC 2580, April 1999. 1399 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition 1400 of the DS Field in the IPv4 Headers", RFC 2474, 1401 December 1998. 1403 [RFC4022] McCloghrie, K., "Management Information Base for the 1404 Transmission Control Protocol", RFC 4022, March 2005. 1406 [RFC3822] Peterson, D., "Finding Fibre Channel over TCP/IP (FCIP) 1407 Entities Using Service Location Protocol version 2 (SLPv2)", 1408 RFC 3822, July 2004. 1410 [RFC2883] Floyd, S., Mahdavi, J., Mathis, M., and M. Podolsky, 1411 "An Extension to the Selective Acknowledgement (SACK) Option 1412 for TCP", RFC 2883, July 2000. 1414 [RFC1323] Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for 1415 High Performance", RFC 1323, May 1992. 1417 10. Informative References 1419 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1420 "Introduction and Applicability Statements for Internet- 1421 Standard Management Framework", RFC 3410, December 2002. 1423 11. Authors' Addresses 1425 Anil Rijhsinghani 1426 Accton Technology Corporation 1427 5 Mount Royal Ave 1428 Marlboro, MA 01752 1429 USA 1430 E-mail: anil@charter.net 1432 Ravi Natarajan 1433 F5 Networks 1434 181 Metro Drive Suite 400 1435 San Jose, CA 95110 1436 USA 1437 E-mail: r.natarajan@f5.com 1439 12. Disclaimer of Validity 1441 This document and the information contained herein are provided on 1442 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1443 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 1444 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 1445 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1446 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1447 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1449 13. Copyright Statement 1451 Copyright (C) The Internet Society (2005). This document is subject 1452 to the rights, licenses and restrictions contained in BCP 78, and 1453 except as set forth therein, the authors retain all their rights.