EV9 Centera - 6760 - No access node can be found
Hello all,
While also working with EMC on this, I figured I'd ask here to see if anyone has seen this before.
On Journal Archving servers, we see the event 6760, indicating EV cannot find an Access Node for centera. I've verified that the ip-addresses in the Journal Partitions used are correct, and functioning. According to EMC, replication is fine. I do not have large queues, or large journalmailboxes, so it appears to be functioning fine. The error however is worrying me slightly. There is little internal knowledge on EMC Centera. The network-team is investigating possible firewall changes, no result yet. If any of you have seen this before, please advise?
Log Name: Symantec Enterprise Vault
Source: Enterprise Vault
Date: 26-2-2013 8:08:31
Event ID: 6760
Task Category: Storage File Watch
Level: Error
Keywords: Classic
User: N/A
Computer: SPNLAPP92515.domain.com
Description:
Error from EMC Centera FPLibrary
Function call: Cluster::DeleteBlob(BT7LDF9P7U3N4e5CNK61FJHUE8SG415PAVTP1E0H67ICDQVP2NRLR,,0)<ClusterCloud::DeleteBlob(BT7LDF9P7U3N4e5CNK61FJHUE8SG415PAVTP1E0H67ICDQVP2NRLR,,0) with 6 retries<FPClip::Delete(pool,BT7LDF9P7U3N4e5CNK61FJHUE8SG415PAVTP1E0H67ICDQVP2NRLR,,0)<_FPClip_Delete(pool,BT7LDF9P7U3N4e5CNK61FJHUE8SG415PAVTP1E0H67ICDQVP2NRLR,NULL,0)<FPClip_Delete(-,BT7LDF9P7U3N4e5CNK61FJHUE8SG415PAVTP1E0H67ICDQVP2NRLR)
Status: FP_ACCESSNODE_ERR (-10103)
Reason: No Access Node can be found
Pool Address: 10.131.139.1:3218,10.131.139.2:3218,10.131.139.3:3218,10.131.139.4:3218?\\servername\EVCentera\prf_ev.pea
(edited domain.com and servername)
The 'Test Settings' and 'Test' on the connection-tab of the partitions does not give an error.
Thanks,
Gertjan
Comments 2 Comments • Jump to latest comment
To me it sounds like it might be an issue with the replica, deletes are always processed against the replica first, so it could be an issue attempting to send the delete to that replica first but the ip address is incorrect etc
EMC API Guide just shows that its network related, and to verify the ip address that you are using is correct etc, so it could also be a routing problem or network binding problem etc..
Working on network issues. There might have been a firewall change or something. Using a telnet to the ipaddresses and ports listed shows only a connection possible to 1 of the 4 addresses.
Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl
www.quadrotech-it.com
www.symantec.com/vision
Would you like to reply?
Login or Register to post your comment.