I am running Fabric Manager 3.1(2) to manage a pair of MDS 9509s. Every time I start the application, it discovers the fabric and gives it a new name with the next highest number than it used the last time. e.g., if it was called Fabric 2 last time I ran it, on the next startup of the application, it calls it Fabric 3. It really doesn't hurt anything, but there doesn't seem to be a point to it and it seems like it shouldn't happen.
Thank you for your reply. I looked at these and I don't see anything that seems to address this issue. It's possible that I'm missing something. Could you direct me specifically to what you're referring to?
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...