QoS for CEM traffic

I have two 3750ME switches connecting two ends of a LES100. On each switch, i have 3845 routers with the NM-CEM-4SER modules, plus direct to switch internet traffic. My complete setup is as shown in the attached PDF.
My problem is that with the default QoS settings, i have lots of drops in the Txqueue of the switches.
The CEM's send traffic as EF, which is trusted throughout the switch setup. Other traffic that comes into the switch is marked down to best effort. Thus, most of the traffic the switches handle is EF,(about 70%, 20MB for now). How do i tune the QoS parameters on the switch to handle this amount and more of EF traffic?

Regaring the QOS, I think we should implement this on the 3750 . It is worth advising you to first upgrade the IOS on this device. The following URL will help you:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_sec/configuration/guide/swqos.html
As you are unable to specify the "bandwidth/priority" on 3750 cli, you will need to use the Queuing and Scheduling (SRR) section from the config guide. So basically you enable the expidite queue for the CEM traffic egreesing the 3750. However I believe you cannot classify the traffic via acl to assign it to queues, so you will need to mark it.

Similar Messages

QOS for inbound traffic on 3560

Just to clarify what I'm asking.... I would like to make the congestion happen on our end and not on the ISP's equipment that I have no control over traffic shaping etc... I can't limit the bandwidth on the aggregate port that the metro e connects to (3750) because it would limit it for all locations and not just one. I think my only option is to limit the bandwidth on the switch at the location in question but I guess it would have to be on the ingress side, but then will it still drop packets according to dscp priority during congestion?

I have a little problem I hope you guys can help me with. We have a location that has a metro e hand off from our ISP. The same metro e also serves other locations and the aggregate point is at our main office which goes to a Cisco 3750 stack. The location in question has a single Cisco 3560 switch. We need to apply QOS for both inbound and outbound traffic to this location. I can tag the traffic to and from there but how do I make it so that the 3560 (or 3750) gets saturated and not the ISP connection for incoming traffic (so we decide what packets get dropped)? srr-queue bandwidth limit can't be used on the metro e port on the 3750 because this would limit all locations and not just the one.Should I put another small switch and put it in from of the 3560? This way I could use srr-queue and apply QOS to the egress queue.I hope this...
This topic first appeared in the Spiceworks Community

Putting QOS for voice traffic in switches.

Hi All,
does anybody know how to prioritize the voice traffic over data in the 2960 SW, in a scenario in which ethernet cable coming to ipphone & from IPphone to PC.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Yes, I do.
laugh - I was temped to stop with the above, as it directly answers your question, but I assume you want to know how.
In principle, you recognize the VoIP traffic as being different from data traffic and provide it "special" egress treatment. Normally you would enable QoS, and for egress, enable PQ, direct VoIP bearer traffic to that queue. You might also direct VoIP signalling traffic to a queue that insures it's not unduly delayed or dropped. You might also set rate caps on ingress VoIP traffic.
Recognition of VoIP traffic can be done in different ways. Your phones might support L2 CoS or L3 ToS marking, your switch might "analyze" ingress traffic, your switch might trust a Cisco VoIP phone, your switch and VoIP phones might use a dedicated VLAN. Basically, there's lots of variables dealing with ingress.
Unfortunately, you've provided insufficient information for specific recommendations.
PS:
BTW, your 2960 might also support auto-QoS, which may, or may not, be all you need to enable.

VoIP QoS for Site-to-Site Tunnel

Hi all,
I need some help with setting up QoS for VoIP between two Cisco ASA 5505 with Site-to-Site VPN.
There is no need for bandwith reservation, only DSCP 46 (EF) should be highest and DSCP 26 second highest queue and the rules should only apply to a site-to-site VPN.
Usually i try to configure the ASAs via ASDM and found out in the Cisco Documentations how to setup QoS for the DSCP bits with a Service Policy and how to set up QoS for a Site-to-Site VPN (Service Policy Rule -> Traffic Match). But how do i configure the QoS for a DSCP bit to only apply to a Site-to-Site Tunnel? And how do i configure different priorities for the two DSCP bits, is this defined by the order of Service Policies?
The QoS has to be enabled on both ASAs for the inside interface?
Thanks in advance
Tobias

Hi Collin,
ok so from the document i think this has to be added on both ASAs to prioritize DSCP 46. Could you have a quick look if this is all i need?
class-map voice_traffic
match dscp ef
class-map data
match tunnel-group <Tunnel Name>
match flow ip destination-address
policy-map voice_policy
class voice_traffic
priority
class Data
police output 200000 37500
service-policy voice_policy interface outside
But there is still the question how two configure another DSCP bit for priority 2, I could not find out how this is done, neither CLI nor ASDM. Any ideas?
BR
Tobias

To configure a QoS for the attached topolgy

Dear friends,
I have to configure QoS for the attached topology with the following requirements, can any one please help me to do the same.
The minimum requirements are that 4 simultaneous VoIP calls need to be supported across the backbone, as well as a dedicated 10MBs of http traffic. Of the remainder of the bandwidth ftp traffic should be given a high priority. Make sure routing protocols are given a suitable priority level.
Thanks and expecting replies

Here are some questions that you'll need to answer, to get started.
What does the HTTP requirement mean? It is not possible to get 10 Megabytes per second on a 1.544 Megabit per second line.
What voice codec will be used on the IP Phones? This will determine how much bandwidth you need to allocate.
Next, read the following link:
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/12_4t/qos_12_4t_book.html
It's all in there. Unfortunately, it's a big topic, so there is a lot there.

QoS for IPTV WS-C4948E / WS-C6506-E / WS-C2960S-48LPS-L

I need your help to understand how best to apply QoS settings to an IPTV service.
Service is delivered by ISP Router -> 4948E -> WS-C6506-E -> WS-C2960S-48LPS-L
I prepared this template, but I think this does not run.
I have questions about enabling qos in WS-C4948E and WS-C6506-E, And if it requires something extra.
I hope your support...
Best Regards!
Joan Rozas
(Attachment Topology).
Sw_Serv_C4948-1_Dehesa
ip access-list extended ACL_IPTV
permit ip 10.1.154.0 0.0.0.255 any
class-map CLASS_IPTV
match access-group name ACL_IPTV
policy-map setDSCP
description Mark DSCP values for ingress traffic
class CLASS_IPTV
set dscp cs5
int G1/5
service-policy input setDSCP
int po5
mls qos trust dscp
VSS_DEHESA
int po241
mls qos trust dscp
int po301
mls qos trust dscp
SW_ACC_P_4B_DEHESA
mls qos
int po5
mls qos trust dscp
int G1/0/35
mls qos trust dscp

I met similiar problem on C4500.
Try to remove etherchannel configuration by taking ports to it's defaults and also interface Port-channel68.
Then create port channel interface by first issuing :
interface GigabitEthernet1/3/10
description SAC88
channel-group 68 mode active
interface GigabitEthernet2/3/10
description ECM DELEJ02SAC88-D20
channel-group 68 mode active
Then configure all stuff around switchport under interface Port-channel68.

Per session QoS for LNS

We have some LNSs running 12.4 SP Services, running with the following config (qos specific lines and currently not working):
class-map match-all voice-signaling
match access-group 101
class-map match-all voice-traffic
match access-group 102
policy-map sub-policy
class voice-traffic
priority 240
class voice-signaling
bandwidth 16
policy-map XXX_qos-voice
class class-default
shape average 256000
fair-queue
service-policy sub-policy
interface Virtual-Template1
ip unnumbered Loopback0
ip mroute-cache
no peer default ip address
ppp authentication chap
no clns route-cache
access-list 101 remark -- SCCP/H323/MGCP/SIP --
access-list 101 permit tcp any any range 2000 2002
access-list 101 permit tcp any any eq 1720
access-list 101 permit tcp any any range 11000 11999
access-list 101 permit udp any any eq 2427
access-list 101 permit udp any any eq 4569
access-list 101 permit udp any any eq 5036
access-list 101 permit udp any any eq 5060
access-list 102 remark -- RTP Traffic --
access-list 102 permit udp any any range 16384 32767
in the feature set for the IOS currently running it suggests this configuration should work, however it will not apply the policy via the Cisco-AVPair command (the command is visible via the debug AAA per user so radius is working, even when we test it by applying the service-policy to the actual virtual-template it errors saying it will only work on an MPL bundle. From what I have read it is suggested that even though this feature is supposed to work, it does not in practice and an upgrade to a feature set which includes QoS:per session shaping and queueing on LNS is needed.
If anyone has any experience of the or has any suggestion of if we can achieve our QoS for voice per session with the current IOS that would be great.

This feature is not related to the NPE type. This feature is performance impacting so you should do some tests to see if your NPE-400 can support the number of L2TP tunnels you want with this feature enabled. If it's not the case, you will have to upgrade your NPE.
HTH
Laurent.

QOS on WAN traffic

Can anyone help on this below configuration
Platinum (According to real time class)
Voice RTP
Gold (40% of remaining)
Voice signalling
Citrix
Video conferencing
Silver (20% of remaining)
Notes
Internet browsing
Bronze (10% of remaining)
SNMP
TFTP
Best effort
Other

Ed,
That is right. QOS and bandwidth profile functionality is for outbound traffic and traffic over VPN, and using QOS you should be able to limit bandwidth for outbound traffic and traffic over Site-to-Site VPN.
Thanks,
Nitin

AutoQoS for voice traffic settings?

Hi Everybody,
I have enabled auto qos on switch and following are information
Voice is the most important traffic in network, must ensure voice traffic goes first
SW# show mls qos map dscp-output-q
Dscp-outputq-threshold map:
d1 :d2 0 1 2 3 4 5 6 7 8 9
0 : 04-03 04-03 04-03 04-03 04-03 04-03 04-03 04-03 04-01 04-02
1 : 04-02 04-02 04-02 04-02 04-02 04-02 03-03 03-03 03-03 03-03
2 : 03-03 03-03 03-03 03-03 02-03 02-03 02-03 02-03 02-03 02-03
3 : 02-03 02-03 03-03 03-03 03-03 03-03 03-03 03-03 03-03 03-03
4 : 01-03 01-03 01-03 01-03 01-03 01-03 01-03 01-03 02-03 02-03
5 : 02-03 02-03 02-03 02-03 02-03 02-03 02-03 02-03 02-03 02-03
6 : 02-03 02-03 02-03 02-03
SW# show mls qos queue-set
Queueset: 1
Queue : 1 2 3 4
buffers : 10 10 26 54
threshold1: 138 138 36 20
threshold2: 138 138 77 50
reserved : 92 92 100 67
maximum : 138 400 318 400
For the
DSCP 46 : it's 01-03 (voice)
DSCP 0 : it's 04-03 (general traffic)
From my understanding
- 01-03 means queue 1 and threshold3. (by default threshold3 is 100 and hidden)
- queue-set 1 is enabled by default on all interface and hidden
According to the above information,
- Does the Auto Qos is design for voice goes first?
- Why the Q1 buffer and maximum are less then Q4? isn't suppose to set more buffer on Q1 for voice traffic? or I have to re-distribute the queue buffer and threshold, etc...
- or I just use priority-queue out, then those queue setting will be ignored?
Thanks in advance
Sam

udp ports 16384 to 32767 for rtp traffic
1720 tcp for control (h323 protocol)

Enabling QoS for enterprise on a router

Hello,
I plan to enable QOS for enterprise on a customer's router between three (3) to five (5) days. Will this have an impact on the router for the said days?
Thanks you in advance,
Martin.

Generally speaking no, qos will not impact any operations at all. It will just classify, mark, police/shape, guarantee bandwidth according to the criteria you specify.
But it will not cause any performance issues.
-Terry
Please rate all helpful posts and mark the thread as answered if you have no other queries.

QoS for App-V

Hello,
I'm currently configuring new 3750X switches.
I must implement QoS on the stack. The QoS must be the following:
VOIP Class (50%)
App-V Class (40%)
Movie Class (10%)
How I can do this (in particular for AppV)? I do the following for the moment:
class-map match-any VOIP
match protocol voice
match dscp ef
match protocol sip
match protocol skype
match protocol rtp audio
match protocol rtp video
exit
class-map AppV
exit
class-map Movie
match protocol rtp video
exit
policy-map BandwidthTraffic
class VOIP
priority percent 50
set dscp ef
class AppV
bandwidth remaining percent 40
class Movie
bandwidth remaining percent 10
interface Gig1/0/3
ip nbar protocol-discovery
service-policy input BandwidthTraffic
Anyone can says me if it's correct or not? And why?
Thank you for your help.
Florent

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
It appears you've some router QoS. 3750X QoS is quite different for egress as you're limited to working with four egress queues. I don't recall 3750X supporting NBAR.
Suggest you read the configuration guide's chapter on QoS, for you 3750X IOS version, and then post questions as necessary. (My concern is, 3750X QoS is so different, it wouldn't be helpful to suggest a QoS configuration until you had a basic understanding of the 3750 QoS architecture and features.)

Administration port - network channel for admin traffic

I am trying to configure a separate channel for Administration traffic on weblogic. I followed the oracle docos and configured the SSL, domain wide admin port, server listen address, ‘admin’ channel.
The issue is admin traffic in not happening through the newly created channel.
L2 network is not getting used. I can’t see any activity in the monitoring tab of new Channel. Also the netstat is showing that the port 9101/9102 is getting used on the 192.168.100.218 and not on 10.254.252.849.
I also tried by setting up the newly created channel weight as 51, but no luck.
Is JMX connectivity related to admin channel?
Any help is highly appreciated. Thanks.
Ipconfig:
Admin: adminserver701.mycompany.internal, 192.168.100.238, 10.254.252.808
Managed: appserver701.mycompany.internal, :192.168.100.218, 10.254.252.849
Domain wide admin port: 9101
Admin:
Listen address –> adminserver701.mycompany.internal
Channel –> admin -> 10.254.252.808/9101
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.808:9101
Managed:(appserver701)
Listen address –> appserver701.mycompany.internal
Admin port override: 9102
Channel –> admin -> 10.254.252.849/9102
Startup -> -Dweblogic.admin.ListenAddress=admin://10.254.252.849:9102
AdminServer Logs:
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613346> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613353> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.edit .>
####<Feb 18, 2013 1:53:33 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159613367> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://adminserver701.mycompany.internal:9101/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616699> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.238:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:53:36 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361159616700> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.808:9101 for protocols admin, ldaps, https.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "Default" is now listening on 192.168.100.238:7001 for protocols iiop, t3, ldap, snmp, http.>
####<Feb 18, 2013 1:55:12 PM EST> <Notice> <Server> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-000000000000001a> <1361159712920> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.238:7002 for protocols iiops, t3s, ldaps, https.>
ManagedServer Logs:
####<Feb 18, 2013 2:54:19 PM EST> <Info> <JMX> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163259911> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://appserver701.mycompany.internal:9102/jndi/weblogic.management.mbeanservers.runtime .>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "Channel-0" is now listening on 10.254.252.849:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:20 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361163260350> <BEA-002613> <Channel "DefaultAdministration" is now listening on 192.168.100.218:9102 for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.100.218:7102 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
####<Feb 18, 2013 2:54:58 PM EST> <Notice> <Server> <appserver701.mycompany.internal> <adp_ms01> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <d3208ed6c2482016:-46ac5fed:13ceba69a8e:-7ffe-000000000000000e> <1361163298045> <BEA-002613> <Channel "Default" is now listening on 192.168.100.218:7101 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
AdminServer logs update while starting managed:
####<Feb 18, 2013 2:54:57 PM EST> <Info> <JMX> <adminserver701.mycompany.internal> <soa_as> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <cd259038c7dcf5a8:-26ac3ba0:13ceb6f767d:-8000-0000000000000162> <1361163297488> <BEA-149506> <Established JMX Connectivity with adp_ms01 at the JMX Service URL of service: jmx:admin://appserver701.mycompany.internal:9102 /jndi/weblogic.management.mbeanservers.runtime.>
Admin Server :
[oracle@adminserver701 bin]$ netstat -an | grep 9101
tcp 0 0 10.254.252.808:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 0.0.0.0:* LISTEN
tcp 0 0 192.168.100.238:9101 192.168.100.218:59038 ESTABLISHED
I am wondering if the JMX connectivity is using the server listen address (adminserver701.mycompany.internal) which will by default resolve to 192.168.100.238. Is there a way to force JMX to use 10.254.252.808?

Hi
For first question the answer is no. With the administration port, you enable the SSL between the admin server and Node manager-managed Servers. You can still use the web console.
For teh second question, you can use ANT or can use the WLS Scripting ..you can get more details in dev2dev.bea.com
Jin

QoS for Video Data

Hello Together,
I like to implement a QoS Policy class to prioritise "Windows Netmeeting". Does somebody know the well known port number and can somebody recommend an bandwidth that i should provide at least to this class ?
Thanks in advance.

As you can find in the Netmeeting IP ports table below, netmeeting uses dynamic ports for Video streaming. So I am not really sure how you can configure QoS for the same.
Anyone has a good tip to achieve this.?
Port Purpose
389 Internet Locator Server (TCP)
522 User Location Server (TCP)
1503 T.120 (TCP)
1720 H.323 call setup (TCP)
1731 Audio call control (TCP)
Dynamic H.323 call control (TCP)
Dynamic H.323 streaming (RTP over UDP)

6500 IOS QoS for Multicast

Question Summary:
How do I set the p-bit (COS value) for multicast traffic ingressing on an interface?
Additional details:
Although I have had success matching all IP traffic ingressing from the encoder/streamer (multicast source) I want to match only multicast traffic.
I see no obvious reason why my attempts with ACL's for multicast are failing to match. Help!
I verified failing or work by output of policy-map information, wireshark from port mirror, and remote client receiving the multicast.
Traffic Type (Multicast):
Source IP: 10.0.0.1
Source Port: 1025
Destination IP: 239.100.0.5
Destination Port: 8208
Destination MAC: 01:00:5e:64:00:05
Here is my configuration:
class-map IPTV
match access-group <ATTEMPT X>
policy-map MARK_INBOUND_IPTV
class IPTV
   set dscp cs4
interface GigabitEthernet3/9
service-policy input MARK_INBOUND_IPTV
Individually attempted the following ACL's for the match statement<ATTEMPT X>:
FAIL:
access-list 81 permit 224.0.0.0 15.255.255.255
access-list 4 permit 239.100.0.5
access-list 700 permit 0100.5e13.05b8 0000.00ff.ffff
access-list 700 permit 0100.5e00.0000 0000.00ff.ffff
SUCCESS: (inadequate because it is all IP traffic not just multicast)
access-list 7 permit any
Command output from Fails:
sho policy-map int g3/9 detailed
GigabitEthernet3/9
   Service-policy input: MARK_INBOUND_IPTV
    class-map: IPTV (match-all)
      Match: access-group 4
      set dscp 32:
      Earl in slot 5 :
        Traffic:        Total bytes          30-s bytes          peak bytes       5-min avg bps            peak bps
        Offered                   0                   0                   0                   0                   0
        Agg-fwd                   0                   0                   0                   0                   0
        Exceed                    0                   0                   0                   0                   0
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      30 second offered rate 0000 bps, drop rate 0000 bps
      Match: any
        0 packets, 0 bytes
        30 second rate 0 bps
sho policy-map int g3/9 input
GigabitEthernet3/9
Service-policy input: MARK_INBOUND_IPTV
    class-map: IPTV (match-all)
      Match: access-group 4
      set dscp 32:
      Earl in slot 5 :
        0 bytes
        30 second offered rate 0 bps
        aggregate-forwarded 0 bytes
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      30 second offered rate 0000 bps, drop rate 0000 bps
      Match: any
        0 packets, 0 bytes
        30 second rate 0 bps

I found that matching on the destination port number works as well:
access-list 104 permit udp any any eq 8208
sho policy-map int g3/9 input
GigabitEthernet3/9
Service-policy input: MARK_INBOUND_IPTV
    class-map: IPTV (match-all)
      Match: access-group 104
      set dscp 32:
      Earl in slot 5 :
        64144752 bytes
        30 second offered rate 3980472 bps
        aggregate-forwarded 64144752 bytes
    Class-map: class-default (match-any)
      0 packets, 0 bytes
      30 second offered rate 0000 bps, drop rate 0000 bps
      Match: any
        0 packets, 0 bytes
        30 second rate 0 bps
I'd really like to match on all multicast though. The destination IP or MAC makes the most sense but they fail.

Determination of QOS for IDOC messages

Hi,
sending IDOC from SAP to XI, and then to an external system using a JDBC adapter, the QOS for messages is automatically set to EO: anyone knows if it's possible to change this parameter (I need EOIO)? Where can I find documentation about setting/changing QOS?
Thanks for any suggestion.
Simona

I had the same scenario as Simona and at the end it turned out to be pretty simple (if WAS >= 6.40). On the sender system (SAP ERP) in partner profiles -> in the outbound parameters for the message type, you need to check Queue Processing parameter. When you do this an aditionalfield will apear: Rule name. This determines which rule will be used as QueueID. Rules are customized in WE85 where you can assign your own function modules to custom rule names.
Once I assigned appropriate rule (for test I used FIRST_16_OF_MESTYP) xml message was automaticaly set to
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
and the message got the QueueID XBQO* (in SXMB_ADMIN).
Again, if WAS is WAS >= 6.40 you don't need to set up IDXQUEUE table.
Regards,
Elvis

QoS for CEM traffic

Similar Messages

Maybe you are looking for