HPE EVA Storage
1819802 Members
2889 Online
109607 Solutions
New Discussion

Zone Admin and SwitchExplorer on Brocade switches disagree as to which zone config is effective

 
David Moczygemba
Occasional Advisor

Zone Admin and SwitchExplorer on Brocade switches disagree as to which zone config is effective

Zone Admin tool and SwitchExplorer disagree as to which zone configuration is effective. I'm trying to determine if this is a problem.


Fabric "B" Environment:
Two HP/Brocade switches (8/16 ports, 1 principle & 1 subordinate)both running V5.2.0b.

Zoning has been enabled for two years. Last change added new host in August 2007 (zoning config_2007_1118)

Most recently, turned-up four more ports for two additional hosts and through Zone Admin, enabled the new zone config early Sunday morning (config_20080416) on the "B" Fabric.

As of this morning (24 hours later), Zone Admin confirms the effective zone config is the new one, config_20080416. However, the lowerleft corner of SwitchExplorer's default view from both switches is still showing the effective config as being config_20071118 which I think should have already changed by now. There's some i/o underway but the switches aren't all that busy.

Any opinions/ideas as to why SwitchExplorer hasn't yet updated/ is this a problem and what I might be able to do about it would be greatly appreciated as I have very limited experience in FC SAN area.

Fabric "A" remains unchanged.

Both Fabrics appears to be working normally and our storage (EVA6000 2c8d) now sees the new HBAs so the true effective config appears to be the newest one (config_20080416) as reported by Zone Admin.

Both switches event log report "The effective configuration has changed to config_20080416) It's just SwitchExplorer default webpage which disagrees as far as I can tell.

Thank you in advance! -David
1 REPLY 1
TTr
Honored Contributor

Re: Zone Admin and SwitchExplorer on Brocade switches disagree as to which zone config is effective

I had the same problem with two 16port Brocade (Brocade label) switches. After I noticed it, I confirmed that the config that is reported by the zoneadmin is the actual one in effect and I rebooted the switches a couple of times but it made no difference.

A firmware upgrade might fix this but I did not have the time to do it.