Serial Number Of Brocade Switch

The Brocade ® ICX 7250 Switch delivers the performance, flexibility, and scalability required for enterprise Gigabit Ethernet (GbE) access deployment. It raises the bar with up to 8×10 GbE ports for uplinks or stacking and market-leading stacking density with up to 12 switches (576×1 GbE) per stack. Obtaining the Serial Number of a Card Log in to the master switch through Telnet or the console interface, and then run the display elabel command in the user view and specify a slot ID according to help information to display the electronic label of a card. The BarCode field in the command output shows the serial number of the card.

SECTION 3: Data required for a new case. INPUT these questions:Customer – If opening a case on the NetApp site, be prepared to discuss these questions with the Technical Support Engineer that works on your case.TSE - Copy/Paste these questions and the customer’s answers into a private case note.

Is the configuration supported? To do this, you must first determine how the switch is being used. Is it for a target SAN, SAN tape, MetroCluster or V-Series?. If used for a target SAN, click to go to Interoperability Matrix Tool.Note: Make sure to change the storage solution to 'SAN-Switch'. If this is a SAN tape, go:.

If this is a MetroCluster, go:. If this is V-Series, download the V-Series support matrix from. You will need to look for the switch in question, and if the Fabric OS level is running. Is this a new switch installation or is this a new issue with an equipment that has worked in the past?. If it has worked before, what changed in the environment? Was the storage system or switch moved? Were there fabric changes?.

Depending on the scenario, has a different cable and port on the switch been tried?. Depending on the scenario, does the host work when directly connected to the storage system?. What type of host is being used? That is, Windows 2K, Sun, UNIX (specify Vendor) for all hosts. Was there an upgrade made to the host?

Or, patches or firmware?. What is the HBA Type, Firmware revision and Driver version for all the hosts?. Were any host's HBA cards replaced or upgraded?

New HBA cards/firmware?. Capture the switch model: switchswitchshow, and look for the digits after.

If using as a FCP target, ensure FCP is licensed and active: filerfcp status. Verify that the storage system port is configured as a target (not an initiator): filerfcp show adapter -v. Is the port on the switch repeatedly coming up, and then going down? Known as flapping.

Are multiple ports or clients affected by this? How many?. Check that the ports are online, logged in. Is zoning enabled? Verify zoning is set to ON.

Identify the zones on the switch: switchcfgshow. Identify the ports in the effective configuration and match the zones to determine if the WWNN (or WWPN) of the host ad storage system are in those zones. Send the serial number or WWN for switch(s) involved in this issue to NetApp. Send a complete topology diagram (specifying the host types and storage types) to NetApp. Send the output of switch supportsave from all the switches involved in the issue. (If the issue can be reproduced, it is preferable to take the supportsave before and immediately after the issue is reproduced).

UPLOAD the required information:If opening a case on the NetApp site and files are under 25 MB, please use:For information on how to UPLOAD files via FTP/HTTP/AsperaConnect, see KB: How to upload a file to NetApp. NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein.

Ready to die album cover. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.