Brocade Network Advisor SMI Agent Developers Guide v12.3.0 - Manual (Page 52)

36 Brocade Network Advisor SMI Agent Developer’s Guide
53-1003159-01
Fabric profile
3
• 7 SANActiveConnections corresponding to the discovered switches
- 2 XISLs
- 1 ISL
- 4 LISLs
• Zone databases (size = 1 MB for each fabric) corresponding to the three fabrics.
• All of the classes corresponding to the three discovered fabrics as defined in the Fabric and
other profiles.
To discover the fabric formed by Switch A and logical switch 18 in Chassis 3, the provider must be
configured to connect to either Chassis 3 or Switch A, because the Fabric OS will not provide the
information for these switches if the SMI Agent is connected only to Chassis 2.
The devices connected to ports in a logical switch are discovered in the fabrics to which these
switch ports belong. For example, a device connected to a port belonging to a logical switch with
Fabric ID 1 is discovered only if you have access to Fabric ID 1. Device discovery follows the existing
model in the Fabric profile.
Blades subprofile support
The following model supports the blade subprofile in Virtual Fabrics setup as the blade subprofile
in Virtual Fabrics scenario on a director switch is not specified in SMI-S 1.4:
• There is one instance of Brocade_Blade for each physical blade in the director switch.
• For each Brocade_Blade, there can be multiple Brocade_PortModule instances, depending on
the number of existing logical switches and how the ports are allocated throughout the
chassis.
• The association Brocade_PortModuleRealizes cannot be one-to-one in a Virtual Fabrics
scenario, but one-to-many.
Figure 16 shows a basic instance diagram for a director switch containing two logical switches,
where both the logical switches contain a port from the blade in slot 1.
FIGURE 16 Director switch instance diagram