This post is more than 5 years old
45 Posts
0
1336
June 24th, 2010 06:00
ECC.6.1 UB7 with Smi Agent 120.10: all port unused on all brocade
hi
I install ECC 6.1UB7 last week and i have a big problem (SR 35382876)
My configuration :
ECC 6.1 UB7
ECC FCC Agent : 6.1.0.7.423 (last version)
Smi Agent 120.10
1 fabric Brocade with 2 12000 FOS v4.4.0e
1 fabric Brocade with 2 24000 FOS v5.0.1b
1/ ECC discover Brocade fabric without problem. It find Name, Model, Revision, WWN, .... -> ok
2/ ECC import all zone + zoneset -> ok
When i want to create a new zone on brocade fabric, ECC dont see Host, Storage .. which are connected on port.
I must to select all fabric to see all host and storage but ecc doesnt say on which fabric are connected
And, all port of brocade fabric are seen like unzoned
Does anyone have the same problem ?
For your information, i dont have problem on Cisco
thanks
ConorLawlor
2 Intern
•
233 Posts
0
June 25th, 2010 04:00
Hi,
I have seeing similar types of issue with port discovery etc.. when NPIV has being enabled on the switches.
Confirm the NPIV feature is enabled / disabled on the Brocade switches you require to discover in ControlCenter 6.1
ControlCenter does not currently support N_Port ID Virtualization (NPIV) and this will cause inconsistent / unpredictable behaviour for switch discovery in ControlCenter resulting in switches not discovering correctly or information not displaying correctly / blank spaces in the console. ( Primus Solution emc180436)
If possible disable the NPIV feature on any Switches/Fabrics you require to discover in ControlCenter.
Remove the switch from ControlCenter and then rediscover them again after this NPIV feature is disabled.
EMC Engineering is currently evaluating what is required to provide support for NPIV in an upcoming release of ControlCenter.
Regards
Conor Lawlor
ConorLawlor
2 Intern
•
233 Posts
0
June 25th, 2010 05:00
Hi,
For the above WARNING mesages review primus solution emc142289
When an API connection is established with the proxy switch in the Fabric, the Switch will start a session with the events manager on the API management station. When the API connection is closed to the proxy Switch, the session to the events manager running on the management station, is closed which results in this error message in the FOS error log. The API always sends out a delete command to the Switch, but when the Switch receives this command, it does not close the event socket as it is waiting for the CLOSE message from the API.
Fixed in Brocade Fabric OS v5.1.0 or later.
The Brocade 12000 & 24000 switches are supported by ControlCenter 6.1 (6.1 support matrix available here (https://support.emc.com/products/ControlCenter)) and Brocade SMI (release notes) as long as they are not proxy for a fabric
Review SMI 120.10 Brocade SMI Agent release Notes page 8 which list the switches which cannot be proxy (http://www.brocade.com/downloads/documents/support_plans/SMIAGENT/120.10.0/smiagent120.10.0_releasenotes_v1.0.pdf)
The following switches are not supported as proxy, since the highest supported firmware for these switches does not meet the minimum requirement for proxy.
Switches Model Maximum Supported Version
Brocade 3000 (HP MSA embedded) FOS v3.2.1
Brocade 3016 (IBM embedded) FOS v5.3.x
Brocade 3014 (Dell embedded) FOS v5.3.x
Brocade 3200 FOS v3.2.1c
Brocade 3800 FOS v3.2.1c
Brocade 3250 FOS v5.3.x
Brocade 3850 FOS v5.3.x
Brocade 3900 FOS v5.3.x
Brocade 24000 FOS v5.3.x
Brocade 12000 FOS v5.0.x
Have you other Brocade Switches in the fabrics besides 12000 & 24000?
Regards
Conor Lawlor
doof1
45 Posts
0
June 25th, 2010 05:00
FOS version of my switch doesnt had npiv support
In switch log, i see
2010/06/24-13:14:24, [EVMD-1001], 91168,, WARNING, , Event session killed, host IP = , port = 4555
andreas.scht
2 Intern
•
219 Posts
0
June 28th, 2010 05:00
Hi,
we had no chance to discover our 24000 (5.3.2c only FC2-16 Blades) with SMI-S in combination with CC6.0. I had to wait until we installed our new 48000. Now switches are discovered by using 48000 as proxy switch.
Regards
Andreas
youngp2
90 Posts
0
July 2nd, 2010 07:00
Looks like there is some good information here. I was just wondering if the original issue was ever resolved or are you still dealing with this issue?
Regards,
Paul Young
EMC Global Services