12-05-2006 01:41 PM
These are appearing when I connect to the switch. Its a silkworm 3800 running v3.2.1. The switch appears to be operating normally. They are annoying. Can anyone tell me what they are and why I am getting these? They will go away if I enable "rapid" but I don't want that running if posible.
12-06-2006 10:52 AM
The errors go away when the configuration parameter "rapid" is enabled. They reappear when it's disabled. It will happen on any switch, so it's not a hardware issue. I all ready checked through all the available documenation, which was pretty useless. I wanted to know if anyone had any more insights to these errors.
12-07-2006 07:26 AM
Let's look at this from the perspective of any generic program. SEMTAKE => take a semafore. What does that mean, a semafore is an autonomous object in an operating system used for synchronization. Basicially its job is to only allow a single process or thread to access a critical section of code at a time. SEMGIVE => release the semafore, allow someone else to take the semafore and access the code. So, in this case, the error is probably caused by a piece of code trying to take/give a semafore that is not set up. Once you start rapid the semafore is setup and no error messages are given.
12-07-2006 07:37 AM
In response to f_det ...Thanks for the explanation. I pretty much assumed that all ready. However, it doesn't explain how to get rid of the messages without enabling the rapid service. I do not want that running on my switches.
12-14-2006 08:39 PM
I think we both know what rapid is right? If you have your switches behind a firewall, block port 111 and then no one will be able to make a connection, then you can enable rapid and get rid of the messages. Rapid is fairly benign when no one makes a connection to it.
12-18-2006 02:31 PM
By turning the rapid service "on" the messages go away. When it's disabled, the messages return. I can leave it on, but since I do not need or want this service running, I should be able to turn it off. If there is anyone from Brocade out there, please fix this in your firmware or take out the option to disable/enable it. <!