Guest

Preview Tool

Cisco Bug: CSCvs47686 - B200M5 "end-point-unavailable Code: unspecified Message: no connection to MC endpoint"

Last Modified

Oct 04, 2020

Products (1)

  • Cisco Unified Computing System

Known Affected Releases

3.2(2d)B 3.2(3d)A 3.2(3h)A 4.0(2d)A 4.0(4b)A

Description (partial)

Symptom:
B200M5's will encounter the following issue, causing UCSM to lose all communication with the Blade.

Severity: Warning
Code: F77960
Last Transition Time: 2019-12-14T08:46:10.227
ID: 574574
Status: None
Description: [FSM:STAGE:REMOTE-ERROR]: Result: end-point-unavailable Code: unspecified Message: no connection to MC endpoint(sam:dme:ComputeBladeDiscover:BmcInventory)
Affected Object: sys/chassis-2/blade-3
Name: Fsm Sam Dme Compute Blade Discover Remote Inv
Cause: Bmc Inventory Failed
Type: Fsm
Acknowledged: No
Occurrences: 1
Creation Time: 2019-12-14T08:46:10.227
Original Severity: Warning
Previous Severity: Warning
Highest Severity: Warning

The OBFL logs will show mcserver write failed messages and the bioscomd process failing and trying to restart.

3:2019 Dec 14 05:51:37 EST:4.1(30b):mctool@127.5.254.1:13454: mcserver_net.c:422:Write failed, closing socket 3 - 127.5.254.1, opcode 103, ret -1
3:2019 Dec 14 05:51:37 EST:4.1(30b):mctool@127.5.254.1:14635: mcserver_net.c:422:Write failed, closing socket 3 - 127.5.254.1, opcode 103, ret -1
3:2019 Dec 14 05:51:37 EST:4.1(30b):mctool@127.5.254.1:19951: mcserver_net.c:422:Write failed, closing socket 3 - 127.5.254.1, opcode 103, ret -1

5:2019 Dec 14 05:51:38 EST:4.1(30b):doctor-bmc-app-mon:1427: app_monitor.c:515:cmp_proc_node_ctime: stat(/proc/2079) failed, errno 2 (No such file or directory)
5:2019 Dec 14 05:51:38 EST:4.1(30b):doctor-bmc-app-mon:1427: app_monitor.c:670:cmp_proc_node_ctime bioscomd stat(/proc/2079) returned errno 2 (No such file or directory)
4:2019 Dec 14 05:51:38 EST:4.1(30b):doctor-bmc-app-mon:1427: app_monitor.c:626:Restarting Process bioscomd

Conditions:
UCS B200 M5 
UCSM 3.2.x and 4.0.x
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.