Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Filesync to ESS

Status
Not open for further replies.

keschber

Technical User
Mar 10, 2010
104
US
Filesync is failing from my main switch CM 5.2.1 to an ESS also on 5.2.1. I'm pretty sure this is a firewall issue. Registration is OK, but filesync fails.

I think the TCP port 21874 needs to be opened up but is this the only thing taht needs to be allowed.
 
Yes TCP port 21874 is the only port that needs to be opened to allow a transalation update to an ESS server
 
Port 21874 should be for any CM3.x or higher.

You may want to run the command 'swversion' from the command prompt on both the primary server and ess server. Verify both have the same software release and patch version. You will get a filesync to fail if your ESS/LSP is below the main.

If all else fails run the command 'server -z' on the ESS server and reboot. This will ensure the server is properly set as an ESS and restart the filesync service.

Run the command 'statapp -p' to verify the service is running on both systems.

Depending on your setup you may require static routing. Verify your network routing by doing a traceroute between the servers.

When you do a save trans ESS you should see the /etc/opt/defty/xln1 file update on the ESS server using the 'ls -a' command to get a timestamp.

Of course I am assuming here the ESS server is showing as registered in the main server when you do a 'list survivable'.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top