UNSOLVED
A
Aleksandr1
53 Posts
0
3605
August 29th, 2008 00:00
FP_AUTHENTICATION_FAILED_ERR
I am connected to Centera with JCenteraVerify.
**************************************************************
************** Start of JCenteraVerify log ******************
**************************************************************
--------------------- General information -----------------------
Time: Thu Aug 14 18:03:29 YEKST 2008
Tool Version: 3.2.23
SDK Version: 3.2.607
--------------------- User configuration ------------------------
TOOL SETTINGS
Number Of Files: 3
FileSize (KB): 1, 10, 100
Working Dir: .\Temp
Restore Dir: .\Temp\Retrieve
Log File: .\JCenteraVerify.log
Delete temp Files: true
Delete restore Files: true
SDK SETTINGS
Number of Retries: -1
Retry Sleep: -1
----------------- JCenteraVerify test results -------------------
ACCESS NODE CONNECTIVITY CHECK
192.168.82.9?C:\Installs\appve.pea is not available.
FP_AUTHENTICATION_FAILED_ERR -10153
**************************************************************
***************** End of JCenteraVerify log ****************
Config# show profile detail appve
Centera Profile Detail Report
------------------------------------------------------
Generated on 14 Август 2008 г. 17:59:34 YEKST
Profile Name: appve
Profile Enabled: yes
Profile Secret Persistency Format: obfuscated
IP Restrictions:
Data Access Capabilities:
Profile-metadata Capability: on (disabled by clustermask)
Home Pool: appve
Profile Type: Access
Cluster Mask: rdqe-cw--h
Granted Rights in Application Pools:
Pool Name Pool Mask Granted Effective
----------------------------------------------------------------------
app rdqeDcwh rdqeDcw- rdqe-cw-
----------------------------------------------------------------------
Scratchpad Pool Mapping: -
Active Pool Mapping: -
Cluster Management Roles: none
Config#
Message was edited by:
Aleksandr
**************************************************************
************** Start of JCenteraVerify log ******************
**************************************************************
--------------------- General information -----------------------
Time: Thu Aug 14 18:03:29 YEKST 2008
Tool Version: 3.2.23
SDK Version: 3.2.607
--------------------- User configuration ------------------------
TOOL SETTINGS
Number Of Files: 3
FileSize (KB): 1, 10, 100
Working Dir: .\Temp
Restore Dir: .\Temp\Retrieve
Log File: .\JCenteraVerify.log
Delete temp Files: true
Delete restore Files: true
SDK SETTINGS
Number of Retries: -1
Retry Sleep: -1
----------------- JCenteraVerify test results -------------------
ACCESS NODE CONNECTIVITY CHECK
192.168.82.9?C:\Installs\appve.pea is not available.
FP_AUTHENTICATION_FAILED_ERR -10153
**************************************************************
***************** End of JCenteraVerify log ****************
Config# show profile detail appve
Centera Profile Detail Report
------------------------------------------------------
Generated on 14 Август 2008 г. 17:59:34 YEKST
Profile Name: appve
Profile Enabled: yes
Profile Secret Persistency Format: obfuscated
IP Restrictions:
Data Access Capabilities:
Profile-metadata Capability: on (disabled by clustermask)
Home Pool: appve
Profile Type: Access
Cluster Mask: rdqe-cw--h
Granted Rights in Application Pools:
Pool Name Pool Mask Granted Effective
----------------------------------------------------------------------
app rdqeDcwh rdqeDcw- rdqe-cw-
----------------------------------------------------------------------
Scratchpad Pool Mapping: -
Active Pool Mapping: -
Cluster Management Roles: none
Config#
Message was edited by:
Aleksandr
- I had this issue recently and the issue was due to the .pea file secret not matching thep profile secret on the Centera. The customer recently experienced a power outage and when the Centeras came back up the DX media service would not come online. I regenterated the .pea files for bot Centeras, re-merged, and then tested again. This time the test was successful. I then replaced the .pea file on the DX server and the media service came online successfully.
EMCDennis
124 Posts
1274
2
Posted August 29th, 2008 06:00
FP_AUTHENTICATION_FAILED_ERR -10153
The "is not available" sounds like maybe it can't find the pea file - check the path/filename.
If cluster 192.168.82.9 has replication enabled, the SDK will automatically try to authenticate to the replica. This requires that the pool and profile be exported from 192.168.82.9 and imported onto the replica and a pea file created from the replica. You will then need to merge the pea files.
To disable the SDK from attempting to authenticate to the replica (to test your existing pea file), set the following environment variables:
export FP_OPTION_ENABLE_MULTICLUSTER_FAILOVER=0
export FP_OPTION_OPENSTRATEGY_OVERRIDE=1