How to fix error time out communicating with DME

[sendi-septiawan]

Hi all,

I have Fabric Interconnect 6120 firmware 1.4(1m),  suddenly my UCS manager problem error is "Software Error: Exception during execution: [Error: Timed out communicating with DME]" and my console ucs manager via GUI error is aplication to time out and to ask relogin.

thanks for response.

[padramas]

Hello,

Can you please share output of following commands

connect local-mgmt a

show cluster extended-state

show pmon state

connect local-mgmt b

show cluster extended-state

show pmon state

Padma

[sendi-septiawan]

hello Padma,

thanks for response my discussion.

FI-A --> Down

FI-B --> Primarry

FabricInterconnect-B(local-mgmt)# show cluster state

Cluster Id: 0x11993bd2409d11e0-0xb674000573c97984

Cluster State not available, cluster id mismatch:

local: 11993bd2-409d-11e0-b674-000573c97984, peer: 1054c1ba-f437-11e2-86a1-000de

cd2a804

B: UP, PRIMARY

A: DOWN, INAPPLICABLE

INTERNAL NETWORK INTERFACES:

eth1, DOWN

eth2, DOWN

HA NOT READY

Peer Fabric Interconnect is down

Cluster State not available, cluster id mismatch:

local: 11993bd2-409d-11e0-b674-000573c97984, peer: 1054c1ba-f437-11e2-86a1-000de

cd2a804

FabricInterconnect-B(local-mgmt)# show pmon state

SERVICE NAME             STATE     RETRY(MAX)    EXITCODE    SIGNAL    CORE

------------             -----     ----------    --------    ------    ----

svc_sam_controller     running           0(4)           0         0      no

svc_sam_dme            running       51167(4)           0        11     yes

svc_sam_dcosAG         running           0(4)           0         0      no

svc_sam_bladeAG        running          13(4)           0         6     yes

svc_sam_portAG         running           2(4)           0        11     yes

svc_sam_statsAG        running           0(4)           0         0      no

svc_sam_hostagentAG    running           0(4)           0         0      no

svc_sam_nicAG          running           0(4)           0         0      no

svc_sam_licenseAG      running           0(4)           0         0      no

svc_sam_extvmmAG       running           0(4)           0         0      no

httpd.sh               running           0(4)           0         0      no

svc_sam_sessionmgrAG   running           0(4)           0         0      no

svc_sam_pamProxy       running           0(4)           0         0      no

sfcbd                  running           0(4)           0         0      no

dhcpd                  running           0(4)           0         0      no

sam_core_mon           running           0(4)           0         0      no

svc_sam_rsdAG          running           0(4)           0         0      no

sendi

[padramas]

Hello Sendi,

Are you able to ping / SSH into FI  A ?

Any information on why FI A is down ?

I would suggest you to open a TAC service request to further investigate the issue.

Padma

[sendi-septiawan]

Hi,

FI-A down because the firmware is crash. so FI-A to suggest open TAC, and now progress download firmware to FI and install firmware.

oke thanks for information.

sendi

[Abhayvaya70297]

Hi,

Thanks for raising this. We are also facing this issue. Just wondering if you manage to fix or get around this issue.

- Abhay

[mahdi.ramezankhani]

Both Fabric interconnects think other FI is primary and itself is secondary. When this happens, DME functionality will not work and following error message is seen: "Software Error: Exception during execution: {Error: Timed out communicating with DME].

This is very corner condition case when for some unknown reasons, the two FIs were not able to communicate between themselves for some time period. This forced HA election mechanism to kicked in, but did not successfully complete.

# connect local-mgmt

(local-mgmt)# cluster force primary