idnits 2.17.1 draft-kzm-fc-rtm-mib-03.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 3979, Section 5, paragraph 1 on line 926. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 933. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 939. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 34), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 34. ** Found boilerplate matching RFC 3979, Section 5, paragraph 1 (on line 926), which is fine, but *also* found old RFC 2026, Section 10.4A text on line 748. ** Found boilerplate matching RFC 3979, Section 5, paragraph 3 (on line 939), which is fine, but *also* found old RFC 2026, Section 10.4B text on line 754. ** 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. 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? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 860: '... It is RECOMMENDED that implementors...' RFC 2119 keyword, line 866: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == In addition to RFC 3979, Section 5, paragraph 1 boilerplate, a section with a similar start was also found: The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. == In addition to RFC 3979, Section 5, paragraph 3 boilerplate, a section with a similar start was also found: The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 139 has weird spacing: '...tion of route...' -- 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 (9 June 2005) is 6890 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-FS' is mentioned on line 189, but not defined == Missing Reference: 'RFC2741' is mentioned on line 241, but not defined == Missing Reference: 'RFC2863' is mentioned on line 302, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-3' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-4' -- No information found for draft-ietf-ips-fcmgmt-mib-nn - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-MGMT' -- No information found for draft-ietf-imss-fc-fam-mib-nn - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-FAM-MIB' -- No information found for draft-kzm-imss-fc-fspf-mib-nn - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-FSM-MIB' -- Obsolete informational reference (is this intentional?): RFC 2837 (Obsoleted by RFC 4044) Summary: 11 errors (**), 0 flaws (~~), 8 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft C. DeSanti 3 S. Kode 4 K. McCloghrie 5 S. Gai 6 Cisco Systems 7 9 June 2005 8 Fibre-Channel Routing Information MIB 9 draft-kzm-fc-rtm-mib-03.txt (and T11/05-011v4) 11 Status of this Memo 13 "By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79." 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as "work in progress". 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. Internet-Draft Shadow 30 Directories are listed at http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2005). All Rights Reserved. 36 Abstract 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in the Internet community. 40 In particular, it describes managed objects for information related 41 to routing within a Fibre Channel fabric which is independent of the 42 usage of a particular routing protocol. At present, this memo is in 43 development as part of the SM-RTM project of T11.5 44 (http://www.t11.org). The plan is that it will later become a work 45 item of IETF's IMSS working group. 47 Table of Contents 49 1 Introduction ................................................. 3 50 1.1 Change Log ................................................. 3 51 2 The Internet-Standard Management Framework ................... 4 52 3 Short Overview of Fibre Channel .............................. 5 53 4 Relationship to Other MIBs ................................... 6 54 5 MIB Overview ................................................. 6 55 5.1 Fibre Channel management instance .......................... 6 56 5.2 Switch Index ............................................... 7 57 5.3 Fabric Index ............................................... 7 58 5.4 The t11FcRouteGroup Group .................................. 7 59 6 The T11-FC-ROUTE-MIB Module .................................. 8 60 7 Intellectual Property ........................................ 18 61 8 Acknowledgements ............................................. 18 62 9 Normative References ......................................... 18 63 10 Informative References ...................................... 19 64 11 IANA Considerations ......................................... 19 65 12 Security Considerations ..................................... 20 66 13 Authors' Addresses .......................................... 21 68 1. Introduction 70 This memo defines a portion of the Management Information Base (MIB) 71 for use with network management protocols in the Internet community. 72 In particular, it describes managed objects for information related 73 to the Fibre Channel network's Routing Table for routing within a 74 Fabric. Managed objects specific to particular routing protocols, 75 such as FSPF, are not specified in this MIB module. 77 1.1. Change Log 79 This section to be deleted when the document becomes approved. 81 1.1.1. Initial version: 83 Initial version was submitted to T11.5 as 04-747v0 on 13 November 84 2004. 86 1.1.2. Changes made in January/February 2005 version 88 The following changes were made for the version was submitted to 89 T11.5 as: 05-011v0 (on 10 January), and to the IETF (on 7 February) 90 as: draft-kzm--fc-rtm-mib-00.txt. 92 - created the t11FcRouteFabricTable to hold 93 t11FcRouteFabricLastChange (was previously a scalar). 95 - added t11FcRouteStorageType (see requirement for a StorageType 96 object on page 22 of draft-ietf-ops-mib-review-guidelines-03.txt). 98 1.1.3. Changes made in March 2005 version 100 The following changes were made for the version was submitted to 101 T11.5 (05-011v1) and the IETF (draft-kzm-fc-rtm-mib-01.txt). 103 - changed the name and syntax (but not the semantics) of 104 t11FcRouteTemporary to be t11FcRouteIfDown, so as to avoid 105 confusion with t11FcRouteStorageType. 107 1.1.4. Changes made in April 2005 version 109 The following changes were made for the version was submitted to 110 T11.5 (05-011v2) and the IETF (draft-kzm-fc-rtm-mib-02.txt). 112 - defined t11FcRouteSrcAddrId and t11FcRouteSrcMask as new objects, 113 added them to the INDEX of the t11FcRouteTable, and indicated that 114 support for the "zero" values of these objects is sufficient for 115 compliance. 117 1.1.5. Changes made in 26 May 2005 version 119 The following changes were made for the version was submitted to 120 T11.5 as 05-011v3. 122 - Section 5.3 was clarified to indicate that the Fabric Index could 123 be used to distinguish between multiple physcial and/or virtual 124 Fabrics. 126 - Defined the usage of the zero-length string as a value of 127 t11FcRouteDestAddrId and t11FcRouteDestMask. 129 - Clarified several DESCRIPTIONs and fixed several typos. 131 - Updated the Normative Reference to be Revision 7.4 of FC-SW-4, and 132 added a reference for FC-SW-3. 134 1.1.6. Changes made in 9 June 2005 version 136 The following changes were made for the version was submitted to 137 T11.5 as 05-011v4 and to the IETF as draft-kzm-fc-rtm-mib-03.txt. 139 - Added a description of route lookup and mask operation to the 140 DESCRIPTION of the t11FcRouteTable. 142 - Added t11FCRouteInInterface as a new object in the t11FcRouteTable 143 and in its INDEX clause, with syntax of InterfaceIndexorZero. 144 Changed t11FCRouteInterface to be t11FCRouteOutInterface. 146 2. The Internet-Standard Management Framework 148 For a detailed overview of the documents that describe the current 149 Internet-Standard Management Framework, please refer to section 7 of 150 RFC 3410 [RFC3410]. 152 Managed objects are accessed via a virtual information store, termed 153 the Management Information Base or MIB. MIB objects are generally 154 accessed through the Simple Network Management Protocol (SNMP). 155 Objects in the MIB are defined using the mechanisms defined in the 156 Structure of Management Information (SMI). This memo specifies a MIB 157 module that is compliant to the SMIv2, which is described in STD 58, 158 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 159 [RFC2580]. 161 3. Short Overview of Fibre Channel 163 The Fibre Channel (FC) is logically a bidirectional point-to-point 164 serial data channel, structured for high performance. Fibre Channel 165 provides a general transport vehicle for higher level protocols such 166 as Small Computer System Interface (SCSI) command sets, the High- 167 Performance Parallel Interface (HIPPI) data framing, IP (Internet 168 Protocol), IEEE 802.2, and others. 170 Physically, Fibre Channel is an interconnection of multiple 171 communication points, called N_Ports, interconnected either by a 172 switching network, called a Fabric, or by a point-to-point link. A 173 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 174 consist of multiple Interconnect Elements, some of which are 175 switches. An N_Port connects to the Fabric via a port on a switch 176 called an F_Port. When multiple FC nodes are connected to a single 177 port on a switch via an "Arbitrated Loop" topology, the switch port 178 is called an FL_Port, and the nodes' ports are called NL_Ports. The 179 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 180 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 181 switch port, which is interconnected to another switch port via an 182 Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a 183 bridge device with an E_Port on a switch; a B_Port provides a subset 184 of E_Port functionality. 186 Many Fibre Channel components, including the fabric, each node, and 187 most ports, have globally-unique names. These globally-unique names 188 are typically formatted as World Wide Names (WWNs). More information 189 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 190 across agent and unit resets. 192 Fibre Channel frames contain 24-bit address identifiers which 193 identify the frame's source and destination ports. Each FC port has 194 both an address identifier and a WWN. When a fabric is in use, the 195 FC address identifiers are dynamic and are assigned by a switch. 196 Each octet of a 24-bit address represents a level in an address 197 hierarchy, with a Domain_ID being the highest level of the hierarchy. 199 The routing of frames within the Fabric is normally based on the 200 standard routing protocol, called the Fabric Shortest Path First 201 (FSPF) protocol. The operation of FSPF (or any other routing 202 protocol) allows a switch to generate and maintain its own routing 203 table of how to forward frames it receives, i.e., a table in which to 204 lookup the destination address of a received frame in order to 205 determine the best link by which to forward that frame towards its 206 destination. 208 4. Relationship to Other MIBs 210 The first standardized MIB for Fibre Channel [RFC2837] was focussed 211 on Fibre Channel switches. It is being replaced by the more generic 212 Fibre Channel Management MIB [FC-MGMT] which defines basic 213 information for Fibre Channel hosts and switches, including 214 extensions to the standard IF-MIB for Fibre Channel interfaces. 216 This MIB extends beyond [FC-MGMT] to cover the routing of traffic 217 within a Fabric of a Fibre Channel network. The standard routing 218 protocol for Fibre Channel is FSPF [FC-SW-4]. Another MIB [FC-FSM- 219 MIB] specifies management information specific to FSPF. This MIB 220 contains routing information which is independent of FSPF (i.e., it 221 would still apply even if a routing protocol other than FSPF were in 222 use in the network). 224 This MIB imports some common Textual Conventions from T11-TC-MIB, 225 defined in [FC-FAM-MIB]. 227 5. MIB Overview 229 This MIB module provides the means for monitoring the operation of, 230 and configuring some parameters of, one or more instances of the FSPF 231 protocol. (Note that there are no definitions in this MIB module of 232 "managed actions" which can be invoked via SNMP.) 234 5.1. Fibre Channel management instance 236 A Fibre Channel management instance is defined in [FC-MGMT] as a 237 separable managed instance of Fibre Channel functionality. Fibre 238 Channel functionality may be grouped into Fibre Channel management 239 instances in whatever way is most convenient for the 240 implementation(s). For example, one such grouping accommodates a 241 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 242 each sub-agent implementing a different Fibre Channel management 243 instance. 245 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB 246 [FC-MGMT] as the index value to uniquely identify each Fibre Channel 247 management instance within the same SNMP context ([RFC3411] section 248 3.3.1). 250 5.2. Switch Index 252 The FC-MGMT-MIB [FC-MGMT] defines the fcmSwitchTable as a table of 253 information about Fibre Channel switches which are managed by Fibre 254 Channel management instances. Each Fibre Channel management instance 255 can manage one or more Fibre Channel switches. The Switch Index, 256 fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value 257 to uniquely identify a Fibre Channel switch amongst those (one or 258 more) managed by the same Fibre Channel management instance. 260 5.3. Fabric Index 262 The latest standard for an interconnecting Fabric containing multiple 263 Fabric Switch elements is [FC-SW-4] (which replaces the previous 264 revision [FC-SW-3]). [FC-SW-4] specifies the operation of both a 265 single Fabric in a physical infrastructure, as well as the support of 266 multiple Virtual Fabrics operating within one (or more) physical 267 infrastructures. Whether operating on a physical Fabric (i.e., 268 without Virtual Fabrics) or within a Virtual Fabric, the operation of 269 FSPF within a Fabric is identical. Therefore, this MIB defines all 270 Fabric-related information in tables which are INDEX-ed by an 271 arbitrary integer, named a "Fabric Index", the syntax of which is 272 IMPORTed from the T11-TC-MIB. When a device is connected to a single 273 physical Fabric, without use of any virtual Fabrics, the value of 274 this Fabric Index will always be 1. In an environment of multiple 275 virtual and/or physical Fabrics, this index provides a means to 276 distinguish one Fabric from another. 278 It is quite possible, and may even be likely, that a Fibre Channel 279 switch will have ports connected to multiple virtual and/or physical 280 Fabrics. Thus, in order to simplify a management protocol query 281 concerning all the Fabrics to which a single switch is connected, 282 fcmSwitchIndex will be listed before t11FcRouteFabricIndex when they 283 both appear in the same INDEX clause. 285 5.4. The t11FcRouteGroup Group 287 This MIB contains one object group, the t11FcRouteGroup. This group 288 contains objects to allow the displaying and the configuring of 289 routes in the Fibre Channel Routing tables for the locally-managed 290 switches. 292 6. The T11-FC-ROUTE-MIB Module 294 T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN 296 IMPORTS 297 MODULE-IDENTITY, OBJECT-TYPE, 298 Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578] 299 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 300 RowStatus, TimeStamp, 301 StorageType FROM SNMPv2-TC -- [RFC2579] 302 InterfaceIndex FROM IF-MIB -- [RFC2863] 303 fcmInstanceIndex, fcmSwitchIndex, 304 FcAddressIdOrZero, FcDomainIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT] 305 T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] 307 t11FcRouteMIB MODULE-IDENTITY 308 LAST-UPDATED "200504140000Z" 309 ORGANIZATION "T11" 310 CONTACT-INFO 311 " Claudio DeSanti 312 Cisco Systems, Inc. 313 170 West Tasman Drive 314 San Jose, CA 95134 USA 315 EMail: cds@cisco.com 317 Keith McCloghrie 318 Cisco Systems, Inc. 319 170 West Tasman Drive 320 San Jose, CA USA 95134 321 Email: kzm@cisco.com" 322 DESCRIPTION 323 "The MIB module for configuring and displaying Fibre 324 Channel Route Information." 326 REVISION "200504140000Z" 327 DESCRIPTION 328 "Initial version of this MIB module." 329 ::= { mib-2 nnn } -- to be determined later 331 t11FcRouteNotifications OBJECT IDENTIFIER ::= { t11FcRouteMIB 0 } 332 t11FcRouteObjects OBJECT IDENTIFIER ::= { t11FcRouteMIB 1 } 333 t11FcRouteConformance OBJECT IDENTIFIER ::= { t11FcRouteMIB 2 } 335 -- 336 -- Per-Fabric routing information 337 -- 338 t11FcRouteFabricTable OBJECT-TYPE 339 SYNTAX SEQUENCE OF T11FcRouteFabricEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "The table containing Fibre Channel Routing information 344 which is specific to a Fabric." 345 ::= { t11FcRouteObjects 1 } 347 t11FcRouteFabricEntry OBJECT-TYPE 348 SYNTAX T11FcRouteFabricEntry 349 MAX-ACCESS not-accessible 350 STATUS current 351 DESCRIPTION 352 "Each entry contains routing information specific to a 353 particular Fabric on a particular switch (identified by 354 values of fcmInstanceIndex and fcmSwitchIndex)." 355 INDEX { fcmInstanceIndex, fcmSwitchIndex, 356 t11FcRouteFabricIndex } 357 ::= { t11FcRouteFabricTable 1 } 359 T11FcRouteFabricEntry ::= 360 SEQUENCE { 361 t11FcRouteFabricIndex T11FabricIndex, 362 t11FcRouteFabricLastChange TimeStamp 363 } 365 t11FcRouteFabricIndex OBJECT-TYPE 366 SYNTAX T11FabricIndex 367 MAX-ACCESS not-accessible 368 STATUS current 369 DESCRIPTION 370 "A unique index value which uniquely identifies a 371 particular Fabric. 373 In a Fabric conformant to FC-SW-3, only a single Fabric 374 can operate within a physical infrastructure, and thus, 375 the value of this Fabric Index will always be 1. 377 In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics 378 can operate within one (or more) physical infrastructures. 379 In such a case, index value is used to uniquely identify a 380 particular Fabric within a physical infrastructure." 381 ::= { t11FcRouteFabricEntry 1 } 383 t11FcRouteFabricLastChange OBJECT-TYPE 384 SYNTAX TimeStamp 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The value of sysUpTime at the most recent time when any 389 corresponding row in the t11FcRouteTable, was created, 390 modified, or deleted. A corresponding row in the 391 t11FcRouteTable is for the same management instance, 392 the same switch and same Fabric as the row in this table. 394 If no change has occurred since the last restart of the 395 management system, then the value of this object is 0." 396 ::= { t11FcRouteFabricEntry 2 } 398 -- 399 -- Fibre Channel Routing table 400 -- 401 t11FcRouteTable OBJECT-TYPE 402 SYNTAX SEQUENCE OF T11FcRouteEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "The Fibre Channel Routing tables for the 407 locally-managed switches. This table lists all the 408 routes that are configured in and/or computed by any 409 local switch for any Fabric. 411 Such routes are used by a switch to forward frames (of user 412 data) on a Fabric. The conceptual process is based on 413 extracting the Destination Fibre Channel Addresss Identifier 414 (D_ID) out of a received frame (of user data), and comparing 415 it to each entry of this table which is applicable to the 416 given switch and Fabric. Such comparsion consists of first 417 performing a logical-AND of the extracted D_ID with a mask 418 (the value of t11FcRouteDestMask), and second comparing the 419 result of that 'AND' operation to the value of 420 t11FcRouteDestAddrId. A similar comparison is made of the 421 Source Fibre Channel Addresss Identifier (D_ID) of a frame 422 against the t11FcRouteSrcAddrId and t11FcRouteSrcMask values 423 of an entry. If an entry's value of t11FcRouteInInterface 424 is non-zero, then a further comparison determines if the 425 frame was received on the appropriate interface. If all of 426 these comparisons for a particular entry are successful, 427 then that entry represents a potential route for forwarding 428 the received frame. 430 For entries configured by a user, t11FcRouteProto has 431 the value 'netmgmt'; only entries of this type can be 432 deleted by the user." 433 ::= { t11FcRouteObjects 2 } 435 t11FcRouteEntry OBJECT-TYPE 436 SYNTAX T11FcRouteEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "Each entry contains a route to a particular destination, 441 possibly from a particular subset of source addresses, 442 on a particular Fabric via a particular output interface, 443 and learned in a particular manner." 444 INDEX { fcmInstanceIndex, fcmSwitchIndex, 445 t11FcRouteFabricIndex, 446 t11FcRouteDestAddrId, t11FcRouteDestMask, 447 t11FcRouteSrcAddrId, t11FcRouteSrcMask, 448 t11FcRouteInInterface, t11FcRouteProto, 449 t11FcRouteOutInterface } 450 ::= { t11FcRouteTable 1 } 452 T11FcRouteEntry ::= 453 SEQUENCE { 454 t11FcRouteDestAddrId FcAddressIdOrZero, 455 t11FcRouteDestMask FcAddressIdOrZero, 456 t11FcRouteSrcAddrId FcAddressIdOrZero, 457 t11FcRouteSrcMask FcAddressIdOrZero, 458 t11FcRouteInInterface InterfaceIndexOrZero, 459 t11FcRouteProto INTEGER, 460 t11FcRouteOutInterface InterfaceIndex, 461 t11FcRouteDomainId FcDomainIdOrZero, 462 t11FcRouteMetric Unsigned32, 463 t11FcRouteType INTEGER, 464 t11FcRouteIfDown INTEGER, 465 t11FcRouteStorageType StorageType, 466 t11FcRouteRowStatus RowStatus 468 } 470 t11FcRouteDestAddrId OBJECT-TYPE 471 SYNTAX FcAddressIdOrZero 472 MAX-ACCESS not-accessible 473 STATUS current 474 DESCRIPTION 475 "The destination Fibre Channel Address Identifier of 476 this route. A zero-length string for this field is 477 not allowed." 478 ::= { t11FcRouteEntry 1 } 480 t11FcRouteDestMask OBJECT-TYPE 481 SYNTAX FcAddressIdOrZero 482 MAX-ACCESS not-accessible 483 STATUS current 484 DESCRIPTION 485 "The mask to be logical-ANDed with a destination 486 Fibre Channel Address Identifier before it is campared 487 to the value in the t11FcRouteDestAddrId field. 488 Allowed values are 255.255.255, 255.255.0 or 255.0.0. 489 FSPF's definition generates routes to a Domain_ID, and 490 so the mask for all FSPF-generated routes is 255.0.0. 491 The zero-length value has the same meaning as 0.0.0." 492 ::= { t11FcRouteEntry 2 } 494 t11FcRouteSrcAddrId OBJECT-TYPE 495 SYNTAX FcAddressIdOrZero 496 MAX-ACCESS not-accessible 497 STATUS current 498 DESCRIPTION 499 "The source Fibre Channel Address Identifier of this 500 route. Note that if this object and the corresponding 501 instance of t11FcRouteSrcMask both have a value of 0.0.0, 502 then this route matches all source addresses. The 503 zero-length value has the same meaning as 0.0.0." 504 ::= { t11FcRouteEntry 3 } 506 t11FcRouteSrcMask OBJECT-TYPE 507 SYNTAX FcAddressIdOrZero 508 MAX-ACCESS not-accessible 509 STATUS current 510 DESCRIPTION 511 "The mask to be logical-ANDed with a source 512 Fibre Channel Address Identifier before it is compared 513 to the value in the t11FcRouteSrcAddrId field. Allowed 514 values are 255.255.255, 255.255.0, 255.0.0 or 0.0.0. 515 The zero-length value has the same meaning as 0.0.0." 516 ::= { t11FcRouteEntry 4 } 518 t11FcRouteInInterface OBJECT-TYPE 519 SYNTAX InterfaceIndexOrZero 520 MAX-ACCESS not-accessible 521 STATUS current 522 DESCRIPTION 523 "If the value of this object is non-zero, it is the 524 value of ifIndex which identifies the local 525 Fibre Channel interface through which a frame 526 must have been received in order to match with 527 this entry. If the value of this object is zero, 528 the matching does not require the frame to be 529 received on any specific interface." 530 ::= { t11FcRouteEntry 5 } 532 t11FcRouteProto OBJECT-TYPE 533 SYNTAX INTEGER { 534 other(1), 535 local(2), 536 netmgmt(3), 537 fspf(4) 538 } 539 MAX-ACCESS not-accessible 540 STATUS current 541 DESCRIPTION 542 "The mechanism via which this route was learned: 544 other(1) - not specified 545 local(2) - local interface 546 netmgmt(3)- static route 547 fspf(4) - Fibre Shortest Path First. 548 " 549 ::= { t11FcRouteEntry 6 } 551 t11FcRouteOutInterface OBJECT-TYPE 552 SYNTAX InterfaceIndex 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "The value of ifIndex which identifies the local 557 Fibre Channel interface through which the next hop 558 of this route is to be reached." 559 ::= { t11FcRouteEntry 7 } 561 t11FcRouteDomainId OBJECT-TYPE 562 SYNTAX FcDomainIdOrZero 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 566 "The domain_ID of next hop switch. 568 This object can have a value of zero if the value 569 of t11FcRouteProto is 'local'." 570 ::= { t11FcRouteEntry 8 } 572 t11FcRouteMetric OBJECT-TYPE 573 SYNTAX Unsigned32 (0..65536) 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "The routing metric for this route. 578 The use of this object is dependent on 579 t11FcRouteProto." 580 ::= { t11FcRouteEntry 9 } 582 t11FcRouteType OBJECT-TYPE 583 SYNTAX INTEGER { 584 local(1), 585 remote(2) 586 } 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "The type of route. 591 local(1): refers to a route for which the next Fibre 592 Channel port is the final destination; 593 remote(2): refers to a route for which the next Fibre 594 Channel port is not the final destination." 595 DEFVAL {local} 596 ::= { t11FcRouteEntry 10 } 598 t11FcRouteIfDown OBJECT-TYPE 599 SYNTAX INTEGER { 600 remove(1), 601 retain(2) 602 } 604 MAX-ACCESS read-create 605 STATUS current 606 DESCRIPTION 607 "The value of this object indicates what happens to 608 this route when the output interface (given by the 609 corresponding value of t11FcRouteOutInterface) is 610 operationally 'down'. If this object's value is 'retain', 611 the route is to be retained in this table. If this 612 object's value is 'remove', the route is to be removed 613 from this table." 614 DEFVAL { retain } 615 ::= { t11FcRouteEntry 11 } 617 t11FcRouteStorageType OBJECT-TYPE 618 SYNTAX StorageType 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "The storage type for this conceptual row. 623 Conceptual rows having the value 'permanent' need not 624 allow write-access to any columnar objects in the row." 625 DEFVAL { nonVolatile } 626 ::= { t11FcRouteEntry 12 } 628 t11FcRouteRowStatus OBJECT-TYPE 629 SYNTAX RowStatus 630 MAX-ACCESS read-create 631 STATUS current 632 DESCRIPTION 633 "The status of this conceptual row." 634 ::= { t11FcRouteEntry 13 } 636 -- 637 -- Conformance 638 -- 639 t11FcRouteCompliances OBJECT IDENTIFIER 640 ::= { t11FcRouteConformance 1 } 641 t11FcRouteGroups OBJECT IDENTIFIER 642 ::= { t11FcRouteConformance 2 } 644 t11FcRouteCompliance MODULE-COMPLIANCE 645 STATUS current 646 DESCRIPTION 647 "The compliance statement for entities which 648 implement the T11-FC-ROUTE-MIB." 649 MODULE -- this module 650 MANDATORY-GROUPS { t11FcRouteGroup } 652 OBJECT t11FcRouteIfDown 653 MIN-ACCESS read-only 654 DESCRIPTION 655 "Write access is not required." 657 OBJECT t11FcRouteDomainId 658 MIN-ACCESS read-only 659 DESCRIPTION 660 "Write access is not required." 662 OBJECT t11FcRouteMetric 663 MIN-ACCESS read-only 664 DESCRIPTION 665 "Write access is not required." 667 OBJECT t11FcRouteType 668 MIN-ACCESS read-only 669 DESCRIPTION 670 "Write access is not required." 672 OBJECT t11FcRouteStorageType 673 MIN-ACCESS read-only 674 DESCRIPTION 675 "Write access is not required." 677 OBJECT t11FcRouteRowStatus 678 SYNTAX INTEGER { active(1) } 679 MIN-ACCESS read-only 680 DESCRIPTION 681 "Write access is not required." 682 -- 683 -- Note: the next two objects are auxiliary objects and the SMIv2 684 -- does not permit inclusion of objects that are not accessible in 685 -- an OBJECT clause (see sections 3.1 & 5.4.3 in STD 58, RFC 2580). 686 -- Thus, the following OBJECT clauses must be commented-out. 687 -- 688 -- OBJECT t11FcRouteSrcAddrId 689 -- SYNTAX FcAddressIdOrZero (SIZE (0)) 690 -- DESCRIPTION 691 -- "Support is not required for routes which 692 -- match only a subset of possible source 693 -- addresses." 694 -- 695 -- OBJECT t11FcRouteSrcMask 696 -- SYNTAX FcAddressIdOrZero (SIZE (0)) 697 -- DESCRIPTION 698 -- "Support is not required for routes which 699 -- match only a subset of possible source 700 -- addresses." 701 -- 702 -- OBJECT t11FcRouteDestMask 703 -- DESCRIPTION 704 -- "Support is mandatory only for FSPF-generated 705 -- routes. Since FSPF's definition generates 706 -- routes to a Domain_ID, the mask for all 707 -- FSPF-generated routes is 255.0.0. Thus, 708 -- support is only required for 255.0.0." 709 -- 710 -- OBJECT t11FcRouteInInterface 711 -- SYNTAX InterfaceIndexOrZero (0) 712 -- DESCRIPTION 713 -- "Support for routes specific to particular 714 -- source interfaces is not required." 716 ::= { t11FcRouteCompliances 1 } 718 t11FcRouteGroup OBJECT-GROUP 719 OBJECTS { t11FcRouteFabricLastChange, 720 t11FcRouteDomainId, 721 t11FcRouteMetric, 722 t11FcRouteType, 723 t11FcRouteIfDown, 724 t11FcRouteStorageType, 725 t11FcRouteRowStatus 726 } 727 STATUS current 728 DESCRIPTION 729 "A collection of objects for displaying and configuring 730 routes." 731 ::= { t11FcRouteGroups 1 } 733 END 734 7. Intellectual Property 736 The IETF takes no position regarding the validity or scope of any 737 intellectual property or other rights that might be claimed to 738 pertain to the implementation or use of the technology described in 739 this document or the extent to which any license under such rights 740 might or might not be available; neither does it represent that it 741 has made any effort to identify any such rights. Information on the 742 IETF's procedures with respect to rights in standards-track and 743 standards-related documentation can be found in BCP-11. Copies of 744 claims of rights made available for publication and any assurances of 745 licenses to be made available, or the result of an attempt made to 746 obtain a general license or permission for the use of such 747 proprietary rights by implementors or users of this specification can 748 be obtained from the IETF Secretariat. 750 The IETF invites any interested party to bring to its attention any 751 copyrights, patents or patent applications, or other proprietary 752 rights which may cover technology that may be required to practice 753 this standard. Please address the information to the IETF Executive 754 Director. 756 8. Acknowledgements 758 This document is currently a work item of the INCITS Task Group 759 T11.5. 761 9. Normative References 763 [RFC2578] 764 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 765 and S. Waldbusser, "Structure of Management Information Version 2 766 (SMIv2)", STD 58, RFC 2578, April 1999. 768 [RFC2579] 769 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 770 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 771 2579, April 1999. 773 [RFC2580] 774 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 775 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 776 2580, April 1999. 778 [RFC3411] 779 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 780 Describing Simple Network Management Protocol (SNMP) Management 781 Frameworks", STD 58, RFC 3411, December 2002. 783 [FC-SW-3] 784 "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", INCITS 384-2004, 785 2004. 787 [FC-SW-4] 788 "Fibre Channel - Switch Fabric - 4 (FC-SW-4)", ANSI NCITS xxx-xxxx, 789 T11/Project 1674-D/Rev 7.4, May 2005. 791 [FC-MGMT] 792 K. McCloghrie, "Fibre Channel Management MIB", Internet-Draft 793 (draft-ietf-ips-fcmgmt-mib-nn.txt), work-in-progress. 795 [FC-FAM-MIB] 796 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- 797 Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf- 798 imss-fc-fam-mib-nn.txt), work-in-progress. 800 [FC-FSM-MIB] 801 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "MIB for 802 Fibre-Channel's Fabric Shortest Path First Protocol", Internet- 803 Draft (draft-kzm-imss-fc-fspf-mib-nn.txt), work-in-progress. 805 10. Informative References 807 [RFC2837] 808 Teow, K., "Definitions of Managed Objects for the Fabric Element in 809 Fibre Channel Standard", RFC 2837, May 2000. 811 [RFC3410] 812 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 813 Applicability Statements for Internet- Standard Management 814 Framework", RFC 3410, December 2002. 816 11. IANA Considerations 818 IANA is requested to make the OID assignment for the MIB module under 819 the appropriate subtree. 821 12. Security Considerations 823 There are several management objects defined in this MIB module with 824 a MAX-ACCESS clause of read-write and/or read-create. Such objects 825 may be considered sensitive or vulnerable in some network 826 environments. The support for SET operations in a non-secure 827 environment without proper protection can have a negative effect on 828 network operations. These objects and their 829 sensitivity/vulnerability are: 831 t11FcRouteDomainId, t11FcRouteMetric, t11FcRouteType, 832 t11FcRouteIfDown, t11FcRouteRowStatus 833 -- configure new routes and/or modify existing routes. 835 Such objects may be considered sensitive or vulnerable in some 836 network environments. For example, the ability to change network 837 topology or network speed may afford an attacker the ability to 838 obtain better performance at the expense of other network users. The 839 support for SET operations in a non-secure environment without proper 840 protection can have a negative effect on network operations. 842 Some of the readable objects in this MIB module (i.e., objects with a 843 MAX-ACCESS other than not-accessible) may be considered sensitive or 844 vulnerable in some network environments. It is thus important to 845 control even GET and/or NOTIFY access to these objects and possibly 846 to even encrypt the values of these objects when sending them over 847 the network via SNMP. The objects and their 848 sensitivity/vulnerability are: the write-able objects listed above 849 plus one other: 851 t11FcRouteLastChangeTime 852 -- the time of the last routing table change. 854 SNMP versions prior to SNMPv3 did not include adequate security. 855 Even if the network itself is secure (for example by using IPSec), 856 even then, there is no control as to who on the secure network is 857 allowed to access and GET/SET (read/change/create/delete) the objects 858 in this MIB module. 860 It is RECOMMENDED that implementors consider the security features as 861 provided by the SNMPv3 framework (see [RFC3410], section 8), 862 including full support for the SNMPv3 cryptographic mechanisms (for 863 authentication and privacy). 865 Further, deployment of SNMP versions prior to SNMPv3 is NOT 866 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 867 enable cryptographic security. It is then a customer/operator 868 responsibility to ensure that the SNMP entity giving access to an 869 instance of this MIB module is properly configured to give access to 870 the objects only to those principals (users) that have legitimate 871 rights to indeed GET or SET (change/create/delete) them. 873 13. Authors' Addresses 875 Claudio DeSanti 876 Cisco Systems, Inc. 877 170 West Tasman Drive 878 San Jose, CA 95134 USA 879 Phone: +1 408 853-9172 880 EMail: cds@cisco.com 882 Srini Kode 883 Cisco Systems, Inc. 884 170 West Tasman Drive 885 San Jose, CA 95134 USA 886 Phone: +1 408 853-9164 887 EMail: skode@cisco.com 889 Keith McCloghrie 890 Cisco Systems, Inc. 891 170 West Tasman Drive 892 San Jose, CA USA 95134 893 Phone: +1 408-526-5260 894 Email: kzm@cisco.com 896 Silvano Gai 897 Cisco Systems, Inc. 898 170 West Tasman Drive 899 San Jose, CA USA 95134 900 Phone: +1 408-526-7269 901 Email: sgai@cisco.com 903 14. Full Copyright Statement 905 Copyright (C) The Internet Society (2005). This document is subject 906 to the rights, licenses and restrictions contained in BCP 78, and 907 except as set forth therein, the authors retain all their rights. 909 "This document and the information contained herein are provided on 910 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 911 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 912 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 913 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 914 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 915 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 917 15. Disclaimer of validity 919 The IETF takes no position regarding the validity or scope of any 920 Intellectual Property Rights or other rights that might be claimed to 921 pertain to the implementation or use of the technology described in 922 this document or the extent to which any license under such rights 923 might or might not be available; nor does it represent that it has 924 made any independent effort to identify any such rights. Information 925 on the procedures with respect to rights in RFC documents can be 926 found in BCP 78 and BCP 79. 928 Copies of IPR disclosures made to the IETF Secretariat and any 929 assurances of licenses to be made available, or the result of an 930 attempt made to obtain a general license or permission for the use of 931 such proprietary rights by implementers or users of this 932 specification can be obtained from the IETF on-line IPR repository at 933 http://www.ietf.org/ipr. 935 The IETF invites any interested party to bring to its attention any 936 copyrights, patents or patent applications, or other proprietary 937 rights that may cover technology that may be required to implement 938 this standard. Please address the information to the IETF at 939 ietf-ipr@ietf.org. 941 Acknowledgment 943 Funding for the RFC Editor function is currently provided by the 944 Internet Society.