Gebruiksaanwijzing /service van het product IPMC5000PEF van de fabrikant Brocade Communications Systems
Ga naar pagina of 230
53-1003085-02 17 February 2014 FastIron Ethernet Switch IP Multicast Configuration Guide Supporting FastIron Software Release 08.0.10a.
© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScr.
Contents Preface..................................................................................................................................... 7 Document conventions...............................................................................
Enabling IGMP V3 membership tracking and fast leave for the VLAN........................................................................................... 24 Enabling fast leave for IGMP V2....................................................... 25 Enabling fast convergence .
Configuring the MLD version for individual ports................................ 53 Configuring static groups.................................................................... 53 Configuring static router ports.......................................
Initiating PIM multicasts on a network............................................... 82 Pruning a multicast tree.................................................................... 82 Grafts to a multicast tree........................................
IGMP proxy limitations...................................................................... 144 Configuring IGMP Proxy................................................................... 144 Filtering groups in proxy report messages...................
Clearing IPv6 MLD traffic................................................................ 206 Clearing the IPv6 MLD group membership table cache................. 206 IPv6 Multicast Boundaries............................................................
Preface ● Document conventions...................................................................................................... 7 ● Brocade resources.............................................................................................
Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [ ] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets.
Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at www.brocade.com . • Adapter documentation is available on the Downloads and Documentation for Brocade Adapters page.
Document feedback To send feedback and report errors in the documentation you can use the feedback form posted with the document or you can e-mail the documentation team. Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document.
About This Guide ● Introduction..................................................................................................................... 11 ● What’s new in this document................................................................
How command information is presented in this guide For all new content, command syntax and parameters are documented in a separate command reference section at the end of the publication.
IPv4 Multicast Traffic Reduction ● Supported IPv4 Multicast Traffic Reduction.................................................................... 13 ● IGMP snooping overview..........................................................................
membership information by processing the IGMP reports and leave messages, so traffic can be forwarded to ports receiving IGMP reports. An IPv4 multicast address is a destination address in the range of 224.0.0.0 to 239.255.255.255. Addresses of 224.0.
multiple devices are configured as queriers, Brocade recommends that only one device (preferably the one with the traffic source) is configured as a querier. The non-queriers always forward multicast data traffic and IGMP messages to router ports which receive IGMP queries or PIM hellos.
On both switch and router software images, IGMP snooping is either *,G based or S,G based. The hardware can either match the group address only (* G), or both the source and group (S, G) of the data stream. This is 32-bit IP address matching, not 23-bit multicast MAC address 01-00-5e-xx-xx-xx matching.
• A user can configure static router ports to force all multicast traffic to these specific ports. • If a VLAN has a connection to a PIM-enabled port on another router, the VLAN must be configured as a non-querier (passive).
• Configuring the IGMP mode for a VLAN (active or passive) • Disabling IGMP snooping on a VLAN • Configuring the IGMP version for a VLAN • Configuring static router ports • Turning off stati.
Setting the maximum number of IGMP group addresses The configured number of IGMP group addresses is the upper limit of an expandable database. Client memberships exceeding the group limit are not processed. Configure the system-max igmp-snoop- group-addr command to define the maximum number of IGMP group addresses.
this case, enable the active IGMP mode on only one of the devices and leave the other devices configured for passive IGMP mode. • Passive - When passive IGMP mode is enabled, it forwards reports to the router ports which receive queries. IGMP snooping in the passive mode does not send queries.
Configuring the IGMP version for individual ports in a VLAN You can specify the IGMP version for individual ports in a VLAN. For example, the following commands configure ports 4, 5, and 6 to use IGMP V3. The other ports either use the IGMP version specified with the multicast version command, or the globally-configured IGMP version.
Disabling IGMP snooping on a VLAN When IGMP snooping is enabled globally, you can still disable it for a specific VLAN. For example, the following commands cause IGMP snooping to be disabled for VLAN 20.
Configuring report control A device in passive mode forwards reports and leave messages from clients to the upstream router ports that are receiving queries. You can configure report control to rate-limit report forwarding within the same group to no more than once every 10 seconds.
Enabling or disabling error and warning messages The device prints error or warning messages when it runs out of software resources or when it receives packets with the wrong checksum or groups. These messages are rate-limited. You can turn off these messages by entering the following command.
device immediately stops forwarding traffic to the interface. This feature requires the entire VLAN be configured for IGMP V3 with no IGMP V2 clients. If a client does not send a report during the specified group membership time (the default is 260 seconds), that client is removed from the tracking list.
Syntax: multicast fast-convergence IGMP snooping show commands This section describes the show commands for IGMP snooping. Displaying the IGMP snooping configuration To display the global IGMP snooping configuration, enter the show ip multicast command at any level of the CLI.
Field Description rtr port The router ports, which are the ports receiving queries. Displaying IGMP snooping errors To display information about possible IGMP errors, enter the show ip multicast error command.
group: 226.1.1.1, EX, permit 0 (source, life): life=120, deny 0: If the tracking and fast leave features are enabled, you can display the list of clients that belong to a particular group by entering the following command. device#show ip multicast group 224.
System Parameters Default Maximum Current Configured igmp-snoop-mcache 512 8192 300 300 The IGMP snooping mcache contains multicast forwarding information for VLANs. To display information in the multicast forwarding mcache, enter the show ip multicast mcache command.
Field Description alloc The allocated number of units. in-use The number of units which are currently being used. avail The number of available units. get-fail This displays the number of resource failures. NOTE It is important to pay attention to this field.
Field Description Qry General Query QryV2 Number of general IGMP V2 queries received or sent. QryV3 Number of general IGMP V3 queries received or sent. G-Qry Number of group-specific queries received or sent. GSQry Number of group source-specific queries received or sent.
Displaying the active interface with no other querier present The following example shows the output in which the VLAN interface is active and no other querier is present with the lowest IP address.
1/1/16 has 4 groups, This interface is Querier default V2 group: 226.6.6.6, life = 240 group: 228.8.8.8, life = 240 group: 230.0.0.0, life = 240 group: 224.4.4.4, life = 240 1/1/24 has 1 groups, This interface is Querier default V2 group: 228.8.8.8, life = 240 2/1/16 has 4 groups, This interface is Querier default V2 group: 226.
default V2 **** Warning! has V3 (age=0) nbrs group: 234.4.4.4, life = 260 group: 226.6.6.6, life = 260 3/1/1 has 4 groups, This interface is non-Querier (passive) default V2 group: 238.8.8.8, life = 260 group: 228.8.8.8, life = 260 group: 230.0.0.0, life = 260 group: 224.
Clearing IGMP counters on VLANs To clear IGMP snooping on error and traffic counters for all VLANs, enter the clear ip multicast counters command. device#clear ip multicast counters Syntax: clear ip m.
device receives a join message or group membership report for a group, the device forwards subsequent traffic for that group only on the ports from which the join messages or IGMP reports were received. In this example, the router connected to the receiver for group 239.
NOTE This example assumes that the devices are actually Brocade devices running Layer 2 Switch software. FIGURE 1 PIM SM traffic reduction in Global Ethernet environment The devices on the edge of the Global Ethernet cloud are configured for IGMP snooping and PIM SM traffic snooping.
NOTE Use the passive mode of IGMP snooping instead of the active mode. The passive mode assumes that a router is sending group membership queries as well as join and prune messages on behalf of receivers. The active mode configures the device to send group membership queries.
This command enables PIM SM traffic snooping. The PIM SM traffic snooping feature assumes that the network has routers that are running PIM SM. NOTE The device must be in passive mode before it can be configured for PIM SM snooping. To disable the feature, enter the no ip pimsm-snooping command.
1 (age=60) 1 has 1 src: 10.20.20.66(60) 2 (* 230.2.2.2) has 1 pim join ports out of 1 OIF 1 (age=60) 1 has 1 src: 10.20.20.66(60) This output shows the number of PIM join OIF out of the total OIF.
Field Description Multicast Group The IP address of the multicast group. NOTE The fid and camindex values are used by Brocade Technical Support for troubleshooting. Forwarding Port The ports attached to the group receivers. A port is listed here when it receives a join message for the group, an IGMP membership report for the group, or both.
Field Description age The age of the port, in seconds. src The source address and age. The age (number of seconds) is indicated in brackets immediately following the source.
IPv6 Multicast Traffic Reduction ● IPv6 Multicast Traffic Reduction...................................................................................... 43 ● MLD snooping overview...................................................................
ports without going through the CPU. If there is no client report, the hardware resource drops the data stream. MLD protocols provide a way for clients and a device to exchange messages, and allow the device to build a database indicating which port wants what traffic.
Forwarding mechanism in hardware IP-based forwarding implementation on FCX and ICX devices The following information about *,G or S,G fdb-based implementation is specific to FCX, ICX 6610, ICX 6430, ICX 6450, and ICX 6650 devices. On both switch and router software images, MLD snooping is either *,G based or S,G based.
is unable to install resources for a specific matching address due to hashing collision. The hardware hashes addresses into available entries, with some addresses hashed into the same entry. If the collision number in an entry is more than the hardware chain length, the resource cannot be installed.
Because Brocade does not support MRD, this can lead to stream loss when non-Querier router ports age out on the Querier after the initial Query election. To avoid such stream loss, configure a static router port on the querier on each interface that connects to a non-querier snooping device.
MLD and VLAN configuration You can configure MLD snooping on some VLANs or all VLANs. Each VLAN can be independently enabled or disabled for MLD snooping, or can be configured with MLDv1 or MLDv2. In general, the IPv6 MLD snooping commands apply globally to all VLANs except those configured with VLAN- specific MLD snooping commands.
Configuring the hardware and software resource limits The system supports up to 8K of hardware-switched multicast streams. The following are the resource limits: • The default is 512 for most devices; for ICX 6430 devices the default is 256. • FCX, FSX, ICX 6610, ICX 6450 and ICX 6650 devices support up to 8192 MLD snooping mcache entries.
Omitting both the active and passive keywords is the same as entering ipv6 multicast passive . NOTE The ipv6 mld-snooping command is replaced by the ipv6 multicast command; the mld-snooping command is replaced by the multicast6 command.
Configuring report control When a device is in passive mode, it forwards reports and leave messages from clients to the upstream router ports that are receiving queries. You can configure report control to rate-limit report forwarding for the same group to no more than once per 10 seconds.
Disabling error and warning messages Error or warning messages are printed when the device runs out of software resources or when it receives packets with the wrong checksum or groups. These messages are rate limited. You can turn off these messages by entering the ipv6 multicast verbose-off command.
Configuring the MLD version for individual ports You can specify the MLD version for individual ports in a VLAN. For example, the following commands configure ports 1/4, 1/5, 1/6 and 2/1 to use MLDv2. The other ports use the MLD version specified with the multicast6 version command, or the globally configured MLD version.
Syntax: [no] multicast6 proxy-off By default, MLD snooping proxy is enabled. Enabling MLDv2 membership tracking and fast leave for the VLAN MLDv2 provides membership tracking and fast leave services to clients.
Enabling fast convergence In addition to periodically sending general queries, an active (querier) device sends out general queries when it detects a new port. However, since it does not recognize the other device port-up event, the multicast traffic might still use the query-interval time to resume after a topology change.
Displaying MLD group information To display default, maximum, current, and configured values for system maximum parameters, use the show default values command. The following output example does not show complete output; it shows only MLD group values.
Field Description ST Yes indicates that the MLD group was configured as a static group; No means it was learned from reports. QR Yes means the port is a querier port; No means it is not. A port becomes a non-querier port when it receives a query from a source with a lower source IP address than the port.
Field Description (abcd:ef50 0:100): The lowest 32 bits of source and group. It is displayed in XXXX:XXXX hex format. Here XXXX is a 16-bit hex number. cnt The number of packets processed in software. OIF Output interfaces. age The mcache age in seconds.
Field Displays get-mem The current memory allocation. This number should continue to increase. size The size of a unit (in bytes). init The initial allocated amount of memory. NOTE This number can be increased. (More memory can be allocated if necessary.
Field Description MbrV2 The MLDv2 membership report. IsIN Number of source addresses that were included in the traffic. IsEX Number of source addresses that were excluded in the traffic. ToIN Number of times the interface mode changed from EXCLUDE to INCLUDE.
Field Description QR Indicates that the port is a querier. Clearing MLD snooping counters and mcache The clear commands for MLD snooping should only be used in troubleshooting situations or when recovering from error conditions.
Disabling the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN NOTE Disabling the flooding of unregistered IPv6 multicast frames in an MLD-snooping-enabled VLAN is supported only on ICX 6650 devices.
Notice that the receiver for group ff1e::3:4 is directly connected to the device. As a result, the device does not see a join message on behalf of the client. However, because MLD snooping also is enabled, the device uses the MLD group membership report from the client to select the port for forwarding traffic to group ff1e::3:4 receivers.
NOTE This example assumes that the devices are actually Brocade devices running Layer 2 Switch software. FIGURE 2 PIM6 SM traffic reduction in Global Ethernet environment The devices on the edge of the Global Ethernet cloud are configured for MLD snooping and PIM6 SM traffic snooping.
• All the device ports connected to the source and receivers or routers must be in the same port- based VLAN. • The PIM6 SM snooping feature assumes that the group source and the device are in different subnets and communicate through a router. The source must be in a different IP subnet than the receivers.
To disable PIM6 SM snooping, enter the no ipv6 pimsm-snooping command. device(config)#no ipv6 pimsm-snooping If you also want to disable IP multicast traffic reduction, enter the no ipv6 multicast command.
1/1/2 has 1 src: 15::11(0), 2/1/3 has 1 src: 15::11(0), 2 (0:16 1:3) has 2 pim join ports out of 2 OIF 2/1/3 (age=0), 1/1/2 (age=0), 1/1/2 has 1 src: 15::16(0), This output shows the number of PIM join OIF out of the total OIF. The join or prune messages are source-specific.
Displaying PIM6 SM snooping for a VLAN 68 FastIron Ethernet Switch IP Multicast Configuration Guide 53-1003085-02.
IPv4 Multicast Protocols ● Supported IPv4 Multicast Protocols features.................................................................. 69 ● Overview of IP multicasting..............................................................................
Feature ICX 6430 ICX 6450 FCX ICX 6610 ICX 6650 FSX 800 FSX 1600 ICX 7750 PMRI No 08.0.01 1 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 PIM-SSM No 08.0.01 1 08.0.01 08.0.01 08.0.01 08.0.01 08.0.10 Multi-VRF support No 08.0.01 1 08.0.01 08.0.01 08.0.01 08.
Overview of IP multicasting Multicast protocols allow a group or channel to be accessed over different networks by multiple stations (clients) for the receipt and transmission of multicast data.
The following new runtime commands have been introduced: max-mcache This command is described in the “Defining the maximum number of PIM cache entries” section.
Defining the maximum number of PIM cache entries You can use the following run-time command to define the maximum number of repeated PIM traffic being sent from the same source address and being received by the same destination address. To define this maximum for the default VRF, enter the following commands.
Changing IGMP V1 and V2 parameters IGMP allows Brocade devices to limit the multicast of IGMP packets to only those ports on the device that are identified as IP Multicast members.
Syntax:[no] ip igmp max-response-time num The num variable specifies the number of seconds and can be a value from 1 to 25. The default is 10. Security enhancement for IGMP A security enhancement was .
To display static multicast groups in the default VRF, enter the following command. device#show ip igmp static Group Address Interface Port List ---------------------------------- 224.
Syntax: ip multicast-nonstop-routing During a hitless upgrade and switchover, this syslog message is generated on the CLI. The message displayed depends on which version of PIM is configured.
The vrf parameter allows you to display IP PIM counters for the VRF instance specified by the vrf- name variable. The following table displays the output from the show ip pim counter nsr command. This field... Displays... Mcache sync The mcache NSR sync queue that carries the NSR sync message for mcache updates.
Configuring PMRI PMRI is enabled by default. To disable PMRI, enter commands such as the following. device(config)# router pim device(config-pim-router)# hardware-drop-disable Syntax: [no] hardware-drop-disable Displaying hardware-drop Use the show ip pim sparse command to display if the hardware-drop feature has been enabled or disabled.
• When a boundary is applied to an ingress interface, all packets destined to a multicast group that is filtered out will be dropped by software. Currently, there is no support to drop such packets in hardware.
|Address | | |Address Port|Thr|Boundary | | Prio | Interval ---------+---------------+----+---+-----------------------+---+---------+------- +------+---------+ e1/1/7 30.
PIM was introduced to simplify some of the complexity of the routing protocol at the cost of additional overhead tied with a greater replication of forwarded multicast packets. PIM builds source-routed multicast delivery trees and employs reverse path check when forwarding multicast packets.
sends a prune message to R1. With R4 in a prune state, the resulting multicast delivery tree would consist only of leaf nodes R2 and R3. FIGURE 3 Transmission of multicast packets from the source to h.
Grafts to a multicast tree A PIM device restores pruned branches to a multicast tree by sending graft messages towards the upstream device. Graft messages start at the leaf node and travel up the tree, first sending the message to its neighbor upstream device.
PIM DM versions The Brocade device supports only PIM V2. PIM DM V2 sends messages to the multicast address 224.0.0.13 (ALL-PIM-ROUTERS) with protocol number 103. Configuring PIM DM NOTE This section describes how to configure the "dense" mode of PIM, described in RFC 1075.
The [no] router pim vrf command behaves in the following manner: • Entering the router pim vrf command to enable PIM does not require a software reload. • Entering a no router pim vrf command removes all configuration for PIM multicast on the specified VRF.
The default is 105 seconds. The range is 3 to 65535 seconds. Modifying hello timer This parameter defines the interval at which periodic hellos are sent out PIM interfaces. Devices use hello messages to inform neighboring devices of their presence. The interval can be set between 10 and 3600 seconds, and the default rate is 30 seconds.
Modifying graft retransmit timer The graft retransmit timer defines the interval between the transmission of graft messages. A graft message is sent by a device to cancel a prune state. When a device receives a graft message, the device responds with a Graft Ack (acknowledge) message.
Configuring a DR priority The DR priority option lets you give preference to a particular device in the DR election process by assigning it a numerically higher DR priority.
Field Description Inactivity interval How long a forwarding entry can remain unused before the device deletes it. Hardware Drop Enabled Displays Yes if the Passive Multicast Route Insertion feature is enabled and No if it is not.
IP Multicast Mcache Table Entry Flags : SM - Sparse Mode, SSM - Source Specific Multicast, DM - Dense Mode RPT - RPT Bit, SPT - SPT Bit, LSRC - Local Source, LRCV - Local Receiver HW - HW Forwarding E.
Output fields from the show ip pim mcache command (Continued) TABLE 1 Field Description BF Blocked Filter BI Blocked IIF Uptime Shows the software entry uptime.
Output fields from the show ip pim mcache command (Continued) TABLE 1 Field Description AgeSltMsk Shows the slot number on which active module expects ingress traffic. This value is 1 if the entry is programmed in hardware and is 0 if the entry is not programmed in hardware.
Output fields from the show ip pim mcache command (Continued) TABLE 1 Field Description Flags (explanation of flags in the OIF section) Shows the flags set in each of the Outgoing interface in abbreviated string format whose explanations are as follows.
bsr Bootstrap router flow-count Show flowcache counters hw-resource PIM hw resources interface PIM interface neighbor PIM neighbor states resource PIM resources rp-set List of rendezvous point (RP) candidates traffic Active multicast traffic PIM Sparse Brocade devices support Protocol Independent Multicast (PIM) Sparse version 2.
• PMBR - A PIM device that has some interfaces within the PIM domain and other interface outside the PIM domain. PBMRs connect the PIM domain to the Internet. • BSR - The Bootstrap Router (BSR) distributes RP information to the other PIM Sparse devices within the domain.
‐ Identify the Brocade device as a candidate PIM Sparse Bootstrap Router (BSR), if applicable. ‐ Identify the Brocade device as a candidate PIM Sparse Rendezvous Point (RP), if applicable. ‐ Specify the IP address of the RP (if you want to statically select the RP).
• Entering the router pim vrf command to enable PIM does not require a software reload. • Entering a no router pim vrf command removes all configuration for PIM multicast on the specified VRF.
The numhash-mask-length variable specifies the number of bits in a group address that are significant when calculating the group-to-RP mapping. You can specify a value from 1 to 32. NOTE it is recommended that you specify 30 for IP version 4 (IPv4) networks.
add a range, you override the default. The device then becomes a candidate RP only for the group address ranges you add. You also can delete the configured rp-candidate group ranges by entering the following command. device(config-pim-router)# rp-candidate delete 224.
ACL based RP assignment The rp-address command allows multiple static rendezvous point (RP) configurations. For each static RP, an ACL can be given as an option to define the multicast address ranges that the static RP permit or deny to serve. A static RP by default serves the range of 224.
------------------------------------------- 1 225.1.1.1 25.0.0.25 2 225.1.1.2 25.0.0.25 3 225.1.1.3 25.0.0.25 4 225.1.1.4 25.0.0.25 5 225.1.1.5 25.0.0.25 PIM Passive PIM Passive is used to reduce and minimize unnecessary PIM Hello and other PIM control messages.
NOTE IPv4 multicast routes do not share hardware replication table entries with IPv6 multicast routes even if they share the same OIF lists. Displaying system values To display default, maximum, current, and configured values for system maximum parameters, use the show default values command.
Total hw w/Tag MVID entries 0 Total hw w/Tag invalid MVID entries 0 Syntax: show ip pim [ all-vrf | [ vrf vrf-name ] ] resource The vrf parameter allows you to display hardware resource information for the VRF instance identified by the vrf-name variable.
Output from the show ip pim all-vrf hw-resource command TABLE 3 Field Description VRF Name of the VRF. Usage Number of allocated SG entries in this VRF. Fail Number of failures while allocating SG entries in this VRF (due to the system-max limit. Total usage Total number of SG entries in the system (all VRFs).
The vrf keyword allows you to display PIM sparse configuration information for the VRF instance identified by the vrf-name variable. This example shows the PIM Sparse configuration information on PIM Sparse device A in Figure 5 on page 95. The following table shows the information displayed by the show ip pim sparse command.
Output of the show ip pim sparse command (Continued) TABLE 4 This field... Displays... Bootstrap Msg interval How frequently the BSR configured on the device sends the RP set to the RPs within the PIM Sparse domain. The RP set is a list of candidate RPs and their group prefixes.
Group member at e2/9: v59 Group member at e1/16: v57 3 Group 226.0.120.0 Group member at e2/9: v59 Group member at e1/16: v57 4 Group 226.0.163.0 Group member at e2/9: v59 Group member at e1/16: v57 5 Group 226.0.206.0 Group member at e2/9: v59 Group member at e1/16: v57 6 Group 226.
This example shows information displayed on a device that has been elected as the BSR. The next example shows information displayed on a device that is not the BSR.
Output from the show ip pim bsr command (Continued) TABLE 6 This field... Displays... RP Indicates the IP address of the Rendezvous Point (RP). NOTE This field appears only if this device is a candidate BSR. group prefixes Indicates the multicast groups for which the RP listed by the previous field is a candidate RP.
Output from the show ip pim rp-candidate command TABLE 7 This field... Displays... Candidate-RP-advertisement in Indicates how time will pass before the BSR sends the next RP message. The time is displayed in "hh:mm:ss" format. NOTE This field appears only if this device is a candidate RP.
Output of the show ip pim rp-map command TABLE 8 This field... Displays... Group address Indicates the PIM Sparse multicast group address using the listed RP. RP address Indicates the IP address of the Rendezvous Point (RP) for the listed PIM Sparse group.
Number of group prefixes Learnt from BSR: 1 Group prefix = 224.0.0.0/4 # RPs expected: 2 # RPs received: 2 RP 1: 1.51.51.1 priority=0 age=60 holdtime=150 RP 2: 1.
The vrf option allows you to display information about the PIM neighbors for the VRF instance identified by the vrf-name variable. The following table describes the output from this command. Output from the show ip pim vrf neighbor command TABLE 11 This field.
e4/29(VL13), 00:03:12/0, Flags: MJ e5/2(VL1004), 00:03:12/0, Flags: MJ L2 (HW) 1: e5/2, 00:00:07/0, Flags: MJ L2 MASK: ethe 5/2 Src-Vlan: 1001 Syntax: show ip pim [ vrf vrf-name ] mcache [ source-addr.
Output fields from the show ip pim mcache command (Continued) TABLE 12 Field Description upstream neighbor Shows the upstream neighbor for the Source/RP based on the type of entry. For (*,G) it shows the upstream neighbor towards the RP. For (S,G) entries it shows the upstream neighbor towards the source.
Output fields from the show ip pim mcache command (Continued) TABLE 12 Field Description Profile Shows the Profile ID associated with the Stream. Number of matching entries Shows the total number of mcache entries matching a particular multicast filter specified.
HW - HW Forwarding Enabled, FAST - Resource Allocated, TAG - Need For Replication Entry REGPROB - Register In Progress, REGSUPP - Register Suppression Timer MSDPADV - Advertise MSDP, NEEDRTE - Route R.
------+---------+-----------+---------+---------+---------+---------+---------+--- v30 0 0 0 0 0 0 0 0 v50 2526 1260 0 0 0 1263 0 0 v150 2531 0 0 0 0 1263 0 0 v200 2531 0 0 0 0 1 0 0 Port HELLO JOIN-PRUNE ASSERT REGISTER REGISTER BOOTSTRAP CAND. RP Err GRAFT(DM) STOP(SM) MSGS (SM) ADV.
NOTE If you have configured interfaces for standard PIM (dense mode) on the device, statistics for these interfaces are listed first by the display. The following table describes the output for this show command. Output from the show ip pim vrf traffic command TABLE 13 This field.
Displaying PIM RPF The show ip pim rfp command displays what PIM sees as the reverse path to the source as shown in the following. While there may be multiple routes back to the source, the one displayed by this command is the one that PIM thinks is best.
information with other PIM Sparse domains by communicating with RPs in other domains that are running MSDP. The RP sends the source information to each peer through a Source Active message. The message contains the IP address of the source, the group address to which the source is sending, and the IP address of the RP.
Configuring MSDP To configure MSDP, perform the following tasks: • Enable MSDP. • Configure the MSDP peers. NOTE The PIM Sparse Rendezvous Point (RP) is also an MSDP peer. NOTE Devices that run MSDP usually also run BGP. The source address used by the MSDP device is normally configured to be the same source address used by BGP.
The connect-source loopback num parameter specifies the loopback interface you want to use as the source for sessions with the neighbor and must be reachable within the VRF. NOTE It is strongly recommended that you use the connect-source loopback num parameter when issuing the msdp-peer command.
device(config)# router msdp vrf blue device(config-msdp-router-vrf blue)# originator-id loopback 2 device(config-msdp-router-vrf blue)# exit Syntax: [no] originator-id type number The originator-id command instructs MSDP to use the specified interface IP address as the IP address of the RP in an SA message.
device(config)# route-map msdp2_map permit 1 device(config-routemap msdp2_map)# match ip address 125 device(config-routemap msdp2_map)# exit device(config)# route-map msdp2_rp_map deny 1 device(config.
Filtering advertised Source-Active messages The following example configures the device to advertise all source-group pairs except the ones that have source address 10.x.x.x. The following commands configure extended ACLs to be used in the route map definition.
KA: Keepalive SA:Source-Active NOT: Notification Peer Address Peer As State KA SA NOT Age In Out In Out In Out 40.40.40.1 1001 ESTABLISH 59 59 0 0 0 0 6 40.40.40.3 1001 ESTABLISH 59 59 0 0 0 0 47 47.1.1.2 N/A ESTABLISH 59 59 0 0 0 0 47 Brocade(config)# Syntax: show ip msdp summary The following table describes the output from this command.
TotalRcv: 49 RcvQue: 0 SendQue: 0 Input SA Filter:Not Applicable Input (S,G) route-map:None Input RP route-map:None Output SA Filter:Not Applicable Output (S,G) route-map:None Output RP route-map:None Syntax: show ip msdp [ vrf vrf-name ] peer The following table describes the output from this command.
MSDP peer information (Continued) TABLE 15 This field... Displays... Notification Message Error Code Received The MSDP device has received a notification message from the neighbor that contains an error code corresponding to one of the following errors.
MSDP peer information (Continued) TABLE 15 This field... Displays... TCP connection state The state of the connection with the neighbor. Can be one of the following: • LISTEN - Waiting for a connection request. • SYN-SENT - Waiting for a matching connection request after having sent a connection request.
MSDP peer information (Continued) TABLE 15 This field... Displays... TotalRcv The number of sequence numbers received from the neighbor. RcvQue The number of sequence numbers in the receive queue. SendQue The number of sequence numbers in the send queue.
MSDP source active cache (Continued) TABLE 16 This field... Displays... Orig Peer The peer from which this source-active entry was received. Age The number of seconds the entry has been in the cache You can use the following command to filter the output to display only the entries matching a specific source.
Displaying MSDP Peer To display MSDP peer information, enter the following command. Brocade# show ip msdp peer 40.40.40.3 MSDP Peer Status Summary KA: Keepalive SA:Source-Active NOT: Notification Peer Address Peer As State KA SA NOT Age In Out In Out In Out 40.
Clearing the source active cache To clear the source active cache, enter the following command at the Privileged EXEC level of the CLI. device# clear ip msdp sa-cache Syntax: clear ip msdp sa-cache [ ip-addr ] The command in this example clears all the cache entries.
mesh group. An RP can forward an SA message to any MSDP router as long as that peer is farther away from the originating RP than the current MSDP router. The following figure shows an example of an MSDP mesh group. In a PIM-SM mesh group the RPs are configured to be peers of each other.
Syntax: [no] mesh-group group-name peer-address The sample configuration above reflects the configuration in Figure 7 on page 136. On RP 206.251.21.31 you specify its peers within the same domain (206.
NOTE The anycast RP address *must* not be the IGP router-id. • Enable PIM-SM on all interfaces on which multicast routing is desired. • Enable an IGP on each of the loopback interfaces and physical interfaces configured for PIM-SM. • Configure loopback interfaces with unique IP addresses on each of the RPs for MSDP peering.
The configuration examples demonstrate the commands required to enable this application. FIGURE 8 Example of a MDSP Anycast RP network RP 1 configuration The following commands provide the configuration for the RP 1 router in Figure 8 .
RP1(config)# router pim RP1(config-pim-router)# rp-candidate loopback 1 RP1(config-pim-router)# exit RP1(config)# router msdp RP1(config-msdp-router)# msdp-peer 10.1.1.2 connect-source loopback 2 RP1(config-msdp-router)# originator-id loopback 2 RP 2 configuration The following commands provide the configuration for the RP 2 router in Figure 8 .
PIMR2 configuration The following commands provide the configuration for the PIMR2 router in Figure 8 . PIMR2(config)#router ospf PIMR2(config-ospf-router)# area 0 PIMR2(config-ospf-router)# exit PIMR.
as a router-id. A PIM First Hop router will register the source with the closest RP. The first RP that receives the register will re-encapsulate the register to all other Anycast RP peers. Please refer to Figure 9 as described in the configuration of PIM Anycast RP 100.
The following table describes the parameters of the show ip pim anycast-rp command: Display of show ip pim anycast-rp TABLE 17 This field... Displays... Number of Anycast RP: The Number of Anycast RP specifies the number of Anycast RP sets in the multicast domain.
Configure the route-precedence command to specify a precedence table that dictates how routes are selected for multicast. IGMP Proxy IGMP Proxy provides a means for routers to receive any or all multicast traffic from an upstream device if the router is not able to run PIM and runs only IGMP.
1. Configure router PIM globally. device(config)#router pim 2. Configure an IP address on the interface (physical, virtual routing, or tunnel interface) that will serve as the IGMP proxy for an upstream device by entering commands such as the following.
Output of show ip igmp proxy TABLE 18 Field Description Address Group address. Mode Multicast group mode. Can be "exclude" or "include." Source count Number sources in the given mode. A group in IGMP v2 has exclude mode with zero sources.
The report shows the following information. Output of show ip igmp proxy stats TABLE 20 Field Description Intf Interface genQv1 RX IGMP v1 general query received on proxy interface. genQv2 RX IGMP v2 general query received on proxy interface. genQv3 RX IGMP v3 general query received on proxy interface.
Address field contains the multicast address of interest, and the Number of Sources (N) field contains zero. • A "Group-and-Source-Specific Query" is sent by a multicast router to learn if any neighboring interface desires reception of packets sent to a specified multicast address, from any of a specified list of sources.
An interface or router sends the queries and reports that include its IGMP version specified on it. It may recognize a query or report that has a different version. For example, an interface running IGMP V2 can recognize IGMP V3 packets, but cannot process them.
In this example, the second line sets IGMP V2 on virtual routing interface 3. However, the third line set IGMP V3 on ports 1/3 through 1/7 and port e2/9. All other ports in this virtual routing interface are configured with IGMP V2. Syntax: [no] ip igmp port-version version-number ethernet port-number Enter 1, 2, or 3 for version-number .
Creating a static IGMP group You can configure one or more physical ports to be a permanent (static) member of an IGMP group based on the range or count. To configure two static groups starting from 226.0.0.1, enter either this command: Device(config)# interface ethernet 1/5 Device(config-if-e1000-1/5)# ip igmp static-group 226.
Setting the group membership time Group membership time defines how long a group will remain active on an interface in the absence of a group report. Possible values are from 5 - 26000 seconds and the default value is 260 seconds. To define an IGMP membership time of 240 seconds, enter the following.
If the tracking and fast leave feature is enabled, you can display the list of clients that belong to a particular group by entering commands such as the following.
Clearing the IGMP group membership table To clear the IGMP group membership table, enter the following command. device# clear ip igmp cache Syntax: clear ip igmp [ vrf vrf-name ] cache This command clears the IGMP membership for the default router instance or for a specified VRF.
Enter ve and its number , or ethernet and its port-address to display information for a specific virtual routing interface, or ethernet interface. The tunnel num parameter specifies a GRE tunnel interface that is being configured. The GRE tunnel interface is enabled under the router PIM configuration.
Displaying IGMP traffic status To display the traffic status on each virtual routing interface, enter the following command. device# show ip igmp traffic Recv QryV2 QryV3 G-Qry GSQry MbrV2 MbrV3 Leave.
Syntax: clear ip igmp [ vrf vrf-name ] traffic This command clears all the multicast traffic information on all interfaces on the device. Use the vrf option to clear the traffic information for a VRF instance specified by the vrf-name variable. T Displaying IGMP settings To display global IGMP settings or IGMP settings for a specified VRF.
Output of show ip igmp settings (Continued) TABLE 25 This field Displays Last Member Query Interval The Last Member Query Interval is the Max Response Time used to calculate the Max Resp Code inserted into Group-Specific Queries sent in response to Leave Group messages.
To configure a single SSM group address, enter the following command under the router pim configuration: device(config)#router pim device(config-pim-router)#ssm-enable range 232.1.1.1/8 Syntax: [no] ssm-enable range group-address address-mask The group-address parameter specifies the multicast address for the SSM address range.
The acl-id/acl-name parameter specifies the ACL id or name used to configure multiple SSM group ranges. To disable the SSM mapping range ACL, use the [no] form of this command. NOTE The ssm-enable range acl-id acl-name or command also supports IPv6 traffic.
Configuring an ACL for IGMPv2 SSM mapping You can use either a standard or extended ACL to identify the group multicast address you want to add source addresses to when creating a IGMPv3 report. For standard ACLs, you must create an ACL with a permit clause and the ip-source-address variable must contain the group multicast address.
The acl-id variable specifies the ACL ID that contains the group multicast address. The source-address variable specifies the source address that you want to map to the group multicast address specified in the ACL. The no option is used to delete a previously configured SSM map.
IPv6 Multicast Protocols ● Supported IPv6 Multicast Features............................................................................... 163 ● IPv6 PIM Sparse .....................................................................................
IPv6 PIM Sparse IPv6 Protocol Independent Multicast (PIM) Sparse is supported. IPv6 PIM Sparse provides multicasting that is especially suitable for widely distributed multicast environments.
between the receiver and the source (the Shortest Path Tree, or SPT) and uses the SPT for subsequent packets from the source to the receiver. The device calculates a separate SPT for each source-receiver pair. NOTE It is recommended that you configure the same ports as candidate BSRs and RPs.
NOTE It is recommended that you configure the same device as both the BSR and the RP. IPv6 PIM-Sparse mode To configure a device for IPv6 PIM Sparse, perform the following tasks: • Identify the Layer 3 switch as a candidate sparse Rendezvous Point (RP), if applicable.
Configuring BSRs In addition to the global and interface parameters configured in the prior sections, you must identify an interface on at least one device as a candidate PIM Sparse Bootstrap Router (BSR) and a candidate PIM Sparse Rendezvous Point (RP).
The num parameter specifies the number of seconds and can be from 10 - 65535. The default is 60. Use the no option to disable a timer that has been configured. Configuring candidate RP Enter a command such as the following to configure the device as a candidate RP.
If you explicitly specify the RP, the device uses the specified RP for all group-to-RP mappings and overrides the set of candidate RPs supplied by the BSR. NOTE Specify the same IP address as the RP on all IPv6 PIM Sparse routers within the IPv6 PIM Sparse domain.
To disable embedded RP support for a specified VRF, enter the following commands. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# no rp-embedded Syntax: [no] rp-embed.
To specify how frequently the candidate RP configured on the device sends candidate RP advertisement messages to the BSR for a specified VRF, enter commands such as the following.
Setting the prune wait interval The prune-wait command allows you to set the amount of time the PIM router should wait for a join override before pruning an Outgoing Interface List Optimization (OIF) from the entry. To change the default join override time to 2 seconds, enter commands such as the following.
To change the default register probe time to 20 seconds, enter commands such as following. device(config)# ipv6 router pim device(config-ipv6-pim-router)# register-probe-time 20 To change the default register probe time to 20 seconds for a specified VRF, enter commands such as the following.
Enabling Source-specific Multicast Using the Any-Source Multicast (ASM) service model, sources and receivers register with a multicast address. The protocol uses regular messages to maintain a correctly configured broadcast network where all sources can send data to all receivers and all receivers get broadcasts from all sources.
• If more than one router has the same DR priority on a subnet (as in the case of default DR priority on all), the router with the numerically highest IP address on that subnet will get elected as the DR. • The DR priority information is used in the DR election only if all the PIM routers connected to the subnet support the DR priority option.
Join/Prune interval : 60 Inactivity interval : 180 Hardware Drop Enabled : Yes Prune Wait Interval : 3 Bootstrap Msg interval : 60 Candidate-RP Msg interval : 60 Register Suppress Time : 60 Register P.
Syntax: show ipv6 pim [ vrf vrf-name ] sparse The vrf parameter allows you to configure IPv6 PIM on the virtual routing instance (VRF) specified by the vrf-name variable.
Output from the show ipv6 pim sparse command (Continued) TABLE 26 Field Description Candidate-RP Msg interval Number of seconds the candidate RP configured on the Layer 3 switch sends candidate RP advertisement messages to the BSR. Default is 60 seconds.
Syntax: show ipv6 pim [ vrf vrf-name ] interface [ ethernet slot/portnum | loopback num | ve num ] The vrf option allows you to display multicast boundary information for the VRF instance identified by the vrf-name variable. The ethernet port-number parameter specifies the physical port.
Output from the show ipv6 pim group command TABLE 28 Field Description Total number of Groups Lists the total number of IPv6 multicast groups the device is forwarding.
Output from the show ipv6 pim bsr command (Continued) TABLE 29 Field Description Hash mask length The number of significant bits in the IPv6 multicast group comparison mask. This mask determines the IPv6 multicast group numbers for which the device can be a BSR.
RP: 1be::11:21 group prefixes: ff00:: / 8 Candidate-RP-advertisement period: 60 This example shows information displayed on a device that is a candidate RP. The following example shows the message displayed on a device that is not a candidate RP. device# show ipv6 pim rp-candidate This system is not a Candidate-RP.
------------------------------------------------------------------------------- 1 ff07::c:1 3200:12::32 2 ff07::c:2 3200:12::32 3 ff07::c:3 3200:12::32 Number of group-to-RP mappings: 3 Brocade# Synta.
--------- Static RP count: 1 100::1 Number of group prefixes Learnt from BSR: 0 No RP-Set present Syntax: show ipv6 pim [ vrf vrf-name ] rp-set The vrf parameter allows you to display the RP set for the VRF instance identified by the vrf-name variable.
The vrf parameter allows you to display the IPv6 PIM neighbors for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 pim neighbor command.
For Replication Entry REGPROB - Register In Progress, REGSUPP - Register Suppression Timer MSDPADV - Advertise MSDP, NEEDRTE - Route Required for Src/RP, PRUN - DM Prune Upstream Interface Flags: IM -.
Output parameters of the show ipv6 pim mcache command (Continued) TABLE 35 Field Description Flags Show the flags associated with the forward entry. slow ports ethe Shows the forwarding port ID of the mcache entry which is in the software forwarding path.
Brocade#show ipv pim vrf eng counter Event Callback: DFTVlanChange : 0 VlanPort : 0 LP to MP IPCs: SM_REGISTER : 8315 MCAST_CREATE : 0 S_G_AGEOUT : 3 WRONG_IF : 0 ABOVE_THRESHOLD: 0 MCAST_FIRST_DATA :.
pim/dvm intf. group 64 0 64 0 14848 0 24 64 pim/dvm global group 512 0 512 0 14848 6700 46 64 repl entry(Global) 1024 2 1022 0 237568 40644 49 1024 MLD Resources(All Vrfs): groups 1024 0 1024 0 4096 7.
System-max limit for SG entries: 6144 Syntax: show ipv6 pim [ all-vrf | [ vrf vrf-name ] ] hw-resource The vrf parameter allows you to display hardware resource information for the VRF instance identified by the vrf-name variable. The following table displays the output from the show ipv6 pim all-vrf hw-resource command.
Output from the show ipv6 pim traffic command (Continued) TABLE 39 Field Description Join-Prune The number of Join or Prune messages sent or received on the interface. NOTE Unlike PIM dense, PIM Sparse uses the same messages for Joins and Prunes. Assert The number of Assert messages sent or received on the interface.
The clear IPv6 pim rp-map command allows you to update the entries in the static multicast forwarding table immediately after making RP configuration changes.
The system-max pim6-hw-mcache command sets the maximum number of SG entries that are allowed in the hardware. Configuring a static multicast route within a VRF You can configure a static multicast route within a virtual routing instance (VRF). 1. Configure a VRF.
The following examples show how to configure the route precedence and display the route-precedence setting. Device(config-ipv6-pim-router)#route-precedence mc-non-default mc-default uc-non- default uc.
device(config-ipv6-pim-router)# rp-address 1001::1 device(config-ipv6-pim-router)# anycast-rp 1001::1 my-anycast-rp-set-acl To configure PIM Anycast RP for a specified VRF, enter the commands as shown in the following example.
Displaying information for an IPv6 PIM Anycast RP interface To display information for an IPv6 PIM Anycast RP interface, enter the show ipv6 pim anycast-rp command.
The source list and filter mode are created when the IPv6 querier router sends a query. The querier router is the one with the lowest source IPv6 address. It sends out any of the following queries: • General query - The querier sends this query to learn all multicast addresses that need to be listened to on an interface.
To define an MLD group membership time of 2000 seconds for a specified VRF, enter the following commands. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# ipv6 mld gro.
Setting the query interval You can define the frequency at which MLD query messages are sent. For example, if you want queries to be sent every 50 seconds, enter a command such as the following. device(config)# ipv6 mld query-interval 50 Syntax: [no] ipv6 mld query-interval seconds The seconds variable specifies the MLD query interval in seconds.
To set the robustness for a specified VRF, enter the following commands. device(config)# ipv6 router pim vrf blue device(config-ipv6-pim-router-vrf-blue)# ipv6 mld robustness 3 Syntax: [no] ipv6 router pim [ vrf vrf-name ] The vrf parameter specifies the virtual routing instance (VRF) specified by the variable vrf-name .
To configure two static groups, starting from ff0d::1, without having to receive an MLDv1 report on a virtual Ethernet interface, enter either this command: Device(config-if-e1000-1/5)# ipv6 mld stati.
Displaying MLD group information To display the list of multicast groups, enter a command such as the following. device #show ipv6 mld group Total 2 groups --------------------------------------------.
e1/1/2 0 2 - Self 0 0 No v220 0 2 - Disabled e1/1/1 3 2 - Self 0 12 No Syntax: show ipv6 mld [ vrf vrf-name ] interface [ ethernet port-number | ve num ] The vrf parameter allows you to display MLD parameters on an interface for the VRF instance identified by the vrf-name variable.
Max Response Time : 10s Group Membership Time : 260s Operating Version : 2 Configured Version : 0 Robustness Variable : 2 Last Member Query Interval: 1s Last Member Query Count: 2 Older Host Present T.
Output from the show ipv6 mld vrf cs static command TABLE 44 Field Description Group Address The address of the multicast group. Interface Port List The physical ports on which the multicast groups are received. Displaying MLD traffic To display information on MLD traffic, enter a command such as the following.
Output from the show ipv6 mld traffic command (Continued) TABLE 45 Field Description Is_EX Number of source addresses that were excluded in the traffic. ToIN Number of times the interface mode changed from exclude to include. ToEX Number of times the interface mode changed from include to exclude.
Configuration considerations • Only one ACL can be bound to any interface. • Normal ACL restrictions apply as to how many software ACLs can be created, but there is no hardware restrictions on ACLs with this feature.
Displaying multicast boundaries To display multicast boundary information, use the show ipv6 pim interface command. In this example, abc is the name of the access list.
IP Multicast Commands ● clear ip mroute.............................................................................................................. 209 ● clear ipv6 mroute..........................................................................
Modes Privileged EXEC mode Usage Guidelines After mroutes are cleared from an IP multicast routing table, the best static mroutes are added back to it.
ip max-mroute Configures a limit to the number of multicast routes supported. Syntax ip max-mroute num no ip max-mroute Command Default The default is no limit.
Configures a virtual interface as the route path. tunnel num Configures a tunnel interface as the route path. cost Configures a metric for comparing the route to other static routes in the static route table that have the same destination. The range is 1-16; the default is 1.
Configures a metric for comparing the route to other static routes in the static route table that have the same destination. The range is 1-16; the default is 1. distance distance-value Configures the route's administrative distance. The range is 1-255; the default is 1.
ip mroute next-hop-recursion Configures the recursion level while using static mroutes to resolve a static mroute next hop. Syntax ip mroute [ vrf vrf-name ] next-hop-recursion 1-10 no ip mroute [ vrf vrf-name ] next-hop-recursion 1-10 Command Default The recursion level for resolving a static mroute next hop is 3.
After the hardware forwarding database (FDB) entry is made, the multicast traffic is switched only to the VLAN hosts that are members of the multicast group. This can avoid congestion and loss of traffic on the ports that have not subscribed to this IPv4 multicast traffic.
Parameters vrf vrf-name Configures a static mroute for this virtual routing and forwarding (VRF) route. ipv6-address-prefix/prefix-length Configures the destination IPv6 address and prefix for which the route should be added. ethernet Configures an Ethernet interface as the route path.
Configures a static mroute for this virtual routing and forwarding (VRF) route. ipv6-address-prefix/prefix-length Configures the destination IPv6 address and prefix for which the route should be added. next-hop address Configures a next-hop address as the route path.
History Release version Command history 8.0.10a This command was introduced. ipv6 mroute next-hop-recursion Configures the recursion level while using static mroutes to resolve a static mroute next hop.
Usage Guidelines NOTE This command is supported only on ICX 6650 devices. The no form of this command enables the flooding of unregistered IPv6 multicast frames in an MLD- snooping-enabled VLAN.
You must configure four parameters indicating the four different route types. If you want to specify that a particular route type not be used, configure the none keyword to fill the precedence table.
Specifies a VRF route. static Specifies a static multicast route. connected Specifies a directly attached (connected) multicast route. ip-subnet [ mask ] Specifies an IP address.
show ip multicast optimization Displays Internet Group Management Protocol (IGMP) snooping hardware resource-sharing information. You can configure it to display the availability of IP multicast (IPMC) group indexes in the hardware and how it is been used and shared.
Examples This example displays information for configured multicast routes: Device(config)# show ip static mroute IP Static Routing Table - 2 entries: IP Prefix Next Hop Interface Dis/Metric/Tag Name *20.20.20.0/24 220.220.220.1 - 1/1/0 20.20.20.0/24 50.
This example displays information for static IPv6 multicast routes: Device(config)# show ipv6 mroute static Type Codes - B:BGP C:Connected S:Static Type IPv6 Prefix Next Hop Router Interface Dis/Metri.
History Release version Command history 8.0.10 This command was introduced. show ipv6 static mroute Displays information for configured IPv6 multicast routes. Syntax show ipv6 static mroute [ vrf vrf-name ] ipv6-address-prefix/prefix-length Parameters vrf vrf-name Specifies a VRF route.
show ipv6 static mroute 226 FastIron Ethernet Switch IP Multicast Configuration Guide 53-1003085-02.
Index C command clear ip multicast counters 35 clear ip multicast mcache 34 clear ip multicast vlan 34 ip multicast 20 ip multicast age-interval 22 ip multicast leave-wait-time 23 ip multicast max-res.
configuration 38 , 65 disabling on a VLAN 39 , 66 displaying errors 27 displaying information 39 , 66 displaying information for a specific group or source group pair 41 displaying information on a La.
Een belangrijk punt na aankoop van elk apparaat Brocade Communications Systems IPMC5000PEF (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen Brocade Communications Systems IPMC5000PEF heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens Brocade Communications Systems IPMC5000PEF vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding Brocade Communications Systems IPMC5000PEF leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over Brocade Communications Systems IPMC5000PEF krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van Brocade Communications Systems IPMC5000PEF bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de Brocade Communications Systems IPMC5000PEF kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met Brocade Communications Systems IPMC5000PEF . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
