This post is more than 5 years old
16 Posts
0
1808
Brocade switch discovery in 3.6.1.1
Hi All, in a 3.6.1.1 environment (planned to update to 3.6.1.2 in January) we have to expand the discovered object; expecially, we have to discover Brocade via CMCNE Provider. It is a big SAN, with Core - Edge configuration and Access Gateway for ESX blades. Is it possible to discover only Cores in the CMCNE? All storage and hosts involved in provisioning are connected to this kind of switches.
Thanks,
Andrea
julien3192
38 Posts
0
December 21st, 2017 08:00
All switches that belong to the fabric will indirectly be discovered, ie. Core + Edge switches.
Access Gateways are not "joining" the fabric, hence not discovered.
You don't really need to wonder much, the discovery from CMCNE is all done over IP to the Core /seed switch who knows all the other switches over FC protocol. This is very common configuration and it works fine !
What is your concern exactly?
julien3192
38 Posts
0
December 21st, 2017 08:00
Hi,
Actually you discover CMCNE in VIPR, and a prereq is CMCNE must discover fabrics via seed switches (usually you set up the core switches). VIPR is then able to discover the fabrics (switches, FC nodes, zoning...etc). Any zoning performed by VIPR is sent to CMCNE, which is then handling the request.
Hope that helps!
deruva
16 Posts
0
December 21st, 2017 08:00
I was concerned about the possible discovery of AG through Cores....that's enough, thanks!
deruva
16 Posts
0
December 21st, 2017 08:00
Thanks Julian, but if I insert into CMCNE the seed switch (core), all edges and access gateways connected to it will be discovered by ViPR? Or only switches in the same fabric of the core?