08-04-2008 12:50 AM
swd77:root> ad --show -i
The Fabric is busy, try again later.
No change in switch persistent state
swd77:root> portenable 0
Operation not allowed in AD context
08-04-2008 01:56 AM
U seem to be more experienced than me, but did you notice that the switch is marked faulty and domain unconfigured (quite possible critical errors and failure of POST). I will have a look at the supportsave once he uploads it.
If the switch cannot be replaced then the person can try completely powering off and powering on the system or do fastboot to avoid POST.
08-04-2008 02:04 AM
My verdict replace the switch -
08-04-2008 09:48 PM
is it possible that we can identify which hardware part gone bad, and we can replace that part with new part.
i don't want to replace switch.
from the logs whic i provided, the part whcih is gone bad. is that part is replacable with new part /
08-05-2008 08:14 AM
I just check the supportshow, and your are correct about the error.
But i cannot see in the othyer "errorshow" posted here from shashi similary error....
....it is another story, this was trunkated.
03-30-2011 12:45 AM
I apologize for jumping into this thread. I am new to this forum and new to Brocade switches. I have a question which is, I have 2 Brocade 300 fabrics that is spewing out port 0 domain id overlap. I found a manual that says change domian id on both switches, is this the best method to correct this Warning message and if so what are the impact on production system?
03-30-2011 01:37 AM
This is (was) an old thread conserning old hardware (with) failures in a different situation.
It's better to create your own thread ,explain whats wrong an what you're trying to accomplish.
When you start a new thread please provide some output, like error messages/dumps, perhaps config of switches etc...