imss WG Last Call: Fibre Channel RSCN, Fabric Config S vr, and Zone Svr MIBs

SMIC strict checking reveals the following:

  C:\bwijnen\smicng\work>smicstrict

  C:\bwijnen\smicng\work>smicng
T11-FC-ZONE-SERVER-MIB.inc
  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (959,15) Row
"t11ZsSetZoneEntry"
  does not have a consistent indexing scheme - cannot
specify an
  index item from additional "base row"
t11ZsSetEntry, since can
  have only one "base row" which is
t11ZsZoneEntry

Keith, what is your comments on this one?

  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2254,20) Variable
"ifIndex"
  in notification "t11ZsMergeFailureNotify" is
an index for a table
  W: f(T11-FC-ZONE-SERVER-MIB.mi2), (2269,20) Variable
"ifIndex" in
  notification "t11ZsMergeSuccessNotify" is an
index for a table

I do not see the above two as fatal flaws. We could pass
ifAlias,
or some other columnar-object of the ifTable I guess. That
would make
the warning go away, and we would be sending extra
information in
the notification.

  C:\bwijnen\smicng\work>smicng T11-FC-RSCN-MIB.inc
  E: f(T11-FC-RSCN-MIB.mi2), (198,5) Missing comma between
sequence
  items

Just add the comma (as stated earlier).

  C:\bwijnen\smicng\work>smicng
T11-FC-FABRIC-LOCK-MIB.inc

is OK

  C:\bwijnen\smicng\work>smicng
T11-FC-FABRIC-CONFIG-SERVER-MIB.inc
  W: f(T11-FC-FABRIC-CONFIG-SERVER-MIB.mi2), (716,15) Row
  "t11FcsPortListEntry" does not have a
consistent indexing scheme
  - index items from current table must come after index
items from
  other tables

Keith, can you comment?

Bert

_______________________________________________
imss mailing list
imssietf.org
https://w
ww1.ietf.org/mailman/listinfo/imss