The AFS should live on your file server box, have you set that component up there?
On which File Server Box? We have one for the BladeLogic System, and we also are trying to set an advanced file Server up, this is the issue. Following the instructions it tells you to set up the file server using using the "SET FILESERVER NAME SERVERNAME" but this replaces our normal file server.
Ignore previous posts, I have managed to set up the advanced File Server and advanced repeater, but now have issues connect Servers through the advanced repeater, either says timed out or server doesn't have a Agent.
What ports need to be open between the following
Repeater -> File Server
Repeater -> App server
Servers -> Repeater
Also do i need to add anything to the
Export file on any of the Servers?
Set up any routing?
Porperties of the Server I'm adding?
5282 between the AR and the AFS, initiated from the AR.
Servers to Repeater is just 4750
Can telnet from teh AR to FS on 5282 and from the Server to repeater to AR on 4750, nut still timing out. How do you point the servers to the repeater?
You establish repeater rules but really a repeater is just for payload (by selecting stage indirectly in a job). So you still need to make sure that your standard ports to the agents are open (4750) and that you can resolve the target server names when trying to add to BL. Can you add the servers as a test, ignoring the repeater?
No can't telnet to the Servers directly from the app Server on 4750. I thought that is what the repeater does? Is there any doc's on setting up rules etc?
1 of 1 people found this helpful
A Repeater is there to minmise bandwidth use over a WAN. You are thinking of a SOCKS proxy.
The repeater rules are very simple to work out.
Just create a new rule that says if server has Server.Property equal to XYZ then use repeater A.
For example I use a _DATACENTER value to determine which repeater to use.
Ports still need to be open unless you start using a SOCKS proxy to limit the firewall rules requirements.
Quick question (I'm installing an Advanced Repeater)... Uni-directional on 4750 from AR -> Agents won't cut it then?
It needs to be bi-directional for the agents to initiate a connection to the AR? Or just unidirectional from the agents to the AR?
uni-directional from the AR to the agents on 4750.
I thought what happened was the agents knew they should get the package from the AR and they "requested" it though? Is the file "pushed" from the AR to the agent then?
When the deploy is staged, the AFS requests the files from the AFS to get the files to the ARS, then during the deploy it works like a normal repeater as the files are already in the staging dir on the repeater.
OK, so now I've installed the Advanced Repeater and set everything up, I'll have to request the following firewall rules:
App > AR: 7717TCP (admin port) and 8082 (proxy service port)
AR > App: 5282TCP
AR > Agents: 4750TCP
Yes – ARS to agents is unidirectional