Unsolved
This post is more than 5 years old
29 Posts
0
1555
December 8th, 2008 15:00
Getting a system busy error when attempting to discover Cisco switches
Sorry for the fairly long post but I do have a question at the end...
I have installed a new ECC 6.1 infrastructure last week and made sure that all the latest patches were applied (I think the latest one was 4432). My ECC environment has two FCC agents running on two different OSes (SPARC Solaris 10 and Windows 2003).
One problem that I ran into was getting the following error message when trying to discover Cisco switches:
"The system is busy. Please perform this task later."
The strange thing was that this happened after I had already successfully discovered some Cisco switches. At first I thought it was because I had overloaded my FCC agents when attempting to add all the Cisco switches one by one. I waited for about half an hour and tried again with the same result.
I found that by stopping the Windows FCC agent (picked because it was easier to look at the log on the Solaris server) I was able to add the rest of the Cisco switches. However, the moment I started the second FCC agent, I got the same system busy error again.
I initially opened a case with EMC and then informed them about this issue. They have stated that since I am using enhanced zoning on the Cisco switches, that could be the cause of the problem and since enhanced zoning is not supported, they may not be able to troubleshoot further.
However, I don't think this is related to enhanced zoning because I am able to discover the switches when only one FCC agent is running. So I wanted to find out whether any one else had run into this problem and whether this was caused by something that I had set up incorrectly when installing ECC.
Thanks.
I have installed a new ECC 6.1 infrastructure last week and made sure that all the latest patches were applied (I think the latest one was 4432). My ECC environment has two FCC agents running on two different OSes (SPARC Solaris 10 and Windows 2003).
One problem that I ran into was getting the following error message when trying to discover Cisco switches:
"The system is busy. Please perform this task later."
The strange thing was that this happened after I had already successfully discovered some Cisco switches. At first I thought it was because I had overloaded my FCC agents when attempting to add all the Cisco switches one by one. I waited for about half an hour and tried again with the same result.
I found that by stopping the Windows FCC agent (picked because it was easier to look at the log on the Solaris server) I was able to add the rest of the Cisco switches. However, the moment I started the second FCC agent, I got the same system busy error again.
I initially opened a case with EMC and then informed them about this issue. They have stated that since I am using enhanced zoning on the Cisco switches, that could be the cause of the problem and since enhanced zoning is not supported, they may not be able to troubleshoot further.
However, I don't think this is related to enhanced zoning because I am able to discover the switches when only one FCC agent is running. So I wanted to find out whether any one else had run into this problem and whether this was caused by something that I had set up incorrectly when installing ECC.
Thanks.
No Events found!
seamuscoffey
472 Posts
1
December 9th, 2008 00:00
Enhanced zoning is definitely not supported in CC 6.1.
Did you give the second FCC Agent a chance to become primary for some of the switches once it was started? Maybe the 'system busy' error was fired because the agent was still initializing.
Regards,
Séamus Coffey
EMC Global Services
g.srinivasan
29 Posts
0
December 9th, 2008 15:00
Thanks for the response. I'm not too concerned about enhanced zoning because I don't plan on using ECC to create zones and zonesets.
The second FCC agent did show some of the connectivity components as primary. I even waited until the following day to retry the operation and it still failed. However, the moment I turned off one of the FCC agents, the discovery worked like a charm.
seamuscoffey
472 Posts
0
December 10th, 2008 00:00
Technical Support probably need to take a further look at this because the issue has nothing to do with the enhanced zoning feature.
Regards,
Séamus
g.srinivasan
29 Posts
0
December 31st, 2008 13:00
But in case there are others who have this issue, one workaround I have found is to have a single instance of the FCC agent running (stop the other FCC agents on other servers) and then discover the Cisco switches.
This always works and once the switches have been discovered, the other FCC agents can be re-started. Since 6.1 has the load balancing feature, the other agents will eventually get their share of connectivity devices assigned to them.
I do have two new switches that I am going to test with. I have turned off the enhanced zoning feature on all the VSANs on the two switches. I should be able to discover the two switches without getting the system busy error.
I'll update this thread with the results of the tests and with any EMC response.
tazal
59 Posts
0
January 28th, 2011 08:00
Digging up an old thread but if you're around still did you get this error when just the windows FCC agent was running? I'm trying to figure out if the problem was purely with 2 FCC agents or more related to the windows FCC agent?
Thanks
g.srinivasan
29 Posts
0
March 25th, 2011 03:00
It's been a while but the problem happened even with just the Windows FCC agents running. From the newer documentation (or perhaps I didn't read the earlier documentation carefully enough) I think EMC recommends not having more than 2 FCC agents anyway. So my current ECC infrastrucure has two FCC agents, both running on Windows. I haven't run into the problem again but since I've had to remove enhanced zoning (to enable other Cisco features) I am not really sure what fixed the problem in the end.