{"id":1958,"date":"2017-05-06T15:40:12","date_gmt":"2017-05-06T15:40:12","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=1958"},"modified":"2022-10-19T16:10:43","modified_gmt":"2022-10-19T23:10:43","slug":"ipv6-neighbor-discovery-cache-part-2-of-2","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/","title":{"rendered":"IPv6 Neighbor Discovery Cache (part 2 of 2)"},"content":{"rendered":"

Last time around we reviewed some of\u00a0the technical details behind the IPv6 Neighbor Discovery cache. This time we\u2019ll look at how to observe the IPv6 Neighbor Discovery cache in operation.<\/p>\n

IPv6 was conceived and designed\u00a0primarily to overcome IPv4\u2019s\u00a0limited total number\u00a0of unique node\u00a0addresses and the address exhaustion that has resulted from this. But the redesign was also an opportunity to improve other aspects of\u00a0IPv4. In particular, the original IPv4 protocol offered no inherent\u00a0auto-addressing functionality; i.e., the ability of nodes to obtain their own unique Layer 3\u00a0address, whether local or global in scope. DHCP was created as a workaround for this lack of functionality\u00a0but the designers of IPv6 wanted to include a stand-alone\u00a0auto-addressing function in the protocol definition (i.e., one that wouldn\u2019t require an additional standard\/application like DHCP). Stateless Address Auto Configuration (SLAAC) is the mechanism built-in to IPv6 that provides this. While\u00a0IPv6 Neighbor Discovery works perfectly well on a single link, providing addresses of link-local scope (e.g., fe80::a43e:44ff:fe16:565a), for SLAAC to be useful,\u00a0a router on the link must send Router Advertisements to announce the availability of an\u00a0IPv6 prefix with a non-local scope (e.g., a\u00a0GUA or ULA prefix).<\/p>\n

To demonstrate this mechanism, here\u2019s a very simple virtual network topology (using GNS3) with one router and one host connected via a switch:<\/p>\n

\"Virtual<\/p>\n

The interface configuration on the router is simply a GUA address\/prefix from the documentation range: 2001:db8::1\/64:<\/p>\n

\"Configuration<\/p>\n

In addition, we need to enter the global command\u00a0ipv6 unicast-routing<\/em><\/strong> to enable router advertisements. Otherwise, SLAAC will not work and the host will not auto-configure an address:<\/p>\n

\"IPv6<\/p>\n

We can now verify on the host that it has configured itself with an IPv6 address using the prefix announced in the router advertisement:<\/p>\n

\"IPv6<\/p>\n

Notice that two GUA addresses and one link-local address have been self-configured. Note also that none of these addresses appear to use the EUI-64 method of construction (the absence of the “ff:fe” in nibbles 23-26 indicates this). Instead, the link-local address and one of the GUA addresses appear to be constructed using the method from RFC 3972,\u00a0Cryptographically Generated Addresses. These addresses are permanent and would only change if the operating system were to be reinstalled. The remaining GUA address is a temporary address and will change once we reboot the system.<\/p>\n

Now that we have IPv6 addresses configured on the router and the node, we can examine the neighbor discovery cache on each device and observe its state as well as how that state changes.<\/p>\n

The command to examine the neighbor discovery cache on the router is\u00a0show ipv6 neighbors <interface n\/n><\/em><\/strong>:<\/p>\n

\"Show<\/p>\n

The first column lists the\u00a0IPv6 address<\/strong>\u00a0in the neighbor discovery cache.<\/p>\n

The next column is the\u00a0age<\/strong>\u00a0of the entry in minutes.<\/p>\n

The next column shows the\u00a0link-layer address<\/strong>\u00a0the IPv6 address in the first column is mapped to.<\/p>\n

The next column shows the\u00a0state<\/strong>\u00a0of the entry. As covered in the previous post, the possible entry states are as follows<\/p>\n

    \n
  1. Incomplete<\/li>\n
  2. Reachable<\/li>\n
  3. Stale<\/li>\n
  4. Delay<\/li>\n
  5. Probe<\/li>\n<\/ol>\n

    Notice that the three entries correspond to the addresses assigned on the host. Two of them are\u00a0reachable<\/strong>\u00a0according to the status column, while one entry is marked as\u00a0stale<\/strong>.<\/p>\n

    Recall that a status of\u00a0reachable<\/strong>\u00a0indicates that a positive confirmation of reachability for the associated ND cache entry was received within a certain time interval (defined as the ReachableTime).<\/p>\n

    Meanwhile, a\u00a0stale<\/strong>\u00a0ND cache entry means the ReachableTime has elapsed before a subsequent confirmation of reachability has been received.<\/p>\n

    Recall also that confirmation of reachability is accomplished by an upper layer protocol\u2019s use of the ND entry. We can demonstrate this by sending an ICMPv6 ping to the entry\u2019s corresponding address:<\/p>\n

    \"ICMPv6<\/p>\n

    Running the\u00a0show ipv6 neighbors<\/em><\/strong>\u00a0command again now shows the updated cache entry:<\/p>\n

    \"Show<\/p>\n

    Now let\u2019s look at the neighbor discover cache on the host. The command for most Linux systems\u00a0is\u00a0ip -6 neigh show<\/em><\/strong>:<\/p>\n

    \"Neighbor<\/p>\n

    As with our router example, we\u2019ll go ahead and send a ping to force the IPv6 neighbor discovery cache state to change for the entry that is currently listed as\u00a0stale<\/strong>:<\/p>\n

    \"Neighbor<\/p>\n

    Upon completion of the ping, we run the\u00a0ip -6 neigh show<\/em><\/strong>\u00a0command again and notice that the status of the entry is now listed as\u00a0delay<\/strong>.<\/p>\n

    Recall from our last post that a status of\u00a0delay<\/strong>\u00a0indicates that, though the ReachableTime has expired, a\u00a0packet was recently sent to the cache entry\u2019s address\u00a0by an upper-layer protocol. After a defined interval, a Neighbor Solicitation is sent and the ND cache entry is changed to\u00a0probe<\/em>\u00a0status. The\u00a0delay<\/em>\u00a0status merely provides time for upper-layer protocols to potentially refresh the cache entry without resorting to a Neighbor Solicitation.<\/p>\n

    Had we been running a packet capture, after sending the ping we would see the router issue a Neighbor Solicitation and the entry state would briefly change to\u00a0probe<\/strong>\u00a0before updating to\u00a0reachable\u00a0<\/em><\/strong>again.<\/p>\n

    As with IPv4 ARP it\u2019s possible to statically map an IPv6 neighbor entry. The syntax of the command to do so in Cisco IOS is\u00a0ipv6 neighbor <IPv6 address> <interface n\/n> <48-bit hardware address><\/em><\/strong>:<\/p>\n

    \"IPv6<\/p>\n

    After configuring a static IPv6 ND entry, the ND cache looks identical but with two key exceptions: first, the age is shown as a hyphen, indicating that the entry is static (and will not age out). According to the Cisco website “Static entries in the IPv6 neighbor discovery cache are not modified by the neighbor discovery process.\u201d<\/p>\n

    The two possible states for statically defined entries are:<\/p>\n

    INCMP (Incomplete)–The interface for this entry is down.<\/p>\n

    REACH (Reachable)–The interface for this entry is up.<\/p>\n

    To view overall statistics for the IPv6 ND cache use the command\u00a0show\u00a0ipv6 neighbor statistics<\/em><\/strong>:<\/p>\n

    \"IPv6<\/p>\n

    As evident, Cisco provides data for ND cache entries that goes beyond the formally defined ND cache entry states we\u2019ve listed so far. For instance,\u00a0gleaned<\/em><\/strong>\u00a0entries are \u201cthe number of ND neighbor entries gleaned (that is, learned from a neighbor NA or other ND packet).\u201d\u00a0High-water<\/em><\/strong>\u00a0indicates the “maximum amount (so far) of ND neighbor entries in ND cache.\u201d Values beyond the baseline for either of these fields may be used to detect excessive ND activity on the attached segments \u2014 activity which could indicate an underlying problem. For more info on these commands, check out the\u00a0Cisco IPv6 command reference<\/a>.<\/p>\n

    Knowledge of the IPv6 Neighbor Discovery cache, how to observe and modify it, is a critical tool in the belt of the network administrator tasked with deploying and maintaining IPv6. I hope you find the above information useful in helping to enhance your IPv6 administration skills.<\/p>\n

    As always, please leave a comment if you have questions or examples of your own experience with the IPv6 ND cache.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Last time around we reviewed some of\u00a0the technical details behind the IPv6 Neighbor Discovery cache. This time we\u2019ll look at how to observe the IPv6 Neighbor Discovery cache in operation. IPv6 was conceived and designed\u00a0primarily to overcome IPv4\u2019s\u00a0limited total number\u00a0of unique node\u00a0addresses and the address exhaustion that has resulted from this. But the redesign was […]<\/p>\n","protected":false},"author":319,"featured_media":1853,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[17],"tags":[28,38],"class_list":{"0":"post-1958","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-ddi","9":"tag-ipv6","10":"entry"},"acf":[],"yoast_head":"\nIPv6 Neighbor Discovery Cache (part 2 of 2)<\/title>\n<meta name=\"description\" content=\"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"IPv6 Neighbor Discovery Cache (part 2 of 2)\" \/>\n<meta property=\"og:description\" content=\"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2017-05-06T15:40:12+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-10-19T23:10:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"660\" \/>\n\t<meta property=\"og:image:height\" content=\"454\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Tom Coffeen\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Tom Coffeen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/\"},\"author\":{\"name\":\"Tom Coffeen\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\"},\"headline\":\"IPv6 Neighbor Discovery Cache (part 2 of 2)\",\"datePublished\":\"2017-05-06T15:40:12+00:00\",\"dateModified\":\"2022-10-19T23:10:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/\"},\"wordCount\":1150,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/oct-10.jpg\",\"keywords\":[\"DDI\",\"IPv6\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/\",\"name\":\"IPv6 Neighbor Discovery Cache (part 2 of 2)\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/oct-10.jpg\",\"datePublished\":\"2017-05-06T15:40:12+00:00\",\"dateModified\":\"2022-10-19T23:10:43+00:00\",\"description\":\"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/oct-10.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/oct-10.jpg\",\"width\":660,\"height\":454},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/ipv6-neighbor-discovery-cache-part-2-of-2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"IPv6 CoE\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/category\\\/ipv6-coe\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"IPv6 Neighbor Discovery Cache (part 2 of 2)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"name\":\"infoblox.com\\\/blog\\\/\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\",\"name\":\"Infoblox\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"width\":137,\"height\":30,\"caption\":\"Infoblox\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/b299068ee4a9f542d2ad7d59a5b1d5b1\",\"name\":\"Tom Coffeen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_319_1574118081-96x96.jpg\",\"caption\":\"Tom Coffeen\"},\"description\":\"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/tom-coffeen\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"IPv6 Neighbor Discovery Cache (part 2 of 2)","description":"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/","og_locale":"en_US","og_type":"article","og_title":"IPv6 Neighbor Discovery Cache (part 2 of 2)","og_description":"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/","og_site_name":"Infoblox Blog","article_published_time":"2017-05-06T15:40:12+00:00","article_modified_time":"2022-10-19T23:10:43+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg","type":"image\/jpeg"}],"author":"Tom Coffeen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Tom Coffeen","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/"},"author":{"name":"Tom Coffeen","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1"},"headline":"IPv6 Neighbor Discovery Cache (part 2 of 2)","datePublished":"2017-05-06T15:40:12+00:00","dateModified":"2022-10-19T23:10:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/"},"wordCount":1150,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg","keywords":["DDI","IPv6"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/","name":"IPv6 Neighbor Discovery Cache (part 2 of 2)","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg","datePublished":"2017-05-06T15:40:12+00:00","dateModified":"2022-10-19T23:10:43+00:00","description":"The importance of the IPv6 Neighbor Discovery cache often goes unnoticed. Find out how your IPv6 administration skills can be enhanced by utilizing this cache.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/oct-10.jpg","width":660,"height":454},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/ipv6-neighbor-discovery-cache-part-2-of-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.infoblox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"IPv6 CoE","item":"https:\/\/www.infoblox.com\/blog\/category\/ipv6-coe\/"},{"@type":"ListItem","position":3,"name":"IPv6 Neighbor Discovery Cache (part 2 of 2)"}]},{"@type":"WebSite","@id":"https:\/\/www.infoblox.com\/blog\/#website","url":"https:\/\/www.infoblox.com\/blog\/","name":"infoblox.com\/blog\/","description":"","publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.infoblox.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.infoblox.com\/blog\/#organization","name":"Infoblox","url":"https:\/\/www.infoblox.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","width":137,"height":30,"caption":"Infoblox"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/b299068ee4a9f542d2ad7d59a5b1d5b1","name":"Tom Coffeen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_319_1574118081-96x96.jpg","caption":"Tom Coffeen"},"description":"Tom Coffeen is a network engineer, architect, and author with over twenty years of internetwork design, deployment, administration, and management experience. Tom co-founded HexaBuild, an IT consultancy specializing in the advancement of cloud, IoT, and security deployment best practices through IPv6 adoption. Prior to co-founding HexaBuild, Tom was an IPv6 Evangelist and a Distinguished Architect at Infoblox. Before that Tom was the VP of network architecture at the global CDN Limelight Networks where he led their deployment of IPv6. He is also the author of O\u2019Reilly Media\u2019s IPv6 Address Planning.","url":"https:\/\/www.infoblox.com\/blog\/author\/tom-coffeen\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1958","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/users\/319"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=1958"}],"version-history":[{"count":2,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1958\/revisions"}],"predecessor-version":[{"id":8103,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/1958\/revisions\/8103"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/1853"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=1958"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=1958"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=1958"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}