cancel
Showing results for 
Search instead for 
Did you mean: 

Portumleitung des RemoteAgents funktioniert nicht

opticomIT
Level 4

Hallo,

 

wir haben einen Server im Einsatz, auf dem eine andere Software den NDMP Port 10.000 beansprucht.

Daher haben wir wie in TECH24256 auf dem Remote Server den NDMP Port geändert. Nach Auswertung des Debuggings versucht dieser auch den Mediaserver auf dem neuen Port 10.001 zu kontaktieren.

[6288] 02/02/12 16:52:58 [ndmp\ndmpcomm]      - Successfully resolved the "ndmp" service to port: 10001 (host order)
[6288] 02/02/12 16:52:59 [ndmp\ndmpcomm]      - Started NDMP Listener on port 10001

Laut Debugging, weiß der MediaServer davon aber garnichts und versucht weiterhin die Kommunikation auf Port 10.000 und erhält dort keine Antwort.

[11480] 02/02/12 17:30:31 [ndmp\ndmpcomm]      - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
[11480] 02/02/12 17:30:31 [ndmp\ndmpcomm]      - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'SERVER' ...
[11480] 02/02/12 17:30:31 [ndmp\ndmpcomm]      - ndmpConnectEx : Control Connection information: A connection was established between end-points 172.16.1.21:51554 and 172.16.1.22:10000.

Auch das Setzen des Parameters für die Dynamic Port Range auf 10.000 - 10.001 ändert nichts daran.
Die Firewall blockiert definitiv nichts mehr.

Wie erkläre ich meinem Mediaserver, dass er Port 10.001 für die Kommunikation mit diesem Server nutzen soll?

6 REPLIES 6

pkh
Moderator
Moderator
   VIP    Certified

You use the same procedure on the media server and change the port to 10,001.

opticomIT
Level 4

But if I change the ndmp port on the media server i have to change the port on every remote server too.

The KB says "The steps above can be done on only the server(s) affected. All other remote servers can have the existing/default NDMP Port."

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...not so, that KB states you can change the port ont he media server, and you can leave the remote servers. That's what you need to do...

pkh
Moderator
Moderator
   VIP    Certified

You did not say what version of BE you are using. For BE 10d and below, you would need to change the port for all servers.  For BE 11d and above, by right you only need to change the port on the remote server that you want to change the port and leave the port unchanged for all the other servers.  However, in some cases, the remote server with the changed port is unable to notify the media server of the port change.  This would require that the port on the media server be changed as well.  The other remote servers should not be affected, but their port may need to be changed as well.

opticomIT
Level 4

Hi,

yes pkh you're right - that's exactly the problem!

(We are using BE 2010 R3 SP1)

 

We tried it out: If we change the ndmp port on the media server to 10.001 it's true we can reach the server with the changed port, but in this case all other servers don't answer.

So what's the solution to this problem? To change the port on every server couldn't be the answer!

pkh
Moderator
Moderator
   VIP    Certified

Try changing the media server port back to 10,000 and see if it "remembers" that there is one remote server with a port set to 10,001.  If this does not work, then I am afraid that you have to change the port on all your servers to 10,001.

Also, go to the server with port 10,001 and check that it is publishing to the media server.  Start the BE Agent Utility, you should see the media server listed in the Publish tab.