idnits 2.17.1 draft-ietf-ips-fcmgmt-mib-06.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 3667, Section 5.1 on line 13. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 32), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 32. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ( - It does however have an RFC 2026 Section 10.4(A) Disclaimer.) ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation -- however, there's a paragraph with a matching beginning. Boilerplate error? ( - It does however have an RFC 2026 Section 10.4(B) IPR Disclosure Invitation.) ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 6 characters in excess of 72. ** 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 299: '... this object SHOULD reflect the ma...' RFC 2119 keyword, line 369: '... SHOULD reflect the ma...' RFC 2119 keyword, line 2792: '...It is RECOMMENDED that implementors co...' RFC 2119 keyword, line 2797: '...ns prior to SNMPv3 is NOT RECOMMENDED....' RFC 2119 keyword, line 2798: '...Instead, it is RECOMMENDED to deploy S...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2605 has weird spacing: '...imed to perta...' == Line 2845 has weird spacing: '...unknown for ...' == Line 2851 has weird spacing: '...NL_Port see...' == Line 2853 has weird spacing: '...FL_Port see...' == Line 2857 has weird spacing: '...GL_Port see...' == (4 more instances...) -- 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 (17 December 2004) is 7063 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: 'FC-SW-3' is mentioned on line 2857, but not defined == Unused Reference: 'FC-AL' is defined on line 2673, but no explicit reference was found in the text == Unused Reference: 'FC-BB' is defined on line 2681, but no explicit reference was found in the text == Unused Reference: 'FCP' is defined on line 2684, but no explicit reference was found in the text == Unused Reference: 'FC-FLA' is defined on line 2687, but no explicit reference was found in the text == Unused Reference: 'FC-PH' is defined on line 2703, but no explicit reference was found in the text == Unused Reference: 'FC-SW' is defined on line 2707, but no explicit reference was found in the text == Unused Reference: 'FC-SW2' is defined on line 2711, but no explicit reference was found in the text == Unused Reference: 'RFC2837' is defined on line 2721, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 2737 (Obsoleted by RFC 4133) -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-AL' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-AL-2' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-BB' -- Possible downref: Non-RFC (?) normative reference: ref. 'FCP' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FLA' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FS' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-GS-3' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-MI' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-PH' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW2' -- Obsolete informational reference (is this intentional?): RFC 2837 (Obsoleted by RFC 4044) Summary: 15 errors (**), 0 flaws (~~), 17 warnings (==), 15 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Keith McCloghrie 3 Cisco Systems, Inc 4 17 December 2004 6 Fibre Channel Management MIB 7 draft-ietf-ips-fcmgmt-mib-06.txt 9 Status of this Memo 11 By submitting this Internet-Draft, I certify that any applicable patent 12 or other IPR claims of which I am aware have been disclosed, and any of 13 which I become aware will be disclosed, in accordance with RFC 3668. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet- Drafts as reference material 22 or to cite them other than as "work in progress". 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Copyright Notice 32 Copyright (C) The Internet Society (2004). All Rights Reserved. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) for 37 use with network management protocols in the Internet community. In 38 particular, it describes managed objects for information related to 39 Fibre Channel. 41 Table of Contents 43 1 Introduction .................................................... 3 44 2 The Internet-Standard Management Framework ...................... 3 45 3 Short Overview of Fibre Channel ................................. 3 46 4 MIB Overview .................................................... 4 47 4.1 The fcmInstanceBasicGroup group ............................... 4 48 4.2 The fcmSwitchBasicGroup group ................................. 4 49 4.3 The fcmPortBasicGroup group ................................... 4 50 4.4 The fcmPortStatsGroup group ................................... 5 51 4.5 The fcmPortClass23StatsGroup group ............................ 5 52 4.6 The fcmPortLcStatsGroup group ................................. 5 53 4.7 The fcmPortClassFStatsGroup group ............................. 5 54 4.8 The fcmPortErrorsGroup group .................................. 5 55 4.9 The fcmSwitchPortGroup group .................................. 5 56 4.10 The fcmSwitchLoginGroup group ................................ 6 57 4.11 The fcmLinkBasicGroup group .................................. 6 58 5 Relationship to Other MIBs ...................................... 6 59 5.1 The Interfaces Group MIB ...................................... 6 60 5.2 Entity MIB .................................................... 9 61 5.3 Host Resources MIB ............................................ 10 62 6 Definitions ..................................................... 11 63 7 Intellectual Property ........................................... 63 64 8 Acknowledgements ................................................ 63 65 9 Normative References ............................................ 63 66 10 Informative References ......................................... 65 67 11 Security Considerations ........................................ 66 68 12 IANA Considerations ............................................ 67 69 12.1 OID Assignment ............................................... 67 70 12.2 FC Port Type Registry ........................................ 67 71 13 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 70 72 14 Comparison to RFC 2837 ......................................... 77 73 15 Author's Address ............................................... 78 74 16 Full Copyright Statement ....................................... 78 75 1. Introduction 77 This memo defines a portion of the Management Information Base (MIB) for 78 use with network management protocols in the Internet community. In 79 particular, it describes managed objects for information related to 80 Fibre Channel. 82 2. The Internet-Standard Management Framework 84 For a detailed overview of the documents that describe the current 85 Internet-Standard Management Framework, please refer to section 7 of RFC 86 3410 [RFC3410]. 88 Managed objects are accessed via a virtual information store, termed the 89 Management Information Base or MIB. MIB objects are generally accessed 90 through the Simple Network Management Protocol (SNMP). Objects in the 91 MIB are defined using the mechanisms defined in the Structure of 92 Management Information (SMI). This memo specifies a MIB module that is 93 compliant to the SMIv2, which is described in STD 58, RFC 2578 94 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 96 3. Short Overview of Fibre Channel 98 The Fibre Channel (FC) is logically a bidirectional point-to-point 99 serial data channel, structured for high performance capability. The 100 Fibre Channel provides a general transport vehicle for higher level 101 protocols such as Intelligent Peripheral Interface (IPI) and Small 102 Computer System Interface (SCSI) command sets, the High-Performance 103 Parallel Interface (HIPPI) data framing, IP (Internet Protocol), IEEE 104 802.2, and others. 106 Physically, Fibre Channel is an interconnection of multiple 107 communication points, called N_Ports, interconnected either by a 108 switching network, called a Fabric, or by a point-to-point link. A 109 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 110 consist of multiple Interconnect Elements, some of which are switches. 111 An N_Port connects to the Fabric via a port on a switch called an 112 F_Port. When multiple FC nodes are connected to a single port on a 113 switch via an "Arbitrated Loop" topology, the switch port is called an 114 FL_Port, and the nodes' ports are called NL_Ports. The term Nx_Port is 115 used to refer to either an N_Port or an NL_port. The term Fx_Port is 116 used to refer to either an F_Port or an FL_port. A switch port, which 117 is interconnected to another switch port via an Inter Element Link 118 (IEL), is called an E_Port. A B_Port connects a bridge device with an 119 E_Port on a switch; a B_Port provides a subset of E_Port functionality. 121 Many Fibre Channel components, including the fabric, each node, and most 122 ports, have globally-unique names. These globally-unique names are 123 typically formatted as World Wide Names (WWNs). More information on 124 WWNs can be found in [WWN1] and [WWN2]. WWNs are expected to be 125 persistent across agent and unit resets. 127 Fibre Channel frames contain 24-bit address identifiers which identify 128 the frame's source and destination ports. Each FC port has an address 129 identifier and a WWN. When a fabric is in use, the FC address 130 identifiers are dynamic and are assigned by a switch. 132 4. MIB Overview 134 This MIB contains the notion of a Fibre Channel management instance, 135 which is defined as a separable managed instance of Fibre Channel 136 functionality. Fibre Channel functionality may be grouped into Fibre 137 Channel management instances in whatever way is most convenient for the 138 implementation(s). For example, one such grouping accommodates a single 139 SNMP agent having multiple AgentX [RFC2741] sub-agents, with each sub- 140 agent implementing a different Fibre Channel management instance. In 141 order to represent such multiple Fibre Channel management instances 142 within the same SNMP context (see section 3.3.1 of [RFC3411]), all 143 tables in this MIB are INDEX-ed by fcmInstanceIndex which is defined as 144 an arbitrary integer to uniquely identify a particular Fibre Channel 145 management instance. 147 This MIB contains eleven MIB groups, as follows. 149 4.1. The fcmInstanceBasicGroup group 151 This group contains basic information about a Fibre Channel managed 152 instance, including its name and description, the Fibre Channel 153 function(s) it performs, and optional pointers to hardware and/or 154 software components. 156 4.2. The fcmSwitchBasicGroup group 158 This group contains basic information about a Fibre Channel switch, 159 including its domain-id and whether it is the principal switch of its 160 fabric. 162 4.3. The fcmPortBasicGroup group 164 This group contains basic information about a Fibre Channel port, 165 including its port name (WWN), the name of the node (if any) of which it 166 is a part, the type of port, the classes of service it supports, its 167 transmitter and connector types, and the higher level protocols it 168 supports. 170 Each Fibre Channel port is represented by an entry in the ifTable (see 171 below). The tables relating to ports in this MIB are indexed by the 172 port's value of ifIndex. 174 4.4. The fcmPortStatsGroup group 176 This group contains traffic statistics, which are not specific to any 177 particular class of service, for Fibre Channel ports. 179 4.5. The fcmPortClass23StatsGroup group 181 This group contains traffic statistics which are specific to Class 2 or 182 Class 3 traffic on Fibre Channel ports, including class-specific frame 183 and octet counters and counters of busy and reject frames. 185 4.6. The fcmPortLcStatsGroup group 187 Some of the statistics in the fcmPortClass23StatsGroup can increase 188 rapidly enough to warrant them being defined using the Counter64 syntax. 189 However, some old SNMP systems do not (yet) support Counter64 objects. 190 Thus, this group defines low-capacity (Counter32-based) equivalents for 191 the Counter64-based statistics in the fcmPortClass23StatsGroup group. 193 4.7. The fcmPortClassFStatsGroup group 195 This group contains traffic statistics which are specific to Class F 196 traffic on the E_Ports of a Fibre Channel switch. 198 4.8. The fcmPortErrorsGroup group 200 This group contains counters of various error conditions which can occur 201 on Fibre Channel ports. 203 4.9. The fcmSwitchPortGroup group 205 This group contains information about ports on a Fibre Channel switch. 206 For an Fx_Port, it includes the port's timeout values, its hold-time, 207 and its capabilities in terms of maximum and minimum buffer-to-buffer 208 credit allocations, maximum and minimum data field size, and support for 209 class 2 and class 3 sequenced delivery. For an E_Port or B_Port, it 210 includes the buffer-to-buffer credit allocation and data field size. 212 4.10. The fcmSwitchLoginGroup group 214 This group contains information, known to a Fibre Channel switch, about 215 its attached/logged-in Nx_Ports and the service parameters which have 216 been agreed with them. 218 4.11. The fcmLinkBasicGroup group 220 This group contains information, known to a local Fibre Channel 221 management instance, about Fibre Channel links, including links which 222 terminate locally. 224 5. Relationship to Other MIBs 226 This MIB is a replacement for two other MIBs: RFC 2837, and the Fibre 227 Channel Management Integration MIB which was originally submitted as an 228 Internet Draft to the IETF's IPFC Working Group as draft-ietf-ipfc- 229 fcmgmt-int-mib-0n.txt. 231 5.1. The Interfaces Group MIB 233 The Interfaces Group MIB [RFC2863] contains generic information about 234 all lower layer interfaces, i.e., interfaces which are (potentially) 235 below the internet layer. Thus, each Fibre Channel port should have its 236 own row in the ifTable, and that row will contain the generic 237 information about the interface/port. The Interfaces Group MIB 238 specifies that additional information which is specific to a particular 239 type of interface media, should be defined in a media-specific MIB. 240 This MIB is the media-specific MIB for Fibre Channel ports/interfaces. 242 Section 4 of [RFC2863] requires that a media-specific MIB clarify how 243 the generic definitions apply for the particular type of media. The 244 clarifications for Fibre Channel interfaces are as follows. 246 5.1.1. Layering Model 248 The Interfaces Group MIB permits multiple ifTable entries to be defined 249 for interface sub-layers, and for those multiple entries to be arranged 250 in a stack. 252 For Fibre Channel interfaces, no sublayers are defined and a Fibre 253 Channel interface will typically have no other ifTable rows stacked on 254 top of it, nor underneath it. 256 5.1.2. Virtual Circuits 258 This Fibre Channel MIB does not deal with virtual circuits. 260 5.1.3. ifRcvAddressTable 262 The ifRcvAddressTable does not apply to Fibre Channel interfaces. 264 5.1.4. ifType 266 The value of ifType for a Fibre Channel interface is 56. 268 5.1.5. ifXxxOctets 270 The definitions of ifInOctets and ifOutOctets (and similarly, 271 ifHCInOctets and ifHCOutOctets) specify that their values include 272 framing characters. For Fibre Channel interfaces, they include all the 273 octets contained in frames between the Start-of-Frame and End-of-Frame 274 delimiters (excluding the delimiters). 276 5.1.6. Specific Interface Group MIB Objects 278 The following table provides specific implementation guidelines for 279 applying the objects defined in the Interfaces Group MIB to Fibre 280 Channel interfaces. For those objects not listed here, refer to their 281 generic definitions in [RFC2863]. (RFC 2863 takes precedence over these 282 guidelines in the event of any conflict.) 284 Object Guidelines 286 ifType 56 288 ifMtu The MTU as seen by a higher layer 289 protocol, like IP. That is, when IP is 290 running over the interface, this object is 291 the size of the largest IP datagram that 292 can be sent/received over the interface. 294 ifSpeed For 1Gbs, this will be 1,000,000,000; for 295 2Gbs, it will be 2,000,000,000. If auto- 296 negotiation is implemented and enabled on 297 an interface, and the interface has not 298 yet negotiated to an operational speed, 299 this object SHOULD reflect the maximum 300 speed supported by the interface. 302 ifPhysAddress The interface's 24-bit Fibre Channel 303 Address Identifier, or the zero-length 304 string if no Address Identifier has been 305 assigned to the interface. 307 ifAdminStatus Write access is not required, and support 308 for 'testing' is not required. 310 ifOperStatus Support for 'testing' is not required. 311 The value 'dormant' has no meaning for 312 Fibre Channel interfaces. 314 ifInOctets The number of octets of information 315 ifHCInOctets contained in received frames between the 316 Start-of-Frame and End-of-Frame delimiters 317 (excluding the delimiters). 319 ifInUcastPkts The number of unicast frames received, 320 ifHCInUcastPkts i.e., the number of Start-of-Frame 321 delimiters received for unicast frames. 323 ifInErrors The sum for this interface of 325 fcmPortLossofSynchs 326 fcmPortLossofSignals 327 fcmPortPrimSeqProtocolErrors 328 fcmPortInvalidTxWords 329 fcmPortInvalidCRCs 330 fcmPortAddressErrors 331 fcmPortDelimiterErrors 332 fcmPortTruncatedFrames 333 fcmPortEncodingDisparityErrors 335 plus any errors in fcmPortOtherErrors 336 which were input errors. 338 ifOutOctets The number of octets of information 339 ifHCOutOctets contained in transmitted frames between 340 the Start-of-Frame and End-of-Frame 341 delimiters (excluding the delimiters). 343 ifOutUcastPkts The number of frames transmitted, 344 ifHCOutUcastPkts i.e., the number of start-of-frame 345 delimiters transmitted for unicast frames. 347 ifOutErrors This is the number of errors in 348 fcmPortOtherErrors which were output 349 errors. 351 ifInMulticastPkts These counters are not incremented 352 ifInBroadcastPkts (unless a proprietary mechanism for 353 ifOutMulticastPkts multicast/broadcast is supported). 354 ifOutBroadcastPkts 355 ifHCInMulticastPkts 356 ifHCInBroadcastPkts 357 ifHCOutMulticastPkts 358 ifHCOutBroadcastPkts 360 ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled' 362 ifHighSpeed The current operational speed of the 363 interface in millions of bits per second. 364 For 1Gbs, this will be 1000; for 2Gbs, it 365 will be 2000. If auto-negotiation is 366 implemented and enabled on an interface, 367 and the interface has not yet negotiated 368 to an operational speed, this object 369 SHOULD reflect the maximum speed supported 370 by the interface. 372 ifPromiscuousMode This will normally be 'false' 374 ifConnectorPresent This will normally be 'true'. 376 5.2. Entity MIB 378 The Entity MIB [RFC2737] contains information about individual physical 379 components and any hierarchical relationship which may exist between 380 them. Any Fibre Channel management instance with a relationship to a 381 physical component (or to a hierarchy of physical components) will have 382 its value of the fcmInstancePhysicalIndex object contain a pointer to 383 the relevant row in the Entity MIB. If there is no correspondence to a 384 physical component (or said component does not have a row in the Entity 385 MIB), then the value of fcmInstancePhysicalIndex is zero. (Note that an 386 implementation is not required to support a non-zero value of 387 fcmInstancePhysicalIndex.) 388 5.3. Host Resources MIB 390 The Host Resources MIB [RFC2790] includes information about installed 391 software modules. Any Fibre Channel management instance with a 392 correspondence to a software module, will have its value of the 393 fcmInstanceSoftwareIndex object contain a pointer to the relevant row in 394 the Host Resources MIB. If there is no correspondence to a software 395 module (or said software module does not has a row in the Host Resources 396 MIB), then the value of fcmInstanceSoftwareIndex is zero. (Note that an 397 agent implementation is not required to support a non-zero value of 398 fcmInstanceSoftwareIndex.) 399 6. Definitions 401 FC-MGMT-MIB DEFINITIONS ::= BEGIN 403 IMPORTS 404 MODULE-IDENTITY, OBJECT-TYPE, 405 Integer32, Unsigned32, Counter32, Counter64, transmission 406 FROM SNMPv2-SMI 407 MODULE-COMPLIANCE, OBJECT-GROUP 408 FROM SNMPv2-CONF 409 TruthValue, TEXTUAL-CONVENTION 410 FROM SNMPv2-TC 411 ifIndex FROM IF-MIB 412 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 414 fcMgmtMIB MODULE-IDENTITY 415 LAST-UPDATED "200412140000Z" 416 ORGANIZATION "IETF IPS (IP-Storage) Working Group" 417 CONTACT-INFO 418 " Keith McCloghrie 419 Cisco Systems, Inc. 420 Tel: +1 408 526-5260 421 E-mail: kzm@cisco.com 422 Postal: 170 West Tasman Drive 423 San Jose, CA USA 95134 424 " 425 DESCRIPTION 426 "This module defines management information specific to 427 Fibre Channel-attached devices. 429 Copyright (C) The Internet Society (2004). This version of 430 this MIB module is part of RFC yyyy; see the RFC itself for 431 full legal notices." 432 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 433 REVISION "200412140000Z" 434 DESCRIPTION 435 "Initial version of the Fibre Channel Mgmt MIB module." 436 ::= { transmission nnn } -- IANA, please enter the value you assign here 438 fcmgmtObjects OBJECT IDENTIFIER ::= { fcMgmtMIB 1 } 439 fcmgmtNotifications OBJECT IDENTIFIER ::= { fcMgmtMIB 2 } 440 fcmgmtNotifPrefix OBJECT IDENTIFIER ::= { fcmgmtNotifications 0 } 441 fcmgmtConformance OBJECT IDENTIFIER ::= { fcMgmtMIB 3 } 442 --******************************** 443 -- Textual Conventions 444 -- 446 FcNameIdOrZero ::= TEXTUAL-CONVENTION 447 STATUS current 448 DESCRIPTION 449 "The World Wide Name (WWN) associated with a Fibre Channel 450 (FC) entity. WWNs were initially defined as 64-bits in 451 length. The latest definition (for future use) is 128-bits 452 long. The zero-length string value is used in circumstances 453 where the WWN is unassigned/unknown." 454 SYNTAX OCTET STRING (SIZE(0 | 8 | 16)) 456 FcAddressIdOrZero ::= TEXTUAL-CONVENTION 457 STATUS current 458 DESCRIPTION 459 "A Fibre Channel Address ID, a 24-bit value unique within 460 the address space of a Fabric. The zero-length string value 461 is used in circumstances where the WWN is 462 unassigned/unknown." 463 SYNTAX OCTET STRING (SIZE(0 | 3)) 465 FcDomainIdOrZero ::= TEXTUAL-CONVENTION 466 STATUS current 467 DESCRIPTION 468 "The Domain Id (of a FC switch), or zero if the no Domain Id 469 has been assigned." 470 SYNTAX Integer32 (0..239) 472 FcPortType ::= TEXTUAL-CONVENTION 473 STATUS current 474 DESCRIPTION 475 "The type of a Fibre Channel port, as indicated by the use 476 of the appropriate value assigned by IANA." 477 REFERENCE 478 "The IANA-maintained registry for 479 Fibre Channel port types. " 480 -- IANA, please extend the text inside the immediately 481 -- preceeding quotes to include a location at which a 482 -- reader can ascertain the latest assigned values 483 SYNTAX Unsigned32 485 FcClasses ::= TEXTUAL-CONVENTION 486 STATUS current 487 DESCRIPTION 488 "A set of Fibre Channel classes of service." 489 REFERENCE 490 "Classes of service are described in FC-FS Section 13." 491 SYNTAX BITS { classF(0), class1(1), class2(2), class3(3), 492 class4(4), class5(5), class6(6) } 494 FcBbCredit ::= TEXTUAL-CONVENTION 495 STATUS current 496 DESCRIPTION 497 "The buffer-to-buffer credit of an FC port." 498 SYNTAX Integer32 (0..32767) 500 FcBbCreditModel ::= TEXTUAL-CONVENTION 501 STATUS current 502 DESCRIPTION 503 "The buffer-to-buffer credit model of an Fx_Port." 504 SYNTAX INTEGER { regular(1), alternate (2) } 506 FcDataFieldSize ::= TEXTUAL-CONVENTION 507 STATUS current 508 DESCRIPTION 509 "The Receive Data Field Size associated with an FC port." 510 SYNTAX Integer32 (128..2112) 512 FcUnitFunctions ::= TEXTUAL-CONVENTION 513 STATUS current 514 DESCRIPTION 515 "A set of functions that a Fibre Channel Interconnect 516 Element or Platform might perform. A value with no bits 517 set, indicates the function(s) are unknown. The individual 518 bits have the following meanings: 520 other - none of the following. 522 hub - a device that interconnects L_Ports, but does not 523 operate as an FL_Port. 525 switch - a fabric element conforming to the Fibre Channel 526 switch fabric set of standards (e.g., FC-SW, FC-SW-2). 528 bridge - a device that encapsulates Fibre Channel frames 529 within another protocol (e.g., FC-BB, FC-BB-2). 531 gateway - a device that converts an FC-4 to another protocol 532 (e.g., FCP to iSCSI). 534 host - a computer system that provides end users services 535 such as computation and storage access. 537 storageSubsys - an integrated collection of storage 538 controllers, storage devices, and necessary software, that 539 provides storage services to one or more hosts. 541 storageAccessDev - a device that provides storage management 542 and access for heterogeneous hosts and heterogeneous devices 543 (e.g., medium changer). 545 nas - a device that connects to a network and provides file 546 access services. 548 wdmux - a device that modulates/demodulates each of several 549 data streams (e.g., Fibre Channel protocol data streams) 550 onto/from a different part of the light spectrum in an 551 optical fiber. 553 storageDevice - a disk/tape/etc. device (without the 554 controller and/or software required for it to be a 555 'storageSubsys')." 556 SYNTAX BITS { 557 other(0), -- none of the following 558 hub(1), 559 switch(2), 560 bridge(3), 561 gateway(4), 562 host(5), 563 storageSubsys(6), 564 storageAccessDev(7), 565 nas(8), 566 wdmux(9), 567 storageDevice(10) 568 } 570 --******************************** 571 -- MIB object definitions 572 -- 574 fcmInstanceTable OBJECT-TYPE 575 SYNTAX SEQUENCE OF FcmInstanceEntry 576 MAX-ACCESS not-accessible 577 STATUS current 578 DESCRIPTION 579 "Information about the local Fibre Channel management 580 instances." 581 ::= { fcmgmtObjects 1 } 583 fcmInstanceEntry OBJECT-TYPE 584 SYNTAX FcmInstanceEntry 585 MAX-ACCESS not-accessible 586 STATUS current 587 DESCRIPTION 588 "A list of attributes for a particular local Fibre Channel 589 management instance." 590 INDEX { fcmInstanceIndex } 591 ::= { fcmInstanceTable 1 } 593 FcmInstanceEntry ::= 594 SEQUENCE { 595 fcmInstanceIndex Unsigned32, 596 fcmInstanceWwn FcNameIdOrZero, 597 fcmInstanceFunctions FcUnitFunctions, 598 fcmInstancePhysicalIndex Integer32, 599 fcmInstanceSoftwareIndex Integer32, 600 fcmInstanceStatus INTEGER, 601 fcmInstanceTextName SnmpAdminString, 602 fcmInstanceDescr SnmpAdminString, 603 fcmInstanceFabricId FcNameIdOrZero 604 } 606 fcmInstanceIndex OBJECT-TYPE 607 SYNTAX Unsigned32 (1..4294967295) 608 MAX-ACCESS not-accessible 609 STATUS current 610 DESCRIPTION 611 "An arbitrary integer value which uniquely identifies this 612 instance amongst all local Fibre Channel management 613 instances. 615 It is mandatory to keep this value constant between restarts 616 of the agent, and to make every possible effort to keep it 617 constant across restarts (but note, it is unrealistic to 618 expect it to remain constant across all re-configurations of 619 the local system, e.g., across the replacement of all non- 620 volatile storage)." 621 ::= { fcmInstanceEntry 1 } 623 fcmInstanceWwn OBJECT-TYPE 624 SYNTAX FcNameIdOrZero 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "If the instance has one (or more) WWN(s), then this object 629 contains that (or one of those) WWN(s). 631 If the instance does not have a WWN associated with it, then 632 this object contains the zero-length string." 633 ::= { fcmInstanceEntry 2 } 635 fcmInstanceFunctions OBJECT-TYPE 636 SYNTAX FcUnitFunctions 637 MAX-ACCESS read-only 638 STATUS current 639 DESCRIPTION 640 "One (or more) Fibre Channel unit functions being performed 641 by this instance." 642 ::= { fcmInstanceEntry 3 } 644 fcmInstancePhysicalIndex OBJECT-TYPE 645 SYNTAX Integer32 (0..2147483647) 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "If this management instance corresponds to a physical 650 component (or to a hierarchy of physical components) 651 identified by the Entity-MIB, then this object's value is 652 the value of the entPhysicalIndex of that component (or of 653 the component at the root of that hierarchy). If there is 654 no correspondence to a physical component (or no component 655 which has an entPhysicalIndex value), then the value of this 656 object is zero." 657 REFERENCE 658 "entPhysicalIndex is defined in the Entity MIB, RFC 2737." 659 ::= { fcmInstanceEntry 4 } 661 fcmInstanceSoftwareIndex OBJECT-TYPE 662 SYNTAX Integer32 (0..2147483647) 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "If this management instance corresponds to an installed 667 software module identified in the Host Resources MIB, then 668 this object's value is the value of the hrSWInstalledIndex 669 of that module. If there is no correspondence to an 670 installed software module (or no module which has a 671 hrSWInstalledIndex value), then the value of this object is 672 zero." 673 REFERENCE 674 "hrSWInstalledIndex is defined in the Host Resources MIB, 675 RFC 2790" 676 ::= { fcmInstanceEntry 5 } 678 fcmInstanceStatus OBJECT-TYPE 679 SYNTAX INTEGER { 680 unknown(1), 681 ok(2), -- able to operate correctly 682 warning(3), -- needs attention 683 failed(4) -- something has failed 684 } 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Overall status of the Fibre Channel entity/entities managed 689 by this management instance. The value should reflect the 690 most serious status of such entities." 691 ::= { fcmInstanceEntry 6 } 693 fcmInstanceTextName OBJECT-TYPE 694 SYNTAX SnmpAdminString (SIZE(0..79)) 695 MAX-ACCESS read-write 696 STATUS current 697 DESCRIPTION 698 "A textual name for this management instance and the Fibre 699 Channel entity/entities that it is managing." 700 ::= { fcmInstanceEntry 7 } 702 fcmInstanceDescr OBJECT-TYPE 703 SYNTAX SnmpAdminString 704 MAX-ACCESS read-write 705 STATUS current 706 DESCRIPTION 707 "A textual description of this management instance and the 708 Fibre Channel entity/entities that it is managing." 709 ::= { fcmInstanceEntry 8 } 711 fcmInstanceFabricId OBJECT-TYPE 712 SYNTAX FcNameIdOrZero 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "The globally unique Fabric Identifier which identifies the 717 fabric to which the Fibre Channel entity/entities managed by 718 this management instance are connected, or, of which they 719 are a part. This is typically the Node WWN of the principal 720 switch of a Fibre Channel fabric. The zero-length string 721 indicates that the fabric identifier is unknown (or not 722 applicable). 724 In the event that the Fibre Channel entity/entities managed 725 by this management instance is/are connected to multiple 726 fabrics, then this object records the first (known) one." 727 ::= { fcmInstanceEntry 9 } 729 --******************************** 730 -- The Fibre Channel Switch Table 731 -- 733 fcmSwitchTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF FcmSwitchEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "A table of information about Fibre Channel switches which 739 are managed by Fibre Channel management instances. Each 740 Fibre Channel management instance can manage one or more 741 Fibre Channel switches." 742 ::= { fcmgmtObjects 2 } 744 fcmSwitchEntry OBJECT-TYPE 745 SYNTAX FcmSwitchEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "Information about a particular Fibre Channel switch which 750 is managed by the management instance given by 751 fcmInstanceIndex." 752 INDEX { fcmInstanceIndex, fcmSwitchIndex } 753 ::= { fcmSwitchTable 1 } 755 FcmSwitchEntry ::= 756 SEQUENCE { 757 fcmSwitchIndex Unsigned32, 758 fcmSwitchDomainId FcDomainIdOrZero, 759 fcmSwitchPrincipal TruthValue, 760 fcmSwitchWWN FcNameIdOrZero 761 } 763 fcmSwitchIndex OBJECT-TYPE 764 SYNTAX Unsigned32 (1..4294967295) 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "An arbitrary integer which uniquely identifies a Fibre 769 Channel switch amongst those managed by one Fibre Channel 770 management instance. 772 It is mandatory to keep this value constant between restarts 773 of the agent, and to make every possible effort to keep it 774 constant across restarts." 775 ::= { fcmSwitchEntry 1 } 777 fcmSwitchDomainId OBJECT-TYPE 778 SYNTAX FcDomainIdOrZero 779 MAX-ACCESS read-write 780 STATUS current 781 DESCRIPTION 782 "The Domain Id of this switch. A value of zero indicates 783 that a switch has not (yet) been assigned a Domain Id." 784 ::= { fcmSwitchEntry 2 } 786 fcmSwitchPrincipal OBJECT-TYPE 787 SYNTAX TruthValue 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "An indication of whether this switch is the principal 792 switch within its fabric." 793 ::= { fcmSwitchEntry 3 } 795 fcmSwitchWWN OBJECT-TYPE 796 SYNTAX FcNameIdOrZero 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "The World Wide Name of this switch." 801 ::= { fcmSwitchEntry 4 } 803 --******************************** 804 -- The Fibre Channel Port Table 805 -- 807 fcmPortTable OBJECT-TYPE 808 SYNTAX SEQUENCE OF FcmPortEntry 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "Information about Fibre Channel ports. Each Fibre Channel 813 port is represented by one entry in the IF-MIB's ifTable." 814 REFERENCE 815 "RFC 2863, The Interfaces Group MIB, June 2000." 816 ::= { fcmgmtObjects 3 } 818 fcmPortEntry OBJECT-TYPE 819 SYNTAX FcmPortEntry 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "Each entry contains information about a specific port." 824 INDEX { ifIndex } 825 ::= { fcmPortTable 1 } 827 FcmPortEntry ::= 828 SEQUENCE { 829 fcmPortInstanceIndex Unsigned32, 830 fcmPortWwn FcNameIdOrZero, 831 fcmPortNodeWwn FcNameIdOrZero, 832 fcmPortAdminType FcPortType, 833 fcmPortOperType FcPortType, 834 fcmPortFcCapClass FcClasses, 835 fcmPortFcOperClass FcClasses, 836 fcmPortTransmitterType INTEGER, 837 fcmPortConnectorType INTEGER, 838 fcmPortSerialNumber SnmpAdminString, 839 fcmPortPhysicalNumber Unsigned32, 840 fcmPortAdminSpeed INTEGER, 841 fcmPortCapProtocols BITS, 842 fcmPortOperProtocols BITS 843 } 845 fcmPortInstanceIndex OBJECT-TYPE 846 SYNTAX Unsigned32 (1..4294967295) 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The value of fcmInstanceIndex by which the Fibre Channel 851 management instance, which manages this port, is identified 852 in the fcmInstanceTable." 853 ::= { fcmPortEntry 1 } 855 fcmPortWwn OBJECT-TYPE 856 SYNTAX FcNameIdOrZero 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "The World Wide Name of the port, or the zero-length string 861 if the port does not have a WWN." 862 ::= { fcmPortEntry 2 } 864 fcmPortNodeWwn OBJECT-TYPE 865 SYNTAX FcNameIdOrZero 866 MAX-ACCESS read-only 867 STATUS current 868 DESCRIPTION 869 "The World Wide Name of the Node which contains this port, 870 or the zero-length string if the port does not have a node 871 WWN." 872 ::= { fcmPortEntry 3 } 874 fcmPortAdminType OBJECT-TYPE 875 SYNTAX FcPortType 876 MAX-ACCESS read-write 877 STATUS current 878 DESCRIPTION 879 "The administratively desired type of this port." 880 ::= { fcmPortEntry 4 } 882 fcmPortOperType OBJECT-TYPE 883 SYNTAX FcPortType 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The current operational type of this port." 888 ::= { fcmPortEntry 5 } 890 fcmPortFcCapClass OBJECT-TYPE 891 SYNTAX FcClasses 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The classes of service capability of this port." 896 ::= { fcmPortEntry 6 } 898 fcmPortFcOperClass OBJECT-TYPE 899 SYNTAX FcClasses 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The classes of service that are currently operational on 904 this port. For an FL_Port, this is the union of the classes 905 being supported across all attached NL_Ports." 906 ::= { fcmPortEntry 7 } 908 fcmPortTransmitterType OBJECT-TYPE 909 SYNTAX INTEGER { 910 unknown(1), 911 other(2), 912 shortwave850nm(3), 913 longwave1550nm(4), 914 longwave1310nm(5), 915 electrical(6) 916 } 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The technology of the port transceiver." 921 REFERENCE 922 "FC-GS-3, section 6.1.2.2.3" 923 ::= { fcmPortEntry 8 } 925 fcmPortConnectorType OBJECT-TYPE 926 SYNTAX INTEGER { 927 unknown(1), 928 other(2), 929 gbic(3), 930 embedded(4), 931 glm(5), 932 gbicSerialId(6), 933 gbicNoSerialId(7), 934 sfpSerialId(8), 935 sfpNoSerialId(9) 936 } 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "The module type of the port connector. This object refers 941 to the hardware implementation of the port. It will be 942 'embedded' if the hardware equivalent to Gigabit interface 943 card (GBIC) is part of the line card and is unremovable. It 944 will be 'glm' if it's a gigabit link module (GLM). It will 945 be 'gbicSerialId' if the GBIC serial id can be read, else it 946 will be 'gbicNoSerialId'. It will be 'sfpSerialId', if the 947 small form factor (SFP) pluggable GBICs serial id can be 948 read, else it will be 'sfpNoSerialId'." 949 REFERENCE 950 "FC-GS-3, section 6.1.2.2.4" 951 ::= { fcmPortEntry 9 } 953 fcmPortSerialNumber OBJECT-TYPE 954 SYNTAX SnmpAdminString 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The serial number associated with the port (e.g., for a 959 GBIC). If not applicable, the object's value is a zero- 960 length string." 961 REFERENCE 962 "FC-GS-3, section 6.1.2.2.4" 963 ::= { fcmPortEntry 10 } 965 fcmPortPhysicalNumber OBJECT-TYPE 966 SYNTAX Unsigned32 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "This is the port's 'Physical Port Number' as defined by 971 GS-3." 972 REFERENCE 973 "FC-GS-3, section 6.1.2.2.5" 974 ::= { fcmPortEntry 11 } 976 fcmPortAdminSpeed OBJECT-TYPE 977 SYNTAX INTEGER { 978 auto(1), 979 eighthGbs(2), -- 125Mbs 980 quarterGbs(3), -- 250Mbs 981 halfGbs(4), -- 500Mbs 982 oneGbs(5), -- 1Gbs 983 twoGbs(6), -- 2Gbs 984 fourGbs(7), -- 4Gbs 985 tenGbs(8) -- 10Gbs 986 } 987 MAX-ACCESS read-write 988 STATUS current 989 DESCRIPTION 990 "The speed of the interface: 992 'auto' - auto-negotiation 993 'tenGbs' - 10Gbs 994 'fourGbs' - 4Gbs 995 'twoGbs' - 2Gbs 996 'oneGbs' - 1Gbs 997 'halfGbs' - 500Mbs 998 'quarterGbs' - 250Mbs 999 'eighthGbs' - 125Mbs" 1000 ::= { fcmPortEntry 12 } 1002 fcmPortCapProtocols OBJECT-TYPE 1003 SYNTAX BITS { 1004 unknown(0), 1005 loop(1), 1006 fabric(2), 1007 scsi(3), 1008 tcpIp(4), 1009 vi(5), 1010 ficon(6) 1011 } 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "A bit mask specifying the higher level protocols which are 1016 capable of being running over this port. Note that for 1017 generic Fx_Ports, E_Ports and B_Ports, this object will 1018 indicate all protocols." 1019 ::= { fcmPortEntry 13 } 1021 fcmPortOperProtocols OBJECT-TYPE 1022 SYNTAX BITS { 1023 unknown(0), 1024 loop(1), 1025 fabric(2), 1026 scsi(3), 1027 tcpIp(4), 1028 vi(5), 1029 ficon(6) 1030 } 1031 MAX-ACCESS read-only 1032 STATUS current 1033 DESCRIPTION 1034 "A bit mask specifying the higher level protocols which are 1035 currently operational on this port. For Fx_Ports, E_Ports 1036 and B_Ports, this object will typically have the value 1037 'unknown'." 1038 ::= { fcmPortEntry 14 } 1040 --******************************** 1041 -- Port Statistics 1042 -- 1044 fcmPortStatsTable OBJECT-TYPE 1045 SYNTAX SEQUENCE OF FcmPortStatsEntry 1046 MAX-ACCESS not-accessible 1047 STATUS current 1048 DESCRIPTION 1049 "A list of statistics for Fibre Channel ports." 1050 ::= { fcmgmtObjects 4 } 1052 fcmPortStatsEntry OBJECT-TYPE 1053 SYNTAX FcmPortStatsEntry 1054 MAX-ACCESS not-accessible 1055 STATUS current 1056 DESCRIPTION 1057 "An entry containing statistics for a Fibre Channel port. 1058 If any counter in this table suffers a discontinuity, the 1059 value of ifCounterDiscontinuityTime (defined in the IF-MIB) 1060 must be updated." 1061 REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000." 1062 AUGMENTS { fcmPortEntry } 1063 ::= { fcmPortStatsTable 1 } 1065 FcmPortStatsEntry ::= 1066 SEQUENCE { 1067 fcmPortBBCreditZeros Counter64, 1068 fcmPortFullInputBuffers Counter64, 1069 fcmPortClass2RxFrames Counter64, 1070 fcmPortClass2RxOctets Counter64, 1071 fcmPortClass2TxFrames Counter64, 1072 fcmPortClass2TxOctets Counter64, 1073 fcmPortClass2Discards Counter64, 1074 fcmPortClass2RxFbsyFrames Counter64, 1075 fcmPortClass2RxPbsyFrames Counter64, 1076 fcmPortClass2RxFrjtFrames Counter64, 1077 fcmPortClass2RxPrjtFrames Counter64, 1078 fcmPortClass2TxFbsyFrames Counter64, 1079 fcmPortClass2TxPbsyFrames Counter64, 1080 fcmPortClass2TxFrjtFrames Counter64, 1081 fcmPortClass2TxPrjtFrames Counter64, 1082 fcmPortClass3RxFrames Counter64, 1083 fcmPortClass3RxOctets Counter64, 1084 fcmPortClass3TxFrames Counter64, 1085 fcmPortClass3TxOctets Counter64, 1086 fcmPortClass3Discards Counter64, 1087 fcmPortClassFRxFrames Counter32, 1088 fcmPortClassFRxOctets Counter32, 1089 fcmPortClassFTxFrames Counter32, 1090 fcmPortClassFTxOctets Counter32, 1091 fcmPortClassFDiscards Counter32 1092 } 1094 fcmPortBBCreditZeros OBJECT-TYPE 1095 SYNTAX Counter64 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "The number of transitions in/out of the buffer-to-buffer 1100 credit zero state. The other side is not providing any 1101 credit." 1102 ::= { fcmPortStatsEntry 1 } 1104 fcmPortFullInputBuffers OBJECT-TYPE 1105 SYNTAX Counter64 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The number of occurrences when all input buffers of a port 1110 were full and outbound buffer-to-buffer credit transitioned 1111 to zero, i.e., there became no credit to provide to other 1112 side." 1113 ::= { fcmPortStatsEntry 2 } 1115 fcmPortClass2RxFrames OBJECT-TYPE 1116 SYNTAX Counter64 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "The number of Class 2 frames received at this port." 1121 ::= { fcmPortStatsEntry 3 } 1123 fcmPortClass2RxOctets OBJECT-TYPE 1124 SYNTAX Counter64 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The number of octets contained in Class 2 frames received 1129 at this port." 1130 ::= { fcmPortStatsEntry 4 } 1132 fcmPortClass2TxFrames OBJECT-TYPE 1133 SYNTAX Counter64 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "The number of Class 2 frames transmitted out of this port." 1138 ::= { fcmPortStatsEntry 5 } 1140 fcmPortClass2TxOctets OBJECT-TYPE 1141 SYNTAX Counter64 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "The number of octets contained in Class 2 frames 1146 transmitted out of this port." 1147 ::= { fcmPortStatsEntry 6 } 1149 fcmPortClass2Discards OBJECT-TYPE 1150 SYNTAX Counter64 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The number of Class 2 frames that were discarded upon 1155 reception at this port." 1156 ::= { fcmPortStatsEntry 7 } 1158 fcmPortClass2RxFbsyFrames OBJECT-TYPE 1159 SYNTAX Counter64 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The number of times that F_BSY was returned to this port as 1164 a result of a Class 2 frame that could not be delivered to 1165 the other end of the link. This can occur when either the 1166 fabric or the destination port is temporarily busy. Note 1167 that this counter will never increment for an F_Port." 1168 ::= { fcmPortStatsEntry 8 } 1170 fcmPortClass2RxPbsyFrames OBJECT-TYPE 1171 SYNTAX Counter64 1172 MAX-ACCESS read-only 1173 STATUS current 1174 DESCRIPTION 1175 "The number of times that P_BSY was returned to this port as 1176 a result of a Class 2 frame that could not be delivered to 1177 the other end of the link. This can occur when the 1178 destination port is temporarily busy." 1179 ::= { fcmPortStatsEntry 9 } 1181 fcmPortClass2RxFrjtFrames OBJECT-TYPE 1182 SYNTAX Counter64 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "The number of times that F_RJT was returned to this port as 1187 a result of a Class 2 frame that was rejected by the fabric. 1188 Note that this counter will never increment for an F_Port." 1189 ::= { fcmPortStatsEntry 10 } 1191 fcmPortClass2RxPrjtFrames OBJECT-TYPE 1192 SYNTAX Counter64 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The number of times that P_RJT was returned to this port as 1197 a result of a Class 2 frame that was rejected at the 1198 destination N_Port." 1199 ::= { fcmPortStatsEntry 11 } 1201 fcmPortClass2TxFbsyFrames OBJECT-TYPE 1202 SYNTAX Counter64 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "The number of times that F_BSY was generated by this port 1207 as a result of a Class 2 frame that could not be delivered 1208 because either the Fabric or the destination port was 1209 temporarily busy. Note that this counter will never 1210 increment for an N_Port." 1211 ::= { fcmPortStatsEntry 12 } 1213 fcmPortClass2TxPbsyFrames OBJECT-TYPE 1214 SYNTAX Counter64 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The number of times that P_BSY was generated by this port 1219 as a result of a Class 2 frame that could not be delivered 1220 because the destination port was temporarily busy. Note 1221 that this counter will never increment for an F_Port." 1222 ::= { fcmPortStatsEntry 13 } 1224 fcmPortClass2TxFrjtFrames OBJECT-TYPE 1225 SYNTAX Counter64 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The number of times that F_RJT was generated by this port 1230 as a result of a Class 2 frame being rejected by the fabric. 1231 Note that this counter will never increment for an N_Port." 1232 ::= { fcmPortStatsEntry 14 } 1234 fcmPortClass2TxPrjtFrames OBJECT-TYPE 1235 SYNTAX Counter64 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "The number of times that P_RJT was generated by this port 1240 as a result of a Class 2 frame being rejected at the 1241 destination N_Port. Note that this counter will never 1242 increment for an F_Port." 1243 ::= { fcmPortStatsEntry 15 } 1245 fcmPortClass3RxFrames OBJECT-TYPE 1246 SYNTAX Counter64 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "The number of Class 3 frames received at this port." 1251 ::= { fcmPortStatsEntry 16 } 1253 fcmPortClass3RxOctets OBJECT-TYPE 1254 SYNTAX Counter64 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The number of octets contained in Class 3 frames received 1259 at this port." 1260 ::= { fcmPortStatsEntry 17 } 1262 fcmPortClass3TxFrames OBJECT-TYPE 1263 SYNTAX Counter64 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The number of Class 3 frames transmitted out of this port." 1268 ::= { fcmPortStatsEntry 18 } 1270 fcmPortClass3TxOctets OBJECT-TYPE 1271 SYNTAX Counter64 1272 MAX-ACCESS read-only 1273 STATUS current 1274 DESCRIPTION 1275 "The number of octets contained in Class 3 frames 1276 transmitted out of this port." 1277 ::= { fcmPortStatsEntry 19 } 1279 fcmPortClass3Discards OBJECT-TYPE 1280 SYNTAX Counter64 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "The number of Class 3 frames that were discarded upon 1285 reception at this port." 1286 ::= { fcmPortStatsEntry 20 } 1288 fcmPortClassFRxFrames OBJECT-TYPE 1289 SYNTAX Counter32 1290 MAX-ACCESS read-only 1291 STATUS current 1292 DESCRIPTION 1293 "The number of Class F frames received at this port." 1294 ::= { fcmPortStatsEntry 21 } 1296 fcmPortClassFRxOctets OBJECT-TYPE 1297 SYNTAX Counter32 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "The number of octets contained in Class F frames received 1302 at this port." 1303 ::= { fcmPortStatsEntry 22 } 1305 fcmPortClassFTxFrames OBJECT-TYPE 1306 SYNTAX Counter32 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "The number of Class F frames transmitted out of this port." 1311 ::= { fcmPortStatsEntry 23 } 1313 fcmPortClassFTxOctets OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The number of octets contained in Class F frames 1319 transmitted out of this port." 1320 ::= { fcmPortStatsEntry 24 } 1322 fcmPortClassFDiscards OBJECT-TYPE 1323 SYNTAX Counter32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "The number of Class F frames that were discarded upon 1328 reception at this port." 1329 ::= { fcmPortStatsEntry 25 } 1331 --******************************** 1332 -- Port Low-capacity Statistics 1333 -- 1334 -- these are Counter32 "low-capacity" counters for systems 1335 -- which do not support Counter64's 1337 fcmPortLcStatsTable OBJECT-TYPE 1338 SYNTAX SEQUENCE OF FcmPortLcStatsEntry 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "A list of Counter32-based statistics for systems which do 1343 not support Counter64." 1344 ::= { fcmgmtObjects 5 } 1346 fcmPortLcStatsEntry OBJECT-TYPE 1347 SYNTAX FcmPortLcStatsEntry 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "An entry containing low-capacity (i.e., based on Counter32) 1352 statistics for a Fibre Channel port. If any counter in this 1353 table suffers a discontinuity, the value of 1354 ifCounterDiscontinuityTime (defined in the IF-MIB) must be 1355 updated." 1356 REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000." 1357 AUGMENTS { fcmPortEntry } 1358 ::= { fcmPortLcStatsTable 1 } 1360 FcmPortLcStatsEntry ::= 1361 SEQUENCE { 1362 fcmPortLcBBCreditZeros Counter32, 1363 fcmPortLcFullInputBuffers Counter32, 1364 fcmPortLcClass2RxFrames Counter32, 1365 fcmPortLcClass2RxOctets Counter32, 1366 fcmPortLcClass2TxFrames Counter32, 1367 fcmPortLcClass2TxOctets Counter32, 1368 fcmPortLcClass2Discards Counter32, 1369 fcmPortLcClass2RxFbsyFrames Counter32, 1370 fcmPortLcClass2RxPbsyFrames Counter32, 1371 fcmPortLcClass2RxFrjtFrames Counter32, 1372 fcmPortLcClass2RxPrjtFrames Counter32, 1373 fcmPortLcClass2TxFbsyFrames Counter32, 1374 fcmPortLcClass2TxPbsyFrames Counter32, 1375 fcmPortLcClass2TxFrjtFrames Counter32, 1376 fcmPortLcClass2TxPrjtFrames Counter32, 1377 fcmPortLcClass3RxFrames Counter32, 1378 fcmPortLcClass3RxOctets Counter32, 1379 fcmPortLcClass3TxFrames Counter32, 1380 fcmPortLcClass3TxOctets Counter32, 1381 fcmPortLcClass3Discards Counter32 1382 } 1384 fcmPortLcBBCreditZeros OBJECT-TYPE 1385 SYNTAX Counter32 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "The number of transitions in/out of the buffer-to-buffer 1390 credit zero state. The other side is not providing any 1391 credit." 1392 ::= { fcmPortLcStatsEntry 1 } 1394 fcmPortLcFullInputBuffers OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "The number of occurrences when all input buffers of a port 1400 were full and outbound buffer-to-buffer credit transitioned 1401 to zero, i.e., there became no credit to provide to other 1402 side." 1403 ::= { fcmPortLcStatsEntry 2 } 1405 fcmPortLcClass2RxFrames OBJECT-TYPE 1406 SYNTAX Counter32 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "The number of Class 2 frames received at this port." 1411 ::= { fcmPortLcStatsEntry 3 } 1413 fcmPortLcClass2RxOctets OBJECT-TYPE 1414 SYNTAX Counter32 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "The number of octets contained in Class 2 frames received 1419 at this port." 1420 ::= { fcmPortLcStatsEntry 4 } 1422 fcmPortLcClass2TxFrames OBJECT-TYPE 1423 SYNTAX Counter32 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The number of Class 2 frames transmitted out of this port." 1428 ::= { fcmPortLcStatsEntry 5 } 1430 fcmPortLcClass2TxOctets OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The number of octets contained in Class 2 frames 1436 transmitted out of this port." 1437 ::= { fcmPortLcStatsEntry 6 } 1439 fcmPortLcClass2Discards OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "The number of Class 2 frames that were discarded upon 1445 reception at this port." 1446 ::= { fcmPortLcStatsEntry 7 } 1448 fcmPortLcClass2RxFbsyFrames OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The number of times that F_BSY was returned to this port as 1454 a result of a Class 2 frame that could not be delivered to 1455 the other end of the link. This can occur when either the 1456 fabric or the destination port is temporarily busy. Note 1457 that this counter will never increment for an F_Port." 1458 ::= { fcmPortLcStatsEntry 8 } 1460 fcmPortLcClass2RxPbsyFrames OBJECT-TYPE 1461 SYNTAX Counter32 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The number of times that P_BSY was returned to this port as 1466 a result of a Class 2 frame that could not be delivered to 1467 the other end of the link. This can occur when the 1468 destination port is temporarily busy." 1469 ::= { fcmPortLcStatsEntry 9 } 1471 fcmPortLcClass2RxFrjtFrames OBJECT-TYPE 1472 SYNTAX Counter32 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "The number of times that F_RJT was returned to this port as 1477 a result of a Class 2 frame that was rejected by the fabric. 1478 Note that this counter will never increment for an F_Port." 1479 ::= { fcmPortLcStatsEntry 10 } 1481 fcmPortLcClass2RxPrjtFrames OBJECT-TYPE 1482 SYNTAX Counter32 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "The number of times that P_RJT was returned to this port as 1487 a result of a Class 2 frame that was rejected at the 1488 destination N_Port." 1489 ::= { fcmPortLcStatsEntry 11 } 1491 fcmPortLcClass2TxFbsyFrames OBJECT-TYPE 1492 SYNTAX Counter32 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "The number of times that F_BSY was generated by this port 1497 as a result of a Class 2 frame that could not be delivered 1498 because either the Fabric or the destination port was 1499 temporarily busy. Note that this counter will never 1500 increment for an N_Port." 1501 ::= { fcmPortLcStatsEntry 12 } 1503 fcmPortLcClass2TxPbsyFrames OBJECT-TYPE 1504 SYNTAX Counter32 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "The number of times that P_BSY was generated by this port 1509 as a result of a Class 2 frame that could not be delivered 1510 because the destination port was temporarily busy. Note 1511 that this counter will never increment for an F_Port." 1512 ::= { fcmPortLcStatsEntry 13 } 1514 fcmPortLcClass2TxFrjtFrames OBJECT-TYPE 1515 SYNTAX Counter32 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The number of times that F_RJT was generated by this port 1520 as a result of a Class 2 frame being rejected by the fabric. 1521 Note that this counter will never increment for an N_Port." 1522 ::= { fcmPortLcStatsEntry 14 } 1524 fcmPortLcClass2TxPrjtFrames OBJECT-TYPE 1525 SYNTAX Counter32 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The number of times that P_RJT was generated by this port 1530 as a result of a Class 2 frame being rejected at the 1531 destination N_Port. Note that this counter will never 1532 increment for an F_Port." 1533 ::= { fcmPortLcStatsEntry 15 } 1535 fcmPortLcClass3RxFrames OBJECT-TYPE 1536 SYNTAX Counter32 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "The number of Class 3 frames received at this port." 1541 ::= { fcmPortLcStatsEntry 16 } 1543 fcmPortLcClass3RxOctets OBJECT-TYPE 1544 SYNTAX Counter32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The number of octets contained in Class 3 frames received 1549 at this port." 1550 ::= { fcmPortLcStatsEntry 17 } 1552 fcmPortLcClass3TxFrames OBJECT-TYPE 1553 SYNTAX Counter32 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "The number of Class 3 frames transmitted out of this port." 1558 ::= { fcmPortLcStatsEntry 18 } 1560 fcmPortLcClass3TxOctets OBJECT-TYPE 1561 SYNTAX Counter32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "The number of octets contained in Class 3 frames 1566 transmitted out of this port." 1567 ::= { fcmPortLcStatsEntry 19 } 1569 fcmPortLcClass3Discards OBJECT-TYPE 1570 SYNTAX Counter32 1571 MAX-ACCESS read-only 1572 STATUS current 1573 DESCRIPTION 1574 "The number of Class 3 frames that were discarded upon 1575 reception at this port." 1576 ::= { fcmPortLcStatsEntry 20 } 1578 --******************************** 1579 -- Port Error Counters 1580 -- 1582 fcmPortErrorsTable OBJECT-TYPE 1583 SYNTAX SEQUENCE OF FcmPortErrorsEntry 1584 MAX-ACCESS not-accessible 1585 STATUS current 1586 DESCRIPTION 1587 "Error counters for Fibre Channel ports." 1588 ::= { fcmgmtObjects 6 } 1590 fcmPortErrorsEntry OBJECT-TYPE 1591 SYNTAX FcmPortErrorsEntry 1592 MAX-ACCESS not-accessible 1593 STATUS current 1594 DESCRIPTION 1595 "Error counters for a Fibre Channel port. If any counter in 1596 this table suffers a discontinuity, the value of 1597 ifCounterDiscontinuityTime (defined in the IF-MIB) must be 1598 updated." 1599 REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000." 1600 AUGMENTS { fcmPortEntry } 1601 ::= { fcmPortErrorsTable 1 } 1603 FcmPortErrorsEntry ::= 1604 SEQUENCE { 1605 fcmPortRxLinkResets Counter32, 1606 fcmPortTxLinkResets Counter32, 1607 fcmPortLinkResets Counter32, 1608 fcmPortRxOfflineSequences Counter32, 1609 fcmPortTxOfflineSequences Counter32, 1610 fcmPortLinkFailures Counter32, 1611 fcmPortLossofSynchs Counter32, 1612 fcmPortLossofSignals Counter32, 1613 fcmPortPrimSeqProtocolErrors Counter32, 1614 fcmPortInvalidTxWords Counter32, 1615 fcmPortInvalidCRCs Counter32, 1616 fcmPortInvalidOrderedSets Counter32, 1617 fcmPortFrameTooLongs Counter32, 1618 fcmPortTruncatedFrames Counter32, 1619 fcmPortAddressErrors Counter32, 1620 fcmPortDelimiterErrors Counter32, 1621 fcmPortEncodingDisparityErrors Counter32, 1622 fcmPortOtherErrors Counter32 1623 } 1625 fcmPortRxLinkResets OBJECT-TYPE 1626 SYNTAX Counter32 1627 MAX-ACCESS read-only 1628 STATUS current 1629 DESCRIPTION 1630 "The number of Link Reset (LR) Primitive Sequences 1631 received." 1632 ::= { fcmPortErrorsEntry 1 } 1634 fcmPortTxLinkResets OBJECT-TYPE 1635 SYNTAX Counter32 1636 MAX-ACCESS read-only 1637 STATUS current 1638 DESCRIPTION 1639 "The number of Link Reset (LR) Primitive Sequences 1640 transmitted." 1641 ::= { fcmPortErrorsEntry 2 } 1643 fcmPortLinkResets OBJECT-TYPE 1644 SYNTAX Counter32 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "The number of times the reset link protocol was initiated 1649 on this port. This includes the number of Loop 1650 Initialization Primitive (LIP) events on an arbitrated loop 1651 port." 1652 ::= { fcmPortErrorsEntry 3 } 1654 fcmPortRxOfflineSequences OBJECT-TYPE 1655 SYNTAX Counter32 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The number of Offline (OLS) Primitive Sequences received at 1660 this port." 1661 ::= { fcmPortErrorsEntry 4 } 1663 fcmPortTxOfflineSequences OBJECT-TYPE 1664 SYNTAX Counter32 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "The number of Offline (OLS) Primitive Sequences transmitted 1669 by this port." 1670 ::= { fcmPortErrorsEntry 5 } 1672 fcmPortLinkFailures OBJECT-TYPE 1673 SYNTAX Counter32 1674 MAX-ACCESS read-only 1675 STATUS current 1676 DESCRIPTION 1677 "The number of link failures. This count is part of FC-PH's 1678 Link Error Status Block (LESB)." 1679 REFERENCE 1680 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1681 ::= { fcmPortErrorsEntry 6 } 1683 fcmPortLossofSynchs OBJECT-TYPE 1684 SYNTAX Counter32 1685 MAX-ACCESS read-only 1686 STATUS current 1687 DESCRIPTION 1688 "The number of instances of synchronization loss detected at 1689 this port. This count is part of FC-PH's Link Error Status 1690 Block (LESB)." 1691 REFERENCE 1692 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1693 ::= { fcmPortErrorsEntry 7 } 1695 fcmPortLossofSignals OBJECT-TYPE 1696 SYNTAX Counter32 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "The number of instances of signal loss detected at this 1701 port. This count is part of FC-PH's Link Error Status Block 1702 (LESB)." 1703 REFERENCE 1704 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1705 ::= { fcmPortErrorsEntry 8 } 1707 fcmPortPrimSeqProtocolErrors OBJECT-TYPE 1708 SYNTAX Counter32 1709 MAX-ACCESS read-only 1710 STATUS current 1711 DESCRIPTION 1712 "The number of primitive sequence protocol errors detected 1713 at this port. This count is part of FC-PH's Link Error 1714 Status Block (LESB)." 1715 REFERENCE 1716 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1717 ::= { fcmPortErrorsEntry 9 } 1719 fcmPortInvalidTxWords OBJECT-TYPE 1720 SYNTAX Counter32 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "The number of invalid transmission words received at this 1725 port. This count is part of FC-PH's Link Error Status Block 1726 (LESB)." 1727 REFERENCE 1728 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1729 ::= { fcmPortErrorsEntry 10 } 1731 fcmPortInvalidCRCs OBJECT-TYPE 1732 SYNTAX Counter32 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "The number of frames received with invalid CRC. This count 1737 is part of FC-PH's Link Error Status Block (LESB)." 1738 REFERENCE 1739 "FC-PH, rev 4.3, 1 June 1994, section 29.8." 1741 ::= { fcmPortErrorsEntry 11 } 1743 fcmPortInvalidOrderedSets OBJECT-TYPE 1744 SYNTAX Counter32 1745 MAX-ACCESS read-only 1746 STATUS current 1747 DESCRIPTION 1748 "The number of invalid ordered sets received at this port." 1749 ::= { fcmPortErrorsEntry 12 } 1751 fcmPortFrameTooLongs OBJECT-TYPE 1752 SYNTAX Counter32 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "The number of frames received at this port where the frame 1757 length was greater than what was agreed to in FLOGI/PLOGI. 1758 This could be caused by losing the end of frame delimiter." 1759 ::= { fcmPortErrorsEntry 13 } 1761 fcmPortTruncatedFrames OBJECT-TYPE 1762 SYNTAX Counter32 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "The number of frames received at this port where the frame 1767 length was less than the minimum indicated by the frame 1768 header - normally 24 bytes, but it could be more if the 1769 DFCTL field indicates an optional header should have been 1770 present." 1771 ::= { fcmPortErrorsEntry 14 } 1773 fcmPortAddressErrors OBJECT-TYPE 1774 SYNTAX Counter32 1775 MAX-ACCESS read-only 1776 STATUS current 1777 DESCRIPTION 1778 "The number of frames received with unknown addressing; for 1779 example, an unknown SID or DID." 1780 ::= { fcmPortErrorsEntry 15 } 1782 fcmPortDelimiterErrors OBJECT-TYPE 1783 SYNTAX Counter32 1784 MAX-ACCESS read-only 1785 STATUS current 1786 DESCRIPTION 1787 "The number of invalid frame delimiters received at this 1788 port. An example is a frame with a class 2 start and a class 1789 3 at the end." 1790 ::= { fcmPortErrorsEntry 16 } 1792 fcmPortEncodingDisparityErrors OBJECT-TYPE 1793 SYNTAX Counter32 1794 MAX-ACCESS read-only 1795 STATUS current 1796 DESCRIPTION 1797 "The number of encoding disparity errors received at this 1798 port." 1799 ::= { fcmPortErrorsEntry 17 } 1801 fcmPortOtherErrors OBJECT-TYPE 1802 SYNTAX Counter32 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "The number of errors which were detected on this port but 1807 which were not counted by any other error counter in this 1808 row." 1809 ::= { fcmPortErrorsEntry 18 } 1811 --******************************** 1812 -- The Fibre Channel Fx_Port Table 1813 -- 1815 fcmFxPortTable OBJECT-TYPE 1816 SYNTAX SEQUENCE OF FcmFxPortEntry 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "Additional information about Fibre Channel ports which is 1821 specific to Fx_Ports. This table will contain one entry for 1822 each fcmPortTable entry which represents an Fx_Port." 1823 ::= { fcmgmtObjects 7 } 1825 fcmFxPortEntry OBJECT-TYPE 1826 SYNTAX FcmFxPortEntry 1827 MAX-ACCESS not-accessible 1828 STATUS current 1829 DESCRIPTION 1830 "Each entry contains information about a specific Fx_Port." 1831 INDEX { ifIndex } 1832 ::= { fcmFxPortTable 1 } 1834 FcmFxPortEntry ::= 1835 SEQUENCE { 1836 fcmFxPortRatov Unsigned32, 1837 fcmFxPortEdtov Unsigned32, 1838 fcmFxPortRttov Unsigned32, 1839 fcmFxPortHoldTime Unsigned32, 1840 fcmFxPortCapBbCreditMax FcBbCredit, 1841 fcmFxPortCapBbCreditMin FcBbCredit, 1842 fcmFxPortCapDataFieldSizeMax FcDataFieldSize, 1843 fcmFxPortCapDataFieldSizeMin FcDataFieldSize, 1844 fcmFxPortCapClass2SeqDeliv TruthValue, 1845 fcmFxPortCapClass3SeqDeliv TruthValue, 1846 fcmFxPortCapHoldTimeMax Unsigned32, 1847 fcmFxPortCapHoldTimeMin Unsigned32 1848 } 1850 fcmFxPortRatov OBJECT-TYPE 1851 SYNTAX Unsigned32 1852 UNITS "milliseconds" 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "The Resource_Allocation_Timeout Value configured for this 1857 Fx_Port. This is used as the timeout value for determining 1858 when to reuse an Nx_Port resource such as a 1859 Recovery_Qualifier. It represents the Error_Detect_Timeout 1860 value (see fcmFxPortEdtov) plus twice the maximum time that 1861 a frame may be delayed within the Fabric and still be 1862 delivered." 1863 ::= { fcmFxPortEntry 1 } 1865 fcmFxPortEdtov OBJECT-TYPE 1866 SYNTAX Unsigned32 1867 UNITS "milliseconds" 1868 MAX-ACCESS read-only 1869 STATUS current 1870 DESCRIPTION 1871 "The Error_Detect_Timeout value configured for this Fx_Port. 1872 This is used as the timeout value for detecting an error 1873 condition." 1874 ::= { fcmFxPortEntry 2 } 1876 fcmFxPortRttov OBJECT-TYPE 1877 SYNTAX Unsigned32 1878 UNITS "milliseconds" 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "The Receiver_Transmitter_Timeout value of this Fx_Port. 1883 This is used by the receiver logic to detect Loss of 1884 Synchronization." 1885 ::= { fcmFxPortEntry 3 } 1887 fcmFxPortHoldTime OBJECT-TYPE 1888 SYNTAX Unsigned32 1889 UNITS "microseconds" 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "The maximum time that this Fx_Port shall hold a frame 1894 before discarding the frame if it is unable to deliver the 1895 frame. The value 0 means that this Fx_Port does not support 1896 this parameter." 1897 ::= { fcmFxPortEntry 4 } 1899 fcmFxPortCapBbCreditMax OBJECT-TYPE 1900 SYNTAX FcBbCredit 1901 UNITS "buffers" 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "The maximum number of receive buffers which this port is 1906 capable of making available for holding frames from attached 1907 Nx_Port(s)." 1908 ::= { fcmFxPortEntry 5 } 1910 fcmFxPortCapBbCreditMin OBJECT-TYPE 1911 SYNTAX FcBbCredit 1912 UNITS "buffers" 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "The minimum number of receive buffers which this port is 1917 capable of making available for holding frames from attached 1918 Nx_Port(s)." 1919 ::= { fcmFxPortEntry 6 } 1921 fcmFxPortCapDataFieldSizeMax OBJECT-TYPE 1922 SYNTAX FcDataFieldSize 1923 UNITS "bytes" 1924 MAX-ACCESS read-only 1925 STATUS current 1926 DESCRIPTION 1927 "The maximum size in bytes of the Data Field in a frame that 1928 this Fx_Port is capable of receiving from an attached 1929 Nx_Port." 1930 ::= { fcmFxPortEntry 7 } 1932 fcmFxPortCapDataFieldSizeMin OBJECT-TYPE 1933 SYNTAX FcDataFieldSize 1934 UNITS "bytes" 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "The minimum size in bytes of the Data Field in a frame that 1939 this Fx_Port is capable of receiving from an attached 1940 Nx_Port." 1941 ::= { fcmFxPortEntry 8 } 1943 fcmFxPortCapClass2SeqDeliv OBJECT-TYPE 1944 SYNTAX TruthValue 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "An indication of whether this Fx_Port is capable of 1949 supporting Class 2 Sequential Delivery." 1950 ::= { fcmFxPortEntry 9 } 1952 fcmFxPortCapClass3SeqDeliv OBJECT-TYPE 1953 SYNTAX TruthValue 1954 MAX-ACCESS read-only 1955 STATUS current 1956 DESCRIPTION 1957 "An indication of whether this Fx_Port is capable of 1958 supporting Class 3 Sequential Delivery." 1959 ::= { fcmFxPortEntry 10 } 1961 fcmFxPortCapHoldTimeMax OBJECT-TYPE 1962 SYNTAX Unsigned32 1963 UNITS "microseconds" 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The maximum holding time that this Fx_Port is capable of 1968 supporting." 1969 ::= { fcmFxPortEntry 11 } 1971 fcmFxPortCapHoldTimeMin OBJECT-TYPE 1972 SYNTAX Unsigned32 1973 UNITS "microseconds" 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "The minimum holding time that this Fx_Port is capable of 1978 supporting." 1979 ::= { fcmFxPortEntry 12 } 1981 --******************************** 1982 -- The Fibre Channel Inter-Switch Port Table 1983 -- 1985 fcmISPortTable OBJECT-TYPE 1986 SYNTAX SEQUENCE OF FcmISPortEntry 1987 MAX-ACCESS not-accessible 1988 STATUS current 1989 DESCRIPTION 1990 "Additional information about E_Ports, B_Ports, and any 1991 other type of Fibre Channel port to which inter-switch links 1992 can be connected. This table will contain one entry for 1993 each fcmPortTable entry which represents such a port." 1994 ::= { fcmgmtObjects 8 } 1996 fcmISPortEntry OBJECT-TYPE 1997 SYNTAX FcmISPortEntry 1998 MAX-ACCESS not-accessible 1999 STATUS current 2000 DESCRIPTION 2001 "Each entry contains information about a specific port 2002 connected to an inter-switch link." 2003 INDEX { ifIndex } 2004 ::= { fcmISPortTable 1 } 2006 FcmISPortEntry ::= 2007 SEQUENCE { 2008 fcmISPortClassFCredit FcBbCredit, 2009 fcmISPortClassFDataFieldSize FcDataFieldSize 2010 } 2012 fcmISPortClassFCredit OBJECT-TYPE 2013 SYNTAX FcBbCredit 2014 MAX-ACCESS read-write 2015 STATUS current 2016 DESCRIPTION 2017 "The maximum number of Class F data frames which can be 2018 transmitted by the inter-switch port without receipt of ACK 2019 or Link_Response frames." 2020 ::= { fcmISPortEntry 1 } 2022 fcmISPortClassFDataFieldSize OBJECT-TYPE 2023 SYNTAX FcDataFieldSize 2024 UNITS "bytes" 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "The Receive Data Field Size which the inter-switch port has 2029 agreed to support for Class F frames to/from this port. The 2030 size specifies the largest Data Field Size for an FT_1 2031 frame." 2032 ::= { fcmISPortEntry 2 } 2034 --******************************** 2035 -- The Fabric Login table 2036 -- 2037 -- This table contains the information held by FC switches 2038 -- about the Nx_Ports which are logged-in/attached to their 2039 -- Fx_Ports 2041 fcmFLoginTable OBJECT-TYPE 2042 SYNTAX SEQUENCE OF FcmFLoginEntry 2043 MAX-ACCESS not-accessible 2044 STATUS current 2045 DESCRIPTION 2046 "A table that contains one entry for each Nx_Port logged- 2047 in/attached to a particular Fx_Port in the switch. Each 2048 entry contains the services parameters established during 2049 the most recent Fabric Login, explicit or implicit. Note 2050 that an Fx_Port may have one or more Nx_Ports attached to 2051 it." 2052 ::= { fcmgmtObjects 9 } 2054 fcmFLoginEntry OBJECT-TYPE 2055 SYNTAX FcmFLoginEntry 2056 MAX-ACCESS not-accessible 2057 STATUS current 2058 DESCRIPTION 2059 "An entry containing service parameters established from a 2060 successful Fabric Login." 2061 INDEX { ifIndex, fcmFLoginNxPortIndex } 2062 ::= { fcmFLoginTable 1 } 2064 FcmFLoginEntry ::= 2065 SEQUENCE { 2066 fcmFLoginNxPortIndex Unsigned32, 2067 fcmFLoginPortWwn FcNameIdOrZero, 2068 fcmFLoginNodeWwn FcNameIdOrZero, 2069 fcmFLoginBbCreditModel FcBbCreditModel, 2070 fcmFLoginBbCredit FcBbCredit, 2071 fcmFLoginClassesAgreed FcClasses, 2072 fcmFLoginClass2SeqDelivAgreed TruthValue, 2073 fcmFLoginClass2DataFieldSize FcDataFieldSize, 2074 fcmFLoginClass3SeqDelivAgreed TruthValue, 2075 fcmFLoginClass3DataFieldSize FcDataFieldSize 2076 } 2078 fcmFLoginNxPortIndex OBJECT-TYPE 2079 SYNTAX Unsigned32 (1..4294967295) 2080 MAX-ACCESS not-accessible 2081 STATUS current 2082 DESCRIPTION 2083 "An arbitrary integer which uniquely identifies an Nx_Port 2084 amongst all those attached to the Fx_Port indicated by 2085 ifIndex. 2087 After a value of this object is assigned to a particular 2088 Nx_Port, that value can be re-used when and only when it is 2089 assigned to the same Nx_Port, or, after a reset of the value 2090 of the relevant instance of ifCounterDiscontinuityTime." 2091 REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000." 2092 ::= { fcmFLoginEntry 1 } 2094 fcmFLoginPortWwn OBJECT-TYPE 2095 SYNTAX FcNameIdOrZero 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "The port name of the attached Nx_Port, or the zero-length 2100 string if unknown." 2101 ::= { fcmFLoginEntry 2 } 2103 fcmFLoginNodeWwn OBJECT-TYPE 2104 SYNTAX FcNameIdOrZero 2105 MAX-ACCESS read-only 2106 STATUS current 2107 DESCRIPTION 2108 "The node name of the attached Nx_Port, or the zero-length 2109 string if unknown." 2110 ::= { fcmFLoginEntry 3 } 2112 fcmFLoginBbCreditModel OBJECT-TYPE 2113 SYNTAX FcBbCreditModel 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "The buffer-to-buffer credit model in use by the Fx_Port." 2118 ::= { fcmFLoginEntry 4 } 2120 fcmFLoginBbCredit OBJECT-TYPE 2121 SYNTAX FcBbCredit 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "The number of buffers available for holding frames to be 2126 transmitted to the attached Nx_Port. These buffers are for 2127 buffer-to-buffer flow control in the direction from Fx_Port 2128 to Nx_Port." 2129 ::= { fcmFLoginEntry 5 } 2131 fcmFLoginClassesAgreed OBJECT-TYPE 2132 SYNTAX FcClasses 2133 MAX-ACCESS read-only 2134 STATUS current 2135 DESCRIPTION 2136 "The Classes of Service which the Fx_Port has agreed to 2137 support for this Nx_Port." 2138 ::= { fcmFLoginEntry 6 } 2140 fcmFLoginClass2SeqDelivAgreed OBJECT-TYPE 2141 SYNTAX TruthValue 2142 MAX-ACCESS read-only 2143 STATUS current 2144 DESCRIPTION 2145 "An indication of whether the Fx_Port has agreed to support 2146 Class 2 sequential delivery for this Nx_Port. This is only 2147 meaningful if Class 2 service has been agreed." 2148 ::= { fcmFLoginEntry 7 } 2150 fcmFLoginClass2DataFieldSize OBJECT-TYPE 2151 SYNTAX FcDataFieldSize 2152 MAX-ACCESS read-only 2153 STATUS current 2154 DESCRIPTION 2155 "The Receive Data Field Size which the Fx_Port has agreed to 2156 support for Class 2 frames to/from this Nx_Port. The size 2157 specifies the largest Data Field Size for an FT_1 frame. 2158 This is only meaningful if Class 2 service has been agreed." 2159 ::= { fcmFLoginEntry 8 } 2161 fcmFLoginClass3SeqDelivAgreed OBJECT-TYPE 2162 SYNTAX TruthValue 2163 MAX-ACCESS read-only 2164 STATUS current 2165 DESCRIPTION 2166 "An indication of whether the Fx_Port has agreed to support 2167 Class 3 sequential delivery for this Nx_Port. This is only 2168 meaningful if Class 3 service has been agreed." 2169 ::= { fcmFLoginEntry 9 } 2171 fcmFLoginClass3DataFieldSize OBJECT-TYPE 2172 SYNTAX FcDataFieldSize 2173 MAX-ACCESS read-only 2174 STATUS current 2175 DESCRIPTION 2176 "The Receive Data Field Size which the Fx_Port has agreed to 2177 support for Class 3 frames to/from this Nx_Port. The size 2178 specifies the largest Data Field Size for an FT_1 frame. 2179 This is only meaningful if Class 3 service has been agreed." 2180 ::= { fcmFLoginEntry 10 } 2182 --******************************** 2183 -- The Link table 2184 -- 2185 -- This table is intended to assist management applications 2186 -- in determining the topology of the network. The table 2187 -- contains any recent information which the agent knows 2188 -- about Fibre Channel links, both those which terminate at 2189 -- a local port, as well as any others for which information 2190 -- is known. 2192 fcmLinkTable OBJECT-TYPE 2193 SYNTAX SEQUENCE OF FcmLinkEntry 2194 MAX-ACCESS not-accessible 2195 STATUS current 2196 DESCRIPTION 2197 "A table containing any Fibre Channel link information which 2198 is known to local Fibre Channel managed instances. One end 2199 of such a link is typically at a local port, but the table 2200 can also contain information on links for which neither end 2201 is a local port. 2203 If one end of a link terminates locally, then that end is 2204 termed 'end1'; the other end is termed 'end2'." 2206 ::= { fcmgmtObjects 10 } 2208 fcmLinkEntry OBJECT-TYPE 2209 SYNTAX FcmLinkEntry 2210 MAX-ACCESS not-accessible 2211 STATUS current 2212 DESCRIPTION 2213 "An entry containing information which a particular Fibre 2214 Channel managed instance has about a Fibre Channel link. 2216 The two ends of the link are called 'end1' and 'end2'." 2217 INDEX { fcmInstanceIndex, fcmLinkIndex } 2218 ::= { fcmLinkTable 1 } 2220 FcmLinkEntry ::= 2221 SEQUENCE { 2222 fcmLinkIndex Unsigned32, 2223 fcmLinkEnd1NodeWwn FcNameIdOrZero, 2224 fcmLinkEnd1PhysPortNumber Unsigned32, 2225 fcmLinkEnd1PortWwn FcNameIdOrZero, 2226 fcmLinkEnd2NodeWwn FcNameIdOrZero, 2227 fcmLinkEnd2PhysPortNumber Unsigned32, 2228 fcmLinkEnd2PortWwn FcNameIdOrZero, 2229 fcmLinkEnd2AgentAddress SnmpAdminString, 2230 fcmLinkEnd2PortType FcPortType, 2231 fcmLinkEnd2UnitType FcUnitFunctions, 2232 fcmLinkEnd2FcAddressId FcAddressIdOrZero 2233 } 2235 fcmLinkIndex OBJECT-TYPE 2236 SYNTAX Unsigned32 (1..4294967295) 2237 MAX-ACCESS not-accessible 2238 STATUS current 2239 DESCRIPTION 2240 "An arbitrary integer which uniquely identifies one link 2241 within the set of links about which a particular managed 2242 instance has information." 2243 ::= { fcmLinkEntry 1 } 2245 fcmLinkEnd1NodeWwn OBJECT-TYPE 2246 SYNTAX FcNameIdOrZero 2247 MAX-ACCESS read-only 2248 STATUS current 2249 DESCRIPTION 2250 "The node name of end1, or the zero-length string if 2251 unknown." 2252 ::= { fcmLinkEntry 2 } 2254 fcmLinkEnd1PhysPortNumber OBJECT-TYPE 2255 SYNTAX Unsigned32 2256 MAX-ACCESS read-only 2257 STATUS current 2258 DESCRIPTION 2259 "The physical port number of end1, or zero if unknown." 2260 REFERENCE 2261 "FC-GS-3, section 6.1.2.2.5" 2262 ::= { fcmLinkEntry 3 } 2264 fcmLinkEnd1PortWwn OBJECT-TYPE 2265 SYNTAX FcNameIdOrZero 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "The port WWN of end1, or the zero-length string if unknown. 2270 ('end1' is local if this value is equal to the value of 2271 fcmPortWwn in one of the rows of the fcmPortTable.)" 2272 ::= { fcmLinkEntry 4 } 2274 fcmLinkEnd2NodeWwn OBJECT-TYPE 2275 SYNTAX FcNameIdOrZero 2276 MAX-ACCESS read-only 2277 STATUS current 2278 DESCRIPTION 2279 "The node name of end2, or the zero-length string if 2280 unknown." 2281 ::= { fcmLinkEntry 5 } 2283 fcmLinkEnd2PhysPortNumber OBJECT-TYPE 2284 SYNTAX Unsigned32 2285 MAX-ACCESS read-only 2286 STATUS current 2287 DESCRIPTION 2288 "The physical port number of end2, or zero if unknown." 2289 REFERENCE 2290 "FC-GS-3, section 6.1.2.2.5" 2291 ::= { fcmLinkEntry 6 } 2293 fcmLinkEnd2PortWwn OBJECT-TYPE 2294 SYNTAX FcNameIdOrZero 2295 MAX-ACCESS read-only 2296 STATUS current 2297 DESCRIPTION 2298 "The port WWN of end2, or the zero-length string if 2299 unknown." 2300 ::= { fcmLinkEntry 7 } 2302 fcmLinkEnd2AgentAddress OBJECT-TYPE 2303 SYNTAX SnmpAdminString 2304 MAX-ACCESS read-only 2305 STATUS current 2306 DESCRIPTION 2307 "The address of the management agent for the Fibre Channel 2308 Interconnect Element or Platform of which end2 is a part. 2309 The GS-4 specification provides some information about 2310 management agents. If the address is unknown, the value of 2311 this object is the zero-length string." 2312 REFERENCE 2313 "FC-GS-3, section 6.1.2.1.7" 2314 ::= { fcmLinkEntry 8 } 2316 fcmLinkEnd2PortType OBJECT-TYPE 2317 SYNTAX FcPortType 2318 MAX-ACCESS read-only 2319 STATUS current 2320 DESCRIPTION 2321 "The port type of end2." 2322 REFERENCE 2323 "FC-GS-3, section 6.1.2.2.2" 2324 ::= { fcmLinkEntry 9 } 2326 fcmLinkEnd2UnitType OBJECT-TYPE 2327 SYNTAX FcUnitFunctions 2328 MAX-ACCESS read-only 2329 STATUS current 2330 DESCRIPTION 2331 "The type of/function(s) performed by the Fibre Channel 2332 Interconnect Element or Platform of which end2 is a part." 2333 REFERENCE 2334 "FC-GS-3, sections 6.1.2.1.2 and 6.1.2.3.2" 2335 ::= { fcmLinkEntry 10 } 2337 fcmLinkEnd2FcAddressId OBJECT-TYPE 2338 SYNTAX FcAddressIdOrZero 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "The Fibre Channel Address ID of end2, or the zero-length 2343 string if unknown." 2344 ::= { fcmLinkEntry 11 } 2346 --******************************** 2347 -- Conformance Section 2348 -- 2350 fcmgmtCompliances OBJECT IDENTIFIER ::= { fcmgmtConformance 1 } 2351 fcmgmtGroups OBJECT IDENTIFIER ::= { fcmgmtConformance 2 } 2353 fcmgmtCompliance MODULE-COMPLIANCE 2354 STATUS current 2355 DESCRIPTION 2356 "Describes the requirements for compliance to this Fibre 2357 Channel Management MIB." 2358 MODULE -- this module 2359 MANDATORY-GROUPS { fcmInstanceBasicGroup, 2360 fcmPortBasicGroup, 2361 fcmPortErrorsGroup } 2363 GROUP fcmPortStatsGroup 2364 DESCRIPTION 2365 "This group is mandatory for all systems which 2366 are able to support the Counter64 date type." 2368 GROUP fcmPortClass23StatsGroup 2369 DESCRIPTION 2370 "This group is mandatory only for systems which 2371 keep class-specific traffic statistics on Class 2 2372 on Class 3 traffic and are able to support the 2373 Counter64 date type." 2375 GROUP fcmPortClassFStatsGroup 2376 DESCRIPTION 2377 "This group is mandatory only for FC switches which 2378 keep statistics on Class F traffic." 2380 GROUP fcmPortLcStatsGroup 2381 DESCRIPTION 2382 "This group is mandatory only for agents which can not 2383 support the Counter64 data type and/or need to provide 2384 information accessible by SNMPv1 applications." 2386 GROUP fcmSwitchBasicGroup 2387 DESCRIPTION 2388 "This group is mandatory only for Fibre Channel 2389 managed instances which manage Fibre Channel 2390 switches." 2392 GROUP fcmSwitchPortGroup 2393 DESCRIPTION 2394 "This group is mandatory only for Fibre Channel 2395 managed instances which manage Fibre Channel 2396 switches." 2398 GROUP fcmSwitchLoginGroup 2399 DESCRIPTION 2400 "This group is mandatory only for Fibre Channel 2401 managed instances which manage Fibre Channel 2402 switches." 2404 GROUP fcmLinkBasicGroup 2405 DESCRIPTION 2406 "This group is optional." 2408 OBJECT fcmInstancePhysicalIndex 2409 SYNTAX Integer32 (0) 2410 DESCRIPTION 2411 "Implementation of a non-zero value is not required." 2413 OBJECT fcmInstanceSoftwareIndex 2414 SYNTAX Integer32 (0) 2415 DESCRIPTION 2416 "Implementation of a non-zero value is not required." 2418 OBJECT fcmInstanceTextName 2419 MIN-ACCESS read-only 2420 DESCRIPTION 2421 "Write access is not required." 2423 OBJECT fcmInstanceDescr 2424 MIN-ACCESS read-only 2425 DESCRIPTION 2426 "Write access is not required." 2428 OBJECT fcmPortAdminType 2429 MIN-ACCESS read-only 2430 DESCRIPTION 2431 "Write access is not required." 2433 OBJECT fcmPortAdminSpeed 2434 MIN-ACCESS read-only 2435 DESCRIPTION 2436 "Write access is not required." 2438 OBJECT fcmSwitchDomainId 2439 MIN-ACCESS read-only 2440 DESCRIPTION 2441 "Write access is not required." 2443 OBJECT fcmISPortClassFCredit 2444 MIN-ACCESS read-only 2445 DESCRIPTION 2446 "Write access is not required." 2448 ::= { fcmgmtCompliances 1 } 2450 --******************************** 2451 -- Object Groups 2452 -- 2454 fcmInstanceBasicGroup OBJECT-GROUP 2455 OBJECTS { fcmInstanceWwn, fcmInstanceFunctions, 2456 fcmInstancePhysicalIndex, fcmInstanceSoftwareIndex, 2457 fcmInstanceStatus, fcmInstanceTextName, 2458 fcmInstanceDescr, fcmInstanceFabricId } 2459 STATUS current 2460 DESCRIPTION 2461 "Basic information about Fibre Channel managed instances." 2462 ::= { fcmgmtGroups 1 } 2464 fcmSwitchBasicGroup OBJECT-GROUP 2465 OBJECTS { fcmSwitchDomainId, fcmSwitchPrincipal, fcmSwitchWWN } 2466 STATUS current 2467 DESCRIPTION 2468 "Basic information about Fibre Channel switches." 2469 ::= { fcmgmtGroups 2 } 2471 fcmPortBasicGroup OBJECT-GROUP 2472 OBJECTS { fcmPortInstanceIndex, fcmPortWwn, fcmPortNodeWwn, 2473 fcmPortAdminType, fcmPortOperType, fcmPortFcCapClass, 2474 fcmPortFcOperClass, fcmPortTransmitterType, 2475 fcmPortConnectorType, fcmPortSerialNumber, 2476 fcmPortPhysicalNumber, fcmPortAdminSpeed, 2477 fcmPortCapProtocols, fcmPortOperProtocols } 2478 STATUS current 2479 DESCRIPTION 2480 "Basic information about Fibre Channel ports." 2482 ::= { fcmgmtGroups 3 } 2484 fcmPortStatsGroup OBJECT-GROUP 2485 OBJECTS { fcmPortBBCreditZeros, fcmPortFullInputBuffers } 2486 STATUS current 2487 DESCRIPTION 2488 "Traffic statistics, which are not specific to any one class 2489 of service, for Fibre Channel ports." 2490 ::= { fcmgmtGroups 4 } 2492 fcmPortClass23StatsGroup OBJECT-GROUP 2493 OBJECTS { fcmPortClass2RxFrames, fcmPortClass2RxOctets, 2494 fcmPortClass2TxFrames, fcmPortClass2TxOctets, 2495 fcmPortClass2Discards, fcmPortClass2RxFbsyFrames, 2496 fcmPortClass2RxPbsyFrames, 2497 fcmPortClass2RxFrjtFrames, 2498 fcmPortClass2RxPrjtFrames, 2499 fcmPortClass2TxFbsyFrames, 2500 fcmPortClass2TxPbsyFrames, 2501 fcmPortClass2TxFrjtFrames, 2502 fcmPortClass2TxPrjtFrames, fcmPortClass3RxFrames, 2503 fcmPortClass3RxOctets, fcmPortClass3TxFrames, 2504 fcmPortClass3TxOctets, fcmPortClass3Discards } 2505 STATUS current 2506 DESCRIPTION 2507 "Traffic statistics for Class 2 and Class 3 traffic on Fibre 2508 Channel ports." 2509 ::= { fcmgmtGroups 5 } 2511 fcmPortClassFStatsGroup OBJECT-GROUP 2512 OBJECTS { fcmPortClassFRxFrames, 2513 fcmPortClassFRxOctets, 2514 fcmPortClassFTxFrames, 2515 fcmPortClassFTxOctets, 2516 fcmPortClassFDiscards } 2517 STATUS current 2518 DESCRIPTION 2519 "Traffic statistics for Class F traffic on Fibre Channel 2520 ports." 2521 ::= { fcmgmtGroups 6 } 2523 fcmPortLcStatsGroup OBJECT-GROUP 2524 OBJECTS { fcmPortLcBBCreditZeros, fcmPortLcFullInputBuffers, 2525 fcmPortLcClass2RxFrames, fcmPortLcClass2RxOctets, 2526 fcmPortLcClass2TxFrames, fcmPortLcClass2TxOctets, 2527 fcmPortLcClass2Discards, fcmPortLcClass3Discards, 2528 fcmPortLcClass3RxFrames, fcmPortLcClass3RxOctets, 2529 fcmPortLcClass3TxFrames, fcmPortLcClass3TxOctets, 2530 fcmPortLcClass2RxFbsyFrames, 2531 fcmPortLcClass2RxPbsyFrames, 2532 fcmPortLcClass2RxFrjtFrames, 2533 fcmPortLcClass2RxPrjtFrames, 2534 fcmPortLcClass2TxFbsyFrames, 2535 fcmPortLcClass2TxPbsyFrames, 2536 fcmPortLcClass2TxFrjtFrames, 2537 fcmPortLcClass2TxPrjtFrames } 2538 STATUS current 2539 DESCRIPTION 2540 "Low-capacity (32-bit) statistics for Fibre Channel ports." 2541 ::= { fcmgmtGroups 7 } 2543 fcmPortErrorsGroup OBJECT-GROUP 2544 OBJECTS { fcmPortRxLinkResets, fcmPortTxLinkResets, 2545 fcmPortLinkResets, fcmPortRxOfflineSequences, 2546 fcmPortTxOfflineSequences, fcmPortLinkFailures, 2547 fcmPortLossofSynchs, fcmPortLossofSignals, 2548 fcmPortPrimSeqProtocolErrors, fcmPortInvalidTxWords, 2549 fcmPortInvalidCRCs, fcmPortInvalidOrderedSets, 2550 fcmPortFrameTooLongs, fcmPortTruncatedFrames, 2551 fcmPortAddressErrors, fcmPortDelimiterErrors, 2552 fcmPortEncodingDisparityErrors, 2553 fcmPortOtherErrors } 2554 STATUS current 2555 DESCRIPTION 2556 "Error statistics for Fibre Channel ports." 2557 ::= { fcmgmtGroups 8 } 2559 fcmSwitchPortGroup OBJECT-GROUP 2560 OBJECTS { fcmFxPortRatov, fcmFxPortEdtov, fcmFxPortRttov, 2561 fcmFxPortHoldTime, fcmFxPortCapBbCreditMax, 2562 fcmFxPortCapBbCreditMin, 2563 fcmFxPortCapDataFieldSizeMax, 2564 fcmFxPortCapDataFieldSizeMin, 2565 fcmFxPortCapClass2SeqDeliv, 2566 fcmFxPortCapClass3SeqDeliv, 2567 fcmFxPortCapHoldTimeMax, 2568 fcmFxPortCapHoldTimeMin, 2569 fcmISPortClassFCredit, 2570 fcmISPortClassFDataFieldSize } 2571 STATUS current 2572 DESCRIPTION 2573 "Information about ports on a Fibre Channel switch." 2574 ::= { fcmgmtGroups 9 } 2576 fcmSwitchLoginGroup OBJECT-GROUP 2577 OBJECTS { fcmFLoginPortWwn, fcmFLoginNodeWwn, 2578 fcmFLoginBbCreditModel, fcmFLoginBbCredit, 2579 fcmFLoginClassesAgreed, 2580 fcmFLoginClass2SeqDelivAgreed, 2581 fcmFLoginClass2DataFieldSize, 2582 fcmFLoginClass3SeqDelivAgreed, 2583 fcmFLoginClass3DataFieldSize } 2584 STATUS current 2585 DESCRIPTION 2586 "Information known to a Fibre Channel switch about 2587 attached/logged-in Nx_Ports." 2588 ::= { fcmgmtGroups 10 } 2590 fcmLinkBasicGroup OBJECT-GROUP 2591 OBJECTS { fcmLinkEnd1NodeWwn , fcmLinkEnd1PhysPortNumber, 2592 fcmLinkEnd1PortWwn, fcmLinkEnd2NodeWwn , 2593 fcmLinkEnd2PhysPortNumber, fcmLinkEnd2PortWwn, 2594 fcmLinkEnd2AgentAddress, fcmLinkEnd2PortType, 2595 fcmLinkEnd2UnitType, fcmLinkEnd2FcAddressId } 2596 STATUS current 2597 DESCRIPTION 2598 "Information about Fibre Channel links." 2599 ::= { fcmgmtGroups 11 } 2601 END 2602 7. Intellectual Property 2604 The IETF takes no position regarding the validity or scope of any 2605 intellectual property or other rights that might be claimed to pertain 2606 to the implementation or use of the technology described in this 2607 document or the extent to which any license under such rights might or 2608 might not be available; neither does it represent that it has made any 2609 effort to identify any such rights. Information on the IETF's 2610 procedures with respect to rights in standards-track and standards- 2611 related documentation can be found in BCP-11. Copies of claims of 2612 rights made available for publication and any assurances of licenses to 2613 be made available, or the result of an attempt made to obtain a general 2614 license or permission for the use of such proprietary rights by 2615 implementors or users of this specification can be obtained from the 2616 IETF Secretariat. 2618 The IETF invites any interested party to bring to its attention any 2619 copyrights, patents or patent applications, or other proprietary rights 2620 which may cover technology that may be required to practice this 2621 standard. Please address the information to the IETF Executive 2622 Director. 2624 8. Acknowledgements 2626 This memo is partly based on the information contained in the original 2627 submission of the Fibre Channel Management Integration MIB to the IETF's 2628 IPFC Working Group as draft-ietf-ipfc-fcmgmt-int-mib-0n.txt, and partly 2629 based on RFC 2837. 2631 Feedback has been incorporated into this document based on the comments 2632 of the following: Sudhir Pendse, SimpleSoft; Steve Senum, Cisco Systems; 2633 and Kha Sin Teow, Brocade. 2635 9. Normative References 2637 [RFC2434] 2638 Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA 2639 Considerations Section in RFCs", BCP:26, RFC 2434, October 1998. 2641 [RFC2578] 2642 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 2643 and S. Waldbusser, "Structure of Management Information Version 2 2644 (SMIv2)", STD 58, RFC 2578, April 1999. 2646 [RFC2579] 2647 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 2648 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2649 2579, April 1999. 2651 [RFC2580] 2652 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 2653 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2654 2580, April 1999. 2656 [RFC2737] 2657 McCloghrie, K., and A. Bierman, "Entity MIB (Version 2)", RFC 2737, 2658 December 1999. 2660 [RFC2790] 2661 Waldbusser, S., and P. Grillo, "Host Resources MIB", RFC 2790, 2662 March 2000. 2664 [RFC2863] 2665 McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 2666 2863, Cisco Systems, Argon Networks, June 2000. 2668 [RFC3411] 2669 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2670 Describing Simple Network Management Protocol (SNMP) Management 2671 Frameworks", STD 58, RFC 3411, December 2002. 2673 [FC-AL] 2674 "Information Technology - Fibre Channel - Arbitrated Loop (FC-AL)", 2675 ANSI X3.272, 1996. 2677 [FC-AL-2] 2678 "Fibre Channel - Arbitrated Loop (FC-AL-2)", ANSI INCITS 332-1999, 2679 1999. 2681 [FC-BB] 2682 "Fibre Channel - Backbone (FC-BB)" ANSI INCITS 342-2001, 2001. 2684 [FCP] 2685 "SCSI-3 Fibre Channel Protocol (FCP)", ANSI X3.269, 1996. 2687 [FC-FLA] 2688 "Fibre Channel - Fabric Loop Attachment (FC-FLA)", ANSI INCITS 2689 TR-20-1998, 1998. 2691 [FC-FS] 2692 "Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS 2693 373-2003, April 2003. 2695 [FC-GS-3] 2696 "Fibre Channel - Generic Services - 3 (FC-GS-3)" ANSI INCITS 2697 348-2001, 2001. 2699 [FC-MI] 2700 "Fibre Channel - Methodologies for Interconnects Technical Report 2701 (FC-MI)" INCITS TR-30-2002, 2002. 2703 [FC-PH] 2704 "Information Technology - Fibre Channel Physical and Signaling 2705 Interface (FC-PH)", ANSI X3.230, 1994. 2707 [FC-SW] 2708 "Fibre Channel - Switch Fabric (FC-SW)", ANSI INCITS 321-1998, 2709 1998. 2711 [FC-SW2] 2712 "Fibre Channel - Switch Fabric - 2 (FC-SW-2)", ANSI INCITS 2713 355-2001, June 2001. 2715 10. Informative References 2717 [RFC2741] 2718 Daniele, M., Wijnen, B., Ellison, M., and D. Francisco. "Agent 2719 Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000. 2721 [RFC2837] 2722 Teow, K., "Definitions of Managed Objects for the Fabric Element in 2723 Fibre Channel Standard", RFC 2837, May 2000. 2725 [RFC3410] 2726 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 2727 Applicability Statements for Internet-Standard Management 2728 Framework", RFC 3410, December 2002. 2730 [WWN1] 2731 Snively, R., "New identifier formats based on IEEE registration", 2732 http://standards.ieee.org/regauth/oui/tutorials/fibreformat.html, 2733 16 January 2001. 2735 [WWN2] 2736 Snively, R., "Use of the IEEE Registration Authority assigned 2737 'company_id' with the ANSI X3.230 FC-PH Fibre Channel specification 2738 and its extensions", 2739 http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.html, 2740 24 February 1997. 2742 [SENSOR] 2743 Bierman, A., Romascanu, D., and KC Norseth, "Entity Sensor 2744 Management Information Base", Internet Draft, working draft, 16 2745 October 2002. 2747 11. Security Considerations 2749 There are a number of management objects defined in this MIB that have a 2750 MAX-ACCESS clause of read-write: 2752 fcmInstanceTextName 2753 fcmInstanceDescr 2754 fcmSwitchDomainId 2755 fcmPortAdminType 2756 fcmPortAdminSpeed 2757 fcmISPortClassFCredit 2759 Such objects may be considered sensitive or vulnerable in some network 2760 environments. For example, the ability to change network topology or 2761 network speed may afford an attacker the ability to obtain better 2762 performance at the expense of other network users; setting 2763 fcmSwitchDomainId to an invalid value could lead to denial of service in 2764 some configurations. The support for SET operations in a non-secure 2765 environment without proper protection can have a negative effect on 2766 network operations. 2768 Some of the readable objects in this MIB module (i.e., objects with a 2769 MAX-ACCESS other than not-accessible) may be considered sensitive or 2770 vulnerable in some network environments. It is thus important to 2771 control even GET and/or NOTIFY access to these objects and possibly to 2772 even encrypt the values of these objects when sending them over the 2773 network via SNMP. In particular, these objects provide information on 2774 network topology: 2776 fcmLinkEnd1NodeWwn 2777 fcmLinkEnd1PhysPortNumber 2778 fcmLinkEnd1PortWwn 2779 fcmLinkEnd2NodeWwn 2780 fcmLinkEnd2PhysPortNumber 2781 fcmLinkEnd2PortWwn 2782 fcmLinkEnd2AgentAddress 2783 fcmLinkEnd2PortType 2784 fcmLinkEnd2UnitType 2785 fcmLinkEnd2FcAddressId 2787 SNMP versions prior to SNMPv3 did not include adequate security. Even 2788 if the network itself is secure (for example by using IPSec), even then, 2789 there is no control as to who on the secure network is allowed to access 2790 and GET/SET (read/change/create/delete) the objects in this MIB module. 2792 It is RECOMMENDED that implementors consider the security features as 2793 provided by the SNMPv3 framework (see [RFC3410], section 8), including 2794 full support for the SNMPv3 cryptographic mechanisms (for authentication 2795 and privacy). 2797 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. 2798 Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic 2799 security. It is then a customer/operator responsibility to ensure that 2800 the SNMP entity giving access to an instance of this MIB module is 2801 properly configured to give access to the objects only to those 2802 principals (users) that have legitimate rights to indeed GET or SET 2803 (change/create/delete) them. 2805 12. IANA Considerations 2807 12.1. OID Assignment 2809 IANA is requested to make a MIB OID assignment under the transmission 2810 branch. Specifically, for { transmission 56 } to be assigned as the OID 2811 for fcMgmtMIB. This sub-identifier is requested because this MIB 2812 contains the media-specific definitions which correspond to the ifType 2813 value of fibreChannel(56). 2815 12.2. FC Port Type Registry 2817 IANA is requested to establish a registry for Fibre Channel Port Types. 2818 The registry is to be split into disjoint subset ranges: 2820 1) a 'standard' range for Fibre Channel Port Types which have been 2821 standardized by the InterNational Committee for Information 2822 Technology Standards (INCITS)'s Technical Committee T11 (see 2823 http://www.incits.org/tc_home/t11.htm and 2824 http://www.t11.org/index.htm). This range will be subject to the 2825 'Expert Review' and 'Specification Required' policies described in 2826 [RFC2434], with the following provisions: 2828 - the Expert Reviewer is to be appointed by the IESG. 2830 - the Expert Reviewer shall obtain approval (or rejection) from 2831 INCITS Technical Committee T11 via the chair of that Committee. 2832 Rejected values shall not be added to the registry. 2834 - if the addition is approved, the Expert shall advise IANA of how 2835 to record the reference to the T11 specification document which 2836 describes the newly added port type(s), and which is considered 2837 to be the "other permanent and readily available reference" 2838 required by [RFC2434]. 2840 The initial assignments in the 'standard' range will be as follows: 2842 Assigned 2843 Value Type Meaning 2844 -------- ------ ------- 2845 1 unknown for use when the type is not known, 2846 or is "unidentified" as specified in 2847 section 5.1.2.10 of [FC-GS-3] 2848 2 other used for types without assigned values 2849 3 -- an obsolete value, not to be re-assigned 2850 4 N_Port see [FC-FS] 2851 5 NL_Port see [FC-FS] 2852 6 F_Port see [FC-FS] 2853 7 FL_Port see [FC-FS] 2854 8 E_Port see [FC-FS] 2855 9 B_Port see [FC-FS] 2856 10 G_Port see [FC-SW-3] 2857 11 GL_Port see [FC-SW-3] 2858 12 F/NL_Port see [FC-AL-2] 2860 It is suggested that the above range can be extended up to a maximum 2861 of 9,999. 2863 2) a range which is assigned under the "Private Use" policy described in 2864 [RFC2434] and is for values intended for private use by one party or 2865 among mutually consenting parties. It is suggested that values in 2866 this range extend from 10,000 to 99,999. IANA is instructed not to 2867 make any allocations from this range. 2869 3) values larger than 99,999 be RESERVED. 2871 13. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt 2873 13.1. Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt 2875 The Fibre Channel Management Integration MIB had the following major 2876 problems: 2878 - It wasn't formatted using SMIv2, which is mandatory. 2880 - The MIB seemed to have been defined with the notion that it would 2881 be the only MIB that a Fibre Channel product will require. The 2882 notion of an agent implementing just a single MIB was abandoned by 2883 the IETF in 1992 as being non-scaleable. Rather, a Fibre Channel 2884 MIB needed to be another MIB in the continuing series of MIBs 2885 defined by the IETF, and thus, it needed to be consistent with its 2886 predecessors. In other words, there are existing MIBs which all 2887 SNMP agents must support, even if the support of Fibre Channel 2888 interfaces is the only functionality that they have. Thus, it was 2889 essential that the Fibre Channel Integration MIB contained only 2890 objects for information which is specific to Fibre Channel. All 2891 objects relevant to non-Fibre Channel environments needed to be 2892 removed. This issue applied to a large fraction of the objects 2893 defined in the MIB. 2895 - The MIB had some but not complete overlap in functionality with RFC 2896 2837. 2898 - Every SNMP agent must implement the ifTable. The ifTable counters 2899 are the MIB objects most well-used by administrators in SNMP 2900 management. SNMP agents need to implement a row in the ifTable for 2901 each of their network interfaces, including their Fibre Channel 2902 interfaces. The IF-MIB requires a media-specific MIB to specify 2903 how that type of interface uses the ifTable (see section 4 in RFC 2904 2863). RFC 2837 doesn't do that, and nor did the Fibre Channel 2905 Integration MIB. 2907 - It incorrectly used the OCTET STRING syntax (instead of Counter32 2908 or Counter64) for counters. 2910 13.2. Detailed Changes 2912 13.2.1. Removal of Sensor-related objects 2914 Information about sensors is not specific to Fibre Channel, and 2915 therefore should not be in this MIB. (At the time of writing, the the 2916 IETF's ENTITY MIB Working Group has produced a first draft of a Sensor 2917 MIB, see [SENSOR].) This removed the need for: 2919 connUnitSensorTable (and all its contents) 2920 connUnitNumSensors 2921 connUnitSensorStatusChange 2923 13.2.2. Removal of Trap-registration objects 2925 Information about registering "traps" is not specific to Fibre Channel, 2926 and therefore should not be in this MIB. (For similar functionality, 2927 see SNMP-NOTIFICATION-MIB and SNMP-TARGET-MIB in RFC 2573). This 2928 removed the need for: 2930 trapMaxClients 2931 trapClientCount 2932 trapRegTable (and all its contents) 2934 13.2.3. Removal of Event-related objects 2936 Information about generic events is not specific to Fibre Channel, and 2937 therefore should not be in this MIB. (For similar functionality, see 2938 the Event group in RFC 2819 and the Notification Log MIB in RFC 3014; 2939 the SNMP-NOTIFICATION-MIB provides for the filtering of notifications.) 2940 This removed the need for: 2942 connUnitEventTable (and all its contents) 2943 connUnitEventFilter 2944 connUnitNumEvents 2945 connUnitMaxEvents 2946 connUnitEventCurrID 2947 connUnitEventTrap 2949 13.2.4. Removal of inventory-related information 2951 Aspects of hardware (physical) components are represented in the Entity 2952 MIB (RFC 2737); aspects of software modules are represented in the Host 2953 Resources MIB (RFC 2790). Two new objects provide indexing from this 2954 MIB into those MIBs: one having the value of PhysicalIndex (or zero) and 2955 the other having the value of hrSWInstalledIndex (or zero). These 2956 replaced the need for: 2958 connUnitNumports 2959 connUnitRevsTable (and all its contents) 2960 connUnitNumRevs 2961 connUnitPortRevision 2962 connUnitPortVendor 2963 connUnitProduct 2964 connUnitInfo 2965 connUnitSn 2966 connUnitModuleId 2967 connUnitVendorId 2968 connUnitDeletedTrap 2970 13.2.5. Removal of revision numbers 2972 The forward/backward compatibility rules of how to evolve MIBs are 2973 designed such that MIBs do not have revision numbers. This removed the 2974 need for: 2976 revisionNumber 2978 13.2.6. Removal of other not FC-specific information 2980 Other information was removed because it was not specific to Fibre 2981 Channel: 2983 systemURL 2984 statusChangeTime 2985 configurationChangeTime 2986 connUnitUrl 2987 connUnitUpTime 2988 connUnitState 2989 connUnitContact 2990 connUnitLocation 2991 connUnitProxyMaster 2992 connUnitControl 2993 connUnitStatus 2994 connUnitStatusChange 2996 13.2.7. Clean-up of ambiguous/obsolete definitions 2998 Some information in the FC Management integration was obsolete or 2999 ambiguous: 3001 statusChangeTime (obsolete) 3002 configurationChangeTime (obsolete) 3003 connUnitTableChangeTime (obsolete) 3004 connUnitStatusChangeTime (obsolete) 3005 connUnitConfigurationChangeTime (obsolete) 3006 connUnitNumZones (obsolete) 3007 connUnitZoneTable (referenced but not defined) 3008 connUnitLinkCurrIndex (badly defined) 3010 13.2.8. Use of an ifTable entry 3012 The following objects were removed because they duplicated existing IF- 3013 MIB objects: 3015 redundant object existing object(s) 3016 ---------------- ------------------ 3017 connUnitPortStatCountError ifInErrors & ifOutErrors 3018 connUnitPortStatCountTxObjects ifOutUcastPkts & 3019 ifHCOutUcastPkts 3020 connUnitPortStatCountRxObjects ifInUcastPkts & 3021 ifHCInUcastPkts 3022 connUnitPortStatCountTxElements ifOutOctets & 3023 ifHCOutOctets 3024 connUnitPortStatCountRxElements ifInOctets & 3025 ifHCInOctets 3026 connUnitPortStatCountRxMulticastObjects 3027 ifInMulticastPkts & 3028 ifHCInMulticastPkts 3029 connUnitPortStatCountTxMulticastObjects 3030 ifOutMulticastPkts & 3031 ifHCOutMulticastPkts 3032 connUnitPortStatCountRxBroadcastObjects 3033 ifInBroadcastPkts & 3034 ifHCInBroadcastPkts 3035 connUnitPortStatCountTxBroadcastObjects 3036 ifOutBroadcastPkts & 3037 ifHCOutBroadcastPkts 3038 connUnitPortFCId ifPhysAddress 3039 connUnitPortControl ifAdminStatus 3040 connUnitPortState ifAdminStatus 3041 connUnitPortHWState ifOperStatus 3042 connUnitPortStatus ifOperStatus 3043 connUnitPortName ifAlias 3044 connUnitPortStatObject ifSpecific 3045 connUnitNumports ifNumber 3046 connUnitPortStatusChange linkUp/linkDown 3048 13.2.9. Removed because of AgentX difficulty 3050 An AgentX environment [RFC2741] consists of a master agent and several 3051 sub-agents. It is not difficult to implement the same MIB in several 3052 such sub-agents if all of the MIB's tables have a common index variable 3053 as the first auxiliary object in their INDEX clauses. However, any 3054 scalars which the MIB contains pose a problem for the AgentX 3055 environment. All the (remaining) scalars were therefore removed: 3057 revisionNumber 3058 uNumber 3059 systemURL 3061 13.2.10. FC Management Instance 3063 The term "connectivity unit" was changed to "FC management instance". 3065 The term "connectivity unit" was not properly defined in draft-ietf- 3066 ipfc-fcmgmt-int-mib-07.txt, and its usage provided a confused mixture of 3067 indications to the implementor: 3069 - the definition of FcUnitType suggested it was functional; 3070 - the definition of uNumber suggested it was physical; 3071 - the definition of connUnitProduct suggested it was a vendor's product; 3072 - etc. 3074 The common implementation strategy for "connectivity unit" was whatever 3075 grouping was easiest in providing access to the management 3076 functionality. (One such grouping accommodates a single SNMP agent 3077 having multiple AgentX [RFC2741] sub-agents, each supporting a separate 3078 implementation of the MIB.) 3080 In fact, this scenario is not new; in practice, a "connectivity unit" 3081 will have the same semantics as a management "instance" in other MIBs, 3082 e.g., the IPS WG's own iSCSI MIB. For this MIB, its meaning is: "a 3083 separable managed instance of Fibre Channel functionality". Given this 3084 definition, then "FC management instance" is a better name because it is 3085 more accurate and more representative of the definition, than is 3086 "connectivity unit". 3088 13.2.11. Counter Syntax 3090 All packet and octet counters have been changed to be Counter64's (but 3091 Counter32 versions of them are also included for use by old agents). 3092 The error counters have been changed to Counter32's. (In the probably 3093 impossible, and at most improbable, circumstances that the rate of 3094 occurrence of errors, even on a 10Gbs Fibre Channel interface, might 3095 wrap faster than a hour, the fact that errors are occurring will almost 3096 certainly be apparent from other MIB objects.) 3098 13.2.12. Obsolete/Little-Used Fibre Channel features 3100 Information relating to Fibre Channel features which are obsolete or not 3101 widely-implemented has been deleted. (For more information, see section 3102 6.2.1 and section 6.2.2 of [FC-MI].) 3104 - Class 1 service, 3105 - Intermix Mode, 3106 - Stacked Conn Mode. 3107 - PH version numbers 3109 Note that with support for Class 1 service being deleted, only class 2 3110 now needs F_BSY, F_RJT, P_BSY and P_RJT counters, and thus they no 3111 longer need to be counted for all classes as well as for class 2, and 3112 therefore these objects: 3114 connUnitPortStatCountFBSYFrames 3115 connUnitPortStatCountPBSYFrames 3116 connUnitPortStatCountFRJTFrames 3117 connUnitPortStatCountPRJTFrames 3119 have been deleted. 3121 13.3. Name Server objects 3123 A table of Name Server information was present in draft-ietf-ipfc- 3124 fcmgmt-int-mib-07.txt. That information is not currently represented in 3125 this MIB, because this MIB is already quite large, and a set of Name 3126 Server objects are expected to be defined in a separate (new) MIB. 3128 13.4. Additional objects 3130 Support for Class F traffic, including 32-bit octet and frame counters, 3131 has been added. 3133 14. Comparison to RFC 2837 3135 This MIB is a superset of RFC 2837, except for the following: 3137 - the fcFeClass1AccountingGroup group is obsolete, 3138 - fcFxPortConnectedNxPort, fcFxPortFcphVersionHigh, 3139 fcFxPortFcphVersionLow, fcFxPortFcphVersionAgreed, 3140 fcFxPortStackedConnModeAgreed, fcFxPortIntermixSuppAgreed, 3141 fcFxPortCapStackedConnMode and fcFxPortCapIntermix are obsolete, 3142 - fcFxPortBbCredit and fcFxPortRxBufSize are per attached Nx_Port, 3143 - fcFxPortBbCreditAvailable is ephemeral, 3144 - fcFeModuleTable is mostly contained in the entPhysicalTable, 3145 - fcFxPortPhysAdminStatus, fcFxPortPhysOperStatus, and 3146 fcFxPortPhysLastChange have equivalents in the ifTable. 3148 15. Author's Address 3150 Keith McCloghrie 3151 Cisco Systems, Inc. 3152 170 West Tasman Drive 3153 San Jose, CA USA 95134 3154 Phone: +1 408-526-5260 3155 Email: kzm@cisco.com 3157 16. Full Copyright Statement 3159 Copyright (C) The Internet Society (2004). All Rights Reserved. 3161 This document and translations of it may be copied and furnished to 3162 others, and derivative works that comment on or otherwise explain it or 3163 assist in its implementation may be prepared, copied, published and 3164 distributed, in whole or in part, without restriction of any kind, 3165 provided that the above copyright notice and this paragraph are included 3166 on all such copies and derivative works. However, this document itself 3167 may not be modified in any way, such as by removing the copyright notice 3168 or references to the Internet Society or other Internet organizations, 3169 except as needed for the purpose of developing Internet standards in 3170 which case the procedures for copyrights defined in the Internet 3171 Standards process must be followed, or as required to translate it into 3172 languages other than English. 3174 The limited permissions granted above are perpetual and will not be 3175 revoked by the Internet Society or its successors or assigns. 3177 This document and the information contained herein is provided on an "AS 3178 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 3179 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 3180 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 3181 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 3182 FITNESS FOR A PARTICULAR PURPOSE. 3184 "Copyright (C) The Internet Society (2004). This document is subject to 3185 the rights, licenses and restrictions contained in BCP 78, and except as 3186 set forth therein, the authors retain all their rights." 3188 "This document and the information contained herein are provided on an 3189 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 3190 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3191 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3192 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3193 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3194 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."