IP multicast configuration command directory
ip igmp immediate-leave group-list
ip igmp last-member-query-interval
ip igmp query-max-response-time
ip pim-dm state-refresh
origination-interval
If you want to
clear the multicast group member information saved in multicast router that
supports IGMP, you can use the command “clear ip igmp group”.
clear ip igmp group [type number] [group-address
| <cr>]
Parameter:
type number:port type and port number
group-address: Multicast group’s
group
address to clear information
Default:
none
Command mode:
Supervisor
mode
Explanation:
Using this command,
you can clear the multicast group member information saved in router when the
saved multicast group information has a problem.
Example:
The following example shows
you how to clear the information
of multicast group 233.33.1.1 on e1/0 port.
clear ip igmp group e1/0 233.33.1.1
Relevant
command:
none
use the following command in supervisor mode to clear the (S,G) routing list items submitted by PIM-DM to mrouting:
clear ip mroute pim-dm {* | group
[source]}
Parameter:
* |
Delete all multicast routing list items
submitted by pim-dm. |
group |
Delete all list items submitted by pim-dm and
satisfied in the specified group. |
source |
(optional) Delete all list items submitted by
pim-dm and satisfied in the specified group’s source. |
Default:
none
Command mode:
Supervisor mode
Explanation:
The command will delete all or part of table lists of local multicast router table,and it is possible to affect the normal multicast packet forwarding. This command can only delete the (S,G) items, whose upstream port is created by PIM-DM multicast routing protocol, and inform mrouting, then mrouting will determine if it should re-establish the corresponding (S,G).
Example:
Example1:
Router#clear ip mroute pim-dm *
All (S,G) items, whose middlestream/upstream port is created by PIM-DM, on local MRT will be cleared.
Example2:
Router#clear ip mroute pim-dm 239.1.1.1
All (S,G) items with the group address 239.1.1.1, whose middlestream/upstream port is created by PIM-DM, on local MRT will be cleared.
Example3:
Router#clear ip mroute pim-dm 239.1.1.1 192.168.20.131
All (S,G) items with the address (192.168.20.138, 239.1.1.1), whose middlestream/upstream port is created by PIM-DM, on local MRT will be cleared.
clear ip
pim-dm interface
Reset the multicast packet statistic value forwarded through (S,G) on PIM-DM port. You can use the command in supervisor mode:
clear ip pim-dm
interface {count | type number{count}}
Parameter:
count |
(optional) Delete all multicast packet
statistic values on PIM-DM port. |
type number |
(optional) Delete multicast packet statistic
values on the specified port. |
Default:
none
Command mode:
supervisor mode
Explanation:
This operation will reset the multicast packet number statistic values forwarded through PIM-DM port in local multicast routing list. This command can only reset the (S,G) items, whose upstream port is created by PIM-DM multicast routing protocol.
Example:
Example1:
Router#clear ip pim-dm interface count
It will reset all multicast packet number statistic values forwarded by (S,G) items, whose upstream port is created by PIM-DM, on local MRT.
Example2:
Router#clear
ip pim-dm interface Ethernet1/1 count
It will reset all multicast packet number statistic values forwarded by (S,G) items, whose upstream port is Ethernet1/1 and created by PIM-DM, on local MRT.
If you want to track the process for igmp-router
end protocol, you can use this command “debug ip igmp”, and use the”no” forma of the
command to close debug information.
debug ip igmp
no debug ip igmp
Parameter:
none
Default:
Close debug information output
Command
mode:
Supervisor
mode
Explanation:
You can use this command
to track the main process for igmp-router end protocol to find the reason for
protocol processing failure.
Example:
igmp-router function module’s debug information usually use
the natural language to make description. Due to its simplicity, we will not
list all of the debug information.
If you want to track the process for igmp-host
end protocol, you can use this command “debug ip igmph”, and use the”no” forma of the
command to close debug information.
debug ip igmph [group-address]
no debug ip igmph
Parameter:
none
Default:
Close debug information output
Command
mode:
Supervisor
mode
Explanation:
You can use this command
to track the main process for igmp-host end protocol to find the reason for
protocol processing failure.
Example:
igmp-host function module’s debug information usually use
the natural language to make description. Due to its simplicity, we will not
list all of the debug information.
If you want to track the
process for the multicast packet, you can use this command “debug ip mpacket”, and use the”no” forma
of the command to close debug information.
debug ip mpacket [access-list][group-address][detail]
no debug ip mpacket
Parameter:
access-list |
Range for tracked multicast packets |
group-address |
The tracked
multicast packet group address |
detail |
Details for
multicast packet processing |
Default:
Close
debug information output
Command
mode:
Supervisor mode
Explanation:
You can use this command to track the main process for
igmp-host end protocol.
Example:
The following example
shows some situations for multicast packet processing.
You have received the
(100.168.20.151,224.1.1.1) packet on e0/1 port, and the packet length is 112
bytes.
You have sent
the (192.168.20.99,224.0.0.5) packet on e0/1 port, and the packet length is 64
bytes.
router#debug ip
mpacket
M INPUT : IP Ethernet0/1
(100.168.20.151,224.1.1.1) , len=112
M OUTPUT : IP Ethernet0/1 (192.168.20.99,224.0.0.5)
, len=64
Use this command “debug ip mrouting” to enable “mrouting”
tracking function, then you can see the change from the multicast transfer
list. In addition, use the”no” forma of the command to close debug information.
debug ip mrouting
no debug ip mrouting
Parameter:
none
default:
Close
all tracking functions.
Command mode:
Supervisor mode
Explanation:
You can use this command to see the change from the multicast
transfer list, such as (S, G)/(*,G) adding/deleting and downstream interface adding/deleting.
Example:
The following example
shows you some changes from the multicast transfer list. First the
(192.168.20.110, 239.0.0.100) item is created, and then Loopback0 is added for
downstream interface. Finally, the item is deleted due to timeout.
router#debug
ip mrouting
MBR:
create (192.168.20.110, 239.0.0.100)
MBR:
w/ oif Loopback0
MBR:
delete (192.168.20.110, 239.0.0.100)
Relevant command:
Use this command “debug ip mrouting” to enable “mroute-cache”
tracking function, then you can see the change from the multicast routing
cache. In addition, you can use the “no”format of the command to close the tracking.
debug ip mroute-cache [group-address]
no debug ip mroute-cache
Parameter:
group-address |
The tracked multicast routing cache group address |
Default:
Close all tracking functions.
Command mode:
Supervisor mode
explanation:
You can use this command to see the change of the adding/deleting of multicast routing cache.
example:
The following example shows you some changes on the multicast
routing cache, and the creating and timeout of (192.168.20.97,230.0.0.1) cache.
router#debug
ip mroute-cache
MRC:
create (192.168.20.97,230.0.0.1) mroute-cache
MRC:
expired (192.168.20.97,230.0.0.1) mroute-cache
You can use this command “debug ip multicast” to enable
multicast event tracking function, and then see the interaction between the
multicast protocol and mrouting. you can use the “no”format of the command to close the .
debug
ip multicast [alert | border-router]
no
debug ip multicast [alert | border-router]
Parameter:
alert |
Track the alert interaction among multicast
routing components |
border-router |
Track related events of multicast border router
MBR |
default:
Close
all tracking functions.
Command mode:
Supervisor
mode
explanation:
Defining some standard events
between multicast routing protocol and mrouting indicates “alert”, for
example: creation alert/deletion alert which related (S,G). You can use “debug
ip multicast alert” to see these alerts.
D-Link’s multicast routing
protocol supports MBR, and each multicast routing protocol is a “component”.
You can use “debug ip multicast border-router” to see the component’s running
information.
example:
In the following example, the alert router is turned
on for output:
router#debug
ip multicast alert
MBR:
[(S, G) deletion alert], originated by OLNK, sent to all components
MBR:
[(S, G) creation alert], originated by NONE, sent to all components
MBR: src = 192.168.20.110, grp =
239.0.0.100
MBR: sent to owner OLNK first
MBR:
[(S, G) join alert], originated by NONE, sent to OLNK
MBR: src = 192.168.20.110, grp =
239.0.0.100
MBR:
[(S, G) firstuse alert], originated by NONE, sent to OLNK
MBR: src = 192.168.20.110, grp =
239.0.0.100
MBR:
[(S, G) deletion alert], originated by OLNK, sent to all components
MBR: src = 192.168.20.110, grp =
239.0.0.100
use this command to
track input/output PIM packets and caused events. Set this command to “no” to
stop tracking.
debug ip pim-dm
[group|alert]
Parameter:
group |
(optional)
Track the specified group status. |
alert |
(optional) Track the
alert status received from mrouting. |
Default:
none
Command mode:
supervisor mode
Explanation:
receive Alert from mrouting.
Send alert to other components..
Example:
Example 1, the output information is as follows:
Hello packet prompt sent to each port.
Hello packet prompt received from each port.
A new neighbor is found.
Delete neighbor.
Port sending status refresh packet.
Port receiving status refresh packet.
Port is sending Assert packet.
Port is receiving Assert packet.
Port is sending prune packet.
Port is receiving prune packet.
Port is sending graft ack packet.
Port is receiving graft ack packet.
Port is sending graft packet.
Port is receiving graft packet.
Port is sending join/prune packet.
Port is receiving join/prune packet.
When a new (S,G) is created
When deleting (S,G)
Router#debug ip pim-dm
2003-3-26 11:45:17 received V2 hello packet
on Ethernet2/1 from 192.168.20.133(GenID = 3539)
2003-3-26 11:45:17 Ethernet2/1 create new nbr
192.168.20.133
2003-3-26 11:45:25 send hello packet to
224.0.0.13 on Loopback1
2003-3-26 11:50:29 Ethernet2/1 delete nbr
192.168.20.133
2003-3-26 11:50:51 received V2 hello packet
on Ethernet2/1 from 192.168.20.152
2003-3-26 11:50:51 send hello packet to
224.0.0.13 on Ethernet2/1
2003-3-26 12:04:37 PIM-DM: delete (192.168.20.138, 239.1.1.1) in
MRT success
2003-3-26 12:04:37 PIM-DM: clear
(192.168.20.138, 239.1.1.1) from MRT successful
2003-3-26 12:04:39 PIM-DM: ignored V2 packet
on Ethernet2/1 from 192.168.10.204 (validate source address failed)
2003-3-26 12:04:39 PIM-DM: (192.168.20.138, 239.1.1.1)'s
upstream:192.168.20.132 Adding in MRT success
2003-3-26 12:04:39 PIM-DM: (192.168.20.138,
239.1.1.1) Adding in MRT
Example 2, output received alert message:
Router#debug ip pim-dm alert
2003-3-26 12:09:51 receive alert_rt_change
alert from mroute
2003-3-26 12:09:54 receive alert_rt_change
alert from mroute
2003-3-26 12:11:08 PIM-DM: send sg_deletion
alert
2003-3-26 12:11:19 receive alert_sg_creation
alert from mroute
2003-3-26 12:11:20 receive alert_sg_prune
alert from mroute
2003-3-26 12:11:56 receive alert_group_report
alert from mroute
2003-3-26 12:11:56 receive alert_sg_join
alert from mroute
Example 3, track the specified group status:
Router#deb ip pim-dm 239.1.1.1
Router#2003-3-26 12:35:27 PIM-DM: clear (192.168.20.138, 239.1.1.1) forwd pkt count success
2003-3-26 12:35:37 PIM-DM: delete (192.168.20.138, 239.1.1.1) in MRT success
2003-3-26 12:35:37 PIM-DM: clear (192.168.20.138, 239.1.1.1) from MRT successful
2003-3-26 12:35:37 PIM-DM: (192.168.20.138, 239.1.1.1)'s upstream: 192.168.20.132 Adding in MRT success
2003-3-26 12:35:37 PIM-DM: (192.168.20.138, 239.1.1.1)'s downstream: 1.1.1.1 create success
2003-3-26 12:35:37 PIM-DM: (192.168.20.138, 239.1.1.1)'s downstream: 192.167.20.132 create success
2003-3-26 12:35:42 PIM-DM: (192.168.20.138, 239.1.1.1) Adding in MRT
If you want a
port to transit IGMP packet, you can use this command to configure the
port. One port can configure the command only once time, so the next configured command will overwrite the original
command.
ip igmp helper-address destination-address
no ip igmp helper-address destination-address
Parameter:
destination-address: the
destination address of transitting IGMP packet
Default:
The port will
not transit IGMP packet
Command mode:
interface configuration mode
Explanation:
Use this
command “ip igmp helper-address” to transit all received igmp packets.
Example:
ip igmp helper-address 192.168.20.10
If you want to
add a multicast group on the port, you can use this command to perform
it.
ip igmp join-group group-address
[{include|exclude} source-address]
no ip igmp join-group group-address
[{include|exclude} source-address]
Parameter:
group-address: the multicast
group required to be added to the port
include : The mode of SSM needed
to add a multicast group is “include”
exclude : The mode of SSM needed
to add a multicast group is “exclude”
source-address: source filter
address whose port is added to multicast group
Default:
No multicast group will be added to the port.
Command mode:
interface configuration mode
Explanation:
Use this
command “ip igmp join-group” to dynamically add a multicast group to the
port.
Example:
ip igmp join-group 230.0.0.1
ip igmp join-group 230.0.0.1 exclude 192.168.20.10
ip igmp immediate-leave group-list
If you want the
router
port running IGMP version 2 to run
the multicast group function “Exit Now”, you can use this command “ip igmp immediate-leave group-list” to perform configuring. In addition, you can use
the “no”format of the command to forbid the IGMP host to “exit now”.
ip igmp immediate-leave
group-list list-name
no ip igmp immediate-leave
group-list
Parameter:
list-name: Pre-configured ip standard access-list name
Default:
The IGMP host is not allowed to run “Exit Now” function.
Command mode:
global configuration mode/interface configuration mode
Explanation:
This command is available only for the port of running
IGMP version 2.it can be used when the network connecting with the port has
only one IGMP host. Through configuring this command, the host can immediately
exit from a multicast group without the process for packet exchanging and
delaying from the router. Besides, you can configure this command in “global
configuration mode” and “interface configuration mode”, but this command
configured in “global configuration mode” will be prior to the command
configured in “interface configuration mode”. If you have configured the
command in “global configuration mode”, the next command configured in “interface
configuration mode “will be ignored. On the
other hand, the command configured in “global configurationmode” will overwrite the original command
configured in “interface configurationmode”.
Example:
Prefer to “Configure multicast routing”.
relevant command:
ip
access-list
ip igmp last-member-query-interval
To change the query
interval of last group member l on the current port, use this command “ip igmp last-member-query-interval”. You can use
the “no” format of the command to
restore default settings.
ip igmp
last-member-query-interval time
no ip igmp
last-member-query-interval
Parameter:
time:the value of last member query interval
configured on the port. Its unit is millisecond.
Default:
The default of the last group member query
interval on the port is 1000ms.
Command mode:
interface configuration mode
Explanation:
You can use
this command “ip igmp last-member-query-interval” to modify the last group member
query interval on the port.
Example:
The following example will modify the last
member query interval on the port to
2 seconds.
interface ethernet 0
ip igmp last-member-query-interval
2000
you can use
this command “ip igmp querier-timeout”to modify other routers for IGMP
querier timeout,.use the “no” f ormat of this command to restore
default.
ip igmp querier-timeout time
no ip igmp querier-timeout
Parameter:
time:other querier timeout. Its unit is second.
Default:
125 seconds
Command mode:
interface configuration mode
Explanation:
You can use
this command “ip igmp querier-timeout” to modify other routers for querier
timeout. This command is available only for the port which running IGMP version
2.
Example:
The following example shows that the
querier-timeout specified on interface Ethernet 0/0 is 100 seconds.
interface ethernet 0/0
ip igmp querier-timeout 100
To set the
interval for IGMP General Query packet sending on the port, you can use this command “ip igmp query-interval”. Use the “no”format of this
command to restore default.
ip igmp query-interval time
no ip igmp query-interval
Parameter:
time: interval of sending general query packet. Its
unit is second.
Default:
60 seconds
Command mode:
interface configuration mode
Explanation:
you can use this command “ip igmp query-interval”to set the interval for IGMP General Query
packet sending on the port,
Example:
The following example shows that the interval of
sending general query packet on Ethernet 0/0 port is specified to 50 seconds.
interface ethernet 0/0
ip igmp query-interval 50
ip igmp query-max-response-time
To specify the
maximum interval for IGMP host to
respond General Query packet, you
can use this command “ip igmp query-max-resposne-time”. Use the “no”format of this
command to restore default.
ip igmp
query-max-response-time time
no ip igmp
query-max-response-time
Parameter:
time:value of the maximum response time configured on
the port.
Default:
10 seconds
Command mode:
interface configuration mode
Explanation:
you can use
this command “ip igmp query-max-resposne-time”to specify the maximum interval for IGMP host to respond General Query packet. This command is available only for the port
which running IGMP version 2 and 3.
Example:
The following example will
set the IGMP maximum response time on Ethernet 0/0 port as 15 seconds.
ip igmp
query-max-response-time 15
If you want to
configure a static multicast group on the port, you can use this command “ip igmp
static-group” to perform it. Use the “no”format of
this command to restore default.
ip igmp static-group { * |
group-address } {include source-address | <cr> }
no ip igmp static-group { * |
group-address } {include source-address | <cr> }
Parameter:
*:all multicast
groups.
group-address:specified multicast group address.
source-address:specified host source address.
Default:
In default, no multicast group is static
configured on the port.
Command mode:
interface configuration mode
Explanation:
Configure
the static IGMP multicast group information on the
current port.
Note: For the
same group-address, you can configure several “include
source-address” commands for the corresponding static multicast group to have
several source-addresses existing. However, for the same group-address, you can’t
configure both commands with/without “include source-address”.
Example:
Refer to “Configure multicast routing”
To set the IGMP version
number running on the port, you can use
this command “ip igmp version”. use the “no”format
of the command to restore default.
ip igmp version version-number
no ip igmp version
Parameter:
version-number:The value 1.2 or 3 indicates separately
the IGMP version number 1,2 or3.
Default:
If you don’t configure this command, the default
version number for IGMP-Router end protocol running on the port is 3.
Command mode:
interface configuration mode
Explanation:
use this command “ip igmp version”can set
the IGMP version number running on the
port,
Example:
The following example will
specify the IGMP version number running
on Ethernet 0/0 port as 2.
interface ethernet 0/0
ip igmp version 2
Use the command “ip mroute” to configure the static
multicast routing, and use “no ip mroute” to delete the configured
static multicast routing.
ip mroute source-address mask rpf-address
type number [distance]
no
ip mroute source-address mask [rpf-address type number
[distance]]
Parameter:
source-address |
Multicast source IP address |
mask |
Multicast source IP address mask |
rpf-address |
RPF address of Static multicast routing |
type number |
RPF interface of Static multicast routing |
distance |
Optional management
distance |
default:
The default management distance is 0.
Command mode:
global configuration mode
explanation:
This command allows you to manually configure the location
information for the multicast source. It is used when the multicast and unicast
topologies are not identical.
example:
The following example will configure a static multicast routing
through the specified interface:
router_config#ip
mroute 100.1.1.0 255.255.255.0 192.1.1.1 f0/0
Relevant command:
Use this command “ip mroute-cache”
to configure a multicast routing cache on the port, and “no ip mroute-cache”
to disable the multicast routing cache.
ip mroute-cache
no ip mroute-cache
Parameter:
none
default:
The default is to use
the multicast routing cache on the port.
Command mode:
interface configuration mode
explanation:
Use the command when a port uses
the multicast routing cache to receive/send the packet, ip will search the
cache when a multicast packet is received. If there is no routing information
in the cache, the port will ask for multicast routing module.
example:
The following example will enable multicast
routing cache on interface e1/0.
router_config_e1/0#ip
mroute-cache
Relevant command:
show ip mroute-cache
Use this command “ip multicast-routing” to enable IP
multicast packet transferring function, and “no ip multicast-routing” to
disable the function.
ip multicast-routing
no
ip multicast-routing
Parameter:
none
default:
The default is not to transfer multicast packets.
Command mode:
global configuration mode
explanation:
If you disable this function, the router will no longer transfer
multicast packets, meanwhile, the multicast routing list and the multicast
cache will be empty.
example:
The following example will configure the router to transfer
multicast packets:
router_config#ip
multicast-routing
Relevant command:
Use this command “ip multicast route-limit” to configure
the maximum number of multicast routing item, and “no ip multicast
route-limit” to un-limit the number.
ip multicast route-limit size
no
ip multicast route-limit [size]
Parameter:
size |
Maximum number of multicast routing item |
default:
The default multicast routing item number is unlimited.
Command mode:
global configuration mode
explanation:
If you have configured this function, the multicast routing item
number will be limited.
example:
The following example will configure the maximum number of multicast
routing list to 2000:
router_config#ip
multicast route-limit 2000
Relevant command:
Use this command “ip multicast
boundary” to manage the range for the port allowed processing multicast
packets; it is valid for input/output packets on the port. use “no ip multicast boundary”
to cancel this command.
ip multicast boundary access-list
no ip multicast boundary
Parameter:
access-list |
the access-list name used to specify the range for processing
multicast packets. |
default:
Process all multicast packets.
Command mode:
interface configuration mode
explanation:
If the function is configured, the range
for the port allowed processing multicast packets will be limited.
example:
The following example
will configure the range for the port e1/0 allowed processing multicast packets
to the range limited by the access-list testacl:
router_config_e1/0#ip
multicast boundary testacl
ip multicast helper-map
Use this command “ip multicast helper-map” to
configure the connection of two broadcast networks with the multicast routing
on the multicast network, and “no ip multicast helper-map” to cancel
this command.
ip multicast boundary helper-map {group-address|broadcast}{broadcast-address|multicast-address} access-list
no
ip multicast boundary helper-map {group-address|broadcast}{broadcast-address|multicast-address} access-list
Parameter:
group-address |
The multicast packet group address which needed
to be converted to the broadcast packet. it is used with the broadcast-address
keyword. |
broadcast |
It can convert the broadcast packet to the
multicast packet. it is used with the multicast-address keyword. |
broadcast-address |
The target address of broadcast packet which
is sent after converting. it is used with the group-address keyword. |
multicast-address |
The target address of multicast packet which
is sent after converting. It is used with the broadcast keyword. |
access-list |
IP extended access-list name. You can use it to specify the port number for packet converting. |
default:
not perform the conversion between any
multicast packets and broadcast packets.
Command mode:
interface configuration mode
explanation:
If two broadcast networks are connected
with a multicast network, you can convert the broadcast flow to multicast flow
on the first hop router connected with the source broadcast network, and then
convert the multicast flow to broadcast flow on the last hop router connected
with the target broadcast network.
Thus, you can utilize the multicast network’s multicast characteristic
between the two broadcast networks which are required to be connected with each
other. Furthermore, it can prevent
the packets between two broadcast networks from being sent repeatedly, and
utilize the “quick forward” characteristic on the multicast network.
Before using “ip multicast helper-map”,
you should have configured this command “ip directed-broadcast” on the port.
example:
Configuration
on the router is as follow:
if you configure command”ip directed-broadcast” on port e0 of the
first hop router, it will be allowed to process the link broadcast packets.
If you have configured “ip
multicast helper-map broadcast 230.0.0.1 testacl1”, you can convert the udp
broadcast packet, whose port number is 4000(“ip forward-protocol” command
specified) and the source address is 192.168.20.97/24 (testacl1 specified) ,to multicast
packet whose target address is 230.0.0.1 (“ip multicast helper-map” command
specified).
if
you configure command”ip
directed-broadcast” on port e1 of the last hop router, it will be allowed to
process the link broadcast packets.
If you have configured “ip multicast helper-map broadcast 230.0.0.1 172.10.255.255 testacl2”, you can convert the multicast packet, whose port number is 4000(“ip forward-protocol” command specified), the source address is 192.168.20.97/24 (testacl2 specified) and target address is 230.0.0.1 ,to broadcast packet whose target address is 170.10.255.255 (“ip multicast helper-map” command specified).
On the first hop router which is connected
with the source broadcast network:
interface ethernet 0
ip directed-broadcast
ip multicast helper-map
broadcast 230.0.0.1 testacl
ip pim dense-mode
!
ip access-list extended
testacl permit udp 192.168.20.97 255.255.255.0
any
ip forward-protocol udp 4000
On the last
hop router which is connected with the target broadcast network:
interface ethernet 1
ip directed-broadcast
ip multicast helper-map
230.0.0.1 172.10.255.255 testacl2
ip pim dense-mode
!
ip access-list extended
testacl2 permit udp 192.168.20.97
255.255.255.0 any
ip forward-protocol udp 4000
Relevant command:
ip forward-protocol
ip directed-broadcast
Use this command “ip
multicast rate-limit” to limit the multicast packet flow receiving
and sending in the range of a source/group on the port, and “no ip multicast
rate-limit” to cancel this flow limitation.
ip multicast rate-limit {in | out} [group-list access-list] [source-list access-list] kbps
no ip multicast rate-limit {in | out} [group-list
access-list] [source-list access-list]
Parameter:
in |
Limit the input packet flow on the port. |
out |
Limit the output packet flow on the port. |
group-list access-list |
(optional) Limit the multicast packet flow
for the group address in access-list. |
source-list access-list |
(optional) Limit the multicast packet flow
for the source address in access-list. |
kbps |
(optional) Allowed maximum flow. If its value
is 0, no packet will be allowed to pass. |
default:
No limitation to the flow.
Command mode:
interface configuration mode
explanation:
The packet flow in specified range has
exceeded the limit at last second. You have to discard the packet, or the
packet will be forwarded.
example:
The maximum output packet flow rate on
port s0 (192.168.20.97 , 230.0.0.1) is limited to 64kbps.
interface serial 0
ip multicast rate-limit out
group-list gacl source-list sacl 64
ip access-list standard sacl
permit 192.168.20.97
255.255.255.255
ip access-list standard gacl
permit 230.0.0.1 255.255.255.255
Use this command “ip
multicast ttl-threshold” to configure the maximum threshold value of
multicast packet ttl on the port, and “no ip multicast ttl-threshold” to
restore default.
ip
multicast ttl-threshold ttl-value
no ip multicast ttl-threshold
Parameter:
ttl-value |
The multicast packet ttl threshold value on the port. |
default:
The default ttl threshold value on the
port is 1.
Command mode:
interface configuration mode
explanation:
The ttl
value of receiving/sending packet should be largerer than the specified
threshold value on the port, you can use this command to configure a router to
border router.
example:
The ttl threshold value
configured on port s0 is 200, it means only the multicast packet with ttl value
more than 200 is allowed to be received/sent on the port.
interface serial 0
ip multicast ttl-threshold 200
Use this command “ip olnk” to run igmp only-link on the
interface, and then enable the multicast function; command “no ip olnk”
can cancel the multicast function on the port.
ip olnk
no
ip olnk
Parameter:
none
default:
The port doesn’t support multicast forwarding.
Command mode:
interface configuration mode
explanation:
The olnk is a multicast routing protocol without protocol
exchanging process, and it can generate the multicast routing list only
according to the configuration information and IGMP group information, and
provide services for multicast packet forwarding.
In the simple topology environment, using olnk can prevent the
dynamic multicast routing protocol from occupying CPU usage and bandwidth.
example:
The following example is a configuration to run olnk on f0/0
interface:
router_config_f0/0#ip
olnk
Relevant command:
This command is used to run PIM-DM on the port. set this command to “no” to disable PIM-DM on the port.
ip pim-dm
no ip pim-dm
Parameter:
none
Default:
none
Command mode:
interface configuration mode
Explanation:
1.If the “ip multicast-routing” is not
configured before configuring this command, it will display the following
warning: WARNING: "ip multicast-routing" is not configured, IP
Multicast packets will not be forwarded
2.Once this function is disabled, PIMDM will no longer run on the port.but it will not affect other PIM-DM configurations. After rerun PIM-DM on the port, all PIM-DM configurations are still valid.
3.Enabling this function means it is available
for forwarding multicast packet on the port, however, you have to enable the
global multicast packet forwarding function first.
Example:
Router_config#ip multicast-routing
Router_config#interface Ethernet1/1
Router_config_e1/1#ip
pim-dm
Relevant command:
ip multicast-routing: belongs to mrouting module, which allows multicast routing protocol to work.
show ip pim-dm interface: displays multicast information configured on the port.
Set a router as the priority to specified router (DR). You can set this command to “no” to restore default DR priority on the port.
ip pim-dm
dr-prioirty priority
no pim-dm dr-prioirty
Parameter:
priority |
Port DR priority. The larger the value is,
the higher the priority is. Its range is from 0 to 4294967294, and the
default is 1. |
Default:
default DR priority on PIM port is 1.
Command mode:
interface configuration mode
Explanation:
1.if all PIM neighbors support DR Priority on
the port, select the one with the highest priority as DR. If all have the same
priority, just select the one with the highest port IP value as DR.
2.If router didn’t advertise its priority in Hello packet and there are several routers have the same situation, just select the router with the highest port IP value as DR.
This command is used to configure the interval of regularly sent PIM-Hello packets on the port. You can set this command to “no” to restore default interval.
ip pim-dm
hello-interval interval
no ip pim-dm
hello-interval
Parameter:
interval |
The interval of regularly sent PIM-Hello packets. Its range is from 0 to 65535, and the default is 30 seconds. |
Default:
30 seconds
Command mode:
interface configuration mode
Explanation:
Regularly sending Hello packets can check if the neighbor exists. Generally, if Hello packets is not received after the 3.5 times hello-interval timeout configured by neighbor, the neighbor will be considered disappeared.
For IGMP v1, you can select the specified
router (DR) through PIM-DM Hello packet.
Example:
Router_config#interface
Ethernet1/1
Router_config_e1/1#ip pim-dm hello-interval 30
Relevant command:
ip igmp
query-interval
ip igmp query-interval IGMP querier regularly sends IGMP group member relation query to all hosts on some subnet multicast groups.
Configure PIM-DM version on the router port.
ip pim version [version]
Parameter:
version |
PIM-DM version. |
Default:
version: 2
Command mode:
interface configuration mode
Explanation:
By default, it will run the installation
version 2. If the interface has been configured version 2, and a neighbor who
is non PIM-DM version 2 is found, the router will not change this interface’s
PIM-DM version. We only support version 2.
Example:
Router_config_e1/1#ip pim version 2
Relevant command:
none
ip pim-dm state-refresh
origination-interval
It allows the router to generate original PIM-DM state refresh packet and configure the state refresh interval. To cancel the generation for original PIM-DM state refresh packet, set this command to “no”.
ip pim state-refresh
origination-interval [interval]
no ip pim state-refresh origination-interval
Parameter:
interval |
For the first port router connected with the
source directly, it is the interval of regularly sending state refresh
packet. For the following router, it is interval of allowed receiving and
processing state refresh packet for the port. This parameter is configured optionally, and
its range is from 4 to 100 seconds. The default is 60 seconds. |
Default:
This parameter is configured optionally.
The default is 60 seconds.
Command mode:
interface configuration mode
Explanation:
Configure
this command on the first router’s, neighboring directly on the multicast
source, incoming port. By default, it will generate original state refresh
packet. During configuring this command on the following router’s port, you can
use interval to limit the process for received state
refresh packet interval. By default, all routers where is running PIM-DM can process and forward state refresh packet.
Example:
Router_config_e1/1#ip pim-dm state-refresh origination-interval 80
Relevant command:
ip pim-dm state-refresh disable Disable port
receiving/sending state refresh packet.
This command is used to prevent some routers from participating PIM-DM
operation. Set this command to “no” to cancel the
limit.
ip pim-dm neighor-filter acess-list-name
no ip pim-dm neighor-filter acess-list-name
Parameter:
access-list-name |
Standard access-list, whose definition is to deny PIM packets from the specified source. |
Default:
No filter function.
Command mode:
interface configuration mode
Explanation:
You can use multiple filter lists. The router denied
by anyone of the lists can’t be a neighbor of local PIM-DM.
Example:
Router_config_e1/1#ip
pim-dm neighbor-filter nbr_filter
Router_config#ip access-list
standard nbr_filter
Router_config_std_nacl#deny
192.167.20.132 255.255.255.255
Router_config_std_nacl#permit 192.168.20.0 255.255.255.0
Relevant command:
access-list (IP standard) it defines a standard IP access-list.
ip pim-dm state-refresh disable
It will not allow running router process for PIM-DM multicast protocol or forward PIM-DM state refresh control message. You can set this command to “no” to restore the forwarding function.
ip pim-dm state-refresh disable
no ip pim-dm state-refresh disable
Parameter:
none
Default:
By default, it is allowed to run forwarding PIM dense mode state refresh control message.
Command mode:
Supervisor mode
Explanation:
After configuring this command to forbid processing and forwarding PIM-DM state refresh control message, the Hello message in PIM-DM will no longer contain state refresh control options and receive/send state refresh control packet.
Example:
The following command forbids forwarding state refresh control message to downstream neighbors of PIM dense mode.
ip pim-dm
state-refresh disable
Relevant command:
ip pim-dm state-refresh origination-interval
You can use the
following command to see the multicast group member information that is
saved on the current router.
show ip igmp groups {interface
| group-address | detail}
Parameter:
interface: The port where
you want to see the multicast group information. If you don’t add this parameter,
all multicast groups information on the port will be displayed.
group-address:The multicast group address to see. If you don’t add this parameter, all multicast groups information on
the router will be displayed
detail:The router whether you want to see the multicast group
information.
Default:
none
Command mode:
Supervisor mode/global configuration mode/interface configuration
mode
Explanation:
You can use
this command to see the multicast group member information that is
saved on the router.
Example:
show ip igmp groups e0/0 detail
Running this command will
display the following message:
………………………….
Interface: Ethernet0/0
Group address: 233.33.1.3
Uptime:
Group status: Static
Group filter mode: INCLUDE
Last reporter: 0.0.0.0
Group source-list: (Flags: S-Static,
R-Remote)
Source address:
Uptime
Timer
Fwd Flags
192.168.20.5 00:03:46 stopped Yes
S
Interface: Ethernet0/0
Group address: 233.33.1.1
Uptime:
Group status: Static
Group filter mode: INCLUDE
Last reporter: 0.0.0.0
Group source-list: (Flags: S-Static,
R-Remote)
Source
address: Uptime Timer Fwd Flags
192.168.20.5 00:03:46 stopped Yes
S
192.168.20.3 00:03:46 stopped Yes
S
192.168.20.1 00:03:46 stopped Yes
S
……………………………….
show ip igmp groups 233.33.1.1 detail
Running this command will
display the following message:
Interface: Ethernet0/0
Group address: 233.33.1.1
Uptime:
Group status: Static
Group filter mode: INCLUDE
Last reporter: 0.0.0.0
Group source-list: (Flags: S-Static,
R-Remote)
Source address:
Uptime
Timer
Fwd Flags
192.168.20.5 00:02:42 stopped Yes
S
192.168.20.3 00:02:42 stopped Yes
S
192.168.20.1 00:02:42 stopped Yes
S
show ip igmp groups
Running this command will
display the following message:
Interface Group address Uptime Expires Last Reporter Flags
Ethernet0/0 239.255.255.250 00:01:08 00:02:05 192.168.20.141 R
Ethernet0/0 224.2.127.254 00:01:09 00:02:00 32.1.1.67 R
Ethernet0/0 224.1.1.1 00:01:24 stopped 0.0.0.0 S
Ethernet0/0 233.33.1.5 00:01:24
stopped 0.0.0.0 S
Ethernet0/0 233.33.1.3 00:01:24 stopped 0.0.0.0 S
Ethernet0/0 233.33.1.1 00:01:24 stopped 0.0.0.0 S
Interface Group address Uptime Expires Last Reporter Flags
Loopback10 239.255.255.250 00:01:08 00:02:05
192.168.20.141 R
Loopback10 224.2.127.254 00:01:09 00:02:00 32.1.1.67 R
You can use this command to see information on
the current router’s port where IGMP is activated.
show ip igmp interface { interface
| <cr> }
Parameter:
interface: The specified port to
display information. If you don’t add this parameter, all information on ports
where IGMP is activated will be displayed.
Default:
none
Command mode:
Supervisor mode/global configuration mode/interface configuration
mode
Explanation:
You can use this command to display information
on the port where IGMP is activated.
Example:
show ip igmp interface e0/0
Running this
command will display the following information:
Ethernet0/0 is up, line protocol is up
Internet address is
192.168.20.167
Current IGMP router
version is 3
Router plays role of
querier on the interface now
IGMP is enable on
the interface
IGMP query-interval
is 60 seconds
IGMP max query
response time is 10 seconds
IGMP Last member
query response time is 1000 milliseconds
IGMP querier timeout
is 125 seconds
Multicast routing is
enabled on the interface
You can use this command
to see IGMP host information on the port ofcurrent router.
show ip igmph { interface
} [detail]
Parameter:
interface: The specified port to
display information.
detail : Display igmp host
detailed information.
Default:
none
Command mode:
Supervisor mode/global configuration mode/interface configuration
mode
Explanation:
You can use this command
to display basic IGMP host information on the port.
Example:
show ip igmph interface e0/0
Running this
command will display the following information:
IGMP host Mode is IGMP_V3_ROUTER
IGMP host Query Interval
is 23 second
IGMP host Query
Response Interval is 125
IGMP host Query
Robustness Variable is 2
IGMP host Last Query
Interval is 0
IGMP interface timer
is 0
IGMP host group
joined(number of users):
230.0.0.1(1)
You can use this command “show ip mflow” to display global
flow information processed by
system and multicast flow information processed on the port.
show ip mflow [group-address][source-address][interface]
Parameter:
group-address |
The displayed multicast
flow information group address. |
source-address |
The displayed multicast
flow information source address. |
interface |
The displayed port multicast flow information. |
default:
none
Command mode:
Supervisor mode
explanation:
Display the processed packet number from the
multicast flow, wrong incoming interface packet number, and current flow value.
example:
The following example will display global
multicast flow information:
router#show
ip mflow
IP
Multicast Flow
(100.168.20.151,224.1.1.1)
total
process : 0 wrong_if_count : 0
curr-flux : 0.00
(192.167.20.131,239.1.1.1)
total
process : 0 wrong_if_count : 0
curr-flux : 0.00
The following example
will display port multicast flow information:
router#show
ip mflow interface e0/1
IP
Multicast Flow
(192.168.20.97,230.0.0.1)
total
recv : 21180 total send : 0 curr-in-flux : 0.00
curr-out-flux : 0.00
(100.168.20.151,224.1.1.1)
total
recv : 16822400 total send :
0 curr-in-flux : 0.00
curr-out-flux : 0.00
(192.168.20.97,232.0.0.1)
total
recv : 240 total send : 0 curr-in-flux : 0.00
curr-out-flux : 0.00
(192.167.20.131,239.1.1.1)
total
recv : 103264 total send : 0 curr-in-flux : 0.90
curr-out-flux : 0.00
use this command “show ip mroute-cache” to display the
information on the multicast routing cache.
show ip mroute-cache [group-address]
Parameter:
group-address |
The displayed multicast routing cache group address |
default:
none
Command mode:
Supervisor mode
explanation:
MRC (Multicast Route Cache) is a global multicast
routing cache, and every MRC item contains the (S, G)/ (*, G) information,
upstream/downstream interface information received from the multicast routing.
example:
The following example will display multicast
routing list information:
router#show
ip mroute-cache
IP
Multicast Route Cache
(192.168.20.97,
230.0.0.1)|(192.168.20.97,230.0.0.1)
Incoming interface: Ethernet0/2, Last
used :
Outgoing interface list:
Loopback0
(192.168.20.97,
230.0.0.2)|(192.168.20.97,230.0.0.2)
Incoming interface: Ethernet0/2, Last
used :
Outgoing interface list:
Loopback1
You can use this command “show ip mroute mfc” to display
the multicast forwarding list information, and then activate the multicast
function.
show ip mroute mfc
Parameter:
none
default:
none
Command mode:
Supervisor mode
explanation:
MFC (Multicast Forwarding Cache) is a global multicast forwarding
list, and the multicast packet is forwarded by it. Every MFC item has (S, G)/
(*, G) information and upstream/downstream interface information.
example:
The following example will display multicast routing list
information:
router#show
ip mroute mfc
IP Multicast
Forwarding Cache
(192.168.20.110/32,
239.0.0.100/32)
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, owned by OLNK
Outgoing interface list:
Loopback0, owned by OLNK
(192.168.20.110/32,
239.0.0.101/32)
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, owned by OLNK
Outgoing interface list:
Loopback0, owned by OLNK
(192.168.20.138/32,
239.1.1.1/32)
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, owned by OLNK
Outgoing interface list:
Loopback0, owned by OLNK
Relevant command:
Display PIM-DM
multicast routing list information.
show ip mroute pim-dm [group-address]
[source]
Parameter:
group-address |
(可选)group address |
source |
(可选)source address |
Default:
none
Command mode:
The mode except
user mode.
Explanation:
It can display
all (S,G) or specified (S,G) only in local MRT.
Example:
Example1:
Display all (S,G) in local MRT.
Router#show
ip mroute pim-dm
PIM-DM
Multicast Routing Table
Timers:
Uptime/Expires
State:
Interface state
RPF nbr: RPF
neighbor address
(192.168.20.151,
224.1.1.1), 00:00:03
/00:03:27
Incoming interface:
Ethernet2/1 Forwarding 0.0.0.0
Outgoing interface list:
Loopback1 NoInfo 00:00:07 /00:00:00
(192.168.20.138,
239.1.1.1), 00:00:03
/00:03:27
Incoming interface:
Ethernet2/1 Forwarding 0.0.0.0
Outgoing interface list:
Loopback1 NoInfo 00:00:07 /00:00:00
Ethernet1/1 NoInfo
00:02:43 /
Example 2: Display the specified (S,G) in
local MRT.
Router#show ip mroute pim-dm 224.1.1.1
PIM-DM Multicast Routing Table
Timers: Uptime/Expires
State: Interface state
RPF nbr: RPF neighbor address
(192.168.20.151, 224.1.1.1), 00:00:01 /00:03:29
Incoming interface:
Ethernet2/1 Forwarding 0.0.0.0
Outgoing interface list:
Loopback1 NoInfo 00:03:50 /
Example 2: Display the specified (S,G) in
local MRT.
Router#show ip mroute pim-dm 224.1.1.1 192.168.20.131
PIM-DM Multicast
Routing Table
You can use this command “show ip mroute mstatic” to
display olnk multicast routing list information.
show ip mroute olnk [group-address
| statistics]
Parameter:
group-address |
The specified group address |
mask |
Routing item statistic information |
default:
none
Command mode:
Supervisor mode
explanation:
Each
multicast routing protocol has a multicast routing list at local, which has the
similar structure to the global multicast forwarding list, including some
related information with protocol.
example:
The following example will display olnk multicast routing list
information:
router#show
ip mroute olnk
IGMP
only-link Multicast Routing Table
Timers: Uptime/Expires
Total Group: 6
Total (S,G): 4
(192.168.20.1/32,
225.1.1.1/32) 00:01:46/00:00:05 Packets: 22
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, Owner: OLNK, Packets: 35
Outgoing interface list:
Loopback0
Packets out: 35
(192.168.20.141/32,
225.1.1.1/32) 00:00:10/00:00:05 Packets: 3
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, Owner: OLNK, Packets: 3
Outgoing interface list:
Loopback0
Packets out: 3
(192.168.20.110/32,
239.0.0.101/32) 00:08:52/00:00:05 Packets: 532
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, Owner: OLNK, Packets: 532
Outgoing interface list:
Loopback0
Packets out: 532
(192.168.20.138/32,
239.1.1.1/32) 01:40:54/00:00:05 Packets: 6052
Incoming interface: Ethernet0/2, RPF
nbr 0.0.0.0, Owner: OLNK, Packets: 6052
Outgoing interface list:
Loopback0
Packets out: 4066
show ip mroute static
You can use “show ip mroute mstatic” to display information
on static multicast routing.
show ip mroute static
Parameter:
none
default:
none
Command mode:
Supervisor mode
explanation:
use “show ip mroute static” to see the static multicast routing
configured by the “ip mroute” command.
example:
The following example will display the static multicast routing
configuration information:
router#show
ip mroute static
Mroute:
200.1.1.1/24, RPF nbr: 192.168.20.1, RPF interface: Ethernet0/2
Administrative distance: 0, metric: 0, valid: TRUE
Mroute:
201.1.1.1/24, RPF nbr: 192.168.20.1, RPF interface: Serial0/0
Administrative distance: 0, metric: 0, valid: FALSE
show ip rpf olnk
use “show ip rpf olnk” to display RPF information on which
olnk to reach multicast source:
show ip rpf olnk
Parameter:
none
default:
none
Command mode:
Supervisor mode
explanation:
You can use this command to see the RPF information of specified
multicast source. such as RPF interface, RPF neighbor address, network number,
mask and routing information.
example:
The following example will display RPF information on which olnk
reaches multicast source 192.168.20.1:
router#show
ip rpf olnk 192.168.20.1
RPF
information for (192.168.20.1)
RPF interface: Ethernet0/2
RPF neighbor: 0.0.0.0
RPF route/mask: 192.168.20.1/24
RPF type: connect (ucast)
Metric preference: 0
Metric: 0
Relevant command:
Display the PIM-DM neighbor and selected DR.
show ip pim-dm
neighbor [interface-type interface-number]
Parameter:
interface-type
interface-number:Optional .interface type and number (e.g.
Ethernet1/1,Seria11/0 and so on).
Default:
none
Command mode:
Other mode except user mode
Explanation:
You can
use this command to determine
which router configuration is running PIM-DM or PIM-SM on LAN.
Example:
Example 1:
Router#show ip pim-dm
neighbor
PIM-DM Neighbor Table
Neighbor
Interface Uptime/Expires
Ver DR Prior/Mode
Address
192.167.20.132
Ethernet1/1
1.1.1.1
Loopback1
192.168.20.132
Ethernet2/1
192.168.20.152
Ethernet2/1
192.168.20.204
Ethernet2/1
Example 2:
Router# show ip pim-dm neighbor Ethernet2/1
PIM-DM Neighbor Table
Neighbor Interface
Uptime/Expires Ver DR Prior/Mode
Address
192.168.20.132
Ethernet2/1
192.168.20.152
Ethernet2/1
192.168.20.204
Ethernet2/1
Relevant
command:
Commands |
Description |
Running multicast protocol type. |
|
ip pim-dm dr-priority |
DR priority. |
Hello counter interval. |
|
Pim version. |
|
Neighbor filter list. |
|
PIM-DM port neighbor information. |
You can use this command to display the overall status for PIM-DM port.
show ip pim-dm interface [interface-type interface-number] [count][detail]
Parameter:
interface-type:optional .interface type and number (e.g. Ethernet1/1,Seria11/0 and so on).
Default:
none
Command mode:
Other mode except
user mode
Explanation:
This command displays only the port where PIM-DM is configured. If you didn’t specify any port, it will display all pim-dm interfaces information.
Example:
Example 1:
Router#show ip pim interface
address
Interface Ver/ Nbr Hello
DR
DR
Mode Count intvl Prior
192.167.20.132 Ethernet1/1 v2/D 0 30 4 192.167.20.132
1.1.1.1
Loopback1 v2/D 0 30 1 1.1.1.1
192.168.20.132 Ethernet2/1 v2/D 2 30 1 192.168.20.204
Example 2:
Router#show ip pim interface Ethernet2/1
address
Interface Ver/ Nbr Hello
DR
DR
Mode Count intvl Prior
192.168.20.132 Ethernet2/1 v2/D 2 30 1 192.168.20.204
Relevant
command:
Commands |
Description |
Running multicast protocol type. |
|
ip pim-dm dr-priority |
DR priority. |
Hello counter interval. |
|
Pim version. |
|
Neighbor filter list. |
|
PIM-DM port neighbor information. |
You can use this command to display the way how a multicast routing performs reverse path forwarding.
show ip rpf pim-dm source-address
Parameter:
source-address: displays the RFP information of specified source address.
Default:
none
Command mode:
Other mode except user mode
Explanation:
The pim-dm routing protocol can get the reverse path forwarding information from various type of routing lists (unicast routing list, DVMRP routing list or configured static multicast routing). This command also indicates the users where the RPF information is get from.
Example:
Router#show ip rpf pim 4.1.1.1
RPF information for (4.1.1.1)
RPF interface: Ethernet2/1
RPF neighbor: 192.168.20.80
RPF route/mask: 192.168.20.0/24
RPF type: unicast
Metric preference: 120
Metric: 1