Multicast – IPv6 PIM

clear ipv6 pim counters

To reset the Protocol Independent Multicast (PIM) traffic counters, use the clear ipv6 pim counters command in privileged EXEC mode.

Syntax

clear ipv6 pim counters

Parameters

N/A.

Command Mode

Privileged EXEC mode

User Guidelines

Using the clear ipv6 pim counters command will reset all PIM traffic counters.

Example

The following example resets the PIM traffic counters:

switchxxxxxx# clear ipv6 pim counters

ipv6 pim

To enable IPv6 Protocol Independent Multicast (PIM) on an interface, use the ipv6 pim command in interface configuration mode. To disable PIM on the interface, use the no form of this command.

Syntax

ipv6 pim no ipv6 pim

Parameters

This command has no arguments or keywords.

Default Configuration Disabled

Command Mode

Interface Configuration mode

User Guidelines

After a user has enabled the ipv6 multicast-routing command, PIM is enabled to run on every interface. Because PIM is enabled on every interface by default, use the no form of the ipv6 pim command to disable PIM on a specified interface.

Example

The following example turns off PIM on VLAN 100:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# no ipv6 pim
switchxxxxxx(config-if)# exit

Verge Documentation – English//IPv6 PIM Commands

Angora Networks Product Support Portal

ipv6 pim accept-register

To configure a candidate rendezvous point (RP) router to filter Protocol Independent Multicast (PIM) register messages, use the ipv6 pim accept-register command in global configuration mode. To disable this function, use the no form of this command.

Syntax

ipv6 pim accept-register list access-list no ipv6 pim accept-register list

Parameters

n acces-list—Defines the IPv6 pair access list name.

Default Configuration The command is disabled.

Command Mode

Global Configuration mode

User Guidelines

Use this command to prevent unauthorized sources from registering with the RP. If an unauthorized source sends a register message to the RP, the RP will immediately send back a register-stop message.

Example

The following example shows how to deny register packets for source addresses 2001:1:1::/48 and 2001:1:10::1 sending to the FF07:1:1:1::/48 group range. All other PIM register messages not matching the pair access list are permitted. These statements should be configured on all candidate RPs because candidate RPs will receive PIM registers from first hop routers:

switchxxxxxx(config)# ip6 pim accept-register list no-range
switchxxxxxx(config)# ip6 access-list pair no-range deny 2001:1:1::/48 FF07:1:1:1::/48
switchxxxxxx(config)# ip6 access-list pair no-range deny 2001:1:10::1 FF07:1:1:1::/48
switchxxxxxx(config)# ip6 access-list pair no-range permit any any

ipv6 pim bsr-border

To configure a border for all bootstrap message (BSMs) on a specified interface, use the ipv6 pim bsr-border command in interface configuration mode. To remove the border, use the no form of this command

Syntax

  • ipv6 pim bsr-border
  • no ipv6 pim bsr-border

Parameters

N/A.

Default Configuration No border is configured.

Command Mode

Interface Configuration mode

User Guidelines

The ipv6 pim bsr-border command is used to configure a border. The command filters incoming or outgoing BSMs, preventing the BSMs from being forwarded or accepted on the interface on which the ipv6 pim bsr-border command is configured.

When this command is configured on an interface, no Protocol Independent Multicast (PIM) Version 2 BSR messages will be sent or received through the interface. Configure an interface bordering another PIM domain with this command to avoid BSR messages from being exchanged between the two domains. BSR messages should not be exchanged between different domains, because routers in one domain may elect rendezvous points (RPs) in the other domain, resulting in protocol malfunction or loss of isolation between the domains.

Note. This command does not set up multicast boundaries. It sets up only a PIM domain BSR message border.

Example

The following example configures a BSR border on VLAN 100:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# ipv6 pim bsr-border
switchxxxxxx(config-if)# exit

ipv6 pim bsr-candidate

To configure a router to be a candidate bootstrap router (BSR), use the ipv6 pim bsr-candidate  command in global configuration mode. To remove this router as a candidate BSR, use the no form of this command.

Syntax

ipv6 pim bsr-candidate ipv6-address [hash-mask-length] [priority priority-value] no ipv6 pim bsr-candidate

Parameters

  • ipv6-address—The IPv6 address of the router to be configured as a candidate BSR. This argument must be in the form documented in RFC 4291 where the address is specified in hexadecimal using 16-bit values between colons.
  • hash-mask-length—Length of a mask (128 bits maximum) that is to be ANDed with the group address before the hash function is called. All groups with the same seed hash (correspond) to the same RP. For example, if this value is 126, only the first 126 bits of the group addresses matter. This fact allows you to get one RP for multiple groups. The default value is 126.
  • priority—Priority of the candidate BSR.
  • priority-value—Integer from 0 through 192. The BSR with the larger priority is preferred. If the priority values are the same, the router with the larger IPv6 address is the BSR. The default value is 0.

Default Configuration

Router is not enabled as a BSR.

Command Mode

Global Configuration mode

User Guidelines

The ipv6 pim bsr-candidate command is used to configure a router as a candidate BSR. When a router is configured, it will participate in BSR election. If elected BSR, this router will periodically originate BSR messages advertising the group-to-RP mappings it has learned through candidate-RP-advertisement messages.

Example

The following example configures the router with the IPv6 address 2001:0DB8:3000:3000::42 as the candidate BSR, with a hash mask length of 124 and a priority of 10:

switchxxxxxx(config)# ipv6 pim bsr-candidate 2001:0DB8:3000:3000::42 124 priority 10

ipv6 pim dr-priority

To configure the designated router (DR) priority on a Protocol Independent Multicast (PIM) router, use the ipv6 pim dr-priority command in interface configuration mode. To restore the default value, use the no form of this command.

Syntax

ipv6 pim dr-priority value no ipv6 pim dr-priority

Parameters

n value—An integer value to represent DR priority. Value range is from 0 to 4294967294.

Default Configuration

Default value is 1.

Command Mode

Interface Configuration mode

User Guidelines

The ipv6 pim dr-priority command configures the neighbor priority used for PIM DR election. The router with the highest DR priority on an interface becomes the PIM DR. If several routers have the same priority, then the router with the highest IPv6 address on the interface becomes the DR.

If a router does not include the DR priority option in its hello messages, then the router is considered to be the highest-priority router and becomes the DR. If several routers do not include the DR priority option in their hello messages, then the router with the highest IPv6 address becomes the DR.

Example

The following example configures the router to use DR priority 3:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# ipv6 pim dr-priority 3
switchxxxxxx(config-if)# exit

ipv6 pim hello-interval

To configure the frequency of Protocol Independent Multicast (PIM) hello messages on an interface, use the ipv6 pim hello-interval command in interface configuration mode. To return to the default interval, use the no form of this command.

Syntax

ipv6 pim hello-interval seconds no ipv6 pim hello-interval

Parameters

n seconds—Interval, in seconds, at which PIM hello messages are sent. The range is from 1 to 18000.

Default Configuration

Hello messages are sent at 30-second intervals with small random jitter.

Command Mode

Interface Configuration mode

User Guidelines

Periodic hello messages are sent out at 30-second intervals with a small jitter. The ipv6 pim hello-interval command allows users to set a periodic interval.

Example

The following example sets the PIM hello message interval to 45 seconds:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# ipv6 pim hello-interval 45
switchxxxxxx(config-if)# exit

ipv6 pim join-prune-interval

To configure periodic join and prune announcement intervals for a specified interface, use the ipv6 pim join-prune-interval command in interface configuration mode. To return to the default value, use the no form of the command.

Syntax

ipv6 pim join-prune-interval seconds no ipv6 pim join-prune-interval

Parameters

n seconds—The join and prune announcement intervals, in number of seconds. The range is from 1 to 18000.

Default Configuration

The default is 60 seconds.

Command Mode

Interface Configuration mode

User Guidelines

The ipv6 pim join-prune-interval command allows users to set a periodic interval. The configured PIM join/prune interval also determines the join/prune hold time used by a PIM router as follows:

                         3.5 * join/prune interval

Example

The following example sets the join and prune announcement intervals to 75 seconds:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# ipv6 pim join-prune-interval 75
switchxxxxxx(config-if)# exit

ipv6 pim neighbor-filter

To filter Protocol Independent Multicast (PIM) neighbor messages from specific IPv6 addresses, use the ipv6 pim neighbor-filter command in the interface configuration mode. To return to the router default, use the no form of this command.

Syntax

ipv6 pim neighbor-filter access-list no ipv6 pim neighbor-filter

Parameters

n access-list—Name of an IPv6 standard access list that denies PIM hello packets from a source.

The name may contain maximum  characters.

Default Configuration

PIM neighbor messages are not filtered.

Command Mode

Interface Configuration mode

User Guidelines

The ipv6 pim neighbor-filter command is used to prevent unauthorized routers on the LAN from becoming PIM neighbors. Hello messages from addresses specified in this command are ignored.

Example

The following example causes PIM to ignore all hello messages from IPv6 address FE80::A8BB:CCFF:FE03:7200:

switchxxxxxx(config)# interface vlan 100
switchxxxxxx(config-if)# ipv6 pim neighbor-filter nbr_filter_acl
switchxxxxxx(config-if)# exit
switchxxxxxx(config)# ipv6 access-list deny nbr_filter_acl FE80::A8BB:CCFF:FE03:7200
switchxxxxxx(config)# ipv6 access-list permit nbr_filter_acl any

ipv6 pim rp-address

To configure the address of a Protocol Independent Multicast (PIM) rendezvous point (RP) for a particular group range, use the ipv6 pim rp-address command in global configuration mode. To remove an RP address, use the no form of this command.

Syntax

ipv6 pim rp-address rp-address [group-access-list] no ipv6 pim rp-address rp-address

Parameters

  • rp-address—The IPv6 address of a router to be a PIM RP. The ipv6-address argument must be in the form documented in RFC 4291 where the address is specified in hexadecimal using 16-bit values between colons.
  • group-access-list—Name of an IPv6 standard access list that defines for which multicast groups the RP should be used. The name may contain maximum 32 characters.

If the access list contains any group address ranges that overlap the assigned source-specific multicast (SSM) group address range, a warning message is displayed, and the overlapping ranges are ignored. If no access list is specified, the specified RP is used for all valid multicast non-SSM address ranges.

To support embedded RP, the router configured as the RP must use a configured access list that permits the embedded RP group ranges derived from the embedded RP address.

Default Configuration

No PIM RPs are preconfigured.

Embedded RP support is enabled by default when IPv6 PIM is enabled

Command Mode

Global Configuration mode

User Guidelines

Groups in sparse mode need to have the IP address of one router to operate as the RP for the group. All routers in a PIM domain need to have a consistent configuration for the mode and RP addresses of the multicast groups.

The RP address is used by first-hop routers to send register packets on behalf of source multicast hosts. The RP address is also used by routers on behalf of multicast hosts that want to become members of a group. These routers send join and prune messages to the RP.

If the optional group-access-list argument is not specified, the RP is applied to the entire routable IPv6 multicast group range, excluding SSM (FF3E::/32). If the group-access-list argument is specified, the IPv6 address is the RP address for the group range specified in the group-access-list argument.

You can configure switch to use a single RP for more than one group. The conditions specified by the access list determine which groups the RP can be used for. If no access list is configured, the RP is used for all groups.

A PIM router can use multiple RPs, but only one per group.

Static definitions for the group mode and RP address of the ipv6 pim rp-address command may be used together with dynamically learned group mode and RP address mapping through BSR. The mappings statistically defined by the ipv6 pim rp-address command take precedences over mappings learned through BSR.

Static definitions for the group mode and RP address of the ipv6 pim rp-address command may be used together with enabling of embedded RP support. The mappings statistically defined by the ipv6 pim rp-address command take precedences over embedded RP support.

Example

Example 1. The following example shows how to set the PIM RP address to 2001::10:10 for all multicast groups:

switchxxxxxx(config)# ipv6 pim rp-address 2001::10:10

Example 2. The following example sets the PIM RP address to 2001::10:10 for the multicast group FF04::/64 only:

switchxxxxxx(config)# ipv6 access-list acc-grp-1 permit ff04::/64
switchxxxxxx(config)# ipv6 pim rp-address 2001::10:10 acc-grp-1

Example 3. The following example shows how to configure a group access list that permits the embedded RP ranges derived from the IPv6 RP address 2001:0DB8:2::2:

switchxxxxxx(config)# ipv6 pim rp-address 2001:0DB8:2::2 embd-ranges
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff73:240:2:2:2::/96
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff74:240:2:2:2::/96
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff75:240:2:2:2::/96
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff76:240:2:2:2::/96
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff77:240:2:2:2::/96
switchxxxxxx(config)# ipv6 access-list embd-ranges permit ff78:240:2:2:2::/96

ipv6 pim rp-candidate

To configure the candidate rendezvous point (RP) to send Protocol Independent Multicast (PIM) RP advertisements to the bootstrap router (BSR), use the ipv6 pim rp-candidate command in global configuration mode. To disable PIM RP advertisements to the BSR, use the no form of this command.

Syntax

ipv6 pim rp-candidate ipv6-address [group-list access-list-name] [priority priority-value] [interval seconds]

no ipv6 pim rp-candidate ipv6-address

Parameters

  • ipv6-address—The IPv6 address of the router to be advertised as the candidate RP (C-RP). This argument must be in the form documented in RFC 4291 where the address is specified in hexadecimal using 16-bit values between colons.
  • group-list—List of group prefixes. If no access list is specified, all valid multicast nonsource-specific multicast (SSM) address ranges are advertised in association with the specified RP address.
  • access-list-name—Name of the IPv6 standard access list containing group prefixes that will be advertised in association with the RP address. If the access list contains any group address ranges that overlap the assigned SSM group address range, a warning message is displayed, and the overlapping address ranges are ignored.
  • priority—Priority of the candidate BSR.
  • priority-value—Integer from 0 through 192. The RP with the higher priority is preferred. If the priority values are the same, the router with the higher IPv6 address is the RP. The default value is 192.
  • interval—Configures the C-RP advertisement interval. The range is from 1 to 16383 seconds. The default value is 60 seconds.
  • seconds—Advertisement interval in number of seconds.

Default Configuration

Router is not enabled as a candidate RP.

Command Mode

Global Configuration mode

User Guidelines

Use the ipv6 pim rp-candidate command to send PIM RP advertisements to the BSR.

The group prefixes defined by the access-list-name argument will also be advertised in association with the RP address. If a group prefix in the access list is denied, it will not be included in the C-RP advertisement.

If the priority priority-value keyword and argument are specified, then the router will announce itself to be a candidate RP with the specified priority.

Example

Example 1. The following example configures the router with the IPv6 address

2001:0DB8:3000:3000::42 to be advertised as the candidate RP, with a priority of 0:

switchxxxxxx(config)# ipv6 pim rp-candidate 2001:0DB8:3000:3000::42 priority 0

Example 2. The following example configures the router with the IPv6 address 2001:0DB8:1:1:1 as the candidate RP for the group ranges specified in the access list named list1:

switchxxxxxx(config)# ipv6 pim rp-candidate 2001:0DB8:1:1:1 group-list list1

ipv6 pim rp-embedded

To enable embedded rendezvous point (RP) support in IPv6 Protocol Independent Multicast (PIM), use the ipv6 pim rp-embedded command in global configuration mode. To disable embedded RP support, use the no form of this command.

Syntax

ipv6 pim rp-embedded no ipv6 pim rp-embedded

Parameters

This command has no arguments or keywords.

Default Configuration

Embedded RP support is enabled by default.

Command Mode

Global Configuration mode

User Guidelines

Because embedded RP support is enabled by default, users will generally use the no form of this command to turn off embedded RP support (see RFC 3956 about details).

The ipv6 pim rp-embedded command applies only to the embedded RP group addresses defined by RFC3956. When the feature is enabled, the IP Multicast router parses a embedded RP group address and extracts the RP to be used from the group address.

Example

The following example disables embedded RP support in IPv6 PIM:

switchxxxxxx(config)# no ipv6 pim rp-embedded

ipv6 pim ssm

To define the Source Specific Multicast (SSM) range of IP multicast addresses, use the ipv6 pim ssm command in global configuration mode. To disable the SSM range, use the no form of this command.

Syntax

ipv6 pim ssm {default | range access-list} no ipv6 pim ssm

Parameters

  • default—Defines the SSM range access list to FF3x::/32 (see rfc4607).
  • range access-list—Specifies the standard IPv6 access list name defining the SSM range.

Default Configuration

The command is disabled.

Command Mode

Global Configuration mode

User Guidelines

To define a few ranges, configure the ipv6 pim ssm command a few times.

Use the no ipv6 pim ssm command without the keywords to remove all defined ranges.

Example

The following example shows how to configure SSM service for the default IPv6 address range and the IPv6 address ranges defined by access lists list1 and list2 :

switchxxxxxx(config)# ipv6 access-list list1 permit FF7E:1220:2001:DB8::/64
switchxxxxxx(config)# ipv6 access-list list1 deny FF7E:1220:2001:DB1::1
switchxxxxxx(config)# ipv6 access-list list1 permit FF7E:1220:2001:DB1::/64
switchxxxxxx(config)# ipv6 pim ssm range list1

show ipv6 pim bsr

To display information related to Protocol Independent Multicast (PIM) bootstrap router (BSR) protocol processing, use the show ipv6 pim bsr command in user EXEC or privileged EXEC mode.

Syntax

show ipv6 pim bsr {election | rp-cache | candidate-rp}

Parameters

  • election—Displays BSR state, BSR election, and bootstrap message (BSM)-related timers.
  • rp-cache—Displays candidate rendezvous point (C-RP) cache learned from unicast C-RP announcements on the elected BSR.
  • candidate-rp—Displays C-RP state on routers that are configured as C-RPs.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

Use the show ipv6 pim bsr command to display details of the BSR election-state machine, C-RP advertisement state machine, and the C-RP cache. Information on the C-RP cache is displayed only on the elected BSR router, and information on the C-RP state machine is displayed only on a router configured as a C-RP.

Example

Example 1. The following example displays BSM election information:

switchxxxxxx# show ipv6 pim bsr election
 
PIMv2 BSR information
 
BSR Election Information
 
Scope Range List: ff00::/8
 
This system is the Bootstrap Router (BSR)
 
BSR Address: 60::1:1:4
 
Uptime: 00:11:55, BSR Priority: 0, Hash mask length: 126
 
RPF: FE80::A8BB:CCFF:FE03:C400,VLAN 10
 
BS Timer: 00:00:07
 
This system is candidate BSR
 
Candidate BSR address: 60::1:1:4, priority: 0, hash mask length: 126

show ipv6 pim counters

To display the Protocol Independent Multicast (PIM) counters, use the show ipv6 pim counters command in user EXEC or privileged EXEC mode.

Syntax

show ipv6 pim counters

Parameters

N/A.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

Use the show ipv6 pim counters command to check if the expected number of PIM protocol messages have been received and sent.

Example

The following example shows the number of PIM protocol messages received and sent:

switchxxxxxx# show ipv6 pim counters iPIM Traffic Counters
 
Elapsed time since counters cleared: 00:05:29
 
Received    Sent
 
Valid PIM Packets            22      22
 
Hello                        22      22
 
Join-Prune                    0       0
 
Register                      0       0
 
Register Stop                 0       0
 
Assert                        0       0
 
Bootstrap                     0       0
 
Errors:
 
Send Errors                                0
 
Bad Checksums                              0
 
Packets Received on PIM-disabled Interface 0
 
Packets Received with Unknown PIM Version  0

show ipv6 pim group-map

To display an IPv6 Protocol Independent Multicast (PIM) group mapping table, use the show ipv6 pim group-map command in user EXEC or privileged EXEC mode.

Syntax show ipv6 pim group-map [group-address]

Parameters

n group-address—IPv6 address of the multicast group.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

Use the show ipv6 pim group-map command without the group-address argument to display information about all groups.

Example

The following example displays information about all groups:

switchxxxxxx# show ipv6 pim group-map
 
Group(s) FF32::/32
 
SM RP 20::1:2:1 (?)
 
Info source: Local
 
Group(s) FF33::/32
 
SM RP 20::1:1:1 (?)
 
Info source: Static Group(s) FF34::/32
 
SM RP 10::1:1:3 (?)
 
Info source: From BSR 10.10.0.3 (?), Priority: 192
 
Uptime:00:01:26, expires:00:00:34
 
Group(s) FF35::/32
 
SM RP 15::1:1:5 (?)
 
Info source: From BSR 10.10.0.5 (mcast1.aaaa.com), Priority: 192
 
Uptime:00:00:52, expires:00:00:37
 
Group(s) FF3E::/32
 
SMM
 
Group(s) FF7E::1220:2001:DB8::/64
 
SM RP 2001:DB8::12 (?)
 
Info source: Embedded-RP

show ipv6 pim interface

To display information about interfaces configured for Protocol Independent Multicast (PIM), use the show ipv6 pim interface command in user EXEC or privileged EXEC mode.

Syntax

show ipv6 pim interface [state-on] [state-off] [interface-id]

Parameters

  • state-on—Displays interfaces with PIM enabled.
  • state-off—Displays interfaces with PIM disabled.
  • interface-id—Interface identifier.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

The show ipv6 pim interface command is used to check if PIM is enabled on an interface, the number of neighbors, and the designated router (DR) on the interface.

Example

Example 1. The following example displays only PIM state on all interfaces:

switchxxxxxx# show ipv6 pim interface
 
IP Forwarding is enabled
 
IP Multicast Routing is enabled PIM is enabled rp-embedded: enabled
 
SSM IP ranges:
 
default   access list: list1   access list: list2
 
Interface  Address                   PIM vlan 1     FE80::208:20FF:FE08:D7FF  off vlan 100   FE80::208:20FF:FE08:D7FF  on vlan 102   FE80::208:20FF:FE08:D7FF  on

Example 2. The following is sample output from the show ipv6 pim interface command using the state-on keyword when IP Multicast Routing is disabled:

switchxxxxxx# show ip pim interface state-on
 
IP Forwarding is enabled
 
IP Multicast Routing is disabled PIM is disabled
 
SSM IP ranges:
 
default   access list: list1   access list: list2
 
Interface Status    Nbr     Hello    Join-Prune  DR                     Count   Intvl    Intvl       Prior vlan 1    disabled
 
Address: FE80::208:20FF:FE08:D7FF    DR:
 
Neighbor Filter List: filt vlan 100  disabled
 
Address: FE80::208:20FF:FE08:D7FF    DR:
 
Neighbor Filter List: nbr-filter vlan 102  enabled
 
Address: FE80::208:20FF:FE08:D7FF    DR:
 
Neighbor Filter List:
 
vlan 103  enabled    Address:
 
DR:
 
Neighbor Filter List: filter1

Example 3. The following is sample output from the show ipv6 pim interface command using the state-on keyword:

switchxxxxxx# show ip pim interface state-on
 
IP Forwarding is enabled
 
IP Multicast Routing is enabled
 
PIM is enabled SSM IP ranges:
 
default   access list: list1   access list: list2
 
Interface Statuse  Nbr     Hello    Join-Prune  DR                    Count   Intvl    Intvl       Prior vlan 100  enabled      0      30      60          1
 
Address: FE80::208:20FF:FE08:D7FF
 
DR: this system
 
Neighbor Filter List: nbr-filter vlan 102  enabled      1      30      60          1
 
Address: FE80::208:20FF:FE08:D7FF
 
DR: FE80::250:E2FF:FE8B:4C80    Neighbor Filter List:
 
vlan 103  enabled    Address:
 
DR:
 
Neighbor Filter List: filter1

Example 4. The following is sample output from the show ipv6 pim interface command using the interface-id argument:

switchxxxxxx# show ip pim interface vlan 100
 
IP Forwarding is enabled
 
IP Multicast Routing is enabled
 
PIM is enabled SSM IP ranges:
 
default   access list: list1   access list: list2
 
Interface Statuse  Nbr     Hello    Join-Prune  DR
 
Count   Intvl    Intvl       Prior
 
vlan 100  enabled      0      30      60          1
 
Address: FE80::208:20FF:FE08:D7FF
 
DR: this system
 
Neighbor Filter List: nbr-filter

show ipv6 pim neighbor

To display the Protocol Independent Multicast (PIM) neighbors discovered by the switch, use the show ipv6 pim neighbor command in user EXEC or privileged EXEC mode.

Syntax

show ipv6 pim neighbor [detail] [interface-id]

Parameters

  • detail—Displays the additional addresses of the neighbors learned, if any, through the Address List (type 24) Hello option.
  • interface-id—Interface identifier.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

The show ipv6 pim neighbor command displays which routers on the LAN are configured for PIM.

Example

The following is sample output from the show ipv6 pim neighbor command using the detail keyword to identify the additional addresses of the neighbors learned through the routable address hello option:

switchxxxxxx# show ipv6 pim neighbor detail
 
Neighbor Address(es)     Interface  Uptime   Expires  DR pri
 
FE80::A8BB:CCFF:FE00:401 vlan 100   01:34:16 00:01:16   1 60::1:1:3
 
FE80::A8BB:CCFF:FE00:501 vlan 140   01:34:15 00:01:18   1 60::1:1:4

show ipv6 pim rp mapping

To display active rendezvous points (RPs) that are cached with associated multicast routing entries, use the show ipv6 pim rp mapping command in user EXEC or privileged EXEC mode.

Syntax

show ipv6 pim rp mapping [rp–address]

Parameters

n rp-address—RP IPv6 address. This argument must be in the form documented in RFC 4291 where the address is specified in hexadecimal using 16-bit values between colons.

Command Mode User EXEC mode

Privileged EXEC mode

User Guidelines

Use the show ipv6 pim rp mapping command with the rp-address argument to display information about the given RP.

Use the show ipv6 pim rp mapping command without the rp-address argument to display information about all known RPs.

Example

The following example displays information about all known all RPs:

switchxxxxxx# show ipv6 pim rp mapping
 
This system is an RP
 
Register Acces List: list1
 
Group(s) FF32::/32
 
RP 20::1:2:1 (?)
 
Info source: Local
 
Uptime: 00:02:40
 
Group(s) FF33::/32
 
RP 20::1:1:1 (?)
 
Info source: Static
 
Uptime: 00:01:42
 
Group(s) FF34::/32
 
RP 10::1:1:3 (?)
 
Info source: From BSR 10.10.0.3 (?), Priority: 192
 
Uptime:00:01:26, expires:00:00:34
 
Group(s) FF35::/32
 
RP 15::1:1:5 (?)
 
Info source: From BSR 10.10.0.5 (mcast1.aaaa.com), Priority: 192
 
Uptime:00:00:52, expires:00:00:37
 
Group(s) FF7E::1220:2001:DB8::/64
 
RP 2001:DB8::12 (?)
 
Info source: Embedded-RP
 
Uptime:00:00:52

Was this article helpful?

Related Articles

Leave A Comment?