Guest

Preview Tool

Cisco Bug: CSCut02412 - Nexus 1000v Service "vms" hasn't caught signal 11 SV3(1.2)

Last Modified

Aug 29, 2017

Products (3)

  • Cisco Nexus 1000V Switch for VMware vSphere
  • Cisco Nexus 1000V Switch
  • Cisco Application Virtual Switch

Known Affected Releases

5.2(1)SV3(1.2) 5.2(1)SV3(1.4)

Description (partial)

Symptom:
vms service cores causing a VSM reboot, and failover.

version 5.2(1)SV3(1.2)

2015 Feb 10 13:26:17 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-2-SERVICE_CRASHED: Service "vms" (PID 3605) hasn't caught signal 11 (core will be saved).
2015 Feb 10 13:26:17 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-3-SERVICE_TERMINATED: Service "vms" (PID 9487) has finished with error code SYSMGR_EXITCODE_USERDEF (64).
2015 Feb 10 13:26:18 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-3-SERVICE_TERMINATED: Service "vms" (PID 9505) has finished with error code SYSMGR_EXITCODE_USERDEF (64).
2015 Feb 10 13:26:18 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-3-SERVICE_TERMINATED: Service "vms" (PID 9510) has finished with error code SYSMGR_EXITCODE_USERDEF (64).
2015 Feb 10 13:26:18 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-2-SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG: This supervisor will temporarily remain online in order to collect show tech-support. This behavior is configurable via 'system [no] auto-collect tech-support'.
2015 Feb 10 13:26:18 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active (pre-start phase).
2015 Feb 10 13:26:18 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-2-HASWITCHOVER_START: Supervisor 1 is becoming active.
2015 Feb 10 13:26:18 corp-pilot-dvs-3 Feb 10 13:26:18 %KERN-3-SYSTEM_MSG: redun_platform_ioctl : Host name is set corp-pilot-dvs-3 - kernel
2015 Feb 10 13:26:18 corp-pilot-dvs-3 Feb 10 13:26:18 %KERN-3-SYSTEM_MSG: stun_remove_arp_entry: Remove slot 1 - kernel
2015 Feb 10 13:26:19 corp-pilot-dvs-3 last message repeated 3 times
2015 Feb 10 13:26:19 corp-pilot-dvs-3 vdc_mgr[2819]: %VDC_MGR-5-VDC_STATE_CHANGE: vdc 1 state changed to active 
2015 Feb 10 13:26:19 corp-pilot-dvs-3 vdc_mgr[2819]: %VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to m1 f1 m1xl  
2015 Feb 10 13:26:20 corp-pilot-dvs-3 sysmgr[1318]: %SYSMGR-2-SWITCHOVER_OVER: Switchover completed.

`show cores`
Module  Instance  Process-name     PID       Date(Year-Month-Day Time)
------  --------  ---------------  --------  -------------------------
2       1         vms              3605      2015-02-10 13:30:31
2       2         vms              3605      2015-02-10 13:30:36
2       3         vms              3605      2015-02-10 13:30:39

Conditions:
The VMS crash is a consequence of broken connection between VSM and VC.

2015 Feb 18 09:36:39 corp-pilot-dvs-3 vms[3513]: %VMS-3-DVS_UPDATE_ERROR: Unable to Update DVS in the VMware vCenterError: [VMware vCenter Server 5.5.0 build-2183111] Operation could not be completed due to connection failure.End of file or no input: Operation interrupted or timed out after 160s send or 160s r030751

 If the connection between VSM and VC is restored, we shouldn't be seeing the crash.
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.