Bug 429327
| Summary: | IPMI hardware steals ports; bind to these ports so that they are not used by accident | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Jeff Moyer <jmoyer> | ||||
| Component: | OpenIPMI | Assignee: | Jan Safranek <jsafrane> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.6 | CC: | agospoda, jlayton, pknirsch | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-02-11 14:10:51 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jeff Moyer
2008-01-18 18:25:10 UTC
Created attachment 292182 [details]
code to bind to an ipmi port
Phil, As mentioned, this problem affects our internal test environment. It would be of great help to us if this problem was addressed. It's been suggested to me that the IPMI hardware should not be configured to use the same IP address as the host. That makes a lot of sense to me, but it appears that there are at least some installations that do not heed that advice. Can you comment on what you feel is an appropriate fix for this problem? Thanks. Thats a tricky problem. Of course the right choice is to have different IP addresses, but as you mentioned in the real world this sometimes doesn't happen. A possible solution that we're looking into for Fedora 10 at the moment is a daemon called portreserve. With this services can at bootup time reserve specific ports that won't be randomly allocated by other apps or services and can actively be "claimed" later when the system is running and the specific service needs the port to operate. This could be used to basically reserve those 2 ports automatically during bootup. The chances though that this change will make it into RHEL-4 is highly unlikely as it quite drastically changes bootup behavior. Possibly for RHEL-5 but the main aim is to have it for RHEL-6. Hope this clears it up a bit. Read ya, Phil I think portreserve is a decent solution (as long as someone takes the 5 minutes to extend it to support UDP as well since IPMI uses UDP). I don't think this would be a terrible idea in RHEL either. Once in rawhide maybe EPEL would be a good place to try it out? That sounds definitely reasonable. As soon as we have something ready i'll update the bugzilla here. Read ya, Phil We're now shipping portreserve in Fedora 10, so please take a look at that and report if that would fix your problems. Thanks, Read ya, Phil Does portreserve now contain support for udp ports as well? If it's still tcp only that isn't helpful for this problem. I'll ping the engineer that is taking care of it. Read ya, Phil Ok, portreserve in the current form in Fedora supports TCP and UDP ports, so you should all be set. If you have any more detailed questions about portreserve please send an email to Tim Waugh <twaugh>, the maintainer of the package. Thanks, Read ya, Phil I think this has been sufficiently addressed. I have a program that does this reservation for my test infrastructure. I think you can close this as nextrelease or whatever seems appropriate. Thanks! Alright, closing this as nextrelease then. Thanks Jeffrey. |