Unable to recognize Ethernet Switch or Compute Nodes with Frontend (Rocks Cluster 6.2)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to recognize Ethernet Switch or Compute Nodes with Frontend (Rocks Cluster 6.2)
Hello,
I've installed Rocks Cluster 6.2 with CentOS 6.6 onto the Frontend. I am using an HP Procurve Ethernet Switch, which is plugged into the Frontend and 19 Compute Nodes.
When I type 'insert-ethers' I select Ethernet Switch and after waiting longer then 10 minutes nothing has appeared. Thinking there was a problem with the Ethernet Switch I plugged the Frontend directly into the Compute 0-0 Node, then I selected Compute and turned on the Node (selecting PXE Boot), and still nothing happens.
Typically if I were to have a question, I'd wait about 24 hours to see if anyone has any thoughts, sometimes questions are very complex and unique where someone else really hasn't encountered this problem.
Myself I have no experience with that software, except whatever I can learn via general web search.
Perhaps there are log files which you can identify and add as replies to your question, which may help someone evaluating your problem for a possible solution.
I know that for things like XServer, where I've done very out of the box type of modifications, the log file was very full of information, and much of it was "I:" type of reports, or "W:" for Info or Warning, but eventually I found "E:" where it was Errors and those did help me to zero in on modifying my configuration to get my intentions to work, or at least it informed me that my latest attempt was not working, and approximately what line in my config file was the problem.
Perhaps if there are log files for Rocks Cluster, this can help you find out if it cannot communicate with the switch and give you an idea what it feels the problem is.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
First of all, are all your network interfaces up. The OS doesn't need to recognize an Ethernet switch. The switch is on it's own. The network interfaces communicate directly to it. It has its own OS.
All the interfaces are up,the frontend and compute nodes are plugged into the ethernet switch and the lights by the ethernet ports are orange. Ive tried unplugging and re-plugging them in to no avail
If a mini-GBIC installed in a slot then the, associated RJ-45 port is disabled
If you are using fiber optics with mini-GBIC then this will require special configurations as shown in the manual. If you have your active RJ-45 in the disabled port then this could be the issue.
You can use the LED chart in the manual trouble-shooting section to identify the state of the switch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.