idnits 2.17.1 draft-ietf-ipfc-fabric-element-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 50 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 10 instances of too long lines in the document, the longest one being 6 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 392 has weird spacing: '...Element or an...' == Line 2097 has weird spacing: '...for the purpo...' -- 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 (Sep 20, 1999) is 8957 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 section? '1' on line 1954 looks like a reference -- Missing reference section? '2' on line 1959 looks like a reference -- Missing reference section? '3' on line 1964 looks like a reference -- Missing reference section? '4' on line 1968 looks like a reference -- Missing reference section? '5' on line 1971 looks like a reference -- Missing reference section? '6' on line 1977 looks like a reference -- Missing reference section? '7' on line 1983 looks like a reference -- Missing reference section? '8' on line 1989 looks like a reference -- Missing reference section? '9' on line 1994 looks like a reference -- Missing reference section? '10' on line 1999 looks like a reference -- Missing reference section? '11' on line 2005 looks like a reference -- Missing reference section? '12' on line 2011 looks like a reference -- Missing reference section? '13' on line 2015 looks like a reference -- Missing reference section? '14' on line 2021 looks like a reference -- Missing reference section? '15' on line 2025 looks like a reference -- Missing reference section? '16' on line 2030 looks like a reference -- Missing reference section? '17' on line 2037 looks like a reference -- Missing reference section? '21' on line 2054 looks like a reference -- Missing reference section? '22' on line 2059 looks like a reference -- Missing reference section? '20' on line 2050 looks like a reference -- Missing reference section? '24' on line 2070 looks like a reference -- Missing reference section? '18' on line 2042 looks like a reference -- Missing reference section? '23' on line 2064 looks like a reference -- Missing reference section? 'L' on line 214 looks like a reference -- Missing reference section? '19' on line 2046 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 28 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IP and ARP Over FC Working Group Kha Sin Teow 2 INTERNET-DRAFT Brocade Communications Systems, Inc. 3 Sep 20, 1999 5 Definitions of Managed Objects 6 for the Fabric Element in Fibre Channel Standard 7 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 30 This memo defines an extension to the Management Information Base 31 (MIB) for use with network management protocols in TCP/IP-based 32 internets. In particular, it defines the objects for managing the 33 operations of the Fabric Element portion of the Fibre Channel 34 Standards. 36 Copyright Notice 38 Copyright (C) The Internet Society (1999). All Rights Reserved. 40 Table of Contents 42 1. The SNMP Management Framework ..................................3 43 2. Overview .......................................................4 44 2.1 Management View of a Fabric Element ...........................4 45 2.2 Structure of the Fabric Element MIB ...........................6 46 3. Object Definitions .............................................7 47 The Configuration Group .....................................10 48 The Module Table ..........................................10 49 The FxPort Configuration Table ............................13 50 The Operation Group .........................................18 51 The FxPort Operation Table ................................18 52 The FxPort Physical Level Table ...........................20 53 The FxPort Fabric Login Table .............................23 54 The Error Group .............................................27 55 The Accounting Group ........................................30 56 The Class 1 Accounting Table ..............................31 57 The Class 2 Accounting Table ..............................34 58 The Class 3 Accounting Table ..............................36 59 The Capability Group ........................................38 60 Conformance information .....................................41 61 4. Security Considerations .......................................45 62 5. Intellectual Property .........................................45 63 6. Acknowledgements ..............................................46 64 7. References ....................................................46 65 7.1 IETF References ..............................................46 66 7.2 Approved ANSI/NCITS References ...............................48 67 7.3 ANSI/NCITS References Under Development ......................49 68 8. Editors' Addresses ............................................49 69 9. Full Copyright Statement ......................................49 71 1. The SNMP Management Framework 73 The SNMP Management Framework presently consists of five major components: 75 o An overall architecture, described in RFC 2571 [1]. 77 o Mechanisms for describing and naming objects and events for 78 the purpose of management. The first version of this Struc- 79 ture of Management Information (SMI) is called SMIv1 and 80 described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The 81 second version, called SMIv2, is described in RFC 2578 [5], 82 RFC 2579 [6] and RFC 2580 [7]. 84 o Message protocols for transferring management information. 85 The first version of the SNMP message protocol is called 86 SNMPv1 and described in RFC 1157 [8]. A second version of the 87 SNMP message protocol, which is not an Internet standards 88 track protocol, is called SNMPv2c and described in RFC 1901 89 [9] and RFC 1906 [10]. The third version of the message pro- 90 tocol is called SNMPv3 and described in RFC 1906 [10], RFC 91 2572 [11] and RFC 2574 [12]. 93 o Protocol operations for accessing management information. The 94 first set of protocol operations and associated PDU formats 95 is described in RFC 1157 [8]. A second set of protocol opera- 96 tions and associated PDU formats is described in RFC 1905 97 [13]. 99 o A set of fundamental applications described in RFC 2573 [14] 100 and the view-based access control mechanism described in RFC 101 2575 [15]. 103 A more detailed introduction to the current SNMP Management Framework 104 can be found in RFC 2570 [16]. 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. Objects in the MIB are 108 defined using the mechanisms defined in the SMI. 110 This memo specifies a MIB module that is compliant to the SMIv2. A 111 MIB conforming to the SMIv1 can be produced through the appropriate 112 translations. The resulting translated MIB must be semantically 113 equivalent, except where objects or events are omitted because no 114 translation is possible (use of Counter64). Some machine readable 115 information in SMIv2 will be converted into textual descriptions in 116 SMIv1 during the translation process. However, this loss of machine 117 readable information is not considered to change the semantics of the 118 MIB. 120 2. Overview 122 A Fibre Channel Fabric is an entity which interconnects Node Ports 123 (N_Ports) or Node Loop Ports (NL_Ports). It provides transport and 124 routing functions. In essence, a Fabric is a network of N_Ports 125 and/or NL_Ports to communicate with one another. A Fabric is com- 126 posed of one or more Fabric Element that are interconnected via 127 Inter-element Links (IEL). A Fabric Element is the smallest unit of 128 a Fabric that meets the definition of a Fabric. It must consist of 129 at least three external ports to connect to either N_Ports, NL_Ports 130 or other Fabric Elements. In general, a Fabric Element port may be 131 of one of the following types: 133 (1) F_Port, a fabric port to connect to an N_Port ([17], [21], 134 [22]); 136 (2) FL_Port, a fabric port that also supports a FC Arbitrated Loop 137 consisting of one or more NL_Ports ([20], [24]). 139 (3) E_Port, an expansion port to connect to another Fabric Element 140 ([18], [23]); 142 This memo shall define objects related to a Fabric Element, its 143 F_Ports and FL_Ports. Objects related to other types of FC ports 144 shall be defined in future. 146 For the rest of the document, the term, "FxPort", will be used to 147 refer to both F_Port and FL_Port where the distinction is not 148 necessary. The term, "NxPort" will be used to refer to both N_Port 149 and NL_Port in the similar fashion. 151 2.1. Management View of a Fabric Element 153 From the management perspective, it is helpful to view a Fabric 154 Element to be consisting of multiple "modules". Each module is a 155 grouping, either physical or logical, of one or more ports that may 156 be managed as a sub-entity within the Fabric Element. 158 This module mapping is recommended but optional. A vendor may elect 159 to put all ports into a single module, or to divide the ports into 160 modules that do not match physical divisions. 162 The object fcFeModuleCapacity indicates the maximum number of modules 163 that a given Fabric Element may contain. This value must remain 164 constant from one management restart to the next. 166 Each module is uniquely identified by a module number in the range of 167 1 through fcFeModuleCapacity inclusive. Modules may come and go 168 without causing a management reset (of sysUpTime), and may be 169 sparsely numbered within the Fabric Element. That is, the module 170 numbering is not required to be contiguous. For instance, if a 171 module is mapped physically to a field-replaceable card and in a 172 13-card cage Fabric Element, cards 3, 5, 6 and 7 may be installed. 173 The vendor may choose to label them as modules 3, 5, 6 and 7 174 respectively. In this example, the value of fcFeModuleCapacity is 175 13. 177 A Fabric Element may also provide a proxy management on behalf of 178 another management entity by presenting it as one of its Fabric 179 Element modules. 181 The object fcFeModuleFxPortCapacity indicates the maximum number of 182 ports that a given module may contain. The value of 183 fcFeModuleFxPortCapacity must not change for a given module. 184 However, a module may be deleted from the Fabric Element and replaced 185 with a module containing a different number of ports. The value of 186 fcFeModuleLastChange will indicate that a change took place. 188 Each port within the Fabric Element is uniquely identified by a 189 combination of module index and port index, where port index is an 190 integer in the range 1..fcFeModuleFxPortCapacity. As with modules 191 within a Fabric Element, ports within a module may be sparsely 192 numbered. That is the port numbering is not required to be 193 contiguous. Likewise, ports may come and go within a module without 194 causing a management reset. 196 In terms of attachment, an F_Port will be attached to another N_Port; 197 and an FL_Port will be attached to one or up to 126 NL_Ports. In 198 general, an FxPort may be attached to one or more NxPorts. Each 199 NxPort associated with an FxPort will be uniquely identified by a 200 combination of module index, FxPort index and NxPort index. An 201 NxPort index is an integer in the range (1..126). The following 202 diagram illustrates the management view of a Fabric Element. 204 #=======================================================# 205 # +----------------- - - - -----------------+ # 206 # | Module 1 [1] . . . [i] | # 207 # +----------------- - - - -----------------+ # 208 # o o o # 209 # +---------------------- - - - --------+ # 210 # | Module M [1] . . . [n] | # 211 # +---------------------- - - - -----^--+ # 212 #=====================================|=================# 213 | 214 One or more NxPorts { [1] . . . [L] }<-+ 215 - - - - - - - - - 216 where "i", "n", "M" and "L" are some arbitrary sample integer values, 217 and "L" must be less than 127. 219 2.2. Structure of the Fabric Element MIB 221 This memo assumes that a Fabric Element has an SNMP entity associated 222 with its managed objects. The managed objects are divided as follow: 224 - the Configuration group 225 - the Operation group 226 - the Error group 227 - the Accounting group 228 - the Capability group 230 In each group, scalar objects and table entries are defined. 232 The Configuration group contains configuration and service parameters 233 for the Fabric Element, modules and the FxPorts. 235 The Operation group contains the operational status and parameters of 236 an FxPort. The group also contains the service parameters that have 237 been established between the FxPort and its attached NxPort, if 238 applicable. 240 The Error group contains counters tracking various types of errors 241 detected by each FxPort. The information may be used for diagnostics 242 and/or to derive the quality of the link between an FxPort and one or 243 more attached NxPorts. 245 The Accounting group contains statistic data suitable for deriving 246 accounting and performance information. 248 The Capability group contains parameters indicating the inherent 249 capability of the Fabric Element and each FxPort. 251 3. Object Definitions 253 FCFABRIC-ELEMENT-MIB DEFINITIONS ::= BEGIN 254 IMPORTS 255 MODULE-IDENTITY, OBJECT-TYPE, 256 Unsigned32, Counter32, Gauge32, BITS 257 FROM SNMPv2-SMI 258 TEXTUAL-CONVENTION, TruthValue, DisplayString, TimeStamp 259 FROM SNMPv2-TC 260 MODULE-COMPLIANCE, OBJECT-GROUP 261 FROM SNMPv2-CONF; 263 fcFabric MODULE-IDENTITY 264 LAST-UPDATED "9906250000Z" 265 ORGANIZATION "IETF IPFC Working Group" 266 CONTACT-INFO "Kha Sin Teow 267 Brocade Communications Systems, 268 1901 Guadalupe Parkway, 269 San Jose, CA 95131 270 U.S.A 271 Tel: +1 408 487 8180 272 Fax: +1 408 487 8190 273 Email: khasin@Brocade.COM" 274 DESCRIPTION "The MIB module for Fibre Channel Fabric Element." 275 REVISION "9909270000Z" 276 DESCRIPTION "The revision submitted for IESG review." 277 ::= { fibreChannel(XXX) 1 } -- TO BE ASSIGNED 279 -- Fabric Element 280 fcFe OBJECT IDENTIFIER ::= { fcFabric 1 } 282 fcFeMIBObjects OBJECT IDENTIFIER ::= { fcFe 1 } 284 -- Note: 285 -- fcFeMIBCompformance OBJECT IDENTIFIER ::= { fcFe 2 } 286 -- see at the end of the module 288 -- Groups under fcFe 289 fcFeConfig OBJECT IDENTIFIER ::= { fcFeMIBObjects 1 } 290 fcFeOp OBJECT IDENTIFIER ::= { fcFeMIBObjects 2 } 291 fcFeError OBJECT IDENTIFIER ::= { fcFeMIBObjects 3 } 292 fcFeAcct OBJECT IDENTIFIER ::= { fcFeMIBObjects 4 } 293 fcFeCap OBJECT IDENTIFIER ::= { fcFeMIBObjects 5 } 295 -- Textual Conventions 296 MilliSeconds ::= TEXTUAL-CONVENTION 297 STATUS current 298 DESCRIPTION "Represents time unit value in milliseconds." 299 SYNTAX Unsigned32 301 MicroSeconds ::= TEXTUAL-CONVENTION 302 STATUS current 303 DESCRIPTION "Represents time unit value in microseconds." 304 SYNTAX Unsigned32 306 FcNameId ::= TEXTUAL-CONVENTION 307 STATUS current 308 DESCRIPTION "Represents the Worldwide Name associated with 309 a Fibre Channel (FC) entity." 310 SYNTAX OCTET STRING (SIZE (8)) 312 FcAddressId ::= TEXTUAL-CONVENTION 313 STATUS current 314 DESCRIPTION "Represents Fibre Channel Address ID, a 24-bit 315 value unique within the address space of a Fabric" 316 SYNTAX OCTET STRING (SIZE (3)) 318 FcRxDataFieldSize ::= TEXTUAL-CONVENTION 319 STATUS current 320 DESCRIPTION "Represents the receive data field size of an 321 NxPort or FxPort." 322 SYNTAX INTEGER (128..2112) 324 FcBbCredit ::= TEXTUAL-CONVENTION 325 STATUS current 326 DESCRIPTION "Represents the buffer-to-buffer credit of an 327 NxPort or FxPort." 328 SYNTAX INTEGER (0..32767) 330 FcphVersion ::= TEXTUAL-CONVENTION 331 STATUS current 332 DESCRIPTION "Represents the version of FC-PH supported by an 333 NxPort or FxPort." 334 SYNTAX INTEGER (0..255) 336 FcStackedConnMode ::= TEXTUAL-CONVENTION 337 STATUS current 338 DESCRIPTION "Represents an enumerated value used to indicate 339 the Class 1 Stacked Connect Mode supported by 340 an NxPort or FxPort." 341 SYNTAX INTEGER { 342 none(1), 343 transparent(2), 344 lockedDown(3) 345 } 347 FcCosCap ::= TEXTUAL-CONVENTION 348 STATUS current 349 DESCRIPTION "Represents the class of service capability of an 350 NxPort or FxPort." 351 SYNTAX BITS { classF(0), class1(1), class2(2), class3(3), 352 class4(4), class5(5), class6(6) } 354 FcFeModuleCapacity ::= TEXTUAL-CONVENTION 355 STATUS current 356 DESCRIPTION "Represents the maximum number of modules within 357 a Fabric Element." 358 SYNTAX Unsigned32 360 FcFeFxPortCapacity ::= TEXTUAL-CONVENTION 361 STATUS current 362 DESCRIPTION "Represents the maximum number of FxPorts within 363 a module." 364 SYNTAX Unsigned32 366 FcFeModuleIndex ::= TEXTUAL-CONVENTION 367 STATUS current 368 DESCRIPTION "Represents the module index within a conceptual table." 369 SYNTAX Unsigned32 371 FcFeFxPortIndex ::= TEXTUAL-CONVENTION 372 STATUS current 373 DESCRIPTION "Represents the FxPort index within a conceptual table." 374 SYNTAX Unsigned32 376 FcFeNxPortIndex ::= TEXTUAL-CONVENTION 377 STATUS current 378 DESCRIPTION "Represents the NxPort index within a conceptual table." 379 SYNTAX INTEGER (1..126) 381 FcBbCreditModel ::= TEXTUAL-CONVENTION 382 STATUS current 383 DESCRIPTION "Represents the BB_Credit model of an FxPort." 384 SYNTAX INTEGER { regular(1), alternate (2) } 386 -- The Configuration group 388 -- This group consists of scalar objects and tables. 389 -- It contains the configuration and service parameters 390 -- of the Fabric Element and the FxPorts. 391 -- The group represents a set of parameters associated with 392 -- the Fabric Element or an FxPort to support its NxPorts. 393 -- Implementation of this group is mandatory. 395 fcFabricName OBJECT-TYPE 396 SYNTAX FcNameId 397 MAX-ACCESS read-write 398 STATUS current 399 DESCRIPTION 400 "The Name_Identifier of the Fabric to which this Fabric 401 Element belongs." 402 ::= { fcFeConfig 1 } 404 fcElementName OBJECT-TYPE 405 SYNTAX FcNameId 406 MAX-ACCESS read-write 407 STATUS current 408 DESCRIPTION 409 "The Name_Identifier of the Fabric Element." 410 ::= { fcFeConfig 2 } 412 fcFeModuleCapacity OBJECT-TYPE 413 SYNTAX FcFeModuleCapacity 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The maximum number of modules in the Fabric Element, 418 regardless of their current state." 419 ::= { fcFeConfig 3 } 420 -- The Module Table. 421 -- This table contains one entry for each module, 422 -- information of the modules. 424 fcFeModuleTable OBJECT-TYPE 425 SYNTAX SEQUENCE OF FcFeModuleEntry 426 MAX-ACCESS not-accessible 427 STATUS current 428 DESCRIPTION 429 "A table that contains, one entry for each module in the 430 Fabric Element, information of the modules." 431 ::= { fcFeConfig 4 } 433 fcFeModuleEntry OBJECT-TYPE 434 SYNTAX FcFeModuleEntry 435 MAX-ACCESS not-accessible 436 STATUS current 437 DESCRIPTION 438 "An entry containing the configuration parameters of a 439 module." 440 INDEX { fcFeModuleIndex } 441 ::= { fcFeModuleTable 1 } 443 FcFeModuleEntry ::= 444 SEQUENCE { 445 fcFeModuleIndex 446 FcFeModuleIndex, 447 fcFeModuleDescr 448 DisplayString, 449 fcFeModuleObjectID 450 OBJECT IDENTIFIER, 451 fcFeModuleOperStatus 452 INTEGER, 453 fcFeModuleLastChange 454 TimeStamp, 455 fcFeModuleFxPortCapacity 456 FcFeFxPortCapacity, 457 fcFeModuleName 458 FcNameId 459 } 461 fcFeModuleIndex OBJECT-TYPE 462 SYNTAX FcFeModuleIndex 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION 466 "This object identifies the module within the Fabric Element 467 for which this entry contains information. This value is 468 never greater than fcFeModuleCapacity." 469 ::= { fcFeModuleEntry 1 } 471 fcFeModuleDescr OBJECT-TYPE 472 SYNTAX DisplayString 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "A textual description of the module. This value should 477 include the full name and version identification of the 478 module. It should contain printable ASCII characters." 479 ::= { fcFeModuleEntry 2 } 481 fcFeModuleObjectID OBJECT-TYPE 482 SYNTAX OBJECT IDENTIFIER 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The vendor's authoritative identification of the module. 487 This value may be allocated within the SMI enterprises 488 subtree (1.3.6.1.4.1) and provides a straight-forward and 489 unambiguous means for determining what kind of module is 490 being managed. 492 For example, this object could take the value 493 1.3.6.1.4.1.99649.3.9 if vendor 'Neufe Inc.' was assigned 494 the subtree 1.3.6.1.4.1.99649, and had assigned the 495 identifier 1.3.6.1.4.1.99649.3.9 to its 'FeFiFo-16 496 PlugInCard.'" 497 ::= { fcFeModuleEntry 3 } 499 fcFeModuleOperStatus OBJECT-TYPE 500 SYNTAX INTEGER { 501 online (1), -- functional 502 offline (2), -- not available 503 testing (3), -- under testing 504 faulty (4) -- defective 505 } 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "This object indicates the operational status of the module: 510 online(1) the module is functioning properly; 511 offline(2) the module is not available; 512 testing(3) the module is under testing; and 513 faulty(4) the module is defective in some way." 514 ::= { fcFeModuleEntry 4 } 516 fcFeModuleLastChange OBJECT-TYPE 517 SYNTAX TimeStamp 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "This object contains the value of sysUpTime when the module 522 entered its current operational status. A value of zero 523 indicates that the operational status of the module has not 524 changed since the agent last restarted." 525 ::= { fcFeModuleEntry 5 } 527 fcFeModuleFxPortCapacity OBJECT-TYPE 528 SYNTAX FcFeFxPortCapacity 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The number of FxPort that can be contained within the 533 module. Within each module, the ports are uniquely numbered 534 in the range from 1 to fcFeModuleFxPortCapacity inclusive. 535 However, the numbers are not required to be contiguous." 536 ::= { fcFeModuleEntry 6 } 538 fcFeModuleName OBJECT-TYPE 539 SYNTAX FcNameId 540 MAX-ACCESS read-write 541 STATUS current 542 DESCRIPTION 543 "The Name_Identifier of the module." 544 ::= { fcFeModuleEntry 7 } 546 -- the FxPort Configuration Table. 547 -- This table contains, one entry for each FxPort, 548 -- configuration parameters of the ports. 550 fcFxPortTable OBJECT-TYPE 551 SYNTAX SEQUENCE OF FcFxPortEntry 552 MAX-ACCESS not-accessible 553 STATUS current 554 DESCRIPTION 555 "A table that contains, one entry for each FxPort in the 556 Fabric Element, configuration and service parameters of the 557 FxPorts." 558 ::= { fcFeConfig 5 } 560 fcFxPortEntry OBJECT-TYPE 561 SYNTAX FcFxPortEntry 562 MAX-ACCESS not-accessible 563 STATUS current 564 DESCRIPTION 565 "An entry containing the configuration and service parameters 566 of a FxPort." 567 INDEX { fcFxPortModuleIndex, fcFxPortIndex } 568 ::= { fcFxPortTable 1 } 570 FcFxPortEntry ::= 571 SEQUENCE { 572 fcFxPortModuleIndex 573 FcFeModuleIndex, 574 fcFxPortIndex 575 FcFeFxPortIndex, 576 fcFxPortName 577 FcNameId, 578 -- FxPort common service parameters 579 fcFxPortFcphVersionHigh 580 FcphVersion, 581 fcFxPortFcphVersionLow 582 FcphVersion, 583 fcFxPortBbCredit 584 FcBbCredit, 585 fcFxPortRxBufSize 586 FcRxDataFieldSize, 587 fcFxPortRatov 588 MilliSeconds, 589 fcFxPortEdtov 590 MilliSeconds, 591 -- FxPort class service parameters 592 fcFxPortCosSupported 593 FcCosCap, 594 fcFxPortIntermixSupported 595 TruthValue, 596 fcFxPortStackedConnMode 597 FcStackedConnMode, 598 fcFxPortClass2SeqDeliv 599 TruthValue, 600 fcFxPortClass3SeqDeliv 601 TruthValue, 602 -- other configuration parameters 603 fcFxPortHoldTime 604 MicroSeconds 605 } 607 fcFxPortModuleIndex OBJECT-TYPE 608 SYNTAX FcFeModuleIndex 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "This object identifies the module containing the FxPort for 613 which this entry contains information." 614 ::= { fcFxPortEntry 1 } 616 fcFxPortIndex OBJECT-TYPE 617 SYNTAX FcFeFxPortIndex 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "This object identifies the FxPort within the module. This 622 number ranges from 1 to the value of fcFeModulePortCapacity 623 for the associated module. The value remains constant for 624 the identified FxPort until the module is re-initialized." 625 ::= { fcFxPortEntry 2 } 627 fcFxPortName OBJECT-TYPE 628 SYNTAX FcNameId 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The World_wide Name of this FxPort. Each FxPort has a 633 unique Port World_wide Name within the Fabric." 634 ::= { fcFxPortEntry 3 } 636 -- FxPort common service parameters 637 fcFxPortFcphVersionHigh OBJECT-TYPE 638 SYNTAX FcphVersion 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "The highest or most recent version of FC-PH that the FxPort 643 is configured to support." 644 ::= { fcFxPortEntry 4 } 646 fcFxPortFcphVersionLow OBJECT-TYPE 647 SYNTAX FcphVersion 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "The lowest or earliest version of FC-PH that the FxPort is 652 configured to support." 653 ::= { fcFxPortEntry 5 } 655 fcFxPortBbCredit OBJECT-TYPE 656 SYNTAX FcBbCredit 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The total number of receive buffers available for holding 661 Class 1 connect-request, Class 2 or 3 frames from the 662 attached NxPort. It is for buffer-to-buffer flow control 663 in the direction from the attached NxPort (if applicable) 664 to FxPort." 665 ::= { fcFxPortEntry 6 } 667 fcFxPortRxBufSize OBJECT-TYPE 668 SYNTAX FcRxDataFieldSize 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "The largest Data_Field Size (in octets) for an FT_1 frame 673 that can be received by the FxPort." 674 ::= { fcFxPortEntry 7 } 676 fcFxPortRatov OBJECT-TYPE 677 SYNTAX MilliSeconds 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The Resource_Allocation_Timeout Value configured for the 682 FxPort. This is used as the timeout value for determining 683 when to reuse an NxPort resource such as a 684 Recovery_Qualifier. It represents E_D_TOV (see next 685 object) plus twice the maximum time that a frame may be 686 delayed within the Fabric and still be delivered." 687 ::= { fcFxPortEntry 8 } 689 fcFxPortEdtov OBJECT-TYPE 690 SYNTAX MilliSeconds 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The E_D_TOV value configured for the FxPort. The 695 Error_Detect_Timeout Value is used as the timeout value for 696 detecting an error condition." 697 ::= { fcFxPortEntry 9 } 699 -- FxPort class service parameters 701 fcFxPortCosSupported OBJECT-TYPE 702 SYNTAX FcCosCap 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "A value indicating the set of Classes of Service supported 707 by the FxPort." 708 ::= { fcFxPortEntry 10 } 710 fcFxPortIntermixSupported OBJECT-TYPE 711 SYNTAX TruthValue 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "A flag indicating whether or not the FxPort supports an 716 Intermixed Dedicated Connection." 717 ::= { fcFxPortEntry 11 } 719 fcFxPortStackedConnMode OBJECT-TYPE 720 SYNTAX FcStackedConnMode 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "A value indicating the mode of Stacked Connect supported by 725 the FxPort." 726 ::= { fcFxPortEntry 12 } 727 fcFxPortClass2SeqDeliv OBJECT-TYPE 728 SYNTAX TruthValue 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "A flag indicating whether or not Class 2 Sequential 733 Delivery is supported by the FxPort." 734 ::= { fcFxPortEntry 13 } 736 fcFxPortClass3SeqDeliv OBJECT-TYPE 737 SYNTAX TruthValue 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "A flag indicating whether or not Class 3 Sequential 742 Delivery is supported by the FxPort." 743 ::= { fcFxPortEntry 14 } 745 -- other FxPort parameters 747 fcFxPortHoldTime OBJECT-TYPE 748 SYNTAX MicroSeconds 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The maximum time (in microseconds) that the FxPort shall 753 hold a frame before discarding the frame if it is unable to 754 deliver the frame. The value 0 means that the FxPort does 755 not support this parameter." 756 ::= { fcFxPortEntry 15 } 758 -- the Operation group 760 -- This group consists of tables that contains operational 761 -- status and established service parameters for the Fabric 762 -- Element and the attached NxPorts. 763 -- Implementation of this group is mandatory. 765 -- The FxPort Operation table 766 -- This table contains, one entry for each FxPort, 767 -- the operational status and parameters of the FxPorts. 769 fcFxPortOperTable OBJECT-TYPE 770 SYNTAX SEQUENCE OF FcFxPortOperEntry 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION 774 "A table that contains, one entry for each FxPort in the 775 Fabric Element, operational status and parameters of the 776 FxPorts." 777 ::= { fcFeOp 1 } 779 fcFxPortOperEntry OBJECT-TYPE 780 SYNTAX FcFxPortOperEntry 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "An entry containing operational status and parameters of a 785 FxPort." 786 AUGMENTS { fcFxPortEntry } 787 ::= { fcFxPortOperTable 1 } 789 FcFxPortOperEntry ::= 790 SEQUENCE { 791 fcFxPortID 792 FcAddressId, 793 fcFxPortBbCreditAvailable 794 Gauge32, 795 fcFxPortOperMode 796 INTEGER, 797 fcFxPortAdminMode 798 INTEGER 799 } 801 fcFxPortID OBJECT-TYPE 802 SYNTAX FcAddressId 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "The address identifier by which this FxPort is identified 807 within the Fabric. The FxPort may assign its address 808 identifier to its attached NxPort(s) during Fabric Login." 809 ::= { fcFxPortOperEntry 1 } 810 fcFxPortBbCreditAvailable OBJECT-TYPE 811 SYNTAX Gauge32 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "The number of buffers currently available for receiving 816 frames from the attached port in the buffer-to-buffer flow 817 control. The value should be less than or equal to 818 fcFxPortBbCredit." 819 ::= { fcFxPortOperEntry 2 } 821 fcFxPortOperMode OBJECT-TYPE 822 SYNTAX INTEGER { unknown(1), fPort(2), flPort(3) } 823 MAX-ACCESS read-write 824 STATUS current 825 DESCRIPTION 826 "The current operational mode of the FxPort." 827 ::= { fcFxPortOperEntry 3 } 829 fcFxPortAdminMode OBJECT-TYPE 830 SYNTAX INTEGER { fPort(2), flPort(3) } 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "The desired operational mode of the FxPort." 835 ::= { fcFxPortOperEntry 4 } 837 -- the FxPort Physical Level table 838 -- This table contains, one entry for each FxPort in the 839 -- Fabric Element, the physical level status and parameters 840 -- of the FxPorts. 842 fcFxPortPhysTable OBJECT-TYPE 843 SYNTAX SEQUENCE OF FcFxPortPhysEntry 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "A table that contains, one entry for each FxPort in the 848 Fabric Element, physical level status and parameters of the 849 FxPorts." 850 ::= { fcFeOp 2 } 851 fcFxPortPhysEntry OBJECT-TYPE 852 SYNTAX FcFxPortPhysEntry 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "An entry containing physical level status and parameters of 857 a FxPort." 858 AUGMENTS { fcFxPortEntry } 859 ::= { fcFxPortPhysTable 1 } 861 FcFxPortPhysEntry ::= 862 SEQUENCE { 863 fcFxPortPhysAdminStatus 864 INTEGER, 865 fcFxPortPhysOperStatus 866 INTEGER, 867 fcFxPortPhysLastChange 868 TimeStamp, 869 fcFxPortPhysRttov 870 MilliSeconds 871 } 873 fcFxPortPhysAdminStatus OBJECT-TYPE 874 SYNTAX INTEGER { 875 online (1), -- place port online 876 offline (2), -- take port offline 877 testing (3) -- initiate test procedures 878 } 879 MAX-ACCESS read-write 880 STATUS current 881 DESCRIPTION 882 "The desired state of the FxPort. A management station may 883 place the FxPort in a desired state by setting this object 884 accordingly. The testing(3) state indicates that no 885 operational frames can be passed. When a Fabric Element 886 initializes, all FxPorts start with fcFxPortPhysAdminStatus 887 in the offline(2) state. As the result of either explicit 888 management action or per configuration information 889 accessible by the Fabric Element, fcFxPortPhysAdminStatus 890 is then changed to either the online(1) or testing(3) 891 states, or remains in the offline state." 892 ::= { fcFxPortPhysEntry 1 } 893 fcFxPortPhysOperStatus OBJECT-TYPE 894 SYNTAX INTEGER { 895 online (1), -- Login may proceed 896 offline (2), -- Login cannot proceed 897 testing (3), -- port is under test 898 linkFailure (4) -- failure after online/testing 899 } 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The current operational status of the FxPort. The 904 testing(3) indicates that no operational frames can be 905 passed. If fcFxPortPhysAdminStatus is offline(2) then 906 fcFxPortPhysOperStatus should be offline(2). If 907 fcFxPortPhysAdminStatus is changed to online(1) then 908 fcFxPortPhysOperStatus should change to online(1) if the 909 FxPort is ready to accept Fabric Login request from the 910 attached NxPort; it should proceed and remain in the link- 911 failure(4) state if and only if there is a fault that 912 prevents it from going to the online(1) state." 913 ::= { fcFxPortPhysEntry 2 } 915 fcFxPortPhysLastChange OBJECT-TYPE 916 SYNTAX TimeStamp 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The value of sysUpTime at the time the FxPort entered its 921 current operational status. A value of zero indicates that 922 the FxPort's operational status has not changed since the 923 agent last restarted." 924 ::= { fcFxPortPhysEntry 3 } 926 fcFxPortPhysRttov OBJECT-TYPE 927 SYNTAX MilliSeconds 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "The Receiver_Transmitter_Timeout value of the FxPort. This 932 is used by the receiver logic to detect Loss of 933 Synchronization." 934 ::= { fcFxPortPhysEntry 4 } 935 -- The FxPort Fabric Login table 936 -- 937 -- This table contains, one entry for each FxPort in the 938 -- Fabric Element, the Service Parameters that have been 939 -- established from the most recent Fabric Login, 940 -- implicit or explicit. 942 fcFxlogiTable OBJECT-TYPE 943 SYNTAX SEQUENCE OF FcFxlogiEntry 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "A table that contains, one entry for each FxPort in the 948 Fabric Element, services parameters established from the 949 most recent Fabric Login, explicit or implicit." 950 ::= { fcFeOp 4 } 952 fcFxlogiEntry OBJECT-TYPE 953 SYNTAX FcFxlogiEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "An entry containing service parameters established from a 958 successful Fabric Login." 959 INDEX { fcFxPortModuleIndex, fcFxPortIndex, fcFxlogiNxPortIndex 960 } 961 ::= { fcFxlogiTable 1 } 963 FcFxlogiEntry ::= 964 SEQUENCE { 965 fcFxlogiNxPortIndex 966 FcFeNxPortIndex, 967 fcFxPortFcphVersionAgreed 968 FcphVersion, 969 fcFxPortNxPortBbCredit 970 FcBbCredit, 971 fcFxPortNxPortRxDataFieldSize 972 FcRxDataFieldSize, 973 fcFxPortCosSuppAgreed 974 FcCosCap, 975 fcFxPortIntermixSuppAgreed 976 TruthValue, 977 fcFxPortStackedConnModeAgreed 978 FcStackedConnMode, 979 fcFxPortClass2SeqDelivAgreed 980 TruthValue, 981 fcFxPortClass3SeqDelivAgreed 982 TruthValue, 983 -- 984 fcFxPortNxPortName 985 FcNameId, 986 fcFxPortConnectedNxPort 987 FcAddressId, 988 fcFxPortBbCreditModel 989 FcBbCreditModel 990 } 992 fcFxlogiNxPortIndex OBJECT-TYPE 993 SYNTAX FcFeNxPortIndex 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "The object identifies the associated NxPort in the 998 attachment for which the entry contains information." 999 ::= { fcFxlogiEntry 1 } 1001 fcFxPortFcphVersionAgreed OBJECT-TYPE 1002 SYNTAX FcphVersion 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "The version of FC-PH that the FxPort has agreed to support 1007 from the Fabric Login" 1008 ::= { fcFxlogiEntry 2 } 1010 fcFxPortNxPortBbCredit OBJECT-TYPE 1011 SYNTAX FcBbCredit 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The total number of buffers available for holding Class 1 1016 connect-request, Class 2 or Class 3 frames to be 1017 transmitted to the attached NxPort. It is for buffer-to- 1018 buffer flow control in the direction from FxPort to NxPort. 1019 The buffer-to-buffer flow control mechanism is indicated in 1020 the respective fcFxPortBbCreditModel." 1021 ::= { fcFxlogiEntry 3 } 1022 fcFxPortNxPortRxDataFieldSize OBJECT-TYPE 1023 SYNTAX FcRxDataFieldSize 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "The Receive Data Field Size of the attached NxPort. This is 1028 a binary value that specifies the largest Data Field Size 1029 for an FT_1 frame that can be received by the NxPort." 1030 ::= { fcFxlogiEntry 4 } 1032 fcFxPortCosSuppAgreed OBJECT-TYPE 1033 SYNTAX FcCosCap 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "A variable indicating that the attached NxPort has 1038 requested the FxPort for the support of classes of services 1039 and the FxPort has granted the request." 1040 ::= { fcFxlogiEntry 5 } 1042 fcFxPortIntermixSuppAgreed OBJECT-TYPE 1043 SYNTAX TruthValue 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "A variable indicating that the attached NxPort has 1048 requested the FxPort for the support of Intermix and the 1049 FxPort has granted the request. This flag is only valid if 1050 Class 1 service is supported." 1051 ::= { fcFxlogiEntry 6 } 1053 fcFxPortStackedConnModeAgreed OBJECT-TYPE 1054 SYNTAX FcStackedConnMode 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "A variable indicating whether the FxPort has agreed to 1059 support stacked connect from the Fabric Login. This is only 1060 meaningful if Class 1 service has been agreed." 1061 ::= { fcFxlogiEntry 7 } 1062 fcFxPortClass2SeqDelivAgreed OBJECT-TYPE 1063 SYNTAX TruthValue 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "A variable indicating whether the FxPort has agreed to 1068 support Class 2 sequential delivery from the Fabric Login. 1069 This is only meaningful if Class 2 service has been 1070 agreed." 1071 ::= { fcFxlogiEntry 8 } 1073 fcFxPortClass3SeqDelivAgreed OBJECT-TYPE 1074 SYNTAX TruthValue 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "A flag indicating whether the FxPort has agreed to support 1079 Class 3 sequential delivery from the Fabric Login. This is 1080 only meaningful if Class 3 service has been agreed." 1081 ::= { fcFxlogiEntry 9 } 1083 fcFxPortNxPortName OBJECT-TYPE 1084 SYNTAX FcNameId 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The port name of the attached NxPort." 1089 ::= { fcFxlogiEntry 10 } 1091 fcFxPortConnectedNxPort OBJECT-TYPE 1092 SYNTAX FcAddressId 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "The address identifier of the destination NxPort with which 1097 this FxPort is currently engaged in a either a Class 1 or 1098 loop connection. If this FxPort is not engaged in a 1099 connection, then the value of this object is '000000'H." 1100 ::= { fcFxlogiEntry 11 } 1102 fcFxPortBbCreditModel OBJECT-TYPE 1103 SYNTAX FcBbCreditModel 1104 MAX-ACCESS read-write 1105 STATUS current 1106 DESCRIPTION 1107 "This object identifies the BB_Credit model used by the 1108 FxPort." 1109 ::= { fcFxlogiEntry 12 } 1111 -- the Error group 1112 -- This group consists of tables that contain information about 1113 -- the various types of errors detected. The management station 1114 -- may use the information in this group to determine the 1115 -- quality of the link between the FxPort and its attached NxPort. 1116 -- Implementation of this group is optional. 1118 -- the FxPort Error table 1119 -- This table contains, one entry for each FxPort in the Fabric 1120 -- Element, counters recording numbers of errors detected 1121 -- since the management agent re-initialized. 1122 -- The first 6 columnar objects after the port index corresponds 1123 -- to the counters in the Link Error Status Block. 1125 fcFxPortErrorTable OBJECT-TYPE 1126 SYNTAX SEQUENCE OF FcFxPortErrorEntry 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "A table that contains, one entry for each FxPort, counters 1131 that record the numbers of errors detected." 1132 ::= { fcFeError 1 } 1134 fcFxPortErrorEntry OBJECT-TYPE 1135 SYNTAX FcFxPortErrorEntry 1136 MAX-ACCESS not-accessible 1137 STATUS current 1138 DESCRIPTION 1139 "An entry containing error counters of a FxPort." 1140 AUGMENTS { fcFxPortEntry } 1141 ::= { fcFxPortErrorTable 1 } 1143 FcFxPortErrorEntry ::= 1144 SEQUENCE { 1145 fcFxPortLinkFailures 1146 Counter32, 1147 fcFxPortSyncLosses 1148 Counter32, 1149 fcFxPortSigLosses 1150 Counter32, 1151 fcFxPortPrimSeqProtoErrors 1152 Counter32, 1153 fcFxPortInvalidTxWords 1154 Counter32, 1155 fcFxPortInvalidCrcs 1156 Counter32, 1157 fcFxPortDelimiterErrors 1158 Counter32, 1159 fcFxPortAddressIdErrors 1160 Counter32, 1161 fcFxPortLinkResetIns 1162 Counter32, 1163 fcFxPortLinkResetOuts 1164 Counter32, 1165 fcFxPortOlsIns 1166 Counter32, 1167 fcFxPortOlsOuts 1168 Counter32 1169 } 1171 fcFxPortLinkFailures OBJECT-TYPE 1172 SYNTAX Counter32 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "The number of link failures detected by this FxPort." 1177 ::= { fcFxPortErrorEntry 1 } 1179 fcFxPortSyncLosses OBJECT-TYPE 1180 SYNTAX Counter32 1181 MAX-ACCESS read-only 1182 STATUS current 1183 DESCRIPTION 1184 "The number of loss of synchronization detected by the 1185 FxPort." 1186 ::= { fcFxPortErrorEntry 2 } 1188 fcFxPortSigLosses OBJECT-TYPE 1189 SYNTAX Counter32 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "The number of loss of signal detected by the FxPort." 1194 ::= { fcFxPortErrorEntry 3 } 1195 fcFxPortPrimSeqProtoErrors OBJECT-TYPE 1196 SYNTAX Counter32 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "The number of primitive sequence protocol errors detected 1201 by the FxPort." 1202 ::= { fcFxPortErrorEntry 4 } 1204 fcFxPortInvalidTxWords OBJECT-TYPE 1205 SYNTAX Counter32 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "The number of invalid transmission word detected by the 1210 FxPort." 1211 ::= { fcFxPortErrorEntry 5 } 1213 fcFxPortInvalidCrcs OBJECT-TYPE 1214 SYNTAX Counter32 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "The number of invalid CRC detected by this FxPort." 1219 ::= { fcFxPortErrorEntry 6 } 1221 fcFxPortDelimiterErrors OBJECT-TYPE 1222 SYNTAX Counter32 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "The number of Delimiter Errors detected by this FxPort." 1227 ::= { fcFxPortErrorEntry 7 } 1229 fcFxPortAddressIdErrors OBJECT-TYPE 1230 SYNTAX Counter32 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "The number of address identifier errors detected by this 1235 FxPort." 1236 ::= { fcFxPortErrorEntry 8 } 1237 fcFxPortLinkResetIns OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "The number of Link Reset Protocol received by this FxPort 1243 from the attached NxPort." 1244 ::= { fcFxPortErrorEntry 9 } 1246 fcFxPortLinkResetOuts OBJECT-TYPE 1247 SYNTAX Counter32 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "The number of Link Reset Protocol issued by this FxPort to 1252 the attached NxPort." 1253 ::= { fcFxPortErrorEntry 10 } 1255 fcFxPortOlsIns OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "The number of Offline Sequence received by this FxPort." 1261 ::= { fcFxPortErrorEntry 11 } 1263 fcFxPortOlsOuts OBJECT-TYPE 1264 SYNTAX Counter32 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "The number of Offline Sequence issued by this FxPort." 1269 ::= { fcFxPortErrorEntry 12 } 1271 -- Accounting Groups: 1272 -- (1) Class 1 Accounting Group, 1273 -- (2) Class 2 Accounting Group, and 1274 -- (3) Class 3 Accounting Group. 1275 -- Each group consists of a table that contains accounting 1276 -- information for the FxPorts in the Fabric Element. 1277 -- Implementation of each group is optional. 1279 -- the Class 1 Accounting table 1280 -- This table contains, one entry for each FxPort in the Fabric 1281 -- Element, Counter32s for certain types of events occurred in the 1282 -- the FxPorts since the the management agent has re-initialized. 1283 -- Implementation of this group is optional. 1285 fcFxPortC1AcctTable OBJECT-TYPE 1286 SYNTAX SEQUENCE OF FcFxPortC1AcctEntry 1287 MAX-ACCESS not-accessible 1288 STATUS current 1289 DESCRIPTION 1290 "A table that contains, one entry for each FxPort in the 1291 Fabric Element, Class 1 accounting information recorded 1292 since the management agent has re-initialized." 1293 ::= { fcFeAcct 1 } 1295 fcFxPortC1AcctEntry OBJECT-TYPE 1296 SYNTAX FcFxPortC1AcctEntry 1297 MAX-ACCESS not-accessible 1298 STATUS current 1299 DESCRIPTION 1300 "An entry containing Class 1 accounting information for each 1301 FxPort." 1302 AUGMENTS { fcFxPortEntry } 1303 ::= { fcFxPortC1AcctTable 1 } 1305 FcFxPortC1AcctEntry ::= 1306 SEQUENCE { 1307 fcFxPortC1InFrames 1308 Counter32, 1309 fcFxPortC1OutFrames 1310 Counter32, 1311 fcFxPortC1InOctets 1312 Counter32, 1313 fcFxPortC1OutOctets 1314 Counter32, 1315 fcFxPortC1Discards 1316 Counter32, 1317 fcFxPortC1FbsyFrames 1318 Counter32, 1319 fcFxPortC1FrjtFrames 1320 Counter32, 1321 fcFxPortC1InConnections 1322 Counter32, 1323 fcFxPortC1OutConnections 1324 Counter32, 1325 fcFxPortC1ConnTime 1326 Counter32 1327 } 1329 fcFxPortC1InFrames OBJECT-TYPE 1330 SYNTAX Counter32 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "The number of Class 1 frames (other than Class 1 connect- 1335 request) received by this FxPort from its attached NxPort." 1336 ::= { fcFxPortC1AcctEntry 1 } 1338 fcFxPortC1OutFrames OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "The number of Class 1 frames (other than Class 1 connect- 1344 request) delivered through this FxPort to its attached 1345 NxPort." 1346 ::= { fcFxPortC1AcctEntry 2 } 1348 fcFxPortC1InOctets OBJECT-TYPE 1349 SYNTAX Counter32 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The number of Class 1 frame octets, including the frame 1354 delimiters, received by this FxPort from its attached 1355 NxPort." 1356 ::= { fcFxPortC1AcctEntry 3 } 1358 fcFxPortC1OutOctets OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The number of Class 1 frame octets, including the frame 1364 delimiters, delivered through this FxPort its attached 1365 NxPort." 1366 ::= { fcFxPortC1AcctEntry 4 } 1367 fcFxPortC1Discards OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "The number of Class 1 frames discarded by this FxPort." 1373 ::= { fcFxPortC1AcctEntry 5 } 1375 fcFxPortC1FbsyFrames OBJECT-TYPE 1376 SYNTAX Counter32 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "The number of F_BSY frames generated by this FxPort against 1381 Class 1 connect-request." 1382 ::= { fcFxPortC1AcctEntry 6 } 1384 fcFxPortC1FrjtFrames OBJECT-TYPE 1385 SYNTAX Counter32 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "The number of F_RJT frames generated by this FxPort against 1390 Class 1 connect-request." 1391 ::= { fcFxPortC1AcctEntry 7 } 1393 fcFxPortC1InConnections OBJECT-TYPE 1394 SYNTAX Counter32 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "The number of Class 1 connections successfully established 1399 in which the attached NxPort is the source of the connect- 1400 request." 1401 ::= { fcFxPortC1AcctEntry 8 } 1403 fcFxPortC1OutConnections OBJECT-TYPE 1404 SYNTAX Counter32 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "The number of Class 1 connections successfully established 1409 in which the attached NxPort is the destination of the 1410 connect-request." 1411 ::= { fcFxPortC1AcctEntry 9 } 1412 fcFxPortC1ConnTime OBJECT-TYPE 1413 SYNTAX Counter32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "The cumulative time that this FxPort has been engaged in 1418 Class 1 connection. The amount of time of each connection 1419 is counted in octets from after a connect-request has been 1420 accepted until the connection is disengaged, either by an 1421 EOFdt or Link Reset." 1422 ::= { fcFxPortC1AcctEntry 10 } 1424 -- the Class 2 Accounting table 1425 -- This table contains, one entry for each FxPort in the Fabric 1426 -- Element, Counter32s for certain types of events occurred in the 1427 -- the FxPorts since the the management agent has re-initialized. 1428 -- Implementation of this group is optional. 1430 fcFxPortC2AcctTable OBJECT-TYPE 1431 SYNTAX SEQUENCE OF FcFxPortC2AcctEntry 1432 MAX-ACCESS not-accessible 1433 STATUS current 1434 DESCRIPTION 1435 "A table that contains, one entry for each FxPort in the 1436 Fabric Element, Class 2 accounting information recorded 1437 since the management agent has re-initialized." 1438 ::= { fcFeAcct 2 } 1440 fcFxPortC2AcctEntry OBJECT-TYPE 1441 SYNTAX FcFxPortC2AcctEntry 1442 MAX-ACCESS not-accessible 1443 STATUS current 1444 DESCRIPTION 1445 "An entry containing Class 2 accounting information for each 1446 FxPort." 1447 AUGMENTS { fcFxPortEntry } 1448 ::= { fcFxPortC2AcctTable 1 } 1450 FcFxPortC2AcctEntry ::= 1451 SEQUENCE { 1452 fcFxPortC2InFrames 1453 Counter32, 1454 fcFxPortC2OutFrames 1455 Counter32, 1456 fcFxPortC2InOctets 1457 Counter32, 1458 fcFxPortC2OutOctets 1459 Counter32, 1460 fcFxPortC2Discards 1461 Counter32, 1462 fcFxPortC2FbsyFrames 1463 Counter32, 1464 fcFxPortC2FrjtFrames 1465 Counter32 1466 } 1468 fcFxPortC2InFrames OBJECT-TYPE 1469 SYNTAX Counter32 1470 MAX-ACCESS read-only 1471 STATUS current 1472 DESCRIPTION 1473 "The number of Class 2 frames received by this FxPort from 1474 its attached NxPort." 1475 ::= { fcFxPortC2AcctEntry 1 } 1477 fcFxPortC2OutFrames OBJECT-TYPE 1478 SYNTAX Counter32 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "The number of Class 2 frames delivered through this FxPort 1483 to its attached NxPort." 1484 ::= { fcFxPortC2AcctEntry 2 } 1486 fcFxPortC2InOctets OBJECT-TYPE 1487 SYNTAX Counter32 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The number of Class 2 frame octets, including the frame 1492 delimiters, received by this FxPort from its attached 1493 NxPort." 1494 ::= { fcFxPortC2AcctEntry 3 } 1496 fcFxPortC2OutOctets OBJECT-TYPE 1497 SYNTAX Counter32 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The number of Class 2 frame octets, including the frame 1502 delimiters, delivered through this FxPort to its attached 1503 NxPort." 1504 ::= { fcFxPortC2AcctEntry 4 } 1506 fcFxPortC2Discards OBJECT-TYPE 1507 SYNTAX Counter32 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "The number of Class 2 frames discarded by this FxPort." 1512 ::= { fcFxPortC2AcctEntry 5 } 1514 fcFxPortC2FbsyFrames OBJECT-TYPE 1515 SYNTAX Counter32 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The number of F_BSY frames generated by this FxPort against 1520 Class 2 frames." 1521 ::= { fcFxPortC2AcctEntry 6 } 1523 fcFxPortC2FrjtFrames OBJECT-TYPE 1524 SYNTAX Counter32 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The number of F_RJT frames generated by this FxPort against 1529 Class 2 frames." 1530 ::= { fcFxPortC2AcctEntry 7 } 1532 -- the Class 3 Accounting Group 1533 -- This table contains, one entry for each FxPort in the Fabric 1534 -- Element, Counter32s for certain types of events occurred in the 1535 -- the FxPorts since the management agent has re-initialized. 1536 -- Implementation of this group is optional. 1538 fcFxPortC3AcctTable OBJECT-TYPE 1539 SYNTAX SEQUENCE OF FcFxPortC3AcctEntry 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "A table that contains, one entry for each FxPort in the 1544 Fabric Element, Class 3 accounting information recorded 1545 since the management agent has re-initialized." 1546 ::= { fcFeAcct 3 } 1547 fcFxPortC3AcctEntry OBJECT-TYPE 1548 SYNTAX FcFxPortC3AcctEntry 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "An entry containing Class 3 accounting information for each 1553 FxPort." 1554 AUGMENTS { fcFxPortEntry } 1555 ::= { fcFxPortC3AcctTable 1 } 1557 FcFxPortC3AcctEntry ::= 1558 SEQUENCE { 1559 fcFxPortC3InFrames 1560 Counter32, 1561 fcFxPortC3OutFrames 1562 Counter32, 1563 fcFxPortC3InOctets 1564 Counter32, 1565 fcFxPortC3OutOctets 1566 Counter32, 1567 fcFxPortC3Discards 1568 Counter32 1569 } 1571 fcFxPortC3InFrames OBJECT-TYPE 1572 SYNTAX Counter32 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "The number of Class 3 frames received by this FxPort from 1577 its attached NxPort." 1578 ::= { fcFxPortC3AcctEntry 1 } 1580 fcFxPortC3OutFrames OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "The number of Class 3 frames delivered through this FxPort 1586 to its attached NxPort." 1587 ::= { fcFxPortC3AcctEntry 2 } 1588 fcFxPortC3InOctets OBJECT-TYPE 1589 SYNTAX Counter32 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "The number of Class 3 frame octets, including the frame 1594 delimiters, received by this FxPort from its attached 1595 NxPort." 1596 ::= { fcFxPortC3AcctEntry 3 } 1598 fcFxPortC3OutOctets OBJECT-TYPE 1599 SYNTAX Counter32 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "The number of Class 3 frame octets, including the frame 1604 delimiters, delivered through this FxPort to its attached 1605 NxPort." 1606 ::= { fcFxPortC3AcctEntry 4 } 1608 fcFxPortC3Discards OBJECT-TYPE 1609 SYNTAX Counter32 1610 MAX-ACCESS read-only 1611 STATUS current 1612 DESCRIPTION 1613 "The number of Class 3 frames discarded by this FxPort." 1614 ::= { fcFxPortC3AcctEntry 5 } 1616 -- The Capability Group - consists of a table describing 1617 -- information about what each FxPort is inherently capable 1618 -- of operating or supporting. 1619 -- A capability may be used, as expressed in its respective 1620 -- object value in the Configuration group. 1621 -- Implementation of this group is optional. 1623 fcFxPortCapTable OBJECT-TYPE 1624 SYNTAX SEQUENCE OF FcFxPortCapEntry 1625 MAX-ACCESS not-accessible 1626 STATUS current 1627 DESCRIPTION 1628 "A table that contains, one entry for each FxPort, the 1629 capabilities of the port within the Fabric Element." 1630 ::= { fcFeCap 1 } 1631 fcFxPortCapEntry OBJECT-TYPE 1632 SYNTAX FcFxPortCapEntry 1633 MAX-ACCESS not-accessible 1634 STATUS current 1635 DESCRIPTION 1636 "An entry containing the capabilities of a FxPort." 1637 AUGMENTS { fcFxPortEntry } 1638 ::= { fcFxPortCapTable 1 } 1640 FcFxPortCapEntry ::= 1641 SEQUENCE { 1642 fcFxPortCapFcphVersionHigh 1643 FcphVersion, 1644 fcFxPortCapFcphVersionLow 1645 FcphVersion, 1646 fcFxPortCapBbCreditMax 1647 FcBbCredit, 1648 fcFxPortCapBbCreditMin 1649 FcBbCredit, 1650 fcFxPortCapRxDataFieldSizeMax 1651 FcRxDataFieldSize, 1652 fcFxPortCapRxDataFieldSizeMin 1653 FcRxDataFieldSize, 1654 fcFxPortCapCos 1655 FcCosCap, 1656 fcFxPortCapIntermix 1657 TruthValue, 1658 fcFxPortCapStackedConnMode 1659 FcStackedConnMode, 1660 fcFxPortCapClass2SeqDeliv 1661 TruthValue, 1662 fcFxPortCapClass3SeqDeliv 1663 TruthValue, 1664 fcFxPortCapHoldTimeMax 1665 MicroSeconds, 1666 fcFxPortCapHoldTimeMin 1667 MicroSeconds 1668 } 1670 fcFxPortCapFcphVersionHigh OBJECT-TYPE 1671 SYNTAX FcphVersion 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "The highest or most recent version of FC-PH that the FxPort 1676 is capable of supporting." 1677 ::= { fcFxPortCapEntry 1 } 1679 fcFxPortCapFcphVersionLow OBJECT-TYPE 1680 SYNTAX FcphVersion 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "The lowest or earliest version of FC-PH that the FxPort is 1685 capable of supporting." 1686 ::= { fcFxPortCapEntry 2 } 1688 fcFxPortCapBbCreditMax OBJECT-TYPE 1689 SYNTAX FcBbCredit 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "The maximum number of receive buffers available for holding 1694 Class 1 connect-request, Class 2 or Class 3 frames from the 1695 attached NxPort." 1696 ::= { fcFxPortCapEntry 3 } 1698 fcFxPortCapBbCreditMin OBJECT-TYPE 1699 SYNTAX FcBbCredit 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "The minimum number of receive buffers available for holding 1704 Class 1 connect-request, Class 2 or Class 3 frames from the 1705 attached NxPort." 1706 ::= { fcFxPortCapEntry 4 } 1708 fcFxPortCapRxDataFieldSizeMax OBJECT-TYPE 1709 SYNTAX FcRxDataFieldSize 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The maximum size in bytes of the Data Field in a frame that 1714 the FxPort is capable of receiving from its attached 1715 NxPort." 1716 ::= { fcFxPortCapEntry 5 } 1717 fcFxPortCapRxDataFieldSizeMin OBJECT-TYPE 1718 SYNTAX FcRxDataFieldSize 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "The minimum size in bytes of the Data Field in a frame that 1723 the FxPort is capable of receiving from its attached 1724 NxPort." 1725 ::= { fcFxPortCapEntry 6 } 1727 fcFxPortCapCos OBJECT-TYPE 1728 SYNTAX FcCosCap 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "A value indicating the set of Classes of Service that the 1733 FxPort is capable of supporting." 1734 ::= { fcFxPortCapEntry 7 } 1736 fcFxPortCapIntermix OBJECT-TYPE 1737 SYNTAX TruthValue 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "A flag indicating whether or not the FxPort is capable of 1742 supporting the intermixing of Class 2 and Class 3 frames 1743 during a Class 1 connection. This flag is only valid if the 1744 port is capable of supporting Class 1 service." 1745 ::= { fcFxPortCapEntry 8 } 1747 fcFxPortCapStackedConnMode OBJECT-TYPE 1748 SYNTAX FcStackedConnMode 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "A value indicating the mode of Stacked Connect request that 1753 the FxPort is capable of supporting." 1754 ::= { fcFxPortCapEntry 9 } 1756 fcFxPortCapClass2SeqDeliv OBJECT-TYPE 1757 SYNTAX TruthValue 1758 MAX-ACCESS read-only 1759 STATUS current 1760 DESCRIPTION 1761 "A flag indicating whether or not the FxPort is capable of 1762 supporting Class 2 Sequential Delivery." 1764 ::= { fcFxPortCapEntry 10 } 1766 fcFxPortCapClass3SeqDeliv OBJECT-TYPE 1767 SYNTAX TruthValue 1768 MAX-ACCESS read-only 1769 STATUS current 1770 DESCRIPTION 1771 "A flag indicating whether or not the FxPort is capable of 1772 supporting Class 3 Sequential Delivery." 1773 ::= { fcFxPortCapEntry 11 } 1775 fcFxPortCapHoldTimeMax OBJECT-TYPE 1776 SYNTAX MicroSeconds 1777 MAX-ACCESS read-only 1778 STATUS current 1779 DESCRIPTION 1780 "The maximum holding time (in microseconds) that the FxPort 1781 is capable of supporting." 1782 ::= { fcFxPortCapEntry 12 } 1784 fcFxPortCapHoldTimeMin OBJECT-TYPE 1785 SYNTAX MicroSeconds 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "The minimum holding time (in microseconds) that the FxPort 1790 is capable of supporting." 1791 ::= { fcFxPortCapEntry 13 } 1793 -- conformance information 1795 fcFeMIBComformance OBJECT IDENTIFIER ::= { fcFe 2 } 1796 fcFeMIBCompliances OBJECT IDENTIFIER ::= { fcFeMIBComformance 1 } 1797 fcFeMIBGroups OBJECT IDENTIFIER ::= { fcFeMIBComformance 2 } 1799 -- compliance statements 1800 fcFeMIBCompliance MODULE-COMPLIANCE 1801 STATUS current 1802 DESCRIPTION "The compliance statement for SNMPv2 entities 1803 which implement the fcFe MIB." 1804 MODULE -- this module 1805 MANDATORY-GROUPS { fcFeConfigGroup, fcFeOpGroup } 1806 ::= { fcFeMIBCompliances 1 } 1807 -- units of conformance 1808 fcFeConfigGroup OBJECT-GROUP 1809 OBJECTS { fcFabricName, fcElementName, fcFeModuleCapacity, 1810 fcFeModuleDescr, fcFeModuleObjectID, 1811 fcFeModuleOperStatus, fcFeModuleLastChange, 1812 fcFeModuleFxPortCapacity, fcFeModuleName, 1813 fcFxPortName, fcFxPortFcphVersionHigh, 1814 fcFxPortFcphVersionLow, fcFxPortBbCredit, 1815 fcFxPortRxBufSize, fcFxPortRatov, fcFxPortEdtov, 1816 fcFxPortCosSupported, fcFxPortIntermixSupported, 1817 fcFxPortStackedConnMode, fcFxPortClass2SeqDeliv, 1818 fcFxPortClass3SeqDeliv, fcFxPortHoldTime } 1819 STATUS current 1820 DESCRIPTION 1821 "A collection of objects providing the configuration 1822 and service parameters of the Fabric Element, the 1823 modules, and FxPorts." 1824 ::= { fcFeMIBGroups 1 } 1826 fcFeOpGroup OBJECT-GROUP 1827 OBJECTS { fcFxPortID, fcFxPortBbCreditAvailable, 1828 fcFxPortOperMode, fcFxPortAdminMode, 1829 fcFxPortPhysAdminStatus, fcFxPortPhysOperStatus, 1830 fcFxPortPhysLastChange, fcFxPortPhysRttov, 1831 fcFxPortFcphVersionAgreed, fcFxPortNxPortBbCredit, 1832 fcFxPortNxPortRxDataFieldSize, fcFxPortCosSuppAgreed, 1833 fcFxPortIntermixSuppAgreed, 1834 fcFxPortStackedConnModeAgreed, 1835 fcFxPortClass2SeqDelivAgreed, 1836 fcFxPortClass3SeqDelivAgreed, 1837 fcFxPortNxPortName, fcFxPortConnectedNxPort, 1838 fcFxPortBbCreditModel } 1839 STATUS current 1840 DESCRIPTION 1841 "A collection of objects providing the operational 1842 status and established service parameters for the 1843 Fabric Element and the attached NxPorts." 1844 ::= { fcFeMIBGroups 2 } 1846 fcFeErrorGroup OBJECT-GROUP 1847 OBJECTS { fcFxPortLinkFailures, fcFxPortSyncLosses, 1848 fcFxPortSigLosses, fcFxPortPrimSeqProtoErrors, 1849 fcFxPortInvalidTxWords, fcFxPortInvalidCrcs, 1850 fcFxPortDelimiterErrors, fcFxPortAddressIdErrors, 1851 fcFxPortLinkResetIns, fcFxPortLinkResetOuts, 1852 fcFxPortOlsIns, fcFxPortOlsOuts } 1853 STATUS current 1854 DESCRIPTION 1855 "A collection of objects providing various error 1856 statistics detected by the FxPorts." 1857 ::= { fcFeMIBGroups 3 } 1859 fcFeAcctGroup OBJECT-GROUP 1860 OBJECTS { -- Class 1 1861 fcFxPortC1InFrames, fcFxPortC1OutFrames, 1862 fcFxPortC1InOctets, fcFxPortC1OutOctets, 1863 fcFxPortC1Discards, fcFxPortC1FbsyFrames, 1864 fcFxPortC1FrjtFrames, fcFxPortC1InConnections, 1865 fcFxPortC1OutConnections, fcFxPortC1ConnTime, 1867 -- Class 2 1868 fcFxPortC2InFrames, fcFxPortC2OutFrames, 1869 fcFxPortC2InOctets, fcFxPortC2OutOctets, 1870 fcFxPortC2Discards, fcFxPortC2FbsyFrames, 1871 fcFxPortC2FrjtFrames, 1873 -- Class 3 1874 fcFxPortC3InFrames, fcFxPortC3OutFrames, 1875 fcFxPortC3InOctets, fcFxPortC3OutOctets, 1876 fcFxPortC3Discards 1877 } 1878 STATUS current 1879 DESCRIPTION 1880 "A collection of objects providing various performance 1881 statistics detected by the FxPorts." 1882 ::= { fcFeMIBGroups 4 } 1884 fcFeCapGroup OBJECT-GROUP 1885 OBJECTS { fcFxPortCapFcphVersionHigh, fcFxPortCapFcphVersionLow, 1886 fcFxPortCapBbCreditMax, fcFxPortCapBbCreditMin, 1887 fcFxPortCapRxDataFieldSizeMax, 1888 fcFxPortCapRxDataFieldSizeMin, 1889 fcFxPortCapCos, fcFxPortCapIntermix, 1890 fcFxPortCapStackedConnMode, fcFxPortCapClass2SeqDeliv, 1891 fcFxPortCapClass3SeqDeliv, fcFxPortCapHoldTimeMax, 1892 fcFxPortCapHoldTimeMin 1893 } 1894 STATUS current 1895 DESCRIPTION 1896 "A collection of objects providing the inherent 1897 capability of each FxPort within the Fabric Element." 1898 ::= { fcFeMIBGroups 5 } 1900 END 1901 -- End of Object Definitions 1903 4. Security Considerations 1905 There are a number of management objects defined in this MIB that 1906 have a MAX-ACCESS clause of read-write. Such objects may be 1907 considered sensitive or vulnerable in some network environments. The 1908 support for SET operations in a non-secure environment without proper 1909 protection can have a negative effect on network operations. 1911 5. Intellectual Property 1913 The IETF takes no position regarding the validity or scope of any 1914 intellectual property or other rights that might be claimed to 1915 pertain to the implementation or use of the technology described in 1916 this document or the extent to which any license under such rights 1917 might or might not be available; neither does it represent that it 1918 has made any effort to identify any such rights. Information on the 1919 IETF's procedures with respect to rights in standards-track and 1920 standards-related documentation can be found in BCP-11. Copies of 1921 claims of rights made available for publication and any assurances of 1922 licenses to be made available, or the result of an attempt made to 1923 obtain a general license or permission for the use of such 1924 proprietary rights by implementors or users of this specification can 1925 be obtained from the IETF Secretariat. 1927 The IETF invites any interested party to bring to its attention any 1928 copyrights, patents or patent applications, or other proprietary 1929 rights which may cover technology that may be required to practice 1930 this standard. Please address the information to the IETF Executive 1931 Director. 1933 6. Acknowledgements 1935 The editors would like to thank the following individuals for their 1936 assistance and constructive comments: 1937 Vincent Guan, BCSI Gavin Bowlby, Gadzoox 1938 Bent Stoevhase, BCSI Jeff Meyer, HP 1939 John Y. Chu, IBM 1940 Yakov Rekhter, IBM Martin Sachs, IBM 1941 Dan Eisenhauer, IBM Beth Vanderbeck, IBM 1942 Carl Zeitler, IBM Paul Griffiths, IBM 1943 KC Chennappan, IBM Jessie Haug, IBM 1944 Bob Cornelius, ANCOR Lansing Sloan, LLNL 1945 Paul Rupert, LLNL Rich Taborak, Amdahl 1946 Steve Wilson, Amdahl Jerry Rouse, IBM 1947 Dal Allan, ENDL Hubert Huot, IBM 1948 Venkat Rao, HP Amir Artsi, RADWAY International Ltd. 1950 7. References 1952 7.1. IETF References 1954 [1] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for 1955 Describing SNMP Management Frameworks, RFC 2571, Cabletron 1956 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1957 April 1999 1959 [2] Rose, M., and K. McCloghrie, Structure and Identification of 1960 Management Information for TCP/IP-based Internets, RFC 1155, STD 1961 16, Performance Systems International, Hughes LAN Systems, May 1962 1990 1964 [3] Rose, M., and K. McCloghrie, Concise MIB Definitions, RFC 1212, 1965 STD 16, Performance Systems International, Hughes LAN Systems, 1966 March 1991 1968 [4] M. Rose, A Convention for Defining Traps for use with the SNMP, 1969 RFC 1215, Performance Systems International, March 1991 1971 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1972 M., and S. Waldbusser, Structure of Management Information 1973 Version 2 (SMIv2), RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1974 Braunschweig, SNMP Research, First Virtual Holdings, 1975 International Network Services, April 1999 1977 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1978 M., and S. Waldbusser, Textual Conventions for SMIv2, RFC 2579, 1979 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1980 First Virtual Holdings, International Network Services, April 1981 1999 1983 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1984 M., and S. Waldbusser, Conformance Statements for SMIv2, RFC 1985 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 1986 Research, First Virtual Holdings, International Network 1987 Services, April 1999 1989 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple 1990 Network Management Protocol, RFC 1157, STD 15, SNMP Research, 1991 Performance Systems International, Performance Systems 1992 International, MIT Laboratory for Computer Science, May 1990. 1994 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1995 Introduction to Community-based SNMPv2, RFC 1901, SNMP Research, 1996 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1997 International Network Services, January 1996. 1999 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Transport 2000 Mappings for Version 2 of the Simple Network Management Protocol 2001 (SNMPv2), RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 2002 Dover Beach Consulting, Inc., International Network Services, 2003 January 1996. 2005 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 2006 Processing and Dispatching for the Simple Network Management 2007 Protocol (SNMP), RFC 2572, SNMP Research, Inc., Cabletron 2008 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2009 April 1999 2011 [12] Blumenthal, U., and B. Wijnen, User-based Security Model (USM) 2012 for version 3 of the Simple Network Management Protocol 2013 (SNMPv3), RFC 2574, IBM T. J. Watson Research, April 1999 2015 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Protocol 2016 Operations for Version 2 of the Simple Network Management 2017 Protocol (SNMPv2), RFC 1905, SNMP Research, Inc., Cisco Systems, 2018 Inc., Dover Beach Consulting, Inc., International Network 2019 Services, January 1996. 2021 [14] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, RFC 2022 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 2023 Systems, April 1999 2025 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based Access 2026 Control Model (VACM) for the Simple Network Management Protocol 2027 (SNMP), RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 2028 Cisco Systems, Inc., April 1999 2030 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, Introduction 2031 to Version 3 of the Internet-standard Network Management 2032 Framework, RFC 2570, SNMP Research, Inc., TIS Labs at Network 2033 Associates, Inc., Ericsson, Cisco Systems, April 1999 2035 7.2. Approved ANSI/NCITS References 2037 [17] Fibre Channel Physical and Signaling Interface (FC-PH), American 2038 National Standard for Information Systems X3.230:1994, Computer 2039 and Business Equipment Manufacturers Association, Washington, 2040 DC. 2042 [18] Fibre Channel Fabric Generic (FC-FG), American National Standard 2043 for Information Systems X3.289:1996, Computer and Business 2044 Equipment Manufacturers Association, Washington, DC. 2046 [19] Fibre Channel Generic Services (FC-GS), American National 2047 Standard for Information Systems X3.288:1996, Computer and 2048 Business Equipment Manufacturers Association, Washington, DC. 2050 [20] Fibre Channel Arbitrated Loop (FC-AL), American National 2051 Standard for Information Systems X3.272:1996, Computer and 2052 Business Equipment Manufacturers Association, Washington, DC. 2054 [21] Fibre Channel Physical and Signaling Interface-2 (FC-PH-2), 2055 American National Standard for Information Systems, X3.297:1997, 2056 Computer and Business Equipment Manufacturers Association, 2057 Washington, DC. 2059 [22] Fibre Channel Physical and Signaling Interface-3 (FC-PH-3), 2060 American National Standard for Information Systems, X3.303:1998, 2061 Computer and Business Equipment Manufacturers Association, 2062 Washington, DC. 2064 [23] Fibre Channel Switch Fabric (FC-SW), American National Standard 2065 for Information Systems, NCITS 321:1998, Computer and Business 2066 Equipment Manufacturers Association, Washington, DC. 2068 7.3. ANSI/NCITS References Under Development 2070 [24] Fibre Channel Arbitrated Loop-2 (FC-AL-2), American National 2071 Standard for Information Systems, X3T11/1133D Rev 5.2, Computer 2072 and Business Equipment Manufacturers Association, Washington, 2073 DC. 2075 8. Editors' Addresses 2077 Kha Sin Teow 2078 Brocade Communications Systems, Inc. 2079 1901 Guadalupe Parkway, 2080 San Jose, CA 95131 2081 U.S.A. 2082 Phone: +1 408-487-8180 2083 Email: khasin@Brocade.COM 2085 9. Full Copyright Statement 2087 Copyright (C) The Internet Society (1999). All Rights Reserved. 2089 This document and translations of it may be copied and furnished to 2090 others, and derivative works that comment on or otherwise explain it 2091 or assist in its implementation may be prepared, copied, published 2092 and distributed, in whole or in part, without restriction of any 2093 kind, provided that the above copyright notice and this paragraph are 2094 included on all such copies and derivative works. However, this 2095 document itself may not be modified in any way, such as by removing 2096 the copyright notice or references to the Internet Society or other 2097 Internet organizations, except as needed for the purpose of 2098 developing Internet standards in which case the procedures for 2099 copyrights defined in the Internet Standards process must be 2100 followed, or as required to translate it into languages other than 2101 English. 2103 The limited permissions granted above are perpectual and will not be 2104 revoked by the Internet Society or its successors or assigns. 2106 This document and the information contained herein is provided on an 2107 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2108 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2109 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2110 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2111 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.