In a Brocade environment the “switchshow” is one of the most used commands out there. It provides a quick overview of what the state of the switch is, switch name, switch attributes and a list of all ports and states. It had however its limitations which, with later codelevels, can be corrected.
About two months ago I received my new shiny Marshall Stanmore multiroom smartspeaker. I’ve been dubbing between this one and a Sonos for a long time but when…
In 2008 Brocade announced the 8G director class switches DCX and DCX-4S. A rather impactful release of a new piece of hardware where the next generation FC ASIC saw light. The Condor.The marketing department of Brocade back then had probably been smoking something as the introduction of the platform was accompanied with a rather cringy “Marvel-like” super-hero called DCX-man. (uhhhhh… shivers….)
Whenever things goes haywire on an OS or application there are two areas that are looked at first:
In a fair few cases the issue is founded to be external from the host systems but when it comes to performance related problems from a storage perspective the entire IO-stack is at play.
If you’ve read my articles over the last decade or so you’ve seen I’m keen on maintenance. Both from a physical hardware as well as software perspective a storage environment needs to be kept in tip-top shape at all times.
I’ve already mentioned that BNA was End-of-Life and will/is (be) replaced by SANNav.
As of the time of this writing any BNA version older than 14.4.1 is no longer supported. This basically means that your BNA (or any OEM version) older than that release is not being looked at when yo have a problem with it.
A while ago I wrote an article whereby I provided an OpenDNS resolver server via DHCP to the computers, tablets and phones of my kids. (See here). This worked very well and I have been able to keep the nastiness of the web out of sight. Plus it gave me the option to block certain sites which were not captured under a certain category or, if those domains fell under a category that also included a lot of useful domains, exclude them.
Whenever you’ve encountered an output of a nameserver entry you may have come across the phenomenon that the fabric has no clue what the attached device is. For a FC switch an attached device (or N-port in technical terms) is not more than a source or destination where frames originate from or can be sent to. As soon as smarter functions are required it may be helpful (or required) to be able to obtain more information from that device.