Joe W., Here is how it might work...long post...
The FCIA site...Pretty neat. There is a SANmark trademark...check the bottom of the pages.
fibrechannel.com
SANmark Style Guide
Licensees of the SANmark trademark are granted permission to name those products meeting the SANmark compliance guidelines and may use the following formats in conjunction with their qualified products:
SANmark™ compliant
A SANmark™ product
The following logo is a sample of the version that may also be used with products that have been specifically licensed as "SANmark Qualified" per this program:
........The FCIA may not be big enough to get BRCD to want a sticker, but remember that they have a deal between the FCIA and the SNIA...
For proof of this take a look at some of these pdfs...
SANmark™ Qualified Program
Purpose of the Program
The FCIA established the SANmark Qualified Program to provide the industry with an objective indication of how Fibre Channel products perform against reasonable standards and to permit the use of the trademarked term "SANmark", and any associated logo(s), in the identification and promotion of products meeting the published test indices. The SANmark Qualified Program goals are:
Make Fibre Channel solutions easy to use, easy to install, manage, configure, diagnose, trouble shoot;
Ensure Fibre Channel continues to attain the highest performance and "installed base maturity" available in the market;
Proliferate heterogeneous shared SAN resources & heterogeneous management framework over WAN connections.
Content of this Program Guide:
SANmark Conformance Documents
Calendar of Meetings
Program Guide Sections
SANmark Revision A Test Suite
Program Guidelines
Fees & Non-FCIA Members
Application Process
SANmark Style Guide
SANmark Trademark License Enforcement Procedures
Role of Independent Labs
sanmark-tech@fibrechannel.org
Presentations
SANmark Tech Working Documents & Minutes
SCD-0000 -- Program Descriptions & Directions
Document Links Document Descriptions Recent Status Control Person
SCD-0001v1.pdf SANmark Program Overview Released
3/21/01 Michael Hoard
SCD-0401vC.pdf SANmark Industry Standards Overview Working Draft
3/22/01 Scott Kipp
SCD-1000 -- Physical & Mechanical
Document Links Document Descriptions Recent Status Control Person
SCD-1001v1.pdf
(previously: SFF-8410.PDF) Cable plant, connectors, transceivers, signal integrity, hubs, enclosures Released
10/12/00 Jay Neer
SCD-2000 -- Port Behavior
Document Links Document Descriptions Recent Status Control Person
SCD-2001vB.pdf
Nx_Ports, Fx_Ports, B-Ports, other port types, multi-protocol ports Test Suite in Development
3/22/01 Bill Martin
SCD-2002vA.pdf NL-Port Conformance Test Working Draft
3/29/01 Stephen Cortese
SCD-2003vC.pdf Nx_port Fabric Attach Working Draft
3/29/01 Bill Martin
SCD-3000 -- Fabric Behavior
Document Links Document Descriptions Recent Status Control Person
SCD-3001vB.pdf E_Ports, fabric distributed services Working Draft Bill Martin
SCD-3002vA.pdf Conformance and Interoperability of FL_Ports 3/22/01 Bill Martin
SCD-3003 Three Switch E_Port Behavior Planned Bill Martin
SCD-3010vA.pdf Registered State Change Notification Working Draft
3/29/01 Dennis De Simone
SCD-3020 Multi-Switch Zoning Planned Scott Kipp
SCD-4000 -- Management Functionality
Document Links Document Descriptions Recent Status Control Person
Middle-ware, system & resource management, diagnostic synthesis Planned
Bill Martin
SCD-5000 -- Fault Tolerance
Document Links Document Descriptions Recent Status Control Person
Multi-path IO, fail-over policies, subsystem robustness, error recovery Planned
Bill Martin
SCD-6000 -- Security
Document Links Document Descriptions Recent Status Control Person
System security policy, authentication, encryption services, practices Planned
Bill Martin
SCD-7000 -- Extended SAN Behavior
Document Links Document Descriptions Recent Status Control Person
Distance connectivity, diagnostics, troubleshooting for LAN, MAN, WAN Planned
Bill Martin
SCD-8000 -- Applications & Solutions
Document Links Document Descriptions Recent Status Control Person
Cluster functionality, copy services, backup, high level system services Planned
Bill Martin
SANmark Trademark License Enforcement Procedures
Complaint lodged. Complaints are made to the FCIA's Secretariat staff and examples of the non-conformance should also be submitted with the complaint. All complaints will be treated confidentially (i.e., the complainant will not be identified).
The FCIA Secretariat staff will investigate within an appropriate time frame based on the urgency of the circumstances of the complaint.
Make determination about the complaint resulting in a brief written report filed in the FCIA office records and included in a report at the next meeting of the board of directors.
If there's a finding of non-conformance, violator will be notified in writing with a request to take certain corrective action.
Secretariat staff will follow up notification to see that the requested action has been taken. If the corrective action has been taken, the written record in the office will be updated accordingly. If it has not been taken the FCIA Secretariat staff will follow up and make every reasonable attempt to resolve the matter. If the FCIA Secretariat staff determines that it can no be resolved through the FCIA office, the matter will be referred to the FCIA's legal counsel for further action.
The board of directors will be notified when any trademark matter is referred to legal counsel. Legal counsel will be instructed to review actions taken by the FCIA Secretariat in the specific matter and asked to contact the violator to try and resolve the matter.
If legal counsel can not resolve the matter satisfactorily, counsel should recommend further action to be considered to resolve the matter to the benefit of the FCIA.
Further action, if any, rests with the board of directors.
The Role of Independent Labs
The SANmark Qualification program is not intended to endorse specific independent testing labs or to certify testing labs for the purposes of administering the SANmark test suites.
Prospective licensees are free to self test, or use any independent lab of their choice.
Presentations
SMK-01-004v0.pdf
SANmark Program Status
February 5, 2001; Michael Hoard
Huntington Beach, CA -- 7 slides
SMK-01-001v0.pdf
SANmark Qualified Program Overview & Strategic Plan
January 16, 2001; Michael Hoard
London - FCIA-Europe Annual General Meeting -- 10 slides
SMK-00-003v0.pdf
SANmark Program Overview
December 4, 2000; Michael Hoard
Austin, TX -- 10 slides
SMK-00-004v0.pdf
SANmark Revision A Plugfest Test Results
December 4, 2000; Bill Martin
Austin, TX -- 5 slides
SMK-00-002v0.pdf
Fibre Channel Interoperability Roadmap
October 4, 2000 -- Michael Hoard
Nashua, NH -- 6 slides ( This one has the proof of FCIA and SNIA putting some muscle into interop)
SMK-00-001v0.pdf
Fibre Channel Interoperability
August 28-30, 2000 -- David Deming & Michael Hoard
FCIA 2001 Annual Meeting
SANmark Tech Working Documents & Minutes
SANmark Style Guide
Licensees of the SANmark trademark are granted permission to name those products meeting the SANmark compliance guidelines and may use the following formats in conjunction with their qualified products:
The minutes of the meetings are very interesting...
BIll Martin of Zoox seems to be overseeing the E-port stuff.
Micheal Hoard is from IBM...
There are PDFs up on the SANmark test for E-ports.....
The newest members are an ecclectic group...
Cereva Networks
Concurrent Computer Corp.(Video servers anyone?)
Grande Vitesse Systems
Texas Memory Systems(what do they see in the FCIA?)
Hats off to you folks! Thanks for all the hard work!
So it seems that as far as fabric goes ZOOX, VXL, MCDT, and QLGC will validate all their SAN stuff(probably about done already) internally, perhaps get an outside lab to make sure that they did it right and put the trademark on.
To the customer the SNIA can support the idea that no one should buy any equipmant that doesn't have the sticker.
If BRCD wants to play ball they will have to get a sticker evenually.
The potential problem as I see it is when a company like BRCD puts a sticker on, but the equipment still doesn't work with the rest, what will happen?
There are documents on the site that already talk about how such problems will be investigated and dealt with.
I think these are BRCD provisions.
ALso if I were a SSP like STOR, or was building data centers I would just say if you want us to use yur stuff it better have a sticker by end of July or no dice. EDS too. Same goes for big storage guys like EMC, CPQ, SUNW. |
