2.20. Show, Clear, and Tools Command Reference

This section provides an overview of the show, clear, debug and tools command reference.

Topics in this section include:

2.20.1. Command Hierarchies

Note:

For information on egress multicast group commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN.

2.20.1.1. Show Commands

show
— service
customer [customer-id] [site customer-site-name]
fdb-mac [ieee-address] [expiry]
id service-id
id service-id base
id service-id bgp [bgp-instance]
id service-id mac-notification
id service-id macsec
id service-id mrp
id service-id mvrp vlan vlan-id
id service-id mvrp vlan detail
id service-id provider-tunnel
id service-id sap base
id service-id sap mrp
id service-id sdp
id service-id vpls-group [vpls-group-id]
id service-id vpls-group vpls-group-id non-template-saps
isid-using [range-id]
l2-route-table [detail] [bgp-ad] [multi-homing] [bgp-vpls] [bgp-vpws] [all-routes]
oper-group [group-name]
oper-group [group-name] detail
oper-group [group-name] members [sap] [sdp] [site] [bgp-evpn]
oper-group [group-name] monitoring [sap] [sdp] [site] [mvrp]
pw-template [policy-id]
saii-type2-using global-id[:prefix[:ac-id]]
sap-using [msap] [dyn-script] [description]
sap-using [sap sap-id] [vlan-transaction | anti-spoof] [description]
sap-using {ingress | egress} atm-td-profile td-profile-id
sap-using {ingress | egress} filter any-filter-id
sap-using {ingress | egress} qos-policy qos-policy-id [msap]
sap-using etree
sdp sdp-id pw-port [pw-port-id] [statistics]
sdp [consistent | inconsistent | na] egressifs
sdp sdp-id keep-alive-history
sdp far-end ip-address keep-alive-history
sdp [sdp-id] [detail]
sdp far-end ip-address [detail]
sdp-group [group-name]
sdp-group-using [sdp-group]
sdp-using [sdp-id[:vc-id] | far-end ip-address]
service-name-using [detail]
service-using [epipe] [ies] [vpls] [vprn] [mirror] [b-vpls] [i-vpls] [m-vpls] [apipe] [fpipe] [ipipe] [sdp sdp-id] [customer customer-id]
system
bgp-route-distinguisher [vprn] [vpls] [epipe]
bgp-route-distinguisher ad-evi-rt-set
taii-type2-using global-id[:prefix[:ac-id]]
vpls-sap-template template-name
vpls-sap-template-using template-name
vpls-template template-name
vpls-template-using template-name
connection-profile-vlan [con-prof-id]
eth-tunnel {aps | status}
eth-tunnel tunnel-index [path path-index] [detail]

2.20.1.1.1. ETH-CFM Show Commands

show
association [ma-index] [detail]
cfm-stack-table [port [port-id [vlan vlan-id]] | sdp sdp-id[:vc-id]] [level level] [direction up | down]
cfm-stack-table port [{all-ports | all-sdps | all-virtuals}] [level level] [direction up | down]
cfm-stack-table port port-id [vlan qtag[.qtag]] [level level] [direction up | down]
cfm-stack-table sdp sdp-id[:vc-id] [level level] [direction up | down]
cfm-stack-table virtual service-id [level 0..7]
cfm-stack-table facility [{all-ports | all-lags | all-lag-ports | all-tunnel-meps | all-router-interfaces}] [level level] [direction up | down]
cfm-stack-table facility collect-lmm-stats
cfm-stack-table facility lag id [tunnel tunnel-id [level level] [direction up | down]
cfm-stack-table facility port id [level level] [direction up | down]
cfm-stack-table facility router-interface ip-int-name [level level] [direction up | down]
default-domain [bridge-identifier bridge-id vlan vlan-id]
domain [md-index] [association ma-index | all-associations] [detail]
lbm-svc-act-responder [domain md-index] [association ma-index] [mep mep-id]
mep mep-id domain md-index association ma-index [loopback] [linktrace] [eth-bandwidth-notification] [statistics]
mep mep-id domain md-index association ma-index remote-mepid mep-id | all-remote-mepids
mep mep-id domain md-index association ma-index eth-test-results [remote-peer mac-address]
mep mep-id domain md-index association ma-index one-way-delay-test [remote-peer mac-address]
mep mep-id domain md-index association ma-index two-way-delay-test [remote-peer mac-address]
mep mep-id domain md-index association ma-index two-way-slm-test [remote-peer mac-address]
mip
mip-instantiation [level level] [{sap sap-id | sdp sdp-id}]
eth-ring [status]
eth-ring [ring-index] hierarchy
eth-ring ring-index [path {a | b}]

2.20.1.1.2. PW-Port Show Commands

show
pw-port [pw-port-id] [detail]
pw-port sdp sdp-id
pw-port sdp none
pw-port sdp statistics

2.20.1.1.3. NGE Show Commands

show
encryption-keygroup keygroup-id [spi spi]

2.20.1.2. Clear Commands

clear
encryption-keygroup keygroup-id [spi spi]

2.20.1.3. Tools Perform Commands

The following commands are applicable to the 7750 SR and 7450 ESS.

tools
id service-id
pw
sdp sdp-id:vc-id [test-service-id service-id] [start]
eth
sap sap-id start mode [mac-swap] [mac ieee-address] [all]
sap sap-id stop
sdp sdp-id:vc-id start mode [mac-swap] [mac ieee-address] [all]
sdp sdp-id:vc-id stop
pw
sdp sdp-id:vc-id {start | stop}
— eth-ring
clear ring-index
force ring-index path {a | b}
manual ring-index path {a | b}

2.20.1.4. Tools Dump Commands

tools
dump
id service-id
loopback sap sap-id
loopback sdp sdp-id:vc-id
5.4. Configuring PIM with CLI

5.4. Configuring PIM with CLI

This section provides information to configure PIM using the command line interface.

5.4.1. PIM Configuration Overview

PIM is not enabled by default. When PIM is enabled, data is forwarded to network segments with active receivers that have explicitly requested the multicast group. When enabled, at least one interface must be specified in the PIM context as PIM is an interface function. Creating an interface enables PIM.

5.4.2. Basic PIM Configuration

Perform the following basic PIM configuration tasks:

  1. Enable PIM (required)
  2. Add interfaces so the protocol establishes adjacencies with the neighboring routers (required)
  3. Configure a way to calculate group-to-RP mapping (required) by either:
    1. Static group-to-RP mapping
    2. Enable Candidate RP/Bootstrap mechanism on some routers.
  4. Enable unicast routing protocols to learn routes towards the RP/source for reverse path forwarding (required)
  5. Add SSM ranges (optional)
  6. Enable Candidate BSR (optional)
  7. Enable Candidate RP (optional)
  8. Change hello interval (optional)
  9. Configure route policies (bootstrap-export, bootstrap-import, import join and register)

5.4.3. Configuring PIM Parameters

5.4.3.1. Enabling PIM

When configuring PIM, make sure to enable PIM on all interfaces for the routing instance, otherwise multicast routing errors can occur.

Use the following CLI syntax to enable PIM.

CLI Syntax:
config>router# pim

The following example displays the detailed output when PIM is enabled.

A:LAX>>config>router# info detail
...
#------------------------------------------
echo "PIM Configuration"
#------------------------------------------
        pim
            no import join-policy
            no import register-policy
            apply-to none
            rp
                no bootstrap-import
                no bootstrap-export
                static
                exit
                bsr-candidate
                    shutdown
                    priority 0
                    hash-mask-len 30
                    no address
                exit
                rp-candidate
                    shutdown
                    no address
                    holdtime 150
                    priority 192
                exit
            exit
            no shutdown
        exit
#------------------------------------------
...
A:LAX>>config>system#

5.4.3.2. Configuring PIM Interface Parameters

The following example displays the command usage to configure PIM interface parameters:

Example:
A:LAX>config>router# pim
A:LAX>config>router>pim# interface "system"
A:LAX>config>router>pim>if# exit
A:LAX>config>router>pim# interface "lax-vls"
A:LAX>config>router>pim>if# exit
A:LAX>config>router>pim# interface "lax-sjc"
A:LAX>config>router>pim>if# exit
A:LAX>config>router>pim# interface "p1-ix"
A:LAX>config>router>pim>if# exit
A:LAX>config>router>pim# rp
A:LAX>config>router>pim>rp# static
A:LAX>config>router>pim>rp>static# address 239.22.187.237
A:LAX>config>router>..>address# group-prefix 239.24.24.24/32
A:LAX>config>router>pim>rp>static>address# exit
A:LAX>config>router>pim>rp>static# exit
A:LAX>config>router>pim>rp# exit
A:LAX>config>router>pim#

The following example displays the PIM configuration:

A:LAX>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "lax-vls"
            exit
            interface "lax-sjc"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                    address 10.10.10.10
                    exit
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:LAX>config>router>pim#
Example:
A:SJC>config>router# pim
A:SJC>config>router>pim# interface "system"
A:SJC>config>router>pim>if# exit
A:SJC>config>router>pim# interface "sjc-lax"
A:SJC>config>router>pim>if# exit
A:SJC>config>router>pim# interface "sjc-nyc"
A:SJC>config>router>pim>if# exit
A:SJC>config>router>pim# interface "sjc-sfo"
A:SJC>config>router>pim>if# exit
A:SJC>config>router>pim# rp
A:SJC>config>router>pim>rp# static
A:SJC>config>router>pim>rp>static# address 239.22.187.237
A:SJC>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
A:SJC>config>router>pim>rp>static>address# exit
A:SJC>config>router>pim>rp>static# exit
A:SJC>config>router>pim>rp# exit
A:SJC>config>router>pim#
A:SJC>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "sjc-lax"
            exit
            interface "sjc-nyc"
            exit
            interface "sjc-sfo"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:SJC>config>router>pim#
Example:
A:MV>config>router# pim
A:MV>config>router>pim# interface "system"
A:MV>config>router>pim>if# exit
A:MV>config>router>pim# interface "mv-sfo"
A:MV>config>router>pim>if# exit
A:MV>config>router>pim# interface "mv-v1c"
A:MV>config>router>pim>if# exit
A:MV>config>router>pim# interface "p3-ix"
A:MV>config>router>pim>if# exit
A:MV>config>router>pim# rp
A:MV>config>router>pim>rp# static
A:MV>config>router>pim>rp>static# address 239.22.187.237
A:MV>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
A:MV>config>router>pim>rp>static>address# exit
A:MV>config>router>pim>rp>static#
A:MV>config>router>pim>rp# exit
A:MV>config>router>pim#
A:MV>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "mv-sfo"
            exit
            interface "mv-vlc"
            exit
            interface "p3-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                bsr-candidate
                    address 2.22.187.236
                    no shutdown
                exit
                rp-candidate
                    address 2.22.187.236
                    no shutdown
                exit
            exit
----------------------------------------------
A:MV>config>router>pim#

2.20.2. Command Descriptions

This section provides show command descriptions and output.

Note:

For VLL, VPLS, and PBB show, clear, and debug commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN.

For IES and VPRN show, clear, and debug commands, refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN.

2.20.2.1. Service Commands

customer

Syntax 
customer [customer-id] [site customer-site-name]]
Context 
show>service
Description 

This command displays service customer information.

Parameters 
customer-id—
Displays only information for the specified customer ID.
Default—
All customer IDs display.
Values—
1 to 2147483647

 

customer-site-name
Specifies the customer site name up to 32 characters in length which is an anchor point for an ingress and egress virtual scheduler hierarchy.
Output 

The following shows an example of customer information.

Table 15 describes the show customer command output fields:

Sample Output
*A:ALA-12# show service customer
==========================================================
Customers
==========================================================
Customer-ID : 1
Contact     : Manager
Description : Default customer
Phone       : (123) 555-1212
 
Customer-ID : 2
Contact     : Tech Support
Description : TiMetra Networks
Phone       : (234) 555-1212
 
Customer-ID : 3
Contact     : Test
Description : TiMetra Networks
Phone       : (345) 555-1212
 
Customer-ID : 6
Contact     : Test1
Description : Epipe Customer
Phone       : (456) 555-1212
 
Customer-ID : 7
Contact     : Test2
Description : VPLS Customer
Phone       : (567) 555-1212
 
Customer-ID : 8
Contact     : Customer Service
Description : IES Customer
Phone       : (678) 555-1212
 
Customer-ID : 274
Contact     : TestA
Description : ABC Company
Phone       : 650 123-4567
 
Customer-ID : 94043
Contact     : Test Engineer on Duty
Description : TEST Customer
Phone       : (789) 555-1212
------------------------------------------------------
Total Customers : 8
-----------------------------------------------------------
*A:ALA-12#
*A:ALA-12# show service customer 274
==============================================================================
Customer  274
==============================================================================
Customer-ID : 274
Contact     : Mssrs. Beaucoup
Description : ABC Company
Phone       : 650 123-4567
------------------------------------------------------------------------------
Multi Service Site
------------------------------------------------------------------------------
Site        : west
Description : (Not Specified)
==============================================================================
*A:ALA-12#
 
 
*A:ALA-12# show service customer 274 site west
==============================================================================
Customer  274
==============================================================================
Customer-ID : 274
Contact     : Mssrs. Beaucoup
Description : ABC Company
Phone       : 650 123-4567
------------------------------------------------------------------------------
Multi Service Site
------------------------------------------------------------------------------
Site        : west
Description : (Not Specified)
Assignment  : Card 1
I. Sched Pol: SLA1
E. Sched Pol: (Not Specified)
------------------------------------------------------------------------------
Service Association
------------------------------------------------------------------------------
No Service Association Found.
==============================================================================
*A:ALA-12#
 
Table 15:  Service Commands Customer Field Descriptions   

Label

Description

Customer-ID

Displays the ID that uniquely identifies a customer.

Contact

Displays the name of the primary contact person.

Description

Displays generic information about the customer.

Phone

Displays the phone or pager number to reach the primary contact.

Total Customers

Displays the total number of customers configured.

Site

Displays the multi-service site name. A multi-service customer site is a group of SAPs with common origination and termination points.

Description

Displays information about a specific customer's multi-service site.

Assignment

Displays the port ID, MDA, or card number, where the SAP's that are members of this multi- service site are defined.

I. Sched Pol

Displays the ingress QoS scheduler policy assigned to this multi-service site.

E. Sched Pol

Displays the egress QoS scheduler policy assigned to this multi-service site.

Service-ID

Displays the ID that uniquely identifies a service.

SAP

Displays the SAP assigned to the service.

fdb-mac

Syntax 
fdb-mac [ieee-address] [expiry]
Context 
show>service
Description 

This command displays the FDB entry for a given MAC address.

Parameters 
ieee-address—
Specifies the 48-bit MAC address in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee, and ff are hexadecimal numbers.
expiry—
shows amount of time until the MAC is aged out.
Output 

The following displays an example of service FDB MAC address information.

Sample Output
*A:ALA-48# show service fdb-mac
===============================================================================
Service Forwarding Database
===============================================================================
ServId    MAC               Source-Identifier     Type/Age  Last Change
-------------------------------------------------------------------------------
103       12:34:56:78:90:0f sap:1/1/7:0           Static    02/02/2009 09:27:57
700       90:30:ff:ff:ff:8f cpm                   Host      02/02/2009 09:27:57
-------------------------------------------------------------------------------
No. of Entries: 2
===============================================================================
*A:ALA-48#
 
 
*A:ALA-48# show service fdb-mac expiry
===============================================================================
Service Forwarding Database
===============================================================================
ServId    MAC               Source-Identifier     Type/     Last Change
                                                  Expiry
-------------------------------------------------------------------------------
103       12:34:56:78:90:0f sap:1/1/7:0           Static    02/02/2009 09:27:57
700       90:30:ff:ff:ff:8f cpm                   Host      02/02/2009 09:27:57
-------------------------------------------------------------------------------
No. of Entries: 2
===============================================================================
*A:ALA-48#

id

Syntax 
id service-id
>rp>static# address 239.22.187.237
A:SFO>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
A:SFO>config>router>pim>rp>static>address# exit
A:SFO>config>router>pim>rp>static# exit
A:SFO>config>router>pim>rp # exit
A:SFO>config>router>pim#
A:SFO>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "sfo-sjc"
            exit
            interface "sfo-was"
            exit
            interface "sfo-mv"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                bsr-candidate
                    address 239.22.187.239
                    no shutdown
                exit
                rp-candidate
                    address 239.22.187.239
                    no shutdown
                exit
            exit
----------------------------------------------
A:SFO>config>router>pim#
Example:
A:WAS>config>router# pim
A:WAS>config>router>pim# interface "system"
A:WAS>config>router>pim>if# exit
A:WAS>config>router>pim# interface "was-sfo"
A:WAS>config>router>pim>if# exit
A:WAS>config>router>pim# interface "was-vlc"
A:WAS>config>router>pim>if# exit
A:WAS>config>router>pim# interface "p4-ix"
A:WAS>config>router>pim>if# exit
A:WAS>config>router>pim# rp
A:WAS>config>router>pim>rp# static
A:WAS>config>router>pim>rp>static# address 239.22.187.237
A:WAS>config>router>pim>rp>static>address# group-prefix 239.24.24.24/32
A:WAS>config>router>pim>rp>static>address# exit
A:WAS>config>router>pim>rp>static# exit
A:WAS>config>router>pim>rp# bsr-candidate
A:WAS>config>router>pim>rp>bsr-cand# address 239.22.187.240
A:WAS>config>router>pim>rp>bsr-cand# no shutdown
A:WAS>config>router>pim>rp>bsr-cand# exit
A:WAS>config>router>pim>rp# exit
A:WAS>config>router>pim#
A:WAS>config>router>pim# info
----------------------------------------------
            interface "system"
            exit
            interface "was-sfo"
            exit
            interface "was-vlc"
            exit
            interface "p4-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                exit
                bsr-candidate
                    address 239.22.187.240
                    no shutdown
                exit
                rp-candidate
                    address 239.22.187.240
                    no shutdown
                exit
            exit
----------------------------------------------
A:WAS>config>router>pim#

5.4.3.3. Configuring PIM Join/Register Policies

Join policies are used in Protocol Independent Multicast (PIM) configurations to prevent the transportation of multicast traffic across a network and the dropping of packets at a scope at the edge of the network. PIM Join filters reduce the potential for denial of service (DoS) attacks and PIM state explosion—large numbers of Joins forwarded to each router on the RPT, resulting in memory consumption. Refer to the Importing PIM Join/Register Policies section of the Multicast Routing Guide for more information.

(*,G) or (S,G) is the information used to forward unicast or multicast packets.

  1. group-address matches the group address policy in join/prune messages
    group-address “group-address-policy”
  2. source-address matches the source address in join/prune messages
    source-address 192.168.0.1
  3. interface matches any join message received on the specified interface
    interface port 1/1/1
  4. neighbor matches any join message received from the specified neighbor
    neighbor 1.1.1.1

The following configuration example will not allow join messages for group 229.50.50.208/32 and source 192.168.0.1 but allows other join messages.

Configuring policy-statement

A:ALA-B>config>router# policy-options
A:ALA-B>config>router>policy-options# begin
A:ALA-B>config>router>policy-options# policy-statement foo
A:ALA-B>config>router>policy-options>policy-statement$ entry 10
A:ALA-B>config>router>policy-options>policy-statement>entry$ from
A:ALA-B>config>router>policy-options>policy-statement>entry>from$ group-address 
“group-address-policy”
A:ALA-B>config>router>policy-options>policy-statement>entry>from$ source-address 
192.168.0.1
A:ALA-B>config>router>policy-options>policy-statement>entry>from$ exit
A:ALA-B>config>router>policy-options>policy-statement>entry# action reject
A:ALA-B>config>router>policy-options>policy-statement>entry#

5.4.3.4. Importing PIM Join/Register Policies

The import command provides a mechanism to control the (*,G) and (S,G) state that gets created on a router. Import policies are defined in the config>router>policy-options context.

Note:

In the import policy, if an action is not specified in the entry then the default-action takes precedence. If no entry matches then the default-action also takes precedence. If no default-action is specified, then the default default-action is executed.

Use the following commands to configure PIM parameters:

CLI Syntax:
config>router# pim
import {join-policy | register-policy} [policy-name [.. policy-name]

The following example displays the command usage to apply the policy statement which does not allow join messages for group 229.50.50.208/32 and source 192.168.0.0/16 but allows join messages for 192.168.0.0/16, 229.50.50.208 (refer to the “Configuring Route Policy Components” section of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Unicast Routing Protocols Guide).

Example:
config>router# pim
config>router>pim# import join-policy "foo"
config>router>pim# no shutdown

The following example displays the PIM configuration:

A:LAX>config>router>pim# info
----------------------------------------------
            import join-policy "foo"
            interface "system"
            exit
            interface "lax-vls"
            exit
            interface "lax-sjc"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/3
                    exit
                    address 10.10.10.10
                    exit
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
----------------------------------------------
A:LAX>config>router>pim# 

5.4.3.5. Configuring Bootstrap Message Import and Export Policies

Bootstrap import and export policies are used to control the flow of bootstrap messages to and from the RP.

The following configuration example specifies that no BSR messages received or sent out of interface port 1/1/1.

 
A:ALA-B>config>router>policy-options# policy-statement pim-import
:A:ALA-B>config>router>policy-options>policy-statement$ entry 10
:A:ALA-B>config>router>policy-options>policy-statement>entry$ from
:A:ALA-B>config>router>policy-options>policy-statement>entry>from$ interface 
port 1/1/1
:A:ALA-B>config>router>policy-options>policy-statement>entry>from$ exit
:A:ALA-B>config>router>policy-options>policy-statement>entry# action reject
:A:ALA-B>config>router>policy-options>policy-statement>entry# exit
:A:ALA-B>config>router>policy-options>policy-statement# exit
 
:A:ALA-B>config>router>policy-options# policy-statement pim-export
:A:ALA-B>config>router>policy-options>policy-statement$ entry 10
:A:ALA-B>config>router>policy-options>policy-statement>entry$ to
:A:ALA-B>config>router>policy-options>policy-statement>entry>to$interface port 1/1/1
:A:ALA-B>config>router>policy-options>policy-statement>entry# action reject
:A:ALA-B>config>router>policy-options>policy-statement>entry# exit
:A:ALA-B>config>router>policy-options>policy-statement# exit
 
:A:ALA-B>configure router pim rp bootstrap-import pim-import
:A:ALA-B>configure router pim rp bootstrap-export pim-export

5.4.4. Disabling PIM

Use the following CLI syntax to disable PIM.

CLI Syntax:
config>router#
pim
shutdown

The following example displays the command usage to disable multicast:

Example:
config>router# pim
config>router>pim# shutdown
config>router>pim# exit

The following example displays the configuration output:

A:LAX>config>router# info
----------------------------------------------
...
#------------------------------------------
echo "PIM Configuration"
#------------------------------------------
        pim
            shutdown
            import join-policy "foo"
            interface "system"
            exit
            interface "lax-sjc"
            exit
            interface "lax-vls"
            exit
            interface "p1-ix"
            exit
            rp
                static
                    address 239.22.187.237
                        group-prefix 239.24.24.24/32
                    exit
                    address 10.10.10.10
                    exit
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
        exit
#------------------------------------------
....
------------------------------------------
A:LAX>config>router#