Brocade resource-type and fcTable collection could be nicer
Description
The swFCPortIndex generic resource type currently lacks a custom resource label, with the result that resources of this type show up in the resource graphs pick-list as just the numeric instance ID corresponding to the port in question. This gives the user no context.
I'm adding a new string object (alias swFCPortSpecifier, OID .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.37) to the brocade-switch-fctable group. Since this object's type is "string", adding it will not break existing store-by-group RRDs. I'm also adding a custom resource label for this type: "FC port ${swFCPortSpecifier}: ${swFCPortName}".
This work was done during the JSI tuning engagement and has been sitting in my clone since then. Sorry, John
Environment
Any system collecting data from a Brocade fibrechannel switch, i.e. sysObjectID starting with .1.3.6.1.4.1.1588
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Jeff Gehlbach May 4, 2011 at 6:14 AM
Changes pushed to 1.8 and hand-picked (with cherry-pick recorded) to multi-file layout in master.
The swFCPortIndex generic resource type currently lacks a custom resource label, with the result that resources of this type show up in the resource graphs pick-list as just the numeric instance ID corresponding to the port in question. This gives the user no context.
I'm adding a new string object (alias swFCPortSpecifier, OID .1.3.6.1.4.1.1588.2.1.1.1.6.2.1.37) to the brocade-switch-fctable group. Since this object's type is "string", adding it will not break existing store-by-group RRDs. I'm also adding a custom resource label for this type: "FC port ${swFCPortSpecifier}: ${swFCPortName}".
This work was done during the JSI tuning engagement and has been sitting in my clone since then. Sorry, John