QOS 6509 v12.2(17d)SXB10

6509 has WS-X6724-SFP, WS-X6748-GE-TX (RcvQ-1Q8T, xmtQ-1P3Q8T) and Sup720. I have questions about the command: mls qos rewrite ip dscp
Q.1. When is the received TOS rewritten ?
Q.2 Why would I want to use: no mls qos rewrite ip dscp ' to preserve TOS byte ?? At 6509, I am 'trusting dscp' at trunk ports, Can TOS byte still be overwritten ?

Hi,
1. The TOS is rewritten on egress
2. You seem to be right. When you set a port to trust DSCP, you are getting the switch to not reset the DSCP to 0 for incoming packets. The switch will use whatever DSCP the packet came with. On egress, the switch will use the DSCP to CoS map to select the egress queue. Finally, when sending the frame out, the switch will set the CoS value to whatever CoS value the DSCP was mapped to. However, the DSCP value will not be overwritten, since that is supposed to be trusted. Therefore, the 'no mls qos rewrite ip dscp' appears to be redundant in this case. However, the difference is that this command is a global command and will result in ToS-preservation for packets received on all interfaces and not just those set to trust DSCP
Hope that helps - pls rate the post if it does.
Regards,
Paresh.

Similar Messages

  • QOS-ios 12.2

    6509(12.2(17d)SXB10)-->4500(12.2.25SG)
    I am planning to use vlan-based-qos.
    -Several VLANs are defined at 6509 and trunked to 4500. To use, vlan-based-qos, is it enough to define qos-vlan at vlan interfaces at 6509 only.
    Do i have to define one interface for each vlan at 4500 ? At present only one interface (VLAN1) with IP address is configured on 4500 though ports belong to different Vlans.

    Hi,
    generally QoS has to be applied where there can be a lack of resources. In your case this can be f.e. trunk and access ports. The question is what you want to achieve where. In case you want a VLAN based policer you need a vlan interface to apply the policy to. For queueing you can apply per port or per switch settings, so no VLAN interfaces nessessary.
    Hope this helps
    Martin

  • CATOS QOS commands - what are they in IOS?

    I have the following commands in CATOS on a 6500 but I need to know what they should be in IOS 12.2(17d)SXB10?
    set qos enable
    set qos cos-dscp-map 0 8 16 24 32 46 50 56
    set qos map 2q2t tx 2 2 cos 5
    set qos acl ip TRUST-DSCP trust-dscp any
    commit qos acl TRUST-DSCP
    set qos acl map TRUST-DSCP 8/1-48
    Please can someone help???

    !!set qos enable
    Router(config)# mls qos
    !!set qos cos-dscp-map 0 8 16 24 32 46 50 56
    Router(config)# mls qos map cos-dscp
    !!set qos map 2q2t tx 2 2 cos 5
    Router(config)# interface gigabitethernet 1/1
    Router(config-if)# rcv-queue cos-map queue_# threshold_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]]
    Router(config)# interface gigabitethernet 1/1
    Router(config-if)# wrr-queue cos-map 1 1 0 1
    !!set qos acl ip TRUST-DSCP trust-dscp any
    !!commit qos acl TRUST-DSCP
    !!set qos acl map TRUST-DSCP 8/1-48
    Router(config)# class-map class_name
    Router(config-cmap)# match access-group name acl_index_or_name
    Router(config)# policy-map policy_name
    Router(config-pmap)# class class_name
    Router(config-pmap-c)# trust dscp
    Router(config)# interface fastethernet 1/1
    Router(config-if)# service-policy [input | output] policy_map_name
    I believe this is right. If you need further clarification please ask or refer to…
    http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a00801679f8.html

  • Cat3750 per interface queue statistics

    Hi there
    I know each interfaces has 4 outgoing queues and one can be configured to have the highest priority.
    So far I have not seen a command or way to know exactly how many packets/bytes are being forwarded through each queue in each interface.
    (i.e. show mls qos ....)
    Any ideas?
    Even more: any SNMP MIBs you may know?
    I know we can see counters for different DSCP values and we can also see mappings between DSCP and outgoing queues (which are not very clear to me). Is there something that clearly shows which traffic is really using the high priority queue and which is not?
    Thanks

    Thanks for the reply.. but on my 6509 with ios 12.2(17d)SXB10, theres no option for stats - only one is for stats export.. why is that ?? How to get stats ??
    to0#sho mls qos ?
    aggregate-policer aggregate-policer keyword
    ip ip keyword
    last last keyword
    mac mac keyword
    maps maps keyword
    module show entries in module
    mpls mpls keyword
    protocol protocol passthrough information
    statistics-export QOS Statistics export
    | Output modifiers

  • WS-X6704-10GE Problem

    I have a Catalyst 6509 with supervisor 720-3B and IOS 12.2(17d)SXB10. I have installed a X6704 4 port 10Gb card in slot 1 and powered up the system. The X6704 is recognised but is powered off with a message stating that it is not supported. Using show module the online daig status is unknown and the detals for the card are as follows:
    HW FW Sw Status
    1.5 12.2(14r)S5 12.2(17d)SXB Other
    I have tried using alternate IOS levels such as 12.2(18)SXD4 but get the following error messages:
    %PM_SCP-SP-1-LCP_FW_ERR: System resetting module 1 to recover from error: Linecard received system exception
    %OIR-SP-3-PWRCYCLE: Card in module 1, is being power-cycled Off (Module Reset due to exception or user request)
    Can someone please tell me what is wrong and if its the IOS I'm using what level I need to support the card.
    Thanks

    Hi Paresh,
    I don't think I have any of those cards. Using show module I have the following:
    Mod Ports Card Type Model Serial No.
    1 16 SFM-capable 16 port 1000mb GBIC WS-X6516A-GBIC SAL0715BHAR
    2 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL08280B14
    3 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAL09465FNV
    4 6 Firewall Module WS-SVC-FWM-1 SAD071903HF
    5 2 Supervisor Engine 720 (Active) WS-SUP720-3B SAL09358QGZ
    6 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAL09475WKY
    9 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAL094448HW
    Mod MAC addresses Hw Fw Sw Status
    1 0009.11f7.ff90 to 0009.11f7.ff9f 1.0 7.2(1) 8.3(0.156)RO Ok
    2 0011.5ccf.08b0 to 0011.5ccf.08b3 1.5 12.2(14r)S5 12.2(18)SXD7 PwrDown
    3 0015.f998.2e38 to 0015.f998.2e67 1.1 7.2(1) 8.3(0.156)RO Ok
    4 0003.feab.7538 to 0003.feab.753f 2.0 7.2(1) 2.3(3)2 Ok
    5 0013.7f0a.e194 to 0013.7f0a.e197 4.4 8.1(3) 12.2(18)SXD7 Ok
    6 0015.f943.e990 to 0015.f943.e9bf 1.1 7.2(1) 8.3(0.156)RO Ok
    9 0015.c6c9.32a4 to 0015.c6c9.32d3 1.1 7.2(1) 8.3(0.156)RO Ok
    Mod Sub-Module Model Serial Hw Status
    5 Policy Feature Card 3 WS-F6K-PFC3B SAL09358QTN 2.1 Ok
    5 MSFC3 Daughterboard WS-SUP720 SAL09358N63 2.3 Ok
    Mod Online Diag Status
    1 Pass
    2 Unknown
    3 Pass
    4 Pass
    5 Pass
    6 Pass
    9 Pass
    does this mean I need some extra kit to use the x6704 ?
    Thanks,
    Paul

  • Traffic shaping CIR refering to layer 2?

    Hi,
    When I use following command,
    shape average 50m
    is the CIR rate 50Mbps referring to layer1? I am asking this question because I observed throughput difference between 64bytes and 1500bytes packet (calculated from show interface throughput reading). I am wondering if it is caused by preamble and inter-frame gap impact of Ethernet.
    Thanks,
    James

    here is your whitepaper
    6509-1
    int loopback0
    ip address 10.0.0.1
    pseudowire-class EOIP
    encapsulation l2tpv3
    interworking ip    <<<< OPTIONAL if you have different L2 types on two sides, don't need it if it's VLAN mode on both sides
    ip local interface Loopback0
    interface Vlan1000
    xconnect 10.0.0.2 999 pw-class EOIP
    ip access-list ex EOIP
    permit 115 host 10.0.0.1 host 10.0.0.2          <<<< IP Protocol 115 is used by L2TPv3 for encapsulation
    class-map EOIP
    match access-group name EOIP
    policy-map QOS
    class EOIP
      police 1000000               <<<<< Police to 1Mbps
    interface Gig1/1 (or whatever interface facing core)
    ip address x.x.x.x x.x.x.x
    service-policy output QOS
    6509-2
    int loopback0
    ip address 10.0.0.2
    pseudowire-class EOIP
    encapsulation l2tpv3
    interworking ip
    ip local interface Loopback0
    interface Vlan1000
    xconnect 10.0.0.1 999 pw-class EOIP
    ip access-list ex EOIP
    permit 115 host 10.0.0.2 host 10.0.0.1
    class-map EOIP
    match access-group name EOIP
    policy-map QOS
    class EOIP
      police 1000000
    interface Gig1/1
    ip address x.x.x.x x.x.x.x
    service-policy output QOS
    verify operation with:
    show xconnect all
    show policy-map int gig1/1 output

  • 6500 with SLB blade dropped the packets from HA device.

    A weird behavior observed in 6500 with SLB blade. the topology is as below:
    client--HA---6500 with SLB----server farm
    The first Syn packet reached the 6500 with client MAC address as source MAC and can be forwarded to the server correctly. But due to HA vendor special behavior, the second Syn packet's source MAC is rewritten to HA device MAC address and this Syn is dropped by the 6500.
    Is this a special feature for 6500? And is it possible to change this behavior?
    Thanks in advance.

    Thanks for your reply.
    1, HA device is from other vendor. It works as transparent mode and the session will be processed by 2 blades in the round-robin schedule.
    The first SYN is processed by the master and reach the 6500 with client MAC as the source MAC. the second SYN is processed by the slave and the source MAC is rewritten to the slave's interface mac. This SYN packet is dropped by either 6500 or CSM, not quite sure.
    2, The image on the 6500 is as below:
    Cisco Internetwork Operating System Software
    IOS (tm) s72033_rp Software (s72033_rp-PK9SV-M), Version 12.2(17d)SXB10, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2005 by cisco Systems, Inc.
    Compiled Thu 11-Aug-05 14:15 by kellythw
    Image text-base: 0x40020FBC, data-base: 0x41F20000
    cisco WS-C6503-E (R7000) processor (revision 1.1) with 458752K/65536K bytes of memory.
    Processor board ID FOX0930005J
    SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
    3, which command should be used to "Capture a trace of the csm etherchannel"?
    It seems that only the SYN with rewritten source MAC is dropped. The SYN with client MAC works fine.
    Should you need any other information, pls let me know.
    Thanks & Regards

  • VTY not getting auto updated

    Its a 6509 v12.2; debug output does not get auto displayed on the putty/vty terminal. However all the output is visible with show logging and i have to do sh logging again and again to check new output. Below is the configuration for logging and i have used terminal monitor aswell.
    logging trap notifications
    logging source-interface Loopback0
    logging 10.10.10.10

    Hi, rajitoor55.
    Yes, you need to put command "terminal monitor" every time after connecting to vty  line (this command stop works after droping connection) or after command "terminal no monitor".
    Best Regards.

  • LLQ priority issue after upgrading to Sup32 on Cisco 6509

    Hi,
    I have 1x Cisco 6509 with Sup2 and MSFC2 and it is running on IOS (c6k222-jk9sv-mz.122-17d.SXB11).
    I have following policy map :
    Policy Map VOIP
        Class IPPHONE
          priority percent 75
    and the following command on each interface:
    service-policy output VOIP
    those configuration are working fine on SUP2 with MSFC2 but last week I tried to upgrade the SUP2 to SUP32 on the switch and upgrade the IOS to the latest version (s3223-adventerprisek9-mz.122-33.SXJ4)
    but when I try to put service-policy output VOIP on each physical interface I am getting the following error:
    "Priority command is not supported in output direction for this interface"
    and when I try to add service-policy output VOIP on a VLAN interface I am getting following error:
    MQC features are not supported in output direction for this interface.
    Please let me know if I need to change something after upgrading to SUP32.
    Thanks

    Hi
    Hi
    Sup32 uses PFC3B for Hardware forwarding and implemenation of features like qos, acl, netflow etc
    PFC QoS does not support these policy map class commands:
    •bandwidth
    •priority
    •queue-limit
    •random-detect
    •set qos-group
    •service-policy
    http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html
    Thanks
    Raju

  • 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 Regard

    hi,
    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]

  • What is the best way to trust DSCP values on 6509 interfaces?

    I have 6509's with 2 Ten-gig interfaces configured into a Port Channel (routed with IP addressing) - the IOS is 12.2(18)SXE3. I want to trust the DSCP values of packets traveling through the interfaces and have applied 'mls qos trust dscp' on both the physical Ten-gig interfaces as well as the L3 Port Channel interface.
    1.Is it necessary to have the statement on all the interfaces, or is just having it on the Port channel enough?
    Here is the config right now:
    interface Port-channel4
    description to 6509-Core-A P4 (T1/3, T2/3)
    ip address 164.xxx.xx.xx 255.255.255.252
    ip pim sparse-mode
    ip route-cache flow
    mls qos trust dscp
    interface TenGigabitEthernet1/1
    description to 6509-Core-A T1/3 (P4)
    no ip address
    ip route-cache flow
    mls qos trust dscp
    channel-group 4 mode desirable
    interface TenGigabitEthernet1/2
    description to 6509-Core-A T2/3 (P4)
    no ip address
    ip route-cache flow
    mls qos trust dscp
    channel-group 4 mode desirable
    Also, what command can I use to see the dscp counters? In the 3560/3750 catalyst line you can enter: 'sh mls qos int f0/1 statistics' and get a display of all the dscp/cos input/output packet counts, but I can't find a comparable command in the 6509.
    2. Is there one?

    I think you do this on the individual port interfaces, not the port-channel interface, becasue the queueing mechanisims associated with DSCP values are port based.
    By doing this, if you have policy maps you want to use, you attach them to the ports not the port-channel.
    For the command on 6509, you can use:
    sh mls qos ip gigabitEthernet 1/1
    Hope this helps and let me know how that works out.
    Gary

  • QoS - End to End

    v\:* {behavior:url(#default#VML);}
    o\:* {behavior:url(#default#VML);}
    w\:* {behavior:url(#default#VML);}
    .shape {behavior:url(#default#VML);}
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman";
    mso-ansi-language:#0400;
    mso-fareast-language:#0400;
    mso-bidi-language:#0400;}
    END to END QOS:
    There are two sites and we are going to implement end to end Qos.
    Site1: Avaya IP phones are connected (Users)
    Site2: IPT Servers are connected
    Bandwidth Requirement is 9.6 Mbps between two sites for Voice traffic.
    Below is the topology Detail:
    Avaya Phones are connected ----L2--àCisco 3750G ---L2---à Cisco 6509-----L3----->Cisco 7206--------àWAN ---------àCisco 7609-------àCisco 6509-------àCisco 3750G—Access link---------àIPT SERVERS
    As per above topology, what will be the configuration for End to End Quality of Service? And what configuration need to apply on Access Switches ports on which  Avaya phones are connected and  the ports on which Core switch are  connected?
    And Also what configuration need to apply on Core switches  on both side and what will be configuration on both routers?
    Appreciating providing configuration for end to end QOS.
    Thanks for Help.

    All networks can take advantage of aspects of QoS for optimum efficiency. ISPs require assured scalability and performance.
    For more information refer this link.
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/qos_c/qcintro.pdf

  • QoS/bandwidth throttling on autonamous WAPs?

    We have about 5 autonamous 1231AG WAPs running IOS v12.3(8)JEC. I want to be able to limit, or at very best, prioritize corporate and voice WLAN traffic over those using guest SSID (VLANs listed below). So, I want to priortize traffic by VLAN. VLAN priortiy is: voice, corporate, management, guest.
    Would the best way to be to go to each WAP, QoS, and make a new policy for each VLAN? For corporate, I assigned all IP precedences a CoS of 3 (Excellent). For voice, all IP precedences a coS of Voice (6), and guest, all IP porecedences a CoS of (1). I would then assign the respective policies to each VLAN, inbound and outbound. IMy thinking is that no matter what precedence traffic is on guest VLAN, the WAP will downgrade it to CoS 1, making it the lowest priority traffic coming through the WAP.
    Would this accomplish what I am trying to do? Please note, these WAPs are not plugged into Cisco gear. Rather, we have Nortel switches, so talking of Catalyst gear won't work.
    VLAN1=management (native)
    VLAN10=Corporate LAN
    VLAN20=voice
    VLAN66=guest

    Hmmm...I have to ask if the Nortel switches recognize the CoS functionality. I have no idea.
    Your scenario is this - QoS really happens at the switch anyway. You can set the settings you discussed, but in the air, there is no QoS in a radio contention based network. Not yet anyway.
    So, if you are fighting for radio space, make it to the AP and then get passed on to a switch that may or may not recognize the effort, you might not be doing yourself any favors.
    Are you prioritizing voice now? This is a good question I'd like to read up on - thanks.

  • QoS Questions for 3750 Switches

    2x3750 switches are stacked and we are trying to simulate traffic congestion at the UTP ports by using Smartbit 6000C. The objective of the test is to see if the QoS setting works in reality even though we see from Wireshark that the packets are marked with DSCP for voice traffic.
    Setup is as follows :
    Smartbit<->Avaya IP Phone<->3750 switches<->6509 switch.
    Please note that the configuration is set on the 3750 switch port as well as trusted on the Cat 6 switch port. However, when I set to continuous traffic with byte size of 64. Even though its a 100Mbps port, the Avaya IP Phone is already acting weird with hanged symptom. Just side note is that performing "show mls qos inter gi2/0/7 statistic" shows that data and voice traffic are marked on the different priority which seemed correct.
    1) Is this the right way to test? If not, what should be the correct way?
    2) The port that's connected to Smartbit is configured and it seemed that with the continuous traffic, even other IP Phones are hanged even though I have set Smartbit to hit on the IP address of the CAT6 Switch port. This is not normal right as this is supposed to be unicast traffic. Any idea what could be the reason?

    Hello Brandon,
    I understand your concern and how you want to test, but with the VoIP services you need to understand that there are 2 points (telephones if you want) involved. Your local one, where you might have taken all the necessary steps to protect and prioritize your voice traffic, and the oposite end which also need to have the voice packets prioritized.
    Now, from your description, I understand that the packets (voice and data) marked correctly (I believe on C3750), but that's not enough. You need to use CBWFQ together with LLQ to give priority to the Voice traffic over data in case of congestion. Do you have such configuration? Can you show us some excerpt from it?
    Next, during the testing, you said that your phone hang-up...where you in a call?
    To respond to your questions:
    1. The start is ok, but we need more details. You are pushing traffic from Smarbit, this is your local end, but where is the traffic pushed to (remote end), who is receiving the traffic?
    2. In theory, you shouldn't have any impact over voice if links are 100Mbit, only if you have such a power packet generator that could fill 100Mbit. What do you mean by "This is not normal right as this is supposed to be unicast traffic"? VoIP is also unicast traffic...
    I can see that you are determined to solve this issue, and this is OK as it will help you back with gained knowledge, but I have to warn you that troubleshooting QoS / Voice related problems may be more tricky than you think, as it will involve a strong know-how in these areas.
    We will help, but you have to come back with more precise details.
    Good luck!
    Calin

  • Mls qos trust dscp??? is setting my DSCP values to zero!?

    Hi,
    I was just doing some testing to ensure that the command 'mls qos trust dscp' is working on my 6509 switches before rolling out QoS.
    Before adding any configuration I could see using wireshark that traffic from my Avaya 9608 handset was coming through with a DSCP value of 46 (as it is supposed to).
    I then added the command 'mls qos' (at global level)
    on examining the wireshark output this time, the DSCP value had been set to zero (i.e. it defaulted it to best effort)
    I then expected by adding the commmand 'mls qos trust dscp' on the interface the phone is connected to that the DSCP value would would again be left alone?
    does anybody know why this is happening?
    Many thanks in advance.
    Andy

    Hi,
    thanks for your reply.
    mls qos
    interface GigabitEthernet3/34
    description *** DATA VLAN 35 - VOICE VLAN 34 ***
    switchport
    switchport trunk native vlan 36
    switchport trunk allowed vlan 34,36
    switchport mode trunk
    mls qos trust dscp
    no cdp enable
    spanning-tree portfast trunk
    If i don't include the global 'mls qos' command then the voice packets keep the dscp 46 value.  If I add the mls qos command this causes the switch to set the dscp values to zero.
    Thanks again 
    ps.  there are some other mls commands on the switch... i don't know if these could interfere but they were already on there so i'm reluctant to remove them..

Maybe you are looking for

  • Adobe Support Responding to an invalid serial number

    Adobe is deliberately stealing my software and blocking it from usage.  While they recognize my email address when I tried to create a new account to share this with fellow consumers, they cannot find my records and are blocking my Adobe product from

  • How can I transfer a file from Lion to Windows 7

    Hello everybody, I need to transfer a big file from mac Lion To windows 7. How can I do this task? thanks

  • Multiple OMAs on same OMS Host

    Hi - I have not tried this but wanted to get some input if i can do it etall. I have two different OMS servers. I'm planning to install additional agent on each OMS and monitor other OMS---meaning... OMS1 - has its own agent OMA1 OMS2 - has its own a

  • Agent and TNSListener service can not run when system starting

    The Agent and TNSListener services can not run automaticaly when system startes.If run Agent service by hand in control panel,system prompt 3221356559 error message.If run TNSListener service in control panel,system prompt none.But after refresh,TNSL

  • V_T7XSSPERBIZFLC doesnt influence portal Biz card view

    I am trying to show IT0009-ZLSCH on biz card view on Bank Details overview screen at ESS. I maintained entry at V_T7XSSPERBIZFLC but still it doesnt have any impact. 1. I tried to see where the underlying table of this view(T7XSSPERBIZFLDC) is being