Tips and tricks: What TCP/IP ports are required to be open on an RHN Satellite, Proxy or Client system?

30 September 2008, 6:10 am

For Satellite: If the Satellite server is “connected”, then it will initiate outbound connections to ports 80 and 443 on the Red Hat Network (RHN) hosted service (rhn.redhat.com / satellite.rhn.redhat.com). Access to these hosts and ports should not be restricted to ensure correct functioning of the satellite system. If required, an HTTP(S) proxy may be used, by passing the “–http-proxy” option to the “satellite-sync” command. If using a proxy server, Satellite will initiate connections to port 5222 on each proxy server connected. This is used for communications relating to the “OSA” service (also known as “Push to Client“). If using the OSA service, access to this port should not be restricted. A Satellite service will also connect to individual client systems on port 4545 if the monitoring service be enabled on these specific systems. This port needs to be unrestricted if the RHN Monitoring service is being used. For Proxy: The RHN proxy server will connect to ports 80 and 443 on the “upstream” system, either RHN Hosted or an internal Satellite server. If the Monitoring Scout is enabled on a proxy server, then the proxy will initiate connections to port 4545 on Monitoring-enabled client systems. For Client Systems: Client systems will initiate connections to ports 80 and 443 of their upstream RHN server (Satellite, Proxy or RHN Hosted). If OSA is being used, then the client systems will also connect to the Jabber service running on the Satellite or Proxy server, on port 5269. Red Hat’s customer service and support teams receive technical support questions from users all over the world. Red Hat technicians add the questions and answers to Red Hat Knowledgebase on a daily basis. Access to Red Hat Knowledgebase is free. Red Hat Magazine offers a preview into the Red Hat Knowledgebase by highlighting some of the most recent entries. The information provided in this article is for your information only. The origin of this information may be internal or external to Red Hat. While Red Hat attempts to verify the validity of this information before it is posted, Red Hat makes no express or implied claims to its validity. ... read more

More Topics from "News"

• Video: Spotlight on Extra Packages for Enterprise Linux (EPEL)
• This isn’t your grandpappy’s dd command
• ccmixter: Red Hat soundscape, shared with you
• Tips and tricks: How do I force users to change their passwords upon first login?
• Friday roundup