Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SC 3.4.0 agent not reachable remotely Windows Server 2008 R2
2011-07-15
01:03 PM
4,226 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. I am looking for assistance again. I am working with SC 3.4.0 (64-bit) agent on Windows Server 2008 R2 which has been installed with the default port of 9090. This can be successfully accessed via telnet (both IP address and hostname) on the host that the agent has been installed. However, it cannot be accessed from another host which has the SC server installed. I have confirmed there is no firewall in place between these servers nor is there a firewall running locally. I have not found suggestions in the NetApp Snap Creator Framework 3.4.0 Installation and Administration Guide document suggesting that any modifications are needed. There was another thread that asked about this <http://communities.netapp.com/thread/15913?tstart=0>.
Is there a configuration file that needs to be modified to provide access (e.g. scAgent3.4.0\config\agent.conf)?
Thank you.
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Strangely enough after waiting a bit - it is now working. Please ignore my request for help. Thank you.
3 REPLIES 3
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Strangely enough after waiting a bit - it is now working. Please ignore my request for help. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good news
Just for info config/agent.conf is for allowing commands to run so any parameter in scServer config with a CMD must be allowed. A common obe is snapdrive.
And example for windows snapdrive
command: sdcli.exe
The agent does take a few seconds to start after service starts
Also if you need to troubleshoot agent best thing is running it manually in debug mode
ie: snapcreator.exe --start-agent <port> --verbose --debug
Let us know if you need anymore help
Keith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Keith (again) for your quick reply.
