EPAgP on 3750X with VSS
Hello all,
I'm right now testing VSS dual active detection using EPAgP on a 3750X Stack.
I've noticed that CrossStack Etherchannel is ONLY supported within a Stack if both aggregated links belongs to the same unit...so if I use "desirable" mode all the links should be connected in example to unit1. This is what I would like to avoid having a channel with aggregated interfaces on the same unit of the Stack (very strange restriction moreover considering PAgP is Cisco proprietary).
What about using channel mode ON? Forcing the ports to belong to a channel without negotiating can be configured on all the units of a Stack with no restricitons...Is this gonna work? Or EPAgP requires all the ports of the Etherchannel on both the VSS and Stack units configured as desirable?
Thanks a lot for sharing ideas...
Omar
Hi Omar,
Indeed the limitation comes from the 3750 which does not support cross-stack PagP (so ePagp will not be supported as well in a cross-stack fashion).
As Glen stated LACP is recommended (but you will loose VSS dual active detection).
Otherwise you will have indeed to use ePagp through the same unit.
It is document by the VSS guide => http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch4.html#wp1129136 (look at Enhanced PAgP Support part) :
"PAgP is supported in all platforms except the Cisco Catalyst 37xx stack configuration in which cross-stack EtherChannel (LACP) is required to have MEC-connectivity with the VSS. Because cross-stack EtherChannel does not support PAgP, it cannot use enhanced PAgP for dual-active detection. A common approach to resolve this gap in support is to use two EtherChannel links from the same stack member. This solution is a non-optimal design choice because"
Best regards.
Karim
Similar Messages
-
A Problem with VSS in the 6509
Hello,
I have a problem with VSS in the 6500, when the switch 1 is active,probably a few months will switchover to switch 2 and switch 1 reload.
config:
switch virtual domain 1
switch mode virtual
switch 1 priority 110
switch 2 priority 110
interface Port-channel1
description To 6509-B-VSS
no switchport
no ip address
switch virtual link 1
mls qos trust cos
no mls qos channel-consistency
interface Port-channel2
description 6509-A-VSS
no switchport
no ip address
switch virtual link 2
mls qos trust cos
no mls qos channel-consistency
interface GigabitEthernet1/4/20
no switchport
no ip address
dual-active fast-hello
interface TenGigabitEthernet1/5/4
description To 6509-B-VSS
no switchport
no ip address
mls qos trust cos
channel-group 1 mode on
interface TenGigabitEthernet1/5/5
description To 6509-B-VSS
no switchport
no ip address
mls qos trust cos
channel-group 1 mode on
interface GigabitEthernet2/4/20
no switchport
no ip address
dual-active fast-hello
interface TenGigabitEthernet2/5/4
description To 6509-A-VSS
no switchport
no ip address
mls qos trust cos
channel-group 2 mode on
interface TenGigabitEthernet2/5/5
description To 6509-A-VSS
no switchport
no ip address
mls qos trust cos
channel-group 2 mode on
show switch virtual redundancy
My Switch Id = 2
Peer Switch Id = 1
Last switchover reason = active unit removed
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso
Switch 2 Slot 5 Processor Information :
Current Software state = ACTIVE
Uptime in current state = 5 hours, 24 minutes
Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-M), Version 12.2(33)SXJ5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 31-Jan-13 14:30 by prod_rel_team
BOOT = sup-bootdisk:/s72033-ipbasek9-mz.122-33.SXJ5.bin,12;
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = ACTIVE
Switch 1 Slot 5 Processor Information :
Current Software state = STANDBY HOT (switchover target)
Uptime in current state = 5 hours, 18 minutes
Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPBASEK9-M), Version 12.2(33)SXJ5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 31-Jan-13 14:30 by prod_rel_team
BOOT = sup-bootdisk:/s72033-ipbasek9-mz.122-33.SXJ5.bin,12;
Configuration register = 0x2102
Fabric State = ACTIVE
Control Plane State = STANDBY
show log
Jun 21 11:20:52.742: %VSL-SW2_SPSTBY-5-VSL_CNTRL_LINK: New VSL Control Link Te2/5/4
Jun 21 11:20:52.786: %VSLP-SW2_SPSTBY-3-VSLP_LMP_FAIL_REASON: Te2/5/4: Link down
Jun 21 11:20:52.786: %VSLP-SW2_SPSTBY-2-VSL_DOWN: Last VSL interface Te2/5/4 went down
Jun 21 11:20:52.790: %VSLP-SW2_SPSTBY-2-VSL_DOWN: All VSL links went down while switch is in Standby role
Jun 21 11:20:52.790: %DUAL_ACTIVE-SW2_SPSTBY-1-VSL_DOWN: VSL is down - switchover, or possible dual-active situation has occurred
Jun 21 11:20:53.622: %SYS-SW2_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
Jun 21 11:20:54.678: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
Jun 21 11:20:54.682: %C6KPWR-SP-4-PSOK: power supply 2 turned on.
Jun 21 11:20:54.738: %SATVS_IBC-SW2_SP-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:0x4/0x4, SSAP/DSAP:0x19/0x0, OP/SEQ:0x320/0x8FD9, SIG/INFO:0x1/0x502, eSA:0000.0500.0000)
Jun 21 11:20:56.490: %SATVS_IBC-5-VSL_DOWN_SCP_DROP: VSL inactive - dropping cached SCP packet: (SA/DA:0x14/0x4, SSAP/DSAP:0x18/0x0, OP/SEQ:0x19/0x98, SIG/INFO:0x1/0x502, eSA:0000.1500.0000)
Jun 21 11:21:02.125: %VSDA-SW2_SP-3-LINK_DOWN: Interface Gi2/4/20 is no longer dual-active detection capable
Jun 21 11:23:27.719: %VSLP-SW2_SP-5-RRP_ROLE_RESOLVED: Role resolved as ACTIVE by VSLP
Jun 21 11:23:27.719: %VSL-SW2_SP-5-VSL_CNTRL_LINK: New VSL Control Link Te2/5/4
Jun 21 11:23:27.799: %VSLP-SW2_SP-5-VSL_UP: Ready for control traffic
Jun 21 11:24:43.346: %PFINIT-SW2_SP-5-CONFIG_SYNC: Sync'ing the startup configuration to the standby Router.
Jun 21 11:25:35.304: %VSLP-SW2_SP-5-VSL_UP: Ready for data traffic
Jun 21 11:25:14.946: %C6KPWR-SW1_SPSTBY-4-PSOK: power supply 1 turned on.
Jun 21 11:25:14.950: %C6KPWR-SW1_SPSTBY-4-PSOK: power supply 2 turned on.
Jun 21 11:25:16.975: %FABRIC-SW1_SPSTBY-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 5.
Jun 21 11:25:16.975: %FABRIC-SW1_SPSTBY-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
Jun 21 11:26:13.738: %SYS-SW1_SPSTBY-5-RESTART: System restarted --
Jun 21 11:26:20.446: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:01:47 to ensure console debugging output.
Jun 21 11:26:32.056: %RF-SW2_SP-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Jun 21 11:27:56.962: %SYS-SW1_SPSTBY-3-LOGGER_FLUSHED: System was paused for 00:01:24 to ensure console debugging output.
Jun 21 11:27:53.970: %SYS-DFC4-5-RESTART: System restarted --
Jun 21 11:28:34.222: %VSDA-SW1_SPSTBY-5-LINK_UP: Interface Gi1/4/20 is now dual-active detection capable
Jun 21 11:28:36.236: %VSDA-SW2_SP-5-LINK_UP: Interface Gi2/4/20 is now dual-active detection capable
Best Regardhi,
Information of Last System Crash - SP
Writing crashinfo to bootflash:crashinfo_SP_20140621-192052-TW 00 07 00 00 00 00 00 00 00 0F 00 00 00 00 00 00 10 D6 0A 06 FD 37 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
Jun 21 11:19:43.723: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.723: SW1_SP: IPC: Message 504CA554 timed out waiting for Ack
Jun 21 11:19:43.723: SW1_SP: IPC: MSG: ptr: 0x504CA554, flags: 0x24100, retries: 8, seq: 0x315E1ED, refcount: 1, rpc_result = 0x0, data_buffer = 0x504104BC, header = 0x8A453C8, data = 0x8A453E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57837, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF38, lo: 0x8A453E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 5E 0A 06 01 01 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
Jun 21 11:19:43.723: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504CA554, flags: 0x24100, retries: 8, seq: 0x315E1ED, refcount: 1, rpc_result = 0x0, data_buffer = 0x504104BC, header = 0x8A453C8, data = 0x8A453E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57837, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF38, lo: 0x8A453E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 5E 0A 06 01 01 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
Jun 21 11:19:43.727: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.727: SW1_SP: IPC: Message 4528FE20 timed out waiting for Ack
Jun 21 11:19:43.727: SW1_SP: IPC: MSG: ptr: 0x4528FE20, flags: 0x24100, retries: 8, seq: 0x315E1EE, refcount: 1, rpc_result = 0x0, data_buffer = 0x4520B23C, header = 0x8C884C8, data = 0x8C884E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57838, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF39, lo: 0x8C884E8 || DATA: 2C D5 00 01 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 40 0A 06 0A 15 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
Jun 21 11:19:43.727: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4528FE20, flags: 0x24100, retries: 8, seq: 0x315E1EE, refcount: 1, rpc_result = 0x0, data_buffer = 0x4520B23C, header = 0x8C884C8, data = 0x8C884E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57838, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF39, lo: 0x8C884E8 || DATA: 2C D5 00 01 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 40 0A 06 0A 15 01 04 00 00 00 87 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
Jun 21 11:19:43.727: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.727: SW1_SP: IPC: Message 4529E380 timed out waiting for Ack
Jun 21 11:19:43.727: SW1_SP: IPC: MSG: ptr: 0x4529E380, flags: 0x24100, retries: 8, seq: 0x315E1EF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50418920, header = 0x8A93DC8, data = 0x8A93DE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57839, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3A, lo: 0x8A93DE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 12 00 00 00 00 00 00 08 9E 0A 06 9A 0B 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 16 00 00
Jun 21 11:19:43.727: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4529E380, flags: 0x24100, retries: 8, seq: 0x315E1EF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50418920, header = 0x8A93DC8, data = 0x8A93DE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57839, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3A, lo: 0x8A93DE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 12 00 00 00 00 00 00 08 9E 0A 06 9A 0B 01 04 00 00 00 BC 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 16 00 00
Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.731: SW1_SP: IPC: Message 45238524 timed out waiting for Ack
Jun 21 11:19:43.731: SW1_SP: IPC: MSG: ptr: 0x45238524, flags: 0x24100, retries: 8, seq: 0x315E1F0, refcount: 1, rpc_result = 0x0, data_buffer = 0x50372694, header = 0x8468FC8, data = 0x8468FE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57840, sz: 1332, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3B, lo: 0x8468FE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 03 74 0A 06 FD 4C 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45238524, flags: 0x24100, retries: 8, seq: 0x315E1F0, refcount: 1, rpc_result = 0x0, data_buffer = 0x50372694, header = 0x8468FC8, data = 0x8468FE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57840, sz: 1332, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AF3B, lo: 0x8468FE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 03 74 0A 06 FD 4C 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.731: SW1_SP: IPC: Message 4524C89C timed out waiting for Ack
Jun 21 11:19:43.731: SW1_SP: IPC: MSG: ptr: 0x4524C89C, flags: 0x24100, retries: 6, seq: 0x315E1F1, refcount: 1, rpc_result = 0x0, data_buffer = 0x451B45EC, header = 0x894FCC8, data = 0x894FCE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57841, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFE9, lo: 0x894FCE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4524C89C, flags: 0x24100, retries: 6, seq: 0x315E1F1, refcount: 1, rpc_result = 0x0, data_buffer = 0x451B45EC, header = 0x894FCC8, data = 0x894FCE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57841, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFE9, lo: 0x894FCE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 01 00 00
Jun 21 11:19:43.731: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.731: SW1_SP: IPC: Message 45268348 timed out waiting for Ack
Jun 21 11:19:43.731: SW1_SP: IPC: MSG: ptr: 0x45268348, flags: 0x24100, retries: 6, seq: 0x315E1F2, refcount: 1, rpc_result = 0x0, data_buffer = 0x50462254, header = 0x8D4EFC8, data = 0x8D4EFE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57842, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEA, lo: 0x8D4EFE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 38 00 00 00 00 00 00 26 AB 0A 06 05 41 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 19 00 00
Jun 21 11:19:43.731: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45268348, flags: 0x24100, retries: 6, seq: 0x315E1F2, refcount: 1, rpc_result = 0x0, data_buffer = 0x50462254, header = 0x8D4EFC8, data = 0x8D4EFE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57842, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEA, lo: 0x8D4EFE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 38 00 00 00 00 00 00 26 AB 0A 06 05 41 01 04 00 00 00 86 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 19 00 00
Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.735: SW1_SP: IPC: Message 45281D58 timed out waiting for Ack
Jun 21 11:19:43.735: SW1_SP: IPC: MSG: ptr: 0x45281D58, flags: 0x24100, retries: 6, seq: 0x315E1F3, refcount: 1, rpc_result = 0x0, data_buffer = 0x45201860, header = 0x8C2CEC8, data = 0x8C2CEE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57843, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEB, lo: 0x8C2CEE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 B9 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 97 0D 01 04 00 00 00 BB 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.735: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45281D58, flags: 0x24100, retries: 6, seq: 0x315E1F3, refcount: 1, rpc_result = 0x0, data_buffer = 0x45201860, header = 0x8C2CEC8, data = 0x8C2CEE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57843, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEB, lo: 0x8C2CEE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 B9 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 97 0D 01 04 00 00 00 BB 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.735: SW1_SP: IPC: Message 504A2D18 timed out waiting for Ack
Jun 21 11:19:43.735: SW1_SP: IPC: MSG: ptr: 0x504A2D18, flags: 0x24100, retries: 6, seq: 0x315E1F4, refcount: 1, rpc_result = 0x0, data_buffer = 0x451F3A88, header = 0x8BA92C8, data = 0x8BA92E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57844, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEC, lo: 0x8BA92E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 01 48 0A 06 FD 2F 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00
Jun 21 11:19:43.735: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504A2D18, flags: 0x24100, retries: 6, seq: 0x315E1F4, refcount: 1, rpc_result = 0x0, data_buffer = 0x451F3A88, header = 0x8BA92C8, data = 0x8BA92E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57844, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFEC, lo: 0x8BA92E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 05 00 00 00 00 00 00 01 48 0A 06 FD 2F 01 04 00 00 00 DD 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00
Jun 21 11:19:43.735: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.735: SW1_SP: IPC: Message 504AA128 timed out waiting for Ack
Jun 21 11:19:43.735: SW1_SP: IPC: MSG: ptr: 0x504AA128, flags: 0x24100, retries: 6, seq: 0x315E1F5, refcount: 1, rpc_result = 0x0, data_buffer = 0x45228364, header = 0x8D9C8C8, data = 0x8D9C8E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57845, sz: 568, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFED, lo: 0x8D9C8E8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 26 00 0D 00 10 02 20 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00 00 00 00 00 02 3D 0A 06 FE 6C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 2D 00 00
Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504AA128, flags: 0x24100, retries: 6, seq: 0x315E1F5, refcount: 1, rpc_result = 0x0, data_buffer = 0x45228364, header = 0x8D9C8C8, data = 0x8D9C8E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57845, sz: 568, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56AFED, lo: 0x8D9C8E8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 26 00 0D 00 10 02 20 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00 00 00 00 00 02 3D 0A 06 FE 6C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 2D 00 00
Jun 21 11:19:43.739: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.739: SW1_SP: IPC: Message 504C15B4 timed out waiting for Ack
Jun 21 11:19:43.739: SW1_SP: IPC: MSG: ptr: 0x504C15B4, flags: 0x24100, retries: 4, seq: 0x315E1F6, refcount: 1, rpc_result = 0x0, data_buffer = 0x503C193C, header = 0x87593C8, data = 0x87593E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57846, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08B, lo: 0x87593E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 3B 00 00 00 00 00 00 10 A7 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 3B 00 00
Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504C15B4, flags: 0x24100, retries: 4, seq: 0x315E1F6, refcount: 1, rpc_result = 0x0, data_buffer = 0x503C193C, header = 0x87593C8, data = 0x87593E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57846, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08B, lo: 0x87593E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 3B 00 00 00 00 00 00 10 A7 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 3B 00 00
Jun 21 11:19:43.739: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.739: SW1_SP: IPC: Message 45273050 timed out waiting for Ack
Jun 21 11:19:43.739: SW1_SP: IPC: MSG: ptr: 0x45273050, flags: 0x24100, retries: 4, seq: 0x315E1F7, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044348C, header = 0x8C29BC8, data = 0x8C29BE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57847, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08C, lo: 0x8C29BE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00 00 00 00 00 02 24 0A 06 0C 18 01 04 00 00 00 98 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.739: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45273050, flags: 0x24100, retries: 4, seq: 0x315E1F7, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044348C, header = 0x8C29BC8, data = 0x8C29BE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57847, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08C, lo: 0x8C29BE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00 00 00 00 00 02 24 0A 06 0C 18 01 04 00 00 00 98 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.743: SW1_SP: IPC: Message 452A33E4 timed out waiting for Ack
Jun 21 11:19:43.743: SW1_SP: IPC: MSG: ptr: 0x452A33E4, flags: 0x24100, retries: 4, seq: 0x315E1F8, refcount: 1, rpc_result = 0x0, data_buffer = 0x50432830, header = 0x8B8A5C8, data = 0x8B8A5E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57848, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08D, lo: 0x8B8A5E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C4 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 A2 0B 01 04 00 00 00 C5 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.743: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452A33E4, flags: 0x24100, retries: 4, seq: 0x315E1F8, refcount: 1, rpc_result = 0x0, data_buffer = 0x50432830, header = 0x8B8A5C8, data = 0x8B8A5E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57848, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08D, lo: 0x8B8A5E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C4 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 04 24 0A 06 A2 0B 01 04 00 00 00 C5 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00
Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.743: SW1_SP: IPC: Message 4523FFA4 timed out waiting for Ack
Jun 21 11:19:43.743: SW1_SP: IPC: MSG: ptr: 0x4523FFA4, flags: 0x24100, retries: 4, seq: 0x315E1F9, refcount: 1, rpc_result = 0x0, data_buffer = 0x5036F47C, header = 0x844B3C8, data = 0x844B3E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57849, sz: 772, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08E, lo: 0x844B3E8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 F2 00 0D 00 16 02 EC 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 01 46 0A 06 FE 5A 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
Jun 21 11:19:43.743: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4523FFA4, flags: 0x24100, retries: 4, seq: 0x315E1F9, refcount: 1, rpc_result = 0x0, data_buffer = 0x5036F47C, header = 0x844B3C8, data = 0x844B3E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57849, sz: 772, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B08E, lo: 0x844B3E8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 02 F2 00 0D 00 16 02 EC 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 01 46 0A 06 FE 5A 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
Jun 21 11:19:43.743: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.743: SW1_SP: IPC: Message 45279200 timed out waiting for Ack
Jun 21 11:19:43.743: SW1_SP: IPC: MSG: ptr: 0x45279200, flags: 0x24100, retries: 2, seq: 0x315E1FA, refcount: 1, rpc_result = 0x0, data_buffer = 0x5039C3B0, header = 0x85F65C8, data = 0x85F65E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57850, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B123, lo: 0x85F65E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x45279200, flags: 0x24100, retries: 2, seq: 0x315E1FA, refcount: 1, rpc_result = 0x0, data_buffer = 0x5039C3B0, header = 0x85F65C8, data = 0x85F65E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57850, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B123, lo: 0x85F65E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
Jun 21 11:19:43.747: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.747: SW1_SP: IPC: Message 504D3544 timed out waiting for Ack
Jun 21 11:19:43.747: SW1_SP: IPC: MSG: ptr: 0x504D3544, flags: 0x24100, retries: 2, seq: 0x315E1FB, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044AE34, header = 0x8C71FC8, data = 0x8C71FE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57851, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B124, lo: 0x8C71FE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 04 48 0A 06 0B 24 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504D3544, flags: 0x24100, retries: 2, seq: 0x315E1FB, refcount: 1, rpc_result = 0x0, data_buffer = 0x5044AE34, header = 0x8C71FC8, data = 0x8C71FE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57851, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B124, lo: 0x8C71FE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00 00 00 00 00 04 48 0A 06 0B 24 01 04 00 00 00 89 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 04 00 00
Jun 21 11:19:43.747: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.747: SW1_SP: IPC: Message 504D5940 timed out waiting for Ack
Jun 21 11:19:43.747: SW1_SP: IPC: MSG: ptr: 0x504D5940, flags: 0x24100, retries: 2, seq: 0x315E1FC, refcount: 1, rpc_result = 0x0, data_buffer = 0x4521415C, header = 0x8CDD4C8, data = 0x8CDD4E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57852, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B125, lo: 0x8CDD4E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 0E 6D 0A 06 9C 5C 01 04 00 00 00 BF 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
Jun 21 11:19:43.747: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504D5940, flags: 0x24100, retries: 2, seq: 0x315E1FC, refcount: 1, rpc_result = 0x0, data_buffer = 0x4521415C, header = 0x8CDD4C8, data = 0x8CDD4E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57852, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B125, lo: 0x8CDD4E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 BE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 0E 6D 0A 06 9C 5C 01 04 00 00 00 BF 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 08 00 00
Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.751: SW1_SP: IPC: Message 452989EC timed out waiting for Ack
Jun 21 11:19:43.751: SW1_SP: IPC: MSG: ptr: 0x452989EC, flags: 0x24100, retries: 2, seq: 0x315E1FD, refcount: 1, rpc_result = 0x0, data_buffer = 0x45172660, header = 0x86DCEC8, data = 0x86DCEE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57853, sz: 1060, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B126, lo: 0x86DCEE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 3E 0A 06 FE 1D 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 BF 00 00
Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452989EC, flags: 0x24100, retries: 2, seq: 0x315E1FD, refcount: 1, rpc_result = 0x0, data_buffer = 0x45172660, header = 0x86DCEC8, data = 0x86DCEE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57853, sz: 1060, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B126, lo: 0x86DCEE8 || DATA: 2C D5 00 00 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 3E 0A 06 FE 1D 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 03 BF 00 00
Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.751: SW1_SP: IPC: Message 504C9DAC timed out waiting for Ack
Jun 21 11:19:43.751: SW1_SP: IPC: MSG: ptr: 0x504C9DAC, flags: 0x24108, retries: 0, seq: 0x315E1FE, refcount: 1, rpc_result = 0x0, data_buffer = 0x451D3748, header = 0x8A772C8, data = 0x8A772E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57854, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D4, lo: 0x8A772E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 97 00 00
Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504C9DAC, flags: 0x24108, retries: 0, seq: 0x315E1FE, refcount: 1, rpc_result = 0x0, data_buffer = 0x451D3748, header = 0x8A772C8, data = 0x8A772E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57854, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D4, lo: 0x8A772E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 CF 0A 06 01 06 01 04 00 00 00 3F 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 97 00 00
Jun 21 11:19:43.751: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.751: SW1_SP: IPC: Message 4525926C timed out waiting for Ack
Jun 21 11:19:43.751: SW1_SP: IPC: MSG: ptr: 0x4525926C, flags: 0x24108, retries: 0, seq: 0x315E1FF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50405568, header = 0x89DD1C8, data = 0x89DD1E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57855, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D5, lo: 0x89DD1E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 80 0A 06 0B 24 01 04 00 00 00 8A 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
Jun 21 11:19:43.751: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x4525926C, flags: 0x24108, retries: 0, seq: 0x315E1FF, refcount: 1, rpc_result = 0x0, data_buffer = 0x50405568, header = 0x89DD1C8, data = 0x89DD1E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57855, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D5, lo: 0x89DD1E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 88 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 06 00 00 00 00 00 00 01 80 0A 06 0B 24 01 04 00 00 00 8A 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 02 00 00
Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.755: SW1_SP: IPC: Message 452512E0 timed out waiting for Ack
Jun 21 11:19:43.755: SW1_SP: IPC: MSG: ptr: 0x452512E0, flags: 0x24108, retries: 0, seq: 0x315E200, refcount: 1, rpc_result = 0x0, data_buffer = 0x451AF00C, header = 0x891CCC8, data = 0x891CCE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57856, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D6, lo: 0x891CCE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C0 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0B 00 00 00 00 00 00 04 B2 0A 06 9E 0B 01 04 00 00 00 C3 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 17 00 00
Jun 21 11:19:43.755: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x452512E0, flags: 0x24108, retries: 0, seq: 0x315E200, refcount: 1, rpc_result = 0x0, data_buffer = 0x451AF00C, header = 0x891CCC8, data = 0x891CCE8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57856, sz: 1008, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D6, lo: 0x891CCE8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 03 E0 00 0D 00 1D 03 DA 01 04 00 00 00 C0 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0B 00 00 00 00 00 00 04 B2 0A 06 9E 0B 01 04 00 00 00 C3 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 17 00 00
Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:43.755: SW1_SP: IPC: Message 504A9C90 timed out waiting for Ack
Jun 21 11:19:43.755: SW1_SP: IPC: MSG: ptr: 0x504A9C90, flags: 0x24108, retries: 0, seq: 0x315E201, refcount: 1, rpc_result = 0x0, data_buffer = 0x45158028, header = 0x85E22C8, data = 0x85E22E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57857, sz: 736, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D7, lo: 0x85E22E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 02 D0 00 0D 00 15 02 CA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 03 4E 0A 06 FE 4C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 C2 00 00
Jun 21 11:19:43.755: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504A9C90, flags: 0x24108, retries: 0, seq: 0x315E201, refcount: 1, rpc_result = 0x0, data_buffer = 0x45158028, header = 0x85E22C8, data = 0x85E22E8 || HDR: src: 0x10000, dst: 0x315001B, index: 0, seq: 57857, sz: 736, type: 882, flags: 0x400, ext_flags: 0x0, hi: 0xA56B1D7, lo: 0x85E22E8 || DATA: 2C D5 00 02 0E 0B 00 00 00 00 00 20 00 00 02 D0 00 0D 00 15 02 CA 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 00 0A 00 00 00 00 00 00 03 4E 0A 06 FE 4C 01 04 00 00 00 DE 00 00 00 00 00 00 00 07 00 00 00 00 00 00 01 C2 00 00
Jun 21 11:19:43.755: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:19:52.687: %CPU_MONITOR-SW1_SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 120 seconds [21/1]
Jun 21 11:20:22.687: %CPU_MONITOR-SW1_SP-6-NOT_HEARD: CPU_MONITOR messages have not been heard for 150 seconds [21/1]
Jun 21 11:20:33.175: SW1_SP: IPC: Message 504F68E8 timed out waiting for Ack
Jun 21 11:20:33.175: SW1_SP: IPC: MSG: ptr: 0x504F68E8, flags: 0x34101, retries: 21, seq: 0x315AABD, refcount: 2, rpc_result = 0x0, data_buffer = 0x4517147C, header = 0x86D24C8, data = 0x86D24E8 || HDR: src: 0x10000, dst: 0x315000E, index: 1, seq: 43709, sz: 80, type: 1, flags: 0x1404, ext_flags: 0x0, hi: 0xA56AE85, lo: 0x86D24E8 || DATA: 00 00 00 15 00 00 00 00 00 00 07 D1 00 00 00 0A 00 00 00 0C 00 00 00 0F 00 00 00 05 00 00 00 0A 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jun 21 11:20:33.175: SW1_SP: IPC: Send failed: IPC msg timeout MSG: ptr: 0x504F68E8, flags: 0x34101, retries: 21, seq: 0x315AABD, refcount: 2, rpc_result = 0x0, data_buffer = 0x4517147C, header = 0x86D24C8, data = 0x86D24E8 || HDR: src: 0x10000, dst: 0x315000E, index: 1, seq: 43709, sz: 80, type: 1, flags: 0x1404, ext_flags: 0x0, hi: 0xA56AE85, lo: 0x86D24E8 || DATA: 00 00 00 15 00 00 00 00 00 00 07 D1 00 00 00 0A 00 00 00 0C 00 00 00 0F 00 00 00 05 00 00 00 0A 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jun 21 11:20:33.175: SW1_SP: -Traceback= 4042B17C 404543D0 40454508 408A5DE4 4044FF98 408AAFE8 408AAFD4
Jun 21 11:20:33.179: %C6K_PROCMIB-SW1_SP-3-IPC_TRANSMIT_FAIL: Failed to send process statistics update : error code = timeout
-Traceback= 40BF9E18 40BF9E68 40BFA070 40BFA2D4 408AAFE8 408AAFD4
Jun 21 11:20:52.687: %CPU_MONITOR-SW1_SP-3-TIMED_OUT: CPU_MONITOR messages have failed, resetting system [21/1] -
Can't see previous versions with VSS enabled.
Hi,
I have a W2008R2 with VSS configured and running, I can see shadow copies till today saved in a volume D:, but when I go to see previous versions of a file or directory inside this volume, these previous versions don't appear since 17/11/2014. This date
I changed the max value for number os shadow copies via registry editor, but I didn't check previous versions in files and directories later.
I've checked writers with vssadmin command, and all writers are ok. No errors in system logs neither. I've tried restarting VSS service with no result.
Is there any place I can check for solve this?
Regards,
QuiqueHi Umesh:
- Can you run "vssadmin list shadows" and see if it lists shadow copies?
Yes it does. Also checked if I can access to a the shadow copy, doing a mklink of the shadow copy
volume, and I can access to shadow copies not listed in previous versions.
- Reboot the server if possible and see if it helps.
Done
- Also check the below link. It is for Windows vista but I believe it still works for Windows 2008
R2 as well.
I found this article googling the problem, but I hace all checkboxes ok.
- What is the number you set and what do you see in previous version tab?
Default number os shadow copies is 64, I changed to 512 according to this article: https://msdn.microsoft.com/en-us/library/windows/desktop/bb891959(v=vs.85).aspx#maxshadowcopies
I'm still with the problem...
Regards,
Quique -
Jdeveloper 11g integration with VSS
I am trying to integrate JDev with VSS using latest available extension VSSExtension_v06, but it can only used for JDev10g version.Can anybody help me findout the Jdev11g extension for VSS.
no jdev extension for 11g as the latest version is for jdev10
org.jdev10.vss.VSSExtension.0.6.jar
http://jdev-vss-ext.cvs.sourceforge.net/viewvc/jdev-vss-ext/jdev_vss_ext/java/org/ -
XCode Integration With VSS (Visual Source Safe)
We have recently start developing for iPhone using XCode. We already have Visual Source Safe in place as our source control and I want to give it a try (integrate with XCode) before thinking of using CVS or SVN.
Sometime back TheSilverHammer talk about VSS integration with XCode in his post "Two questions: Xcode 2.4 (reloading a source file) and endianness ...", however it was not clear how he did that? This post is now archived and is no longer available for replies. TheSilverHammer can you, or anyone else please tell how is it possible?I don't really know about VSS/XCode integration but I have to make a comment. Dump VSS. Pour gasoline on it, light a match and run.
There are so many issues with VSS I'm not sure where to begin. No scalability, terrible stability, proprietary, etc.
You mentioned CVS and SVN. In the long run you'll be way better off with either of those. Personally I prefer SVN.
Just my 2 cents -
Hi-
Looked thru the thread related to my questions and found nothing that applies yet.
Example:
http://social.technet.microsoft.com/Forums/en-US/4e4472b9-8e6f-4fdc-a287-1cc8c0f6de09/windows-2008-r2-backup-fails-with-event-521-error-code-2155348001?forum=windowsbackup
http://social.technet.microsoft.com/Forums/en-US/e8c910f7-f0dd-4613-beae-b98894fb6f23/windows-server-2008-std-backup-fails-constantly-with-error-code-2155348001?forum=windowsbackup
Here are details of the issues....
Backup - OS error - system image:
External disk - USB
Mon - Fri @ 6PM.
Windows SystemState
OS(C:)
Last backup failure...
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
[Critical error WINIMAGE_UNABLE_VSS] Unable to create VSS snapshot
- Additional information: Refer to the log for more details
- Troubleshooting link:
http://kb.backupassist.com/errormap.php?BA2512
The backup operation stopped before completing.
Detailed error: ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-12-08-2014_04-41-00.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-12-08-2014_04-41-00.log
NOTE:
The errors logs are not there?
Windows Backup timed-out before the shared protection point was created.
ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Event Viewer Log:
Sequence of Events...
1.
The Block Level Backup Engine service has successfully started.
2.
Backup operation that started...
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 8/12/2014 4:51:06 AM
Event ID: 521
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: mdnfile.Auxiant.local
Description:
The backup operation that started at '?2014?-?08?-?12T09:41:00.492000000Z' has failed because the
Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed
with following error code '2155348001'.
Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
--> Suggestion are to check Virus scanner or consult DPM forum...
3.
OS Job failed with errors...( Backup Assist is 3rd party backup - wrapper round Wbadmin/Win Backup)
Log Name: Application
Source: BackupAssist
Date: 8/12/2014 4:51:51 AM
Event ID: 5634
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
Backup job OS backup failed with errors.
Critical error: Unable to create VSS snapshot
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
4.
Backup Assist reports via Win backup - Snapshot in progress
Log Name: Application
Source: BackupAssist
Date: 8/12/2014 4:52:20 AM
Event ID: 5634
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
Backup job Data backup failed with errors.
Ultra critical error: Volume Shadow Copy Error 0x80042316 - snapshot set in progress
Destination: Local directory
Start time: 8/12/2014 4:52:10 AM
End time: 8/12/2014 4:52:12 AM
Duration: 00:00:02.7300000
5.
The Block Level Backup Engine service has stopped.
6.
Later...we tried manually stopping VSS and SWPRV services - only VSS had the issue.
WBengine was not running...
C:\>sc stop swprv
SERVICE_NAME: swprv
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\>sc query swprv
SERVICE_NAME: swprv
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\>sc query wbengine
SERVICE_NAME: wbengine
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\>sc query vss
SERVICE_NAME: vss
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\>sc stop vss
[SC] ControlService FAILED 1061:
The service cannot accept control messages at this time.
Log Name: Application
Source: VSS
Date: 8/12/2014 9:20:33 AM
Event ID: 8225
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
The VSS service is shutting down due to shutdown event from the Service Control Manager.
7.
VSS still having issues here...not stopping!
Log Name: Application
Source: VSS
Date: 8/12/2014 9:42:33 AM
Event ID: 11
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service information:
The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started.
Most likely the CPU is under heavy load. [0x80080005, Server execution failed]
8.
Not sure why this is started again?
Plus a DCOM timeout...
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 8/12/2014 9:31:13 AM
Event ID: 753
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has successfully started.
Event Xml:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 8/12/2014 9:31:43 AM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
The server {E579AB5F-1CC4-44B4-BED9-DE0991FF0623} did not register with DCOM within the required timeout.
9.
Lots more errors about VSS...repeating Event ID's 11 and 8193...
Log Name: Application
Source: VSS
Date: 8/12/2014 9:42:33 AM
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
hr = 0x80080005, Server execution failed
. Operation:
Instantiating VSS server
10.
Then, finally stopping again...
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 8/12/2014 9:51:13 AM
Event ID: 754
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has stopped.
11.
And still repeating 11 & 8193 at this point...as we write up this post.
12.
This was suggested by the Backup Assist - software vendor....
A.)
...for 0x81080101:
"ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try again this operation."
If you receive the above error in your report, we have recently found a registry key which
contains the timeout value set by Microsoft for VSS and found that you can edit this to extend it.
To get to the registry key, open Regedit (Start > Run > Regedit) and browse to:
"HKLM\Software\\Microsoft\\Windows NT\\CurrentVersion\\SPP\\CreateTimeout".
Change value to 1200000 (2*10*60*1000 = 20 mins).
The default for the timeout period is 10 mins so hopefully doubling this will give enough time to
complete the snapshot.
If this isn't present, you'll need to manually enter the registry key. It's a DWORD 32-bit key.
--> NOTE: HAve not done this yet.
B.)
And for 0x80080005...
http://support.microsoft.com/kb/870655/en-gb
Our server does have high CPU load at times...
13.
Another post from technet mentions system volume size - here is our layout below:
A.)
OS/system Disk...
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
Disk 0 Online 278 GB 0 B (System Vol = C: Drive - OS w/ Programs and batch jobs)
Disk 1 Online 2791 GB 0 B * (Data drive - DFS, rsync,etc. run on D: Drive)
Disk 2 Online 1863 GB 0 B (USB 2/3.0 - Enclosure w/ SATA disk = 2GB formatted w/ NTFS.)
DISKPART> detail disk
DELL PERC H710P SCSI Disk Device
Disk ID: CA0DEEA5
Type : RAID
Status : Online
Path : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0100)#PCI(0000)#RAID(P01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
Volume 1 RECOVERY NTFS Partition 3072 MB Healthy System
Volume 2 C OS NTFS Partition 275 GB Healthy Boot
B.)
Backup disk...
ST320006 41AS USB Device
Disk ID: 801AF48C
Type : USB
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
Volume 4 F BACKUPS NTFS Partition 1863 GB Healthy
C.)
NOTE:
Also on disk 0(system Disk) - we have a small OEM partition = 39MB and a Recovery Partition = 3GB.
D.)
Issues with WBAdmin now...
C:\>wbadmin get disks
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x80042302)
A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
14.
Ran "Check-Disk" -no errors...
C:\>chkdsk
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
116224 file records processed.
File verification completed.
654 large file records processed.
0 bad file records processed.
0 EA records processed.
76 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
156676 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
116224 file SDs/SIDs processed.
Security descriptor verification completed.
20227 data files processed.
CHKDSK is verifying Usn Journal...
35628352 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
289233919 KB total disk space.
100241492 KB in 85477 files.
57380 KB in 20228 indexes.
0 KB in bad sectors.
226627 KB in use by the system.
65536 KB occupied by the log file.
188708420 KB available on disk.
4096 bytes in each allocation unit.
72308479 total allocation units on disk.
47177105 allocation units available on disk.
15.
There are no backup error logs here - only .etl files...
C:\Windows\Logs\WindowsServerBackup\
Wbadmin.1.etl = 9:42AM on 8/12
Wbadmin.2.etl = 4:51AM on 8/12
Per windows Win troubleshooting:
http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
--> Related to Windows backup and not VSS?
2155348001 - 0x80780021 - Windows Backup timed-out before the shared protection point was created.
Should we run the "FIXVSS08.BAT" script - restarts services and re-registers DLL's - does this ever help?
Will this server need a reboot since VSS is in a state and we can't even test backups?
Is there a tool we can use to debug VSS or troubleshoot or OS backups further?
MSReport/Diag, VSS debugging, or another way of helping fix our OS(SystemState/C: drive) backup issues?
Any help is greatly appreciated - thx.
-SP
Scot PichelmanHi Scot,
Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
after testing.
And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
If issue still exists, please try the steps below as well:
1. Please check DCOM Server Process Launcher service is started.
2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
Note: Backup the key before edit incase it cause any issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
Find "ObjectName" and change the value to LocalSystem.
Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
If DCOM still not work, please compare the content of the following key with a working server:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Edit if there is any difference and make sure you created a backup of the key before editing.
If you have any feedback on our support, please send to [email protected] -
Problems with VSS and RoboHelp on second machine
Hi all,
We chose to use Visual Source Safe as our source control tool
to use with RoboHelp. To build the VSS database containing the help
project on the server, we successfully used the version of our help
project on my machine. I have had no problems using it for the last
several weeks. Everything works great. Files are retrieved, checked
out, and checked back in with no issues.
The problem is we have been unable to successfully set anyone
else on the team up with the VSS-RoboHelp source control. Since
we're not building the database from scratch, the way we did with
mine, we're trying to "get" the version from VSS on the server and
place it on her machine. I'm guessing this is the way to do it, but
we don't know how. When we try to get the version in source
control, only the top level of .htm topics are retrieved, not
anything that is nested in child folders. Then, when we attempt to
open the help project on her machine, we get all sorts of errors
ranging from "corrupt .cpd" files to "invalid characters" to "the
local version is different from the version in source control"
(DUH!). We tell it to get files from RoboHelp when we try to open
the help project on her C drive, but it doesn't download them
correctly, and invariably RoboHelp crashes.
Has anyone successfully used VSS with RoboHelp, and if so,
how do you get a new computer set up with an existing RoboHelp
project that is already in VSS? I need exact steps, if possible,
since it's not intuitive (or since we're just clueless).
I really appreciate any help anyone can offer!
Thanks!
LisaHi Kathy,
Thank you for your response. I'm not sure we're on the same
page, but it just may be because I'm so new to this. The problem
isn't with checking in or checking out files -- It sounds like you
might be at step 5 and we're still at step 1. The problem is with
getting the entire help project down from source control to her
machine the very first time. For example... Imagine a new RoboHelp
author who has just started with the company and has just gotten
RoboHelp and VSS installed on her machine. We now need to get the
project down from VSS to her machine. We can't check out or get
anything yet because the project hasn't even come down to her
machine yet. RoboHelp on her machine doesn't even know about this
help project out there. We open RoboHelp, and there's nothing on
her C drive to browse to because the project isn't even there yet.
I believe our infrastructure guy (who has been trying to get her
set up with this, but is as much in the dark as I am) was trying to
somehow "get" the files from VSS to her C drive from within VSS,
but obviously that didn't work because it only grabbed the
top-level files. I don't know if any of this makes sense. I thought
there'd be a way, in RoboHelp, to tell it that we have something
out in source control, and "please go get it." It doesn't seem to
work that way.
If you and I *are* on the same page and I just don't
understand, I apologize, in which case do you mean she's supposed
to check out files or get files from within VSS? Apparently that's
what the infrastructure guy did, and it didn't work. She needs to
be able to work on these help files just like I do, so she needs to
be able to get, check out, and check in. Or do you mean we need to
check out or get files from within RoboHelp?
Color me confused... :P
Thanks,
Lisa -
I am trying to backup a VM which before it had Oracle installed backed up with no problems. It is a Windows 2008 R2 server which sites on an 8 node Hyper-V 2012 R2 cluster (with CSVs). I am using DPM 2012 R2 to run the backups which have been
successful for the last few weeks but then Oracle was installed and the backups have failed since then.
The job fails and a large number of VSS writers go into a 'Failed' state with the 'Last Error' showing as 'Timed out'. I then get 4 popups appear each referring to a 'temporary' drive which appears briefly in Disk Management with a RAW file system.
These pops say "You need to format the disk in drive X: before you can use it. Do you want to format it?" (where
X: is replaced by the drive letter assigned to each 'temporary' drive).
The System event log is populated with a large number of warnings with Event 51, Disk, stating "An error was detected on device \Device\Harddisk<number>\DR<number> during a paging operation". There are also a
few warnings for Ntfs (eventid 57) stating that "The system failed to flush data to the transaction log. Corruption may occur."
Prior to these warnings there are 5 other warnings for partmgr (eventid 58) stating "The disk signature of disk
<number x> is equal to the disk signatuire of disk <number y>" and 4 errors (eventid 1, VDS Basic Provider), "Unexpected failure. Error code: 490@01010004".
There is a script which is run to stop the Oracle application on the server and if this is run then the backups will complete successfully. We have been troubleshooting this by running a certain amount of the script and seeing which part affects the
backup and it seems that if the Weblogic (wls_reports) service is stopped then the backup will succeed but if it is running then the backup will fail and the above symptoms occur.
Another point which may help is that there is a pre-production server which resides on a Windows 2008 R2 Hyper-V standalone server, has the same scripts and installation of Oracle but backs up without any issues.
I have experienced VSS writer failures before with VM backups but I have not seen this before. It is not intermittent and I can find no work around to alleviate the problem of having no backup (except stopping this service or shutting the server down,
but as it is a production server this is not practical).
If anyone has experienced this before or have any suggestions / advice it would be much appreciated.
Thanks
ChrisHi Chris
I have exactly the same issue.
2008 R2 Server running Oracle
6 node 2012 R2 Hyper-V Cluster with CSV
Exact same errors and popup "format disk" message.
DPM2012 R2
I also have some other VM's on the same cluster which do back up through DPM
The only difference I can see is the server which has the issue has a legacy network adapter.
Production server so cannot make any changes until later but will add new adapter and report back.
Interesting about the Weblogic service, may test this also.
Cheers
Kev. -
Schema Binding with VSS in SQL Developer
Hi guys is it possible to bind a Sql Developer or TOAD with Visual Source Safe or i can change database object in toad or sql developer and check in into VSS?
Thanks
PurvikTOAD can do version control with any software that uses Microsoft's Source Code Control (SCC) API, which includes VSS. Look at the help pages for more info.
While SQL Developer only supports Subversion and CVS directly, I've used its External Tools capability to add ClearCase check out, check in, undo check out, and add capabilities. If you can do basic version control operations from the command line with Visual SourceSafe, you ought to be able to do the same thing. Just look up the syntax for the command line tools, and build your commands by selecting the Tools menu, select External Tools, and add a new tool. This is very much like creating a new desktop shortcut in Windows. -
Is it possible to run RoboHelp 8 with VSS on Windows 7
Is anyone aware of whether it is possible to use VSS with RoboHelp 8 on windows 7? My understanding is that robohelp is fully compatible with windows 7 however i have not seen anything specific on using VSS as source control and given my recent experiences after upgrading i think it may not be possible.
Basically after upgrading from windows xp to windows 7, i reinstalled robohelp 8 and VSS. I then got the latest version of my project down to my c: drive and double clicked the xpj file to open the project.
As RoboHelp is loading i get the following error:
I click yes but nothing happens and RoboHelp continues to open. Strangely once it has opened, there is no link to Version Control from the File option and no option to select the Version Control toolbar!? It's as if it just doesnt exist at all.
For reference i am using RoboHelp HTML, Version 8.0.2
Any advice or help would be much appreciated.SDSputnik wrote:
Noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Why does Mac have to be expensive?!?!
PC's are cheap and nasty, why is that so? -
Hi,
Plz ny1 can suggest me,how can i integrate siebel with Microsoft Visual SourceSafe (VSS).
i've made changes in srcctrl.bat file in siebel but at the time of check in it's gving error.
thnx.Pradeep,
You might want to check this weblog.
Adapters to Integrate SAP XI and Siebel system
James -
Hello,
At work i was handed a task for investigation and truly speaking, i dont know where to start with.
Here is the description of the issue. You help is greatly appreciated.
we have encountered three incidents in one month of the same type.
Following Filesystem backup, after the Configuration backup (using DataProtector) of IIS settings, the VSS is not correctly released,
thus impacting the following backups, resulting in dismounted databases on Exchange.
Each time we had to reboot both the passive and active node in order to get back to nominal situation.
I join a screenshot of the log, could you please investigate as soon as possible as it is going to cause severity 1 incidents each time
this will happen.
Regards,Hello,
I'm unable to attach the file:
Here is the error:
Application - VSS 12289 10.01.2014 - 00:28:31
Volume Shadow Copy Service error; Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported
limit. hr=0x80042409. Operation : Aborting Writer Context: Maximum supported sessions: 64 Completed sessions: 8 Active sessions: 64 Aborted sessions: 0 Writer failed sessions: 0 New Snapshot set {1c2d4422-0181-4d24-bf05-c403c238d6b1} Old Snapshot set: {b2890d99-d486-4e1d-820a-599fb5d5be0c}
Old Operation: 1014 Old State: 1 Old Failure: 0 Writer Class Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Name: IIS Config Writer Writer Instance ID: {86180699-0172-47fe-b484-9a784da997ea}
Application - VSS 12298 10.01.2014 - 00:28:31
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy
creation period on volume C:\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000],
Release[0x80042314],
OnRun[0x00000000].
Operation: Executing Asynchronous Operation Context; Current State: DoSnpshotSet
Application - VSS 12310 10.01.2014 - 00:28:31
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed
out. Error context: Device IoControl(\\?\Volume.(0e61390d-d795-11df-8780-806e6f6e6963} - 00000000000001CC, 0x0053c010, 000000000002060E0, 0,00000000002050D0, 4096, [0]).
Operation: Commiting Shadow copies context: Execution Context; System Provider -
4500X with VSS and Dual-Active Fast-Hello
Hello,
ich have two pairs of 4500X-32, with other word two vss-systems in a test environment. IOS running version is 03.05.02.E.152-1.E2, dual-active detection with a fast-hello link is running. When i pull the VSL connectors to simulate a failure the active switch go into recovery-mode. After the vsl is restored the switch in recovery-mode start a reboot as desired. The configuration is saved and if i repeat the procedure, all is working fine. But when i start the systems the next day and begin to test the dual-active detection again, the vsl port stucks in " waiting to be aggregated" after restoring it. No reboot happens, the only solution is to reboot the switch manually. After that this misbehavior is repeating. Only setting the dual-active detection interfaces to its default, and reconfiguring them for fast-hello dual active detection again brings the feature back to normal operation:
interface TenGigabitEthernet1/1/12
switchport mode access
switchport nonegotiate
dual-active fast-hello
Both vss systems shows the same behavior from time to time, i have no explanation, can somebody help?
Regards, StephanFast hello is not supported for the 4500 series unless you are running the latest version of the IOS (3.5E)
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/XE3-5-0E/15-21E/configuration/guide/config/vss.html#87652
HTH -
I am looking at deploying a redundant, load balancing WAAS solution at a Data Center.
Hardware:
2 x 694 WAE's Application Accelerators
1 x 294 WAE Central Manager
2 x 6506 Catalyst core switches running VSS
2 x 3925 ISR WAN routers connecting to seperate WAN clouds.
We will not be using AppNav thus I will use WCCP to provide high availability and load sharing.
I have some basic questions for the Application Accelerators:
- Which interfaces do a patch to the switches? I assume I do not use the inline ports for a WCCP deployment?
- Can the Gi0/0 and Gi0/1 interfaces be in a port-channel?
- Which WCCP pack-forwarding method would be recommended with my hardware?
- Which egress method would be recommended?
Any assistanace is appreciated.based on you setup, and considering 6500 doing redirection rather than routers (we can also build setup where router will act as WCCP server and take role of traffic redirection, and 6500 is only used a L2 media between router and WAE), belows is the best recommendation for 6500---
assignement method----mask (reduce it from default value to satisfy our need and save TCAM resource)
redirection--GRE
Egress---generic GRE
interception--in direction (61in ,62 in)
Abve combination will fully supported in H/w.
And yes gig0/1 and gi0/0 can be configured as etherchannel
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-629052.pdf for more detail -
Hello all,
I am in the process of designing a phase locked loop based frequency synthesizer. I successfully simulated the PLL. The PLL chip was simulated using the Phase frequency detector/charge pump and the divider provided in VSS element browser. For the VCO, I used the behavioural model, again in the element browser. The loop filter was simulated in MWO using discrete components.
My problem is this. I am trying to generate the entire layout within Microwave Office Design Environment. How can I assign artwork cells (footprints) to the PLL chip and the VCO? I can create the footprint, but so far unsuccessful in attaching to a component (in VSS). The alternative is doing the layouting using a separate layout package. But I am trying to do everything (including routing) within VSS as VSS seems to be capable of analyzing the effects of traces and trace coupling etc using ACE and AXIUM.
I found a very interesting video in the AWR/Ni short video series, which is very relevant to this question. The particular one I am referring here is PCB Design Part 4: PCB trace design. This video is on a VSS simulation accounting the trace effects as well. Unfortunately, the video focuses on the simulation part and does not address my problem. In this video, they have attached a foot print to a non-linear power amplifier model created using VSS. Apparently, there is a footprint attached, but the video does not show how it was done. Your help is greatly appreciated.VSS system diagrams do not include layout. Layout, including footprints, is part of circuit level design (Circuit Schematics). You can create a circuit schematic and its layout to describe your interconnect, simulate the circuit using the circuit simulator or EM, and then use that circuit schematic as a model of the interconnect in the top level system diagram as a LIN_S block.
Maybe you are looking for
-
How to connect Macbook air to tv via airplay ?
How do I connect my Macbook Air to tv via Apple TV and airplay ?
-
Officejet Pro 8600 plus e-all-in-one N-911g App Connection Error
Windows 8.1 Update 64 bit version Printer connected wirelessly "Connection Error: The printer was unable to connet to the server. Check your internet connection and try again." I get this message when touching the "Apps" Icon on the printer touch
-
I used the adm from Frontmotion but it only works with the FirefixCE version, I need to force Firefox configuration in my domain with a standar version of Firefox, how can I do this, it could be by GPO or logon script
-
Truncating data in prepared statement
I'm using a prepared statement to pull data out of one SQL database into a recordSet, and another prepared statement to take the data from the recordSet and insert the data into another SQL database. In the source database, the lastname and firstname
-
Hey!!!! Just wondering if you could help me. I 'm hesitating to buy MacBook or MacBook pro to use the LOgic Pro7. My question is; do you think that with the MacBOok will work properlly, or not? Do I need to buy the MacBook Pro? Please, help me becous