This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| fintech:multicast [2023/04/13 18:33] – jotasandoku | fintech:multicast [2025/05/18 10:02] (current) – jotasandoku | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | * Cisco fintech architecture: | + | * Multicast summary |
| TECH NOTES: | TECH NOTES: | ||
| Line 29: | Line 29: | ||
| * “BLOCK_OLD_SOURCE” Record type 6 indicating it is no longer interested to hear multicast traffic to that group from specific host. | * “BLOCK_OLD_SOURCE” Record type 6 indicating it is no longer interested to hear multicast traffic to that group from specific host. | ||
| - | MEMBERSHIP-QUERY: | + | MEMBERSHIP-QUERY |
| * Sent by the last hop router. Normally when a listener has left a group and it wants to know if there are still anybody in there interested on the group. | * Sent by the last hop router. Normally when a listener has left a group and it wants to know if there are still anybody in there interested on the group. | ||
| * General Query – to learn complete multicast reception state of the neighboring interface. Sent to 224.0.0.1 | * General Query – to learn complete multicast reception state of the neighboring interface. Sent to 224.0.0.1 | ||
| Line 94: | Line 94: | ||
| * DESIGNATED ROUTER: Routers configured for IP multicast send PIM hello messages to determine which router will be the designated router (DR) for each LAN segment (subnet). The hello messages contain the router' | * DESIGNATED ROUTER: Routers configured for IP multicast send PIM hello messages to determine which router will be the designated router (DR) for each LAN segment (subnet). The hello messages contain the router' | ||
| * in each LAN segment where one or more multicast enabled routers are connected to you can see the three roles of PIM DR, IGMP querier, PIM forwarder. | * in each LAN segment where one or more multicast enabled routers are connected to you can see the three roles of PIM DR, IGMP querier, PIM forwarder. | ||
| - | * **PIM DR has to represent the LAN segment/ | + | |
| * QUERIER: When a multicast-enabled router first becomes active on a subnet, it assumes that it is the Querier — the router responsible for sending all General and Group-Specific Queries to the subnet. When there are multiple routers, the rule for electing the Querier is simple: The router whose connected interface has the **lowest IP address is the Querie**. [[http:// | * QUERIER: When a multicast-enabled router first becomes active on a subnet, it assumes that it is the Querier — the router responsible for sending all General and Group-Specific Queries to the subnet. When there are multiple routers, the rule for electing the Querier is simple: The router whose connected interface has the **lowest IP address is the Querie**. [[http:// | ||
| + | |||
| show ip igmp snooping querier | show ip igmp snooping querier | ||
| Line 277: | Line 278: | ||
| * pim cannot be enabled in loopback interfaces. Nonetheless is not required to enable RP. | * pim cannot be enabled in loopback interfaces. Nonetheless is not required to enable RP. | ||
| - | This is for static and BSR RP: | + | ! This is for static and BSR RP: |
| interface Vlan100 | interface Vlan100 | ||
| ip address 10.1.8.3/24 | ip address 10.1.8.3/24 | ||
| Line 302: | Line 303: | ||
| spt-threshold infinity | spt-threshold infinity | ||
| ssm disable | ssm disable | ||
| + | |||
| + | ---- | ||
| + | __IPV6 MULTICAST__ | ||
| + | * PIM > IPv6 PIM | ||
| + | * **IGMPv2 > MLDv1** | ||
| + | * **IGMPv3 > MLDv2** | ||
| + | |||
| + | ipv6 multicast-routing | ||
| + | show ipv6 mroute | ||
| + | ! | ||
| + | show ipv6 pim neighbor | ||
| + | ! | ||
| + | show ipv6 mld group | ||
| + | show ipv6 mld interface g0/0 | ||
| + | show ipv6 mld traffic | ||
| + | |||
| + | |||
| ---- | ---- | ||