SM-FSM LB Comment Response

SM-FSM LB Comment Response

-

English
4 Pages
Read
Download
Downloading requires you to have access to the YouScribe library
Learn all about the services we offer

Description

05-356v0 -- Consolidated Comments on SM-FSM Letter BallotCompany-# Technical/ Physical Sectionlocator Problem Description Comment's suggested Proposed Resolution Proposed Editorial Page solution StatusBrocade-01 T 8 5.3 The Fabric Index tutorial Make suggested change.information is either incomplete or too thorough. It explains how multiple virtual fabrics are indexed, but does not indicate how multiple physical fabrics are identified. I assume that they are identified by their fabric name, and if more than one virtual OR physical fabric appears in a single entity, that the index may be other than 1. Suggest completing the tutorial to express this.Brocade-02 T 10 6 T11FspfLsrType allows a Make suggested change.value of 02, indicating an AR summary record. That type is obsolete in FC-SW-4 and should be labeled as such in this MIB, unless another MIB is going to be generated somewhere to explain its behavior.Brocade-03 T 11 6 T11FspfLastCreationTime is a Discuss removal, or non-FC-SW-4 value. It is an alternatively bring proposals object apparently used in into FC-SW-5 that create a multiple places, where the value for it.time is related to sysUpTime, By the way, this resembles which is not imported or the LSR Age function defined anywhere. It also defined in FC-SW-4.falls into that category of parameters created by the MIB not used by Fibre Channel and therefore of uncertain value, availability, or usefulness. It is also not ...

Subjects

Informations

Published by
Reads 23
Language English
Report a problem
05-356v0 -- Consolidated Comments on SM-FSM Letter Ballot
Company-# Technical/
Editorial
Physical
Page
Sectionlocator
Problem Description
Comment's suggested
solution
Proposed Resolution
Proposed
Status
Brocade-01
T
8
5.3
The Fabric Index tutorial
information is either
incomplete or too thorough.
It
explains how multiple virtual
fabrics are indexed, but does
not indicate how multiple
physical fabrics are identified.
I assume that they are
identified by their fabric name,
and if more than one virtual
OR physical fabric appears in
a single entity, that the index
may be other than 1.
Suggest
completing the tutorial to
express this.
Make suggested change.
Brocade-02
T
10
6
T11FspfLsrType allows a
value of 02, indicating an AR
summary record.
That type is
obsolete in FC-SW-4 and
should be labeled as such in
this MIB, unless another MIB
is going to be generated
somewhere to explain its
behavior.
Make suggested change.
Brocade-03
T
11
6
T11FspfLastCreationTime is a
non-FC-SW-4 value.
It is an
object apparently used in
multiple places, where the
time is related to sysUpTime,
which is not imported or
defined anywhere.
It also
falls into that category of
parameters created by the
MIB not used by Fibre
Channel and therefore of
uncertain value, availability, or
usefulness.
It is also not
given a conformance rating
that I was able to find.
Discuss removal, or
alternatively bring proposals
into FC-SW-5 that create a
value for it.
By the way, this resembles
the LSR Age function
defined in FC-SW-4.
DotHill-01
E
Document needs to be nit
checked prior to submitting to
IETF.
See
http://www.ietf.org/ID-
Checklist.html.
Also run ID
nits tool at
http://ietf.levkowetz.com/tools/
idnits/.
McDATA-1
E
15
t11FFspfChecksu
mErrors
"occurred on this in this
Fabric" is wrong.
delete the text in quotes and
the sentence reads well.
We don't need to say "in
this Fabric" all the time.
It's
superfluous.
This happens
in many places and should
be checked for the whole
document.
McDATA-2
T
19
RetransmitInterval What is an unacknlowledged
link update
Change Link Update to
LSU.
McDATA-3
E
23
SetToDefault
every every s/b every
McDATA-4
E
26
Incarnation
Number
with largest incarnation s/b
with the largest incarnation.
McDATA-5
E
30
changes
changes s/b changes
McDATA-6
T
14
LsRefreshTime
LsRefreshTime and
FSPFMaxAge should be read
only since there is no way to
change this on the Fabric at
once.
Change MAX-ACCESS to
Read-only for
LsRefreshTime and
FspfMaxAge.
McDATA-7
T
15
MaxAgeDiscards
Does this include the LSRs
that are discarded on arrival
or just ones that time out on
the Switch.
Any LSR is too
vague.
Instead of specifying any
LSR, specify that it is the
combination of frames that
arrived with an Age of
MaxAge or when an LSR
ages out.
McDATA-8
E
15
PathComputations Is this calculations per Fabric
or Switch?
change "invoked" to
"invoked by this Switch"
McDATA-9
T
15
Checksumerrors
Is this the count of checksum
errors found on the switch or
discarded by the switch or
both.
please specify.
McDATA-10
T
16
FSPF AdminStatus What is the behavior when
FSPF is 'down'?
I don't think
this is standardized, so we
shouldn't have this state.
Remove
t11FspfAdminStatusFSPFif
AdminStatus, and
t11FspfOperStatus.
McDATA-11
T
26
LSRAge
This definition is incorrect
since this is the time since the
LSR originator created it.
Change the description to
reality.
McDATA-12
T
27
LSR Links and
FSPFLinkNumber
LSRLinks and LinkNumber
seem to be the same thing.
What is the difference
between these two?
Please clarify.
VRTS-001
E
5
3
A reference is needed for a
FSPF defininition
Add a reference to [FC-SW-
4] near the bottom of page 5
VRTS-002
E
8
5.3
The first sentence of the last
paragraph implies that a
(single) port of a FC switch is
connected to multiple fabrics?
Is this true? Also such is
unclear given that both
physical and virtual fabrics
are referenced in the previous
paragraph.
It is quite possible, and may
even be likely, that
a
Fibre
Channel switch will have
ports connected to more
than 1 physical or virtual
Fabrics.
VRTS-003
T
8
5.3
The reference to
t11FamFabricIndex is
incorrect
Replace by t11FabricIndex
(see [FC-FAM-MIB]) or
t11fspfFabricIndex as
appropriate.
VRTS-004
E
9
6 IMPORTS
The RTM and VRM MIBS
import InterfaceIndex from the
IF-MIB. Both are correct - is
there a reason for them to be
different?
Make all 3 MIBs consistent
in absence of a reason for
them to be different.
VRTS-005
E
13
REFERENCE
Clauses
The revision of FC-SW-4
referenced is given in the
Normative References. Does
it need to be repeated in each
reference clause?
Remove revision