IBM Support

IC81824: DATAPOWER NFS WRITE OPERATIONS MIGHT NOT REPORT FAILURE WHEN PERFORMED AGAINST AN UNRELIABLE REMOTE NFS SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • DataPower write operations over the NFS protocol might not
    report internal write failures when performed against an
    unreliable remote NFS server.
    
    DataPower write operations can be compromised if the NFS server
    crashes, goes down, experiences slow performance or reboots
    while these write operations are in progress.
    
    Under these conditions, the RPC re-transmission sequence will
    end after a timeout, because the NFS Volumes in DataPower are
    soft-mounted.
    

Local fix

  • Insure that your NFS server and the network connectivity to the
    NFS server are stable.   For situations, where several DataPower
    appliances are using the same unreliable NFS server, you may
    wish to investigate a High Availability NFS server solution.
    
    Until this is fixed, write operations on NFS Volumes (read-only
    volumes are not affected) should be avoided if the NFS Server is
    unreliable. The following alternatives can be chosen for the
    different uses of NFS in the appliance:
    
    - Logging targets: choose a different log target type for
    logging messages; for example, you may log the messages to the
    files in the hard-disk of the appliance and select a best fit
    archiving option, either rotation or upload using FTP (all
    appliance types)
    
    - B2B Gateway Archive Target: It is recommended to use FTP or
    SFTP  to upload the archive files to a remote data store. You
    can also select any other supported protocols; such as,  FTP,
    FTP over SSL, SFTP, HTTP, HTTPS, MQ, MQFTE or RAID.
    
    - NFS Destinations: for destinations used in any of the
    gateways, via Routing URL or stylesheet extensions, such as
    url-open(), you can select any other supported protocol
    available.
    

Problem summary

  • This will be fixed in the next major release.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC81824

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    402

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-06

  • Closed date

    2012-03-16

  • Last modified date

    2012-03-16

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R500 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 February 2022