This post is more than 5 years old
12 Posts
0
2173
November 28th, 2008 08:00
FCC Agents in different Network Zones / Firewall
Hi,
we have Control Center 6.0, and have several SAN Switches (Brocade), which are different Network Zones (different Locations). I have the ControlCenter Server in a Central Zone, with firewall ports for the FCC Agent <-> Server communication open. In each location I have an FCC Agent installed, so it can discover the switches in its location.
The problem is, I cannot force each FCC agent to only discover switches it its location. ECC picks another FCC agent, which cannot reach the SAN Switch I want to discover, as the Firewall blocks it. I don't want to open a whole horde of ports for each individual SAN Switch, and generate excessive traffic on our WAN (I will want to use WLA as well). Is there any way of assigning specific switches to specific FCC Agents, similar to the "Add Permission to Manage" for the Clariion Agent?
Thanks in advance,
Stephen
we have Control Center 6.0, and have several SAN Switches (Brocade), which are different Network Zones (different Locations). I have the ControlCenter Server in a Central Zone, with firewall ports for the FCC Agent <-> Server communication open. In each location I have an FCC Agent installed, so it can discover the switches in its location.
The problem is, I cannot force each FCC agent to only discover switches it its location. ECC picks another FCC agent, which cannot reach the SAN Switch I want to discover, as the Firewall blocks it. I don't want to open a whole horde of ports for each individual SAN Switch, and generate excessive traffic on our WAN (I will want to use WLA as well). Is there any way of assigning specific switches to specific FCC Agents, similar to the "Add Permission to Manage" for the Clariion Agent?
Thanks in advance,
Stephen
No Events found!
seamuscoffey
472 Posts
0
December 1st, 2008 02:00
The FCC Agent uses automatic load balancing and there is no way (that I know of) to assign specific switches to certain FCC Agents. The Planning & Installation Guide states that primary status for an object is based on the following criteria:
ControlCenter uses the following criteria to determine which agent of a particular type is primary. If ControlCenter cannot determine primary status based on the first criterion, it considers the second, then the third, and so on.
1. The agent that has the highest version level (for example, 6.0). The primary agent should have version equal or higher than the version of the agent that last reported data on the managed object to ControlCenter.
2. The agent that has the shortest logical distance to the managed object.]
3. The agent that has the lowest processing load.
4. The first agent located by the ECC Server.
I have already emailed Engineering and await their official confirmation of the above.
Regards,
Séamus Coffey
EMC Global Services
Jurjen_Oskam
56 Posts
0
November 29th, 2008 06:00
It would be quite handy to assign specific switches to specific FCC agents. (Perhaps by configuring each FCC agent to prefer a certain range of IP-adresses, for example.)
What is the current selection algorithm? How does ECC determine which FCC agent will manage which switch?
Jurjen_Oskam
56 Posts
0
December 1st, 2008 06:00
Could you also specify what "shortest logical distance" means?
seamuscoffey
472 Posts
0
December 2nd, 2008 03:00
Shortest logical distance means the minimum number of hops between the FCC Agent and the switch.
Regards,
Séamus Coffey
EMC Global Services
Jurjen_Oskam
56 Posts
0
December 2nd, 2008 03:00
Does this mean the FCC agent performs the equivalent of a traceroute, and counts the number of routers between the agent and a switch?
seamuscoffey
472 Posts
0
December 2nd, 2008 03:00
Regards,
Séamus