NFS protocol

Hello Experts,
I do have a doubt in using NFS protocol in FILE Adapter.
Is it is possible post the Message to a Local drive ( Say D drive ) or a Network Drive ( Say Z drive ) whcih was Mapped to server Machine .
If so please provide me some suggestions to post the message.
Cheers!
Ram

Hi Smitha,
Thanks for the blog
Unfortunately, I can able to post the message sucessfully.
As mentioned I have downloaded GUILDFTPd server and installed in my system .
I have even given the paths as mentioned. ( After clicking ok, I cant able t o find the path once again ... Stange !!!!)
As mentioned I have also created a folder by name Output .
I have also given my local System IP in File communication channel ( with FTP Protocol) .
After all this when I have tried to post the message from FTP server I can see below error in RWB .
Attempt to process file failed with Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: SocketException: Connection timed out:could be due to invalid address

Similar Messages

OS commands with NFS protocol

Hi All,
I have written a shell script to generate a blank file at FTP folder. It works fine with FTP protocol.... But when i try to execute same script through NFS protocol it doesn't work...
Can anybody tell me why is it so? Do we have any restrictions on scripts with adaptors n protocols...?
Thanks,

Hey
there is a difference between executing an OS command via telnet and executing it via PI,secondly an OS command on FTP is executed indirectly(script on PI calls the actual script on FTP) whereas an OS command on NFS is executed directly(script on PI is the one which does all the work,no calling of any other script mandatory).
the reason you are able to execute a script via telnet and not via PI can be quiet a few,the most common one is the way you have given the OS cmd in communication channel.
is this a Unix or perl script?
Thanx
Aamir

NFS protocol across the Pix firewall

I have a Pix 515E running PixOS version 8.0.4 with two interfaces, inside and outside.
On the inside interface, I have a Redhat Enterprise Linux 5.4 64 bits machine as an NFS server version 4 (NFSv4).
On the outside interface, I have three (3) Redhat Enterprise Linux 5.4 64 bits as NFS clients.
I have the following configuration on the Pix:
static (inside,outside) 192.168.1.1 4.2.2.2 netmask 255.255.255.255
access-list external permit icmp any any log
access-group external in interface outside
At the moment, none of the Linux client machines can mount a share on the NFS server because
my ACL is too restrictive. I would like to be able to open the firewall so that Linux client
machines can mount the NFS server using NFS over UDP or NFS over TCP.
I am looking for the exact UDP and TCP ports to be added to the ACL in order to accomplish
this, from someone who have done this before.
Anyone know how to do this?
Thanks,

I think I just answer my own post. Just need to add about three lines to the configuration:
access-list external permit tcp any host 4.2.2.2 eq 111 log
access-list external permit udp any host 4.2.2.2 eq 111 log
fixup protocol sunrpc 111
Now I can mount the NFS server from my linux machines

[SOLVED] NFS protocol not supported

I get this error:
mount.nfs4: Protocol not supported
when trying to mount a NFS share from my server like so:
sudo mount -t nfs4 192.168.1.20:/srv/nfs4/ /media/server
I can mount it on my raspberry pi, but not on my arch laptop.
The server configuration is like this:
/srv/nfs4/ 192.168.1.1/24(rw,fsid=root,no_subtree_check)
/srv/nfs4/media 192.168.1.1/24(rw,no_subtree_check,nohide)
showmount -e gives this:
Export list for 192.168.1.20:
/srv/nfs4/media 192.168.1.1/24
/srv/nfs4 192.168.1.1/24
Any ideas?
Last edited by marius (2013-08-17 12:50:46)

I don't think you are supplying all the information that you are given by your machine. The error you mention is often preceeded by a number of other messages which give some idea of what is actually occurring. Please post error messages exactly as they are given to you, and check the journal and/or dmesg for more information.
Also as a side note, you need to use code tags for things like commands and output. Hit the quote button on this post to see how I created the boxes below (the arrows will make sense when this post is quoted):
<--These are code tags-->
<--These are quote tags-->

File sender adapter with nfs as NFS as transport protocol

hi all.
can any abody explain me what is the main difference between FTP and NFS protocols and why there is no need to pass connection parameters for nfr ptotocol.
waiting for excellent reply.
bye.
regards.
seeta ram.

Hi,
FTP - It is a file transfer protocol where the source system in this XI has to connect to any other system's particular location it requires connection parameters IP Address, port and you can have authentication in this case also.
Here the system need not be in Network also. You can access the remote system by providing valid userid and password, hence we require conn parameters here.
NFS - This protocol is used to access files which are present accross the network where XI also lies within the same network.
Regards,
Ramesh P

Username and pwd for FileAdapter with NFS as transport protocol

Hi,
we installed PI 7.1 in windows env.
to access a particular target location manually from the PI windows server, the procedure is:
in the Start->Run or in the explorer bar we type the ip as "
121.1.2.3\SourceFolder", then the windows asks for the username and pwd, once we enter valid username/pwd, we get the access to the "
121.1.2.3\SourceFolder".
to poll the files under this folder, we setup a FileAdapter Communication Channel with TransportProtocol=NFS. (so its not FTP).
In the "File access Parameters" section, in the "source directory" value we entered as "
121.1.2.3\SourceFolder"
but where can we provide the username and password that would be required to access this folder.
when we activated the CC, in the RWB, we see log as:
Configured source directory '
121.1.2.3\SourceFolder' does not exist
thanks.

Hi,
to access a particular target location manually from the PI windows server, the procedure is:
in the Start->Run or in the explorer bar we type the ip as "\\121.1.2.3\SourceFolder", then the windows asks for the username and pwd, once we enter valid username/pwd, we get the access to the "\\121.1.2.3\SourceFolder".
So the folder does not exits in your XI installed server. It will be there in some other Server location.If am correct then NFS protocol not work for this. you should required FTP for accessing the external server path. NFS protocol used to access the local XI machine path only.
Regards,
Prakasu.M

Custom NFS share point directory showing up on all network machines

Hi,
I'm in the process of migrating our 10.4 PowerMac server to a Mac Pro (running 10.5). I've been trying to recreate our 10.4 server setup as much as possible and so far I've only come across one annoying issue.
We have fink installed on the server and under our 10.4 setup the /sw directory was set up as an NFS automounted share point with a custom mount point of '/sw'. I.e. users logging into client machines saw a /sw directory and could work with that. This made it easier to add fink packages as I only needed to do this on one machine (the server). This setup worked very well under 10.4 and had been working stably for the last couple of years.
As we now have (for another month or two at least) a mix of intel and Power PC machines, I don't want to share out the (intel) server version of fink to all clients. In Server Admin, I have chosen to set the NFS protocol options to specify the IP address of just one client (an intel machine). I am only using NFS to share this directory. The plan is to add more client IP addresses as we get more intel machines.
This works for the one intel client machine. Logging in via the GUI or via ssh allows you to run programs located under the /sw directory. The problem is that a phantom /sw directory appears on all client machines, even though their IP addresses are not specified in Server Admin. The /sw directory has root/wheel permissions (for user/group) and attempting to list its contents returns 'Operation not permitted' (even with 'sudo ls /sw').
If I use Directory Utility to remove the connection to the Directory server on our main server, then the /sw directory becomes owned by root/admin and I can remove it (it appears empty). Reconnecting to the Directory Server changes the permissions back to root/wheel. It is also worth noting that when I first installed fink on the server (in /sw) the act of making this a share point also changed the permissions on /sw to root/wheel meaning that I couldn't access the fink programs that I had only just installed (this forced me to reinstall fink in /Volumes/Data/fink).
Has anyone else noticed this behavior? It almost seems like Server Admin is not honoring the list of IP addresses that are being listed as targets for client machines. I had planned to install fink locally on the PowerPC clients until we upgrade them to intel machines. However, I would then also have to install fink somewhere other than /sw as I can't write to that directory. I would presume that this behavior should happen on any NFS share point that is trying to automount to a custom mount point on a client. Can anyone else verify this?
Regards,
Keith

As a footnote. I have now removed my shared fink installation. It is no longer listed as an NFS sharepoint in Server Admin and running the 'showmount -e' command does not list it. However, a /sw directory is still being created on the server and on the client machines on our network.
This is perplexing and frustrating. There is no sharepoint any more. I rebooted the server but it makes no difference. I removed the /sw directory (on the server) by booting the machine in target firewire mode and removing it by using a 2nd machine. But following the restart, it appeared again.
This suggests that once you make any custom mountpoint (using NFS sharing) then you will forever be stuck with a directory at the root level of all your clients which you can not remove.
Keith

PI sender communication channel not reading files from NFS directory

Hello,
I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
Any suggestions?
Thanks,
Sangita

Hello Sangita,
Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
You can use NFS protocol when you have a local directory in XI server.
Best Regards,
.Luis Bernal.

How to specify source directory in File sender adpate using (NFS)?

Hello experts,
I am doing File-PI-Proxy scenario.
Input file is available on machine which is within the Network area and FTP is not available on that machine.
For this reason I am using the NFS Transport Protocol.
In ID File sender I have specified Source Directory:-
IP Address\Directory
I am geeting the Error in RWB as 'Configured source directory '
IP Address\Directory' does not exist'.
Please suggest how to specify the Source Directory path.
Regards,
Jagesh

Hi,
If you want to use NFS protocol, then the file needs to be within the a folder in the XI server and not outside it, In your case if you need to use the file in a different machine which is on a network then try to use the FTP protocol.
Refer this blog:
/people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang which shows the details of how you can install a local FTP and use it
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on Mar 18, 2009 10:43 AM

Windows Server 2012 R2 wouldn't response SMB Negotiate Protocol Request

Hello
I've got an windows 2012 r2 as a file server, it worked fine with windows client but not with lunix-based client
I first discovered this problem on an Android phone:http://social.technet.microsoft.com/Forums/en-US/b3a8a7f9-f4b7-4b9f-b586-2ec87fc14d71/cant-access-shared-folders-on-win-2012-r2-with-android-phone?forum=winserverPN
then I did some test on a newly installed lunix OS on a VM today, I found that my server do not response SMB Negotiate Protocol Request from my phone or the testing OS at all.
when I try smbclient -L ServerIP, I get
read_socket_with_timeout: timeout read. read error = Connection reset by peer.
Receiving SMB: Server stopped responding
protocol negotiation failed
the wireshark capture are like this:
35 22.704658
192.168.1.20 192.168.1.10
SMB 260
Negotiate Protocol Request
36 22.704745
192.168.1.10 192.168.1.20
TCP 54
microsoft-ds → 41733 [RST, ACK] Seq=1 Ack=195 Win=0 Len=0
37 23.090116
192.168.1.20 192.168.1.10
TCP 74
41734 → microsoft-ds [SYN] Seq=0 Win=5840 Len=0 MSS=1460 SACK_PERM=1 TSval=8758786 TSecr=0 WS=16
38 23.090237
192.168.1.10 192.168.1.20
TCP 74
microsoft-ds → 41734 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1 TSval=5473099 TSecr=8758786
39 23.090382
192.168.1.20 192.168.1.10
TCP 66
41734 → microsoft-ds [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSval=8758787 TSecr=5473099
I don'tknow what's causing this problem ,is there anyone could help me?

Hi,
If you access files stored on Windows Server 2012 R2 from other non-Windows client computers, you need to use NFS protocol.
Using the NFS protocol, you can transfer files between computers running Windows and other non-Windows operating systems, such as Linux or UNIX.
In Windows Server 2012, NFS includes the components, Server for NFS and Client for NFS. Server for NFS enables a computer running Windows Server 2012 to act as a NFS file server for other non-Windows client computers. Client for NFS enables a Windows-based
computer that is running Windows Server 2012 to access files that are stored on a non-Windows NFS server.
For more detailed information, please refer to the articles below:
Network File System Overview
http://technet.microsoft.com/en-us/library/jj592688.aspx
Server for Network File System First Share End-to-End
http://blogs.technet.com/b/filecab/archive/2012/10/08/server-for-network-file-system-first-share-end-to-end.aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

NFS or FTP to Pick files from Windows Directory

Hi All,
I am working of File to File Scenario. PI needs to pick a file placed in Windows Directory. I have configured the scenario as NFS and given the proper Folder path and file name. PI is not able to Pick the file. It is saying "Configured Directory Does not Exists".
Both PI (HP Unix) and Windows systems are in same network. Do I need to use FTP for this scenario? Is there any way to access the files in Windows Directory using NFS protocol?
Thanks.

Hi Achuth,
Ask you BASIS person to create one shared folder in PI Server(HP Unix) and use that directory in channel.
thanks,
madhu

Slow nfs read/write from solaris 8 to solaris 10

there is a bug:4852269 which sums up my problem well.
I have a solaris 10 sparc with a big nfs shared raid5, and most of the other suns I have run solaris 8. the access time from sol8 to sol10 is awfull.
Is there some config/patch I can apply to the solaris 10 box?
I have put on the latest 10_Recommended.zip

it's a ufs filesystem
If it helps, here is my /etc/default/nfs
# ident "@(#)nfs 1.10 04/09/01 SMI"
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# Sets the maximum number of concurrent connection oriented connections.
# Default is unlimited and is obtained by not setting NFSD_MAX_CONNECTIONS.
# Equivalent to -c.
#NFSD_MAX_CONNECTIONS=
# Set connection queue length for the NFS over a connection-oriented
# transport. The default value is 32 entries.
# Equivalent to -l.
NFSD_LISTEN_BACKLOG=32
# Start NFS daemon over the specified protocol only.
# Equivalent to -p, ALL is equivalent to -a on the nfsd command line.
# Mutually exclusive with NFSD_DEVICE.
NFSD_PROTOCOL=ALL
# Start NFS daemon for the transport specified by the given device only.
# Equivalent to -t.
# Mutually exclusive with setting NFSD_PROTOCOL.
#NFSD_DEVICE=
# Maximum number of concurrent NFS requests.
# Equivalent to last numeric argument on nfsd command line.
NFSD_SERVERS=16
# Set connection queue length for lockd over a connection-oriented transport.
# Default and minimum value is 32.
LOCKD_LISTEN_BACKLOG=32
# Maximum number of concurrent lockd requests.
# Default is 20.
LOCKD_SERVERS=20
# Retransmit Timeout before lockd tries again.
# Default is 5.
LOCKD_RETRANSMIT_TIMEOUT=5
# Grace period in seconds that all clients (both NLM & NFSv4) have to
# reclaim locks after a server reboot. Also controls the NFSv4 lease
# interval.
# Overrides the deprecated setting LOCKD_GRACE_PERIOD.
# Default is 90 seconds.
GRACE_PERIOD=90
# Deprecated.
# As for GRACE_PERIOD, above.
# Default is 90 seconds.
#LOCKD_GRACE_PERIOD=90
# Sets the minimum version of the NFS protocol that will be registered
# and offered by the server. The default is 2.
#NFS_SERVER_VERSMIN=2
# Sets the maximum version of the NFS protocol that will be registered
# and offered by the server. The default is 4.
NFS_SERVER_VERSMAX=2
# Sets the minimum version of the NFS protocol that will be used by
# the NFS client. Can be overridden by the "vers=" NFS mount option.
# The default is 2.
#NFS_CLIENT_VERSMIN=2
# Sets the maximum version of the NFS protocol that will be used by
# the NFS client. Can be overridden by the "vers=" NFS mount option.
# If "vers=" is not specified for an NFS mount, this is the version
# that will be attempted first. The default is 4.
#NFS_CLIENT_VERSMAX=4
# Determines if the NFS version 4 delegation feature will be enabled
# for the server. If it is enabled, the server will attempt to
# provide delegations to the NFS version 4 client. The default is on.
#NFS_SERVER_DELEGATION=on
# Specifies to nfsmapid daemon that it is to override its default
# behavior of using the DNS domain, and that it is to use 'domain' as
# the domain to append to outbound attribute strings, and that it is to
# use 'domain' to compare against inbound attribute strings.
#NFSMAPID_DOMAIN=domain
#

FTP vs. NFS- basic configuration and doubts - bt. unix and windows systems

Hi all,
I need to configure a connection between PI (unix box) and a windows server using File Adapter (both sender and receiver).
My doubts are:
- Which is preferable type of conection: NFS or FTP?
- Which are the advantages and disadvanteges of both?
- Most important: Which are the prerrequisites for both ways? Such as installing server ftp, or mounting folders, OS configuration, security config. Etc. etc.
I will apprettiate if you could also post a direct link to documentation.
Thanks in advance.
Exe.
Edited by: EZEG80 on Nov 9, 2010 1:18 AM

Hi,
NFS: when the file folder is available on the XI Server
FTP: when it is at remote
If the Sharing folder is in the same XI system then NFS..If the sharing folder is in different system it is FTP.
we will use NFS when we required to poll the files from local machines.and we will use FTP when we required to poll the data from the FTP server which are in the remote side or outside of the firewall
FTP (file transfer protocol) here you are getting data from ftp server or you are writing to FTP server.
NFS is used when your XI can access the file location directly using the NFS protocol.
When the File System can be access using FTP protocol, then you need to use FTP and provide the FTP server details and user crendentials to pull data from the File Server.
NFS is used when you want XI to use the NFS protocol to access thye location of the file.
FTP is File Transfer Protocol and is used when your Sender SYstem is using an FTP system to send / receiver files.
we are using NFS when we required to poll the files from local machines..
We are using FTP when we required to poll the data from the FTP server which are in the remote side or outside of the firewall..
For more info....go thru these threads...
FTP and NFS?????
differnce between nfs and ftp
FTP Vs NFS
Regds,
Pinangshuk.

Wrapper.Classpath and NFS issue

Using Jserv1.1.2
It seems that there are Issues When you try
to create
wrapper.classpath that points to a mapped Network drive
using NFS protocol.
It result in a Internal Server Error
Did someone encounter same issues??
Thanks to answer.

BigMike86 wrote:
Well, the JAR I'm trying to add is here.
The instructions specifically say to put it in the ext folder.
The JAR should contain an Options application which I should be able to open by only typing "java Options".Based on what? Do the docs say specifically that? Is the Options class in a package?
Again, you're not providing much in the way of detail, so all I can say is that there's something wrong with your assumptions.

After Effects CS4 and NFS Network Drop-Outs

Hi all,
We're experiencing a high number of NFS drop-outs ever since we've upgraded our department to AE CS4. I'm not saying CS4 is the culprit, I'm just saying this is when we started noticing the issue.
13 Apple MacPro 8-core systems. 12 Leopard, 1 Snow Leopard.
Projects are located on an Apple XServe 2.26 Quad-Core Xeon with 12GB RAM running 10.5.8 Server
Projects are shared up via NFS protocol via gigabit network.
Basically throughout the day, a random number of peole will lose connection to the NFS share, to which it returns on its own in a few moments. Though it's not everyone each time, all users encounter the issue at least once-a-day, usually more. (We have to different servers with NFS shares, one does not drop, the other does) The server that drops the share is the newer XServe Leopard and is the primary server where all the footage and projects are located. The 2nd server is just secondary library media and stock footage...
Essentially, I'm curious if anyone else is having NFS issues since the update to CS4. I'm just trying to weed out all elements. It's hard to say if it's the server itself, as the logs only note a drop once-in-a-while... We also use Rush Rendering for our Maya renders, which we have just upgraded to the latest version and we get drops even when no one is using Rush or Maya...
Very strange but extremely frustrating issue. It's not fun when someone is working on a project and loses it because the share drops out.
Any input greatly appreciated. Let me know if you need more info.
Thanks!

Session timeouts.... I really do think it's the server. AE doesn't care for specific network stuff, it's all just volumes/ drives to the program. To avoid these issues, you would have to shorten the refresh cycles on your server availability broadcasts or the "keep alive" cycles on the connection/ session settings themselves. I'd know how to do it on Win Server, but I have no clue with regards to XServe configuration. Still, certainly some simple console commands and a restart of the server software should be able to take care of the matter.
Mylenium

NFS protocol

Similar Messages

Maybe you are looking for