Company-# Technical Physical Section/table/figure Problem Description
/Editorial Page (not locator
pdf page)
Here's a big one. The year says 2005, but
McDATA-01 E 1 Copyright we're in 2006 now.
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?
Shouldn't you mention platforms and their
McDATA-03 E 5 third paragraph properties too?
Please mention that the Fabric Configuration
McDATA-04 E 5 Fourth paragraph Server is part of the Management Service.
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
McDATA-05 T 5 5.4.2 and 5.4.3 local FCS is accessed.
The last paragraph shouldn't end on the next
McDATA-06 E 9 last sentence page.
McDATA-07 E 9 Imports Tabbing on Imports is odd.
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
t11FcsFabricDiscov the management instance will query the
McDATA-08 T 16 eryStart Switches?
t11FcsFabricDiscoveryTimeOut confuses me
in a similar fashion to McDATA-08. There is
no time limit for how long the FCS stores
configuration data. The FCS should have it all
of the time. The data could be cached by the
management instance for a short amount of
t11FcsFabricDiscov time, but the FCS stores it as long as it is
McDATA-09 T 16 eryTimeOut online.
McDATA-10 T 19 t11FcsIeTable When or how is discovered data invalidated?
is the Node WWN of the switch s/b is the
McDATA-11 E 20 t11FcsIeName Switch_Name of the switch
t11FcsIeFabricNam
McDATA-12 T 20 e fabric name s/b Fabric_Name
information the ports s/b information pn the
McDATA-13 E 25 t11FcsPortTable ports
McDATA-14 E 26 t11FcsPortName WWN of the port s/b Port_Name
The reference to
t11FcsFabricDiscoveryTimeOut needs to be
McDATA-15 T 30 t11FcsPlatformTable removed.
t11FcsTxRscns and t11FcsRxRscns should
not be counted by the FCS. This is more
related to the Name Server and sent from the
McDATA-16 T 38 t11FcsTxRscns Fabric Controller.
t11FcsReqRejectNot t11FcsReqectRejNotify s/b
McDATA-17 E 40 ifyEnable t11FcsReqRejectNotify
t11FcsDiscoveryCompNotifyEnable should
t11FcsDiscoveryCo never be sent because discovery is always real
McDATA-18 T 40 mpNotifyEnable time.
A collection of objects for requesting a Fabric
t11FcsDiscoveryCon Configuration Server to discover the
McDATA-19 T 44 trolGroup configuration is not accurate.
t11FcsDiscoveryStat t11FcsDiscoveryStatusGroup doesn't make
T 45 usGroup sense after all of the other comments.
Suggested solution
Change to 2006 in multiple places in the
document.
If so mention loops.
Add a platform description.
Add a new sentence.
Delete or extremely modify these groups.
See more in McDATA-08/09.
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
change the 72 character/line limit.
Please clarify.
Delete this timer because it is implementation
specific. The FCS must respond to the query
whenever it is made, but caching
requirements are not specified in T11. This
means that the Discovery State Table should
be deleted as well. Usually, only local
information is stored on each switch and
distributed information is acquired at the time
of the query. This affects t11FcsIeTable also.
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.
Delete this notification.
Remove this group.
Remove this group.