Sun StorEdge[TM] 6130: Getting "communication lost" events on the management host with StorADE 2.4

Asset ID:	1-72-1011120.1
Update Date:	2010-10-14
Keywords:

Solution Type Problem Resolution Sure

Solution 1011120.1 : Sun StorEdge[TM] 6130: Getting "communication lost" events on the management host with StorADE 2.4

Applies to:

Sun Storage 6130 Array
All Platforms

Symptoms

Management host keeps getting "lost communication" for other data hosts or Sun StorEdge[TM] 6130 occasionally and we check connectivity using ping/telnet there seems to be no problem.

Following messages are logged on the management host by StorADE.
20051107220002.000000+0800      agent.CommunicationLostEvent    oob     Lost Communication with xxxx at 10.252.32.171      Sev:3   Action:TRUE     Enc:
mgmtLevel:D  AgentH:local    Agg:    ECode:agent.CommunicationLostEvent.oob  Topic:
...
...
20051107233002.000000+0800      agent.CommunicationLostEvent    oob     Lost Communication with xxxx at 10.252.32.158      Sev:3   Action:TRUE     Enc:
mgmtLevel:D  AgentH:local    Agg:    ECode:agent.CommunicationLostEvent.oob  Topic:
Note: This problem was discovered with Storade and SE6130 but it can happen with any storage array and Storade 2.4

Cause

This problem occurs if a master has a slave on a private network but doesn't have and entry for the slave in the /etc/hosts file.

Solution

SUNWstade Support Patch ID 117650-67

or any Sun StorageTek Common Array Manager version 5.0 or later.

6130, storade, EM
Previously Published As
83680

Change History
Date: 2006-02-10
User Name: 25440
Action: Approved
Comment: Publishing.
Version: 3
Date: 2006-02-10
User Name: 25440
Action: Accept
Comment:
Version: 0
Date: 2006-02-10
User Name: 71772
Action: Approved
Comment: Have checked the details of the two bugs and the escalation.
The information is correct.
Passing on to final review
Version: 0

Attachments

This solution has no attachment