srzaizats "Network Computing - Understanding IPV6: What Is Solicited Node Muticast? InformatiorWeek Denise Fishbume Commentary Connect Directly bad BS scowments connent Now Denise Fishburne lays down the basics of solicited-node multicast, which provides the functionality for Neighbor Discovery in IPv6 addressing. IPV6 solicited-node multicast somtimes seems to confuse those new to IPV6 in the beginning. | think this is because it seems so foreign and new. In this post, we will explore exactly what IPvé's solicited- node multicast is and the rules of creating such an address as told to us by RFC 4291 However, before we start on what's new and different, let's look at what solicited-node multicast has in common with IPv4 and IPV6 constructs that we already know. In this blog post, we looked at IPv6 link-local scope multicast addresses, One of the examples was FFO2::A. This address is for all devices on a wire that want to "talk" EIGRP with one another. Focusing specifically on FFO2::A and how routers join it, we can see and say three things: + Local: FF02::A is local to the wire. + Join: Each device "joins" FFO2::A by just “deciding to listen" to the IPv6 link-local scope multicast address FFO2::A. Then, by extension, it listens to the corresponding MAC address for that multicast IPv6 address (33:33:00:00:00:0A). + Common interest: As we can see, these varying groups have something in common that they would all like to hear about. For FF02::A, the common interest - the "connection" among the devices joining that group -- is that they all want to listen to or participate in EIGRP. Guess what? Solicited-node multicast has all those things, too. + Solicited-node multicast is also /ocal to the wire. + Each device joins a solicited-node multicast group address by just "deciding to listen” to the IPV6 solicited-node multicast address and then to the corresponding MAC address for that multicast IPv6 group. + Devices that join a specific solicited-node multicast address share a common interest hitp:wnw.networkcomputing.com/networkinglunderstandingiov6-what-is-soicted-node-mulicastia‘¢di19157037prnt=yes uasrzaizats "Network Computing - Understanding IPV6: What Is Solicited Node Muticast? Solicited-Node| Multicast Let's do these introductions properly. As RFC 4291 section 2.7.1 states: Solicited-node multicast address are computed as a function of a node's unicast and anycast addresses. A solicited-node multicast address is formed by taking the low-order 24 bits of an address (unicast or anycast) and appending those bits to the prefix FF02:0: -FF00::/104 resulting ina multicast address in the range FF02:0:0:0:0:1:FF00:0000 to FF02:0:0:0:0:1:FFFF:FFFF For example, the solicited-node multicast address corresponding to the IPvé address 4037::01:800:200E:8C6C is FF02::1:FFOE:8C6C. IPv6 addresses that differ only in the high-order bits (o.g., due to multiple high-order prefixes associated with different aggregations) will map to the same solicited-node address, thereby reducing the number of multicast addresses a node must join. A node is required to compute and join (on the appropriate interface) the associated solicited-node multicast addresses for all unicast and anycast addresses that have been configured for the node's interfaces (manually or automatically) So, what did we just read? Let's break this down, Here's RouterA with one IPv6 address. a FESO: Link-Local As we can see, RouterA has one IPv6 unicast address defined, link-local FE80::1. According to what we read above from RFC, 4291 RouterA is “required to compute and join" on interface gigi/0/1 “the bit: ew networkcamputing.cometworknglindertandng ipv6-what ie soled node-mulicasvald1315703prnt=yes 2srzaizats "Network Computing - Understanding IPV6: What Is Solicited Node Muticast? associated solicited-node multicast address.” So we must compute first and then join Compute “A solicited-node multicast address is formed by taking the low-order 24 bits of an address (unicast or anycast) and appending those bits to the prefix FF02:0:0:0:0:1:FF00::/104 resulting in a multicast, address." The compute is two steps -- simple enough, + Low-order 24 bits for the IPV6 link-local unicast address FE80::1 is ::1. That was easy. + Append ::1 to FF02:0:0:0:0:1:FF00::/104, and we get FF02:0:0:0:0:1:FF00:1 or FFO2::1:FFOO:1. Join Router is now supposed to "join" this IPV6 solicited-node multicast group (FFO2::1:FFO0:1) on the corresponding interface gig1/0/1. As we can see below, RouterA does join the associated IPv6 solicited-node multicast group (FF02::1:FF00:1) for IPV6 unicast address FE80::1. RouterA#sh ipv6 interface gig1/0/1 GigabitEthernet1/0/1 is up, line protocol is up IPV6 is enabled, link-local address is FE80::1 No Virtual link-local address(es): No global unicast address is configure Joined group address(es): ‘As we can see, RouterA now has 2 IPV6 unicast addresses: + IPV6 link-local address FE80::1 + IPvé global address 2001:DB8::AB:1 eect Remember that, according to what we read above from RFC 4291, RouterA is "required to compute and join" on interface gig1/0/1 "the associated solicited-node multicast addresses for all unicast and anycast addresses that have been configured.” Since RouterA has already computed and joined the associated IPV6 solicited-node multicast group (FF02::1:FF00:1) for IPv6 unicast address FE80::1, we just have to compute and join for the newly hitp:wnw.networkcomputing.com/networkinglunderstandingiov6-what-is-soicted-node-mulicastia‘¢di19157037prnt=yes aiasrzaizats "Network Computing - Understanding IPV6: What Is Solicited Node Muticast? added IPv6 global unicast address, 2001:DB8::AB:1 So we must compute first and then join Compute + Low-order 24 bits for the IPV6 link-local unicast address 2001:DB8::AB:1 is ::AB:1. + Append ::AB:1 to FF02:0:0:0:0:1:FF00::/104, and we get FF02:0:0:0:0:1:FFAB: Join RouterA is now supposed to join this IPV6 solicited-node multicast group (FF02::1:FFAB:1) on the corresponding interface gig1/0/1. As we can see below, RouterA has now joined both IPv6 solicited- node multicast addresses. RouterA#sh ipv6 int gigi /0/1 GigabitEthernet1/0/1 is up, line protocol is up IPvé6 is enabled, link-local address is FEBO::1. No Virtual link-local address(es): Global unicast address(es): 2001:DB8::AB:1, subnet is 2001:DB8::/64 Joined group address(es): Why? Of course, an obvious question here is why we need a device to compute and join the IPv6 solicited- node multicast address for each and every IPV6 unicast and anycast on an interface? Simply put, itis the basis for Neighbor Discovery (RFC 4861). In my next post, we will revisit RouterA and RouterB and see an example of how a solicited-node multicast address is used, Denise "Fish” Fishburne, (CCIE #2639, CCDE #2009:0014, Cisco Champion) is a team lead with Cisco's Customer Proof of Concept Lab in Research Triangle Park, N.C. Fish loves playing in the lab, troubleshooting, leaming, and passing it on. She has been regular speaker at .. View Full Bio COMMENT | EMAIL THIS | PRINT | RSS MORE INSIGHTS Webcasts # Measuring Cyber Risk Through Security Data Analysis ‘# NoSQL's role in solving Moody's Analytics big data challenge MORE WEBCASTS White Papers #5 Strategies for Modern Data Protection # State of the CISO: CISOs Face an Uphill Battle in the C-Suite MORE WHITE PAPERS. Reports + [InformationWeek & Dark Reading Repor!] 2015 Strategic Security Survey Results ++ [Gartner Report] Hype Cycle for Enterprise Mobile Security MORE REPORTS Copyright © 2015 UBM Electronics, A UBM company, All rights reserved. Privacy Policy | Terms of Service hitp:wnw.networkcomputing.com/networkinglunderstandingiov6-what-is-soicted-node-mulicastia‘¢di19157037prnt=yes as