Cisco MWR 2941 Installation Manual Page 191
- Page / 710
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
-191
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 pim rp-address
Usage Guidelines In the Cisco IOS implementation of PIM, each multicast group individually operates in one of the
following modes: dense mode, sparse mode, or sparse-dense mode. Groups in sparse mode (PIM-SM)
use RPs to connect sources and receivers. All routers in a PIM domain need to have a consistent
configuration for the mode and RP addresses of the multicast groups.
The Cisco IOS software learns the mode and RP addresses of multicast groups through the following
three mechanisms: static group-to-RP mapping configurations, Auto-RP, and bootstrap router (BSR). By
default, groups will operate in dense mode. No commands explicitly define groups to operate in dense
mode.
Use the ip pim rp-address command to statically define the RP address for PIM-SM or bidir-PIM
groups (an ip pim rp-address command configuration is referred to as a static group-to-RP mapping).
You can configure a single RP for more than one group using an access list. If no access list is specified,
the static RP will map to all multicast groups, 224/4.
You can configure multiple RPs, but only one RP per group range.
If multiple ip pim rp-address commands are configured, the following rules apply:
• Highest RP IP address selected regardless of reachability: If a multicast group is matched by the
access list of more than one configured ip pim rp-address command, then the RP for the group is
determined by the RP with the highest RP address configured.
• One RP address per command: If multiple ip pim rp-address commands are configured, each static
group-to-RP mapping must be configured with a unique RP address (if not, it will be
overwritten).This restriction also means that only one RP address can be used to provide RP
functions for either sparse mode or bidirectional mode groups. If you want to configure static
group-to-RP mappings for both bidirectional and sparse mode, the RP addresses must be unique for
each mode.
• One access list per command: If multiple ip pim rp-address commands are configured, only one
access list can be configured per static group-to-RP mapping. An access list cannot be reused with
other static group-to-RP mappings configured on a router.
If dynamic and static group-to-RP mappings are used together, the following rule applies to a multicast
group: Dynamic group-to-RP mappings take precedence over static group-to-RP mappings—unless the
override keyword is used.
Examples The following example shows how to set the PIM RP address to 192.168.0.1 for all multicast groups
(224/4) and defines all groups to operate in sparse mode:
ip pim rp-address 192.168.0.1
Note The RP address used for static group-to-RP mappings must be unique. You cannot use the same RP
address for both bidir-PIM and PIM-SM groups.
12.2SX This command is supported in the Cisco IOS Release 12.2SX train. Support in a
specific 12.2SX release of this train depends on your feature set, platform, and
platform hardware.
12.4(20)MR This command was incorporated into Cisco IOS Release 12.4(20)MR.
12.2(33)MRA This command was integrated into Cisco IOS Release 12.2(33)MRA.
15.0(1)MR This command was integrated into Cisco IOS Release 15.0(1)MR.
Release Modification
- 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.114 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals