SAN Health Utility

Reply
N/A
Posts: 1
Registered: ‎05-30-2011

DCX switches are shown as if nothing were connected to them

Hello,
I've run a SAN Health in a customer's site and found that the DCX switches are shown as if nothing were connected to them, what is false.
I think problem would be because we've virtual fabrics in these DCXs switches, are Virtual Fabrics in DCX supported by SAN Health?
Everything else was fine, McData switches through EFCM server, old Brocade switch, but the problem is with the DCX and DCX-4S in our SAN.
It's possible that hetereogeneus fabrics aren't supported either?
I've been searching in your communities but I haven't found any similar problem.
Any idea???
Moderator
Posts: 206
Registered: ‎07-21-2009

Re: DCX switches are shown as if nothing were connected to them

Hi huete_vicente,

If you haven't already received the answer to this question, here it is below. 

Regards,

HealthDude

VFs are supported, just make sure you point SAN Health at every switch's IP address including each Logical switch.
Each virtual fabric needs to have a user ID that is set to manage it.  You then use that user ID and the IP address of each logical switch in SAN Health.
Here's what we tell our customers with VF questions:
Understanding how SAN Health works against Virtual Fabrics and Logical switches.

SAN Health works against any switch, be it physical or logical, by connecting under the provided user context to the IP Address of the management port of that switch and discovering what that switch/user context knows about for its given fabric.
Therefore to discover logical switches and virtual fabrics, you need to log into an IP address that is assigned to the logical switch under a user ID that is set to manage the given Fabric ID (Home FID).
Unlike Cisco VSANs where the VSANs are effectively just a visualization layer as all processes run under the same set of daemons, Brocades logical switch implementation runs completely separate daemons for each logical switch keeping the logical switches truly partitioned. E.g. Brocade runs a separate name server daemon for each logical switch where Cisco runs just one for all supposedly separate VSANs.  This means that if, for example, SAN health wants to retrieve the name server information for a given logical switch it needs to login to that specific logical switch just as it would a physical switch. This is because Brocades logical switch is true partitioning rather than just a presentation layer mapped over the same software processes as Cisco VSANs do.
For specific configs on a given logical switch SAN Health must log into each switch to retrieve information, however if you're not looking to drill into the specifics of a given logical switch or virtual fabric, connecting to any of the switches in the environment will also map out the higher level view for the virtual fabric setup.
Note that on the Visio diagram we do not try to collapse the logical switches down onto the physical switch that they originate from as the diagram becomes difficult to interpret.  We found that it's far easier to read and more useable to simply present each Virtual fabric and group of logical switches as an entity of their own. i.e. we draw each virtual fabric out separate from each other.
Importantly note that it is always best to try and capture the entire virtual fabric environment in a given SAN Health Audit Set.  When we generate the report we attempt to cross relate all of the components (physical, logical and base switches).  When all components are included in the BSH file the report generator can do a better job of this improving the quality of the report.
-------------------------------------------
For specific commands required to configure virtual fabrics, please refer to the following and to the Command Reference Manual.
ipaddrset -ls FID --add IPv4_address/prefix
ipaddrset -ls FID --delete
-ls FID
Specifies the logical fabric ID for which to configure an IPFC network interface. The FID is a decimal number. A switch that is not in Virtual Fabric mode uses the -ls parameter with FID 128 (the effective, single Logical Fabric number on such switches) to set the IPv4 FC address.
--add
Assigns a specified IPv4 FC address and prefix to the logical switch instance represented by the specified FID. This command replaces any existing FC IPv4 address.
IPv4_address/prefix
Specifies the IPv4 address and prefix for the IPFC network interface. The IP Address is represented by a dotted decimal number, followed by a slash and a prefix. This operand is required with the --add option.
--delete
Deletes the IPv4 FC address and prefix from a logical switch.
-ls IFID
Specifies the fabric ID that identifies the logical switch for which to delete the FC IPv4 address and prefix. This operand is required when deleting an FC IPv4 address from a logical switch. On a switch that is not in Virtual Fabric mode, use the -ls parameter with FID 128 (the effective, single Logical Fabric number on such switches) to delete the IPv4 FC address.
--

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook