1. Fibre Channel MIBs Keith McCloghrie 9 Nov 2004

2. A Brief History RFC2837 = first standardized MIB for FC Fibre Alliance MIB submitted to IETF –lots of implementations, but –too many changes to be acceptable –T11 has published MIB-FA as informational IPStorage WG defined FC-MGMT-MIB –merging of 2837 & MIB-FA –lots of FC functionality not covered –proposal to define additional MIBs

3. Brief History (ctd) The proposal listed 9 additional MIBs After some discussion, process is: –the technical MIB definitions will be submitted first to T11 (T11.5 Management Ad Hoc) –T11 will review/update/edit to ensure conformance with FC standards; then pass to IMSS WG of IETF –IETF will ensure conformance to SMIv2 and consistency with other MIBs –when both organizations are happy, publish as RFC.

4. Current Status T11 have now passed the first two MIBs to the IETF: –Fabric Address Manager MIB draft-ietf-imss-fc-fam-mib-00.txt –Name Server MIB draft-ietf-imss-fc-nsm-mib-00.txt T11 beginning work on the next two: –FC Routing –FSPF

5. draft-ietf-imss-fc-fam-mib-00.txt Contains two MIB modules: –T11-TC-MIB FabricIndex is only TC defined (so far): –to support multiple Virtual Fabrics (new in FC-SW-4) –T11-FC-FABRIC-ADDR-MGR-MIB management of FC address assignment: –Domain_IDs & FC_IDs all tables are INDEX-ed by: –FC Management Instance Index (from FC-MGMT-MIB), –Switch Index (from FC-MGMT-MIB) –Fabric Index

6. FAM MIB (ctd) Five tables containing address-related information: –per-Fabric parameters/status/statistics –per-interface configuration/status –per-Area Port_ID assignments –per-Domain assignments (to switches) –cache of released assignments Three notifications –assignment failed; new principal switch; BF/RCF

7. draft-ietf-imss-fc-nsm-mib-00.txt Contains one MIB module: –T11-FC-NAME-SERVER-MIB management of information registered with the Name Server T11 had much discussion about the INDEX-ing –FC’s Name Server is defined as a distributed function –eventually agreement to focus on subsets of the registered information, (not on where or how it’s implemented) –each subset can be the information known/registered: at a switch or at a central location, or anywhere else within the Fabric !

8. NSM-MIB (ctd) All tables are INDEX-ed by: –Management Instance (from FC-MGMT-MIB), –Subset Index Five tables: –per-subset information (various) –info registered about a port (in a Fabric) –the one or more FC-4 types registered for a port –per-Fabric stats –per-port log of most-recently rejected registration One notification: on a rejected registration –binary content of registration request, and –error codes