SM-FCFGM Letter Ballot Comment Resolution, Rev 2 06-050v2, dated 4/5/2006Company-# Tec Physical Section/table/figure Problem Description Suggested solutionhnic Page locatoral (not pdf The subject of this ballot does not materially Emulex-001 E general affect our organization.Here's a big one. The year says 2005, but Change to 2006 in multiple places in the McDATA-01 E 1 Copyright we're in 2006 now. document.What does it meant for an Nx_Port to be connected to Nx_Ports outside of the physical McDATA-02 E 5 third paragraph fabric? Are you talking about NL_Ports? If so mention loops.Shouldn't you mention platforms and their McDATA-03 E 5 third paragraph properties too? Add a platform description.Please mention that the Fabric Configuration McDATA-04 E 5 Fourth paragraph Server is part of the Management Service. Add a new sentence.These groups are incorrect because a Fabric Configuration Server should not be told to discover. The Discovery is always real time and replies should not be sent out unless the Delete or extremely modify these groups. McDATA-05 T 5 5.4.2 and 5.4.3 local FCS is accessed. See more in McDATA-08/09.The last paragraph shouldn't end on the next McDATA-06 E 9 last sentence page. Connect the sentence.At least correct spacing on From T11-TC-MIB. It would probably be better to have the IETF use longer lines, so have the IETF McDATA-07 E 9 Imports Tabbing on Imports is odd. change the 72 character/line limit ...
SMFCFGM Letter Ballot Comment Resolution, Rev 2 06050v2, dated 4/5/2006
Tec Physical Section/table/figure hnic Page locator al (not pdf
E
E
E
E
E
general
1 Copyright
5 third paragraph
5 third paragraph
5 Fourth paragraph
Problem Description
The subject of this ballot does not materially affect our organization. Here's a big one. The year says 2005, but we're in 2006 now.
What does it meant for an Nx_Port to be connected to Nx_Ports outside of the physical fabric? Are you talking about NL_Ports?
Shouldn't you mention platforms and their properties too?
Please mention that the Fabric Configuration Server is part of the Management Service.
Suggested solution
Change to 2006 in multiple places in the document.
If so mention loops.
Add a platform description.
Add a new sentence.
McDATA05
McDATA06
McDATA07
T
E
E
5 5.4.2 and 5.4.3
9 last sentence
9 Imports
These groups are incorrect because a Fabric Configuration Server should not be told to discover. The Discovery is always real time and replies should not be sent out unless the local FCS is accessed. The last paragraph shouldn't end on the next page.
Tabbing on Imports is odd.
Delete or extremely modify these groups. See more in McDATA08/09.
Connect the sentence. t least correct spacing on From T11TC MIB. It would probably be better to have the IETF use longer lines, so have the IETF change the 72 character/line limit.
McDATA08
McDATA09
McDATA10
McDATA11
McDATA12
McDATA13 McDATA14
McDATA15
T
T
T
E
T
E E
T
t11FcsFabricDiscoveryStart doesn't seem to correlate with GS. A Fabric Configuration Server is only on a single Fabric. So you shouldn't be able to tell it to discover on multiple Fabrics. It seems odd to tell a Fabric Configuration Server to start discovery since it is part of Nx_Port login. Are you saying that the IE will query end devices or are you saying t11FcsFabricDiscove the management instance will query the 16 ryStart Switches? Please clarify.
Delete this timer because it is implementation t11FcsFabricDiscoveryTimeOut confuses me specific. The FCS must respond to the query in a similar fashion to McDATA08. There is no whenever it is made, but caching time limit for how long the FCS stores requirements are not specified in T11. This configuration data. The FCS should have it all means that the Discovery State Table should of the time. The data could be cached by the be deleted as well. Usually, only local management instance for a short amount of information is stored on each switch and t11FcsFabricDiscove time, but the FCS stores it as long as it is distributed information is acquired at the time 16 ryTimeOut online. of the query. This affects t11FcsIeTable also.
19 t11FcsIeTable
20 t11FcsIeName
When or how is discovered data invalidated? is the Node WWN of the switch s/b is the Switch_Name of the switch
20 t11FcsIeFabricName fabric name s/b Fabric_Name information the ports s/b information on the 25 t11FcsPortTable ports 26 t11FcsPortName WWN of the port s/b Port_Name The reference to t11FcsFabricDiscoveryTimeOut needs to be 30 t11FcsPlatformTable removed.
Delete this reference.
I think the formal Fibre Channel name should be used when possible. This applies to Fabric_Name, Switch_Name, Port_Name, Logical Name, Platform Name etc. Fibre Channel capitalizes names to give them differentiation. It would be helpful.
This distinguishes it from the Node_Name.
McDATA16
McDATA17
McDATA18
McDATA19
McDATA20 Symantec001
Symantec002
Symantec003
Symantec004
T
E
T
T
T E
E
E
E
5
5
7
7
t11FcsTxRscns and t11FcsRxRscns should not be counted by the FCS. This is more related to the Name Server and sent from the 38 t11FcsTxRscns Fabric Controller. t11FcsReqRejectNot t11FcsReqectRejNotify s/b 40 ifyEnable t11FcsReqRejectNotify t11FcsDiscoveryCompNotifyEnable should t11FcsDiscoveryCo never be sent because discovery is always real 40 mpNotifyEnable time. Delete this notification. collection of objects for requesting a Fabric t11FcsDiscoveryCon Configuration Server to discover the 44 trolGroup configuration is not accurate. Remove this group.
t11FcsDiscoveryStat t11FcsDiscoveryStatusGroup doesn't make 45 usGroup sense after all of the other comments. 3 In the 2nd sentence of the 5th paragraph, delete the second "it can be".
3
5.3
5.3
In the 2nd sentence of the last paragraph, replace "specification" by "version". The sentence "With multiple fabrics, each fabric has its own mangament instrumentation." needs clarification. Separate agents?
The first sentenced of the last paragraph is unclear.
Remove this group. "The Fabric Configuration Server is designed so that it can be distributed among switches and accessed from any Nx_Port.
"The latest version is [FCGS5]."
Clarify.
Suggest "In a fabric conformant to FC switch standards prior to FCSW4 ."
Symantec005
Symantec006
Symantec007
Symantec008
Symantec009
Symantec010
Symantec011
Symantec012
Symantec013
Symantec014
T
T
T
T
T
T
T
T
T
T
14
16
18
19
23
24
25
29
30
30
6
6
6
6
6
6
6
6
6
6
The description of the t11FcsFabricDiscoveryTable is the first instance of the use of the term "locally managed switch". This needs some clarification, and possible some definition in section 5. I also don't remember this term being used before. Is it intended to mean the switch on which the FCS is implemented etc. The description of the t11FcsDiscoveryStateTable uses the term "locallymanaged switch".
In the last paragraph of the description of the t11FcsDiscoveryStatus object, is the discovery aborted ONLY if it was initiated from this switch?
Clarify
Clarify
Clarify and add additional text if necessary.
In the Description of the t11FcsIeTable, please Clarify clarify what is meant by "remote topology". The term is not apparently used in GS5.
The description of the t11FcsMgmtListEntry Clarify uses the term "locallymanaged switch". The description of the t11FcsPortListEntry uses Clarify the term "locallymanaged switch". The description of the t11FcsPortEntry uses Clarify the term "locallymanaged switch". The description of the Clarify t11FcsAttachPortNameListEntry uses the term "locallymanaged switch". The description of the t11FcsPlatformTable Clarify uses the term "locallymanaged switch". The description of the t11FcsPlatformEntry Clarify uses the term "locallymanaged switch".
Symantec015
Symantec016
Symantec017
Symantec018
Symantec019
Symantec020
T
T
T
T
E
T
34
34
35
36
20
21
6
6
6
6
8
9
The format in GS5 of the Management Change reference to include the Management address referenced in the Address Value in GS5 section 6.2.3.2.7 t11FcsPlatformSysMgmtAddr object includes a length field? Is this length field included in the object?
The format in GS5 of the Management address referenced in the t11FcsPlatformCLusterMgmtAddr object includes a length field? Is this length field included in the object?
The description of the t11FcsNodeNameListEntry uses the term "locallymanaged switch". The description of the t11FcsStatsEntry uses the term "locallymanaged switch". Reference Scott as T11.5 Vice Chair
FSNSMIB missing from list of references.
Change reference to include the Management Address Value in GS5 section 6.2.3.2.7
Clarify
Clarify
T11.5 ViceChair: Scott Kipp, McData. T11.5 members. Add reference
editor's response
accepted
accepted accepted it's not referring to NL_Ports; will rephrase to change "ports outside the fabric" to "Nx_Ports" accepted will add a sentence: "Each platform may have attributes including its name "
accepted
agreement at T11.5 meeting on 2/8/2006
agreed
agreed
agreed
agreed
Final status as of 4/5/2006
no change
done
done
done
done
rejected these groups are an optional means to manage "local data copies" as described in SW4; specifically, GS5's section B.6.4.2 (informative) points to SW3, and section 9.4.1 of SW4 says "The dMS within the Entry Switch services the request by making any needed requests of other dMS contained by the other Switches, if the required information is not available locally" and "A dMS may maintain local data copies, and a dMS shall notify other dMS that they should remove local data copies". Also note that FCS commands (section 6.2.5 in GS5) have lots of Gets but only a few Registers so to be reviewed by the approved (at info can not be distributed submitter of the 4/5/06 at registration time, comment meeting)
accepted
accepted
agreed
agreed
done
done
related to McDATA05
related to McDATA05
related to McDATA05
accepted
accepted
accepted accepted
related to McDATA05
to be reviewed by the approved (at submitter of the 4/5/06 comment meeting)
to be reviewed by the approved (at submitter of the 4/5/06 comment meeting) to be reviewed by the approved (at submitter of the 4/5/06 comment meeting)
agreed
agreed
done
done
agreed done agreed done to be reviewed by the approved (at submitter of the 4/5/06 comment meeting)
tobediscussed
accepted
related to McDATA05
related to McDATA05
related to McDATA05
accepted
accepted
accepted "With multiple fabrics, each fabric has its own instances of the fabric related management instrumentation.
accepted
agreed to remove RSCNrelated counters from this MIB (and add to RSCNMIB).
done
agreed done to be reviewed by the approved (at submitter of the 4/5/06 comment meeting) to be reviewed by the approved (at submitter of the 4/5/06 comment meeting) to be reviewed by the approved (at submitter of the 4/5/06 comment meeting)
agreed
agreed
agreed
agreed
done
done
done
done
accepted will delete "locallymanaged" accepted is "all known fabrics" or "all locally known fabrics" unambiguous ??
agreed
will use "locally known fabrics"
accepted yes, will clarify that it can only be set when the discovery was initiated from this switch agreed accepted local (e.g., on the local switch) topology is always present in the table; Will clarify agreed accepted will delete "locallymanaged" agreed accepted will delete "locallymanaged" agreed accepted will delete "locallymanaged" agreed
accepted will delete "locallymanaged" accepted will delete "locallymanaged" accepted will delete "locallymanaged"