Cisco MWR 2941 Installation Manual Page 193
- Page / 710
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
-193
Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Command Reference, Cisco IOS Release 15.1(3)MR
OL-26895-01
Chapter Cisco MWR 2941 Router Command Reference, Release 15.1(3)MR
ip rtp header-compression
Usage Guidelines You can compress IP/User Datagram Protocol (UDP)/RTP headers to reduce the size of your packets.
Compressing headers is especially useful for RTP because RTP payload size can be as small as 20 bytes,
and the uncompressed header is 40 bytes.
ietf-format Keyword
The ietf-format keyword indicates that the IETF format of header compression will be used. For HDLC
interfaces, the ietf-format keyword compresses only UDP packets. For PPP interfaces, when the
ietf-format keyword is specified, TCP header compression is also enabled. For this reason, the ip tcp
header-compression command appears in the output of the show running-config command. Because
both RTP header compression and TCP header compression are enabled, both UDP packets and TCP
packets are compressed.
Note The Cisco MWR 2941 supports UDP header-compression in IEFT format only.
With the ietf-format keyword, any even destination port number higher than 1024 can be used. Valid
RTP packets that meet the criteria (that is, the port number is even and is higher than 1024) are
compressed using the compressed RTP packet format. Otherwise, packets are compressed using the
less-efficient compressed non-TCP packet format.
Note The header compression format (in this case, IETF) must be the same at both ends of the network. That
is, if you specify the ietf-format keyword on the local router, you must also specify the ietf-format
keyword on the remote router.
Support for Distributed IPHC on Multilink Interfaces
You can use the configure distributed IPHC (dIPHC) on a multilink interface for improved Multilink
Point-to-Point Protocol (MLPPP) performance.
Distributed IP Header Compression (dIPHC) allows the Cisco MWR 2941 to compress IP packet headers
for more efficient use of bandwidth. Release 3.5 improves dIPHC performance by shifting processing
from the main CPU to the network processor.
When using the ip rtp header-compression ietf-format command for dIPHC on a multilink interface,
note the following:
• The Cisco MWR 2941 supports for UDP traffic only.
• The Cisco MWR 2941 supports up to 300 dIPHC sessions over 3 multilinks.
• The Cisco MWR 2941 supports only the IEFT format of IPHC.
• The Cisco MWR 2941 supports dIPHC only for UDP traffic.
• After enabling dIPHC on an interface, ensure that you “flap” the interface by using the shutdown
and no shutdown commands in interface configuration mode for the configuration to take effect.
• If a QoS policy is attached to the multilink interface on which IPHC has been enable, ensure that
you configure the platform header-compression match access-group command in interface
configuration mode to apply an extended named Access Control List (ACL) of static flows (source
IP address, destination IP address, and destination port) to compress using IPHC.
You must configure the matching ACL as an extended named access-list and add the static flow
configuration to a Multilink interface that is in an UP state and on which the ip rtp
header-compression command is configured.
- Release 15.1(3)MR 1
- Configuring a Policy Map 14
- Restrictions 15
- Policy Map Configuration Mode 27
- Class Characteristics 27
- Predefined Default Class 27
- Tail Drop or WRED 27
- Fragments 28
- If ID Choice Is Anything Else 72
- Unique Device Identifier 73
- Cisco HWIC-4SHDSL 88
- SNAP Encapsulation Example 96
- OL-26895-01 105
- • n393—1 to 10. Default is 4 133
- • proxy-register 187
- • list access-list 187
- • route-map map-name 187
- Support for Serial Lines 194
- Syntax Description 195
- Keepalive Time Interval 203
- Line Failure 203
- Dropped Packets 203
- DSCP Values 226
- Match Packets on DSCP Values 227
- • match access-group 231
- • match input-interface 231
- • match mpls experimental 231
- • match protocol 231
- Precedence Values and Names 233
- IPv4-Specific Traffic Match 233
- IPv6-Specific Traffic Match 234
- Support Restrictions 237
- ATM Mode Example 247
- CAS Mode Example 247
- Router(config)# no mpls ip 250
- Release 12.2(33)SRB 259
- • QL-PRC 275
- • QL-SSU-A 275
- • QL-SSU-B 275
- • QL-SEC 275
- • QL-DNU 275
- All Supported Platforms 303
- Hierarchical Policy Maps 304
- How Bandwidth Is Calculated 305
- • conform-action is transmit 311
- • exceed-action is drop 311
- • violate-action is drop 311
- Token Buckets 314
- Updating Token Buckets 315
- Marking Traffic 315
- Two-Rate Policing 316
- Syntax for Percent 318
- Command Application 332
- • Data encapsulation type 334
- • Control protocol 334
- • 4—1 packet every 16 seconds 336
- • 3—1 packet every 8 seconds 336
- • 2—1 packet every 4 seconds 336
- • 1—1 packet every 2 seconds 336
- • 0—1 packet every second 336
- Command Description 341
- Router(config)# exit 358
- Weighted Fair Queueing 366
- • Control network loops 376
- • Handle link failures 376
- • Improve convergence time 376
- the following adapters: the 409
- to specify the “from-field” 412
- • EF (expedited forwarding) 420
- Precedence Value and Queueing 421
- 2. ip tos reflect 429
- 3. ip tos tos-value 429
- Command Compatibility 440
- Bit Settings 440
- Precedence Value 441
- Committed Information Rate 449
- IMA Group 456
- M-PAIR Group 456
- 1-PAIR and 2-PAIR Group 456
- DSL Group with 1 Pair 458
- DSL Group with 2 Pairs 458
- DSL Group with 3 Pairs 458
- DSL Group with 4 Pairs 458
- • Interface name and number 471
- • Identifier (group ID) 475
- ADSL: Example 490
- • Domain name 495
- • Domain index 495
- • Domain level 495
- Field Description 504
- Reliability Errors 524
- Protocol Errors 524
- UNI Id Identifier of the UNI 526
- EVC Id Identifier of the EVC 526
- • Local and remote OAM mode 528
- • Remote platform identity 528
- • Remote loopback events 531
- Traffic Policing: Example 583
- Tunnel Marking: Example 588
- ATM Shared Port Adapter 590
- (continued) 595
- Policing 597
- Policing and Shaping 599
- Traffic Shaping: Example 600
- UDP encapsulation 613
- • priority is 128 647
- Router(config-if)# 648
- • Up to 2 queues 670
- • Up to 2 interfaces 670
- • 1 queue and 1 interface 670
- Router(config-if)# switchport 672
- GRE Tunneling Example 693
- Peak Value 705
- Average Value 705
- Burst Value 705
- Activating the Primary Member 709
- Activating the Backup Member: 709
Related products and manuals for Networking Cisco MWR 2941
Networking Cisco WMP110 User Manual
(2 pages)
(2 pages)
Networking Cisco Ex SERIES User Manual
(15 pages)
(15 pages)
Networking Cisco Soho series User Manual
(4 pages)
(4 pages)
Networking Cisco AS2509-RJ User Manual
(26 pages)
(26 pages)
Networking Cisco WKPC54G User Manual
(2 pages)
(2 pages)
Networking Cisco Dial NMS User Manual
(8 pages)
(8 pages)
Networking Cisco DMA2100 User Manual
(3 pages)
(3 pages)
(2 pages)© 2020, manymanuals.com. All rights reserved. | 0.071 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals