RVS4000 problem with QOS
Hello.
I have problem with bandwidth management on my RVS4000.
That is the way how i done it:
All traffic (TCP & UDP on all ports)
IP range 192.168.0.2 - 192.168.0.2 (My IP adress)
Guaranted download speed 1kbps
Maximum download speed 5000kbps
after saving setting and rebooting router
I have maximum download speed on my PC 12000kbps
Please help me to solve this problem.
Why QOS doesnt work ?
By the way sorry for my english i do not ue this language very often
Looking forward for some advices.
Jaroslaw,
Please call into Cisco Small Business Support Center and speak with next available engineer (Support Numbers)
Jasbryan
Similar Messages
-
Problem with QOS for SIP on RV082
Hello,
I have problem with quality of VOIP call with Linskys RV082. Firmware is 2.0.0.19tm.
Router is configured as dual-wan , one port (WAN2) is for ADSL 8000/512kb and other one is (WAN1) SHDSL 8000/8000kb.
VOIP traffic from certain IP of LAN is routed to WAN2 (through protocol binding). We have quaranted QOS on ADSL by ISP.
Problem is that voice is dropping when we load WAN2 with other data connection. Last week i reload new firmware, restore default factory and configured router whole again. All was ok only for 1 day and then voice was dropping again. I mean that problem is at mark packets, because when I put VOIP PBX in front of behind router , QOS is working fine.
Can you help me? Is this know issue?
Thanks.
Jan Babak
Message was edited by: jabacomCZthank you for reply !!!
below is the show output :
ciscoasa# show priority-queue statistics outside_wan
Priority-Queue Statistics interface outside_wan
Queue Type = BE
Tail Drops = 0
Reset Drops = 0
Packets Transmit = 7971924
Packets Enqueued = 0
Current Q Length = 0
Max Q Length = 0
Queue Type = LLQ
Tail Drops = 0
Reset Drops = 0
Packets Transmit = 189321
Packets Enqueued = 0
Current Q Length = 0
Max Q Length = 0
ciscoasa#
so does the command look like, the one I should use instead of priority-queue outside_wan ?? -
Problems with QoS between 2950 and 3550 with use of Native VLAN
Hi!
I try to set up QoS between a C2950 and a C3550, I have provided a drawing that might help understanding the setup.
As I understand it, since I only have the SMI image on the C2950 I have to run a 802.1Q trunk over the leased 2Mb line to get QoS to work. And I DO get it to work, or at least it seems so to me.
What I'm trying to setup QoS on is between a Nortel Succession Media Server and a Nortel i2004 IP Phone.
And when I sniff the port that the Succession Media Server is connected to, I get this output:
*BEGIN*
*** TO IP Phone ***
IP version: 0x04 (4)
Header length: 0x05 (5) - 20 bytes
Type of service: 0xB8 (184)
Precedence: 101 - CRITIC/ECP
Delay: 1 - Low delay
Throughput: 1 - High throughput
Reliability: 0 - Normal reliability
Total length: 0x00C8 (200)
ID: 0x5FE1 (24545)
Flags
Don't fragment bit: 0 - May fragment
More fragments bit: 0 - Last fragment
Fragment offset: 0x0000 (0)
Time to live: 0x40 (64)
Protocol: 0x11 (17) - UDP
Checksum: 0x69EC (27116) - correct
Source IP: 10.40.2.10
Destination IP: 10.10.153.100
IP Options: None
UDP
Source port: 5216
Destination port: 5200
Length: 0x00B4 (180)
Checksum: 0x5C02 (23554) - correct
*** FROM IP Phone ***
IP version: 0x04 (4)
Header length: 0x05 (5) - 20 bytes
Type of service: 0xB8 (184)
Precedence: 101 - CRITIC/ECP
Delay: 1 - Low delay
Throughput: 1 - High throughput
Reliability: 0 - Normal reliability
Total length: 0x00C8 (200)
ID: 0x8285 (33413)
Flags
Don't fragment bit: 0 - May fragment
More fragments bit: 0 - Last fragment
Fragment offset: 0x0000 (0)
Time to live: 0x7F (127)
Protocol: 0x11 (17) - UDP
Checksum: 0x0848 (2120) - correct
Source IP: 10.10.153.100
Destination IP: 10.40.2.10
IP Options: None
UDP
Source port: 5200
Destination port: 5216
Length: 0x00B4 (180)
Checksum: 0x5631 (22065) - correct
*END*
But, then to the problem:
Since the modems I use have ip adresses in them I want to monitor them and be able to change settings in them.
But to connect to units within the trunk, I have to set the native vlan to VLAN 144, which provides the ip adresses I use for the modems, in both ends of the trunk.
But if I do that the tagging of the packets from the IP Phone disappears!
Here's an output after native VLAN is applied:
*BEGIN*
*** TO IP Phone ***
IP version: 0x04 (4)
Header length: 0x05 (5) - 20 bytes
Type of service: 0xB8 (184)
Precedence: 101 - CRITIC/ECP
Delay: 1 - Low delay
Throughput: 1 - High throughput
Reliability: 0 - Normal reliability
Total length: 0x00C8 (200)
ID: 0xDEF8 (57080)
Flags
Don't fragment bit: 0 - May fragment
More fragments bit: 0 - Last fragment
Fragment offset: 0x0000 (0)
Time to live: 0x40 (64)
Protocol: 0x11 (17) - UDP
Checksum: 0xEAD4 (60116) - correct
Source IP: 10.40.2.10
Destination IP: 10.10.153.100
IP Options: None
UDP
Source port: 5240
Destination port: 5200
Length: 0x00B4 (180)
*** FROM IP Phone ***
IP version: 0x04 (4)
Header length: 0x05 (5) - 20 bytes
Type of service: 0x00 (0)
Precedence: 000 - Routine
Delay: 0 - Normal delay
Throughput: 0 - Normal throughput
Reliability: 0 - Normal reliability
Total length: 0x00C8 (200)
ID: 0x89E4 (35300)
Flags
Don't fragment bit: 0 - May fragment
More fragments bit: 0 - Last fragment
Fragment offset: 0x0000 (0)
Time to live: 0x7F (127)
Protocol: 0x11 (17) - UDP
Checksum: 0x01A1 (417) - correct
Source IP: 10.10.153.100
Destination IP: 10.40.2.10
IP Options: None
UDP
Source port: 5200
Destination port: 5240
Length: 0x00B4 (180)
Checksum: 0x31CA (12746) - correct
*END*
See, there is noe QoS tagging from the IP Phone anymore.
If I set no switchport trunk native vlan 144 in both ends the tagging is back.
Any ideas? Is this a bug, or just some command I don't know about?
Please take a look at the picture to get a more understandable view of the setup.
Thanks!Well, native VLANs are by definition untagged so there´s nothing wrong with that as far as you are getting the expected results. By the other way I think you should include VLAN 402 on your allowed vlan range on Catalyst 3550's FastEth0/45 trunk port, otherwise this VLAN will be completly isolated from the rest of the network.
-
Problem with IP phone over VPN
| UC520 | ------------------------ | 861 |
| |
LAN LAN
Scenario:
UC520 box is at HQ and serving as a EZVPN server and 861 at branch as a EZVPN client. There is no problem with VPN i can communicate with HQ network. My ip phone get registered but facing these problems.
1) Dialling out and in OK
2) Connects OK after picking up
3) NO sound either way
4) Cannot end call from this side. End call button does not work
5) When other end hangs up - message "UCM down, features disabled". Then phone registers again.
Identical symptoms for both softphone and 7941.This document provides a sample configuration for Quality of Service (QoS) for Voice over IP (VoIP) traffic on VPN tunnels that terminate on the PIX/ASA Security Appliances.
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008080dfa7.shtml -
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] -
Hi
We r facing typical problem with file adapter.
Lets say there are 30 files to be processed by placing an copy in arichive folder by file adapter based on pooling
parameters.
All the 30 files are picked up and we can see the copies in archive folder.
But when we go to RWB and check the audit log,
there we could see only 25 files , the 5 files are missing.
no trace found therre about the 5 files.
This is happening only some times and not to all the files placed in the FTP. Later when the same file is placed back from the Archive folder to the Source folder, the file is being picked and processed succesfully.
unfortunately this is happening on Production server
Any pointers which could trouble shoot this issue.
Regards
shekar chandraHi,
Couple of thing which you can try....
1. Use EOIO QoS and check if you still face the issue.
Is some program or application writing files to the directory? If yes I would recommend the use of a temporary name to write the files and then rename them.
Sometimes when an external application connects via FTP and transfers the files...
The file could be picked up by the adapter poll even before the transfer of data is done.
Which is why you will find that the file is archived but there is no xml message created for the same in the Integration engine.
Try increasing the poll interval. This helps sometimes.
Regards,
Sidharth -
hi
i have an mpls nework with equipment cisco 2821, 2901 and 2801, and i have problems with fax calls, i configured the fax protocol t38 in all routers but when i want to send a fax to the 2821 equipment from either 2801 and 2901, the protocol t38 is not working and the fax call use cisco protocol (although t38 is configured in all routers). the calls betwen 2801 and 2901 works ok, and from 2821 to 2801/2901 works ok too.
any idea of whats happens? do you think is a problem of ios version?
these are de ios version
2821 .-c2800nm-spservicesk9-mz.124-3i.bin
2801 .- c2801-spservicesk9-mz.150-1.M6.bin
2901 .-c2900-universalk9-mz.SPA.150-1.M7.binhi
this is the configuration on the 2821:
voice service voip
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
dial-peer voice 10037 voip
description CONEXION CELAYA DISTRITO XV
destination-pattern 561.
session target ipv4:172.16.200.37
incoming called-number .
dtmf-relay h245-alphanumeric
codec g729r8 bytes 50
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
ip qos dscp ef signaling
no vad
this is the configuration on 2801
voice service voip
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
dial-peer voice 10016 voip
description CONEXION VOZ A FAXES
destination-pattern 300[1-6,8]
session target ipv4:172.1.1.51
incoming called-number .
dtmf-relay h245-alphanumeric
codec g729r8 bytes 50
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco
ip qos dscp ef signaling
no vad
i want to use T38 because the bandwidth of the fax call is 16K, if i use cisco protocol the bandwidth reaches up 24k, and the router start to drop voice packets
thanks -
Am I likely to recieve problems with these stats?
Hi
Just recently ordered BT vision and even tho its not due to arrive for a few weeks, BT have kindly enabled the Assured Rate/QOS already ;-)
Now the wife is a bit pessemestic as to whether it will work on our line as she has heard horror stories from our neighbours.. THese are my just posted stats from the BT speed tester. Can anyone see any problem with these?
FAQ
Test1 comprises of two tests
1. Best Effort Test: -provides background information.
Download Speed
3757 Kbps
0 Kbps
7150 Kbps
Max Achievable Speed
Download speedachieved during the test was - 3757 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :5312 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 4000 Kbps
2. Assured Rate Test: -provides background information.
Download Speed
666 Kbps
0 Kbps
600 Kbps
Max Achievable Speed
Download speedachieved during the test was - 666 Kbps
For your connection, the acceptable range of speeds is 576-600 Kbps.
Additional Information:
Assured Rate IP profile on your line is - 600 Kbps
THis test was done over a BT Business Hub and if these results are decent, im reluctant to change it for the BT Home hub that i will be getting for free....looks pretty perfect you should have no problems at all
Life | 1967 Plus Radio | 1000 Classical Hits | Kafka's World
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Helpful Post?
If a post has been helpful, say thanks by clicking the ratings star. -
Problem with Webservice - XI - JDBC scenario
Hi Experts,
When I have tried to test the Webservice -> XI -> JDBC scenario with the mention address, I am getting the below error.
<b>Address :</b> http://<Host>:50100/XISOAPAdapter/MessageServlet?channel=:WEB_SERVICE:SOAP_CC&version=3.0&Sender.Service=WEB_SERVICE&Interface=http%3A%2F%2Fatl.com%2Ftar%5EMI_Outbound
<b>Error:</b>
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>RecoverableException</code>
<text><![CDATA[
com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
JDBC Part works fine only problem with the SOAP sender side. Any suggestion please..
Regards
Sara
Message was edited by:
Sara DHi,
As per Bhavesh & Krishna's suggestion, I have changed the JDBC Data type. Now I could able to see the SXMB_MONI error too.
Latest error:
When I have tried to test the scenario using xmlApy, I am getting the below error.
<b>RWB error:</b>
2007-06-21 03:04:24 Success Receiver JDBC adapter: processing started; QoS required: BestEffort
2007-06-21 03:04:24 Success JDBC adapter receiver channel DB_CC: processing started; party , service DB_SERVICE
2007-06-21 03:04:24 Error Unable to execute statement for table or stored procedure. 'Address' (Structure 'STATEMENT') due to java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', no key element found
<b>xmlSpy Error:</b>
<context>XIAdapter</context>
<code>RecoverableException</code>
<text><![CDATA[
com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'Address' (structure 'STATEMENT'): java.sql.SQLException: FATAL ERROR document format: structure 'STATEMENT', no key element found
at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
I have mapped the EmpId in the mapping as well as in the DB the EmpId is Primary Key. Could you please tell me,what I am missing here?
Regards
Sara
Message was edited by:
Sara D -
Problem with video, My upload video is zero when I initiate ???
I recently upgraded my cable to 8megs download, 1 full meg upload.
Now in some two way and most three way video chats my upload starts as
zero or goes to zero shortly.
When it does work intermittently, it is very high. Connection doctor shows up and downloads as high as 900 framerate 20.
I have roadrunner time warner cable, no router, no firewalls, QT streaming set at 1.5 as Ralph and other say, NONE as limite in ichat. I have tried altering the AIM port from 5190 to 443 no help.
Could it be a bad modem? Is there a problem with ichat being able to match the higher upload and download I have now with the premium service/ Prior to this I had no problem with two way ichats. I only went to premium service because the prior service was just not quite enough to initiate three way videos, the upload was only 340 at best.
Thanks everyone,
Evan
My computer is imac intel core duo, 2.16 2 gb memoryHi Evanshaw,
Ok on the Uninstall.
I would Repair Permissions and run the Cron scripts at this point just to get it as Clean a system as it can be.
See here for Why and Links.
1) The Instant On setting seems to make no difference.
Changing the Streaming setting to match your download or to 1.5Mbps is the real key of the Quicktime adjustment.
2) Newer modems seem to offer forwarding not only ports but list the Protocols as well.
Now in earlier devices it was impossible to forward the same port to two computers (IP addresses) on most of them.
As port 5190 needs to be forwarded for TCP and UDP it as if the modem thinks it is being forwarded twice.
For this reason we suggest that as a test at least that the Login port is dropped to port 443. This does two things:
a) drops it below the 1024 threshold and avoids NAT being done on it.
b) Leaves just 5190 on UDP to be forwarded in the Modem.
Just changing the port in iChat seems to do it, as then no data is on the 5190 TCP port.
3) As for the lower spec machine.
The lowest spec Mac can be a G3/600 with at least 100kbps up and down to Video chat.
A G4/1Ghz single processor is in fact at the lowest point of Multichats IF the connection is at least 384Kbps both up and down. (I used to have 1Mb down and only 256K up and Host multichats [on a Dual 1Ghz G4) so there is a sort of tolerance in these figures).
iChat works out a compromise that works in most cases so I would not worry too much.
4) Yes it is fair to say that pushing the envelope on the Specs does have an Effect.
My G4/Dual 1Ghz is fast enough and my previous internet speeds had a too low Uplink but did allow me to multichat. (there seems to be some sort of balancing out/averaging going on). However adding a second and a third Buddy to make a Four way did cause some blurriness of the pictures.
Also If I was invited to a Chat as a non host My slowness could effect the chat as well but to a lesser extent.
Get the fastest Computer with the best internet connection to Host.
5) With new modems it is sometimes difficult to judge whether they are good or not.
Sometimes they come loaded with "extra" features that can impact on something like iChat.
For Instance:
a) Denial of Service Attack protection (DoS) This is supposed to stop your computer being swamped with requests if you were running a web page server. It judges if too much data is coming to your machine and closes the connection if it thinks this is happening. Sometimes this is too restrictive for Video Chats at the Quality that iChat can produce. As to whether a particular device can alter this in a setting tends to vary. (my Netgear is an On or Off setting)
b) SPI (Stateful Packet Inspection) is Similar but devices that have this can normally adjust it.
c) QoS (Quality of Service) is similar again but more restrictive than SPI and more like DoS
d) As I have mentioned Protocols on Port Forwarding.
e) There is a setting on most devices called the MTU. It is about packet size. The default is always 1500 and changing it to 1492 can help.
f) The way the device may do NAT (Network Address Translation) may not be liked by the device at the other end. It has about 6 main popular ways this is done by Manufacturers and can be a problem. (Hence the push towards UPnP if you have it as UPnP does not use NAT).
5:42 PM Sunday; December 24, 2006 -
Port-channel problem with WiSM
Has anybody met following similar problem:
I put WiSM into slot 3(also tried slot 6) of 6506(sup720-3B, s72033-adventerprisek9_wan-mz.122-33.SXH.bin), using following command to setup the port-channel:
interface Port-channel1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 5
switchport trunk allowed vlan 1-1000
switchport mode trunk
int range g3/1-4
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 5
switchport trunk allowed vlan 1-1000
switchport mode trunk
channel-group 1 mode on
I can use "session slot 3 pro 1" to login to the WiSM, but can't ping WiSM's management IP address from 6506, then I find the port-channel has problem, only G3/1 is up and included in the channel, G3/2-4 are up but line protocol is down, then I found from the log that: "AESUT: %EC-SP-5-CANNOT_BUNDLE2: Gi3/2 is not compatible with Gi3/1 and will be suspended (qos-card type unavailable for Gi3/2 or Gi3/1)". It says those GE port are not compatible for qos-card type, but I checked the configuration, all GE using the same configuration. Don't know why, maybe a bug? Appreciate for any feedbackI have the same problem, but it has something to do with QoS. When you disable "mls qos" on the switch, the port-channel will function normal again.
It doesn't help when you configure "mls qos trust dscp" on the port-channel!!!!! -
I have had a WRT350N router since they first came out and have had the same problems with it the entire time. I have 2 systems with static IP's, 1 wireless B (dhcp) 2 wireless G (DHCP), and 4 wired devices. (1 Gigabit, 1 10 Base, and 2 100 Base)
1. After the unit has been powered on for a while (a day or so) The DHCP server quits giving IP addresses. (DHCP server unreachable messages)
2. Unable to use the restore config feature. (file uploads and seems to apply yet no changes are actually made.)
3. QOS locks up router. If I try to set up QOS the router has to be reset to factory defaults.
I have kind-of just dealt with it, but the DHCP thing is really bothersome. I have to go in the room with all of my network equipment and power cycle the thing to get an internet connection, that raises the possibility that I will have to reset the other devices.I am seriously reconsidering returning my WRT350N for another N-based router. The current firmware is not stable. I have had a WRT54G V1 and WRT54G V5 for years and never had a signel issue. Just to make sure I didn't get a bad unit I returned for another so I know it isn't hardware related.
1) DDNS not updating. This has always worked on my WRT54G's without issue
2) XBOX 360 wouldn't stay connect to Live. Changing MTU size seems to 1365 make more stable
3) Storage support works for a while and then stops or randomly freezes unit.
4) FTP changes require unit to be manually rebooted for changes to take effect.
Really hope a new firmware release is soon. I love the features of the 350N but
it is not a very stable router at this point. If DD-WRT releases a firmware that has the storage gui enabled might take a look there but at this point I am frustrated with the unit.
Message Edited by GAH1068 on 03-30-200707:02 AM
Message Edited by GAH1068 on 03-30-200707:02 AM -
ThinInstaller problems with SCCM
Hi,
I am having very frustrating problems with ThinInstaller. I am trying to deploy drivers to a Thinkpad with ThinInstaller via SCCM. Hope anyone with experience of it working or any experience of ThinInstaller in general can help.
I am not too sure where the problem lies, although I think it is mainly with ThinInstaller. I am quite new to both SCCM and to ThinInstaller so I have built up what I have for it using what I found on the Internet.
SCCM Setup
I have a Task Sequence setup to initially install the Networking and Storage drivers, this works ok. The machine adds to the domain without any problem. Then I run the commands in the screenshot below.
Task Sequence
Step 1 – Run ThinInstaller Trustzone
%Windir%\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -pp off -m -ag 1.2 -url file://\\192.168.100.236\PackageSource\OSDDrivers\Win7x86\LenovoT420-4236JDO FullTrust
Step 2 – CMD CP ThinInstaller
I run the following command line;
cmd.exe /c xcopy.exe "\\192.168.100.236\smspkge$\SHR0012E\*.*" C:\Lenovo\thininstaller\ /E /D
It gets passed this step; I can see the C:\Lenovo\ThinInstaller folder
Step 3 – CMD Run Thininstaller
I run the following command line;
cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\192.168.100.236\PackageSource\OSDDrivers\Win7x86\LenovoT420-4236JDO -noicon -includerebootpackages 1,2,3,4
This step doesn’t seem to work.
I have pasted in sections of the Task Sequence as well as details of my ThinInstaller setup below;
Part of ThinInstaller error log
[Thin Installer build: 2009-12-09 Version: 1.1.0005] 5/31/2012 12:09:09 PM
Info 2012-05-31 , 12:09:09
at Tvsu.Environment.EnvironmentManager..ctor()
Message: Starting Environment Manager...
Info 2012-05-31 , 12:09:09
at Tvsu.Nls.NlsResources..ctor()
Message: Starting the instance of NLS@Runtime
Info 2012-05-31 , 12:09:09
at Tvsu.Nls.NlsResources..ctor()
Message:
The active language is: EN
The default language is: EN
The OS language is: EN
The language loaded type is: Override
Info 2012-05-31 , 12:09:09
at Tvsu.CommandLine.CommandLineParameters.ValidateArguments(String[] args)
Message: Validating arguments: System.String[]
Info 2012-05-31 , 12:09:09
at Tvsu.CommandLine.CommandLineParameters.ValidateArguments(String[] args)
Message: The command is: /CM -searchA-actionINSTALL
Info 2012-05-31 , 12:09:09
at Tvsu.CommandLine.CommandLineParameters.SearchForUpdates()
Message: Searching for Updates: A
Info 2012-05-31 , 12:09:09
at Tvsu.CommandLine.CommandLineParameters.SearchForUpdates()
Message: Notify method: INSTALL
Severe 2012-05-31 , 12:09:09
at Tvsu.Sdk.SuSdk.StartApplication()
Message: Application runs with the framework: 2.0.50727.4927
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.DataBase.InitializeDataBase()
Message: Initializing the DataBase from file: updates.ser
Info 2012-05-31 , 12:09:09
at Tvsu.Sdk.SuSdk.StartApplication()
Message: Starting the Application
Info 2012-05-31 , 12:09:09
at Tvsu.Sdk.SuSdk.GetSystemProperties()
Message: Get the System Properties
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.StartExecution()
Message: PreTask
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.StartExecution()
Message: Start
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Starting the task
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The current process is:HelloProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the PreProcess HelloProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the StartProcess HelloProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.HelloProcess.Start()
Message: HelloProcess Started
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.HelloProcess.Start()
Message: MTM is: 4236JD0
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.HelloProcess.Start()
Message: Data to be set in the Environment Manager to use with Quest:
QOS (Quest OS): Windows 7
QOSLang (Quest language): EN
MTM: 4236JD0
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the PostProcess HelloProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The process HelloProcesshas been finished.
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.StartExecution()
Message: PostTask
Info 2012-05-31 , 12:09:09
at Tvsu.Sdk.SuSdk.GetSystemProperties()
Message: Return the System Properties
Info 2012-05-31 , 12:09:09
at Tvsu.CommandLine.CommandLineParameters.SearchForUpdates()
Message: The System Properties are:
4236JD0
Windows 7
EN
Info 2012-05-31 , 12:09:09
at Tvsu.Sdk.SuSdk.GetApplicableUpdates(searchingFolderDelegate spd, showErrMsgDelegate sed)
Message: Get Applicable Updates
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.StartExecution()
Message: PreTask
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.StartExecution()
Message: Start
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Starting the task
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The current process is:HelpCenterIndexRepositoryProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the PreProcess HelpCenterIndexRepositoryProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.HelpCenterIndexRepositoryProcess.PreProcess()
Message: 'Share name' to use: \\192.168.100.236\PackageSource\OSDDrivers\Win7x86\LenovoT420-4236JDO\
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the StartProcess HelpCenterIndexRepositoryProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.HelpCenterIndexRepositoryProcess.LaunchEgather()
Message: Launching Egather
Info 2012-05-31 , 12:09:09
at Tvsu.Egather.EgatherManager.GetEgatherParser(String type)
Message: Running egather complete.....
Info 2012-05-31 , 12:09:09
at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabaseManager.GetDescriptors(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
Message: Received data -> ShareName: \\192.168.100.236\PackageSource\OSDDrivers\Win7x86\LenovoT420-4236JDO\, Agent:
Info 2012-05-31 , 12:09:09
at Tvsu.Egather.EgatherExecutor.RunAsWindowsService(String directory, String command, String arguments)
Message: I received this info:
Directory: C:\Lenovo\ThinInstaller\egather\
Command: ia.exe
Arguments: -filename"C:\Lenovo\ThinInstaller\egather\sysreco" -silent -local -section SYSTEM_SUMMARY REGIONAL_SETTINGS SMBIOS_INFORMATION Firmware_Information Installed_Software SMBIOS_INFORMATION DEVICE_DRIVERS_AND_SERVICES IDE_DEVICE_INFORMATION DEVICE_MANAGER_SETTINGS -p device_manager enable_hardwareid
Info 2012-05-31 , 12:09:09
at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(String dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
Message: Directory: C:\Lenovo\ThinInstaller\egather\
Command: ia.exe
Arguments: -filename"C:\Lenovo\ThinInstaller\egather\sysreco" -silent -local -section SYSTEM_SUMMARY REGIONAL_SETTINGS SMBIOS_INFORMATION Firmware_Information Installed_Software SMBIOS_INFORMATION DEVICE_DRIVERS_AND_SERVICES IDE_DEVICE_INFORMATION DEVICE_MANAGER_SETTINGS -p device_manager enable_hardwareid
Install type: COMMAND
TimeOut: 300000
HideWindow?: True
Info 2012-05-31 , 12:09:09
at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(String dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
Message: Directory 1: C:\Lenovo\ThinInstaller\egather\
Info 2012-05-31 , 12:09:09
at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(String dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
Message: If directory 1 exists: C:\Lenovo\ThinInstaller\egather\
Info 2012-05-31 , 12:09:09
at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(String dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
Message: The parameters directory and command stay as follows:
Command: ia.exe
Directory: C:\Lenovo\ThinInstaller\egather\
Info 2012-05-31 , 12:09:09
at Tvsu.Executor.CommandLauncher.ExecuteCommandLine(String dir, String cmd, String args, String _installType, Int64 timeOut, Boolean hide)
Message: Type hidden
Info 2012-05-31 , 12:09:09
at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabaseManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
Message: The database.xml file was found in \\192.168.100.236\PackageSource\OSDDrivers\Win7x86\LenovoT420-4236JDO\
Info 2012-05-31 , 12:09:09
at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabaseManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
Message: Processing the data base xml file
Info 2012-05-31 , 12:09:09
at Tvt.LocalRepositoryDatabase.LocalRepositoryDatabaseManager.GetDescrips(String shareName, String mtm, String os, String oslang, String agent, Boolean bValidateLocalRepository)
Message: Processing the data base schema file
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the PostProcess HelpCenterIndexRepositoryProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The size for the UpdateResponse is 32
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The process HelpCenterIndexRepositoryProcesshas been finished.
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: The current process isescriptorLoaderProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the PreProcess DescriptorLoaderProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Task.Task.Start()
Message: Executing the StartProcess DescriptorLoaderProcess
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.DescriptorLoaderProcess.Start()
Message: Failed to get the file Object reference not set to an instance of an object.
Info 2012-05-31 , 12:09:09
at Tvsu.Engine.Process.DescriptorLoaderProcess.Start()
Message: Failed to get the file Object reference not set to an instance of an object.
Info 2012-05-31 , 12:09:10
at Tvsu.Sdk.SuSdk.ShutDownApplication()
Message: Shut Down the Application
ThinInstaller.exe.configuration
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<RepositoryPath></RepositoryPath>
<LogPath>C:\Lenovo\ThinInstaller\ExtraLogs</LogPath>
<LanguageOverride>EN</LanguageOverride>
<BlockSize>4096</BlockSize>
<AskBeforeClosing>NO</AskBeforeClosing>
<DisplayLicenseNotice>NO</DisplayLicenseNotice>
<IgnoreLocalLicense>YES</IgnoreLocalLicense>
<IgnoreRMLicCRCSize>YES</IgnoreRMLicCRCSize>
<DebugEnable>NO</DebugEnable>
<ContentMode>Active</ContentMode>
</configuration>
Task Sequence Error
Failed to run the action: CMD Run ThinInstaller.
Incorrect function. (Error: 00000001; Source: Windows)Create a Folder Applications in Microsoft Deployment Kit
Copy de application ThinInstaller in this folder
Install Lenovo "Update Retriever" on a Windows Machine.
Configure Lenovo "Update Retriever" for download the Drivers
Modify the Repository with;
Close "Update Retriever" and go to the location of your Repository folder on the machine
Copy this folder to the \ThinInstaller folder that you create in Microsoft Deployment Kit
Example: ...\Microsoft Deployment Toolkit 2012\Applications\ThinInstaller
Update sccm dp's
Sccm Task Sequence
Create a Task Sequence lines after Setup Windows and ConfigMgr
Example:
Run Command Line
Apply - Lenovo Driver Based Applications (01) and Apply - Lenovo Driver Based Applications (02)
You need run this twice because there are dependency on the drives package’s
More info let me know
Maarten -
Problems with spotty cable modem connection when connected to 3rd gen Airport Extreme
Hi All, here's my problem:
I've got a 3rd gen airport extreme (AEBS) that I've been using for the last several years and had no issue. Recently, I decided to switch from Verizon DSL to Time Warner Cable, and in order to avoid extra fees, I decided to purchase my own cable modem. Here begins an epic battle with sanity...
- 1st modem Motorolla SB6141: This was the first modem that I bought and it worked like a charm... at first. The first week was like a dream come true, with incredibly fast speeds and very low latency (ping=15ms, dl=30Mbps, ul=5Mbps). The AEBS and the modem got along great, no issues until all the sudden the connection speeds started dropping off. The connection would never fully drop to zero, but close. The bandwidth would hover around 1Mb down, which was about a 1/30 of the speed I was supposed to be getting. I chalked it up to a bad model so I headed back to Best Buy.
- 2nd modem Zoom 5341J: This modem istalled with little issue and worked pretty well. The only problem I encountered with this modem was that it seems to cause a ton of network latency (ping=200ms average), which was way too slow for me. On the first night that I had this modem working, I cycled the power (to try to resolve the latency issue) and it never came back on. there must have been a short in the board or something. Back to Best Buy.
-3rd modem Netgear CMD31T: This modem was an absolute nightmare to get connected to the AEBS. The process involved following a VERY specific order of operations that involved powering down the modem and the AEBS, doing a factory reset on the AEBS, poweing down the AEBS, powering on the modem, plugging the modem into the AEBS, and powering on the AEBS. None of the other modems gave me that much trouble, but when I eventually got it working it was FAST. I was getting the best latency and bandwidth out of all of the modems. Unfortunately, that lasted about 5 minutes, when the bandwidth dropped to 1Mbps and never recovered.
I know what you all are thinking... the problem must be with the AEBS. But here's the kicker, I have an Airport Express that I tested with all three modems and got the same results. Well then (you must be thinking), the problem is obviously with the ISP! But when I connected all three modems directly to my MacBook Pro, they all worked fine, with no connectivity issues. The only time I encounter a problem is when I involve an Apple router. I love my AEBS and my Airport Express, so I'm avoiding buying a different brand router. Does anybody have any suggestions? Thanks for your help!Well after doing some research, I've figured out that the problem I was encountering had nothing to do with the Airport Extreme or the cable modem! Apparently, my problem was caused my uplink saturation. In other words, my cloud backup service (BackBlaze) was using up all of my upload bandwidth, which meant that ACK packets (acknowledgments) weren't even getting through. This would basically cause any server I was downloading from to stop sending additional packets, making it appear that connection to the internet had been severed. My simple fix was to cap the bandwidth of my BackBlaze backups to about half of my total upload bandwidth. One thing I did learn is that the this issue is usually fixed by using a router with QOS (Quality of Service) capabilities to prioritize ACK packets. Unfortunately, for some reason Apple has neglected to add this feature to even their high end routers.
-
I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
LeftyThis was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
boolean active = true;
public void run(){
ss.setSoTimeout(90);
while (active){
try{
serverSocket = ss.accept();
catch (SocketTimeoutException ste){
// do nothing
// interrupt thread
public void deactivate(){
active = false;
// you gotta sleep for a time longer than the
// accept() timeout to make sure that timeout is finished.
try{
sleep(91);
}catch (InterruptedException ie){
interrupt();
}
Maybe you are looking for
-
I am new to Apple and thought I would try a free game App but it is requesting me to change my Apple id (I do not want to change it) and it will not allow me to type or cancel the box or the game. Can anyony assist me please.
-
Hi, I ahve entered the order information. When i am trying to Book it, I am getting the below error:The Booking Activity has errored out, please contact your System Administrator. Can anyone help me with a solution for this. Regards, Sravan.
-
HT4759 how do i retrieve my contact information that was in my iphone 4s n transfered to 5s
how do i retrieve my contact infornation after sale of new phone
-
I'm trying to understand this so bare with me. The current form we have in SharePoint ask for a user to enter and There name, Event, and # of Tickets requested. I create a new column named Events to list all the events we hold. Now the form part wo
-
My i tunes appears to work perfectly well but when i connect my i pod (older 20G model)via the apple cable the i pod fails to appear on the screen and within 30 seconds or so my computer shuts down and starts up again. I have reset my i pod several t