Centera Fixed Content Device configuration troubleshooting, and tuning

Transcription

1 Centera Fixed Content Device configuration troubleshooting, and tuning Storage Management Ruben Salazar and Patricia Gatewood - CE FileNET P8 support September 30 th. 2015

2 Agenda Introduction to Centera Common Centera Storage Area issues Centera Troubleshooting Tools to Diagnose Tuning Great resource links Questions 2

3 Introduction - How a document gets ingested to Centera Client Application 2 Inbound Filestorage Area Staging Area Content Area 1 Objects are created and sent to the CPE server 3 Objectstore Migration queue Referrals CPE server sends the Object to the Centera device via the Centera API. 3

4 Introduction to Centera - retrievals DocVersion Content_referral_blob 1 BLOB Object stored as a BLOB. 5 C-clip ID Centera Authenticates the request and delivers the object 4 CDF 2 BLOB BLOB BLOB BLOB is referenced by the Content Address and stored in the Content Descriptor File. 3 CA references to the object. Calls the Clip ID. 4

5 Common Storage Area issues Configuration Connectivity 5

6 Common issues Configuring FCD devices Pathing issues Environment Variables incorrect Root directory not correctly defined incorrect Pointing to the wrong libraries Connectivity Not writing to the FCD device # of connections and pool sizes incorrect part of tuning 6

7 Configuring FCD Check whether your env. is 32 bit or 64 bit. Make sure to install the FCD libraries Modify the script setcenteralibpath.bat or setcenteralibpath.sh Configure the env. Variables UNIX 01.ibm.com/support/knowledgecenter/SSNW2F_5.2.0/com.ibm.p8.install.doc /p8pin182.htm 7

8 Troubleshoot scenario steps New Centera setup Not be able to write to the Centera device. 1. Check the p8_server_error.logs for errors. 2. Enable the following CE tracing in FEM or ACCE (Content Cache, Fixed Content Provider, Content Storage, Engine and Error). 8

9 Troubleshooting One common issue is forgetting to add the Staging Area. FEM ACCE 9

10 Connection pooling issues # of connections is too small in FEM or ACCE Review how many nodes you have configured. 10

11 EMC Tools to Diagnose Reading and Writing to a Centera Device JCenteraVerify (Can download from the EMC website) CenteraPing (Can also be downloaded from the EMC website) For ECM Centera devices to test outside of P8. NOTE: Both tools - Available for all UNIX, Linux and Windows 11

12 Tools to diagnose Centera Devices JCenteraVerify Cmd> Java jar JCenteraVerify gui or Java jar JCenteraVerify Ipaddress

13 Tools to diagnose Centera Devices JCenteraVerify.log *********************************************************************** ***** Start of JCenteraVerify log *********************************************************************** ********* General information Time: Tue May 05 21:04:59 PDT 2015Tool Version: SDK Version: User configuration TOOL SETTINGS Number Of Files: 3 FileSize (KB): 1, 10, 100 Working Dir:.\Temp Restore Dir:.\Temp\Retrieve Log File: 13.\JCenteraVerify.log Delete temp Files: true Delete restore Files: truesdk SETTINGS Number of Retries: -1 Retry Sleep: -1 ACCESS NODE CONNECTIVITY CHECK is available.cluster INFORMATION ClusterId: 1cc3d0f2-1dd2-11b2-b887-b53c9d331cb7 CentraStar: Available Capacity:6,605 GB Total Free Capacity: 28,961 GB Replica Address: CAPABILITIES Read allowed: true Write allowed: true Delete allowed: true Exists allowed: true Purge allowed: false Monitor allowed: true Query allowed: true PrivDelete allowed: false Writing the file 1 1 File(s) written successfully. CA: BO1VCQP5I0TRMeD72OBP5Q1A1TEG419KIR11030B966ALAOALVPAF Reading the file 1. CA: BO1VCQP5I0TRMeD72OBP5Q1A1TEG419KIR11030B966ALAOALVPAF 1 File(s) read successfully Deleting the file 1. CA: BO1VCQP5I0TRMeD72OBP5Q1A1TEG419KIR11030B966ALAOALVPAF 1 File(s) deleted successfully Writing the file 2 2 File(s) written successfully. CA: 08L7BM6KJR80NeBS1VKQPOEN3KAG419KIR15050O760VCSRU1PLHT Reading the file 2. CA: 08L7BM6KJR80NeBS1VKQPOEN3KAG419KIR15050O760VCSRU1PLHT 2 File(s) read successfully Deleting the file 2. CA: 08L7BM6KJR80NeBS1VKQPOEN3KAG419KIR15050O760VCSRU1PLHT 2 File(s) deleted successfully Writing the file 3 3 File(s) written successfully. CA: EAOKLEL2MFEJDeAL6ARB7140P89G419KIR180705ANH46UDF6RAJ5 Reading the file 3. CA: EAOKLEL2MFEJDeAL6ARB7140P89G419KIR180705ANH46UDF6RAJ5 3 File(s) read successfully Deleting the file 3. CA: EAOKLEL2MFEJDeAL6ARB7140P89G419KIR180705ANH46UDF6RAJ5 3 File(s) deleted successfully ******************************************************************************* End of JCenteraVerify log ******************************************************************************

14 Tools to diagnose Centera Devices Cmd> CenteraPing address is accessible Otherwise, CenteraPing returns the following message : IP_address Open Error: No connection with pool NOTE: Cannot use the regular ping command, will not work 14

15 Centera tuning NOTE: Before making any changes, please check with EMC Support first! 15

16 Centera tuning 16

17 FCP Pool Max in Use If this value for this parameter is set to too low, the server may experience CONTENT_FCP_POOL_MAX_REACHED errors in the p8_server_error.log. Default = -1 (unlimited) 17

18 Max. # of connections / pooling tuning Max. # of sockets that the SDK will allocate for your app. Default: 100 Max:

19 Max. # of connections formula Centera Node 1 Centera Node 2 Centera Node 3 Centera Node

20 Max. # of connections if too Low If set too low, Centera error Code of com.filepool.fplibrary.fplibraryexception: Maximum amount of open sockets reached D-1751C (Centera error code: ) com.filepool.fplibrary.fplibraryexception: Maximum amount of open sockets reached at com.filepool.fplibrary.fptag.blobwrite(unknown Source) at com.filenet.engine.content.fcprovider.centera.centeraadaptor.addtaga ndcontent(centeraadaptor.java:2175) at 20

21 Concurrent Readers The value for the Concurrent Readers is suggested to be ½ the value set for Maximum Connections. The default value is 1. 21

22 Max Reader Semaphore Wait time The maximum waiting time to get a read semaphore for read operation before the system fails the operation. (Set in milliseconds) Works with Max Concurrent Readers. Recommedation set to 30,000 ms (30 sec) or smaller. 22

23 Embedded Data Threshold This parameter supplies the maximum data size per content element to embed in the C-Clip. By default this value is 0, meaning that content is never embedded in the C-Clip. The maximum value for this parameter is (bytes). 23

24 Open Strategy Avoid issues with unavailable nodes or replication addresses. FP_NORMAL_OPEN(0) FPPool_Open() attempts to open connections to all addresses in the connection string, and to all associated replication addresses. Use this strategy if your application performs numerous operations while the pool is open FP_OPTION_DEFAULT_OPTIONS. FP_LAZY_OPEN (1) FPPool_Open() opens connections to addresses only as needed. 24 Use this strategy if your application frequently opens and closes the pool.

25 Content_referral_blob Or Not NULL SELECT OBJECT_ID FROM DOCVERSION WHERE CONTENT_REFERRAL_BLOB OBJECT_ID='{43656Y3MMERD-DGGFGFDS}';

26 Great Resource links Understanding Storage Management filenetstoragemanagement/ Configuring EMC Centera 01.ibm.com/support/knowledgecenter/SSNW2F_5.2.0/com.ibm.p8.install.doc/p8pin182.htm Centera Technote (Unable to add the Centera device in P8 Test connection fails) Centera Technote ( Connecting to the Centera device fails) EMC forum 26

27 Great Resource links continued IBM DeveloperWorks forum IBM Enterprise Content Management for FileNet Content Manager product page. 27

28 28