SM-FCFGM LB Comment Resolution

Roger Cummings

Description

Comments on SM-FCFGM Letter BallotOriginal Version 06-050v0, dated 1/23/2006Company-# Technical Physical Section/table/figure Problem Description/Editorial Page (not locatorpdf page)Emulex-001 E general The subject of this ballot does not materially 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 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 t11FcsFabricDiscove the management instance will query the ...

Informations

• Publié par: Soob
• Nombre de lectures: 22
• Langue: English

Extrait

Comments on SM-FCFGM Letter Ballot

Original Version 06-050v0, dated 1/23/2006

Company-#

Technical

/Editorial

Physical

Page (not

pdf page)

Section/table/figure

locator

Problem Description

Emulex-001

E

general

The subject of this ballot does not materially

McDATA-01

E

1 Copyright

Here's a big one. The year says 2005, but

we're in 2006 now.

McDATA-02

E

5 third paragraph

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?

McDATA-03

E

5 third paragraph

Shouldn't you mention platforms and their

properties too?

McDATA-04

E

5 Fourth paragraph

Please mention that the Fabric Configuration

Server is part of the Management Service.

McDATA-05

T

5 5.4.2 and 5.4.3

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.

McDATA-06

E

9 last sentence

The last paragraph shouldn't end on the next

page.

McDATA-07

E

9 Imports

Tabbing on Imports is odd.

McDATA-08

T

16

t11FcsFabricDiscove

ryStart

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

the management instance will query the

Switches?

McDATA-09

T

16

t11FcsFabricDiscove

ryTimeOut

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

time, but the FCS stores it as long as it is

online.

McDATA-10

T

19 t11FcsIeTable

When or how is discovered data invalidated?

McDATA-11

E

20 t11FcsIeName

is the Node WWN of the switch s/b is the

Switch_Name of the switch

McDATA-12

T

20 t11FcsIeFabricName fabric name s/b Fabric_Name

McDATA-13

E

25 t11FcsPortTable

information the ports s/b information pn the

ports

McDATA-14

E

26 t11FcsPortName

WWN of the port s/b Port_Name

McDATA-15

T

30 t11FcsPlatformTable

The reference to

t11FcsFabricDiscoveryTimeOut needs to be

removed.

McDATA-16

T

38 t11FcsTxRscns

t11FcsTxRscns and t11FcsRxRscns should

not be counted by the FCS.

This is more

related to the Name Server and sent from the

Fabric Controller.

McDATA-17

E

40

t11FcsReqRejectNot

ifyEnable

t11FcsReqectRejNotify s/b

t11FcsReqRejectNotify

McDATA-18

T

40

t11FcsDiscoveryCo

mpNotifyEnable

t11FcsDiscoveryCompNotifyEnable should

never be sent because discovery is always real

time.

McDATA-19

T

44

t11FcsDiscoveryCon

trolGroup

A collection of objects for requesting a Fabric

Configuration Server to discover the

configuration is not accurate.

McDATA-20

T

45

t11FcsDiscoveryStat

usGroup

t11FcsDiscoveryStatusGroup doesn't make

sense after all of the other comments.

Symantec-001

E

5

3

In the 2nd sentence of the 5th paragraph,

delete the second "it can be".

Symantec-002

E

5

3

In the 2nd sentence of the last paragraph,

replace "specification" by "version".

Symantec-003

E

7

5.3

The sentence "With multiple fabrics, each

fabric has its own mangament

instrumentation." needs clarification. Separate

agents?

Symantec-004

E

7

5.3

The first sentenced of the last paragraph is

unclear.

Symantec-005

T

14

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.

Symantec-006

T

16

6

The description of the

t11FcsDiscoveryStateTable uses the term

"locally-managed switch".

Symantec-007

T

18

6

In the last paragraph of the description of the

t11FcsDiscoveryStatus object, is the discovery

aborted ONLY if it was initiated from this

switch?

Symantec-008

T

19

6

In the Description of the t11FcsIeTable, please

clarify what is meant by "remote topology". The

term is not apparently used in GS-5.

Symantec-009

T

23

6

The description of the t11FcsMgmtListEntry

uses the term "locally-managed switch".

Symantec-010

T

24

6

The description of the t11FcsPortListEntry uses

the term "locally-managed switch".

Symantec-011

T

25

6

The description of the t11FcsPortEntry uses

the term "locally-managed switch".

Symantec-012

T

29

6

The description of the

t11FcsAttachPortNameListEntry uses the term

"locally-managed switch".

Symantec-013

T

30

6

The description of the t11FcsPlatformTable

uses the term "locally-managed switch".

Symantec-014

T

30

6

The description of the t11FcsPlatformEntry

uses the term "locally-managed switch".

Symantec-015

T

34

6

The format in GS-5 of the Management

address referenced in the

t11FcsPlatformSysMgmtAddr object includes a

length field? Is this length field included in the

object?

Symantec-016

T

34

6

The format in GS-5 of the Management

address referenced in the

t11FcsPlatformCLusterMgmtAddr object

includes a length field? Is this length field

included in the object?

Symantec-017

T

35

6

The description of the

t11FcsNodeNameListEntry uses the term

"locally-managed switch".

Symantec-018

T

36

6

The description of the t11FcsStatsEntry uses

the term "locally-managed switch".

Symantec-019

E

20

8

Reference Scott as T11.5 Vice Chair

Symantec-020

T

21

9

FS-NS-MIB missing from list of references.