NSM-MIB INDEX-ing INDEX-ing still under discussion Primary issue is that FC standards describe having one Name Server (per fabric): implementation is often distributed, e.g., on each switch does MIB need to represent registered info on a per-location basis? statistics+state are different at different locations. Latest draft has: fcmInstanceIndex & fcmNsIndex – likely to change and FabricIndex for registration info, stats & rejects |